Solved DID numbers automatically diverting to reception (Catchall)

[GrahamBell1!]

Hi

I am having an issue with a new customer's DID numbers. They are on Version 20. When I assign DID's to users and dial the DID it goes to reception. No matter what DID I use the call diverts to reception. I have tried assigning the DID from the SIP provider to my company and it works fine. If the DID is assigned on the Sip providers side (to the company) but not assigned in the PBX it rings the reception as well. If I unassign the DID from the providers side - it goes dead. There are three other companies using the SIP provider without any issues.

 

[TheodorosG_3CX]

The DID's are configured in E164 format?

 

[GrahamBell1!]

The DID's are configured in E164 format?

Yip - I copied the formats and all setting from another company that works. And used one of the numbers in my company to test. In other words assigned the DID on the SIP supplier side to my company.

 

[TheodorosG_3CX]

Is there any CID rule or exception configured?

 

[AWS2P]

I got same problem, assigned DID to user and the DID is E164 , each call goes directly on main trunk number and not on DID
EXT 16810 is with a DID assigned

in the Trunk settings the DIDs are there and only one is assigned to the user 16810

In trunk Settings ID conversion is enabled too


None of these settings change the incoming route for the DID, it always goes on the "catch all route" which is the main trunk number.

The default route set in the Trunk is the customer Q File so it seems this is always the Q which takes all the incoming traffic

 

[TheodorosG_3CX]

@aws2p What is your provider?

 

[AWS2P]

Supported one Dstny.
I changed trunk setting to department instead of QFile and then the DID is reachable but no more the QFile even affecting the DID number in Qfile Settings.
It gives me the feeling like this is only one route usable at a time and not a mix of DIDs and other routes

 

[AWS2P]

@TheodorosG_3CX @nikolascx
Are you able to reproduce that behavior on your side ?
On SMB I don't see what can be set differently from my side to get this to work as it should.

As now the SMB is ready to be delivered to my customer I should install it to its garage before the weekend , so i'd be happy to know what to do with DIDs not being forwarded to user ext.
Thanks

 

[TheodorosG_3CX]

The only requirement is to configure the number in E164 format.
Is this a Free SMB and you have multiple DID's?

 

[AWS2P]

Hi,
E164 is done, for pbx this is SMB20 and yes we have 1 main number and 4 DIDs

 

[AWS2P]

I finally found out what was the cause, it was on trunk provider side the format number was not E164 by default
so using the 3CX guide I noticed that setting missing (https://www.3cx.fr/docs/trunks-sip/dstny/).

in Ten years using 3CX and Dstny, I never been there to set this and never got a problem, so it's a discovery for me

 

[TheodorosG_3CX]

Glad to know the issue is now resolved