Specifications

Integrator’s Reference Manual for Polycom HDX Systems
4–4 Polycom, Inc.
may receive multiple API registration responses if you are registered for
multiple notifications that are affected by the API command you are currently
sending.
For example, after your system has already been registered to receive camera
notifications (the notify vidsourcechanges API command enables these
notifications), the following responses are returned when you change the
camera source using the camera near 1 API command:
• camera near 1 <CR>API command
returns
camera near 1<LF><CR>API echo
camera near 1<CR><LF>API acknowledgement
notification:vidsourcechange:near:1:Main:people<CR><LF>
API registration response
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 telnetechoeol on
page 4-309 for more details.