Event Entries In The Logs - Polycom SoundStructure C16 Design Manual

To permanently store the enable/disable state of an event, save the configuration file to disk using File Save
or File Save As. When connected online to a SoundStructure system, the File Save or File Save as forces
the settings in the device to be written to the flash memory of the device.
Enabling Events

Event Entries In The Logs

The SoundStructure device logs record which events executed and the resulting command
acknowledgments there were generated. An example log file is shown below where the events that
executed are highlighted. If in doubt whether events are executing, check the logs within a SoundStructure
system.
Oct 10 23:05:18 gcp: cmd: [1:6:172.25.240.31] set mute "Table Mic" 1
Oct 10 23:05:18 gcp: sts: event "Table Mic LED Event" triggered
Oct 10 23:05:18 gcp: ack: [all] val digital_gpio_state "Table Mic LED" 0
Oct 10 23:05:18 gcp: sts: event "Table Mic Mute Event" triggered
Oct 10 23:05:18 gcp: sts: event "CLink to Mics Mute" triggered
Oct 10 23:05:18 gcp: ack: [all] val mute "Lectern Mic" 1
Oct 10 23:05:18 gcp: sts: event "Table Mic A Mute Event" triggered
Oct 10 23:05:18 gcp: ack: [all] val mute "Table Mic A" 1
Oct 10 23:05:18 gcp: sts: event "Table Mic B Mute Event" triggered
Oct 10 23:05:18 gcp: ack: [all] val mute "Table Mic B" 1
Oct 10 23:05:18 gcp: sts: event "Table Mic C Mute Event" triggered
Oct 10 23:05:18 gcp: ack: [all] val mute "Table Mic C" 1
Oct 10 23:05:18 gcp: ack: [all] val clink_mute 1 1
Oct 10 23:05:18 gcp: ack: [all] val mute "Table Mic" 1
Polycom, Inc. 237