In rpt.conf I have the following:
telemdefault = 0
telemdynamic=1
I restart asterisk and transmit *70 to my node and I get no telemetry.
I then execute an asterisk command: rpt cmd [my node #] cop 33 0
I again transmit *70 to my node and I DO get telemetry - the cop 33 command works!
I then execute an asterisk command: rpt cmd [my node #] cop 37 0
I connect my node to a local hub.
I connect another local repeater to the same hub
My node transmits telemetry that the repeater has connected to the hub.
cop 37 doesn’t seem to be preventing foreign telemetry from being transmitted on my node. Any suggestions as to what I’m doing wrong?
I should add that the goal is to be able to hear local telemetry so that RF users know if a DTMF link command is successful or not, but to stop all of the telemetry announcements that are coming from the rest of the network. No need to hear if someone else’s node or repeater has connected/disconnected to the hub we are linked to. I’m not sure why the configuration isn’t set this way by default.
Do you mean to try this in addition to the cop,33 and cop,37 commands? Because, won’t telemdefault=0 prevent telemetry from being transmitted from my local node for RF users who are are trying to determine node status and link/unlink? I do want local RF users on my node to be able to hear telemetry response to their DTMF commands. I just don’t want to transmit telemetry coming from other nodes linked over the internet.
Do you want to turn off all telemetry except for local DTMF command responses? Do you want NO connect/disconnect messages from any node, including the local one?
Do you want to turn off all telemetry except for local DTMF command responses?
Yes, I definitely want telemetry responses for local DTMF commands.
Do you want NO connect/disconnect messages from any node, including the local one?
Telemetry for connections/disconnections to my local node would be nice, but not a must.
Telemetry for connections/disconnections for other nodes (foreign telemetry) I definitely want to turn off.
We connect to a hub for a weekly net, and that hub gets a lot of connects/disconnects during the net and all of that telemetry gets announced over our node (repeater) on top of the net traffic. Yes, I know I can turn on holdofftelem and yes, I do have telemduckdb set at -30, and that helps some, but I really don’t want to hear any of that foreign telemetry.
I’m trying to turn off foreign telemetry using cop,37, but it doesn’t seem to have any effect.
So telemdefault = 2 does stop foreign telemetry a couple of minutes after the last command executed on the local node. But why doesn’t cop,37 stop all foreign telemetry? It’s like we are stuck with foreign telemetry always following local telemetry (cop,38) and the cop,37 command doesn’t work at all.
I cannot say, because I have always just set telemdefault = 2. I've never used those COP commands to control foreign telemetry explicitly. To be honest, I don't think I even knew it was possible (or, intended to be possible) to explicitly control foreign telemetry. If so, then what is the point of 2 timed telemetry even being an option? We do we not just have:
; 0 = off | 1 = on
localtelemdefault = 1
foreigntelemdefault = 0
That would be great if we had those configuration options!
I’ve tried some of the other cop command such as cop,4 and that works to produce a test tone. and cop,33 and cop,34 seem to work just fine to enable or disable local telemetry. But it seems like foreign telemetry is stuck in “Foreign link local output path follows local telemetry” (cop,38). I see the same thing on my simplex node at my house and the repeater I’m helping to set up.
I was hoping someone knew a trick to make these work, or even if it was a known bug.
On my node at home I have duplex = 1 and on the repeater I have duplex = 2. Both of these settings work on each of these nodes. telemdefault does change whether telemetry is transmitted or not, and telemdynamic does work a cop,33 works fine telemdefault=0.
