Dialogic PowerMedia XMS and Amazon Web Services (AWS)

Dialogic PowerMedia XMS and Amazon Web Services (AWS) Using PowerMedia XMS with a J2EE Application Server and Dialogic JSR 309

Introduction This is the third tech note in the series Dialogic PowerMedia XMS and Amazon Web Services. The first covered getting a PowerMedia XMS media server running on Amazon Web Services (AWS) using an Amazon Machine Image (AMI), where XMS used the four (4) port trial license built into the image. The next showed how the same XMS image can be licensed - with a trial or permanent license - for more ports, thus paving the way for use with more realistic applications. This scenario used an Amazon Virtual Private Cloud. (VPC) With the VPC, it is possible to define a permanent Elastic Network Interface (ENI) with a permanent MAC address and a permanent Elastic IP (EIP) address that will remain the same whenever the instance is used. This all sets the stage for this third tech note, where the XMS JSR309 connector is used with a Telestax open source VoIP platform running on an Apache/Tomcat Java web server and servlet container. This Application Server (AS) is run on a separate virtual machine from XMS and is used as the endpoint for SIP calls to the platform, with XMS providing media services for the calls. TheTelestax/Tomcat XMS and AS combination is covered in detail in XMS documentation; however, there are several network-related changes that are needed to run under AWS. This tech note focuses both on those, and on AWS configuration. As with the XMS-only configurations, a public Amazon Machine Image (AMI) for Telestax/Apache is available to provide an almost ready-to-use server. For readers, a working familiarity with AWS and an AWS account are presumed. Creating a VPC and Running an XMS Image in it A working XMS instance is needed and should be created first. Instructions for doing this were given in the second tech note in this series - Dialogic PowerMedia XMS and Amazon Web Services - Using PowerMedia XMS Licenses with AWS - and will not be repeated here. The Amazon VPC created for XMS will also be used to run the Application Server. (S) Two notes concerning running the AS in a VPC: 1. It is possible to run the AS directly on EC2, but the instructions in this tech note cover running it in an XMS VPC. 2. The standard four (4) port verification license shipped with XMS is sufficient for use with the AS. A larger trial license is not needed unless running at a higher call density is desired, in which case follow the procedures outlined in the XMS tech note mentioned above to upgrade the licensing. Once the XMS instance is running and verified, make a note of its Public Elastic IP address and the ID of its VPC. Run the JSR309 Application Server Image There should now be an XMS instance running. This section will cover configuring and running the AS with XMS using the AWS EC2 web GUI. 2

Create VPC Security Group A new security group specifically for the AS should first be created: 1. Services VPC Security Groups 2. Create Security Group 3. Name tag, Group name and Description just descriptive; not important 4. VPC must be the XMS VPC just created 5. Yes, Create to create the group Once the group is created, inbound rules must be added. Click the Inbound Rules tab and Edit. Add the following rules: Type Protocol Port Range Source SSH TCP 22 0.0.0.0/0, or as desired Custom TCP Rule TCP 8080 0.0.0.0/0, or as desired Custom TCP Rule TCP 5080 0.0.0.0/0, or as desired Custom TCP Rule TCP 8000 0.0.0.0/0, or as desired Custom TCP Rule TCP 9990 0.0.0.0/0, or as desired Custom UDP Rule UDP 5080 0.0.0.0/0, or as desired The source IP address can be left as 0.0.0.0/0 (anywhere), or, for security reasons, restricted to certain IP addresses. Save will save the ports just added to the group. Note that the firewall on the AS image used here is disabled. All security for the instance is handled through the Amazon security group. Create an Additional Network Interface in the XMS VPC Since the AS is run in the XMS VPC, it will need its own permanent Network Interface and Public IP Address. Create the Network Interface first. In the EC2 configuration screen: 1. Services EC2 Network Interfaces 2. Create Network Interface 3. Add a convenient description 4. Select the subnet that was created as part of the XMS VPC 5. Private IP can remain at the default of auto assign 6. Select the AS security group just created that belongs to the VPC 7. Yes, Create will create the interface 3

Create an Additional Elastic IP (EIP) Address in the XMS VPC The EIP address, along with the Elastic Network Interface (ENI) created in the last section make up a permanent public network interface. The MAC and IP addresses will remain the same over multiple uses of the same image. Note that an extra cost is incurred for an EIP. Please refer to AWS for details. To create the EIP address: 1. Services VPC Elastic IPs 2. Allocate New Address 3. Network platform must be EC2-VPC 4. Yes, Allocate Choose and launch an Amazon Machine Image (AMI) Images may be found in Services EC2 AMIs. The JSR309/Telestax/Tomcat AMI is located in these AWS Regions: US West (N. California) US East (N. Virginia) EU (Frankfurt) Asia Pacific (Singapore) South America (Sao Paulo) Search IMAGES/AMIs for Public images, AMI Name dialogic_jsr309. Choose the latest release. For example, there may be a dialogic_jsr309_2.4, a dialogic_jsr309_2.4_su1 and a dialogic_jsr309_2.4_su2. In that case, the latest would be dialogic_jsr309_2.4_su2. (This would be the AS that goes with XMS release 2.4, service update 2) Once the image is located, the instance can be started. Do this by either right clicking on the image and selecting Launch or checking off the image and selecting: Actions Launch. The steps below correspond to the AWS steps used to launch the AMI. Step 2: Choose an Instance Type This tech note assumes that no greater than a ten (10) port XMS trial license will be used on the XMS media server used with this AS. An instance type of m3.large or better should be used. 4

