Help from someone using bandwidth.com with 3CX

[Kobo Williams]

I'm come across an issue in the past that has reared its ugly head again. The template for bandwidth.com provides the IP of their IP-based registration as 67.231.8.195. Bandwidth also has calls use the IP of 67.231.4.195. Sometime I get an error (as shown in the activity log) when someone tries to make an outbound call showing something similar to the following -

10/02/2019 6:17:13 PM
SIP Server/Call Manager ID: 12284
Call or Registration to 1XXXXXXXXXX@([email protected]) has failed. 67.231.4.195 replied: 403 Forbidden - This proxy does not serve that domain; from IP:67.231.4.195:5060

IF I change my registrar IP to the 4.195, I sometimes get an error message showing the 8.195 IP address. I've tried changing the registrar to a DNS name with 2 A records for both IPs, SRV records, nothing seems to work. Inbound comes in fine, but outbound calls get forbidden unless it is using one of the two IPs. Has anyone found a working solution for this?

 

[JohnS_3CX]

Hi Kobo,

Are you using a single NIC / single Bandwidth.com trunk only on your PBX?

Also consider providing more info before posting so we can better understand the setup
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Kobo Williams]

Hi Kobo,

Are you using a single NIC / single Bandwidth.com trunk only on your PBX?

Also consider providing more info before posting so we can better understand the setup
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Yes, with that one IP address.

 

[JohnS_3CX]

Please also follow the link I sent you and provide all the additional info if possible

 

[Kobo Williams]

MY 3CX version is Pro Annual 16.0.676
Server OS is Debian 9
Server is hosted
IP phones are Yealink T29G, though the issue happens with softphones also
Provisioning is Remote STUN
Firewall Checker YES, Custom Template YES

 

[JohnS_3CX]

Ok I think you should contact your provider in this case, and if you can give them a capture or at least logs that show what is happening. They should be able to inform you why they are rejecting the request.

 

[Kobo Williams]

Thanks, I was hoping there was someone who uses bandwidth.com who set this up previously.

 

[JohnS_3CX]

I think even if others had this issue, it may not be applicable for your specific case unless the provider tells us why.

 

[fleebs]

I have bandwidth.com. Don't use the template (not recommended by Bandwidth.com). You need to use the SIP Signaling IP's provided by Bandwidth.com which should be 216.82.224.202 & 216.82.225.202 or OT.BandWidth.com. You also need to permit media traffic coming to you from the following BandWidth.com IP's.

67.231.13.11 / 67.231.13.12 / 67.231.13.13 / 67.231.13.14
67.231.9.91 / 67.231.9.92 / 67.231.9.93 / 67.231.9.94
67.231.0.7 / 67.231.0.8 / 67.231.0.9 / 67.231.0.10
67.231.4.6 / 67.231.4.7 / 67.231.4.8 / 67.231.4.9

Hope this helps.