Aastra Models 6735i and 6737i SIP IP Phones. SIP Service Pack 2 Release Notes

Aastra Models 6735i and 6737i SIP IP Phones SIP 3.2.2 Service Pack 2 Release Notes RN-001038-00 REV00 07.2012

Content SIP IP Phone Models 6735i and 6737i Release Notes 3.2.2 Service Pack (SP)2............................................................ 1 About this document...................................................... 1 Release notes topics....................................................... 1 General information....................................................... 2 Release content information............................................... 2 Hardware supported....................................................... 2 Bootloader requirements................................................... 2 New Features in Release 3.2.2 SP2........................................ 3 Configuration Features..................................................... 3 SIP Features................................................................ 3 User Interface Features..................................................... 3 Additional Information..................................................... 4 Configuration Features.................................................... 4 Configurable Display for Blank BLF/List Softkeys............................ 4 SIP Features............................................................... 5 Blind Transfer to a Contact in Phone Directory.............................. 5 User Interface Features.................................................... 7 Scrolling Phone Numbers.................................................. 7 Increased Number of Displayed Characters for Softkey Line Labels........... 8 Issues Resolved in Release 3.2.2 SP2..................................... 9 Contacting Aastra Telecom Support.................................... 15 II RN-001038-00 REV00 07.2012

SIP IP Phone Models 6735i and 6737i Release Notes 3.2.2 Service Pack (SP)2 About this document This document provides new features for the Aastra models 6735i and the 6737i SIP IP Phones for release 3.2.2 SP2. Note: This release applies to the phone models mentioned above only. For more detailed information about features associated with each phone, and for information on how to use the phones, see your model-specific SIP IP Phone Installation Guide and the SIP IP Phone User Guide. For detailed information about more advanced features, see the Aastra Models 9000i and 6700i Series SIP IP Phones Administrator Guide and/or the Development Guide XML API For Aastra SIP Phones Firmware 3.2.2. Release notes topics Topics in these release notes include: General information New Features in Release 3.2.2 SP2 Additional Information Issues Resolved in Release 3.2.2 SP2 Contacting Aastra Telecom Support RN-001038-00 REV00 07.2012 1

SIP IP Phone Models 6735i and 6737i Release Notes 3.2.2 Service Pack General information Release content information This document provides release content information on the Aastra 6735i and 6737i Series SIP IP Phone firmware. Model Release name Release version Release filename Release date 6735i Generic SIP 3.2.2 SP2 FC-001362-00-REV01 July 2012 6737i Generic SIP 3.2.2 SP2 FC-001363-00-REV01 July 2012 Hardware supported This release of firmware is compatible with the following Aastra IP portfolio products: 6735i 6737i Bootloader requirements This release of firmware is compatible with the following Aastra IP portfolio product bootloader versions: 6735i: Boot2 1.0.0.0 or higher 6737i: Boot2 1.0.0.0 or higher 2 RN-001038-00 REV00 07.2012

New Features in Release 3.2.2 SP2 This section provides the new features in Release 3.2.2 SP2. These new features apply to both of the Aastra model 6735i and 6737i IP Phones, unless specifically stated otherwise. 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 Display for Blank BLF/List Softkeys (For Administrators) Previously, when softkeys were configured as BLF/List keys on the phone but there were not enough members in the BLF/List on the BroadSoft BroadWorks server side, then a series of question marks would be displayed on screen beside some of the softkeys. Administrators can now configure whether or not the series of question marks should be hidden using the new keys noname hidden parameter. SIP Features Blind Transfer to a Contact in Phone Directory (For Users) Users can now complete a blind transfer to a contact in their local directory. If a user is in a call and initiates a transfer, they can navigate to the Directory screen where a new Transfer key can be pressed to complete a blind transfer. User Interface Features Scrolling Phone Numbers (For Users) Increased Number of Displayed Characters for Softkey Line Labels (For Administrators) Previously, if a long remote (outgoing or incoming) number was displayed on the phone, users were not able to scroll to the end of the number. Users now have the ability to scroll through a remote number that is displayed on the phone. Users can press the scroll down navigation key to view the rest of the phone number content. Administrators can now disable line state icons to display 10 characters on softkeys and top softkeys for line labels on the phones. This is useful if the user wants to display a full 10 digit number as the softkey label, instead of a shortened label containing only 7 digits followed by ellipsis characters. RN-001038-00 REV00 07.2012 3

