Aastra 9143i Series How to use

Aastra Model
9143i, 9480i, 9480i CT, and
67xxi Series Phones
Aastra 2.6 Release Notes
RN-001029-05 REV 00 – 04.2010

2RN-001029-05 REV 00 – 04.2010
Content
SIP IP Phone Models 9143i, 9480i, 9480i CT,
and 67xxi Series Phones Release Notes 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Release notes topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Release content information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Hardware supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bootloader requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Before you upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Please read before upgrading your phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
New features in release 2.6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuration Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Specifying the Caret (“ ^ “) Character in Configuration Files
to Overwrite Locally Configured Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Redirection and Configuration Server (RCS) Bypass via Option 43 . . . . . . . . . . . 12
DHCP Time Offset (Option 2) Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configuration Server Redundancy via DNS A Records . . . . . . . . . . . . . . . . . . . . . . 15
Configuration and Crash File Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Malaysian Tone Set and Cadences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Call Hold Reminder During Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Call Hold Reminder on Single Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Call Hold Reminder Timer & Call Hold Reminder Frequency Parameters . . . . . 31
Call Waiting Tone Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Per-Account Call Waiting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Successful Transfer Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Errors Messages Display when Incorrect Network Settings . . . . . . . . . . . . . . . . . . 37

Content
RN-001029-05 REV 00 – 04.2010 3
SIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Switching Between Early Media and Local Ringing . . . . . . . . . . . . . . . . . . . . . . . . . 38
Added “Call-Info” Header to 200ok Responses for
Shared Call Appearance (SCA) Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
XML Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Connected Action URI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
New “DialLine” URI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
New “Line” Parameter in the Dial Tag for AastraIPPhoneTextMenu Object. . . 43
AastraIPPhoneInputScreen Object Supports Up to
10 fields in “Normal” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Issues Resolved in Release 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Contacting Aastra Telecom Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4RN-001029-05 REV 00 - 04.2010
SIP IP Phone Models 9143i, 9480i,
9480i CT, and 67xxi Series Phones
Release Notes 2.6
About this document
These Release Notes 2.6* provide new features for the 9143i, 9480i, and 9480i CT SIP IP
Phones and the 67xxi Series SIP IP Phones (6730i, 6731i, 6751i, 6753i, 6755i, 6757i,
6757i CT). It also includes the issues resolved since Release 2.5.3 of the IP Phones.
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 SIP IP Phone Administrator Guide.
Release notes topics
Topics in these release notes include:
•General information
•New features in release 2.6
•Issues Resolved in Release 2.6
•Contacting Aastra Telecom Support
* Release 2.6 of the 67xxi SIP phones is not supported on Model 6739i.

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones
RN-001029-05 REV 00 – 04.2010 5
General information
Release content information
This document provides release content information on the Aastra 9143i, 9480i, and
9480i CT SIP IP Phone firmware and the 67xxi 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 2.6 FC-001240-03-Rev00 April 2010
6731i Generic SIP 2.6 FC-001224-04-Rev00 April 2010
6751i Generic SIP 2.6 FC-001126-06-Rev00 April 2010
6753i Generic SIP 2.6 FC-001086-10-Rev00 April 2010
6755i Generic SIP 2.6 FC-001087-11-Rev00 April 2010
6757i Generic SIP 2.6 FC-001088-10-Rev00 April 2010
6757i CT Generic SIP 2.6 FC-001089-08-Rev00 April 2010
9143i Generic SIP 2.6 FC-001092-06-Rev00 April 2010
9480i Generic SIP 2.6 FC-001097-06-Rev00 April 2010
9480i CT Generic SIP 2.6 FC-001101-06-Rev00 April 2010
•6730i •6757i
•6731i •6757i CT
•6751i •9143i
•6753i •9480i
•6755i •9480i CT

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones
6RN-001029-05 REV 00 – 04.2010
Bootloader requirements
This release of firmware is compatible with the following Aastra IP portfolio product
bootloader versions:
•6730i - Bootloader 2.4.0.80 or higher •6757i - Bootloader 2.0.1.1055 or higher
•6731i - Bootloader 2.4.0.80 or higher •6757i CT - Bootloader 2.0.1.1055 or higher
•6751i - Bootloader 2.0.1.1055 or higher •9143i - Bootloader 2.2.0.166 or higher
•6753i - Bootloader 2.0.1.1055 or higher •9480i - Bootloader 2.2.0.166 or higher
•6755i - Bootloader 2.0.1.1055 or higher •9480i CT - Bootloader 2.2.0.166 or higher

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones
RN-001029-05 REV 00 – 04.2010 7
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 SIP IP Phone
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 SIP IP Phone 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 SIP IP Phone 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 SIP IP
Phone Administrator Guide.
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-
negotiation”. 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 2.6. 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 2.6
8RN-001029-05 REV 00 – 04.2010
New features in release 2.6
This section provides the new features in SIP IP Phone Release 2.6. These new features
apply to all of the Aastra IP Phones, unless specifically stated otherwise. Each feature
also specifies whether it affects the Administrator, the User, or both.
Feature Description
Configuration Features
Specifying the Caret (“ ^ “) Character in Con-
figuration Files to Overwrite Locally Config-
ured Values
(For Administrators)
An Administrator can now specify a “ ^ “ (caret character)
before a configuration parameter in the aastra.cfg and
<mac>.cfg configuration files which allows the parameter
to be overwritten and reset back to a specified value.
Redirection and Configuration Server (RCS)
Bypass via Option 43
(For Administrators)
DHCP Option 43 support has been extended to include the
ability to bypass contacting Aastra's Redirection and Con-
figuration Server (RCS), in addition to the previous support
of setting the configuration server to contact.
DHCP Time Offset (Option 2) Support
(For Administrators)
An Administrator can now set the offset of UTC using DHCP
Option 2.
Configuration Server Redundancy via DNS A
Records
(For Administrators)
The phones now provide support of multiple IP addresses
being returned for the DNS lookup for server redundancy
via multiple DNS A record entries.
Configuration and Crash File Retrieval
(For Administrators)
An Administrator can now also use three new configura-
tion parameters in the configuration files (or an XML
object) to enable/disable the uploading of support infor-
mation to a pre-defined server.
User Interface Features
Malaysian Tone Set and Cadences
(For Users and Administrators)
The IP Phones now support the Malaysian tone set and
tone set cadences.
Call Hold Reminder During Active Calls
(For Users and Administrators)
The phones now allow a User or Administrator to enable or
disable the ability for the phone to initiate a continuous
reminder tone on the active call when another call is on
hold.
Call Hold Reminder on Single Hold
(For Users and Administrators)
You can enable or disable a feature that would start the
reminder ring splash timer as soon as you put a call on hold
(even when no other calls are active on the phone).

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 9
Call Hold Reminder Timer & Call Hold
Reminder Frequency Parameters
(For Administrators)
An Administrator can set a time delay and frequency of the
call hold ring splash on an active call when another call is
on hold.
Call Waiting Tone Period
(For Users and Administrators)
You can now specify a specific time period (in seconds) for
the call waiting tone to play at regular intervals on an
active call.
Per-Account Call Waiting Control
(For Administrators)
An Administrator can now set call waiting on a per-line
basis using the configuration files or the Aastra Web UI.
Successful Transfer Indication
(For Users and Administrators)
The phone now displays a message when a call transfer is
successful.
Errors Messages Display when Incorrect Net-
work Settings
(For Administrators)
The IP Phone UI AND the Aastra Web UI now immediately
notify the Administrator if an incorrect value is being
entered for the above network parameters in the IP Phone
UI and the Aastra Web UI
SIP Features
Switching Between Early Media and Local
Ringing
(For Administrators)
The phone supports switching between early media and
local ring tone.
Added “Call-Info” Header to 200ok Responses
for Shared Call Appearance (SCA) Lines
(For Administrators)
A “Call-Info” header has been added to call related 200ok
responses sent by the phone for all SCA lines.
XML Features
Connected Action URI
(For XML Developers)
A new parameter called “action uri connected” (configura-
tion files) and “Connected” (Aastra Web UI) now allows
XML scripts to determine when a call is connected.
New “DialLine” URI Command
(For XML Developers)
A new “DialLine” URI command can be used with the Aas-
traIPPhoneExecute object. This URI command allows an
XML application to select the line to use to perform a “dial”
event.
Feature Description

