[asterisk-bugs] [Asterisk 0014665]: Hangup causecode is improper in case ring/dial timeout specified.
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 24 12:56:49 CDT 2009
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=14665
======================================================================
Reported By: sambeet_jena
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14665
Category: Applications/app_dial
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.22
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-03-14 03:22 CDT
Last Modified: 2009-06-24 12:56 CDT
======================================================================
Summary: Hangup causecode is improper in case ring/dial
timeout specified.
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.
Sambeet Jena
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-06-24 12:56 lmadsen Severity major => minor
2009-06-24 12:56 lmadsen Description Updated
======================================================================
More information about the asterisk-bugs
mailing list