-
- Downloads
Allow SRTP policies to be reloaded
Currently, when using res_srtp, once the SRTP policy has been added to the current session the policy is locked into place. Any attempt to replace an existing policy, which would be needed if the remote endpoint negotiated a new cryptographic key, is instead rejected in res_srtp. This happens in particular in transfer scenarios, where the endpoint that Asterisk is communicating with changes but uses the same RTP session. This patch modifies res_srtp to allow remote and local policies to be reloaded in the underlying SRTP library. From the perspective of users of the SRTP API, the only change is that the adding of remote and local policies are now added in a single method call, whereas they previously were added separately. This was changed to account for the differences in handling remote and local policies in libsrtp. Review: https://reviewboard.asterisk.org/r/1741/ (closes issue ASTERISK-19253) Reported by: Thomas Arimont Tested by: Thomas Arimont Patches: srtp_renew_keys_2012_02_22.diff uploaded by Matt Jordan (license 6283) (with some small modifications for this check-in) ........ Merged revisions 356604 from http://svn.asterisk.org/svn/asterisk/branches/1.8 ........ Merged revisions 356605 from http://svn.asterisk.org/svn/asterisk/branches/10 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@356606 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Showing
- channels/sip/sdp_crypto.c 3 additions, 11 deletionschannels/sip/sdp_crypto.c
- include/asterisk/res_srtp.h 10 additions, 0 deletionsinclude/asterisk/res_srtp.h
- include/asterisk/rtp_engine.h 19 additions, 1 deletioninclude/asterisk/rtp_engine.h
- main/rtp_engine.c 10 additions, 3 deletionsmain/rtp_engine.c
- res/res_srtp.c 60 additions, 18 deletionsres/res_srtp.c
Loading
Please register or sign in to comment