[asterisk-bugs] [JIRA] (ASTERISK-27162) Access incoming SIP REFER headers in the dialplan

[Kirill Katsnelson (JIRA)]

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

Kirill Katsnelson updated ASTERISK-27162:
-----------------------------------------

    Description: 
This has been requested every so infrequently but steadily (e. g. https://community.asterisk.org/t/how-to-send-variable-information-via-sip-header/70178 for a fairly recent request). Now we are stuck without it too. An obvious hack-around that we once used is pack more data into 

Feature description I am putting into the Git comment that explains it:
----
This adds a way to access information passed along with SIP headers in a REFER message that initiates a transfer. Headers matching a dialplan variable GET_TRANSFERRER_DATA in the transferrer channel are added to a HASH object TRANSFER_DATA to be accessed with functions HASHKEY and HASH.

The variable GET_TRANSFERRER_DATA is interpreted to be a prefix for headers that should be put into the hash. If not set, no headers are included. If set to a string (perhaps 'X-' in a typical case), all headers starting this string are added. Empty string matches all headers.

If there are multiple of the same header, only the latest occurrence in the REFER message is available in the hash.

Obviously, the variable GET_TRANSFERRER_DATA must be inherited by the referrer channel, and should be set with the '__' or '___' prefix.

I avoided a specific reference to SIP or REFER, as in my mind the mechanism can be generalized to other channel techs.
----
I would appreciate comments on the feature and ways to possibly implement it better. I do not expect it to be used widely, but as is it is fairly cryptic. I posted a message asking for dev's thoughts on it (as a cross-reference): http://lists.digium.com/pipermail/asterisk-dev/2017-July/076419.html

I'll submit a patch on Gerrit later today.


  was:
This has been requested every so infrequently but steadily (e. g. https://community.asterisk.org/t/how-to-send-variable-information-via-sip-header/70178 for a fairly recent request). Now we are stuck without it too. An obvious hack-around that we once used is pack more data into 

Feature description I am putting into the Git comment that explains it:
----
This adds a way to access information passed along with SIP headers in a REFER message that initiates a transfer. Headers matching a dialplan variable GET_TRANSFERRER_DATA in the transferrer channel are added to a HASH object TRANSFER_DATA to be accessed with functions HASHKEY and HASH.

The variable GET_TRANSFERRER_DATA is interpreted to be a prefix for headers that should be put into the hash. If not set, no headers are included. If set to a string (perhaps 'X-' in a typical case), all headers starting this string are added. Empty string matches all headers.

If there are multiple of the same header, only the latest occurrence in the REFER message is available in the hash.

Obviously, the variable GET_TRANSFERRER_DATA must be inherited by the referrer channel, and should be set with the '_' or '__' prefix.

I avoided a specific reference to SIP or REFER, as in my mind the mechanism can be generalized to other channel techs.
----
I would appreciate comments on the feature and ways to possibly implement it better. I do not expect it to be used widely, but as is it is fairly cryptic. I posted a message asking for dev's thoughts on it (as a cross-reference): http://lists.digium.com/pipermail/asterisk-dev/2017-July/076419.html

I'll submit a patch on Gerrit later today.



> Access incoming SIP REFER headers in the dialplan
> -------------------------------------------------
>
>                 Key: ASTERISK-27162
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27162
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_sip/NewFeature, PBX/NewFeature
>    Affects Versions: GIT
>            Reporter: Kirill Katsnelson
>
> This has been requested every so infrequently but steadily (e. g. https://community.asterisk.org/t/how-to-send-variable-information-via-sip-header/70178 for a fairly recent request). Now we are stuck without it too. An obvious hack-around that we once used is pack more data into 
> Feature description I am putting into the Git comment that explains it:
> ----
> This adds a way to access information passed along with SIP headers in a REFER message that initiates a transfer. Headers matching a dialplan variable GET_TRANSFERRER_DATA in the transferrer channel are added to a HASH object TRANSFER_DATA to be accessed with functions HASHKEY and HASH.
> The variable GET_TRANSFERRER_DATA is interpreted to be a prefix for headers that should be put into the hash. If not set, no headers are included. If set to a string (perhaps 'X-' in a typical case), all headers starting this string are added. Empty string matches all headers.
> If there are multiple of the same header, only the latest occurrence in the REFER message is available in the hash.
> Obviously, the variable GET_TRANSFERRER_DATA must be inherited by the referrer channel, and should be set with the '__' or '___' prefix.
> I avoided a specific reference to SIP or REFER, as in my mind the mechanism can be generalized to other channel techs.
> ----
> I would appreciate comments on the feature and ways to possibly implement it better. I do not expect it to be used widely, but as is it is fairly cryptic. I posted a message asking for dev's thoughts on it (as a cross-reference): http://lists.digium.com/pipermail/asterisk-dev/2017-July/076419.html
> I'll submit a patch on Gerrit later today.



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