AASTRA 675xi User Manual

Download

Page 1

SIP

PHONE

9143i, 9480i, 9480i CT and

675xi Series Phones

PHONE

RN-001029-03

Rev 00

Release Note

Release 2.4

Page 2

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.

Page 3

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

Page 4

Page 5

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

Page 6

IP Phone Release Notes 2.4

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

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

Page 7

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

Page 8

IP Phone Release Notes 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.

Page 9

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.

Page 10

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.

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

Page 11

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

Page 12

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

Page 13

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

Page 14

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

Page 15

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

Note: The P-Preferred-Identity for BLA accounts is also sent for hold/

unhold messages.

RN-001029-03, Release 2.4, Rev 00 11

Page 16

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

Page 17

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Configuring BLA Support for MWI using the Configuration Files

Use the following parameter to configure BLA support for MWI.

Parameter – sip mwi for bla account

MWI for BLA Account

(in Web UI)

Description Enables or disables a BLA configured line to send an MWI

Format Boolean

Default Value 0 (disabled)

Range 0 (disabled)

Example sip mwi for bla account: 1

Configuration Files aastra.cfg, <mac>.cfg Aastra Web UI Advanced Settings->Global SIP->

Advanced SIP Settings

SUBSCRIBE message for the BLA account.

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.

1 (enabled)

RN-001029-03, Release 2.4, Rev 00 13

Page 18

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuring BLA Support for MWI using the Aastra Web UI

Use the following procedure to configure BLA support for MWI.

Aastra Web UI

1 Click on Advanced Settings->Global SIP->Advanced SIP Settings.

MWI for BLA Account Parameter

2 The “MWI for BLA Account” field is disabled by default. To enable this feature, place a checkmark in the

“Enabled” box.

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.

3 Click to save your changes and reboot the phone for the change to take affect.

14 RN-001029-03, Release 2.4, Rev 00

Page 19

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Reason Header Field in SIP Message

The IP Phones now support the receiving of the Reason Header Field in a SIP CANCEL message, as described in RFC3326. This allows a call that is answered from somewhere else to still display that it was answered elsewhere in the Callers List. Also, the missed calls indicator and counter do not change.

Limitation

If the call is answered somewhere else, the duration of the call does not display in the Callers List.

RN-001029-03, Release 2.4, Rev 00 15

Page 20

IP Phone Release Notes 2.4

New Features in Release 2.4

User Interface Features

New Speeddial/Conference Key (not applicable to the 6751i)

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) while remaining in the current call. This key allows a user on a call, to conference another party at a pre-defined number while remaining in the conference.

For example, while on an active call, a user can use the Speeddial/Conf key to dial a recording service and have the resulting conference recorded.

Note: If not currently in a conference, the Speeddial/Conf key is disabled

on the active call.

How it Works

If you configure a softkey/programmable key/expansion module as a Speeddial/Conf key, and you press this key while on an active call, the focused line changes to the dialing line. A Cancel softkey displays on the phone (only those phones that have LCDs larger then 3 lines), allowing you to abort the conference speeddial if required. The message "Ringing..." displays below the number when the far end is ringing. The message "Conf. Unavailable" briefly displays when a conference is already in progress or when the CT handset is in use. The active call is not put on hold when the speeddial number is dialed.

Limitations for Speeddial/Conference Key

The following are limitations for the Speeddial/Conference key:

• The CT handsets are not supported.

• The feature is not compatible with centralized conferencing.

The new softkey/programmable key is called "Speeddial/Conf" in the Web UI drop down list. In the configuration file, use "speeddialconf" as the type.

16 RN-001029-03, Release 2.4, Rev 00

Page 21

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Configuring the Speeddial/Conf Key Using the Configuration Files

To configure the Speeddial/Conf key using the configuration files, you enter “speeddialconf” for the key type. The following parameters are examples you can use to configure the Speeddial/Conf key:

softkey1 type: speeddialconf softkey1 label: Sales softkey1 value: 5645 softkey1 line: 3

topsoftkey1 type: speeddialconf topsoftkey1 label: Sales topsoftkey1 value: 5645 topsoftkey1 line: 3

prgkey1 type: speeddialconf prgkey1 value: 5645 prgkey1 line: 1

expmod1 key1 type: speeddialconf expmod1 key1 label: Sales expmod1 key1 value: 5645 expmod1 key1 line: 3

RN-001029-03, Release 2.4, Rev 00 17

Page 22

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuring the Speeddial/Conf Key Using the Aastra Web UI

Use the following procedure to configure the Speeddial/Conf Key using the Aastra Web UI.

Aastra Web UI

1 Click on Operation->Softkeys and XML.

or Click on Operation->Programmable Keys. or Click on Operation->Expansion Module Keys.

Speeddial/Conf Option

2 In the “Type” field, select Speeddial/Conf from the list of options.

