PCN Template Rev .041213 Page 1 of 12

Product Correction Notice #1924S
Product Correction Notice (PCN)
Issue Date: 18-October-2013

Supplement 2 Date: 2-December-2014
Archive Date: NA
PCN Number: 1924S
SECTION 1 - CUSTOMER NOTICE
Products Avaya Aura® Communication Manager 6.3 Solution Templates running on System Platform R6.3
affected by this equipped S8300D, S8510, S8800 and Common Servers (HP® DL360 G7 and Dell® R610 Servers, plus the
PCN: newly released HP® DL360 G8, and Dell® R620 Servers) at Department of Defense (DoD) and other
installations that follow the Security Technical Implementation Guides (STIGs) provided by the Defense
Information Systems Agency (DISA).
Avaya Aura® Communication Manager 6.3 Simplex vAppliance and Duplex vAppliance running on
VMware® vSphere® ESXi 5.0/5.1/5.5 infrastructures at Department of Defense (DoD) and other
installations that follow the Security Technical Implementation Guides (STIGs) provided by the Defense
Information Systems Agency (DISA).
Description: 2 December 2014 – Supplement 2 of this PCN introduces the following System Platform (R6.3.5) update
to Communication Manager 6.3.6.100 (03.0.124.0-21862.tar).
 System Platform R6.3.5 (vsp-patch-6.3.5.01003.0.noarch.rpm). This patch is applied on top of
System Platform 6.3.0.0.18002 (vsp-6.3.0.0.18002.iso), which is the original System Platform
version for Communication Manager 6.3. Communication Manager 6.3.6.100 (21862) uses
System Platform 6.3.5 (PLDS ID CM000000384). See the System Platform R6.3.5 Release Notes
for more information.
 Communication Manager 6.3.6.100 (03.0.124.0-21862.tar). See Supplement 1 description
(dated 14 October) below.
14 October 2014 – Supplement 1 of this PCN introduces the following update.

 Communication Manager 6.3.6.100 (03.0.124.0-21862.tar). This service pack only applies to
CM6.3 load R016x.03.0.124.0 on S8300D, S8800 and HP® DL350 G7 servers at the DoD and
other installations that follow the STIGs provided by DISA. This is not applicable to any other
servers, software loads, or releases of Communication Manager. Service Pack 6.3.6.100 delivers
software fixes for Communication Manager 6.3.6 as part of Avaya Aura® 6.2 Feature Pack 4. See
the Communication Manager 6.3.6 Release Notes for more information.
 System Platform R6.3.4 (vsp-patch-6.3.4.08011.0.noarch.rpm). This patch was applied on top
of System Platform 6.3.0.0.18002 (vsp-6.3.0.0.18002.iso), which is the original System Platform
version for Communication Manager 6.3. Communication Manager 6.3.6.100 (21862) used
System Platform 6.3.4. See the System Platform R6.3.4 Release Notes for more information.
18 October 2013 – The original PCN introduced Communication Manager 6.3.1.1 (03.0.124.0-
20983.tar). This service pack only applied to CM6.3 load R016x.03.0.124.0 running System Platform
6.3.0.0.18002 (vsp.3.0.0.18002.iso) on S8300D, S8800 and HP® DL350 G7 servers at the DoD and other
installations that follow the STIGs provided by DISA. This is not applicable to any other servers, software
loads, or releases of Communication Manager.
PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 1 of 12

