advertisement
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
Avaya 1600 Series IP Deskphone Software Release 1.3.4 Read me
This file is the Readme for the Avaya 1600 Series IP Deskphone Software Release 1.3.4
(H.323 1.3 Maintenance Release 4). This file describes the content of the March 2014
Maintenance Release software distribution package. It also includes Product Advisements related to known issues with this Software Release.
Avaya 1600 Series IP Deskphone H.323 Software Release 1.3.4 is supported on the 1603,
1603-I, 1603SW, 1603SW-I, 1608, 1608-I, 1616, and 1616-I IP Deskphones only. It will not load or operate on any other models.
Aura
®
Communication Manager, IP Office and B5800 Branch Gateway users are advised to consult their respective product publications for information regarding support of this release on their platform.
This Maintenance Release supersedes all previous Avaya 1600 Series IP Deskphone Service
Packs. Avaya recommends that all customers upgrade both new and installed 1600 Series
IP Deskphones to this version at their earliest convenience.
To upgrade 1600 Series IP Deskphone:
• Install zip package on Avaya Utility Server. Alternatively, the package can be unzipped in the root directory of any HTTP server.
•
Make any adjustments required by your environment to the 46xxsettings.txt
• Reset Avaya 1600 Series IP Deskphone
IMPORTANT
If you downloaded the version 1.3.4B software between August 27 th
, 2013 and February
17 th , 2014 please upgrade to 1.3.4D as soon as possible. 1.3.4B was removed from the
Avaya Support website on February 17 th
, due to the issues captured in PSNs cited below:
PSN004151u - 16XX IP Deskphones experience rolling reboots after upgrading to 1.3.4B
PSN004134u - Downgrade of 16xx H.323 phones to 1.3.2 (or earlier) from 1.3.3 (or 1.3.4B) factory loaded software results in duplicate MAC and Serial Number
Avaya Servers Compatibility
Copyright Avaya 2013 All rights reserved
Page 1 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
Servers Supported versions
Comments
Avaya Aura®
Communication
Manager (CM)
5.2.1 and higher Avaya recommends using the latest Communication
Manager release with these models of IP
Deskphone. See the “Communication Manager
Software & Firmware Compatibility Matrix” at http://support.avaya.com
for the supported software/firmware versions of the Media Server,
Media Gateway, and circuit packs.
CM 5.2 is the minimum version required to support the following features:
• Native support of 1600 Series IP
Deskphone
CM releases prior to 5.2 do not provide native support for the 1600 Series IP Deskphone. Avaya recommends that the 1616/1616-I IP Deskphone be administered as a 4620/4621 IP Deskphone, other models be administered as a 4610 IP
Deskphone, and the BM32 as a EU24 expansion module.
For more details, please refer to the H.323 configuration section in the CM Administration
Guide which can be downloaded from http://support.avaya.com
.
Avaya IP Office
(IPO)
6.0 or later and
IP500 V2 hardware only
Avaya B5800
Branch Gateway
(B5800)
Customers are requested to consult the IP Office
Technical Bulletin(s) or Release Notes for compatibility with specific IP Office releases
Please consult the B5800 Release Note(s) for details on specific B5800 software compatibility.
H.323 1.3.4 Package Content
The H.323 Software Release 1.3.4 package contains all the files necessary to upgrade Avaya new or previously installed 1600 Series IP Deskphones to H.323 R1.3.4.
The following files are included in this package:
H.323 1.3 Maintenance Release 4 List of Firmware files and supported Phones
Hardware Software
Comcode Model Boot Code Application Code
Copyright Avaya 2013 All rights reserved
Page 2 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
700415540
700476849
700458508
700858524
700415557
700458532
700450190
700458540
1603
1603-I
1603SW
1603SW-I
1608
1608-I
1616
1616-I hb1603ua1_340D1_340D.bin ha1603ua1_340D.bin hb1603ua1_340D.bin hb1603ua1_340D.bin hb1603ua1_340D.bin hb1608ua1_340D.bin hb1608ua1_340D.bin hb1616ua1_340D.bin hb1616ua1_340D.bin ha1603ua1_340D.bin ha1603ua1_340D.bin ha1603ua1_340D.bin ha1608ua1_340D.bin ha1608ua1_340D.bin ha1616ua1_340D.bin ha1616ua1_340D.bin
• GBM32_B_1_1_0.hex - Button Module firmware version 1.1.0 for BM32.
• 16xxupgrade.txt – To upgrade to R1.3.4, you must change your
16xxupgrade.txt file. The sample upgrade script that is included in the package is generic, in that it will upgrade all existing 1600 Series IP Deskphones to
R1.3.4. If you have other phones that are using this script for other software upgrades and installations, please note the changes between the scripts. Please make a backup copy of your current upgrade script, and incorporate the binary name changes for release R1.3.4 into your 16xxupgrade.txt file.
• Ten predefined language files for phone display: o mlf_Sage_v69_dutch.txt o mlf_Sage_v69_french_can.txt o mlf_Sage_v69_french_paris.txt o mlf_Sage_v69_german.txt o mlf_Sage_v69_italian.txt o mlf_Sage_v69_japaneseKat.txt o mlf_Sage_v69_portuguese.txt o mlf_Sage_v69_russian.txt o mlf_Sage_v69_spanish.txt o mlf_Sage_v69_spanish_latin.txt
• Five configurable language files for the phone display: o mlf_Sage_v69_arabic.txt o mlf_Sage_v69_chinese.txt o mlf_Sage_v69_trad_chinese.txt o mlf_Sage_v69_hebrew.txt o mlf_Sage_v69_korean.txt
• Five configurable font files for the five languages above o Arabic_S11_V34.rbm.lzma (Font file for Arabic Language) o GB_S11_V34.rbm.lzma (Font file for Simplified Chinese Language) o Big5_S11_V34.rbm.lzma (Font file for Traditional Chinese Language) o Hebrew_S11_V34.rbm.lzma (Font file for Hebrew Language) o KSC_S11_V34.rbm.lzma (Font file for Korean Language)
• release.xml
• The signatures in the signatures subdirectory of the .zip distribution packages
Copyright Avaya 2013 All rights reserved
Page 3 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme are only intended to be used by the file server, and the file server that is on the
CM 6.0 Utility Server is the only file server that currently supports this.
Refer to the 1600 Series IP Deskphone Administration Guide on http://support.avaya.com
for more information on the use of FONTFILE and LANGxFILE.
System specific parameters should be entered into the 46xxsettings.txt file which is available for separate download at http://support.avaya.com
. Warning: Before modifying your 46xxsettings.txt file, please make a backup copy of the file.
Copyright Avaya 2013 All rights reserved
Page 4 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
Resolved issues in Avaya 1600 Deskphone H.323 1.3
Maintenance Release 4 version D (1.3.4D)
Released March 7
th
, 2014
Area
Upgrade
Defect ID Defect Name
SAGE16XX-829 Phones downgraded from 1.3.3 or 1.3.4B to 1.3.2 or earlier result in phones with duplicate/default MAC
Addresses and factory Serial Numbers.
Refer to - PSN004134u
SAGE16XX-838 16XX phones get into a rolling reboot state after upgrading to 1.3.4B
Refer to - PSN004151u
Resolved issues in Avaya 1600 Deskphone H.323 1.3
Maintenance Release 4 version B (1.3.4B)
Released August 27
th
, 2013
Area
Audio
Performance
Defect ID Defect Name
SAGE16XX-751 AGC (Automatic Gain Control) is not working on 16xx.
SAGE16XX-765 Improvement of the handset audio quality.
SAGE16XX-774 Low Ringer Volume of second call when first call is terminated by DROP button.
SAGE16XX-745 Fixed multiple memory issues that can cause rebooting.
SAGE16XX-746 Fixed null pointer dereferences that can cause unpredictable behavior.
SAGE16XX-747 Fixed multiple out of bounds errors that can cause rebooting.
SAGE16XX-607 1616 phone reboots when connected to IPO after pressing the call appearance button on BM32
SAGE16XX-727 16xx H323 logging engine improvement.
SAGE16XX-767 Resource leaks that can cause performance degradation and rebooting.
SAGE16XX-775 1608 phone reboots if logged in to 1616 account with some bridge-appearances configured on BM after call to bridge-appearance numbers.
SAGE16XX-677 16xx UI performance improvement.
SAGE16XX-754 TFFS recovering mechanism.
Copyright Avaya 2013 All rights reserved
Page 5 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
Area
Backup\Restore
Defect ID Defect Name
SAGE16XX-705 Font recovery mechanism.
SAGE16XX-700 Phone 1616 with BM32 is frozen at the enter credential screen when subfolder is configured on IIS7.
Application\UI SAGE16XX-488 The phone does not synchronize language with IPO.
SAGE16XX-731 Some parameters in Screen/Sound, Call Settings,
Application, Advanced options are changed to default after rebooting.
SAGE16XX-729 Extension configured for busy-indicator or call-forward is displayed in wrong format when changing CM language to Arabic.
SAGE16XX-760 Phone displays wrong conference icon if it isn’t main initiator.
SAGE16XX-758 Join soft key disappears after hold recall timeout.
SAGE16XX-762 Redial List is empty although there’s information in outgoing call log.
SAGE16XX-782 Phone displays wrong holding conference icon if it isn’t main initiator.
SAGE16XX-763 Complete and Cancel softkeys disappear when Hold
Recall timeout expires
Configuration/Upgrade SAGE16XX-689 Skip upgrade of 1603 phone to H323 firmware if it is a
SIP phone.
Known Issues in Avaya 1600 Deskphone H.323 1.3 Maintenance
Release 4
Defect Number Description
SAGE16XX-612 Second BM is not upgrading when two BMs are connected during phone’s software upgrade to R1.3 SP1.
Details/Workaround
While upgrading the 1616 IP Deskphone to release 1.3200, if there are Button Modules
(BMs) attached to the 1616 IP Deskphone being upgraded, then the BMs will also be upgraded.
Note: You will need to carry out the following procedure, when updating phones with more than one Button Module attached.
When the BM software is being upgraded, each of the BM LEDs will turn ON and then
OFF in a sequential fashion. The sequence will stop after the 19th LED has turned ON as if the upgrade process has stopped. The phone will display the messaging, “Updating, Do not
Unplug”, while the upgrade is going on.
After the first Button Module has upgraded, the LEDs on the second Button Module may appear to start blinking RED and GREEN. But to force the second Button Module to upgrade, you must press a button on the FIRST Button
Copyright Avaya 2013 All rights reserved
Page 6 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
Defect Number Description Details/Workaround
Module to start the upgrade of the SECOND
Button Module. The SECOND Button Module upgrades with the same sequence of LEDs’ activities as the first Button Module.
If a phone is registered with an IP office, it may have a 3rd button module attached. In such case, the Third Button
Module must be disconnected before the phone is upgraded to the new software.
If this is not done, and the phone is updated before disconnecting the 3rd
Button Module from the phone, the
THIRD Button Module might become dysfunctional during the upgrade and it cannot be revived. The THIRD Button
Module has to be upgraded independently by connecting it to any other 1616 phone or by connecting it to the same phone as above, but only after the first two button modules have been disconnected.
It should be noted that Avaya doesn’t recommend connecting/disconnecting
Button Modules to/from the phone, while it is powered up.
Access the ‘A’ menu to check the version of
Button Module software, and to confirm if all the button modules have been upgraded. It should display: GBM32_B_1_1_0
SAGE16XX-749 Phone can’t get HTTPPORT from
DHCP or 46xxsetting.txt
SAGE16XX-787 Phone displays wrong call-park icon after parking call
Port 80 should be used on the server
NA
Copyright Avaya 2013 All rights reserved
Page 7 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
License Agreements
W3C(r) SOFTWARE NOTICE AND LICENSE
Copyright (c) 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institute National de
Recherche en Informatique et en Automatique, Keio University).
All Rights Reserved. http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make: The full text of this
NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code:
"Copyright (c) 2004 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de
Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE
OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders June NOT be used in advertising or publicity pertaining to the software without specific, written prior permission.
Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
________________________________________________________________________
Copyright (c) 1998, 1999, 2010 Thai Open Source Software Center Ltd
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
Copyright Avaya 2013 All rights reserved
Page 8 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
________________________________________________________________________
HTTP Server functionality is provided by the GoAhead WebServer 2.1,
Copyright (c) 2004 GoAhead Software, Inc. All Rights Reserved.
________________________________________________________________________
Secure sockets layer functionality is provided by OpenSSL 0.9.7g
Website: http://www.openssl.org/
Copyright notice:
Copyright(c) 1998-2005 The OpenSSL Project
Copyright(C) 1995-1998 Eric A. Young, Tim J. Hudson
All rights reserved.
License Name: BSD-style Open Source licenses
License URL: http://www.openssl.org/source/license.html
Licence version: NA
License text:
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the
OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact [email protected]
.
OpenSSL License
---------------
/* ====================================================================
* Copyright (c) 1998 2004 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
Copyright Avaya 2013 All rights reserved
Page 9 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributi ons in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning f eatures or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" an d "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* openssl [email protected].
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product in cludes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLI GENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software writ ten by Eric Young
* ([email protected]). This product includes software written by Tim
* Hudson ([email protected]).
*
*/
Original SSLeay License
-----------------------
/* Copyright (C) 1995 1998 Eric Young ([email protected])
* All rights reser ved.
*
* This package is an SSL implementation written
* by Eric Young ([email protected]).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non commercial use as long as
* the follow ing conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson ([email protected]).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
Copyright Avaya 2013 All rights reserved
Page 10 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary form s, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young ([email protected])"
* The word 'cryptographic' can be left out if the rouines from the library
* be ing used are not cryptographic related : ).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson ([email protected])"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIM ED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFI TS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU P ublic Licence.]
*/
© 2013 Avaya Inc. All Rights Reserved
Notice
While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.
Documentation disclaimer.
Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this
Documentation, and Avaya does not necessarily endorse the products, services, or information described or offered
Copyright Avaya 2013 All rights reserved
Page 11 of 12
Avaya 1600 Series IP Deskphone Release 1.3.4 Readme within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.
License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE TERMS
SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT http://support.avaya.com/LicenseInfo/ (“GENERAL LICENSE TERMS”). IF YOU DO NOT WISH TO BE BOUND BY
THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10)
DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. “Designated Processor” means a single stand-alone computing device.
“Server” means a Designated Processor that hosts a software application to be accessed by multiple users.
“Software” means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End
User, whether as stand-alone Products or pre-installed on Hardware. “Hardware” means the standard hardware
Products, originally sold by Avaya and ultimately utilized by End User.
License Type(s):
Designated System(s) License (DS). End User June install and use each copy of the Software on only one
Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya June require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.
Copyright
Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.
Third-party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (“Third Party Components”), which may contain terms that expand or limit rights to use certain portions of the Product (“Third Party Terms”). Information identifying Third Party Components and the Third Party
Terms that apply to them is available on Avaya web site at: http://support.avaya.com/ThirdPartyLicense/
Trademarks
Avaya, Avaya Aura, Communications Manager and the Avaya logo are registered trademarks and/or service marks of Avaya Inc. in the U.S. and certain other jurisdictions.
All other trademarks are the property of their respective owners.
Copyright Avaya 2013 All rights reserved
Page 12 of 12
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement