Call Routing issue

[amannick]

I have configured 2 SIP TRUNKS with 2 Different DID for 2 Different queues but calls keep going to only one extension. I checked with sip provider calls are going to and through respective route but it doesn't seems to be working in 3CX.

 

[amannick]

also this is hosted on 3CX. We have given a trial to the client and first impression is definitely not good. Please help at earliest,

 

[amannick]

Hello everyone

Suggestions?

 

[leejor]

Are the two SIP trunks to different providers? ..or do you mean one SIP trunk (one provider) with two DIDs?

Have you used the 3CX Activity logs to follow the calls through to the destination?

When you create a trunk in 3CX, you assign a default destination. All calls will route to that destination unless you have created a DID rule and the DID number sent by the provider matches the number, in the rule, exactly.

Many use the wildcard *, to replace all digits except the last 6, or 7, in the DID rule. This way the rule will be followed even if the provider adds unexpected prefixes, to the DID number.

 

[amannick]

Are the two SIP trunks to different providers? ..or do you mean one SIP trunk (one provider) with two DIDs?

Have you used the 3CX Activity logs to follow the calls through to the destination?

When you create a trunk in 3CX, you assign a default destination. All calls will route to that destination unless you have created a DID rule and the DID number sent by the provider matches the number, in the rule, exactly.

Many use the wildcard *, to replace all digits except the last 6, or 7, in the DID rule. This way the rule will be followed even if the provider adds unexpected prefixes, to the DID number.

Hello leejor


Thank you for your response.

Yes this is one SIP Trunk Provider But To Different login ID password for each DID. I am not using any prefix or wildcard. I created and checked 2 separate inbound rules but nothing works call keep landing to to same Group where First DID is mapped.



Thanks
Aman

 

[leejor]

If you have one (business) SIP provider, you don't normally have two trunks in 3CX, each attempting to register to the same destination. That just ends up causing problems. Your DIDs should all be able to come over one trunk. If you are talking about a residential provider that does not support DIDs, and is simply providing two different phone numbers, each with a separate registration required, then (separate service), again, you may have some issues.

 

[amannick]

You mean inbound rule will not work?? and Yes one sip provider but number are being authenticated using separate username and password.

 

[leejor]

It all depends on if they are sending DID information with the call. As each number is a separate registration, they may not be sending DID information. As each number is on it's own trunk, you should not really need this anyway. Simply route each trunk to the desired destination.

 

[YiannisH_3CX]

I suspect you are having a conflict with source identification since the source is the same IP/Hostname. The PBX sees that all calls come from the same destination and it somehow matches always with the first trunk.
I am guessing something like the contact: HostPArt of the Invite and this is causing the issue.

Since we are not aware of your providers settings or how the Invites are structured its hard to say how to fix this. Here is how the PBX does the source identification. Follow the diagram and see what matches