[asterisk-dev] Fax with Asterisk and T38Modem

[Steve Totaro]

It has been a while, but I do remember creating a dynamic cover page for
outbound faxes.

http://hylafax.sourceforge.net/man/faxcover.php

Thanks,
Steve Totaro

On Fri, Jul 1, 2011 at 3:44 AM, Wolfgang Pichler <wpichler at yosd.at> wrote:

> Hi,
>
> i have already used t38modem with asterisk 1.8.3 with the problems you
> have described...
>
> But i did have had another problem - i was not able to somehow pass
> the sender information onto asterisk. I wanted to get the hylafax
> username which has originated the fax to asterisk - to be able to set
> the correct outgoing callerid - but didn't manage this.
>
> Have you already got this working ?
>
> br,
> Wolfgang
>
> 2011/6/29 Thorolf Godawa <nospam at godawa.de>:
> > Hi,
> >
> > I'm fighting with HylaFAX, Asterisk and T38Modem since some time, to get
> > fax2mail and mail2fax working, my SIP-provider only supports T38 and
> > thus using G711 with IAXModem is not an option.
> >
> >
> > I have got running mail2fax with HylaFAX+ 5.5.0, Asterisk 1.4.20 and
> > T38Modem 2.0.0 successfull, but I'm not able to upgrade to anything
> > newer than Asterisk 1.4.24.
> >
> > I was able to track down this problem to some changes in the chan_sip.c,
> > where a "improved support for T38 on initial INVITE" has been
> > implemented, see:
> > <https://reviewboard.asterisk.org/r/208/diff/#index_header>
> >
> > I'm not sure what the problem is, but it seems that the T38 handshake
> > does not work correct any more bacause the CFR (confirm to receive) is
> > missing.
> >
> > Goal is, to get running this with the latest Asterisk, right now
> > 1.8.4.4. Is there s.b. who can give me a hint how to solve the problem?
> >
> >
> > For fax2mail I use Asterisk 1.8.4.4, but it is not working too, after a
> > fax call, the connection with T38Modem is established, HylaFAX reports
> > "ANSWER: FAX CONNECTION DEVICE '/dev/ttyT380'", but a fax is never
> received.
> >
> > In the tcpdump I see the correct handshaking between Asterisk and
> > T38Modem, but finaly T38Modem makes a second REINVITE with "recvonly"
> > and Asterisk answers with "SIP/2.0 488 Not acceptable here" and the call
> > ends shortly after that.
> >
> > As far as I can see, T38Modem does not accept the portchange from rtp to
> > udtpl and thus tries a REINVITE. Probably there is a problem in
> > T38Modem, so I filed a bug at sourceforge for that:
> >
> >
> https://sourceforge.net/tracker/?func=detail&aid=3337581&group_id=152230&atid=783657
> >
> > But may be, somebody has a solution for this too.
> >
> >
> > Thanks a lot,
> > --
> >
> > Chau y hasta luego,
> >
> > Thorolf
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20110701/acdaad98/attachment.htm>