[App_rpt-users] EchoLink Policy Reminder

[Kirk Just Kirk]

They can close/kill my account anytime. EchoStink sounds horrible most of
the time...constant drivebys from dingalings that connect and disconnect
over and over and say nothing...or connect at 3 in the morning and call CQ
CQ. For 5 minutes.....I am so tired of that shit I could delete it tonight.
 On Nov 11, 2014 2:00 PM, "kk6ecm" <kk6ecm at gmail.com> wrote:

> Can anyone shed light on this Echolink requirement and Allstar? I'm not
> sure what makes us compliant. We have Echolink enabled on our repeater... I
> know of no way a non-ham could link in during an Echolink connection. Is
> there a way of setting app_rpt so an Echolink connection precludes all
> others? Also, Echolink has Apps for the PC, Android, and the iPhone/iPad...
> Their PC app (phones are RF, but not ham) seems to invalidate their rf only
> policy, although they do verify a license before granting a node number.
> What am I missing?
>
> Thanks,
> Bob
> kk6ecm
>
> Sent from iPad
>
>
> ---------- Forwarded message ----------
> From: EchoLink Support <support at 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)
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20141111/a4afc073/attachment.html>