Mediant Cloud Edition (CE)

Transcription

1 Installation Manual AudioCodes Mediant Family of Session Border Controllers (SBC) Mediant Cloud Edition (CE) Session Border Controller Version 7.2

2

3 Installation Manual Contents Table of Contents 1 Introduction Installation Prerequisites for AWS Environment AudioCodes Mediant CE AMI IAM Role for Mediant CE Network Prerequisites Cluster Subnet Instance Types Installation Prerequisites for Microsoft Azure Environment Mediant VE/CE VHD Image for Azure Environment Prerequisites Opening the Azure Portal Creating a Resource Group Creating a Storage Account Uploading Mediant VE/CE VHD Image Creating a Managed Image Network Prerequisites Virtual Machine Sizes Installation Prerequisites for OpenStack Environment AudioCodes Mediant CE Image Network Prerequisites Instance Flavors Deploying Mediant CE Licensing Mediant CE Obtaining and Activating a Purchased License Key Installing the License Key Installing the License Key on a Mediant CE with One SC Instance Installing License Key on a Mediant CE with Two SC Instances Product Key Version Software-based SBC Series

4 Mediant Cloud Edition SBC List of Figures Figure 1-1: Mediant CE Architecture... 7 Figure 2-1: "Public Images" in AWS EC2 Dashboard... 9 Figure 2-2: Copy AMI Window... 9 Figure 2-3: Mediant CE Network Architecture - AWS Figure 2-4: Create Subnet Dialog Box Figure 2-5: Route Table Tab Figure 2-6: Creating NAT Gateway Figure 2-7: Created NAT Gateway Figure 2-8: Route Table - Edit Figure 2-9: Routes - Save Figure 3-1: Creating a Resource Group Figure 3-2: Creating a Storage Account Figure 3-3: Selecting Storage Account Figure 3-4: Creating a Container Figure 3-5: Selecting Storage Account Figure 3-6: Uploading VHD Image File to Storage Account Container Figure 3-7: Creating a Managed Image Figure 3-8: Mediant CE Network Architecture (Azure) Figure 4-1: Mediant CE Network Architecture - OpenStack Figure 6-1: Software License Activation Tool Figure 6-2: Product Key in Order Confirmation Figure 6-3: Apply New License Key Message Figure 6-4: Reset in Progress for License Key Figure 6-5: Reset and Save-to-Flash Success Message Figure 6-6: Hitless License Key Upgrade - Progress Figure 6-7: Hitless License Upgrade Successfully Completed Figure 6-8: Reset in Progress for License Key Figure 6-9: Reset and Save-to-Flash Success Message Figure 6-10: Viewing Product Key Figure 6-11: Empty Product Key Field Figure 6-12: Entering Product Key Installation Manual 4 Document #: LTRT-10842

5 Installation Manual Notices Notice Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document can be downloaded from This document is subject to change without notice. Date Published: August WEEE EU Directive Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product. Customer Support Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our website at Abbreviations and Terminology Each abbreviation, unless widely used, is spelled out in full when first used. Related Documentation Mediant Software SBC User's Manual SBC-Gateway-MSBR Series Release Notes Manual Name Document Revision Record LTRT Description Initial document release for Version Microsoft Azure added Installation prerequisites for OpenStack Version Software-based SBC Series

6 Mediant Cloud Edition SBC Documentation Feedback AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our website at Installation Manual 6 Document #: LTRT-10842

7 Installation Manual 1. Introduction 1 Introduction This document describes initial installation of AudioCodes' Mediant Cloud Edition (CE) Session Border Controller (SBC), hereafter referred to as Mediant CE. Mediant CE is a software-based product that is installed and hosted in a cloud computing environment (see note below). Mediant CE is composed of two component types: Signaling Component (SC): The SC handles all SIP signaling traffic. It also determines which Media Component (see below) handles the specific media traffic, which is based on load balancing between the Media Components. Media Components (MC): The MCs handle all media traffic, including transcoding functionality. Up to 21 MCs can be used in the deployed Mediant CE. Mediant CE provides a unified configuration and management interface, implemented by the SC. This interface provides complete control over all Mediant CE components both SC and MCs. Mediant CE supports High Availability (HA), which is implemented by: Employing two SC instances that operate in a 1+1 Active/Standby mode and that provide high availability for management and signaling traffic. Employing multiple MC instances that operate in an N+1 Active/Active mode and that provide capacity preservation for media traffic. The Stack Manager tool is provided as part of the solution. It implements complete lifecycle management of the Mediant CE stack, including initial deployment, manual and automatic scaling, healing and service teardown. The following figure provides an overview of the Mediant CE architecture. Figure 1-1: Mediant CE Architecture Version Software-based SBC Series

