You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there. This is a continuation of this issue: 197
I'm facing some issues because of the way that I used to solve this, creating a single dispatch rule with no trunks (so, in theory, it should handle any "scenario" or "number")
few weeks ago it was working as expected, but today that I tried again this scenario, all the calls are being rejected by the server.
am I missing any configuration or something?
this is what my inbound trunks look like:
Yes, we now require an inbound trunk with no numbers to handle this case. However, the latest LiveKit version doesn't allow creating these trunks. This PR will fix it: livekit/protocol#890.
Hi there. This is a continuation of this issue: 197
I'm facing some issues because of the way that I used to solve this, creating a single dispatch rule with no trunks (so, in theory, it should handle any "scenario" or "number")
few weeks ago it was working as expected, but today that I tried again this scenario, all the calls are being rejected by the server.
am I missing any configuration or something?
this is what my inbound trunks look like:
and these are my dispatch rules:
Room for call rule:
thanks in advance for any help.
Originally posted by @Kedaqusa1604 in #197 (comment)
The text was updated successfully, but these errors were encountered: