Polycom HDX series Reference Manual page 230

• is status specific code returned by system call engine
cause code
• is
calltype videocall
audio only call with POTS or ISDN voice
The following are examples of notifications that may be returned after
registering to receive them.
Key off of
"notification:"
• notification:callstatus:outgoing:41:::opened::0
• notification:mutestatus:near:near:near:near:muted
• notification:screenchange:systemsetup:systemsetup_a
• notification:vidsourcechange:near:1:Main:people
• notification:linestatus:outgoing:32:0:0:disconnected
• notification:vidsourcechange:near:6:ppcip:content
• notification:vidsourcechange:near:none:none:content
Comments
The
notify callstatus
status notifications. The API client receives call status notifications as a call
progresses.
Registration for status notifications is session-specific. For example,
registering for alerts in a Telnet session does not return alerts in a
simultaneous RS-232 session with the same system.
The command registers the current API session to receive
notify captions
notifications as closed captions are displayed. If closed captions are dropped
for some reason, no notification is received. This command is typically used
for capturing captions being displayed for archival purpose.
Duplicate registrations produce another success response. The notify setting
remains in effect, even if you restart the system or update the software with
system settings saved.
This command works with all Polycom HDX systems, and VSX systems
running version 8.0 or later.
Command History
Introduced in VSX version 8.0.
See Also
See also the related
nonotify
command on page 4-29.
if the call is a video call or
command registers the current API session for call
command on page 4-164 and
System Commands
if the call is
voiceonly
callinfo
4 - 167