[asterisk-bugs] [LibPRI 0017428]: [patch] Regression in libpri 1.4.11 - handling ROSE

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17428 
====================================================================== 
Reported By:                patrol-cz
Assigned To:                rmudgett
====================================================================== 
Project:                    LibPRI
Issue ID:                   17428
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.2.7 
JIRA:                       SWP-1610 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-05-31 14:30 CDT
Last Modified:              2010-06-01 11:30 CDT
====================================================================== 
Summary:                    [patch] Regression in libpri 1.4.11 - handling ROSE
Description: 
I've upgraded libpri to 1.4.11 and I've found that I can't see the QSIG
calling name for incoming calls now. The problem is, that there is
an unknown/unhandled operation (85) before the Calling Name operation
(supplied by the interworking PBX), and libpri now fails to continue
interpreting the facility contents since it encounters the unknown
operation. In older libPRI (libpri-1.4.10.1) the problem is not present,
the parser just skips the unknown operation and continues, thus properly
parsing the Calling Name operation.

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-01 11:30 svnbot         Status                   assigned => resolved
2010-06-01 11:30 svnbot         Resolution               open => fixed       
======================================================================