V2.6.0, May 2010, pdf

Aastra Model9143i, 9480i, 9480i CT, and67xxi Series Phones

Aastra 2.6 Release Notes

RN-001029-05 REV 00 – 04.2010

Content

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones Release Notes 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Release notes topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release content information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Hardware supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Bootloader requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Before you upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Please read before upgrading your phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

New features in release 2.6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Specifying the Caret (“ ^ “) Character in Configuration Filesto Overwrite Locally Configured Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Redirection and Configuration Server (RCS) Bypass via Option 43 . . . . . . . . . . . 12DHCP Time Offset (Option 2) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Configuration Server Redundancy via DNS A Records . . . . . . . . . . . . . . . . . . . . . . 15Configuration and Crash File Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Malaysian Tone Set and Cadences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Call Hold Reminder During Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Call Hold Reminder on Single Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Call Hold Reminder Timer & Call Hold Reminder Frequency Parameters . . . . . 31Call Waiting Tone Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Per-Account Call Waiting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Successful Transfer Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Errors Messages Display when Incorrect Network Settings . . . . . . . . . . . . . . . . . . 37

2 RN-001029-05 REV 00 – 04.2010

Content

SIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Switching Between Early Media and Local Ringing . . . . . . . . . . . . . . . . . . . . . . . . . 38Added “Call-Info” Header to 200ok Responses for Shared Call Appearance (SCA) Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

XML Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Connected Action URI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39New “DialLine” URI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41New “Line” Parameter in the Dial Tag for AastraIPPhoneTextMenu Object. . . 43AastraIPPhoneInputScreen Object Supports Up to 10 fields in “Normal” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Issues Resolved in Release 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Contacting Aastra Telecom Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

RN-001029-05 REV 00 – 04.2010 3

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series PhonesRelease Notes 2.6

About this documentThese Release Notes 2.6* provide new features for the 9143i, 9480i, and 9480i CT SIP IP Phones and the 67xxi Series SIP IP Phones (6730i, 6731i, 6751i, 6753i, 6755i, 6757i, 6757i CT). It also includes the issues resolved since Release 2.5.3 of the IP Phones.

For more detailed information about features associated with each phone, and for information on how to use the phones, see your model-specific SIP IP Phone Installa-tion Guide and the SIP IP Phone User Guide. For detailed information about more advanced features, see the SIP IP Phone Administrator Guide.

Release notes topicsTopics in these release notes include:

• General information

• New features in release 2.6

• Issues Resolved in Release 2.6

• Contacting Aastra Telecom Support

* Release 2.6 of the 67xxi SIP phones is not supported on Model 6739i.

4 RN-001029-05 REV 00 - 04.2010

SIP IP Phone Models 9143i, 9480i, 9480i CT, and 67xxi Series Phones

General information

Release content information

This document provides release content information on the Aastra 9143i, 9480i, and 9480i CT SIP IP Phone firmware and the 67xxi Series SIP IP Phone firmware.

Hardware supported

This release of firmware is compatible with the following Aastra IP portfolio products:

Model Release name Release version Release filename Release date

6730i Generic SIP 2.6 FC-001240-03-Rev00 April 2010






6757i CT Generic SIP 2.6 FC-001089-08-Rev00 April 2010



9480i CT Generic SIP 2.6 FC-001101-06-Rev00 April 2010

• 6730i • 6757i

• 6731i • 6757i CT

• 6751i • 9143i

• 6753i • 9480i

• 6755i • 9480i CT

RN-001029-05 REV 00 – 04.2010 5


Bootloader requirements

This release of firmware is compatible with the following Aastra IP portfolio product bootloader versions:

• 6730i - Bootloader 2.4.0.80 or higher • 6757i - Bootloader 2.0.1.1055 or higher

• 6731i - Bootloader 2.4.0.80 or higher • 6757i CT - Bootloader 2.0.1.1055 or higher



• 6755i - Bootloader 2.0.1.1055 or higher • 9480i CT - Bootloader 2.2.0.166 or higher

6 RN-001029-05 REV 00 – 04.2010


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 defaultIf LLDP is enabled on your network, the phones may come up with different net-work settings. For more information about LLDP, see the Aastra SIP IP Phone Administrator Guide.

• Support for DHCP Options 159 and 160If the DHCP server supplies Options 159 and 160, the phones will attempt to con-tact the configuration server given in these options. For more information about Options 159 and 160, see the Aastra SIP IP Phone Administrator Guide.

• HTTPS validationIf you are using HTTPS and the certificates are not valid or are not signed by Veri-sign, Thawte, or GeoTrust, the phones fail to download configuration files. For more information about HTTPS validation, see the Aastra SIP IP Phone Administrator Guide.

• Watchdog task featureIf the phone detects a failure (for example, a crash), the phone automatically reboots. For more information about the Watchdog feature, see the Aastra SIP IP Phone Administrator Guide.

Note:If you factory default a phone with Release 2.3 and above software, when the phone reboots, it attempts to connect to rcs.aastra.com. There is no personal information transmitted from the phone and the phone continues to boot up as normal.

Warning:Applicable to IP Phone Models 6730i and 6731i only: The default negotiation setting for the Ethernet ports on the phones is “auto-negotiation”. If you have changed this default setting to another value (i.e., Half Duplex or Full Duplex), you MUST set the negotiation value back to the default value of “auto-negotiation” before upgrading to Release 2.6. Failure to do so may cause the phone to fail to connect to the network. In addition, downgrade will not be possible.

RN-001029-05 REV 00 – 04.2010 7

New features in release 2.6

New features in release 2.6This section provides the new features in SIP IP Phone Release 2.6. These new features apply to all of the Aastra IP Phones, unless specifically stated otherwise. Each feature also specifies whether it affects the Administrator, the User, or both.

Feature Description

Configuration Features

Specifying the Caret (“ ^ “) Character in Con-figuration Files to Overwrite Locally Config-ured Values(For Administrators)

An Administrator can now specify a “ ^ “ (caret character) before a configuration parameter in the aastra.cfg and <mac>.cfg configuration files which allows the parameter to be overwritten and reset back to a specified value.

Redirection and Configuration Server (RCS) Bypass via Option 43

(For Administrators)

DHCP Option 43 support has been extended to include the ability to bypass contacting Aastra's Redirection and Con-figuration Server (RCS), in addition to the previous support of setting the configuration server to contact.

DHCP Time Offset (Option 2) Support


An Administrator can now set the offset of UTC using DHCP Option 2.

Configuration Server Redundancy via DNS A Records


The phones now provide support of multiple IP addresses being returned for the DNS lookup for server redundancy via multiple DNS A record entries.

Configuration and Crash File Retrieval


