[Asterisk-Users] IAX2 call causes SEGFAULT

[Jim Gottlieb]

Hi.  I'm trying to do a pretty generic IAX2 call between two asterisk
machines, but when the call arrives, I get a SEGFAULT.  The receiving
machine is running the latest code from the stable branch, though this
also happened with a snapshot from 2004-01-30 so I don' think it's a
recent problem in the code.  More likely something I'm doing wrong, but
I can't figure out what.

The IAX2 debug shows:

x-Frame Retry[No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: NEW    
   Timestamp: 00001ms  SCall: 00001  DCall: 00000 [192.168.14.21:4569]
   VERSION         : 2
   CALLED NUMBER   : 16026247788
   CALLING NUMBER  : 6026241111
   LANGUAGE        : en
   USERNAME        : guest
   FORMAT          : 2
   CAPABILITY      : 65282
   ADSICPE         : 2

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: ACCEPT 
   Timestamp: 00001ms  SCall: 00001  DCall: 00001 [192.168.14.21:4569]
   FORMAT          : 2
tus01*CLI> 
Rx-Frame Retry[No] -- OSeqno: 001 ISeqno: 000 Type: VOICE   Subclass: 2
   Timestamp: 00019ms  SCall: 00001  DCall: 00000 [192.168.14.21:4569]
Tx-Frame Retry[-01] -- OSeqno: 000 ISeqno: 002 Type: IAX     Subclass: ACK    
   Timestamp: 00019ms  SCall: 00001  DCall: 00001 [192.168.14.21:4569]
Tx-Frame Retry[000] -- OSeqno: 001 ISeqno: 001 Type: CONTROL Subclass: (11?)
   Timestamp: 00002ms  SCall: 00001  DCall: 00001 [192.168.14.21:4569]
tus01*CLI> 
Disconnected from Asterisk server


The backtraces seem to show something different each time.  Once
it referenced chan_iax2.c, but other times it seems to show random stuff:

#0  0x4018f90e in __select () from /lib/i686/libc.so.6
#1  0x462514cc in ?? ()
#2  0x0805c723 in ast_waitfor (c=0x80ef2c0, ms=1000) at channel.c:930


#0  0x4018e227 in __poll (fds=0x80ede90, nfds=1, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:63
#1  0x08051a8c in ast_io_wait (ioc=0x80ede70, howlong=-1) at io.c:254
#2  0x42542ef7 in do_monitor (data=0x0) at chan_mgcp.c:2543
#3  0x40027bfd in pthread_start_thread (arg=0x42749c00) at manager.c:262


Thanks...