Avaya 1600 Series H323 3 Service Pack 1 Users Manual H.323 Release 1.3100 Readme

2015-06-01

: Avaya Avaya-1600-Series-H323-3-Service-Pack-1-Users-Manual-736929 avaya-1600-series-h323-3-service-pack-1-users-manual-736929 avaya pdf

Open the PDF directly: View PDF PDF.
Page Count: 9

DownloadAvaya Avaya-1600-Series-H323-3-Service-Pack-1-Users-Manual- H.323 Release 1.3100 Readme  Avaya-1600-series-h323-3-service-pack-1-users-manual
Open PDF In BrowserView PDF
Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

Avaya One-X® Deskphone Value Edition Software Release 1.3100
Read me
This file is the Readme for the Avaya One-X® Deskphone Value Edition Software Release
1.3100 (H.323 1.3 Service Pack 1). This file describes the contents of the October 2011
Service Pack software distribution package. It also includes Product Advisements related to
known issues with this Software Release.
Avaya One-X® Deskphone H.323 Release 1.3100 software is supported on the 1603,
1603C, 1603-I, 1603SW, 1603SW-I, 1608, 1608-I, 1616, and 1616-I Deskphones IP
Deskphones only, and when used with Avaya Aura® Communication Manager. It will not
load or operate on any other models. This Release 1.3100 software is not yet supported
with IP Office or B5800 Branch Gateway platforms.
This software has not been introduced as the default load for the IP Deskphones shipped
from Avaya. This service pack supersedes all previous Avaya One-X® Deskphone Value
Edition 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 your 1600 Series IP Deskphones:
1.

Unzip the zip file in the root directory of your HTTP server.

2.

Make any adjustments required by your environment to your 46xxsettings.txt
file.

3.

Reset your Avaya 1600 Series IP Deskphone.0.

Avaya Aura ® Communication Manager (CM) Compatibility
Although the 1600 Series IP Deskphones are supported on Avaya Aura® Communication
Manager 3.1.4 and higher, Avaya recommends using the latest Communication Manager
release with these models of IP Deskphones. 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 for to support the following features:
Native support of 1600 Series IP Deskphones
CM releases prior to 5.2 do not provide native support for the 1600 Series IP Deskphones.
It is recommended 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 refer to the H.323 configuration section in the CM Administration Guide
which can be downloaded from http://support.avaya.com.

Copyright Avaya 2011 All rights reserved

Page 1 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

Avaya IP Office (IPO) Compatibility
Note that the H.323 1.3100 software is not included in the latest IP Office Service
Pack.
The 1600 Series IP Deskphones are supported on IP Office 4.2 and higher.
IPO 6.0 is the minimum version required for to support the following features:
Graphical displays on the “-I” versions of 1600 Series IP Deskphones
IPO 5.0 is the minimum version required to support the following features:
Call Log, Redial, Contacts, and Text Entry
Please consult the IP Office Technical Bulletin(s) for details on specific IP Office software
compatibility.

Avaya B5800 Branch Gateway (B5800) Compatibility
Note that the H.323 1.3100 software is not included in the latest B5800 Service
Pack.
The 1600 Series IP Deskphones are supported on B5800 6.1 and higher.
Please consult the B5800 Release Note(s) for details on specific B5800 software
compatibility.

H.323 1.3100 Package Content
The H.323 R1.3100 package contains all the files necessary to upgrade new or previously
installed 1600 Series IP Deskphones to H.323 R1.3100.
The following files are included in this package:
1603, 1603-I, 1603SW, 1603SW-I
o
Boot Code
o
Application Code

hb1603ua1_3100.bin
ha1603ua1_3100.bin

1608, 1608-I
o
o

Boot Code
Application Code

hb1608ua1_3100.bin
ha1608ua1_3100.bin

1616, 1616-I
o
o

Boot Code
Application Code

hb1616ua1_3100.bin
ha1616ua1_3100.bin

Button Module

GBM32_B_1_1_0.hex

16xxupgrade.txt – To upgrade to R1.3100, 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.3100. If you have other phones that are using this script for other software
upgrades and installations, please note the changes between the scripts. Make a
backup copy of your current upgrade script, and incorporate the binary name
changes for release R1.3100 into your 16xxupgrade.txt file.
Copyright Avaya 2011 All rights reserved

Page 2 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

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 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. If you are going to modify
your 46xxsettings.txt file, make a backup copy of that file, and incorporate the feature
changes.

Issues resolved with Avaya One-X® Deskphone H.323 Software
Release 1.3100
Patches incorporated in this release include:
Patch ID

MR Number

MR Description

1.257
1.2203

TRAC10702
TRAC12658

1.303

TRAC15127
TRAC15822
TRAC15823
TRAC15459

16xx phone reboots after changing setup in menu
Outgoing calls logs of the 16xx phone does not show the
called party number when dialed from CTI application
16xx confirms FURQ with wrong requestNum

1.304

When PC is disconnected from a 1608 phone that is
connected to 802.1x switch, phone requests 802.1x login
Copyright Avaya 2011 All rights reserved

Page 3 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

1.305

TRAC15203

1608 REDIAL list shows only 5 digit number if the number
length is more than 5

1.307

TRAC15508

Combo patch R1.252a with R1.3

1.311

TRAC15914

Combo R1.2203a + 1.307a with R1.3

1.312

TRAC16033

