<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=307032112-23022008><FONT face=Arial
color=#0000ff size=2>Will the built-in T.38 support eliminate the need for
spandsp? I'm curious how this will affect iaxmodem.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=307032112-23022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=307032112-23022008><FONT face=Arial
color=#0000ff size=2>MD</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <B>On Behalf Of </B>Rob
Hillis<BR><B>Sent:</B> Saturday, February 23, 2008 7:12 AM<BR><B>To:</B>
Asterisk Users List<BR><B>Subject:</B> Re: [asterisk-users] FXO Cards -
T38<BR></FONT><BR></DIV>
<DIV></DIV>T.38 is a codec in exactly the same way that GSM or G.729 is a
codec, so yes it <I>can</I> be used at the same time as any other codec - just
that only <I>one</I> codec will be used at a time. What often happens is
that the call will initially be established with a codec such as G.729 or
G.711a, but once fax tones are detected the call will change codecs to
T.38.<BR><BR>According to the release notes for 1.6.0-b4...<BR><BR><PRE wrap=""> - 11873, Added core API changes to handle T.38 origination and termination
(The version of app_fax in Asterisk-addons now supports this.)
</PRE><BR>This should be all that is necessary to run a T.38
gateway.<BR><BR><BR>Steve Underwood wrote:
<BLOCKQUOTE cite=mid:47BFCB4C.3040805@coppice.org type="cite"><PRE wrap="">Rob Hillis wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">Not unless you're running CallWeaver or Asterisk 1.6.0-beta4. Asterisk
has had passthrough support for T.38 for a while (somewhere in 1.4 it
became available IIRC) but is currently completely incapable of
terminating or encoding a fax call to T.38.
</PRE></BLOCKQUOTE><PRE wrap=""><!---->I thought * was still not capable for T.38 gateway operation. Doesn't
beta 4 just added T.38 termination? And, I believe it misses out some
key elements of doing that properly. Note that T.38 termination is an
addon, so it can't be used with, say, G.729.
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">The only real option available at the moment is to keep one PSTN line on
an ATA with an FXO port and T.38 support available and direct calls from
the fax machines through to it. However, I should point out that while
I believe this should be possible, I haven't actually tried it myself.
</PRE></BLOCKQUOTE><PRE wrap=""><!---->Steve
_______________________________________________
-- Bandwidth and Colocation Provided by <A class=moz-txt-link-freetext href="http://www.api-digital.com">http://www.api-digital.com</A> --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<A class=moz-txt-link-freetext href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>