Agilent Technologies A.18.00 User Manual
432
S:\agilent\8920\8920b\PRGGUIDE\BOOK\CHAPTERS\callproc.fb
Chapter 8, Programming the Call Processing Subsystem
Using the Call Processing Subsystem’s Remote User Interface
Command Syntax
. Refer to the “Programming the
(screen name) Screen” sections in this chapter for detailed information on using
the Call Processing Subsystem programming commands for each screen.
the Call Processing Subsystem programming commands for each screen.
CAUTION:
The *OPC, *OPC? and *WAI commands should not be used for determining if a Call
Processing Subsystem state command has completed successfully. Call Processing
Subsystem states do not complete, a state is either active or not active. Using the *OPC,
*OPC? or *WAI commands with a Call Processing Subsystem state command results in a
deadlock condition. Refer to the *OPC, *OPC? and *WAI commands in section
Subsystem states do not complete, a state is either active or not active. Using the *OPC,
*OPC? or *WAI commands with a Call Processing Subsystem state command results in a
deadlock condition. Refer to the *OPC, *OPC? and *WAI commands in section
for descriptions of the deadlock conditions.
The *OPC, *OPC? or *WAI commands should not be used with any of the following Call
Processing Subsystem commands: :ACTive, :REGister, :PAGE, :HANDoff, :RELease.
Processing Subsystem commands: :ACTive, :REGister, :PAGE, :HANDoff, :RELease.
The Call Processing Subsystem Status Register Group should be used to control
program flow. Refer to
program flow. Refer to
for further information.