Christopher Mylonas
2005-Sep-19 17:34 UTC
[Asterisk-Users] Call dropped 100% of time when incoming IAX routed to outgoing CAPI
Good day,
The unusual thing about this problem is that it doesn't occur just during a
CAPI call, or just during an IAX/SIP call. Only during IAX/CAPI
I'm having some trouble with the CAPI interface and it only occurs when a
call
comes in on an IAX channel and goes out the CAPI interface.
The capi debug in the asterisk console is below as well as the relevent parts
of .conf files from the machines involved.
The scenario is this (extension numbers):
4074 is connected to a Siemens Hipath 3000 PBX.
The Hipath3000 has a cable running to asterisk at address 192.168.1.222
connected to a wcte11xp zaptel card - Single span PRI.
The asterisk at 222 just mentioned (*@222) is on the LAN and it accepts calls
from the Hipath3000 in a certain range and sends the calls to locally
connected SIP extensions. When ext 4074 calls 4050 we've set up a test
scenario where the Hipath3000 sends all calls for 4050 to *@222, which then
has an IAX connection to another asterisk machine set up at 192.168.1.224
(*@224). This call is then sent out the CAPI interface on the second
machine to the Hipath3000 and pointed to extension 4028. This connection
drops out 100% of the time at different times though - none longer than
one minute. On this particular debug within asterisk the call got dropped
during the ringing stage.
4074 dials (4050) hp3k pbx -> in thru zap *@222 -> iax to *@224 -> capi
to
hp3k pbx -> 4028
The CAPI device is an AVM C2 card on the 224 machine
chan_capi version is 0.5.4 on 192.168.1.224
asterisk version on 192.168.1.222 is CVS-HEAD and the chan_iax2.c files says
revision 1.332
asterisk version on 192.168.1.224 is Asterisk 1.0.9
***CONF FILES****
192.168.1.222's extension.conf
******************************
; DO NOT REMOVE
; FOR USE BY OLCS SYDNEY TO DIAL OUT VIA IAX2
;*************************
[iax-out]
exten => 4050,1,Dial(IAX2/iax-olcs-brisbane/4050)
192.168.1.224's extensions.conf
*******************************
[iax-net-in]
exten = 4050,1,Dial(CAPI/g1/4028)
192.168.1.224's capi.conf
*************************
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
[interfaces]
group=1
msn=4150
incomingmsn=*
controller=1
softdtmf=1
accountcodecontext=trunkincoming
devices=2
Just to re-iterate, the CAPI interface is fine when it is used as a normal
operation from the extension.conf file,
i.e. exten => 5555,1,Dial(CAPI/g1/${EXTEN}
The problem only occurs when it is an IAX call coming in and being routed out
the CAPI interface.
CAPI Debugging Enabled
-- Accepting AUTHENTICATED call from 192.168.1.222, requested format = 2,
actual format = 2
-- Executing Dial("IAX2/iax-olcs-brisbane at iax-olcs-brisbane/2",
"CAPI/g1/4028") in new stack
-- data = g1/4028
-- capi request group = 2
-- creating pipe for PLCI=0
== CAPI Call CAPI/contr1/4028-5 (pres=0x00)
CONNECT_REQ ID=002 #0x3f55 LEN=0051
Controller/PLCI/NCCI = 0x1
CIPValue = 0x10
CalledPartyNumber = <80>4028
CallingPartyNumber = <00 80>4074
CalledPartySubaddress = default
CallingPartySubaddress = default
BProtocol
B1protocol = 0x1
B2protocol = 0x1
B3protocol = 0x0
B1configuration = default
B2configuration = default
B3configuration = default
GlobalConfiguration = default
BC = default
LLC = default
HLC = default
AdditionalInfo
BChannelinformation = <00 00>
Keypadfacility = default
Useruserdata = default
Facilitydataarray = default
SendingComplete = default
-- Called g1/4028
CONNECT_CONF ID=002 #0x3f55 LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
== received CONNECT_CONF PLCI = 0x101 INFO = 0
INFO_IND ID=002 #0x5755 LEN=0015
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x800d
InfoElement = default
INFO_RESP ID=002 #0x5755 LEN=0012
Controller/PLCI/NCCI = 0x101
== info element SETUP ACK
INFO_IND ID=002 #0x5756 LEN=0017
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x1e
InfoElement = <81 88>
INFO_RESP ID=002 #0x5756 LEN=0012
Controller/PLCI/NCCI = 0x101
== info element PI 81 88
In-band information available
INFO_IND ID=002 #0x5757 LEN=0016
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x18
InfoElement = <8a>
INFO_RESP ID=002 #0x5757 LEN=0012
Controller/PLCI/NCCI = 0x101
== info element CHANNEL IDENTIFIKATION 8a
INFO_IND ID=002 #0x5758 LEN=0015
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x8002
InfoElement = default
INFO_RESP ID=002 #0x5758 LEN=0012
Controller/PLCI/NCCI = 0x101
== info element CALL PROCEEDING
INFO_IND ID=002 #0x5759 LEN=0015
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x8001
InfoElement = default
INFO_RESP ID=002 #0x5759 LEN=0012
Controller/PLCI/NCCI = 0x101
== info element ALERTING
-- CAPI/contr1/4028-5 is ringing
-- CAPI Hangingup
> activehangingup
DISCONNECT_REQ ID=002 #0x3f56 LEN=0018
Controller/PLCI/NCCI = 0x101
AdditionalInfo
BChannelinformation = default
Keypadfacility = default
Useruserdata = default
Facilitydataarray = default
SendingComplete = default
== Spawn extension (iax-net-in, 4050, 1) exited non-zero on
'IAX2/iax-olcs-brisbane at iax-olcs-brisbane/2'
DISCONNECT_CONF ID=002 #0x3f56 LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
-- Hungup 'IAX2/iax-olcs-brisbane at iax-olcs-brisbane/2'
INFO_IND ID=002 #0x575a LEN=0017
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x8
InfoElement = <80 90>
INFO_RESP ID=002 #0x575a LEN=0012
Controller/PLCI/NCCI = 0x101
== info element CAUSE 80 90
INFO_IND ID=002 #0x575b LEN=0037
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x1c
InfoElement = <91 a1 13 02 02 89 d2 02 01 22>0<0a
a1
05>0<03 02 01 00 82 01 01>
INFO_RESP ID=002 #0x575b LEN=0012
Controller/PLCI/NCCI = 0x101
== info element FACILITY
DISCONNECT_IND ID=002 #0x575c LEN=0014
Controller/PLCI/NCCI = 0x101
Reason = 0x3490
DISCONNECT_RESP ID=002 #0x575c LEN=0012
Controller/PLCI/NCCI = 0x101
-- removed pipe for PLCI = 0x101
If you would like some additional info, email me direct
(christopher.mylonas at olcs.com.au) and I'll send whatever you need to the
mailing list and/or to your own email.
Kind Regards,
Christopher Mylonas
Maybe Matching Threads
Wisdom of the Ancients
