Aastra 6700i Series User manual

Aastra Models 6700i and 9000i
Series SIP IP Phones
SIP 3.2.2 Release Notes
RN-001037-02 REV03 – 06.2011

II RN-001037-02 REV03 – 06.2011
Content
SIP IP Phone Models 6700i and 9000i Series
Phones Release Notes 3.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Release notes topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release content information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Hardware supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Bootloader requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Before you upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Please read before upgrading your phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
New Features in Release 3.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
SIP Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Usability Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Network Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuration Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Model Specific Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
SIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Keep-Alive Feature for Persistent TLS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Custom Ad Hoc Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring Custom Ad Hoc Conference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Shifting of Softkey Positions for Busy States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Local Directory Loose Number Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Background Image on Idle Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Usability Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Content
RN-001037-02 REV03 – 06.2011 III
Filter Out Incoming DTMF Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Send DTMF for Remapping Conference or Redial Key. . . . . . . . . . . . . . . . . . . . . . . 15
Network Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
LLDP-MED Time-out Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Issues Resolved in Release 3.2.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Issues Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Contacting Aastra Telecom Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1RN-001037-02 REV03 - 06.2011
SIP IP Phone Models 6700i and 9000i
Series Phones Release Notes 3.2.2
About this document
This document provides new features for the 6700i Series SIP IP Phones (6730i, 6731i,
6739i, 6753i, 6755i, 6757i, 6757i CT) and the 9000i Series SIP IP Phones (9143i, 9480i,
9480i CT) for release 3.2.2.
For more detailed information about features associated with each phone, and for
information on how to use the phones, see your model-specific SIP IP Phone Installa-
tion Guide and the SIP IP Phone User Guide.
For detailed information about more advanced features, see the Aastra Models 9000i
and 6700i Series SIP IP Phones Administrator Guide and/or the Development Guide XML
API For Aastra SIP Phones Firmware 3.2.2.
Release notes topics
Topics in these release notes include:
•General information
•New Features in Release 3.2.2
•Additional Information
•Issues Resolved in Release 3.2.2
•Contacting Aastra Telecom Support
Note:
This release applies to the phone models mentioned above only.

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes
RN-001037-02 REV03 – 06.2011 2
General information
Release content information
This document provides release content information on the Aastra 9000i and 6700i
Series SIP IP Phone firmware.
Hardware supported
This release of firmware is compatible with the following Aastra IP portfolio products:
Model Release name Release version Release filename Release date
6730i Generic SIP 3.2.2 FC-001319-01-REV05 June 2011
6731i Generic SIP 3.2.2 FC-001318-01-REV05 June 2011
6739i Generic SIP 3.2.2 FC-001317-01-REV05 June 2011
6753i Generic SIP 3.2.2 FC-001321-01-REV05 June 2011
6755i Generic SIP 3.2.2 FC-001322-01-REV05 June 2011
6757i Generic SIP 3.2.2 FC-001323-01-REV05 June 2011
6757i CT Generic SIP 3.2.2 FC-001324-01-REV05 June 2011
9143i Generic SIP 3.2.2 FC-001325-01-REV05 June 2011
9480i Generic SIP 3.2.2 FC-001326-01-REV05 June 2011
9480i CT Generic SIP 3.2.2 FC-001327-01-REV05 June 2011
673xi Models 675xi Models 9xxxi Models
6730i 6753i 9143i
6731i 6755i 9480i
6739i 6757i 9480i CT
6757i CT

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.2.2
3RN-001037-02 REV03 – 06.2011
Bootloader requirements
This release of firmware is compatible with the following Aastra IP portfolio product
bootloader versions:
673xi Models 675xi Models 9xxxi Models
6730i: Bootloader 2.4.0.80 or
higher
6753i: Bootloader 2.0.1.1055 or
higher
9143i: Bootloader 2.2.0.166 or
higher
6731i: Bootloader 2.4.0.80 or
higher
6755i: Bootloader 2.0.1.1055 or
higher
9480i: Bootloader 2.2.0.166 or
higher
6739i: Bootloader 3.0.0.167 or
higher
6757i: Bootloader 2.0.1.1055 or
higher
9480i CT: Bootloader 2.2.0.166 or
higher
6757i CT: Bootloader 2.0.1.1055 or
higher

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes
RN-001037-02 REV03 – 06.2011 4
Before you upgrade
Please read before upgrading your phone
If you have a firmware version on your phone prior to 2.3, please read the following
IMPORTANT information before upgrading the phones:
•LLDP is enabled by default
If LLDP is enabled on your network, the phones may come up with different net-
work settings. For more information about LLDP, see the Aastra Models 9000i and
6700i Series SIP IP Phones Administrator Guide.
•Support for DHCP Options 159 and 160
If the DHCP server supplies Options 159 and 160, the phones will attempt to con-
tact the configuration server given in these options. For more information about
Options 159 and 160, see the Aastra Models 9000i and 6700i Series SIP IP Phones
Administrator Guide.
•HTTPS validation
If you are using HTTPS and the certificates are not valid or are not signed by Veri-
sign, Thawte, or GeoTrust, the phones fail to download configuration files. For more
information about HTTPS validation, see the Aastra Models 9000i and 6700i Series
SIP IP Phones Administrator Guide.
•WatchDog task feature
If the phone detects a failure (for example, a crash), the phone automatically
reboots. For more information about the WatchDog feature, see the Aastra Models
9000i and 6700i Series SIP IP Phones Administrator Guide.
Note:
The following information applies to all IP phones EXCEPT the 6739i.
Note:
If you factory default a phone with Release 2.3 and above software, when the phone
reboots, it attempts to connect to rcs.aastra.com. There is no personal information
transmitted from the phone and the phone continues to boot up as normal.
Warning:
Applicable to IP Phone Models 6730i and 6731i only:
The default negotiation setting for the Ethernet ports on the phones is “auto-nego-
tiation”. If you have changed this default setting to another value (i.e., Half Duplex or
Full Duplex), you MUST set the negotiation value back to the default value of “auto-
negotiation” before upgrading to Release 3.2. Failure to do so may cause the phone
to fail to connect to the network. In addition, downgrade will not be possible.