© 2013 Avaya Inc. All Rights Reserved. Use pursuant to the terms of signed agreements or Avaya All trademarks identified by the ® or TM are
policy. All other trademarks are the property of their owners . registered trademarks or trademarks,
respectively, of Avaya Inc.
Level of Class 2
Risk/Severity
Class 1=High
Class
2=Medium
Class 3=Low
Is it required This PCN is not required but is highly recommended for S8300D, S8510, S8800, HP DL360 G7 and Dell
that this PCN R610 Servers running System Platform R6.3 and any of the Communication Manager 6.3 Solution
be applied to Templates at the DoD and other installations that follow the STIGs provided by DISA.
my system?
This PCN is required for HP DL360 G8 and Dell R620 Servers running System Platform R6.3.5 and
Communication Manager 6.3.6.100.
This PCN is also recommended for the Communication Manager 6.3 Simplex VAppliance and Duplex
VAppliance running on VMware® vSphereTM ESXi 5.0/5.1/5.5 infrastructures at the DoD and other
installations that follow the STIGs provided by DISA.
The risk if this It is possible that Communication Manager service disruptions could occur, as well as some features not
PCN working as expected.
is not installed:
Is this PCN for This PCN applies to both US and non-US customers.
US customers,
non-US
customers, or
both?
Does applying This Communication Manager service pack will disrupt service in that it requires a reset 4 to take effect.
this PCN disrupt Duplicated servers can use the call preserving service pack installation procedure described in the
my service installation instructions.
during
installation?
Installation of Customer or Avaya Authorized Service Provider. This service pack is customer installable and remotely
this PCN installable.
is required by:
Release notes The Communication Manager 6.3.6 (Service Pack 6) release notes contain the specific software updates
and included in the service pack and can be obtained by performing the following steps from a browser:
workarounds
1. Go to http://support.avaya.com then enter your Username and Password and click LOG IN.
are located:
2. Click 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.3.x from the Choose Release pull down menu to the right.
5. Scroll down (if necessary) and check the box for Release Notes & Software Update Notes.

6. Click ENTER. Available documents are displayed.

7. Click on the document titled Avaya Aura® Communication Manager 6.3.6.0 Release Notes.
The System Platform R6.3.5 release notes contain the specific software updates included in this release
and can be obtained by performing the following steps from a browser:
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.
5. Scroll down (if necessary) and check the box for Release Notes & Software Update Notes.
7. Click on the document titled Avaya Aura® System Platform R6.3.5 Release Notes.
The Communication Manager 6.3.6.100 (03.0.123.0-21862.tar) service pack has no release notes or
workarounds, but the problems resolved are described in the following table.
Problem Keyword
When periodic maintenance ran for a SIP signaling group which
had all trunk members active on calls then this SIP signaling 140589
group would be put in far-end-bypass mode and out-of-service.
An erroneous attendant return call occurs while the ATQA
(Attendant Queue Announcement) is connected to a calling 140592
party which goes onhook before the ATQA is completed.
MLPP call preemption will fail if the to be preempted party has a
140619
call waiting call active during the preemption attempt.
Provides fix for intermittent sftp/scp timeout when using web
140654
backup in FIPS mode.
This software modification is to resolve two issues:
(1) call preemption will fail if the to be preempted call involves
an attendant party. 140655
(2) call preemption to a station with bridged call appearance will
cause the bridging station lock-up.
While processing MLPP SIP calls, CM encountered an internal
error that incorrectly managed the system memory associated 140662
with the call, causing a restart.
Occasionally, while processing SRTP calls, CM encountered a
rare internal error that incorrectly managed the system memory 140683
associated with the call, causing a restart.
While processing MLPP SIP calls, CM encountered an internal
error due to overload condition that incorrectly managed the 140719
system memory associated with the call, causing a restart.
A problem with customer installed certificates was hidden by
the use of software embedded certificates. The use of software 140773
embedded certificates is now removed.

In a call center configuration with more than 1000 hunt group

members translation corruption may occur on small or medium 140779
survivable servers.
There was some confusion with the setting of 100% blockage
precedence calls. Originally calls were blocked close to 100% but
some were allowed to continue. However, this arrangement
140808
seems confusing so now if the setting is 100% all calls are
blocked for that precedence entry destination, if the possible
route pattern entry is a DSN SIP trunk type.
No new inter CM calls could be made until one of the existing
calls were dropped when inter CM trunk was SIP with shuffling 140820
enabled.
Incorrect warning message was displayed on the SAT when a SIP
140854
trunk group contained 255 members and a budget of 255.
After customer added a "Dialed String” with a length greater
than 8 on the PRECEDENCE ROUTING DIGIT ANALYSIS TABLE
form, the next time the customer tried to administer the form 140856
the customer saw "Error encountered, can't complete request;
check errors before retrying."
CM did not return cause value 46 for incoming ISDN PRI call
140861
when call is blocked due to insufficient precedence level.
When an equal MLPP precedence level is forwarded to a busy
CFWD destination the calling party did not terminate to a Block 140863
Precedence Announcement.
Previously, a local held call or an incoming MF2/6 trunk call will
not get preemption tone when the call is preempted by a higher 140878
precedence call. Now, preemption tone will be properly applied.
Previously, when an IP EI makes outbound AS-SIP trunk call the
audio PHB value (administered in the ip-network-region) is used
as the DSCP value. Now, the correct DSCP value (administered in 140917
the MLPP system parameters) will be sent for the dialed MLPP
precedence call.
Busy not equipped Announcement is connected when far end
returns 486 (Busy Here) response code. Instead, Block 140918
Precedence Announcement should be connected.
In a MLPP call flow, call transfer from local CM to Cisco fails.
140919
Need to Add Resource Priority Header to REFER message.
If Enable Failover Event Package Subscription was turned on for
SIP signaling group number 1, the system locked up and would 140933
eventually restart.
In JITC configurations, outgoing SUBSCRIBE messages for the
Failover event were not being routed properly through the 140961
border controller.
When an ISDN CONNECT message is sent to far-end sever, if an
incoming ISDN PRI trunk is to be tandemed out to an automatic
141214
dial-out CO loop-start trunk, upon the CO trunk group's answer
supervision timer expires.
Service Pack(6.3.6.100) will include the fixes below from previous Communication Manager 6.3 service