An Administrator can now also use three new configura-tion parameters in the configuration files (or an XML object) to enable/disable the uploading of support infor-mation to a pre-defined server.

User Interface Features

Malaysian Tone Set and Cadences

(For Users and Administrators)

The IP Phones now support the Malaysian tone set and tone set cadences.

Call Hold Reminder During Active Calls


The phones now allow a User or Administrator to enable or disable the ability for the phone to initiate a continuous reminder tone on the active call when another call is on hold.

Call Hold Reminder on Single Hold


You can enable or disable a feature that would start the reminder ring splash timer as soon as you put a call on hold (even when no other calls are active on the phone).

8 RN-001029-05 REV 00 – 04.2010


Call Hold Reminder Timer & Call Hold Reminder Frequency Parameters


An Administrator can set a time delay and frequency of the call hold ring splash on an active call when another call is on hold.

Call Waiting Tone Period


You can now specify a specific time period (in seconds) for the call waiting tone to play at regular intervals on an active call.

Per-Account Call Waiting Control


An Administrator can now set call waiting on a per-line basis using the configuration files or the Aastra Web UI.

Successful Transfer Indication


The phone now displays a message when a call transfer is successful.

Errors Messages Display when Incorrect Net-work Settings


The IP Phone UI AND the Aastra Web UI now immediately notify the Administrator if an incorrect value is being entered for the above network parameters in the IP Phone UI and the Aastra Web UI

SIP Features

Switching Between Early Media and Local Ringing


The phone supports switching between early media and local ring tone.

Added “Call-Info” Header to 200ok Responses for Shared Call Appearance (SCA) Lines


A “Call-Info” header has been added to call related 200ok responses sent by the phone for all SCA lines.

XML Features

Connected Action URI

(For XML Developers)

A new parameter called “action uri connected” (configura-tion files) and “Connected” (Aastra Web UI) now allows XML scripts to determine when a call is connected.

New “DialLine” URI Command


A new “DialLine” URI command can be used with the Aas-traIPPhoneExecute object. This URI command allows an XML application to select the line to use to perform a “dial” event.

Feature Description

RN-001029-05 REV 00 – 04.2010 9


The following paragraphs describe these features in more detail.

New “Line” Parameter in the Dial Tag for Aas-traIPPhoneTextMenu Object


An XML Developer can now define which SIP line to use when using the “dial” tag in the AastraIPPhoneTextMenu object instead of having the phone selecting the first avail-able line.

AastraIPPhoneInputScreen Object Supports Up to 10 fields in “Normal” Mode


An Administrator can now use the AastraIPPhoneInput-Screen object in an XML application to input up to 10 fields (normal mode) and up to 5 fields (condensed mode) in the same object.

Feature Description

10 RN-001029-05 REV 00 – 04.2010


Specifying the Caret (“ ^ “) Character in Configuration Files to Overwrite Locally Configured Values

In Release 2.6, an Administrator can now specify a “ ^ “ (caret character) before a con-figuration parameter in the aastra.cfg and <mac>.cfg configuration files which allows the parameter to be overwritten and reset back to a specified value. This can be con-venient when changes are made by a user to specific parameters on the phone locally (via Aastra Web UI or IP Phone UI), and the Administrator wants to set the parameters back to the default values using the configuration files.

As an example, the following table describes how the parameter “sip proxy ip” is han-dled by the phone during phone bootup when either the “ ^ “ (default parameter) is used or the “ ! “ (locked parameter) is used.

Configuration Features

IF THEN

new <mac>.cfg file is loaded to the phone with “^sip proxy ip” and any other parameter(s) from the file specifying a “ ^ “

the “^sip proxy ip” and any other “ ^ “ parameters are overwritten if previously changed by the user.

new aastra.cfg file is loaded to the phone with “^sip proxy ip” and any other parameter(s) from the file specifying a “ ^ “

the “^sip proxy ip” and any other “ ^ “ parameters are overwritten if previously changed by the user.

the first instance is “^sip proxy ip” and second instance is “!sip proxy ip” in the aastra.cfg and/or <mac>.cfg file,

the value for the second instance of the parameter (“!sip proxy ip”) overwrites to the aastra.cfg and/or <mac>.cfg files previously on the phone.

Notes:• XML reboots take precedence over server.cfg values. Therefore, “ ^ “ parameters

are ignored in the aastra.cfg file during XML reboots.• If a parameter has both a “ ^ “ and a “ ! “ preceding the same parameter (i.e., ^!sip

proxy ip: pbx.company.com), then the parameter is ignored and NOT overwritten.• When Check Sync updates the configuration, it does not parse files before reboot-

ing so it does not overwrite the values. The phone needs to reboot, re-read files, and then remove locally configured parameters.

RN-001029-05 REV 00 – 04.2010 11


ExampleThe following example illustrates the use of the “ ^ “ in the configuration files.

aastra.cfg^sip proxy ip: pbx.company.com^sip proxy port: 5060^sip registrar ip: pbx.company.com^sip registrar port: 5060

In the above example, if an Administrator indicates the “ ^ “ before the parameters in the aastra.cfg file, and then loads the aastra.cfg file to the phone, these four parame-ters are reset to their default values, even if the parameters were previously changed on the phone.

Redirection and Configuration Server (RCS) Bypass via Option 43

In Release 2.6, DHCP Option 43 support has been extended to include the ability to bypass contacting Aastra's Redirection and Configuration Server (RCS), in addition to the previous support of setting the configuration server to contact.

A new sub-option code 3 has been defined that uses a boolean value (true or false) that controls whether or not the phone should contact the RCS after a factory default. If this value is set to false, the RCS is not contacted. If it is set to true or is missing, then the RCS is contacted as per previous releases. This can be used in conjunction with the existing code 2 sub-option to set the configuration server.

Configuring RCS Bypass via Option 43 on a Linux DHCP ServerThe following example illustrates how to configure RCS bypass via Option 43 on a Linux DHCP server.

option space AastraIPPhone;

option AastraIPPhone.cfg-server-name code 02 = text;option AastraIPPhone.contact-rcs code 03 = boolean;

Subnet 192.168.1.0 netmask 255.255.255.0 {

#The 6757i phones do not contact the RCS but use the defined FTP server for configuration files. class "vendor-class-57i" {

match if option vendor-class-identifier="AastraIPPhone57i";

12 RN-001029-05 REV 00 – 04.2010


vendor-option-space AastraIPPhone; option AastraIPPhone.cfg-server-name "ftp://username:[email protected]"; option AastraIPPhone.contact-rcs false; }

#The 6757iCT phones do not contact the RCS.class "vendor-class-57iCT" {

