[App_rpt-users] Echolink : Now hearing four (unwanted) quick bips -> RANGER hidden courtesy

Buddy Brannan buddy at brannan.name
Thu Apr 14 12:40:26 UTC 2016


To be in compliance/play nice with other All Star nodes, make your Echolink node, if you only intend it to be accessed locally, as opposed to being on a public All Star node for anyone to get directly, start with 1. For instance, attach your echolink node to node 199 and define that in your rpt.conf instead of just 99. 

--
Buddy Brannan, KB5ELV - Erie, PA
Phone: 814-860-3194 
Mobile: 814-431-0962
Email: buddy at brannan.name




> On Apr 14, 2016, at 6:36 AM, Toussaint OTTAVI <t.ottavi at bc-109.com> wrote:
> 
> 
> Le 14/04/2016 12:06, Toussaint OTTAVI a écrit :
>> I was wondering if there are some hidden and/or hardcoded CTs. I'll try browse the sourcecode ASAP. 
> 
> I found this "hidden" courtesy in app_rpt.c:
> {"ranger","|t(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,150,0)"}
> This one is not (re-)defined in my default rpt.conf.
> 
> According to the source, this "ranger" courtesy is sent when a "RANGER" node is connected. Also, all "RANGER" node numbers should begin with "9". And my Echolink node number, choosed at random, is... 99 !
> 
> So, I found my answer ;-)
> 
> But, what on earth is a "RANGER" node ???
> 
> --
> Then, I'll try to :
> - rename my Echolink node number to something else not starting with "9"
> - redefine the "ranger" ct in rpt.conf. That would allow a "special" ct when the Echolink node is connected (which is an interesting behavior)
> _______________________________________________
> 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. 




More information about the App_rpt-users mailing list