[asterisk-bugs] [Asterisk 0014592]: [patch] export the SIP peer username of the transferer
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 4 12:30:26 CST 2009
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-04 12:30 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)
======================================================================
----------------------------------------------------------------------
(0101204) tilghman (administrator) - 2009-03-04 12:30
http://bugs.digium.com/view.php?id=14592#c101204
----------------------------------------------------------------------
Still, I'd like to see a dialplan function access the values, instead of
polluting the variable namespace. If that means that you pass more values
through the referedby structure, then that may be the approach to take.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-04 12:30 tilghman Note Added: 0101204
======================================================================
More information about the asterisk-bugs
mailing list