Attendant

The feature states that it allows multiple attendant codes but not multiple attendant groups. You can use this feature to administer multiple attendant groups. However, you cannot use this feature to administer multiple attendant groups. You can have only one attendant group unless you have Attendant Partitioning. This feature provides a way to support multiple local centralized answering points (LCAPs). The LCAPs do not use attendant groups.

Attendant Vectoring

Attendant Vectoring, if enabled, takes precedence over any local attendant codes that are administered. The software uses call vectors to process calls to an attendant. Such calls are:

• Local attendant codes

• The attendant code on the Dial Plan Analysis Table screen

• The attendant access code on the Feature Access Code (FAC) screen

Automatic Circuit Assurance (ACA)

The ACA Referral Destination field on the System Features Parameters screen requires that an attendant group exists. This field also requires either:

• The attd administration on the Dial Plan Analysis Table screen, or

• Administration of the attendant access code on the Feature Access Code (FAC) screen

Automatic Wakeup

If a telephone has Automatic Wakeup requests pending when you run the change extension-station command, the system cancels the wakeup requests.

Call Forwarding

Any call forwarding information that is stored with an extension is lost when you use the change extension-station command. If the telephone that you change with the change extension-station command is a forwarded-to telephone, you must manually update the extension that uses the forwarded-to extension. If you do not manually update the extension, the system does not forward calls correctly.

Call Park

This feature does not support common shared extensions to park calls. Since common shared extensions are not assigned to physical telephones, the range of common shared extensions can be shared in all locations.

Crisis Alert

The change extension-station command does not update the Originating Extension field on the Crisis Alert System Parameters screen. You must manually update the Originating Extension field if you change the originating extension field.

Leave Word Calling (LWC)

The Stations with System-wide Retrieval Permission for the Leave Word Calling Parameters field on the System Features Parameters screen requires that an attendant group exists. This field also requires either:

• The attd administration on the Dial Plan Analysis Table screen, or

• Administration of the Attendant Access Code on the Feature Access Code (FAC) screen

Survivable Remote Server (Local Survivable Processor)

If you run the change extension-station command on the controller, but do not also save the translations to the Survivable Remote Server, the two system translations might be unsynchronized.

Use either of these following commands to save the translations to the Survivable Remote Server:

• The save trans lsp command locally saves the translations, and performs a filesync operation to all registered Survivable Remote Servers.

• The save trans lsp n command, where n is the IP address of a specific Survivable Remote Server, locally saves the translations, and performs a filesync operation to the specified Survivable Remote Server.

Night Service

This feature does not support location-based Night Service. Therefore, you might want to restrict calls to attendants who are local to the calling party. The attendant most likely speaks the same language as the caller. At night, instead of putting the entire system into Night Service, you might want an attendant to put only one location into Night Service.

To accomplish this, you can use hunt groups as attendant queues. Each hunt group can be put into Night Service separately, and have its own Night Service destination. You can also administer the Night Service destination by tenant, trunk group, and trunk group number.

Security Violations Notification

The referral destination fields on the Security-Related System Parameters screen requires that an attendant group exists. This field also requires either:

• The attd administration on the Dial Plan Analysis Table screen, or

• Administration of the attendant access code on the Feature Access Code (FAC) screen

  The referral destination fields are:

• SVN Login Violation Notification Enabled

• SVN Remote Access Violation Notification Enabled

• SVN Authorization Code Violation Notification Enabled

Station Hunting

Changing a telephone extension with the change extension-station command maintains the hunting chain.

Survivable Remote EPN/WAN Spare Processor

If you run the change extension-station command in a configuration where a survivable remote processor exists, you must also run the command on the survivable processor. If you do not, the extensions that you changed on the server do not exist on the survivable remote when the remote processor takes control.

Uniform dial plan (UDP)

The change extension-station command does not update extensions that are in the Uniform Dial Plan Table screen. Avaya supports external system management tools that handles changes to the UDP table.