From: Kevin P. Fleming Date: Thu, 23 Jul 2009 22:32:17 +0000 (+0000) Subject: Use correct formatting for T.38 change note in UPGRADE.txt X-Git-Tag: 1.6.1.3-rc1~22 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=51f4a162c7416bc0824ef80d2d13729fa78f0771;p=thirdparty%2Fasterisk.git Use correct formatting for T.38 change note in UPGRADE.txt git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@208503 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/UPGRADE.txt b/UPGRADE.txt index 9a2901b4a0..e804548f21 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -20,15 +20,15 @@ From 1.6.1.1 to 1.6.1.2: -Beginning with this release, Asterisk's internal methods of -negotiating T.38 (FAX over IP) sessions changed in -non-backwards-compatible ways. Any applications that previously used -AST_CONTROL_T38 control frames will have to be upgraded to use -AST_CONTROL_T38_PARAMETERS control frames instead; app_fax.c is a good -example of how to generate and respond to these frames. These changes -were made to solve significant T.38 interoperability problems between -Asterisk and various SIP/T.38 endpoints identified by many users of -Asterisk. +* Beginning with this release, Asterisk's internal methods of + negotiating T.38 (FAX over IP) sessions changed in + non-backwards-compatible ways. Any applications that previously used + AST_CONTROL_T38 control frames will have to be upgraded to use + AST_CONTROL_T38_PARAMETERS control frames instead; app_fax.c is a good + example of how to generate and respond to these frames. These changes + were made to solve significant T.38 interoperability problems between + Asterisk and various SIP/T.38 endpoints identified by many users of + Asterisk. From 1.6.0.1 to 1.6.1: