[asterisk-bugs] [JIRA] (ASTERISK-29252) TRANSFERSTATUSPROTOCOL variable to report Transfer (REFER) failure SIP code

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253632#comment-253632 ] 

Friendly Automation commented on ASTERISK-29252:
------------------------------------------------

Change 15377 merged by Friendly Automation:
chan_pjsip, app_transfer: Add TRANSFERSTATUSPROTOCOL variable

[https://gerrit.asterisk.org/c/asterisk/+/15377|https://gerrit.asterisk.org/c/asterisk/+/15377]

> TRANSFERSTATUSPROTOCOL variable to report Transfer (REFER) failure SIP code
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-29252
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29252
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_transfer, Channels/chan_pjsip
>    Affects Versions: 16.15.0, 18.1.0
>            Reporter: Dan Cropp
>            Assignee: Dan Cropp
>            Severity: Minor
>
> There are many different cases where each system wants a unique behavior based on the reason the connected system rejects a Transfer/REFER.
> For example, a system may need a cascade of numbers to transfer to.  Transfer to the primary, if 486 (Busy Here), transfer to the secondary, if 486 (Busy Here), transfer to the tertiary, etc.
> Similarly, if a system rejects the REFER with a 404 Not Found, the system administrator may want to not allow transferring to this number.



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