Re: [hylafax-users] Hylafax + IaxModem: No response to PPS repeated 3 times

[Tim Nelson]

----- Original Message -----

> Tim,

> Do you have any experience with T38?

> I am trying to use hylafax with t38 and am having issues with getting
> it installed and configured.

> Do you know if there is a good set of instructions?

> my provider supports t38. I am an trying to take advantage of that.

> i have used asterisk and hylafax with iaxmodem in the past but with a
> sangoma on pots lines.


You need "something" in place to do a T.38 gateway. This converts the T.38 media back to G.711u audio that IAXmodem can understand. This can be done in software (both Asterisk and FreeSWITCH have implementations), or via an external gateway like Audiocodes.

Also, you could use T38modem[1] to replace Asterisk/IAXmodem, allowing Hylafax to talk to your provider directly, depending on the setup. However, in the past I've not had success getting it compiled cleanly. Using available packages, I also got marginal success. However, many others report great success with it. YMMV

--Tim

[1] http://sourceforge.net/projects/t38modem/


____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*

[David Egger]

Hi!

With t38modem i hat the same problem...
Since I switched from T38modem to GOfax.IP
(https://github.com/gonicus/gofaxip) everything works fine for me.
We are currently receiving about 300+ faxes per day and send about 100.
Maybe you should give it a try?

Dave

[Tim Nelson]

----- Original Message -----
> Hi!
>
> With t38modem i hat the same problem...
> Since I switched from T38modem to GOfax.IP
> (https://github.com/gonicus/gofaxip) everything works fine for me.
> We are currently receiving about 300+ faxes per day and send about
> 100.
> Maybe you should give it a try?
>

Dave- Very interesting, I was not aware of the gofaxip project. Thanks!

--Tim

[Lee Howard]

On 10/09/2014 09:20 AM, David Egger wrote:
> With t38modem i hat the same problem...
> Since I switched from T38modem to GOfax.IP
> (https://github.com/gonicus/gofaxip) everything works fine for me.
> We are currently receiving about 300+ faxes per day and send about
> 100. Maybe you should give it a try?

Quoting the GOfax.IP URL given:

"In contrast to solutions like t38modem, iaxmodem and mod_spandsp's
softmodem feature, GOfax.IP does not emulate fax modem devices but
replaces HylaFAX's |faxgetty| and |faxsend| processes to communicate
directly with FreeSWITCH using FreeSWITCH's Event Socket interface."

It's unfortunate that they chose to go this route (replacing faxgetty
and faxsend). We have a long history of various developers doing as
much (replacing faxgetty and faxsend) such as CAPI4HylaFAX and over time
it breaks in some minor or major way because HylaFAX adds some feature
or modifies something such that the "replacements" either don't work at
all (usually not the case since we usually develop faxq in a
backwards-compatible way) or some new feature is added into the HylaFAX
version of faxgetty/faxsend, and users want it... but can't get it.

I would have much-preferred to have seen that FreeSWITCH Event Socket
interface developed-into HylaFAX directly. OR... there are other ways
to accomplish the same. (For example, the "proxy" feature in HylaFAX+.)

Thanks,

Lee.

[Steve Underwood]

On 10/11/2014 12:46 AM, Lee Howard wrote:
> On 10/09/2014 09:20 AM, David Egger wrote:
>> With t38modem i hat the same problem...
>> Since I switched from T38modem to GOfax.IP
>> (https://github.com/gonicus/gofaxip) everything works fine for me.
>> We are currently receiving about 300+ faxes per day and send about
>> 100. Maybe you should give it a try?
>
> Quoting the GOfax.IP URL given:
>
> "In contrast to solutions like t38modem, iaxmodem and mod_spandsp's
> softmodem feature, GOfax.IP does not emulate fax modem devices but
> replaces HylaFAX's |faxgetty| and |faxsend| processes to communicate
> directly with FreeSWITCH using FreeSWITCH's Event Socket interface."
>
> It's unfortunate that they chose to go this route (replacing faxgetty
> and faxsend). We have a long history of various developers doing as
> much (replacing faxgetty and faxsend) such as CAPI4HylaFAX and over
> time it breaks in some minor or major way because HylaFAX adds some
> feature or modifies something such that the "replacements" either
> don't work at all (usually not the case since we usually develop faxq
> in a backwards-compatible way) or some new feature is added into the
> HylaFAX version of faxgetty/faxsend, and users want it... but can't
> get it.
>
> I would have much-preferred to have seen that FreeSWITCH Event Socket
> interface developed-into HylaFAX directly. OR... there are other ways
> to accomplish the same. (For example, the "proxy" feature in HylaFAX+.)

Freeswitch can be configured to present a T.31 interface to HylaFAX, but
at this time that only supports audio FAXing. The T.31 modem module in
spandsp has a half finished T.38 mode, but there hasn't been a strong
incentive to finish it off.

Regards,
Steve