[Asterisk-Users] chan_sccp bug / problem

Remco Barende asterisk at barendse.to
Mon Jan 31 11:52:00 MST 2005


Hi list!

I'm having some problems with chan_sccp and a Kirk IP600. Basically the 
handsets work (they emulate a Cisco 7940) but I have the following issues:


1. If a handset is in a conversation and there is a new incoming call,
the incoming audio is muted (but the other party can still hear anything
spoken on the handset). What is normal Asterisk behaviour, that a handset 
is left alone when it is busy or is there still signalling going to the 
handset even when it is in conversation (I guess that is what is happening 
now).

2. Asterisk seems to crash at random, sometimes after an hour sometimes 
after two days. It just exits with a Segfault:

I did a trace on asterisk and this is the result:

Reading symbols from /usr/lib/asterisk/modules/cdr_pgsql.so...done.
Loaded symbols for /usr/lib/asterisk/modules/cdr_pgsql.so
Reading symbols from /usr/lib64/libpq.so.3...done.
Loaded symbols for /usr/lib64/libpq.so.3
Reading symbols from /lib64/libcrypt.so.1...done.
Loaded symbols for /lib64/libcrypt.so.1
Reading symbols from /lib64/libnsl.so.1...done.
Loaded symbols for /lib64/libnsl.so.1
Reading symbols from /usr/lib/asterisk/modules/chan_sccp.so...done.
Loaded symbols for /usr/lib/asterisk/modules/chan_sccp.so
Reading symbols from /lib64/libgcc_s.so.1...done.
Loaded symbols for /lib64/libgcc_s.so.1
#0  sccp_pbx_read (ast=0x0) at sccp_pbx.c:38
38            if (f->frametype == AST_FRAME_VOICE) {
(gdb)
(gdb)
(gdb) bt
# 0  sccp_pbx_read (ast=0x0) at sccp_pbx.c:38
# 1  0x0000000000416261 in ast_read (chan=0x6439f0) at channel.c:1337
# 2  0x000000000041aa42 in ast_waitfordigit (c=0x6439f0, ms=2) at
channel.c:1140
# 3  0x0000002a9e326af1 in sccp_start_channel (data=0x0) at sccp_pbx.c:505
# 4  0x0000002a95774c6b in start_thread () from /lib64/tls/libpthread.so.0
# 5  0x0000002a95e8ce43 in thread_start () from /lib64/tls/libc.so.6
# 6  0x0000000000000000 in ?? ()

The box is running a RHEL Rebuild for x86_64 arch, and Asterisk 
1.0.5-BRIstuffed-0.2.0-RC5

I guess this is a bug, not a feature?





More information about the asterisk-users mailing list