- Joined
- Jun 8, 2020
- Messages
- 46
- Reaction score
- 27
Hi,
We are using an unsupported SIP provider with a number of fully updated v16 3CX installs and intermittently we are unable to complete any outbound calls.
When this occurs we need to restart the SIP service on the afflicted 3CX server. We tried disable/enable the trunk, but that isn't enough to rectify the problem.
This past weekend our ISP/SIP provider had a serious issue which pretty much blocked all traffic. This resulted in all SIP trunks going offline with the following error
After the ISP fixed the problem - which impacted all traffic, not just SIP - we had 4 seperate 3CX installs with 403 Forbidden errors when attempting outbound calls which could only be solved by restarting the SIP service. Inbound calls were not affected.
I believe the error is on the side of the service provider, but if anyone has experienced anything similar I would love to hear about it to better.
Mikkel
We are using an unsupported SIP provider with a number of fully updated v16 3CX installs and intermittently we are unable to complete any outbound calls.
When this occurs we need to restart the SIP service on the afflicted 3CX server. We tried disable/enable the trunk, but that isn't enough to rectify the problem.
Call or Registration to Destination-Phone-Number@(Ln.10000@SIPTRUNK (Generic SIP Trunk)) has failed. IP.of.SIP.Provider replied: 403 Forbidden; from IP:IP.of.SIP.Provider:5060
This past weekend our ISP/SIP provider had a serious issue which pretty much blocked all traffic. This resulted in all SIP trunks going offline with the following error
Entirely understandable.Registration at SIPTRUNK (Generic SIP Trunk) has failed. Destination (sip:IP.of.SIP.Provider:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available.
After the ISP fixed the problem - which impacted all traffic, not just SIP - we had 4 seperate 3CX installs with 403 Forbidden errors when attempting outbound calls which could only be solved by restarting the SIP service. Inbound calls were not affected.
I believe the error is on the side of the service provider, but if anyone has experienced anything similar I would love to hear about it to better.
Mikkel