New features in release 2.6
10 RN-001029-05 REV 00 – 04.2010
The following paragraphs describe these features in more detail.
New “Line” Parameter in the Dial Tag for Aas-
traIPPhoneTextMenu Object
(For XML Developers)
An XML Developer can now define which SIP line to use
when using the “dial” tag in the AastraIPPhoneTextMenu
object instead of having the phone selecting the first avail-
able line.
AastraIPPhoneInputScreen Object Supports
Up to 10 fields in “Normal” Mode
(For XML Developers)
An Administrator can now use the AastraIPPhoneInput-
Screen object in an XML application to input up to 10 fields
(normal mode) and up to 5 fields (condensed mode) in the
same object.
Feature Description

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 11
Specifying the Caret (“ ^ “) Character in Configuration Files to
Overwrite Locally Configured Values
In Release 2.6, an Administrator can now specify a “ ^“ (caret character) before a con-
figuration parameter in the aastra.cfg and <mac>.cfg configuration files which allows
the parameter to be overwritten and reset back to a specified value. This can be con-
venient when changes are made by a user to specific parameters on the phone locally
(via Aastra Web UI or IP Phone UI), and the Administrator wants to set the parameters
back to the default values using the configuration files.
As an example, the following table describes how the parameter “sip proxy ip” is han-
dled by the phone during phone bootup when either the “ ^ “ (default parameter) is
used or the “ ! “ (locked parameter) is used.
Configuration Features
IF THEN
new <mac>.cfg file is loaded to the phone with
“^sip proxy ip” and any other parameter(s) from
the file specifying a “ ^“
the “^sip proxy ip” and any other “ ^ “ parameters
are overwritten if previously changed by the user.
new aastra.cfg file is loaded to the phone with
“^sip proxy ip” and any other parameter(s) from
the file specifying a “ ^“
the “^sip proxy ip” and any other “ ^ “ parameters
are overwritten if previously changed by the user.
the first instance is “^sip proxy ip” and second
instance is “!sip proxy ip” in the aastra.cfg and/or
<mac>.cfg file,
the value for the second instance of the parameter
(“!sip proxy ip”) overwrites to the aastra.cfg and/or
<mac>.cfg files previously on the phone.
Notes:
•XML reboots take precedence over server.cfg values. Therefore, “ ^ “ parameters
are ignored in the aastra.cfg file during XML reboots.
•If a parameter has both a “ ^ “ and a “ ! “ preceding the same parameter (i.e., ^!sip
proxy ip: pbx.company.com), then the parameter is ignored and NOT overwritten.
•When Check Sync updates the configuration, it does not parse files before reboot-
ing so it does not overwrite the values. The phone needs to reboot, re-read files,
and then remove locally configured parameters.

