Aastra Models 9000i and 6700i Series SIP IP Phones - Mitelgts.aastra.com/publish/mx-one/TeleSys/Version5/ServicePack/fw/A67... · Aastra Models 6700i and 9000i Series SIP IP Phones

Aastra Models 6700i and 9000i Series SIP IP Phones

SIP 3.3.0 Hot Fix 1 Release Notes

RN-001037-03 REV01 – 06.2012

Content

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.3.0 Hot Fix (HF)1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Release notes topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release content information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Hardware supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Bootloader requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Before you upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

New Features in Release 3.3.0 HF1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5SIP Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7XML Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92048-Bit Certificate Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Transfer VLAN ID Assignment Using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Support for Partial URL in Firmware Server Parameter . . . . . . . . . . . . . . . . . . . . . . 12

SIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Call Failed Message Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14BLF Page Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Ring Signal Type for BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17BLF Hold State - Support for Directed Call Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . 23Edgewater Local Mode Support for BLA and SCA . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Blind Transfer to a Contact in Phone Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25ININ Callpark/Pickup Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

II RN-001037-03 REV01 – 06.2012

Content

User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38PIN and Authorization Code Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Scrolling Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Displayed Directory Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Increased Number of Displayed Characters for Softkey Line Labels. . . . . . . . . . 42Configurable Display for Blank BLF/List Softkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Additional Italy and Updated Slovakia Tone Sets and Cadences. . . . . . . . . . . . . 44

Issues Resolved in Release 3.3.0 HF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Contacting Aastra Telecom Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

RN-001037-03 REV01 – 06.2012 III

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.3.0 Hot Fix (HF)1

About this documentThis document provides new features for the 6700i Series SIP IP Phones (6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT) and the 9000i Series SIP IP Phones (9143i, 9480i, 9480i CT) for release 3.3.0 HF1.

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

For detailed information about more advanced features, see the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and/or the Development Guide XML API For Aastra SIP Phones Firmware 3.3.0.

Release notes topicsTopics in these release notes include:

• General information

• New Features in Release 3.3.0 HF1

• Additional Information

• Issues Resolved in Release 3.3.0 HF1

• Contacting Aastra Telecom Support

Notes:1. This release applies to the phone models mentioned above only.2. 6735i and 6737i are not supported in this release.

1 RN-001037-03 REV01 - 06.2012

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes

General information

Release content information

This document provides release content information on the Aastra 9000i and 6700i Series SIP IP Phone firmware.

Hardware supported

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

Model Release name Release version Release filename Release date

6730i Generic SIP 3.3.0 HF1 FC-001319-02-REV01 June 2012






6757i CT Generic SIP 3.3.0 HF1 FC-001324-02-REV01 June 2012



9480i CT Generic SIP 3.3.0 HF1 FC-001327-02-REV01 June 2012

673xi Models 675xi Models 9xxxi Models

6730i 6753i 9143i

6731i 6755i 9480i

6739i 6757i 9480i CT

6757i CT

RN-001037-03 REV01 – 06.2012 2

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.3.0

Bootloader requirements

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

673xi Models 675xi Models 9xxxi Models

6730i: Bootloader 2.4.0.80 or higher








9480i CT: Bootloader 2.2.0.166 or higher

6757i CT: Bootloader 2.0.1.1055 or higher

3 RN-001037-03 REV01 – 06.2012

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes

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 Models 9000i and 6700i Series SIP IP Phones 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 Models 9000i and 6700i Series SIP IP Phones 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 Models 9000i and 6700i Series SIP IP Phones 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 Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

Note:The following information applies to all IP phones EXCEPT the 6739i.

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

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

RN-001037-03 REV01 – 06.2012 4

New Features in Release 3.3.0 HF1

New Features in Release 3.3.0 HF1This section provides the new features in SIP IP Phone Release 3.3.0 HF1. These new features apply to all of the Aastra IP Phones, unless specifically stated otherwise.

The following table summarizes each new feature and provides a link to more infor-mation within this Release Note. Each feature also specifies whether it affects the Administrator, the User, or the XML Developer.

This table may also provide the documentation location of features that have already been documented in Aastra’s documentation suite. Refer to those documents for more information about the applicable feature.

Feature Description

Configuration Features

2048-Bit Certificate Handling

(For Administrators)

An improvement has been made to the Verisign certificate support on the IP phones. The phones now support 2048-bit certificates. Also, in case of a certificate error, detailed descriptions can now be found from the error message list in the phone status menu.*New for all phones

Transfer VLAN ID Assignment Using DHCP


There are now two ways of transporting the VLAN ID parameter in the DHCP: By DHCP Option 43 or by Option 132.Now when the phone receives the VLAN ID from the DHCP and the value is different from the one used by the phone to trigger the DHCP request, the phone sends a new DHCP request in the new VLAN without rebooting. The phone will remember the VLAN ID obtained by DHCP options so that on a reboot, the phone will send a DHCP request using the correct VLAN. Administrators can use the new “dhcp option 132 vlan id enabled” parameter for transporting the VLAN ID parameter by DHCP Option 132. If using DHCP Option 43, the phone will get the VLAN ID param-eter from the new Option 43 values.*New for all phones

Support for Partial URL in Firmware Server Parameter


The “firmware server” parameter can now specify a partial URL of a server (other than the original configuration server) from which the phones in the network get their firmware. *New for all phones

5 RN-001037-03 REV01 – 06.2012


SIP Features

Call Failed Message Improvements


Administrators can place certain restrictions on users for making outgoing calls. Previously when a restriction was active and a user dialed a number that was not allowed, the PBX sent a certain status code (4xx) and the phone displayed “Call Failed” or “Busy”, which is not very informative to the user. Now when an outgoing call fails with a status code 4xx or 5xx, the phone will look for the Reason Header (RFC 3326) in the status mes-sage and display the Reason Header to the user. The reason text is displayed in the center of the screen and is limited to 20 characters. *New for all phones

BLF Page Switch

(For Users and Administrators)

A new feature enables the 6755i, 6757i, 6757i CT, and 6739i model phones to automatically switch the screen focus to a softkey page or M675i expansion module page that has an active Busy Lamp Field (BLF) or BLF/List key(s). Administrators can configure this feature using the new “blf activity page switch” parameter. *New for 6755i, 6757i, 6757i CT, & 6739i only

Ring Signal Type for BLF


Currently there is a global parameter “play a ring splash” that con-trols whether or not a ring splash is played when there is an incom-ing call on a Busy Lamp Field (BLF) monitored extension. If the host tone is Idle, the tone plays a ring splash. Now in 3.3.0 HF1, administrators can control the ring splash alert pattern on a per key basis. Each type of key can have a different ring splash alerting pattern and volume. *New for all phones

BLF Hold State - Support for Directed Call Pickup


The phones support the BLF hold state that is expressed by a slow flashing LED. Previously, if a user pressed the slow flashing key, the phone sent an INVITE message to the extension number of the mon-itored extension and the call could fail because the extension was busy (on hold).Now in 3.3.0 HF1, if administrators configure BLF for Directed Call Pickup, users are able to pickup the held call, as the phone sends the directed call pickup prefix to the extension number. *New for all phones

Edgewater Local Mode Support for BLA and SCA


Previously, if the phone was configured for Bridged Line Appear-ance (BLA) and shared Call Appearances (SCA), it would send a SUB-SCRIBE message to get a dial tone to make a call. If the Edgewater Edgemarc box lost WAN Internet connectivity, the phone went into local mode. Now in 3.3.0 HF1. when the phone looses connection (i.e. is in local mode) with the Edgewater device, the phone goes into a “generic” mode instead of BLA mode to ensure users are able to make and receive calls (and the phone does not need to send the SUBSCRIBE message to get a dial tone to make a call). Once the phone gets con-nected (i.e. leaves the local mode) with Edgewater, the phone switches back to its original BLA mode.*New for all phones

Feature Description

RN-001037-03 REV01 – 06.2012 6


Blind Transfer to a Contact in Phone Directory

(For Users)

Users can now complete a blind transfer to a contact in their local directory. If a user is in a call and initiates a transfer, they can navi-gate to the Directory screen where a new Transfer key can be pressed to complete a blind transfer. *New 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, & 6757i CT only

ININ Callpark/Pickup Support


The IP phones (including the CT handsets) have a park and pickup call feature that allows you to park a call and pickup a call when required. Administrators can now configure the callpark and pickup feature for use with ININ servers.*New for all phones

User Interface Features

PIN and Authorization Code Sup-pression


Certain features on MX-ONE require a PIN/authorization code to be entered on the phone (e.g. to register, for authorization, lock-ing/unlocking, or accounting).Administrators can now configure the “pin suppression dial plan” parameter so that if such a feature code with a PIN is entered, the PIN does not show up in any of the phone logs (i.e. redial list) nor is it displayed on the screen during a call. The pin will be masked with wildcard characters. *New for all phones

