[App_rpt-users] autopatch when linked

[Bob Brown - WØNQX]

All,

Listen to Him ( JIM ), He Speaks the Truth.

He has been there, done that and got a few Tattoos and T-shirts, maybe had
the Tats removed, or never had them applied.

But at any rate, he knows best here!



Sm0ke.

--
Thanks in Advance

   Bob Brown, WØNQX

   Kansas City Metro Area

   http://drsm0ke.net

   http://byrg.net

   http://sm0kenet.net

   http://kcdstar.byrg.net

Quis custodiet ipsos custodes?




--


On Mon, Sep 9, 2013 at 12:00 PM, Jim Duuuude <telesistant at hotmail.com>wrote:

> First of all, the Allstar Autopatch  subscription is per SERVER, not NODE.
> All the nodes
> on any server, by inherent design, share autopatch accessibility.
>
> There is not so much as a SINGLE manufacturer of an FXO card that will
> provide
> sufficient quality, especially in the area of trans-hybrid loss, for radio
> autopatch
> (full duplex) use, without hardware echo cancellation, which is going to
> be a DARNED
> EXPENSIVE CARD!!!! Nor will any ATA!!! Even current FXO cards with H/W
> echo cancellation
> *REALLY* sound CRAPPY when used this way.
>
> Don't do it. Don't try it. It won't work. That is reality.
>
> Now, for those of you "poised" to press the reply button and share your
> "wealth" of
> advice on how "gee, it works fine for me", I am just going to say, "in
> this case, just don't".
> Trust me. I invented this technology (Zapata Technology/Zaptel/DAHDI). I
> understand why
> it works, and why (in this case) it can't (in great detail).
>
> I certainly acknowledge that there have been a number of really good open
> S/W echo
> cancelers contributed to the Asterisk project, especially the one that
> David Rowe wrote.
> Even it can't "forgive" a poopy hardware FXO implementation (which they
> ALL are) along
> with the SUPER DEMANDING (well in excess of normal telecom) needs of a
> two-way radio
> full duplex autopatch.
>
> I dedicated a vast part of my life, to, amongst other things, making
> reasonable *FOUR WIRE*
> telecom interfaces available to *EVERYONE ON THE PLANET*. Previous to
> Zapata/Asterisk, we
> were all *FORCED* to use 2 wire (standard POTS) for things that *REALLY*
> required a trunk
> (4 wire) for proper quality and control. We can now. And its so incredibly
> inexpensive. It makes
> me smile!! Take advantage of it.
>
> Jim WB6NIL
>
>
> ------------------------------
> Date: Mon, 9 Sep 2013 08:20:21 -0700
> From: harvard5362 at yahoo.com
> To: app_rpt-users at ohnosec.org
> Subject: [App_rpt-users] autopatch when linked
>
>
> Hi
>
> in trying to figure out a good way to implement auto-patch on a linked
> system.
>
> 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.
>
> 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.
>
> 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?
>
> please let me apologize if this has been covered but I could not find it.
>
> thank you for your help.
>
> Chris
>
> _______________________________________________ App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130909/7051a92b/attachment.html>