8 Mediant Cloud Edition SBC Mediant CE currently supports the following cloud computing platforms: Amazon Web Services (AWS) Microsoft Azure OpenStack Note: The Mediant CE deployment on Azure and OpenStack is currently available for evaluation purposes only. Support for signaling components HA is currently not available in the Microsoft Azure environment. The scope of this document does not fully cover security aspects for deploying the product in the cloud. Security measures should be done in accordance with specific cloud security policies and recommendations. For configuring Mediant CE, refer to the Mediant Software SBC User's Manual. Installation Manual 8 Document #: LTRT-10842

9 Installation Manual 2. Installation Prerequisites for AWS Environment 2 Installation Prerequisites for AWS Environment Prior to installing Mediant CE in the Amazon Web Services (AWS) environment, make sure that you meet the following prerequisites: You have an AWS account. If you don't have an AWS account, you can sign up for one on Amazon's website at You have copied AudioCodes Mediant CE AMI to your account. For more information, see Section AudioCodes Mediant CE AMI on page 9. You have created an Identity and Access Management (IAM) role that enables Mediant CE to manage its network interfaces. For more information, see Section IAM Role for Mediant CE on page 10. You have created all subnets needed for Mediant CE deployment, including the Cluster subnet with a NAT gateway. For more information, see Section Network Prerequisites on page AudioCodes Mediant CE AMI AudioCodes distributes Mediant CE SBC images (AMIs) by publishing them. The images can be found under the "Public Images" section in the AWS EC2 dashboard: Figure 2-1: "Public Images" in AWS EC2 Dashboard For more information, refer to Prior to deploying the Mediant CE cluster, you must copy the public AMI to your account and use this copied AMI when creating the Mediant CE stack. This operation ensures that your instance of Mediant CE will continue to operate normally (including the ability to perform scale-in and scale-out operations) even if the public AMI becomes unavailable. To copy Mediant CE SBC AMI to your account: 1. Locate the public Mediant CE SBC AMI under the Public Images section in the AWS EC2 dashboard. 2. Right-click the AMI, and then from the shortcut menu, choose Copy AMI. Figure 2-2: Copy AMI Window Version Software-based SBC Series

10 Mediant Cloud Edition SBC 3. Enter the destination region, the AMI name, and a description. 4. Click Copy AMI to complete the operation. 2.2 IAM Role for Mediant CE The following IAM role must be created prior to creating the Mediant CE stack. This role ensures that Mediant CE components can manage their network interfaces and re-assign IP addresses in case of a switchover. { "Version": " ", "Statement": [ { "Action": [ "ec2:assignprivateipaddresses", "ec2:unassignprivateipaddresses", "ec2:associateaddress", "ec2:describeaddresses", "ec2:describenetworkinterfaceattribute", "ec2:describenetworkinterfaces", "s3:get*", "s3:list*" ], "Effect": "Allow", "Resource": "*" } ] } To create an IAM Role: 1. Open the AWS IAM console. 2. Under Policies, create a new policy as specified above. 3. Under Rules, create a new rule based on the policy created in the previous step. Installation Manual 10 Document #: LTRT-10842

