<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Same. Healthcare facilities won't let go. But client types form my
observation. Most of our clients have at least one physical fax
device, with some having more than 5 in one office, generally for
business units. And many of those will also have an efax solution
available as well.<br>
<br>
<div class="moz-cite-prefix">On 4/19/2024 12:42 PM, Shawn L via
VoiceOps wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMOTM_Rfs5tQwyZhmGm=wF95tq1tR_Bcbr1TEmuNArxr8cqasg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">More than we'd like to. Medical institutions and
law firms seem to be the two biggest ones. We have one hospital
that has multiple PRIs just devoted to faxing -- thankfully that
is TDM, so in general it just works. Otherwise, for those that
use SIP there doesn't seem to ever be a "just do X, and it'll
work". There's always some trial and error with the individual
site, the MTA / ATA model, the fax machines involved, etc.
<div><br>
</div>
<div>The worst one I have seen was during the height of COVID.
A new testing lab was opened and they could not be convinced
that sending 1500 page faxes was fraught with potential
problems. Regardless if there was an ATA involved or not. In
the end, we declined to provide them service because we knew
nothing good would come of it.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Apr 19, 2024 at
12:14 PM Jawaid Bazyar via VoiceOps <<a
href="mailto:voiceops@voiceops.org" moz-do-not-send="true"
class="moz-txt-link-freetext">voiceops@voiceops.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">What are everyone's thoughts on trying to do
fax this way, versus, an E-Fax solution that supports
receiving as well as sending ?
<div><br>
</div>
<div>How many legit physical fax machines are you all
supporting out there?</div>
<div><br>
</div>
<div>Jawaid</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Apr 19, 2024 at
12:13 PM Mark Wiater via VoiceOps <<a
href="mailto:voiceops@voiceops.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">voiceops@voiceops.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> I can echo, that the ATA matters. But so does the
configuration of the faxing device (14400 Baud and ECM
on), the switches that the calls go through, the
configuation of the network equipment and the quality of
the internet connection, even the cable type connecting
the ATA and the fax device sometimes. <br>
<br>
I have excellent faxing history with Cisco ATA-191's
using G.711 (but not T.38 with the softswitch I use
predominantly) and a client network with well configured
QOS enabled firewalls. <br>
<br>
It's not logical to me, but I've even seen instances
where using a 2 conductor cable from fax to ata improved
communication over a 4 conductor cable.<br>
<br>
Nathan and Ross covered other great points as well.<br>
<br>
Mark<br>
<br>
<div>On 4/18/2024 10:22 PM, KARIM MEKKAOUI via VoiceOps
wrote:<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal">Hi VOIPOPS Community</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Do you know about any fax over
internet solution that works? We tried multiple
ATA and multiple ATA configurations, sometime it
works sometimes not.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Also, do you know about any
eFax solution provider that works good.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks in advance for your
help.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span
style="color:rgb(31,73,125)">KARIM</span></p>
<p class="MsoNormal"><span
style="color:rgb(31,73,125)">MEKTEL INC. </span></p>
<p class="MsoNormal"> </p>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
VoiceOps mailing list
<a href="mailto:VoiceOps@voiceops.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">VoiceOps@voiceops.org</a>
<a href="https://puck.nether.net/mailman/listinfo/voiceops"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">VoiceOps@voiceops.org</a><br>
<a
href="https://puck.nether.net/mailman/listinfo/voiceops"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>