asterisk users - Jun 2004 - chan_capi problem - hangup???

Hi,

I installed Asterisk with CAPI support. Everything works fine while 
starting Asterisk, but when a call comes in Asterisk hangsup the call 
after two times of ringing.

The output is like:

Jun 24 22:19:49 NOTICE[1082178480]: chan_capi.c:1931 capi_handle_msg: 
CONNECT_IND ID=002 #0x011d LEN=0048
   Controller/PLCI/NCCI            = 0x101
   CIPValue                        = 0x10
   CalledPartyNumber               = <c1>**some_number**
   CallingPartyNumber              = <21 83>**some_number**
   CalledPartySubaddress           = default
   CallingPartySubaddress          = default
   BC                              = <80 90 a3>
   LLC                             = default
   HLC                             = <91 81>
   AdditionalInfo                  = default

   == CONNECT_IND 
(PLCI=0x101,DID=**some_number**,CID=**some_number**,CIP=0x10,CONTROLLER=0x1)
Jun 24 22:19:49 WARNING[1086696368]: pbx.c:1819 ast_pbx_run: Channel 
'CAPI[contr1/**some_number**]/0' sent into invalid extension 's'
in
context 'default', but no invalid handler
     -- CAPI Hangingup
        > activehangingup
     -- started pbx on channel (callgroup=0)!
     -- INFO_IND ID=002 #0x011e LEN=0023
   Controller/PLCI/NCCI            = 0x101
   InfoNumber                      = 0x70
   InfoElement                     = <c1>**some_number**


I read in the mailing list archives of commenting out line 2615 in 
chan_capi.c, but that did not change anything.

Has anybody got an idea what the error:

"Channel 'CAPI[contr1/**some_number**]/0' sent into invalid
extension
's' in context 'default', but no invalid handler"

could be and how to solve it.

Thanks
Tobi

Tobi,

By the looks of it your problem has nothing to do with chan_capi.
> Jun 24 22:19:49 WARNING[1086696368]: pbx.c:1819 ast_pbx_run: Channel 
> 'CAPI[contr1/**some_number**]/0' sent into invalid extension
's' in
> context 'default', but no invalid handler
Have a look at the error message - it tells you the context the 
controller puts you into does not have an exten s=> handler, nor does 
it have an invalid handler (exten i=> ). You can discover this context 
by examining the context=> line in your capi.conf



Create one, and see if that fixes the problem.

Andrew

_________________________
Andrew Yager
Real World Technology Solutions
Real People, Real SolUtions (tm)
ph: (02) 9945 2567 fax: (02) 9945 2566
mob: 0405 15 2568
http://www.rwts.com.au/
_________________________
On 25/06/2004, at 6:28 AM, Tobi Anton wrote:

Hi Tobi, 
> I installed Asterisk with CAPI support. Everything works fine 
> while starting Asterisk, but when a call comes in Asterisk 
> hangsup the call after two times of ringing.
> 
> The output is like:
> 
> Jun 24 22:19:49 NOTICE[1082178480]: chan_capi.c:1931 capi_handle_msg: 
> CONNECT_IND ID=002 #0x011d LEN=0048
>    Controller/PLCI/NCCI            = 0x101
>    CIPValue                        = 0x10
>    CalledPartyNumber               = <c1>**some_number**
>    CallingPartyNumber              = <21 83>**some_number**
>    CalledPartySubaddress           = default
>    CallingPartySubaddress          = default
>    BC                              = <80 90 a3>
>    LLC                             = default
>    HLC                             = <91 81>
>    AdditionalInfo                  = default
> 
>    == CONNECT_IND
> (PLCI=0x101,DID=**some_number**,CID=**some_number**,CIP=0x10,C
> ONTROLLER=0x1)
> Jun 24 22:19:49 WARNING[1086696368]: pbx.c:1819 ast_pbx_run: 
> Channel 'CAPI[contr1/**some_number**]/0' sent into invalid 
> extension 's' in context 'default', but no invalid handler
>      -- CAPI Hangingup
>         > activehangingup
>      -- started pbx on channel (callgroup=0)!
>      -- INFO_IND ID=002 #0x011e LEN=0023
>    Controller/PLCI/NCCI            = 0x101
>    InfoNumber                      = 0x70
>    InfoElement                     = <c1>**some_number**
> 
> 
> I read in the mailing list archives of commenting out line 
> 2615 in chan_capi.c, but that did not change anything.
> 
> Has anybody got an idea what the error:
> 
> "Channel 'CAPI[contr1/**some_number**]/0' sent into invalid 
> extension 's' in context 'default', but no invalid
handler"
Do you have DIDs (PTP-ISDN)?

Bye

Felix

ePyron Felix Deierlein wrote:
> 
> Do you have DIDs (PTP-ISDN)?
> 
> Bye
> 
> Felix
yes

Tobi, 
> > Do you have DIDs (PTP-ISDN)?
> yes
then I guess that I have the same problem.
If I get a overlaped dial from PSTN, i get only the first did-digit as
extension
, p.e: my number 8993-12 then it goes to 89931 and that extension does not
exist
If I get a call from ISDN (or maybe mobile) with block transfer, I get
899312 and it works.

For me it seems that chan_capi does not supply inbound overlap-dial. Could
anybody clearify that, please?


Bye


Felix

Hi,

Philipp von Klitzing wrote:

 > Hi!
 >
 >
 >> "Channel 'CAPI[contr1/**some_number**]/0' sent into
invalid
extension 's' in context 'default', but no invalid handler"
 >
 >
 >
 > Look at Asterisk's "standard extensions" like s, i, o and so
forth.
 >
 > Insert this in your context [default] in extensions.conf:
 >
 >   exten => s,1,Answer
 >   exten => s,2,Dial(Local/1234/n)    ; replace 1234 with any valid 
extension
 >
 > Cheers, Philipp
 >
 >
 >

This doesn't change a thing...

I've this config:

capi.conf:

;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]
msn="mymsn"
incomingmsn=*
controller=1
softdtmf=1
accountcodecontext=default
devices=2

extensions.conf:

[general]
static=yes
writeprotect=yes

TRUNK=CAPI

[default]
exten => s,1,Answer
exten => s,2,Background(welcome)

I'm expecting the Asterisk "welcome"-message??? But instead comes
the
hangup?

Any solutions would be great

Thanks
Tobi