---------- Forwarded message ----------
From:
EchoLink Support <support@echolink.org>Date: Wed, Sep 3, 2014 at 9:14 AM
Subject: EchoLink Policy Reminder
To:
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)