11 Installation Manual 2. Installation Prerequisites for AWS Environment 2.3 Network Prerequisites Mediant CE uses the following subnets: Cluster Subnet: This subnet is used for internal communication between Mediant CE components and for accessing the AWS API. It must have a NAT gateway attached (for more information, see Section Cluster Subnet on page 12). The subnet is connected to both SC and MC components as the first network interface (eth0). OAM Subnet: This subnet carries management traffic (e.g., HTTP, SSH, and NTP). It is connected to both SC and MC components as the second network interface (eth1). Despite the name, this subnet may also carry signaling (SIP) and media (RTP) traffic. Signaling Subnets 1 and 2: These subnets carry signaling (SIP) traffic. They are connected to SC as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry signaling traffic. Media Subnets 1 and 2: These subnets carry media (RTP) traffic. They are connected to MCs as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry media traffic. All subnets must reside in the same Availability Zone of your Virtual Private Cloud (VPC). The following figure illustrates the Mediant CE network architecture: Figure 2-3: Mediant CE Network Architecture - AWS Version Software-based SBC Series

12 Mediant Cloud Edition SBC Cluster Subnet The Cluster Subnet is used for the following tasks: Internal communication between Mediant CE components Accessing AWS API (for IP address management) Mediant CE uses private addresses in the Cluster Subnet. Therefore, it is mandatory to attach a NAT gateway to the Cluster Subnet to enable access to AWS API. In addition, since the Cluster Subnet carries sensitive information, it is recommended to create a dedicated subnet and protect it from unauthorized access. To create the Cluster subnet: 1. Open the VPC service in the Amazon dashboard. 2. Under Subnets, click Create Subnet. Figure 2-4: Create Subnet Dialog Box 3. In the 'Name tag' field, enter the name tag. 4. From the 'Availability Zone' drop-down list, select the Availability Zone where Mediant CE will be deployed. 5. In the 'IPv4 CIDR block' field, enter the IPv4 CIDR for the subnet. 6. Click Yes, Create to create the subnet. 7. In the Cluster Subnet properties, locate the name of the Route Table associated with it: Figure 2-5: Route Table Tab Installation Manual 12 Document #: LTRT-10842

13 Installation Manual 2. Installation Prerequisites for AWS Environment 8. In NAT Gateways, click Create NAT Gateway: Figure 2-6: Creating NAT Gateway 9. From the 'Subnet' drop-down list, select a subnet that belongs to the same Availability Zone where the Cluster subnet was created (and where Mediant CE will be deployed) and that has the Internet Gateway attached to it. 10. From the 'Elastic IP Allocation ID' drop-down list, select an existing Elastic IP if you have pre-allocated Elastic IPs in your VPC, or click Create New EIP to create a new one. 11. Click Create a NAT Gateway to create the NAT gateway: Figure 2-7: Created NAT Gateway 12. Click Edit route tables to attach the NAT gateway to the Cluster Subnet. 13. Locate the route table that is associated with the Cluster Subnet. In the Route Table properties, switch to the Routes tab, and then click Edit to edit the route table. Figure 2-8: Route Table - Edit Version Software-based SBC Series

14 Mediant Cloud Edition SBC 14. Change the default route entry ( /0) so that it points to the NAT gateway that you created previously, and then click Save to save your changes. Figure 2-9: Routes - Save 2.4 Instance Types The Amazon EC2 instance types supported by Mediant CE are listed in the SBC-Gateway- MSBR Series Release Notes, which can be downloaded from AudioCodes website at Note: The SC and MC instances use different instance types. Installation Manual 14 Document #: LTRT-10842