packs that applied to the Department of Defense (DoD) and other installations that follow the Security
Technical Implementation Guides (STIGs) provided by the Defense Information Systems Agency (DISA).
The Communication Manager 6.3.1.1 (03.0.123.0-20983.tar) has no release notes or workarounds, but
the problem resolved is described in the following table.
Problem Keyword
When a caller on a far end server (Redcom) went on hold and
then picked up this call from hold, there was a one-way talk 131935
path.
What materials This PCN is being issued as a customer installable PCN. The specified Communication Manager updates
are required to are required. To obtain the update refer to the How do I order this PCN section of this PCN.
implement this
PCN If unfamiliar with installing Communication Manager service packs, the installation instructions are
(If PCN can be required. To obtain the installation instructions please refer to the Finding the installation instructions
customer section of this PCN.
installed):
How do I order The software updates can be downloaded by performing the following steps from a browser:
this PCN
(If PCN can be
customer 2. Click DOWNLOADS at the top of the page.
installed):
3. Begin to type Communication Manager in the Enter Product Name box and when Avaya Aura®
5. Scroll down if necessary and click on Avaya Aura® Communication Manager 6.3.6.100 DISA Service
Packs and Firmware and System Platform R6.3...
6. Scroll down the page to find the following download links 03.0.124.0-21862.tar, vsp-patch-
6.3.5.01003.0.noarch.rpm and vsp-6.3.0.0.18002.iso (if required). These links will take you to the
PLDS system with the Download pub ID: already entered.
The software updates 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 CM000000370 in the Download Pub ID: search field to access
Communication Manager 6.3.6.100 (21862). Click the Download link to begin the download.
4. The System Platform software can be downloaded in a similar fashion using PLDS ID CM000000384
for vsp-patch-6.3.5.01003.0.noarch.rpm, and CM000000354 for vsp-6.3.0.0.18002.iso.
PLDS Hints:
1. In the PLDS View Downloads section under the Suggested Downloads tab, select Communication

Manager in the Product Line search field to display frequently downloaded Communication
Manager software, including recent service packs and updates.
2. Previous Communication Manager 6.3 Service Packs and System Platform updates are also available
on PLDS. In the PLDS View Downloads section under the Search by Download tab, select
Communication Manager in the Application search field and Version 6.3 to display all available
Communication Manager 6.3 software downloads.
System Platform R6.3.0.0.18002 is also orderable on a DVD (Material Code 700505971)
The MD5 sums for this download is:

CM 6.3.6.100 (03.0.124.0-21862.tar): dd4961a13913c38554909cf6b49e1d29
CM 6.3.1.1 (03.0.124.0-20983.tar): 2067bd09d8954c7c691d6b09fa1ef333
SP R6.3.0 (vsp-6.3.0.0.18002.iso): e78359b9fb5f4ad3ce81b299130b69d0
SP R6.3.4 (vsp-patch-6.3.4.08011.0.noarch.rpm): 11f1ffd14a3077ca65d9ad6a2bb80399
SP R6.3.5 (vsp-patch-6.3.5.01003.0.noarch.rpm): 6f1473a022616492dc50419ea7193872
Finding the The instructions for installing Communication Manager software updates in a System Platform
installation environment can be obtained by performing the following steps from a browser:
instructions
(If PCN can be
customer 2. Click DOCUMENTS at the top of the page.
installed):
5. Check the box for Installation, Migrations, Upgrades and Configurations.
7. Scroll down (if necessary) and click on the document titled Deploying Avaya Aura® Communication
Manager on System Platform.
8. See Chapter 10: Managing Patches.
The instructions for patching and upgrading System Platform can be obtained by performing the
following steps from a browser:
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.
7. Click on the document titled Upgrading Avaya Aura® System Platform Release 6.3.5.