Additional Information Configuration Features Configurable Display for Blank BLF/List Softkeys Previously, when softkeys were configured as BLF/List keys on the phone but there were not enough members in the BLF/List on the BroadSoft BroadWorks server side, then a series of question marks would be displayed on screen beside some of the softkeys. Administrators can now configure whether or not the series of question marks should be hidden using the new keys noname hidden parameter. If this parameter is set to 1 (enabled) then the series of question marks will be hidden and nothing will be shown on the screen beside the affected softkeys. If this parameter is set to 0 (disabled) then the series of question marks will be displayed on the screen indicating blank BLF/List softkeys. Configuring the Display for Blank BLF/List Softkeys Use the following parameter to configure the display for blank BLF/List softkeys: Parameter keys noname hidden Configuration Files aastra.cfg, <model>.cfg, <mac>.cfg Description Format If this parameter is set to 0 (disabled) then a series of question marks will be displayed on the screen indicating blank BLF/List softkeys. If this parameter is set to 1 (enabled) then the series of question marks will be hidden and nothing will be shown on the screen beside the affected softkeys. String Default value 0 Range 0-1 0 (disabled) 1 (enabled) Example keys noname hidden: 1 4 RN-001038-00 REV00-07.2012

Additional Information SIP Features Blind Transfer to a Contact in Phone Directory In 3.2.2 SP2, users can complete a blind transfer to a contact in their local directory. If a user is in a call and initiates a transfer, they can navigate to the Directory screen where a new Transfer key can be pressed to complete a blind transfer. When a directory entry is shown, there is a new Xfer softkey below the current Dial softkey to trigger a blind transfer. This new Xfer softkey is only available if a transfer has been initiated. If a directory entry has multiple numbers, softkey 2 is used for the Arrange function. If a transfer has been initiated, the Arrange function will be replaced with the Xfer function. For example: Case 1: Consultation of personal directory from a phone in Idle state or during a call (no transfer initiated): Directory 001 - Dial 1. John 2. Kim 3. Steve - Add New Delete - Details - Quit - 905-760-9999 Line: 1 Dial Delete Arrange Change Add Number Quit Entry has multiple numbers RN-001038-00 REV00 07.2012 5

Additional Information Case 2: Consultation of personal directory from a phone while in a call and a transfer has been initiated: - Dial - Xfer - Add New Directory 1. John 2. Kim 3. Steve Delete - Details - Quit - 001 905-760-9999 Line: 1 Dial Xfer Add Number Delete Change Quit Entry has multiple numbers To Transfer a Call to a Contact in the Phone Directory: 1. Connect to Party 1 (if not already connected). Party 1 is the party you want to transfer. 2. Press the Transfer key. You should hear a dial tone as a second line opens up. 3. Press the Directory key and select a contact. 4. To complete a blind transfer, press the Transfer key again before the receiving end answers. To complete a consultative transfer, press Dial to call the contact. Remain on the line to speak with Party 2 before pressing the Transfer key again to transfer Party 1 to Party 2. To cancel the transfer, select Cancel on the display screen or press the Goodbye key. 6 RN-001038-00 REV00 07.2012

Additional Information User Interface Features Scrolling Phone Numbers Previously, if a long remote (outgoing or incoming) number was displayed on the phone users were not able to scroll to the end of the number. Now in 3.2.2 SP2, users have the ability to scroll through a remote number that is displayed on the phone. Users can press the scroll down navigation key to view the rest of the phone number content. For example: If a remote incoming call number is 123456789012345678901234567 (27 numbers long), the phones will display the following number portion initially: L1 #1 2212 John 1234567890123456789 Answer Ignore After the user presses the scroll down navigation key, the rest of the remote number content is displayed, with shown at the end: L1 #1 2212 John 01234567 Answer Ignore If the user presses the scroll up navigation key, the first line will be rolled back to the screen showing 1234567890123456789. RN-001038-00 REV00 07.2012 7

Additional Information Increased Number of Displayed Characters for Softkey Line Labels Administrators can now disable line state icons to display 10 characters on softkeys and top softkeys for line labels on the phones. This is useful if the user wants to display a full 10 digit number as the softkey label, instead of a shortened label containing only 7 digits followed by ellipsis characters. When a softkey or top softkey is defined as a line, the circle in front of the softkey label (line icon) can be removed using the new line icon disabled parameter. When the line icon disabled parameter is set to 1, the line icon will not appear and the label can be displayed with up to 10 characters (label will not be shortened and no ellipsis characters will appear). Configuring the Increase of Displayed Characters for Softkey Line Labels Use the following parameter to disable the line icon and increase the number of characters displayed for softkey line labels: Parameter line icon disabled Configuration Files aastra.cfg, <model>.cfg, <mac>.cfg Description Format Disable the line icon (circle) displayed in front of the softkey line label. This allows the softkey line label to be displayed with up to 10 characters (label will not be shortened and no ellipsis characters will appear). Boolean Default value 0 Range 0-1 0 (disabled) 1 (enabled) Example line icon disabled: 1 8 RN-001038-00 REV00 07.2012

Issues Resolved in Release 3.2.2 SP2 This section describes the issues resolved on the IP Phones in Release 3.2.2 SP2. The following table provides the issue number and a brief description of each fix. Note: Unless specifically indicated, these resolved issues apply to both phone models. Issues Resolved Issue Number Description of Fix Configuration DEF26461/CLN27446 DEF26754/CLN27320 DEF26981/CLN27595 DEF23251/CLN27480 DEF27843 DEF28851/CLN28873 DEF27756 When utilizing pin code masking, if a syntax error was made in one of the strings for the pin suppression dial plan parameter, the phone would intermittently reboot. This issue has been resolved. If Microphone Mute (under the Incoming Intercom Settings) was disabled utilizing the Aastra Web UI, when a call was made using the Zultys MXIE client, the microphone continued to be in a muted state. This has been fixed and configuring the Microphone Mute feature now functions as expected. If the confxfer live dial parameter was enabled, the phone failed to execute a transfer of an incoming call when using the directory to dial out to the second leg. This issue has been resolved. If the Do No Disturb (DND) feature was enabled on the phone and an incoming call was rejected, the phone would previously reject the call by indicating the configurable rejection code sip ignore status code instead of the expected 486 Busy Here message. This has been corrected and the correct message is now sent when the DND feature is enabled. 6737i: The Park Call and Pick Up Parked Call options are now available to be configured through the phone s Web UI. These options can be found under the Basic Settings :: Preferences :: General category. With Microphone Mute (under the Incoming Intercom Settings) enabled through the Aastra Web UI, when a user established an active call using the Zultys MXIE client, if the remote party placed the call on hold and then retrieved the call, the call would lose two-way audio functionality. This issue has been fixed. The PoE Power Class in Link Layer Discovery Protocol (LLDP) advertisements has been corrected to PoE Class 2 for the 6735i/6737i IP phones. SIP DEF25069/CLN25254 After a muted call initiated by the Zultys MXIE client was transferred by the REFER method sucessfully to a user s phone, the mute button LED would flash on the phone but the call was automatically unmuted. This issue has been corrected and the mute status is now unaffected for calls transferred by the REFER method and initiated by the Zultys MXIE client. RN-001038-00 REV00 07.2012 9

Issues Resolved in Release 3.2.2 SP2 Issue Number DEF26523/CLN27494 DEF22347/CLN27433 DEF23018/CLN26769 DEF26578/DEF26579/ CLN27272/CLN27314 DEF26681/CLN27033 DEF26654/CLN27034 DEF26287/CLN27447 DEF25860/CLN27392 DEF26722/CLN27445 Description of Fix When using the Zultys MXIE client, continuously dialing and cancelling outgoing calls (before the call was picked up on the remote side) would cause the phone to reboot. This issue has been resolved. If a phone call was made using the Zultys MXIE client, and the call was then terminated using the client while in the Waiting state, the phone would not clear the call after receiving a 410 Gone message. This issue has been corrected and in such situations the phone now shows a call failed message and clears the call. When a call was incoming on Line 2 (with an active call on Line 1) and the caller on Line 1 had dropped the call so the user had the handset off-hook, the phone did not play the expected ring tone for the incoming call on Line 2. This issue has been corrected and ring tone behavior while the handset is offhook is now functioning as expected. Immediately after the phone was rebooted and an outgoing call was made (placing the phone in a ringback state), if the phone received an incoming call during this state, after the call waiting tone subsided both local and remote ringback tones could be heard, either at the same time or at alternating intervals. This behavior has been corrected and the remote ringback is now inaudible in the above scenario. An issue was found where a user taking the handset off hook to make a secondary call while on hold in an SCA bridged conference call activated Line 1 instead of Line 2, therefore reconnecting the user to the initial SCA bridged conference call. This issue has been resolved and taking the handset off-hook in the above scenario will now produce the expected result. With phones configured for SCA, issues were observed when a user placed an active call on Line 1 on hold, and a secondary user on the SCA account picked up the handset to place a call. The secondary user s phone would intermittently pick up the call on hold on Line 1 instead of seizing Line 2. This has been corrected. Intermittent reboots were observed when trying to edit a key for speed dial functionality. This issue has been corrected and editing keys for speed dial functionality is behaving as expected. With the phone configured for use with the Zultys MXIE client with the autoanswer feature enabled, when an active call on the phone was placed on hold and an intercom call initiated by an MXIE client user was sent to the phone, the phone did not automatically answer the call as expected. This issue has been resolved and the phone now automatically answers all incoming intercom calls when the auto-answer feature is enabled. In dual-registration situations with the MX-ONE call manager, the phone, at times, would not log off the MX-ONE system as expected and would become unresponsive. Additionally, when the MX-ONE call manager sent a forced logoff message to the phone, this intermittently caused the phone to reboot. This has been corrected and the phone will now gracefully log off when required. 10 RN-001038-00 REV00 07.2012

Issues Resolved in Release 3.2.2 SP2 Issue Number DEF24623/CLN27449 DEF26363/CLN27434 DEF26359/CLN27602 DEF25471/DEF25472/ CLN27263/CLN27264 DEF26688/CLN27598 DEF26473/CLN27298 DEF24637/CLN26920 DEF26488/CLN27468 DEF22723/CLN27020 ENH27025/CLN27474 DEF26865/CLN27281 DEF27014/CLN27282 Description of Fix If a digit key on the phone was set up for speed dial functionality and the configured speed dial number contained a comma (i.e. pause), initiating the speed dial feature would prepend the digit key value to the configured speed dial number. This issue has been corrected and speed dial functionality is now unaffected by speed dial numbers containing commas. When performing a blind transfer using the REFER method, the phone would not send a NOTIFY message with a sipfrag 200 OK response. This would cause blind transfer failures. This issue has been resolved and blind transfers using the REFER method are now functioning as expected. Stability issues were observed on the phone when configuring options in the Services menu. The issues have been fixed and stability has been improved. Callpark and pickup for ININ was not functioning correctly in 3.2 GA firmware. This issue has been resolved and the feature is now working as expected. An issue was observed where the phone did not send the expected SDP/200 OK response after the server sent an SDP/UPDATE request. The phone instead sent a 491 Request Pending response, which caused issues with regards to the phone not switching to voice mail. This issue has been resolved. Utilizing Metaswitch, when the phone had more than one SCA line configured, if the first line was connected and a second call was incoming, the phone sent a 486 Busy message. This has been fixed and the phone now handles additional incoming SCA calls correctly. An issue was observed where the phone incorrectly accepted (i.e. responded with a 200 OK response) an SDP Answer containing an unsupported offer in the PRACK message. This issue has been corrected and the phone now sends 488 Not Acceptable Here response in such situations. When on a Clearspan account and with BLF/List configured, the phone would resubscribe to the BLF/List service too frequently (i.e. before the subscription was set to expire). This issue has been resolved and resubscription to the BLF/List service is now only performed at the set intervals. Support for the Remove route header in SIP packet feature has now been implemented. Improvements have been made to allow for SDP support in both 180 Ringing and 200 OK messages. When the park/pickup feature was configured for use with an ININ server, if a user selected a line and pressed the Pickup key, the phone did not wait for the orbit number to be dialed before trying to pick up a call. This issue has been corrected and the phone now waits for an orbit number before trying to pick up a call. Additionally, if no orbit number is dialed, the Pickup label is displayed on screen. When the park/pickup feature was configured for use with an ININ server, if a user pressed the Dial key after selecting a line, pressing the Pickup key, and dialing the orbit number, the call would not be picked up and the call would fail. This has been corrected. RN-001038-00 REV00 07.2012 11

