Busy signals detected

Help
2013-02-03
2013-05-28
  • Phil Reynolds
    Phil Reynolds
    2013-02-03

    I am using Debian wheezy, Asterisk 1:1.8.13.1~dfsg-1+0.1, t38modem 2.0.0-3, HylaFAX server 3:6.0.5-1 and all depenencies instaled fromthe Debian repository.

    I am, for the testing I am currently doing, starting t38modem with the command:

    t38modem -tt -o /var/log/t38modem.log -no-h323 -u T38modem -sip-listen udp\$127.0.0.1:6060 -ptty +/dev/ttyT38-1 -route "modem:.*=sip:<dn>@127.0.0.1" -route "sip:.*=modem:<dn>"

    … or the equivalent with my real IP - I have tried both.

    Calls are being made when I send a fax, but they are all resulting in "Busy signal detected" in HylaFAX.

    My complete t38modem.log for the last attempted use is at http://paste.debian.net/231373/ - can anyone advise me what I've got wrong?

     
  • Phil Reynolds
    Phil Reynolds
    2013-02-05

    I added t38pt_rtp = yes to my asterisk configs. Now I get this: http://paste.debian.net/231905/

    It's still considered a "Busy" by hylafax.

     
  • Phil Reynolds
    Phil Reynolds
    2013-05-08

    Further: I've now got to the stage where I have proven receiving to work. However, when sending, I get through to the other end but the fax is not sent and hylafax reports "Busy signal detected". This does not happen where the other end is another t38modem, it seems, but evidence suggests it does where it's anything else.

    Is there anything I can do about this, short of "give up"?