<div>I'm not expert on this matter,but base on experience that is a normal situation on SIP/IAX channels since the call made is answered by the other end regardless of the situation you might found.</div>
<div>I'm on PRI ISDN and for me dialstatus and hangupcause works pretty good.</div>
<div>Regards</div>
<div>Jb<br><br> </div>
<div><span class="gmail_quote">On 9/15/05, <b class="gmail_sendername">Mark Edwards</b> <<a href="mailto:mark.p.edwards@gmail.com">mark.p.edwards@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">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 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 (NOANSWER,BUSY,CHANUNAVAIL
<div>,CONGESTION,ANSWER)<br>exten => s-CHANUNAVAIL,1,NoOp("CHANUNAVAIL")<br>exten => s-CHANUNAVAIL,2,UserEvent(ChannelUnavailable|Account: ${ACCOUNTCODE}^${CALLERIDNUM})<br>exten => s-CONGESTION,1,NoOp("CONGESTION")
<br>exten => s-CONGESTION,2,UserEvent(Congestion|Account: ${ACCOUNTCODE}^${CALLERIDNUM})<br>exten => s-ANSWER,1,NoOp("ANSWER")<br>exten => s-ANSWER,2,UserEvent(Answer|Account: ${ACCOUNTCODE}^${CALLERIDNUM})
<br>exten => s-BUSY,1,NoOp("BUSY")<br>exten => s-BUSY,2,UserEvent(Busy|Account: ${ACCOUNTCODE}^${CALLERIDNUM})<br>exten => s-NOANSWER,1,NoOp("NOANSWER")<br>exten => s-NOANSWER,2,UserEvent(NoAnswer|Account: ${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 channel Local/4000/n where 4000 is an extension which accesses the meetme 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 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 meaningful?<br><br>Also, does ${DIALSTATUS} or ${HANGUPCAUSE} work better on PRI?<br><br>Cheers,<br><span><br>Mark.</span></div><span class="sg">
<br clear="all"><br>-- <br>regards,<br><br>Mark P. Edwards<br>FWD: 667917<br></span><br>_______________________________________________<br>--Bandwidth and Colocation sponsored by <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://easynews.com/" target="_blank">
Easynews.com</a> --<br><br>Asterisk-Users mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Asterisk-Users@lists.digium.com">Asterisk-Users@lists.digium.com</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>To UNSUBSCRIBE or update options visit:<br> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br><br></blockquote></div><br>