Thanks for your input so far everyone. The background is that I started with Asterisk (Trixbox actually), and had iaxmodem configured and running with hylafax. But alas, this was not T.38. My SIP provider fully supports T.38, and being a SIP provider, IAX was not an option anyway.
Next I stumbled upon t38modem, but I could not get OPAL to compile, an issue with missing libexpat-1 header files, which I failed to resolve. After more searching I found out about Callweaver and it's superior T.38 support. This is where I am now. I got Callweaver compiled, installed, and running, making successful outgoing voice calls. And I'm about to try the T.38 as per the link http://www.callweaver.org/wiki/Faxing+With+CallWeaver I'll concentrate on getting that to work for me for now. But the concern about lack of "managing the fax queue" remains. I'd love to use Hylafax in tandem with Callweaver but it doesn't appear to be possible at this stage? Unless I can have this scenario (all on the same host by the way): hylafax -> iaxmodem -> callweaver -> T.38 -> sip provider Cheers, Pete -----Original Message----- From: callweaver-users-boun...@callweaver.org [mailto:callweaver-users-boun...@callweaver.org] On Behalf Of Thomas Kenyon Sent: Tuesday, October 27, 2009 6:39 PM To: Users Mailing List - Non-Commercial Discussion Subject: Re: [Callweaver-users] outbound faxing Eric-Vittorio Li Destri wrote: > Hi, > > There's also T38modem. If your setup supports T38modem, the reliability > should be better because T38 protocol is specially designed for faxing over > IP. > > If you choose to use IAXmodem, your fax will be transported over a voice > codec that is not designed for this purpose, only a few codecs would give > decent results (such as G711 also called PCM) and the latency between your > provider MUST be as little as possible (less than 10ms where most dsl links > have 40ms latency). That's why i'd prefer T38 because latency is not a > problem with it. > > Give us your feedback ;) > > Eric I was assuming that he meant either iaxmodem and callweaver running on the same network (typical latency 0.2ms), or on the same host (typical latency barely measurable, around 0.04ms). I've not tried it, but this is a common setup. _______________________________________________ Callweaver-users mailing list Callweaver-users@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-users This communication including any email attachments is confidential. If you are not the intended recipient you are hereby notified that any use, disclosure or action taken in reliance on this email is unauthorized and strictly prohibited. If you have received the email in error please reply to the sender and destroy all copies. The sender does not warrant that this email is free from viruses and other defects. By opening this email you accept responsibility for all damages whether direct or indirect and agree that the sender's liability, if any, is limited to the re-supply of the email. The views expressed herein are those of the individual and not the organization unless expressly stated otherwise. _______________________________________________ Callweaver-users mailing list Callweaver-users@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-users