Scrolling Phone Numbers

(For Users)

Previously, if a long remote (outgoing or incoming) number was dis-played on the phone, users were not able to scroll to the end of the number. Users now have the ability to scroll through a remote number that is displayed on the phone. Users can press the scroll down navigation key to view the rest of the phone number content. *New for 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9480i, & 9480i CT only

Displayed Directory Instructions

(For Users)

Previously on the 6730i, 6731i, and 6753i model phones, procedures on how to modify directory entries were not specified. There is now a line on the screen that explains how to edit a directory entry. *New for 6730i, 6731i, 6753i, & 9143i only

Increased Number of Displayed Characters for Softkey Line Labels


Administrators can now disable line state icons to display 10 charac-ters on softkeys and top softkeys for line labels on 6755i, 6757i, and 6757i CT model phones. This is useful if the user wants to display a full 10 digit number as the softkey label, instead of a shortened label containing only 7 digits followed by ellipsis characters. *New for 6755i, 6757i, & 6757i CT only

Configurable Display for Blank BLF/List Softkeys


Previously, when softkeys for the 6755i, 6757i, 6757i CT model phones and the M675i Expansion Module were configured as BLF/List keys on the phone but there were not enough members in the BLF/List on the BroadSoft BroadWorks server side, then a series of question marks would be displayed on screen beside some of the softkeys.Administrators can now configure whether or not the series of ques-tion marks should be hidden using the new “keys noname hidden” parameter.*New for 6755i, 6757i, 6757i CT, & M675i Expansion Module only

Feature Description

7 RN-001037-03 REV01 – 06.2012


Additional Italy and Updated Slova-kia Tone Sets and Cadences

(For Administrators and Users)

The IP phones now support an additional Italy tone set with corre-sponding cadences. Additionally, the Slovakia tone set has been updated with revised cadences.*New for all phones

XML Features

LED and Key Management

(For XML Developers)

For more information, refer to the:• Aastra XML Developer’s Guide*New for all phones

XML Call Log Display


For more information, refer to the:• Aastra XML Developer’s Guide*New for 6739i only

Control of the Icons in the Phone Status Bar



Input data with an XML InputScreen Object



XML Server Redundancy Support



XML Lockin Enhancement



Configurable Colors in Menus and Input Screens and Buttons



True Custom Icons



Use of Red Key in XML Pages with “lockin” Parameter Activated



Feature Description

RN-001037-03 REV01 – 06.2012 8

Additional Information


2048-Bit Certificate Handling

An improvement has been made to the Verisign certificate support on the IP phones. The phones now support 2048-bit certificates. Also, in case of a certificate error, detailed descriptions can now be found from the error message list in the phone sta-tus menu.

The following error descriptions are now available:

• No Certificate

• Bad Certificate

• Unsupported Certificate

• Certificate Revoked

• Certificate Expired

• Certificate Unknown

Configuration Features

9 RN-001037-03 REV01 – 06.2012


Transfer VLAN ID Assignment Using DHCP

There are now two ways of transporting the VLAN ID parameter in the Dynamic Host Configuration Protocol (DHCP):

• By DHCP Option 43 (vendor specific information)

• By DHCP Option 132 (802.1P VLAN ID)

Now when the phone receives the VLAN ID from the DHCP and the value is different from the one used by the phone to trigger the DHCP request, the phone reboots and then sends a new DHCP request in the new VLAN. The phone will remember the VLAN ID obtained by DHCP options so that on a reboot, the phone will send a DHCP request using the correct VLAN.

If using DHCP Option 43 to transfer VLAN ID assignment the following sub-options are utilized. Additionally, the corresponding rules must be followed:

Alternatively, administrators can use the “dhcp option 132 vlan id enabled” parame-ter to enable the VLAN ID assignment transfer using DHCP feature. Option 132 pro-vides the same functionality as Option 43 and the data format of the VLAN ID value is identical to the format listed for Option 43 sub-option 09 in the table above.

Precedence• LLDP values should have precedence over the DHCP

• DHCP values should have precedence over the configuration files

• DHCP should have precedence over the Local values (configured by the Local MMI of the phone)

• DHCP Option 43 should have precedence over DHCP Option 132

Sub-Option/Code Description Rule

08 ID string to enable the use of the VLAN identity in sub-option/code 09. Must be spec-ified to avoid conflict with other vendors.

Must be the 16-byte character string “Aastra{space}Tele-com{space}{space}” (i.e. Aastra Telecom followed by two space characters).

16-byte hex equivalent: 4161737472612054656c65636f6d2020

09 VLAN ID value Must be 4 bytes, whereas the first and second byte must be 0x00, and the third and fourth bytes encompass the VLAN ID. The valid range of the VLAN ID is 1 - 4094.

For example, a VLAN ID of 100 (in dec) is 00 00 00 64 in hex.

RN-001037-03 REV01 – 06.2012 10


Configuring VLAN ID Assignment Using DHCP Option 132Use the following parameter to configure the VLAN ID parameter using DHCP Option 132:

Parameter– dhcp option 132 vlan id enabled

Configuration Files aastra.cfg, <model>.cfg, <mac>.cfg

Description Enables the phone to transport the VLAN ID parameter in the DHCP protocol. When the phone receives the VLAN ID from the DHCP and the value is different from the one used by the phone to trigger the DHCP request, the phone reboots and then sends a new DHCP request in the new VLAN. The phone will remember the VLAN ID obtained by DHCP options so that on a reboot, the phone will send a DHCP request using the correct VLAN.

Format Integer

Default value 1 (enabled)

Range 0-10 (disabled)1 (enabled)

Example dhcp option 132 vlan id enabled: 0

11 RN-001037-03 REV01 – 06.2012


Support for Partial URL in Firmware Server Parameter

The “firmware server” parameter can now specify a partial URL of a server (other than the original configuration server) from which the phones in the network get their firmware.

When the “firmware server” parameter specifies a full URL path, the phones in the network get the security.tuz, aastra.cfg, <model>.cfg, and <mac>.cfg files from the original configuration server, and the firmware files from the server specified in the URL used to load the firmware. For example, firmware server: ftp://username:[email protected]:port/path

When the “firmware server” parameter specifies a partial URL path, the configuration server that is linked to the partial path is used to load the firmware. For example, firmware server: /path

When there is no “firmware server” parameter (or if it is empty), the original configu-ration server is used to load the firmware.

RN-001037-03 REV01 – 06.2012 12


To Configure Multiple Configuration Server SupportUse the following parameter to specify a server other than the original configuration server from which the phones get their firmware:

Parameter– firmware server


Description Specifies either a full or partial URL of a server (other than the original configuration server) from which the phones in the network get their firmware.

Note: The default method for the update of firmware to the phones is from the original configuration server. The Administrator must specify a correct server URL for the phones to get their firmware information from that server. If the URL is incorrect, no firmware download occurs to the phones from the specified server.

Format String (up to 256 characters)

Full URLs:FTP“ftp://username:[email protected]:port/path”

TFTP“tftp://0.0.0.0:port/path”

HTTP“http://0.0.0.0:port/path”

HTTPS“https://0.0.0.0:port/path”

Partial URL“/path”

Default Value Blank

Range Not Applicable

Example firmware server:

Leaving this parameter blank downloads all configuration and firmware files from the original configuration server.

firmware server: tftp://10.30.102.158/test1

The above example uses TFTP to download all firmware files that exist in the “test1” directory on the specified server, to the phones.

firmware server: /path

The above example uses the configuration server that is linked to the partial path to load the firmware.

13 RN-001037-03 REV01 – 06.2012


Call Failed Message Improvements

Administrators can place certain restrictions on users for making outgoing calls (e.g. only allow national calls, only allow internal calls, only allow emergency calls, etc.). Previously when a restriction was active and a user dialed a number that was not allowed, the PBX sent a certain status code (4xx) and the phone displayed “Call Failed” or “Busy”, which was not very informative to the user.

Now when an outgoing call fails with a status code 4xx or 5xx, the phone will look for the Reason Header (RFC 3326) in the status message and display the Reason Header to the user. The reason text is displayed in the center of the screen and is limited to 20 characters.

If there is a Reason Header in the status code message, the reason text (if any) will be displayed on the phone. The tone that is played follows the status code (i.e. the busy tone for 486 and 503, and the call failed tone for all others).

If there is no Reason Header in the status message, the behaviour of the phone should be unchanged:

• “Busy” is displayed for the status codes 486 and 503 (SERVICE UNAVAILABLE) and the busy tone will be played,

• or “Call Failed” is displayed for status codes 4xx to 5xx and the call failed tone will be played,

• or “Not Configured” or “Seize Failed” is displayed in case of an internal error,

