Below is a list of all the strings that are sent over the Mic Control TCP port connection. All commands are in ascii format follow by \r

• disableMics: This command is sent when the meeting manager logs into the meeting. A use case for this command could be disabling the actual microphone buttons so that requesting to speak and granting access to speak is the only way a members mic can be controlled which all happens in our software.
• enableMics: This command is sent when the meeting manager presses "Meeting Adjournment" signifying the meeting is complete. A use case for this is to then enable the buttons on the microphones again after the meeting is complete so that if you are in a meeting space where other types of regular meetings are held the room can function independently.
• MICSOFF: This command is sent when the "End Vote" button is pressed every time during a meeting. A use case for this is so that if any mics are left on or there are people in the request to speak queue it will reset everything back to off to begin the next topic.
• mic#ON: This command is sent whenever a members mic card was turned on in the software. Thus granting that user permission to speak. The # is replaced by the microphone number being used by that member.
• mic#OFF: This command is sent whenever a members mic card was turned off in the software. Thus removing the ability for the user to speak. The # is replaced by the microphone number being used by that member.

The mic number in the on / off commands is determined by the URL being used by the member. This URL is automatically generated via our software but can also be manually set.

http://{address of solo}/manager/1

(In the above example the microphone number would be 1. So whatever the number is is what microphone it will tell the AV system to control.)