<br><br><div class="gmail_quote">On Tue, Dec 22, 2009 at 7:58 PM, Joseph L. Casale <span dir="ltr"><<a href="mailto:JCasale@activenetwerx.com">JCasale@activenetwerx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>> Am I correct in presuming that Freeswitch will answer a fax from a local zap based user<br>
>> just like it does from an FXO port connected to a POTS line? What I hope to do here is<br>
>> catch any call made from that extension (the zap based fax machine/user) and push its<br>
>> call into the fax module.<br>
><br>
> Yes, when a device (phone/fax/modem/whatever) is plugged into the FXS it gets dialtone<br>
> and dials. Whatever it dials is put into ${destination_number} just like any SIP phone that<br>
> dials. This extension looks ok. Try it out and let us know how it goes.<br>
> -MC<br>
<br>
Michael,<br>
It worked well, there was however a humorous moment: I was testing with my own shell script<br>
that simply emailed me directly to my postfix gateway, my exchange server and mua understood the<br>
uuencoded attachment so once it started working I modified the script to send to our fax service.<br>
<br>
Well they didn't understand uuencode so the attachment, a single page tiff, got faxed as 23 pages<br>
of binary :) I used mutt with a redirection to a specific muttrc which understands mime encoding<br>
which should work everywhere...<br>
<br>
Thanks for the help, you've made an office full of people happy...<br></blockquote><div>Thanks for letting us know that everything worked! I'm glad we didn't have to honor Tony's triple-your-money-back guarantee. :)<br>
-MC<br></div></div><br>