Re: [hylafax-users] faxing over sip

[Fernando <fernando.alhambra@xxxxxxxxx>]

I'm fed up with hearing that Fax over IP doesn't work at all:


Talking about my own experience (I'm not an expert and have not very
knowledge about these protocols),
I only have setup the HylaFAX server and all related to this box, all
about lan/wan, lines, etc. is anothers' job, this is my scenario:

I have setup HylaFAX 4.3.2 (by the moment only for receiving) with t38modem.
I have the Fax server in the headquarters of the company, right now
there are 40 fax numbers in a building 30kms far and 100 offices
around the country, most of them, more than 200kms far. I received
about 800-1000 faxes/day, from monday to friday and from 8:00-19:00
mainly. 35984 pages/month.
We need the best quality, and all of them are of the gratest importance.
I setup it in August, and from then to right now it's working wihtout
any problem.

It is working FoIP? It's a reality? Of course yes.



2007/11/23, Lee Howard <faxguy@xxxxxxxxxxxxxxxx>:
> Robert Moskowitz wrote:
>
> > Interestingly, IAXModem is enough like V.34 (It does have Steve's
> > spandsp code built-in) to work over most Internet connections (I am
> > told it does breakdown when the Net gets congested and RED kicks in on
> > the routers).
>
>
> I don't really understand the correlation between IAXmodem and V.34, but
> yes, I have done a number of things with IAXmodem to try to compensate
> for VoIP issues.  However, I suspect that the vast majority of the
> compensations are due to things done in HylaFAX/HylaFAX+, namely a
> tolerant Class 1 ECM protocol.
>
> > Also once IAXmodem incorporates this version of spanDSP, it should
> > work as well with T.38.
>
>
> Well, I have considered making IAXmodem use spandsp's T.38 features
> rather than the DSP... but I haven't settled on doing that.  If t38modem
> works then I don't have any reason to do that.  Furthermore, I don't
> have any immediate motivation to develop T.38 projects right now (I've
> no customers that depend on it).
>
> > Another piece of the puzzle is T38Modem for Hylafax.  A number of
> > people use that.  But us Trixbox people cannot as it requires kernel
> > patches to Centos :(
>
>
> t38modem 1.0.0 (in the OPAL project) supports both SIP and UNIX98 ptys.
> So... if that code can ever make it out of CVS/SVN then there's no
> patching of kernels required.
>
> > FAX is holding back large-scale movement to VoIP over classic switched
> > circuits.  Classic switch circuits are going away and except for
> > 'lifeline' will start costing more.  More people are going with GSM
> > for their only phone, and GSM CANNOT support T.30; no how/no way.
> >
> > T.38 will be the key piece that pulls fax over to the Internet along
> > with everything else.
>
>
> I disagree with this to some extent.  I do not doubt that fax is holding
> some people back from changing fully to VoIP.  I do not believe,
> however, that it is holding back a large-scale movement.  I have had
> enough experience with businesses and VoIP over the last few years to
> realize that to many of them the quality of their phone calls is too
> important, too valuable to concern themselves over the price
> difference.  The occassional audible jitter, the disconnections, etc...
> they aren't worth the price savings to them.
>
> It's really not a technical problem to solve, either.  VoIP cannot
> reliably replace the PSTN in all cases.  It's not a clear "better-than"
> kind of thing here.  I think that over time you're more likely to see a
> hybridization of VoIP and PSTN instead of a clear migration.
>
> Thanks,
>
> Lee.
>
>
> ____________________ HylaFAX(tm) Users Mailing List _______________________
>  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
>  On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
>  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
>
>


-- 
FAP


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