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
This commit is contained in:
Kevin P. Fleming 2009-07-10 18:44:09 +00:00
parent 5aab96f0b7
commit 7574941cb4
1 changed files with 5 additions and 5 deletions

View File

@ -30,12 +30,11 @@
* *
* \author Mark Spencer <markster@digium.com>, Steve Underwood <steveu@coppice.org> * \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 * Asterisk supports T.38 fax passthrough, origination and termination. It does
* or any form of gateway. Currently fax passthrough is only implemented in the * not support gateway operation. The only channel driver that supports T.38 at
* SIP channel for strict SIP to SIP calls. If you are using chan_local or chan_agent * this time is chan_sip.
* as a proxy channel, T.38 passthrough will not work.
* *
* UDPTL is handled very much like RTP. It can be reinvited to go directly between * UDPTL is handled very much like RTP. It can be reinvited to go directly between
* the endpoints, without involving Asterisk in the media stream. * the endpoints, without involving Asterisk in the media stream.
@ -43,6 +42,7 @@
* \b References: * \b References:
* - chan_sip.c * - chan_sip.c
* - udptl.c * - udptl.c
* - app_fax.c
*/ */