[asterisk-bugs] [Asterisk 0014987]: invalid value in Remote-Party-ID (RPID)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14987 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14987
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 190797 
Request Review:              
====================================================================== 
Date Submitted:             2009-04-28 13:18 CDT
Last Modified:              2009-06-24 08:18 CDT
====================================================================== 
Summary:                    invalid value in Remote-Party-ID (RPID)
Description: 
SIP/ringing message contains correct RPID info, but after call is answered,
SIP/OK message, contains RPID with incorrect value, look below, or at
attached packet dump.
If looking to wrong RPID value: "sw-146-324", I have suspicion, that can
be related do dialplan logic - I'm using Dial application from inside
switch() statement. This value "sw-146-324" is actually dialplan label,
that is constructed from AEL.



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

---------------------------------------------------------------------- 
 (0106903) pj (reporter) - 2009-06-24 08:18
 https://issues.asterisk.org/view.php?id=14987#c106903 
---------------------------------------------------------------------- 
I updated to Asterisk SVN-trunk-r200254 and it seems, that RPID is now OK
in my case (even without 'I' or any other dialplan modification). So it
seems, that some commit between initial revision 190797 and current 200254
resolved this issue. But please leave this bugreport open some days, until
I will have this proven with real phones. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-24 08:18 pj             Note Added: 0106903                          
======================================================================