|Summary:||ASTERISK-14777: reloading doesn't clean everything|
|Reporter:||Raphaël Jacquot (sxpert)||Labels:|
|Date Opened:||2009-09-05 00:23:16||Date Closed:||2011-06-07 14:00:44|
Asterisk 184.108.40.206~dfsg~beta3-1 built by pbuilder @ grnetbox on a x86_64 running Linux on 2009-07-28 00:56:52 UTC
it appears that chan sip doesn't clean everything on reload, and keeps stray information from previous versions of the configuration, leading to 401 errors on incoming calls because it's looking for a peer that has disappeared.
a complete restart of the switch fixes the problem.
|Comments:||By: Tilghman Lesher (tilghman) 2009-09-06 11:04:35|
By: Olle Johansson (oej) 2009-09-07 08:17:17
401 is not an error really - it's an authentication challenge. We need more informatin from you and SIP debug output that shows that we're still trying to match a peer that supposedly should have been removed.
By: Raphaël Jacquot (sxpert) 2009-09-07 09:08:17
I had it... it scrolled out of screen ;(
I'm sure of seeing some message about not being able to find a non-existant peer..
of course, I can't seem to reproduce it now...
By: Raphaël Jacquot (sxpert) 2009-09-08 16:35:57
ah. there. have a proof !!
[Sep 8 23:31:49] NOTICE: chan_sip.c:21900 sip_poke_noanswer: Peer 'horsfall_free' is now UNREACHABLE! Last qualify: 38
[Sep 8 23:31:54] NOTICE: chan_sip.c:21900 sip_poke_noanswer: Peer 'sxpert_free' is now UNREACHABLE! Last qualify: 33
[Sep 8 23:31:59] NOTICE: chan_sip.c:17439 handle_response_peerpoke: Peer 'horsfall_free' is now Reachable. (33ms / 60000ms)
[Sep 8 23:32:04] NOTICE: chan_sip.c:17439 handle_response_peerpoke: Peer 'sxpert_free' is now Reachable. (33ms / 60000ms)
ecureuil*CLI> !vi /etc/asterisk/sip.conf
ecureuil*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
a580ip/a580ip 192.168.0.50 D 5060 OK (89 ms)
nortel/1234 192.168.0.51 5060 OK (23 ms)
sxpert_free/0950380122 220.127.116.11 N 5060 OK (33 ms)
3 sip peers [Monitored: 3 online, 0 offline Unmonitored: 0 online, 0 offline]
there's no "horsfall_free" anymore in the list... yet... I'm still getting messages about it
By: Leif Madsen (lmadsen) 2009-09-30 09:36:50
Can you please retry on a newer version of 18.104.22.168? I can't find any other issues in the issue tracker related to this one, and you're the only one who seems to be having this issue, so I'd like to verify upgrading doesn't resolve this issue.
If it doesn't, please provide sip debug, sip history, and console output with debugging enabled.
This is probably best done by reproducing the issue with the 'full' logging option in logger.conf and attaching that file. Please filter out only the stuff that is applicable to this issue.
By: Leif Madsen (lmadsen) 2009-10-26 09:51:44
Closed due to lack of feedback. If the reporter is able to provide the requested information, please reopen this issue. Thanks!