• or “Unavailable” is displayed in case of codeless support (6755i, 6757i, 6757i CT, 9480i, and 9480i CT phones only).

SIP Features

RN-001037-03 REV01 – 06.2012 14


BLF Page Switch

A new feature enables the 6755i, 6757i, 6757i CT, and 6739i model phones to auto-matically switch the screen focus to a softkey page or an M675i expansion module page that has an active Busy Lamp Field (BLF) or BLF/List key(s). Administrators can configure this feature using the new “blf activity page switch” parameter.

If this parameter is set to “1”, the screen will switch to a softkey page or an M675i expansion module page if a monitored extension transitions to a ringing (fast flash-ing) state. If this parameter is set to “2”, the screen will switch if a monitored extension transitions to either a ringing (fast flashing) or a hold (slow flashing) state. Finally, if this parameter is set to “3”, the screen will switch if a monitored extension transitions to either a ringing or hold state OR from an idle (off ) state to an “in call” (solid) state.

The following can be observed with this new feature:

• If there is a lot of activity on the monitored extensions, the page will be shown on the screen for at least 5 seconds before switching again. When a user manually scrolls through the pages by pressing the More key or the Function key on the M675i, no activity-triggered page flipping should occur for 5 seconds after the manual switch.

• If the phone softkeys are hidden by an overlay screen, such as an XML UI object, a menu (e.g. the Services, Directory, or Callers List menu), or if the phone is in an active call, the screen will not automatically switch focus to a softkey page with BLF activity (it will, however, for an expansion module page).

• When the phone is in Idle mode, the menu switches to the page with the BLF key when there is an incoming call to the monitored extension. The page is shown for 10 seconds if the call is answered. If the call is not answered by the BLF extension, the BLF key page will be shown as long as ringing is ongoing.

• When the BLF key page is shown and there is another incoming call on another BLF key on the same page, the new call is also shown on this BLF key.

• When the BLF key page is shown and there is another incoming call on another BLF key on another page, the switch to the other page will be done after 10 seconds.

• When the BLF key page is shown and there are several more incoming calls on BLF keys, after 10 seconds the next active BLF key will be shown in the key number order.

15 RN-001037-03 REV01 – 06.2012


Configuring BLF Page SwitchUse the following parameter to configure the BLF page switch feature:

Notes:1. To minimize the chance of a lot of switching between the Idle screen and the page(s) with BLF keys, it is recommended to have the BLF keys with the most fre-quent traffic on one page.

2. If the expansion module has several BLF keys, it is recommended to use an extra display panel unit.

Parameter– blf activity page switch


Description Enables the phone to automatically switch the screen focus to an expansion module or softkey page that has BLF activity.

Format Integer

Default value 0 (disabled)

Range 0-30 (disabled)1 (switch page if monitored extension transitions to ringing (fast

flashing) state)2 (switch page if monitored extension transitions to either ringing

(fast flashing) or hold (slow flashing) state)3 (switch page if monitored extension transitions to either ringing or

hold state OR from idle (off ) state to “in call” (solid) state)

Example blf activity page switch: 1

RN-001037-03 REV01 – 06.2012 16


Ring Signal Type for BLF

Currently there is a global parameter “play a ring splash” that controls whether or not a ring splash is played when there is an incoming call on a Busy Lamp Field (BLF) mon-itored extension. If the host tone is Idle, the tone plays a ring splash.

Now in 3.3.0 HF1, administrators can control the ring splash alert pattern on a per key basis. Each type of key can have a different ring splash alerting pattern and volume. When the phone UI receives the event update from the line manager for BLF transi-tions to ringing state, the ring splash value is checked to take the appropriate action.

The following alerting patterns are available:

• Silence (Ring splash is off ).

• Normal splash (Same as current BLF ring splash).

• Normal - delayed (After a delay of (x) seconds, the normal ring splash is played).

• Periodic (Similar to the normal ring signal that is used by the phone itself. The actual ring melody is based on the current melody set for the line where the BLF key is associated to).

• Periodic - delayed (After a delay of (x) seconds, the ring signal that is used by the phone is played - see above).

• One low volume splash (Same as the current BLF ring splash but at a lower level to be less intrusive).

• One low volume splash - delayed (After a delay of (x) seconds, the ring signal that is the same as the current BLF ring splash is played at a lower level).

The following new parameters have been added to allow administrators to set and pass the control of the ring splash to the key (instead of the phone using the global “play a ring splash” parameter).

• “prgkeyN ring splash”

• “softkeyN ring splash”

• “topsoftkeyN ring splash”

• “expmodX KeyN ring splash”

• “ring splash delay”

• “ring splash volume”

The per key settings overwrite the global setting (“play a ring splash” parameter) on the phone. If the global parameter is disabled, a ring splash can still be enabled on a key basis. If the global parameter is enabled, all keys will have a ring splash unless the value “0” is configured explicitly for a key.

17 RN-001037-03 REV01 – 06.2012


Configuring Ring Splash On a Per Key Basis Use the following parameters to configure the ring splash on a per key basis:

Parameter– prgkeyN ring splash


Description Controls the ring splash alert pattern per programmable key. The following alerting patterns are available:• Silence (Ring splash off.)• Normal splash (Same as current BLF ring splash.)• Normal - delayed (After a delay of (x) seconds, the normal ring

splash is played.)• Periodic (Similar to the normal ring signal that is used by the phone

itself. The actual ring melody is based on the current melody set for the line where the BLF key is associated to.)

• Periodic - delayed (After a delay of (x) seconds, the ring signal that is used by the phone is played - see above.)

• One low volume splash (Same as the current BLF ring splash but at a lower level to be less intrusive.)

• One low volume splash - delayed (After a delay of (x) seconds, the ring signal that is the same as the current BLF ring splash is played at a lower level.)

Format Integer


Range 0-60 (disabled)1 (normal)2 (normal - delayed)3 (periodic)4 (periodic - delayed)5 (low volume)6 (low volume - delayed)

Example prgkey1 ring splash: 1

RN-001037-03 REV01 – 06.2012 18


Parameter– softkeyN ring splash