The instructions for installing Communication Manager software updates in a VMware® Virtualized
Environment can be obtained by performing the following steps from a browser:
7. Scroll down (if necessary) and click on the document titled Deploying Avaya Aura® Communication
Manager on VMware® in Virtualized Environment.
8. See Appendix D: Upgrading Communication Manager Open Virtual Application.
SECTION 1A – SOFTWARE SERVICE PACK INFORMATION
Note: Customers are required to backup their systems before applying the Service Pack.
How to verify To verify the Communication Manager service pack installation was successful access the Server
the installation Management > Patch Management > Manage page on the System Platform Web Console which should
of the Service show the status of the service pack or patch as “active.”
Pack has been
successful: For steps to verify that System Platform was successfully upgraded refer to the document titled
Upgrading Avaya Aura® System Platform Release 6.3.5 referenced above.
For VMware® Virtualized Environments you can verify that the Service Pack is activated using the
Communication Manager System Management Interface from the Administration > Server
(Maintenance) >Server Upgrades > Manage Updates page.
What you Escalate to Avaya Global Support Services (GSS) or an Avaya authorized Business Partner.
should do if the
Service Pack
installation
fails?
How to remove IMPORTANT: To avoid losing service, IP Softphone users should logoff thereby restoring their base
the Service phone to service before removing a Communication Manager service pack.
Pack
if malfunction To remove the Communication Manager service pack:
of 1) On System Platform click Server Management > Patch Management.
your system 2) Click Manage.
occurs: The Patch List page displays the list of patches and the current status of the patches.
3) On the Patch List page, click on the patch that you want to remove.
4) Click Remove.
For steps to roll back the System Platform upgrade refer to the document titled Upgrading Avaya Aura®

System Platform Release 6.3.5 referenced above.
For VMware® Virtualized Environments deactivate the service pack using the Communication Manager
System Management Interface from the Administration > Server (Maintenance) >Server Upgrades >
Manage Updates page.
SECTION 1B – SECURITY INFORMATION
Are there any No.

security risks
involved?
Avaya Security N/A

Vulnerability
Classification:
Mitigation: N/A
SECTION 1C – ENTITLEMENTS AND CONTACTS
Material This Communication Manager 6.3 service pack is available free of charge to customers with a valid
Coverage support contract for Communication Manager 6.x. However, starting with Release 6.2 the Service Pack
Entitlements: and Dot Release Guardian feature controls customer entitlement to these Communication Manager
software updates as described below.
Communication Manager 6.2 introduced the Service Pack and Dot Release Guardian feature. This
feature determines customer software entitlement by comparing the software Publication Date
embedded in the Communication Manager 6.2 (or greater) dot release or service pack software to the
Support End Date (SED) in the Product Licensing and Delivery System (PLDS) generated license. The SED
is set as the later of the warranty expiration date or the support contract expiration date.
-If the service pack/dot release has a Publication Date on or before the SED, the service
pack/dot release is allowed.
-If the service pack/dot release has a Publication Date after the SED, the service pack/dot
release is not allowed.
Attempting to install a service pack that is not allowed will fail with an error message indicating that the
Publication Date is after the SED in the license file.
Starting on August 20, 2011 all Communication Manager 6.x license files generated in PLDS include the
SED. Installing service packs on Communication Manager 6.2 (or greater) systems using these licenses
will be subject to the Guardian entitlement check.
Communication Manager 6.x license files generated before August 20, 2011 do not have the SED and
systems using these licenses can upgrade to Communication Manager 6.2 (or greater) without the
Guardian entitlement check. Installing service packs on Communication Manager 6.2 (or greater)
systems using these licenses will not be subject to the Guardian entitlement check.
Avaya recommends generating and installing a license file with SED before upgrading to Communication
Manager 6.3 or installing CM 6.3 service packs. This will help insure the SED supports the

Communication Manager 6.3.6.100 Service Pack (21862) Publication Date of 01 June 2014.
For more information on Service Pack and Dot Release Guardian refer to the document titled Deploying
Avaya Aura® Communication Manager on System Platform.

