Hi Jared, the behaviour of rxfax changed between 1.2rc3 and trunk. In 1.2rc3 rxfax doesn't issue a reinvite if it detects fax, in trunk it does. I disabled this feature in rxfax for a client who needed to receive in *LAW due to a non-interoperable t.38 gateway.
Craig From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jared Geiger Sent: Saturday, 28 April 2007 8:32 AM To: Users Mailing List - Non-Commercial Discussion Subject: Re: [Callweaver-users] T38 woes On 4/25/07, CtRiX <[EMAIL PROTECTED]> wrote: Jared Geiger wrote: > I am getting further with getting Callweaver to talk to my fax machine > connected to a HT386. However I get a message from RxFax saying it can't > open TIFF file. The directory permissions are set to > callweaver:callweaver > I'm just not sure why its still having issues. > maybe because it can't traverse the previous directories. Try to specify a path like /tmp/test.tif to see if it works. > I have also found that I must do SipT38SwitchOver() to get the > reinvite to > occur. RxFax didn't do it automatically. depends on the codec you're using. Max Well I was able to get it working I had an extra ( in my sipfax context. exten => fax,n,RxFAX((${FAXFILE}|debug|ecm) should be exten => fax,n,RxFAX(${FAXFILE}|debug|ecm) However with the codec being ulaw I still have to initiate the SipT38SwitchOver() command to get it to work as t38. I did also notice if during a fax comes in and I have verified its using t38 by checking for activity with udptl debug ip I see that the codec shows ulaw when I do sip show channels. Is this normal? I haven't tested sending faxes yet. I will do that soon. Then I'll work on pass through support. Jared
_______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