New Features in Release 3.2.2
5RN-001037-02 REV03 – 06.2011
New Features in Release 3.2.2
This section provides the new features in SIP IP Phone Release 3.2.2. These new fea-
tures apply to all of the Aastra IP Phones, unless specifically stated otherwise.
The following table summarizes each new feature and provides a link to more infor-
mation within this Release Note. Each feature also specifies whether it affects the
Administrator, the User, or the XML Developer.
This table also provides the documentation location of features that have already
been documented in Aastra’s documentation suite. Refer to those documents for
more information about the applicable feature.
Feature Description
Configuration Features
Model Specific Configuration File
(For Administrators)
In addition to the aastra.cfg and <mac>.cfg files, there is now a
model specific configuration file that is requested after the aas-
tra.cfg file is downloaded. The file is called <model>.cfg.
*New for all phones
SIP Features
Keep-Alive Feature for Persistent TLS
Connections
(For Administrators)
Now in 3.2.2, the keep-alive feature has been added for persistent
TLS connections only. Administrators can configure this keep-alive
feature using the new parameter called “sip persistent tls keep alive”.
When this feature is configured, the phone will send keep-alive
pings to the proxy server at configured intervals.
*New for all phones
Custom Ad Hoc Conference
(For Administrators)
Now Administrators can use the “custom adhoc conference” param-
eter to enable the phone to interoperate with Genband Call Man-
ager for ad hoc conferences. This parameter is disabled by default.
*New for all phones
User Interface Features
Shifting of Softkey Positions for Busy
States
(For Administrators)
User programmable softkeys 1 and 2 on the 6755i, 6757i, 6757iCT,
9480i, and 9480iCT phones will now appear on page 1 in position 4
and 5 during the outgoing, ringing, connected, and hold states.
*New for 6757i, 6757i, 57iCT, 9480i, & 9480iCT only
Local Directory Loose Number
Matching
(For Administrators)
Administrators can enter a parameter “directory digits match” to
determine the number of digits (from the incoming call) that the
phone will use to perform a lookup in the local directory to match
the number to a contact.
*New for all phones
Background Image on Idle Screen
(For Administrators)
The 6739i phone can now display a background image that will be
shown on the idle screen only.
*New for 6739i only

