[App_rpt-users] EchoLink Policy Reminder

[REDBUTTON_CTRL]

Correct me if I'm wrong but setting up an Allstar node doesnt set up an 
Echolink node. You must already have an Echolink node to embed into the 
Allstar node.
So you must already have a call sign to get an Echolink node number 
right? And you must also have a call sign to have an Allstar node right?
So how does having an Echolink node embedded into your Allstar node have 
to do with non licensed people getting into Echolink?

I dont have any Echolink nodes so I dont know but just asking. Or is the 
problem the cross linking voip systems thing?

Ahh just love the politics. Next thing you know the Dstar crowd will be 
banning analog bridges.... wait they are!

Allstar does everything Echolink does and IRLP too and more. So that's 
why I dont bother with Echolink. I have IRLP on a separate system but 
its almost never used. Time for the rest of the word to migrate to Allstar.

VA3RQ



On 9/6/2014 8:33 AM, Geoff wrote:
> On 09/03/2014 11:55 AM, Bryan Fields wrote:
>> On 9/3/14, 12:34 PM, Tim Sawyer wrote:
>>> This new (to me) Echolink policy gives me the perfect excuse to turn it off.
>> Agreed.
>>
>> Could be worse, cough IRLP, cough.....
>>
> at least IRLP -sounds- (or could, anyway) a lot better than EchoClunk.
>
> _______________________________________________
> 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.
>