aboutsummaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authorkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2009-06-16 01:08:56 +0000
committerkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2009-06-16 01:08:56 +0000
commit1c05391846dfea23af207f3a183fbbdb74f05f4b (patch)
tree334e46b40825f613e02566fb40c0e6dd489dfe9f /CHANGES
parent4f1b3c545b3c01487a7485ead2461b9e9299f507 (diff)
Merged revisions 200726 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk ........ r200726 | kpfleming | 2009-06-15 20:03:22 -0500 (Mon, 15 Jun 2009) | 6 lines Document the new automatic 'ignoresdpversion' behavior. Asterisk will now automatically ignore incorrect incoming SDP version numbers when necessary to complete a T.38 re-INVITE operation. ........ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@200729 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES20
1 files changed, 20 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 817fd7702..c57b7fc9e 100644
--- a/CHANGES
+++ b/CHANGES
@@ -8,6 +8,26 @@
===
======================================================================
+-----------------------------------------------------------------------------------
+--- Functionality changes from Asterisk 1.6.0.10 to Asterisk 1.6.0.11 -------------
+-----------------------------------------------------------------------------------
+
+SIP Changes
+-----------
+ * Added a new 'ignoresdpversion' option to sip.conf. When this is enabled
+ (either globally or for a specific peer), chan_sip will treat any SDP data
+ it receives as new data and update the media stream accordingly. By
+ default, Asterisk will only modify the media stream if the SDP session
+ version received is different from the current SDP session version. This
+ option is required to interoperate with devices that have non-standard SDP
+ session version implementations (observed with Microsoft OCS). This option
+ is disabled by default. In addition, this behavior is automatic when the SDP received
+ is in response to a T.38 re-INVITE that Asterisk initiated. In this situation,
+ since the call will fail if Asterisk does not process the incoming SDP, Asterisk
+ will accept the SDP even if the SDP version number is not properly incremented,
+ but will generate a warning in the log indicating that the SIP peer that sent
+ the SDP should have the 'ignoresdpversion' option set.
+
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 1.4.X to Asterisk 1.6.0 -------------
------------------------------------------------------------------------------