match if option vendor-class-identifier="AastraIPPhone57iCT";

vendor-option-space AastraIPPhone;

option AastraIPPhone.contact-rcs false;

DHCP Time Offset (Option 2) Support

DHCP Option 42 enables the phone to be configured with the Network Time Protocol (NTP) server addresses. However, NTP provides the Coordinated Universal Time (UTC) time so the phone requires the offset from UTC in order to deliver the correct local time.

Previously, the phones set the offset of UTC from the current timezone setting on the phone. In Release 2.6, an Administrator can now set the offset of UTC using DHCP Option 2.

Using the configuration files, an Administrator can use configuration parameter “time zone name” to enable DHCP Option 2. If this parameter contains the DP-Dhcp value, the phone derives the time and date from UTC and the time offset offered by the DHCP server.

Using the IP Phone UI, you can enable the phone to use DHCP Option 2 by setting the following values from the Country Code list on the phone:

Country Name Country Code

Dhcp DP

Note: The country name, country code, and time zone name are case sensitive.

RN-001029-05 REV 00 – 04.2010 13


On the IP Phone UI for 5-line phones, a User or Administrator can select Preferences->Time and Date->Time Zone and choose “DP-Dhcp” from the displayed time zone list. On the IP Phone UI for 3-line phones, you select Preferences->Time and Date->Time Zone and enter “DP” for the country code, or press “*” and select “Dhcp” from the displayed time zone list. If you enable DHCP Option 2 via the IP Phone UI, the change takes place dynamically.

ReferenceFor more information about using the “time zone name” parameter in the configura-tion files, see the IP Phone Administrator Guide.

Configuring DHCP Option 2 Using the IP Phone UIUse the following procedure to configure DHCP Option 2 using the IP Phone UI.

For 5-Line Phones:

Notes:• When DHCP Option 2 is enabled on the phone, the phone still uses the values set

at Preferences->Time and Date->Daylight Savings configuration settings to control daylight savings time.

• The default behaviour for the phone is to use the NTP server from Option 42 (or current configuration setting) and the current time zone settings.

• If the time zone name parameter is set to a value other than Dhcp, then DHCP Option 2 is disabled.

IP Phone UI

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

2. Select Preferences.

3. Select Time and Date.

4. Select Time Zone.

5. Select DP-Dhcp from the time zone list.

6. Press Done to save the change. The change is dynamic and occurs immedi-ately.

14 RN-001029-05 REV 00 – 04.2010


For 3-Line Phones:

Configuration Server Redundancy via DNS A Records

Currently the phone sends a DNS query and in the DNS response, it accepts the first server IP address and contacts that server, ignoring any additional IP addresses in the response. This allows service providers to manage load balancing (via the DNS server putting different records first on each request), but does not provide redundancy.

In Release 2.6, the phones now provide support of multiple IP addresses being returned for the DNS lookup for server redundancy via multiple DNS A record entries. The phone tries to contact the first server address it receives, but if this fails, it now tries to contact the second server address, etch.

This feature supports all the download protocols (TFTP, FTP, HTTP, and HTTPS).



3. Select Time and Date.

4. Select Time Zone.

5. In the Country Code field, enter “DP”;orPress “*” and select Dhcp from the time zone list.

6. Press Enter to save the change. The change is dynamic and occurs immedi-ately.

Notes:• Once the phone has failed over to a redundant server, it continues to use that

server for all other server-related processes on the phone (i.e., firmware upgrades from the Web UI, boot-up process, etc.).

• If a server fails while downloading a file(s) to the phone, the phone performs the discovery process of finding a redundant server that is available. When the boot is complete on the redundant server, the phone tries to download the file(s) again from the previous server. The check-sync process also performs the same way when a server fails.

• The “Skip” softkey displays in the event of a network outage, the user can skip the configuration download and continue the boot.

• All server failovers and failed server IP addresses are logged in the “Error Mes-sages” page on the IP Phone UI at Options->Phone Status->Error Messages.

RN-001029-05 REV 00 – 04.2010 15


LimitationIn certain cases, the TFTP Protocol cannot distinguish between “server down” and “no file on server” error messages; therefore, the failover in these instances may fail.

Configuration and Crash File Retrieval

Previously, an Administrator could obtain the current support information on the phone (configuration information and crash logs) from the Troubleshooting Web UI page.

In Release 2.6, an Administrator can now also use three new configuration parameters in the configuration files to enable/disable the uploading of support information to a pre-defined server. An XML developer can also enable/disable the uploading of sup-port information using the AastraIPPhoneExecute object. These methods are described below.

Configuration Parameters for Crash File RetrievalAn Administrator can enter the following parameters in the configuration files to ena-ble/disable crash file retrieval:

• upload system info server - Specifies the server for which the phone sends the system and crash files.

• upload system info manual option - Enables and disables the ability to manually upload support information from the IP Phone UI and Aastra Web UI.

• upload system info on crash - Enables or disables whether or not the crash file is sent to the pre-defined server each time the watch-dog reboots the phone. When enabled, each time the watch-dog reboots the phone, the crash file is sent to the pre-defined server. When disabled, each time the watch-dog reboots the phone, no crash file is sent to the pre-defined server.

When this feature is enabled (configuration files only), support files can be automati-cally or manually generated and uploaded when the server detects a phone failure. An Administrator or User can manually send the files when required using the IP Phone UI or the Aastra Web UI. Each time the files are generated and uploaded, a new timestamp on the file name is created so that existing files are not overwritten on the

Notes:• This feature is disabled by default and can only be enabled by an Administrator.• For security purposes, Aastra recommends using the HTTPS protocol when trans-

ferring the configuration and crash files to the server.

16 RN-001029-05 REV 00 – 04.2010


server. File names are generated in the format MAC ID_Date_Time_server.cfg, MAC ID_Date_Time_local.cfg, and MAC ID_Date_Time_crash.cfg

When this feature is enabled, the phone sends the following support information files to the server:

• Server.cfg - File in the format MAC ID_Date_Time_server.cfg that contains config-uration information from the aastra.cfg and the <mac>.cfg files. The MAC address, date, and time are specified in the file name to identify the phone sending the information, and the date and time the file was generated and sent to the server.(for example, 00093D435522_2010-02-25_1141_server.cfg)

• Local.cfg - File in the format MAC ID_Date_Time_local.cfg that contains informa-tion of locally modified values made using the Aastra Web UI and/or the IP Phone UI. The MAC address, date, and time are specified in the file name to identify the phone sending the information, and the date and time the file was generated and sent to the server. (for example, 00043D199345_2010-02-26_1030_local.cfg)

