Table of Contents
Advertisement
Integrator's Reference Manual for Polycom HDX Systems
When your system is registered for notifications, always use the API registration response (<CR><LF>),
which indicates that the command was sent, accepted, and processed. Never use the API echo
(<LF><CR>), which only indicates that you sent an API command but does not indicate whether the API
command you sent was actually processed. For example, you receive an API echo even if you send an
invalid API command. In this case, the API echo responds by echoing the invalid API command that you
attempted to send.
End Of Line (EOL) Characters When Connected to the API Using a LAN
Connection
In software versions prior to 2.5.0.6, the EOL characters for the echo responses on a system connected to
the LAN and using a Telnet session were as follows:
camera near 2 <CR> API command
returns
camera near 2<CR><CR><LF> API echo
camera near 2<CR><LF> API acknowledgement
Starting with software version 2.5.0.6, the response changed to a single <CR>; for example:
camera near 2 <CR> API command
returns
camera near 2<CR><LF> API echo
camera near 2<CR><LF> API acknowledgement
The telnetechoeol command allows you to change the EOL characters of the API echo to the EOL
characters of the serial port echo. See
Commands that Restart the System
Commands that Restart the System with a Prompt
● reboot
Commands that Restart the System without a Prompt
● reboot yes
● reboot now
● resetsystem
Additional Tips
● The Polycom HDX system does not provide flow control. If the connection is lost through restarting
the system or other means, you must re-establish the connection.
● The API processes one command at a time.
● Polycom does not recommend sending multiple commands simultaneously without a pause or delay
between them.
Polycom, Inc.
telnetechoeol
on page 536 for more details.
System Commands
111
Advertisement
Table of Contents
