![]() |
Luke,
We have yet to find ANY 'VoIP' service that is sufficiently robust to be used for a reliable fax service in the real world.
It's Voice Codecs over ATM -> i.e. AAL1/AAL2 over DSL/ATM PVCs terminated in ATM. There is No IP carrying the voice here. I clearly didn't say VOIP.
The box the Telco provides can also do VoIP as well which is annoying because customers can never know what gets provisioned. So it could be VoIP if the Telco is lying and ripping of all their customers [not likely], but for the purpose of informing the users can you show that you clearly acknowledge what kind of technology we are talking about here.
Can you please acknowledge that it's not VOIP and post again your opinions about running fax services using AAL2, specifically its own fax relay protocol (something like T.38). Can you refer it to someone else at mainpine, like in the US office (not the UK) if you don't feel qualified to comment on VoATM/VoDSL.
Have you tested what modes that IADs operate in and how they effect V.34 fax support - which I believe is your products main selling point?
Please confirm what I'm pretty sure that fax works fine over CBR 64k channels, The IAD's data sheet says "fax support - V27ter V.29 - NOT V.34, G3 & G4 data". So it is going to cap V.34 mode. This is a very common device in Australia that many businesses are taking up according to it's proponents.
I can see why the Telco is a fan of it due to political issues with telecoms trying to pay less for access to the copper wires (ULL) from the former monopoly holder - or just rent less PSTN lines. I'm trying to tee up to V.34 fax machines modems for a test tomorrow....
____________________ 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*