• Crash.cfg - (only generated if an error or crash occurs on the phone) File in the for-mat MAC ID_Date_Time_crash.cfg that contains information about a current phone error/crash causing a reboot of the phone. The MAC address, date, and time are specified in the file name to identify the phone sending the information, and the date and time the file was generated and sent to the server.(for example, 00033D000111_2010-02-27_0204_crash.cfg)

Notes:• The phone performs the generation and sending of Support Information in the

background. This feature does not affect the use or operation of the phone.• During a startup or reboot of the phone, an upload of Support Information is

automatically generated and sent to the pre-defined server.• This feature supports the TFTP, FTP, HTTP, and HTTPS Protocols.

RN-001029-05 REV 00 – 04.2010 17


The following table identifies the methods you can use to retrieve support informa-tion from the phone to the pre-defined server when the above configuration parame-ters are enabled.

Configuring Crash File Retrieval Using the Configuration FilesUse the following parameters to configure crash file retrieval from the phone to a server.

Method for Retrieving Support Info Description

Configuration Files (automatic retrieval) 1. Enter “upload system info server” parameter in the configuration files and specify the server for which the phone sends the system and crash information.

2. Enter “upload system info on crash: 1” to enable the phone to automatically send system crash information to the pre-defined server each time the watchdog reboots the phone.

IP Phone UI(manual retrieval)

1. On the phone, navigate to Options->Phone Sta-tus->Upload System Info.

2. Press “Select” or “Enter”. The system information is immediately sent to the pre-defined server and the message “Files Sent” displays.

Aastra Web UI(manual retrieval)

1. On the Aastra Web UI, navigate to Status->Sys-tem Information->Support Information.

2. Press <Upload>. The system information is immediately sent to the pre-defined server and the message “Files Sent” displays.

Parameter– upload system info server

Configuration Files aastra.cfg, <mac>.cfg

Description Specifies the server for which the phone sends the system and crash files (server.cfg, local.cfg, and crash.cfg).

Format IP address or qualified domain name.Example:tftp://0.0.0.0ftp://username:password@hostname:port/path

Default Value N/A

Range N/A

Example upload system info server: tftp://132.432.0.43

18 RN-001029-05 REV 00 – 04.2010


Parameter– upload system info manual option


Description Enables and disables the ability to manually upload support information from the IP Phone UI and Aastra Web UI.IP Phone UI: Options->Phone Status->Upload System InfoAastra Web UI: Status->System Information->Support Information

When this parameter is enabled, an “Upload System Info” option displays on the IP Phone UI AND an <Upload> button displays on the System Information page in the Aastra Web UI.

Format Boolean

Default Value 1

Range 0 (disabled)1 (enabled)

Example upload system info manual option: 1

Parameter– upload system info on crash


Description Enables or disables whether or not the crash file is sent to the pre-defined server each time the watch-dog reboots the phone.

When enabled, each time the watch-dog reboots the phone, the crash file is sent to the pre-defined server. When disabled, each time the watch-dog reboots the phone, no crash file is sent to the pre-defined server.

Format Boolean

Default Value 0

Range 0 (disabled)1 (enabled)

Example upload system info on crash: 1

RN-001029-05 REV 00 – 04.2010 19


Generating and Sending Support Information from the IP Phone UIUse the following procedure to generate and send Support Information files to the server.

For 5-Line Phones:

IP Phone UI


2. Select Phone Status.

3. Select Upload System Info and press <Select>. The phone immediately generates the applicable Support Information files (server.cfg, local.cfg, and/or crash.cfg) and sends the files to the pre-defined server. The message “Files Sent” displays.

- Select Done -

Options List

1. Call Forward2. Preferences3. Phone Status4. User Password

Done -

- Select

Phone Status

1. IP&MAC Address2. LAN Port3. PC Port4. Firmware Info5. Error Messages6. Upload System Info

Done -

- Upload

Upload System Info

Done -

Files Sent

20 RN-001029-05 REV 00 – 04.2010


For 3-Line Phones:

Generating and Sending Support Information from the Aastra Web UI

Use the following procedure to generate and send Support Information files to the server.


2. Select Phone Status.

3. Select Upload System Info and press <Enter>. The phone immediately gen-erates the applicable Support Information files (server.cfg, local.cfg, and/or crash.cfg) and sends the files to the pre-defined server. The message “Files Sent” displays.

Aastra Web UI

1. Click on Status->System Information->Support Information.

Phone Status3

Enter Cancel

Upload System Info6

Enter Cancel Upload System Info

Enter Cancel Files Sent

Next

RN-001029-05 REV 00 – 04.2010 21


New AastraIPPhoneExecute command for Crash File RetrievalAn Administrator can also use the AastraIPPhoneExecute object to send a command to the phone for retrieving the phone crash files and configuration files. The com-mand is “UploadSystemInfo”. The files are sent to the location defined in the configu-ration parameter “upload system info server” located in aastra.cfg or MAC.cfg.

The following is an example of using the new AastraIPPhoneExecute command to retrieve the crash and configuration files:

<AastraIPPhoneExecute>

<ExecuteItem URI="Command: UploadSystemInfo"/>

</AastraIPPhoneExecute>

For more information about using the AastraIPPhoneExecute object, see the“Aastra XML Developer’s Guide.”

Limitations• After upload is initiated there is no feedback to the user if upload was successful. If

upload fails, both the Aastra Web UI and TUI still display "File Sent".

• If the Administrator password and username are configured in the Server.cfg file, a User can retrieve that information after the Server.cfg file is loaded to the server. For security purposes, Aastra recommends using the HTTPS protocol when trans-ferring the configuration and crash files to the server.

• TFTP does not report transmission failure if the destination server is down. In this case, the Support Information files are not sent.

2. Press <Upload>. The phone immediately generates the applicable Support Information files (server.cfg, local.cfg, and/or crash.cfg) and sends the files to the pre-defined server. The message “Files Sent” displays.

22 RN-001029-05 REV 00 – 04.2010


Malaysian Tone Set and Cadences

The IP Phones now support the Malaysian tone set and tone set cadences. You can use the IP Phone UI, the Aastra Web UI, or the configuration files to set tone sets.

Configuring Malaysian Tone Set Using the IP Phone UIUse the following procedure to configure the Malaysian tone set using the IP Phone UI.

For global configuration only:

User Interface Features

IP Phone UI



3. Select Tones.

4. Select Set Ring Tone.

5. Select the type of ring tone (Tone 1 through Tone 5, or Silent).

6. Press Done to save the change.

7. Select Tone Set.

8. Select “Malaysia” for a tone set.

9. Press Done to save the change. The ring tone and tone set you select is immediately applied to the IP phone.

RN-001029-05 REV 00 – 04.2010 23


