Are COP Commands persisted?

G0JSV · April 16, 2025, 3:50pm

If I run a cop command such as;

/usr/sbin/asterisk -rx 'rpt cmd cop 34'

Which is disable local telemetry. Is this persisted when Asterisk is restarted or if the node is rebooted?

If it is peristed, is there a config file?

The reason for asking, and not just trying, is that I have used various cop commands in connect/disconnect macros but I am now experiencing some strange behaviours. One node appears to want to keyup every 15 mins (0,15,30,45) and it just sends two beeps about 5 seconds apart. I have stripped everything out of Crontab and the Asterisk schedular but I am still getting these internal keyups.

Mike · April 16, 2025, 4:56pm

Yes, I do believe that setting is persistent past a boot.
No editable file I know of but I do think it is stored in a temp file to make it past boot.

Your other is a separate issue.
But you might try capturing log or asterisk in foreground to give some insight.
asterisk -rvvv

N8RAW · April 17, 2025, 12:42pm

Does not look persistent:

github.com/AllStarLink/app_rpt

apps/app_rpt/rpt_config.c

7695c7e9b


      
          	if (!rpt_vars[n].p.telemdefault) {
          		rpt_vars[n].telemmode = 0;
          	} else if (rpt_vars[n].p.telemdefault == 2) {
          		rpt_vars[n].telemmode = 1;
          	} else {
          		rpt_vars[n].telemmode = 0x7fffffff;

telemmode is initialized on reboot based on telemdefault (from the rpt.conf)
And the COP command only changes "stuff" in memory IF dynamic is "allowed":

github.com/AllStarLink/app_rpt

apps/app_rpt/rpt_functions.c

7695c7e9b


      
          	case 34:					/* Local Telem mode Disable */
          		if (myrpt->p.telemdynamic) {
          			myrpt->telemmode = 0;
          			rpt_telemetry(myrpt, COMPLETE, NULL);
          			return DC_COMPLETE;

Mike · April 17, 2025, 4:30pm

Then a setting in startupmacro= would be in order.