The message is actually "remote already in this mode". It's a telemetry announcement that means whatever you're trying to do, it's already been done. So either you, or someone else in the link path, is trying to command something that is already in the state that it is trying to be commanded to.
The problem I've encountered is that many of my nodes are connected to other nodes, yet those other nodes remain connected to each other without hearing the message. I suspect someone maliciously prevents me from connecting to those nodes because they're not "unfriendly" nodes, and has configured many of them because they appear to be modeled after a person. Is it technically possible to configure the system so that when certain nodes connect, this message plays repeatedly, prompting the "unfriendly" nodes to disconnect?
Hi!
In my experience, this happens when the nodes you connect to have an auto connect script which runs at regular intervals. Since they are already connected that message is played.
To silence the announcement you can turn off telemetry in rpt.conf by adding the following to your node section. This will also silence your node connection and disconnection announcement.
telemdefault = 0
telemdynamic = 0
holdofftelem = 1
I understand that this configuration must be done by the node I connect to, because with my node connected to other nodes, this doesn't happen; it only happens with certain nodes that I assume have this problem by default because they installed the same configuration.
You can make these changes in your rpt.conf and you will not hear these announcements.
I can only speak for myself as the nodes you are trying to connect may have different settings. We have a network of nodes and I have set cron jobs for connection to each other. When I connect my personal node which doesnt have these lines in rpt.conf, I hear the announcement however if I change my personal node's rpt.conf and add these lines then I won't have announcements.
You can go ahead and add these lines in /etc/asterisk/rpt.conf and it should stop these announcements on your node. The particular nodes you are connecting to might have cron jobs like mine.
Agreed, the most likely cause for you hearing these telemetry messages is due to other people not scripting correctly.
They are using improper methods for connection scheduling. They are just putting a connect command into a cronjob rather than using a proper script that checks to see if it's already connected first before it tries to connect again.
Unfortunately the only way to keep from having to listen to these annoying telemetry messages is to use timed telemetry mode, or disable telemetry on your end completely as suggested above.
…or tediously talk to every person that connects to your node and walk them through what they need to do to fix it. If I'm not mistaken, you should be able to watch the asterisk command line as these messages are happening to see the source node(s). Of course, I know everybody that connects on my loose network so it's easy for me to talk to them.
If this is “remote already in this mode’
If you have foreign telemetry enabled on your node, you will hear everything downwind.
I hear this a lot on heavy connected nodes and any one of them may be in error from a live person commanding the node.
It does not necessarily mean it is scripted errors. Not that it isn’t.
Just think if you were using iaxrpt to command your node while listening to make a connection that is already made. Nobody hears you ‘key-up’.
Best bet is to turn foreign telemetry off if you have no good reason to hear it.
Or put up with it. You can’t change others behavior. Less hobby enjoyment for trying.
2 Likes