User's Manual

The sections in the custom keys file can be in any order. Each section contains parameters
and values. All parameters should contain values, except for the following:
• banner
• screensvrText
• screensvrImage
• backgroundImage
• hotlineURL
If a parameter has no value, its previous value is restored. For parameters which are allowed
blank values, if the parameter is blank then the value is cleared.
The custom keys file supports sections which contain user preferences. This file has the same
format as the prefs.txt file which is stored on the flash of the IP Deskphone. After downloading
the custom keys file, this information is merged with information from the user profile (file
prefs.txt). If the parameter has a new value in the custom keys file, then the old value is
replaced. If any parameter is not provisioned through the custom keys file, the old parameter
with its corresponding value is used. After the merge, the new data is written on the flash to
the prefs.txt file. This information is then used by the profile manager.
Note:
The label for a programmable key can be modified by the IP Deskphone end-user through
the phone UI in the Feature Options > Feature Keys menu. If the end-user enters a blank
label for a key that has a default label defined in the custom keys file, then that default label
overrides the blank label and is applied to the key
The following table describes the sections and keys, and provides examples.
Section name Key Value example Description
[audiocodecs] The priority-ordered list of
codecs
str-0 PCMU The key consists of prefix “str-
“ and the sequence number
0,1…
The value can be any
supported codec.
str-1 G729
[autoanswer]
str-0 3007@mycompan
y.com
The list of allowed addresses
from whom auto-answer
requests should be accepted.
[key] Contains special section(s) for
describing configuration for the
programmable keys.
Features
168 SIP Software for Avaya 1100 Series IP Deskphones-Administration November 2012
Comments? infodev@avaya.com