[asterisk-commits] file: branch file/sha256-a-harsh-reality r417586 - in /team/file/sha256-a-har...

[SVN commits to the Asterisk project]

Author: file
Date: Sun Jun 29 13:01:20 2014
New Revision: 417586

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=417586
Log:
Incorporate feedback.

Modified:
    team/file/sha256-a-harsh-reality/UPGRADE.txt
    team/file/sha256-a-harsh-reality/include/asterisk/rtp_engine.h

Modified: team/file/sha256-a-harsh-reality/UPGRADE.txt
URL: http://svnview.digium.com/svn/asterisk/team/file/sha256-a-harsh-reality/UPGRADE.txt?view=diff&rev=417586&r1=417585&r2=417586
==============================================================================
--- team/file/sha256-a-harsh-reality/UPGRADE.txt (original)
+++ team/file/sha256-a-harsh-reality/UPGRADE.txt Sun Jun 29 13:01:20 2014
@@ -26,6 +26,20 @@
    amount of data to the connected client, and the connected client is slow
    to process the received data, the socket may be disconnected. In such
    cases, it may be necessary to adjust this value. Default is 100 ms.
+ - Added a 'force_avp' option for chan_sip. When enabled this option will
+   cause the media transport in the offer or answer SDP to be 'RTP/AVP',
+   'RTP/AVPF', 'RTP/SAVP', or 'RTP/SAVPF' even if a DTLS stream has been
+   configured. This option can be set to improve interoperability with WebRTC
+   clients that don't use the RFC defined transport for DTLS.
+ - The 'dtlsverify' option in chan_sip now has additional values besides
+   'yes' and 'no'. If 'yes' is specified both the certificate and fingerprint
+   will be verified. If 'no' is specified then neither the certificate or
+   fingerprint is verified. If 'certificate' is specified then only the
+   certificate is verified. If 'fingerprint' is specified then only the
+   fingerprint is verified.
+ - A 'dtlsfingerprint' option has been added to chan_sip which allows the
+   hash to be specified for the DTLS fingerprint placed in SDP. Supported
+   values are 'sha-1' and 'sha-256' with 'sha-256' being the default.
 
 from 11.10.0 to 11.10.1
  - MixMonitor AMI actions now require users to have authorization classes.

Modified: team/file/sha256-a-harsh-reality/include/asterisk/rtp_engine.h
URL: http://svnview.digium.com/svn/asterisk/team/file/sha256-a-harsh-reality/include/asterisk/rtp_engine.h?view=diff&rev=417586&r1=417585&r2=417586
==============================================================================
--- team/file/sha256-a-harsh-reality/include/asterisk/rtp_engine.h (original)
+++ team/file/sha256-a-harsh-reality/include/asterisk/rtp_engine.h Sun Jun 29 13:01:20 2014
@@ -389,7 +389,7 @@
 
 /*! \brief DTLS verification settings */
 enum ast_rtp_dtls_verify {
-	AST_RTP_DTLS_VERIFY_NONE = 0,		 		/*!< Don't verify anything */
+	AST_RTP_DTLS_VERIFY_NONE = 0,               /*!< Don't verify anything */
 	AST_RTP_DTLS_VERIFY_FINGERPRINT = (1 << 0), /*!< Verify the fingerprint */
 	AST_RTP_DTLS_VERIFY_CERTIFICATE = (1 << 1), /*!< Verify the certificate */
 };