New Features in Release 3.2.2
RN-001037-02 REV03 – 06.2011 6
Usability Features
Filter Out Incoming DTMF Events
(For Administrators)
Administrator can now enter a parameter in the configuration files
to suppress incoming DTMF playback. This new parameter called
“suppress incoming dtmf playback” will suppress the playback of
both SIP INFO and RFC2833 incoming DTMF tones.
*New for all phones
Send DTMF for Remapping Confer-
ence or Redial Key
(For Administrators)
Administrator can now enter two parameters to remap the “Conf”
and “Redial” keys to send the stored number as DTMF using the
phone configured DTMF method.
*New for all phones
Network Features
LLDP-MED Time-out Period
(For Administrators)
Currently, Aastra IP Phones have a 5 second time-out for listening to
LLDP-MED responses when the phone is booting up. Now adminis-
trators can configure this time-out interval using the new "lldp
startinterval" parameter.
*New for all phones
Feature Description

Additional Information
7RN-001037-02 REV03 – 06.2011
Additional Information
Model Specific Configuration File
In addition to the aastra.cfg and <mac>.cfg files, there is now a model specific config-
uration file that is requested after the aastra.cfg file is downloaded. The file is called
<model>.cfg, where “model” should be the same string that is used for the model
name (e.g. 6730i.cfg, 6731i.cfg, 6739i.cfg, 6753i.cfg, 6755i.cfg, 6757i.cfg, 6757iCT.cfg,
9143i.cfg, 9480i.cfg, 9480iCT.cfg).
When the phone starts up, it request configuration files in the following order:
1. aastra.cfg
2. <model>.cfg
3. <mac>.cfg
If the same parameter appears in more once in the above configuration files, the last
parameter/value read will be used (i.e., the following precedence rules will apply):
•Settings in the <model>.cfg file can overwrite aastra.cfg settings
•Settings in the <mac>.cfg file can overwrite <model>.cfg settings
The same download protocol and URL is used for the <model>.cfg file.
As with the aastra.cfg and <mac>.cfg, the <model>.cfg will be written to the
server.cfg on the phone. The server.cfg contents will be a concatenation of the aas-
tra.cfg, <model>.cfg, and <mac>.cfg, respectively.
Administrators can also encrypt the <model>.cfg file using an Aastra-supplied
encryption tool called "anacrypt.exe" to create a <model>.tuz file.
Configuration Features
Note:
The <model>.cfg file is only requested if the aastra.cfg file has been downloaded
successfully. If the <model>.cfg file does not exist on the server and/or has timed
out on the download, the phone will proceed to request download of the
<mac>.cfg file.

Additional Information
RN-001037-02 REV03 – 06.2011 8
Keep-Alive Feature for Persistent TLS Connections
Now in 3.2.2, the keep-alive feature has been added for persistent TLS connections
only. Administrators can configure this keep-alive feature using the new parameter
called “sip persistent tls keep alive”. When this feature is configured, the phone will
send keep-alive pings to the proxy server at configured intervals.
The keep-alive feature for persistent TLS connections performs the following func-
tionalities:
1. After a persistent TLS connection is established or re-established, activate the keep-
alive, which will send CRLF to peer periodically.
2. The phone will retry the connection automatically when a persistent TLS connection
is down.
3. When a persistent TLS connection is re-established (primary is up or primary is down
and backup is up), refresh registration of the accounts associated with the connec-
tion.
4. When a persistent TLS connection to primary is down, switch to backup ifconnection
to backup is working.
SIP Features

Additional Information
9RN-001037-02 REV03 – 06.2011
Configuring Persistent TLS Keep-Alive
Use the following parameter to configure the persistent TLS keep-alive feature:
Custom Ad Hoc Conference
Previously, the phone will wait for server response prior to completing the ad hoc and
centralized conference feature. This results in an interoperability issue with certain call
managers, such as Genband. Now the phone no longer waits for server response
before referring the call to the conference host when the "custom adhoc conference"
parameter is enabled.
Configuring Custom Ad Hoc Conference
Use the following parameters to configure the custom ad hoc conference:
Parameter–
sip persistent tls keep alive
Configuration Files aastra.cfg, <mac>.cfg
Description When enabled, the configured value indicates frequency (in seconds)
that phone will send the keep alive messages.
Format Integer
Default Value 0 (disabled)
Range 0-3600
Example sip persistent tls keep alive: 10
Parameter–
custom adhoc conference
Configuration Files aastra.cfg, <mac>.cfg
Description Enables/disables the phone to interoperate with Genband Call
Manager for ad hoc conference.
Format Boolean
Default Value 0
Range 0-1
0 (disable)
1 (enable)
Example custom adhoc conference: 1

