mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-07 05:39:39 +00:00
Recorded merge of revisions 417677 from http://svn.asterisk.org/svn/asterisk/branches/11
........ res_rtp_asterisk: Add SHA-256 support for DTLS and perform DTLS negotiation on RTCP. This change fixes up DTLS support in res_rtp_asterisk so it can accept and provide a SHA-256 fingerprint, so it occurs on RTCP, and so it occurs after ICE negotiation completes. Configuration options to chan_sip and chan_pjsip have also been added to allow behavior to be tweaked (such as forcing the AVP type media transports in SDP). ASTERISK-22961 #close Reported by: Jay Jideliov Review: https://reviewboard.asterisk.org/r/3679/ Review: https://reviewboard.asterisk.org/r/3686/ ........ Merged revisions 417678 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@417679 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
@@ -473,6 +473,10 @@ struct ast_sip_media_rtp_configuration {
|
||||
unsigned int use_ptime;
|
||||
/*! Do we use AVPF exclusively for this endpoint? */
|
||||
unsigned int use_avpf;
|
||||
/*! Do we force AVP, AVPF, SAVP, or SAVPF even for DTLS media streams? */
|
||||
unsigned int force_avp;
|
||||
/*! Do we use the received media transport in our answer SDP */
|
||||
unsigned int use_received_transport;
|
||||
/*! \brief DTLS-SRTP configuration information */
|
||||
struct ast_rtp_dtls_cfg dtls_cfg;
|
||||
/*! Should SRTP use a 32 byte tag instead of an 80 byte tag? */
|
||||
|
Reference in New Issue
Block a user