3 Click to save your changes.

18 RN-001029-03, Release 2.4, Rev 00

Page 23

Ability for User/Administrator to Configure Time Server Settings

Previously, in the IP Phone UI, the Time Server parameters required an Administrator password to access at the location Options->Preferences->Time and Date->Time Servers. Also, the Time Server parameters in the Aastra Web UI could be set by an Administrator only at the location

Advanced Settings->Network->Advanced Network Settings.

Time Server parameters now located under Time and Date Settings for both User and Administrator

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

RN-001029-03, Release 2.4, Rev 00 19

Page 24

IP Phone Release Notes 2.4

New Features in Release 2.4

Additional Protocol Support for Manual Firmware Upgrade

Previously, the manual firmware upgrade feature in the Aastra Web UI allowed an Administrator to upload firmware from a TFTP server only.

In Release 2.4, an Administrator can now upload firmware updates from TFTP, FTP, HTTP, and HTTPS servers. Applicable fields for each Protocol have been added to allow the Administrator to enter the required information before upgrading the firmware (Path, Port, Username, Password). Specific fields not used by a Protocol are grayed out.

Updating the Firmware Manually Using the Aastra Web UI

Use the following procedure to manually update the firmware on the phone.

Aastra Web UI

1 Click on Advanced Settings->Firmware Update.

2 In the “File Name” field, enter the “.st” file located on your Protocol server. For example, 57i.st, 55i.st, 9480i.st.

3 In the “Download Protocol” field, select the Protocol server type from which you want to download the firmware.

Valid options are:

•TFTP

•FTP

•HTTP

•HTTPS

4 In the “Server” field, enter the IP address of the Protocol server in dotted decimal format.

For example, 10.34.13.45.

20 RN-001029-03, Release 2.4, Rev 00

Page 25

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Aastra Web UI

5 In the “Path” field, enter the path on the Protocol server that contains the “.st” file.

For HTTP and HTTPS

6 In the “Port” field, enter the port on the HTTP or HTTPS server that is used to download the firmware.

For example, 5160.

For FTP

7 In the “Username” field, enter your username used for authentication in accessing the FTP server.

8 In the “Password” field, enter your password used for authentication in accessing the FTP server.

9 Click to save your changes and begin the manual download of firmware from your server.

RN-001029-03, Release 2.4, Rev 00 21

Page 26

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuration Features

Per-Parameter Locking from the Configuration File

An Administrator can lock parameters on the phone by placing an exclamation mark ( the parameter in the configuration file. For example,

!) before

!admin password: 22222 !emergency dial plan: 911|999

You can lock parameters on the phone using the configuration files only. Once the parameters are locked, they cannot be changed at all during the phones run-time. The parameters appear as read-only when accessing the Aastra Web UI and the IP Phone UI. In the Aastra Web UI, they appear grayed out. In the IP Phone UI the ability to change the parameters is removed. In addition, when parameters are locked, they cannot be changed via XML.

Notes:

1. The “parameter locking” feature applies to Release 2.4 and up. Any phones that have a previous release loaded on the phone will not be able to use the locking functionality in the configuration file.

2. Any parameter duplicated in the mac.cfg from the aastra.cfg is overwritten by the locking status and the value of the parameter found in the mac.cfg file.

Limitations

• A User possessing the Administrator password can bypass the locking of configuration server details by defaulting the phone.

• Parameters cannot be locked using XML.

• Configuration files that include locked parameters are not backwards compatible

22 RN-001029-03, Release 2.4, Rev 00

Page 27

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Ability to Enable/Disable the Addition or Editing of a Speeddial Key

The default for this parameter is enabled, allowing you to create and edit speeddial keys on the phone using the Press-and-hold feature, softkeys, programmable keys, expansion module keys and key pad, speeddial menu in the IP Phone UI, and the SAVE TO key.

If this parameter is set to disabled, it blocks the user from using any of the features on the phone to create or edit a speeddial key.

Enabling/Disabling the Addition or Editing of a Speeddial Key Using the Configuration Files

Use the following parameter to enable/disable the ability to add and edit a speeddial key.

Parameter – speeddial edit

Description Allows you to enable or disable the ability to add a speeddial key or

Format Boolean

Default Value 1 (Enabled)

Range 0 (Disabled)

Example speeddial edit: 0

Configuration Files aastra.cfg, <mac>.cfg

edit a speeddial key.

The default is enabled (Yes) allowing you to create and edit speeddial keys on the phone using the Press-and-hold feature, softkeys, programmable keys, expansion module keys and key pad, speeddial menu in the IP Phone UI, and the SAVE TO key.

If this parameter is set to disabled (No), it blocks the user from using any of the features on the phone to create or edit a speeddial key.

1 (Enabled)

RN-001029-03, Release 2.4, Rev 00 23

