Solved Default inbound routing on SIP Trunk

[GeorgeTs]

Hello,

In 3cx v16 we had noticed that the default inbound routing for numbers that did not have specific Inbound Routes, was defined under SIP Trunks / Route calls to.
Now we are using v18 (Professional Annual) and found out that for numbers belonging to that SIP trunk which did not have specific inbound rules defined, the call was rejected with 404 from 3cx.
Even more strange, there were no respective logs under Dashboard/Activity log.
Is there a way to preserve the default inbound routing defined under "SIP Trunks/Route calls to" for numbers which belong to that provider's SIP trunk, but do not have inbound rules defined?

if not, what is the point of the "Route Calls to" option under the SIP trunk?

Thank you,
George

 

[GeorgeTs]

As a side note, I just realized that simply defining this DID in the SIP Trunk, is using the default routing (Route Calls To).
I guess this is a security feature enabled on v18.
In previous versions - if i recall correctly - regardless if the DID was defined in the SIP trunk or not, if the SIP provider was sending a call to any DID, the default inbound routing for that SIp trunk was used.

 

[ChrisC_3CX]

The way inbound calls are handled should actually be the same as in v16. There are many factors that come into play such as the SIP Provider being used, the SIP Trunk settings, the DIDs configured, etc so if you've noticed differences in behavior it may simply be due to some changes such as removing a DID, or changing the Source Identification settings on the SIP Trunk.

You can read the following documentation which explains how inbound calls are handled in detail: https://www.3cx.com/docs/sip-trunk-inbound-calls/

 

[GeorgeTs]

That works. Thanks a lot @ChrisC_3CX , please close this issue.

 

[ChrisC_3CX]

You're very welcome!

Glad to see you got this sorted!