login | register
Tue 09 of Feb, 2010 [19:10 UTC]

voip-info.org

History

DIALSTATUS

Created by: fredo,Last modification on Wed 30 of Nov, 2005 [21:21 UTC] by rkarlsba
Status of the call, one of
CHANUNAVAIL | CONGESTION | BUSY | NOANSWER | ANSWER | CANCEL | HANGUP

See Also:


Comments

Comments Filter
222

333${DIALSTATUS} in perl AGI

by dhineshkumar, Saturday 31 of May, 2008 [14:42:18 UTC]

I unable to get the DIALSTATUS, when the caller hangup the call.
222

333

by arfeen, Friday 25 of May, 2007 [05:11:00 UTC]
Dariusz,I could not understand wat u said. the same thing working on my other servers.
222

333

by arfeen, Monday 23 of April, 2007 [06:12:38 UTC]
i'm not getting dialstatus in PERL AGI. whats the reason behind? sometimes i feel, a verbose command affect on dialstatus.
222

333

by tdi, Tuesday 12 of December, 2006 [15:46:50 UTC]
You can do it using local channel. Originitae call from local channel, and there issue Dial, so you could use the DIALSTATUS variable.
222

333Re: ${DIALSTATUS} and Manager API interaction

by asteriskexpert, Thursday 30 of November, 2006 [08:44:47 UTC]
${DIALSTATUS} variable is set when you execute Dial application. You will not get it if you originate call from manager API.
222

333${DIALSTATUS} and Manager API interaction

by , Thursday 04 of November, 2004 [05:07:03 UTC]
I am running a very recent CVS version of code, and it seems that I cannot evaluate DIALSTATUS
after an Originate request from Manager API. Is ${DIALSTATUS} supposed to be set upon
result of Originate on a Zap channel (effectively, this *acts* like a Dial cmd, but maybe semantics
or pragmatics are supposed to be different, I dunno, that's why I am puzzled....) ???

hvidal at tesseract-tech.com