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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/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-09-03 14:50 CDT
====================================================================== 
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)
====================================================================== 

---------------------------------------------------------------------- 
 (0110177) oej (manager) - 2009-09-03 14:50
 https://issues.asterisk.org/view.php?id=14592#c110177 
---------------------------------------------------------------------- 
We just discussed this on IRC. I wasn't aware of this bug report then.

I think we need to look into this, we need to identify who caused a call
forward or a transfer, if it's an identifiable peer. Maybe it's possible as
tilghman says, but then we need to document it clearly.

THink about a call to multiple devices dial(SIP/345&SIP/567) - one of them
can cause a forward, we need to identfy whom. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-03 14:50 oej            Note Added: 0110177                          
======================================================================