[asterisk-bugs] [Asterisk 0018087]: [regression] Caller ID in SIP PAI Header is anonymous instead of Number

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Oct 5 15:16:55 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18087 
====================================================================== 
Reported By:                1stbs
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18087
Category:                   Core/Channels
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Target Version:             1.8.0
Asterisk Version:           1.8.0-rc2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-03 19:43 CDT
Last Modified:              2010-10-05 15:16 CDT
====================================================================== 
Summary:                    [regression] Caller ID in SIP PAI Header is
anonymous instead of Number
Description: 
The current enviroment is used:
Openser as Callserver and registrar
Asterisk 1.8 rc2 (current dahdi-lunix & dahdi tools svn head) as Gateway
to Avaya Integral over QSIG
If a call is etablished the information in PAI contains anonymous instead
of the dialed number and the phones which support this PAI header shows
that you are connected with anonymous.
it seems that the function int ast_party_id_presentation(const struct
ast_party_id *id) is wrong.  i have changed the selection of the winning 
presentation value from if (name_priority < number_priority) to if
(name_priority > number_priority). Now it behaves correct in that scenario.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-05 15:16 lmadsen        Target Version            => 1.8.0           
======================================================================




More information about the asterisk-bugs mailing list