[svn-commits] kpfleming: trunk r205939 - /trunk/main/udptl.c

[SVN commits to the Digium repositories]

Author: kpfleming
Date: Fri Jul 10 13:44:09 2009
New Revision: 205939

URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=205939
Log:
Update comments about the level of T.38 support in Asterisk.

Modified:
    trunk/main/udptl.c

Modified: trunk/main/udptl.c
URL: http://svn.asterisk.org/svn-view/asterisk/trunk/main/udptl.c?view=diff&rev=205939&r1=205938&r2=205939
==============================================================================
--- trunk/main/udptl.c (original)
+++ trunk/main/udptl.c Fri Jul 10 13:44:09 2009
@@ -30,12 +30,11 @@
  *
  * \author Mark Spencer <markster at digium.com>,  Steve Underwood <steveu at coppice.org>
  * 
- * \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
  */