Installation guide

AASTRA 6700I SIP TERMINALS FOR MX-ONE
50 26/1531-ANF 901 14 Uen E10 2014-01-22
tory numbers are represented on line keys or softkeys. The EDN number
has basically the same characteristics as the Line1 except for busy;
when there is a call on an EDN line, the line is regarded as busy. When
there is a call on Line1 it is still possible to receive another call on Line2.
The EDN keys are initiated with Manager Provisioning (or via the
MX-ONE command interface). No settings in the aastra.cfg file are
needed.
For more information how to initiate the softkeys as EDN keys, see 11.13
Using Shortcut Keys on page 37.
11.13.8 Softkeys for busy services
To get the softkeys for busy services to show up on the first page, one
parameter in the aastra.cfg file has to be enabled:
! collapsed context user softkey screen:1
The following is valid for 6735i/55i and 6737i/57i: The busy services
call-back and call pickup are shown on softkeys on page 1 when calling
a busy extension. Call waiting and intrusion are shown on softkeys on
page 2, which means that the user has to press More to see these soft
keys.
The following is valid for 6739i: All busy services are shown on the first
page.
See also section 11.2 Settings in the configuration file aastra.cfg on
page 30.
11.13.9 Key Lock / Unlock
It is possible to lock or unlock softkeys, programmable keys and expan-
sion keys. When key locking is enabled, the phone uses the settings
from the configuration files and ignores any previous local configuration.
A user cannot override the configuration of a locked key. Example:
#Save
prgkey5 locked: 1
#Delete
prgkey6 locked:1
When viewing the locked key via the Aastra Web UI, the key is grayed
out (disabled) and cannot be changed.
It is also possible to lock parameters in the configuration files, by starting
the line with an exclamation mark (!). Example:
! collapsed context user softkey screen:1