Oracle Communications WebRTC Session Controller. Preparation Guide

Transcription

1 Oracle Communications WebRTC Session Controller Preparation Guide Edition 1.0 February 2015

2 Copyright 2015, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

3 Table of Contents Preparations Overview Preparation 1: Downloading and Configuring the Virtual Machine Preparation 2: Changing the Networking Topology Preparation 3: Downloading, Installing and Configuring Kamailio...1-9

4

5 Chapter 1 Chapter 1 - Page 1

6 Chapter 1 - Page 2

7 Preparations Overview Overview To be able to run Oracle Communications WebRTC Session Controller, you need two separate machines; one machine for the Signaling Engine and one machine for the Media Engine. To run this setup on a laptop, you will need to use virtual machines. One of the installation alternatives for the Media Engine is to execute the installer directly on a virtual machine, and you will do that in the installations practice later. The Signaling Engine, on the other hand, needs a certified platform before installation. In the preparations below you will download and setup a virtual machine, running Oracle Enterprise Linux, which will be the platform where you will install the Signaling Engine. Chapter 1 - Page 3

8 Preparation 1: Downloading and Configuring the Virtual Machine Overview In this practice you will go to the public webpage to download a base virtual machine that will be used for the labs. You will setup and do some specific configuration of this virtual machine. Tasks Downloading and Setting Up the Virtual Machine 1. Open a browser and go to html. 2. Follow the Download and Setup Instructions for SDP-VM that is available on the webpage. Renaming the Virtual Machine 3. Start the Oracle VM VirtualBox Manager and make sure your virtual machine is not running. 4. Right-click the SDP_VM and select Show in Explorer. A file explorer window appears. 5. In the file explorer window, right-click the SDP_VM folder and select Properties. The SDP_VM Properties dialog appears. 6. Deselect Read-only in the Attributes settings and click OK. The Confirm Attribute Changes dialog appears. 7. Click OK. 8. In the VirtualBox Manager, right-click on SDP_VM and select Settings. The SDP_VM - Settings screen appears. 9. In the Name field, replace SDP_VM with WSC_71_SE. 10. Click OK. The VirtualBox Manager appears again and the virtual machine is now named WSC_71_SE. Summary You have now a working virtual machine. Chapter 1 - Page 4

9 Preparation 2: Changing the Networking Topology Overview In the practices for WebRTC Session Controller, you will be running two separate virtual machines that will communicate with each other, the Signaling Engine and the Media Engine. Configuring the virtual machines network topology to be Host Only will enable the two virtual machines to effectively communicate with each other, and the host machine. Tasks Changing the Networking Settings in VirtualBox 1. Start the Oracle VM VirtualBox Manager and make sure your virtual machine is not running. 2. From the File menu, select Preferences. The Virtual Box - Settings screen appears. 3. From the list of settings, select Network. The Network panel appears. 4. Select the Host-only Networks tab. A panel with one VirtualBox Host-Only Ethernet Adapter appears. Note: If there is no VirtualBox Host-Only Ethernet Adapter available, click the icon on the right with the + symbol to create one. 5. Right click VirtualBox Host-Only Ethernet Adapter and select Edit host-only network. The Host-only Network Details screen appears. 6. In the IPv4 Address field, enter In the IPv4 Network Mask field, enter Click OK and then click OK. The VirtualBox Manager appears again. 9. In the list of virtual machines, right-click on WSC-SE and select Settings. The WSC-SE - Settings screen appears. 10. From the list of settings, select Network. The Network panel appears. 11. For the Attached to field, select Host-only Adapter. 12. Click Advanced. The advanced settings are expanded. 13. In the MAC Address field, the identifier assigned to the virtual network interface is shown. This address is now going to be used in your virtual machine, and you need to reconfigure the networking settings accordingly, which you will do in the following instructions. 14. Click OK. The VirtualBox Manager appears again. Checking the Networking Settings in Linux 15. Start the virtual machine and log in as the user oracle, with the password oracle. 16. Open a new terminal window and check the network settings: $ ifconfig Chapter 1 - Page 5

10 You should now see that the network interface is using the MAC address that you saw earlier in the VirtualBox settings. The IP address is probably set to the first available in the DHCP range, which is You might also see that the network interface is called eth1 instead of the normal eth0. In the following instructions you will reset the network interface to eth0 and change the IP address to be static. Configuring the Network Interface If the network interface is already set to eth0, you can skip the following section and jump to the instructions for setting the IP address to static. 17. Open the udev network rule file for edit: $ sudo gedit /etc/udev/rules.d/70-persistent-net.rules 18. Copy the mac address from eth1 to eth0 and remove the rule for eth1. Example before edit: # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:21:72:7a", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:a3:41:43", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" Example after edit: # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:a3:41:43", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" 19. Save the file and close the editor. Setting the IP Address to Static 20. Open the network configuration for eth0 file for edit: $ sudo gedit /etc/sysconfig/network-scripts/ifcfg-eth0 21. Change the value of BOOTPROTO to none. 22. Change the value of HWADDR to the new MAC address. 23. Add the following after the HWADDR line: IPADDR= NETMASK= NETWORK= Example before edit DEVICE=eth0 TYPE=Ethernet UUID=06114fbc-8c6a-4b32-abe2-8adbe586febd ONBOOT=yes NM_CONTROLLED=yes Chapter 1 - Page 6

