Inbound Calls goes to Trunk Main DID ONLY

[DYHLYU]

Hello, this started to happen after I upgraded to V20.

I have a Trunk with Flowroute and 3 DIDs, routing to 3 different extensions.
Now all DID will route only to the default destination of the main trunk.

The Ring Group and Digital Receptionist doesn't seem to work for me.

Please let me know what information you'll need to check.

Thanks

 

[DYHLYU]

Updates:
Even setting the DIDs directly for users doesn't work.

The default route seems to be overwriting everything.

My goal is to have different DIDs going to different extensions.

Thanks

 

[leejor]

When this happens it usually means that the incoming DID numbers are not exactly matching the DID route number you are using in your rules. When that happens, the call will follow the default route.
You can either confirm the DID being sent, and adjust your rules so he numbers match, or, make use of the * as a leading character in your rules. If incoming digits are expected to be 10 digits, then *9095551234 would accept any additional prefix digits that your provider may be sending.

 

[DYHLYU]

Hello Leejor,

In V20 the Inbound Rule tab is gone and replaced by Call Handling. I cannot specify the incoming DIDs here but just to select from the Trunk's DIDs.
After playing with it for a while it turns out I cannot add the DIDs for Flowroute's Trunk as the notification listed on the Trunk setup page.

I specifically changed my DIDs to e164 format after seeing this yesterday and it screwed up everything.
Dev team If this helps anyone, please update your prompt to have the correct information reflected.
Aslo the Trunk configuration page could use a bit more provider-specific instructions to avoid issues like this.



After changing all the DIDs back to the original format (Country Code + Area Code + Number = 11 digits in total) but without the +, everything worked as expected.

This worked for ONE of my clients. The other client is actually having the numbers setup in e164 format, but the inbound rule has no issues at all. I'm really confused now. Please see the screenshot below.

 

[SteveITS]

Check the medium+ activity log for the number to see what is being sent and how routing is handled. As noted above the * will match any characters so works as a catch-all for providers using different formats.

 

[DYHLYU]

Check the medium+ activity log for the number to see what is being sent and how routing is handled. As noted above the * will match any characters so works as a catch-all for providers using different formats.

Hello Steve,

In V20 the Activity Log is not available, there's only the Event Log and it doesn't show the details.

 

[SteveITS]

In V20 the Activity Log is not available

It's a bit hidden, see: https://www.3cx.com/community/threads/verbose-logging-in-v20.125618/