[asterisk-bugs] [Asterisk 0014592]: [patch] export the SIP peer username of the transferer

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14592 
====================================================================== 
Reported By:                klaus3000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14592
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-03 09:42 CST
Last Modified:              2009-03-03 17:14 CST
====================================================================== 
Summary:                    [patch] export the SIP peer username of the
transferer
Description: 
Hi!

When a blind transfer is initiated from a SIP, often the name of the
transferer is needed (e.g. billing, applying restrictions ...). Currently
there is a variable called SIPTRANSFER_REFERER which contains the value of
the Refered-By header - but this variable is not trustworthy, as the SIP
client can put anything into this variable.

Attached patch adds the variables SIPTRANSFERER_PEERNAME and
SIPTRANSFERER_USERNAME which contain the respective SIP username (peer or
user)
====================================================================== 

---------------------------------------------------------------------- 
 (0101155) tilghman (administrator) - 2009-03-03 17:14
 http://bugs.digium.com/view.php?id=14592#c101155 
---------------------------------------------------------------------- 
It may be, but we try to avoid setting arbitrary variables, other than what
is there for backwards compatibility.  We prefer if people implement
dialplan functions which provide a wide assortment of information, without
needlessly polluting the channel variable space.

Upon further examination, the peername is already available as
${SIPCHANINFO(peername)}.  If you wanted to add a similar value for
username, that would be an acceptable change. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-03 17:14 tilghman       Note Added: 0101155                          
======================================================================