Incoming call goes to wrong extension

[tsmvp]

Gents,

Newbie here but I do have a good understanding of the 3CX system and SIP/etc in general. I cannot see anything wrong with my setup.
I added three SIP trunks to my setup. One from Twillio, two (with two different accounts) from Nexmo.
I have two users created, extensions 001 and 007.
In total the three trunks have 5 numbers. Twillio one number on area code 336, Nexmo1 two numbers on areas code 425 and 250, Nexmo2 two numbers on area code 425.
For example:
Twillio is 336-1234567
Nexmo1 250-1231111, 425-1232828
Nexmo2 250-1232829, 425-1232830

Idea is main number is 425-2830
Extension 007 has 336-1234567 and 425-1232828
Extension 001 has 425-1232829
Extension 888 (FAX) uses the 250-1234567

I can see the proper inbound rules.
If I dial 425-123-2829 call goes to extension 001, no issues
If I dial 336-XXXXXXX call goes to extension 007, no issues
if I dial 250-XXXXXXX call goes to fax (can hear the fax signal)
if I dial 425-123-2839 call goes to the virtual attendant thing (I did not set it up yet but I can see it asks for a voice mail).
if I dial 425-123-2828 call goes to extension 001 and NOT 007 as per the rules, DID assigned to the extensions, etc.
I have no clue why it is doing this.
On the 3CXDialer.log I can see the call coming in and somehow going to that extension and NOT the correct 007 one.
Any ideas/comments?

Thanks!

CR

 

[tsmvp]

I found the problem. For some reason (I am new to Nexmo and not sure if other SIP Trunk providers behave the same way) when using multiple trunks from Nexmo you have to UNCHECK the 'Call Source Identification' in the 'Inbound Parameters' tab for the SIP trunk under the 3CX Management Console. Once I did that for both SIP trunks from Nexmo, everything works as expected and calls get routed to the proper extensions based on the DID.

CR

 

[YiannisH_3CX]

Hello @tsmvp

Glad to see the issue has been resolved but i think you might encounter other issues in the future if you Call source identification is turned off.
Call source identification is used by the PBX to determine to what trunk the incoming call belongs. Because the template uses the providers host and you have 2 trunks from the same provider the PBX could match the call to both trunks. By turning the option off you disabled the check of the PBX and it is now routing randomly to the correct trunk. In the future if more numbers are added and more inbound rules you might not be so lucky.
I would recommend re-enabling the Call source identification option in both trunks and also enabling the option "Use both "Call Source Identification" rules and "Caller Number/Name -> CalledNum" field mappings" in both trunks.
This tells the PBX to check the source of the call against the trunks host and also check the DIDs of each trunk. For this to work DIDs in trunks must be unique.