Solved SIP Errors

[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.