Configuring Malaysian Tone Set Using the Aastra Web UIUse the following procedure to configure the Malaysian tone set using the Aastra Web UI.

Aastra Web UI

1. Click on Basic Settings->Preferences.

2. In the "Tone Set" field, select “Malaysia”.

3. Select a value from the "Global Ring Tone" field or select a ring tone for a specific line.

Note: Refer to the <Model-Specific> IP Phone user Guide, for a table that provides the applicable ring tone settings.

4. Click to save your changes.

24 RN-001029-05 REV 00 – 04.2010


Configuring Malaysian Tone Set Using the Configuration FilesUse the following parameter to configure Malaysian tone set using the configuration files.

Malaysian Tone Set CadencesThe following are Malaysian tone set cadences.

Parameter – tone set

Tone Set(in Web UI)

IP Phone UI Options->Tones->Tone SetAastra Web UI Basic Settings->Preferences->Ring TonesConfiguration Files aastra.cfg, <mac>.cfg

Description Globally sets a tone set for a specific country.

Format Text

Default Value US

Range AustraliaBrazilEurope (generic tones)FranceGermanyItalyMalaysiaMexicoRussiaUnited Kingdom (UK)US (also used in Canada)

Example tone set: Malaysia

Tone Frequency (Hz) Cadence (on/off)

Dial 425 Continuous

Secondary Dial 425 160/160

Ringing 425 * 50 400/200/400/2000

Busy 425 500/500

Congestion 425 250/250

Call Waiting 425 100/200/100/8600

Ring Cadence - 400/200/400/2000

RN-001029-05 REV 00 – 04.2010 25


Limitations• The phone does not apply a different volume level to the first part of the call wait-

ing tone.

• The level of the 50Hz modulation signal for ring back is 90%.

Call Hold Reminder During Active Calls

In previous releases, the phone initiated a reminder ring splash when you left a call on hold after answering a second call on another line, but there was no reminder that a call was still on hold when the second call was still active.

In Release 2.6, the phones now allow a User or Administrator to enable or disable the ability for the phone to initiate a continuous reminder tone on the active call when another call is on hold. For example, when this feature is enabled, and the call on Line 1 is on hold, and then the User answers a call on Line 2 and stays on that line, a reminder tone is played in the active audio path on Line 2 to remind the User that there is still a call on hold on Line 1.

When this feature is disabled, a ring splash is heard when the active call hangs up and there is still a call on hold.

Your can enable or disable this feature using the “call hold reminder during active calls” parameter in the configuration files or in the Aastra Web UI.

26 RN-001029-05 REV 00 – 04.2010


Configuring “Call Hold Reminder During Active Calls” Using the Configuration FilesUse the following parameter to configure this feature using the configuration files.

Parameter – call hold reminder during active calls

Call Hold Reminder During Active Calls(in Web UI)

Aastra Web UI: Basic Settings->Preferences->Ring TonesConfiguration Files aastra.cfg, <mac>.cfg

Description Enables or disables the ability for the phone to initiate a continu-ous reminder tone on the active call when another call is on hold. For example, when the call on Line 1 is on hold, and the User answers a call on Line 2 and stays on that line, a reminder tone is played in the active audio path on Line 2 to remind the User that there is still a call on hold on Line 1.

When this feature is disabled, a ring splash is heard when the active call hangs up and there is still a call on hold.

Format Boolean

Default Value 0

Range 0 (disable)1 (enable)

Example call hold reminder during active calls: 1

RN-001029-05 REV 00 – 04.2010 27


Configuring “Call Hold Reminder During Active Calls” Using the Aastra Web UIUse the following procedure to configure this feature using the Aastra Web UI.

Aastra Web UI


2. In the "Call Hold Reminder During Active Calls" field, enable this feature by placing a check mark in the box.

When this feature is enabled, a reminder tone is heard on the active call when another call is on hold. When disabled, a ring splash is heard when the active call hangs up and there is still a call on hold.


Call Hold Reminder During Active Calls Parameter

28 RN-001029-05 REV 00 – 04.2010


Call Hold Reminder on Single Hold

Previously, the call hold reminder ring splash was triggered when you hung up a call and there was at least one other call on hold. The reminder ring splash timer started only when the active call hung up and there was still another call on hold.

In Release 2.6, a User or Administrator can enable or disable a feature that would start the reminder ring splash timer as soon as you put a call on hold (even when no other calls are active on the phone). When enabled, the phone initiates a reminder ring splash periodically for the single call on hold. When disabled, no reminder ring splash is audible.

You can enable or disable this feature using the “call hold reminder” parameter in the configuration files or in the Aastra Web UI.

Configuring “Call Hold Reminder” Using the Configuration FilesUse the following parameter to configure this feature using the configuration files.

Parameter – call hold reminder

Call Hold Reminder(in Web UI)

Aastra Web UI: Basic Settings->PreferencesConfiguration Files aastra.cfg, <mac>.cfg

Description Enables or disables the reminder ring splash timer to start as soon as you put a call on hold (even when no other calls are active on the phone). When enabled, the phone initiates a reminder ring splash periodically for the single call on hold. When disabled, no reminder ring splash is audible.

Format Boolean

Default Value 0

Range 0 (disable)1 (enable)

Example call hold reminder: 1

RN-001029-05 REV 00 – 04.2010 29


Configuring “Call Hold Reminder” Using the Aastra Web UIUse the following procedure to configure this feature using the Aastra Web UI.

Aastra Web UI


2. In the "Call Hold Reminder" field, enable this feature by placing a check mark in the box.

When this feature is enabled, the reminder ring splash timer starts as soon as you put a call on hold (even when no other calls are active on the phone).The phone initiates a reminder ring splash periodically for the single call on hold. When disabled, no reminder ring splash is audible.


Call Hold Reminder Parameter

30 RN-001029-05 REV 00 – 04.2010


Call Hold Reminder Timer & Call Hold Reminder Frequency Parameters

There are two parameters an Administrator can set on the IP Phones along with the “call hold reminder” and “call hold reminder during active calls” parameters:

• call hold reminder timer

• call hold reminder frequency

These parameters specify the time delay and time frequency of the ring splash that sounds when you are on an active call and have placed another call on hold. You can configure these parameters using the configuration files only.

Configuring “Call Hold Reminder Timer” Using the Configuration FilesUse the following parameter to configure this feature using the configuration files.

Notes: • You must enable the “call hold reminder” and/or “call hold reminder during active

calls” parameter(s) for the above parameters to work. • Setting “call hold reminder frequency” to zero (0) disables this feature. • Setting the “call hold reminder timer” to zero (0) disables subsequent rings.

Parameter – call hold reminder timer


