No outbound calls

[segate]

Running V15.5 on a Windows Server

Outbound calls have stopped mid day without any changes to 3CX settings or the network. This system has been working for several years without issue.

Event log shows the following:
Call or Registration to 18**77***58@(Ln.10001@Patton Analog FXO 2) has failed. 192.168.1.*** replied: 504 Server Time-out; from IP:192.168.1.***:5060

Call or Registration to 18**77***58@(Ln.10000@Patton Analog FXO) has failed. 192.168.1.*** replied: 503 Service Unavailable; from IP:192.168.1.136:5060

Phones show message- Internal Server Error

Inbound calls are working fine.

Where do I go from here?

 

[leejor]

It would appear to be an issue with your gateway, or, perhaps one, or more of the PSTN lines going to the gateway. I would reset (power down and up), the gateway, and confirm dialtone on all PSTN lines.

 

[eddv123]

I agree, a 5xx style response suggests the issue is server side (provider or gateway) I would look at upgrading your 3CX to v16 definitely but also as far as the Patton is concerned check:

* Confirm model and firmware of unit (is it a 3CX supported model)
* Network: where is the unit and where is 3CX
* Login to the Patton interface and check:

Ports >> FXO >> Status >> fxo 0/0 (for example but could be any line).
What does the line state say ? it should be "up".

Failing that trace a call and see what the Patton reports (see below).

Login to the CLI of the unit via SSH:

enable
configure
debug ccfxo
debug fxo
debug call-control
debug call-router
debug context sip-gateway transport
debug context sip-gateway error

Then "no debug all" after to cease the log flow.

These may differ slightly between the Smartware and Trinity operating systems so use this as reference: https://www.patton.com/support/kb_art.asp?art=446&

Although this is for Trinity based smartnodes commandline, this video gives the jist of the process: