Successful faxing with spandsp / T38 and stats
Hello everyone, I have been working on faxing for awhile now and figure I would post back with some results and method. Much of my method I have documented on the wiki about faxing but some more details on my method are also below. Faxing overall is a horrific thing and when I first looked into VOIP faxing I did not think I would be able to achieve nearly the success rate I have been able to with FreeSWITCH. These stats were collected over 1000 individual faxes and over 4000 pages sent to over 500 unique fax numbers. I would guess a lot of these numbers are geographically clustered around the northwest of the US but I doubt that should matter a whole lot. Up until last week I had but 1 fax that didn't complete (it was an 80+ page fax that failed twice mid-fax before we just emailed it so it probably would have completed with some extra time). In the last week I have had two I have yet to get through (not sure why or if I have finally found fax machines I just can't send to or what have you). I was blown away with the current success rate. I did not collect as detailed stats the entire time I was logging data (probably only 3/4's+ of the total faxes have full detailed stats). With all that said the below numbers should be decently reflective of real world use. First on the method: I try a progressive retry system, I try one method if it fails I wait 60 seconds then try the next. I use two providers, flowroute and t38faxing.com. Flowroute I highly recommend they are a great provider and have worked very well for faxing. T38Faxing.com / EZCALL are quite bad and I highly recommend avoiding (see bottom of email for why). My 8 methods are: T38,ECM / ECM / T38_DISABLED,ECM / T38,SLOW / T38_DISABLED,SLOW / BACKUP,ECM / BACKUP,SLOW / BACKUP,SLOW,T38_DISABLED Slashes delimit the method and commas delimit the flags for that method. Slow=fax_disable_v17, T38=fax_enable_t38_request, T38_DISABLED=fax_enable_t38=false BACKUP=T38Faxing.com (T38faxing.com fails if t38_request is enabled so thats why T38 is not used with them). If the line is busy I don't move to the next method nor if there is a channel error. The methods are tried in order they are not tried randomly. Randomly would make the below stats better but I care about fax through a fast as possible so I try in order of what I thought had the best chance of success. average secs per page: 28.055 average tries until success: 1.33 (not including busy). Method Usage Rates: 75% T38,ECM success rate: 82% avg secs/page: 27.4 13% ECM success rate: 46% avg secs/page: 29.5 7% ECM,T38_DISABLED success rate: 60% avg secs/page: 28.3 2% T38,SLOW success rate: 56% avg secs/page: 45.7 1% SLOW,T38_DISABLED success rate: 57% avg secs/page: 40.6 1% ECM,BACKUP success rate: 57% avg secs/page: 35.8 Failure Reasons: 40% The call dropped prematurely 25% No response after sending a page 11% Invalid response after sending a page 6% Invalid ECM response received from receiver 5% Received no response to DCS or TCF 2% Unexpected message received 2% Timed out waiting for initial communication 2% The HDLC carrier did not stop in a timely manner 1% Received bad response to DCS or training 1% Disconnected after permitted retries 0% Timed out waiting for the first message Hope you enjoy the method and stats, honestly with this rate of success and either a few better backup providers or even a single hard line for faxing over you could run a very respectable faxing service using FS. ~Mitch Providers: As I mention on the wiki certainly one very important thing other than trying various methods is quality providers. Flowroute handled 99% of the faxes above obviously and did a great job. T38Faxing however I cannot recommend avoiding more. I used them as my backup provider after surveying #freeswitch a bit and while I normally try to avoid a brand bash it has just be a horrible experience. They have a very poor backend which would be livable if their support was not equally poor. They frequently don't answer the phone and their support email system has been down for awhile before (emails bounce) along with their control panel for their website. Their entire faxing service wasn't working for over a week when contacted they said they were adjusting their north american routing and it took over a day before it was back up. So overall I would suggest finding a different provider from t38faxing.
Mitch, That is very impressive. Truly, far higher than I thought possible with VOIP. How about sharing your dialplan and hardware (ata brand and model) and configuration that achieves this magic! Are your ATAs NAT'ed and remote from your fs server? Details man Details! :-) I would love a reliable fax solution for my customers. I have about 99% inbound and 80% outbound for one customer and another that we could find no way to limit its transmission speed so we have 0% for it. Thanks, Sean -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Mitch Capper Sent: Tuesday, June 26, 2012 9:02 PM To: FreeSWITCH Users Help Subject: [Freeswitch-users] Successful faxing with spandsp / T38 and stats Hello everyone, I have been working on faxing for awhile now and figure I would post back with some results and method. Much of my method I have documented on the wiki about faxing but some more details on my method are also below. Faxing overall is a horrific thing and when I first looked into VOIP faxing I did not think I would be able to achieve nearly the success rate I have been able to with FreeSWITCH. These stats were collected over 1000 individual faxes and over 4000 pages sent to over 500 unique fax numbers. I would guess a lot of these numbers are geographically clustered around the northwest of the US but I doubt that should matter a whole lot. Up until last week I had but 1 fax that didn't complete (it was an 80+ page fax that failed twice mid-fax before we just emailed it so it probably would have completed with some extra time). In the last week I have had two I have yet to get through (not sure why or if I have finally found fax machines I just can't send to or what have you). I was blown away with the current success rate. I did not collect as detailed stats the entire time I was logging data (probably only 3/4's+ of the total faxes have full detailed stats). With all that said the below numbers should be decently reflective of real world use. First on the method: I try a progressive retry system, I try one method if it fails I wait 60 seconds then try the next. I use two providers, flowroute and t38faxing.com. Flowroute I highly recommend they are a great provider and have worked very well for faxing. T38Faxing.com / EZCALL are quite bad and I highly recommend avoiding (see bottom of email for why). My 8 methods are: T38,ECM / ECM / T38_DISABLED,ECM / T38,SLOW / T38_DISABLED,SLOW / BACKUP,ECM / BACKUP,SLOW / BACKUP,SLOW,T38_DISABLED Slashes delimit the method and commas delimit the flags for that method. Slow=fax_disable_v17, T38=fax_enable_t38_request, T38_DISABLED=fax_enable_t38=false BACKUP=T38Faxing.com (T38faxing.com fails if t38_request is enabled so thats why T38 is not used with them). If the line is busy I don't move to the next method nor if there is a channel error. The methods are tried in order they are not tried randomly. Randomly would make the below stats better but I care about fax through a fast as possible so I try in order of what I thought had the best chance of success. average secs per page: 28.055 average tries until success: 1.33 (not including busy). Method Usage Rates: 75% T38,ECM success rate: 82% avg secs/page: 27.4 13% ECM success rate: 46% avg secs/page: 29.5 7% ECM,T38_DISABLED success rate: 60% avg secs/page: 28.3 2% T38,SLOW success rate: 56% avg secs/page: 45.7 1% SLOW,T38_DISABLED success rate: 57% avg secs/page: 40.6 1% ECM,BACKUP success rate: 57% avg secs/page: 35.8 Failure Reasons: 40% The call dropped prematurely 25% No response after sending a page 11% Invalid response after sending a page 6% Invalid ECM response received from receiver 5% Received no response to DCS or TCF 2% Unexpected message received 2% Timed out waiting for initial communication 2% The HDLC carrier did not stop in a timely manner 1% Received bad response to DCS or training 1% Disconnected after permitted retries 0% Timed out waiting for the first message Hope you enjoy the method and stats, honestly with this rate of success and either a few better backup providers or even a single hard line for faxing over you could run a very respectable faxing service using FS. ~Mitch Providers: As I mention on the wiki certainly one very important thing other than trying various methods is quality providers. Flowroute handled 99% of the faxes above obviously and did a great job. T38Faxing however I cannot recommend avoiding more. I used them as my backup provider after surveying #freeswitch a bit and while I normally try to avoid a brand bash it has just be a horrible experience. They have a very poor backend which would be livable if their support was not equally poor. They frequently don't answer the phone and their support email system has been down for awhile before (emails bounce) along with their control panel for their website. Their entire faxing service wasn't working for over a week when contacted they said they were adjusting their north american routing and it took over a day before it was back up. So overall I would suggest finding a different provider from t38faxing. _________________________________________________________________________ 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 Join Us At ClueCon - Aug 7-9, 2012 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
Thanks for sharing value able information, Will give a try to flowroute I have bad experience with T38faxing too, used gafachi and found them ok for T.38 faxing We have also contributed following open source fax related projects based on plivo / freeswitch *ICTFAX http://www.ictfax.org * Open Source Email to Fax , Fax to Email software *ICTDialer http://www.ictdialer.org * Open Source SMS, Fax and Voice broadcasting solution Regards *Tahir Almas* Managing Partner ICT Innovations http://www.ictinnovations.com Leveraging open source in ICT On Wed, Jun 27, 2012 at 7:50 AM, Sean Devoy <sdevoy@bizfocused.com> wrote:
Mitch,
That is very impressive. Truly, far higher than I thought possible with VOIP. How about sharing your dialplan and hardware (ata brand and model) and configuration that achieves this magic! Are your ATAs NAT'ed and remote from your fs server?
Details man Details! :-) I would love a reliable fax solution for my customers. I have about 99% inbound and 80% outbound for one customer and another that we could find no way to limit its transmission speed so we have 0% for it.
Thanks, Sean
-----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Mitch Capper Sent: Tuesday, June 26, 2012 9:02 PM To: FreeSWITCH Users Help Subject: [Freeswitch-users] Successful faxing with spandsp / T38 and stats
Hello everyone, I have been working on faxing for awhile now and figure I would post back with some results and method. Much of my method I have documented on the wiki about faxing but some more details on my method are also below. Faxing overall is a horrific thing and when I first looked into VOIP faxing I did not think I would be able to achieve nearly the success rate I have been able to with FreeSWITCH.
These stats were collected over 1000 individual faxes and over 4000 pages sent to over 500 unique fax numbers. I would guess a lot of these numbers are geographically clustered around the northwest of the US but I doubt that should matter a whole lot. Up until last week I had but 1 fax that didn't complete (it was an 80+ page fax that failed twice mid-fax before we just emailed it so it probably would have completed with some extra time).
In the last week I have had two I have yet to get through (not sure why or if I have finally found fax machines I just can't send to or what have you). I was blown away with the current success rate. I did not collect as detailed stats the entire time I was logging data (probably only 3/4's+ of the total faxes have full detailed stats). With all that said the below numbers should be decently reflective of real world use.
First on the method:
I try a progressive retry system, I try one method if it fails I wait 60 seconds then try the next. I use two providers, flowroute and t38faxing.com. Flowroute I highly recommend they are a great provider and have worked very well for faxing. T38Faxing.com / EZCALL are quite bad and I highly recommend avoiding (see bottom of email for why).
My 8 methods are: T38,ECM / ECM / T38_DISABLED,ECM / T38,SLOW / T38_DISABLED,SLOW / BACKUP,ECM / BACKUP,SLOW / BACKUP,SLOW,T38_DISABLED
Slashes delimit the method and commas delimit the flags for that method. Slow=fax_disable_v17, T38=fax_enable_t38_request, T38_DISABLED=fax_enable_t38=false BACKUP=T38Faxing.com (T38faxing.com fails if t38_request is enabled so thats why T38 is not used with them).
If the line is busy I don't move to the next method nor if there is a channel error.
The methods are tried in order they are not tried randomly. Randomly would make the below stats better but I care about fax through a fast as possible so I try in order of what I thought had the best chance of success.
average secs per page: 28.055 average tries until success: 1.33 (not including busy).
Method Usage Rates: 75% T38,ECM success rate: 82% avg secs/page: 27.4 13% ECM success rate: 46% avg secs/page: 29.5 7% ECM,T38_DISABLED success rate: 60% avg secs/page: 28.3 2% T38,SLOW success rate: 56% avg secs/page: 45.7 1% SLOW,T38_DISABLED success rate: 57% avg secs/page: 40.6 1% ECM,BACKUP success rate: 57% avg secs/page: 35.8
Failure Reasons: 40% The call dropped prematurely 25% No response after sending a page 11% Invalid response after sending a page 6% Invalid ECM response received from receiver 5% Received no response to DCS or TCF 2% Unexpected message received 2% Timed out waiting for initial communication 2% The HDLC carrier did not stop in a timely manner 1% Received bad response to DCS or training 1% Disconnected after permitted retries 0% Timed out waiting for the first message
Hope you enjoy the method and stats, honestly with this rate of success and either a few better backup providers or even a single hard line for faxing over you could run a very respectable faxing service using FS.
~Mitch
Providers: As I mention on the wiki certainly one very important thing other than trying various methods is quality providers. Flowroute handled 99% of the faxes above obviously and did a great job. T38Faxing however I cannot recommend avoiding more. I used them as my backup provider after surveying #freeswitch a bit and while I normally try to avoid a brand bash it has just be a horrible experience. They have a very poor backend which would be livable if their support was not equally poor. They frequently don't answer the phone and their support email system has been down for awhile before (emails bounce) along with their control panel for their website. Their entire faxing service wasn't working for over a week when contacted they said they were adjusting their north american routing and it took over a day before it was back up. So overall I would suggest finding a different provider from t38faxing.
_________________________________________________________________________ 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
Join Us At ClueCon - Aug 7-9, 2012
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
Join Us At ClueCon - Aug 7-9, 2012
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
I've had nothing but good tests with t38faxing.com but I was mostly doing passthru with an SPA3102, For flowroute you may need to set sip_require_timer=false on some destinations. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire T: +1.918.420.9266 | F: +1.918.420.9267 | M: +1.918.424.WEST iNUM: +883 5100 1420 9266 UK: +44 20 3298 4900 On Jun 26, 2012, at 11:30 PM, tahir almas wrote:
Thanks for sharing value able information, Will give a try to flowroute
I have bad experience with T38faxing too, used gafachi and found them ok for T.38 faxing
We have also contributed following open source fax related projects based on plivo / freeswitch
BKW Thanks for the tip I will add it into the methods tried. Sean between this and the mod_spandsp wiki page I have virtually all of my details public at this point. My three biggest tips would be: 1) Always resize the fax down to the most common resolution and size (well technically I support two resolutions letter and legal) 2) Use quality providers and decent hardware for FS (nothing huge but given the importance of timing you certainly may want to start without using a VM to ensure that is not a factor) 3) Try try again with different methods, while faxing should be more of a negotiation I can't tell you how many fax machines just can't negotiate well. ~Mitch On Wed, Jun 27, 2012 at 6:37 AM, Brian West <brian@freeswitch.org> wrote:
I've had nothing but good tests with t38faxing.com but I was mostly doing passthru with an SPA3102,
For flowroute you may need to set sip_require_timer=false on some destinations.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire T: +1.918.420.9266 | F: +1.918.420.9267 | M: +1.918.424.WEST iNUM: +883 5100 1420 9266 UK: +44 20 3298 4900
On Jun 26, 2012, at 11:30 PM, tahir almas wrote:
Thanks for sharing value able information, Will give a try to flowroute
I have bad experience with T38faxing too, used gafachi and found them ok for T.38 faxing
We have also contributed following open source fax related projects based on plivo / freeswitch
_________________________________________________________________________ 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
Join Us At ClueCon - Aug 7-9, 2012
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
Also as for t38faxing the quality of their routes may be fine, but it was down for a decent period and their CS/support is just the worst I have seen so as long as they are just one of the providers in your pool it may be a good option. ~Mitch On Wed, Jun 27, 2012 at 6:37 AM, Brian West <brian@freeswitch.org> wrote:
I've had nothing but good tests with t38faxing.com but I was mostly doing passthru with an SPA3102,
On 06/27/2012 09:01 AM, Mitch Capper wrote:
Hello everyone, I have been working on faxing for awhile now and figure I would post back with some results and method. Much of my method I have documented on the wiki about faxing but some more details on my method are also below. Faxing overall is a horrific thing and when I first looked into VOIP faxing I did not think I would be able to achieve nearly the success rate I have been able to with FreeSWITCH.
These stats were collected over 1000 individual faxes and over 4000 pages sent to over 500 unique fax numbers. I would guess a lot of these numbers are geographically clustered around the northwest of the US but I doubt that should matter a whole lot. Up until last week I had but 1 fax that didn't complete (it was an 80+ page fax that failed twice mid-fax before we just emailed it so it probably would have completed with some extra time).
In the last week I have had two I have yet to get through (not sure why or if I have finally found fax machines I just can't send to or what have you). I was blown away with the current success rate. I did not collect as detailed stats the entire time I was logging data (probably only 3/4's+ of the total faxes have full detailed stats). With all that said the below numbers should be decently reflective of real world use.
First on the method:
I try a progressive retry system, I try one method if it fails I wait 60 seconds then try the next. I use two providers, flowroute and t38faxing.com. Flowroute I highly recommend they are a great provider and have worked very well for faxing. T38Faxing.com / EZCALL are quite bad and I highly recommend avoiding (see bottom of email for why).
My 8 methods are: T38,ECM / ECM / T38_DISABLED,ECM / T38,SLOW / T38_DISABLED,SLOW / BACKUP,ECM / BACKUP,SLOW / BACKUP,SLOW,T38_DISABLED
Slashes delimit the method and commas delimit the flags for that method. Slow=fax_disable_v17, T38=fax_enable_t38_request, T38_DISABLED=fax_enable_t38=false BACKUP=T38Faxing.com (T38faxing.com fails if t38_request is enabled so thats why T38 is not used with them).
If the line is busy I don't move to the next method nor if there is a channel error.
The methods are tried in order they are not tried randomly. Randomly would make the below stats better but I care about fax through a fast as possible so I try in order of what I thought had the best chance of success.
average secs per page: 28.055 average tries until success: 1.33 (not including busy).
Method Usage Rates: 75% T38,ECM success rate: 82% avg secs/page: 27.4 13% ECM success rate: 46% avg secs/page: 29.5 7% ECM,T38_DISABLED success rate: 60% avg secs/page: 28.3 2% T38,SLOW success rate: 56% avg secs/page: 45.7 1% SLOW,T38_DISABLED success rate: 57% avg secs/page: 40.6 1% ECM,BACKUP success rate: 57% avg secs/page: 35.8 How should I interpret those percentages? Does it mean 75% of call attempts were with T.38 and ECM, and 82% of those attempts were successful? If so, that's somewhat encouraging, as a lot of T.38 boxes have broken ECM support, and quite a lot of operators suppress ECM mode.
Overall, its rather sad. On the PSTN we would get 99.5% success first time as a bare minimum, and then look to improve the results. :-)
Failure Reasons: 40% The call dropped prematurely 25% No response after sending a page 11% Invalid response after sending a page 6% Invalid ECM response received from receiver 5% Received no response to DCS or TCF 2% Unexpected message received 2% Timed out waiting for initial communication 2% The HDLC carrier did not stop in a timely manner 1% Received bad response to DCS or training 1% Disconnected after permitted retries 0% Timed out waiting for the first message
I don't think you can get much from those figures. Its a real mixed bag of results. If there were a dominant pattern it might represent a bug or design weakness I might be able to address. This just suggests poor channels. Steve
Sorry Steve for the confusion so: 75% T38,ECM success rate: 82% does mean that 75% of the tries used the T38,ECM flags and 82% succeed. Whats important to note is that while I turn ECM on frequently it gets disabled as the remote faxing does not support it or the operator suppresses it. I actually had a hard time getting ECM to be enabled to most places. What I show in the flags are the options I pass to FS not necessarily how the fax ends up going. So a T38,ECM flag means I tell FS to use ECM and to invite with T38 but obviously they could turn around and negotiate no T38 and no ECM. Also remember that T38/ECM is the first method tried and with most faxes only taking 1.3 tries there is a good chance the first method would always have a high percent. For the stats to be super useful it would be better if I chose the method at random unfortunately I care more about getting the faxes through faster than providing the perfect FS faxing stats. It is sad that VOIP faxing has such a lower first try success rate, maybe with some tweaks it could get above where I have it now for the first try, but (atleast for my situation) getting to the 99%+ success rate overall for outbound faxing was something I did not initially get the impression was highly likely to achieve. (And sorry these are all Outbound faxing stats I did not include any inbound as those are less interesting) . Finally yes the Failure reasons stats I assume are not super useful but as I had them I figured I would throw them up. Keep in mind the % for each failure reason is not how often is occurs just how often it is the reason a fax fails. The idea being if you are trying to do faxing and seeing percentages hugely different than that you may be doing something else wrong. There certainly could be a better provider for T38 faxing than flowroute, but I was already using them and as they were quite successful in delivering faxes for me I did not do a huge search for other providers. If however anyone does have other recommendations I do want to replace T38faxing as my backup provider. ~Mitch On Wed, Jun 27, 2012 at 7:24 AM, Steve Underwood <steveu@coppice.org> wrote:
I seem to be the only one not following this, so forgive me if this is a stupid question. Is the schema here that you "send a fax" from a fax machine on an ATA but have Freeswitch intercept it with RXFAX and then try to send it with TXFAX using successively different setups until it goes through? Thanks, Sean -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Mitch Capper Sent: Wednesday, June 27, 2012 10:40 AM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Successful faxing with spandsp / T38 and stats Sorry Steve for the confusion so: 75% T38,ECM success rate: 82% does mean that 75% of the tries used the T38,ECM flags and 82% succeed. Whats important to note is that while I turn ECM on frequently it gets disabled as the remote faxing does not support it or the operator suppresses it. I actually had a hard time getting ECM to be enabled to most places. What I show in the flags are the options I pass to FS not necessarily how the fax ends up going. So a T38,ECM flag means I tell FS to use ECM and to invite with T38 but obviously they could turn around and negotiate no T38 and no ECM. Also remember that T38/ECM is the first method tried and with most faxes only taking 1.3 tries there is a good chance the first method would always have a high percent. For the stats to be super useful it would be better if I chose the method at random unfortunately I care more about getting the faxes through faster than providing the perfect FS faxing stats. It is sad that VOIP faxing has such a lower first try success rate, maybe with some tweaks it could get above where I have it now for the first try, but (atleast for my situation) getting to the 99%+ success rate overall for outbound faxing was something I did not initially get the impression was highly likely to achieve. (And sorry these are all Outbound faxing stats I did not include any inbound as those are less interesting) . Finally yes the Failure reasons stats I assume are not super useful but as I had them I figured I would throw them up. Keep in mind the % for each failure reason is not how often is occurs just how often it is the reason a fax fails. The idea being if you are trying to do faxing and seeing percentages hugely different than that you may be doing something else wrong. There certainly could be a better provider for T38 faxing than flowroute, but I was already using them and as they were quite successful in delivering faxes for me I did not do a huge search for other providers. If however anyone does have other recommendations I do want to replace T38faxing as my backup provider. ~Mitch On Wed, Jun 27, 2012 at 7:24 AM, Steve Underwood <steveu@coppice.org> wrote: _________________________________________________________________________ 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 Join Us At ClueCon - Aug 7-9, 2012 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
Sorry this is Freeswitch sending the fax using TXFAX. What you describe is possible and possibly desirable. I did some early testing using an actual fax machine over VOIP but given our situation scan to fax was a much better solution than trying to work harder on getting the actual fax machine to work. By using Freeswitch as the faxing agent it allows for better control of options and retry protocol.s ~Mitch On Wed, Jun 27, 2012 at 8:23 AM, Sean Devoy <sdevoy@bizfocused.com> wrote:
I seem to be the only one not following this, so forgive me if this is a stupid question.
Is the schema here that you "send a fax" from a fax machine on an ATA but have Freeswitch intercept it with RXFAX and then try to send it with TXFAX using successively different setups until it goes through?
Thanks, Sean
participants (5)
-
Brian West
-
Mitch Capper
-
Sean Devoy
-
Steve Underwood
-
tahir almas