<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="ltr">Not providing fax still leaves the local telco with one foot in the door. Also, if you are not careful the one pots line a business gets for faxing is likely to get published as their main number.
</div>
<br>
<br>
<div dir="ltr">-------- Original Message --------</div>
<div dir="ltr">Subject: [VoiceOps] Fax ATAs/devices</div>
<div dir="ltr">From: Carlos Alvarez <caalvarez@gmail.com></div>
<div dir="ltr">Date: Apr 27, 2017, 2:31 PM</div>
<div dir="ltr">To: voiceops@voiceops.org</div>
<div>
<div dir="ltr">Fax is dead. Long live fax.
<div><br>
</div>
<div>We've resisted supporting it, but customers still need it on occasion, and they hate having a separate landline carrier just for a fax line. So I'm wondering what others here use successfully to provide their customers with a "fax line" to a physical
machine. We would only use a handful of them, and only with our customers who have a fully managed service (IE, 2-3ms connection directly to us over MPLS). We run Asterisk and pass T.38 to a few carriers. We currently do fax to e-mail inbound on Asterisk
with no issues. </div>
<div><br>
</div>
<div>Volume is very light, maybe 3-5 per day per customer, so things like the Vitelity FaxEnable don't make economic sense ($25/mo unlimited our cost).</div>
<div><br>
</div>
</div>
</div>
<HR>This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.<BR>
</body>
</html>