[App_rpt-users] Echolink and app_rpt: Looking for more information on permit=*-*

[Doug Crompton]

Mike,

 I am going to break my own rule and respond here! I don't think you are interpreting there statement correctly...

They say....

"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."

They go on to specifically prohibit connections to Allstar, Wires, and many others is not to be connected to Echolink. Bottom line is they think their validation process is better than ours or others. I say we police it just fine. A non ham popping up would stick out like a sore thumb.

Bottom line they don't want us connected. In other words they want it like IRLP with echolink. You can either connect to a echolink station or an IRLP node, NOT both at the same time.

My assertion still stands, ignore it but on the other hand like any good ham make sure you police the activity on your nodes. There is no way to practically isolate echolink from Allstar unless you somehow disconnect all allstar nodes when an echolink call comes in and this would be crazy to do.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: mike at midnighteng.com
To: App_rpt-users at ohnosec.org
Date: Tue, 11 Nov 2014 21:15:26 -0700
Subject: Re: [App_rpt-users] Echolink and app_rpt: Looking for more information on permit=*-*


Like many times before you, you don't seem to understand their statement.So nobody needs to go off on a tangent again.
You only need to be concerned if you do something like"have a web portal to your system that has no limitation to who uses it" (as in non-hams).

If you do then they have the possibility to use the echolink system through your system and that is what they do not want.
Neither do we with allstar or via radio.I'm sure there are a few bad actors out there somewhere allowing access.just make sure it is not you.

They could use better wording to keep the confusion/fuss down.
As far as permit or deny...permit= a list that only allows calls you place in the list to connect.deny= a list of calls that can not connect.See the drupal site for info.

...mike/kb8jnm


-------- Original Message --------

Subject: [App_rpt-users] Echolink and app_rpt: Looking for more

information on permit=*-*

From: "Bob" <kk6ecm at gmail.com>

Date: Tue, November 11, 2014 10:13 pm

To: <App_rpt-users at ohnosec.org>



             OK... Echolink quality aside, I’m looking for some clarification how app_rpt works with Echolink.   Attempting to understand the statement from Echolink, “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.” It seems that “other VoIP” means non-Echolink nodes; not sure how Allstar can do this.   How does permit=*-* (“prohibit computer-based connections”) work with an incoming Echolink computer based node, or with an app_rpt hosted Echolink node in an Echolink to Echolink configuration. When the user enters *33 to connect, is it actually Echolink nodes connecting, or is there a difference?   I think I get their point they don’t want an Allstar node with Echolink node, to simultaneously connect to another Allstar node that does not support Echolink, but not sure why... still licensed amateurs involved.   I am dismayed with Echolink’s assertion that the use of a copy of a paper license is more official than the FCC recognized ULS site, which it appears Allstarlink.org uses to validate the users license.    Thanks, Bob kk6ecm         _______________________________________________

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. 



_______________________________________________
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/20141112/9d5629f3/attachment.html>