[asterisk-bugs] [LibPRI 0017619]: [patch] Calling name not successfully processed on inbound QSIG PRI calls from Mitel PBX

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jul 16 11:37:07 CDT 2010


The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17619 
====================================================================== 
Reported By:                jims8650
Assigned To:                rmudgett
====================================================================== 
Project:                    LibPRI
Issue ID:                   17619
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.2.9 
JIRA:                       SWP-185 
libpri Version:             1.4.11.3 
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-07-10 11:31 CDT
Last Modified:              2010-07-16 11:37 CDT
====================================================================== 
Summary:                    [patch] Calling name not successfully processed on
inbound QSIG PRI calls from Mitel PBX
Description: 
Calling name sent from Mitel PBX is not succesfully processed for inbound
calls over a QSIG PRI.  The calling name is arriving in a "Sequence/C (48
0x30)" element.  It is visible in the pri debug output ASN.1 dump.  There
is a "Did not expect: Sequence/C (48 0x30)" complaint in debug output, too.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-16 11:37 svnbot         Status                   assigned => resolved
2010-07-16 11:37 svnbot         Resolution               open => fixed       
======================================================================




More information about the asterisk-bugs mailing list