<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'>Hmmm..<br><br>I have never actually seen this policy before... somewhat disturbing...<br><br>However, practical experience shows that Echolink seems to be perfectly aware of our interconnections<br>and seems to be perfectly content with what we are doing. So, I guess its okay.... ???<br><br>Jim WB6NIL<br><br><div><div id="SkyDrivePlaceholder"></div>> From: petem001@hotmail.com<br>> To: app_rpt-users@ohnosec.org<br>> Date: Thu, 21 Mar 2013 15:59:34 -0400<br>> Subject: Re: [App_rpt-users] Echolink Connectivity Issue<br>> <br>> Well, thats bad.<br>> <br>> But if echolink remove my node from there system It's their Loss,not mine.<br>> <br>> Some would day that I am arrogant. nope, I just dont care for poeple that <br>> wont think more then that..<br>> <br>> the more system on their or other networks that can interact together, the <br>> best for every one.<br>> <br>> <br>> -----Message d'origine----- <br>> From: Pawlowski, Adam<br>> Sent: Thursday, March 21, 2013 3:48 PM<br>> To: app_rpt-users@ohnosec.org<br>> Subject: Re: [App_rpt-users] Echolink Connectivity Issue<br>> <br>> I sent this a while back but it was bounced for the wrong mail address. I <br>> don't see it ever made it to the list.<br>> <br>> This was re: someone being advised that their app_rpt node is not permitted <br>> on the Echolink network.<br>> <br>> > Echolink is a nice service<br>> > that allows hams around the world to keep up pc to pc. And nobody asks<br>> > for any money, nice. But this is very, very out of the norm for them.<br>> ><br>> <br>> I looked this up recently when I started to talk about IRLP and how they <br>> don't want other traffic on their network. Then I looked at their Access <br>> Policy:<br>> <br>> 4. Stations operating in Sysop mode may interconnect EchoLink only with <br>> equipment operating on Amateur frequencies. EchoLink does not permit use of <br>> the system with other services such as GMRS, FRS, or MARS. For security <br>> reasons, it is also not permitted to interconnect EchoLink with other VoIP <br>> systems that support direct access from a computer.<br>> <br>> 10. The "addressing servers" are designed to be accessed by EchoLink <br>> software only. For the sake of system security and stability, any other <br>> access requires the permission of the server administrator. As a matter of <br>> security, in no event should the IP addresses (or Internet hostnames) of <br>> logged-in stations be displayed to anyone who is not a validated, logged-in <br>> user.<br>> <br>> 11. Although every effort will be made to apply these policies universally <br>> and fairly, the EchoLink Support staff reserves the right to withdraw a <br>> station's access privileges at any time, without notice. EchoLink is a <br>> privately owned and operated system that has no connection with, and is not <br>> governed by, any radio licensing authority.<br>> <br>> So, I interpret that as that you are not supposed to connect to with <br>> asterisk at all anyways, if you read that verbosely, via app_rpt or <br>> otherwise. I don't have the history to know if they've made any statement <br>> about what app_rpt is doing, but it seems like it's not permitted via their <br>> policy only they are less vocal about it than the IRLP folks.<br>> <br>> <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br></div> </div></body>
</html>