Table of Contents
Advertisement
Integrator's Reference Manual for Polycom HDX Systems
● For commands with a single action and a single response: A delay of 200 milliseconds between
commands is usually sufficient. Examples of these commands include the commands for switching
cameras (camera near 1), sending content (vcbutton play), and checking the status of the
audio mute (mute near get).
● For commands with a single action and a more extensive response: The time required to receive the
response, and thus the time between commands, may be longer than 200 milliseconds. The
response length, which can vary in size, determines the time required to receive the response.
Examples of these commands include the commands for retrieving the local address book
(addrbook all), the global address book (gaddrbook all), the list of system settings(such as
displayparams), and system session information (such as whoami).
● When developing your program, always allow enough time for the response to the requested
command to complete before sending another command.
● Do not send any commands while an incoming or outgoing call is being established.
● The API provides feedback status in two ways: registrations or polling.
● It is only required that you send registration and notification API commands once, because the
registrations become written into Flash memory and are retained even upon restarting the system.
● Polycom recommends putting registrations in the initialization or startup of Crestron and AMX
systems.
● Registrations are recommended over polling since they will provide status updates without having to
query for changes.
● Never poll for registrations.
● Registrations are specific to the port from which they are registered. If you register for notifications
from com port 1, registration will not be sent to com port 2 or Telnet port 24.
Polycom, Inc.
System Commands
112
Advertisement
Table of Contents
