# \[RESOLVED\] Can not make outgoing capi isdn calls

**URL:** <https://community.asterisk.org/t/resolved-can-not-make-outgoing-capi-isdn-calls/1605>\
**Category:** Asterisk Support\
**Created:** [September 27, 2005, 1:58pm UTC](https://community.asterisk.org/t/resolved-can-not-make-outgoing-capi-isdn-calls/1605 "2005-09-27T13:58:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DonaldCook](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@DonaldCook](https://community.asterisk.org/u/DonaldCook)\
**Post date:** [September 27, 2005, 1:58pm UTC](https://community.asterisk.org/t/resolved-can-not-make-outgoing-capi-isdn-calls/1605/1 "2005-09-27T13:58:16Z")

</div>

Would someone please help an asterisk newbe (started configuring asterisk 5 days ago).

I am having problems with out going isdn calls with a capi driver. In coming calls work fine. Any assistance would be appreciated.

Here are my relevant config files and capi debug for both outgoing and incoming calls:

capi.conf

[ISDN1]  
isdnmode=msn  
controller=1  
group=1  
msn=925653  
context=capi-in

extensions.conf

[default]  
; outbound  
exten =\> \_9.,1,Dial(CAPI/925653:B${EXTEN},180)  
exten =\> \_9.,2,Playback(invalid)  
exten =\> \_9.,102,Busy

[capi-in]  
; inbound:  
exten =\> 925654,1,Goto(default,s,1)

outgoing call capi debug:

\*CLI\>  
== CDR updated on CAPI/ISDN1/925654-0  
– Executing Dial(“CAPI/ISDN1/925654-0”, “CAPI/925653:B9xxxxx5750|180”) in new stack  
\> data = 925653:B9xxxxx5750  
\> parsed dialstring: ‘925653:B9xxxxx5750’ ‘’ ‘’  
\> capi request for interface ‘925653:B9xxxxx5750’  
– didn’t find capi device for interface '925653:B9xxxxx5750’  
Sep 27 15:44:11 NOTICE[9792]: app\_dial.c:1109 dial\_exec\_full: Unable to create channel of type ‘CAPI’ (cause 44 - Requested channel not available)  
== Everyone is busy/congested at this time (1:0/0/1)

Incoming call capi debug:

\*CLI\> – CONNECT\_IND (PLCI=0x101,DID=925654,CID=xxxx57589451,CIP=0x1,CONTROLLER=0x1)  
== ISDN1: Incoming call ‘xxxxx57589451’ -\> ‘925654’  
– ISDN1: info element PI 80 83  
– ISDN1: info element CALLED PARTY NUMBER  
– ISDN1: info element CHANNEL IDENTIFICATION 89  
– ISDN1: info element Sending Complete  
– ISDN1: CAPI/ISDN1/925654-0: 925654 matches in context capi-in  
== Started pbx on channel CAPI/ISDN1/925654-0  
– Executing Goto(“CAPI/ISDN1/925654-0”, “default|s|1”) in new stack  
– Goto (default,s,1)  
– Executing Wait(“CAPI/ISDN1/925654-0”, “1”) in new stack  
– Executing Answer(“CAPI/ISDN1/925654-0”, “”) in new stack  
== ISDN1: Answering for 925654  
❓

---

<div class="post-metadata">

**Author:** ![DonaldCook](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@DonaldCook](https://community.asterisk.org/u/DonaldCook)\
**Post date:** [September 30, 2005, 11:04am UTC](https://community.asterisk.org/t/resolved-can-not-make-outgoing-capi-isdn-calls/1605/2 "2005-09-30T11:04:18Z")

</div>

After going over (and over and over) the documentation I found the problem.

It appears that all the documentation on the web on how to set up chan\_isdn is based on version 0.3.6 of the chan\_capi driver. Somewhere between that version and version 0.6, the version that I compiled, the dial string has changed. I found this in the chan\_capi README file.

Here is an excerpt from the README file:

# The Dial string

Example: Dial(CAPI/g/[/])  
Or: Dial(CAPI/contr/[/])  
Or: Dial(CAPI//[/])

‘group’ can be a value, comma separated list of values or a range  
using ‘-’. The according interface is found by searching a match with  
the ‘group’ specified in the capi.conf for each interface.

‘params’ is an optional part to set special settings for this call.  
The string consists of a list of characters with the following meaning:  
‘b’ : early B3 always.  
‘B’ : early B3 on successful calls only.  
‘o’ : use overlap sending of number if number is longer than 2 digits  
(This is useful, when further digits shall be send to complete the  
destination address).

If the is used in dialstring, be sure the name (specified  
in capi.conf) does not start with ‘contr’ or ‘g’.