That solution works for both inbound and outbound although it's used primarily for inbound on my network. I use PRI T1s for the bulk of my outbound traffic.
I've been down the t38modem road and I've ended up with the same results you have. OPAL never compiles and that's where I'm stuck. Please let me know if you find a way around this. :-) I'd be very interested to retest it again. I've tried building on Debian 4.x/5.x as well as CentOS 5.x. To use t38modem, you'd still need some sort of softswitch that 'understands' the T.38 format. This would include Callweaver and Asterisk 1.6.x. --Tim Peter Verhoeven wrote: > So is that's an inbound or outbound solution you described there? > > I think I'm going to try t38modem again. Last time I attempted this I could > not get OPAL to compile. > > Would t38modem negate the need for Callweaver altogether? (in a send only > environment I mean). > > Cheers, > Pete > > -----Original Message----- > From: callweaver-users-boun...@callweaver.org > [mailto:callweaver-users-boun...@callweaver.org] On Behalf Of Tim Nelson > Sent: Thursday, November 19, 2009 1:30 AM > To: Users Mailing List - Non-Commercial Discussion > Subject: Re: [Callweaver-users] hylafax -> iaxmodem -> callweaver > > That sounds about right... I think that was the error message I was receiving > as well. > > I've been attempting to get T.38 working with > IAXmodem/Hylafax/{Asterisk|Callweaver} for some time now. My eventual route > has been to do SIP/T.38 to a Cisco gateway (1760 w/ DSPs) that pushes the > calls to an onboard PRI port(VWIC). This PRI port is connected to my > {Asterisk|Callweaver} system's PRI card which is in turn routed through to > the IAXmodems. Simple right? :-) It's a bit more complicated but it gets the > job done. > > --Tim > > ----- Original Message ----- > From: "Peter Verhoeven" <pe...@morrisint.com.au> > To: "Users Mailing List - Non-Commercial Discussion" > <callweaver-users@callweaver.org> > Sent: Tuesday, November 17, 2009 8:04:52 PM > Subject: Re: [Callweaver-users] hylafax -> iaxmodem -> callweaver > > Thanks Tim - it gives a warning that SipT38SwitchOver can only be used on SIP > channels, and then fails with the "exceptionally long queue" errors. > > So looks I'll need to write some inhouse software that creates the manual > spool files and copies them to the outgoing directory and let CallWeaver do > the rest. > > Basically noone in the world has a software based T.38 outgoing fax server is > my conclusion. Really weird given how long this technology has been around > and how unreliable any other form of ip based faxing is! > > Cheers, > Pete > > _______________________________________________ > 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 _______________________________________________ Callweaver-users mailing list Callweaver-users@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-users
