If you use bandwidth.com, do you do 2 trunks are stick with 1?

[dandenson]

I'm just configuring 1 trunk right now and every now and then I get hit with a number of calls on their secondary IP which I don't have configured. That causes 3cx to blacklist (and email me) that IP and then the call fails over to the 'main' number.

I'm tempted to just block that secondary IP. I'm not too interested or concerned about not having the redundancy right now and I really don't like the mess of having 2 identical trunks and handing inbound rules etc.

 

[eddv123]

This sounds like a poor implementation by the provider.

We use Twilio and Gamma and like most providers they have (normally - and you can see this if you do a Wireshark trace) 1 IP/SBC device for signalling and one for RTP/Media.

It sounds to me like there are 2 (like the above) but they don't have specific jobs, I would switch providers. If you want a clearer indication please feel free to send over a Wireshark trace.

 

[JohnS_3CX]

Hi @dandenson

If you use only one trunk, then you can try disabling the Call Source Identification option in the Inbound Parameters and see if this helps.

So long as the DIDs you defined match with what the provider sends, you should be fine even if they send calls via a secondary IP

 

[dandenson]

JohnS_3CX, the template for bandwidth.com has call source identification set as contact:host part, GWHostPort gateway/provider host/port

disabling this didn't make the trunk non-functional, but I'm wonder what else it might break.

 

[JohnS_3CX]

Call Source identification can help in cases when, for example you have two trunks from the same provider so the PBX receives all the calls from one source and would not be able to tell your trunks apart.
Turning it off now means that your PBX will accept the calls no matter which IP the provider uses (if the DID matches of course exactly as the provider sends them).

Since you only have one though, this would not be a problem.