To administer the Pre-configuration of keys feature, you can set the
PHONEKEY parameter in the
46xxsettings.txt file. An administrator can use this parameter to do the following:
-
Place a specific line in a line key location
-
Provide a label for this line
-
Specify if a user can move or relabel this line
This parameter is used to map the feature, application, line and auto-dial keys available on the Phone screen. All the PHONEKEY values and keywords are case-insensitive except values set in Label.
For the full list of PHONEKEY parameter values and examples of their syntax, refer to their description in Appendix.
The PHONEKEY parameter should be set in the following format without any intervening spaces before and after the equal sign (“=”):SET PHONEKEY "Key=[n1];Type=[Feature|Application|Line|Autodial];Name=[name];attr1=[value];attr2=[value];Label=[label][;Forced]"
where:
-
[n1] corresponds to the number of the phone key to be configured. The allowed values are positive integers from 1 to 96.
-
[Feature|Application|Line|Autodial] corresponds to the functionality to be assigned to a key. The allowed values are: feature, application , line, or autodial.
Note:
In the Avaya Aura® environment, use Avaya Aura® System Manager to pre-configure all line and custom keys, including call appearances, features, and automatic dials. Do not use the PHONEKEY parameter to configure line or custom keys.
-
[name], depending on the functionality entered in Type, it can be either of the following:
-
the feature name that you can access by pressing the customized phone key, e.g., callfwd (Call Forward), team (Team button), etc.
-
the application name, for example, lock, logout, screensaver, etc.
-
the type of the phone line accessed. The allowed values are: primary andbca (Bridged Call Appearance).
-
autodialing of a defined phone extension.
-
[label] is the key label that is displayed on the Phone screen. This setting is optional and case-sensitive.
You can configure Label through the 46xxsettings.txt file and the Web Interface in the Key Configuration tab.
-
Forced determines whether the user can move, delete, or relabel a key. This setting is recommended in the Avaya Aura® environment.
There are several main scenarios for the Forced and Non-forced settings:
-
If Forced is set and the key location is empty, the key definition is applied.
-
If Forced is set for an occupied key location, it overrides the existing key and moves it to a different location.
-
If Forced is not set and the location is empty, the new definition is applied.
-
If Forced is not set and the location is already occupied, the closest empty location is selected.
-
If Forced is set and you configure Favorites using PHONEKEY, and the designated location is occupied by another line key, the new key definition overrides the existing key. The existing key is moved it to a nearest empty location if one is available. If no empty location is available, the new definition overrides the existing key.
-
If Forced is not set and you configure Favorites using PHONEKEY, and the designated location is occupied by another line key, the new key definition is placed at a nearest empty location. If no empty location is available, the new definition overrides the existing key.
-
If you configure Favorites in Forced or Non-forced mode and add a new Favorites entity using PHONEKEY, the existing application or contact which occupies the designated location is replaced only if the new definition is not an application or a contact.
-
If Non-forced or Forced is set and you configure a linekey using the 46xxsettings.txt file, you cannot delete it using the web interface, but you can move it.
