[asterisk-bugs] [Asterisk 0018303]: Caller Name does not preserve multiple spaces

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18303 
====================================================================== 
Reported By:                trev
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18303
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
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-11-14 00:43 CST
Last Modified:              2010-11-16 06:51 CST
====================================================================== 
Summary:                    Caller Name does not preserve multiple spaces
Description: 
When asterisk receives an INVITE with a Caller Name containing multiple
spaces, only one space is preserved.

Other SIP user agents / proxies / gateways as well as previous releases of
asterisk do preserve multiple spaces.

For example, "Victoria     BC" <2505551234> becomes "Victoria BC"
<2505551234> which is undesired.
====================================================================== 

---------------------------------------------------------------------- 
 (0128882) schmidts (manager) - 2010-11-16 06:51
 https://issues.asterisk.org/view.php?id=18303#c128882 
---------------------------------------------------------------------- 
i am not sure but i think this happens here:
http://www.asterisk.org/doxygen/trunk/callerid_8c-source.html#l01010
the question is if this is a RFC violation or not. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-16 06:51 schmidts       Note Added: 0128882                          
======================================================================