[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
A NOTE has been added to this issue.
======================================================================
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: assigned
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:
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0124616) svnbot (reporter) - 2010-07-16 11:37
https://issues.asterisk.org/view.php?id=17619#c124616
----------------------------------------------------------------------
Repository: libpri
Revision: 1828
U branches/1.4/rose_qsig_name.c
U branches/1.4/rosetest.c
------------------------------------------------------------------------
r1828 | rmudgett | 2010-07-16 11:37:06 -0500 (Fri, 16 Jul 2010) | 18 lines
Calling name not successfully processed on inbound QSIG PRI calls from
Mitel PBX
The alternate form of the Q.SIG Name sequence that allows manufacturer
extensions for CallingName, CalledName, ConnectedName, and BusyName was
not consuming the next ASN.1 tag. The code that processed the ASN.1 Name
structure was then using a stale tag value. The stale tag value was then
rejected with the "Did not expect" message.
I have added a test case using the supplied PRI debug output to the
rosetest utility to verify that this alternate encoding is tested in the
future.
(closes issue https://issues.asterisk.org/view.php?id=17619)
Reported by: jims8650
Patches:
issue17619_v1.4.11.3.patch uploaded by rmudgett (license 664)
Tested by: rmudgett
------------------------------------------------------------------------
http://svn.digium.com/view/libpri?view=rev&revision=1828
Issue History
Date Modified Username Field Change
======================================================================
2010-07-16 11:37 svnbot Checkin
2010-07-16 11:37 svnbot Note Added: 0124616
======================================================================
More information about the asterisk-bugs
mailing list