Displaying 2 results from an estimated 2 matches for "capi_control".
Did you mean:
call_control
2004 May 24
1
Chan_capi 0.3.1 , Asterisk , 3 x C4 active ISDN card Segmentation fault
...> activehangingup
> sent DISCONNECT_REQ PLCI=0x108
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1084259248 (LWP 3118)]
0x407e81f1 in pipe_msg (PLCI=Variable "PLCI" is not available.) at
chan_capi.c:1319
1319
capi_controllers[p->i->controller]->nfreebchannels++;
(gdb) bt
#0 0x407e81f1 in pipe_msg (PLCI=Variable "PLCI" is not available.) at
chan_capi.c:1319
#1 0x407e98e4 in do_monitor (data=0x0) at chan_capi.c:2182
#2 0x4002a9dd in start_thread () from /lib/tls/libpthread.so.0
#3 0x40166ffa i...
2004 Jul 20
0
received a call waiting CONNECT_IND
...y * just crashed and the nearest events to the time of the core dump
were two "received a call waiting CONNECT_IND" within 23 seconds of each
other according to the code in chan_capi.c this is because of the
following:-
if ((CONNECT_IND_BCHANNELINFORMATION(CMSG)[1] == 0x02) && (!
capi_controllers[controller]->isdnmode)) {
// this is a call waiting CONNECT_IND with BChannelinformation[1]
== 0x02
// meaning "no B or D channel for this call", since we can't do
anything with call waiting now
// just reject it with "user busy"
// however....