aboutsummaryrefslogtreecommitdiffstats
path: root/UPGRADE.txt
diff options
context:
space:
mode:
authorkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2009-10-01 16:18:43 +0000
committerkpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b>2009-10-01 16:18:43 +0000
commit1b3e1bd8ff5fd9516a490e955033ec9d62a70c12 (patch)
tree3b13d6ba9dc3bd3939833364f49eb949aadc532b /UPGRADE.txt
parentdb5df2fb6c5a2aee871ac36cd23efc54f0a46e60 (diff)
Merged revisions 221592 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk ........ r221592 | kpfleming | 2009-10-01 11:16:09 -0500 (Thu, 01 Oct 2009) | 12 lines Remove ability to control T.38 FAX error correction from udptl.conf. chan_sip has had the ability to control T.38 FAX error correction mode on a per-peer (or global) basis for a couple of releases now, which is where it should have been all along. This patch removes the ability to configure it in udptl.conf, but issues a warning if the user tries to do, telling them to look at sip.conf.sample for how to configure it now. For any SIP peers that are T.38 enabled in sip.conf, there is already a default for FEC error correction even if the user does not specify any mode, so this change will not turn off error correction by default, it will have the same default value that has been in the udptl.conf sample file. ........ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@221598 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r--UPGRADE.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt
index 01fb8f748..ce13b75ef 100644
--- a/UPGRADE.txt
+++ b/UPGRADE.txt
@@ -26,6 +26,10 @@ As of 1.6.0.16:
contrib/firmware/iax/ directory in the Asterisk source tree before running
"make install".
+* T.38 FAX error correction mode can no longer be configured in udptl.conf;
+ instead, it is configured on a per-peer (or global) basis in sip.conf, with
+ the same default as was present in udptl.conf.sample.
+
As of 1.6.0.15:
* There have been some changes to the IAX2 protocol to address the security