26/1531-ANF 901 14 Uen E10 2014-01-22
43
C
ONFIGURING
THE
P
HONE
11.13.3
Flexible IP Function keys in MP
For most telephone models, Manager Provisioning makes keys avail-
able for individual programming based on the assumption that both
ip_telephony.conf and the model specific configuration file has standard
definitions. For the 6730i and 6731 models, Manager Provisioning
analyzes the actual settings to determine which function keys are avail-
able for individual programming.
The function keys defined for an Aastra67xxi terminal depends on two
configuration files:
•
the global ip_telephony.conf
•
model specific, e.g. 6731i.cfg.
The ip_telephony.conf file is stored in the MX-ONE Telephony Server
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 TS.
The model specific configuration file, e.g. 6731i.cfg, is read by the tele-
phones 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 MTS, 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.
Do as follows
:
1.
Edit
/etc/opt/eri_sn/ip_telephony.conf
in MX-ONE Telephony
Server ,so it looks like the following example :
Figure 9: Configure file
