[Asterisk-Dev] SIP crash backtrace

John Todd jtodd at loligo.com
Fri Jul 4 10:44:40 MST 2003

I have about 6 or 7 SIP "register =>" statements in my sip.conf, 
which seems to be killing Asterisk regularly (it seems after I make a 
SIP call, it dies about 50% of the time.)

Note: One of my "register =>" lines always results in a failure - the 
server refuses the request (it's to one of my "test" SIP proxies, and 
that machine is down...)  Perhaps this is relevant.

I am not able to get meaningful debug on the console due to an 
inexplicable slowdown of console messages to the point of stoppage. 
I think this is due to problems unrelated to Asterisk.

#0  sip_reg_timeout (data=0x80e0a68) at chan_sip.c:2700
2700                    p->registry = NULL;
(gdb) bt
#0  sip_reg_timeout (data=0x80e0a68) at chan_sip.c:2700
#1  0x080518b5 in ast_sched_runq (con=0x80d9a58) at sched.c:330
#2  0x4345505e in do_monitor (data=0x0) at chan_sip.c:4890
#3  0x40033b9c in pthread_start_thread (arg=0x43c5ebe0) at manager.c:274


More information about the asterisk-dev mailing list