Need combo patch of 1.2009 on top of 1.3

1.313

TRAC16037

Call timer not getting displayed when conferencing into a
VDN

1.314

TRAC16173
TRAC16189

16xx add +Contact from Call Log truncating Name to 14
characters, 1603-i phone truncates calling number

1.2201c

TRAC 11870

Release button not working in LSP failover scenario for 16xx

1.323

TRAC18086

1616 BM32 user buttons are not functioning correctly when
IPO is restarted

R1.1006

IPT00047623

16xx phones reply to IP 192.168.1.10 ARP request during
bootup

1.322B

TRAC18057

Periodic transmit noise heard from 1616i headset call with
1.300b

1.316

TRAC 16276
TRAC19648

Native name feature doesn't work with 16xx phones
Phone displays the native name in English for Arabic
language

Unresolved issues in Avaya One-X® Deskphone H.323 Software
Release 1.3100
The following is a list of advisements associated with H.323 Software Release 1.3100.
Some advisements remain form previous releases of software, whereas other
advisements reflect newly observed or changed behavior with this release.
MR Number

MR Description

TRAC13101
SAGE16XX439

1616i type IP phones have a delay of 2sec to send the RTP to the right
port.

TRAC10034
SAGE16XX301

Japanese user-defined can‟t be displayed on full width white backlight
1608-I and 1616-I displays.

Copyright Avaya 2011 All rights reserved

Page 4 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

1616 IP Deskphones on different customer sites are facing randomly
audio static noise. Currently under review, a test patch software load
is available that includes a recovery mechanism and helps to gather
more information from customer sites experiencing this issue.
SAGE16XX –
531

Call Log shows as unavailable for name and number field conference
call on second dropped phone

TRAC10508
SAGE16xx400

Phone is stuck on booting up and requesting 16xxupgrade.txt via
HTTPS. This happens with the IIS http server when the certificate has
not been installed.

TRAC9840
SAGE16XX265

Under certain conditions, some login-related error messages may
appear in English, instead of the system language (LANGSYS).

TRAC10035
SAGE16XX302

Bad typeface for UNICODE char, FF9D.

TRAC10183
SAGE16XX343

“#next” string getting truncated when first string length is more than
10 characters in some languages on the 1603 models.

TRAC10180
SAGE16XX340

Button Rollover- The second button is reported on screen

TRAC10277
SAGE16XX355

In certain cases, 802.1X port authentication does not work properly.
The work-around is to "force authorize" the port.

Copyright Avaya 2011 All rights reserved

Page 5 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

SAGE16XX539

Upgrading 1600 Series IP Deskphones with attached Button Modules
While upgrading the IP Deskphone to release 1.3100, if there are
Button Modules (BMs) attached to the 1600 Series IP Deskphone being
upgraded, then the BMs will also be upgraded. However, please note
the following advisements when updating phones with more than one
Button Module attached.
When the BM software is being upgraded, each of the BM LED‟s will
turn ON and then OFF in a sequential fashion, and will stop after the
19th LED has turned ON, and it will appear 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 LED‟s on the second
module may appear to start blinking RED and GREEN, but to force the
second button module to upgrade, the user will need to press a button
on the FIRST Button Module to start the upgrade of the SECOND
button module. When the SECOND Button Module upgrades, you will
see it go through a similar pattern of LED‟s being turned ON and OFF,
as was the case with the first Button Module.
If there is a 3rd button module attached – and this is only
possible for configurations in which the phone is registered to
an IP Office, before upgrading a phone to which THREE Button
Modules are attached, it is of the utmost importance that the
customer should disconnect the 3rd Button Module from the
phone. If this is not done, and the phone is updated before
disconnecting the 3rd Button Module from the phone, the
THIRD Button Module becomes dysfunctional during the
upgrade and 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.
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

The following is a list of known issues caused by Communications Manager.
MR Number

MR Description

TRAC 9634
SAGE16XX222

Incorrect call log entry in call log, when participant drops the call from
the Conference.

TRAC 9652

16xx phones show 'Unavailable' in call log when call is reverted to the
phone after transferring the call.

Copyright Avaya 2011 All rights reserved

Page 6 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

TRAC 9684
SAGE16XX225

Add softkey is working as Hold hard key when call is in BrdgConference state.

TRAC 10034
SAGE16XX301

Japanese user-defined can't be displayed, on white backlight 1608-I
and 1616-I.

License Agreements
W3C(r) SOFTWARE NOTICE AND LICENSE
Copyright (c) 1994-2002 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/
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 Avaya 2011 All rights reserved

Page 7 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

Copyright (c) 1998, 1999, 2110 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:
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.
________________________________________________________________________

© 2011 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
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.
Copyright Avaya 2011 All rights reserved

Page 8 of 9

Avaya One-X® Deskphone Value Edition Release 1.3100 Readme

“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 2011 All rights reserved

Page 9 of 9



Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 9
Language                        : en-US
Tagged PDF                      : Yes
Title                           : H.323 Release 1.3100 Readme
Author                          : Avaya
Keywords                        : 1600, Series, Software, Release, 1.3, Service, Pack, 1
Creator                         : Microsoft® Office Word 2007
Create Date                     : 2011:10:14 14:18:45
Modify Date                     : 2011:10:14 14:18:45
Producer                        : Microsoft® Office Word 2007
EXIF Metadata provided by EXIF.tools

Navigation menu