Summary:ASTERISK-07352: Sip registration causes Asterisk to hang
Reporter:chrisde (chrisde)Labels:
Date Opened:2006-07-18 04:58:07Date Closed:2006-08-25 11:13:56
Versions:Frequency of
Environment:Attachments:( 0) debug.txt
( 1) sipdebugregister.txt
( 2) sipregister.txt
Description:Having a big amount (40) of sip registration statements
I recognized asterisk to hang every day at half past 7 pm.
Connecting to the asterisk console Asterisk shows all these registrations as "unregistered" or "request sent". While asterisk is trying to register these peers it doesn't allow any other operations like calls. Typing "sip show registry" some times asterisk hangs completely after the 2nd or 3d time.


load average is very low
Comments:By: Serge Vecher (serge-v) 2006-07-18 09:00:49

a. Please read the bug guidelines, all bugs in SIP project must be accompanied by a SIP debug trace.
b. The latest version of Asterisk is 1.2.10. Please upgrade and produce a SIP debug trace using the following.

1) Prepare test environment (reduce the ammount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterik.
4) Enable SIP transaction logging with the following CLI commands:
set debug 4
set verbose 4
sip debug
5) Save complete console log to file and _attach_ said file to the bug

By: chrisde (chrisde) 2006-07-18 10:54:33

the following are the things I did on the console... That already shows that asterisk is hanging. Doing nothing. You have to kill the process. If I wouldn't stop asterisk it would try registering for hours... Noone could connect or do any calls:


sip1-ffm*CLI> sip reload
sip1-ffm*CLI> sip show registry
sip1-ffm*CLI> sip reload
sip1-ffm*CLI> stop now
sip1-ffm*CLI> quit
sip1-ffm:/etc/asterisk# asterisk -r
Asterisk 1.2.10, Copyright (C) 1999 - 2006 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'show license' for details.
Connected to Asterisk 1.2.10 currently running on sip1-ffm (pid = 30788)
Verbosity is at least 5
sip1-ffm*CLI> quit
sip1-ffm:/etc/asterisk# ps aux
root     30788  0.0  0.4 16428 8352 ?        Ss   15:32   0:00 asterisk
root     31297  0.0  0.0  2496  844 pts/0    R+   15:44   0:00 ps aux
sip1-ffm:/etc/asterisk# kill 30788

By: Olle Johansson (oej) 2006-08-07 15:43:33

I need to see a full SIP debug of this, following vechers instructions. Seems like there is a possibility that the subscription expired before re-subscription.

By: Olle Johansson (oej) 2006-08-07 15:44:33

Also, please enable sip history and add a full sip history for one of those subscriptions. Thanks.

By: chrisde (chrisde) 2006-08-09 02:08:02

I appended the requested debug (sipregister.txt). but I don't get the error now... As I told initially it only appeared once a day. So "debug.txt" is when the error occured, but sipregister.txt is only after reloading the sip.conf file with the register= statements in it.

By: Serge Vecher (serge-v) 2006-08-09 09:12:24

what do you mean by "after reloading the sip.conf file with the register= statements in it."?

Also, please make sure you read instructions carefully -- debug.txt is debug => capture. We need to see debug enabled for console and a console snapshot attached.

By: chrisde (chrisde) 2006-08-09 11:05:32

sorry for not being precise. .. I uploaded a new debug (sipdebugregister.txt). The server crashed again now... The debug output is from now. Typing "sip reload" causes Asterisk to crash completely as you can see.

By: Serge Vecher (serge-v) 2006-08-09 11:21:52

again, I don't see any of the debug messages do you have the following line in your logger.conf? console => notice,warning,error,debug

By: Serge Vecher (serge-v) 2006-08-25 11:13:55

no response from the reporter. If you are able to reproduce this with unmodified sources and able to produce requested debug information per instructions provided, please feel free to reopen the issue.