[asterisk-bugs] [Asterisk 0009511]: Q931 inband information not interpreted as alerting signal

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9511 
====================================================================== 
Reported By:                wzedi
Assigned To:                PCadach
====================================================================== 
Project:                    Asterisk
Issue ID:                   9511
Category:                   Core/General
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             04-09-2007 17:36 CDT
Last Modified:              03-06-2008 13:03 CST
====================================================================== 
Summary:                    Q931 inband information not interpreted as alerting
signal
Description: 
We received reports from a customer that they were not hearing a ring tone
when making calls to certain extensions in their office even though the
extension was ringing.

Further investigation showed that this occurred when calls were made to
non-isdn extensions through one particular exchange. In this scenario
inband information is received from the network in the PROGRESS signal
which should be interpreted as an ALERTING signal.

The libpri implementation of Q931 does not accommodate this scenario.
====================================================================== 

---------------------------------------------------------------------- 
 kpfleming - 03-06-08 13:03  
---------------------------------------------------------------------- 
Closing issue at tester/reporter's request, as it appears that the issue
has been resolved by a patch for a different issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-06-08 13:03  kpfleming      Status                   feedback => resolved
03-06-08 13:03  kpfleming      Resolution               reopened => fixed   
03-06-08 13:03  kpfleming      Note Added: 0083550                          
======================================================================