Solved PSTN ATA Unregistred since reinstall V16

[AWS2P]

Hi,
have done a v16 reinstall this afternoon with a backup done previously.
The only change has been on SIP Port, don't use anymore 5060.

Since that my ATA SPA3102 (unsupported GW) that was perfectly working before reinstall isn't registering on PBX, nothing changed on his settings nor on pbx side.

Pbx has been rebooted -- > result KO
A power Off / On has done nothing on SPA3102 -> KO
A change on SIP GW port was using 5062, tested with 5064 on both side, --> KO
Log on Verbose with weird messages

25/10/2019 16:49:24 - Failed to add outbound CID reformating rule for DN:10001: <Rules />

25/10/2019 16:49:24 - DN:10001 got config update notification

25/10/2019 16:18:35 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Configuration updated

25/10/2019 16:18:35 - DN:10001 is unregistered

25/10/2019 16:18:35 - Failed to add outbound CID reformating rule for DN:10001: <Rules />

25/10/2019 16:18:35 - Failed to add outbound CID reformating rule for DN:10001: <Rules />

25/10/2019 16:18:35 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Updating configuration

25/10/2019 16:18:35 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Being updated

25/10/2019 16:18:35 - Failed to add outbound CID reformating rule for DN:10001: <Rules />

25/10/2019 16:18:35 - Failed to add outbound CID reformating rule for DN:10001: <Rules />

25/10/2019 16:18:35 - DN:10001 got config update notification

25/10/2019 15:53:11 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>]) is not added to outbound line set - no known target

25/10/2019 15:53:11 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Failed to create device

25/10/2019 15:53:11 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Creating master device

25/10/2019 15:52:57 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>]) is not added to outbound line set - no known target

25/10/2019 15:52:57 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Failed to create device

25/10/2019 15:52:57 - Lc:10001(@SPA3102 Orange / 3CX[<sip:0/UDP>])Creating master device

i'm not using CID reformating, what means Creating master device ?

Any ideas ?

 

[leejor]

You say you don't use port 5060 any longer, do you mean, at the PBX end? If that is the case, they you will have to specify which port is now being used, in the 3102 setttings. It will default to using 5060 (to the server at the far end) if no other port is specified. You specify the port in the server setting by adding something like :5070, to the server address, if 5070 is the new port you are using. my3cxpbx.server.com:5070

Not certain why the 3102 would be updating as I'm assuming it was manually configured.

 

[eddv123]

I would try a reset and re-provision (manual setup since you are not using a supported device) obviously you have your port on 3CX you can check but if you run a Wireshark trace on 3CX (and the same on the ATA if it supports it - or mirror a switch port) and see what the SIP register ports are.

 

[leejor]

I would not go as far as a complete reset, at least for now.

The only change has been on SIP Port, don't use anymore 5060.

This change requires clarification.

 

[AWS2P]

WHY:
Have changed SIP 5060 to other port because one of my customers is using a Box PRO from Orange , French ISP , and recently they change their Livebox firmware to restraign use of 5060 for their phone system, so this cause i'm no more able to create nat rules to redirect 5060port.

HOW :
3X staff ask me to do a backup and reinstall changing SIP port, that's what have done no less no more.


RESULT:
Everything works fine , but no more my ATA GW used as Trunk PSTN only, I have several SPA3102 on different PBX and working fine, as it was the same before reinstall for the one we speak about.

Have done a new generic Trunk 10002 and changed port to 5064 on ATA with no change, log is here



Credentials SPA3102 side , changed userid to 10002 and password only



PBX SIDE

 

[leejor]

So if the 3CX server port was changed from 5060 to another port, then you would have to change the Proxy setting to something like... 192.168.20.10:5063, or whatever port the server now uses. As i say, without a specified port, the 3102 assumes it is to use 5060.

Changing the local port on the ATA, for the FXO , will require that the trunk,settings in 3CX reflect that change. The FXS local port is identified during registration.

 

[AWS2P]

Well done Leejor, right on target ATA is back in 3cx world