Dialogic Video Conferencing Demo Installation Guide

Transcription

1 Dialogic Video Conferencing Demo Installation Guide October

2 Copyright and Legal Notice Copyright 2011 Dialogic Inc. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc. 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 Inc. 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 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 Inc. at the address indicated below or on the web at 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 1504 McCarthy Boulevard, Milpitas, CA USA. 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, Diva ISDN, Making Innovation Thrive, Video is the New Voice, VisionVideo, Diastar, Cantata, TruFax, SwitchKit, SnowShore, Eicon, Eiconcard, NMS Communications, NMS (stylized), SIPcontrol, Exnet, EXS, Vision, PowerMedia, PacketMedia, BorderNet, incloud9, I-Gate, ControlSwitch, NaturalAccess, NaturalCallControl, NaturalConference, NaturalFax and Shiva, among others as well as related logos, are either registered trademarks or trademarks of Dialogic Inc. 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 1504 McCarthy Boulevard, Milpitas, CA USA. 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.

3 Table of Contents 1. Introduction Installation Instructions... 6 Getting and Preparing the ISO File... 6 Pre-Installation General Notes and Warnings... 6 System Requirements... 6 Installing the Operating System from the CD... 7 Post-Installation... 7 Verifying the Installation... 7 Obtaining a License... 7 Dialogic Media Engine Licensing... 8 Installing the Second Package Calling into the Video Conference Demo... 9 Useful Tips... 9 Transferring the Second Package to the Linux System from a USB Drive... 9 Transferring the Second Package to the Linux System from a CD... 9 Installing the Bria 3 Video Softphone Manually Running the Video Conferencing Demo Servers DiaStar Server Logging Additional Information

4 Revision History Revision Release date Notes October 2011 Initial release of this document. Refer to for product updates and for information about support policies, warranty information, and service offerings. 4

5 Introduction 1. Introduction The Dialogic Video Conferencing Demo (referred to herein as the Demo) provides several examples of how video conferencing can be deployed using the Dialogic PowerMedia product family. The Demo allows you to demonstrate video conferencing applications for up to 10 (ten) callers on smart phones, tablets, PC clients with soft phones, or IP video phones. The applications developed can be expanded to support larger conferences with up to 240 participants. Figure 1 illustrates an example of a multimedia conferencing solution that is based on the demo. Figure 1. Multimedia Conferencing Solution The current version of the Demo is built using a media server based on the DiaStar Server (DSS), which utilizes the same advanced multimedia processing engine as all Dialogic PowerMedia products. In addition to the DSS, the Demo also includes other Open Source components. This document describes the steps required to install and configure the Demo. The media and application servers reside on the same physical system. Installation of the DSS used in the Demo is done by using an.iso image, which creates a media server based on the DSS. A second package contains the application scripts, an Asterisk application server image, a SIP Registrar and the audio/video media required to run the demo. 5

6 Dialogic Video Conferencing Demo Installation Guide 2. Installation Instructions This chapter provides the steps required to successfully install the Demo. The installation process consists of the following bullet items: Download a single.iso file which contains the Community ENTerprise Operating System (referred to herein as CentOS) and DiaStar Server (DSS) packages Burn the.iso image onto a CD Ensure the system is connected to your network Boot a system from the DSS CD. The CD will install the CentOS 5.5 operating system and everything needed for the media server. Note: The DSS installation will reformat the system hard drive. Perform licensing and configuration Copy on the second package (a compressed Linux tar file) and install the additional application services and media Getting and Preparing the ISO File The.ISO file may be downloaded from Once downloaded, the file must be burned onto a bootable CD. Use a CD drive that has write capabilities, along with the appropriate CD burning software. Note: A bootable ISO image must be created from the downloaded file rather than simply copying the file to the CD. The second package, also be available for downloaded from should be downloaded at the same time. This package contains a collection of files in a Linux tar archive and cannot be made into a bootable image. It simply needs to be copied to the system created from the ISO file. Pre-Installation General Notes and Warnings This section provides information needed prior to continuing with the Demo installation. The Demo should not be installed on any virtual machine that may be on the system. Nor should it be installed on a laptop system. System Requirements The recommended minimum system requirements to install and run the 10-user Demo is as follows: Intel Xeon Processor 2.50 GHz, quad core 4 GB memory (The Demo uses a 32-bit image so more than 4 GB of memory is not required.) 6

7 Installation Instructions Installing the Operating System from the CD Install the Demo according to the following steps: 1. Put the bootable CD in the drive on the system on which the installation will be done and boot the system from the CD. Caution: This install will overwrite everything on the system's hard drive! 2. At the boot prompt, press Enter. Note: Do not use any other possible boot options or the automatic DSS installation will not take place. The installation requires little interaction. The main task is setting up the IP characteristics for the system. The following guidelines are provided: Edit eth0, disable IPv6 and enable IPv4 support. The interface used for DSS must be eth0. Use the manual configuration method to set a static IP address on the system. For a class C network, the netmask of should be used. Change the system name if desired. The system name will default to "diastar". Set the Gateway and DNS server addresses if desired. Once the IP characteristics are complete, the remainder of the installation is "hands off". Be sure to remove the installation CD when the final reboot is finished. Post-Installation For post-operating system installation configuration tasks, access the system either by the terminal used during installation or by secure shell (ssh) access. All post-installation work should be done as user "root". The default root password is "opendialogic". If you wish to change the password, do so before proceeding. Verifying the Installation Once the system has rebooted after the installation, check that the installation was successful. If successful, the following is present: The /usr/dialogic directory, along with its subdirectories, exists. Anaconda, the CentOS system installer, creates its logs in the /root directory. Dialogic system processes are running. A ps ax grep dialogic command, done at the system prompt, shows 11 dialogic processes up and running. Once you have verified the basic installation of the DSS ISO, the system must be licensed to enable the 10 ports of video conferencing. Obtaining a License A 45-day trial license for the Video Conferencing Demo may be obtained by registering at the following URL: Before requesting the license, you should record the MAC address of a working network interface (typically eth0). This can be obtained by calling ifconfig on the system. The license will be locked to this MAC address value. The format of the MAC address is AA:BB:CC:DD:EE:FF. 7

