[Asterisk-Users] CHAN_CAPI problem

Armin Schindler armin at melware.de
Wed Jan 11 02:24:04 MST 2006


There is no 'sending-complete'/'setup' info-element, please use
immediate=yes in capi.conf

Armin


On Wed, 11 Jan 2006 asterisk at frameweb.it wrote:
> Thank you very much for your attention;
> Here is what you asked for:
> ***********************************************************************************
> asteriskge03*CLI> set verbose 15
> Verbosity is at least 15
> asteriskge03*CLI> capi debug
> CAPI Debugging Enabled
> asteriskge03*CLI> capi info
> Contr1: 2 B channels total, 2 B channels free.
> 
> CONNECT_IND ID=002 #0x2011 LEN=0047
>   Controller/PLCI/NCCI            = 0x101
>   CIPValue                        = 0x1
>   CalledPartyNumber               = <a1>104695467
>   CallingPartyNumber              = <21 81>108680550
>   CalledPartySubaddress           = default
>   CallingPartySubaddress          = default
>   BC                              = <80 90 a3>
>   LLC                             = default
>   HLC                             = default
>   AdditionalInfo                  = default
> 
>     -- CONNECT_IND
> (PLCI=0x101,DID=104695467,CID=108680550,CIP=0x1,CONTROLLER=0x1)
>        > BRI1: msn='*' DNID='104695467' MSN
>   == BRI1: Incoming call '0108680550' -> '104695467'
> INFO_IND ID=002 #0x2012 LEN=0017
>   Controller/PLCI/NCCI            = 0x101
>   InfoNumber                      = 0x1e
>   InfoElement                     = <82 81>
> 
> INFO_RESP ID=002 #0x2012 LEN=0012
>   Controller/PLCI/NCCI            = 0x101
> 
>     -- BRI1: info element PI 82 81
>        > BRI1: Not end-to-end ISDN
> INFO_IND ID=002 #0x2013 LEN=0025
>   Controller/PLCI/NCCI            = 0x101
>   InfoNumber                      = 0x70
>   InfoElement                     = <a1>104695467
> 
> INFO_RESP ID=002 #0x2013 LEN=0012
>   Controller/PLCI/NCCI            = 0x101
> 
>     -- BRI1: info element CALLED PARTY NUMBER
>        > BRI1: INFO_IND DID digits not used in this state.
> INFO_IND ID=002 #0x2014 LEN=0016
>   Controller/PLCI/NCCI            = 0x101
>   InfoNumber                      = 0x18
>   InfoElement                     = <89>
> 
> INFO_RESP ID=002 #0x2014 LEN=0012
>   Controller/PLCI/NCCI            = 0x101
> 
>     -- BRI1: info element CHANNEL IDENTIFICATION 89
> DISCONNECT_IND ID=002 #0x2017 LEN=0014
>   Controller/PLCI/NCCI            = 0x101
>   Reason                          = 0x0
> 
> DISCONNECT_RESP ID=002 #0x2017 LEN=0012
>   Controller/PLCI/NCCI            = 0x101
> 
>     -- BRI1: DISCONNECT_IND on incoming without pbx, doing hangup.
>   == BRI1: CAPI Hangingup
>   == BRI1: Interface cleanup PLCI=0x101
>        > CAPI devicestate requested for BRI1/104695467
> 
> ***********************************************************************************
> 
> The lines:
> 
> BRI1: DISCONNECT_IND on incoming without pbx, doing hangup.
>   == BRI1: CAPI Hangingup
>   == BRI1: Interface cleanup PLCI=0x101
>        > CAPI devicestate requested for BRI1/104695467
> 
> appeared on the console WHILE I was still earing the ring tone on the
> calling phone. When I , at last, after other 4 rings, hangup the calling
> phone,
> nothing changed on the console
> 
> 
> Andrea
> 
> 
> 
>                                                                            
>              Armin Schindler                                               
>              <armin at melware.de                                             
>              >                                                          To 
>              Sent by:                  Asterisk Users Mailing List -       
>              asterisk-users-bo         Non-Commercial Discussion           
>              unces at lists.digiu         <asterisk-users at lists.digium.com>   
>              m.com                                                      cc 
>                                                                            
>                                                                    Subject 
>              10/01/2006 19.16          Re: [Asterisk-Users] CHAN_CAPI      
>                                        problem                             
>                                                                            
>              Please respond to                                             
>               Asterisk Users                                               
>               Mailing List -                                               
>               Non-Commercial                                               
>                 Discussion                                                 
>              <asterisk-users at l                                             
>              ists.digium.com>                                              
>                                                                            
>                                                                            
> 
> 
> 
> 
> On Tue, 10 Jan 2006 asterisk at frameweb.it wrote:
> > Thank you.
> > I already downloaded and installed it (they are dated 07-01-2006, version
> > 0.6.3, correct ?)
> 
> Yes.
> 
> > I maked clean, make and make install.
> >
> > Nothing changed, dial out perfect, dial in: (capi debug on)
> >
> > asteriskge03*CLI> capi info
> > Contr1: 2 B channels total, 2 B channels free.
> > asteriskge03*CLI>
> > asteriskge03*CLI>
> >     -- CONNECT_IND
> > (PLCI=0x101,DID=104695467,CID=108680550,CIP=0x1,CONTROLLER=0x1)
> >   == BRI1: Interface cleanup PLCI=0x101
> >
> > BRI1 is the name of my interface
> >
> > could it be a kernel issue ?? I am using SUSE Linux 10;
> 
> I don't think so. Please increase the the verbose level to 5
> (set verbose 5) in addition to 'capi debug'.
> 
> Armin
> 
> > kernel :  2.6.13-15.7-smp
> >
> > Andrea
> >
> >
> >
> >
> 
> >              Armin Schindler
> 
> >              <armin at melware.de
> 
> >              >
> To
> >              Sent by:                  Asterisk Users Mailing List -
> 
> >              asterisk-users-bo         Non-Commercial Discussion
> 
> >              unces at lists.digiu         <asterisk-users at lists.digium.com>
> 
> >              m.com
> cc
> >
> 
> >
> Subject
> >              10/01/2006 18.29          Re: [Asterisk-Users] CHAN_CAPI
> 
> >                                        problem
> 
> >
> 
> >              Please respond to
> 
> >               Asterisk Users
> 
> >               Mailing List -
> 
> >               Non-Commercial
> 
> >                 Discussion
> 
> >              <asterisk-users at l
> 
> >              ists.digium.com>
> 
> >
> 
> >
> 
> >
> >
> >
> >
> > I suggest you use the newer chan_capi-cm (loadable from sourceforge.net).
> >
> > Armin
> >
> > On Tue, 10 Jan 2006 asterisk at frameweb.it wrote:
> > > Hi all,
> > > I installed asterisk stable cvs 1.2 and chan_capi 0.4.0 PRE1, with one
> > AVM
> > > Fritz Card ISDN connected to a Telecom NT1 Plus
> > >
> > > I configured asterisk via AMP.
> > > No problem in making calls.
> > > If I try to ring the ISDN Phone Number, I don't see anything on the
> > > asterisk Console,
> > > I I activate the capi debug , I see the ring on the capi channel.
> > > If the context were wrong , I anyway should  see some line about
> this....
> > >
> > > Why I cannot see anything on asterisk ,nor in the
> /var/log/asterisk/full
> > ?
> > >
> > > here is my /etc/asterisk/capi.conf
> > >
> > > asteriskge03:/etc/asterisk # cat capi.conf
> > > ;
> > > ; CAPI config
> > > ;
> > > ;
> > >
> > > ; general section
> > >
> > > [general]
> > > nationalprefix=0
> > > internationalprefix=00
> > > rxgain=0.8
> > > txgain=0.8
> > > ;ulaw=yes        ;set this, if you live in u-law world instead of a-law
> > >
> > > ; interface sections ...
> > >
> > > [BRI1]          ;this example interface gets name 'ISDN1' and may be
> any
> > >                  ;name not starting with 'g' or 'contr'.
> > > ;ntmode=yes      ;if isdn card operates in nt mode, set this to yes
> > > isdnmode=msn     ;'MSN' (point-to-multipoint) or 'DID' (direct inward
> > dial)
> > >                  ;when using NT-mode, 'DID' should be set in any case
> > > incomingmsn=*    ;allow incoming calls to this list of MSNs/DIDs, * =
> any
> > > ;defaultcid=123  ;set a default caller id to that interface for
> dial-out,
> > >                  ;this caller id will be used when dial option 'd' is
> > set.
> > > ;controller=0    ;ISDN4BSD default
> > > ;controller=7    ;ISDN4BSD USB default
> > > controller=1     ;capi controller number to use
> > > group=1          ;dialout group
> > > ;prefix=0        ;set a prefix to calling number on incoming calls
> > > softdtmf=on      ;enable/disable software dtmf detection, recommended
> for
> > > AVM cards
> > > relaxdtmf=on     ;in addition to softdtmf, you can use relaxed dtmf
> > > detection
> > > accountcode=     ;Asterisk accountcode to use in CDRs
> > > context=from-pstn  ;context for incoming calls
> > > holdtype=hold    ;when Asterisk puts the call on hold, ISDN HOLD will
> be
> > > used. If
> > >                  ;set to 'local' (default value), no hold is done and
> > > Asterisk may
> > >                  ;play MOH.
> > > ;immediate=yes   ;DID: immediate start of pbx with extension 's' if no
> > > digits were
> > >                  ;     received on incoming call (no destination number
> > > yet)
> > >                  ;MSN: start pbx on CONNECT_IND and don't wait for
> > > SETUP/SENDING-COMPLETE.
> > >                  ;     info like REDIRECTINGNUMBER may be lost, but
> this
> > is
> > > necessary for
> > >                  ;     drivers/pbx/telco which does not send SETUP or
> > > SENDING-COMPLETE.
> > > ;echosquelch=1   ;_VERY_PRIMITIVE_ echo suppression
> > > ;echocancel=yes  ;EICON DIVA SERVER (CAPI) echo cancelation
> > >                  ;(possible values: 'no', 'yes', 'force', 'g164',
> 'g165')
> > > echocancelold=yes;use facility selector 6 instead of correct 8
> (necessary
> > > for older eicon drivers)
> > > ;echotail=64     ;echo cancel tail setting
> > > ;bridge=yes      ;native bridging (CAPI line interconnect) if available
> > > ;callgroup=1     ;Asterisk call group
> > > devices=2        ;number of concurrent calls on this controller
> > >                  ;(2 makes sense for single BRI, 30 for PRI)
> > >
> > > thanks in advance,
> > > Andrea
> > >
> > > Chi ricevesse questa mail per errore e' gentilmente pregato di
> > cancellarla.
> > >
> > > Visitate il sito http://www.frameweb.it
> > >
> > > _______________________________________________
> > > --Bandwidth and Colocation provided by Easynews.com --
> > >
> > > Asterisk-Users mailing list
> > > To UNSUBSCRIBE or update options visit:
> > >    http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > Asterisk-Users mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > Asterisk-Users mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 



More information about the asterisk-users mailing list