[asterisk-bugs] [JIRA] (ASTERISK-21416) Implement SDES-SRTP support in chan_gulp

[Kinsey Moore (JIRA)]

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

Kinsey Moore commented on ASTERISK-21416:
-----------------------------------------

The work for this issue is occurring on the following branch:
http://svn.digium.com/svn/asterisk/team/kmoore/pimp_sip_srtp

The sdp/srtp parser functions have been pulled into main and cleaned up a little (removed unused items).  Next up will be factoring out the SRTP/RTP engine setup from chan_sip so it can be used from res_sip as well.
                
> Implement SDES-SRTP support in chan_gulp
> ----------------------------------------
>
>                 Key: ASTERISK-21416
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21416
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_gulp, Resources/res_srtp
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>              Labels: Asterisk12, NewSIP
>
> This task is to implement SDES-SRTP support in chan_gulp. This includes:
> * Refactoring out the setup of an SRTP session - given a set of SDP parameters - to minimize code duplication between chan_sip and chan_gulp. This would involve improving the code in sdp_crypto and sharing it between both channel drivers.
> * Defining and adding the necessary configuration parameters to an endpoint to enable encryption
> * Performing SRTP initialization on inbound requests and responding with the appropriate keys in a response
> * Transmitting SRTP keys given an endpoint's support for encryption
> * Re-initializing an SRTP session on a channel if a re-INVITE contains new keys
> * Adding automated tests to the test suite for chan_gulp that test negotiating SRTP keys

--
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