#15 SIP to Analog

Mark Norton

I'm trying to setup a hylafax installation that will accept faxes from a SIP based PBX (zultys) and send faxes through an analog modem (ttyS0).

I'm using t38modem 2.0 with the SIPPDU patch and spanDSP plugin.

T38Modem Version 2.0.0 (OPAL-3.9.0/3.9beta0, PTLIB-2.9.0/2.9beta0 (svn:24174)) by Vyacheslav Frolov on Unix Linux (2.6.32-28-server-x86_64)

Using the following parameters:

t38modem -ttttt -o /var/log/t38modem.log --sip-proxy T38modem:1234@ --sip-disable-t38-mode --sip-register T38modem@,1234,, --ptty "+/dev/ttyT38-1,+/dev/ttyT38-2,+/dev/ttyT38-3" --no-h323 --route "sip:.*=modem:<dn>"

Hylafax receives the fax and stores it in the RECVQ directory.

I don't get a message back to the PBX that the fax was sent, so it keeps trying.

Also, I was hoping to configure the route so that Hylafax spooled up the fax and sent it out the analog modem (ttyS0)

Thank you for taking a look.



  • Mark Norton

    Mark Norton - 2011-07-20

    t38modem output

  • Mark Norton

    Mark Norton - 2011-07-20

    Additional information:

    OS: Linux Ubuntu 10.0.4
    Hylafax version 6.0.5 from scratch

    When sendfax is run from the command line, the USR modem on ttyS0 sends the fax without error

    Several places in the log file I see the local IP address along with "%eth0" for example:

    OpalUDP Setting interface to

    Also found this in the log:

    RTP_UDP Session 1, Control PDU from incorrect host, is should be

  • Mark Norton

    Mark Norton - 2011-07-23

    Just to followup, I changed the version of Hylafax to (hylafax+) 5.5.0.

    The pbx now sees faxes as received when sent to hylafax. (a step forward)

    Is there a way to get t38modem to send out via the hardware modem? I've tried to use the ModemGroup command in the config.ttyT38-1 file with no success.

    I think that I'm not understanding how the --route command works.

    Any help would be appreciated.




Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks