[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-05 05:56 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)
====================================================================== 

---------------------------------------------------------------------- 
 (0101255) klaus3000 (reporter) - 2009-03-05 05:56
 http://bugs.digium.com/view.php?id=14592#c101255 
---------------------------------------------------------------------- 
So a read only function TRANSFER(option), where option is:
  peer: returns the peer/user name of the transferer
  referedby: information from the SIP Refered-By header

Obviously this function can be useful to other channels too. I wonder how
transfers are signaled to the core. I couldn't find something like
AST_CONTROL_TRANSFER 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-05 05:56 klaus3000      Note Added: 0101255                          
======================================================================