Page 28

IP Phone Release Notes 2.4

New Features in Release 2.4

Configurable Key Type List

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). Currently, in the Aastra Web UI for a phone, you can select a type of key from a list of approximately 26 key types to assign to a softkey, programmable key, expansion module key, and/or feature key. Now an Administrator can select specific key types that display in the key type list that apply to the User’s environment.

List of Available Keys Types

Example of a List of Configured Keys Types (None, Line, XML, Empty)

In addition to being able to specify which key types display in the list, the Administrator can also determine in which order the key types display.

24 RN-001029-03, Release 2.4, Rev 00

Page 29

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

You can use the following configuration file parameters to control which key types to display and specify in which order to display them in:

• softkey selection list

• feature key selection list

If no value is specified for the “softkey selection list” and/or “feature key selection list” parameters, the key “Type” list displays all of the key types by default.

If an Administrator configures specific key types for a phone in the configuration file, and the phone for which he will download the configuration to already has key types configured on it, those key types display in the key list for those keys, in addition to the key types specified by the Administrator. For example, a phone has a Park key and a Pickup key already configured on the phone, and the Administrator downloads a configuration file to the phone that has specific key types of None, Line, Speeddial, and XML. After the configuration file is downloaded, the Park key list will show None, Line, Speeddial, XML, and Park; the Pickup key list will show None, Line, Speeddial, XML, and Pickup; all other keys that were configured as None before the download will show only None, Line, Speeddial, and XML.

Notes:

1. Any key types configured that do not apply to the phone are ignored.

2. The SAVE and DELETE keys appear by default as Keys 1 and 2 on the 6753i and 9143i, unless specifically allowed by the Administrator to be configurable.

3. An Administrator must use the English value when configuring the key types in the configuration files.

5. After configuring specific key types for a phone, the key types in the Aastra Web UI display the same for both the User and Administrator Web interfaces for that phone.

RN-001029-03, Release 2.4, Rev 00 25

Page 30

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuring the Key Type List Using the Configuration Files

Softkeys, Programmable Keys, Expansion Module Keys

Use the following parameters to specify key types to display in the “Type” list for softkeys, programmable keys, and expansion module keys.

Parameter – softkey selection list

Description Allows you to specify which key types to display and the order in

Format Alpha Characters in a comma separated list

Configuration Files aastra.cfg, <mac>.cfg

which to display them in the “Type” list for softkeys, programmable keys, and/or expansion module keys when configuring the keys in the Aastra Web UI.

If no value is specified for this “softkey selection list” parameter, the key “Typ e” list displays ALL of the key types by default in the Aastra Web UI.

1. Any key types configured that do not apply to the phone’s environment are ignored.

2. The SAVE and DELETE keys appear by default as Keys 1 and 2 on the 6753i and 9143i, unless specifically allowed by the Administrator to be configurable.

3. An Administrator must use the English value when configuring the key types in the configuration files.

4. Any key type already configured on a phone displays in that key’s “Typ e” list, in addition to the values specified for this parameter.

5. After configuring specific key types for a phone, the key types in the Aastra Web UI display the same for both the User and Administrator Web interfaces for that phone.

Default Value

•none •lcr

• line • call forward

• speeddial • blf/xfer

• dnd • speeddial/xfer

• blf • speeddial/conf

• list • directory

•acd •callers

• dcp • conf (6753i, 9143i)

• xml • xfer (6753i, 9143i)

•webapps •icom

• flash • services

• sprecode • phonelock

• park • paging

• pi ckup • empty (6755i, 6757i, 6757 CT, 9480i, 9480i CT)

26 RN-001029-03, Release 2.4, Rev 00

Page 31

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Range Any of the key types in the “Default Value” field above.

Example softkey selection list: blf, speeddial, line, xml

Handset Feature Keys (for CT Models ONLY)

Use the following parameters to specify key types to display in the “Type” list for feature keys.

Parameter – feature key selection list

Description Allows you to specify which key types to display and the order in

Format Alpha Characters in a comma separated list

Default Value

Configuration Files aastra.cfg, <mac>.cfg

which to display them in the “Type” list for the feature keys (CT models only) when configuring the keys in the Aastra Web UI.

If no value is specified for this “feature key selection list” parameter, the key “Typ e” list displays ALL of the key types by default in the Aastra Web UI.

1. Any key types configured that do not apply to the phone’s environment are ignored.

2. An Administrator must use the English value when configuring the key types in the configuration files.

3. Any key type already configured on a phone displays in that key’s “Typ e” list, in addition to the values specified for this parameter.

4. After configuring specific key types for a phone, the key types in the Aastra Web UI display the same for both the User and Administrator Web interfaces for that phone.

• none • park

• line • pickup

• icom • conf

•dir •private

• callers • public

• xfer • flash

Range Any of the key types in the “Default Value” field above.

