call or registration to patton analog fxo 503 service unavailable from ip

[asdfasdfasdfasdf]

Hello,

I have a client who is reporting (on Yealink T-42S phones) the following: Getting internal server error on a few phones, this is a sporadic thing that has been happening. It will go away after a about 5 or 10 mins.

Upon checking call logs I see:

call or registration to 15555555555@(Ln.10000@Patton-Analog-FXO) has failed. 192.168.0.123 replied 503 Service unavailable; from IP: 192.168.0.123:5060

555 number made up of course. Upon looking at more logs, all of the errors are on "Ln.10000".

Then I realized the customer only has one POTS line active out of four initially when I set this all up. I called the other 3 numbers and sure enough none go to the client. I also checked the port status on the patton for the last 3 ports (of 4) and their status was "Line State: DOWN".

If they purchased a new Comcast service and/or ditched 3 out of 4 of their POTS numbers, could this be the reason the phones sporadically say "internal server error" but then goes away after 5-10 minutes? My thought is a second person is trying to dial out while someone else is already using their one-and-only line. I have not contacted them to make a test yet, and most threads on here say to call the provider, just curious if this could be a cause.

Patton model is SN4114, 3CX version 15.5.

Thanks

 

[eddv123]

First things first - a 503 service un-available if you PCAP/Wireshark would be coming most likely from the Patton - which in turn could be the configuration on the device itself or some sort of issue with the lines/provider side.

Questions:

• Where is the Patton in relation to 3CX.
• Are you using standard or customised templates on the Patton.
• Where are you located - who is the provider and have you confirmed whether these lines are standard lines and dont have any additional services running - such as featureline/redcare we call it in the UK which offers PBX-like services on the line itself and can really ruin your day.
• While were at it a firwmare check on the Patton might be in order.

With standard templates with 3CX the FXO lines will call in order - FXO port 0, 1, 2,3 etc you cannot assign/select outgoing lines without modification to the standard template: https://www.3cx.com/community/threads/assigning-outgoing-pstn-lines-using-patton-sn4xxx-fxo.39856/

The simplest way to see where the error lies is to run the debug commands from the CLI of the Patton device - login via SSH and run:

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

Replicate your issue/make a call.

no debug all is required to turn off debugging once run.

I assisted a user with a similar issue a few months ago and found that only 1 out of their 4 lines were actually in service - a trace should show us more but you can (as you have already said) login to the Patton and look at the port status itself.

 

[leejor]

Use an analogue phone to check that there is dial tone on all of the lines that are going into the gateway. If one is "dead", and that is the line the Patton is going to try to call out on, then the call will fail.

 

[eddv123]

I have found the forum string i mentioned with the similar problem: https://www.3cx.com/community/threads/phones-showing-please-hang-up-message.65787/page-2#post-283793

Destination out of order is what the Patton logging will state if the line is not working, in which case this is a provider issue.