Solved Multiple SIP trunks not routing

[Chad Yost]

I can't figure out what I'm missing. I have two Vitelity inbound trunks set up, and using Register/Account based authentication. Both trunks are registering and "up". The first trunk gets routed to an extension: 90 IVR Operator. This is configured on the SIP - General - Route calls to section, only the Trunk 1 DID is in there. The other trunk, I want routed directly to a person, no matter what I try it always goes to the same IVR operator as the First trunk. I only have the two incoming rules. Trunk 1 to IVR, and Trunk 2 to user extension. I'm on Version 16.
Ideas?

 

[Saqqara]

Check the activity log, which will give you more details on what is happening.

Check to see if the numbers are coming in on the correct trunk

Does each trunk have one number associated with it, if so configure call routing on the SIP trunk under 'Route calls to' , remove DDI settings.

 

[YiannisH_3CX]

Hello @Chad Yost

Please make sure that your DIDs are in the correct format to match Vitelity's Invites. Check the Activity log of the PBX and look for the Invite from Vitelity. Check the To: number and how it is formatted. Then adjust your DIDs to match that number.
As Vitelity is an IP based provider that we cannot perform source identification on, the PBX can only match the call to the trunk via the DID number sent.

 

[leejor]

These are two separate trunks, to the same provider (same IP/URL?) , or two virtual trunks?

 

[Chad Yost]

They are two separate trunks to the same provider (same IP).

I had "Call Source Identification" configured with "Contact: Host Part", "Custom Field", and the IP of the Vitality server. They happened to be the same for both trunks in this case, and once I removed that it started routing like it should be. Now with that IP check out of there, will I be susceptible to outside connections, from non Vitality IP's? Or is there a better way to block unknown connections?

 

[YiannisH_3CX]

The source identification check is not to limit the connections to the Vitelity IP. It is to help the PBX match the call to the right trunk. The option was not enabled by default as Vitelity has multiple servers and the call might come from any one of them. I am guessing routing failed because the option was enabled. If you want to block unknown connection attempts to the server then you need to do so from your firewall. You will need to know all Vitelity IPs to do so.