<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 01/17/2014 12:41 PM, Jared K. Smith
wrote:<br>
</div>
<blockquote
cite="mid:CA+0bQbF2NAMmBw-w5gqU1AVsN4EJMFV=mXy_YuSBk7XBJqNxxA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jan 17, 2014 at 11:05 AM,
Robert Moskowitz <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:rgm@htt-consult.com"
target="_blank">rgm@htt-consult.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">I was reminded that with
spandsp, you can get a v32modem to function as an fxs
port. Of course this puts the burden for i/o handling on
your cpu. Use to do this lots of years ago, and really
forgot those days.</blockquote>
</div>
<br>
<br>
</div>
<div class="gmail_extra">You *can* do this, however you're not
likely to have great results. Traditionally this was done to
function as an FXO port (connected to the central office), but
this doesn't handle remote disconnect supervision (at least
the American way of doing far-end disconnect supervision), so
it's easy get stuck lines.<br>
</div>
</div>
</blockquote>
<br>
But I am only using it for fxs for my fax. My goal is to totally
drop pstn. The only justification for pstn is fax. 'efax' via
scanning is not an option.<br>
<br>
And if it does not work, and no hardware developer sees the value of
arm pbxs with an fxs port, well there is always the SPA-112.<br>
<br>
</body>
</html>