Issues Resolved in Release 3.2.2 SP2 Issue Number DEF27038/CLN27108 DEF26705/CLN27313 DEF27091/CLN27438 DEF26830/CLN27283 DEF27156/CLN27488 DEF26979/CLN27494 DEF28032 DEF28309/CLN28447 DEF27376/CLN28587 DEF28130/CLN28192 DEF28553/CLN28593 DEF28409/DEF28201 Description of Fix An issue was observed where the phone would restart when receiving a check-sync notification. This issue has been corrected and the phone now operates as expected when a check-sync NOTIFY message is received. If a user was on an active call using an SCA configured line and ended the call during a network outage, the line status remained active as the server could not modify the SCA status of the phone. When the user seized Line 1, a new call would automatically be sent out without any user input. This issue has been fixed. Previously, when a call was initiated using the Zultys MXIE client and answered by the remote party, pressing the Goodbye key would not send a BYE message to the server and the remote party would not be disconnected. This has been resolved and a BYE message is now sent in such situations. When performing an ININ call park, pressing the Xfer softkey did not complete the park as expected, but instead put the call on hold. This issue has been resolved and the Xfer key now completes the ININ park in such situations. An issue was observed whereby after performing an attended transfer the phone could not make or receive calls. This issue has been resolved. Intermittent stability issues were observed with regards to the SIP engine when starting another call before the previous call was answered using the Zultys MXIE client. This has been fixed. When the phone was configured for server-side intercom with the Zultys MX250 system and auto-answer, mute microphone, and barge-in were enabled, if an intercom call was delivered to the phone while the phone was already in an initial call, the phone would correctly receive the intercom call but no audio could be heard. This issue has been corrected. With phones configured for SCA, if a call on an SCA-configured line was answered and then terminated quickly, the phone did not send a BYE message causing the line s LED indicator to stay on. This issue has been resolved. When in an active call using headset mode on a phone configured for use on a Zultys account, if a secondary call was incoming and call waiting tone was enabled, audio would be lost on the active call. This issue has been fixed and the audio is now functioning as expected in such situations. When using the phone with the Aastra MX-ONE server, intermittent freezes were observed when the phone switched between two calls on two active lines (i.e. Line 1 and Line 2). This issue has been corrected. When using the phone s UI call list XML application in conjunction with the Aastra 400 server, the phone intermittently would not switch the audio to the handset after going off hook to place a call. Ringback and speech audio was incorrectly played back on the speaker. This has been resolved and the audio is now sent to the correct path/device in such situations. Improvements have been made to the phones to help mitigate intermittent audio distortion/quality issues. 12 RN-001038-00 REV00 07.2012

