Mitel 6900 - Flexible IP Function keys in MX-ONE Provisioning Manager

MITEL 6900, 6970, 6800, AND 6700 SIP TERMINALS FOR MIVOICE MX-ONE
37 26/1531-ANF 901 14 Uen S 2019-10-18
Figure 16: Mitel 6940
11.13.3 Flexible IP Function keys in MX-ONE Provisioning
Manager
For most telephone models, MX-ONE Provisioning Manager makes keys available for
individual programming based on the assumption that both ip_telephony.conf and the
model specific configuration file has standard definitions. For the 6730, 6731, 6863,
6865, 6867, 6869, 6873, 6920, 6930 and 6940 models, MX-ONE Provisioning Manager
analyzes the actual settings to determine which function keys are available for indi-
vidual programming.
The function keys defined for an Aastra67xxi/Mitel 68xx/69xx terminal depends on two
configuration files:
• the global ip_telephony.conf
• model specific, e.g. 6863i.cfg.
The ip_telephony.conf file is stored in the MX-ONE Service Node and is read by it at
start-up but not by the telephones directly. This file contains telephone model specific
definitions of function keys that shall be pushed to the telephone, e.g. Log on/off and
Diversion keys. Also a key offset is defined per model type which defines an offset
number of the first key that can be programmed in the MX-Service Node.
The model specific configuration file, e.g. 6863i.cfg, is read by the telephones and
contains this model’s default definition of the function keys layout. These files can be
defined and changed in the Configuration File task in MX-ONE Service Node Manager,
see chapter 6.
Example - Make all function keys programmable
In this use case all keys will be freed up for the user to be programmed individually.