We have Asterisk 13.11.2 compiled on Ubuntu 16.04.1 (clean install). Previously we were running Asterisk 12.2. The contents of /etc/asterisk was copied across from Asterisk 12.2.
When we were running 12.2 we could do a ‘sip reload’ without any issues.
Since upgrading to 13.11.2 existing registered phones seem to lose their registration when we run ‘sip reload’ and when I run ‘core set verbose 9’ soon afterwards I can see all the phones re-registering over the next few minutes.
An ‘authentication failed’ warning is shown in the Asterisk log when phones attempt to make a call prior to re-registering.
Everything is in sip.conf and not using realtime or anything special as far as I know.
The log shows the following after ‘sip reload’:
[Nov 10 08:15:55] VERBOSE[10778][C-000004a7] app_dial.c: SIP/601-00000fb6 is ringing
[Nov 10 08:15:55] VERBOSE[10778][C-000004a7] app_dial.c: SIP/625-00000fb7 is ringing
[Nov 10 08:16:05] VERBOSE[1237] asterisk.c: Remote UNIX connection
[Nov 10 08:16:08] VERBOSE[1484] chan_sip.c: Reloading SIP
[Nov 10 08:16:08] VERBOSE[1484] config.c: Parsing ‘/etc/asterisk/sip.conf’: Found
[Nov 10 08:16:08] VERBOSE[1484] config.c: Parsing ‘/etc/asterisk/users.conf’: Found
[Nov 10 08:16:08] VERBOSE[1484] netsock2.c: Using SIP CoS mark 4
[Nov 10 08:16:08] VERBOSE[1484] config.c: Parsing ‘/etc/asterisk/sip_notify.conf’: Found
[Nov 10 08:16:08] VERBOSE[10778][C-000004a7] app_dial.c: Nobody picked up in 13000 ms
[Nov 10 08:16:08] VERBOSE[1283] chan_sip.c: Extension Changed 601[localext-nz] new state Idle for Notify User 606
Interestingly it appears to only be affecting around 10% of our phones based on the number we see re-registering after ‘sip reload’’. This is what I get when grepping the log file for “Registered SIP”. When I run ‘sip show peers’ after the ‘sip reload’ I remember that things looked generally ok, although I can’t be sure of that (don’t want to run it again during business hours at this stage).
[Nov 10 08:16:31] VERBOSE[1484] chan_sip.c: Registered SIP ‘704’ at 192.168.6.131:5060
[Nov 10 08:17:05] VERBOSE[1484] chan_sip.c: Registered SIP ‘702’ at 192.168.6.137:5060
[Nov 10 08:17:07] VERBOSE[1484] chan_sip.c: Registered SIP ‘703’ at 192.168.6.138:5060
[Nov 10 08:17:47] VERBOSE[1484] chan_sip.c: Registered SIP ‘710’ at 192.168.6.143:5060
[Nov 10 08:21:40] VERBOSE[1484] chan_sip.c: Registered SIP ‘856’ at 192.168.2.11:5060
[Nov 10 08:30:27] VERBOSE[1484] chan_sip.c: Registered SIP ‘675’ at 192.168.6.133:5060
[Nov 10 08:30:31] VERBOSE[1484] chan_sip.c: Registered SIP ‘681’ at 192.168.6.127:5060
[Nov 10 08:30:33] VERBOSE[1484] chan_sip.c: Registered SIP ‘683’ at 192.168.6.126:5060
[Nov 10 08:30:38] VERBOSE[1484] chan_sip.c: Registered SIP ‘679’ at 192.168.6.132:5060
And here is the result when grepping the log for “Failed to authenticate” after the SIP reload. This users phone came right after re-registering a few minutes later.