Additional Information
RN-001037-02 REV03 – 06.2011 10
Shifting of Softkey Positions for Busy States
Administrators can shift the softkey position for busy states using the “collapsed con-
text user softkey screen” parameter. If this parameter is configured, user program-
mable softkeys 1 and 2 on the 6755i, 6757i, 6757iCT, 9480i, and 9480iCT phones will
appear on page 1 in position 4 and 5 during the following states:
•outgoing
•ringing
•connected
•hold
If there are more than two softkeys, the phone will still show the “More” key and then
show softkey 3 on the next page in position 1.
For Example:
During a call with this parameter disabled (Example 1), softkeys 1 (Park) and 2 (DND)
do not appear on page 1. The user has to press the More key to access them on page
2.
During a call with the “collapsed context user softkey screen” parameter enabled
(Example 2), Park and DND appear on page 1 in position 4 and 5.
User Interface Features
Note:
The phone defined context-sensitive softkeys (including empty/unassigned keys)
will remain in the same location. As a result, some screens may only show 1 addi-
tional softkey (e.g. softkey 1).

Additional Information
11 RN-001037-02 REV03 – 06.2011
Example 1: During a call with the “collapsed context user softkey screen” parameter
disabled (default).
Example 2: During a call with the “collapsed context user softkey screen” parameter
enabled.
Configuring Collapsed Context User Softkey Screen
Use the following parameters to configure the collapsed context user softkey screen:
Parameter–
collapsed context user softkey
screen
Configuration Files aastra.cfg, <mac>.cfg
Description This will display the configured softkey1 and softkey2 on page 1 in
position 4 and 5.
Format Boolean
Default Value 0
Range 0-1
0 (Disabled)
1 (Enabled)
Example collapsed context user softkey screen:1
416-123-4567
Drop
Xfer
More
L1
Conf
John 2001
416-123-4567
Park
MyXML
More
L1
DND
John 2001
James
John
Page 1 Page 2
Page 1 Page 2
416-123-4567
Drop
Xfer
More
L1
Conf
John 2001
Park
DND
416-123-4567
MyXML
James
More
L1
John
John 2001

Additional Information
RN-001037-02 REV03 – 06.2011 12
Local Directory Loose Number Matching
If the incoming calling number does not match exactly to the local directory, the
lookup will fail and the phone will not display the stored directory name. Now, the
phone can be configured to match only the specified number of digits against the
local directory.
Administrators can enter a parameter “directory digits match” to determine the
number of digits (from the incoming call) that the phone will use to perform a lookup
in the local directory to match the number to a contact. The phone will take the last n
digits of the incoming call to perform the lookup.
For example, if a local directory contains the following contact:
555123456 Spain Office,
and the “directory digits match” parameter is configured (directory digits match: 9),
the phone will take the last 9 digits of the incoming number ([phone]) and
match it to the contact in the directory and display the following on the phone:
Spain Office
[phone]
Configuring Local Directory Loose Number Matching
Use the following parameters to configure the local directory loose number matching:
Parameter–
directory digits match
Configuration Files aastra.cfg, <mac>.cfg
Description The phone will take the last n digits of the incoming call to perform
the lookup.
Format Integer
Default Value 0 (No Exact Matching)
Range 0-10
Example directory digits match: 9

Additional Information
13 RN-001037-02 REV03 – 06.2011
Background Image on Idle Screen
Customers can now brand the idle screen of the 6739i with their own company logo
or image. The 6739i phone can now display a background image in the bottom layer
of the idle screen. This image can be set by the new “background image” parameter.
Current text (i.e. screen name, extension, and date) and softkeys on the idle screen are
on top of the background image. The background image can be downloaded from
your configuration server using either tftp, ftp, http, and https protocols.
Idle Screen Image Requirements:
•640 x 480 pixels
•There should be no frame around the image
•24-bit color depth recommended
•Both .png and .jpg files are supported
Note:
The background image should not have white areas where the overlaying white text
is located.
L1 John Smith 401 12 : 45pm
Mon Jan 1
John Smith
401
Home
403
404
405
406
503
Office
BLF
Park
Pickup
402

