Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dispatch rules not working well for <any> #213

Open
Kedaqusa1604 opened this issue Oct 25, 2024 · 1 comment
Open

Dispatch rules not working well for <any> #213

Kedaqusa1604 opened this issue Oct 25, 2024 · 1 comment
Assignees

Comments

@Kedaqusa1604
Copy link

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:

{FC762B6B-56CE-48F1-B91A-17BBAA397EBC}

and these are my dispatch rules:

{C0888417-44AB-44C6-BA6D-9E8C88839B8C}

Room for call rule:

{
    "name": "Room for call number",
    "trunk_ids": [],
    "hide_phone_number": false,
    "rule": {
        "dispatchRuleCallee": {
            "roomPrefix": "number-",
            "randomize": false,
            "pin": ""
        }
    }
}

thanks in advance for any help.

Originally posted by @Kedaqusa1604 in #197 (comment)

@dennwc
Copy link
Contributor

dennwc commented Nov 25, 2024

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.

@dennwc dennwc self-assigned this Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants