V3.3.1, 08/2013, pdf

Aastra Models 6700i and 9000i Series SIP IP Phones

SIP 3.3.1 Service Pack 2 Release Notes

RN-001037-03 REV10 – 08.2013

Content

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.3.1 Service Pack (SP)2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Release Notes Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release Content Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Hardware Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Bootloader Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

New Features in Release 3.3.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4SIP Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6XML Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Configurable Alphanumeric Input Order for Username Prompts . . . . . . . . . . . . . 8VLAN ID Assignment Using DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Configurable Subscription Period for BLF/List Subscriptions . . . . . . . . . . . . . . . . 12Configurable Beep Tone for Active Voice-over-IP (VoIP) Recording . . . . . . . . . . 14Option to Include/Remove Silence Suppression Attribute from SDP Offer . . . 16Ring Signal Type for BLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SIP Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Configurable URI Scheme When TLS Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23AMR and AMR-WB (G.722.2) Codec Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24BroadSoft BroadWorks Executive and Assistant Services Feature . . . . . . . . . . . . 35Passthrough Support for Data from VLAN-Enabled PC Port to VLAN-Disabled LAN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Directory File Reloading with Auto-Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Emergency Call Behavior Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

II RN-001037-03 REV10 – 08.2013

Content

User Interface Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100PIN and Authorization Code Suppression UI Enhancement . . . . . . . . . . . . . . . .100Automatic BLF Activity Page Switching Enhancement . . . . . . . . . . . . . . . . . . . . .101Active VoIP Recording Visual Indicators During Conference Calls . . . . . . . . . .102Ring Tone via Speaker During Active Calls Support . . . . . . . . . . . . . . . . . . . . . . . .104Improved Accessibility When Phone Has No Service. . . . . . . . . . . . . . . . . . . . . . .105Shared Call Appearance (SCA) Voicemail Enhancements . . . . . . . . . . . . . . . . . .107Ability to Edit the Name Field of a Callers List Record . . . . . . . . . . . . . . . . . . . . . .109

XML Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Melody Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Issues Resolved in Release 3.3.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Contacting Aastra Telecom Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

New Features in Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

New Features in Release 3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

New Features in Release 3.3.1 SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

RN-001037-03 REV10 – 08.2013 III

SIP IP Phone Models 6700i and 9000i Series Phones Release Notes 3.3.1 Service Pack (SP)2

About this DocumentThis document provides details on new features and/or issues resolved for the 6700i Series SIP IP Phones (6730i, 6731i, 6735i, 6737i, 6739i, 6753i, 6755i, 6757i, 6757i CT) and the 9000i Series SIP IP Phones (9143i, 9480i, 9480i CT) for Release 3.3.1 SP2.

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.

Release Notes TopicsTopics in these release notes include:

• General Information

• New Features in Release 3.3.1 SP2

• Additional Information

• Issues Resolved in Release 3.3.1 SP2

• Contacting Aastra Telecom Support

Note:This release applies to the phone models mentioned above only.

1 RN-001037-03 REV10 - 08.2013

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.1 SP2 FC-001319-02-REV10 August 2013








6757i CT Generic SIP 3.3.1 SP2 FC-001324-02-REV10 August 2013



9480i CT Generic SIP 3.3.1 SP2 FC-001327-02-REV10 August 2013

673xi Models 675xi Models 9xxxi Models

6730i 6753i 9143i

6731i 6755i 9480i

6735i 6757i 9480i CT

6737i 6757i CT

6739i

RN-001037-03 REV10 – 08.2013 2

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

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






6735i: Bootloader 2 1.0.0.0 or higher


9480i CT: Bootloader 2.2.0.166 or higher

6737i: Bootloader 2 1.0.0.0 or higher

6757i CT: Bootloader 2.0.1.1055 or higher


3 RN-001037-03 REV10 – 08.2013

New Features in Release 3.3.1 SP2This section provides the new features in SIP IP Phone Release 3.3.1 SP2. The following table summarizes each new feature and provides a link to more information 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

Configurable Alphanumeric Input Order for Username Prompts

(For Administrators)

A new configuration parameter “username alphanumeric input order” has been introduced in Release 3.3.1 SP2. When defined as “1”, this parameter changes the default behavior of the keypad input order during username prompts from uppercase letters > digit > lower case letters to digit > uppercase letters > lower case letters. *New for 6730i, 6731i, 6753i & 9143i

VLAN ID Assignment Using DHCP


The 6735i and 6737i IP phones now support VLAN ID assignment using DHCP Option 43 or Option 132. Administrators can use the new “dhcp option 132 vlan id enabled” parameter for VLAN ID assignment by DHCP Option 132. If using DHCP Option 43, the device will receive the VLAN ID from the new Option 43 values.*New for 6735i & 6737iFeature previously available for all other IP phones

Configurable Subscription Period for BLF/List Subscriptions


Previously, the “sip blf subscription period” configuration param-eter and “BLF Subscription Period” Web UI field were applicable only to BLF subscriptions. With Release 3.3.1 SP2, the subscription period for BLF/List subscriptions are now configurable using the same configuration parameter and Web UI field.*New for all phones

Configurable Beep Tone for Active Voice-over-IP (VoIP) Recording


With Release 3.3.1 SP2, Administrators can now configure how often and to whom the audible periodic beep tone is played when the active VoIP recording feature is being utilized.*New for 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT

Option to Include/Remove Silence Suppression Attribute from SDP Offer


The parameter “sip remove silence suppression offer” has been introduced in Release 3.3.1 SP2 for the 6735i and 6737i IP phones allowing administrators the ability to control whether or not the silence suppression attribute should be included in the Session Description Protocol (SDP) offer.*New for 6735i & 6737iFeature previously available for all other IP phones

RN-001037-03 REV10 – 08.2013 4

New Features in Release 3.3.1 SP2

Ring Signal Type for BLF


The global parameter “play a ring splash” controls whether or not a ring splash is played when there is an incoming call on a Busy Lamp Field (BLF) monitored extension. If the host tone is Idle, the tone plays a ring splash. In 3.3.1 SP2, Administrators can now control the ring splash alert pattern on a per key basis for the 6735i and 6737i IP phones. Each type of key can have a different ring splash alerting pattern and vol-ume. *New for 6735i & 6737iFeature previously available for all other IP phones

SIP Features

Configurable URI Scheme When TLS Enabled


The newly introduced “sip send sips over tls” parameter allows administrators the ability to configure the IP phones to use either the SIP or SIPS URI scheme when TLS or persistent TLS is enabled.*New for all phones

AMR and AMR-WB (G.722.2) Codec Support


The 6735i and 6737i IP phones now support the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR -WB) codecs. AMR/AMR-WB codecs provide improved speech quality during calls due to wider speech bandwidth, and cover both real-time transfers through Real-time Transport Protocol (RTP) and non-real-time transfers through stored files.*New for 6735i & 6737i

BroadSoft BroadWorks Executive and Assistant Services Feature

(For Administrators and Users)

Release 3.3.1 SP2 introduces support for the BroadSoft BroadWorks Executive and Assistant Services feature for the 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT IP phones. The Executive and Assistant Services feature allows Administrators to create an inter-network relationship between Executives and Assist-ants allowing calls to the Executive’s phone to be screened, filtered, and routed to an Assistant, whereby the Assistant can answer, divert, or push the filtered call back to the Executive.*New for 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT

Passthrough Support for Data from VLAN-Enabled PC Port to VLAN-Disa-bled LAN Port


Data passthrough is now supported on the 6735i and 6737i IP phones in scenarios where the IP phone’s PC port is connected to a VLAN-enabled PC and the LAN port is connected to a device with-out VLAN support.*New for 6735i & 6737iFeature previously available for all other IP phones except 6730i

Directory File Reloading with Auto-Resync


During an auto-resync, the 6735i and 6737i IP phones now initiate a comparison of its local directory files with those located on the con-figuration server and automatically update the local directory files if changes are detected.*New for 6735i & 6737iFeature previously available for all other IP phones

Feature Description

5 RN-001037-03 REV10 – 08.2013


Emergency Call Behavior Enhance-ments


Administrators now have the option of changing the default behav-ior of the 6735i and 6737i IP phones when an emergency call is placed. If the “emergency call connection hold enabled” configu-ration parameter is set, the IP phones will ensure that the voice/audio path and other resources associated with the emer-gency call are continually active and any functions that could reduce the continuous reachability of the caller are disabled.*New for 6735i & 6737iFeature previously available for all other IP phones

User Interface Features

PIN and Authorization Code Sup-pression UI Enhancement


An enhancement has been made to the PIN and authorization code suppression feature in Release 3.3.1 SP2 whereby if the feature is enabled, the phone will now dynamically mask the PIN/authoriza-tion code on the display within a second of the code being entered by the user.*New for all phones

Automatic BLF Activity Page Switch-ing Enhancement


An enhancement has been made to the BLF page switch feature in Release 3.3.1 SP2 whereby the IP phones now automatically switch to the idle page (or the first page on the M675i Expansion Module) if there is no BLF activity is detected by the phone.*New for 6735i, 6737i, 6739i, 6755i, 6757i, 6757i CT IP Phones, & M675i Expansion Module

Active VoIP Recording Visual Indica-tors During Conference Calls

(For Users)

When in a conference call, if the call is being recorded, icons (i.e. depending on the phone model, a red or black circle) are now dis-played on the phones’ screens indicating the recording status.*New for 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT

Ring Tone via Speaker During Active Calls Support


The parameter, “ring audibly enable”, is now available to be utilized for the 6735i and 6737i. This parameter allows administrators the ability to configure the IP phones to play the ring tone of an incom-ing call via the phone’s speaker while in an active call or if the user is in the process of dialing out.*New for 6735i & 6737iFeature previously available for all other IP phones

Improved Accessibility When Phone Has No Service


The option is now available for administrators to configure the 6735i and 6737i IP phones to relay a congestion/fast busy tone instead of a dial tone when the phone is in a “No Service” state. This enhance-ment allows visually impaired persons the ability to discern whether or not the phone is in service and can be used to send/receive calls.*New for 6735i & 6737iFeature previously available for all other IP phones

Feature Description

RN-001037-03 REV10 – 08.2013 6


Shared Call Appearance (SCA) Voice-mail Enhancements


Visual indicators for voicemail messages on Shared Call Appearance (SCA) lines have now been implemented on the 6735i and 6737i IP phones. The parameter, “voice mail indicator” is available allowing administrators the ability to configure what types of visual indica-tors the IP phones should display when an voicemail message is pending on a respective SCA line.*New for 6735i & 6737iFeature previously available for 9480i, 9480i CT, 6755i, 6757i, and 6757i CT

Ability to Edit the Name Field of a Callers List Record

(For Users)

With Release 3.3.1 SP2 users are now able to directly edit the name field of a call record in the phone’s Callers List before copying the record to the Directory.*New for 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT

XML Features

Melody Playback

(For Administrators, Users, and XML Developers)

Melody playback support has been introduced in Release 3.3.1 SP2. WAV files on a server can be stored on and played by the IP phone by defining the WAV file URL in an XML script. When the Play Melody XML script is executed, the IP phone will download and store the WAV file internally and start playback of the WAV file.*New for all phones

AastraIPPhoneConfiguration Lock-ing/Unlocking Support for Softkeys and Programmable Hardkeys

(For XML Developers)

For more information, refer to the Development Guide, XML API for Aastra SIP Phones.*New for 6735i & 6737iFeature previously available for all other IP phones

XML Server Redundancy Support


For more information, refer to the Development Guide, XML API for Aastra SIP Phones.*New for 6735i & 6737iFeature previously available for all other IP phones

Feature Description

7 RN-001037-03 REV10 – 08.2013

Additional Information

Configurable Alphanumeric Input Order for Username PromptsA new configuration parameter “username alphanumeric input order” has been introduced in Release 3.3.1 SP2 for the 6730i, 6731i, 6753i and 9143i IP phones. By default, keypad input order during username prompts changes from uppercase let-ters to the respective digit and then to lowercase letters with each successive press of the key. For example, when pressing “2” on the keypad, the following will be input with each successive press:

When the “username alphanumeric input order” parameter is defined as “1”, the respective digit will be available as the first input option followed by upper case and then lower case letters. For example, when pressing “2” on the keypad with this parameter enabled, the following will be input with each successive press:


# of Presses Letter/Number

1 A

2 B

3 C

4 2

5 a

6 b

7 c

# of Presses Letter/Number

1 2

2 A

3 B

4 C

5 a

6 b

7 c

RN-001037-03 REV10 – 08.2013 8


The behavior of the “username alphanumeric input order” parameter is applicable to the following username prompts as displayed on the phone’s UI:

• HTTPS Login User Name

• SIP User Name

• SIP Display Name

• SIP Auth. Name

• FTP User Name

Configuring the Alphanumeric Input Order for Username PromptsUse the following parameter to configure the alphanumeric input order for username prompts:

Note:This parameter is set to “0” (uppercase letters first) by default.

Parameter – username alphanumeric input order

Configuration Filesaastra.cfg, <model>.cfg, <mac>.cfg

Description When set to “1”, this parameter changes the default behavior of the keypad input order 6730i, 6731i, 6753i and 9143i IP phones during username prompts from uppercase letters > digit > lowercase letters to digit > uppercase letters > lowercase letters.

For example, when pressing “2” on the keypad during a username prompt with this parameter disabled (default) each key press will successively enter the letter/digit A, B, C, 2, a, b, c. When enabled, each key press will successively enter 2, A, B, C, a, b, c.

Format Integer

Default Value 0 (Uppercase letters first)

Range 0-10 (Uppercase letters first)1 (Digit first)

Example username alphanumeric input order: 1

9 RN-001037-03 REV10 – 08.2013


VLAN ID Assignment Using DHCP

The 6735i and 6737i IP phones now support VLAN ID assignment using Dynamic Host Configuration Protocol (DHCP) Option 43 or Option 132.

If using DHCP Option 43 to assign the VLAN ID, the following sub-options are utilized and the corresponding rules must be followed:

Alternatively, administrators can use the “dhcp option 132 vlan id enabled” parame-ter for VLAN ID assignment by DHCP Option 132. Option 132 provides the same func-tionality as Option 43 but the data format of the VLAN ID value must be 2 bytes, whereas the first and second bytes encompass the VLAN ID (the valid range of the VLAN ID being 1 - 4095).

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.

Note:This feature was already supported in all other IP phones in a previous release.

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 - 4095.

For example, a VLAN ID of 100 (in decimal) is 00 00 00 64 in hexadecimal.

RN-001037-03 REV10 – 08.2013 10


Configuring VLAN ID Assignment Using DHCP Option 132Use the following parameter to configure the VLAN ID 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 REV10 – 08.2013


Configurable Subscription Period for BLF/List Subscriptions

Previously, the “sip blf subscription period” configuration parameter and “BLF Sub-scription Period” Web UI field were applicable only to BLF subscriptions. With Release 3.3.1 SP2, the subscription period for BLF/List subscriptions are now config-urable using the same configuration parameter and Web UI field.

The BLF subscription period feature allows administrators the ability to set the time period, in seconds, in which the IP phone re-subscribes the BLF or BLF/List subscrip-tion service. The minimum value for the BLF subscription period setting is 120 sec-onds (2 minutes) and the maximum is 2147483647 seconds. The default is 3600 (1 hour). The phone re-subscribes to the BLF or BLF/List subscription service before the defined subscription period ends.

Configuring the BLF and BLF/List Subscription Period Using the Configuration FilesUse the following parameter to configure the BLF and BLF/List subscription period:

Parameter – sip blf subscription period


Description The requested duration, in seconds, before the BLF or BLF/List sub-scription times out. The phone re-subscribes to the BLF or BLF/List subscription service before the defined subscription period ends.

Format Integer

Default Value 3600

Range 120 - 2147483647

Example sip blf subscription period: 2000

RN-001037-03 REV10 – 08.2013 12


Configuring the BLF and BLF/List Subscription Period Using the Aastra Web UIUse the following procedure to configure the BLF and BLF/List subscription period using the Aastra Web UI:

Aastra Web UI

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

2. Enter a value, in seconds, from 120 to 2147483647 in the "BLF Subscription Period" field.

3. Click Save Settings to save your changes.

13 RN-001037-03 REV10 – 08.2013


Configurable Beep Tone for Active Voice-over-IP (VoIP) Recording

Administrators can now configure the duration of the audible beep tone and the direction of the tone for the previously implemented active VoIP recording feature (for the 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT IP phones).

When a recording session is in progress, the IP phone will, by default, play a periodic audible beep tone through the selected audio path notifying users that their call is being recorded. Previously, administrators could only enable/disable the beep tone by defining the “recording periodic beep” parameter as “1” or “0” respectively in the configuration files.

