Avaya Communication Manager Administrator's Manual page 165

3. If you want this attendant to have its own extension, enter one in the Extension field.
Tip:
If you assign an extension to the console, the class of restriction (COR) and class
Tip:
of service (COS) that you assign on this Console screen override the COR and
COS you assigned on the Console Parameters screen. To avoid unexpected
behavior, you should assign the same COR and same COS on both screens.
If you give your attendants an individual extension, users can call the attendant directly by
dialing the extension.
Individual attendant extensions also allow attendants to use features that an attendant
group cannot use — for example, you can assign them to hunt groups.
4. In the Console Type field, enter night-only.
This indicates how this console is used in your organization—as a principal, day only, night
only, or day/night console. You can have only one night-time console (night only or day/
night) in the system.
5. In the Port field, enter the port address for this console.
6. Type a name to associate with this console in the Name field.
7. In the Direct Trunk Group Select Button Assignments fields, enter trunk access codes
for the trunks you want the attendant to be able to select with just one button.
8. If you are using the Enhanced Selector console, assign the Hundreds Select Buttons
that you want this console to have.
If you want this console to be able to access extensions in the range 3500 to 3999, you
need to assign them 5 Hundreds Select Buttons: 35 for extensions 3500 to 3599, 36, 37,
38, and 39.
9. Assign the Feature Buttons that you want the 302 console to have.
To determine which buttons you can assign to a console, see
Buttons
Tip:
Feature buttons are not numbered top-to-bottom on the attendant console, as
Tip:
you might expect. Button numbers map to physical positions on the console as
shown in Figure
10. Press Enter to save your changes.
52.
Adding an Attendant Console
Attendant Console Feature
Issue 1 June 2005 165