Description Specifies the time delay, in seconds, that a ring splash is heard on an active call when another call was placed on hold. For example, if a call comes into Line 1, and then a call comes into Line 2 and you answer Line 2, Line 1 is automatically placed on hold. While on the active Line 2, after 7 seconds, a ring splash audio sounds on the line reminding you that the call on Line 1 is still on hold. This timer begins to increment after Line 2 is answered.

Notes:• This parameter is used with the “call hold reminder frequency”

parameter.• You must enable this “call hold reminder timer” parameter for it

to work.• A value of “0” disables the call hold reminder feature.

Format Integer

Default Value 7

Range 0 to 4294967295 seconds

Example call hold reminder timer: 10

RN-001029-05 REV 00 – 04.2010 31


Configuring “Call Hold Reminder Frequency” Using the Configuration FilesUse the following parameter to configure this feature using the configuration file

Parameter – call hold reminder frequency


Description Specifies the time interval, in seconds, between each ring splash sound on the active line. For example, if a call comes into Line 1, and then a call comes into Line 2 and you answer Line 2, Line 1 is automatically placed on hold. While on the active Line 2, after 7 seconds, a ring splash audio sounds on the line reminding you that the call on Line 1 is still on hold (determined by the “call hold reminder timer” parameter), and then the ring splash is heard again after 60 seconds (determined by this parameter).

Notes:• You must enable the “call hold reminder” and/or “call hold

reminder during active calls” parameter(s), and the “call hold reminder timer” parameter, for this parameter to work.

• A value of “0” prevents additional rings.

Format Integer

Default Value 60

Range 0 to 4294967295

Example call hold reminder frequency: 50

32 RN-001029-05 REV 00 – 04.2010


Call Waiting Tone Period

Previously, when there was an active call on a line and another call came in, a call wait-ing tone would be audible on the active call sounding only once.

In Release 2.6, a User or Administrator can specify a specific time period (in seconds) for the call waiting tone to play at regular intervals on an active call using the parame-ter “call waiting tone period”. A value of “0” is the default and plays the call waiting tone only once on the active call. When the incoming caller hangs up, the call waiting tone stops on the existing active call.

You can enable or disable this feature in the configuration files or in the Aastra Web UI.

Configuring Call Waiting Tone Period Using the Configuration FilesUse the following parameter to configure the call waiting tone period.

Parameter – call waiting tone period


Description Specifies the time period, in seconds, that the call waiting tone is audible on an active call when another call comes in. When ena-bled, the call waiting tone plays at regular intervals for the amount of time set for this parameter. For example, if set to “30” the call waiting tone plays every 30 seconds. When set to “0”, the call waiting tone is audible only once on the active call.

Format Integer

Default Value 0

Range 0 to 4294967295

Example call waiting tone period: 30

RN-001029-05 REV 00 – 04.2010 33


Configuring “Call Waiting Tone Period” Using the Aastra Web UIUse the following procedure to configure this feature using the Aastra Web UI.

Aastra Web UI


2. In the "Call Waiting Tone Period" field, enter a time period, in seconds, that the call waiting tone will be audible on an active call when another call comes in. Default is 0 seconds.

When enabled, the call waiting tone plays at regular intervals for the amount of time set for this parameter. For example, if set to “30” the call waiting tone plays every 30 seconds. When set to “0”, the call waiting tone is audible only once on the active call.


Call Waiting Tone Period Parameter

34 RN-001029-05 REV 00 – 04.2010


Per-Account Call Waiting Control

Previously, call waiting was a feature on the phone that could be set on a global-basis only. In Release 2.6, an Administrator can now set call waiting on a per-line basis using the configuration files or the Aastra Web UI.

Configuring Call Waiting Per Account Using the Configuration FilesUse the following parameter to configure call waiting on a per-account basis.

Global Setting

Per-Line Setting

Parameter – call waiting

Call Waiting(in Web UI)

Aastra Web UI Advanced Settings->Global SIP->Basic SIP Authentication Settings


Description Enables and disables call waiting on a global basis on the phone.

Format Boolean

Default Value 1

Range 0 - Disables call waiting on the phone for all lines.1 - Enables call waiting on the phone for all lines.

Example call waiting: 1

Parameter – sip lineX call waiting

Call Waiting(in Web UI)

Aastra Web UI Advanced Settings->Line X->Basic SIP Authentication Settings


Description Enables and disables call waiting on a per-line basis on the phone.

Format Boolean

Default Value Global

Range Global - Sets call waiting on a global basis on the phone.0 - Disables call waiting on the current line only.1 - Enables call waiting on the current line only.

Example sip line1 call waiting: 1

RN-001029-05 REV 00 – 04.2010 35


Configuring Call Waiting Per Account Using the Aastra Web UIUse the following procedure to configure this feature using the Aastra Web UI.

Aastra Web UI

1. Click on Advanced Settings->LineX.

2. In the "Call Waiting" field, select enabled to enable call waiting on the line. Valid values are:• Global - Sets call waiting on a global basis on the phone• disabled - Disables call waiting for the current line• enabled - Enables call waiting for the current line.


The setting immediately takes affect on the phone.

Call Waiting per-line Parameter

36 RN-001029-05 REV 00 – 04.2010


Successful Transfer Indication

Previously, when a call transfer was made on the phone, and the transfer failed, a mes-sage displayed indicating that the transfer had failed. However, if a call transfer was successful, no message displayed indicating the successful transfer.

In Release 2.6, the phone now displays a message when a call transfer is successful. After the call transfer is complete, the following message now displays for 5 seconds:

“Call Transferred”.

Errors Messages Display when Incorrect Network Settings

Previously, when an Administrator entered incorrect network settings for specific parameters, the phone did not notify the User that the settings were incorrect. Even when the phone rebooted it accepted the parameters but ignored the incorrect set-tings. These errors include:

• A 0.0.0.0 entered as values for the IP Address, Subnet Mask and Gateway parame-ters

• IP Address and Gateway IP address parameter values entered exactly the same

• Gateway IP address and the IP address parameter values configured on the same subnet

In Release 2.6, the IP Phone UI AND the Aastra Web UI now immediately notify the Administrator if an incorrect value is being entered for the above network parameters in the IP Phone UI and the Aastra Web UI. If you configure the Gateway parameter and the IP Address parameter on the same subnet, the following error message displays:

“Gateway IP address and the IP address parameter values configured are not on the same subnet”

RN-001029-05 REV 00 – 04.2010 37


Switching Between Early Media and Local Ringing

Previously, the phone generated a local ring tone when receiving a 180 response unless early media was being played, regardless of SDP. The local ring tone stopped when the first RTP packet was received in the early session. The local ring tone did not resume when it received subsequent 180 responses, even though early media was not being received.