Now in Release 3.3.1 SP2, administrators can change the tone interval to play every 15, 30, 45, or 60 seconds (or disable it entirely) using the same “recording periodic beep” parameter.

Administrators can also determine the direction of the beep tone by defining the “recording beep direction” parameter in the configuration files. The direction can be set to local (i.e. tone played on the local phone, audible in handset, loudspeaker, or headset), network (i.e. tone played to the remote phone), or both local and network.

Note:For more information on the active VoIP recording feature refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

RN-001037-03 REV10 – 08.2013 14


Configuring the Active VoIP Recording Beep ToneUse the following parameters to configure the active VoIP recording beep tone:

Parameter – recording periodic beep


Description Specifies how often (in seconds) the periodic beep tone (notifying users that their call is being recorded) should be played.

Format Integer

Default Value 15 (seconds)

Range 0 (Disabled)15304560

Example recording periodic beep: 30

Parameter – recording beep direction


Description Specifies where the periodic beep tone (notifying users that their call is being recorded) should be played.

Format Integer

Default Value 1 (Network)

Range 0-20 (Local)1 (Network)2 (Both Local and Network)

Example recording beep direction: 2

15 RN-001037-03 REV10 – 08.2013



The parameter “sip remove silence suppression offer” has been introduced in Release 3.3.1 SP2 for the 6735i and 6737i IP phones allowing administrators the ability to control whether or not the silence suppression attribute should be included in the Session Description Protocol (SDP) offer.

If enabled (1), the silence suppression attribute will be removed from the SDP offer. If disabled (0), the attribute will not be removed from the SDP offer. This parameter is disabled by default and requires a reboot if the value of the parameter has changed.

Including/Removing the Silence Suppression Attribute from the SDP OfferUse the following parameter to include/remove the silence suppression attribute from the SDP offer:


Parameter – sip remove silence suppression offer


Description Specifies whether or not the silence suppression attribute should be included in the Session Description Protocol (SDP) offer.If enabled, the silence suppression attribute will be removed from the SDP offer. If disabled, the attribute will not be removed from the SDP offer.Note:If the value of this parameter has changed, a reboot will be required for the change to take effect.

Format Boolean

Default Value 0 (Disabled)


Example sip remove silence suppression offer: 1

RN-001037-03 REV10 – 08.2013 16



The global parameter “play a ring splash” controls whether or not a ring splash is played when there is an incoming call on a Busy Lamp Field (BLF) monitored exten-sion. If the host tone is Idle, the tone plays a ring splash.

In 3.3.1 SP2, Administrators can now control the ring splash alert pattern on a per key basis for the 6735i and 6737i IP phones. 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 transitions 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 parameters are available allowing 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”


17 RN-001037-03 REV10 – 08.2013


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.

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

Default value 0 (Disabled)

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 REV10 – 08.2013 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 REV10 – 08.2013


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 REV10 – 08.2013 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 REV10 – 08.2013


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 REV10 – 08.2013 22


Configurable URI Scheme When TLS Enabled

Release 3.1.1 SP2 introduces the “sip send sips over tls” parameter, which allows administrators the ability to manually configure the IP phones to use either the SIP or SIPS URI scheme when TLS or persistent TLS is enabled. Previously, if TLS or persistent TLS was enabled, the IP phones would automatically switch to SIPS mode whereby all URIs in the headers of outgoing messages would conform to the SIPS URI scheme.

Disabling the “sip send sips over tls” parameter (i.e. defining the parameter as “0” in the configuration files) ensures the IP phones use the SIP URI scheme when TLS or persistent TLS is enabled. Enabling the parameter (i.e. defining the parameter as “1”) ensures the phones use the SIPS URI scheme in such scenarios. This parameter is ena-bled by default.

Configuring the URI Scheme to Use When TLS is EnabledUse the following parameter to configure the URI scheme to use when TLS is enabled:

SIP Features

Parameter– sip send sips over tls


Description Allows administrators the ability to manually configure the IP phones to use either the SIP or SIPS URI scheme when TLS or persistent TLS is enabled

Format Integer

Default Value 1 (Enabled)

Range 0-10 (Disabled - Use SIP URI scheme)1 (Enabled - Use SIPS URI scheme)

Example sip send sips over tls: 0

23 RN-001037-03 REV10 – 08.2013


AMR and AMR-WB (G.722.2) Codec Support

Administrators can now configure Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR -WB) codecs on the 6735i and 6737i IP phones. AMR/AMR-WB codecs provide improved speech quality during calls due to wider speech bandwidth, and cover both real-time transfers through Real-time Transport Protocol (RTP) and non-real-time transfers through stored files. AMR supports eight narrowband speech encoding modes (0-7) with bit-rates ranging from 4.75 to 12.2 kilobits per second (kbps). AMR-WB supports nine wideband speech encoding modes (0-8), with bit-rates ranging from 6.60 to 23.85 kbps.

Administrators can configure AMR/AMR-WB on the IP phones in the Customized Codec Preference List on the Web UI or in the configuration files using the existing “sip customized codec” parameter.

Note:AMR/AMR-WB codecs is a licensed feature on the 6735i and 6737i IP phones. To con-firm that the license is active, Administrators can view the license through the phone's Web UI on the Licensing Status page. AMR/AMR-WB should be listed if the feature is available to be used. If Administrators configure AMR/AMR-WB when there is no license, the codec will be ignored and not negotiated.

RN-001037-03 REV10 – 08.2013 24


Customized Codec Settings

Attribute Value

payload

Codec 1Codec 2.....Codec 10(in Web UI)

Configuration Files Web UI

0 - G711u/8000 G.711u (8K)8 - G711a/8000 G.711a (8K)9 - G722/8000 G.72218 - G729/8000 G.72996 - G726-40/8000 G.726-4097 - G726-24/8000 G.726-2498 - G726-16/8000 G.726-16106 - BV16/8000 BV16 (8K)107 - BV32/16000 BV32 (16K)110 - G711u/16000 G711u (16K)111 - G711a/16000 G711a (16K)112 - L16/8000 L16 (8K)113 - L16/16000 L16 (16K)115 - G726-32/8000 G.726-32118 - AMR G.722.2 AMR119 - AMR-WB G.722.2 AMR-WB

Leave blank for all codecs All (Codec 1 only)Basic (Codec 1 only)None (Codecs 2 thru 10 only)

ptime (in milliseconds)

Packetization Interval(in Web UI)

5, 10, 15, 20.......90

silsupp

Silence Suppression(in Web UI)

onoff

25 RN-001037-03 REV10 – 08.2013


If the Customized Codec Preference List is configured as “All”, the phone will set the codec order of preference as per the following table:

Optional parameters have also been created to configure this feature. Administrators can enable the feature by using the “sip amr codec payload format”, which specifies the payload format for AMR/AMR-WB. AMR/AMR-WB can operate in either band-width-efficient mode (0) or in octet-aligned mode (1), depending on the value config-ured. Administrators can also disable the octet-align mode and still send the octet-align:0 header in the Session Description Protocol (SDP) by using value (2) for the parameter. By default, the IP phones utilize bandwidth-efficient mode.

Administrators can also specify the list of mode sets that the IP phones support and state the preferred mode to use if multiple modes are supported by both sides, using the “sip amr codec mode set” and/or the “sip amr wb codec mode set” parameters. If no modes are defined then all codec modes are allowed for the payload type.

Preference Payload Codec

1 0 G711u/8000

2 18 G729/8000

3 106 BV16/8000

4 107 BV32/16000

5 113 BV32/16000

6 110 G711u/16000

7 111 G711a/16000

8 112 L16/8000

9 98 G726-16/8000

10 97 G726-24/8000

11 115 G726-32/8000

12 96 G726-40/8000

13 9 G722/8000

14 8 G711a/8000

15 118 AMR

16 119 AMR-WB (G.722.2)

RN-001037-03 REV10 – 08.2013 26


The following tables list the AMR/AMR-WB codec modes and corresponding bit-rates.

AMR Codec Modes

AMR-WB (G.722.2) Codec Modes

AMR Mode Bit-Rate (kbps)

0 4.75

1 5.15

2 5.90

3 6.70

4 7.40

5 7.95

6 10.2

7 12.2

AMR-WB Mode Bit-Rate (kbps)

0 6.60

1 8.85

2 12.65

3 14.25

4 15.85

5 18.25

6 19.85

7 23.05

8 23.85

27 RN-001037-03 REV10 – 08.2013


Configuring AMR and AMR-WB (G.722.2) Codecs Using the Configuration FilesUse the following parameters to configure AMR and AMR-WB (G722.2) codecs:

Parameter – sip amr codec payload format

Configuration Filesaastra.cfg, <model>.cfg <mac>.cfg

Description Specifies the payload format for the AMR/AMR-WB codec.

Format Integer

Default Value 0

Range 0-2

0 (Enable bandwidth efficient mode per RFC, no octet-aligned header is in the INVITE SDP [default]).

1 (Enable octet-aligned mode and add octet-align:1 in SDP, negotiate mode for incoming calls).

2 (Disable octet-aligned mode and add octet-align:0 in SDP, negotiate mode for incoming calls).

Example sip amr codec payload format: 1

Parameter – sip amr codec mode set


Description Specifies the list of mode sets supported and also the preferred mode to use if multiple modes are supported by both sides.

Format Integer

Default Value 0

Range 0-70 (4.75 kbps)1 (5.15 kbps)2 (5.90 kbps)3 (6.70 kbps)4 (7.40 kbps)5 (7.95 kbps)6 (10.2 kbps)7 (12.2 kbps)

Example sip amr codec mode set: 2,1,0,3,4

RN-001037-03 REV10 – 08.2013 28


Parameter – sip amr wb codec mode set


Description Specifies the list of mode sets supported and also the preferred mode to use if multiple modes are supported by both sides.

Format Integer

Default Value 0

Range 0-80 (6.60 kbps)1 (8.85 kbps)2 (12.65 kbps)3 (14.25 kbps)4 (15.85 kbps)5 (18.25 kbps)6 (19.85 kbps)7 (23.05 kbps)8 (23.85 kbps)

Example sip amr wb codec mode set: 2,1,0

29 RN-001037-03 REV10 – 08.2013


Parameter – sip customized codec

Codec Preference List(in Web UI)

Aastra Web UIAdvanced Settings->Global SIP->RTP Settings


Description Specifies a customized codec preference list which allows you to select the preferred codecs for this IP phone. You can enter up to 10 codec preferences.

Note:Enabling or disabling silence suppression (sil supp) enables/disables it for all codecs in the customized list. When mismatch occurs in the configured silsupp parameter, the first one specified in the parameter value will be used.

Format Comma-separated list of semicolon-separated values

Default Value Not Applicable

Range Valid values for the syntax are:

payload:Configuration Files Web UI0 - G711u/8000 G.711u (8K)8 - G711a/8000 G.711a (8K)9 - G722/8000 G.72218 - G729/8000 G.72996 - G726-40/8000 G.726-4097 - G726-24/8000 G.726-2498 - G726-16/8000 G.726-16106 - BV16/8000 BV16 (8K)107 - BV32/16000 BV32 (16K)110 - G711u/16000 G711u (16K)111 - G711a/16000 G711a (16K)112 - L16/8000 L16 (8K)113 - L16/16000 L16 (16K)115 - G726-32/8000 G.726-32118 - AMR G.722.2 AMR119 - AMR-WB G.722.2 AMR-WB

Leave blank for all codecs All (Codec 1 only)Basic (Codec 1 only)None (Codecs 2 thru 10 only)

ptime (in milliseconds) 5, 10, 15, 20........90

silsupp on, off

Note:The “silsupp” value is either ON for all codecs or OFF for all codecs.

Example For codec preference for AMR-WB, then G.722/8000, then, G.711u/8000 - sip customized codec: payload=119;ptime=20;silsupp=on,payload=9;ptime=20;silsupp=on,payload=0;ptime=20;silsupp=on

RN-001037-03 REV10 – 08.2013 30


Configuring AMR and AMR-WB (G.722.2) Codecs Using the Aastra Web UIUse the following procedure to configure AMR and AMR-WB (G.722.2) codecs using the Aastra Web UI:

Aastra Web UI

1. Click on Advanced Settings->Global SIP->RTP Settings or Advanced Settings->Line <N>->RTP Settings.

Global Settings

Per-Line Settings

31 RN-001037-03 REV10 – 08.2013


2. Enter an RTP Port Base in the RTP Port field. Default is 3000.The RTP Port indicates the port through which the RTP packets are sent. This value must specify the beginning of the RTP port range on the gateway or router. The RTP port is used for sending DTMF tones and for the audio stream. Your network administrator may close some ports for security reasons. You may want to use this parameter to send RTP data using a different port.

Note:The phones support decoding and playing out DTMF tones sent in SIP INFO requests. The following DTMF tones are supported:• Support signals 0-9, #, *• Support durations up to 5 seconds

3. The "Force RFC2833 Out-of-Band DTMF" field is enabled by default. Disable this field by unchecking the box. Enabling this parameter forces the IP phone to use out-of-band DTMF according to RFC2833.

4. Select a method to use from the “DTMF Method” list box. Valid values are RTP, SIP Info, Both. Default is RTP.

Note:You can configure the DTMF Method on a global or per-line basis.

5. Select the type of RTP encryption to use from the “RTP Encryption” list box. Valid values are SRTP Disabled, SRTP Preferred, or SRTP Only. Default is SRTP Disabled.

Note:You can configure RTP Encryption on a global or per-line basis.

RN-001037-03 REV10 – 08.2013 32


6. In the Codec Preference List, select a codec (with its payload type) you want the phones to use. Valid values are:• All• Basic (G.711 u-law, G.711 a-law, G.729)• G722• G711u/8K• G711u/16K• G711a/8K• G711a/16K• G729• G726-16• G726-24• G726-32• G726-40• BV16 (8K)• BV32 (16K)• L16 (8K)• L16 (16K)• AMR• AMR-WB (G.722.2)

Notes:• Setting Codec 1 to “All” ignores the packetization interval (ptime). The packetization inter-

val setting defaults to 30, which is the default for all codecs. • Setting Codec 1 to “All” automatically sets all other codec preference fields 2 through 10

to “None”.• Setting Codec 1 to “Basic” and all other codec preferences in 2 through 10 to “None”, forces

the phone to use only the basic codecs as in previous releases (G.711 u-law, G.711 a-law, and G.729). If you select an additional codec to use in the codec preferences 2 through 10 fields, those codecs are added to the list of Basic codecs for the phone to use.

33 RN-001037-03 REV10 – 08.2013


7. (Optional) In Codec 2 through Codec 10, select a preference of codecs (with its payload type) to use on the phone. Valid values are:• None• G722• G711u/8K• G711u/16K• G711a/8K• G711a/16K• G729• G726-16• G726-24• G726-32• G726-40• BV16 (8K)• BV32 (16K)• L16 (8K)• L16 (16K)• AMR• AMR-WB (G.722.2)

Note:You can select up to 9 codecs in addition to the codec you selected in step 6.

8. In the “Packetization Interval” field, select the time, in milliseconds. Valid values are 5 to 90, in increments of 5 milliseconds.

9. The “Silence Suppression” field is enabled by default. Disable this field by unchecking the check box.When enabled, the phone negotiates whether or not to use silence suppression. Disabling this feature forces the phone to ignore any negotiated value.

10. Click Save Settings to save your changes.

RN-001037-03 REV10 – 08.2013 34


BroadSoft BroadWorks Executive and Assistant Services Feature

Release 3.3.1 SP2 introduces support for the BroadSoft BroadWorks Executive and Assistant Services feature for the 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT IP phones. The Executive and Assistant Services feature allows Administrators to create an inter-network relationship between Executives and Assist-ants allowing calls to the Executive’s phone to be screened, filtered, and routed to an Assistant, whereby the Assistant can answer, divert the filtered call, or push the call back to the Executive.

Configuration ParametersAfter configuring the applicable options on the BroadSoft Broadworks call manager Web portal, Administrators must define the newly introduced “sip execassist filter call prefix”, “sip execassist fac call push”, and “sip execassist fac initiate call” parameters for the phone.

The “sip execassist filter call prefix” parameter is used to identify the prefix of the Alerting Custom Calling Line ID Name of a filtered call. The Alerting Custom Calling Line ID Name as configured in the BroadWorks Web portal should follow the format:

[prefix] [Identifier] -> [Executive Name]

The Executive Name must match the name that is configured in the user’s profile, sep-arated by a space or comma.