15 Installation Manual 3. Installation Prerequisites for Microsoft Azure Environment 3 Installation Prerequisites for Microsoft Azure Environment Prior to installing Mediant CE in a Microsoft Azure environment, make sure that you meet the following prerequisites: You have a Microsoft Azure account. If you don't have an Azure account, you can sign up for one on Microsoft's website at You have the Mediant VE VHD image for Azure. For more information, see Section Mediant VE/CE VHD Image for Azure on page 15. You have created all subnets needed for Mediant CE deployment, including the Cluster subnet. For more information, see Section Network Prerequisites on page Mediant VE/CE VHD Image for Azure To deploy Mediant CE on Azure, you must use the Mediant VE/CE VHD Image for Azure. For more information, go to Environment Prerequisites Prior to deploying Mediant CE on Azure, you must perform the following steps: Create a Resource Group for all Mediant CE related environmental entities. Create a Storage Account for storing Mediant CE images. Upload Mediant VE/CE VHD Image for Azure to the Storage Account. Create a Managed Image from the uploaded VHD. Create a Virtual Network in to which Mediant VE will be deployed Opening the Azure Portal All operations described in the following sections are done through the Microsoft Azure portal. To access the Azure portal: 1. Go to 2. Log in to your Azure account using your Azure credentials Creating a Resource Group Microsoft Azure uses Resource Groups to create logical grouping of related entities. Start your environment preparations for Mediant CE deployment by creating a new Resource Group. You will later use this group to "group" the Storage Account and Virtual Networks (create in subsequent sections). To create a Resource Group: 1. Open the Resource groups screen on the Azure dashboard. 2. Click Add; the Create Resource Group screen appears. 3. In the 'Resource group name' field, enter a unique Resource Group name (e.g., Sbc1ResourceGroup). Version Software-based SBC Series

16 Mediant Cloud Edition SBC 4. From the 'Subscription' drop-down list, select a proper Subscription. 5. From the Resource group location' drop-down list, select a proper Location. Figure 3-1: Creating a Resource Group 6. Click Create Creating a Storage Account Microsoft Azure uses Storage Accounts to store files and virtual machine images. You must create a Storage Account for storing Mediant VE/CE images. To create a Storage Account: 1. Open the Storage Accounts screen on the Azure dashboard. 2. Click Add; the Create Storage Account screen appears. 3. In the 'Name' field, enter a unique account name (e.g., sbc1). 4. Select a proper Subscription and Location. Installation Manual 16 Document #: LTRT-10842

17 Installation Manual 3. Installation Prerequisites for Microsoft Azure Environment 5. Under Resource Group, select the Use existing option, and then from the drop-down list, select the Resource Group that you created in Section Creating a Resource Group on page 15 (e.g., Sbc1ResourceGroup). Figure 3-2: Creating a Storage Account 6. Click Create. Version Software-based SBC Series

18 Mediant Cloud Edition SBC 7. After creating a Storage Account, you must create images container for storing Mediant VE/CE VHD image (provided by AudioCodes). a. Open the Storage Account that you created above (e.g., sbc1). b. Navigate to the Blobs service. Figure 3-3: Selecting Storage Account c. Create a container named images. Figure 3-4: Creating a Container Installation Manual 18 Document #: LTRT-10842

19 Installation Manual 3. Installation Prerequisites for Microsoft Azure Environment Uploading Mediant VE/CE VHD Image Once you have created a Storage Account, you need to upload the Mediant VE/CE VHD Image for Azure to the Storage Account. To upload the Mediant VE VHD image: 1. Open the Storage Account that you created (e.g. sbc1). 2. Navigate to the Blobs service. Figure 3-5: Selecting Storage Account 3. Upload Mediant VE/CE VHD Image for Azure to the images container: Figure 3-6: Uploading VHD Image File to Storage Account Container Version Software-based SBC Series

20 Mediant Cloud Edition SBC Creating a Managed Image Once you have uploaded the Mediant VE/CE VHD Image for Azure to your Storage Account, you need to create a Managed Image that is based on it. You will later use this image to create new virtual machine instances. To create a Managed Image: 1. Open the Images screen on the Azure dashboard. 2. Click Add; the Create Image screen appears. Figure 3-7: Creating a Managed Image 3. In the 'Name' field, enter a unique image name (e.g., sbc-7.20a ). 4. From the 'Subscription' drop-down list, select a proper Subscription. 5. From the 'Location' drop-down list, select a proper Location. 6. Under Resource group, select the Use existing option, and then from the drop-down list, select the Resource Group that you created in Section Creating a Resource Group on page 15 (e.g., Sbc1ResourceGroup). 7. For the OS type, select the Linux option. 8. From the 'Storage blob' drop-down list, select the Storage Blob that corresponds to the Mediant VE/CE VHD Image for Azure that you uploaded in Section Uploading Mediant VE/CE VHD Image on page Click Create. Installation Manual 20 Document #: LTRT-10842

