AASTRA 675xi User Manual
SIP
IP
PHONE
9143i, 9480i, 9480i CT and
9143i, 9480i, 9480i CT and
675xi Series Phones
675xi Series Phones
SI
I
PHONE
RN-001029-03
Rev 00
Release Note
Release 2.4
Aastra Telecom will not accept liability for any damages and/or long distance charges, which result from unauthorized and/or
unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom will not be liable for technical or editorial errors
or omissions contained within this documentation. The information contained in this documentation is subject to change without
notice.
Copyright 2008 Aastra Telecom. www.aastratelecom.com
All Rights Reserved.
Contents
General Information ..................................................................................................................................2
Release Content Information ................................................................................................................2
Hardware Supported ............................................................................................................................. 2
Bootloader Requirements .....................................................................................................................2
Before you Upgrade .................................................................................................................................. 3
Please Read Before Upgrading Your Phone ......................................................................................... 3
New Features in Release 2.4 .................................................................................................................... 4
Description ............................................................................................................................................ 4
Hardware Features ............................................................................................................................... 7
5xi Series Phones and Expansion Modules Renamed ................................................................... 7
SIP Features ......................................................................................................................................... 9
“SIP Join” Feature (not applicable to the 6751i) ............................................................................. 9
Missed Calls Message Event Notification ..................................................................................... 10
GRUU and sip.instance Support ...................................................................................................10
Support for Early-Only Parameter in Replaces Header RFC3891 ............................................... 11
P-Preferred Identity Header for BLA Accounts ............................................................................. 11
BLA Support for Message Waiting Indicator (MWI) ...................................................................... 12
Reason Header Field in SIP Message .........................................................................................15
User Interface Features ......................................................................................................................16
New Speeddial/Conference Key (not applicable to the 6751i) ..................................................... 16
Ability for User/Administrator to Configure Time Server Settings .................................................19
Additional Protocol Support for Manual Firmware Upgrade .........................................................20
Configuration Features ........................................................................................................................22
Per-Parameter Locking from the Configuration File .....................................................................22
Ability to Enable/Disable the Addition or Editing of a Speeddial Key ............................................ 23
Configurable Key Type List ........................................................................................................... 24
Configuration Server Download Precedence ............................................................................... 28
Dial Plan Length Extended ........................................................................................................... 30
Emergency Dial Plan Supports Pattern Matching ......................................................................... 30
Improved Auto-Resync Functionality ............................................................................................31
XML Features ......................................................................................................................................33
Drop, Conf, and Xfer Softkeys for XML Screens ..........................................................................33
New Action URI for Registration Events .......................................................................................34
Configurable “setType” Attribute for AastraIPPhoneConfiguration Object ....................................37
Troubleshooting Features ...................................................................................................................40
Error Messages Display ............................................................................................................... 40
Issues Resolved in Release 2.4 .............................................................................................................. 44
Contacting Aastra Telecom Support ...................................................................................................... 45
Contents
RN-001029-03, Release 2.4, Rev 00 iii
Models 9143i, 9480i, 9480i CT,
About this Document
This Release Note 2.4 provides new features for the 9143i, 9480i, and 9480i CT SIP IP Phones and
the 675xi Series SIP IP Phones (previously the 5xi Series) (6751i, 6753i, 6755i, 6757i, 6757i CT).
It also includes the issues resolved since Release 2.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 Installation Guide and the SIP IP
Phone User Guide. For detailed information about more advanced features, see the SIP IP Phone
Administrator Guide.
SIP IP Phone
and 675xi Series Phones
Release Note 2.4
Topics in this release note include:
• General Information
(release content, hardware supported, bootloader requirements)
• New Features in Release 2.4
• Issues Resolved in Release 2.4
• Contacting Aastra Telecom Support
RN-001029-03, Release 2.4, Rev 00 1
IP Phone Release Notes 2.4
General Information
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 5i Series SIP IP Phone firmware.
Model Release Name Release Version Release Filename Release Date
6751i Generic SIP 2.4.0.96
6753i Generic SIP 2.4.0.96
6755i Generic SIP 2.4.0.96
6757i Generic SIP 2.4.0.96
6757i CT Generic SIP 2.4.0.96
9143i Generic SIP 2.4.0.96
9480i Generic SIP 2.4.0.96
9480i CT Generic SIP 2.4.0.96
Hardware Supported
This release of firmware is compatible with the following Aastra IP portfolio products:
• 6751i • 6757i CT
• 6753i • 9143i
• 6755i • 9480i
• 6757i • 9480i CT
FC-001126-04-REV00
FC-001086-08-REV00
FC-001087-06-REV00
FC-001088-06-REV00
FC-001089-06-REV00
FC-001092-04-REV00
November 2008
November 2008
November 2008
November 2008
November 2008
November 2008
FC-001097-04-REV00 November 2008
FC-001101-04-REV00
November 2008
Bootloader Requirements
This release of firmware is compatible with the following Aastra IP portfolio product bootloader
versions:
• 6751i - Bootloader 2.1.0.2088 or higher • 6757i CT - Bootloader 2.0.1.1055 or higher
• 6753i - Bootloader 2.0.1.1055 or higher • 9143i - Bootloader 2.2.0.166 or higher
• 6755i - Bootloader 2.0.1.1055 or higher • 9480i - Bootloader 2.2.0.166 or higher
• 6757i - Bootloader 2.0.1.1055 or higher • 9480i CT - Bootloader 2.2.0.166 or higher
2 RN-001029-03, Release 2.4, Rev 00
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.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 network 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 contact 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 Verisign,
Thawte, or GeoTrust, the phones fail to download configuration files. For more information
about HTTPS validation, see the Aastra SIP IP Phone Administrator Guide.
Before you Upgrade
• 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.
RN-001029-03, Release 2.4, Rev 00 3
IP Phone Release Notes 2.4
New Features in Release 2.4
New Features in Release 2.4
Description
This section provides the new features in SIP IP Phone Release 2.4. 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
Hardware Features
5xi Series Phones and Expansion Modules
Renamed
(For Users and Administrators)
SIP Features
“SIP Join” Feature (not applicable to the
6751i)
(For Administrators)
Missed Calls Message Event Notification
(For Administrators)
GRUU and sip.instance Support
(For Administrators)
Support for Early-Only Parameter in
Replaces Header RFC3891
In Release 2.4, the 5xi Series phones have been
renamed to 675xi Series phones to comply with Aastra’s
campaign to harmonize its product names. Expansion
Modules have also been renamed.
Release 2.4 includes support for RFC 3911 which allows
an additional caller to join an active call between two
parties if the caller knows the dialog information.
In Release 2.4, the phones now include a
“Missed-Calls-Message” field in a “message summary”
event of a SIP NOTIFY message.
Globally Routable User-Agent URIs (GRUUs) provide a
way for anyone on the Internet to route a call to a
specific instance of a User-Agent. GRUU allows an
incoming session request to be sent to a specific phone
instead of all phone’s in the network.
The phones now support the early-only parameter in the
“Replaces” header according to RFC3891.
(For Administrators)
P-Preferred Identity Header for BLA Accounts
(For Administrators)
BLA Support for Message Waiting Indicator
(MWI)
(For Administrators)
Reason Header Field in SIP Message
(For Administrators)
4 RN-001029-03, Release 2.4, Rev 00
Release 2.4 now supports the BLA specification,
draft-anil-sipping-bla-02, which states that the
P-Preferred-Identity header (RFC3325) gets added to
the INVITE message to indicate the Caller-ID that is
used for the call.
Release 2.4 allows you to enable or disable the ability
for a BLA configured line to send a SUBSCRIBE SIP
message for a Message Waiting Indicator (MWI)
message-summary event subscription, with the BLA
account in the "TO" contact header and the in a URI.
The IP Phones now support the receiving of the Reason
Header Field in a SIP CANCEL message, as described
in RFC3326.
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4
Feature Description
User Interface Features
New Speeddial/Conference Key (not
applicable to the 6751i)
(For Users and Administrators)
Ability for User/Administrator to Configure
Time Server Settings
(For Users and Administrators)
Additional Protocol Support for Manual
Firmware Upgrade
(For Administrators)
Configuration Features
Per-Parameter Locking from the
Configuration File
(For Administrators)
Ability to Enable/Disable the Addition or
Editing of a Speeddial Key
(For Administrators)
Configurable Key Type List
(For Administrators)
Configuration Server Download Precedence
(For Administrators)
Dial Plan Length Extended
(For Users and Administrators)
Emergency Dial Plan Supports Pattern
Matching
The IP Phones now allow you to configure a softkey/
programmable key/expansion module key to be used as
a speeddial conference key (Speeddial/Conf key). This
key allows a user on a call, to conference another party
at a pre-defined number while remaining in the
conference.
In Release 2.4, the password requirement has been
removed from the IP Phone UI so that a User or
Administrator can now set the Time Server settings. The
Time Server parameters in the Aastra Web UI have been
moved from the Administrator page to both the User and
Administrator pages.
In Release 2.4, an Administrator can now upload
firmware updates from TFTP, FTP, HTTP, and HTTPS
servers.
The IP Phones now allow you to lock individual
configuration parameters to prevent an end user from
changing the configuration on the phone. This feature
allows service providers to prevent the end-user from
changing the values of specific parameters that would
affect the service they provide.
The IP Phones now allow you to set a parameter,
“speeddial edit” using the configuration files that allows
you to enable or disable the ability to add a speeddial
key or edit a speeddial key from the IP Phone UI.
In Release 2.4, an Administrator can now configure
which key types display in the Aastra Web UI list for a
Softkey, Programmable Key, Expansion Module Key,
and/or Feature Key (CT Models).
In Release 2.4, you can now set the phone’s download
precedence to ignore DHCP options, (only during the
boot when the remote configuration server is contacted)
and use a configuration URI as the first download
choice.
In Release 2.4, the dial plan length has been extended
to accept up to 512 characters. Previously, this field
could only accept up to 128 characters.
The IP Phones now support emergency dialing using
pattern matching and prepend dial plan functionality.
New Features in Release 2.4
(For Users and Administrators)
XML Features
Drop, Conf, and Xfer Softkeys for XML
Screens
(For XML Developers)
RN-001029-03, Release 2.4, Rev 00 5
In Release 2.4, the Drop, Conf and Xfer softkeys can
now be customized to use with XML objects and display
on XML screens as required.
IP Phone Release Notes 2.4
New Features in Release 2.4
Feature Description
New Action URI for Registration Events
(For XML Developers)
Configurable “setType” Attribute for
AastraIPPhoneConfiguration Object
(For XML Developers)
Troubleshooting Features
Error Messages Display
(For Users and Administrators)
The IP Phones now include an action URI that is called
whenever registration events occur or when there are
registration state changes. The new action URI is called
“action uri registration event” (in configuration files)
and “Registration Event” (in Aastra Web UI).
The IP phones include a new attribute, “setType” to be
used with the AastraIPPhoneConfiguration XML
object. The “setType” attribute enhances the ability of
the AastraIPPhoneConfiguration object to override
locally set configuration parameters, and parameters
that persist across a reboot.
In Release 2.4, you can now view generated error
messages that may have occurred during startup or
reboot of the IP Phones. The IP Phone UI has a new
selection on the Phone Status page called, “Error
Messages” at the location, Options->Phone
Status->Error Messages. The Aastra Web UI also
allows you to view these error messages at the location
Advanced Settings->Troubleshooting->Error
Messages.
The following paragraphs describe these features in more detail.
6 RN-001029-03, Release 2.4, Rev 00
Hardware Features
5xi Series Phones and Expansion Modules Renamed
Aastra has renamed the 5xi Series phones to the 675xi Series phones in order to comply with
Aastra’s global campaign to harmonize the product names between its multiple divisions and
multiple product portfolios. In addition, the Expansion Modules have been renamed. The
following table identifies each phone and its applicable new name.
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4
New Features in Release 2.4
Previous Model Name New Model Name
IP Phones
51i 6751i
53i 6753i
55i 6755i
57i 6757i
57i CT 6757i CT
Expansion Modules
536M M670i
560M M675i
The phone name change is strictly cosmetic and does not affect the operation of the
phones.
The only visible effects of the change on the existing 5xi phones are:
• The new 6751i and 6753i names display during bootup on the LCD of existing 51i and 53i
models, respectively.
• Model number displays in the upper left corner of the Aastra Web UI to reflect the new 675xi
model name.
• Latest Install Guides, User Guides, and Administrator Guide reflect the new 675xi name.
Future phone builds will include the 675xi on the logo plates and labels.
Will the phones use the same file names as before for upgrading and rebooting?
Yes. The name change has no affect on the file names for the installed base 5xi or the 67xi phones.
The renamed 675xi phones and the installed base 5xi phones, continue to look for the 5xi.st
filenames (51i.st, 53i.st, 55i.st, etc.) after a reboot. There is no impact to the installed based
phones. The “.st” files names do not change. For example, a 53i phone and a 6753i phone will both
look for the 53i.st file.
RN-001029-03, Release 2.4, Rev 00 7
IP Phone Release Notes 2.4
New Features in Release 2.4
Will the SIP user agent, Vendor Class ID, HTTP headers remain the same?
Yes. In SIP signaling, the SIP User agent contains the phone’s model number (5xi model
numbers). The SIP User agent continues to reflect the 5xi name on the renamed phones. This
minimizes the impact on the current installed base.
Example
User-Agent: Aastra 55i/2.4.0.1
DHCP option 60 Vendor Class continues to reflect the 5xi model name on the renamed phones.
The following is an example of the Option 60 on a DHCP request:
Example
Option 60: Vendor class identifier = "AastraIPPhone55i"
:
In XML, the phone sends the model number (5xi model numbers) in the HTTP headers. The 5xi
models numbers continue to be sent by the phone in HTTP headers in XML applications on the
renamed phones.
8 RN-001029-03, Release 2.4, Rev 00
SIP Features
“SIP Join” Feature (not applicable to the 6751i)
Release 2.4 includes support for RFC 3911 which allows an additional caller to join an active call
between two parties if the caller knows the dialog information. This feature begins a conference
using a join header as described in RFC 3911.
The “SIP Join“ feature provides the following:
• Security via the whitelist (which is a feature that already exists on the phone).
• Initiates an offhook action uri when it is answered.
• Initiates an onhook action uri at call termination.
• Creates a caller list entry.
This feature is disabled by default. You can enable the “SIP Join” feature by setting the “sip join
support” parameter in the configuration files.
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4
New Features in Release 2.4
Limitations of the “SIP Join” Feature
The following are limitations of the “SIP Join” feature:
• Not applicable to a conference call already in progress.
• Not applicable to a CT handset that has two active calls.
• Not applicable to a phone mixing RTP.
• Allows secondary parties to join calls if they can determine the dialog parameters. In order to
provide security, it is recommended that the Administrator configure the SIP whitelist.
• Not applicable while the active call between two parties is in the early dialog state.
RN-001029-03, Release 2.4, Rev 00 9
IP Phone Release Notes 2.4
New Features in Release 2.4
Configuring “SIP Join” Using the Configuration Files
User the following parameter to set up the “SIP Join” feature on the IP Phone.
Parameter –
sip join support
Description Enables or disables the phone to allow a conference to be set up with
Format Boolean
Default Value 0 (disabled)
Range 0 (disabled)
Example sip join support: 1
Configuration Files aastra.cfg, <mac>.cfg
a join header as described in RFC 3911.
1 (enabled)
Missed Calls Message Event Notification
In Release 2.4, the phones now include a “Missed-Calls-Message” field in a “message
summary” event of a SIP NOTIFY message.
GRUU and sip.instance Support
Globally Routable User-Agent URIs (GRUUs) provide a way for anyone on the Internet to route
a call to a specific instance of a User-Agent.
Release 2.4 provides GRUU support using draft-ietf-sip-gruu-15. A sip.instance is added to all
non-GRUU contacts. By default, this feature is enabled. You can enable or disable this support
using the configuration files.
Configuring GRUU Using the Configuration Files
Use the following parameter to enable/disable GRUU support on the IP Phones.
Parameter –
sip gruu
Description Enables or disables GRUU support on the IP Phone according to
Format Boolean
Default Value 1 (enabled)
Range 0 (disabled)
Example sip gruu: 0
Configuration Files aastra.cfg, <mac>.cfg
draft-ietf-sip-gruu-15. If this parameter is disabled, parsing of inbound
GRUU's for transfer are still enabled.
1 (enabled)
Limitations of the GRUU Feature
The following are limitations of the GRUU feature on the phones:
• GRUU-Draft-15 is not compatible with versions prior to GRUU-Draft-10.
• Phones do not support temporary or phone-created GRUUs.
10 RN-001029-03, Release 2.4, Rev 00
SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4
New Features in Release 2.4
Support for Early-Only Parameter in Replaces Header RFC3891
The phones now support the early-only parameter in the “Replaces” header according to
RFC3891. When the phone receives a Replaces header with the early-only parameter, it replaces
the existing dialog if the call is still in the early state. If the call has been answered, then the
Replaces request is rejected.
Note: This feature is not supported in outgoing requests.
P-Preferred Identity Header for BLA Accounts
Release 2.4 now supports the BLA specification, draft-anil-sipping-bla-02, which states that the
P-Preferred-Identity header (RFC3325) gets added to the INVITE message to indicate the
Caller-ID that is used for the call.
Note: The P-Preferred-Identity for BLA accounts is also sent for hold/
unhold messages.
RN-001029-03, Release 2.4, Rev 00 11
IP Phone Release Notes 2.4
New Features in Release 2.4
BLA Support for Message Waiting Indicator (MWI)
The IP Phones now have an option for a Bridged Line Appearance (BLA) configured line to
send a SUBSCRIBE SIP message for a Message Waiting Indicator (MWI).
Notes:
1. If you change the setting on this parameter, you must reboot the
phone for it to take affect.
2. Both the “sip explicit mwi subscription” and “sip mwi for bla
account” parameters must be enabled in order for the MWI subscription
for BLA to occur.
3. The MWI re-subscription for the BLA account uses the value set for
the "sip explicit mwi subscription period" parameter to re-subscribe.
4. Whether or not the "sip mwi for bla account" parameter is enabled,
the priority for displaying MWI does not change.
You can configure this feature using the configuration files or the Aastra Web UI.
Limitations
The following are limitations of the BLA Support for MWI feature:
• The phone shows MWI for the first matching identity if more than one line with different
user names has the same BLA account.
• If a normal line has the same user name as the BLA user of another line, the phone shows
MWI only for the normal line.
12 RN-001029-03, Release 2.4, Rev 00
Loading...