Thank you guys, I just sorted out the multiple sofia profiles and have FS accepting SIP registrations on our LAN. I plugged a phone into the LAN and it works. Now I'm trying to get this VoIP Plug-In for Microsoft Fax to work, that I downloaded from www.faxback.com. I configured it with a directory number I created, the dialplan seems to work, but it fails when sending the test FAX. The FAX number I'm calling is a POTS line connected to a Fax modem, which is answered by Hylafax. This works and is used everyday. The faxback software is installed on a Windows 7 machine, and configured by putting in a proxy address of 192.168.1.17, a username and password, and address of user@domain. The test call rings the fax modem, it answers, but then after some handshaking, it hangs up and the window says the call was hung up. Hylafax says: "No answer (T.30 T1 timeout)" -- Steve
What does the FS log say? You should have some mod_spandsp log lines in there that mention what's going on with the fax attempt. Also, are you routing the call to the txfax app? Just curious how the fax call gets connected in the first place. -MC On Mon, Jan 14, 2013 at 4:23 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
Thank you guys, I just sorted out the multiple sofia profiles and have FS accepting SIP registrations on our LAN. I plugged a phone into the LAN and it works.
Now I'm trying to get this VoIP Plug-In for Microsoft Fax to work, that I downloaded from www.faxback.com. I configured it with a directory number I created, the dialplan seems to work, but it fails when sending the test FAX.
The FAX number I'm calling is a POTS line connected to a Fax modem, which is answered by Hylafax. This works and is used everyday. The faxback software is installed on a Windows 7 machine, and configured by putting in a proxy address of 192.168.1.17, a username and password, and address of user@domain.
The test call rings the fax modem, it answers, but then after some handshaking, it hangs up and the window says the call was hung up.
Hylafax says: "No answer (T.30 T1 timeout)"
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org> wrote:
What does the FS log say? You should have some mod_spandsp log lines in there that mention what's going on with the fax attempt. Also, are you routing the call to the txfax app? Just curious how the fax call gets connected in the first place.
The call is being routed *from* the Microsoft FAX plug in. The routing works like this: 1. FAX is initiated with Microsoft FAX on Windows 2. It goes through the faxback.com plug-in on the same machine. 3. The plug-in is configured to make a SIP connection to the FS pbx. 4. The FS pbx routes the call to the PSTN through sip.flowroute.com. 5. The call is received by a POTS line, connected to a modem. 6. The modem is connected with a serial line to a Linux machine. 7. The Linux machine runs Hylafax (www.hylafax.org). Steps 4-5 work for voice calls, using Polycom phones. Steps 5-7 work for other FAX calls, received often. The log for the faxback.com plug-in is at http://pastebin.freeswitch.org/20448. The FS log is at http://pastebin.freeswitch.org/20449. The Hylafax log is at http://pastebin.freeswitch.org/20450. New info: I put a test set on the PSTN fax line. (Yes, I'm old school telephony.) I hear the fax modem giving the normal terminating fax pre-message signal, and the originating fax sending the normal CNG tones. However, these tones don't stop. It's like the originating fax can't hear the pre-message signal from the fax modem. -- Steve
It seems that you may be debugging way too many things at once. Do you know much about the FAXBACK.COM internals? Just for a test you know you can bypass it. FreeSWITCH will work just fine on a windows box, using the FAXModem stuff, and com0com driver. That's what I use to have the M$ fax service talk to, and it works great. No hardware, and FS doing T38 right out of the Fax Service Server. At least if you test this way, you have FS logs and access to all the internals, and you can eliminate the "Black Box" in the middle. --Dave _____ From: Steven Schoch [mailto:schoch+freeswitch.org@xwin32.com] To: FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org] Sent: Tue, 15 Jan 2013 09:58:28 -0800 Subject: Re: [Freeswitch-users] FAX problems On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org> wrote: What does the FS log say? You should have some mod_spandsp log lines in there that mention what's going on with the fax attempt. Also, are you routing the call to the txfax app? Just curious how the fax call gets connected in the first place. The call is being routed from the Microsoft FAX plug in. The routing works like this: 1. FAX is initiated with Microsoft FAX on Windows 2. It goes through the faxback.com plug-in on the same machine. 3. The plug-in is configured to make a SIP connection to the FS pbx. 4. The FS pbx routes the call to the PSTN through sip.flowroute.com. 5. The call is received by a POTS line, connected to a modem. 6. The modem is connected with a serial line to a Linux machine. 7. The Linux machine runs Hylafax (www.hylafax.org). Steps 4-5 work for voice calls, using Polycom phones. Steps 5-7 work for other FAX calls, received often. The log for the faxback.com plug-in is at http://pastebin.freeswitch.org/20448. The FS log is at http://pastebin.freeswitch.org/20449. The Hylafax log is at http://pastebin.freeswitch.org/20450. New info: I put a test set on the PSTN fax line. (Yes, I'm old school telephony.) I hear the fax modem giving the normal terminating fax pre-message signal, and the originating fax sending the normal CNG tones. However, these tones don't stop. It's like the originating fax can't hear the pre-message signal from the fax modem. -- Steve
My whole plan here is to replace the phone system currently in the office (a NexPath system, a really nice PC-chassis pbx system from the 1990's) to a more modern VoIP system, and git rid of all our POTS lines. But I need a simple solution for the users who send FAXes from their Windows systems. On Tue, Jan 15, 2013 at 10:48 AM, Dave R. Kompel <drk@drkngs.net> wrote:
** It seems that you may be debugging way too many things at once. Do you know much about the FAXBACK.COM internals?
Yes, that's probably correct. No, I don't know much about faxback.com. However, I just tried a different one, www.t38faxvoip.com. It's a much more involved Windows installation, but it came up with the same symptoms. This is leading me to believe that the problem is more likely my FS configuration. Just for a test you know you can bypass it. FreeSWITCH will work just fine
on a windows box, using the FAXModem stuff, and com0com driver.
That's not my objective. I'm still early in the learning process for FreeSwitch, and I'd like to keep it to one installation, on an OS that I can understand (Linux). That's what I use to have the M$ fax service talk to, and it works great.
No hardware, and FS doing T38 right out of the Fax Service Server.
Let me see if I understand: MS Fax is talking through a virtual serial cable (com0com) to what it thinks is a FAX modem. On the other side of that virtual serial cable is something that takes the serial FAX data, translates it to T38, and injects it into FS. I'm a little unclear on the last 2 pieces, because it still sounds like a black box to me. What's "Fax Service Server"? On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org> wrote:
Also, are you routing the call to the txfax app?
I'm not. I assumed that the purpose of txfax is to encode a TIFF file into a T.38 stream, and my source is already T.38. Am I missing something? -- Steve
In FreeSWITCH, mod_spandsp, will also emulate fax modems. Com0Com is like a PTY driver for windows. When you set modem_count in spandsp.conf.xml to a count other then 0, the windows implmentation starts at COM3. So to get T.38 emulated fax modems, you don't need anything other then FreeSWITCH. Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box. --Dave _____ From: Steven Schoch [mailto:schoch+freeswitch.org@xwin32.com] To: FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org] Sent: Tue, 15 Jan 2013 16:39:15 -0800 Subject: Re: [Freeswitch-users] FAX problems My whole plan here is to replace the phone system currently in the office (a NexPath system, a really nice PC-chassis pbx system from the 1990's) to a more modern VoIP system, and git rid of all our POTS lines. But I need a simple solution for the users who send FAXes from their Windows systems. On Tue, Jan 15, 2013 at 10:48 AM, Dave R. Kompel <drk@drkngs.net> wrote: It seems that you may be debugging way too many things at once. Do you know much about the FAXBACK.COM internals? Yes, that's probably correct. No, I don't know much about faxback.com. However, I just tried a different one, www.t38faxvoip.com. It's a much more involved Windows installation, but it came up with the same symptoms. This is leading me to believe that the problem is more likely my FS configuration. Just for a test you know you can bypass it. FreeSWITCH will work just fine on a windows box, using the FAXModem stuff, and com0com driver. That's not my objective. I'm still early in the learning process for FreeSwitch, and I'd like to keep it to one installation, on an OS that I can understand (Linux). That's what I use to have the M$ fax service talk to, and it works great. No hardware, and FS doing T38 right out of the Fax Service Server. Let me see if I understand: MS Fax is talking through a virtual serial cable (com0com) to what it thinks is a FAX modem. On the other side of that virtual serial cable is something that takes the serial FAX data, translates it to T38, and injects it into FS. I'm a little unclear on the last 2 pieces, because it still sounds like a black box to me. What's "Fax Service Server"? On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org> wrote: Also, are you routing the call to the txfax app? I'm not. I assumed that the purpose of txfax is to encode a TIFF file into a T.38 stream, and my source is already T.38. Am I missing something? -- Steve
Hi Dave, Thanks for this info. Can you explain a little more detail about the TCP pipe? I can see SpanDSP create a /dev/FS0 on linux, but how to pipe a TCP connection to linux on Windows? Does SpanDSP also listen on a TCP port? Or need other software to map a TCP port to /dev/FS0? Thanks. On Wednesday, January 16, 2013 at 10:52 AM, Dave R. Kompel wrote:
In FreeSWITCH, mod_spandsp, will also emulate fax modems. Com0Com is like a PTY driver for windows. When you set modem_count in spandsp.conf.xml to a count other then 0, the windows implmentation starts at COM3. So to get T.38 emulated fax modems, you don't need anything other then FreeSWITCH.
Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box.
--Dave
From: Steven Schoch [mailto:schoch+freeswitch.org@xwin32.com] To: FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org] Sent: Tue, 15 Jan 2013 16:39:15 -0800 Subject: Re: [Freeswitch-users] FAX problems
My whole plan here is to replace the phone system currently in the office (a NexPath system, a really nice PC-chassis pbx system from the 1990's) to a more modern VoIP system, and git rid of all our POTS lines. But I need a simple solution for the users who send FAXes from their Windows systems.
On Tue, Jan 15, 2013 at 10:48 AM, Dave R. Kompel <drk@drkngs.net (mailto:drk@drkngs.net)> wrote:
It seems that you may be debugging way too many things at once. Do you know much about the FAXBACK.COM (http://faxback.com/) internals?
Yes, that's probably correct. No, I don't know much about faxback.com (http://faxback.com/).
However, I just tried a different one, www.t38faxvoip.com (http://www.t38faxvoip.com/). It's a much more involved Windows installation, but it came up with the same symptoms. This is leading me to believe that the problem is more likely my FS configuration.
Just for a test you know you can bypass it. FreeSWITCH will work just fine on a windows box, using the FAXModem stuff, and com0com driver.
That's not my objective. I'm still early in the learning process for FreeSwitch, and I'd like to keep it to one installation, on an OS that I can understand (Linux).
That's what I use to have the M$ fax service talk to, and it works great. No hardware, and FS doing T38 right out of the Fax Service Server.
Let me see if I understand: MS Fax is talking through a virtual serial cable (com0com) to what it thinks is a FAX modem. On the other side of that virtual serial cable is something that takes the serial FAX data, translates it to T38, and injects it into FS. I'm a little unclear on the last 2 pieces, because it still sounds like a black box to me. What's "Fax Service Server"?
On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org (mailto:msc@freeswitch.org)> wrote:
Also, are you routing the call to the txfax app?
I'm not. I assumed that the purpose of txfax is to encode a TIFF file into a T.38 stream, and my source is already T.38. Am I missing something?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org (mailto:consulting@freeswitch.org) http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org (mailto:FreeSWITCH-users@lists.freeswitch.org) http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
From what I read, you need com0com compiled on Linux as well. So you do COM->IP on Windows and IP->TTY on Linux.
João Mesquita FreeSWITCH™ Solutions On Wed, Jan 16, 2013 at 1:06 PM, Seven Du <dujinfang@gmail.com> wrote:
Hi Dave,
Thanks for this info. Can you explain a little more detail about the TCP pipe? I can see SpanDSP create a /dev/FS0 on linux, but how to pipe a TCP connection to linux on Windows? Does SpanDSP also listen on a TCP port? Or need other software to map a TCP port to /dev/FS0?
Thanks.
On Wednesday, January 16, 2013 at 10:52 AM, Dave R. Kompel wrote:
In FreeSWITCH, mod_spandsp, will also emulate fax modems. Com0Com is like a PTY driver for windows. When you set modem_count in spandsp.conf.xml to a count other then 0, the windows implmentation starts at COM3. So to get T.38 emulated fax modems, you don't need anything other then FreeSWITCH.
Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box.
--Dave
------------------------------ *From:* Steven Schoch [mailto:schoch+freeswitch.org@xwin32.com<schoch+freeswitch.org@xwin32.com> ] *To:* FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org<freeswitch-users@lists.freeswitch.org> ] *Sent:* Tue, 15 Jan 2013 16:39:15 -0800 *Subject:* Re: [Freeswitch-users] FAX problems
My whole plan here is to replace the phone system currently in the office (a NexPath system, a really nice PC-chassis pbx system from the 1990's) to a more modern VoIP system, and git rid of all our POTS lines. But I need a simple solution for the users who send FAXes from their Windows systems.
On Tue, Jan 15, 2013 at 10:48 AM, Dave R. Kompel <drk@drkngs.net> wrote:
** It seems that you may be debugging way too many things at once. Do you know much about the FAXBACK.COM <http://faxback.com/> internals?
Yes, that's probably correct. No, I don't know much about faxback.com.
However, I just tried a different one, www.t38faxvoip.com. It's a much more involved Windows installation, but it came up with the same symptoms. This is leading me to believe that the problem is more likely my FS configuration.
Just for a test you know you can bypass it. FreeSWITCH will work just fine on a windows box, using the FAXModem stuff, and com0com driver.
That's not my objective. I'm still early in the learning process for FreeSwitch, and I'd like to keep it to one installation, on an OS that I can understand (Linux).
That's what I use to have the M$ fax service talk to, and it works great. No hardware, and FS doing T38 right out of the Fax Service Server.
Let me see if I understand: MS Fax is talking through a virtual serial cable (com0com) to what it thinks is a FAX modem. On the other side of that virtual serial cable is something that takes the serial FAX data, translates it to T38, and injects it into FS. I'm a little unclear on the last 2 pieces, because it still sounds like a black box to me. What's "Fax Service Server"?
On Mon, Jan 14, 2013 at 5:12 PM, Michael Collins <msc@freeswitch.org> wrote:
Also, are you routing the call to the txfax app?
I'm not. I assumed that the purpose of txfax is to encode a TIFF file into a T.38 stream, and my source is already T.38. Am I missing something?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Tue, Jan 15, 2013 at 6:52 PM, Dave R. Kompel <drk@drkngs.net> wrote:
** Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box.
That sounds like the way to go. I'll give that a try. But first, I have another FAX problem. The users here use a real FAX machine to send FAXes. Since we're getting rid of the POTS lines, I attempted to use a (cheap) OBi100 to connect the analog FAX machine to the FreeSwitch box. It didn't work. Voice calls work, but it can't seem to sync with the remote FAX machine. Any ideas how to get a regular FAX machine to work with VoIP? -- Steve
You need an ATA that hopefully won't mangle your fax transmissions. I've heard that the SPA 112's are pretty good, but that's only anecdotal. At least they are inexpensive, so it's not a large investment to give it a try. -MC On Wed, Jan 16, 2013 at 3:24 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
On Tue, Jan 15, 2013 at 6:52 PM, Dave R. Kompel <drk@drkngs.net> wrote:
** Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box.
That sounds like the way to go. I'll give that a try.
But first, I have another FAX problem. The users here use a real FAX machine to send FAXes. Since we're getting rid of the POTS lines, I attempted to use a (cheap) OBi100 to connect the analog FAX machine to the FreeSwitch box. It didn't work. Voice calls work, but it can't seem to sync with the remote FAX machine. Any ideas how to get a regular FAX machine to work with VoIP?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
On Tue, Jan 15, 2013 at 6:52 PM, Dave R. Kompel <drk@drkngs.net> wrote:
** Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box.
I just tried that with limited success. I turned on 2 of the SPANDSP modems (and figured I had to give the freeswitch account (the user that runs freeswitch) write permission to the /dev directory so it could create the symlinks). I then installed com0com on my Windows 7 box, installed sercd on the FS server (Linux), and ran hub4com on the Windows box to connect to sercd. As a result of all that, I can use Putty to connect do the CNCA0 serial device, and issue AT commands, and it responds like a modem! I issued an ATDT <fax number> command and the call came through to the fax machine. (This is the FAX machine connected to the POTS line.) However, when I installed a "Standard 56000 bps Modem" connected to CNCA0, and attempted to use it to send a FAX from Windows, it said "An unexpected problem occurred." To make sure Freeswitch can actually do FAX, I ran originate sofia/gateway/<gateway name>/<phone number> &txfax(/path_to_fax_file) where the fax file specified was a TIFF file that I had lying around. This was successful. I'm now considering installing the Windows version of FreeSwitch on the machine of everybody who needs to send FAXes. That may take less time and trouble. -- Steve
I use the windows version of FreeSWITCH with fax modems on a Windows Server box, running the normal Microsoft Fax Service. It's been working using the SPANDSP fax modems perfict for over a year. The thing you have to remember is that the modem in mod_spandsp is T.31, not T.38. If you wan't T.38 you need to run the call through T.38 Gateway, just as if the modem device as a TDM line. Look at the SPANDSP wiki page for reference. I know this works on windows, and should also work on linux. I'm not sure about the built in client fax in windows 7, but I know it works with the fax service role on windows server. --Dave _____ From: Steven Schoch [mailto:schoch+freeswitch.org@xwin32.com] To: FreeSWITCH Users Help [mailto:freeswitch-users@lists.freeswitch.org] Sent: Fri, 18 Jan 2013 17:40:00 -0800 Subject: Re: [Freeswitch-users] FAX problems On Tue, Jan 15, 2013 at 6:52 PM, Dave R. Kompel <drk@drkngs.net> wrote: Another option would be on the Linux box, enable SPANDSP modems, and use com0com on windows to backup com ports to raw TCP connections. It supports both. That way it would talk over a TCP pipe to an emulated modem on your other FreeSWITCH box. I just tried that with limited success. I turned on 2 of the SPANDSP modems (and figured I had to give the freeswitch account (the user that runs freeswitch) write permission to the /dev directory so it could create the symlinks). I then installed com0com on my Windows 7 box, installed sercd on the FS server (Linux), and ran hub4com on the Windows box to connect to sercd. As a result of all that, I can use Putty to connect do the CNCA0 serial device, and issue AT commands, and it responds like a modem! I issued an ATDT <fax number> command and the call came through to the fax machine. (This is the FAX machine connected to the POTS line.) However, when I installed a "Standard 56000 bps Modem" connected to CNCA0, and attempted to use it to send a FAX from Windows, it said "An unexpected problem occurred." To make sure Freeswitch can actually do FAX, I ran originate sofia/gateway/<gateway name>/<phone number> &txfax(/path_to_fax_file) where the fax file specified was a TIFF file that I had lying around. This was successful. I'm now considering installing the Windows version of FreeSwitch on the machine of everybody who needs to send FAXes. That may take less time and trouble. -- Steve
Here's an update on my FAX project: On our main FreeSWITCH pbx (on CentOS), I run this command through the CLI and it works: freeswitch@internal> originate sofia/gateway/flowroute/1408739xxxx &txfax(/home/schoch/fax000007603.tif) I did a basic install on a Windows machine, by downloading the installer, installing it, and changing the "default_provider" lines in vars.xml in order to make it connect to our pbx. A "sofia status" shows it's connected. Then I ran this command on the Windows machine: freeswitch@internal> originate sofia/gateway/external::starnet_fax/1408739xxxx &txfax(C:/Users/Schoch/Pictures/fax000007603.tif) It rang the FAX machine, but the FAX never got there. It got some sort of a timeout: 2013-01-22 14:09:10.224456 [DEBUG] switch_rtp.c:928 [ zrtp engine]: WARNING! HELLO Max retransmissions count reached (20 retries). ID=1 and 2013-01-22 14:10:07.744746 [DEBUG] mod_spandsp_fax.c:500 Fax processing not successful - result (2) Timed out waiting for initial communication. I'm not sure where to go from here. Any ideas? -- Steve
I find it interesting that the ZRTP engine threw a warning. Do you see any ZRTP messages on the Linux log where the fax actually worked? -MC On Tue, Jan 22, 2013 at 2:35 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
Here's an update on my FAX project:
On our main FreeSWITCH pbx (on CentOS), I run this command through the CLI and it works:
freeswitch@internal> originate sofia/gateway/flowroute/1408739xxxx &txfax(/home/schoch/fax000007603.tif)
I did a basic install on a Windows machine, by downloading the installer, installing it, and changing the "default_provider" lines in vars.xml in order to make it connect to our pbx. A "sofia status" shows it's connected.
Then I ran this command on the Windows machine: freeswitch@internal> originate sofia/gateway/external::starnet_fax/1408739xxxx &txfax(C:/Users/Schoch/Pictures/fax000007603.tif)
It rang the FAX machine, but the FAX never got there. It got some sort of a timeout: 2013-01-22 14:09:10.224456 [DEBUG] switch_rtp.c:928 [ zrtp engine]: WARNING! HELLO Max retransmissions count reached (20 retries). ID=1 and 2013-01-22 14:10:07.744746 [DEBUG] mod_spandsp_fax.c:500 Fax processing not successful - result (2) Timed out waiting for initial communication.
I'm not sure where to go from here. Any ideas?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
I've tried a few more things, but it's still not there. Here's the latest log from the Windows machine: http://pastebin.freeswitch.org/20500 I've been told that I need to enable T.38, because the txfax module doesn't do that, but I can't figure out how. Any suggestions? -- Steve
On Wed, Jan 23, 2013 at 9:19 AM, Michael Collins <msc@freeswitch.org> wrote:
I find it interesting that the ZRTP engine threw a warning. Do you see any ZRTP messages on the Linux log where the fax actually worked?
No, it just worked, with none of those messages. The Linux log is here: http://pastebin.freeswitch.org/20501 The Windows log is here: http://pastebin.freeswitch.org/20500 As usual, everything is working just fine on Linux. As soon as it touches Microsoft, it breaks. On Linux, setting "total-modems" to 2 produced /dev/FS0 and /dev/FS1. On Windows, I don't see any additional COM ports. -- Steve
On 01/25/2013 09:23 AM, Steven Schoch wrote:
On Wed, Jan 23, 2013 at 9:19 AM, Michael Collins <msc@freeswitch.org <mailto:msc@freeswitch.org>> wrote:
I find it interesting that the ZRTP engine threw a warning. Do you see any ZRTP messages on the Linux log where the fax actually worked?
No, it just worked, with none of those messages. The Linux log is here: http://pastebin.freeswitch.org/20501 The Windows log is here: http://pastebin.freeswitch.org/20500
As usual, everything is working just fine on Linux. As soon as it touches Microsoft, it breaks.
On Linux, setting "total-modems" to 2 produced /dev/FS0 and /dev/FS1. On Windows, I don't see any additional COM ports. Your previous messages indicate that you are use txfax, so why are you configuring FAX modems?
If you really want FAX modems, because you are trying to work with HylaFAX, Windows FAX, or some other FAX server which talks to FAX modems, the setup is a little different between Linux and Windows. Windows doesn't have a direct equivalent to a Linux PTY, so you need to install com0com, which gives you some back-to-back virtual com ports. The details for that are in the wiki. Steve
On Fri, Jan 25, 2013 at 8:15 AM, Steve Underwood <steveu@coppice.org> wrote:
Your previous messages indicate that you are use txfax, so why are you configuring FAX modems?
I'm using txfax as a test. The goal is to allow a Windows 7 user to send FAXes directly from Word, QuickBooks, etc.
Windows doesn't have a direct equivalent to a Linux PTY, so you need to install com0com, which gives you some back-to-back virtual com ports.
Now I understand. I can do that.
The details for that are in the wiki.
Can you be more specific? http://wiki.freeswitch.org/wiki/Special:Search?search=com0com "Your search - *com0com* - did not match any documents." -- Steve
I'm still struggling with sending FAXes from a Windows 7 system. I believe my requirements are simple: The ability to send a document (like a Word document or a QuickBooks invoice) directly from the Windows system to a FAX number. I don't want to have to use a physical modem and an ATA device. I don't want to run Windows in "Test" mode in order to use an unsigned driver. I don't mind paying some money for a commercial software product. The setup is simple: I have FreeSwitch installed on a Linux machine, on our LAN. Also on the LAN I have several Windows 7 machines and an ATA device (an OBi100). An analog FAX machine is plugged into the ATA. What works: I can send a fax from the FreeSwitch machine using txfax. I can send a fax through the ATA and the FreeSwitch machine using the analog FAX machine. What doesn't: I tried www.t38faxvoip.com through FreeSwitch. It doesn't work. I tried www.t38faxvoip.com directly to Flowroute. That didn't work either. I called the analog fax machine through the ATA and FreeSwitch from www.t38faxvoip.com. I tried www.faxback.com. Same results. The people at www.t38faxvoip.com at least responded to my emails, but said they didn't know what was happening after looking at my Wireshark dump. All of the tests from Windows behaved the same. The called FAX machine answered, but never completed the handshake. The software reported that the call was answered by something other than a FAX machine. Yes, we can live with printing out the document and sticking it in the FAX machine, but it sure would be nice to be able to save some paper. Can't anyone solve my problem? -- Steve
On Fri, Feb 1, 2013 at 1:35 AM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
I'm still struggling with sending FAXes from a Windows 7 system. I believe my requirements are simple: The ability to send a document (like a Word document or a QuickBooks invoice) directly from the Windows system to a FAX number. I don't want to have to use a physical modem and an ATA device. I don't want to run Windows in "Test" mode in order to use an unsigned driver. I don't mind paying some money for a commercial software product.
The setup is simple: I have FreeSwitch installed on a Linux machine, on our LAN. Also on the LAN I have several Windows 7 machines and an ATA device (an OBi100). An analog FAX machine is plugged into the ATA.
What works: I can send a fax from the FreeSwitch machine using txfax. I can send a fax through the ATA and the FreeSwitch machine using the analog FAX machine.
What doesn't: I tried www.t38faxvoip.com through FreeSwitch. It doesn't work. I tried www.t38faxvoip.com directly to Flowroute. That didn't work either. I called the analog fax machine through the ATA and FreeSwitch from www.t38faxvoip.com. I tried www.faxback.com. Same results.
The people at www.t38faxvoip.com at least responded to my emails, but said they didn't know what was happening after looking at my Wireshark dump.
All of the tests from Windows behaved the same. The called FAX machine answered, but never completed the handshake. The software reported that the call was answered by something other than a FAX machine.
Yes, we can live with printing out the document and sticking it in the FAX machine, but it sure would be nice to be able to save some paper. Can't anyone solve my problem?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
As a replacement for the faxback plugin. how about using hylafax+ with t38modem ? http://hylafax.sourceforge.net/ or the commercial "fork" from iFax ? http://www.ifax.com/products/hylafax/fax-over-ip.html
On Fri, Feb 1, 2013 at 4:53 AM, shouldbe q931 <shouldbeq931@gmail.com>wrote:
As a replacement for the faxback plugin.
how about using hylafax+ with t38modem ? http://hylafax.sourceforge.net/
or the commercial "fork" from iFax ? http://www.ifax.com/products/hylafax/fax-over-ip.html
I am happy to report that I have (partial) success! I used HylaFSP (commercial HylaFAX Windows client) to send a FAX to HylaFAX running on the FS machine, connecting to /dev/FS0. The FAX wasn't received 100%, because it didn't go through the T.38 gateway, and the Caller-ID didn't get set, so that's what I'd like to fix next. I already have this rule in the outgoing dialplan: <condition field="${fax_call}" expression="^true$" break="never"> <action application="set" data="fax_enable_t38=true"/> <action application="set" data="execute_on_answer=t38_gateway peer"/> </condition> I set the $fax_call variable (and the $outbound_caller_id_number variable) in the directory entry that's used by the ATA that the analog FAX machine uses. What I want to do now is set the same variables on channels opened by the /dev/FS0 modem. Where should I put these variables? -- Steve
It turns out I was too optimistic. It works *sometimes*. It makes a successful FAX transmission only about 20% of the time. Usually it fails. A typical failure is in http://pastebin.freeswitch.org/20570 This is HylaFax running on the Freeswitch machine, using the SpanDSP modems. I'm calling a FAX number that's an analog PSTN line. Can anybody tell me what I'm doing wrong? -- Steve On Wed, Feb 6, 2013 at 5:58 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
On Fri, Feb 1, 2013 at 4:53 AM, shouldbe q931 <shouldbeq931@gmail.com>wrote:
As a replacement for the faxback plugin.
how about using hylafax+ with t38modem ? http://hylafax.sourceforge.net/
or the commercial "fork" from iFax ? http://www.ifax.com/products/hylafax/fax-over-ip.html
I am happy to report that I have (partial) success! I used HylaFSP (commercial HylaFAX Windows client) to send a FAX to HylaFAX running on the FS machine, connecting to /dev/FS0.
The FAX wasn't received 100%, because it didn't go through the T.38 gateway, and the Caller-ID didn't get set, so that's what I'd like to fix next.
I already have this rule in the outgoing dialplan:
<condition field="${fax_call}" expression="^true$" break="never"> <action application="set" data="fax_enable_t38=true"/> <action application="set" data="execute_on_answer=t38_gateway peer"/> </condition>
I set the $fax_call variable (and the $outbound_caller_id_number variable) in the directory entry that's used by the ATA that the analog FAX machine uses.
What I want to do now is set the same variables on channels opened by the /dev/FS0 modem. Where should I put these variables?
-- Steve
On Mon, Feb 11, 2013 at 3:46 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
It turns out I was too optimistic. It works *sometimes*. It makes a successful FAX transmission only about 20% of the time. Usually it fails. A typical failure is in http://pastebin.freeswitch.org/20570
This is HylaFax running on the Freeswitch machine, using the SpanDSP modems. I'm calling a FAX number that's an analog PSTN line. Can anybody tell me what I'm doing wrong?
Wanting to use faxes? ;) Sorry, as a fax hater I couldn't resist. Question: do you have the capture of a successful call? Can you get pcaps/siptrace of failed vs. successful and open them in Wireshark and do a comparison? I didn't see anything in the FS console log that suggested what the error might be, although if you compare that to a working fax then maybe that will yield a clue as to where to look next. Same w/ the SIP trace. -MC
-- Steve
On Wed, Feb 6, 2013 at 5:58 PM, Steven Schoch < schoch+freeswitch.org@xwin32.com> wrote:
On Fri, Feb 1, 2013 at 4:53 AM, shouldbe q931 <shouldbeq931@gmail.com>wrote:
As a replacement for the faxback plugin.
how about using hylafax+ with t38modem ? http://hylafax.sourceforge.net/
or the commercial "fork" from iFax ? http://www.ifax.com/products/hylafax/fax-over-ip.html
I am happy to report that I have (partial) success! I used HylaFSP (commercial HylaFAX Windows client) to send a FAX to HylaFAX running on the FS machine, connecting to /dev/FS0.
The FAX wasn't received 100%, because it didn't go through the T.38 gateway, and the Caller-ID didn't get set, so that's what I'd like to fix next.
I already have this rule in the outgoing dialplan:
<condition field="${fax_call}" expression="^true$" break="never"> <action application="set" data="fax_enable_t38=true"/> <action application="set" data="execute_on_answer=t38_gateway peer"/> </condition>
I set the $fax_call variable (and the $outbound_caller_id_number variable) in the directory entry that's used by the ATA that the analog FAX machine uses.
What I want to do now is set the same variables on channels opened by the /dev/FS0 modem. Where should I put these variables?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org
Thanks to the helpful people on the conference call, I got HylaFAX working today. It turned out I needed to set not only the "fax_enable_t38" variable, but also the "fax_enable_t38_request" variable. Further input showed that the best solution was to change the context in the spandsp.conf.xml from "default" to "hylafax", and make a separate "hylafax" dialplan that has this: <include> <context name="hylafax"> <extension name="FAX" continue="true"> <action application="set" data="fax_enable_t38=true"/> <action application="set" data="fax_enable_t38_request=true"/> <action application="t38_gateway"/> </extension> ...then the normal dialing rules. But as usual, I still have problems. :-( Now I can't get the old analog FAX machine to successfully send FAXes. I have it plugged into a cheap ATA, the OBi<http://www.obihai.com/what-is.html>. It seemed to be working at one time, but that may have been a fluke. On calls through it, I have fax_enable_t38 and fax_enable_t38_request set, and I also set "execute_on_answer=t38_gateway peer" before the call is bridged to the gateway. Should I be using something else? -- Steve
Not too sure you need t38_gateway on this call flow. I'll have to double check that. On Feb 15, 2013, at 7:51 PM, Steven Schoch wrote:
<action application="t38_gateway"/>
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire http://freeswitchcookbook.com http://freeswitchbook.com T: +1.213.286.0410 | F: +1.213.286.0401 | M: +1.918.424.WEST iNUM: +883 5100 1286 0410
On Sun, Apr 7, 2013 at 6:41 PM, Brian West <brian@freeswitch.org> wrote:
Not too sure you need t38_gateway on this call flow.
I was under the impression that the /dev/FS FAX pseudo-modems did not output T.38, but just a regular audio (G.711) stream. Do I not understand that correctly? -- Steve
I'm still having problems. Is there something I've overlooked? I'm using HylaFAX talking to FreeSWITCH through a mod_spandsp modem, connected to the gateway Flowroute, sending to a FAX number hosted by eFax.com. HylaFAX reports "no carrier". Here is the log of the call, with SIP tracing (the IP address of my PBX redacted): http://pastebin.freeswitch.org/20769 -- Steve
Sorry, false alarm. The FAX was actually received successfully. -- Steve
participants (8)
-
Brian West
-
Dave R. Kompel
-
João Mesquita
-
Michael Collins
-
Seven Du
-
shouldbe q931
-
Steve Underwood
-
Steven Schoch