21 Installation Manual 3. Installation Prerequisites for Microsoft Azure Environment 3.3 Network Prerequisites Mediant CE uses the following subnets: Cluster Subnet: This subnet is used for internal communication between Mediant CE components and for accessing the Azure API. The subnet is connected to both SC and MC components as the first network interface (eth0). OAM Subnet: This subnet carries management traffic (e.g., HTTP, SSH, and NTP). It is connected to both SC and MC components as the second network interface (eth1). Despite the name, this subnet may also carry signaling (SIP) and media (RTP) traffic. Signaling Subnets 1 and 2: These subnets carry signaling (SIP) traffic. They are connected to SC as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry signaling traffic. Media Subnets 1 and 2: These subnets carry media (RTP) traffic. They are connected to MCs as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry media traffic. All subnets must reside in the same Virtual Network. The following figure illustrates the Mediant CE network architecture: Figure 3-8: Mediant CE Network Architecture (Azure) Version Software-based SBC Series

22 Mediant Cloud Edition SBC 3.4 Virtual Machine Sizes Virtual machine (VM) sizes supported by Mediant CE are listed in the SBC-Gateway-MSBR Series Release Notes, which can be downloaded from AudioCodes website at Note: The SC and MC virtual machines use different VM sizes. Installation Manual 22 Document #: LTRT-10842

23 Installation Manual 4. Installation Prerequisites for OpenStack Environment 4 Installation Prerequisites for OpenStack Environment Prior to installing Mediant CE in the OpenStack environment, make sure that you meet the following prerequisites: You have uploaded AudioCodes Mediant VE/CE Image to the image repository. For more information, see Section AudioCodes Mediant CE Image on page 23. You have created all subnets needed for Mediant CE deployment, including the Cluster subnet with a NAT gateway. For more information, see Section Network Prerequisites on page AudioCodes Mediant CE Image To deploy Mediant CE on OpenStack, you must use the Mediant VE/CE QCOW2 Image for KVM/OpenStack. For more information, go to Upload the image to OpenStack image repository, using the following command: # openstack image create --disk-format qcow2 \ --container-format bare --public \ --file./sbc-f7.20a qcow2 sbc-f7.20a Network Prerequisites Mediant CE uses the following subnets: Cluster Subnet: This subnet is used for internal communication between Mediant CE components. The subnet is connected to both SC and MC components as the first network interface (eth0). OAM Subnet: This subnet carries management traffic (e.g., HTTP, SSH, and NTP). It is connected to both SC and MC components as the second network interface (eth1). Despite the name, this subnet may also carry signaling (SIP) and media (RTP) traffic. Signaling Subnets 1 and 2: These subnets carry signaling (SIP) traffic. They are connected to SC as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry signaling traffic. Media Subnets 1 and 2: These subnets carry media (RTP) traffic. They are connected to MCs as the third and fourth network interfaces (eth2 and eth3), respectively. The subnets are optional, as the OAM subnet may also carry media traffic. Version Software-based SBC Series

24 Mediant Cloud Edition SBC The following figure illustrates the Mediant CE network architecture: Figure 4-1: Mediant CE Network Architecture - OpenStack 4.3 Instance Flavors Flavors used for creating Mediant CE instances must satisfy CPU, RAM, disk and resource isolation requirements, as specified in the SBC-Gateway-MSBR Series Release Notes. The document can be downloaded from AudioCodes website at Note: The SC and MC instances use different flavors. Installation Manual 24 Document #: LTRT-10842

25 Installation Manual 5. Deploying Mediant CE 5 Deploying Mediant CE To deploy Mediant CE, you need to use the Stack Manager tool. To deploy Mediant CE: 1. Install the Stack Manager tool, as described in the Stack Manager User's Manual, which you can download from AudioCodes website at 2. Create a new Mediant CE stack via Stack Manager s create command, as described in the Stack Manager User's Manual. Version Software-based SBC Series

26 Mediant Cloud Edition SBC This page is intentionally left blank. Installation Manual 26 Document #: LTRT-10842

