Integrator's Reference Manual for the VSX Series
4 - 182
disconnecting state, or
disconnected
•
speed
is the speed of the call
cause code
is status specific code returned by VSX call engine
•
•
calltype
is
videocall
audio only call with SoundStation VTX 1000, 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
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 VSX systems running version 8.0 or later.
Command History
Introduced in version 8.0.
See Also
See also the related
nonotify
command on page 4-37.
disconnected
when the call is completely
if the call is a video call or
command registers the current API session for call
command on page 4-179 and
voiceonly
if the call is
callinfo
Need help?
Do you have a question about the VSX3000 and is the answer not in the manual?
Questions and answers