In Release 2.6, the phone supports switching between early media and local ring tone. Upon receiving a 180 response, the phone now generates a local ring tone unless it is receiving an early media flow. If the phone receives any subsequent 180 responses, it regenerates the local ring tone unless it is receiving early media flow.

Added “Call-Info” Header to 200ok Responses for Shared Call Appearance (SCA) Lines

In previous IP phone software releases, a "Call-Info" header was only added to the requests generated by the phone for Shared Call Appearance (SCA) lines. In Release 2.6, a “Call-Info” header is now also included in the 200ok response to an INVITE, RE-INVITE, and UPDATE messages for SCA lines. No configuration is required for this fea-ture.

SIP Features

38 RN-001029-05 REV 00 – 04.2010


Connected Action URI

Previously, on the phones there was no way for XML developers to specify a con-nected event in the XML scripts. The XML script had no way of knowing when a call was connected.

In Release 2.6, a new parameter called “action uri connected” (configuration files) and “Connected” (Aastra Web UI) now allows XML scripts to determine when a call is connected. When enabled, the phone triggers an HTTP GET when it goes into the “connected” state. This includes regular phone calls, intercom calls, paging calls, RTP streaming, and the playing of a WAV file. It is also triggered when the phone estab-lishes the second leg of a 3-way call.

Configuring the Connected Action URI Using the Configuration FilesUse the following parameter to configure the phone to use the Connected Action URI.

XML Features

Parameter– action uri connected

Connected(in Web UI)

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

Description Specifies the URI for which the phone executes an HTTP GET when it goes into the “connected” state. This includes regular phone calls, intercom calls, paging calls, RTP streaming, and the playing of a WAV file. It is also triggered when the phone establishes the second leg of a 3-way call. This parameter uses the following variables to determine the state of the line:$$REMOTENUMBER$$$$DISPLAYNAME$$$$SIPUSERNAME$$$$SIPAUTHNAME$$$$INCOMINGNAME$$$PROXYURL$$$$LINESTATE$$$$LOCALIP$$$$DISPLAYNAME$$$$CALLDURATION$$$$CALLDIRECTION$$$$REGISTRATIONSTATE$$$$REGISTRATIONCODE$$

RN-001029-05 REV 00 – 04.2010 39


Configuring the Connected Action URI Using the Aastra Web UIUse the following procedure to configure the Connected Action URI using the Aastra Web UI.

Format Fully qualified HTTP URI

Default Value Not applicable

Range Up to 128 ASCII characters

Example action uri connected: http://www.example.com/connect.php

Aastra Web UI

1. Click on Advanced Settings->Action URI-> Events.

2. Enter an XML URI for a connected event in the “Connected” field. For exam-ple:http://www.example.com/connect.php

This parameter specifies the URI for which the phone executes a GET on when a connected event occurs.


Connected Parameter

40 RN-001029-05 REV 00 – 04.2010


Limitations• During SLA calls, the phone uses the Action URI Connected parameter when the

line is seized before the caller dials out.

• SCA and BLA calls on hold trigger the Action URI Connected parameter, since the retrieval is a 2nd call by the phone, and the phone cannot link the retrieved call with the earlier held call.

For more information about the XML API objects, see Aastra’s XML Developers Guide.

New “DialLine” URI Command

In Release 2.6, a new “DialLine” URI command can be used with the AastraIPPhone-Execute object. This URI command allows an XML application to select the line to use to perform a “dial” event. This command complements the current “Dial:” URI which uses the first available line.

If a value is specified for this command, the phone uses this value to select the line for dialing. If no value is specified, the phone uses the first available line on the phone by default. You must use the following format in an XML script when using the “DialLine” command:

DialLine:<SIP line>:<dial string>

where

• DialLine is the URI command

• <SIP line> is a line 1 to 9 depending on the phone model and the lines configured on the SIP account, and

• <dial string> is the URL to dial.

ExampleThe following is an example of the AastraIPPhoneExecute object using the “Dial-Line” command.

<?xml version="1.0" encoding="UTF-8"?><AastraIPPhoneExecute>

<ExecuteItem URI="DialLine:1:3230" /> <ExecuteItem URI="DialLine:5:[email protected]" />

</AastraIPPhoneExecute>

Note: The “DialLine” URI command may also be used with other XML objects where a URI is processed, for example as a softkey or a menu item.

RN-001029-05 REV 00 – 04.2010 41


XML Schema

The following is the XML schema definition for the new dial tag:< xs:element name="Dial" type="xs:string" minOccurs="0" maxOccurs="1">

< xs:complexType> < xs:attribute name="line" use="optional">

< xs:simpleType>

< xs:restriction base="xs:integer"> < xs:minInclusive value="1" />

< xs:maxInclusive value="9" />

< /xs:restriction> < /xs:simpleType>

< /xs:attribute>

< /xs:complexType>< /xs:element>

Although the line range is defined as 1 to 9, you must have a SIP account configured on the line to use the dial tag. For example, if you configure lines 1 to 4 on a phone, then using a line value of 5 results in undefined behaviour. The range of lines you can use for values is limited to the number of lines that the phone supports. The following table identifies the number of lines supported on each phone type.

Limitations• The Directory object does not support the dial tag and new “DialLine” attribute.


Phone Max Line

6751i 1

6730i, 6731i 6

6753i, 6755i, 6757i, 6757i CT, 9143i, 9480i, 9480i CT

9

42 RN-001029-05 REV 00 – 04.2010


New “Line” Parameter in the Dial Tag for AastraIPPhoneTextMenu Object

In Release 2.6, an XML Developer can now define which SIP line to use when using the “dial” tag in the AastraIPPhoneTextMenu object instead of having the phone selecting the first available line. The AastraIPPhoneTextMenuItem object now supports:

<MenuItem base = ”http://base/” icon = “icon index” ><Prompt>Choice</Prompt>

<URI>http://somepage.xml</URI>

<Dial line=”SIP line”>Number to dial<Dial><Selection>Selection</Selection>

</MenuItem>

ExampleIn the following example, when the User selects the second item in the menu and presses the “Dial” key, the phone dials “6789” using the first available SIP line. If the User presses the “Dial2” key, the phone dials the same number but using line 2 or the first available line if line 2 is not available.

<?xml version="1.0" encoding="ISO-8859-1"?><AastraIPPhoneTextMenu destroyOnExit="yes">

<Title>Title</Title><MenuItem>

<Prompt>Choice 1</Prompt><URI>Dial:1234</URI><DialLine=”2”>1234</Dial>

</MenuItem><MenuItem>

