ASBCE_63SP2_ReleaseNotes

1 2015 Avaya Inc. All Rights Reserved.

Avaya Session Border Controller for Enterprise 6.3 SP2 Release Notes

Release 6.3 SP2 Issue 1

April 2015


2015 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 might 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. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. 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 the time and we have no control over the availability of the linked pages. Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: http://support.avaya.com 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 WEB SITE 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)

Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.


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 the Avaya Support Web site: http://support.avaya.com/ThirdPartyLicense/ Preventing toll fraud

"Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention

If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com Trademarks

Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://support.avaya.com Avaya support

Avaya provides a telephone number for you to use to report problems or to ask questions about your

product. The support telephone number is 1-800-242-2121 in the United States. For additional support

telephone numbers, see the Avaya Support Web site: http://support.avaya.com


Table of Contents Overview ................................................................................................................................................. 5

Documentation ........................................................................................................................................ 5

New Features and Enhancements ........................................................................................................... 5

Overlapped Address Spaces and Non-Unique SBC Signaling/Media Addresses ................................. 5

VMware Enhancements ...................................................................................................................... 7

OVA .................................................................................................................................................. 7

Performance Enhancement ............................................................................................................. 8

List of Issues Fixed ................................................................................................................................... 8

Deployment Instructions ....................................................................................................................... 10

Installation ......................................................................................................................................... 10

Upgrade ............................................................................................................................................. 10

Upgrading Primary EMS .................................................................................................................... 10

Upgrading Secondary EMS ................................................................................................................ 12

Upgrading HA Pairs ............................................................................................................................ 12

Upgrading Avaya SBCE Servers .......................................................................................................... 13

Rolling back using Web Interface ...................................................................................................... 13

Known Issues and Workarounds ........................................................................................................... 14

Transfer towards call server fails after HA Failover when using Refer Handling .......................... 14

Enable/Disable of VLAN interface ................................................................................................. 16

NTP timesync issue on VM ............................................................................................................ 16

Appendix A ............................................................................................................................................ 17

SBCE OVA deployment and Performance Tuning ......................................................................... 17


Overview This document provides information about the features/enhancements and fixes from prior releases

included in ASBCE Release 6.3 SP2 (6.3.2) and instructions for upgrading from 6.3 GA or 6.3 SP1 to 6.3

SP2.

Documentation Go to support.avaya.com to get the latest 6.3 Avaya Session Border Controller for Enterprise

documentation.

Also visit https://sales.avaya.com/en/pss/avaya-session-border-controller-for-

enterprise?view=collateral for more Avaya SBCE documentation

New Features and Enhancements Following new features and enhancements are added in this release.

Overlapped Address Spaces and Non-Unique SBC Signaling/Media Addresses

The networking features introduced in 6.3 included a restriction that prevents the same IP address

from being configured on the SBC more than one time. However, when overlapped address spaces

are configured, it may be desirable for the SBC to present the same signaling and media addresses to

endpoints in each such attached network.

With 6.3.2, this feature allows the same IP address to be configured on the SBC more than once.

Multiple tenants using the same IP address


Consider the example in the deployment shown in the image above. In order to configure the same

IP (10.1.1.10) to two different tenants, the user needs to perform the following configuration.

1) Enable non-unique IP checkbox under Device Specific Settings -> Advanced Options ->

Network Options.

2) Add VLANs by navigating to Device Specific Settings -> Network Management -> Interfaces ->

Add VLAN. (For more details, refer to SBCE 6.3 Admin guide)

3) Add a network for tenant 1 by navigating to Device Specific Settings -> Network

Management -> Networks


4) Add a network for tenant 2 by navigating to Device Specific Settings -> Network

Management -> Networks

VMware Enhancements

OVA

With SBCE 6.3 SP2, there is a single OVA instead of 2 separate OVAs for deploying EMS and SBCE Only

or EMS+SBCE virtual machines.

While deploying the OVA, the user will get a Deployment Configuration option, where one of the

following 3 options needs to be selected:

1) EMS

2) Small SBC

3) Large SBC

This table explains more details about each of these options.

Deployment Option Description

EMS

Deploy VM configured with 3 vCPU( default CPU reservation and limit 7200MHz in case of CPU speed is 2.4GHz), 8192 MB of Memory, 2 vNIC and 160 GB for Disk. This is used as an EMS only VM in a multi-server deployment.

Small SBC

