From: Kevin P. Fleming Date: Fri, 10 Jul 2009 18:45:03 +0000 (+0000) Subject: Merged revisions 205939 via svnmerge from X-Git-Tag: 1.6.1.3-rc1~68 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b1832d4b4783fec0db4b208bcf82ef88869cf01a;p=thirdparty%2Fasterisk.git Merged revisions 205939 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ........ r205939 | kpfleming | 2009-07-10 13:44:09 -0500 (Fri, 10 Jul 2009) | 1 line Update comments about the level of T.38 support in Asterisk. ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@205941 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/main/udptl.c b/main/udptl.c index 2d192928f4..e39a9e7f28 100644 --- a/main/udptl.c +++ b/main/udptl.c @@ -30,12 +30,11 @@ * * \author Mark Spencer , Steve Underwood * - * \page T38fax_udptl T38 fax passhtrough :: UDPTL + * \page T38fax_udptl T.38 support :: UDPTL * - * Asterisk supports T.38 fax passthrough. Asterisk will not be a client, server - * or any form of gateway. Currently fax passthrough is only implemented in the - * SIP channel for strict SIP to SIP calls. If you are using chan_local or chan_agent - * as a proxy channel, T.38 passthrough will not work. + * Asterisk supports T.38 fax passthrough, origination and termination. It does + * not support gateway operation. The only channel driver that supports T.38 at + * this time is chan_sip. * * UDPTL is handled very much like RTP. It can be reinvited to go directly between * the endpoints, without involving Asterisk in the media stream. @@ -43,6 +42,7 @@ * \b References: * - chan_sip.c * - udptl.c + * - app_fax.c */