Proceed to the next step by selecting Next: Configure Instance Details. Step 3: Configure Instance Details The settings for this screen are as follows: Setting Value Comment Number of Instances 1 Leave at default Purchasing option unchecked Leave at default Network Subnet Choose the VPC that is used by XMS The subnet that was automatically created with the VPC will appear here Auto-assign Public IP Use subnet setting (Disable) Public IP will come from EIP Placement Group No placement group Leave at default IAM role None Leave at default Shutdown behavior Stop Stop will leave the instance in a non-running state in your list of instances. It can be restarted without losing any configuration changes made. Terminate will destroy the instance and you will need to start again with the public AS image. Enable termination protection unchecked Leave at default Monitoring unchecked Leave at default 5

EBS-optimized instance unchecked Leave at default Tenancy Shared Tenancy Leave at default Network Interfaces Select the ENI just created Disregard the public IP address warning Advanced Details No changes Leave at default Proceed to the next step with Next: Add Storage Step 4: Add Storage The default storage allocated (10 GB) with a General Purpose Volume Type is sufficient for an AS trial. Proceed to the next step with Next: Tag Instance. Step 5: Tag Instance Add a value - something recognizable when looking at AWS console ( AS-XMS-2.4 for example) Step 6: Configure Security Group This step will open up AWS ports for access to the AS. Keep in mind, this step is not on the AS system itself; it is AWS security. Check off Select an existing security group. All security groups belonging to the VPC will be listed. Select the group that was created to open up the AS ports, rather than the default or XMS group. The next step is Review and Launch. Step 7: Review Instance Launch There will be warnings about improving the instances security and the instance not being eligible for free usage tier. It is OK to ignore such warning(s). Check information entered. If all looks as expected, start the instance with Launch. Remember that a public/private key pair must be associated with each new instance. Create a new key pair if you do not already have one, or you can use an existing key pair. The key pair is used to connect via ssh directly to the AS, which must be done to complete network configuration on the system. Either Choose an existing key pair or Create a new key pair. Your instance is now launching should now be seen. Check the Instances listing to see when the AS instance is up and running. 6

Attach Elastic IP Address While the instance is launching, the Elastic IP (EIP) address can be attached: Services EC2 or VPC Elastic IPs Select Elastic IP just created and then Associate Address. Choose either instance just started or Network Interface just created and the EIP will be attached to the running instance. Network Configuration on the AS System When starting an AS image for the first time, there are a number of IP addresses that must be set in various configuration files used in the different layers of the AS. A convenient script is provided to automatically discover and set most of these addresses. However, the IPv4 address of the XMS media server must be manually entered when the script is run. This should be done by directly logging into the AS system using ssh with the private key that corresponds to the public key attached to the instance: > ssh i my-private-key.pem root@<as_ip_addr> No password will be necessary. The script is called set_addresses.sh and can be found in the directory /root/telestax. It will automatically set the proper hostnames and addresses for the XMS server and the AS itself in the AS configuration files. Run the script as follows: >./set_addresses.sh When prompted, enter the XMS server s public IP address, as found on the Instances page. (Services EC2 Instances) Once there, click on the running XMS instance, and one of the details will be its Public IP address. When prompted to restart the Tomcat server, reply with y. The AS should now be ready for use. Verify JSR309 AS Operation Accessing the Tomcat Administrator s WebGUI If not already noted, find the address for the AS on the details page for the running instance. (Services EC2 Instances) Browse to port 8080 on the AS s public IP address. http://<as_ip_addr>:8080. There, log in using admin/admin for username/password. Under Server Status Manager, select List Applications. The screen will show all available applications. One of them should have a Path of /dlgmsc_tests and a Display Name of Dialogic- Samples. 7

Running the JSR309 Verification Demos Play Demo A simple audio demo can be running using a common SIP phone (such as Linphone or CounterPath X-Lite) by dialling the following SIP URL: sip:dlgcplayerdemo@<as-ip-addr>:5080 You will hear Welcome to Dialogic JSR309 verification demo. If you can hear this, Dialogic XMS media server using JSR309 connector is working correctly. Additional Demos Additional demos available in the AMI are described in section 7, Test Servlets in http://www.dialogic.com/webhelp/xms/2.1/xms_jsr309user.pdf. Note that demos requiring DTMF input will not work with Linphone. They require RFC2833 DTMF, and Linphone is unable to provide this. 8

Next Steps This tech note covered configuring and running a JSR309 application server with XMS on AWS. The setup is intended to be used for test purposes only, not for production. In considering XMS as part of an AWS media server solution, you will likely want to first try it with your own application server, cloud-based or otherwise, and at densities suitable for a production situation. 9

RFP www.dialogic.com For a list of Dialogic offices and locations, please visit: https://www.dialogic.com/contact.aspx Copyright 2015 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries ( Dialogic ). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-use.aspx for more details. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on the web at www.dialogic.com. It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic s legal department at 6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint- Laurent, Montreal, Quebec, Canada H4T 2B5. Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements. Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, ControlSwitch, I-Gate, Mobile Experience Matters, Network Fuel, Video is the New Voice, Making Innovation Thrive, Diastar, Cantata, TruFax, SwitchKit, Eiconcard, NMS Communications, SIPcontrol, Exnet, EXS, Vision, incloud9, NaturalAccess and Shiva, among others as well as related logos, are either registered trademarks or trademarks of Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic s legal department at 6700 Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Any authorized use of Dialogic's trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic s trademarks requires proper acknowledgement. The names of actual companies and products mentioned herein are the trademarks of their respective owners. This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights. 07/15