Moving Among System Programming Screens; About Programming And Idle States - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

System Programming Basics
Moving Among System Programming
Screens
Some general comments regarding moving from one system programming screen to another
follow:
In most cases, you can select Back to exit from a screen without making any changes.
I
Exceptions to this are noted as part of a procedure. When you complete a procedure and
select Back, you usually move up one screen in the menu hierarchy.
Occasionally, when you select Back, you return to the previous screen. In a few cases,
pressing Back brings you back to the System Programming menu, where you can select
another option to program or exit from system programming.
To complete a procedure and save the information you have programmed, select Enter .
I
If you are programming a group of sequentially numbered extensions or trunks, you may
I
optionally select Next . This saves your entry and automatically provides the number of the
next extension or trunk in the sequence, thus saving you several steps. If Next displays on the
screen, you can use it with the current option.
In most cases, you will be at an intermediate step in the procedure you have just completed. At
I
that point, you can select one of the options shown on the screen and continue programming,
or you can select Back again. This usually takes you back to the System Programming menu.
If not, you can continue programming on the current screen or select Back again.

About Programming and Idle States

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 the trunk or
extension be idle only at the instant of programming. Other procedures, which take longer, require
the system, trunk, or extension to be forced 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.
If a procedure requires an idle condition, perform the programming outside of normal
business hours.

Moving Among System Programming Screens

1-4
1
1