|Summary:||ASTERISK-13747: Hangup causecode is improper in case ring/dial timeout specified.|
|Reporter:||sambeet Jena (sambeet_jena)||Labels:|
|Date Opened:||2009-03-14 03:22:29||Date Closed:||2011-06-07 14:07:55|
|Description:||I am using hangup causecode to detect SIT(special information tone) for outbound dialing using dial application. When we specify the ring/dial timeout then the hangup causecode varies. When dial timeout is not specified we get accurate dialstatus and hangup causecode. But for the same number when dial/ring timeout is specified the hangup causecode is different and so is the dialstatus. One can understand dialstatus being different but the hangup causecode =0 (stands for not recognised hangup causecode). |
Also if possible, is there any other method to detect SIT accurately?
Thanks & Regards.
|Comments:||By: David Woolley (davidw) 2009-07-02 08:18:26|
The zero is probably issue ASTERISK-1452686. I wonder if the instability is issue ASTERISK-1464802?
By: David Brooks (dbrooks) 2009-09-17 11:48:28
sambeet_jena, thank you for the bug report. Would you mind clarifying a little bit? I'm having a little trouble understanding what it is you're trying to do. Could you provide some sample output with what you expect and what you're actually getting? Thank you!
By: Leif Madsen (lmadsen) 2010-01-25 09:30:35.000-0600
Closed due to lack of feedback from reporter.