Asterisk And Hylafax: How To Debug …

Home » Asterisk Users » Asterisk And Hylafax: How To Debug …
Asterisk Users 4 Comments

Hi,

I hope you might give me some hints on how to find where my configuration is wrong, I am new to Asterisk and do not know, how to find the problem.

Running Asterisk (version: 1.8.13.1~dfsg-3) on Debian Wheezy. On the same maschine: hylafax fax server. I want hylafax to use t38modem (a virtual T.38 modem) for sending faxes. t38modem schould connect to asterisk on the same host.

If hylafax sends a fax it should use t38modem which ist connected to asterisk. Asterik is expected to establish an outbound connection to my SIP provider which supports T38. The asterisk box is behind nat.

For some reason, t38modem tells hylafax the line is BUSY so there is no fax send. I don’t know why there is a busy signal, maybe the call forwarding configuration is wrong, maybe the registration on my SIP provider fails, maybe ….?

I simply don’t know how to debug what’s going on. If Asterix trying to establish an outgoing connection … Maybe you can help to enlighten me 🙂

———[ sip.conf ]——————————————–

4 thoughts on - Asterisk And Hylafax: How To Debug …

  • Am 07.05.2013 18:23, schrieb Sebastian Niehaus:

    Well, I may add the log of t38modem (sorry for the ugly formatting)
    Parts I consider as most important are:

    ModemConnection::SetUpConnection dstNum9659 srcNum0 srcName=root

    … denied (all modems busy)

    SIP OnSetUp failed for INVITE from sip:06814003340@127.0.0.1:6060
    for Call[Cf64671db22]-EP
    ModemConnection::OnReleased Call -EP[modem:/C8670792521/0] (Call cleared because the line is out of service)

    Thanks for any suggestions ….

    here is all the log:
    ———————————

  • SN> Running Asterisk (version: 1.8.13.1~dfsg-3) on Debian Wheezy. On the SN> same maschine: Hylafax fax server. I want hylafax to use t38modem (a SN> virtual T.38 modem) for sending faxes. t38modem schould connect to SN> asterisk on the same host.

    SN> If hylafax sends a fax it should use t38modem which ist connected to SN> asterisk. Asterik is expected to establish an outbound connection to my SN> SIP provider which supports T38. The asterisk box is behind nat.

    Silly question: If you want to use T38 to the remote provider, and have t38modem, do you /need/ the asterisk in the middle?

    And if you /do/ need something between the two, might a sip proxy work better than a pbx?

    -JimC

  • Hi,

    Am Dienstag, den 07.05.2013, 21:48 +0200 schrieb Sebastian Niehaus:

    [ snip ]

    it seems to me, that the call is routed “from the modem to the modem” (and not to asterisk). t38modem has some config options for call routing. Something like:
    route=modem:.*=sip:@ip:port
    route=sip:.*=modem:

    The first rule routes calls from the modem to a sip destination. I think in Your setup it should be route=modem:.*=sip:@127.0.0.1:5060. (I
    never used localhost in a setup like this, it should work with the IP of Your ethernet too).

    HTH,

    Karsten

  • Am 08.05.2013 01:12, schrieb James Cloos:

    Not so silly …

    The hylafax server is behind NAT and I did not succeed to get t38modem running behind NAT. So I wanted to give asterisk a try since it has some features to make it work behind a natted connection.

    I am behind a IAD which does NAT. I cannot install my own software on the IAD. Therefore I did nit consider a SIP proxy.

    Thanks!

    Sebastian