Have come to a solution on this, and as I suspected, the issue appears
to be a bit of a version mismatch between terminating asterices. (Is
that the plural of asterisk?) Anyway, to cut a long story short, I
tested with another provider, found that they were running a later
version (nearer CVS-HEAD) and started to see some useful data in the
CAUSE CODE coming back in the IAX stream on hangup. Fortunately, this
is finding its way into the ${HANGUPCAUSE} variable, so I am now able
to implement this in the dialplan.<br>
<br>
cheers,<br>
<br>
Mark.<br><br><div><span class="gmail_quote">On 9/21/05, <b class="gmail_sendername">Liu Peter</b> <<a href="mailto:voipforum@gmail.com">voipforum@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I met same problem when dial via zap channel.<br>Does anyone know how to solve it?<br>thanks.<br><br><br>2005/9/15, Mark Edwards <<a href="mailto:mark.p.edwards@gmail.com">mark.p.edwards@gmail.com</a>>:<br>> Hi.<br>
><br>> I'm dialling two numbers - one that's unobtainable, one that's busy.<br>><br>> ${DIALSTATUS} is coming back ANSWER each time right before the channels hang<br>> up.<br>><br>> Am using the following dialplan macro to dial out.
<br>><br>> [macro-advdial]<br>> exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum<br>> exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status<br>> (NOANSWER,BUSY,CHANUNAVAIL
<br>> ,CONGESTION,ANSWER)<br>> exten => s-CHANUNAVAIL,1,NoOp("CHANUNAVAIL")<br>> exten =><br>> s-CHANUNAVAIL,2,UserEvent(ChannelUnavailable|Account:<br>> ${ACCOUNTCODE}^${CALLERIDNUM})<br>> exten => s-CONGESTION,1,NoOp("CONGESTION")
<br>> exten => s-CONGESTION,2,UserEvent(Congestion|Account:<br>> ${ACCOUNTCODE}^${CALLERIDNUM})<br>> exten => s-ANSWER,1,NoOp("ANSWER")<br>> exten => s-ANSWER,2,UserEvent(Answer|Account:<br>
> ${ACCOUNTCODE}^${CALLERIDNUM})<br>> exten => s-BUSY,1,NoOp("BUSY")<br>> exten => s-BUSY,2,UserEvent(Busy|Account:<br>> ${ACCOUNTCODE}^${CALLERIDNUM})<br>> exten => s-NOANSWER,1,NoOp("NOANSWER")
<br>> exten => s-NOANSWER,2,UserEvent(NoAnswer|Account:<br>> ${ACCOUNTCODE}^${CALLERIDNUM})<br>> exten => _s-.,1,Goto(s-NOANSWER,1) ; Treat anything else as no answer<br>><br>> Outbound calls are made using Manager originate interface from a meetme room
<br>> channel Local/4000/n where 4000 is an extension which accesses the meetme<br>> room.<br>><br>> ITSP is terminating outbound calls to me via IAX2.<br>><br>> I need to be able to see the CAUSE CODE status of the call if it is
<br>> answered, CONGESTED or BUSY.<br>><br>> my ITSP is in Australia - as am I.<br>><br>> the IAX2 debug clearly indicates a zero CAUSE CODE on most call cases.<br>><br>> Any idea what I might be able to do to make the CAUSE CODE a little more
<br>> meaningful?<br>><br>> Also, does ${DIALSTATUS} or ${HANGUPCAUSE} work better on PRI?<br>><br>> Cheers,<br>><br>> Mark.<br>><br>> --<br>> regards,<br>><br>> Mark P. Edwards<br>> FWD: 667917
<br>><br>> _______________________________________________<br>> --Bandwidth and Colocation sponsored by <a href="http://Easynews.com">Easynews.com</a> --<br>><br>> Asterisk-Users mailing list<br>> <a href="mailto:Asterisk-Users@lists.digium.com">
Asterisk-Users@lists.digium.com</a><br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>> To UNSUBSCRIBE or update options visit:<br>
><br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>><br>><br></blockquote></div><br><br clear="all"><br>-- <br>regards,<br><br>
Mark P. Edwards<br>FWD: 667917<br>