summaryrefslogtreecommitdiff
path: root/main/udptl.c
diff options
context:
space:
mode:
authorKevin P. Fleming <kpfleming@digium.com>2009-07-10 18:44:09 +0000
committerKevin P. Fleming <kpfleming@digium.com>2009-07-10 18:44:09 +0000
commit7574941cb4130b95d52723c36cec37ceb0f9abea (patch)
treee8d3a20c34f7a614e3e0c5089b8886c91d2227ce /main/udptl.c
parent5aab96f0b7486bb4f7ec0bce74c5adb7f5842527 (diff)
Update comments about the level of T.38 support in Asterisk.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@205939 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'main/udptl.c')
-rw-r--r--main/udptl.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/main/udptl.c b/main/udptl.c
index dfe89e126..7f7a2b76a 100644
--- a/main/udptl.c
+++ b/main/udptl.c
@@ -30,12 +30,11 @@
*
* \author Mark Spencer <markster@digium.com>, Steve Underwood <steveu@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
*/