single trunk, multiple DID's

[kurt5132081]

Hi Guys

I have a SIP trunk with a single DID, i have recently requested an additional DID for this trunk, i have added the DID to the trunk and created an inbound rule to the desired destination.

however, when dialing the new DID the call gets routed to the original trunk number instead of the detination specified in the Inbound rule.

is there something i'm missing here?

 

[kurt5132081]

sorry forgot to mention we are running on the latest v15 service pack

 

[pact]

It could be a setting at your SIP provider, it could also be Inbound Settings on your SIP Trunk in 3CX.

Moving from a single DID to multiple can require changes to how your SIP settings are configured, it may have been incorrect before, but it was just handling the only inbound call it received so it didn't matter.

I presume this is not a 'supported' carrier/SIP trunk?

 

[kurt5132081]

Correct it is not a supported carrier/SIP trunk.

i have checked with the SIP provider and they are passing on the two numbers as is with the correct CLI, so im not sure what the issue could be.

 

[mariosM_3CX]

Hello @kurt5132081

Try adding your DIDs with a wildcard if not done so already. So if for example your DID is 123456789, try adding it like *456789
This is to make sure that you are matching the format of the numbers sent by the provider.

 

[kurt5132081]

Hi @mariosM_3CX

thanks for the suggestion, i have tried it and no luck

 

[mariosM_3CX]

Next step would be to run a wireshark capture on the PBX machine and see what the provider is sending in the invite message. It could be that they are not sending the correct DID or your inbound parameters may need some adjustment.

 

[leejor]

The 3CX Activity Log should also show exactly what number (DID,) is being sent.

 

[kurt5132081]

ok after some troubleshooting with the SIP provider, we have managed to get the correct DID displaying in the SIP Invite.

However now the call just rings, see trace below.

 

[leejor]

You said that the original DID was working...compare the Activity Log, of a working, incoming call, with one of the new DIDs, that is not working. What is different.

 

[YiannisH_3CX]

From the screenshot provider above i can see that you are having source identification issues. Who is your provider? Is it IP or authentication based?
In which sip filed does the provider send the DID? You may need to adjust your inbound parameters to match the correct field if this is an un-supported provider