Did you get the command from Soti Suppot team?  Have you really successfully used the mentioned script on your device(s) to disable outgoing call?  (Frankly speaking, I really doubt your script works fine)   But if so, what changes have been made lately?

What is your device brand and model? What about its Android version and device agent version & build number?

I haven't managed to get it working, i made it with the aid of the script command set.

I'm trying to run t on a Samsung SM-A520F, android 8.0, agent version 13.5.0 build 1327 (ELM)

Please try

  writesecureprofstring  DeviceFeature  DisableBTOutgoingCalls   1

  apply featurecontrol

This should work on most Samsung devices running ELM Android+ device agent.

Unfortunately that still didn't work.

How did you test?  Just send the script command (toggle with argument 0 and 1)  on your hardware from web-console?    Or put the command in the Speed lockdown menu payload script and test it while the device is in motion?

I put the command in the Speed lockdown menu payload script and tested it while the device is in motion.

This is really interesting.    How did you confirm your script got executed in your test while the device is in motion?     What are your settings for speed, engage timer and disengage timer?  What was your device speed during your test, and how long was it above that speed?  Did you run any other sensor app to confirm that the Android system reported the right speed while the device was in motion?  Could it be weak GPS signal that caused the speed reported to be invalid and thus no speed menu/script can be initiated?  Did you check the logs associated with the device to confirm that there was no error due to typos, etc.?

After all, is there any other simpler or more reliable test than simply sending the script command (together with a "log -i ..."  or "showmessagebox ...")  to the device from your web console to first confirm whether the script command works as expected on your hardware?   If not, maybe it's the Android firmware version, app permissions and other issues that stop the command itself from working.   Only when you have confirmed that the script command works before it is meaningful to test its use in the speed lockdown script.