Deploy VM configured with 2 vCPU(default CPU reservation and limit 4800MHz in case of CPU speed is 2.4GHz), 4096 MB of Memory, 4 vNIC and 160 GB for Disk. The resources are comparable with hardware Micro SBC (CAD 0208). This option can only be used as a Single box deployment. (Both EMS and SBC on the same VM). It cannot be used as SBCE only VM used in multi box deployment. Supports 1000 concurrent unencrypted sessions, and 500 encrypted sessions.


Deployment Option Description

Large SBC

Deploy VM configured with 4 vCPU(default CPU reservation and limit 9600MHz in case of CPU speed is 2.4GHz), 8192 MB Memory, 6 vNIC and 160 GB for Disk. The resources are comparable with 310 category hardware. (Dell 210). This option can be used as a SBCE only VM for multi box deployments, or single box (EMS+SBCE). Supports 2500 concurrent unencrypted sessions and 1800 encrypted sessions. Refer to document in Appendix A for performance tuning on VMware.

Performance Enhancement

With ASBCE 6.3 SP2 the concurrent session capacity has been increased.

Unencrypted Sessions Encrypted Sessions

Small SBC 1000 500

Large SBC 2500 1800

Refer to Appendix A for more details on tuning the ASBCE virtual machine on VMware.

List of Issues Fixed

Key Summary

AURORA-5710 Generation of CSR fails while using "underscore" in contact mail.

AURORA-5702 Generate CSR fails for fields "email" and "uri" in Subject Alt Name

AURORA-5692 SSYNDI restarts with no core on callback call scenario

AURORA-5690 SBCE 6.3.x:New openvpn timer causes openvpn looping condition if internal or network delay causes openvpn process to take more than 5 seconds to start

AURORA-5675 Packet capture in GUI doesn't allow choosing IP address anymore

AURORA-5666 Alpha Blue SBC: After upgrade from 6.3.1 to 7.0.0-05-5291, SBC is DOWN

AURORA-5665 Call is not getting preserved after SM failover in ASBC environment

AURORA-5664 Voice patch is not there after rebooting ASBC

AURORA-5653 Large presence messages causes SSYNDI to restart

AURORA-5504 Allowing simple password for IPCS and ROOT

AURORA-5488 System crash, likely due to call transfer (refer handling enabled)

AURORA-5486 RHSA-2015-0092-GHOST: glibc vulnerability

AURORA-5471 Alpha: RTCP application relay does not work

AURORA-5418 Audio failing on calls because SBCE uses wrong IP in SDP

AURORA-5417 Using SDP in sigma script seem to crash the system

AURORA-5416 SBCE sending private IP as Media connection address out public interface

AURORA-5393 DNS/SRV SRV part is not being processed correctly calls fail

AURORA-5281 CFD: SFTP backup gives cosmetic error about partial success but backup succeeds

AURORA-5220 SSYNDI process in Secondary SBCE is crashing.

AURORA-5149 ASG feature is disabled after upgrade and or rollback


Key Summary

AURORA-5130 Logging in via ASG on GUI with sroot fails

AURORA-5089 CFD:ALL:DB::Upgrade from 6.2 to 6.3 caused Network interfaces A1/A2/B1/B2 to go down

AURORA-5017 When DNS/SRV is picked in routing profile, "Next Hop Priority" should not be selectable

AURORA-4986 CFD: POODLE security and bug fix update on Data Interface

AURORA-4955 Media ports not getting free resulting in SBCE not processing calls.

AURORA-4767 SBC doesn't support sdp with no m line from ICR/AVP

AURORA-4402 Shared control fail in 6.2.1Q07, one-x get logout immediately

AURORA-3878 Record routes feature in Server Interworking isn't working correctly

AURORA-3834 Sigma issue %BODY[1].regex_replace doesnt work outbound

AURORA-3446 Asterisk Integration POC : SRTCP is not disabled in 200OK altough media policy towards aura has it disabled, causing call drop

AURORA-1795 Scrubber incidents may be false alarms

AURORA-1786 Server DoS enabled but no DoS protection configured cause blocked calls

AURORA-1447 In IVR blind transfer, if user hang up the call too early, it still cause dead air


Deployment Instructions

Installation

Hardware deployment

ASBCE Release 6.3 SP2 does not support direct installation using a DVD or a USB flash drive on any of

