[asterisk-bugs] [JIRA] (ASTERISK-13684) [patch] export the SIP peer username of the transferer

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-13684:
-------------------------------------

    Assignee: Olle Johansson  (was: klaus3000)
      Status: In Progress  (was: Waiting for Feedback)

> [patch] export the SIP peer username of the transferer
> ------------------------------------------------------
>
>                 Key: ASTERISK-13684
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-13684
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Channels/chan_sip/NewFeature
>            Reporter: klaus3000
>            Assignee: Olle Johansson
>              Labels: patch
>         Attachments: app_dial--FORWARDER.diff, asterisk-patch-sip-transfer-peername-trunk.txt, patch_chan_sip_transfer_forward_peername-1.4.23.txt, patch_chan_sip_transfer_forward_peername-1.6.2.txt
>
>
> 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)
> ****** ADDITIONAL INFORMATION ******
> As I am not up2date with the current peer/user behavior maybe the SIPTRANSFERER_USERNAME can be removed. I greped the code and it seems that p->peername is also set in case of a SIP user, but not vice versa.



--
This message was sent by Atlassian JIRA
(v6.2#6252)