Hi. I'm dialling two numbers - one that's unobtainable, one that's busy. ${DIALSTATUS} is coming back ANSWER each time right before the channels hang up. Am using the following dialplan macro to dial out. [macro-advdial] exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status (NOANSWER,BUSY,CHANUNAVAIL ,CONGESTION,ANSWER) exten => s-CHANUNAVAIL,1,NoOp("CHANUNAVAIL") exten => s-CHANUNAVAIL,2,UserEvent(ChannelUnavailable|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) exten => s-CONGESTION,1,NoOp("CONGESTION") exten => s-CONGESTION,2,UserEvent(Congestion|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) exten => s-ANSWER,1,NoOp("ANSWER") exten => s-ANSWER,2,UserEvent(Answer|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) exten => s-BUSY,1,NoOp("BUSY") exten => s-BUSY,2,UserEvent(Busy|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) exten => s-NOANSWER,1,NoOp("NOANSWER") exten => s-NOANSWER,2,UserEvent(NoAnswer|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) exten => _s-.,1,Goto(s-NOANSWER,1) ; Treat anything else as no answer 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. ITSP is terminating outbound calls to me via IAX2. I need to be able to see the CAUSE CODE status of the call if it is answered, CONGESTED or BUSY. my ITSP is in Australia - as am I. the IAX2 debug clearly indicates a zero CAUSE CODE on most call cases. Any idea what I might be able to do to make the CAUSE CODE a little more meaningful? Also, does ${DIALSTATUS} or ${HANGUPCAUSE} work better on PRI? Cheers, Mark. -- regards, Mark P. Edwards FWD: 667917 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050915/b2bde4a0/attachment.htm
In article <9e7e0d8a05091502286deb19cc@mail.gmail.com>, Mark Edwards <mark.p.edwards@gmail.com> wrote:> > I'm dialling two numbers - one that's unobtainable, one that's busy. > > ${DIALSTATUS} is coming back ANSWER each time right before the channels hang > up. > > [...] > > ITSP is terminating outbound calls to me via IAX2.Aha, that's interesting! I recently noticed exactly the same with my IAX provider in the UK. If I try to call a PSTN number that is busy, I do not get BUSY status passed back via IAX; instead, the call is answered, and then in-band congestion tones are played. This is pretty useless of course, for CTI reporting of call failures. I raised a ticket with them, and they say they can reproduce the fault but haven't yet managed to fix it. I wonder if it is a bug in more recent versions of Asterisk? Cheers Tony -- Tony Mountifield Work: tony@softins.co.uk - http://www.softins.co.uk Play: tony@mountifield.org - http://tony.mountifield.org
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. I'm on PRI ISDN and for me dialstatus and hangupcause works pretty good. Regards Jb On 9/15/05, Mark Edwards <mark.p.edwards@gmail.com> wrote:> > Hi. > > I'm dialling two numbers - one that's unobtainable, one that's busy. > > ${DIALSTATUS} is coming back ANSWER each time right before the channels > hang up. > > Am using the following dialplan macro to dial out. > > [macro-advdial] > exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum > exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status > (NOANSWER,BUSY,CHANUNAVAIL ,CONGESTION,ANSWER) > exten => s-CHANUNAVAIL,1,NoOp("CHANUNAVAIL") > exten => s-CHANUNAVAIL,2,UserEvent(ChannelUnavailable|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-CONGESTION,1,NoOp("CONGESTION") > exten => s-CONGESTION,2,UserEvent(Congestion|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-ANSWER,1,NoOp("ANSWER") > exten => s-ANSWER,2,UserEvent(Answer|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-BUSY,1,NoOp("BUSY") > exten => s-BUSY,2,UserEvent(Busy|Account: ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-NOANSWER,1,NoOp("NOANSWER") > exten => s-NOANSWER,2,UserEvent(NoAnswer|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => _s-.,1,Goto(s-NOANSWER,1) ; Treat anything else as no answer > > 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. > > ITSP is terminating outbound calls to me via IAX2. > > I need to be able to see the CAUSE CODE status of the call if it is > answered, CONGESTED or BUSY. > > my ITSP is in Australia - as am I. > > the IAX2 debug clearly indicates a zero CAUSE CODE on most call cases. > > Any idea what I might be able to do to make the CAUSE CODE a little more > meaningful? > > Also, does ${DIALSTATUS} or ${HANGUPCAUSE} work better on PRI? > > Cheers, > > Mark. > > > -- > regards, > > Mark P. Edwards > FWD: 667917 > > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com<http://easynews.com/>-- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050920/79cbc6ed/attachment.htm
I met same problem when dial via zap channel. Does anyone know how to solve it? thanks. 2005/9/15, Mark Edwards <mark.p.edwards@gmail.com>:> Hi. > > I'm dialling two numbers - one that's unobtainable, one that's busy. > > ${DIALSTATUS} is coming back ANSWER each time right before the channels hang > up. > > Am using the following dialplan macro to dial out. > > [macro-advdial] > exten => s,1,Dial(${ARG1},20,g) ; Ring the interface, 20 seconds maximum > exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status > (NOANSWER,BUSY,CHANUNAVAIL > ,CONGESTION,ANSWER) > exten => s-CHANUNAVAIL,1,NoOp("CHANUNAVAIL") > exten => > s-CHANUNAVAIL,2,UserEvent(ChannelUnavailable|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-CONGESTION,1,NoOp("CONGESTION") > exten => s-CONGESTION,2,UserEvent(Congestion|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-ANSWER,1,NoOp("ANSWER") > exten => s-ANSWER,2,UserEvent(Answer|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-BUSY,1,NoOp("BUSY") > exten => s-BUSY,2,UserEvent(Busy|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => s-NOANSWER,1,NoOp("NOANSWER") > exten => s-NOANSWER,2,UserEvent(NoAnswer|Account: > ${ACCOUNTCODE}^${CALLERIDNUM}) > exten => _s-.,1,Goto(s-NOANSWER,1) ; Treat anything else as no answer > > 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. > > ITSP is terminating outbound calls to me via IAX2. > > I need to be able to see the CAUSE CODE status of the call if it is > answered, CONGESTED or BUSY. > > my ITSP is in Australia - as am I. > > the IAX2 debug clearly indicates a zero CAUSE CODE on most call cases. > > Any idea what I might be able to do to make the CAUSE CODE a little more > meaningful? > > Also, does ${DIALSTATUS} or ${HANGUPCAUSE} work better on PRI? > > Cheers, > > Mark. > > -- > regards, > > Mark P. Edwards > FWD: 667917 > > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > >