Cisco/Yealink phones occasionally unregister

[itagooskar]

Hi there,

Every once in a while some of our phones unregister. The phones are Yealink T23G and Cisco 7941 (unsupported, I know... but still).

In the event log it looks like this:
SIP Server/Call Manager ID: ____
Extension XXXX is unregistered, removed contact: sip:[email protected]:(port_num);transport=tcp, received from: 10.x.x.x

Here are the relevant parts of our Template Settings:
<sipStack>
<sipInviteRetx>6</sipInviteRetx>
<sipRetx>10</sipRetx>
<timerInviteExpires>180</timerInviteExpires>
<timerRegisterExpires>600</timerRegisterExpires>
<timerRegisterDelta>5</timerRegisterDelta>
<timerKeepAliveExpires>120</timerKeepAliveExpires>
<timerSubscribeExpires>120</timerSubscribeExpires>
<timerSubscribeDelta>5</timerSubscribeDelta>
<timerT1>500</timerT1>
<timerT2>4000</timerT2>
<maxRedirects>70</maxRedirects>
<remotePartyID>false</remotePartyID>
<userInfo>None</userInfo>
</sipStack>


I'm not sure what parts in Settings -> Parameters are relevant but here are a few:

• SIPPINGPERIOD: 0 Time intervall to poll endpoints with SIP INFO messages, in seconds. 0 - disabled
• REGISTER_REQUEST_MAX_TIMER: 120 Controls interval of registration period when 3CX is answered with 503 Service Unavailable. Default Re-registration is 600 seconds (10 minutes) Value is in seconds
• KEEPALIVE_TIME_UDP: 30 Controls interval in seconds that keepalives will be sent. Useful to keep firewall port mappings open. Default is 30 seconds.
• NONCEEXPIRATION: 20 defines nonce expiration time (seconds). By default it is 5 sec. After this time has passed since nonce issue -- PBX will treat that nonce as expired and will force re-authentication (will issue 407 response with new nonce freshly generated.

To provision phones, I download from 3CX the SEP<MAC_ADDRESS>cnf.xml file to my TFTP server, reset phone to defaults, and then have DHCP point the phone to the TFTP server. Registering is fine and works well. Then at random times, days or weeks later, it becomes unregistered until I manually reboot.

Is there anywhere else that I should check that could explain these phones becoming unregistered? At this point, it doesn't seem to be ALL phones but it is certainly more than a single phone.

Thanks in advance.

 

[cobaltit]

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[itagooskar]

Here's some more info if that will help:

3CX Version: Professional Annual 16.0.493
Server OS: Debian 9
3CX Server: hosted locally as VM on Hypervisor
IP Phones:

• Cisco CP7941G fw: 8.5.3
• Cisco CP7961G fw: 8.5.3
• Yealink SIP-T23G fw: 44.84.0.95

Provisioning Method: Local
Trunk Provider: ThinkTel
Firewall Checker passed: NO (But shouldn't be relevant for this problem.)
Are custom Phone Templates being used: No.

 

[AWS2P]

try to restore

REGISTER_REQUEST_MAX_TIMER:

try to restore default value to 600s

 

[AWS2P]

Are custom Phone Templates being used: No

you said no custom template , but your first post is about details on template so is it really default or your own?

 

[itagooskar]

As far as I know it is the default template. I posted the sections from the template that seemed like they could be relevant when compared to the 3CX Parameters. The thing that I don't know is whether there is any of these values in the template/Parameters that should be lower or higher (such as your "REGISTER_REQUEST_MAX_TIMER" suggestion) in the context of our 3CX setup.