From: Kevin P. Fleming Date: Tue, 16 Jun 2009 01:07:27 +0000 (+0000) Subject: Merged revisions 200726 via svnmerge from X-Git-Tag: 1.6.1.3-rc1~158 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a498e2f0fecae32dbd468e6d99cf63ddf27c784b;p=thirdparty%2Fasterisk.git 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: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@200728 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/CHANGES b/CHANGES index bcfc1b6932..f441ea0a8a 100644 --- a/CHANGES +++ b/CHANGES @@ -8,6 +8,26 @@ === ====================================================================== +---------------------------------------------------------------------------------- +--- Functionality changes from Asterisk 1.6.1.1 to Asterisk 1.6.1.2 ------------- +---------------------------------------------------------------------------------- + +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.6.0 to Asterisk 1.6.1 ------------- ------------------------------------------------------------------------------