Avaya Avaya is issuing this PCN as installable by the customer. If the customer requests Avaya to install this
Customer PCN, it is considered a billable event as outlined in Section 4 (Software Updates and Product Correction
Service Notices) of the Avaya Service Agreement Supplement (Full Maintenance Coverage) unless the customer
Coverage has purchased an Avaya Services enhanced offer such as the Avaya Services Product Correction Support
Entitlements: 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.
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 Avaya Authorized Partner

Authorized Avaya Authorized Partners are responsible for the implementation of this
Partner PCN on behalf of their customers.
Service
Coverage
Entitlements:

Who to contact If you require further information or assistance please contact your Authorized Service Provider, or visit
for more support.avaya.com. There you can access more product information, chat with an Agent, or open an
information: online Service Request. Support is provided per your warranty or service contract terms unless
otherwise specified in the Avaya support Terms of Use.

SECTION 2 - Avaya Authorized Partner Notice
Avaya Authorized Partners – Please review SECTION 1 in addition to this section. Contact the appropriate Avaya Support
Organization with questions you may have concerning this PCN Notice.
Required Please note required materials in section 1.

Materials:
Is an RFA A new PLDS license is not required for this PCN. If upgrading Communication Manager from a release
License prior to CM 6.0 coincident with implementing this PCN, a new PLDS license file is required for main
Required? servers.
(New or
Existing) However, starting with Communication Manager 6.2 the Guardian feature controls customer
entitlement to Service Packs and Dot Releases as described in Material Coverage Entitlements: in
Section 1 of this PCN.
Provisioning The service pack, release notes and instructions are downloadable. Refer to Section 1 of this PCN.
Instructions:
Coordination Be sure to check for Communication Manager Messaging, Session Manager and Utility Services PCNs
with Other PCN that may also apply. In addition, it is recommended branch gateway firmware be upgraded to 36.7.1.
(If Applicable): Note that this firmware load is only for the DoD and other installations that follow the STIGs provided by
DISA and is not intended for general use.
Scheduling and Any service pack installation should be coordinated and scheduled, even if it is not service disrupting.
Coordination: This particular service pack is customer installable, remotely installable, and does disrupt service.
Installation The Communication Manager service pack typically takes 15 minutes for a simplex server and 30
Time: minutes for duplicated servers. Additional time is required for the System Platform update if required.
Technical The formal Technical Escalation Process is to be used for technical questions pertaining to the
Escalation: application of this PCN.
U.S. Direct: Contact the Avaya GSS @ 1-800-248-1234 for assistance. Caller must provide Avaya
employee number or contractor’s SS number. Also refer to the Maintenance Escalation Procedure.
U.S. Indirect: Contact the Avaya GSS @ 1-877-295-0099 for assistance. Also refer to the Maintenance
Escalation Procedure.
NON-U.S.: Customers or Avaya Authorized Partners are to contact their Regional Support Center.
Normal Escalation procedures apply.
Material Return Not Applicable.

Instructions:


PCN Template Rev .041213 Page 1 of 12

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCN Template Rev .041213 Page 1 of 12

Uploaded by

Copyright:

Available Formats

Product Correction Notice #1924S

Product Correction Notice (PCN)

Issue Date: 18-October-2013

SECTION 1 - CUSTOMER NOTICE

14 October 2014 – Supplement 1 of this PCN introduces the following update.

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 1 of 12

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 2 of 12

6. Click ENTER. Available documents are displayed.

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 3 of 12

In a call center configuration with more than 1000 hunt group

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 4 of 12

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 5 of 12

The MD5 sums for this download is:

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 6 of 12

SECTION 1A – SOFTWARE SERVICE PACK INFORMATION

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 7 of 12

System Platform Release 6.3.5 referenced above.

SECTION 1B – SECURITY INFORMATION

Are there any No.

Avaya Security N/A

SECTION 1C – ENTITLEMENTS AND CONTACTS

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 8 of 12

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 9 of 12

Customers under the following Avaya coverage:

Customers under the following Avaya coverage:

Avaya Product Correction Notice Support Offer

Avaya Avaya Authorized Partner

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 10 of 12

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 11 of 12

SECTION 2 - Avaya Authorized Partner Notice

Required Please note required materials in section 1.

Material Return Not Applicable.

PCN Template Rev .041213 Avaya – Proprietary & Confidential. Page 12 of 12

You might also like