Example feature key selection list: line, dir, callers

Limitation

The following is a limitation of the configuration key type list feature:

• Entering duplicate values for the parameters in the configuration file displays duplicate entries in the “Type” list in the Aastra Web UI.

RN-001029-03, Release 2.4, Rev 00 27

Page 32

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuration Server Download Precedence

In Release 2.4, you can now set the phone’s download precedence to ignore DHCP, (only during the boot when the remote configuration server is contacted) and use the following

precedence instead:

1. Configuration URI,

2. DHCP, and then

3. Direct configuration.

To configure the download precedence, a new option value (-1) has been added to the existing “dhcp config option override” parameter. Setting this parameter to “-1” causes all DHCP configuration options to be ignored.

Notes:

1. In the IP Phone UI, the “Option Override” parameter has been renamed to “Download Options” parameter.

2. In the Aastra Web UI, the “DHCP Option Override” parameter has been renamed to “DHCP Download Options” parameter.

3. In both the IP Phone UI and the Aastra Web UI the “Disabled” download option is new and performs the same function as the “-1” in the configuration files. The “None” option has been renamed to “Any” which performs the same function as “0” in the configuration files.

Configuring a Download Precedence Using the Configuration Files

Use the following parameter and set the value to “-1” to ignore DHCP configuration options 159 and 160.

Parameter– dhcp config option override

DHCP Download Options

(in Web UI)

Description The value specified for this parameter overrides the precedence order for

Format Integer

