[asterisk-bugs] [Asterisk 0014218]: [patch] Not possible to disguise display name on calls to trunks even though user can be disguised

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14218 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   14218
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Target Version:             1.6.2
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-12 10:14 CST
Last Modified:              2009-01-12 12:23 CST
====================================================================== 
Summary:                    [patch] Not possible to disguise display name on
calls to trunks even though user can be disguised
Description: 
When calling from an extension on the asterisk PBX to a trunk the sip
display-name that is received in the invite from the extension is used as
the display-name in the invite sent to the ITSP.

For example:
 From: "John Smith" <sip:101 at mypbx>
is converted to:
 From: "John Smith" <sip:voipaccount at myitsp>
but it would be useful if it could be converted instead to:
 From: "My Corporation" <sip:voipaccount at myitsp>
so that outgoing calls do not reveal the caller name
====================================================================== 

---------------------------------------------------------------------- 
 (0097510) otherwiseguy (administrator) - 2009-01-12 12:23
 http://bugs.digium.com/view.php?id=14218#c97510 
---------------------------------------------------------------------- 
> I think fromname is set from n if it does not exist
Yes, and it will be used to reset n to whatever p->fromname was the first
time that it was modified.  So, basically it sets it to the original cid
name, then uses that from then on.

initreqprep is called any time that transmit_invite is sent with init > 1,
which happens all over the code.  Removing the p->fromname looks to me like
it at least has the potential to cause changes to behavior.  Even under the
very best circumstances it would require tons of testing and and an ABI
change, for no real benefit. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-12 12:23 otherwiseguy   Note Added: 0097510                          
======================================================================