thr3ads.net - asterisk users - [Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem [Jun 2006]

If this information is useful, please help other people find it:
Share via:

Esteban Guana-Jarrin

2006-Jun-04 21:41 UTC

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

I have a problem receving calls via the ISDN line, using the followin 
components

Asterisk 1.0.9 with asterisk@home
chan_capi-cm-0.6
AVM Fritz card
datalink protocol = point to multimode

I can make calls out with no problems so the issue is only incoming calls.

When I make the call from an external line to the ISDN line connected to 
asterisk, I get a busy signal after about 5 seconds. I have read previous 
posts from the list and I made sure I have the settings in my capi.conf and 
extensions.conf according to all the suggestions and as shown below,

Capi.conf:

[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

[ISDN1]          ;this example interface gets name 'ISDN1' and may be
any
                     ;name not starting with 'g' or 'contr'.

isdnmode=msn     ;'MSN' (point-to-multipoint) or 'DID' (direct
inward dial)
                          ;when using NT-mode, ptp should be set in any case
msn=0299546476
incomingmsn=*    ;allow incoming calls to this list of MSNs/DIDs, * == any
controller=1     ;capi controller number to use
group=2          ;dialout group
context=capi-in  ;context for incoming calls
immediate=yes   ;immediate start of pbx with extension 's' if no digits
were
                 ;received on incoming call (no destination number yet)
devices=2        ;number of concurrent calls on this controller
                 ;(2 makes sense for single BRI, 30 for PRI)

In Extensions.conf

[capi-in]
exten => s,1,Dial(Sip/123,20)
exten => s,2,Voicemail(123)
exten => s,3,Hangup

Also the Capi debug output with verbosity 15, is shown below. I can see that 
after the channel identification message and then the sending complete 
message, a DISCONNECT_IND comes straight after and it does not provide any 
reasons...

CAPI Debugging Enabled
CONNECT_IND ID=001 #0x03a6 LEN=0037
  Controller/PLCI/NCCI            = 0x101
  CIPValue                        = 0x10
  CalledPartyNumber               = <c1>99546476
  CallingPartyNumber              = default
  CalledPartySubaddress           = default
  CallingPartySubaddress          = default
  BC                              = <80 90 a3>
  LLC                             = default
  HLC                             = <91 81>
  AdditionalInfo                  = default

    -- CONNECT_IND 
(PLCI=0x101,DID=99546476,CID=(null),CIP=0x10,CONTROLLER=0x1)
       > ISDN1: msn='*' DNID='99546476' MSN
  == ISDN1: Incoming call '' -> '99546476'
INFO_IND ID=001 #0x03a7 LEN=0024
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x70
  InfoElement                     = <c1>99546476

INFO_RESP ID=001 #0x03a7 LEN=0012
  Controller/PLCI/NCCI            = 0x101

    -- ISDN1: info element CALLED PARTY NUMBER
       > ISDN1: INFO_IND DID digits not used in this state.
INFO_IND ID=001 #0x03a8 LEN=0016
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x18
  InfoElement                     = <89>

INFO_RESP ID=001 #0x03a8 LEN=0012
  Controller/PLCI/NCCI            = 0x101

    -- ISDN1: info element CHANNEL IDENTIFICATION 89
INFO_IND ID=001 #0x03a9 LEN=0016
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0xa1
  InfoElement                     = <a1>

INFO_RESP ID=001 #0x03a9 LEN=0012
  Controller/PLCI/NCCI            = 0x101

    -- ISDN1: info element Sending Complete
CONNECT_RESP ID=001 #0x03a9 LEN=0032
  Controller/PLCI/NCCI            = 0x101
  Reject                          = 0x1
  BProtocol
   B1protocol                     = 0x0
   B2protocol                     = 0x0
   B3protocol                     = 0x0
   B1configuration                = default
   B2configuration                = default
   B3configuration                = default
  ConnectedNumber                 = default
  ConnectedSubaddress             = default
  LLC                             = default
  AdditionalInfo
   BChannelinformation            = default
   Keypadfacility                 = default
   Useruserdata                   = default
   Facilitydataarray              = default

DISCONNECT_IND ID=001 #0x03aa LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Reason                          = 0x0

DISCONNECT_RESP ID=001 #0x03aa LEN=0012
  Controller/PLCI/NCCI            = 0x101

  == ISDN1: CAPI Hangingup
  == ISDN1: Interface cleanup PLCI=0x101

I will apreciate your assistance

Esteban

_________________________________________________________________
New year, new job – there's more than 100,00 jobs at SEEK 
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&_t=752315885&_r=Jan05_tagline&_m=EXT

Armin Schindler

2006-Jun-05 03:08 UTC

head link

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

The call is rejected by Asterisk, so it looks like your dialplan
has no rule for accepting calls to '99546476'.

Armin


On Mon, 5 Jun 2006, Esteban Guana-Jarrin wrote:
> I have a problem receving calls via the ISDN line, using the followin
> components
> 
> Asterisk 1.0.9 with asterisk@home
> chan_capi-cm-0.6
> AVM Fritz card
> datalink protocol = point to multimode
> 
> I can make calls out with no problems so the issue is only incoming calls.
> 
> When I make the call from an external line to the ISDN line connected to
> asterisk, I get a busy signal after about 5 seconds. I have read previous
> posts from the list and I made sure I have the settings in my capi.conf and
> extensions.conf according to all the suggestions and as shown below,
> 
> Capi.conf:
> 
> [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
> 
> [ISDN1]          ;this example interface gets name 'ISDN1' and may
be any
> ;name not starting with 'g' or 'contr'.
> 
> isdnmode=msn     ;'MSN' (point-to-multipoint) or 'DID'
(direct inward dial)
>                          ;when using NT-mode, ptp should be set in any case
> msn=0299546476
> incomingmsn=*    ;allow incoming calls to this list of MSNs/DIDs, * == any
> controller=1     ;capi controller number to use
> group=2          ;dialout group
> context=capi-in  ;context for incoming calls
> immediate=yes   ;immediate start of pbx with extension 's' if no
digits were
>                 ;received on incoming call (no destination number yet)
> devices=2        ;number of concurrent calls on this controller
> ;(2 makes sense for single BRI, 30 for PRI)
> 
> In Extensions.conf
> 
> [capi-in]
> exten => s,1,Dial(Sip/123,20)
> exten => s,2,Voicemail(123)
> exten => s,3,Hangup
> 
> Also the Capi debug output with verbosity 15, is shown below. I can see
that
> after the channel identification message and then the sending complete
> message, a DISCONNECT_IND comes straight after and it does not provide any
> reasons...
> 
> CAPI Debugging Enabled
> CONNECT_IND ID=001 #0x03a6 LEN=0037
> Controller/PLCI/NCCI            = 0x101
> CIPValue                        = 0x10
> CalledPartyNumber               = <c1>99546476
> CallingPartyNumber              = default
> CalledPartySubaddress           = default
> CallingPartySubaddress          = default
> BC                              = <80 90 a3>
> LLC                             = default
> HLC                             = <91 81>
> AdditionalInfo                  = default
> 
>    -- CONNECT_IND
(PLCI=0x101,DID=99546476,CID=(null),CIP=0x10,CONTROLLER=0x1)
> > ISDN1: msn='*' DNID='99546476' MSN
>  == ISDN1: Incoming call '' -> '99546476'
> INFO_IND ID=001 #0x03a7 LEN=0024
> Controller/PLCI/NCCI            = 0x101
> InfoNumber                      = 0x70
> InfoElement                     = <c1>99546476
> 
> INFO_RESP ID=001 #0x03a7 LEN=0012
> Controller/PLCI/NCCI            = 0x101
> 
>    -- ISDN1: info element CALLED PARTY NUMBER
> > ISDN1: INFO_IND DID digits not used in this state.
> INFO_IND ID=001 #0x03a8 LEN=0016
> Controller/PLCI/NCCI            = 0x101
> InfoNumber                      = 0x18
> InfoElement                     = <89>
> 
> INFO_RESP ID=001 #0x03a8 LEN=0012
> Controller/PLCI/NCCI            = 0x101
> 
>    -- ISDN1: info element CHANNEL IDENTIFICATION 89
> INFO_IND ID=001 #0x03a9 LEN=0016
> Controller/PLCI/NCCI            = 0x101
> InfoNumber                      = 0xa1
> InfoElement                     = <a1>
> 
> INFO_RESP ID=001 #0x03a9 LEN=0012
> Controller/PLCI/NCCI            = 0x101
> 
>    -- ISDN1: info element Sending Complete
> CONNECT_RESP ID=001 #0x03a9 LEN=0032
> Controller/PLCI/NCCI            = 0x101
> Reject                          = 0x1
> BProtocol
> B1protocol                     = 0x0
> B2protocol                     = 0x0
> B3protocol                     = 0x0
> B1configuration                = default
> B2configuration                = default
> B3configuration                = default
> ConnectedNumber                 = default
> ConnectedSubaddress             = default
> LLC                             = default
> AdditionalInfo
> BChannelinformation            = default
> Keypadfacility                 = default
> Useruserdata                   = default
> Facilitydataarray              = default
> 
> DISCONNECT_IND ID=001 #0x03aa LEN=0014
> Controller/PLCI/NCCI            = 0x101
> Reason                          = 0x0
> 
> DISCONNECT_RESP ID=001 #0x03aa LEN=0012
> Controller/PLCI/NCCI            = 0x101
> 
> == ISDN1: CAPI Hangingup
> == ISDN1: Interface cleanup PLCI=0x101
> 
> I will apreciate your assistance
> 
> Esteban
> 
> _________________________________________________________________
> New year, new job ? there's more than 100,00 jobs at SEEK
>
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&_t=752315885&_r=Jan05_tagline&_m=EXT
> 
> _______________________________________________
> --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
>

Esteban Guana-Jarrin

2006-Jun-05 05:24 UTC

head link

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

Thanks Armin
>>The call is rejected by Asterisk, so it looks like your dialplan
>>has no rule for accepting calls to '99546476'.
>>Armin

My dial plan as shown below is,

[capi-in]
exten => s,1,Dial(Sip/123,20)
exten => s,2,Voicemail(123)
exten => s,3,Hangup

I believe I should be able to receive calls with the above.

I have also tried the following, and i get the same problem and debug output 
is the same.

[capi-in]
exten => 99546476,1,Dial(Sip/123,20)
exten => 99546476,2,Voicemail(123)
exten => 99546476,3,Hangup

Any other ideas ???

Esteban

_________________________________________________________________
Send 1c txt to other Telstra Pre-Paid Plus mobiles. Join now 
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fadsfac%2Enet%2Flink%2Easp%3Fcc%3DTEL185%2E19163%2E0%26clk%3D1%26creativeID%3D29997&_t=754399967&_m=EXT

James Harper

2006-Jun-05 06:18 UTC

head link

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

> My dial plan as shown below is,
> 
> [capi-in]
> exten => s,1,Dial(Sip/123,20)
> exten => s,2,Voicemail(123)
> exten => s,3,Hangup
> 
> I believe I should be able to receive calls with the above.
With immediate = yes then you should.
> I have also tried the following, and i get the same problem and debug
> output is the same.
> 
> [capi-in]
> exten => 99546476,1,Dial(Sip/123,20)
> exten => 99546476,2,Voicemail(123)
> exten => 99546476,3,Hangup
> 
> Any other ideas ???
Turn on asterisk debugging too. Capi seems to be working okay, maybe
asterisk isn't picking up the call for some reason. Maybe: 

asterisk -r
set verbose 9
set debug 9
capi debug

then make an incoming call and copy the output into an email and send it
to the list (unless it is really really long, then you may have to look
for interesting bits).

You should see a message in there somewhere that tells you that either
the capi driver is rejecting the call because it doesn't want to answer
that msn (your earlier logs make that unlikelye), or that asterisk can't
find an extension for it.

James

Esteban Guana-Jarrin

2006-Jun-06 00:43 UTC

head link

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

James and Armin,
>>Turn on asterisk debugging too. Capi seems to be working okay, maybe
>>asterisk isn't picking up the call for some reason. Maybe:
>>asterisk -r
>>set verbose 9
>>set debug 9
>>capi debug
>>then make an incoming call and copy the output into an email and send it
>>to the list (unless it is really really long, then you may have to look
>>for interesting bits).
>>u should see a message in there somewhere that tells you that either
>>the capi driver is rejecting the call because it doesn't want to
answer
>>that msn (your earlier logs make that unlikelye), or that asterisk
can't
>>find an extension for it.
>>James
Thanks for your response I managed to get it working with the following as 
you suggested,

[capi-in]
exten => 99546476,1,Dial(Sip/123,20)
exten => 99546476,2,Voicemail(123)
exten => 99546476,3,Hangup

Following is the debug output when it started working,

-- ISDN1: info element CHANNEL IDENTIFICATION 89
INFO_IND ID=001 #0x09d5 LEN=0016
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0xa1
  InfoElement                     = <a1>

INFO_RESP ID=001 #0x09d5 LEN=0012
  Controller/PLCI/NCCI            = 0x101

    -- ISDN1: info element Sending Complete
    -- ISDN1: CAPI/ISDN1/99546476-16: 99546476 matches in context capi-in
    -- Executing Dial("CAPI/ISDN1/99546476-16",
"Sip/123|20") in new stack
  == Started pbx on channel CAPI/ISDN1/99546476-16
    -- Called 123
    -- SIP/123-0b4d is ringing
  == ISDN1: Requested RINGING-Indication for CAPI/ISDN1/99546476-16

I now have two other problems,

1. Noise is quite loud using this line with asterisk
2. Incoming DTMF tones are not detected via this ISDN line and AVM Fritz 
card

Any ideas on how to overcome these issues?

Esteban

_________________________________________________________________
Research and compare new cars side by side at carpoint.com.au 
http://secure-au.imrworldwide.com/cgi-bin/a/ci_450304/et_2/cg_801459/pi_1004813/ai_833884

Esteban Guana-Jarrin

2006-Jun-06 22:17 UTC

head link

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

Armin,
>2. Incoming DTMF tones are not detected via this ISDN line and AVM Fritz 
>card
>>Did you set for softdtmf/relaxdtmf?
>>Armin
I have tried with the following in capi.conf:

softdtmf=on      ;enable/disable software dtmf detection, recommended for 
AVM cards
relaxdtmf=on     ;in addition to softdtmf, you can use relaxed dtmf 
detection

This is the capi-in context in extensions.conf that i'm just using to test 
the digits detection

[capi-in]
exten => 99546476,1,Answer
exten => 99546476,2,DigitTimeout(10)
exten => 99546476,3,ResponseTimeout(5)
exten => 99546476,4,Read(Digits,enter-phone-number10,10)
exten => 99546476,5,NoOp(${Digits})
exten => t,1, Goto(99546476,4)
exten => t,2, Hangup

Below is the debug output and as you can see the variable Digits is empty 
(User entered ''). No digits were detected.

== ISDN1: Incoming call '' -> '99546476'
    -- Executing Answer("CAPI/ISDN1/99546476-18", "") in new
stack
  == ISDN1: Answering for 99546476
    -- Executing DigitTimeout("CAPI/ISDN1/99546476-18",
"10") in new stack
    -- Set Digit Timeout to 10
    -- Executing ResponseTimeout("CAPI/ISDN1/99546476-18",
"5") in new stack
    -- Set Response Timeout to 5
    -- Executing Read("CAPI/ISDN1/99546476-18", 
"Digits|enter-phone-number10|10") in new stack
    -- Accepting a maximum of 10 digits.
    -- Playing 'enter-phone-number10' (language 'en')
    -- User entered ''
    -- Executing NoOp("CAPI/ISDN1/99546476-18", "") in new
stack
    -- Timeout on CAPI/ISDN1/99546476-18
  == CDR updated on CAPI/ISDN1/99546476-18
    -- Executing Goto("CAPI/ISDN1/99546476-18",
"99546476|4") in new stack
    -- Goto (capi-in,99546476,4)
    -- Executing Read("CAPI/ISDN1/99546476-18", 
"Digits|enter-phone-number10|10") in new stack
    -- Accepting a maximum of 10
    -- Playing 'enter-phone-number10' (language 'en')
    -- User entered ''
    -- Executing NoOp("CAPI/ISDN1/99546476-18", "") in new
stack
    -- Timeout on CAPI/ISDN1/99546476-18

Any ideas?

Esteban

_________________________________________________________________
New year, new job – there's more than 100,00 jobs at SEEK 
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&_t=752315885&_r=Jan05_tagline&_m=EXT

Apparently Analagous Threads

Search for more maybe matching threads

asterisk users - Jun 2006 - chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

[Asterisk-Users] chan_capi-cm-0.6 and incoming calls problem

Apparently Analagous Threads