[asterisk-bugs] [JIRA] (ASTERISK-21456) New SIP Channel Driver - add basic REFER support and SIP blind transfers

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Apr 16 14:08:01 CDT 2013


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

Matt Jordan updated ASTERISK-21456:
-----------------------------------

    Description: 
Oh boy. Here we go.

REFERs, Replaces, and all the joy they bring.

We need to be able to:
* Receive and authenticate a REFER request.
* Use the bridging API's blind transfer function and blind transfer the channel to either an extension or into a new bridge (or parking lot, etc.)
* Convey progress of the transfer using SIP NOTIFY requests

As well, we need to handle a transfer indication. This should determine if the endpoint is ringing, and if not, transmit a REFER request to the target endpoint. (If ringing, we need to redirect it). This also means processing NOTIFY requests and determining the success/failure of the transfer based on the NOTIFY requests.

  was:
Oh boy. Here we go.

REFERs, Replaces, and all the joy they bring.

We need to be able to:
* Receive and authenticate a REFER request.
* Use the bridging API's blind transfer function and blind transfer the channel to either an extension or into a new bridge (or parking lot, etc.)
* Convey success/failure using SIP NOTIFY requests

As well, we need to handle a transfer indication. This should determine if the endpoint is ringing, and if not, transmit a REFER request to the target endpoint. (If ringing, we need to redirect it). This also means processing NOTIFY requests and determining the success/failure of the transfer based on the NOTIFY requests.

    
> New SIP Channel Driver - add basic REFER support and SIP blind transfers
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-21456
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21456
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_gulp
>            Reporter: Matt Jordan
>              Labels: Asterisk12, NewSIP
>
> Oh boy. Here we go.
> REFERs, Replaces, and all the joy they bring.
> We need to be able to:
> * Receive and authenticate a REFER request.
> * Use the bridging API's blind transfer function and blind transfer the channel to either an extension or into a new bridge (or parking lot, etc.)
> * Convey progress of the transfer using SIP NOTIFY requests
> As well, we need to handle a transfer indication. This should determine if the endpoint is ringing, and if not, transmit a REFER request to the target endpoint. (If ringing, we need to redirect it). This also means processing NOTIFY requests and determining the success/failure of the transfer based on the NOTIFY requests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list