Linksys PAP2T gets unregistered after some hours.

[Rob59]

Hi,

I wonder if someone has any suggestions how to fix this.

My 3CX system, latest version, all updates installed, has problems with a Linksys Pap2T unit. Both extensions through this unit get unregistered after some hours. I get the message "Extension 123 is unregistered, removed contact: sip:[email protected]:5061"

Powering off and on the PAP2 does not help, it won't re-register. Stopping and restarting all possible 3CX services does not help either. The only way to get the unit registered again is restarting the pc 3CX is running on.

I swapped both the power supply of the PAP2T and the PAP2T itself. That did not help. I also tried changing the static IP address of the PAP2T, that did not make any difference either.

Any suggestions how to fix this?

I also use som Cisco SPA 504G phones on the same system, these lines are rock stable and stay registered.

Best regards, Rob.

 

[leejor]

This on the same network as the server? If you power op the PAP2T, is there a 3CX Activity Log showing a registration attempt, and rejection? If not, and the destination IP (FQDN?) of the sever is able to be resolved correctly, then something (setting/firewall/network/blacklist) is preventing the PAPT2 from getting through.

 

[Rob59]

This on the same network as the server? If you power op the PAP2T, is there a 3CX Activity Log showing a registration attempt, and rejection? If not, and the destination IP (FQDN?) of the sever is able to be resolved correctly, then something (setting/firewall/network/blacklist) is preventing the PAPT2 from getting through.

Thanks for looking at this.

Yes, on the same server, even on same wireless router. PAP2T connected by network cable and 3cx windows 10 pc connected by wifi.

There is no activity log at all at the time the extensions were unregistered.Activity logger is in "Low" mode, I could put it in "Verbose" and try again.

The PAP2T shows "Can't connect to login server" on it¨s info-page. Strange, because it can be connected for some hours before it gets unregistered. Sometimes it even works some days without problem.

 

[Rob59]

This on the same network as the server? If you power op the PAP2T, is there a 3CX Activity Log showing a registration attempt, and rejection? If not, and the destination IP (FQDN?) of the sever is able to be resolved correctly, then something (setting/firewall/network/blacklist) is preventing the PAPT2 from getting through.

Okay, it happened again and I had the Event logger in Verbose mode. Here are the entries:
09/08/2018 8:08:12 PM - Endpoint Extn:123 has removed contact <sip:[email protected]:5061>
09/08/2018 8:08:12 PM - [CM504002]: Endpoint Extn:123: a contact is unregistered. Contact(s): []
09/08/2018 8:08:12 PM - Endpoint Extn:124 has removed contact <sip:[email protected]:5060>
09/08/2018 8:08:12 PM - [CM504002]: Endpoint Extn:124: a contact is unregistered. Contact(s): []

No other activity is logged for these extensions after this.

 

[mixig]

Connect 3cx to router with the cable not wifi and monitor situation.

 

[leejor]

Yes, on the same server, even on same wireless router. PAP2T connected by network cable and 3cx windows 10 pc connected by wifi.

Yes, I'd agree with trying a wired connection if just for testing. The fact that it did work in the past, but there is now no sign , in the logs, of an attempted registration, suggests that it has lost network (or looses at times) connectivity.

 

[Rob59]

Thanks for the suggestions. I first tried to change the PAP2T network cable and the router port it was connected to. That did not make any difference, the problem still kept coming up.

Finally I connected the 3CX server to the router by cable, as suggested, and that seems to have solved the problem So this was not a 3CX problem but a router problem.

Thanks for the help!

Regards, Rob.