Script Execution Problems; Sections - Nortel Meridian Meridian 1 Scripting Manual

October 2007

Script execution problems

The following sections describe possible problems with script execution.
ASSIGNED command fails to change the value of a variable
The ASSIGNED command is now the ASSIGN TO command. The ASSIGNED
command cannot run if it used within an OPEN VOICE SESSION; however, it
continues to run in all other instances. Nortel recommends that you use the
ASSIGN TO command in your scripts.
The syntax of the ASSIGN TO command is ASSIGN
You can use call variables only of type Item.
Script does not validate
If the script executes a series of commands but then ignores any of the
subsequent commands, you may not have included both an opening and a
closing marker with comments inserted in the script. Comments in your scripts
must begin with an opening marker (/*) and end with a closing marker (*/). If
you do not include both an opening and closing marker, the script does not
validate.
Callers are caught in an endless loop
When using loops to give recorded announcements (GIVE RAN) to callers
waiting in queue, scriptwriters often forget to include a test to determine if the
call is answered. If queuing fails or if the call is disconnected for some reason,
the caller continues to hear a recorded announcement. However, the call is never
answered.
For information about the GIVE RAN command in SIP-enabled contact centers,
see "SIP Contact Center" on page 673.
You must include a test, such as using the QUEUED or OUT OF SERVICE
intrinsics, inside loops. Use the results of these tests to provide default
treatments to the call to ensure that it is successfully routed.
Scripting Guide for Communication Server 1000/Meridian 1 PBX
Troubleshooting
TO
<value> <variable>.
551