[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-19 10:59 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)
====================================================================== 

---------------------------------------------------------------------- 
 (0101973) klaus3000 (reporter) - 2009-03-19 10:59
 http://bugs.digium.com/view.php?id=14592#c101973 
---------------------------------------------------------------------- 
Hi! I attached a new patch. It is still not based on functions, but nice
and also handles the case of a SIP forward (302 moved).

I really wonder how people currently get the information "who" did the
transfer/forward into the CDR.

For the case of the forward I wonder what could be a nice way to implement
this. In this FORWARD_CONTEXT there should be an option to fin out who did
the forward (e.g. to apply restrictions (national, international) and
perform correct billing). Thus, the peer information (in case of SIP) or
maybe tech/peername would have to be copied from the original outgoing
channel to the new outgoing channel. This is different to the case of
transfer:
Forward: the FORWARD_CONTEXT is executed with a new Local channel
Transfer: The TRANSFER_CONTEXT is executed with the TRANSFEREE channel

I think struct ast_chan needs to be extended to handle both cases (e.g.
introducing a member "transforwarder" which contains for both cases the
forwarder/transferer in the format technology/username) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-19 10:59 klaus3000      Note Added: 0101973                          
======================================================================