Default Value 0 (Any - no override - uses normal precedence order of

Range -1 (Disabled - ignores all DHCP configuration options (43, 66, 159, 160)

Example dhcp config option override: -1

Configuration Files aastra.cfg, <mac>.cfg IP Phone UI Options->Administrator Menu->

Network Settings->DHCP Settings-> Download Options

Aastra Web UI Advanced Settings->Network->

Advanced Network Settings

determining a configuration server.

Note: You must restart the IP Phone for this parameter to take affect.

43, 160, 159, 66)

0 (Any) 43 66 159 160

28 RN-001029-03, Release 2.4, Rev 00

Page 33

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Configuring a Download Precedence Using the IP Phone UI

Use the following procedure to configure a download precedence using the IP Phone UI.

1. Press Options and select Administrator Menu.

2. Enter your Administrator password and press Enter.

3. Select Network Settings->DHCP Settings->Download Options.

4. Select “Disabled” and press Enter to save the change.

Note: In the IP Phone UI, the “Disabled” download option performs the

same function as the “-1” in the configuration files (ignores DHCP options).

5. At the reboot prompt, press “Restart” to reboot the phone.

Configuring a Download Precedence Using the Aastra Web UI

Use the following procedure to configure a download precedence using the Aastra Web UI.

Aastra Web UI

1 Click on Advanced Settings->Network->Advanced Network Settings.

DHCP Download Options Parameter

2 In the “DHCP Download Options” field, select “Disabled” from the list of options.

Note: In the Aastra Web UI, the “Disabled” download option performs the same function as the “-1” in the

configuration files (ignores DHCP options).

3 Click to save your setting.

4 Select Operation->Reset, and click RESTART to reboot the phone.

RN-001029-03, Release 2.4, Rev 00 29

Page 34

IP Phone Release Notes 2.4

New Features in Release 2.4

Dial Plan Length Extended

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.

If a User enters a dial plan longer than 512 characters, or a parsing error occurs, the phone uses the default dial plan of “x+#|xx+*”.

Limitations

The following are limitations of the extended field dial plan:

• If the User enters a dial plan longer then 512 characters, the phone uses the default dial plan instead. If this is the case, the Administrator cannot change the dial plan from the configuration files. The dial plan must be changed from the Aastra Web UI.

Emergency Dial Plan Supports Pattern Matching

The IP Phones now support emergency dialing using pattern matching and prepend dial plan functionality.

There are two ways to dial a number on the phone:

• dialing digit-by-digit (i.e., select line and dial)

• dialing by string (i.e., pre-dial then go off-hook)

When a user dials digit-by-digit, the phone adds every digit to a dialed string and checks against the dial plan. If the phone is not locked, it checks against the regular dial plan. If the phone is locked, it checks against the emergency dial plan.

When a user dials by string, (pre-dial, speed-dial, etc., and then goes off-hook), and the phone is not locked, it checks to see if the number matches the registered emergency dial plan. If it doesn’t match, it blocks the call from going through. If the phone is locked, and the number matches the emergency dial plan it allows the call to go through.

Adding a prepend to a dial plan also works with both dialing digit-by-digit and dialing by string.

Limitation

The following is a limitation for emergency dial plans with pattern matching:

• Secondary dial tone is not supported.

30 RN-001029-03, Release 2.4, Rev 00

Page 35

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Improved Auto-Resync Functionality

The existing auto-resync functionality on the IP Phones has been enhanced to reduce load on configuration servers. The following parameters for auto-sync have been added to the configuration file and the Aastra Web UI to support this feature:

•The “auto resync max delay” parameter (in configuration file) and the “Maximum Delay” parameter (in the Aastra Web UI) which allows you to configure the maximum value for the random time the phone waits before beginning a download when the scheduled checksync occurs. Default is 15 minutes.

•The “auto resync days” parameter (in the configuration file) and the “Days” parameter (in the Aastra Web UI) which allows you to specify the number of days the phone should wait after a checksync before trying the download again. Default is 0 days.

Setting these parameters can greatly reduce the load placed on the configuration server when downloading configurations.

Configuring the Auto-Resync Functionality Using the Configuration Files

Use the following parameters to enhance the auto-resync functionality.

Parameter– auto resync max delay

Maximum Delay

(in Web UI)

Description Specifies the maximum time, in minutes, the phone waits past the

Format Integer

Default Value 15

Range 0 to 1439

Example auto resync max delay: 20

Parameter–

auto resync days

Days

(in Web UI)

Description Specifies the amount of days that the phone waits between checksync

Format Integer

Default Value 0

Range 0 to 364

Example auto resync days: 1

Configuration Files aastra.cfg, <mac>.cfg Aastra Web UI Advanced Settings->Configuration Server->

Auto-Resync

scheduled time before starting a checksync.

Configuration Files aastra.cfg, <mac>.cfg Aastra Web UI Advanced Settings->Configuration Server->

Auto-Resync

operations.

Note: A value of 0 causes the phone to checksync every time the clock reads the proper time. A value of 1 forces the phone to wait 24 hours prior to doing the first checksync.

RN-001029-03, Release 2.4, Rev 00 31

Page 36

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuring the Auto-Resync Functionality Using the Aastra Web UI

Use the following procedure to set the Auto-Resync parameters.

Aastra Web UI

1 Click on Advanced Settings->Configuration Server->Auto-Resync.

Maximum Delay Parameter

Days Parameter

2 In the “Maximum Delay” field, enter maximum time, in minutes, the phone waits past the scheduled time before

starting a checksync. Valid values are 0 to 1439. Default is 15 minutes.

3 In the “Days” field, enter the amount of days that the phone waits between checksync operations. Valid values are

0 to 364. Default is 0 days.

Note: A value of 0 causes the phone to checksync every time the clock reads the proper time. A value of 1 forces the phone to wait 24 hours prior to doing the first checksync.

4 Click to save your setting.

32 RN-001029-03, Release 2.4, Rev 00

Page 37

XML Features

Drop, Conf, and Xfer Softkeys for XML Screens

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. These custom softkeys are active ONLY in the connected state. They are available for the following screen objects:

• TextScreen

• FormattedTextScreen

•TextMenu

• InputScreen

• ImageMenu

• ImageScreen

For XML screens on the 6755i, 6757i, 6757i CT, 9480i, and 9480i CT phones with large LCDs, the Drop, Conf and Xfer custom softkeys display on one screen.

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

For XML screens on the 6751i, 6753i, and 9143i phones with small LCDs, adding the "allowDrop", "allowConf" or "allowXfer" attribute to the root tag of the UI XML object allows the corresponding Drop, Conf, or Xfer key to be shown on the command line.

XML Example

<AastraIPPhoneTextScreen

Beep="no" allowDrop="yes" allowConf="yes" allowXfer="yes"> <Title></Title> <Text>Username and Phone number</Text>

</AastraIPPhoneTextScreen>

John Doe 5157

Conf

Xfer

For the smaller LCDs, if all three attributes are included in the XML object, only the Conf and Xfer keys display as shown above.

For all phones, once the user presses the custom softkey (Drop, Conf, Xfer), the softkey disappears after the action is performed. For example, after pressing the Xfer key on an active call from an XML screen, the Xfer key disappears and the dialing screen appears.

RN-001029-03, Release 2.4, Rev 00 33

Page 38

IP Phone Release Notes 2.4

New Features in Release 2.4

New Action URI for Registration Events

• Registered

• Unregistered

• Registration timed out

• Registration refused

• Registration expired

Note: The action URI is not called when the same event is repeated (for

example, a timeout occurs again when registration is already in a timeout state.

To support this feature, the following URI variables have been added for action URIs involving registration events:

Action URI Variable Description

$$REGISTRATIONSTATE$$ Registration states can be:

•REGISTERED

• UNREGISTERED

• EXPIRED

• REFUSED

•TIMEOUT

$$REGISTRATIONCODE$$

Registration code can be: "xxx" where xxx is the 3 digit code; for example, "403". Possible codes are:

• 001 (registration successful)

• 403 (registration failed)

34 RN-001029-03, Release 2.4, Rev 00

Page 39

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Configuring the Registration Event Action URI Using the Configuration Files

Use the following parameter to configure the registration event action URI.

Parameter– action uri registration event

Registration Event

(in Web UI)

Description Specifies the URI that the phone executes a GET on, when a registration

Configuration Files aastra.cfg, <mac>.cfg Aastra Web UI Advanced Settings->Action URI

event change occurs. This parameter uses the following variables to determine the state of the event:

$$REGISTRATIONSTATE$$ $$REGISTRATIONCODE$$

Note: This action URI is not called when the same event is repeated (for example, a timeout occurs again when registration is already in a timeout state.)

Format String

Default Value Not Applicable

Range Any valid URI

Example action uri registration event: http://10.30.100.39/PHPtests/

actionuri.php?action=RegEvt®state=$$REGISTRATIONSTATE$$® code=$$REGISTRATIONCODE$$

RN-001029-03, Release 2.4, Rev 00 35

Page 40

IP Phone Release Notes 2.4

New Features in Release 2.4

Configuring the Registration Event Action URI Using the Aastra Web UI

Use the following procedure to configure the Registration Event URI.

Aastra Web UI

1 Click on Advanced Settings->Action URI.

Registration Event Parameter

2 In the “Registration Event” field, enter the string that the phone executes a GET on, when a registration event

change occurs. Applicable variables to use in the string are:

$$REGISTRATIONSTATE$$$$LOCALIP$$ $$REGISTRATIONCODE$$

For example,

action uri registration event: http://10.30.100.39/PHPtests/ actionuri.php?action=RegEvt®state=$$REGISTRATIONSTATE$$®code=$$REGISTRATIONCODE$$

3 Click to save your setting.

36 RN-001029-03, Release 2.4, Rev 00

Page 41

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Configurable “setType” Attribute for AastraIPPhoneConfiguration Object

The IP phones include a new attribute, “setType” to be used with the AastraIPPhoneConfiguration XML object. The AastraIPPhoneConfiguration object allows you

to make configuration changes to the phone that take affect immediately, without having to reboot the phone. The “setType” attribute enhances the ability of the AastraIPPhoneConfiguration object to override locally set configuration parameters, and parameters that persist across a reboot, allowing the user to control how the configuration parameters are saved (locally, remotely, or override).

The following table describes the values you can use with the “setType” attribute.

Values for “setType” Parameter Description

remote (default) Allows the configuration parameters to be

saved with the same precedence as the server settings. This setting does not persist through a reboot.

Note: This was the behavior of the phone prior to Release 2.4.

local Allows the configuration parameters to be

saved with the same precedence as if you configured them using the IP Phone UI or Aastra Web UI. This setting persists through reboots of the phone. The only way to change this setting is via the IP Phone UI, Aastra Web UI, or another local type setting.

override Allows the configuration parameters to be

saved with the same precedence as server settings. This setting does not persist through a reboot and removes the local setting.

Notes:

1. If you enter a value for the “setType” attribute in the root tag of the AastraIPPhoneConfiguration object, the setting affects all of the configuration parameters and their sub-elements.

2. If you enter a value for the “setType” attribute for a single configuration item, the setting affects on that configuration item and its sub-elements.

The following are examples of using the “remote”, “local”, and “override” values with the setType attribute and the AastraIPPhoneConfiguration object.

RN-001029-03, Release 2.4, Rev 00 37

Page 42

IP Phone Release Notes 2.4

New Features in Release 2.4

Remote Setting Examples (default)

The following are examples that are the same as using setType=”remote” setting for a specific configuration item (softkey1 label).

<Parameter>softkey1 label</Parameter> <Value>Test</Value>

</ConfigurationItem>

</AastraIPPhoneConfigutation>

<Parameter>softkey1 label</Parameter> <Value>Test</Value>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

RESULT: If the value for "softkey1 label" is not specified via the configuration files, or another setType="remote" setting, the XML examples shown above assign the value of "Te st ". This value is lost when the phone reboots. If the value for "softkey1 label" has been specified locally, these XML examples do not change that value.

Local Setting Example

The following is an example of using the setType=”local” setting for a specific configuration item (softkey1 label).

<Parameter>softkey1 label</Parameter> <Value>Test</Value>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

RESULT: The value of "softkey1 label" is set to "Tes t". This value persists through reboots of the phone.

38 RN-001029-03, Release 2.4, Rev 00

Page 43

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Override Setting Example

The following is an example of using the setType=”override” setting for a specific configuration item (softkey1 label)

<Parameter>softkey1 label</Parameter> <Value>Test</Value>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

RESULT: The value of "softkey1 label" is set to "Tes t". When the phone reboots, the value for the "softkey1 label" reverts back to the server configured value, or its default value on the server.

Example of Using Multiple “setType” Values

The following is an example of using multiple “setType” values for multiple configuration items (softkey1, softkey2).

<Parameter>softkey1 label</Parameter>

<Parameter>softkey2 label</Parameter>

RESULT: The value of “Tes t” is set for "softkey2 label" using the local rules. The value of “Te st ” is set for "softkey3 label” using the override rules. When all items have been set, the phone reboots.

Limitation

The following is a limitation for the “setType” attribute:

•Using setType=”local” to set a parameter that is not modifiable via the IP Phone UI or the Aastra Web UI, results in a parameter that can only be changed via XML.

RN-001029-03, Release 2.4, Rev 00 39

Page 44

IP Phone Release Notes 2.4

New Features in Release 2.4

Troubleshooting Features

Error Messages Display

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. These options allow you to view error messages generated by modules during startup only (not after registration has completed). You can use this information for troubleshooting purposes or for reporting the errors to the Administrator.

The IP Phone stores and displays up to 10 error messages (any extra error messages beyond 10 are discarded). The time and date of each error message also displays. After a reboot, the previous error messages are discarded and, if applicable, new error messages display. If there are no error messages during startup or after a reboot, the message, “No Error Messages” displays on the screen. Error messages display in the language currently set on the phone.

The following table identifies the possible error messages that may display.

Possible Error Message Description

Bad Certificate A Transport Layer Security (TLS) certificate

is not valid. The invalid certificate can be any of the following:

• root and intermediate certificate

• local certificate

• private key filename

• trusted certificate

802.1x Startup Failed The Extensible Authentication Protocol TLS (EAP-TLS) certificates and/or the EAP-MD5 information has failed on the phone.

LLDP Startup Failed Link Layer Discovery Protocol (LLDP) failed

during startup of the phone.

HTTP Connection Manager Init Failed The Hypertext Transfer Protocol (HTTP)

connection manager initialization failed while updating the configuration on the phone.

Failed to config Line Manager The configuration of the Line Manager

module on the phone has failed.

40 RN-001029-03, Release 2.4, Rev 00

Page 45

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

New Features in Release 2.4

Viewing the Error Messages Using the IP Phone UI

Use the following procedure to view the error messages, if any, that generated during startup.

IP Phone UI

1 Press the Options key on the phone to enter the Options List.

2Select Phone Status.

3Select Error Messages.

Phone Status

1. IP&MAC Addresses

6755i, 6757i, 6757i CT 9480i, 9480i CT

2. LAN Port

3. PC Port

4. Firmware Info

5. Error Messages

- Select

Done -

6751i, 6753i, 9143i

5. Error Messages

Enter

RN-001029-03, Release 2.4, Rev 00 41

Page 46

IP Phone Release Notes 2.4

New Features in Release 2.4

IP Phone UI

4 If error messages display, use the UP and DOWN navigation keys to view the messages. If no error

message exist, the message, “No Error Messages” displays on the screen.

Error Messages

No Error Messages

6755i, 6757i, 6757i CT 9480i, 9480i CT

6751i, 6753i, 9143i

Error Messages <error message 1> Fri Aug 4 1:55 pm <error message 2> Fri Aug 4 1:57 pm <error message 3> Fri Aug 4 2:00 pm

Done -

Error Messages

<error message 1> Fri Aug 4 2:00 pm

Exit

Error Messages

5 When done viewing, press Done or Exit to exit the Error Messages screen.

Done -

Exit

42 RN-001029-03, Release 2.4, Rev 00

Page 47

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

Viewing the Error Messages Using the Aastra Web UI

Use the following procedure to view the error messages, if any, that generated during startup.

Aastra Web UI

1 Click on Advanced Settings->Troubleshooting->Error Messages.

New Features in Release 2.4

Error Messages

2 Scroll down to the “Error Messages” section to view the error messages that may have generated during startup

or reboot of the IP Phone.

RN-001029-03, Release 2.4, Rev 00 43

Page 48

IP Phone Release Notes 2.4

Issues Resolved in Release 2.4

This section describes the issues resolved on the IP Phones in Release 2.4. The following table provides the issue number and a brief description of each fix.

Note: Unless specifically indicated, these resolved issues apply to all

phone models.

Issue Number Description of Fix

User Interface

DEF10971 If you select a line key and then press redial the selected line is now used for the outgoing call.

DEF11424 Corrected handling of daylight savings in the southern hemisphere.

DEF11529 Updated daylight savings start and end times in Australia.

Web UI

DEF10630 The expansion module web page is now displayed correct in Internet Explorer.

DEF10753 User is now prompted to reboot the phone if they change from DHCP to static IP addressing.

DEF10754 Gateway information is saved if you switch from DHCP to static IP addressing.

SIP

DEF10463 Phones configured to only use SRTP no longer reject INVITE messages without SDP.

DEF08641 Phone no longer sends SDP in ACK message if it receives multiple 1xx messages.

DEF10824 DNS results with a TTL greater than 1 day are now accepted.

DEF10825 UPDATE messages are now correctly rejected if they are received at the wrong time.

DEF10838 Phone now sends a BYE if the session-timers expire.

DEF10894 Phone now falls back to using RFC2543 hold if sendrecv is not supported by the far-end.

DEF10980 Phone no longer does a DNS lookup on the registrar and proxy names when an outbound proxy is

configured.

DEF11037 Calls are now rejected when TURN requests fail.

DEF11044 DTMF now works during early media when you receive multiple 1xx messages.

DEF11093 Via header is now correctly constructed when using manual NAT settings.

Robustness

DEF10703 A very large display name in the From field of an incoming INVITE no longer causes the phone to

terminate.

DEF10755 If a call is forked and a second 200 OK is received, it no longer causes the phone to terminate.

DEF11322 When using the "wrapList=yes" attribute in an XML text menu object is used, it no longer causes the

phone to terminate.

44 RN-001029-03, Release 2.4, Rev 00

Page 49

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series Phones Release Note 2.4

Contacting Aastra Telecom Support

If you’ve read this release note, and consulted the Troubleshooting section of your phone model’s manual and still have problems, please send inquiries via email to support@aastra.com.

Contacting Aastra Telecom Support

RN-001029-03, Release 2.4, Rev 00 45

Page 50

Page 51

Page 52

Generic SIP IP Phone Models 9143i, 9480i, 9480i CT, and 675xi Series

2.4 Release Notes

Copyright © 2008 Aastra Telecom. All rights reserved. Information in this document is subject to change without notice. Aastra Telecom assumes no responsibility for any errors that may appear in this document. Product capabilities described in this document pertain solely to Aastra Telecom's marketing activities in the U.S. and Canada. Availability in other markets may vary.

RN-001029-03 Rev 00 Release 2.4

November 2008

AASTRA 675xi User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About this Document

General Information

Release Content Information

Hardware Supported

Bootloader Requirements

Before you Upgrade

Please Read Before Upgrading Your Phone

New Features in Release 2.4

Description

Hardware Features

5xi Series Phones and Expansion Modules Renamed

Will the phones use the same file names as before for upgrading and rebooting?

Will the SIP user agent, Vendor Class ID, HTTP headers remain the same?

SIP Features

“SIP Join” Feature (not applicable to the 6751i)

Limitations of the “SIP Join” Feature

Configuring “SIP Join” Using the Configuration Files

Missed Calls Message Event Notification

GRUU and sip.instance Support

Configuring GRUU Using the Configuration Files

Limitations of the GRUU Feature

Support for Early-Only Parameter in Replaces Header RFC3891

P-Preferred Identity Header for BLA Accounts

BLA Support for Message Waiting Indicator (MWI)

Limitations

Configuring BLA Support for MWI using the Configuration Files

Configuring BLA Support for MWI using the Aastra Web UI

Reason Header Field in SIP Message

Limitation

User Interface Features

New Speeddial/Conference Key (not applicable to the 6751i)

How it Works

Limitations for Speeddial/Conference Key

Configuring the Speeddial/Conf Key Using the Configuration Files

Configuring the Speeddial/Conf Key Using the Aastra Web UI

Ability for User/Administrator to Configure Time Server Settings

Additional Protocol Support for Manual Firmware Upgrade

Updating the Firmware Manually Using the Aastra Web UI

Configuration Features

Per-Parameter Locking from the Configuration File

Limitations

Ability to Enable/Disable the Addition or Editing of a Speeddial Key

Enabling/Disabling the Addition or Editing of a Speeddial Key Using the Configuration Files

Configurable Key Type List

Configuring the Key Type List Using the Configuration Files

Limitation

Configuration Server Download Precedence

Configuring a Download Precedence Using the Configuration Files

Configuring a Download Precedence Using the IP Phone UI

Configuring a Download Precedence Using the Aastra Web UI

Dial Plan Length Extended

Limitations

Emergency Dial Plan Supports Pattern Matching

Limitation

Improved Auto-Resync Functionality

Configuring the Auto-Resync Functionality Using the Configuration Files

Configuring the Auto-Resync Functionality Using the Aastra Web UI

XML Features

Drop, Conf, and Xfer Softkeys for XML Screens

New Action URI for Registration Events

Configuring the Registration Event Action URI Using the Configuration Files

Configuring the Registration Event Action URI Using the Aastra Web UI

Configurable “setType” Attribute for AastraIPPhoneConfiguration Object

Limitation

Troubleshooting Features

Error Messages Display

Viewing the Error Messages Using the IP Phone UI

Viewing the Error Messages Using the Aastra Web UI

Issues Resolved in Release 2.4

Contacting Aastra Telecom Support