Tim, Thanks for that,

I do stand corrected as to my assumption of the workings of telemetry between nodes.
First the exact link folks need is

http://ohnosec.org/drupal/node/102

To explain the reason of my brain fart, and is interesting data to be pointed out is

telemetry data is passed between the nodes with/as iax data thereby allowing each connected node to discern that data. I was not aware of that.

I'm sorry for having steered anyone incorrectly. But do take the time to read that info.

I'll be stuffing the newly discovered command options in my nodes.

I do think that many times it is important to hear telemetry of nodes you are connected to in TX mode so you and the users of your node know what is going on before a user transmission disrupts other activity. Would not matter if in RX mode (*2xxxxx). Just take the time to think your decisions through on it's implications.

...mike/kb8jnm

-------- Original Message --------
Subject: Re: [App_rpt-users] Telemetry Help
From: Tim Sawyer <tim.sawyer@mac.com>
Date: Sat, January 18, 2014 10:46 am
To: "allstarlink@mcleanzone.com" <allstarlink@mcleanzone.com>
Cc: "mike@midnighteng.com" <mike@midnighteng.com>,
"App_rpt-users@ohnosec.org" <App_rpt-users@ohnosec.org>

That *903 command (cop 35) means that when you issue a link command you hear the telemetry  from your command and a timer starts. I think the timer is a minute or two long. During that time you will here all telemetry just as if you were in *901 (cop 33). Once the timer expires you are in *902 (cop 34) and you won't hear any telemetry. 

This is documented on the ohnosec.org site. Search for telemetry. 

--
Tim
:wq

On Jan 17, 2014, at 9:36 PM, allstarlink@mcleanzone.com wrote:

I think that the tag for *903 isn’t very clear. It should probably read, “Disable telemetry announcements from remote connected nodes.”, or something like that. The way I understood his complaint was hearing telemetry from whatever nodes(s) he was connected to.
 
You are correct. These commands affect only the node you are currently controlling.
 
Most times I have all telemetry enabled as that is the default. The only time I execute a *903 is when I connect to a large linked system and only if the announcements become annoying to me. I rarely use the *902, but sometimes it is nice to disable connections being made locally. A good example for use would be on an RF node that is also used as a hub node.
 
Connect to 29503. We can discuss it. J
 
Thank you,
Fred McLean – w0fcm
832-948-5200
Node 29503
 
From: mike@midnighteng.com [mailto:mike@midnighteng.com]
Sent: Friday, January 17, 2014 10:57 PM
To: App_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Telemetry Help
 
 
Please correct me if I'm not seeing this correctly...
but don't those commands only effect local telemetry (on your node) ?
 
I believe his complaint was hearing the telemetry on a connected node/hub.
 
 
...mike/kb8jnm
 
-------- Original Message --------
Subject: RE: [App_rpt-users] Telemetry Help
From: <allstarlink@mcleanzone.com>
Date: Fri, January 17, 2014 11:16 pm
To: <mike@midnighteng.com>, <App_rpt-users@ohnosec.org>
Cc: <w2ymm1@gmail.com>
Robert,
 
Te stop hearing remote telemetry you just need to disable it.
 
Add these lines to your rpt.conf under the functions stanza.
 
[functions] it may read [functions28183]
901=cop,33              ; Local telemetry output enabled
902=cop,34              ; Local telemetry output disabled
903=cop,35         ; Local telemetry output timed Remote (when anybody connects/disconnects from xxxxx Only)
 
You can also put that into your startup script to stop it from ever happening.
[28183]
startup_macro=*903#
rxchannel = Radio/usb28183       ; Rx audio/ signaling channel
 
If you ever want to re-enable it, just do a *901
 
 
Thank you,
Fred McLean
AllStar 29503
832-948-5200
 
 
 
From: mike@midnighteng.com [mailto:mike@midnighteng.com]
Sent: Friday, January 17, 2014 7:23 PM
To: App_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Telemetry Help
 
 
You have no control of announcements from other nodes you are connected to.
 
If you think about that, others telemetry is important to know if you are going to be connected to them. Otherwise, you could interfere with pending operations.
 
 
...mike/kb8jnm
 
-------- Original Message --------
Subject: [App_rpt-users] Telemetry Help
From: W2YMM <w2ymm1@gmail.com>
Date: Fri, January 17, 2014 5:37 pm
To: App_rpt-users@ohnosec.org
Hello, I wanted to know if there is a way to shut off or limit announcements that I hear on my Allstar node.
When connected to a large hub I very often hear "Remote Already In This Mode" and I'll hear when stations connect and Disconnect from each other, or if a call fails.
I'd like to turn that off, but can't seem figure out where to do it.
I looked at the Telemetry section here    http://ohnosec.org/drupal/node/102
but It doesn't look like anything on my node.. At least in /etc/asterisk/rpt.conf

Any help would be greatly appreciated.
Thanks

Robert Prybyzerski Jr
W2YMM
631-960-1051
http://www.w2ymm.com
Allstar 28183
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users