Avaya Menu Administration With WML Applications

Administer the AMADMIN parameter in the 46xxsettings file to point to a URL where the AvayaMenuAdmin.txt file resides. Then specify objects for the Avaya Menu through the Avaya Menu Administration file, AvayaMenuAdmin.txt. Each administered object, up to the maximum of 12, must have valid, non-null parameter data:

• AMTYPExx - One of four choices. 01=URI, 02=the local “Phone Settings” sub-application, 03=local Log Off sub-application, 04= the About Avaya one-X screen.

If the AMTYPE for an associated administered object is “01”, an additional two parameters must have valid, non-null data for the object to be properly administered:

• AMLBLxx - The label displayed to the user for this object, up to 16 UTF-16 characters, shown left-justified unless spaces precede the label value to center the label.
• AMDATAxx - A URI of up to 255 ASCII characters, without spaces.

The xx in these three parameters is a two-digit integer from 01 to 12 inclusive, including a leading zero if applicable. If AMTYPExx is 01, xx must be the same for each of the three parameters for an Avaya Menu entry to be displayed and associated with the administered data. If AMTYPExx is 02, 03 or 04, any AMLBLxx or AMDATAxx data is ignored if provided.

If a given administered object has null or invalid data in any of the required associated parameters, that object is completely ignored. To list an AMTYPE01 entry on the Avaya Menu, all three associated parameters must be non-null with valid data. For example, an AMTYPE of “00” is considered invalid.

Do not administer more than nine URIs. By implication, there is no way to specify a telephone number as a TYPE (unlike the 9610).

In case of duplicate data in the settings file, the last entry is retained. For example, if two consecutive lines in the Avaya Menu Administration file are:

AMLBL01=ABCD
 
AMLBL01=WXYZ
 

then the user sees “WXYZ” as the label for the first WML application. This example assumes the rest of the administration is correct.

If no AvayaMenuAdmin.txt file is available, or if the file does not contain at least one valid type 1 (URI) object, the Release 1.0/1.1 Avaya Menu shown in Figure 8 is presented instead.