27 Installation Manual 6. Licensing Mediant CE 6 Licensing Mediant CE Once you have successfully installed Mediant CE, you need to obtain, activate and then install the License Key. Note: Licensing is applicable only to SCs; MCs do not require licensing. 6.1 Obtaining and Activating a Purchased License Key For Mediant CE to provide you with all the required capacity and features, you need to obtain and activate a License Key which enables these capabilities. Note: License activation is intended only for first-time software activation upon product purchase (or if your License Key is "lost", due to whatever reason). For subsequent software feature upgrades, the License Key file is ed to you after your Purchase Order has been processed. For Mediant CE with two SC instances, each SC instance has its own Serial Number, Product Key and License Key. Therefore, the instructions in this section must be done per SC instance. To obtain and activate the License Key: 1. Open AudioCodes Web-based Software License Activation tool at Figure 6-1: Software License Activation Tool Version Software-based SBC Series

28 Mediant Cloud Edition SBC 2. Enter the following information: Product Key: The Product Key identifies your specific Mediant CE purchase for the purpose of subsequent communication with AudioCodes (for example, for support and software upgrades). The Product Key is provided in the Order Confirmation sent to you by AudioCodes upon your purchase, as shown in the example below: Figure 6-2: Product Key in Order Confirmation Note: For Mediant CE orders with two SC instances, you are provided with two Product Keys, one for each SC instance. In such cases, you need to perform license activation twice to obtain License Keys for both SC instances. Fingerprint: The fingerprint is the Mediant CE's Serial Number. The Serial Number uniquely identifies the software installation. The Serial Number is displayed in the 'Serial Number' field on the Device Information page (Monitor menu > Monitor menu > Summary tab > Device Information). Provide one or more addresses to where you want the License Key to be sent. 3. Click Send to submit your license activation request. 4. Once AudioCodes processes and completes your license activation, you will receive an notification with the License Key file attached. Open the file with any text-based program (such as Notepad) and make sure that the serial number ("S/N") in the License Key is correct and reflects the Serial Number of your SC instance. Warning: Do not modify the contents of the License Key file. Installation Manual 28 Document #: LTRT-10842

29 Installation Manual 6. Licensing Mediant CE 6.2 Installing the License Key The procedure for installing the License Key depends on whether the Mediant CE has one or two SC instances Installing the License Key on a Mediant CE with One SC Instance Note: The License Key installation process includes an SC instance reset and is therefore, traffic-affecting. To minimize the disruption of current calls, it is recommended to perform this procedure during periods of low traffic. To install a License Key file for Mediant CE with One SC Instance through Web interface: 1. Login to the Mediant CE Web Interface 2. Open the License Key page (Setup menu > Administration tab > Maintenance folder > License Key). 3. Back up the currently installed License Key, as a precaution. If the new License Key does not comply with your requirements, you can re-load this backed-up License Key to restore the Mediant CE s original capabilities. To back up the License Key, click and save it as a file on your PC. 4. Click the Load File button, navigate to the License Key file on your computer, and then select the file; the Apply New License Key button appears. The License Key page uses color-coded icons to indicate the changes between the previous License Key and the newly loaded License Key. Note: If you want to cancel the installation, reset the SC instance without saving the configuration. 5. Click Apply New License Key; the following message box appears: Figure 6-3: Apply New License Key Message Version Software-based SBC Series

30 Mediant Cloud Edition SBC 6. Click Reset; the SC instance saves the license file and resets itself; the following progress message box appears: Figure 6-4: Reset in Progress for License Key When the reset is complete, the following message box appears: Figure 6-5: Reset and Save-to-Flash Success Message 7. Click Close to close the message box; you are logged out of the Web interface and prompted to log in again. The features and capabilities displayed on the License Key page now reflect the newly installed License Key Installing License Key on a Mediant CE with Two SC Instances You can install the License Key using one of the following methods: Hitless Upgrade: The License Key is installed on both SC instances without affecting traffic, by employing the following mechanism: 1. The License Key file is loaded to the active SC instance. 2. The active SC instance sends the file to the redundant SC instance. 3. The redundant SC instance saves the file to disk and is reset to activate the new license key. 4. The active SC instance saves the file to disk (without a reset). 5. The SC instances undergo an HA switchover, whereby the active instance becomes redundant and the redundant instance becomes active. Current calls are maintained and handled by the active SC instance (previously the redundant instance). 6. The redundant SC instance (previously the active instance) is reset to activate the new license key. Non-hitless Upgrade: The License Key is installed on both SC instances simultaneously (both are reset at the same time). Therefore, this method is trafficaffecting and current calls are terminated. The installation process is as follows: 1. The License Key file is loaded to the active SC instance. 2. The active SC instance sends the file to the redundant SC instance. 3. Both SC instances save the file to disk and are reset to activate the new license key. Installation Manual 30 Document #: LTRT-10842

