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

[kk6ecm]

Understand. For more history see http://www.arrl.org/news/fcc-denies-petition-seeking-to-designate-nationwide-emergency-calling-frequency

I may be missing something, but don't see a reason RANGER cant be implemented on a node unofficially. It just doesn't accomplish the goal. I like the idea, and wondered what might not have been said to justify the proposed usage. Seems to me the reasoning was sound.

Thanks,
Bob
kk6ecm
73

Sent from iPad


> On Apr 14, 2016, at 9:52 AM, Jim <jimw7ry at gmail.com> wrote:
> 
> Not start a new discussion... But 146.55 is not in the band plan here in the Pacific Northwest.
> 
> We are on 20 KHz channel spacing. 146.52, 146.54, 146.56 etc.
> 
> 
> 
> 
> -----Original Message----- From: Bob Prybyzerski
> Sent: Thursday, April 14, 2016 6:45 AM
> To: Toussaint OTTAVI
> Cc: <app_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] Echolink : Now hearing four (unwanted) quickbips -> RANGER hidden courtesy
> 
> Here is a very old message about what a Ranger node is.
> http://ohnosec.org/pipermail/app_rpt-users/2011-November/003369.html
> 
> I don't know the whole story about them but wanted to inform those interested, what they were about.
> 
> 
> Sent from my iPhone
> Bob Prybyzerski
> 631-960-1051
> W2YMM
> 
>> On Apr 14, 2016, at 8:53 AM, Toussaint OTTAVI <t.ottavi at bc-109.com> wrote:
>> 
>> 
>> Le 14/04/2016 14:40, Buddy Brannan a écrit :
>>> attach your echolink node to node 199 and define that in your rpt.conf instead of just 99
>> 
>> Hi,
>> 
>> Thank you for your comments. Our network will be local only (island-wide, <10 repeaters). It will not be connected to Allstar network for now. I missed the fact "9" was a reserved prefix for "ranger" nodes (even if I have no idea about what "ranger" is).
>> 
>> I'll rename the Echolink node to 199, and I think it will do the job.
>> 
>> 73 de TK1BI
>> 
>> 
>> _______________________________________________
>> 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. 
> _______________________________________________
> 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.