For example, if the “Alerting Custom Calling Line ID Name” setting in the BroadWorks Web portal is defined as “[F] Filtrage -> Dupont, Francois”, the From header of a filtered call sent by the BroadWorks SIP INVITE message will look similar to:

From:”[F] Filtrage -> Dupont, Francois"<sip:[email protected];user=phone>

The “sip execassist filter call prefix”parameter in this scenario could be defined as:sip execassist filter call prefix: "[F]"

Note:The inter-network relationship is created dynamically through the BroadSoft Broad-Works call manager Web portal. For BroadSoft BroadWorks Executive and Assistant Services Web portal configuration details and procedures, please refer to the respective BroadSoft documentation.

Note:The Alerting Calling Line ID Number can either be configured as the Executive’s Number or Originator’s Number.

35 RN-001037-03 REV10 – 08.2013


The Assistant’s phone will parse the From header of the SIP INVITE message of an incoming call sent by the call manager and will identify whether or not the call is a fil-tered call by the prefix. The prefix itself is not displayed on the phone’s screen (e.g. in the case outlined above, the phone will only display “Filtrage -> Dupont, Francois”).

The “sip execassist fac call push” parameter is used to specify the Feature Access Code (FAC) that is used to push a filtered call from the Assistant’s phone back to the Executive’s phone. The FAC should correspond to the value configured for the “Execu-tive-Assistant Call Push” setting defined in the BroadSoft Web portal.

The “sip execassist fac initiate call” parameter is used to specify the FAC that is used by Assistants to initiate a call on behalf of the Executive. The FAC should correspond to the value configured for the “Executive-Assistant Initiate Call” setting defined in the BroadSoft Web portal.

Configuring the Filter Call Prefix and Call Push and Initiate Call FACsUse the following parameter to configure the filter call prefix and call push FAC:

Parameter– sip execassist filter call prefix


Description Specifies the prefix of the Alerting Custom Calling Line ID name con-figured for Executives. For an incoming call, the phone will treat the call as a filtered call if the prefix is found in the front of the display name of the FROM header of the INVITE. The prefix from the display name of the FROM header or PAI header will be stripped before it is displayed on the phone’s screen.For example, if the From header sent by the BroadWorks call manager SIP INVITE message is:

From:”[F] Filtrage -> Dupont, Francois”<sip:[email protected];user=phone>

then the IP phone displays the calling name as “Filtrage -> Dupont, Francois” since the “[F]” prefix is removed.

Format String (in quotations)

Default Value "[F]"

Range N/A

Example sip execassist filter call prefix: "[F]"

RN-001037-03 REV10 – 08.2013 36


Filter SoftkeyIn addition to the new parameters, a “Filter” softkey type has been introduced allow-ing both Executives and Assistants the ability to easily activate and deactivate the Executive Call Filtering feature.

Parameter– sip execassist fac call push


Description Specifies the Feature Access Code (FAC) for the BroadSoft Executive- Assistant Call Push feature.


Default Value "#63"

Range N/A

Example sip execassist fac call push: "#63"

Parameter– sip execassist fac initiate call


Description Specifies the Feature Access Code (FAC) for the BroadSoft Executive- Assistant Initiate Call feature.


Default Value "#64"

Range N/A

Example sip execassist fac initiate call: "#64"

Notes:• The As-Feature Event Subscription option must also be enabled for the Filter

softkey to function. This feature can be enabled by defining the “sip lineN as-feature-event subscription” parameter as “1” in the configuration files (where “N” corresponds to the applicable line) or through the phone’s Web UI under Advanced Settings > LineN > Advanced SIP Settings > As-Feature-Event Subscription. Refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide for additional details on the As-Feature Event Subscription feature.

37 RN-001037-03 REV10 – 08.2013


Filter Softkey for the Executive’s PhoneThe Executive’s phone requires that only one Filter softkey be configured. The Filter softkey’s value can either be left undefined (which will toggle the Executive Call Filter-ing settings on the call manager via the SIP SUBSCRIPTION/NOTIFY mechanism) or, it can be defined using the following values (which will toggle the settings via an FAC call):

• Executive Call Filtering Activation FAC (e.g. "#61")

– Used when the Deactivation FAC is in the same format as the Activation FAC but sequentially one number above the Activation FAC. For example, if the softkey value is defined as "#61" (the Activation FAC), the phone will automatically assume that the Deactivation FAC is "#62" and will use that code to deactivate Executive Call Filtering.

• Executive Call Filtering Activation FAC followed by a semi-colon and then Executive Call Filtering Deactivation FAC (e.g. "#61;*61" or "#61;#71")

– Used when the Activation and Deactivation FACs are not in the same format or when they are not sequential. For example, if the Activation FAC is configured in the BroadSoft BroadWorks Web portal is "#61" and the Deactivation FAC is config-ured as "*61" or "#71", the softkey value should be defined with the two specific FACs separated by a semi-colon (i.e. "#61;*61" or "#61;#71" respectively).

Irrespective of a defined or undefined key value, when the Filter softkey is pressed, Executive Call Filtering will be activated and the softkey’s corresponding LED will be lit. When the Filter softkey is pressed again, Executive Call Filtering will deactivate and the softkey’s corresponding LED will turn off.

Notes:• If the Deactivation FAC is not specified after the semi-colon (e.g. "#61;"), the phone