31 Installation Manual 6. Licensing Mediant CE Note: The License Key file for Mediant CE with two SC instances must contain two License Keys - one for the active SC instance and one for the redundant SC instance. Each License Key has a different serial number ("S/N"), which reflects the serial number of each SC instance. To install a License Key file for Mediant CE with Two SC Instances through Web interface: 1. Log in to the Mediant CE Web Interface. 2. Open the License Key page (Setup menu > Administration tab > Maintenance folder > License Key). 3. Back up the currently installed License Key, as a precaution. If the new License Key does not comply with your requirements, you can re-load this backed-up License Key to restore the Mediant CE s original capabilities. To back up the License Key, click and save it as file on your PC. 4. Click the Load File button, navigate to the License Key file on your computer, and then select the file to load to the device; the Apply New License Key button appears. The License Key page uses color-coded icons to indicate the changes between the previous License Key and the newly loaded License Key. Note: If you want to cancel installation, reset the SC instance without saving the configuration. 5. Click Apply New License Key; the following appears: 6. Click one of the following buttons: Hitless Upgrade: Installs the License Key without affecting traffic by employing the HA switchover mechanism. When you click the button, the process starts and a message box is displayed indicating the installation progress: Figure 6-6: Hitless License Key Upgrade - Progress Version Software-based SBC Series

32 Mediant Cloud Edition SBC When installation completes, the following message box appears: Figure 6-7: Hitless License Upgrade Successfully Completed Non-Hitless Upgrade: Installs the License Key simultaneously on both SC instances where both undergo a reset and therefore, current calls are terminated. When you click the button, the process starts and the following progress message box appears: Figure 6-8: Reset in Progress for License Key When installation completes, the following message box appears: Figure 6-9: Reset and Save-to-Flash Success Message 7. Clock Close to close the message box; you are logged out of the Web interface and prompted to log in again. The features and capabilities displayed on the License Key page now reflect the newly installed License Key. Installation Manual 32 Document #: LTRT-10842

33 Installation Manual 6. Licensing Mediant CE 6.3 Product Key The Product Key identifies a specific purchase of your Mediant CE deployment for the purpose of subsequent communication with AudioCodes (e.g., for support and software upgrades). The Product Key is provided in the order-confirmation sent to you upon your product purchase and is used for activating your license through AudioCodes Software License Activation tool. The Product Key is included in the License Key. Once the License Key is installed, you can view the Product Key in the following Web pages: License Key page (Setup menu > Administration tab > Maintenance folder > License Key). The Product Key is displayed in the read-only 'Product Key' field, as shown in the example below: Figure 6-10: Viewing Product Key Device Information page. If your License Key was purchased in an earlier version (for example, 7.0), the 'Product Key' field may appear empty. In such a scenario, request the Product Key from your AudioCodes sales representative. Once received, do the following: 1. Open the License Key page. 2. Locate the Product Key group: Figure 6-11: Empty Product Key Field 3. Click "empty"; the following appears: Figure 6-12: Entering Product Key 4. In the field, enter the Product Key, and then click Submit (or Cancel to discard your entry). Version Software-based SBC Series

34 International Headquarters 1 Hayarden Street, Airport City Lod , Israel Tel: Fax: AudioCodes Inc. 27 World s Fair Drive, Somerset, NJ Tel: Fax: Contact us: Website: AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What s Inside Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners. Product specifications are subject to change without notice. Document #: LTRT-10842