Hi chan_capi users, this thing is awesome, no delays like in modem_i4l! Plus, it got those nice ISDN features. Here's my question: Does my service provider (Deutsche Telekom) have to provide me with these Services (CD, ECT)? (the Readme in 0.2.5 says "does not relay on service CD") I know, that I don't have CFU,CFNR,CFBS (which I would have to order seperately). How likely would it be that an ISDN-PBX with an internal S0 supports CD,ECT services, if the line to my telco doesn't? Here's what I get: I get REASON=0x3400 as a disconnect indicator when trying out CD. (calling in on one ISDN line from my mobile number deflecting to my other ISDN line; as laid out in the Readme) I get REASON=0x3490 as a disconnect indicator for the onHOLD party, trying ECT. capiECT says the call has been answered (I picked up the ringing phone where the call was being transferred to), but then I get a warning "file.c Line 823 (ast_waitstream): Unexpected control subclass '14'". This nice lady is reading the digits of the calling party, then nothing happens until a timeout occurrs. I am not a C programmer but I know how to read some source code ... I'd gladly help where I can! Any suggestions are greatly appreciated. Alex - Alexander Noack - Vitus-Bering-Str. 3 - 18106 Rostock - Germany - -Tel: +49 (381) 12839893 -Fax: +49 (381) 12839901 -Web: www.gaussdivision.de
Hi Alexander, you will probably find no Telco that uses ECT in their network, app_capiECT works fine on most isdn PBXes though. Concerning app_capiCD...just give it a try, but of course your telco will have to support CD. "does not rely on sservice CD" refers to the way it is implemented in chan_capi (it uses an INFO_REQ instead of a FACILITY_REQUEST). My cheap isdn pbx with an internal S0 bus happily supports ECT but not CD (so i have 1 capi card on the internal S0 bus for ECT and 1 card on the external line for CD). regards kapejod -- Klaus-Peter Junghanns CEO,CTO Junghanns.NET GmbH Breite Strasse 13 - 12167 Berlin - Germany fon: +49 30 79705392 fax: +49 30 79705391 iaxtel: 1-700-157-8753 email: kpj@junghanns.net http://www.junghanns.net/asterisk Am Son, 2003-09-14 um 17.57 schrieb Alexander Noack:> Hi chan_capi users, > > this thing is awesome, no delays like in modem_i4l! > Plus, it got those nice ISDN features. > > Here's my question: > Does my service provider (Deutsche Telekom) have to provide me with > these Services (CD, ECT)? > (the Readme in 0.2.5 says "does not relay on service CD") > > I know, that I don't have CFU,CFNR,CFBS (which I would have to order > seperately). > How likely would it be that an ISDN-PBX with an internal S0 supports > CD,ECT services, if the line to my telco doesn't? > > > Here's what I get: > I get REASON=0x3400 as a disconnect indicator when trying out CD. > (calling in on one ISDN line from my mobile number deflecting to my > other ISDN line; as laid out in the Readme) > > I get REASON=0x3490 as a disconnect indicator for the onHOLD party, > trying ECT. > capiECT says the call has been answered (I picked up the ringing phone > where the call was being transferred to), but then I get a warning > "file.c Line 823 (ast_waitstream): Unexpected control subclass '14'". > This nice lady is reading the digits of the calling party, then nothing > happens until a timeout occurrs. > > > I am not a C programmer but I know how to read some source code ... I'd > gladly help where I can! > > Any suggestions are greatly appreciated. > Alex > > - Alexander Noack > - Vitus-Bering-Str. 3 > - 18106 Rostock > - Germany > - > -Tel: +49 (381) 12839893 > -Fax: +49 (381) 12839901 > -Web: www.gaussdivision.de > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users
Hello All,
 
I have been using chan_capi with eicon diva server 4 Bri for a few
months now and been very happy with the results. I have now got a small
problem. I needed to upgrade - get more lines in - during an office
move. So we moved office and landed with 3 ISDN2e lines.
 
I can place calls perfectly. Problem is Asterisk is only receiving calls
on 1 channel - so effectively I am only getting 1 out of 3 calls (BT ran
some protocol tests on the line). The ISDN lines are setup to all share
the same number.
 
I have adjusted capi.conf from
 
;
; CAPI config
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
 
[interfaces]
 
;isdnmode=ptp
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
 
[interfaces]
 
;isdnmode=ptp
msn=870582
incomingmsn=870582
;incomingmsn=870582,870583,870878,871310,871743,871821,872215,872355
;incomingmsn=*
controller=2
context=capiIN
devices=2
 
To:
 
 
 
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
 
[interfaces]
 
;isdnmode=ptp
;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
 
[interfaces]
 
;isdnmode=ptp
msn=870582
incomingmsn=870582
;incomingmsn=870582,870583,870878,871310,871743,871821,872215,872355
;incomingmsn=*
controller=1,2,3
context=capiIN
devices=6
 
the asterisk startup script is:
;
#!/bin/bash
case "$1" in
    stop)
        killall asterisk
        rmmod capi
        rmmod divacapi
        rmmod divas
 
        ;;
 
    start)
        modprobe divas
        modprobe divacapi
        modprobe capi
 
        divactrl load -c 1 -f ETSI -u -t 0
 
        asterisk
        ;;
 