will ignore the semi-colon and behave as if only the Activation FAC was defined (i.e. the phone will automatically assume that the Deactivation FAC is in the same format but sequentially one number above the Activation FAC.

• The IP phones support Executive Call Filtering Activation/Deactivation FACs that contain the prefix “#” or “*”.

Note:Upon a reboot, the initial state of the Filter softkey LED will correspond to the Exec-utive Call Filtering state configured on the call manager.

RN-001037-03 REV10 – 08.2013 38


Configuring the Filter Softkey on the Executive’s Phone Using the Aastra Web UIUse the following procedure to configure the Filter Softkey on the Executive’s phone using the Aastra Web UI:

Configuring the Filter Softkey on the Executive’s Phone Using the Configuration FilesTo configure the Filter softkey on the Executive’s phone using the configuration files, you must enter “filter” for the key type. For the label (5-line phones only), enter a key label to assign to the Filter key (e.g. “Filter”). Defining the value is optional. If you pre-fer to toggle Executive Call Filtering using an FAC call, enter in the Executive Call Filter-ing Activation FAC (e.g. "#61") or both the Executive Call Filtering Activation and Deac-tivation FACs followed by a semi-colon (e.g. "#61;*61") for the value. For the line set-ting, enter the line number for which you want to use the key functionality.

Aastra Web UI

1. Click on Operation->Softkeys and XML.orClick on Operation-> Programmable Keys.orClick on Operation->Expansion Module Keys.

2. Select a key that you want to use as a Filter activate/deactivate key.

3. In the "Type" field, select "Filter".

4. In the "Label" field (5-line phones only), enter a label to apply to this key (e.g. Filter).

5. (Optional) In the "Value" field, enter the Executive Call Filtering Activation FAC (e.g. #61) or both the Executive Call Filtering Activation and Deactivation FACs followed by a semi-colon (e.g. #61;*61).

6. In the “Line” field, select the line for which you want to use the key functionality.

7. Click Save Settings to save your settings.

39 RN-001037-03 REV10 – 08.2013


The following parameters are examples you can use to configure the Filter softkey on the Executive’s phone:

For Softkeyssoftkey1 type: filter

softkey1 label: Filter

softkey1 value: "#61;*61"

softkey1 line: 1

For Programmable Keysprgkey1 type: filter

prgkey1 value: "#61;*61"

prgkey1 line: 1

For Top Softkeystopsoftkey1 type: filter

topsoftkey1 label: Filter

topsoftkey1 value: "#61;*61"

topsoftkey1 line: 1

For Expansion Module Softkeysexpmod1 key1 type: filter

expmod1 key1 label: Filter

expmod1 key1 value: "#61;*61"

expmod1 key1 line: 1

Filter Softkey for the Assistant’s PhoneAs an Assistant can be associated with multiple Executives simultaneously, the Assist-ant’s phone can be configured with multiple Filter softkeys; one softkey for each Exec-utive. In this case, the value of each Filter softkey should correspond to the phone number or extension of the respective Executive as per configured in the user’s pro-file.

Note:For more information on how to configure softkeys, programmable keys, and expansion module softkeys using the configuration files, please refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

RN-001037-03 REV10 – 08.2013 40


When Filter softkeys are configured with key values, pressing the respective Filter softkey will activate Executive Call Filtering for the applicable Executive and the softkey’s corresponding LED will be lit. When the same Filter softkey is pressed again, Executive Call Filtering for the applicable Executive will deactivate and the softkey’s corresponding LED will turn off.

Alternatively, a single Filter softkey can be configured without a defined key value. If this is the case, the Assistant will be able to manually activate and deactivate Execu-tive Call Filtering for each associated Executive through the phone’s UI. In this sce-nario, as only one Filter softkey is utilized, the softkey’s corresponding LED will be lit when Executive Call Filtering is activated for even one associated Executive. If Execu-tive Call Filtering is disabled for all associated Executives, the softkey’s corresponding LED will turn off.

Configuring the Filter Softkey on the Assistant’s Phone Using the Aastra Web UIUse the following procedure to configure the Filter Softkey on the Assistant’s phone using the Aastra Web UI:

Note:If Call Forward is enabled for filtered calls, LEDs for all Filter softkeys will be turned off.

Aastra Web UI


2. Select a key that you want to use as a Filter activate/deactivate key.

3. In the "Type" field, select "Filter".

41 RN-001037-03 REV10 – 08.2013


Configuring the Filter Softkey on the Assistant’s Phone Using the Configuration FilesTo configure the Filter softkeys on the Assistant’s phone using the configuration files, you must enter “filter” for the key types. For the labels (5-line phones only), enter key labels to assign to the Filter key (e.g. “Filter-Stefan” for a specific Executive or simply “Filter” for a generic Filter key with no defined value). Defining the value is optional. If you choose to assign a Filter softkey and define values for each Executive, enter in the respective Executive’s phone or extension number (e.g. 4100). For the line setting, enter the line number for which you want to use the key functionality. If you prefer to utilize a single Filter softkey without a defined value you will be able to manually acti-vate and deactivate Executive Call Filtering for each Executive to whom the Assistant is assigned through the phone’s UI.

The following parameters are examples you can use to configure multiple Filter softkeys corresponding to multiple Executives on the Assistant’s phone:

For Softkeyssoftkey1 type: filter

softkey1 label: Filter-Stefan

softkey1 value: 4100

softkey1 line: 1

softkey2 type: filter

softkey2 label: Filter-John

softkey2 value: 4101

softkey2 line: 1

4. In the "Label" field (5-line phones only), enter a label to apply to this key (e.g. Filter-Stefan for a specific Executive or simply Filter for a generic Filter key with no defined value).

Note:To utilize a single Filter softkey without a defined key value (so that you can manually acti-vate and deactivate Executive Call Filtering through the phone’s UI) skip to Step 8.

5. In the "Value" field, enter the Executive’s phone or extension number (e.g. 4100)

6. In the “Line” field, select the line for which you want to use the key functionality.

7. Repeat Steps 2 to 6 for each respective Executive for whom you would like to assign a Filter key.


RN-001037-03 REV10 – 08.2013 42


For Programmable Keysprgkey1 type: filter

prgkey1 value: 4100

prgkey1 line: 1

prgkey2 type: filter

prgkey2 value: 4101

prgkey2 line: 1

For Top Softkeystopsoftkey1 type: filter

topsoftkey1 label: Filter-Stefan

topsoftkey1 value: 4100

topsoftkey1 line: 1

topsoftkey2 type: filter

topsoftkey2 label: Filter-John

topsoftkey2 value: 4101

topsoftkey2 line: 1

For Expansion Module Softkeysexpmod1 key1 type: filter

expmod1 key1 label: Filter-Stefan

expmod1 key1 value: 4100


expmod1 key2 type: filter

expmod1 key2 label: Filter-John

expmod1 key2 value: 4101



43 RN-001037-03 REV10 – 08.2013


Speeddial Softkey with Initiate Call Functionality (Assistants Only)Speeddial softkeys can be configured to efficiently utilize the Executive-Assistant Initi-ate Call function. With a Speeddial softkey configured for this feature, Assistants can initiate a call on behalf of an Executive, whereby the call will appear to the target as one originated by the Executive himself/herself. The Speeddial softkey’s value can be defined using the following syntax:

• Executive-Assistant Initiate Call FAC (e.g. "#64"):

– In such scenarios, the call manager will play an audible prompt asking you to enter the Executive’s Address and Destination Address manually using the key-pad.

• Executive-Assistant Initiate Call FAC followed by the Executive’s Address (e.g. "#644052"):

– In such scenarios, only the Destination Address will need to be manually entered using the keypad.

• Executive-Assistant Initiate Call FAC, followed by the Executive’s Address, an aster-isk, and then the Destination Address (e.g. "#644052*4059"):

– In such scenarios, addresses will not need to be manually entered and the phone will automatically initiate the call to the target phone on behalf of the Executive.

Note:The Speeddial softkey type can be utilized for additional functions related to the Executive and Assistant Services feature that rely on FAC calls (i.e. opting in to an Executive’s filtered call pool, opting out of an Executive’s filtered call pool, etc...). Administrators simply need to configure the Speeddial key value as the FAC and label accordingly.

RN-001037-03 REV10 – 08.2013 44


Configuring the Initiate Call Softkey on the Assistant’s Phone Using the Aastra Web UIUse the following procedure to configure the Initiate Call Softkey on the Assistant’s phone using the Aastra Web UI:

Aastra Web UI


2. Select a key that you want to use as an Initiate Call key.

3. In the "Type" field, select "Speeddial".

4. In the "Label" field (5-line phones only), enter a label to apply to this key (e.g. Init).

5. In the "Value" field, enter the Initiate Call FAC (e.g. #64)or In the "Value" field, enter the Initiate Call FAC, followed by the Executive’s Address (e.g. #644052)orIn the "Value" field, enter the Initiate Call FAC, the Executive’s Address, followed by an asterisk, and then the Destination Address (e.g. #644052*4059)

6. In the "Line" field, select the line for which you want to use the key functionality.


45 RN-001037-03 REV10 – 08.2013


Configuring the Initiate Call Softkey on the Assistant’s Phone Using the Configuration FilesTo configure the Initiate Call Speeddial softkeys on the Assistant’s phone using the configuration files, you must enter “speeddial” for the key types. For the labels (5-line phones only), enter key labels to assign to the Speeddial key (e.g. “Init”). For the val-ues, enter one of the following:

• Executive-Assistant Initiate Call FAC (e.g. "#64")

• Executive-Assistant Initiate Call FAC followed by the Executive’s Address (e.g. "#644052")

• Executive-Assistant Initiate Call FAC, followed by the Executive’s Address, an aster-isk, and then the Destination Address (e.g. "#644052*4059")

For the line setting, enter the line number for which you want to use the key function-ality.

The following parameters are examples you can use to configure multiple Initiate Call Speeddial softkeys:

For Softkeyssoftkey1 type: speeddial

softkey1 label: Init

softkey1 value: "#64"softkey1 line: 1

softkey2 type: speeddial

softkey2 label: Init2

softkey2 value: "#644052"softkey2 line: 1

softkey3 type: speeddial

softkey3 label: Init3

softkey3 value: "#644052*4059"softkey3 line: 1

For Programmable Keysprgkey1 type: speeddial

prgkey1 value: "#64"prgkey1 line: 1

RN-001037-03 REV10 – 08.2013 46


prgkey2 type: speeddial

prgkey2 value: "#644052"prgkey2 line: 1

prgkey3 type: speeddial

prgkey3 value: "#644052*4059"prgkey3 line: 1

For Top Softkeystopsoftkey1 type: speeddial

topsoftkey1 label: Init

topsoftkey1 value: "#64"topsoftkey1 line: 1

topsoftkey2 type: speeddial

topsoftkey2 label: Init2

topsoftkey2 value: "#644052"topsoftkey2 line: 1

topsoftkey3 type: speeddial

topsoftkey3 label: Init3

topsoftkey3 value: "#644052*4059"topsoftkey3 line: 1

For Expansion Module Softkeysexpmod1 key1 type: speeddial

expmod1 key1 label: Init

expmod1 key1 value: "#64"expmod1 key1 line: 1

expmod1 key2 type: speeddial

expmod1 key2 label: Init2

expmod1 key2 value: "#644052"expmod1 key2 line: 1

expmod1 key2 type: speeddial

expmod1 key2 label: Init3

expmod1 key2 value: "#644052*4059"expmod1 key2 line: 1

47 RN-001037-03 REV10 – 08.2013


Executive and Assistant Services Feature Usage

Executive Phone FeaturesUsers with phones assigned with the Executive role are able to:

• Activate and deactivate the Executive Call Filtering service from the phone

• Intercept or ignore filtered calls before they are transferred to the Assistant

To Activate Executive Call Filtering on the Executive’s PhoneUse the following procedure to activate Executive Call Filtering on the Executive’s phone:

For All Phones


IP Phone UI

1. Press the configured “Filter” key.Executive Call Filtering is now activated and the key’s corresponding LED will be lit.

Stefan BayL1

13/05/13 11:40

Filter

MoreCall ForwardDND

Filter

Stefan Bay1

13/05/13 11:40

RN-001037-03 REV10 – 08.2013 48


To Deactivate Executive Call Filtering on the Executive’s PhoneUse the following procedure to deactivate Executive Call Filtering on the Executive’s phone:

For All Phones

IP Phone UI

1. Press the configured “Filter” key.Executive Call Filtering is now deactivated and the key’s corresponding LED will be turned off.

Stefan BayL1

13/05/13 11:40

Filter

MoreCall ForwardDND

Filter

Stefan Bay1

13/05/13 11:40

49 RN-001037-03 REV10 – 08.2013


To Intercept a Filtered Call Before it is Transferred to an AssistantUse the following procedure to intercept a filtered call before it is transferred to an Assistant:

For the 6730i, 6731i, 6753i, and 9143i IP Phones

IP Phone UI

1. (Optional) If the caller’s name is truncated, press the Down navigation key to view the rest of the caller’s name. Press the Up navigation key to return to the initial view.If the caller’s number is also truncated, press and hold the Down navigation key until the rest of the caller’s number is displayed on screen. Press and hold the Up navigation key to return to the initial view.

2. Lift the handset or press the Speaker/Headset button if the phone has no active callsorPress the corresponding Line button if on an active call.

Stefan Bay-Igor2

+33130964202

2

+33130964202Hein

RN-001037-03 REV10 – 08.2013 50


For the 6755i, 6757i, 6757i CT, 9840i, and 9840i CT IP Phones


2. Lift the handset, press the Speaker/Headset button, or press the Answer softkey if the phone has no active callsorPress the Answer softkey if on an active call.

Stefan BayL2

Stefan Bay-Jean-Emil+33130964200

Answer

MoreIgnore

Stefan BayL2

e Paraiso+33130964200

Answer

MoreIgnore

51 RN-001037-03 REV10 – 08.2013


To Ignore a Filtered CallUse the following procedure to ignore a filtered call:


IP Phone UI


2. Press the Goodbye button if the phone has no active callsorPress the Goodbye button if on an active call and the Goodbye Key Cancels Incoming Call feature is enabledorPress and hold the Ignore key until the call is successfully ignored if on an active call and the Goodbye Key Cancels Incoming Call feature is disabled.

Stefan Bay-Igor2

+33130964202

2

+33130964202Hein

RN-001037-03 REV10 – 08.2013 52




2. Press the Goodbye button or Ignore softkey if the phone has no active callsorPress the Ignore softkey if on an active call.

Stefan BayL2


Answer

MoreIgnore

Stefan BayL2

e Paraiso+33130964200

Answer

MoreIgnore

53 RN-001037-03 REV10 – 08.2013


Assistant Phone FeaturesUsers with phones assigned with the Assistant role are able to:

• Activate and deactivate the Executive Call Filtering service from the phone

• Answer or ignore a filtered call

• Push a filtered call back to the Executive

• Perform a blind transfer of a filtered call to the Executive

• Perform a semi-attended transfer of a filtered call to the Executive

• Perform a consultative transfer of a filtered call to the Executive

• Activate and deactivate call forwarding of the Executive’s filtered calls

• Initiate a call on behalf of an Executive

Notes:• Push functionality does not carry over to the target phone when call forwarding of

an Executive’s filtered calls is enabled.• Assistants are also able to handle filtered calls in the same manner as unfiltered

calls. For information on handling calls (e.g. placing calls on hold, transferring calls to another party, conferencing calls, etc...) please refer to the respective Aastra IP Phone User Guide.

RN-001037-03 REV10 – 08.2013 54


To Activate Executive Call Filtering on the Assistant’s Phone when the Filter Key’s Value is DefinedUse the following procedure to activate Executive Call Filtering on the Assistant’s phone when the Filter key’s value is defined:

For All Phones

IP Phone UI

1. Press the configured “Filter” key corresponding to the respective Executive (e.g. “Filter-Ste-fan).Executive Call Filtering is now activated for that Executive and the key’s corresponding LED will be lit.

Note:If Call Forward is enabled for filtered calls, LEDs for all Filter keys will be turned off.

Susan SmithL1

13/05/13 11:40

Filter-Stefan

MoreFilter-JohnDND

Susan Smith1

13/05/13 11:40

Filter-Stefan Filter-John

55 RN-001037-03 REV10 – 08.2013


To Activate Executive Call Filtering on the Assistant’s Phone when the Filter Key’s Value is Not DefinedUse the following procedure to activate Executive Call Filtering on the Assistant’s phone when the Filter key’s value is not defined:


IP Phone UI

1. Press the “Filter” key.The list of associated Executives will appear on screen.

2. Select the Executive for whom you want to activate Executive Call Filtering by pressing the Up or Down navigation keys and then press the Change key.

3. Press the Up or Down navigation key to enter the Filtering menu for the respective Executive.

4. Press the Change key.

Executives1.John Allen X Done Change

Filter

Executives2.Stefan Bay X Done Change

Stefan Bay

Use to view

FilteringOFF Done Change

RN-001037-03 REV10 – 08.2013 56


5. Press the Next key to toggle the Filtering option from OFF to ON.

6. Press the Set key.

7. Press the Done key.

A checkmark will be displayed beside the Executive indicating Executive Call Filtering is to be activated.

8. Press the Done key again.

9. Press the Confirm key to apply the changes and return to the idle screen.

Notes:• The LED corresponding to the “Filter” key will be lit if Executive Call Filtering is activated

for any associated Executive. The LED will turn off if Executive Call Filtering is deactivated for all associated Executives.

• If Call Forward is enabled for filtered calls, the LED for the Filter softkey will be turned off.

FilteringOFF Next Set

FilteringON Next Set

FilteringON Done Change

Executives2.Stefan Bay Done Change

Apply Changes?0Cancel #Confirm

57 RN-001037-03 REV10 – 08.2013



1. Press the “Filter” softkey.The list of associated Executives will appear on screen.

2. Select the Executive for whom you want to activate Executive Call Filtering by pressing the Up or Down navigation keys and then press the Change softkey to enter the Filtering menu for the respective Executive.

3. Press the Change softkey to toggle the Filtering option from OFF to ON.

Executives 1.François Dupont X 2.Stefan Bay X 3.Jane Webber X 4.John Allen XChange

DoneAll OnAll Off

Cancel


DoneAll OnAll Off

Cancel

Stefan Bay

Filtering: OFFOpt Status: Unknown

Change

DoneCancel

RN-001037-03 REV10 – 08.2013 58


4. Press the Done softkey.

A checkmark will be displayed beside the Executive indicating Executive Call Filtering is to be activated.

5. Press the Done softkey to return to the idle screen.

Notes:• The LED corresponding to the “Filter” softkey will be lit if Executive Call Filtering is acti-

vated for any associated Executive. The LED will turn off if Executive Call Filtering is deac-tivated for all associated Executives.


Stefan Bay

Filtering: ONOpt Status: Unknown

Change

DoneCancel

Executives 1.François Dupont X 2.Stefan Bay � 3.Jane Webber X 4.John Allen XChange

DoneAll OnAll Off

Cancel

59 RN-001037-03 REV10 – 08.2013


To Deactivate Executive Call Filtering on the Assistant’s Phone when the Filter Key’s Value is DefinedUse the following procedure to deactivate Executive Call Filtering on the Assistant’s phone when the Filter key’s value is defined:

For All Phones

IP Phone UI

1. Press the configured “Filter” softkey corresponding to the respective Executive (e.g. “Filter-Stefan).Executive Call Filtering is now deactivated for that Executive and the softkey’s corresponding LED will turn off.

Note:If Call Forward is enabled for filtered calls, LEDs for all Filter softkeys will be turned off.

Susan SmithL1

13/05/13 11:40

Filter-Stefan

MoreFilter-JohnDND

Susan Smith1

13/05/13 11:40

Filter-Stefan Filter-John

RN-001037-03 REV10 – 08.2013 60


To Deactivate Executive Call Filtering on the Assistant’s Phone when the Filter Key’s Value is Not DefinedUse the following procedure to deactivate Executive Call Filtering on the Assistant’s phone when the Filter key’s value is not defined:


IP Phone UI

1. Press the “Filter” key.The list of associated Executives will appear on screen.

2. Select the Executive for whom you want to deactivate Executive Call Filtering by pressing the Up or Down navigation keys and then press the Change key.

3. Press the Up or Down navigation key to enter the Filtering menu for the respective Executive.

4. Press the Change key.

Executives1.John Allen X Done Change

Filter

Executives2.Stefan Bay Done Change

Stefan Bay

Use to view

FilteringON Done Change

61 RN-001037-03 REV10 – 08.2013


5. Press the Next key to toggle the Filtering option from ON to OFF.



An X will be displayed beside the Executive indicating Executive Call Filtering is to be deac-tivated.

8. Press the Done key again.

9. Press the Confirm key to apply the changes and return to the idle screen.

Notes:• The LED corresponding to the “Filter” key will be lit if Executive Call Filtering is activated

for any associated Executive. The LED will turn off if Executive Call Filtering is deactivated for all associated Executives.


FilteringON Next Set

FilteringOFF Next Set

FilteringOFF Done Change

Executives2.Stefan Bay X Done Change


RN-001037-03 REV10 – 08.2013 62



1. Press the “Filter” softkey.The list of associated Executives will appear on screen.

2. Select the Executive for whom you want to deactivate Executive Call Filtering by pressing the Up or Down navigation keys and then press the Change softkey to enter the Filtering menu for the respective Executive.

3. Press the Change softkey to toggle the Filtering option from ON to OFF.


DoneAll OnAll Off

Cancel


DoneAll OnAll Off

Cancel

Stefan Bay

Filtering: ONOpt Status: Unknown

Change

DoneCancel

63 RN-001037-03 REV10 – 08.2013


4. Press the Done softkey.

An X will be displayed beside the Executive indicating Executive Call Filtering is to be deac-tivated.

5. Press the Done softkey to return to the idle screen.

Notes:• The LED corresponding to the “Filter” softkey will be lit if Executive Call Filtering is acti-

vated for any associated Executive. The LED will turn off if Executive Call Filtering is deac-tivated for all associated Executives.


Stefan Bay

Filtering: OFFOpt Status: Unknown

Change

DoneCancel


DoneAll OnAll Off

Cancel

RN-001037-03 REV10 – 08.2013 64


To Answer a Filtered CallUse the following procedure to answer a filtered call:


IP Phone UI


2. Lift the handset or press the Speaker/Headset button if the phone has no active callsorPress the corresponding Line button if on an active call.

Stefan Bay-Igor2

+33130964202

2

+33130964202Hein

65 RN-001037-03 REV10 – 08.2013




2. Lift the handset, press the Speaker/Headset button, or press the Answer softkey if the phone has no active callorPress the Answer softkey if on an active call.

Susan SmithL1


Answer

MoreIgnore

Susan SmithL1

e Paraiso+33130964200

Answer

MoreIgnore

RN-001037-03 REV10 – 08.2013 66


To Ignore a Filtered CallUse the following procedure to ignore a filtered call:


IP Phone UI


2. Press the Goodbye button if the phone has no active callsorPress the Goodbye button if on an active call and the Goodbye Key Cancels Incoming Call feature is enabledorPress and hold the Ignore key until the call is successfully ignored if on an active call and the Goodbye Key Cancels Incoming Call feature is disabled.

Stefan Bay-Igor2

+33130964202

2

+33130964202Hein

67 RN-001037-03 REV10 – 08.2013




2. Press the Goodbye button or Ignore softkey if the phone has no active callsorPress the Ignore softkey if on an active call.

Susan SmithL1


Answer

MoreIgnore

Susan SmithL1

e Paraiso+33130964200

Answer

MoreIgnore

RN-001037-03 REV10 – 08.2013 68


To Push a Filtered Call Back to the ExecutiveUse the following procedure to push a filtered call back to the Executive:



IP Phone UI

1. After answering a filtered call, press the Transfer button twice.

The phone will enter in the FAC for the BroadSoft Executive-Assistant Call Push feature and automatically dial the FAC call.The FAC call will be answered and the filtered call will be released if the push is successful.

Note:If the push is unsuccessful, press the respective Line key (corresponding to the filtered call) to retrieve the filtered call.

1. After answering a filtered call, press the Push softkey.


Note:If the push is unsuccessful, press the Pickup softkey to retrieve the filtered call.

1 Stefan Bay-Igor+33130964201

01:00

Susan SmithL1

Igor Hein+33130964200 01:01

Drop

MoreConfXfer

Push

69 RN-001037-03 REV10 – 08.2013


To Perform a Blind Transfer of a Filtered Call to the ExecutiveUse the following procedure to perform a blind transfer of a filtered call to the Execu-tive:


IP Phone UI

1. After answering a filtered call, press the Transfer button.

2. Enter the Executive’s phone or extension number and press the Transfer button.

The phone will recognize the Executive’s number and will change the transfer scenario into an Executive-Assistant Call Push scenario (i.e. the phone will enter in the FAC for the BroadSoft Executive-Assistant Call Push feature and automatically dial the FAC call).The FAC call will be answered and the filtered call will be released if the push is successful.



01:00

1 1.Stefan Bay-Igo2.4052

Dial

RN-001037-03 REV10 – 08.2013 70



1. After answering a filtered call, press the Xfer softkey.

2. Enter the Executive’s phone or extension number and press the Xfer softkey.



Susan SmithL1

Igor Hein+33130964200 01:01

Drop

MoreConfXfer

Push

Susan SmithL1

Dial

MoreCancel

Backspace

Xfer

1. Igor Hein 2.>4052

71 RN-001037-03 REV10 – 08.2013


To Perform a Semi-Attended Transfer of a Filtered Call to the ExecutiveUse the following procedure to perform a semi-attended transfer of a filtered call to the Executive:


IP Phone UI


2. Enter the Executive’s phone or extension number and press the Dial key.

3. When the call is in the ringing state, press the Transfer button.




01:00


Dial

1 1.Stefan Bay-Igo2.4052Cancel

RN-001037-03 REV10 – 08.2013 72




2. Enter the Executive’s phone or extension number and press the Dial softkey.

3. When the call is in the ringing state, press the Xfer softkey.



Susan SmithL1

Igor Hein+33130964200 01:01

Drop

MoreConfXfer

Push

Susan SmithL1

Dial

MoreCancel

Backspace

Xfer


Susan SmithL1

1. Igor Hein 2. 4052

Xfer Cancel

73 RN-001037-03 REV10 – 08.2013


To Perform a Consultative Transfer of a Filtered Call to the ExecutiveUse the following procedure to perform a consultative transfer of a filtered call to the Executive:


IP Phone UI


2. Enter the Executive’s phone or extension number and press the Dial key.

3. When the call is answered by the Executive press the Transfer button.

The call will be transferred normally and the filtered call will be released.


01:00


Dial

1 1.Stefan Bay-D.2.4052

Drop

1 Call Transferred

RN-001037-03 REV10 – 08.2013 74




2. Enter the Executive’s phone or extension number and press the Dial softkey.

3. When the call is answered by the Executive press the Xfer softkey.

The call will be transferred normally and the filtered call will be released.

Susan SmithL1

Igor Hein+33130964200 01:01

Drop

MoreConfXfer

Push

Susan SmithL1

Dial

MoreCancel

Backspace

Xfer


Susan SmithL1

1. Igor Hein 2. 4052

XferDrop

Susan SmithL1

Call Transferred

75 RN-001037-03 REV10 – 08.2013


To Activate Call Forwarding of Filtered CallsUse the following procedure to activate call forwarding of filtered calls:

Aastra Web UI

1. Click on Basic Settings->Account Configuration.

2. Place a checkmark in the “Enabled” box beside the “Divert” option under “Forward Filtering”.

3. Enter the phone number you wish to forward incoming filtered calls to in the “Divert to Number” field.

4. Click Save Settings.

RN-001037-03 REV10 – 08.2013 76



IP Phone UI

1. Press the Options key, the Down navigation key, and then the Enter key to enter the Call Forward menuorPress the Call Forward programmable key.

2. Press the Down navigation key three times to select Forward Filtering.

3. Press the Change key to enter the Call Forward Mode Forward Filtering menu.

4. Press the Down navigation key to highlight the Call Forward State menu.

5. Press the Change key to enter the Call Forward State menu.

6. Press the Next key to toggle the Call Forward State option from OFF to ON.

Cfwd Mode1.All X Done Change

Cfwd Mode4.Fwd Filtering X Done Change

Fwd Filtering

Use to view

Cfwd StateOFF Done Change

1

Cfwd StateOFF Next Set

77 RN-001037-03 REV10 – 08.2013



8. Press the Down navigation key to highlight the Call Forward Number menu.

9. Press the Change key to enter the Call Forward Number menu and enter a forwarding number.

10.Press the Set key.

11.Press the Done key.

12.Press the Confirm key to apply the changes.

A checkmark will be displayed beside Fwd Filtering indicating call forwarding of all filtered calls is to be activated.

Cfwd StateON Next Set

Cfwd StateON Done Change

1

Cfwd Number

Done Change

2

Cfwd Number9057604000 Cancel Set

Cfwd Number9057604000 Done Change

2


RN-001037-03 REV10 – 08.2013 78



13.Press the Done key again.

14.Press the Confirm key again.

15.Press the Goodbye button to return to the idle screen.

The idle screen will display a “CFWD Filtering” message and the Message Waiting Indicator (MWI) and (if configured) Call Forward softkey LEDs will be lit indicating Forward Filtering isactivated.

1. Press the Options key and then the Select softkey to enter the Call Forward menuorPress the Call Forward softkey.


Cfwd Mode4.Fwd Filtering Done Change


Options List

Use to view

Susan Smith1

13/05/13 11:40CFWD Filtering

Call Forward Mode 1.All X 2.Busy X 3.No Answer X 4.Forward Filtering XChange

DoneAll OnAll Off

CancelCopyToAll

79 RN-001037-03 REV10 – 08.2013



4. Press the Change key to toggle the State from OFF to ON.

5. Press the Down navigation key to select the Number field.

6. Enter the applicable forwarding number.


DoneAll OnAll Off

Cancel

State: OFFNumber: Change

DoneCancel

Call Forward Mode Forward Filtering


State: ONNumber: Change

DoneCancel


State:ONNumber: Backspace

DoneCancel

RN-001037-03 REV10 – 08.2013 80



A checkmark will be displayed beside Forward Filtering indicating call forwarding of all fil-tered calls is to be activated.

8. Press the Done key to return to the idle screen.

The idle screen will display a “CFWD Filtering” message and the MWI and (if configured) Call Forward softkey LEDs will be lit indicating Forward Filtering is activated.


State:ONNumber:9057604000 Backspace

DoneCancel

Call Forward Mode 1.All X 2.Busy X 3.No Answer X 4.Forward Filtering �Change

DoneAll OnAll Off

Cancel

Susan Smith

13/05/13 11:40

More

Susan SmithL1

13/05/13 11:40

Filter

MoreCall ForwardDND

CFWD Filtering

81 RN-001037-03 REV10 – 08.2013


To Deactivate Call Forwarding of Filtered CallsUse the following procedure to deactivate call forwarding of filtered calls:

Aastra Web UI

1. Click on Basic Settings->Account Configuration.

2. Remove the checkmark in the “Enabled” box beside the “Divert” option under “Forward Filtering”.


RN-001037-03 REV10 – 08.2013 82



IP Phone UI

1. Press the Options key, the Down navigation key, and then the Enter key to enter the Call Forward menuorPress the Call Forward programmable key.



4. Press the Down navigation key to highlight the Call Forward State menu.

5. Press the Change key to enter the Call Forward State menu.

6. Press the Next key to toggle the Call Forward State option from ON to OFF.

Cfwd Mode1.All X Done Change

Cfwd Mode4.Fwd Filtering Done Change

Fwd Filtering

Use to view

Cfwd StateON Done Change

1

Cfwd StateON Next Set

83 RN-001037-03 REV10 – 08.2013




9. Press the Confirm key to apply the changes.

An X will be displayed beside Fwd Filtering indicating call forwarding of all filtered calls is to be deactivated.

10.Press the Done key again.

11.Press the Confirm key again.

12.Press the Goodbye button to return to the idle screen.

The “CFWD Filtering” message will be removed from the idle screen and the MWI and (if configured) Call Forward softkey LEDs will turn off indicating Forward Filtering is deactivated.

Cfwd StateOFF Next Set

Cfwd StateOFF Done Change

1


Cfwd Mode4.Fwd Filtering X Done Change


Options List

Use to view

Susan Smith1

13/05/13 11:40

RN-001037-03 REV10 – 08.2013 84



1. Press the Options key and then the Select softkey to enter the Call Forward menuorPress the Call Forward softkey.



4. Press the Change key to toggle the State from ON to OFF.


DoneAll OnAll Off

CancelCopyToAll


DoneAll OnAll Off

Cancel


State: ONNumber:9057604000 Change

DoneCancel

85 RN-001037-03 REV10 – 08.2013


5. Press the Done key.An X will be displayed beside Forward Filtering indicating call forwarding of all filtered calls is to be deactivated.

6. Press the Done key to return to the idle screen.

The “CFWD Filtering” message will be removed from the idle screen and the MWI and (if configured) Call Forward softkey LEDs will turn off indicating Forward Filtering is deactivated.


State: OFFNumber:9057604000 Change

DoneCancel


DoneAll OnAll Off

Cancel

Susan Smith

13/05/13 11:40

More

Susan SmithL1

13/05/13 11:40

Filter

MoreCall ForwardDND

RN-001037-03 REV10 – 08.2013 86


To Initiate a Call on Behalf of an ExecutiveUse the following procedure to initiate a call on behalf of an Executive:


IP Phone UI

1. Press the Speeddial softkey programmed with Initiate Call function (e.g. “Init”).

The phone will enter in the FAC for the BroadSoft Executive-Assistant Initiate Call feature and automatically dial the FAC call.

2. Follow any audible instructions (depending on the Speeddial key’s configuration you may be prompted to enter the Executive’s number/extension and/or Destination number/exten-sion manually using the phone’s keypad).The phone will automatically dial the Destination number/extension.

3. When the call is answered, if you would like to push the call to the Executive, press the Trans-fer button twice.


Susan Smith1

13/05/13 11:40

Init

1#64

01:00

87 RN-001037-03 REV10 – 08.2013



1. Press the Speeddial softkey programmed with Initiate Call function (e.g. “Init”).

The phone will enter in the FAC for the BroadSoft Executive-Assistant Initiate Call feature and automatically dial the FAC call.

2. Follow any audible instructions (depending on the Speeddial key’s configuration you may be prompted to enter the Executive’s number/extension and/or Destination number/exten-sion manually using the phone’s keypad).The phone will automatically dial the Destination number/extension.

3. When the call is answered, if you would like to push the call to the Executive, press the Push key.


Susan SmithL1

13/05/13 11:40

Filter

MoreCall ForwardInit

Susan SmithL1

Drop

MoreConfXfer

#6401:00Push

RN-001037-03 REV10 – 08.2013 88


Passthrough Support for Data from VLAN-Enabled PC Port to VLAN-Disabled LAN Port

With Release 3.3.1 SP2, data passthrough is now supported on the 6735i and 6737i IP phones in scenarios where the IP phone’s PC port is connected to a VLAN-enabled PC and the LAN port is connected to a device without VLAN support.

By enabling VLAN, configuring the LAN port VLAN ID to 4095, and entering a valid PC port VLAN ID (i.e. from 1 to 4094), the IP phones will now tag and untag all data accordingly before sending the data to its respective destination. Frames from the PC port (containing a VLAN ID) will be untagged before being forwarded to the LAN port and frames from the LAN port (without a VLAN ID) will be tagged with the configured VLAN ID before being forwarded to the PC port.

Configuring Passthrough Support Using the IP Phone UIUse the following procedure to configure passthrough support using the IP phone’s UI:

Note:This feature was already supported in all other IP phones (excluding the 6730i) in a previous release.

Note:Procedures to configure additional options with regards to the VLAN function (e.g. LAN and PC port VLAN priority) can be found in the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

IP Phone UI

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

2. Select Admin Menu and enter your Administrator password.

3. Select Network Settings.

4. Select Ethernet and VLAN.

5. Select VLAN Settings.

6. Select VLAN.

7. Select Enable.

89 RN-001037-03 REV10 – 08.2013


8. Press Done or Set to save the changes.

9. Select LAN Port VLAN.

10. Select LAN Port VLAN ID and enter 4095.

11. Press Enter or Set to save the change.

12. Navigate back to the VLAN Settings menu.

13. Select PC Port VLAN.

14. Select PC Port VLAN ID.

15. Enter a value from 1 to 4094 to specify the VLAN ID for the PC Port.

16. Press Enter or Set to save the change.

17. Navigate back to the Options List menu.

18. Select Restart Phone and follow the prompts to restart the phone and apply the configu-ration changes.

RN-001037-03 REV10 – 08.2013 90


Configuring Passthrough Support Using the Aastra Web UIUse the following procedure to configure passthrough support using the Aastra Web UI:

Aastra Web UI

1. Navigate to Advanced Settings->Network->VLAN.

2. Enable VLAN by checking the VLAN Enable field check box under Global.

3. Enter 4095 in the VLAN ID field under LAN Port to specify the VLAN ID for the LAN Port.

4. Enter a value from 1 to 4094 in the VLAN ID field under PC Port to specify the VLAN ID for the PC Port.


6. Navigate to Operation->Reset.

7. Click Restart and follow the prompts to restart the phone and apply the configuration changes.

91 RN-001037-03 REV10 – 08.2013


Configuring Passthrough Support Using the Configuration FilesUse the following parameters to configure passthrough support using the configura-tion files:

Parameter – tagging enabled


Description Enables or disables VLAN on the IP phones. This is a global setting.

Format Boolean

Default Value 0 (False)

Range 0 (False)1 (True)

Example tagging enabled: 1

Parameter – vlan id


Description Allows you to configure a VLAN ID that associates with the physical Ethernet Port 0 (LAN port).Notes:• Setting the “vlan id” to 4095 and “vlan id port 1” to any ID from 1 to

4094 will allow frames from the PC port (containing a VLAN ID) to be untagged before being forwarded to the LAN port and frames from the LAN port (without a VLAN ID) to be tagged with the configured VLAN ID before being forwarded to the PC port.

Example:You enable tagging on the phone port as normal but set the “vlan id” to 4095 and the “vlan id port 1” to any ID from 1 to 4094. The fol-lowing example sets the PC port to be on VLAN 3 but the LAN port is configured as untagged:

tagging enabled: 1vlan id: 4095vlan id port 1: 3

• Alternatively setting the “vlan id” to any ID from 1 to 4094 and “vlan id port 1” to 4095 will allow frames from the LAN port (containing a VLAN ID) to be untagged before being forwarded to the PC port and frames from the PC port (without a VLAN ID) to be tagged with the configured VLAN ID before being forwarded to the LAN port.

Format Integer

Default Value 1

Range 1 to 4095

Example vlan id: 4095

RN-001037-03 REV10 – 08.2013 92


Parameter – vlan id port 1


Description Allows you to configure a VLAN ID that associates with the physical Ethernet Port 1 (PC port).Notes:• Setting the “vlan id port 1” to 4095 and “vlan id” to any ID from 1 to

4094 will allow frames from the LAN port (containing a VLAN ID) to be untagged before being forwarded to the PC port and frames from the PC port (without a VLAN ID) to be tagged with the config-ured VLAN ID before being forwarded to the LAN port.

Example:You enable tagging on the phone port as normal but set the “vlan id port 1” to 4095 and the “vlan id” to any ID from 1 to 4094. The fol-lowing example sets the LAN port to be on VLAN 3 but the PC port is configured as untagged:

tagging enabled: 1vlan id: 3vlan id port 1: 4095

• Alternatively setting the “vlan id port 1” to any ID from 1 to 4094 and “vlan id” to 4095 will allow frames from the PC port (containing a VLAN ID) to be untagged before being forwarded to the LAN port and frames from the LAN port (without a VLAN ID) to be tagged with the configured VLAN ID before being forwarded to the PC port.

Format Integer

Default Value 4095

Range 1 to 4095

Example vlan id port 1: 3

93 RN-001037-03 REV10 – 08.2013


Directory File Reloading with Auto-Resync

The auto-resync feature on the IP phones allows an administrator to enable the phone to be updated automatically once a day at a specific time in a 24-hour period if the files on the server have changed. This feature works with TFTP, FTP, HTTP, and HTTPS servers. An administrator can enable this feature using the Aastra Web UI or using the configuration files (aastra.cfg, <model>.cfg, and <mac>.cfg).

During an auto-resync, the 6735i and 6737i IP phones now have the ability to initiate a comparison of its local directory files with those located on the configuration server and automatically update the local directory files if changes are detected.

If the auto-resync mode is set to” Configuration Files (1)” or “Both (3)”, either through the IP phone’s Web UI or configuration files, when the phone reaches the configured auto-resync date/time, the phone will perform a comparison on the directory files and trigger a reboot if differences are found.

If the auto-resync mode is set to “None (0)” or “Firmware Info (2)” and the phone reaches the configured auto-resync date/time, the directory files will not be checked.


Note:Irrespective of the auto-resync feature, if the phone receives a check-sync NOTIFY, the directory file comparison will be performed and the applicable files will be auto-matically updated as required.

RN-001037-03 REV10 – 08.2013 94


Enabling Auto-Resync Using the Aastra Web UIUse the following procedure to enable auto-resync for the phones in your network using the Aastra Web UI.

Aastra Web UI

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

2. In the “Mode” field, select the auto-resync mode you want to use to automatically update the phone.Valid values are:• None: Disable auto-resync.• Configuration Files: Updates the configuration files on the IP phone automatically at

the specified time if the files on the server have changed.• Firmware: Updates the firmware on the IP phone automatically at the specified time if

the files on the server have changed.• Both: Updates the configuration files and firmware automatically at the specified time if

the files on the server have changed.Notes:• If a user is accessing the Aastra Web UI, they are not informed of an auto-reboot.• Any changes made using the Aastra Web UI or the IP phone UI are not overwritten by an

auto-resync update. Auto-resync affects the configuration files only. However, the settings in the Aastra Web UI take precedence over the IP phone UI and the configuration files.

• The resync time is based on the local time of the IP phone.• If the IP phone is in use (not idle) at the time of the resync check, the reboot occurs when

the phone becomes idle.

3. In the “Time (24-hour)” field, select the time that you want the update to take place. Valid values are 00:00 to 23:30 (in 30 minute increments).Notes:• The resync time is based on the local time of the IP phone.• The value of 00:00 is 12:00 A.M.• When selecting a value for this parameter in the Aastra Web UI, the values are in 30-minute

increments only.

95 RN-001037-03 REV10 – 08.2013


4. In the “Maximum Delay” field, specify the maximum time, in minutes, the phone waits past the scheduled time before starting a checksync. The range is 0 to 1439. Default is 15.

5. In the “Days” field, specify the amount of days that the phone waits between checksync operations.The range is 0 to 364. Default is 0.Note:A value of 0 causes the phone to checksync every time the clock reads the proper time. A value of 1 forces the phone to wait 24 hours prior to doing the first checksync.

6. Click Save Settings to save your settings. Note:These changes are not dynamic. You must restart your IP phone for the changes to take affect.

7. Click on Operation->Reset.

8. In the "Restart Phone" field click Restart to restart the IP phone and apply the update.The update performs automatically at the designated time.

RN-001037-03 REV10 – 08.2013 96


Enabling Auto-Resync Using the Configuration FilesUse the following parameter to enable auto-resync using the configuration files:

Parameter – auto resync mode


Description Determines whether the configuration server automatically updates the configuration files only, the firmware only, both the firmware and configuration files, or disables automatic updates.This parameter works with TFTP, FTP, HTTP and HTTPS servers. Valid values are:• None (0) - Disable auto-resync.• Configuration Files (1) - Updates the configuration files on the IP

phone automatically at the specified time if the files on the server have changed.

• Firmware (2) - Updates the firmware on the IP phone automatically at the specified time if the files on the server have changed.

• Both (3) - Updates the configuration files and firmware automati-cally at the specified time if the files on the server have changed.

Notes:• If a user is accessing the Aastra Web UI, they are not informed of an

auto-reboot.• Any changes made using the Aastra Web UI or the IP phone UI are

not overwritten by an auto-resync update. Auto-resync affects the configuration files only. However, the settings in the Aastra Web UI take precedence over the IP phone UI and the configuration files.

• The resync time is based on the local time of the IP phone.• If the IP phone is in use (not idle) at the time of the resync check, the

reboot occurs when the phone becomes idle.• The automatic update feature works with both encrypted and plain

text configuration files.

Format Integer

Default Value 0

Range 0 (None)1 (Configuration files only)2 (Firmware only)3 (Configuration files and firmware)

Example auto resync mode: 3

97 RN-001037-03 REV10 – 08.2013


Emergency Call Behavior Enhancements

Administrators now have the option of changing the default behavior of the 6735i and 6737i IP phones when an emergency call (i.e. a call made to an emergency number matching one of the values defined in the “emergency dial plan” parameter) is placed.

If the “emergency call connection hold enabled” configuration parameter is ena-bled, the IP phones employ the following behaviors:

• Connection Hold: If an emergency call is placed, the IP phones ensure the voice/audio path and other resources associated with the emergency call are con-tinually active, even if the caller hangs up the phone (i.e. the handset is placed on-hook).

– If the handset is placed on-hook, the phone automatically switches to speaker-phone mode ensuring that the call is still active. Alternatively, if the handset is taken off-hook, the phone automatically switches to handset mode.

– All softkey and hardkey events (e.g. hold, conference, transfer, end call, park, mute, etc...) are disabled as they may impede or be disruptive to the active call.

– The phone does not allow for the origination or termination of any call while the phone is connected to the emergency services agent. All incoming calls and pages are ignored and a busy tone is presented to the remote caller.

• Enhanced Called Party Hold: As a complement to the Connection Hold feature, Enhanced Called Party Hold allows the voice/audio path to be established the moment the emergency call is placed.

– When a caller places a call to an emergency services number, all Connection Hold features are activated, even if the SIP session has not been established completely.

– Even if the caller abandons the call before the emergency services agent answers, the voice/audio path and Connection Hold features will still be active.

• Forced Disconnect: As the Connection Hold feature ensures that the caller cannot terminate the call, the only way the call can be terminated is if the emergency serv-ices agent forces the disconnection by ending the call himself/herself.

The “emergency call connection hold enabled” parameter is disabled by default.


Note:For more information regarding emergency calls and defining an emergency dial plan, see the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

RN-001037-03 REV10 – 08.2013 98


Enabling the Emergency Call Enhancement FeatureUse the following parameter to enable the emergency call enhancement feature:

Parameter – emergency call connection hold enabled


Description If enabled, this parameter changes the behavior of the IP phones when an emergency call (i.e. a call made to an emergency number matching one of the values defined in the “emergency dial plan” parameter) is placed. The IP phones will ensure that the voice/audio path and other resources associated with the emergency call are con-tinually active and any functions that could reduce the “continuous reachability” of the caller are disabled. Additionally, the only way the call can be terminated is if the emergency services agent ends the call.

Format Boolean



Example emergency call connection hold enabled: 1

99 RN-001037-03 REV10 – 08.2013


PIN and Authorization Code Suppression UI Enhancement

The previously implemented PIN and authorization code suppression feature allowed Administrators to configure the “pin suppression dial plan” parameter on the IP phones so that PIN/authorization codes entered by a user would be masked by wild-card characters in all phone logs (i.e. redial list) as well as on screen during a call.

An enhancement has been made to the PIN and authorization code suppression fea-ture in Release 3.3.1 SP2 whereby if the “pin suppression dial plan” parameter is defined, the phone will now dynamically mask the PIN/authorization code on the dis-play within a second of the code being entered by the user. Previously, it was required that the user press Dial before the phone masked the PIN/authorization code.

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 N/A

Range Up to 512 alphanumeric characters

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

RN-001037-03 REV10 – 08.2013 100


Automatic BLF Activity Page Switching Enhancement

An enhancement has been made to the BLF page switch feature in Release 3.3.1 SP2 whereby the 6735i, 6737i, 6739i, 6755i, 6757i, and 6757i CT IP phones (as well as the M675i Expansion Module) now automatically switch to the idle page (or the first page on the M675i Expansion Module) if no BLF activity is detected by the phone.

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

Note:For more information on the BLF page switch feature refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

Parameter– blf activity page switch


Description Enables the 6735i, 6737i, 6739i, 6755i, 6757i, and 6757i CT IP phones (as well as the M675i Expansion Module) to automatically switch the screen focus to an expansion module or softkey page that has BLF activity.

Format Integer


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

101 RN-001037-03 REV10 – 08.2013


Active VoIP Recording Visual Indicators During Conference Calls

When in a conference call (using the 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, or 9840i CT IP phone), if the call is being recorded, icons (i.e. depending on the phone model, a red or black circle) are now displayed on the phones’ screens indicating the recording status.

The following figures show examples of the icons and their on-screen positions for each respective phone model when on a recorded conference call:

6730i, 6731i, 6753i, and 9143i

6755i,6757i, 6757i CT, 9840i, and 9840i CT

Note:For more information on the active VoIP recording feature refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.

1 1.Martin Croft2.Dave Brundle

DropLeave

RecordingIndicators

Lewis ButtonL1

1. Martin Croft 2. Dave Brundle

LeaveDrop

RecordingIndicators

RN-001037-03 REV10 – 08.2013 102


6739i

L1 Lewis Button 12 : 45pmMon Jan 1

Home

DND

Call Forward

Hold

Leave

Mute

Martin Croft 402

Dave Brundle 404

RecordingIndicator

103 RN-001037-03 REV10 – 08.2013



The parameter, “ring audibly enable”, is now available to be utilized for the 6735i and 6737i. This parameter allows administrators the ability to configure the IP phones to play the ring tone of an incoming call via the phone’s speaker while in an active call or if a user is in the process of dialing out.

With the parameter enabled, if a user is in an active call on an extension, and the phone receives a call for the same or different extension, the incoming call will be rep-resented by the call’s ring tone being played through the speaker as well as the respective line’s LED flashing. This is also the case if a user is in the process of dialing out to a remote number and the phone receives a call for any line other than the line that is being used to dial out. When the phone exits the ringing state (e.g. the incom-ing call is answered), the tone device of the phone will revert back to the originally configured audio device. The parameter is disabled by default.

Enabling the Ring Tone via Speaker During Active Calls FeatureUse the following parameter to enable the ring tone via speaker during active calls feature:


Note:With this feature enabled and when the phone’s speaker is playing the incoming call’s ring tone, the call-waiting tone will not be played on the handset/headset.

Parameter – ring audibly enable


Description Enables/disables the feature whereby the ring tone of an incoming call is played through the IP phone’s speaker if a user is on an active call or in the process of dialing out.Note:With this feature enabled and when the phone’s speaker is playing the incoming call’s ring tone, the call-waiting tone will not be played on the handset/headset.

Format Boolean

Default Value 0 (disabled)


Example ring audibly enable: 1

RN-001037-03 REV10 – 08.2013 104



The option is now available for administrators to configure the 6735i and 6737i IP phones to play a congestion/fast busy tone instead of a dial tone when the phone is in a “No Service” state. This enhancement allows visually impaired persons the ability to discern whether or not the phone is in service and can be used to send/receive calls.

The configuration parameter “no service congestion tone” is available allowing administrators the ability to enable this accessibility feature. When enabled, the con-gestion tone will replace the conventional dial tone when the handset is off hook, a headset is employed, or the speakerphone is engaged. The congestion tone’s fre-quency/pattern is based on the respective phone’s configured tone set. Additionally, the congestion tone is played on a per-line basis whereby only the specific lines that are without service are affected.

With consideration to scenarios where a dial tone should be played even if the phone is in a “No Service” state (e.g. scenarios where the proxy may still accept INVITEs from the phone even if unregistered), the “no service congestion tone” parameter has been programmed as disabled by default.


Note:If the phone or individual lines are configured to have no registration by intent (e.g. if the Registrar is set to 0.0.0.0) enabling the “no service congestion tone” param-eter will have no effect and the default dial tone will be played.

105 RN-001037-03 REV10 – 08.2013


Enabling/Disabling the Congestion Tone Accessibility FeatureUse the following parameter to enable/disable the congestion tone accessibility fea-ture:

Parameter – no service congestion tone


Description If enabled, the congestion tone will replace the conventional dial tone when the handset is off hook, a headset is employed, or the speaker-phone is engaged. The congestion tone is played on a per line basis whereby only the specific lines that are without service are affected.

Format Boolean

Default Value 0 (disabled)


Example no service congestion tone: 1

RN-001037-03 REV10 – 08.2013 106


Shared Call Appearance (SCA) Voicemail Enhancements

Previously, if a voicemail message was pending on an SCA-configured line for the 6735i and 6737i model IP phones, the Message Waiting Indicator (MWI) LED would illuminate but there would be no indication of the specific SCA line the voicemail message was applicable to. Users had to check each individual line for the stutter dial tone indicating a pending voicemail message.

Visual indicators for voicemail messages on SCA lines have now been implemented on the respective IP phones. The parameter “voice mail indicator” is available allow-ing administrators the ability to configure what types of visual indicators the IP phones should display when voicemail messages are pending on a respective SCA line.

Administrators have three options when configuring the “voice mail indicator” parameter:

• 0: When a line has pending messages, the IP phone does not display any visual indi-cators.

• 1: When a line has pending messages, the line’s corresponding softkey will display an envelope icon and the number of pending messages beside the softkey’s label. Additionally, the softkey’s LED will be illuminated.

• 2: When a line has pending messages, the line’s corresponding softkey will display only the envelope icon beside the softkey’s label (i.e. no indication of the number of pending messages). Additionally, the softkey’s LED will be illuminated.

The parameter is set to 0 (no visual indicators) by default.

Note:This feature was already supported in the 9480i, 9480i CT, 6755i, 6757i, and 6757i CT IP phones in a previous release.

John SmithL1

13/05/13 11:40

3 Peter

107 RN-001037-03 REV10 – 08.2013


Configuring SCA Voicemail Visual IndicatorsUse the following parameter to configure the SCA voicemail visual indicators:

Notes:• The above behaviors are also applicable to expansion module softkeys represent-

ing SCA lines.• For programmable keys representing SCA lines, the respective programmable

key’s LED will flash when voicemail messages are pending.• The “voice mail indicator” parameter takes precedence over the “line icon disa-

bled” parameter. If both “voice mail indicator” and “line icon disabled” are ena-bled, an envelope icon (and number of messages, if configured) will be displayed when voicemail messages are pending.

Parameter – voice mail indicator


Description Controls which visual indicators are displayed on the IP phone when voicemail messages are pending on SCA-configured lines. Applicable to the 9480i, 9480i CT, 6735i, 6737i, 6755i, 6757i, and 6757i CT model IP phones (as well as expansion modules).

Format Integer

Default Value 0

Range 0-20 (Do no display any visual indicators)1 (Display an envelope icon and the number of pending messages beside the respective softkey’s label and illuminate the softkey’s LED [if available])2 (Display only an envelope icon beside the respective softkey’s label [no indication of the number of pending messages] and illuminate the softkey’s LED [if available]).

Example voice mail indicator: 1

RN-001037-03 REV10 – 08.2013 108


Ability to Edit the Name Field of a Callers List Record

For the 6730i, 6731i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9840i, and 9840i CT IP phones, users are now able to directly edit the name field of a call record in the phone’s Callers List before copying the record to the Directory.

To Edit the Name Field of a Callers List Record and Copy the Record to the DirectoryUse the following procedure to edit the name field of a Callers List record and copy the record the Directory:


Note:The Callers List does not save changes. Editing the name and/or number field(s) and copying the record to the Directory only affects the name and/or number saved to the Directory.

IP Phone UI

1. Press the Callers List buttonorPress the Callers List keyorPress the Services key and then select Callers List.

2. Press the Up or Down navigation key to find the entry you want to edit.

3. Press any key on the dialpad to begin edit mode.Note:A number/symbol will be entered in the number field corresponding to the dialpad key you pressed. This number/symbol can be deleted by pressing the Left navigation key if required.

4. Press the Up navigation key to switch the focus to the name field.

5. Edit the name field using the respective keys on the dialpad. Note:Pressing the Right navigation key will delete a character to the right of the cursor while pressing the Left navigation key will delete a character to the left of the cursor.

109 RN-001037-03 REV10 – 08.2013



6. Press the Save key.A “Save To?” prompt displays.

7. Press the Directory key.The edited Callers List record is saved to the Directory.

1. Press the Callers List keyorPress the Services key and then select Callers List.

2. Press the Up or Down navigation key to find the entry you want to edit.

3. Press the EditNum softkey to begin edit mode.

4. Press the Up navigation key to switch the focus to the name field.

5. Edit the name field using the respective keys on the dialpad. Notes:• Pressing the Right navigation key will move the cursor one character to the right while

pressing the Left navigation key will move the cursor one character to the left.• Use the Backspace softkey to delete characters.

6. Press the Copy softkey.The edited Callers List record is saved to the Directory.

RN-001037-03 REV10 – 08.2013 110


Melody Playback

Melody playback support has been introduced in Release 3.3.1 SP2. WAV files on a server can be stored on and played back in a loop on the IP phone by defining the WAV file URL in an XML script. When the Play Melody XML script is executed, the IP phone will download and store the WAV file internally and start playback of the WAV file.

Up to eight WAV files in total can be cached on the IP phone, allowing for faster play-back. If a new WAV file is requested when the IP phone already has eight files stored, the oldest WAV file that was played will be replaced with the new WAV file.

The melodies can be played back and stopped on the IP phone by creating two XML scripts, placing the scripts on an FTP, TFTP, HTTP, or HTTPS server, and configuring softkeys on the IP phone to execute the respective XML scripts. The XML scripts for the Play and Stop Melody commands are as follows:

• playmelody1.xml:<AastraIPPhoneExecute><ExecuteItem URI="Melody.Play:[MelodyURL]:[volume]"/></AastraIPPhoneExecute>

where “MelodyURL” specifies the location of the WAV file and ”volume” is the vol-ume level from 0 (lowest) - 9 (highest). While defining the “MelodyURL” is manda-tory, defining the volume level is optional.

For example,<AastraIPPhoneExecute><ExecuteItem URI="Melody.Play:ftp://192.168.0.5:21/tmp/alarm1.wav:2"/></AastraIPPhoneExecute>

XML Features

Notes:• The IP phones support the following WAV file specifications:

– G.711 μ-law and a-law Codec– 20 ms packet size – Mono 8KHz

• Individual WAV files cannot exceed 200kB in size and the total combined size of the eight WAV files cannot exceed 400kB.

• All melodies will be removed when the phone is rebooted.

111 RN-001037-03 REV10 – 08.2013


• stopmelody.xml:<AastraIPPhoneExecute><ExecuteItem URI="Melody.Stop:"/></AastraIPPhoneExecute>

Configuring the Melody XML Keys Using the Aastra Web UIUse the following procedure to configure the Play Melody and Stop Melody XML keys using the Aastra Web UI:

Notes:• A melody can only be played when the phone is in an idle state.• Melody playback will end when the softkey configured with the Stop Melody

command is pressed, Playback will also be stopped if the Goodbye key is pressed, the Drop softkey is pressed, the phone is on hook (when the handset is active), or when selecting a line on the phone.

• A paging call will not interrupt playback unless barge-in is enabled.• For more information on XML commands, please refer to the Development Guide

XML API For Aastra SIP Phones.

Aastra Web UI


2. Select a key that you want to use to execute the Play Melody XML script.

3. In the "Type" field, select "XML".

4. In the "Label" field, enter a label to apply to this key (e.g. “Play Melody”).

5. In the "Value" field, enter a URI to apply to this key (e.g. http://192.168.0.50/playmelody1.xml)

6. Select a key that you want to use to execute the Stop Melody XML script.

RN-001037-03 REV10 – 08.2013 112


Configuring the Melody XML Keys Using the IP Phone UI (6739i only)Use the following procedure to configure the Play Melody and Stop Melody XML keys using the 6739i IP phone’s UI:

7. In the "Type" field, select "XML".

8. In the "Label" field, enter a label to apply to this key (e.g. “Stop Melody”).

9. In the "Value" field, enter a URI to apply to this key (e.g. http://192.168.0.50/stopmelody.xml)

10.Click Save Settings to save your settings.

IP Phone UI

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

2. Select Softkeys. By default, all of the softkeys that display are configured as “None”.

3. Press a key defined as <None> that you want to use to execute the Play Melody XML script. A softkey configuration screen displays.

4. In the “Type” field, press the <None> key. A screen displays with softkey keys.

5. Press the <XML> function key to apply to the softkey type.

6. In the "Label" field, enter a label to apply to this softkey (e.g. “Play Melody”).

7. In the "Value" field, enter a URI to apply to this softkey (e.g. http://192.168.0.50/playmelody1.xml)

8. Press <Save> to save the softkey.

9. Press another key defined as <None> that you want to use to execute the Stop Melody XML script. A softkey configuration screen displays.

10.In the “Type” field, press the <None> key. A screen displays with softkey keys.

11.Press the <XML> function key to apply to the softkey type.

12.In the "Label" field, enter a label to apply to this softkey (e.g. “Stop Melody”).

13. In the "Value" field, enter a URI to apply to this softkey (e.g. http://192.168.0.50/stopmel-ody.xml)

113 RN-001037-03 REV10 – 08.2013


Configuring the Melody XML Keys Using the Configuration FilesTo configure the Play Melody and Stop Melody XML keys using the configuration files, you must enter “xml” for the key types. For the labels, enter key labels to assign to the Play Melody and Stop Melody XML keys (e.g. “Play Melody” and “Stop Melody”). For the values, enter in the respective URIs that will execute the Play Melody and Stop Melody commands. For example:

• http://192.168.0.50/playmelody1.xml

• http://192.168.0.50/stopmelody.xml

The following parameters are examples you can use to configure the Play Melody and Stop Melody XML keys:

For Softkeyssoftkey1 type: xml

softkey1 label: Play Melody

softkey1 value: http://192.168.0.50/playmelody1.xml

softkey2 type: xml

softkey2 label: Stop Melody

softkey2 value: http://192.168.0.50/stopmelody.xml

For Top Softkeystopsoftkey1 type: xml

topsoftkey1 label: Play Melody

topsoftkey1 value: http://192.168.0.50/playmelody1.xml

topsoftkey2 type: xml

topsoftkey2 label: Stop Melody

topsoftkey2 value: http://192.168.0.50/stopmelody.xml

14.Press <Save> to save the softkey. The softkeys apply to your phone immediately and display on your idle screen.

15.Press the to return to the previous menu or press the key to return to the idle screen.

RN-001037-03 REV10 – 08.2013 114


For Programmable Keysprgkey1 type: xml

prgkey1 value: http://192.168.0.50/playmelody1.xml

prgkey2 type: xml

prgkey2 value: http://192.168.0.50/stopmelody.xml

For Expansion Module Softkeysexpmod1 key1 type: xml

expmod1 key1 label: Play Melody

expmod1 key1 value: http://192.168.0.50/playmelody1.xml

expmod1 key2 type: xml

expmod1 key2 label: Stop Melody

expmod1 key2 value: http://192.168.0.50/stopmelody.xml


115 RN-001037-03 REV10 – 08.2013

Issues Resolved in Release 3.3.1 SP2This section describes the issues resolved on the IP Phones in Release 3.3.1 SP2.

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

Issues Resolved

Note:Unless specifically indicated, the resolved issues below apply to all phone models except the 6735i and 6737i.

Issue Number Description of Fix

Configuration

ENH31198 6735i & 6737i: Previously only supported on the 9000i and 6700i series IP phones, the Technical Report (TR)-069 protocol is now supported for the 6735i and 6737i IP phones.

ENH33477/CLN33572 The phones can now accept a maximum of 256 characters when defining HTTP, HTTPS, TFTP, and FTP server download paths.

DEF22725/CLN32738 6735i & 6737i: The configuration parameter “sip enforce require hdr” was not functional for the 6735i and 6737i IP phones. When enabled, the phone rejects an INVITE or BYE with a 420 Bad Extension response if the INVITE or BYE con-tains and unsupported value in the Require header. This issue has been fixed and the parameter is now fully functional in Release 3.3.1 SP2.

DEF24145/CLN25510/CLN30826

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.

DEF29920 9143i: The Preferred Line and Preferred Line Timeout settings were not availa-ble to be configured through the phone’s Web UI in a previous firmware release. This issue has been corrected and the settings are now available in the Basic Settings > Preferences > General section of the phone’s Web UI.

DEF29832 6755i: Even with the “ringback timeout” parameter defined as “0”, incoming calls would still cause the phone to ring. This issue has been fixed.

DEF29835 An issue was observed whereby users were unable to configure the date on the phone manually using the phone’s UI if the Screen Language was set to German. This issue has been resolved.

DEF31416/CLN31638/CLN31639/CLN31742/CLN33075

An issue occurred whereby if the “call transfer disabled” parameter was set to 1 (True), a call could still be transferred during a conference call if the user pressed the Leave or Xfer softkey/hardkey. This issue has been corrected.

RN-001037-03 REV10 – 08.2013 116

Issues Resolved in Release 3.3.1 SP2

DEF31487/DEF31493 The TLS persistent connection keep alive retry timeout was observed to be exponential instead of periodic resulting in issues when network interruptions occurred. These issues have been fixed.

DEF31549/DEF31818/DEF32197/CLN32233/CLN32299

When using DHCP Option 43 to transfer VLAN ID assignment, in certain sce-narios, upon reboot the phone would receive the applicable VLAN informa-tion and enable VLAN as expected but the VLAN ID would be configured with an invalid value. This issue has been resolved.

DEF32187/CLN32190/CLN32191

6735i & 6737i: The value of the configuration parameter “admin password” only supported 9 digits instead of expected 10. This issue has been fixed and the parameter now correctly supports a total of 10 digits.

DEF32312/CLN32362 When utilizing TR-069 functionality, it was observed that the phone was una-ble to open the required port in order to accept an incoming HTTP request from the Auto Configuration Server (ACS). This issue has been fixed.

DEF32445/CLN32450 6735i & 6737i: An issue was observed whereby the internal ringback timeout timer was not being reset correctly if a user manually cancelled a call during a ringback state. This caused the phone to automatically cancel calls in a ring-back state earlier than expected, ultimately affecting the timeout defined for the “ringback timeout” configuration parameter. This issue has been cor-rected.

DEF33195 6735i & 6737i: A VLAN configuration issue caused the phone’s PC port to become unresponsive when a PC connected to the phone was disconnected, used with another phone on a different switch, and then re-connected to the initial phone. This issue has been resolved.

CLN33500 All phones except the 6735i, 6737i, and 6739i: An enhancement has been made whereby a phone configured with the Assistant role (when using the BroadSoft BroadWorks Executive and Assistant services feature) will now rec-ognize filter key values that start with a national number prefix (e.g. “0” for France).

SIP

ENH28371/DEF32528 6757i: An enhancement has been made in Release 3.3.1 SP2 whereby BLF-monitoring phones can now correctly handle the reception of two dialogs in separate NOTIFY messages sent from the monitored phone.

ENH32107/CLN32240/CLN32242/CLN32323

6735i & 6737i: An enhancement has been implemented in Release 3.3.1 SP2 that allows the phones to ignore the event ID parameter in REFER NOTIFY event headers. This enhancement resolves an issue whereby the phone would reject the REFER NOTIFY message from certain SBCs when a transfer was attempted.

ENH32305/CLN32309/CLN32313

Entrust root certificates are now supported on the phones in Release 3.3.1 SP2.

DEF23824/CLN31197/CLN31246

6757i: An issue occurred whereby the phone only sent one DHSG ring com-mand, despite the fact that the phone rang several times. This issue has been-corrected.


117 RN-001037-03 REV10 – 08.2013


DEF25837/DEF28313/DEF29501/DEF30579/DEF31185/DEF31490/DEF33097

Robustness of the phones was increased to fix various intermittent stability issues observed in certain scenarios.

DEF26377 When performing an outgoing call using the Directory with the handset off hook, the phone would incorrectly switch to a different line to dial out. This issue has been corrected.

DEF27195/DEF32516 6757i: With As-Feature-Event Subscription enabled and after rebooting the phone, the phone correctly sent out a SUBSCRIBE message but did not send the expected re-SUBSCRIBE after receiving a SIP NOTIFY with a Subscription-state value of “Terminated”. This issue has been resolved.

DEF28104 6735i & 6737i: An issue occurred whereby the phone did not release its IP address as expected causing the phone to retrieve a new IP address upon every reboot. This issue has been corrected.

DEF28190 When using the phones in TLS/SRTP mode in conjunction with the Aastra 5000 call manager and CTI dialer, a one-way audio issue was observed when the CTI dialer was used to initiate a phone call with a 5300ip series phone. This issue has been fixed.

DEF28545 6739i: A logging in/out issue was observed when using the phone with the Aastra MX-ONE call manager. This issue has been resolved.

DEF28601 When using the phone with a Metaswitch call manager, if the phone was in a conference call whereby one party was an Interactive Voice Response (IVR) system, the IVR would not recognize the digits pressed on the phone. This issue has been fixed.

DEF29069 An issue was observed whereby the Globally Routable User-Agent URIs (GRUUs) obtained in the 200 OK REGISTER response was not being used in the SUBSCRIBE request sent from the phone. This issue has been fixed.

DEF29574/CLN32041 6755i: When using the Aastra MX-ONE call manager, an issue was observed whereby RTP multicast streams sent by a phone that was attempting to estab-lish a centralized conference call would unexpectedly drop when the mapped Conference key (i.e. 3 keypad key) was pressed in certain situations. This issue has been resolved.

DEF30098 6757i: An issue was observed whereby Out-of-Band DTMF digits were not being forwarded correctly by the conference host when on a three-way con-ference call. This issue has been fixed.

DEF30640 6757i: An issue was observed whereby the phone would not send Out-of-Band DTMF tones after a call was established using the G.722 codec. This issue has been corrected.

DEF30768/CLN31130/CLN31131

Pressing a softkey configured for Intercom functionality when the “Call Trans-ferred” message was displayed on screen would cause the phone to reject subsequent incoming calls with a “486 Busy Here” message. This issue has been fixed.


RN-001037-03 REV10 – 08.2013 118


DEF30809/CLN31727/CLN31728/CLN32340

All phones including 6735i and 6737i: When using the A5000 call manager and calling a number corresponding to the configured local dial plan, no ringback would occur on the phone if the phone received a 180 RINGING message very quickly after receiving the 100 TRYING message. This issue has been corrected.

DEF30869/CLN32141 6739i: After completing a call transfer of an inbound call, the line that received the initial inbound call would still remain in a transferring state in certain sce-narios. This issue has been resolved.

DEF30912/CLN31820 An issue occurred whereby the phone was not taking into account the config-ured LLDP-MED voice signalling priority. This issue has been corrected and the phone now sends the proper configured voice signalling priority in the SIP Real-time Transport Protocol (RTP) packets.

DEF30930/DEF31734 6735i & 6737i: Issues were observed whereby 802.1x authentication either failed or was being lost during the phone’s boot-up process. These issue have been resolved.

DEF31064 6735i & 6737i: When using the phones with the Aastra MX-ONE call manager, the phone would not unregister a user correctly in certain situations causing issues when re-registering the user on a different phone. This issue has been corrected.

DEF31424/CLN32346 6755i: When used in conjunction with the Zultys call manager, the phone would incorrectly handle scenarios where three INVITE messages were received simultaneously. This issue has been fixed.

DEF31495/CLN31636/CLN31637/CLN31743

6755i: An issue occurred, whereby if the phone received an incoming call fol-lowed by an UPDATE with an SDP offer, the phone did not send the Status 500 response. This issue has been corrected and the phone now sends the appro-priate response in this scenario.

DEF31763/CLN32212 6735i & 6737i: When using the Aastra 5000 call manager in conjunction with the CTI dialer, if TLS/SRTP mode was enabled, the audio stream was not being decrypted correctly causing no audio to be heard by both parties in an active call. This issue has been corrected.

DEF31827/CLN31839/CLN31840

6739i: A stability issue occurred causing the phone to restart during a call and when a call was initiated and then subsequently cancelled (i.e. Phone A pressed the Cancel key and Phone B pressed the Options key simultaneously while Phone A was calling Phone B). This issue has been resolved.

DEF31887/CLN32333/CLN32405

6757i: An intermittent stability issue was observed in certain scenarios when auser attempted to park a held call into an indexed orbit. This issue has beenresolved.

DEF31920 When initiating a transfer or conference call by first pressing a Speeddial key configured as a prefix ending with a + symbol (e.g. #31#+) and then by using the dialpad or a Speeddial key to dial a proper phone number, the INVITE of the second leg of the call would only contain the prefix. This issue has been fixed.


119 RN-001037-03 REV10 – 08.2013


DEF32044/CLN32228/CLN32284/CLN32285

When used in the conjunction with the Aastra 5000 call manager and with TLS enabled, if the IP link between the call manager and phone was disconnected for a period of time longer than the configured value for the “sip registration period” parameter, upon reconnection of the IP link, the phone would reestab-lish a TLS connection but would not refresh the registration of the accounts associated with the connection. This issue has been corrected.

DEF32219 An issue was observed whereby the phone would not answer an UPDATE request if the UPDATE request contained an SDP offer. This issue has been fixed.

DEF32278 6757i: When using the phone with the Aastra MX-ONE call manager, a stability issue was observed when a user cancelled an attended transfer to an exten-sion that was diverted. This issue has been corrected.

DEF32376/CLN32380 6735i & 6737i: When using the AMR/AMR-WB codec, an audio issue would occur if there was a discrepancy between the dynamic payload codec num-bers used by the local and remote phones. This issue has been resolved.

DEF32412 6735i & 6737i: An issue was observed whereby, in certain scenarios and after a codec change, the phone would unexpectedly respond to a REINVITE with a 488 Not Acceptable Here message. This issue has been corrected.

DEF32424 When attempting to initiate a transfer in certain scenarios, if the sendonly INVITE (sent when placing the call on hold) was rejected by a 488 Not Accept-able Here response, the phone did not indicate that the hold attempt failed and also remained on the transfer screen. This issue has been fixed and now the phone returns to the previous connected view and displays a “Hold Failed” message in such situations.

DEF32561 6735i & 6737i: An issue was observed whereby the phones were not parsing the Annex B media attribute correctly. This issue has been fixed and parsing of the Annex B attribute is now fully functional in Release 3.3.1 SP2.

DEF32719 6757i: When the phone was configured as a multi-line subscriber on the Aastra 5000 call manager, an issue was observed whereby some lines were not being registered correctly. This issue has been resolved.

DEF33240 When on an active call on Line 1, if the Hold or L2 hardkey was pressed and the resulting sendonly INVITE was rejected by a 488 Not Acceptable Here response, pressing the Hold or L2 hardkey again would have no effect (i.e. the expected sendonly INVITE would not be sent). This issue has been fixed.

DEF33550/CLN33561 An issue was observed whereby in certain situations if a phone with an SCA-configured line received a re-INVITE message with PAI details brought upon by an attended transfer, the expected NOTIFY message to update the caller ID would not be received. This issue has been resolved.

User Interface

ENH30183/CLN30779/CLN30780

6757i: With the Switch Focus to Ringing Line feature enabled, pressing the Hold key while in an active call and with a secondary call incoming would not place the active call on hold as expected. This issue has been corrected.


RN-001037-03 REV10 – 08.2013 120


ENH32106/CLN32140/CLN32339

6730i, 6731i, 6753i & 9143i: A UI enhancement has been implemented inRelease 3.3.1 SP2 whereby the total of number of characters displayed onscreen for the User ID field when the HTTP Digest Login feature is enabled hasbeen increased to 15 (as opposed to 8 in previous releases).

ENH32451 6739i: When the phone is in an idle state and the backlight is turned off (i.e. when the inactivity brightness level is configured as 0), the first touch of the screen now only “wakes up” the phone ensuring there is no inadvertent acti-vation of any buttons/functions.

ENH33541/CLN33499 All phones except the 6735i, 6737i, and 6739i: An enhancement has been made whereby if a phone configured with the Executive role (when using the BroadSoft BroadWorks Executive and Assistant services feature) receives a fil-tered call, the phone now displays the caller’s details stored in the phone’s Directory (if available) instead of the information contained in the FROM header.

DEF32207 6735i & 6737i: When used in conjunction with the Aastra 400 call manager, in certain scenarios, one-way audio would be observed after placing a call on hold and then retrieving the call. This issue has been resolved.

DEF24434 6735i & 6737i: An intermittent issue was observed whereby ring tones were not audible through the speaker when they were selected using the phone’s UI. This issue has been fixed.

DEF24808 All phones except 6735i, 6737i, & 6739i: Pressing the Options hardkey twice did not close the Options menu and return the phone to its idle screen as expected. This issue has been resolved.

DEF27375 6739i: An unexpected icon would at times be displayed on the phone’s screen after a reboot. This issue has been fixed.

DEF27379 6735i & 6737i: When used with the Aastra MX-ONE call manager, if the phone was configured with a Personal Number (PEN) softkey and the softkey was in an ON state, the PEN softkey status was unexpectedly lost during the login/registration process. This issue has been fixed.

DEF27443 6739i, 6755i, 6757i, & 6757i CT: When attempting to initiate a centralized con-ference call from an SCA-configured shared phone, if the attempt failed, no indication of the failure would be displayed by the phone. This issue has been corrected and the phone now displays a “Conf Failed” message in such scenar-ios.

DEF27455/CLN28177/CLN29815

6735i & 6737i: 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 dis-played once as expected.

DEF28640 A noticeable decrease in the maximum on-hook speaker volume was observed when upgrading to 3.x firmware. This issue has been fixed and the on-hook speaker volume is now comparable to the settings of previous releases.

DEF28699/CLN32348/CLN32427

When using the CommuniGate Pro call manager, after completing a successfulsupervised transfer, the transfer recipient’s screen did not display theexpected calling party’s information. This issue has been fixed.


121 RN-001037-03 REV10 – 08.2013


DEF28937 6731i: With the Switch UI Focus to Ringing Line feature disabled, an audio mode switching issue was observed when answering a secondary incoming call using the handset. This issue has been corrected.

DEF29915 6730i, 6731i, 6753i, & 9143i: When dialing digits in pre-dial mode, it was observed that no cursor was displayed on screen. This issue has been resolved and the cursor is now visible in such scenarios.

DEF30122/CLN30811 6739i: A line switching problem occurred when lifting the handset to answer Line 3 (while Line 1 and Line 2 were on hold). This issue has been corrected.

DEF30337/CLN32952 All phones including 6735i and 6737i: The expected “No Service” message was not displayed on screen when the TLS certificate download process failed upon the phone booting up. This issue has been resolved the phone now dis-plays the “No Service” message in such scenarios.

DEF30416/CLN31122/CLN31123

When a successful transfer was performed, the phone would not respond to any dialpad inputs during the period of time the “Call Transferred” message was displayed on screen. This issue has been fixed.

DEF30653 6739i: When using the phone with the Aastra 400 call manager, entries within the Redial and Caller Lists would appear as empty buttons if the entry con-tained only a number and no name. This issue has been resolved.

DEF30800/CLN30982 6739i, 6735i, & 6737i: In situations where an outbound call was unsuccessful and resulted in a “Call Failed” message to appear on screen, any incoming calls during this time were not being indicated to the user. This issue has been cor-rected.

DEF30992/CLN33566 If an outgoing call was made and the phone received a SIP 183 message with PAI details, the phone would at times display the phone number instead of the information contained in the PAI header. This issue has been resolved.

DEF31091 6735i & 6737i: When the phone was in an idle state but the handset was off hook, if a call was incoming, placing the handset on hook caused the incoming call’s ringing to stop. This issue has been fixed.

DEF31124 After establishing a call using the G.722 wideband codec, a decrease in the ringer volume was observed. This issue has been resolved.

DEF31504/CLN31557 6757i: An issue was observed whereby the expected Caller ID would not be displayed on screen during the ringback state when initiating a conference call by pressing the Conf key and then the Redial button twice to (dial the sec-ond leg of the conference). This issue has been corrected.

DEF31595 6739i: An issue was observed whereby incoming caller names were not being displayed correctly on screen if the incoming caller corresponded to an entry in the Directory that contained diacritical marks. This issue has been fixed.

DEF31649/CLN31797 6731i: With the Live Dialpad feature enabled, in certain scenarios the phone would not produce a DTMF tone for the first digit pressed when entering a number. This issue has been resolved.

DEF32209 6757i: After a successful transfer, it was observed that context-sensitive keys (e.g. Drop, Conf, Xfer) were unavailable to be selected if an outgoing call was made using a Speeddial key and the “Call Transferred” message was displayed on screen. This issue has been fixed.


RN-001037-03 REV10 – 08.2013 122


DEF32475/CLN32816 6731i: When using the phones with the Aastra MX-ONE call manager, at times the “Missed Call[s] “message would not be displayed on the phone’s screen when calls were missed. This issue has been corrected.

DEF32948 6730i, 6731i, 6753i, & 9143i: The length of the label associated with the right navigation key in certain screens was incorrectly limited to seven characters causing some labels to be truncated. This issue has been resolved.

DEF33016 6755i, 6757i, 6757i CT, 9480i, & 9480i CT: A discrepancy was observed between recent and previous releases whereby recent releases did not display anything other than the line number when a Line key was selected to dial out. This issue has been fixed and now the screen name, display name, or user name is dis-played on screen in such scenarios (in the above order depending on availabil-ity).

DEF32503 6737i: When a bottom softkey configured with BLF/Xfer functionality was used to establish a call, the softkey’s LED was observed to still be in a flashing state after the call was terminated. This issue has been resolved.

DEF32889/CLN33466 6739i: While in a conference call, if an incoming call on another line was answered and then terminated, the phone would not remove the picture ID of the secondary call from its screen as expected. This issue has been corrected.

DEF33413/CLN33467 6735i & 6737i: When using a BLF-monitoring phone on the Metaswitch call manager, answering an incoming call to a BLF-monitored phone would cause some of the BLF-monitoring phone’s softkey LEDs to start flashing unexpect-edly. This issue has been resolved.

DEF33460/CLN33465 An issue was observed whereby the phone would display unnecessary num-bers on screen when in the Callers List in certain scenarios. This issue has been fixed.

DEF33584/DEF33587 6739i: Issues were observed whereby the backlight of the phone’s touch-screen would not turn on in certain scenarios. These issues have been resolved.

DEF22780/DEF29571/DEF30791/DEF30805/DEF30818/DEF30822/DEF30830/DEF30865/DEF30866/DEF31146/DEF31259/DEF31625/DEF31999/DEF32000/DEF32001/DEF32053/DEF32067/DEF32293/DEF32296/DEF32310/DEF32931/DEF33059/DEF33063/DEF33066/DEF33068/DEF33074/DEF33076/DEF33095/DEF33105/DEF33106/DEF33111/DEF33112/DEF33113/DEF33120/DEF32941/DEF33155/DEF33161/DEF33173/DEF33174/CLN30835

Various language/translation issues have been corrected.


123 RN-001037-03 REV10 – 08.2013


XML

ENH29991/DOC29795 Discrepancies were observed between the XML schema file and the Develop-ment Guide, XML API for Aastra SIP Phones document. These discrepancies have been corrected.

ENH30618 6735i & 6737i: When used in conjunction with the Aastra MX-ONE call man-ager, an issue was observed whereby upon log on the call manager sent a NOTIFY message with XML-formatted data setting the phone’s Diversion key, but the phone did not turn on the LED corresponding to the Diversion key as expected. This issue has been resolved.

DEF31436 6739i: When no date was defined in the XML InputScreen InputField of type “dateInt”, the terminal automatically added the current date as expected, but used single digits to represent the day and month when applicable. This issue has been fixed and the default date is now defined in the correct date format.

DEF31985/DEF32419/DEF32463/CLN32381/CLN32444/CLN32453/CLN32506/CLN32508

6735i, 6737i, 6755i, 6757i, & 6757i CT: During an active call, when an XML For-mattedTextScreen page was sent to the phone and the user pressed the Conf or Xfer softkey offered on the page, the screen did not change as expected. Additionally, an intermittent stability issue was observed in certain scenarios. These issues have been resolved.

DEF32056/DEF32063/CLN32374/CLN32377/CLN32417/CLN32468

6757i with M670i & M675i Expansion Modules: If an XML FormattedTextScreenpage was being displayed on the phone or if the phone was in the process ofstreaming a WAV file, pressing an expansion module key configured with XMLfunctionality did not have the desired effect. These issues have been cor-rected.

DEF32373 An encoding/decoding issue was observed with regards to XML scripts used by the phone. This issue has ben resolved.

DEF32431 Executing the CancelAction on an XML InputScreen would incorrectly cause the phone to return to the idle screen. This issue has been corrected and the phone now returns to the previous menu in such scenarios.

DEF32584/CLN32817 All phones including 6735i and 6737i: When an XML string containing XML escape characters was received by the phone, the phone would incorrectly discard any spaces preceding the escape character. This issue has been fixed.

DEF32685 When the phone was configured to use the Headset audio mode and the “sip xml notify event” parameter was enabled, the beeps of XML scripts could be heard on the speaker first before being heard through the headset. This issue has been resolved.

DEF32725 6755i, 6757i, & 6757i CT: On an XML InputScreen with a number InputField, entering an asterisk in the field caused a period to be displayed on screen instead. This issue has been corrected.


RN-001037-03 REV10 – 08.2013 124

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.

125 RN-001037-03 REV10 - 08.2013

http://www.aastratelecom.com/support

Appendix AThis Appendix provides information on the features implemented in SIP IP Phone Release 3.3.0, Release 3.3.1, and Release 3.3.1 SP1. The following tables summarize each feature and specifies whether it affects the Administrator, the User, or the XML Developer.

For more detailed information on the respective feature, see the latest Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide, your model-specific Aastra SIP IP Phone User Guide, and/or the Development Guide XML API For Aastra SIP Phones Firmware.

Note:Releases 3.3.0, 3.3.1, and 3.3.1 SP1 were applicable to the 6730i, 6731i, 6739i, 6753i, 6755i, 6757i, 6757i CT, 9143i, 9480i, and 9480i CT phone models only. 6735i and 6737i were not supported in these releases. The term “all phones” in this Appendix refers only to the phone models listed above.

RN-001037-03 REV10 – 08.2013 A-1

Appendix A

New Features in Release 3.3.0Feature Description


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 status menu.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Transfer VLAN ID Assignment Using DHCP


The IP phones now support VLAN ID assignment using DHCP Option 43 or Option 132. Administrators can use the new “dhcp option 132 vlan id enabled” parameter for VLAN ID assignment by DHCP Option 132. If using DHCP Option 43, the device will receive the VLAN ID from the new Option 43 values.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*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. For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

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.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for all phones

BLF Page Switch


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.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for 6755i, 6757i, 6757i CT, & 6739i only

A-2 RN-001037-03 REV10 – 08.2013

Appendix A



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, 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. For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*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, 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.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*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. 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.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

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.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Feature Description

RN-001037-03 REV10 – 08.2013 A-3

Appendix A

XML Features

LED and Key Management


For more information, refer to the Development Guide, XML API for Aastra SIP Phones.*New for all phones

XML Call Log Display


For more information, refer to the Development Guide, XML API for Aastra SIP Phones.*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



Feature Description

A-4 RN-001037-03 REV10 – 08.2013

Appendix A

New Features in Release 3.3.1Feature Description


Configuration File Encryption Fea-ture Enhancements


The encryption feature for the IP phones allow service providers the capability of storing encrypted files on their server to protect against unauthorized access and tampering of sensitive informa-tion. With Release 3.3.1, the encryption algorithm and mechanism have been updated allowing for enhanced security of the configu-ration files.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Configurable Symmetric TLS Signal-ing Support


By default, the IP phones use symmetric TLS signaling for outgoing TLS SIP messages (i.e. port 5061 is used as the persistent TLS con-nection source port). A new parameter has been implemented in Release 3.3.1 allowing administrators the ability to configure the phones to utilize a random TLS source port.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

SIP Features

BLF and Directed Call Pickup Sup-port for sipXecs


The IP phones now support the Busy Lamp Field (BLF) and Directed Call Pickup features for sipXecs (and other proxy servers). For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

DHCP Option 120 Support


DHCP Option 120 (as referenced in RFC 3361) allows SIP clients to locate a local SIP server (i.e. outbound proxy server) that can be used for all outbound SIP requests. Using the new “use dhcp option 120” configuration parameter, administrators can now enable support for DHCP Option 120 on the IP phones.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Directory Files and Background Image Reloading with Auto-Resync


During an auto-resync, the IP phones now initiate a comparison of its local directory files with those located on the configuration server and automatically update the local directory files if changes are detected. For the 6739i, the background image is also updated at this time.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

RN-001037-03 REV10 – 08.2013 A-5

Appendix A

Emergency Call Behavior Enhance-ments


Administrators now have the option of changing the default behav-ior of the IP phones when an emergency call is placed. If the new “emergency call connection hold enabled” configuration param-eter is set, the IP phones will ensure that the voice/audio path and other resources associated with the emergency call are continually active and any functions that could reduce the continuous reacha-bility of the caller are disabled.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Additional Intercom/Paging Auto-Answer Call Support


The IP phones previously supported two types of intercom/paging auto answer calls. With Release 3.3.1, support for a third type of intercom/paging auto-answer call has been implemented. When the IP phones recognize this new type of incoming intercom/pag-ing call, the call will automatically be answered and the call’s audio will be played through the IP phone’s speaker (i.e. the user’s audio preferences will be ignored).For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

Passthrough Support for Data from VLAN-Enabled PC Port to VLAN-Disa-bled LAN Port


Data passthrough is now supported on the IP phones in scenarios where the IP phone’s PC port is connected to a VLAN-enabled PC and the LAN port is connected to a device without VLAN support.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones except 6730i




The option is now available for administrators to configure the IP phones to relay a congestion/fast busy tone instead of a dial tone when the phone is in a “No Service” state. This enhancement allows visually impaired persons the ability to discern whether or not the phone is in service and can be used to send/receive calls.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for all phones

Live Dialpad Addition in Options List


Previously, only an administrator could enable or disable the Live Dialpad feature on the 6739i IP phone through the use of a configu-ration parameter. With Release 3.3.1, the Live Dialpad feature is now available to be configured (by an administrator or user) through the 6739i IP phone’s UI.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for 6739i only (implemented in all other 6700i and 9000i IP phones in previous releases).

Feature Description

A-6 RN-001037-03 REV10 – 08.2013

Appendix A



A new parameter, “ring audibly enable”, is now available in Release 3.3.1 that configures the IP phones to play the ring tone of an incom-ing call via the phone’s speaker while in an active call or if the user is in the process of dialing out.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for all phones

Shared Call Appearance (SCA) Voice-mail Enhancements


Visual indicators for voicemail messages on Shared Call Appearance (SCA) lines have now been implemented on the IP phones. A new parameter, “voice mail indicator”, has been introduced that allows administrators the ability to configure what types of visual indica-tors the IP phones should display when an voicemail message is pending on a respective SCA line.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for 9480i, 9480i CT, 6755i, 6757i, and 6757i CT only

Selectable Wideband Audio Equal-izer Settings


Users now have a choice of different wideband audio equalizer set-tings that they can employ for the speakerphone and handset audio paths on their 6739i model IP phone. In addition to the default set-ting, three new equalizer settings for both audio paths are available to choose from and can be configured using the IP phone’s UI or by defining parameters in the configuration files.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for 6739i only

XML Features

AastraIPPhoneConfiguration Lock-ing/Unlocking Support for Softkeys and Programmable Hardkeys



WAV File Streaming Repeat and Volume Support



Feature Description

RN-001037-03 REV10 – 08.2013 A-7

Appendix A

New Features in Release 3.3.1 SP1Feature Description


Dynamic Whitelist


Previously, if the Whitelist Proxy feature was enabled, the whitelist would be loaded only during the phone’s boot up process. With Release 3.3.1 SP1, dynamic whitelist support has been imple-mented, which allows the phones to refresh and resync the whitelist (without a reboot) if the IP addresses corresponding to the proxy FQDNs are changed on the DNS server.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones



The parameter “sip remove silence suppression offer” has been introduced in Release 3.3.1 SP1 allowing administrators the ability to control whether or not the silence suppression attribute should be included in the Session Description Protocol (SDP) offer.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

SIP Features

Multiple Voicemail Registration


Multiple voicemail registration is now supported on the IP phones in Release 3.3.1 SP1. By configuring a softkey or programmable key as “Speeddial/MWI” and defining call and voicemail URIs, users can monitor and listen to pending messages on multiple voicemail accounts.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and your model-specific Aas-tra SIP IP Phone User Guide.*New for all phones

Active Voice-over-IP (VoIP) Record-ing


Active VoIP recording is now supported by the IP phones in Release 3.3.1 SP1. When using the IP phones with the Aastra MX-ONE™ call manager (v4.1 or 5.0) and ASC’s EVOip 10.0 voice recording system, administrators can configure the phones to send duplicate copies of the transmit and receive RTP or SRTP voice packets to the voice recording system.For more information, refer to the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide.*New for all phones

A-8 RN-001037-03 REV10 – 08.2013

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

Documents

V3.3.1, 08/2013, pdf