Hi,

Playing the sound is a part in DataMiner Cube (client side) which gets activated when a new alarm enters (or changes severity). A QAction is running from server side and has no direct access to this part in client side.

A potential way to still get an audible alert is to create a separate alarm tab where the audible alert is configured on. From the QAction, it will then set a parameter to a (discreet value) "Play Alert", which this is then monitored with an alarm template and this alarm is present in the alarm tab. This way when the QAction sets the value, the alarm is raised, which is present in the alarm tab, and as a consequence the sound will be played. Of course logic will need to be implemented to reset the value again to allow the sound to be played again in the future (e.g. correlation rule that goes of after x time, or a timer in the protocol.xml logic, or other logic... like when the QAction needs to set "Play Alert" that it first sets "Clear" and directly after that "Play Alert" to force a new alarm being generated)

The downside is that there needs to be an alarm created, but I don't see an alternative at this moment to prevent this.

Regards,