[svn-commits] kpfleming: branch 1.6.0 r200729 - in /branches/1.6.0: ./ CHANGES

[SVN commits to the Digium repositories]

Author: kpfleming
Date: Mon Jun 15 20:08:56 2009
New Revision: 200729

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=200729
Log:
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.
........

Modified:
    branches/1.6.0/   (props changed)
    branches/1.6.0/CHANGES

Propchange: branches/1.6.0/
------------------------------------------------------------------------------
Binary property 'trunk-merged' - no diff available.

Modified: branches/1.6.0/CHANGES
URL: http://svn.asterisk.org/svn-view/asterisk/branches/1.6.0/CHANGES?view=diff&rev=200729&r1=200728&r2=200729
==============================================================================
--- branches/1.6.0/CHANGES (original)
+++ branches/1.6.0/CHANGES Mon Jun 15 20:08:56 2009
@@ -7,6 +7,26 @@
 === and the other UPGRADE files for older releases.
 ===
 ======================================================================
+
+-----------------------------------------------------------------------------------
+--- 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  -------------