Inbound calls that don't match trunk, what happens?

[dandenson]

I'm looking at my trunk config, which is with VoIP Innovations. I've got one inbound trunk and I've whitelisted their other IPs.

When I look at inbound rules, I see that my main DID appears to be tied to that trunk. What happens when a call comes in outside of that trunk from one of the whitelisted IP addresses?

I have other threads on the symptom (random calls go direct to voicemail, no network issues) but different angles. I'm wondering if the call comes in from a VI address that doesn't have an inbound rule, does it get handled by the system default? ie settings/pbx/operator extension? I have that set to a voicemail only extension because it won't allow me to set it to a ring group.

 

[eddv123]

You should based this on DDI and not IP address. If you have a block of DDI's then you can add them in on the tab in the trunk configuration.

There are two types of provider - IP authenticated and registration based, please advise which yours is.

For an IP authenticated SIP trunk, only 1 IP address is permitted and must be allowed through your local firewall to 3CX (the provider does the same on their side)

 

[dandenson]

Voip Innovations is IP based. They have multiple IPs so I need multiple trunks. Different IPs for in and out and for redundancy.

The complication in 3CX is that if I want to use the same outbound DID in all trunks, I've got all these duplicates.

 

[eddv123]

Sounds similar to Gamma assured SIP service that we have here in the UK.

Not good for setting up with multiple IP addresses but I recall that there is a fudge you can perform by setting up with multiple trunks and assigning different SIP Id's.

 

[NickD_3CX]

Let me start first by saying that they are not supported right now.

Knowing a bit how they work, you would have to:

• Create 1 SIP Trunk in 3CX for each of their IPs (enable Source Identification in Inbound Parameters tab with "Contact : Host Part" <==> GwHostPort). I think you should end up with 8 SIP Trunks last time I checked.
• Each one of your DID, add to all SIP Trunks (you don't know which IP it'll come from)
• Create the same Inbound rule multiple times, once for each SIP Trunk.

Before someone says it, there is a reason we have not announced them as approved to use on 3CX.
This MAY work, but it would be a bit of a nightmare to maintain.

 

[nub]

Voip Innovations is IP based. They have multiple IPs so I need multiple trunks. Different IPs for in and out and for redundancy.

The complication in 3CX is that if I want to use the same outbound DID in all trunks, I've got all these duplicates.

I use Innovations with more than one ip, in endpoints just add another ip to the group. https://backoffice.voipinnovations.com/Dashboards/Endpoints.aspx , you can even test it by just changing the priority.

For voipinovations i only use the 64.136.174.35 address which is not optimal from a redundancy point of view.

You could get a $50 edgewater 4550 off ebay with a sip license and setup ip based registrations for all innovations ips, and if this works then order the must more costly multi wan edgewater for your multiwan setup.