I have tried various computations of the config - but don't really
understand it - can someone help please????
 
Regards
 
Nick
Hi, I'm new to this list and also new to Asterisk. I've set up asterisk in a way that my localclients connect to it thru IAXComm, this works ok. In my asterisk server I have a Fritz!Card from AVM with the AVM Capi driver. People are able to call to my ISDN card from outside and they get connected to my IAXComm clients like the way I want to. But I seem keep having trouble setting things right for dialout. This is what I've set up in my extensions.conf: exten => _0XXXXXXXXXX,1,Dial,CAPI/@433655192:BYEXTENSION,5,tr It looks likes it is trying to dialout but still hangsup after a timeout occurs. What can I be doing wrong? this is my capi.conf msn=433655192 incomingmsn=433655192 controller=1 softdtmf=1 accountcodecontext=default ;echosquelch=1 ;echocancel=yes ;echotail=64 devices=2 -- Met vriendelijke groet, Ing. Marc Dirix Electronics Design Graaf Wolter Hoenstr 2 6243 BE Geulle Nederland.
Hi Guys, does anyone know how to fix chan_capi to work with the current CVS HEAD? It's no longer possible to compile after the recent changes in the locking... Regards, Andreas _________________________________________________________________ There’s never been a better time to get Xtra JetStream @ http://xtra.co.nz/jetstream
I just installed the lastest cvs version of asterisks and addons but after this the chan_capi doesn't compile anymore with ne new header files ? Anyone an idea ? Thnx. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050106/fc63935a/attachment.htm
Hello,
I have installed asterisk but it is impossible to get compiled the 
chan_capi 0.3.5.
I am using slackware 10.1 (kernel 2.4.29) and I am getting the following 
when I issue gcc -v
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/specs
Configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking
--with-gnu-ld --verbose --target=i486-slackware-linux
--host=i486-slackware-linux
Thread model: posix
gcc version 3.3.4
The same happened also with Slackware 9.1 but I do not have anymore an
installation to send info.
I am getting the following errors and in the end of this message I have
part of the file stddef.h.
Any suggestion is welcomed.
Thank you in advance,
Dimitris Kounalakis
----------------------------------------------
root@asterias:~/chan_capi-0.3.5# make
gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -g
-I/usr/include/asterisk -D_REENTRANT -D_GNU_SOURCE -O6 -march=athlon
-DCAPI_ES -DCAPI_GAIN -DCAPI_SYNC -Wno-missing-prototypes
-Wno-missing-declarations -DCRYPTO   -c -o chan_capi.o chan_capi.c
In file included from /usr/include/time.h:38,
                 from /usr/include/pthread.h:21,
                 from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/include/stddef.h:213: error:
syntax error before "typedef"
In file included from /usr/include/pthread.h:21,
                 from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
/usr/include/time.h:60: error: syntax error before "typedef"
/usr/include/time.h:74: error: parse error before
"__BEGIN_NAMESPACE_STD"
/usr/include/time.h:76: error: syntax error before "typedef"
/usr/include/time.h:129: error: parse error before
"__BEGIN_NAMESPACE_STD"
/usr/include/time.h:131: error: syntax error before "struct"
/usr/include/time.h:178: error: parse error before
"__BEGIN_NAMESPACE_STD"
/usr/include/time.h:181: error: syntax error before "extern"
/usr/include/time.h:181: error: parse error before "__THROW"
/usr/include/time.h:184: error: parse error before "__THROW"
/usr/include/time.h:188: error: parse error before "__THROW"
/usr/include/time.h:191: error: parse error before "__THROW"
/usr/include/time.h:199: error: parse error before "__THROW"
/usr/include/time.h:226: error: parse error before
"__BEGIN_NAMESPACE_STD"
/usr/include/time.h:229: error: syntax error before "extern"
/usr/include/time.h:229: error: parse error before "__THROW"
/usr/include/time.h:233: error: parse error before "__THROW"
/usr/include/time.h:248: error: parse error before
"__BEGIN_NAMESPACE_STD"
/usr/include/time.h:251: error: syntax error before "extern"
/usr/include/time.h:251: error: parse error before "__THROW"
/usr/include/time.h:254: error: parse error before "__THROW"
/usr/include/time.h:272: error: syntax error before "extern"
In file included from /usr/include/pthread.h:24,
                 from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
/usr/include/signal.h:31: error: parse error before "__BEGIN_DECLS"
In file included from /usr/include/signal.h:33,
                 from /usr/include/pthread.h:24,
                 from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
/usr/include/bits/sigset.h:23: error: syntax error before "typedef"
In file included from /usr/include/bits/pthreadtypes.h:23,
                 from /usr/include/pthread.h:25,
                 from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
/usr/include/bits/sched.h:83: error: syntax error before "struct"
In file included from /usr/include/asterisk/lock.h:17,
                 from chan_capi.c:14:
...............
------------------------------------------------------------------------------------
File: stddef.h
209: #ifndef __SIZE_TYPE__
210: #define __SIZE_TYPE__ long unsigned int
211: #endif
212: #if !(defined (__GNUG__) && defined (size_t))
213: typedef __SIZE_TYPE__ size_t;
214: #ifdef __BEOS__
215: typedef long ssize_t;
216: #endif /* __BEOS__ */