Re: [hylafax-users] Failure to receive silence (synchronization failure)

["Alex R [MaxoTel]" <alex@xxxxxxxxxxx>]

Ah-huh....

Well other people tend to get better results than me, that's all, so I guess
I assumed that since I was in such close proximity to the terminations (2ms,
over a peering arrangement) that I'd be able to achieve perfect results with
T.30

But, I've just called the VSP and they told me they do support T.38 - so I
guess I will try Hylafax with that. What I am thinking of doing is using
Callweaver (which claims to have T38 ability), but I really did want the
compatibility of Hylafax. Are there any Hylafax add-ons/virtual modems that
do direct T.38?

Thanks for your advice Lee :-)

Regards,

Alex R


-----Original Message-----
From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx] 
Sent: Thursday, 17 April 2008 2:46 PM
To: Alex R [MaxoTel]
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] Failure to receive silence (synchronization
failure)

Alex R [MaxoTel] wrote:
> I read that document the last time someone told me about it.
>
> But that doesn't help me in understanding what is causing this specific
> problem...

Well, you need to ask more specific questions then in order to get a 
more specific answer.

Very specifically the problem with faxing over VoIP is that VoIP uses 
UDP as a medium (as compared to TCP) and thus it's lossy.  The audio is 
modulated data.  If you remove chunks of audio then you remove chunks of 
data.  Thus, the "listener" doesn't consistently get all of the data 
being communicated, and furthermore the "choppiness" of the data causes 
the two endpoints to routinely become out-of-sync.

The degree of problem varies directly with the degree of lossy-ness of 
the UDP medium at the time of the call.  Some devices may tolerate some 
things more than others... and some fax applications may tolerate things 
better than others (i.e. HylaFAX+ is about as tolerant as I can make it 
of VoIP trouble), but in the end unless you have some way to control and 
mitigate the problems inherent with the UDP medium, then you'll likely 
have inconsistent and unreliable results.

However, what I think that you want me to do is point out a problem for 
you to fix.  And, unfortunately, the problem cannot really be fixed.  
This is why T.38 came along as an attempt to fix it... and even then 
T.38 still is not a perfect solution (it still uses UDP).

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*