Description Controls the ring splash alert pattern per softkey. The following alerting patterns are available:• Silence (Ring splash off.)• Normal splash (Same as current BLF ring splash.)• Normal - delayed (After a delay of (x) seconds, the normal ring






Format Integer



Example softkey1 ring splash: 1

19 RN-001037-03 REV01 – 06.2012


Parameter– topsoftkeyN ring splash


Description Controls the ring splash alert pattern per top softkey. The following alerting patterns are available:• Silence (Ring splash off.)• Normal splash (Same as current BLF ring splash.)• Normal - delayed (After a delay of (x) seconds, the normal ring






Format Integer



Example topsoftkey1 ring splash: 1

RN-001037-03 REV01 – 06.2012 20


Parameter– expmodX KeyN ring splash


Description Controls the ring splash alert pattern per expansion module key. The following alerting patterns are available:• Silence (Ring splash off.)• Normal splash (Same as current BLF ring splash.)• Normal - delayed (After a delay of (x) seconds, the normal ring






Format Integer



Example expmod1 key2 ring splash: 1

Parameter– ring splash delay


Description Indicates the delay (seconds) between rings.

Format Numeric

Default value 7 (seconds)

Range NA

Example ring splash delay: 10

21 RN-001037-03 REV01 – 06.2012


Parameter– ring splash volume


Description Indicates the volume of the ring splash.

Format Numeric

Default value 5

Range 0-9

Example ring splash volume: 2

RN-001037-03 REV01 – 06.2012 22


BLF Hold State - Support for Directed Call Pickup

The phones support the Busy Lamp Field (BLF) hold state that is expressed by a slow flashing LED. Previously, if a user pressed the slow flashing key, the phone sent an INVITE message to the extension number of the monitored extension and the call could fail because the extension was busy (on hold).

Now in 3.3.0 HF1, if administrators configure BLF for Directed Call Pickup, users are able to pickup the held call, as the phone sends the directed call pickup prefix to the extension number.

Note:This feature requires support from the call manager.

23 RN-001037-03 REV01 – 06.2012


Edgewater Local Mode Support for BLA and SCA

Previously, if the phone was configured for Bridged Line Appearance (BLA) and shared Call Appearances (SCA), it would send a SUBSCRIBE message to get a dial tone to make a call. If the Edgewater Edgemarc box lost WAN Internet connectivity, the phone went into local mode. In this local mode, the phone would continue to work (make/receive calls) locally until the BLA subscription expired. Once that subscription expired, the phone was no longer able to send a SUBSCRIBE message (no dial tone was available to make a call).

Now in 3.3.0 HF1, when the phone loses connection (i.e. is in local mode) with the Edgewater device, the phone goes into a “generic” mode instead of BLA mode to ensure users are able to make and receive calls (and the phone doesn’t need to send the SUBSCRIBE message to get a dial tone to make a call). Once the phone gets con-nected (i.e. leaves the local mode) with Edgewater, the phone switches back to its original BLA mode.

RN-001037-03 REV01 – 06.2012 24


Blind Transfer to a Contact in Phone Directory

Users can now complete a blind transfer to a contact in their local directory. If a user is in a call and initiates a transfer, they can navigate to the Directory screen where a new Transfer key can be pressed to complete a blind transfer.

For 6730i and 6731i model phones: When a directory entry is shown, the Transfer key can be pressed to trigger a blind transfer.

For the 6753i model phone: When a directory entry is shown, the configured Transfer key (one of the programmable keys 1-6) can be pressed to trigger a blind transfer.

For 6755i, 6757i, and 6757i CT model phones: When a directory entry is shown, there is a new Xfer softkey below the current Dial softkey to trigger a blind transfer. This new Xfer softkey is only available if a transfer has been initiated.

If a directory entry has multiple numbers, softkey 2 is used for the Arrange function. If a transfer has been initiated, the Arrange function will be replaced with the Xfer function.

For example:

Case 1: Consultation of personal directory from a 6755i phone in Idle state or during a call (no transfer initiated):

Entry has multiple numbers

Directory

Delete -

Quit -- Add New

1. John2. Kim3. Steve

- DialDetails -

905-760-9999Line: 1 |

Dial

Add Number

DeleteChange

Quit

001

Arrange

25 RN-001037-03 REV01 – 06.2012


Case 2: Consultation of personal directory from a 6755i phone while in a call and a transfer has been initiated:

For the 6739i model phone: When a directory entry is shown, a new Transfer key can be pressed to trigger a blind transfer. The new Transfer softkey has been added to the contact card in the directory and will only appear if a transfer has been initiated. There is no change to start a consultative call.

For example:

Case 1: Consultation of personal directory from a 6739i phone in Idle state or during a call (no transfer initiated):

Note:The line softkey is greyed out.

Directory

Delete -

Quit -- Add New

1. John2. Kim3. Steve

- Xfer- Dial

Details -

905-760-9999Line: 1 |

DialXferAdd Number

DeleteChange

Quit

001

Entry has multiple numbers

Directory

John Doe12 : 45pm

Mon Sep 1

Edit

9055552233

Office 1

9055551122

Home 2

Delete9055559999

Cell 3Dial

Lines

RN-001037-03 REV01 – 06.2012 26


Case 2: Consultation of personal directory from a 6739i phone while in a call and a transfer has been initiated:

The Transfer softkey has replaced the Edit softkey, and a Cancel softkey has replaced the Delete softkey. From this screen, by pressing Dial you can do a consultative trans-fer and by pressing Transfer you can complete a blind transfer.

To Transfer a Call to a Contact in the Phone Directory1. Connect to Party 1 (if not already connected). Party 1 is the party you want to

transfer.

2. Press the Transfer key. You should hear a dial tone as a second line opens up.

3. Press the Directory key and select a contact.

4. To complete a blind transfer, press the Transfer key again before the receiving end answers.To complete a consultative transfer, press Dial to call the contact. Remain on the line to speak with Party 2 before pressing the Transfer key again to transfer Party 1 to Party 2.

Directory

John Doe12 : 45pm

Mon Sep 1

9055552233

Office 1

9055551122

Home 2

Cancel9055559999

Cell 3Dial

Lines Transfer

27 RN-001037-03 REV01 – 06.2012


ININ Callpark/Pickup Support

The IP phones (including the CT handsets) have a park and pickup call feature that allows you to park a call and pickup a call when required. Administrators can now con-figure the call park and pickup feature for use with ININ servers by using a static con-figuration (for 8 and 11-Line LCD phones) or by using a programmable configuration (3-Line, and 8 and 11-Line LCD phones).

Administrators can use configuration files or the Aastra Web UI to configure a park/pickup static or programmable configuration. Users can make changes to cus-tomize the label and the state of the park/pick up keys using the Web UI.

The following paragraphs describe the static and programmable configuration of the call park and pickup feature.

Park/Pickup Static Configuration

The static method configures park and pickup on a global basis for all supported IP phones. You can use the configuration files or the Aastra Web UI to configure a park/pickup static configuration. In the configuration files, you use the following parameters to statically configure park/pickup: “sprecode” and “pickupsprecode”.

In the Aastra Web UI, you use the following fields at Basic Settings -> Preferences to configure park/pickup statically:

• Park Call

• Pick Up Parked Call

Note:The 8 and 11-LCD phones accept both methods of configuration, however to avoid redundancy, Aastra Telecom recommends you configure either a static configura-tion or a programmable configuration.

Note:On the 6739i, you can configure Park/Pickup softkeys using the IP Phone UI also. For more information, see the Aastra Model 6739i IP Phone User Guide.

Notes:• The park/pickup static configuration method is not supported on the 6739i.• This feature does not work when the “collapsed context user softkey screen”

parameter is enabled.

RN-001037-03 REV01 – 06.2012 28


Configuring Park/Pickup Static Configuration Using the Configuration FilesUse the following parameters to configure park/pickup static configuration:

Parameter– sprecode


Description Specifies the code to enter before entering the extension for where you want to park an incoming call. The applicable value is dependant on the type of server in the network: ServerPark Values**Asterisk 70Sylantro *98BroadWorks *68ININ PBX callpark**Leave “value” fields blank to disable the static park and pickup feature.

Format Alphanumeric characters

Default Value <Blank>

Range See applicable values in table above.

Example sprecode: callpark

Parameter– pickupsprecode


Description Specifies the code to enter before entering the extension for where you want to pickup a parked call. The applicable value is dependant on the type of server in the network:ServerPark Values**Asterisk 70Sylantro *99BroadWorks *88ININ PBX pickup**Leave “value” fields blank to disable the static park and pickup feature.




Example pickupsprecode: pickup

29 RN-001037-03 REV01 – 06.2012


Configuring Park/Pickup Static Configuration Using the Aastra Web UI

Aastra Web UI

1. Click on Basic Settings ->Preferences ->General

2. Enter a server value in the Park Call field to which incoming live calls will be parked.

3. Enter a server value in the Pick Up Parked Call field.

4. Click Save Settings to save your changes.

RN-001037-03 REV01 – 06.2012 30


Park/Pickup Programmable Configuration (Using a Softkey)The programmable method of configuration creates park and pickup keys (softkeys, programmable keys, expansion module keys) that you can configure on the IP phones.

For all 8 and 11-Line LCD phones you can set a key as "Park" or "Pickup" and then:

• specify a customized label to display on the Phone UI

• specify the state of the park and/or pickup keys

For 3-Line LCD display phones, you can set a programmable key as "Park" or "Pickup".

On 8 and 11-Line LCD Phone UIs• When a call comes in, and you pickup the handset, the custom label that you con-

figured for the Park softkey displays on the Phone UI.

• After the call is parked, the label that you configured for the Pickup softkey displays on other phones in the network. You can then press the "Pickup" softkey, followed by the applicable value to pickup the call on another phone in your network.

• On the Model CTs, the customized labels apply to the base unit only. On the Model CT handsets, pressing the Features key displays the default labels of "Park" and "Pickup".

On 3-Line LCD Phone UIs When a call comes in, and you pickup the handset, you can press the applicable "Park" programmable key to park the call.

After the call is parked, you can press the "Pickup" programmable key, followed by the applicable value to pickup the call.

Note:On the 9480i/9480i CT and 6757i/6757i CT, the old softkey labeled "Pickup" has been renamed to "Answer". This softkey uses the old functionality - when you pickup the handset, you see a softkey labeled "Answer". You can then press this key to pick up an incoming call. Do no confuse this feature with the new Park/Pickup configuration feature.

31 RN-001037-03 REV01 – 06.2012


Configuring Park/Pickup Key Using Configuration FilesIn the configuration files, you configure the park/pickup keys using the key parame-ters. You also must specify the "sip lineN park and pickup config” parameter.

Parameter– sip lineN park pickup config


Description Specifies the code to enter before entering the extension for where you want to park an incoming call. The applicable value is dependant on the type of server in the network: ServerPark & Pickup Values*Asterisk 70;70;asteriskSylantro *98;*99;sylantroBroadWorks *68;*88;broadworksININ PBX callpark;pickup;inin*Leave “value” fields blank to disable the park and pickup feature.




Example sip lineN park pickup config: callpark;pickup;inin

RN-001037-03 REV01 – 06.2012 32


The following examples show park/pickup configurations using specific servers.

Examples for Models with 8 and 11-Line LCDs:

*When you configure a softkey as "Park", you must configure the state of the softkey as "connected".

**When you configure a softkey as "Pickup", you can configure the state of the softkey as "idle, outgoing", or just "idle", or just "outgoing".

Examples for Models with 3-Line LCDs:

Server Park Configuration Pickup Configuration

Asterisk softkeyN type: parksoftkeyN label: parkCallsoftkeyN states: connected*sip lineN park pickup config: 70;70;asterisk

softkeyN type: pickupsoftkeyN label: pickupCallsoftkeyN states: idle, outgoing**sip lineN park pickup config: 70;70;asterisk

Sylantro softkeyN type: parksoftkeyN label: parkCallsoftkeyN states: connected*sip lineN park pickup config: *98;*99;sylantro

softkeyN type: pickupsoftkeyN label: pickupCallsoftkeyN states: idle, outgoing**sip lineN park pickup config: *98;*99;sylantro

BroadWorks softkeyN type: parksoftkeyN label: parkCallsoftkeyN states: connected*sip lineN park pickup config: *68;*88;broadworks

softkeyN type: pickupsoftkeyN label: pickupCallsoftkeyN states: idle, outgoing**sip lineN park pickup config: *68;*88;broadworks

ININ PBX softkeyN type: parksoftkeyN label: parkCallsoftkeyN states: connected*sip lineN park pickup config: callpark;pickup;inin

softkeyN type: pickupsoftkeyN label: pickupCallsoftkeyN states: idle, outgoing**sip lineN park pickup config:callpark;pickup;inin

Server Park Configuration Pickup Configuration

Asterisk prgkeyN type: parksip lineN park pickup config: 70;70;asterisk

prgkeyN type: pickupsip lineN park pickup config: 70;70;asterisk

Sylantro prgkeyN type: parksip lineN park pickup config: *98;*99;sylantro

prgkeyN type: pickupsip lineN park pickup config: *98;*99;sylantro

Broad-Works

prgkeyN type: parksip lineN park pickup config: *68;*88;broadworks

prgkeyN type: pickupsip lineN park pickup config: *68;*88;broadworks

ININ PBX prgkeyN type: parksip lineN park pickup config: callpark;pickup;inin

prgkeyN type: pickupsip lineN park pickup config: callpark;pickup;inin

33 RN-001037-03 REV01 – 06.2012


Configuring a Park/Pickup Key Using Aastra Web UI

Park/Pickup Call Server Configuration Values

Use the following procedure to configure the park/pickup call feature using the Aastra Web UI.

For 8 and 11-line phones:

Note:The 6730i, 6731i, 6735i, 6737i, 6753i, 6755i and 9143i do not allow for the configu-ration of labels and states for programmable keys.

Note:Applicable values depend on the server in your network (i.e. Asterisk, BroadWorks, Sylantro, or ININ). See the table below for applicable values.

Server Park Values* Pickup Values*

Asterisk 70 70

Sylantro *98 *99

BroadWorks *68 *88

ININ PBX callpark pickup

Aastra Web UI

1. Click on Advanced Settings ->Line 1 (you can select any line)

2. Under Advanced SIP Settings in the “Park Pickup Config” field, enter the appropriate value based on the server in your network.

Note:Leave the park/pickup configuration field blank to disable the park and pickup feature.

RN-001037-03 REV01 – 06.2012 34


3. Click on Operation->Softkeys and XML.

4. Pick a softkey to configure for parking a call.

5. In the "Type" field, select Park.

6. In the "Label" field, enter a label for the park softkey.

Note:The” Value” and “Line” fields are already configured from the “Park Pickup Config” field.

7. The park softkey has a default state of “Connected”.Leave this state enabled or to disable, uncheck the check box.

8. Pick a softkey to configure for Picking up a call.

9. In the "Type" field, select Pickup.

10.In the "Label" field, enter a label for the Pickup softkey.


11.The pickup softkey has a default state of “Idle” and “Outgoing”.Leave these states enabled or to disable, uncheck the check boxes.

12.Click Save Settings to save your changes.

13.Click on Reset, then click Restart to restart the IP phone and apply the changes.

35 RN-001037-03 REV01 – 06.2012


For CT Handsets:

1. Click on Advanced Settings ->Line 1 (you can select any line)



Click on Operation->Handset Keys.

1. Pick a handset key to configure for parking a call.


3. In the "Label" field, enter a label for the park softkey.

4. Pick another handset key to configure for picking up a call.


6. In the "Label" field, enter a label for the pickup softkey.


8. Click on Reset, then click Restart to restart the IP phone and apply the changes.

RN-001037-03 REV01 – 06.2012 36


For 3-Line Phones:

1. Click on Advanced Settings -> Line 1 (you can select any line)



3. Click on Operation->Programmable Keys.

4. Pick a key to configure for parking a call.



6. Pick a key to configure for picking up a call.




9. Click on Operation->Reset.

10.Click on Reset, then click Restart to restart the IP phone and apply the changes.

37 RN-001037-03 REV01 – 06.2012


PIN and Authorization Code Suppression

Certain features on MX-ONE require a PIN/authorization code to be entered on the phone (for example: to register, for authorization, locking/unlocking, or accounting).The number format is *<feature code>*PIN# or *<feature code>*PIN*<number>#To deactivate features, the first star is replaced by #, (for example, #<feature code>*PIN#).

Administrators can now configure the “pin suppression dial plan” parameter so that if such a feature code with a PIN is entered, the PIN does not show up in any of the phone logs (i.e. redial list) nor is it displayed on the screen during a call. The pin will be masked with wildcard characters.

The “pin suppression dial plan” parameter introduces new alphanumeric characters that control the masking of the PIN: “(“and “)”.

The following is an example value of the new configuration parameter:

"*11*(1XXX)*5555+#|*72*(1XXX)#|#73*(1XXX)#"

where (1XXX) will mask any PINs that are 4 digits long and start with 1.

This parameter value should lead to the following masking:

• Entered digits *11*1234*5555# will lead to INVITE to this number but *11******5555# is shown on the display and in the redial list.

• Entered digits *72*1234# will lead to INVITE to this number but *72*****# is shown on the display and in the redial list.

• Entered digits #73*1234# will lead to INVITE to this number but#73*****# is shown on the display and in the redial list.

User Interface Features

RN-001037-03 REV01 – 06.2012 38


Configuring PIN SuppressionUse the following parameter to configure PIN suppression:

Parameter– pin suppression dial plan


Description Allows a pattern based configuration of the PIN suppression.

Format Alphanumeric charactersSymbol Description0, 1, 2, 3, 4, 5, 6, 7, 8, 9 Digit symbolX Match any digit symbol (wildcard)*, #, . Other keypad symbol; # can terminate a

dial string| Expression inclusive OR+ 0 or more of the preceding digit symbol

or [] expression[] Symbol inclusive OR- Used only with [], represent a range of

acceptable symbols; For example, [2-8]“,” (open/close quotes) In the configuration files, enter the sip

dial plan value using quotes.( ) Controls the masking of the pin. In the

configuration files, enter the pin inside the brackets ().

Default value NA

Range Up to 512 alphanumeric characters

Example pin suppression dial plan: "*11*(x+)*(x+)#"

39 RN-001037-03 REV01 – 06.2012


Scrolling Phone Numbers

Previously, if a long remote (outgoing or incoming) number was displayed on the phone (6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9480i, and 9480i CT models only), users were not able to scroll to the end of the number.

Users now have the ability to scroll through a remote number that is displayed on the phone. Users can press the scroll down navigation key to view the rest of the phone number content.

For example:

If a remote incoming call number is 123456789012345678901234567 (27 numbers long), the 6755i phone will display the following number portion initially:

After the user presses the scroll down navigation key, the rest of the remote number content is displayed, with shown at the end:

If the user presses the scroll up navigation key, the first line will be rolled back to the screen showing 1234567890123456789 .

#1 2212

John1234567890123456789

L1

AnswerIgnore

#1 2212

John01234567

L1

AnswerIgnore

RN-001037-03 REV01 – 06.2012 40


Displayed Directory Instructions

Previously on the 6730i, 6731i, 6753i, and 9143i model phones, procedures on how to modify directory entries were not specified. There is now a line on the screen that explains how to edit a directory entry.

When a user presses the Directory key once, the phone will display:

When the user presses the first letter or the up/down arrow (^v), the first record or indicated record is displayed in a new screen. The text “< to edit” has been added to the screen.

Press 1st letterUse to view

: John Doe2251 to edit L1

41 RN-001037-03 REV01 – 06.2012


Increased Number of Displayed Characters for Softkey Line Labels

Administrators can now disable line state icons to display 10 characters on softkeys and top softkeys for line labels on 6755i, 6757i, and 6757i CT model phones. This is useful if the user wants to display a full 10 digit number as the softkey label, instead of a shortened label containing only 7 digits followed by ellipsis characters.

When a softkey or top softkey is defined as a line, the circle in front of the softkey label (line icon) can be removed using the new “line icon disabled” parameter. When the “line icon disabled” parameter is set to “1”, the line icon will not appear and the label can be displayed with up to 10 characters (label will not be shortened and no ellipsis characters will appear).

Configuring the Increase of Displayed Characters for Softkey Line LabelsUse the following parameter to disable the line icon and increase the number of char-acters displayed for softkey line labels:

Parameter– line icon disabled


Description Disable the line icon (circle) displayed in front of the softkey line label. This allows the softkey line label to be displayed with up to 10 charac-ters (label will not be shortened and no ellipsis characters will appear).

Format Boolean

Default value 0


Example line icon disabled: 1

RN-001037-03 REV01 – 06.2012 42


Configurable Display for Blank BLF/List Softkeys

Previously, when softkeys for the 6755i, 6757i, 6757i CT model phones and the M675i Expansion Module were configured as BLF/List keys on the phone but there were not enough members in the BLF/List on the BroadSoft Broadworks server side, then a series of question marks would be displayed on screen beside some of the softkeys.

Administrators can now configure whether or not the series of question marks should be hidden using the new “keys noname hidden” parameter. If this parameter is set to “1” (enabled) then the series of question marks will be hidden and nothing will be shown on the screen beside the affected softkeys. If this parameter is set to “0” (disa-bled) then the series of question marks will be displayed on the screen indicating blank BLF/List softkeys.

Configuring the Display for Blank BLF/List SoftkeysUse the following parameter to configure the display for blank BLF/List softkeys:

Parameter– keys noname hidden


Description If this parameter is set to “0” (disabled) then a series of question marks will be displayed on the screen indicating blank BLF/List softkeys. If this parameter is set to “1” (enabled) then the series of question marks will be hidden and nothing will be shown on the screen beside the affected softkeys.

Format String

Default value 0


Example keys noname hidden: 1

43 RN-001037-03 REV01 – 06.2012


Additional Italy and Updated Slovakia Tone Sets and Cadences

The IP phones now support an additional Italy tone set with corresponding cadences.

The following table details the new Italy tone set cadences.

Additionally, the Slovakia tone set has been updated with revised cadences.

The following table details the updated Slovakia tone set cadences.

Note:The new Italy tone set has been assigned as “Italy” and can be designated in the Phone UI, Web UI, and configuration files. The original Italy tone set (previously assigned as “Italy”) has been reassigned as “Italy2”.

Tone Frequency (Hz) Cadence (on/off in seconds)

Dial 425 0.2/0.2/0.6/1.0

Secondary Dial 425 Continuous

Ringing 425 1.0/4.0

Busy 425 0.5/0.5

Congestion 425 0.2/0.2

Call Waiting 425 0.40/0.10/0.25/0.10/0.15

Tone Frequency (Hz) Cadence (on/off in seconds)

Dial 425 0.33/0.33/0.66/0.66

Secondary Dial 425 (0.165/0.165)x3 /0.66/0.66

Ringing 425 1.0/4.0

Busy 425 0.33/0.33

Congestion 425 0.165/0.165

Call Waiting 425 0.33 on repeating every 10 sec when Call Waiting period is set to 10

RN-001037-03 REV01 – 06.2012 44


Configuring Tone Sets Using the IP Phone UIUse the following procedure to configure tone sets using the IP Phone UI.

For global configuration only

All Models except 6739i:

For 6739i:

IP Phone UI

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

2. Select Preferences.

3. Select Tone Set.

4. Select the applicable country’s tone set (e.g. “Italy” or “Slovakia”).

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

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

2. Press the <Audio> button.

3. Press the <Tone Set> button.

4. Press the applicable country’s tone set (e.g. “Italy” or “Slovakia”).

5. Press the to return to the previous menu or press the to return to the idle screen.

45 RN-001037-03 REV01 – 06.2012


Configuring Tone Sets Using the Aastra Web UIUse the following procedure to configure tone sets using the Aastra Web UI.

Aastra Web UI

1. Click on Basic Settings->Preferences.

2. In the "Tone Set" field, select the applicable country’s tone set (e.g. “Italy” or “Slovakia”).

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 Save Settings.

RN-001037-03 REV01 – 06.2012 46


Configuring Tone Sets Using the Configuration FilesUse the following parameter to configure tone sets using the configuration files:

Parameter – tone set

Tone Set(in Web UI)

IP Phone UI Options->Tones->Tone Set6739i Phone Options->Audio->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)FranceGermanyItalyItaly2MalaysiaMexicoRussiaSlovakiaUnited Kingdom (UK)US (also used in Canada)

Example tone set: Italy

47 RN-001037-03 REV01 – 06.2012

Issues Resolved in Release 3.3.0 HF1

Issues Resolved in Release 3.3.0 HF1This section describes the issues resolved on the IP Phones in Release 3.3.0 HF1.

The following table provides the issue number and a brief description of each fix.

Issues Resolved

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

Issue Number Description of Fix

Configuration

DEF25750/CLN25762 6739i: An issue was observed where an XML logon/off softkey would be lost (i.e. would be changed to a “None” key) if a speed dial softkey was added via the Web UI. This issue has been fixed.

DEF24678/CLN25991 An issue was observed where the phone was unable to subscribe to BLF when the “sip rport” parameter was enabled. This issue has been resolved and the phone is now able to subscribe to BLF when “sip rport” is enabled.

DEF24145/CLN25510 Previously, when a programmed key was removed (via Web UI or the IP Phone UI’s Speed Dial Edit Menu), the key would not be completely removed from the local.cfg file. Consequently, if the same softkey was defined in the aastra.cfg or MAC.cfg files, the key would not show up (as the remaining parameters in the local.cfg file override the server.cfg file). This issue has been corrected and now when a programmed key is removed, the whole content of the respective key is removed from the local.cfg file.

DEF26134 An issue was observed where the ring splash feature was not functioning as expected when configuring the “expmodX KeyN ring splash” parameter. This has been fixed and the ring splash feature is now working as expected for expansion module keys.

DEF23569/CLN26101 6739i: Users were able to edit speed dial softkeys that were locked by the administrator. This issue has been corrected and keys that are locked by the administrator are now uneditable by users.

DEF26843 If the phone was utilizing BLA and the “switch focus to ringing line” parameter was enabled, when a user had placed an outgoing call and another call was incoming and cancelled by the remote caller, the incoming call would be ter-minated as expected, but also the outgoing call would unexpectedly be dropped. This issue has been fixed.

ENH25728 9480i, 9480i CT, 6755i, 6757i, 6757i CT, and 6739i: Previously, softkeys (as well as expansion module keys) configured as “Empty” were not configurable as speed dial keys using the “press-and-hold” feature. This has been resolved and users can now edit softkeys configured as “Empty” for use as a speed dial key by pressing the respective softkey button on the phone.

RN-001037-03 REV01 – 06.2012 48


DEF25769 With the “call hold reminder” parameter enabled, if a user was in an active call and had a call on hold on a different line, when the active call was terminated, the expected call hold reminder tone at times would not be heard. This issue has been corrected.

DEF23747 Previously, when the “services script” parameter was defined in a configura-tion file, pressing other various softkeys (e.g. softkeys configured as None, Empty, Call Forward, etc...) would unintentionally execute the services script. This issue has been fixed and the services script is now executed only when the Services softkey is pressed.

DEF27444 6731i: With the phone’s Conference hard key configured for use with the MX-ONE server (i.e. setting the applicable “conference disabled: 1”, “map conf as dtmf: 1”, and “map conf key to: 3” parameters), pressing the Conference hard key would not initiate the conference call as expected. This issue has been cor-rected.

DEF26539 When rebooting within approximately 30 seconds after locking the phone, the enabled “phone lock” parameter was omitted in the local.cfg file causing the phone to reboot in an unlocked state. The parameter is now saved immedi-ately after locking the phone and the phone now reboots in a locked state irre-spective of the time the phone was rebooted.

DEF27285/CLN27763 An issue was observed whereby if the phone was locked, pressing a speed dial softkey or speed dial keypad key configured with an emergency dialplan number would not dial the emergency number as expected. This issue has been corrected and emergency number speed dial functionality with locked phones is now working as expected.

SIP

DEF26654/CLN26667 With phones configured for SCA, an issue was observed when a user placed an active call on Line 1 on hold, and a secondary user on the SCA account picked up the handset to place a call. The secondary user’s phone would intermittently pick up the call on hold on Line 1 instead of seizing Line 2. This has been corrected.

DEF25701/DEF26719/DEF26686/DEF26287/CLN26741/CLN26742

Intermittent reboots were observed when repeatedly pressing the delete key in the Callers List (applicable to 6731i and 6753i) and when trying to edit a key for speed dial functionality (applicable to 6731i only). This issue has been corrected and managing logs in the Callers List and editing keys for speed dial functionality is behaving as expected.

DEF26722/CLN26844/CLN26845

In dual-registration situations with the MX-ONE call manager, the phone, at times, would not log off the MX-ONE system as expected and would become unresponsive. Additionally, when the MX-ONE call manager sent a forced log-off message to the phone, this intermittently caused the phone to reboot. This has been corrected and the phone will now gracefully log off when required.

DEF24623/CLN26895 If a digit key on the phone was set up for speed dial functionality and the configured speed dial number contained a comma (i.e. pause), initiating the speed dial feature would prepend the digit key value to the configured speed dial number. This issue has been corrected and speed dial functionality is now unaffected by speed dial numbers containing commas.


49 RN-001037-03 REV01 – 06.2012


DEF26363/CLN26914 When performing a blind transfer using the REFER method, the phone would not send a NOTIFY message with a sipfrag 200 OK response. This would cause blind transfer failures. This issue has been resolved and blind transfers using the REFER method are now functioning as expected.

DEF24637/CLN26916 An issue was observed where the phone incorrectly accepted (i.e. responded with a 200 OK response) an SDP Answer containing an unsupported offer in the PRACK message. This issue has been corrected and the phone now sends 488 Not Acceptable Here response in such situations.

DEF24863/CLN26917 Previously, if the phone received an INVITE without SDP and then a PRACK message, once the call was answered, the phone sent a 200 OK response, but did not send the expected RTP. This issue has been resolved.

DEF27049/CLN27069 An issue was observed where the phone did not send the expected 200 OK response when receiving a SIP UPDATE request after a 183 Session Progress message. The phone instead sent a 500 Internal Server Error response, which caused the call to fail. This has been corrected.

DEF27091/CLN27115 Previously, when a call was initiated using the Zultys MXIE client and answered by the remote party, pressing the Goodbye key would not send a BYE message to the server and the remote party would not be disconnected. This has been resolved and a BYE message is now sent in such situations.

DEF27156/CLN27180 6739i: When utilizing the A5000 server, an issue was observed whereby after performing an attended transfer the phone could not make or receive calls. This issue has been resolved.

DEF25563 If a phone connected to an expansion module was configured with the BLF Activity Page Switch feature enabled and a BLF number was set on specific expansion module keys, the expansion module would at times become unre-sponsive. This has been corrected.

DEF25363 All phones except 6739i: An issue was observed where the phone would auto-matically put an active call on hold if two other calls were incoming and in a ringing state and one incoming call was cancelled. This issue has been resolved.

DEF23954/CLN25926 An issue was observed where the ring tone at the beginning of a call would not start/stop cleanly, which would cause an audible “bleep” either before the ring tone started or after the ring tone stopped (if the call was cancelled before the ring tone ended). This has been fixed and now no “bleep” is audible at the beginning of a call.

DEF25393/CLN25922 If utilizing the MetaSwitch server, the phone’s mute button would become unresponsive when the user was in an active call and an incoming call was in the ringing state. This issue has been corrected and the mute button now functions as expected in such scenarios.

ENH23972/CLN26026 Previously, when the phone received a NOTIFY message with state “early” and direction “initiator”, the BLF key LED would not turn solid as expected but instead would blink. This has been resolved.

DEF24625/CLN25704 If utilizing the A5000 server, the phone would not send the expected REGISTER message after failing over to a backup server in Dual-Homing mode. This issue has been fixed.


RN-001037-03 REV01 – 06.2012 50


DEF25245/CLN25783 6739i: An issue was observed where the phone would not show the state of the BLF/List elements when the connection between the local network switch and server was lost and then subsequently reestablished. This issue has been resolved and the state of BLF/List elements is now displayed as expected in such scenarios.

DEF25679 All phones except 6739i: When lifting the handset and hanging up from an idle state, a double dial-tone burst could at times be heard from the speaker. This also occurred when the ring-back tone was present in the handset at the moment the handset was hung up. This has been fixed and now no dial-tone burst can be heard in such situations.

DEF25737/CLN25739 When utilizing the BroadSoft BroadWorks server, if the phone refreshed a call-info subscription, the server responded with a NOTIFY message with a “termi-nated” state. After responding to the termination NOTIFY with a 200 OK, the phone did not send another subscription as expected. This issue has been cor-rected.

DEF24008/CLN25924 Previously, if a conference call was initiated and a user dropped out of the con-ference, any subsequent calls would have no sidetone. The issue would remain until the call was placed on hold and then retrieved. This has been fixed.

DEF25127/CLN25928 When utilizing the A5000 server, if the phone received a NOTIFY message to switch on the LED of a key before the key was actually programmed (i.e. as an XML softkey), the applicable LED key would stay off. This has been corrected and LEDs are now functioning normally in such situations.

DEF26051/CLN26139 6730i, 6731i, and 6739i: Stability issues were observed when the phone tried to parse an MWI NOTIFY message sent by a server that did not follow RFC 3842 recommendations. The stability issues have been fixed in such situations.

DEF23743 An issue was observed whereby BLF re-subscription would not occur if the server sent a NOTIFY message with a “terminated” subscription state. This has been fixed and the phone will now correctly send a re-subscribe request if it receives a NOTIFY message with a “terminated” subscription state.

DEF25158 With SCA configured lines, when a blind or consultative transfer was per-formed the transferred party would not be updated on the phone’s display as expected. This has issue has been resolved.

DEF23775 An issue was observed whereby the order of preference of the TLS Cipher Suites would be swapped during the phone/server handshake procedure, which would cause TLS registration to fail. This issue has been corrected and TLS registration is now functioning as expected.

DEF25428 When utilizing the MetaSwitch Call Manager and receiving a paged call, if the user picked up the handset and tried to switch the audio device to the speaker, the paged call would be dropped. This has been fixed and the audio device can now be switched between handset, headset, and speaker without any issues during a paged call.

DEF24628/CLN26919 An issue was observed where the phone did not send the expected 5xx Status response when receiving a UPDATE with an SDP offer after an INVITE contain-ing an SDP offer. The phone instead processed the UPDATE resulting in a retransmit from the server. This has been corrected and the phone now gen-erates the correct 500 response in such scenarios.


51 RN-001037-03 REV01 – 06.2012


DEF23964 Real-time BLF monitoring issues were observed when utilizing VLAN and QoS in conjunction with specific switches. This has been resolved and the new“vlan hpq” parameter has been created to enable/disable VLAN High Priority Queue (HPQ), which was found to be the source of the issue.

DEF26894 When joining two active calls to begin a 3-way centralized conference by pressing the Line 1 key, Conf softkey, Line 2 key, and then the Conf softkey again, the conference would not join the two calls as expected. This issue has been fixed.

DEF25159 Previously, the phone did not respond quickly enough to send a SIP BYE mes-sage if an incoming call was picked up by the handset then immediately ter-minated (i.e. either by immediately pressing the Goodbye key or hanging up the handset). This resulted in the incoming call not being terminated as expected. This issue has been resolved.

DEF27198 An issue was observed where the phone would send a 603 response instead of the expected 486 Busy Here response if the phone was acting as a single line (i.e. call waiting on Line 1 was disabled) and the phone received a call on Line 1 when the line was already being used in an active call. This issue has been fixed and the 486 Busy Here response is now correctly sent in such scenarios.

DEF26767/DEF26772 6757i CT: When a 3-way centralized conference was established via cordless handset, the call switched to the base, activated the speaker on the base, and subsequently placed the call on hold on the cordless handset. Additionally, using the cordless handset for a blind transfer from a shared line would cause issues whereby the handset could not be used for subsequent call transfers or conferences. These issues have been resolved.

DEF27117 If utilizing phones with lines configured with the same SCA account, when a user established a 3-way centralized conference call and a secondary user tried to establish his/her own centralized conference call, the secondary user’s phone UI would display incorrect information and the phone would intermit-tently become unresponsive. This issue has been fixed.

DEF23254/CLN24520 6757i CT and 9480i CT: An issue was observed where the cordless handset would not present a transfer option; therefore users were not able to transfer calls using the cordless handset. This has been resolved and transfer options are now available and functioning as expected using the cordless handset.

DEF26729 6755i and 6757i: An issue was observed whereby a failed SIP registration situ-ation would cause the phone’s backlight to turn on automatically. This has been corrected and now invalid registration messages do not affect the back-light.

DEF26846 6757i CT and 9480i CT: Previously, when an intercom call was being conducted between the base and the cordless handset, pressing the Hold key on the base would cause stability issues. This issue has been fixed and placing an intercom call between the base and the cordless handset on hold is now functioning as expected.

DEF26892 6757i CT and 9480i CT: When an intercom call was being conducted between the base and the cordless handset and a call was incoming, the phone would not indicate the incoming call as expected (i.e. no ringing and no flashing LED), and would send a 486 Busy Here response to the server. This has been resolved and the phone now handles incoming calls correctly in such situa-tions.


RN-001037-03 REV01 – 06.2012 52


DEF26267 6739i: When utilizing the Aastra Solidus eCare client, an issue was observed where the no-progress tone would be played on the phone for a very short period of time after receiving a BYE message from the server. This issue has been corrected and the no-progress tone is now played continuously in such scenarios.

DEF26162 Asymmetrical UDP source port issues were observed with regards to BLA SUB-SCRIBE and NOTIFY messaging. This issue has been fixed and port issues have been resolved in such messaging scenarios.

DEF26979/CLN27179 6739i: Intermittent stability issues were observed with regards to the SIP engine when starting another call before the previous call was answered using the Zultys MXIE client. This has been fixed.

DEF27448/CLN27618 6731i and 6757i: When utilizing the MX-ONE server, a stability issue was observed if the server sent an incorrect SDP in a 183 provisional response to the phone. This issue has been corrected and the phone now responds by returning to the idle screen in such situations.

DEF27525 6757i and 6757i CT: With phones configured for SCA, trying to initiate a con-ference between two calls on different SCA lines on the same phone would fail as expected (feature currently not supported on BroadSoft BroadWorks serv-ers) but the phone would not clear the lines correctly and would cause pres-ence issues. This has been fixed.

DEF27608 An issue was observed whereby a continuous DTMF tone would be played if the phone was in the process of initiating a conference call and the phone received an incoming call at the same time. This issue has been resolved.

DEF27116/CLN27887/CLN27893

In addition to 2048-bit Verisign root certificate support, 2048-bit intermediate certificates are now supported by the IP phones in Release 3.3.0 HF1.

DEF27851/CLN27899 Memory stability issues were observed when the Call Forwarding feature was set to CFWD ALL or CFWD BUSY on the phone and an incoming call was for-warded. This issue has been fixed.

DEF27888/CLN27941 6739i: Stability issues were observed when SCA-configured phones on an Aas-tra MX-ONE server switched over to a backup proxy/redundant server due to a network failure. This issue has been resolved and the phones are now working as expected when a failover occurs.

DEF26396 Improvements have been made to increase robustness when an invalid backup proxy has been configured on the phone.

DEF27728/CLN28226/CLN28227

6739i: With a phone configured for multiple lines and subscribed to an A5000 server, after performing two subsequent logoff and login operations, the phone would not be reachable on the primary line (i.e. Line 1 would present a busy tone to the caller) while secondary lines (e.g. Line 2 and Line 3) would be reachable. This issue has been resolved.

DEF27236/CLN28172/CLN27829

6739i: Improvements have been made to address intermittent Transport module stability issues when the phone is registered to an Aastra MX-ONE server.

DEF27340/CLN28228/CLN28229

6739i: Intermittent stability issues were observed when the line mode of the phone was changed from SCA to generic and the phone received an incoming call. This has been fixed and changing line modes now does not affect stability.


53 RN-001037-03 REV01 – 06.2012


User Interface

DEF25429/CLN26847 6739i: An issue was observed where the phone would not display the expected “Paging” label on screen when incoming or outgoing paging activity was conducted. This issue has been corrected.

DEF23612/DEF23909/CLN26907

The “Delete All” option was not available when trying to delete entries from the Callers List. This has been corrected and users can now delete all entries from the Callers List in one step by selecting the “Delete All” option.

DEF25717 6755i, 6757i, and 6757i CT: When entering an entry into the phone (e.g. into the local directory), users could only select upper case characters for the first letter of each key (i.e. users could select “A” but not “B” as an upper case char-acter). This issue has been corrected and all characters can now be entered as upper case.

DEF25528 Secondary Polish and Czech language files have been added allowing users to select the respective language files in either ASCII or UTF-8 encoding. Lan-guage files for Polish now include lang_pl.txt (ASCII) and lang_pl_pl (UTF-8). Language files for Czech now include lang_cs_op.txt (ASCII) and lang_cs.txt (UTF-8).

DEF26994 When an centralized conference call was made from an SCA shared line, the LED for the SCA primary line did not indicate the line’s presence as expected. This has been fixed and line presence is now functioning as expected in such situations.

DEF24100 When utilizing OneBox or Operator, logging off of the phone would not remove message waiting indicators if the phone’s message waiting indicators were being displayed previous to the log off. This issue has been corrected and the Message Waiting Indicator (MWI) LED and applicable icons are now removed as expected after the phone is logged off.

DEF21469 When in a conference and a call was incoming, the phone’s UI focus did not switch to the line of the incoming call, which resulted in the phone not display-ing the corresponding softkeys. This has been resolved and the UI is now func-tioning as expected in such situations.

DEF26806/DEF26801 An issue was observed whereby pressing an unconfigured locked softkey (i.e. a softkey that has no function tied to it but locked by the administrator) on the phone or on an expansion module would cause the menu to unexpectedly open and be displayed on the phone’s screen. This issue has been corrected.

DEF22426 Pressing an unconfigured softkey (to configure a speed dial entry) would unexpectedly cause the Services softkey LED to turn on. This issue has been resolved.

DEF25848 Previously, if a phone was registered using an SCA account that had already been registered with another phone, the Web UI of the initially-registered phone would be unreachable. Additionally, the phone could only be restarted through a hard reboot. This issue has been corrected.


RN-001037-03 REV01 – 06.2012 54


DEF27286/CLN27762 6755i, 6757i, and 6757i CT: An issue was observed whereby if a phone that had more than six configured softkeys was locked, the More softkey would appear on the idle screen as expected (to allow users to navigate to a second page with the additional softkeys), but pressing the More softkey would have no effect. This issue has been resolved and pressing the More softkey now func-tions as expected in such situations.

DEF26567 When pressing the Goodbye key after scrolling through the phone’s different lines using the navigation keys, the phone would unexpectedly remain on the last selected line. This issue has been corrected and the phone now switches back to Line 1 when the Goodbye key is selected in such scenarios.

DEF27346 With phones that are configured for SCA, if a call was placed on hold by one user of the SCA line and another user withdrew the hold on the call, the Caller ID displayed on screen would momentarily be displayed in an incorrect order. This issue has been fixed and the Caller ID is now displayed correctly at all times.

DEF26931 When pressing the EditNum softkey in the Callers List, entering numbers would incorrectly replace the existing numbers stored for the respective entry. This has been corrected and entering numbers now inserts additional num-bers without replacing any existing numbers.

DEF27501 6739i and 6757i: With phones configured for BLF functionality through MX-ONE, if a user started dialing a number for an outgoing call and a BLF update on a different page occurred at the same time, the digits that the user entered would be cleared and would have to be re-entered. This issue has been fixed and BLF updates now do not affect the dial field when initiating an outgoing call.

DEF27284/CLN27759 An issue was observed whereby the Message Waiting Indicator (MWI) LED would not turn on when the phone was locked. This has been corrected and the MWI LED now functions as expected in such situations.

ENH27421/CLN27942 M675i Expansion Module: LED refresh time for BLF/List keys on the M675i expansion modules have been optimized making the LED response time (with regards to the indication of state changes) faster.

DEF22934 6731i: An issue was observed whereby if a user tried to create an entry in the IP phone’s directory, the screen would not display the characters the user entered. This has been resolved and the phone now displays all characters entered by the user when adding or making changes to directory entries.

DEF27455/CLN28177 All phones except 6739i: When utilizing the Aastra MX-ONE server, an issue was observed whereby a phone’s number would be presented twice in an attended transfer, if the phone’s P-Asserted-Identity (PAI) did not contain a display name. This issue has been resolved and in such situations, the number is now only displayed once as expected.

DEF27876/CLN28178/CLN28154

6731i: When a user dialed more than 15 digits (surpassing the per line character limit on the 6731i IP phone’s screen) the phone’s UI did not scroll to the left to reveal the additional dialed digits as expected. This issue has been fixed and the UI now correctly scrolls left to display all additional digits.

DEF27813/DEF27815/DEF27816/DEF27818/DEF27819

Various Dutch language/translation issues have been corrected.


55 RN-001037-03 REV01 – 06.2012

Contacting Aastra Telecom Support

Contacting Aastra Telecom SupportIf you have 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 AmericaPlease contact your regional Aastra Technical Support.

RN-001037-03 REV01 – 06.2012 56

http://www.aastratelecom.com/support

Disclaimer

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

Documents

Aastra Models 9000i and 6700i Series SIP IP Phones - Mitelgts.aastra.com/publish/mx-one/TeleSys/Version5/ServicePack/fw/A67... · Aastra Models 6700i and 9000i Series SIP IP Phones