Additional Tips - Poly Studio G62 Integrator Manual

Additional tips

Refer to the following information when using the command-line API:
The system doesn't provide flow control.
●
If you lose an API connection (for example, the system restarts), you must re-establish it.
●
The API processes one command at a time.
●
Poly doesn't recommend sending multiple commands simultaneously without a pause or delay
●
between each.
For commands with a single action and response: A delay of 200 milliseconds between
●
commands is sufficient. Examples of these commands include the commands for switching
cameras (camera near 1), sending content (vcbutton play), and checking the status of
audio mute (mute near get).
For commands with a single action and a more extensive response: The time it takes to receive
●
the response (and in effect the time between commands) may be longer than 200 milliseconds.
The response length, which can vary, determines the time required to receive the response.
Examples include the commands for retrieving directory information (such as addrbook all)
and system session information (such as whoami).
When developing your application, always allow enough time for a command response before
●
sending another command.
Poly doesn't recommend sending commands while a call is being established.
●
The API provides feedback status in two ways: registrations or polling.
●
Send registration and notification API commands only once. Registrations are written to flash
●
memory and retained when the system restarts.
Poly recommends putting registrations in the initialization or startup of Crestron and AMX
●
systems.
Registrations are recommended over polling since they provide status updates without having to
●
query for changes.
Never poll for registrations.
●
Registrations are specific to the port from which they're registered. If you register for notifications
●
from com port 1, registration will not be sent to com port 2 or telnet port 24.
70 Chapter 14 Command-line API reference for Poly Video Mode