[Asterisk-Users] Dialplan Q: Dialing with Capi

Patrik Schindler poc at pocnet.net
Wed Jun 22 03:28:58 MST 2005


Hello,

I'm using asterisk 1.0.7. with a somewhat advanced setup with IAX and CAPI 
as channels. A call comes in via IAX2 and should be redirected to CAPI.

So I wrote the following dialplan:

[fromiax]
exten => _8XXX,1,Answer
exten => _8XXX,2,Dial(CAPI/265:B${EXTEN:1},,r)

[fromcapi]
exten => 265,1,Answer
exten => 265,2,Dial(IAX2/PoC/11 at from-lw)
exten => 265-BUSY,1,Busy
exten => 265-NOANSWER,1,Busy

[default]
exten => s,1,Answer
exten => s,2,Congestion


The asterisk on the described side is connected to a classic company pbx 
(from Ericsson) and has local Extensions _XXX. The CAPI Interface gets 
signalled with MSN 260-265.

Yesterday I rewrote the dialplan to allow calls from any company phone 
(_XXX) to 265 will be rerouted to PoC/11 (the IAX peer). This works fine, 
the IAX peer will be called with MSN 265 as callerid, so the called party 
can see the number for callback.

I'm encountering the following problem with this setup, when the iax peer 
dials 8253, which should be redirected to CAPI/253 (8 is a extension 
prefix specific to the iax peer configuration).

-- Accepting AUTHENTICATED call from xx.xx.xx.xx, requested format = 4, 
actual format = 4
-- Executing Answer("IAX2/PoC at PoC/3", "") in new stack
-- Executing Dial("IAX2/PoC at PoC/3", "CAPI/265:B253||r") in new stack
Jun 22 11:47:22 NOTICE[13337]: chan_capi.c:1173 capi_request: didn't find 
capi device with outgoing msn = 265. you should check your config!
Jun 22 11:47:22 NOTICE[13337]: app_dial.c:746 dial_exec: Unable to create 
channel of type 'CAPI'
== Everyone is busy/congested at this time
-- Hungup 'IAX2/PoC at PoC/3'

When I change the dialplan to the outgoing MSN will be 260 than it works 
as expected: 253 will be called, but the called party gets 260 as callerid 
instead of the 265.

My capi.conf looks like this:

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

[interfaces]
msn=260
incomingmsn=*
outgoingmsn=260,261,263,264,265
controller=1
softdtmf=1
context=fromcapi
language=de
echocancel=yes
devices=2

Okay, I could also set msn=265; but in the future, more msns should be 
redirected to VoIP channels, so this is not a long term solution.

Any help is very welcome! Thanks for asterisk!

:wq! PoC



More information about the asterisk-users mailing list