- Joined
- Apr 5, 2017
- Messages
- 4
- Reaction score
- 1
Helle there,
Since we are running various hotlines in our operation, alternate internet connection is a must in case of a disconnectivity in the main connection. Rare, but it happens. Therefore we are using a firewall with active gateway routing to sense and switch to the alternate connection in case of a trouble. When the firewall swtiches to the alternate connection, we are able to accept inbound calls without any problem. But the outbound calls rejected by SIP provider with the following error in 3CX:

Then we have checked on our side and we realised out that the IP in the 3CX/SIP Trunk/Options/Put Public IP in SIP VIA Header still shows the offline IP eventhough the Public IP updated in the Dashboard. So we need to update manually the IP in the Options menu for every single SIP trunk. Because of that, the firewall's automatic routing does not make sense.
Please consider this issue as a feedback and please update this issue in the next release.
Since we are running various hotlines in our operation, alternate internet connection is a must in case of a disconnectivity in the main connection. Rare, but it happens. Therefore we are using a firewall with active gateway routing to sense and switch to the alternate connection in case of a trouble. When the firewall swtiches to the alternate connection, we are able to accept inbound calls without any problem. But the outbound calls rejected by SIP provider with the following error in 3CX:
- Call or Registration to 0xx0605xxx7@(Ln.10006@0xx6526xxx0) has failed. 217.xxx.xxx.25 replied: 403 Forbidden-Source Endpoint Lookup Failed; from IP:217.xxx.xxx.25:5060

Then we have checked on our side and we realised out that the IP in the 3CX/SIP Trunk/Options/Put Public IP in SIP VIA Header still shows the offline IP eventhough the Public IP updated in the Dashboard. So we need to update manually the IP in the Options menu for every single SIP trunk. Because of that, the firewall's automatic routing does not make sense.
Please consider this issue as a feedback and please update this issue in the next release.