asterisk users - Mar 2005 - possible bug in chan_capi concerning context handling

Hello,
I am trying to configure asterisk 1.0.7pre to get incoming calls from an 
ISDN line using an AVM fritz PCI 2.0 with Chan_capi 0.3.5. My problem is 
that the context is not recognised in the /etc/asterisk/capi.conf
I have in /etc/asterisk/capi.conf 's section "[interfaces]"  the 
following directive
context=isdn

and the following directive in /etc/asterisk/extensions.conf in the 
context [isdn]
[isdn]
exten => s,1,Dial(SIP/${DNID:4},60,tr)


Here follows the debug info I get when an incoming call starts:
----------------------------------------------------------------------------
  == CONNECT_IND 
(PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
    -- creating pipe for PLCI=0x101 msn = 2810111694
       > sent ALERT_REQ PLCI = 0x101
  == Starting CAPI[contr1/2810111694]/3 at ,2810111694,1 failed so 
falling back to exten 's'
  == Starting CAPI[contr1/2810111694]/3 at ,s,1 still failed so falling 
back to context 'default'
Mar 13 11:52:41 WARNING[10744]: pbx.c:1893 ast_pbx_run: Channel 
'CAPI[contr1/2810111694]/3' sent into invalid extension 's' in
context
'default', but no invalid handler
    -- CAPI Hangingup
-----------------------------------------------------------------------------
When I move the "exten => s,1,Dial(${DNID:4},60,tr)"  in the
context
"[default]"  of the /etc/asterisk/extensions.conf, I get the following
debug info and the sip phone rings ok:
------------------------------------------------------------------------------
  == CONNECT_IND 
(PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
    -- creating pipe for PLCI=0x101 msn = 2810111694
       > sent ALERT_REQ PLCI = 0x101
  == Starting CAPI[contr1/2810111694]/4 at ,2810111694,1 failed so 
falling back to exten 's'
  == Starting CAPI[contr1/2810111694]/4 at ,s,1 still failed so falling 
back to context 'default'
    -- Executing Dial("CAPI[contr1/2810111694]/4",
"SIP/111694|60|tr")
in new stack
    -- Called 111694
------------------------------------------------------------------------------

Is this a bug?  It does not handle the context, so, it can not find what 
to do, it works only with the default context.

Thank you in advance,
Dimitris

Do you have an 's' extention in the default context ?

Marco.


Dimitris Kounalakis wrote:
> Hello,
> I am trying to configure asterisk 1.0.7pre to get incoming calls from an 
> ISDN line using an AVM fritz PCI 2.0 with Chan_capi 0.3.5. My problem is 
> that the context is not recognised in the /etc/asterisk/capi.conf
> I have in /etc/asterisk/capi.conf 's section "[interfaces]" 
the
> following directive
> context=isdn
> 
> and the following directive in /etc/asterisk/extensions.conf in the 
> context [isdn]
> [isdn]
> exten => s,1,Dial(SIP/${DNID:4},60,tr)
> 
> 
> Here follows the debug info I get when an incoming call starts:
>
----------------------------------------------------------------------------
> 
>  == CONNECT_IND 
> (PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
>    -- creating pipe for PLCI=0x101 msn = 2810111694
>       > sent ALERT_REQ PLCI = 0x101
>  == Starting CAPI[contr1/2810111694]/3 at ,2810111694,1 failed so 
> falling back to exten 's'
>  == Starting CAPI[contr1/2810111694]/3 at ,s,1 still failed so falling 
> back to context 'default'
> Mar 13 11:52:41 WARNING[10744]: pbx.c:1893 ast_pbx_run: Channel 
> 'CAPI[contr1/2810111694]/3' sent into invalid extension 's'
in context
> 'default', but no invalid handler
>    -- CAPI Hangingup
>
-----------------------------------------------------------------------------
> 
> When I move the "exten => s,1,Dial(${DNID:4},60,tr)"  in the
context
> "[default]"  of the /etc/asterisk/extensions.conf, I get the
following
> debug info and the sip phone rings ok:
>
------------------------------------------------------------------------------
> 
>  == CONNECT_IND 
> (PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
>    -- creating pipe for PLCI=0x101 msn = 2810111694
>       > sent ALERT_REQ PLCI = 0x101
>  == Starting CAPI[contr1/2810111694]/4 at ,2810111694,1 failed so 
> falling back to exten 's'
>  == Starting CAPI[contr1/2810111694]/4 at ,s,1 still failed so falling 
> back to context 'default'
>    -- Executing Dial("CAPI[contr1/2810111694]/4",
"SIP/111694|60|tr") in
> new stack
>    -- Called 111694
>
------------------------------------------------------------------------------
> 
> 
> Is this a bug?  It does not handle the context, so, it can not find what 
> to do, it works only with the default context.
> 
> Thank you in advance,
> Dimitris
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 
>

Thank you for your response Marco.

I do. The problem is that all incomings calls from ISDN are handled by the
default "s" extension in the context [default] and not by an
"s" extension
in the context [isdn] or by the msm numbers as extensions in the context 
[isdn].

So, what is the reason for the context directive in /etc/asterisk/capi.conf
to exit? What exactly is it used for?

Dimitris

*Marco Supino wrote:*
-------------------------------------------------------------------------
Do you have an 's' extention in the default context ?

Marco.


Dimitris Kounalakis wrote:
>/ Hello,
/>/ I am trying to configure asterisk 1.0.7pre to get incoming calls from an 
/>/ ISDN line using an AVM fritz PCI 2.0 with Chan_capi 0.3.5. My problem is 
/>/ that the context is not recognised in the /etc/asterisk/capi.conf
/>/ I have in /etc/asterisk/capi.conf 's section "[interfaces]"
the
/>/ following directive
/>/ context=isdn
/>/ 
/>/ and the following directive in /etc/asterisk/extensions.conf in the 
/>/ context [isdn]
/>/ [isdn]
/>/ exten => s,1,Dial(SIP/${DNID:4},60,tr)
/>/ 
/>/ 
/>/ Here follows the debug info I get when an incoming call starts:
/>/
----------------------------------------------------------------------------
/>/ 
/>/  == CONNECT_IND 
/>/ (PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
/>/    -- creating pipe for PLCI=0x101 msn = 2810111694
/>/       > sent ALERT_REQ PLCI = 0x101
/>/  == Starting CAPI[contr1/2810111694]/3 at ,2810111694,1 failed so 
/>/ falling back to exten 's'
/>/  == Starting CAPI[contr1/2810111694]/3 at ,s,1 still failed so falling 
/>/ back to context 'default'
/>/ Mar 13 11:52:41 WARNING[10744]: pbx.c:1893 ast_pbx_run: Channel 
/>/ 'CAPI[contr1/2810111694]/3' sent into invalid extension
's' in context
/>/ 'default', but no invalid handler
/>/    -- CAPI Hangingup
/>/
-----------------------------------------------------------------------------
/>/ 
/>/ When I move the "exten => s,1,Dial(${DNID:4},60,tr)"  in the
context
/>/ "[default]"  of the /etc/asterisk/extensions.conf, I get the
following
/>/ debug info and the sip phone rings ok:
/>/
------------------------------------------------------------------------------
/>/ 
/>/  == CONNECT_IND 
/>/ (PLCI=0x101,DID=2810111694,CID=2810111694,CIP=0x1,CONTROLLER=0x1)
/>/    -- creating pipe for PLCI=0x101 msn = 2810111694
/>/       > sent ALERT_REQ PLCI = 0x101
/>/  == Starting CAPI[contr1/2810111694]/4 at ,2810111694,1 failed so 
/>/ falling back to exten 's'
/>/  == Starting CAPI[contr1/2810111694]/4 at ,s,1 still failed so falling 
/>/ back to context 'default'
/>/    -- Executing Dial("CAPI[contr1/2810111694]/4",
"SIP/111694|60|tr") in
/>/ new stack
/>/    -- Called 111694
/>/
------------------------------------------------------------------------------
/>/ 
/>/ 
/>/ Is this a bug?  It does not handle the context, so, it can not find what 
/>/ to do, it works only with the default context.
/>/ 
/>/ Thank you in advance,
/>/ Dimitris
/>/ _______________________________________________
/>/ Asterisk-Users mailing list
/>/ Asterisk-Users at lists.digium.com
<http://lists.digium.com/mailman/listinfo/asterisk-users>
/>/ http://lists.digium.com/mailman/listinfo/asterisk-users
/>/ To UNSUBSCRIBE or update options visit:
/>/   http://lists.digium.com/mailman/listinfo/asterisk-users
/>/ /

Hello,

On Sun, Mar 13, 2005 at 12:21:42PM +0200, Dimitris Kounalakis
wrote:
> I am trying to configure asterisk 1.0.7pre to get incoming calls from an 
> ISDN line using an AVM fritz PCI 2.0 with Chan_capi 0.3.5. My problem is 
> that the context is not recognised in the /etc/asterisk/capi.conf
Is this problem specific to asterisk 1.0.7pre?

The statement order in /etc/asterisk/capi.conf may be relevant.
Could you send the complete section of capi.conf.


-- 
Stefan Tichy   <asterisk@pi4tel.de>

Hello *Martijn,
Thank you for your response.
*That was my opinion too, it looses the context due to a bug, and can anyone
confirm it also?
But I have no output from the command "Show channels", and it happens
so quickly that it is impossible to issue the command before falling to the
default context.
In the logs, I can see that the channel exists like CAPI[contr1/2810211694]/0 
but this is druring call only.
Any other way to debug it more (or to solve it)?

My /etc/asterisk/capi.conf is:
-----------------------------------------
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]
controller=1
msn=2810111694
incomingmsn=*
devices=2
softdtmf=1
callgroup=1
context=isdn
------------------------------------------


*Martijn van Oosterhout wrote:
----------------------------------------------------------------------------
*On Sun, Mar 13, 2005 at 06:44:52PM +0200, Dimitris Kounalakis
wrote:
>/ Thank you for your response Marco.
/>/ 
/>/ I do. The problem is that all incomings calls from ISDN are handled by
the
/>/ default "s" extension in the context [default] and not by an
"s" extension
/>/ in the context [isdn] or by the msm numbers as extensions in the context 
/>/ [isdn].
/
Looking at the line here:
>/ />/  == Starting CAPI[contr1/2810111694]/3 at ,2810111694,1 failed so 
/>/ />/ falling back to exten 's'
/
It looks like the context is blank. What does the show command in
asterisk show the context as being (paste output please).
-- 
Martijn van Oosterhout
Ecomtel Pty Ltd

On Sun, 13 Mar 2005 21:49:52 +0200, Dimitris Kounalakis
<dcoun@medsite.info> wrote:
> Hello *Martijn,
> Thank you for your response.
> *That was my opinion too, it looses the context due to a bug, and can
anyone confirm it also?
> But I have no output from the command "Show channels", and it
happens so quickly that it is impossible to issue the command before falling to
the default context.
> In the logs, I can see that the channel exists like
CAPI[contr1/2810211694]/0  but this is druring call only.
> Any other way to debug it more (or to solve it)?
> 
> My /etc/asterisk/capi.conf is:
> -----------------------------------------
> [general]
> nationalprefix=0
> internationalprefix=00
> rxgain=0.8
> txgain=0.8
> 
> [interfaces]
> controller=1
> msn=2810111694
> incomingmsn=*
> devices=2
> softdtmf=1
> callgroup=1
> context=isdn
On my system I have the devices=2 as the last line this works for me

[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]

msn=330417
incomingmsn=*
controller=1
softdtmf=1
accountcodecontext=from-pstn
echocancel=yes
echotail=64
devices=2