Avaya J169 Installing And Administering page 166

Administering your phone
Note:
If you administered the OPSTAT parameter to suppress changes to one or more applications,
the phone backs up and restores data as usual, but ignores data for "suppressed"
applications. This method prevents a user from bypassing your OPSTAT restrictions by editing
the backup file.
During backup file restoration, do not perform any user activity until the phone displays a
Retrieval successful or Retrieval Failed .
When a restore attempt fails, if a retrieved file has no valid data, or if a retrieved file cannot be
successfully stored, the phone displays a Retrieval Failed message until the user takes
another action.
Important considerations during data retrieval are as follows:
• When you create a backup file instead of editing an existing one, ensure to create the file
with UTF-16 LE (little endian) characters, with Byte Order Mark (BOM) for LE of 0xFFFE.
• Backup saves data values using the generic format name=value.
• All identifiers, for example, names, are interpreted in a case-insensitive manner, except
parameter values, Contact names, and numbers.
• Spaces preceding, within, or following a name are treated as part of the name.
• <CR> and <LF> (UTF-16 characters 0x000D and 0x000A, respectively) are interpreted as
line termination characters.
• Blank lines are ignored.
• When an identifier is not recognized or is invalid, the entire line is ignored. Similarly, if an
identifier is valid but the data itself is invalid or incomplete, the line is ignored.
• When an identifier is valid with valid and complete data, but the data is not applicable to the
current state of the phone, the data is retained for possible use later, and is treated as data to
be backed up at the appropriate time.
For example, if button labels for an JBM24 button module unit are present, but no such
module is attached to the deskphone, the button labels are retained.
• When more than one line contains a value for an option, parameter, or Contacts entry, the
last value read is retrieved, to allow new values to overwrite previous values as lines are read
from the backup file. In all other cases, the line order in the backup file has no bearing on
retrieval.
• The existence of invalid data does not constitute a failed retrieval. The success of the
retrieval process requires the phone to get the backup file and successfully restore valid data.
Related links
Administering backup and restore
May 2018
on page 161
Installing and Administering Avaya J169/J179 IP Phone H.323
Comments on this document? infodev@avaya.com
166