[Home]

Summary:ASTERISK-08087: Asterisk 'invisible' resending registers after registering successful with a peer
Reporter:Drake Swokowski (drake)Labels:
Date Opened:2006-11-08 15:27:37.000-0600Date Closed:2007-01-17 23:15:23.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) register_sip_log.txt
( 1) register-log.cap
Description:The registration procedure succeedes:

REGISTER->
<- 401
REGISTER->
<- 200

but then after 5 seconds asterisk keeps sending REGISTER messages that are not printed with SIP debug, but that can be viewed with ethereal that asterisk really sends the wierd REGISTER requests. The 401 response is printed with sip debug anyway.

Note that incoming and outgoing calls is still working, but we dont want this wierd REGISTER messages every 2-5 second.

We are using asterisk-1.2.10. I suppose that this problem exists in 1.2.12-1 as well.


****** ADDITIONAL INFORMATION ******

I found another person that reports the similiar error, but no solution:
http://lists.digium.com/pipermail/asterisk-users/2006-October/169629.html
Comments:By: Olle Johansson (oej) 2006-11-10 08:04:00.000-0600

Please attach the SIP debug (as we require in the bug guidelines) with verbose set to 4 and debug set to 4 - make sure you capture everything (that can be captured :-) ).

By: Drake Swokowski (drake) 2006-11-13 12:53:44.000-0600

.txt file is the sip debug
.cap is the traffic capture from the network interface

verbosity may be more than 4.

lycka till!! ;)

By: Serge Vecher (serge-v) 2006-11-17 09:54:08.000-0600

drake: quite a bit has changed has changed in chan_sip since 1.2.10. Also debug output needs to be enabled in logger.conf, so ...:
1) upgrade to 1.2.13
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddgc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
sip debug
5) Attach verbosedebug.txt to the issue.

By: Olle Johansson (oej) 2006-12-29 05:47:34.000-0600

Please test again. If the problem still exists, I would like access to your server if possible.

By: Joshua C. Colp (jcolp) 2007-01-17 23:15:23.000-0600

I'm closing this out for now since you did not reply to serge's request or oej. If this is still an issue please read and follow what they said and reopen. Thanks!