96x1 Release R6.1.2 Readme Issue: 1.0 Date: December 23, 2010 Avaya one-X™ Deskphone SIP for 9601 Telephone Release 6.1.2 This file is the readme for the Avaya one-X Deskphone SIP Edition release 6.1.2 for 9601 model IP Telephones. This file describes the contents of the, December 23rd 2010 software distribution package.. Issue Fixed in the 9601 Telephone 6.1.2 Note: This applies to 9601 telephones manufactured with releases lower than 6.1.1. Problem: On rare occasions, the telephone does not respond during a power-up or just after it powers up. Solution: Install version 6.1.2. The upgrade procedure will take about 20 minutes. The telephone will reboot twice during the upgrade. Note: Do not disconnect the telephone while the upgrade is running (a warning message is shown on the telephone during this part of the procedure). For more information, see the Product Support Notice. Copyright Avaya 2010 All rights reserved Page 1 of 104 96x1 Release R6.1.2 Readme Features introduced as part of Release 6.0 not supported by the 9601 (compared to earlier 96x1 releases) Deskphone SIP 6.1 is functionally equivalent to Deskphone SIP 6.0 on the 96x1 models, but the following features are currently not supported: Presence Presence feature is not supported on Presence Server for SM environment in this release. But is supported for the SES environment. WML Browser WML browser is supported for company directory only. Korean language support Korean language display and text entry not supported PPM contact search is not supported Use WML directory search instead Calendar feature is not supported on the 9601 Exchange Server integration is not supported. Favorites Push functionality Push functionality is not supported. NAT New 9600 phones SIP telephones should not be provisioned behind a NAT with private network addresses when the CM and SES switching fabric are provisioned on a different network. The following features available on the 9608 and 9611 will not be supported on the 9601: Half-width mode Brightness Backlight BM12/BM24 USB port Copyright Avaya 2010 All rights reserved Page 2 of 104 96x1 Release R6.1.2 Readme Known Issues in Release 6.1.2 Issues observed specific to SIP 6.1.2 for 9601: Contact Search: On rare occasions, when you search for a contact, characters in the display may be unclear. Workaround: Select the line with the unclear text and press the Details softkey. Log-in: The first time a user logs in with the wrong number or password after logging out, the log-in error message is not displayed. The error message is displayed on subsequent logins.(#17147) CRAFT menu: Performing a reset, restart or clear causes the phone to hang. Workaround: Disconnect the cable and reconnect it. (#17008) System Language” setting the system language (the language to be used by administrator when the phone is logged out) to Arabic by changing SET SYSTEM_LANGUAGE "Mlf_Arabic.xml" does not function correctly. It is recommended not to set system language to Arabic. The Arabic language for users works correctly. Phone displays the personalized labels of the previous user when a new user logs into the same phone Workaround: Go to Applications screen and press Restore Default Button Labels. (#15011) Autodial: Cannot edit Autodial feature when phone is registered with SM. This is a SM issue (SM sends Auto dial as read-only mode in PPM response). Workaround: Administer Autodial with extensions on CM. Autodial works in SES environment. The primary user phone (registered inactive with home SES server) display shows “user logged in at another location” fails to auto login when the visiting user (registered on visited server) logged out. Work around: Re-login the primary phone again.(#16116) SNTP: Phone gets in unstable state when entering SNTP address as FQDN. Workaround: Use IP address instead of FQDN in the settings file.(#16140) Phone calls could be blocked while on full logging mode. If all logging categories are enabled, the phone performance is impacted. Workaround: Do not enable logging or reduce the logging to the minimum categories needed. (#15375) Phone is sending register request for all the controllers but is not displaying them as an active controller list. Copyright Avaya 2010 All rights reserved Page 3 of 104 96x1 Release R6.1.2 Readme Workaround: Logout and login or transport type to be changed from TCP to TLS and again from TLS to TCP. Phone updates the status (#16234) Phone is downloading http message when CONFIG_SERVER_SECURE_MODE is 2 and transport type is TLS Workaround: SET CONFIG_SERVER_SECURE_MODE = 1 when transport type is TLS. (#11644) MWI is not updated if user logs out and new user logs in and MWI has active entry. This MWI information is for the previous user, but displayed for new user logged in. Workaround: Log out and log in again to update MWI LED status.(#16555) PPM download is delayed by 1-2 min if call is in conference state, while fall back. Workaround: Finalize the call, completes the PPM download .(#16359) Phones are not caching the added contact in failover mode when the failover is to a third-party gateway. Workaround: When fall back to primary gateway, logout and login again .(#16795) Host is displaying transfer soft key in a third party conference call. This soft key is not supported in this scenario. (#16695) One-X Communicator shared control: In this case the phone is set to edit dialing mode. An extension is dialed on One-X Communicator, the dialed digits are entered on the new 9600 phone in edit dial mode. But there is no option on the One-X Communicator to make a call in this scenario. Workaround: Clicking on "call" soft key on new 9600 phone. (#17025) Ping is not supported if the HTTPS server is selected from the ping softkey. (#16715) If the language is set to Hebrew or Arabic and the unlock softkey is pressed, user can enter password digits from right to left side. If password is entered completely and cursor is moved from left to right the password is visible. (#16936) Hebrew language alignment issues: Extension number is aligned left instead of right Icon of call status (for example the icon of "off hook") is aligned right instead of left. In the feature page headlines are aligned right instead of left. In contact the three points of a long number are not to the right of the number. (#16978) SIP 6.1:96x1 Incorrect reason header in 380 response causing CM is rejects.(#17061) 96x1 Phone does not enter the Avaya Menu in limited phone service (#16642) Copyright Avaya 2010 All rights reserved Page 4 of 104 96x1 Release R6.1.2 Readme This release does not support larger text options. The top line becomes blank if you go off-hook and then on-hook while the telephone is in the Contact, Avaya Menu or History screen. Workaround: press the Phone button to normal display of top line (#17124). The Exchange Prompt Screen is displayed after you log in, although the 9601 does not support Exchange Server integration. Workaround: press the OK button to continue. (#15386). Copyright Avaya 2010 All rights reserved Page 5 of 104 96x1 Release R6.1.2 Readme 9601phone SIP Release 6.1.2 Package Contents The package contains the readme file and all the files necessary to upgrade the Avaya 9601 SIP telephones to SIP Release 6.1.2. The following files are included in each package S9601aSALB_R6_1_2r26428_V11r1271.tar – The 9601 6.1 SIP phone application tar file S9601aUKR_V11r1270_V11r1270.tar – The 9601 6.1 SIP platform system tar file S9601aSALB_R6_1_0r26418_V11r1271.tar.gz – Intermediate file – used only when upgrading a 9601 to SIP version 6.1.2 96x1Supgrade.txt – This file is downloaded by the Avaya IP telephones and instructs the telephones on how to upgrade. DO NOT EDIT this file. You MUST USE the 96x1Supgrade.txt file included in this package to upgrade to 6.1 SIP SP2 for 9601 phone Note that this file is designed for environments in which all 9601 endpoints will be upgraded to SIP 6.1 SP2 phone application and kernel / root file system files. This file will only be used by the 9601 and not applicable for other 96xx series type (including 9608, 9611G,9621G and 9641G. Earlier 9600 series phones use a different upgrade.txt file (96xxupgrade.txt) release.xml – An XML-format text file that is designed to be used with Avaya Integrated Management (AIM) through the Software Update Manager (SUM). Fifteen predefined language files: Mlf_Arabic.xml Mlf_BrazilianPortuguese.xml Mlf_CanadianFrench.xml Mlf_CastilianSpanish.xml Mlf_Chinese.xml Mlf_Dutch.xml Mlf_English.xml Mlf_German.xml Mlf_Hebrew.xml Mlf_Italian.xml Mlf_Japanese.xml Mlf_Korean.xml Mlf_LatinAmericanSpanish.xml Mlf_ParisianFrench.xml Mlf_Russian.xml Copyright Avaya 2010 All rights reserved Page 6 of 104 96x1 Release R6.1.2 Readme Eight extended Korean ring tone files: KoreanRT1.xml KoreanRT2.xml KoreanRT3.xml KoreanRT4.xml KoreanRT5.xml KoreanRT6.xml KoreanRT7.xml KoreanRT8.xml Four certificate files: av_csca_pem_2032.txt Avaya Call Server CA certificate with an expiration date of 2032 av_prca_pem_2033.txt Avaya Product Root CA certificate with an expiration date of 2033 av_sipca_pem_2011.txt Avaya SIP Root CA certificate with an expiration date of 2011 av_sipca_pem_2027.txt Avaya SIP Root CA certificate with an expiration date of 2027 Other configurations files . 46xxsettings.txt System specific parameters should be entered into this file. This file is not included in the package and available on the Avaya support side. License Agreements HTTP Server functionality is provided by the GoAhead WebServer 2.1, Copyright (c) 2004 GoAhead Software, Inc. All Rights Reserved. iputils 20071127 Copyright (c) 1989 The Regents of the University of California.