Issue with SIP header when using alternative proxy

[joeyd]

Hello,

Using a bandwidth trunk with 2 IP addresses, setup according to the 3CX/Bandwith guide on the website.

Using IP1 on the main tab, using IP2 in the Options/Alternative proxy tab. When the failover occurs it seems to still use IP1 in the SIP invite to bandwidth but it sends it to IP2. The provider rejects the invite and a 403 forbidden message is sent to the user.

Is this a flaw in 3CX or have I done something wrong in setup?

Thanks!

 

[YiannisH_3CX]

Hi @joeyd

Contact your Bandwidth account manager and request to be moved to the new platform. You will be given a new set of IPs and will be able to switch between them with no issues.
If you are having issues with Bandwidth please contact me in a p.m. and let me know your ticket number with Bandwidth and we will try to get this going from our side as well.

 

[joeyd]

Hi @YiannisH_3CX

I had opened a ticket with them when the issue occurred - I asked them to verify my IP addresses, they told me that the SIP invite was using the wrong IP, but they never mentioned anything about a new platform or new IP addresses. Strange. Any idea how the new platform differs from the old?

Is this something I should definitely do? I have 20 systems so far and growing, and I see the 403 forbidden every now and then on various systems every few weeks. Usually a reboot of the instance solves it, but it's a pain for the customer.

 

[YiannisH_3CX]

If you want failover then this is something you will need to do. The new platform supports enhanced 911 capabilities and better failover options if I remember correctly. Also our template is designed to work with the new platform which is what we tested.
Both their platforms are active, and have few differences so I don't think this is something they advertise as it takes a while to migrate users from one to the other.

 

[joeyd]

Great, thank you, I appreciate the help. I'll open a ticket with them now. Will keep you posted.