the hardware supported for ASBCE. Instead the user must install ASBCE 6.3 software on the servers,

and then proceed to upgrade it to 6.3 SP2.

VMWare deployment

Unlike deployment on hardware, a user can deploy the OVA of ASBCE 6.3 SP2 on a VMware host.

During deployment, the user can choose the correct profile (EMS, Small, Large). Refer to Appendix A

for more details.

Upgrade Upgrades are supported on both, Hardware deployment as well as VMware deployment.

ASBCE Release 6.3 GA or 6.3.SP1 is a pre-requisite for upgrading to Release 6.3 SP2. Please make sure

that the system being upgraded is at least on 6.3 GA before proceeding further.

Perform all upgrades during a maintenance window. If an upgrade is performed on a production system, it is quite likely that active/ongoing calls will be dropped. For information about the latest Release 6.3 builds, see http://support.avaya.com. Note: Before starting with the upgrade, ensure that Avaya SBCE servers in the deployment have unique hostnames. In case two or more servers have the same hostname, change the hostname. For more information, see Troubleshooting and Maintaining Avaya Session Border Controller. Also, please take a snapshot of the systems before proceeding with the upgrade. In a multi-server deployment, the upgrade sequence is: 1. Secondary EMS Server 2. Primary EMS Server 3. Avaya SBCE Pair:

a. Secondary Avaya SBCE b. Primary Avaya SBCE

You can check the upgrade status at /archive/log/icu/upgrade.log

Upgrading Primary EMS

Before you begin Download the tar file from the PLDS website. The file should be named as sbce-6.3.2-xx-xxxx-.tar.gz. Procedure Copy the upgrade tar file to the EMS server by using one of the following methods: The upgrade tar file is copied to the EMS by using the web interface. The upgrade tar file is manually copied to the EMS server using SFTP or SCP.


Upgrading EMS using a Web Browser

Before you begin Download the upgrade package to a local or remote PC using Avaya Product Licensing and Delivery System (PLDS). The file should be named as sbce-6.3.2-xx-xxxx-.tar.gz. About this task Uploading larger files using a browser can sometimes be unreliable, especially when using older browser versions such as Internet Explorer (IE7, IE8), or Firefox 3.x. Uploading large files through a browser might result in a failed upload or checksum error. Procedure 1. Log in to the EMS web interface with administrator credentials. 2. In the left navigation pane, click System Management. The system displays the System Management screen. 3. Click the Updates tab. 4. In System Upgrade, click the Upgrade from uploaded file field 5. Select the Browse button and navigate to the folder containing the downloaded upgrade file. 6. Select the upgrade file. 7. Click Upgrade. The system displays the Upgrade Confirmation screen. 8. Click Start Upgrade. The system displays Upgrade Status screen with the upgrade log file in a viewable window. After the upgrade is complete, the system displays the Return to EMS tab. 9. Click Return to EMS to log back in to EMS.

Uploading using SFTP or SCP

Before you begin Download the tar file from the PLDS website. The file should be named as sbce-6.3.2-xx-xxxx-.tar.gz. Procedure 1. Log on to the EMS server as an ipcs user by using port 222. 2. Upload the upgrade tar file to the EMS server using SFTP or SCP. 3. Copy the file to /home/ipcs. 4. Log in with the root privileges and move the file from /home/ipcs to the EMS server folder:/archive/urpackages. Note: If the urpackages folder does not exist, create the urpackages folder in the exact path shown above and then proceed with Step 5. 5. On the command line, type md5sum to verify the integrity of the file. Ensure that results on the left match the string embedded within the file name. 6. Log on to the EMS web interface. 7. In the left navigation pane, click System Management > Updates. The system displays the current EMS version and the available upgrade options. 8. In the Updates tab, in the Upgrade from local file field, select the upgrade file. 9. Click Upgrade. The system displays the Upgrade Confirmation screen. 10. Click Start Upgrade. The system displays a series of windows to indicate that the EMS software is upgrading. When the upgrade is complete, the system displays the final window. 11. Click Return to EMS. The system displays the System Management page.


Upgrading Secondary EMS

