Patton SN4112 FXO cannot dial out

[Kane Wong]

Hi;

Just finished to configure the outbound rules for 3CX to use. I have PRI for "route 1" and FXO for "route 2", in case of route 1 fail, the call can dial out through "route 2"

When I use my both mobile app and the desktop ip phone, when I called to the local number which is 10 digits plus "9" prefix, I cannot make it, I found the "503" issue when looking at the activity logs. Can someone help? Below Line:10001 indicate the traffic is trying the FXO gateway. My FXO unit is SN4112, this come with 1 eth 0/0 interface and two FXO ports, I am connecting a phone cord from FXO 0/0 to the wall jack.

Call to T:Line:10001>>6041115555@[Dev:sip:[email protected]:5060] from L:8.1[Extn:1234] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.168.101:5060

 

[cobaltit]

https://www.3cx.com/pbx/sip-responses/

Basically 503 means it couldn't send the call out. You would first start by confirming that you can dial that number with an analog phone directly connected to the land line. Once that works, you then check the logs on the Patton

As far as the Patton goes, is this a factory reset device provisioned with the 3CX generated config and no config modifications by you?

 

[eddv123]

A 503 from a Patton is either going to be that either the Patton is configured incorrectly, there is an issue with the line, or possibly even the number being dialled.

If this is a standard 3CX template and the device is registered to 3CX I would as a first step is login to the Patton gateway via CLI and run the following commands:

enable
configure
context cs switch
show port fxo 0 0 (number based on which slot/port(s) you are using)

Check the link status is up or down. If up it means you have a connected/working line however with that being said it may also be worth checking with the provider to confirm if there are any PBX-like features on this line (feature line/redcare we call it in the UK) as this can interfere also.

If all this checks out then it will most likely either be your config on the Patton, or that the outbound rule is manipulating the dialling number incorrectly.

 

[Kane Wong]

thank you! I saw the line is up on port FXO 0/0. I have sent the debug result to Patton for further checking. Thank you for your tips.

By the way, how can I use the command line on Patton device to change the default "clock local default-offset +00:00" value, the time is shown incorrect. I want change the offset value to -08:00,

Should I just issue this command "clock local default-offset -08:00", or other? And how about the Daylight Saving?

 

[eddv123]

Happy to take a look at the logging if you want to PM it across also. I assume you ran these from the command line ? https://support.patton.com/index.ph...ebugging--smartware-vs-trinity-debug-commands

There are no Patton time parameters in the template settings for the Patton on 3CX so this will be required manually, the time offset for daylight savings is covered in the Smartware manual here (page 107 I believe): https://www.patton.com/manuals/SmartWare_SCG_r68.pdf

 

[leejor]

it may also be worth checking with the provider to confirm if there are any PBX-like features on this line (feature line/redcare we call it in the UK) as this can interfere also.
[/QUOTE
I've seen you mention this service before. I'm not certain what the different physical characteristics of this is in the UK, but , in North America, PBX-like features, offered by a LEC (usually called something like Centrex) is physically no different from normal POTS service. The differences are in the dialling method... 4, or 5 digits to another extension, dial 9, or 8 to call other PSTN numbers, trunk prefixes, and an often, different list of vertical service codes. There may be a different ring cadence to indicate internal and external calls. With the possible exception of the older 90 vdc message waiting lamps (neon), the line-cards used at the central office are generally the same as other POTS lines

 

[eddv123]

@leejor i cannot say for sure whether it is the same service that you have over there.

I have supported many FXO gateways and had a few with featureline enabled on the line (although none too recently) and from experience know that it can cause signalling issues when being used with an actual PBX.

I will see if I can find out more information however.

 

[leejor]

I have had issues when connecting a gateway to a PBX line (Mitel in particular), as it supplies 24 volts rather than 48. The Gateway had to be "adjusted" to recognise the off-hook/on-hook voltage.
This is common to what is offered by many providers in North America, the name of the service may vary.

https://business.telus.com/en/enter...ness-phone-systems-frequently-asked-questions

As I said, connecting a gateway is no different than any other PSTN line. Only the dialling options/features are different.

 

[eddv123]

Centrex and Feature-line are the same I think - looking at these as a comparison:

https://en.wikipedia.org/wiki/Centrex
https://btbusiness.custhelp.com/app/answers/detail/a_id/10652/~/featureline:-calling-features/c/5115/

I have dug through some historic emails on my side and found that most issues we had with feature-line included call drops and inbound call failure (I have found some online posts also to support this - albeit from different vendors):

https://forums.grandstream.com/t/gwx4104-with-bt-featureline-call-drops/445
https://www.openvox.cn/forum/a400-800-1200-series/518-uk-bt-featureline-fxo.html

Where there is no resolution in either of the above strings unfortunately, all we did was have the customer contact the provider and remove the features - in the cases I dealt with they weren't even aware of the existing feature-line presence (and were probably paying extra for it as well).

Where perhaps adjustment to voltage settings may help its not something personally this is not something I have ever looked into since removal solves the issue and saves money for the client consecutively.

You mention some interesting points yourself regarding Centrex in the final post of this string here also: https://www.3cx.com/community/threads/3cx-spa3102-and-centrex.39952/

 

[Kane Wong]

After change the timeout to either 1 second or 2 second, it works.