Issues Resolved in Release 3.2.2 SP2 Issue Number DEF28575/CLN28594 DEF28835/CLN28853 Description of Fix When used in conjunction with the Aastra 5000 server (Release 5.4), an issue was observed whereby the phone would not send the expected unregister message after a user logged out of his/her account. This issue has been corrected. An audio issue was observed when using the phone in conjunction with a Zultys call manager. When a user was on an active call and had another call on hold, if the call on hold was dropped by the remote party, the active call would lose two-way audio functionality (i.e. the user could not be heard by the other party). This issue has been fixed and audio functionality is now working as expected in such scenarios. User Interface DEF26296/CLN27382 DEF26490/CLN27310 DEF26467/CLN27301 DEF26821/CLN27265 DEF22969/CLN27297 DEF26479/CLN27475 DEF26493 DEF27105/CLN27287 DEF28120/DEF26491 An issue was observed with regards to the phone s screen turning blank on the second leg of a consultation transfer or conference call. This has been corrected. When navigating to the Callers List through the Services :: Directory menus and then exiting all menus to get to the idle screen, the LED beside the Directory softkey would still be on. This issue has been corrected and the Directory LED is now functioning as expected. With the keys noname hidden parameter enabled, when a new member was added to the BLF/List, an artifact would be displayed on screen beside the phone icon for the respective BLF/List key. This has been resolved and the artifact is no longer visible. An issue was observed where the phone would not display the expected Park label on screen when parking a call. This issue has been corrected. If the phone received a SIP NOTIFY check-sync message and the phone s configuration and/or firmware changed, the phone would restart but did not display a Restarting message on screen. This issue has been resolved. If a user pressed the Service softkey and an incoming call occurred, after the phone returned to the idle screen, the Service softkey LED would continue to stay on and the Services and Goodbye keys would be unresponsive. This has been corrected. If a user tried to set a speed dial entry by pressing an empty softkey (either on the phone or on an expansion module) and an incoming call occurred, after the phone returned to the idle screen, the user was not able to continue setting a speed dial entry and speed dial creation was not possible. This issue has been resolved. When a phone was configured for use with ININ and a call was parked using the Call Park Auto softkey (i.e. Speed dial/xfer key) the XML TextScreen page would be displayed on the phone s screen as expected, but would disappear after a few seconds. This has been corrected. An issue was observed whereby BLF LEDs on the BLF monitoring phone would go out of sync if the monitoring phone went off-hook and then back on-hook. Applicable only to softkeys in positions other than position 1 (e.g. softkey2, softkey3, etc.), BLF icons would be displayed correctly, but the LEDs would reflect BLF states incorrectly. This issue has been fixed. RN-001038-00 REV00 07.2012 13

Issues Resolved in Release 3.2.2 SP2 Issue Number DEF28155 DEF28305/CLN28446 DEF28491/CLN28588 DEF28561/CLN28589 DEF28509 DEF28689 DEF26576/DEF26682/ DEF19946/DEF26629/ DEF27190/DEF27191/ DEF27192/DEF24971 Description of Fix Unexpected behavior was observed with regards to the Message Waiting Indicator (MWI) LED when a voicemail message was pending on the phone and the user made various configuration changes to either the Do Not Disturb (DND) or Call Forward (CFWD) features on the phone. This has been resolved and the MWI LED is now functioning as expected in such scenarios. An issue was observed whereby the MWI LED would continuously flash if a conference call was established and then subsequently dropped on a phone configured for SCA functionality. This issue has been fixed. When a message was pending on the phone and the MWI LED was flashing as expected, if an incoming call was received, placed on hold, and then picked up again, the MWI LED would incorrectly flash at the hold-mode cadence instead of returning to the message-waiting cadence. This issue has been resolved. When using the phone with the Aastra 400 server, the server side XML softkey functions configured for the phone did not reflect the correct LED state. After server side activation and when the phone returned to an idle state, the softkey s LED would remain off instead of turning back on as expected. This issue has been fixed. An issue was observed with phones configured to utilize the SCA call bridging feature, whereby the LED status of an SCA-configured line would not change (i.e. from red to green) as expected on a user s phone after the user joined a call in progress on the respective SCA-configured line. This issue has been resolved. When used in conjunction with the Aastra 5000 server in situations where the phone had one or more logged missed calls, pressing a softkey configured as XML with call forward functionality would not turn on the respective softkey s LED as expected. This issue has been fixed. Various language/translation issues have been corrected. 14 RN-001038-00 REV00 07.2012

Contacting Aastra Telecom Support If 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 America Please contact your regional Aastra Technical Support. RN-001038-00 REV00 07.2012 15

Disclaimer Aastra Telecom, Inc. will not accept liability for any damages and/or long distance charges, which result from unauthorized and/or unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom, Inc. will not be liable for technical or editorial errors or omissions contained within this documentation. The information contained in this documentation is subject to change without notice. Copyright 2012 Aastra Technologies Limited, www.aastra.com.