New features in release 2.6
12 RN-001029-05 REV 00 – 04.2010
Example
The following example illustrates the use of the “ ^ “ in the configuration files.
aastra.cfg
^sip proxy ip: pbx.company.com
^sip proxy port: 5060
^sip registrar ip: pbx.company.com
^sip registrar port: 5060
In the above example, if an Administrator indicates the “ ^ “ before the parameters in
the aastra.cfg file, and then loads the aastra.cfg file to the phone, these four parame-
ters are reset to their default values, even if the parameters were previously changed
on the phone.
Redirection and Configuration Server (RCS) Bypass via Option 43
In Release 2.6, DHCP Option 43 support has been extended to include the ability to
bypass contacting Aastra's Redirection and Configuration Server (RCS), in addition to
the previous support of setting the configuration server to contact.
A new sub-option code 3 has been defined that uses a boolean value (true or false)
that controls whether or not the phone should contact the RCS after a factory default.
If this value is set to false, the RCS is not contacted. If it is set to true or is missing, then
the RCS is contacted as per previous releases. This can be used in conjunction with
the existing code 2 sub-option to set the configuration server.
Configuring RCS Bypass via Option 43 on a Linux DHCP Server
The following example illustrates how to configure RCS bypass via Option 43 on a
Linux DHCP server.
option space AastraIPPhone;
option AastraIPPhone.cfg-server-name code 02 = text;
option AastraIPPhone.contact-rcs code 03 = boolean;
Subnet 192.168.1.0 netmask 255.255.255.0 {
#The 6757i phones do not contact the RCS but use the defined
FTP server for configuration files.
class "vendor-class-57i" {
match if option vendor-class-
identifier="AastraIPPhone57i";

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 13
vendor-option-space AastraIPPhone;
option AastraIPPhone.cfg-server-name
"ftp://username:[email protected].1";
option AastraIPPhone.contact-rcs false;
}
#The 6757iCT phones do not contact the RCS.
class "vendor-class-57iCT" {
match if option vendor-class-
identifier="AastraIPPhone57iCT";
vendor-option-space AastraIPPhone;
option AastraIPPhone.contact-rcs false;
DHCP Time Offset (Option 2) Support
DHCP Option 42 enables the phone to be configured with the Network Time Protocol
(NTP) server addresses. However, NTP provides the Coordinated Universal Time (UTC)
time so the phone requires the offset from UTC in order to deliver the correct local
time.
Previously, the phones set the offset of UTC from the current timezone setting on the
phone. In Release 2.6, an Administrator can now set the offset of UTC using DHCP
Option 2.
Using the configuration files, an Administrator can use configuration parameter “time
zone name” to enable DHCP Option 2. If this parameter contains the DP-Dhcp value,
the phone derives the time and date from UTC and the time offset offered by the
DHCP server.
Using the IP Phone UI, you can enable the phone to use DHCP Option 2 by setting the
following values from the Country Code list on the phone:
Country Name Country Code
Dhcp DP
Note:
The country name, country code, and time zone name are case sensitive.

New features in release 2.6
14 RN-001029-05 REV 00 – 04.2010
On the IP Phone UI for 5-line phones, a User or Administrator can select Preferences-
>Time and Date->Time Zone and choose “DP-Dhcp” from the displayed time zone
list. On the IP Phone UI for 3-line phones, you select Preferences->Time and Date-
>Time Zone and enter “DP” for the country code, or press “*” and select “Dhcp” from
the displayed time zone list. If you enable DHCP Option 2 via the IP Phone UI, the
change takes place dynamically.
Reference
For more information about using the “time zone name” parameter in the configura-
tion files, see the IP Phone Administrator Guide.
Configuring DHCP Option 2 Using the IP Phone UI
Use the following procedure to configure DHCP Option 2 using the IP Phone UI.
For 5-Line Phones:
Notes:
•When DHCP Option 2 is enabled on the phone, the phone still uses the values set
at Preferences->Time and Date->Daylight Savings configuration settings to
control daylight savings time.
•The default behaviour for the phone is to use the NTP server from Option 42 (or
current configuration setting) and the current time zone settings.
•If the time zone name parameter is set to a value other than Dhcp, then DHCP
Option 2 is disabled.
IP Phone UI
1. Press on the phone to enter the Options List.
2. Select Preferences.
3. Select Time and Date.
4. Select Time Zone.
5. Select DP-Dhcp from the time zone list.
6. Press Done to save the change. The change is dynamic and occurs immedi-
ately.

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 15
For 3-Line Phones:
Configuration Server Redundancy via DNS A Records
Currently the phone sends a DNS query and in the DNS response, it accepts the first
server IP address and contacts that server, ignoring any additional IP addresses in the
response. This allows service providers to manage load balancing (via the DNS server
putting different records first on each request), but does not provide redundancy.
In Release 2.6, the phones now provide support of multiple IP addresses being
returned for the DNS lookup for server redundancy via multiple DNS A record entries.
The phone tries to contact the first server address it receives, but if this fails, it now
tries to contact the second server address, etch.
This feature supports all the download protocols (TFTP, FTP, HTTP, and HTTPS).
1. Press on the phone to enter the Options List.
2. Select Preferences.
3. Select Time and Date.
4. Select Time Zone.
5. In the Country Code field, enter “DP”;
or
Press “*” and select Dhcp from the time zone list.
6. Press Enter to save the change. The change is dynamic and occurs immedi-
ately.
Notes:
•Once the phone has failed over to a redundant server, it continues to use that
server for all other server-related processes on the phone (i.e., firmware upgrades
from the Web UI, boot-up process, etc.).
•If a server fails while downloading a file(s) to the phone, the phone performs the
discovery process of finding a redundant server that is available. When the boot is
complete on the redundant server, the phone tries to download the file(s) again
from the previous server. The check-sync process also performs the same way
when a server fails.
•The “Skip” softkey displays in the event of a network outage, the user can skip the
configuration download and continue the boot.
•All server failovers and failed server IP addresses are logged in the “Error Mes-
sages” page on the IP Phone UI at Options->Phone Status->Error Messages.

New features in release 2.6
16 RN-001029-05 REV 00 – 04.2010
Limitation
In certain cases, the TFTP Protocol cannot distinguish between “server down” and “no
file on server” error messages; therefore, the failover in these instances may fail.
Configuration and Crash File Retrieval
Previously, an Administrator could obtain the current support information on the
phone (configuration information and crash logs) from the Troubleshooting Web UI
page.
In Release 2.6, an Administrator can now also use three new configuration parameters
in the configuration files to enable/disable the uploading of support information to a
pre-defined server. An XML developer can also enable/disable the uploading of sup-
port information using the AastraIPPhoneExecute object. These methods are
described below.
Configuration Parameters for Crash File Retrieval
An Administrator can enter the following parameters in the configuration files to ena-
ble/disable crash file retrieval:
•upload system info server - Specifies the server for which the phone sends the
system and crash files.
•upload system info manual option - Enables and disables the ability to manually
upload support information from the IP Phone UI and Aastra Web UI.
•upload system info on crash - Enables or disables whether or not the crash file is
sent to the pre-defined server each time the watch-dog reboots the phone. When
enabled, each time the watch-dog reboots the phone, the crash file is sent to the
pre-defined server. When disabled, each time the watch-dog reboots the phone,
no crash file is sent to the pre-defined server.
When this feature is enabled (configuration files only), support files can be automati-
cally or manually generated and uploaded when the server detects a phone failure.
An Administrator or User can manually send the files when required using the IP
Phone UI or the Aastra Web UI. Each time the files are generated and uploaded, a new
timestamp on the file name is created so that existing files are not overwritten on the
Notes:
•This feature is disabled by default and can only be enabled by an Administrator.
•For security purposes, Aastra recommends using the HTTPS protocol when trans-
ferring the configuration and crash files to the server.

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 17
server. File names are generated in the format
MAC ID_Date_Time_server.cfg, MAC ID_Date_Time_local.cfg, and
MAC ID_Date_Time_crash.cfg
When this feature is enabled, the phone sends the following support information files
to the server:
•Server.cfg - File in the format MAC ID_Date_Time_server.cfg that contains config-
uration information from the aastra.cfg and the <mac>.cfg files. The MAC address,
date, and time are specified in the file name to identify the phone sending the
information, and the date and time the file was generated and sent to the server.
(for example, 00093D435522_2010-02-25_1141_server.cfg)
•Local.cfg - File in the format MAC ID_Date_Time_local.cfg that contains informa-
tion of locally modified values made using the Aastra Web UI and/or the IP Phone
UI. The MAC address, date, and time are specified in the file name to identify the
phone sending the information, and the date and time the file was generated and
sent to the server. (for example, 00043D199345_2010-02-26_1030_local.cfg)
•Crash.cfg - (only generated if an error or crash occurs on the phone) File in the for-
mat MAC ID_Date_Time_crash.cfg that contains information about a current
phone error/crash causing a reboot of the phone. The MAC address, date, and time
are specified in the file name to identify the phone sending the information, and
the date and time the file was generated and sent to the server.
(for example, 00033D000111_2010-02-27_0204_crash.cfg)
Notes:
•The phone performs the generation and sending of Support Information in the
background. This feature does not affect the use or operation of the phone.
•During a startup or reboot of the phone, an upload of Support Information is
automatically generated and sent to the pre-defined server.
•This feature supports the TFTP, FTP, HTTP, and HTTPS Protocols.

New features in release 2.6
18 RN-001029-05 REV 00 – 04.2010
The following table identifies the methods you can use to retrieve support informa-
tion from the phone to the pre-defined server when the above configuration parame-
ters are enabled.
Configuring Crash File Retrieval Using the Configuration Files
Use the following parameters to configure crash file retrieval from the phone to a
server.
Method for Retrieving Support Info Description
Configuration Files (automatic retrieval) 1. Enter “upload system info server” parameter in
the configuration files and specify the server for
which the phone sends the system and crash
information.
2. Enter “upload system info on crash: 1” to enable
the phone to automatically send system crash
information to the pre-defined server each time
the watchdog reboots the phone.
IP Phone UI
(manual retrieval)
1. On the phone, navigate to Options->Phone Sta-
tus->Upload System Info.
2. Press “Select” or “Enter”. The system information
is immediately sent to the pre-defined server and
the message “Files Sent” displays.
Aastra Web UI
(manual retrieval)
1. On the Aastra Web UI, navigate to Status->Sys-
tem Information->Support Information.
2. Press <Upload>. The system information is
immediately sent to the pre-defined server and
the message “Files Sent” displays.
Parameter–
upload system info server
Configuration Files aastra.cfg, <mac>.cfg
Description Specifies the server for which the phone sends the system and crash
files (server.cfg, local.cfg, and crash.cfg).
Format IP address or qualified domain name.
Example:
tftp://0.0.0.0
ftp://username:password@hostname:port/path
Default Value N/A
Range N/A
Example upload system info server: tftp://132.432.0.43

New features in release 2.6
RN-001029-05 REV 00 – 04.2010 19
Parameter–
upload system info manual
option
Configuration Files aastra.cfg, <mac>.cfg
Description Enables and disables the ability to manually upload support
information from the IP Phone UI and Aastra Web UI.
IP Phone UI: Options->Phone Status->Upload System Info
Aastra Web UI: Status->System Information->Support
Information
When this parameter is enabled, an “Upload System Info” option
displays on the IP Phone UI AND an <Upload> button displays on the
System Information page in the Aastra Web UI.
Format Boolean
Default Value 1
Range 0 (disabled)
1 (enabled)
Example upload system info manual option: 1
Parameter–
upload system info on crash
Configuration Files aastra.cfg, <mac>.cfg
Description Enables or disables whether or not the crash file is sent to the pre-
defined server each time the watch-dog reboots the phone.
When enabled, each time the watch-dog reboots the phone, the
crash file is sent to the pre-defined server. When disabled, each time
the watch-dog reboots the phone, no crash file is sent to the pre-
defined server.
Format Boolean
Default Value 0
Range 0 (disabled)
1 (enabled)
Example upload system info on crash: 1

New features in release 2.6
20 RN-001029-05 REV 00 – 04.2010
Generating and Sending Support Information from the IP Phone UI
Use the following procedure to generate and send Support Information files to the
server.
For 5-Line Phones:
IP Phone UI
1. Press on the phone to enter the Options List.
2. Select Phone Status.
3. Select Upload System Info and press <Select>. The phone immediately
generates the applicable Support Information files (server.cfg, local.cfg,
and/or crash.cfg) and sends the files to the pre-defined server. The message
“Files Sent” displays.
- Select
Done -
Options List
1. Call Forward
2. Preferences
3. Phone Status
4. User Password
Done -
- Select
Phone Status
1. IP&MAC Address
2. LAN Port
3. PC Port
4. Firmware Info
5. Error Messages
6. Upload System Info
Done -
- Upload
Upload System Info
Done -
Files Sent