8 Dialogic Video Conferencing Demo Installation Guide Dialogic Media Engine Licensing The Dialogic PowerMedia -based Media Engine used in the DSS has already been installed as part of the ISO install, but for full operation some further configuration is needed. For example, you need to install the DSS Media Engine trial license. Proceed as follows: 1. Once you have obtained your license, copy it into the /usr/dialogic/data directory. 2. Install the license to connect to the Media Engine Command Line Interpreter: # telnet localhost Username is root and the Password is public. 3. Once in the CLI, first make sure that the IP Media subsystem is stopped by entering the following command at the CLI prompt: CLI> conf system ipmedia stop This may take a few minutes. When a confirmation message is received, the license can be applied. 4. Enter the following command: CLI> conf license activate <license_file_name.lic> 5. Set media engine start-up to automatic and start media services as follows: CLI> conf system ipmedia start-mode auto CLI> conf system ipmedia start 6. When media startup has successfully completed, exit the CLI: CLI> quit Installing the Second Package Once there is an operational system, the Video Conferencing Demo software may be installed. The file Video_Conferencing_Demo_Pkg_2.tgz should be copied onto the system. (Refer to Useful Tips for ways of doing this.) Expand the file and invoke the install script: # tar xvf Video_Conferencing_Demo_Kit_Pkg_2.tar # cd Video_Conferencing_Demo_Kit_Pkg_2 # script c./install.sh install.log Answer y when asked if you want to proceed. The final operations will start all needed services and the system will be ready to take a call from a SIP video phone. A record of the installation session will be found in install.log file. You may choose to now install and configure the Bria 3 Softphone (refer to Useful Tips) on another system for accessing the Demo. 8

9 Calling into the Video Conference Demo 3. Calling into the Video Conference Demo The SIP video phone that is used for accessing the Demo must first register with the OpenSIPs SIP server acting as a Registrar. Setting up a SIP phone for registration will vary from phone to phone. When the phone has been successfully registered, dialing 400 will bring up the Dialogic Video Conferencing Demo introduction. From there, a menu listing the four video conferencing demos will be displayed. Using the demos will be explained as you choose them. The demos are as follows: Animal Conference This is a video conference in which you are joined by three talkative animals. PIN-Based Conferencing The first caller is assigned a conference ID number. Up to four subsequent callers entering the same ID are allowed into the same conference room. Conference Recording This demo records and replays a video conference. Controlled Conferencing This demo demonstrates the Dialogic conferencing options that can be used for a conference with a moderator, presenters and view/listen-only attendees Useful Tips This section contains instructions beyond system installation for soft phone installation and configuration and system operation. Transferring the Second Package to the Linux System from a USB Drive It may be convenient to transfer the tar file that makes up the second package to the installed Linux system using a USB drive (memory stick). Assuming the USB drive is formatted with a recognizable Windows or Linux file system, proceed using the following commands: # mkdir /mnt/usb # mount /dev/sdb1 /mnt/usb # cp /mnt/usb/ Video_Conferencing_Demo_Kit_Pkg_2 /tmp # umount /mnt/usb Transferring the Second Package to the Linux System from a CD If the tar file that makes up the second package is on a CD, insert the CD in the system s drive and enter the following commands: # mkdir /mnt/cdrom # mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cp /mnt/cdrom/ Video_Conferencing_Demo_Kit_Pkg_2 /somewhere_else # umount /mnt/cdrom 9

10 Dialogic Video Conferencing Demo Installation Guide Installing the Bria 3 Video Softphone A tested and known working SIP Video Softphone for use with the Dialogic PowerMedia server is the Bria 3, refer to The Softphone is compatible with Windows and MAC and should be installed on a system with a sound card and PC camera. Once the Softphone is installed, the following changes should be made: Softphone > Preferences > Application> Default Action> Make a Video Call Softphone > Preferences > Audio Codecs> G722 enabled (all others disabled) Softphone > Preferences > Video Codecs> H.264 enabled (all others disabled) Softphone > Preferences > Media Quality> Video Quality>Standard Softphone > Account Settings>Add SIP Account User Details> User ID> any name User Details> Domain> IP address of the PowerMedia server Softphone> Account Settings>Enabled (any others disabled) Bria will register with the SIP registrar when started and a call may be made by simply dialing extension 400. Manually Running the Video Conferencing Demo Servers All services needed for the Demo should automatically be started when the system is booted. However, manually starting and stopping the services may sometimes be necessary. To run the DSS and the Asterisk application servers, use the service command: # service service_name command Where service_name is asterisk or diastar and the command is start, stop, or status. Both services must be running for video conferencing to work. # service diastar start # service asterisk start DiaStar Server Logging The default DiaStar Server log location is /var/log/diastar. Multiple log files will be created and each capped at 2MB. The DSS log files should always be consulted when troubleshooting the system. 10

11 Additional Information 4. Additional Information For Dialogic product information, refer to Consult the Project DiaStar Wiki at for more information about: Running the DiaStar system Further DiaStar configuration Configuring Asterisk for use with DiaStar Modifying the demos For Asterisk information and support, go to 11