11 BOOTPROTO=dhcp HWADDR=08:00:27:21:72:7A DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" Example after edit: DEVICE=eth0 TYPE=Ethernet UUID=06114fbc-8c6a-4b32-abe2-8adbe586febd ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none HWADDR=08:00:27:A3:41:43 IPADDR= NETMASK= NETWORK= DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" 24. Save the file and close the editor. 25. Open the hosts file for edit: $ sudo gedit /etc/hosts 26. Replace oel64 with wsc-se. 27. Add the following at the end of the file: wsc-se 28. Save the file and close the editor. 29. Open the network configuration file for edit: $ sudo gedit /etc/sysconfig/network 30. Set host name to wsc-se, then save and close the file. HOSTNAME=wsc-se 31. Reboot the virtual machine: $ reboot 32. Log in as the user oracle, with the password oracle. 33. Open a new terminal window and check the network settings: $ ifconfig Chapter 1 - Page 7

12 You should now see that the network interface is called eth0 and that the IP address is set to The prompt should also be set to wsc-se. Summary You have now changed the networking topology for the virtual machine to host-only and configured the IP address to static. Chapter 1 - Page 8

13 Preparation 3: Downloading, Installing and Configuring Kamailio Overview The WebRTC Session Controller is designed to integrate into the IMS core network as a kind of border session controller for WebRTC clients. There is no SIP proxy and registrar functionality available in the WebRTC Session Controller product. In the IMS core network it is done by the Call Session Control Functions (CSCFs). In this practice you will download, install and configure Kamailio, which you will use as the SIP proxy and registrar functionality. Tasks Downloading Kamailio Since websites are often changed, the instructions below might differ slightly from the way the site looks at the moment. But the process should be very similar. 1. In your host machine, open a browser and go to 2. Click Download. 3. Find the section for RPM Packages and click the link for the latest versions, which at the time of writing was 4. Click the link for Red Hat Enterprise Linux 6, which at the time of writing was 5. Click x86_ Download the latest version, which at the time of writing was kamailio x86_64.rpm and save it in your shared directory; C:\VMs\Shared. Installing Kamailio 7. Start the virtual machine and log in as the user oracle, with the password oracle. 8. Open a new terminal window and mount the stage directory: $./mount_shared.sh 9. Start the installer: $ sudo rpm -ivh /mnt/shared/kamailio x86_64.rpm Configuring Kamailio 10. Open the configuration file for editing: $ sudo gedit /etc/kamailio/kamailio.cfg 11. In the local domain alias section, add the example domain as shown below: /* add local domain aliases */ alias="example.com" Note: The configuration is near line Change the SIP port to 5070, as shown below: /* port to listen to * - can be specified more than once if needed to listen on many ports */ port=5070 Note: The configuration is near line 168. Chapter 1 - Page 9

14 13. Save the file and close the editor. Deactivating the Automatic start of the Kamailio Service Kamailio is by default configured to start at boot, which in most cases will be unnecessary. Therefore, deactivate the automatic start of the Kamailio service. 14. Check for which runlevels the Kamailio service is automatically started: $ chkconfig --list kamailio kamailio 0:off 1:off 2:off 3:on 4:on 5:on 6:off 15. Deactivate automatic start of the service: $ sudo chkconfig --level 345 kamailio off 16. Check that the service is not automatically started for any runlevel: $ chkconfig --list kamailio kamailio 0:off 1:off 2:off 3:off 4:off 5:off 6:off Increasing the TCP Read Buffer Size for Kamailio For Kamailio to be able to handle large SDP messages, you need to increase the TCP read buffer size. This configuration value has to be set at every restart of Kamailio. 17. Create a file called kamailio_config.sh, with the following code: #!/bin/sh echo " " echo "Old TCP read buffer size used by Kamailio" sudo kamcmd cfg.get tcp rd_buf_size sudo kamcmd cfg.set tcp rd_buf_size echo "" echo "New TCP read buffer size used by Kamailio" sudo kamcmd cfg.get tcp rd_buf_size echo " " 18. Make the file executable: $ chmod +x kamailio_config.sh Starting Kamailio 19. Create a file called kamailio_start.sh, with the following code: #!/bin/sh sudo service kamailio restart./kamailio_config.sh 20. Make the file executable: $ chmod +x kamailio_start.sh 21. Test the script: $./kamailio_start.sh You should see that the script first tries to stop Kamailio, start it again and then set the tcp read buffer size. Stopping Kamailio 22. Create a file called kamailio_stop.sh, with the following code: Chapter 1 - Page 10

15 #!/bin/sh sudo service kamailio stop 23. Make the file executable: $ chmod +x kamailio_stop.sh 24. Test the script: $./kamailio_stop.sh Summary You have now downloaded, installed and configured Kamailio, which you will use as the SIP proxy and registrar functionality. Chapter 1 - Page 11

16 Chapter 1 - Page 12