MERLIN LEGEND Communications System Release 6.1
System Programming Guide
555-661-111
Issue 1
August 1998
Programming Basics
Page 1-47Idle States
1
Idle States 1
Some programming procedures can be started only when the entire system, or
some part of it, such as a trunk or an extension, is idle (not in use). Some
procedures require that a trunk or extension be idle only at the instant of
programming. Lengthy procedures require the system, trunk, or extension to
remain idle until programming is completed. These procedures wait for the
system, trunk, or extension to become idle and then prevent the initiation of any
new calls. This condition is called
forced idle.
NOTE:NOTE:NOTE:
If a procedure requires an idle condition, do the programming outside of
normal business hours.
If a procedure requires that the system be idle and the system is busy when you
begin, you see the screen shown in Figure 1–12
.
Figure 1–12. System Busy Screen
The screen changes to the appropriate programming screen when the system is
no longer busy.
6\VWHP%XV\3OV:DLW
'LDO&RGH
OOOO
63VVSS
nnnn
= a previously entered extension
ss/pp
= the slot and port number of the
busy extension
([LW (QWHU