<Prompt>Choice 2</Prompt><URI>Dial:6789</URI><DialLine="2">6789</Dial>

</MenuItem><SoftKey index=“1”>

<Label>Dial</Label><URI>SoftKey:Dial</URI>

</SoftKey><SoftKey index=“2”>

<Label>Dial2</Label><URI>SoftKey:Dial2</URI>

</SoftKey><SoftKey index=“6”>

RN-001029-05 REV 00 – 04.2010 43


<Label>Exit</Label><URI>SoftKey:Exit</URI>

</SoftKey></AastraIPPhoneTextMenu>


AastraIPPhoneInputScreen Object Supports Up to 10 fields in “Normal” Mode

An Administrator can now use the AastraIPPhoneInputScreen object in an XML appli-cation to input up to 10 fields (normal mode) and up to 5 fields (condensed mode) in the same object. Previously only 6 fields were allowed in normal mode.

ExampleThe following example displays a screen with ten input fields (field1 to field10):

<?xml version="1.0" encoding="ISO-8859-1"?><AastraIPPhoneInputScreen type="string" destroyOnExit="yes">

<Title>AastraIPPhoneInputScreen</Title>

<URL>http://myserver.com/myxml.php </URL>

<InputField type="string"/><Prompt>Field1:</Prompt>

<Parameter>param1</Parameter>

</InputField><InputField type="string"/>

<Prompt>Field2:</Prompt>




<Parameter>param3</Parameter></InputField>

<InputField type="string"/>

Note:This enhancement for the AastraIPPhoneInputScreen object applies only to the phones which support multiple input fields (Aastra 6755i, 6757i, 6757iCT, 9480i and 9480iCT).

44 RN-001029-05 REV 00 – 04.2010


<Prompt>Field4:</Prompt><Parameter>param4</Parameter>

</InputField>








</InputField>








</InputField>

</AastraIPPhoneInputScreen>


RN-001029-05 REV 00 – 04.2010 45

Issues Resolved in Release 2.6

Issues Resolved in Release 2.6This section describes the issues resolved on the IP Phones in Release 2.6. The follow-ing 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

SIP

CLN20865 The phone was configured to use BLF/list. When a subscription renewal for BLF/list was sent, it got rejected with a “481 Transaction does not exist”. The phone terminated the subscription and did not retry it.

This is now corrected.

DEF18021 A robustness issue related to handling of multiple calls initiated by a third party Computer-Telephony Integration (CTI) is corrected now.

DEF18140 If there are two Users with different numbers that have the same Calling Line ID, the signalling for BLF list comes in only on the first BLF list key. This is now corrected. The signalling now comes in on both User’s BLF list keys as expected.

DEF19276 When using the “as-feature-event” on the phone, and then you changed the DND state, the phone sent an incorrect SUBSCRIBE message.


DEF20271 Phone was sending incorrect remote identity when a call on a BLA line was put on hold.


DEF20707 The phone did not allow duplicate Network Policy type-length-values (TLVs) in the Link Layer Discovery Protocol for Media Endpoint Devices (LLDP-MED) frame for voice signalling.

This has now been corrected.

DEF21127 The phone did not send a re-subscription for BLF if a previous subscription received a 403.


46 RN-001029-05 REV 00 – 04.2010


ENH18198 When the phone played the remote RTP stream on a 183 Call Progress (with SDP), it was not able to come back to the local ring back tone when it received a 180 Ringing (without incoming RTP stream).

This is now corrected. The phone now switches to local ringing when it receives a 180 after a 183.

User Interface

DEF17996DEF19981

Intermittently, dial tone was heard in the background during an active call on Aastra phones.

This is now corrected. A dial tone is no longer heard on the voice path of an active call.

DEF20386 6730i & 6731i: The phone stopped sending audio on the headset mode after a user retrieved a call on hold.


DEF20679 When a call came into the phone, the display showed the correct calling number but an incorrect calling name. If the call that came in had a stored name in the phone’s Directory, the name displayed correctly but displayed an incorrect calling number.


DEF20694 After repeated use of the Icom key on the phone, the key stopped working.


DEF20817 The phone was not processing a pause in the speeddial correctly if “Suppress DTMF Playback” was enabled on SCA lines.

This is now corrected. The phone processes the pause correctly.

DEF20928 On some intercom calls, the phone showed “No Lines Available.”


DEF20954 XML: The LED for an XML Callers List key did not flash after an incoming call was received. When the AastraIPPhoneExecute was pushed to the phone instructing it to turn on the LED, it wouldn’t turn on until the user performed an action on the phone.

This is now corrected. The XML Callers List key now flashes as expected when an incoming call is received.

DEF21016 The HTTP digest authentication feature was not working correctly. The phone was not sending a GET request after sending the default username and pass-word.

This issue is now corrected.


RN-001029-05 REV 00 – 04.2010 47


DEF21030 For Shared Call Appearance (SCA) lines, If a user pressed an intercom softkey or programmable key while an SCA line was already open, phone incorrectly closed the line instead of switching it to the intercom open line.


DEF21067 If a user pressed a Generic line key while an SCA line was already open, the phone incorrectly closed the SCA line instead of switching it to the Generic open line.


Configuration

DEF19765 6731i: Ethernet port settings other than auto-negotiation were not working correctly for the 6731i phones.

This issue is now corrected.

DEF21170 6757i: The phone failed to send DNS queries for the configuration server in a specific setup scenario.


Troubleshooting

CLN20442 The Network Packet Loss Rate (NLR), Burst/Gap densities and durations were incorrect. For example, on an inbound call to the IP phone the NLR was always zero, regardless of how many packets were lost. The NLR value for an out-bound call from the IP phone was non-zero, but the value was lower than expected.


DEF17362 RTCP-XR Feature: Signal level reported by the phone was low compared to the expected value.

Signal level reported by phone now meets the expected value.

DEF20715 RTCP-XR reports sent by the phone were missing Quality Mean Opinion Scores (MOS) information. This issue is now fixed.


48 RN-001029-05 REV 00 – 04.2010

Contacting Aastra Telecom Support

Contacting Aastra Telecom SupportIf you’ve read this release note, and consulted the Troubleshooting section of your phone model’s manual and still have problems, please contact Aastra Telecom Support via one of these methods:

North America• Toll Free 1-800-574-1611

• Direct +1-469-365-3639

• Online at http://www.aastratelecom.com/support, click on Contact Technical Support

Outside North America• Please contact your regional Aastra Technical Support.

RN-001029-05 REV 00 – 04.2010 49

http://www.aastratelecom.com/support

Disclaimer

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 © Aastra Telecom, www.aastra.com.

Documents

V2.6.0, May 2010, pdf