strange courtesy tone (or I'm going insane)

I've defined a local node (902) for testing my 902 MHz repeater. It's on
PCIRADIO/1 and it's up and going on the test box.

When I link it over to my node 40821, (224.28) it works come up and the
repeater audio works as intended.
However when using the 40821 node (ie input on 222.68) it has a courtesy tone
added in only when the local node is linked. This tone is 6 fast beeps at
1800 hz (give or take what audacity says).

I can't find it defined in my rpt.conf at all. I've really run out of ideas
here, and think I might be going insane.

I have audio of it up here http://keekles.org/~w9cr/40821%20wierd%20tone.wav

Anyone have any ideas?

···

--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

Bryan,

Not Defined?
I would put a definition in there as it is probably using a default since
nothing has been defined.(guessing from what you said). I have never not
defined them to know for sure.

Just copy the [telemetry] section from one of your other nodes and use it.

...mike/kb8jnm

···

I've defined a local node (902) for testing my 902 MHz repeater. It's on
PCIRADIO/1 and it's up and going on the test box.

When I link it over to my node 40821, (224.28) it works come up and the
repeater audio works as intended.
However when using the 40821 node (ie input on 222.68) it has a courtesy
tone
added in only when the local node is linked. This tone is 6 fast beeps at
1800 hz (give or take what audacity says).

I can't find it defined in my rpt.conf at all. I've really run out of
ideas
here, and think I might be going insane.

I have audio of it up here
http://keekles.org/~w9cr/40821%20wierd%20tone.wav

Anyone have any ideas?

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

Bryan,

Not Defined?
I would put a definition in there as it is probably using a default since
nothing has been defined.(guessing from what you said). I have never not
defined them to know for sure.

Just copy the [telemetry] section from one of your other nodes and use it.

I'm using a common [telemetry] section. I've grep'd out the comments in my
rpt.conf below. I'm stumped :slight_smile:

···

On 2/9/15, 12:06 AM, mike@midnighteng.com wrote:

root@asterisk:/etc/asterisk# grep "^[^#;]" rpt.conf
[40821] ; Change this to your assigned node number
rxchannel = Voter/1234 ; Rx audio/signalling channel
erxgain=-9 ; Echolink receive gain adjustment
etxgain=-3 ; Echolink transmit gain adjustment
functions=functions ; Repeater Function Table
phone_functions=functions ; Repeater Function Table
link_functions=functions ; Link Function Table
telemetry=telemetry ; Telemetry descriptions
wait_times=wait-times ; Wait times
macro=macro
startup_macro=*95329094
context = radio ; dialing context for phone
callerid = "Repeater" <0000000000> ; callerid for phone calls
idrecording = |iW9CR ; id recording or morse string
accountcode=RADIO ; account code (optional)
hangtime=3000 ; squelch tail hang time (in ms) (optional)
althangtime=6000 ; longer squelch tail
totime=180000 ; transmit time-out time (in ms) (optional)
idtime=540000 ; id interval time (in ms) (optional)
politeid=30000 ; time in milliseconds before ID timer
idtalkover=none ; Talkover ID (optional) default is none
unlinkedct=ct4 ; unlinked courtesy tone (optional) default is none
remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links)
linkunkeyct=ct8 ; sent when a transmission received over the link unkeys
nolocallinkct=0 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC).
eannmode=2 ; Default: 1 = Say only node number on echolink connects
beaconing=1 ; Send ID regardless of repeater activity (Required in the UK, but probably illegal in the US)
statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null
statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates
[902]
rxchannel = Zap/1 ; Rx audio/signalling channel
erxgain=-9 ; Echolink receive gain adjustment
etxgain=-3 ; Echolink transmit gain adjustment
duplex=2
functions=functions ; Repeater Function Table
phone_functions=functions ; Repeater Function Table
link_functions=functions ; Link Function Table
telemetry=telemetry ; Telemetry descriptions
wait_times=wait-times ; Wait times
macro=macro
context = radio ; dialing context for phone
callerid = "Repeater" <0000000000> ; callerid for phone calls
idrecording = |iW9CR ; id recording or morse string
accountcode=RADIO ; account code (optional)
hangtime=3000 ; squelch tail hang time (in ms) (optional)
althangtime=6000 ; longer squelch tail
totime=180000 ; transmit time-out time (in ms) (optional)
idtime=540000 ; id interval time (in ms) (optional)
politeid=30000 ; time in milliseconds before ID timer
idtalkover=none ; Talkover ID (optional) default is none
unlinkedct=ct4 ; unlinked courtesy tone (optional) default is none
remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links)
linkunkeyct=ct8 ; sent when a transmission received over the link unkeys
nolocallinkct=1 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC).
eannmode=2 ; Default: 1 = Say only node number on echolink connects
beaconing=1 ; Send ID regardless of repeater activity (Required in the UK, but probably illegal in the US)
statpost_program=/usr/bin/wget,-q,--timeout=15,--tries=1,--output-document=/dev/null
statpost_url=http://stats.allstarlink.org/uhandler.php ; Status updates
[functions]
1=ilink,1
2=ilink,2
3=ilink,3
4=ilink,4
5=macro,1
70=ilink,5
71=ilink,6 ; disconnect all links
72=ilink,7 ; Last Node to Key Up
73=ilink,15
74=ilink,16
75=ilink,8
80=status,1
81=status,2
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
0=autopatchdn ; Autopatch down
989=cop,4
980=status,3
99=cop,6
951=ilink,11 ; Permanent link disconnect
952=ilink,12 ; Permanent link receive
953=ilink,13 ; Permanent link transceive
[telemetry]
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2=|t(660,880,150,2048)
ct3=|t(440,0,150,4096)
ct4=|t(550,0,150,2048)
ct5=|t(660,0,150,2048)
ct6=|t(880,0,150,2048)
ct7=|t(660,440,150,2048)
ct8=|t(700,1100,150,2048)
remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
remotemon=|t(1209,0,50,2048)
cmdmode=|t(900,903,200,2048)
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
patchup=rpt/callproceeding
patchdown=rpt/callterminated
eannmode=2 ; announce callsign only
[morse]
speed=20 ; Approximate speed in WPM
frequency=300 ; Morse Telemetry Frequency
amplitude=4096 ; Morse Telemetry Amplitude
idfrequency=660 ; Morse ID Frequency
idamplitude=1024 ; Morse ID Amplitude
[wait-times]
telemwait=2000 ; Time to wait before sending most telemetry
idwait=500 ; Time to wait before starting ID
unkeywait=2000 ; Time to wait after unkey before sending CT's and link telemetry
calltermwait=2000 ; Time to wait before announcing "call terminated"
[nodes]
40821 = radio@127.0.0.1/40821,NONE ; This must be changed to your node number
902 = radio@127.0.0.1/902,NONE
[memory]
[macro]

