PCN1789Pu - Avaya Aura® CM 6.0.1 running on

Transcription

Product Correction Notice # 1789S
Product Correction Notice (PCN)
Issue Date:
Supplement 2 Date:
Archive Date:
PCN Number:
24-October-2011
9-August-2013
N/A
1789S
SECTION 1 - CUSTOMER NOTICE
Products
affected by this
PCN:
Description:
Avaya Aura® Communication Manager 6.0.1 running on System Platform R6.0.x equipped S8800 and
Common Servers HP® DL360 G7 at Department of Defense (DOD) and other installations that follow
the Security Technical Implementation Guides (STIGs) provided by the Defense Information Systems
Agency (DISA).
9 August 2013 – Supplement 2 introduces the following software updates for S8800 and HP® DL360
G7 Servers running System Platform R6.0.x and Communication Manager 6.0.1 Solution Templates at
DOD and other installations that follow the STIGs provided by DISA:
1. System Platform patch 6.0.3.9.3 (vsp-patch-6.0.3.9.3.noarch.rpm) for S8800 and HP® DL360
G7 Servers running System Platform R6.0.3 and Communication Manager 6.0.1 Solution
Templates.
2. Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-20554.tar.gz which only
applies to CM 6.0.1 software load R016x.00.1.510.1. This Service pack replaces 00.1.510.119391.tar.gz from Supplement 1 of this PCN.
23 April 2012 – Supplement 1 introduced the following software updates for S8800 and HP® DL360
G7 Servers running System Platform R6.0.x and Communication Manager 6.0.1 Solution Templates at
DOD and other installations that follow the STIGs provided by DISA:
1. System Platform patch 6.0.3.6.3 (vsp-patch-6.0.3.6.3.noarch.rpm) for S8800 and HP® DL360
G7 Servers running System Platform R6.0.3 and Communication Manager 6.0.1 Solution
Templates.
2. Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-19391.tar.gz which only applies
to CM 6.0.1 software load R016x.00.1.510.1. This Service pack replaced 00.1.510.119211.tar.gz from the original PCN.
24 October 2011 – The original PCN introduced the following software updates for S8800 and HP®
DL360 G7 Servers running System Platform R6.0.2 and Communication Manager 6.0.1 Solution
Templates at DOD and other installations that follow the STIGs provided by DISA:
1. System Platform R6.0.3 (vsp-6.0.3.0.3.iso) for S8800 and HP® DL360 G7 Servers running
System Platform R6.0.2 and Communication Manager 6.0.1 Solution Templates.
2. Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-19211.tar.gz which only
applies to CM 6.0.1 software load R016x.00.1.510.1.
Level of Class 2
Risk/Severity
Class 1=High
Class 2=Medium
Class 3=Low
PCN Template Rev Date: 08 June 2012
© 2012 Avaya Inc. All Rights Reserved.
Avaya – Proprietary & Confidential.
Use pursuant to the terms of signed agreements or Avaya
policy. All other trademarks are the property of their owners.
Page 1 of 9
All trademarks identified by the ® or TM are
registered trademarks or trademarks,
respectively, of Avaya Inc.
Is it required
that this PCN be
applied to my
system?
The risk if this
PCN
is not installed:
Is this PCN for
US customers,
non-US
customers, or
both?
Does applying
this PCN disrupt
my service
during
installation?
This PCN is not required but is highly recommended for S8800 and HP® DL360 G7 Servers running
System Platform R6.0.x and Communication Manager 6.0.1 Solution Templates at DOD and other
installations that follow the STIGs provided by DISA.
It is possible that Communication Manager service disruptions could occur, as well as some features not
working as expected.
This applies to both US and non-US customers.
This Communication Manager service pack will disrupt service in that it requires a reset 4 to take
effect. The System Platform update also disrupts service since the System Domain and Console
Domain are rebooted, and as a result all other virtual machines including Communication Manager
will be rebooted.
Installation of
this PCN
is required by:
Customer or Avaya Authorized Service Provider. These service packs and patches are customer
installable and remotely installable.
Release notes
and
workarounds
are located:
Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-20554.tar.gz is based on Communication
Manager 6.0.1 Service Pack #6 (00.1.510.1-19350) and contains additional enhancements and fixes
for DOD and other installations that follow the STIGs provided by DISA. These additional
enhancements and fixes are described in the tables below.
The Communication Manager 6.0.1 Service Pack #6 Release Notes can be obtained by performing the
following steps from a browser:
1.
Go to http://support.avaya.com then enter your Username and Password and click LOG IN
2.
Click DOWNLOADS & DOCUMENTS at the top of the page
3.
Begin to type Communication Manager in the Enter Your Product Here box and when
Avaya Aura® Communication Manager appears as a selection below, select it
4.
Select 6.0.x from the Choose Release pull down menu to the right
5.
If necessary click View documents
6.
The DOCUMENTS table and a Content Type filter are displayed.
Check the box for Release Notes & Software Update Notes in the Content filter. Available
documents are displayed.
7.
Click on the link for Avaya Aura® Communication Manager 6.0.1 SP6 Release Notes.
Additional enhancements above Communication Manager 6.0.1 Service Pack #6 which are included
in Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-20554.tar.gz:
Page 2 of 9
Enhancement
On Communication Manager with H.248 media gateways and
ephemeral caching enabled, traffic conditions caused
Communication Manager to attempt to allocate more VoIP
resources from H.248 media gateways than could be supported.
Once a H.248 media gateway reported that it no longer has VoIP
capacity, Communication Manager stopped attempting to use
the media gateway for VoIP. Communication Manager waited
three minutes before retrying VoIP allocation from the media
gateway. Now Communication Manager will retry VoIP
allocation as soon as an ephemeral has been cached or VoIP is
released from an active call.
The Administrator Accounts System Management Interface
Page now uses SHA512 to hash new passwords.
To improve robustness, SIP message parsing was enhanced to
continue parsing the v150 MR cpar fmtp optional tags that
appear prior to mandatory tags and to parse multiple cdsc
attributes.
To improve robustness, SIP message parsing was enhanced to
continue parsing the v150 MR fmtp rfc 2833 values even if the
values are not supported.
Set a three-second preemption tone timer for a preempted Xport analog station such that when the timer expires the MLPP
call preemption can continue its normal call sequence. Multiple
Level Precedence Preemption (MLPP) environment.
Previously, when a MLPP routine call was preempted at the farend server, the near-end calling party heard T120 tone (Fast
Busy tone); now the near-end calling party will hear the
Preemption tone.
A Security Violation Notification (SVN) was added through the
Station Security Code Violation Notification method when IP
stations attempt to login with an invalid password or extension.
Keyword
120201
120822
121266
121456
122039
122245
130807
Additional fixes over and above Communication Manager 6.0.1 Service Pack #6 which are included in
Communication Manager 6.0.1 DISA Service Pack 00.1.510.1-20554.tar.gz:
Problem
Call Hold, Three-way Calling, and Call Transfer operations were
denied for stations that were administered as Hotline in a
Multiple Level Precedence Preemption (MLPP) environment.
Communication Manager did not apply continuous Preemption
Tone to the preempted endpoint instrument (EI) until the EI
disconnected.
There was a memory leak problem when the system had the
MLPP feature enabled and the 96xx IP station was provisioned
with the DSCP (DiffServ Code Point) capability.
HistoryInfo header with port and transport failed to parse.
Display reinvite sent to far end switch resulted in talk path
Keyword
110046
110047
110760
110899
111261
Page 3 of 9
failure after unhold in SRTP SDES and shuffling off scenario.
Disabling and enabling media gateways for the Sync Over IP
feature occasionally created instability in the synchronization of
the media gateways.
Preemption tone was not applied when a hunt group was
involved in a trunk call.
Preemption failed when applied to a ringing hunt group call.
Preemption failed when applied to an analog station with a held
party if the held party went on-hook within 2 seconds.
The inter-gateway connection established to provide
synchronization between media gateways was torn down after a
link bounce.
The administration of an IPv6 address to a survivable server,
which was a network region's backup server, would cause a
system reset when the server went active.
There was no talk path when the far-end changed key after hold
on a call that was on TDM.
Blocked MLPP Call Preemption caused a system reset under
heavy trunk traffic.
The media gateway’s synchronization timing could sometimes
be set to VOIP when the Synchronization Over IP feature was
off. In addition, the CLI's synchronization administration
commands could not be run because the administration control
was in Communication Manager.
Any time a DS1C board was translated in the Center Stage fiber
arrangement, a system Warm start would occur as soon as an
attempt was made to insert the DS1C board. Multiple Warm
starts could lead to a Communication Manager reboot and
multiple reboots could cause the server to reboot.
Ringback tone was not removed even if the called party
answered the call.
Calls involving SIP trunks would have one-way talk path if the
SIP trunk used a network region in which the ip-codec-set had
only G.726 and SRTP encryption enabled.
On Communication Manager, MLPP was enabled and shuffling
was disabled. An H.323 phone called a SIP phone. After the SIP
phone user answered the call, two way talk path was observed
but ringback did not stop at the H.323 phone.
After an MLPP call preemption, the attendant console was not
able to return to idle when the release button was pressed.
An incoming PSTN call to an x-ported station could not be
answered on its bridged appearance.
Occasionally, Communication Manager reset.
Per RFC 4733 section 7.1.1, when sending telephone-event, no
blank space is allowed for event-parameters. Communication
Manager did not comply with this requirement.
Hold-Unhold on an SRTP Call across two Communication
Managers resulted in a one way talk path.
When Communication Manager was interoperating with an
111409
111991
111991
111991
111922
112779
112821
112885
113050
113164
113183
113195
113237
113242
120223
120844
122008
122054
122408/
Page 4 of 9
AS5300 and an MLPP call preemption was initiated by the
AS5300 to its own station, Communication Manager failed to
apply preemption tone to the local party.
SRTP calls with "Initial INVITE with SDP for secure calls" disabled
failed.
When the far-end server used UPDATE to refresh the call
session, the call between Communication Manager and
REDCOM was disconnected due to the call session not being
refreshed by Communication Manager.
Self-admin of EC500 failed if the first route in a route pattern
had an Facility Restriction Level (FRL) greater than the station
FRL.
On an Avaya Aura Communication Manager, V.150 secure calls
stopped working after several hours of traffic. A reboot was
required for secure calls to be successful again.
When the far-end server used UPDATE to refresh the call
session, the call between Communication Manager and
REDCOM was disconnected due to the call session not being
refreshed by Communication Manager.
Occasionally, Communication Manager rebooted when it
received a call from Business Communication Manager.
Per RFC 4091, the Media ID (MID) attribute of Alternative
Network Address Types (ANAT) would follow the "m" line
attribute. However, if the MID were formatted before the "m"
line in the SDP, although it is invalid, the Communication
Manager server would reset.
When a far-end station put a local station on hold/unhold or
transfer, the talk path between the stations was not restored
correctly
TDR AVA056
122583/
TDR AVA057
122990/
TDR AVA058
130523
130539
130548/
TDR AVA063
130671
130709
130869
The System Platform R6.0.3 release notes also describe fixes in System Platform patch 6.0.3.9.3 and
can be obtained by performing the following steps from a browser:
1.
2.
3.
Begin to type System Platform in the Enter Your Product Here box and when Avaya Aura®
System Platform appears as a selection below, select it
4.
5.
If necessary click View documents
6.
The DOCUMENTS table and a Content Type filter are displayed.
Check the box for Release Notes & Software Update Notes in the Content filter. Available
documents are displayed.
7.
Search for and click on Avaya Aura® System Platform R6.0.3 Release
Notes.
Page 5 of 9
What materials
are required to
implement this
PCN
(If PCN can be
customer
installed):
This PCN is being issued as a customer installable PCN. The specified Communication Manager and
System Platform updates are required. To obtain the updates refer to the How do I order this PCN
section below.
How do I order
this PCN
(If PCN can be
customer
installed):
The service packs and patches can be obtained by performing the following steps from a browser:
If unfamiliar with installing System Platform and Communication Manager service packs, the installation
instructions are required. To obtain the installation instructions please refer to the Finding the
installation instructions section of this PCN.
1.
2.
3.
Begin to type Communication Manager in the Enter Your Product Here box and when Avaya
Aura® Communication Manager appears as a selection below, select it
4.
5.
If necessary click View downloads
6.
In the DOWNLOADS table find and click on Avaya Aura® Communication Manager 6.0.1 DISA
Service Packs and Firmware and System Platform R6.0.x Software for DOD customers only,
6.0.x.
7.
Scroll down and click on the link titled 00.1.510.1-20554.tar.gz to download the Communication
Manager Service pack. Links for System Platform R6.0.3 (vsp-6.0.3.0.3.iso) and system platform
patch 6.0.3.9.3 (vsp- patch-6.0.3.9.3.noarch.rpm) are also provided.
The service pack can also be downloaded directly from the PLDS system at http://plds.avaya.com.
1.
Enter your login ID and password. You may have to search for and enter your company name
and/or accept the one time EULA to gain access to software downloads.
2.
Click View Downloads
3.
In the Search by Download tab enter CM000000194 in the Download Pub ID: search field to
access the Communication Manager Service pack download. Click the Download link to begin
the download
4.
The System Platform Service Pack (vsp-6.0.3.0.3.iso) can be downloaded in a similar fashion using
PLDS ID CM000000021. Use PLDS ID CM000000175 to download System Platform patch
6.0.3.9.3.
The MD5 sums are included in the Support and PLDS descriptions for these downloads.
Finding the
installation
instructions
(If PCN can be
customer
installed):
The instructions for installing Communication Manager software updates in a System Platform
environment can be obtained by performing the following steps from a browser:
1.
2.
3.
Begin to type Communication Manager in the Enter Your Product Here box and when Avaya
Aura® Communication Manager appears as a selection below, select it
Page 6 of 9
4.
5.
Select Documents content type and press Enter, or click View documents if the downloads table
is displayed
6.
The DOCUMENTS table and a Content Type filter are displayed. Check the box for Installation,
Migrations, Upgrades and Configurations in the Content Type filter. Available documents are
displayed.
7.
Click on the document titled Installing and Configuring Avaya Aura® Communication Manager
(03-603558).
See the Managing Patches section in Chapter 4.
8.
The instructions for upgrading System Platform can be obtained by performing the following steps
from a browser:
1.
2.
3.
Begin to type System Platform in the Enter Your Product Here box and when Avaya Aura®
System Platform appears as a selection below, select it
4.
5.
Select Documents content type and press Enter, or click View documents if the downloads
table is displayed
6.
The DOCUMENTS table and a Content Type filter are displayed. Check the box for
Installation, Migrations, Upgrades and Configurations in the Content Type filter. Available
documents are displayed
7.
Click on the document titled Upgrading Avaya Aura® System Platform
SECTION 1A – SOFTWARE SERVICE PACK INFORMATION
Note: Customers are required to backup their systems before applying the Service Pack.
How to verify
the installation
of the Service
Pack has been
successful:
Follow the steps in the document titled Upgrading Avaya Aura® System Platform to verify the System
Platform upgrade was successful.
There are several options to verify the Communication Manager Service Pack installation was successful:
1) Access the Server Management > Patch Management > Manage page on System Platform R6.0.3
which should show the status of the patch as “active.”
2) Or, to verify the Service Pack is successfully installed using the Communication Manager System
Management Interface web pages perform the following steps from a web browser:
Access the Communication Manager System Management Interface web pages by entering the
Server name or IP address in the browser Address box.
Login to the web pages.
Page 7 of 9
From the top navigation bar select Server (Maintenance) under the Administration pull-down
menu.
Then select the Software Version page under the Server links on the left hand menu.
Verify that under “UPDATES:” Service Pack “00.1.510.1-20554” shows “activated”.
3) Or using the Communication Manager Command Line Interface run the following bash command:
> update_show
This should show the status of Service Pack (Update ID)
“00.1.510.1-20554” as “activated”.
What you
should do if the
Service Pack
installation
fails?
Escalate to Avaya Global Support Services (GSS) or an Avaya authorized Business Partner.
How to remove
the Service Pack
if malfunction
of your system
occurs:
IMPORTANT: To avoid losing service, IP Softphone users should logoff thereby restoring their base
phone to service prior to deactivating a Communication Manager Service Pack.
On System Platform 6.0.3 access the Server Management > Patch Management > Manage page.
Click on the patch you want to remove then click Deactivate.
SECTION 1B – SECURITY INFORMATION
Are there any
security risks
involved?
Not Applicable
Avaya Security
Vulnerability
Classification:
Not Applicable
Mitigation:
Not Applicable
SECTION 1C – ENTITLEMENTS AND CONTACTS
Material
Coverage
Entitlements:
Avaya Customer
Service
Coverage
Entitlements:
There is no incremental charge for the material in this PCN. The software updates are available on
support.avaya.com and from plds.avaya.com.
Avaya is issuing this PCN as installable by the customer. If the customer requests Avaya to install this
PCN, it is considered a billable event as outlined in Section 4 (Software Updates and Product
Correction Notices) of the Avaya Service Agreement Supplement (Full Maintenance Coverage) unless
the customer has purchased an Avaya Services enhanced offer such as the Avaya Services Product
Correction Support offer.
Additionally, Avaya on-site support is not included. If on-site support is requested, Avaya will bill the
customer current Per Incident charges unless the customer has purchased an Avaya Services
enhanced offer such as the Avaya Services Product Correction Support offer.
Page 8 of 9
Customers under the following Avaya coverage:
-Full Coverage Service Contract*
-On-site Hardware Maintenance Contract*
Remote Installation
Current Per Incident Rates Apply
Remote or
Current Per Incident Rates Apply
On-site
Services Labor
Service contracts that include both labor and parts support – 24x7, 8x5.
Customers under the following Avaya coverage:
-Warranty
-Software Support
-Software Support Plus Upgrades
-Remote Only
-Parts Plus Remote
-Remote Hardware Support
-Remote Hardware Support w/ Advance Parts Replacement
Help-Line
Per Terms of Services Contract or coverage
Assistance
Remote or
Per Terms of Services Contract or coverage
On-site
Services Labor
Avaya Product Correction Notice Support Offer
The Avaya Product Correction Support Offer provides out-of-hours support for
remote and on-site technician installable PCNs, and Avaya installation for all
Avaya issued PCNs that are classified as “Customer-Installable”. Refer to the
PCN Offer or contact your Avaya Account Representative for complete details.
Avaya
Authorized
Partner
Service
Coverage
Entitlements:
Avaya Contacts:
For assistance
with this PCN
contact your
local or regional
Service group.
Avaya Authorized Partner
Avaya Authorized Partners are responsible for the implementation of this
PCN on behalf of their customers.
Contact Avaya Support
Page 9 of 9

PCN1789Pu - Avaya Aura® CM 6.0.1 running on

Transcription

Documents pareils

Fact sheet partnership with Avaya

BCMRD Release Notes

Application Notes for Configuring Dasan Electron Headsets from

Automating Campus Networks

Product/Process Change Notice - PCN 13_0277 Rev. -

Configuring Secrets Management on the Avaya

Siemens Hicom 300 /300 E, HiPath 4000 (EMEA)

End of Sale Notice

Application Notes for Tango Networks Abrazo 5.3 with Avaya

Wireless Linear CCD Barcode Scanner

System Requirements - 2009b

Configuration Note 6029 Ver. A (11/05) Siemens