Additional Information
RN-001037-02 REV03 – 06.2011 14
Configuring Background Image
Use the following parameters to configure the background image:
Parameter–
background image
Configuration Files aastra.cfg, <mac>.cfg
Description Set up background image for idle screen on 6739i phone.
Format String (up to 256 characters)
Default Value NA
Range tftp://server/image.png
ftp://server/image.jpg
http://server/image.png
https://server/image/jpg
Example background image: http://10.30.100.233/pics/image.png

Additional Information
15 RN-001037-02 REV03 – 06.2011
Filter Out Incoming DTMF Events
In Release 3.2.2, an Administrator can now enter a parameter in the configuration files
to suppress incoming DTMF playback. This new parameter called “suppress incom-
ing dtmf playback” will suppress the playback of both SIP INFO and RFC2833 incom-
ing DTMF tones. The locally generated DTMF tones will still be played.
Configuring Suppress Incoming DTMF Playback
Use the following parameters to suppress incoming DTMF playback:
Send DTMF for Remapping Conference or Redial Key
Previously, the “Conf” and “Redial” keys could be mapped to a speed dial to generate
a call to a custom number when the phone was idle. During an active call, pressing
the “Redial” or “Conf” keys would put the current call on hold and then dial the cus-
tom number. Now the “Conf” and “Redial” key remappings have the same behavior as
the “Speed Dial” key when the phone is idle. During an active call the phone will send
the custom number as DTMF using the phone configured DTMF method (inbound vs
out-of-band RFC2833 vs SIP INFO).
This feature can be configured using the new “map redial as dtmf” and “map conf as
dtmf” parameters.
Usability Features
Parameter–
suppress incoming dtmf
playback
Configuration Files aastra.cfg, <mac>.cfg
Description Suppress playback of both SIP INFO and RFC2833 DTMF tones.
Format Boolean
Default Value 0
Range 0-1
0 (Disabled)
1 (Enabled)
Example suppress incoming dtmf playback:1

Additional Information
RN-001037-02 REV03 – 06.2011 16
When a user presses the “Redial” key, the mapped number will be sent out as DTMF
during an active call if the current “map redial key to” parameter is configured to a
number and the “map redial as dtmf” parameter is set to “1”.
When a user presses the “Conf” key, the mapped number will be sent out as DTMF
during an active call if the current “map conf key to” parameter is configured to a
number and “map conf as dtmf” parameter is set to “1”
Configuring for Sending of DTMF with Remapped Redial and Conf Keys
Use the following parameters to configure the remapping of the “Redial” and “Conf”
keys:
Parameter–
map redial as dtmf
Configuration Files aastra.cfg, <mac>.cfg
Description Allows the phone to send the stored number as DTMF using the
phone configured DTMF method when the “Redial” key is pressed.
Format Boolean
Default Value 0
Range 0-1
0 (Disabled)
1 (Enabled)
Example map redial as dtmf:1
Parameter–
map conf as dtmf
Configuration Files aastra.cfg, <mac>.cfg
Description Allows the phone to send the stored number as DTMF using the
phone configured DTMF method when the “Conf” key is pressed.
Format Boolean
Default Value 0
Range 0-1
0 (Disabled)
1 (Enabled)
Example map conf as dtmf: 1

Additional Information
17 RN-001037-02 REV03 – 06.2011
Parameter–
map conf key to
Map Conf Key To
(In Web UI)
Aastra Web UI Basic Settings->Preferences->Key Mapping
Configuration Files aastra.cfg, <mac>.cfg
Description Sets the Conf key as a Speed Dial key if a value is entered for this
parameter. If you leave this parameter blank, the Conf key returns to
its original functionality.
Note: If you configure the Conf key for speed dialing on the 6757i CT
BaseStation, the Conf key on the 6757i CT handset retains its original
functionality. The Conf key on the handset is not configured for
speed dial.
Format Integer
Default Value NA
Range NA
Example map conf key to: 5551267
Parameter–
map redial key to
Map Redial Key To
(In Web UI)
Aastra Web UI Basic Settings ->Preferences->Key Mapping
Configuration Files aastra.cfg, <mac>.cfg
Description Sets the Redial key as a Speed Dial key if a value is entered for this
parameter. If you leave this parameter blank, the Redial key returns to
its original functionality.
Note: If you configure the Redial key for speed dialing on the 6757i
CTBase Station, the Redial key on the 6757i CT handset retains its
original functionality. The Redial key on the handset is not
configured for speed dial.
Format Integer
Default Value NA
Range NA
Example map redial key to: 5551234