You pretty much have it right. There are a couple of ranger nodes on the nodes list. I think there was some effort to create a national Ranger simplex channel. LiTZ on that channel would trigger an alarm to notify those monitoring of an emergency. I don’t know what happened to the project.

On Feb 9, 2015, at 9:34 PM, Bryan Fields <Bryan@bryanfields.net> wrote:

On 2/9/15, 1:39 AM, Bryan Fields wrote:

I've looked at the logs and run it in debug too.  No obvious errors (or any

for that matter).

Guess I could run it under GDB next....

I read the source to app_rpt.c and found that nodes starting with a 9 are

called a ranger node. No idea what this is.  Can anyone elaborate?

#define ISRANGER(name) (name[0] == '9')

/* if has a RANGER node connected to it, use special telemetry for RANGER mode */

              if (haslink)

              {

                      res = telem_lookup(myrpt,mychannel, myrpt->name, "ranger");

                      if(res)

                              ast_log(LOG_WARNING, "telem_lookup:ranger failed on %s\n", mychannel->name);

              }

looks like a ranger node is suppose to listen for a LiTZ and then connect to

another node.  When others are using that other node as along as the ranger

node is connected to it it will send the "ranger" CT which is what I'm hearing.

{"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)"}

Good news is my 1800 hz decode from audacity was correct!

So I'm guessing this is meant to be some kinda half duplex node that links in

for emergency use.  Anyone have any idea on this?  I can't find anything on

the docs site about ranger nodes.

If I make the node in the 1902 the problem goes away, or I could define the

"ranger" CT to be nothing.

73's

--

Bryan Fields

727-409-1194 - Voice

727-214-2508 - Fax

http://bryanfields.net

_______________________________________________

App_rpt-users mailing list

App_rpt-users@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@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.