Solved SIP Errors

[Shadragon]

3CX is sending me "Trunk/Provider responds to Request with an error" emails with almost every outbound call now. The calls go through, but I get one of two error message shown below (edited for privacy.) The frequency is about twenty emails an hour during business hours.

Call or Registration to +xxxxxxxxxxx@(Ln.10000@Provider SIP) has failed.
172.xx.xxx.xx replied: 500 Server Internal Error; from IP:172.xx.xxx.xx:5060

Call or Registration to +xxxxxxxxxxx@(Ln.10000@Provider SIP) has failed.
172.xx.xxx.xx replied: 480 Temporarily Unavailable; from IP:172.xx.xxx.xx:5060

The 172.xx.xxx.xx IP is our SIP Provider.

I'm convinced either the SIP trunk or my PBX have a wonky setting, but the SIP provider refuses to help me fault find the connection saying, essentially, the calls are going through so it's working.

Any idea what's going on? Is there a SIP utility to fault find SIP connectivity issues out there so I can interrogate the trunk and see what's wrong? Thanks.

 

[cobaltit]

I think you need to set logging to at least 'Medium' to see the rule. No reboot should be required. You are looking for a couple lines. From the bottom up when filtering by call you are looking first for the number formatting from the client to 3CX which should look something like this:

11/20/2018 11:49:56 AM - [CM503001]: Call(C:305): Incoming call from Extn:XXX to <sip:5551212@3CXFQDN or IP:5060>

Then after the Invite you should see a couple lines like this:

11/20/2018 11:49:56 AM - [Flow] Call(C:305): has built target endpoint: Out#:>>Rule{Rule Name}>>5551212 for call from L:305.1[Extn:XXX]

11/20/2018 11:49:56 AM - Call(C:305): Call from Extn:XXX to 5551212 matches outbound rule 'Rule Name'

 

[YiannisH_3CX]

@Shadragon

I would recommend if possible to use a supported provider if possible and see if you are facing the same issues. https://www.3cx.com/partners/sip-trunks/
You could also take a closer look at what the PBX is doing by using the 3CX BinLog Viewer
https://www.3cx.com/docs/3cx-log-viewer/

 

[Shadragon]

Set medium logging and rebooted overnight, just to make sure. I can confirm the numbers are using the correct (and only) 7-digit rule.

11/21/2018 4:40:46 PM - Call(C:1660): Call from Extn:555 to 2980617 matches outbound rule 'Local Calls Allowed'

 

[cobaltit]

So is that an example that is working for failed?

 

[Shadragon]

That was one that failed resulting in a 480 error.

The frequency of these errors has dropped dramatically in the last few days and I've not changed anything on the server. Looks like my numerous error emails to the SIP provider is finally having an effect.

 

[Shadragon]

No error emails for three days now. I think they sorted it out on their end.

 

[cobaltit]

Good, glad to hear it.

 

[YiannisH_3CX]

No error emails for three days now. I think they sorted it out on their end.

Glad to see the issue has been resolved.