[chan-capi-users] Two calls to the same MSN on a BRI

Jim Hickstein jxh at jxh.com
Sat May 10 05:57:59 CEST 2008


Hi, Armin! Remember this thread?

>> The first call is taken in d-channel mode because of a wrong
>> bchannelinfo value:
>>    BChannelinformation            = <02 00>
>> This '02' says 'neither B nor D channel is used' and chan-capi then
>> uses D-channel (ISDN#00) for this connection.
>> The second call is the same and since there only one pseudo
>> channel available, you get the warning.
>> So the question is why is this wrong bchannelinfo value signaled?
> 
> I suppose this is a question for Eicon/Dialogic, arising how I have my 
> Diva Server 4BRI/8M 2.0 configured.  Is Marco Löwl listening?

I did trade some email with Marco and he suggested I try the 8.3.1 driver.  By 
the time I got back to this, 8.5 was current, so I've done that.  The 
installation went smoothly, and it seems happy enough, up to a point.

But now, where "set verbose 5; capi debug" in Asterisk used to show me things, I 
now get nothing.

A lot is right:

$ sudo asterisk -vvvgc
   == Parsing '/etc/asterisk/asterisk.conf': Found
   == Parsing '/etc/asterisk/extconfig.conf': Found
Asterisk 1.2.14, Copyright (C) 1999 - 2006 Digium, Inc. and others.
...
  [chan_capi.so] => (Common ISDN API for Asterisk)
   == Parsing '/etc/asterisk/capi.conf': Found
     -- capi D ISDN1#00 (*:capi-in) contr=1 devs=2 EC=1,opt=4,tail=0
     -- capi B ISDN1#01 (*:capi-in) contr=1 devs=2 EC=1,opt=4,tail=0
     -- capi B ISDN1#02 (*:capi-in) contr=1 devs=2 EC=1,opt=4,tail=0
     -- listening on contr1 CIPmask = 0x1fff03ff
May  9 22:31:38 NOTICE[4478]: chan_capi.c:5911 cc_post_init_capi: Unused contr2
May  9 22:31:38 NOTICE[4478]: chan_capi.c:5911 cc_post_init_capi: Unused contr3
May  9 22:31:38 NOTICE[4478]: chan_capi.c:5911 cc_post_init_capi: Unused contr4
   == Registered channel type 'CAPI' (Common ISDN API Driver (1.0.1))
   == Registered application 'capiCommand'

... [there's only one configured contr so [234] unused is expected -jxh]
...
Asterisk Ready.
*CLI> capi info
Common ISDN API Driver (1.1.1) www.chan-capi.org
Contr1: 2 B channels total, 2 B channels free.
Contr2: 2 B channels total, 2 B channels free. (unused)
Contr3: 2 B channels total, 2 B channels free. (unused)
Contr4: 2 B channels total, 2 B channels free. (unused)
*CLI> capi show channels
CAPI B-channel information:
Line-Name       NTmode state i/o bproto isdnstate   ton  number
----------------------------------------------------------------
ISDN1#02         no    -----  -  trans              0x00 ''->''
ISDN1#01         no    -----  -  trans              0x00 ''->''
*CLI> set verbose 5
Verbosity was 3 and is now 5
*CLI> capi debug
CAPI Debugging Enabled

Yet, when I make a call to the number on ISDN1#01, I see nothing here, where I 
used to get tons of debug output.

The BRI is good (green and amber lights on the port1 connector on the Diva; the 
http://diva:10005 thing shows "failed" incoming calls that result; layer 1 
"Activated", layer 2 "SPID Initialised").  Just nothing coming out the top of 
chan_capi.  incomingmsn=* is present.

I sense that I'm missing something simple.  What is it?


More information about the Chan-capi-users mailing list