Before you begin Download the tar file from the PLDS website. The file should be named as sbce-6.3.2-xx-xxxx-.tar.gz. Procedure 1. Copy the tar file to the Secondary EMS server using ipcs user on port 222. You can use SFTP or SCP tools to access the Secondary EMS server. 2. Connect to the system using VGA or Serial console. 3. Using root permissions move the upgrade tar file from the ipcs user home directory to /archive directory. 4. Ensure that the md5sum of the upgrade tar file matches the checksum given in the name of the file. You can use the md5sum command to verify whether the md5sum and the checksum match. 5. At the command prompt, type mkdir /archive/temp_upgrade, where temp_upgrade is the name of the temporary directory. The system creates a temporary directory in the archive directory. 6. At the command prompt, type rm rf /archive/temp_upgrade/*. This command removes all content in the temporary directory. 7. At the command prompt, type tar xzf /archive/sbce-6.3.2-xx-xxxx-.tar.gz C /archive/temp_upgrade, where xx-xxxx is the build number. The system extracts the upgrade tar file in the temporary directory. 8. At the command prompt, type cd /archive/temp_upgrade, where temp_upgrade is the name of the temporary directory. 9. At the command prompt, type chmod +x ursbce.py. 10. At the command prompt, type ./ursbce.py -U --daemonize. This step reboots the system. 11. Wait for the system to reboot. 12. Type cat /etc/sbce-version and verify the version of the system. The file /archive/log/icu/upgrade.log contains upgrade related logs.

Upgrading HA Pairs

Before you begin Ensure that EMS servers are upgraded before upgrading HA pairs. About this task With this procedure, you can upgrade Avaya SBCE devices that are in HA pairs. For more than one Avaya SBCE pair in HA, repeat the procedure for each HA pair. Procedure 1. In the Updates tab, click System Management and then click Upgrade. The system displays the Upgrade Devices window. 2. Select the Secondary HA-SBC device check box. Whenever you first upgrade the primary SBC, the secondary SBC takes over as the primary and then the existing primary becomes the secondary SBC. 3. Click Next. The system displays a window that states that the Device is upgraded. 4. Click Finish The system displays the Upgrade Devices window. 5. Select the Primary HA-SBC check box. 6. Click Next.


The system displays the message that the Device is upgraded. 7. Click Finish. After the EMS software has been upgraded, the system displays the following message for SBC boxes and HA pairs on the Updates tab: One or more devices are in an orphan state. If you would like to upgrade these devices now, please click the Upgrade button below. You may also choose to rollback your EMS at this point. HA system pairs and all other SBC systems must be upgraded before this message is resolved.

Upgrading Avaya SBCE Servers

Before you begin Ensure that the EMS servers are upgraded before upgrading Avaya SBCE servers. About this task This procedure upgrades Avaya SBCE servers that are not in an HA pair. When more than one Avaya SBCE server is available, repeat this step for each Avaya SBCE server. Procedure 1. In the left navigation pane, click System Management > Upgrade. The system displays the Upgrade Devices message box. 2. Select the check box next to the devices that you want to upgrade. The devices can be upgraded one at a time or as a group. If you select more than one device, the devices are put in a queue and upgraded one at a time. 3. Click Next. The system displays a message box indicating that the device is upgraded. 4. Click Finish. After the EMS software has been upgraded, the following message is displayed for SBC boxes and HA pairs on the Updates tab: One or more devices are in an orphan state. If you would like to upgrade these devices now, please click the Upgrade button below. You may also choose to rollback your EMS at this point. HA system pairs and all other SBC servers must be upgraded before this message is resolved.

Rolling back using Web Interface

About this task When you upgrade from a 6.3GA build to the next version of the 6.3 build i.e. a service pack, then the rollback option is available. Procedure 1. From the left navigation pane, click System Management. The system displays the System Management screen. 2. Select the Updates tab. The system displays the current EMS version and the available upgrade and rollback options. 3. Click Rollback. The system displays the Rollback Status screen during rollback, and displays the Return to EMS tab after the upgrade is complete. 4. Click the Return to EMS tab to log back on to the EMS web interface.


Known Issues and Workarounds

Transfer towards call server fails after HA Failover when using Refer Handling

If the deployment has ALL these features mentioned below, only then it is affected by the issue:

One or more SBC HA pairs configured

Refer Handling is enabled

Version is 6.3.2-08-5478

Transfer towards call server fails after HA failover when Refer Handling is enabled towards Trunk

server. This issue is found when a failover happens during the call transfer.

In order to fix this issue, please install the RPM sbce-bin-6.3.2-5510.i686. This is a service affecting

procedure so it must be done in a maintenance window. The procedure to install the RPM should

be performed for each SBC server in the deployment.

Installing the RPM sbce-bin-6.3.2-5510.i686.rpm

1) The file sbce-bin-6.3.2-5510.i686.rpm is available on the Avaya Support site and PLDS.

Download it first.

2) SSH to the SBC server using ipcs user and assume root privilege by typing the command

sudo su

3) Copy sbce-bin-6.3.2-5510.i686.rpm on the SBCE server /home/ipcs directory with scp or

sftp using ipcs user.

4) Create a temporary directory

mkdir /archive/temp-632-patch

5) Move the file from /home/ipcs to this temp directory

mv /home/ipcs/sbce-bin-6.3.2-5510.i686.rpm /archive/temp-632-patch

6) Ensure that the checksum of the file matches with the one given in sbce-bin-6.3.2-

5510.i686.md5sum.txt using the md5sum command.

md5sum /archive/temp-632-patch/sbce-bin-6.3.2-5510.i686.rpm

7) Stop the application service for this particular SBC using the command:

/etc/init.d/ipcs-init stop


8) Install the RPM

rpm -Uvh sbce-bin-6.3.2-5510.i686.rpm nodeps

9) Start the application service using the following command:

/etc/init.d/ipcs-init start

10) Remove the temporary directory

rm rf /archive/temp-632-patch

Backing out sbce-bin-6.3.2-5510.i686.rpm

This procedure needs to be followed in case the user wants to remove sbce-bin-6.3.2-5510.i686.rpm

and replace it with the RPM installed earlier with version 6.3.2-08-5478. This is applicable only if the

system has not been upgraded after installation of the RPM sbce-bin-6.3.2-5510.i686.rpm. This is a

service affecting procedure so it must be done in a maintenance window.

1) SSH to the SBC server using ipcs user and assume root privilege by typing the command

sudo su

2) Create a temporary directory

mkdir p /archive/temp-632-patch

3) Ensure that this directory is empty

rm rf /archive/temp-632-patch/*

4) Extract the original sbce-bin RPM in this directory.

cd /archive/temp-632-patch

tar xzf /archive/urpackages/sbce-6.3.2-08-5478-*.tar.gz sbce-bin*.rpm

5) Stop the application service for this particular SBC using the command:

/etc/init.d/ipcs-init stop

6) Install the RPM

rpm -Uvh sbce-bin-6.3.2-*.i686.rpm nodeps --oldpackage

7) Start the application service using the following command:


/etc/init.d/ipcs-init start

8) Remove the temporary directory

rm rf /archive/temp-632-patch

Enable/Disable of VLAN interface

All VLAN entries under an interface can be enabled or disabled by enabling or disabling the parent

interface. However, after enabling the parent interface, even though, all the VLAN interfaces are

shown as enabled, their routing entries are not added in the routing table.

This will result in no network communication in those VLAN interfaces even though they appear

enabled on the GUI.

In order to ensure that the routing entries are added, the user needs to do either of the following

steps.

Please note that these steps are service affecting and should be carried out during a maintenance

window.

After enabling the parent interface, all the child interfaces will get enabled. Now, each child

interface will need to be disabled and enabled individually.

OR

Do not disable the parent interface if any of the child interfaces need to be disabled. Keep

the parent interface enabled. Disable only the child interfaces one by one. After that, when

required, enable the child interface one by one.

OR

After enabling the parent interface (which will enable all the child interfaces), restart the

application service. This can be done on the GUI in System Management screen by clicking on

Application restart.

NTP timesync issue on VM

VMs which attempt time sync using vmware tools timesync as well as guest VMs NTP sync

mechanism may have issues with guest VMs time changing at random.

When using the guest VMs NTP service to sync time (This is done when the user specifies an NTP

server during EMS/SBCE configuration), it is recommended that VMWare tools timesync parameter

should be disabled.

In order to do so, run the following command:

vmware-toolbox-cmd timesync disable

This is applicable for both OVA deployment (fresh install) as well as for upgrade on VMs.


Appendix A

SBCE OVA deployment and Performance Tuning

Follow this document to deploy ASBCE 6.3 SP2 OVA on a VMware esxi host, and for its performance

tuning.

Install OVA using Vmware Vcenter on ESXi 5.docx

ASBCE_63SP2_ReleaseNotes

Documents

Transcript of ASBCE_63SP2_ReleaseNotes