[asterisk-bugs] [LibPRI 0017495]: [patch] [regression] Calling Number assignment logic change in libpri 1.4.11.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17495 
====================================================================== 
Reported By:                ibercom
Assigned To:                rmudgett
====================================================================== 
Project:                    LibPRI
Issue ID:                   17495
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.30 
JIRA:                       SWP-1683 
libpri Version:             I did not set the version. :( 
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-06-10 07:28 CDT
Last Modified:              2010-06-25 11:07 CDT
====================================================================== 
Summary:                    [patch] [regression] Calling Number assignment logic
change in libpri 1.4.11.
Description: 
I've upgraded libpri 1.4.10.2 to 1.4.11.2 and I've found that I see another
calling number for incoming calls now. The problem is that there is two
calling number in the setup message (supplied by the interworking PBX) and
libpri now supply the second number. In older libpri (1.4.10.2) it supplied
the first. The parser function is different.

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

---------------------------------------------------------------------- 
 (0123893) klaus3000 (reporter) - 2010-06-25 11:07
 https://issues.asterisk.org/view.php?id=17495#c123893 
---------------------------------------------------------------------- 
I second that. In case of 2 network provided numbers we could make a
chan_dahdi option which one should be put into (num) and (ANI) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-25 11:07 klaus3000      Note Added: 0123893                          
======================================================================