--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

Guessing as you are...

I'm a bit tired and need to hit the hay for now.
Will help tomorrow if still a problem you have not solved.

It is a bit baffling but it must be just something being overlooked.

I hope so, but I'm scratching my head at this point.

It appears to be two different tone sets. Look for something that matches
after the 6 beeps and see if it matches a CT. The 6 beeps are not CT's and
must be some error or triggered by some other event. Have you looked in
the logs ?

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

73's

···

On 2/9/15, 1:35 AM, mike@midnighteng.com wrote:
--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

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

···

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

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

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.

jum and i wrote an nprm to establish a single freq on non interference basis, League lobbied against it, fcc shot it down

simple answer.

···


Bryan

Sent from my iPhone 5…No electrons were harmed in the sending of this message.

On Feb 10, 2015, at 09:37, Tim Sawyer tim.sawyer@mac.com wrote:

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.

:frowning:

I just can't stand the politics of this stuff some times.

···

On 2/10/15 9:47 AM, Bryan D. Boyle wrote:

jum and i wrote an nprm to establish a single freq on non interference basis,
League lobbied against it, fcc shot it down

--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net

NIH syndrome. (Not Invented Here)

Poly: ‘many’

Tics: ‘blood sucking insects’ (work with me, ok?)

Drove me out of the hobby in the late 80s. Pretty much has done the same now.

An object lesson that if the League cabal doesn’t think it furthers their aims (which may or may not be the same as an amateur operator), no matter how good the idea may be, they will marshal their not inconsiderable lobbying forces to roadblock or sandbag you.

···


Bryan

Sent from my iPhone 5…No electrons were harmed in the sending of this message.

On Feb 10, 2015, at 09:55, Bryan Fields Bryan@bryanfields.net wrote:

On 2/10/15 9:47 AM, Bryan D. Boyle wrote:

jum and i wrote an nprm to establish a single freq on non interference basis,
League lobbied against it, fcc shot it down

:frowning:

I just can’t stand the politics of this stuff some times.

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.