Did not get that email. We use Echolink for away members to check into our RACES net. It’s a pain in the butt, the huge delays causes doubling with RF stations and cell phone Echolink clients sound like poop. This new (to me) Echolink policy gives me the perfect excuse to turn it off. -- Tim :wq On Sep 3, 2014, at 7:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.