
Avaya Media Processing Server Series System Reference Manual
Page 200 # P0602477 Ver: 3.1.11
Command Line Interface
Call simulation functions are performed from the command line of the Diagnostics,
Logging, and Tracing (DLT) process (see dlt on page 53). To connect to DLT, open
a command window on the node you wish to monitor and enter the dlt command.
Connections to TRIP and TCAD are attempted: if these connections are successful,
the dlt prompt appears in the command line. The following commands can be
entered from that point (see the DLT Commands section in the Avaya Media
Processing Server Series Command Reference Manual.).
Command Description
scriptload Downloads a script into TMS memory. Before a script can be
loaded it is parsed to check command formats. If errors are
discovered the script is not loaded. Likewise, if the script passes the
parsing but there is not enough memory available, the script is also
not loaded.
A script load response event is generated immediately upon a
successful load or if an error has occurred during the load process.
In addition, a script handle is returned which must be used in all
subsequent commands referencing the script (see Script Control on
page 196).
scriptload <script_name>
scriptbind Binds a script to a resource set (line). When a script is bound to a
resource set, a mapping is created that is used to deliver the
requested commands to the resources in that set when script
commands are run. A script must be bound to a resource set, or
multiple resource sets (one at a time), before it is run.
A script bind response event is generated immediately upon
completion of the bind or if an error has occurred in the process.
scriptbind <rset_handle> <script_handle>
where <rset_handle> is a line number and <script_handle> is that generated by
the scriptload command.
scriptcntrl Controls execution of scripts in the system. In order to execute a
script must first be loaded and then bound to a resource set. Once
this has transpired it can be started and stopped using this
command. Starting a script that is already running or stopping one
that is already stopped has no effect on it (in either case the status
is returned as okay).
A script control response event is generated immediately upon
applying this command.
scriptcntrl <rset_handle> <script_control>
where <rset_handle> is a line number and <script_control> is a numerical value
of 1 to start a script or 0 to stop it.
scriptlist Provides information about the scripts that have been loaded. This
information includes the name of the scripts, whether they have
been bound and how many instances are so, the lines they are
bound to, and their statuses.
A script list response event is generated immediately upon
collection of all the required data.
Comentários a estes Manuais