[asterisk-bugs] [Asterisk 0016265]: Etisalat UAE Disconnect Tone

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16265 
====================================================================== 
Reported By:                otufemi
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16265
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.9 
JIRA:                       SWP-427 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-17 15:46 CST
Last Modified:              2009-12-01 11:11 CST
====================================================================== 
Summary:                    Etisalat UAE Disconnect Tone
Description: 
Hello.

We observed that Asterisk does not detect the Disconnect-Tone, and hence
it does not release a PSTN channel after an external calling party,
hangs-up. 

The PSTN operator is Etisalat and this occurs in certain parts of the
Dubai, UAE. 

The Disconnect-Tone pattern (frequency/duration in milliseconds) is show
below:

   400/400,0/350,400/225,0/525 
====================================================================== 

---------------------------------------------------------------------- 
 (0114459) lmadsen (administrator) - 2009-12-01 11:11
 https://issues.asterisk.org/view.php?id=16265#c114459 
---------------------------------------------------------------------- 
Just wanted to confirm we acknowledge the issue, but this code is quite old
and this is kind of expected behaviour. I'm leaving this open for now as it
is something that should eventually get resolved. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-01 11:11 lmadsen        Note Added: 0114459                          
======================================================================