<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>First of all, the Allstar Autopatch subscription is per SERVER, not NODE. All the nodes<br>on any server, by inherent design, share autopatch accessibility. <br><br>There is not so much as a SINGLE manufacturer of an FXO card that will provide<br>sufficient quality, especially in the area of trans-hybrid loss, for radio autopatch<br>(full duplex) use, without hardware echo cancellation, which is going to be a DARNED<br>EXPENSIVE CARD!!!! Nor will any ATA!!! Even current FXO cards with H/W echo cancellation<br>*REALLY* sound CRAPPY when used this way. <br><br>Don't do it. Don't try it. It won't work. That is reality.<br><br>Now, for those of you "poised" to press the reply button and share your "wealth" of<br>advice on how "gee, it works fine for me", I am just going to say, "in this case, just don't".<br>Trust me. I invented this technology (Zapata Technology/Zaptel/DAHDI). I understand why<br>it works, and why (in this case) it can't (in great detail).<br><br>I certainly acknowledge that there have been a number of really good open S/W echo<br>cancelers contributed to the Asterisk project, especially the one that David Rowe wrote.<br>Even it can't "forgive" a poopy hardware FXO implementation (which they ALL are) along<br>with the SUPER DEMANDING (well in excess of normal telecom) needs of a two-way radio<br>full duplex autopatch.<br><br>I dedicated a vast part of my life, to, amongst other things, making reasonable *FOUR WIRE*<br>telecom interfaces available to *EVERYONE ON THE PLANET*. Previous to Zapata/Asterisk, we<br>were all *FORCED* to use 2 wire (standard POTS) for things that *REALLY* required a trunk<br>(4 wire) for proper quality and control. We can now. And its so incredibly inexpensive. It makes<br>me smile!! Take advantage of it.<br><br>Jim WB6NIL<br><br><br><div><hr id="stopSpelling">Date: Mon, 9 Sep 2013 08:20:21 -0700<br>From: harvard5362@yahoo.com<br>To: app_rpt-users@ohnosec.org<br>Subject: [App_rpt-users] autopatch when linked<br><br><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div>Hi</div><div> </div><div>in trying to figure out a good way to implement auto-patch on a linked system.</div><div> </div><div>I keep several repeaters linked full time, some via my existing system with a ALLSTAR node connected to a port on the controller, others via ALLSTAR directly. thus I feel it would be more efficient if 1 patch served all.</div><div> </div><div>Can 1 node share its auto-patch with other nodes or do I need to have a separate patch for each node? Also I would like to use a PBX (not sip) extension if possible. </div><div> </div><div>If it is possible to share one auto-patch between nodes could I place a FXO card in the HUB node computer and share that connection?</div><div> </div><div>please let me apologize if this has been covered but I could not find
it.</div><div> </div><div>thank you for your help.</div><div> </div><div>Chris</div></div><br>_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</div> </div></body>
</html>