Pexip Infinity Getting Started Guide

Pexip Infinity Getting Started Guide Intrductin Pexip Infinity is a virtualized and distributed multipint cnferencing platfrm. It enables scaling f vide, vice and data cllabratin acrss rganizatins, enabling everyne t engage in high definitin vide, web, and audi cnferencing. It prvides any number f users with their wn persnal Virtual Meeting Rms, as well as Virtual Auditriums, which they can use t hld cnferences, share presentatins, and chat. Participants can jin ver audi r vide frm any lcatin using virtually any type f cmmunicatins tl (such as Micrsft Lync / Skype fr Business, a traditinal cnferencing endpint, a mbile telephne, r a Pexip Infinity Cnnect client) fr a seamless meeting experience. Virtual Meeting Rms and Virtual Auditriums can als be accessed thrugh a Virtual Receptin IVR service, which allws all participants t dial a single number t access Pexip Infinity, and then use the DTMF tnes n their endpint t select the cnference they want t jin. The platfrm als includes the Pexip Distributed Gateway service, allwing end users t place pintt-pint calls t ther endpints that use different prtcls and media frmats. Pexip Infinity is installed as a Management Nde and ne r mre Cnferencing Ndes. All are virtual machines (VMs) that are deplyed nt hst hardware using hypervisrs r are hsted n a clud platfrm service. The Management Nde is deplyed first, and is then used t cnfigure the Pexip Infinity platfrm and deply Cnferencing Ndes. This guide describes the minimum steps required t deply a Pexip Infinity Management Nde n yur wn hst servers. Full infrmatin n cnfiguring and using Pexip Infinity is available: n the Pexip Infinity technical dcumentatin website (frm where all dcumentatin can als be dwnladed in PDF frmat) as nline help, by clicking the Help link in the tp right crner f the Pexip Infinity Administratr interface (available after the Management Nde has been deplyed). 2016 Pexip AS Versin 12.a May 2016 Page 1 f 21

Prerequisites Prerequisites This sectin lists the prerequisites fr installing the Pexip Infinity versin 12 platfrm n yur wn hst servers. There are further requirements fr deplying the cmplete platfrm in yur netwrk. Fr mre infrmatin, see Pexip Infinity installatin verview. Hst servers The fllwing table lists the recmmended hardware requirements fr the Management Nde and Cnferencing Nde hst servers. Management Nde Cnferencing Nde Server manufacturer Any Any Prcessr make Any Intel Xen E5-2600 series (Haswell architecture) r similar Xen prcessrs frm 2012 r later Prcessr instructin set Any AVX2 Prcessr architecture 64-bit 64-bit Prcessr speed 2.0 GHz 2.3 GHz r faster N. f physical cres* 2 10-12 cres per scket Prcessr cache n minimum 20 MB r greater (2.5 MB L3 cache per cre) Ttal RAM* 4 GB 1 GB per cre RAM makeup Any All channels must be ppulated with a DIMM. Hardware allcatin The hst server must nt be ver-cmmitted in terms f either RAM r CPU. In ther wrds, the Management Nde and Cnferencing Ndes each must have dedicated access t their wn RAM and CPU cres. Strage space required 100 GB SSD 50 GB minimum per Cnferencing Nde 500 GB ttal per server (t allw fr snapshts etc.) GPU Netwrk Operating System N specific hardware cards r GPUs are required. Gigabit Ethernet cnnectivity frm the hst server. The Pexip Infinity VMs are delivered as VM images (.va etc) t be run directly n the hypervisr. N OS shuld be installed. Hypervisr VMware ESXi 4.1**, 5.x r 6.0 Micrsft Hyper-V 2012 r later Xen 4.2 r later KVM (Linux kernel 3.10.0 r later, and QEMU 1.5.0 r later) * This des nt include the prcessr and RAM requirements f the Hypervisr. ** Supprt fr ESXi 4.1 is being deprecated. Sufficient fr deplyments f up t 30 Cnferencing Ndes. Fr larger deplyments, yu will need t increase the amunt f RAM and number f cres. Fr mre infrmatin abut ur server design guidelines, cnsult yur Pexip authrized supprt representative. Fr VMware platfrms, ESXi 6 is required t make full use f the AVX2 instructin set. Nte that AVX is als supprted but we n lnger supprt SSE4.1. Fr further infrmatin, see the Pexip Infinity Server Design Guide. 2016 Pexip AS Versin 12.a May 2016 Page 2 f 21

Prerequisites Hypervisrs Pexip Infinity currently ffers specific supprt fr VMware ESXi, Micrsft Hyper-V, KVM and Xen hypervisrs. Other hypervisrs and rchestratin layers may be used but are nt fficially supprted. If yu wish t deply Pexip Infinity using a nn-supprted hypervisr, we recmmend that yu cntact yur Pexip authrized supprt representative fr assistance. Fr details n installatin using a specific hypervisr, refer t the fllwing sectins: Getting started with VMware Getting started with Hyper-V Getting started with KVM Getting started with Xen Getting started with ther hypervisrs The Pexip Infinity platfrm can als be deplyed as a clud service via Amazn Web Services (AWS) r Micrsft Azure, with private, public r hybrid deplyment ptins. Netwrk requirements Nte that in all Pexip Infinity deplyment scenaris: All Pexip ndes must be fully rutable t each ther (full mesh) in bth directins. This means that the Management Nde must be able t reach every Cnferencing Nde, and each Cnferencing Nde must be able t reach every ther Cnferencing Nde. Any internal firewalls must be cnfigured t allw UDP prt 500 and traffic using IP prtcl 50 (ESP) in bth directins between all Pexip ndes. There cannt be a NAT between any Pexip ndes. 2016 Pexip AS Versin 12.a May 2016 Page 3 f 21

Getting started with VMware Getting started with VMware This sectin describes hw t deply the Pexip Infinity Management Nde n a VMware vsphere hypervisr. Supprted ESXi versins Versin 12 f the Pexip Infinity platfrm supprts VMware vsphere ESXi 5.x and 6.0, althugh we recmmend ESXi 5.5 r 6.0. Supprt fr ESXi 4.1 is being deprecated - if yu have upgraded frm a versin prir t v12, yu can still deply Cnferencing Ndes t servers running ESXi 4.1; hwever if yu have a new deplyment using v12 and attempt t deply a Cnferencing Nde t a server running ESXi 4.1, that nde will g straight int maintenance mde. Yu must have a suitable VMware envirnment already installed. Fr infrmatin n cnfiguring a VMware envirnment specifically fr use with Pexip Infinity, see Advanced VMware ESXi administratin. Supprted VMware editins The Pexip Infinity platfrm will run n the free editin f vsphere Hypervisr. Hwever, this editin has a number f limitatins (limited supprt frm VMware, n access t vcenter r vmtin, n access t VMware API). In particular, the lack f access t the VMware API means that all Cnferencing Ndes will have t be deplyed manually. Fr this reasn we d nt recmmend its use except in smaller deplyments, r test r dem envirnments. The minimum editin f VMware that we recmmend is the vsphere Standard editin. This des nt have the limitatins f the free editin. If yu d nt already use VMware in yur enterprise, the vsphere Essentials Kit is a simple way t get started and will prvide yu with Standard editin licenses fr 3 servers (with 2 CPUs each) plus a vcenter license. The Enterprise Plus editin includes further additinal features relevant t the Pexip Infinity platfrm that culd be f benefit t larger deplyments. These include Strage DRS and Distributed Switch. Fr a cmparisn f the VMware editins, see http://www.vmware.cm/prducts/datacenter-virtualizatin/vsphere/cmpareeditins.html. Synchrnizing time All hst servers must be synchrnized with accurate time befre yu install the Pexip Infinity Management Nde r Cnferencing Ndes n them. NTP must be enabled n the Management Nde befre yu deply any Cnferencing Ndes. We strngly recmmend that yu cnfigure at least three distinct NTP servers r NTP server pls n all yur hst servers and the Management Nde itself. This will ensure that lg entries frm all ndes are prperly synchrnized. The fllwing instructins describe hw t synchrnize time n the hst server using the vsphere desktp client. Yu can als use the vsphere web client fr hsts managed using vcenter; fr instructins n this see Cnfiguring VMware fr Pexip Infinity. T synchrnize time n the hst server using the vsphere desktp client: 1. Lg in t the VM manager (vcenter Server r the ESXi hst). 2. Frm the left-hand panel, select the hst server n which the sftware image is t be installed. 3. Select the Cnfiguratin tab. 4. Frm the Sftware pane n the left-hand side, select Time Cnfiguratin. 5. On the tp right f the page, select Prperties. The Time Cnfiguratin dialg bx appears. 6. In the NTP Cnfiguratin sectin, select NTP Client Enabled. 7. Select Optins. The NTP Daemn (ntpd) Optins dialg bx appears. 8. Frm the left-hand panel, select General. Under Startup Plicy, select Start and stp with hst. 2016 Pexip AS Versin 12.a May 2016 Page 4 f 21

Getting started with VMware 9. Select OK. 10. Select Optins again. The NTP Daemn (ntpd) Optins dialg bx appears. 11. Frm the left-hand panel, select NTP Settings. Under NTP Servers, we strngly recmmend that yu cnfigure at least 3 distinct NTP servers r NTP server pls t ensure that lg entries frm all ndes are prperly synchrnized. 12. Select Restart NTP service t apply changes, and then select OK. T verify that NTP has been enabled crrectly: 1. Select the Cnfiguratin tab. 2. Frm the Sftware pane n the left-hand side, select Time Cnfiguratin. 3. Ensure that value in the Date & Time field is crrect. Installing the Management Nde VM The fllwing instructins describe hw t install the sftware image using the vsphere desktp client. Yu can als use the vsphere web client fr deplyments using vcenter Server; fr instructins n this see Installing the Management Nde (using the vsphere web client). T install a new instance f a Pexip Infinity Management Nde using the vsphere desktp client: 1. Dwnlad the Pexip Infinity OVA file (Pexip_Infinity_v12_generic_pxMgr_<release>.va) frm www.pexip.cm/sftwaredwnlad. 2. Lg in t the VM Manager (vcenter Server r the ESXi hst). 3. Select File > Deply OVF Template... Yu will be taken t the Surce page. 4. Brwse t the lcatin f the Pexip Infinity OVA file and select Next >. Yu will be taken t the OVF Template Details page. 5. Select Next >. Yu will be taken t the End User License Agreement page. 6. Read the license agreement, and if yu agree t the terms select Accept and then Next >. Yu will be taken t the Name and Lcatin page. 7. Enter an apprpriate name fr the Management Nde. This name will be used in the VMware interface t identify this Management Nde virtual machine (VM). 8. Select Next >. Yu will be taken t the Resurce Pl page. 9. Select the resurce pl fr the Pexip Infinity Management Nde. 10. Select Next >. Yu will be taken t the Disk Frmat page. 11. Select Thick Prvisin Lazy Zered. 12. Select Next >. Yu will be taken t the Netwrk Mapping page. 13. Select the apprpriate mappings and select Next >. Yu will be taken t the Ready t Cmplete page. 14. Review the infrmatin and select Pwer n after deplyment. 15. Select Finish. A windw will appear shwing the deplyment prgress. When deplyment is cmplete this will say Cmpleted Successfully. Yu can then Clse the windw. 2016 Pexip AS Versin 12.a May 2016 Page 5 f 21

Getting started with VMware Enabling autmatic startup After deplying a new Management Nde frm VMware, yu must enable autmatic startup f that virtual machine (VM). In VMware, autmatic startup is disabled by default fr every new VM. This means that if the hst server is pwered dwn fr any reasn, when it restarts the VM will nt restart and must be started manually. Yu can nly enable autmatic startup after the Management Nde has been deplyed. T enable autmatic startup using the vsphere desktp client: 1. Lg in t the VM manager (vcenter Server r the ESXi hst). 2. Frm the left-hand panel, select the hst server n which the nde's VM is installed. 3. Select the Cnfiguratin tab. 4. Frm the Sftware pane n the left-hand side, select Virtual Machine Startup/Shutdwn. 5. At the tp right f the page, select Prperties. 6. Select the relevant VM and use the Mve Up buttn t mve it t the Autmatic Startup sectin. 7. Select OK. Opening a cnsle windw t run the installatin wizard T run the installatin wizard, which cnfigures the Management Nde, yu must pen a cnsle windw n the Management Nde VM. T d this: 1. Using either the vsphere desktp r web client, lg in t the Management Nde's VM Manager (vcenter Server r, fr standalne deplyments, the ESXi hst). 2. Pwer n the new Management Nde VM (if it is nt already pwered n). 3. Right-click n the new Management Nde VM and select Open Cnsle. Yu must nw run the installatin wizard. Fr step-by-step instructins, see Running the installatin wizard. Disabling EVC in VMware We strngly recmmend that yu disable EVC (Enhanced vmtin Cmpatibility) fr any ESXi clusters hsting Cnferencing Ndes that include a mix f ld and new CPUs. If EVC is enabled n such clusters, the Pexip Infinity platfrm will run mre slwly because the Cnferencing Ndes will assume they are running n lder hardware. Fr mre infrmatin, see Enhanced vmtin Cmpatibility (EVC). T disable EVC: 1. Lg in t vcenter Server using either the vsphere desktp r web client. 2. Display the cluster in the inventry. 3. Right-click the cluster and select Edit Settings. 4. In the left panel, select VMware EVC. The dialg bx displays the current EVC settings. 5. Select Change EVC Settings. 6. Select Disable EVC. 2016 Pexip AS Versin 12.a May 2016 Page 6 f 21

Getting started with Hyper-V Getting started with Hyper-V This sectin describes hw t deply the Pexip Infinity Management Nde n a Micrsft Hyper-V hypervisr. Supprted Hyper-V versins Versin 12 f Pexip Infinity supprts Micrsft Hyper-V in the frm f Micrsft Hyper-V Server 2012 and later, r Windws Server 2012 and later. Yu must have a suitable Hyper-V envirnment already installed. Fr infrmatin n cnfiguring a Hyper-V envirnment specifically fr use with Pexip Infinity, see Cnfiguring Hyper-V fr Pexip Infinity. Synchrnizing time All hst servers must be synchrnized with accurate time befre yu install the Pexip Infinity Management Nde r Cnferencing Ndes n them. NTP must be enabled n the Management Nde befre yu deply any Cnferencing Ndes. We strngly recmmend that yu cnfigure at least three distinct NTP servers r NTP server pls n all yur hst servers and the Management Nde itself. This will ensure that lg entries frm all ndes are prperly synchrnized. In Hyper-V, all time synchrnizatin is cnfigured using the Active Dmain Cntrller. Yu must ensure that all VMs and hst servers are using the same time. Cnsult yur Hyper-V dcumentatin fr infrmatin n hw t d this in yur envirnment. Installing the Management Nde VM T deply a new instance f a Pexip Infinity Management Nde using Hyper-V: 1. Dwnlad the Pexip Infinity ZIP file (Pexip_Infinity_v12_HyperV_pxMgr_<release>.zip) frm www.pexip.cm/sftwaredwnlad, and extract the files. 2. Lg in t Hyper-V. 3. Right-click n the hst server and select Imprt Virtual Machine... This will start the Imprt Virtual Machine wizard. 4. On the Lcate Flder page, Brwse t the flder cntaining the extracted files and select Next. Yu will be taken t the Select Virtual Machine page. 5. The wizard will autmatically detect the flder and file cntaining the Management Nde VM. Cnfirm that this is crrect and select Next. Yu will be taken t the Chse Imprt Type page. 6. Select the type f imprt mst apprpriate fr yur envirnment (if yu are unsure, select Restre the virtual machine). Select Next. 7. Depending n the imprt type yu have chsen, yu may be asked fr further infrmatin. Fllw the prmpts as required. When the setup is cmplete, yu will be taken t the Cmpleting Imprt Wizard page. 8. Review the summary and select Finish. When the Management Nde VM has been created successfully, it will appear in the list f Virtual Machines. Enabling autmatic startup By default, virtual machines deplyed using Hyper-V are cnfigured t restart autmatically if they were running when the hst server was shut dwn r pwered ff. We recmmend that yu leave this setting as is fr the Management Nde and all Cnferencing Ndes. 2016 Pexip AS Versin 12.a May 2016 Page 7 f 21

Getting started with Hyper-V Opening a cnsle windw t run the installatin wizard T run the installatin wizard, which cnfigures the Management Nde, yu must pen a cnsle windw n the Management Nde VM. T d this: 1. Lg in t Hyper-V. 2. Start the new Management Nde VM (if it is nt already running). 3. Right-click n the new Management Nde VM and select Cnnect... Yu must nw run the installatin wizard. Fr step-by-step instructins, see Running the installatin wizard. 2016 Pexip AS Versin 12.a May 2016 Page 8 f 21

Getting started with KVM Getting started with KVM This sectin describes hw t deply the Pexip Infinity Management Nde n a KVM hypervisr. Prerequisites This guide assumes that yu have a KVM envirnment already installed. Pexip Infinity requires yur KVM envirnment t include Linux kernel 3.10.0 r later, and QEMU 1.5.0 r later. This means the fllwing distributins: Debian 8, RHEL 7, SLES 12, r Ubuntu 14.04 (r later, where apprpriate). Yu must ensure that: the KVM envirnment may be managed thrugh libvirt the virt-manager, virsh and virt-install applicatins are available fr use n the client system that is managing the KVM envirnment; t d this, run the cmmand: sud apt-get install virt-manager libvirt-bin The libvirt cmmand line tls are used t imprt the disk image and create the VM. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. Fr mre infrmatin, see http://libvirt.rg/drvqemu.html. Synchrnizing time All hst servers must be synchrnized with accurate time befre yu install the Pexip Infinity Management Nde r Cnferencing Ndes n them. NTP must be enabled n the Management Nde befre yu deply any Cnferencing Ndes. We strngly recmmend that yu cnfigure at least three distinct NTP servers r NTP server pls n all yur hst servers and the Management Nde itself. This will ensure that lg entries frm all ndes are prperly synchrnized. Install the NTP package n yur hst server using the apprpriate package management tl fr yur Linux distributin. Installing the Management Nde VM T deply a new instance f a Pexip Infinity Management Nde n t a KVM hst, yu must: 1. Dwnlad the Management Nde OVA image file and cnvert it fr use with KVM. 2. Create a new vlume n yur KVM server and uplad the disk image. 3. Create the Management Nde virtual machine. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. 4. Enable the virtual machine fr autmatic startup. These steps are described in detail belw. Dwnlad the Pexip.va image and cnvert it fr use with KVM Yu must dwnlad the Management Nde OVA image file and then, t use it with KVM, yu must cnvert it frm VMDK t raw frmat. Frm within yur KVM envirnment: 1. Dwnlad the Pexip Infinity OVA file (Pexip_Infinity_v12_generic_pxMgr_<release>.va) frm www.pexip.cm/sftwaredwnlad. 2. Unpack the.va image, using the cmmand: tar xf Pexip_Infinity_v12_generic_pxMgr_<release>.va 2016 Pexip AS Versin 12.a May 2016 Page 9 f 21

Getting started with KVM This unpacks a set f files including pexipmcumgr-disk01.vmdk. 3. If required, yu can verify the pexipmcumgr.mf manifest file, using the cmmand: sha1sum -c pexipmcumgr.mf 4. Cnvert the disk image frm VMDK t raw, using the cmmand: qemu-img cnvert -O raw pexipmcumgr-disk01.vmdk pexipmcumgr-disk01.raw (This cnversin prcess can take several secnds.) Create a new vlume and uplad the disk image Next, yu create a new vlume n yur KVM server and uplad the cnverted disk image. Frm within yur KVM envirnment: 1. Use virsh t create a new vlume n yur KVM server: virsh --cnnect qemu://<hstname>/system vl-create-as <plname> <vlume_name> 99G --frmat raw where: <hstname> is the hstname f yur KVM server. Nte that yu can mit the <hstname> if yu are running virsh cmmands n the lcal server i.e. yu can use virsh --cnnect qemu:///system. <plname> is the name f the strage pl in which t create the vlume; typically yu wuld use default. (T determine the strage pls available n the target system, use virsh --cnnect qemu://<hstname>/system pl-list.) <vlume_name> is the name f yur new vlume. 99G is the virtual size f the vlume; always use 99G fr a Management Nde. Fr example: virsh --cnnect qemu://hst1.example.cm/system vl-create-as default pexip-manager 99G --frmat raw This example creates a vlume named pexip-manager f size 99 GB and frmat raw in the strage pl named default. 2. Uplad the cnverted disk image t the newly created vlume: virsh --cnnect qemu://<hstname>/system vl-uplad <vlume_name> pexipmcumgr-disk01.raw --pl <plname> Fr example: virsh --cnnect qemu://hst1.example.cm/system vl-uplad pexip-manager pexipmcumgr-disk01.raw --pl default This example uplads the pexipmcumgr-disk01.raw image t the newly created vlume, pexip-manager, in the strage pl named default. Create the virtual machine After the disk image has been upladed, yu can create the virtual machine t use it. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. 1. Identify the filesystem path f the newly upladed disk image: virsh --cnnect qemu://<hstname>/system vl-path <vlume_name> --pl <plname> Fr example: virsh --cnnect qemu://hst1.example.cm/system vl-path pexip-manager --pl default This prints ut the abslute path t the disk image file, fr example: /var/lib/libvirt/images/pexip-manager This path is used in the disk path parameter in the next step. 2. Use the virt-install cmmand line tl t create the virtual machine: virt-install \ --imprt \ --hvm \ --name=<vm_name> \ --arch=x86_64 \ --vcpus=2 \ --ram=4096 \ --cpu hst \ --s-type=linux \ --cnnect=qemu://<hstname>/system \ --virt-type kvm \ --disk path=<image_file_path>,bus=virti,frmat=raw,cache=nne,i=native \ --netwrk bridge=br0,mdel=virti \ 2016 Pexip AS Versin 12.a May 2016 Page 10 f 21

Getting started with KVM --memballn virti \ --graphics vnc,listen=0.0.0.0,passwrd=<passwrd> This creates a new VM (KVM dmain) frm the cnverted disk image. The meaning f the varius ptins are as fllws (items in bld may be changed as necessary): Optin --imprt --hvm --name=<vm_name> --arch=x86_64 --vcpus=2 --ram=4096 --cpu hst --s-type=linux -- cnnect= qemu://<hstname>/system --virt-type kvm Descriptin Build guest dmain arund pre-installed disk image; d nt attempt t install a new OS. Create a fully virtualized (i.e. nt paravirtualized) VM. Name f the new VM, where <vm_name> is, fr example, pexip-management-vm. CPU architecture f new VM (must be x84_64). Number f CPUs allcated t new VM. Typically, this is 2 fr the Management Nde. Memry allcated t new VM (in megabytes). Expse all hst CPU capabilities t new VM (CPUID). The guest OS is Linux. Cnnect t KVM n the target system, where <hstname> is the hstname f yur KVM server. Use KVM t hst the new VM. --disk path=<image_file_path>, bus=virti,frmat=raw,cache=nne,i=native --netwrk bridge=br0,mdel=virti Define the lcatin f the disk image file, where <image_file_path> is as determined in the previus step, fr example /var/lib/libvirt/images/pexip-manager. Expse it t the guest n the virti paravirtualized bus (as ppsed t IDE/SCSI). Define the image file as being in raw frmat. Instruct the hst system nt t cache the disk cntents in memry. Use the native IO backend t access the disk device. Create a netwrk interface cnnected t the br0 bridge interface n the hst. Expse it t the guest as a virti paravirtualized NIC. --memballn virti --graphics vnc,listen=0.0.0.0, passwrd=<passwrd> Expse the virti memry balln t the guest. Expse the graphical cnsle ver VNC, listening n 0.0.0.0 (i.e. all addresses n the target system) and with an access passwrd f <passwrd>. Yu may receive a warning "Unable t cnnect t graphical cnsle: virt-viewer nt installed"; if s, this message can be safely ignred. After the VM has been created, it may be managed using the Virtual Machine Manager desktp interface (virt-manager applicatin) r via the cmmand line interface (virsh). The new nde shuld start autmatically. If it des nt yu can use the Virtual Machine Manager t start the nde, r the CLI cmmand: virsh --cnnect qemu://<hstname>/system start <vm_name> Nte that yu can list existing VMs by using virsh --cnnect qemu://<hstname>/system list Enabling autmatic startup After deplying a new Management Nde in KVM, yu shuld enable autmatic startup f that virtual machine (VM). In KVM, autmatic startup is disabled by default fr every new VM. This means that if the hst server is pwered dwn fr any reasn, when it restarts the VM will nt restart and must be started manually. Yu can nly enable autmatic startup after the Management Nde has been deplyed. 2016 Pexip AS Versin 12.a May 2016 Page 11 f 21

Getting started with KVM T enable autmatic startup using Virtual Machine Manager: 1. Cnnect t the Virtual Machine Manager (virt-manager) that is managing the nde's VM. 2. Select the nde's VM and then, frm the tlbar, select the Shw the virtual machine cnsle and details icn. A new windw fr that VM is pened. 3. If necessary, select View > Details t display the VM infrmatin. 4. Frm the sidebar menu, select Bt Optins. 5. Select the Start virtual machine n hst bt up check bx. 6. Select Apply. Opening a cnsle windw t run the installatin wizard T run the installatin wizard, which cnfigures the Management Nde, yu must pen a cnsle windw n the Management Nde VM. T d this: 1. Cnnect t Virtual Machine Manager (virt-manager) that is managing the Management Nde's VM. 2. Ensure that the Management Nde VM is Running. 3. Select the new Management Nde VM and then, frm the tlbar, select the Shw the virtual machine cnsle and details icn. A new windw fr that VM is pened. 4. If necessary, select View > Cnsle t display the cnsle. Yu must nw run the installatin wizard. Fr step-by-step instructins, see Running the installatin wizard. 2016 Pexip AS Versin 12.a May 2016 Page 12 f 21

Getting started with Xen Getting started with Xen This sectin describes hw t deply the Pexip Infinity Management Nde n a Xen hypervisr. Prerequisites This guide assumes that yu have a Xen envirnment already installed. Pexip Infinity requires Xen 4.2 and later. Yu must ensure that: the Xen envirnment may be managed thrugh libvirt the virt-manager, virsh and virt-install applicatins are available fr use n the client system that is managing the Xen envirnment; t d this, run the cmmand: sud apt-get install virt-manager libvirt-bin The libvirt cmmand line tls are used t imprt the disk image and create the VM. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. Fr mre infrmatin, see http://libvirt.rg/drvxen.html. Synchrnizing time All hst servers must be synchrnized with accurate time befre yu install the Pexip Infinity Management Nde r Cnferencing Ndes n them. NTP must be enabled n the Management Nde befre yu deply any Cnferencing Ndes. We strngly recmmend that yu cnfigure at least three distinct NTP servers r NTP server pls n all yur hst servers and the Management Nde itself. This will ensure that lg entries frm all ndes are prperly synchrnized. Install the NTP package n yur hst server using the apprpriate package management tl fr yur Linux distributin. Installing the Management Nde VM T deply a new instance f a Pexip Infinity Management Nde n t a Xen hst, yu must: 1. Dwnlad the Management Nde OVA image file and cnvert it fr use with Xen. 2. Create a new vlume n yur Xen server and uplad the disk image. 3. Create the Management Nde virtual machine. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. 4. Enable the virtual machine fr autmatic startup. These steps are described in detail belw. Dwnlad the Pexip.va image and cnvert it fr use with Xen Yu must dwnlad the Management Nde OVA image file and then, t use it with Xen, yu must cnvert it frm VMDK t raw frmat. Frm within yur Xen envirnment: 1. Dwnlad the Pexip Infinity OVA file (Pexip_Infinity_v12_generic_pxMgr_<release>.va) frm www.pexip.cm/sftwaredwnlad. 2. Unpack the.va image, using the cmmand: tar xf Pexip_Infinity_v12_generic_pxMgr_<release>.va This unpacks a set f files including pexipmcumgr-disk01.vmdk. 3. If required, yu can verify the pexipmcumgr.mf manifest file, using the cmmand: 2016 Pexip AS Versin 12.a May 2016 Page 13 f 21

Getting started with Xen sha1sum -c pexipmcumgr.mf 4. Cnvert the disk image frm VMDK t raw, using the cmmand: qemu-img cnvert -O raw pexipmcumgr-disk01.vmdk pexipmcumgr-disk01.raw (This cnversin prcess can take several secnds.) Create a new vlume and uplad the disk image Next, yu create a new vlume n yur Xen server and uplad the cnverted disk image. Frm within yur Xen envirnment: 1. Use virsh t create a new vlume n yur Xen server: virsh --cnnect xen://<hstname>/ vl-create-as <plname> <vlume_name> 99G --frmat raw where: <hstname> is the hstname f yur Xen server. Nte that yu can mit the <hstname> if yu are running virsh cmmands n the lcal server i.e. yu can use virsh --cnnect xen:///. <plname> is the name f the strage pl in which t create the vlume; typically yu wuld use default. (T determine the strage pls available n the target system, use virsh --cnnect xen://<hstname>/ pl-list.) <vlume_name> is the name f yur new vlume. 99G is the virtual size f the vlume; always use 99G fr a Management Nde. Fr example: virsh --cnnect xen://hst1.example.cm/ vl-create-as default pexip-manager 99G --frmat raw This example creates a vlume named pexip-manager f size 99 GB and frmat raw in the strage pl named default. 2. Uplad the cnverted disk image t the newly created vlume: virsh --cnnect xen://<hstname>/ vl-uplad <vlume_name> pexipmcumgr-disk01.raw --pl <plname> Fr example: virsh --cnnect xen://hst1.example.cm/ vl-uplad pexip-manager pexipmcumgr-disk01.raw --pl default This example uplads the pexipmcumgr-disk01.raw image t the newly created vlume, pexip-manager, in the strage pl named default. Create the virtual machine After the disk image has been upladed, yu can create the virtual machine t use it. Nte that we use the libvirt cmmand line tls t perfrm the imprt as they prvide greater cntrl than Virtual Machine Manager. 1. Identify the filesystem path f the newly upladed disk image: virsh --cnnect xen://<hstname>/ vl-path <vlume_name> --pl <plname> Fr example: virsh --cnnect xen://hst1.example.cm/ vl-path pexip-manager --pl default This prints ut the abslute path t the disk image file, fr example: /var/lib/libvirt/images/pexip-manager This path is used in the disk path parameter in the next step. 2. Use the virt-install cmmand line tl t create the virtual machine: virt-install \ --imprt \ --hvm \ --name=<vm_name> \ --arch=x86_64 \ --vcpus=2 \ --ram=4096 \ --s-type=linux \ --cnnect=xen://<hstname>/ \ --virt-type xen \ --disk path=<image_file_path>,bus=xen,frmat=raw,driver_name=qemu,cache=nne,i=native \ --netwrk bridge=xenbr0,mdel=e1000 \ --memballn xen \ --graphics vnc,listen=0.0.0.0,passwrd=<passwrd> This creates a new VM (Xen dmain) frm the cnverted disk image. The meaning f the varius ptins are as fllws (items in bld may be changed as necessary): 2016 Pexip AS Versin 12.a May 2016 Page 14 f 21

Getting started with Xen Optin --imprt --hvm --name=<vm_name> --arch=x86_64 --vcpus=2 --ram=4096 --s-type=linux -- cnnect= xen://<hstname>/ --virt-type xen Descriptin Build guest dmain arund pre-installed disk image; d nt attempt t install a new OS. Create a fully virtualized (i.e. nt paravirtualized) VM. Name f the new VM, where <vm_name> is, fr example, pexip-management-vm. CPU architecture f new VM (must be x84_64). Number f CPUs allcated t new VM. Typically, this is 2 fr the Management Nde. Memry allcated t new VM (in megabytes). The guest OS is Linux. Cnnect t Xen n the target system, where <hstname> is the hstname f yur Xen server. Use Xen t hst the new VM. --disk path=<image_file_ path>, bus=xen,frmat=raw, driver_ name=qemu,cache=nne,i=native --netwrk bridge= xenbr0,mdel=e1000 Define the lcatin f the disk image file, where <image_file_path> is as determined in the previus step, fr example /var/lib/libvirt/images/pexip-manager. Expse it t the guest n the xen paravirtualized bus (as ppsed t IDE/SCSI). Define the image file as being in raw frmat and the driver as qemu. Instruct the hst system nt t cache the disk cntents in memry. Use the native IO backend t access the disk device. Create a netwrk interface cnnected t the xenbr0 bridge interface n the hst. Expse it t the guest as an e1000 NIC. --memballn xen --graphics vnc,listen=0.0.0.0, passwrd=<passwrd> Expse the xen memry balln t the guest. Expse the graphical cnsle ver VNC, listening n 0.0.0.0 (i.e. all addresses n the target system) and with an access passwrd f <passwrd>. Yu may receive a warning "Unable t cnnect t graphical cnsle: virt-viewer nt installed"; if s, this message can be safely ignred. After the VM has been created, it may be managed using the Virtual Machine Manager desktp interface (virt-manager applicatin) r via the cmmand line interface (virsh). The new nde shuld start autmatically. If it des nt yu can use the Virtual Machine Manager t start the nde, r the CLI cmmand: virsh --cnnect xen://<hstname>/ start <vm_name> Nte that yu can list existing VMs by using virsh --cnnect xen://<hstname>/ list Enabling autmatic startup After deplying a new Management Nde in Xen, yu shuld enable autmatic startup f that virtual machine (VM). In Xen, autmatic startup is disabled by default fr every new VM. This means that if the hst server is pwered dwn fr any reasn, when it restarts the VM will nt restart and must be started manually. Yu can nly enable autmatic startup after the Management Nde has been deplyed. T enable autmatic startup using Virtual Machine Manager: 1. Cnnect t the Virtual Machine Manager (virt-manager) that is managing the nde's VM. 2. Select the nde's VM and then, frm the tlbar, select the Shw the virtual machine cnsle and details icn. A new windw fr that VM is pened. 2016 Pexip AS Versin 12.a May 2016 Page 15 f 21

Getting started with Xen 3. If necessary, select View > Details t display the VM infrmatin. 4. Frm the sidebar menu, select Bt Optins. 5. Select the Start virtual machine n hst bt up check bx. 6. Select Apply. Opening a cnsle windw t run the installatin wizard T run the installatin wizard, which cnfigures the Management Nde, yu must pen a cnsle windw n the Management Nde VM. T d this: 1. Cnnect t Virtual Machine Manager (virt-manager) that is managing the Management Nde's VM. 2. Ensure that the Management Nde VM is Running. 3. Select the new Management Nde VM and then, frm the tlbar, select the Shw the virtual machine cnsle and details icn. A new windw fr that VM is pened. 4. If necessary, select View > Cnsle t display the cnsle. Yu must nw run the installatin wizard. Fr step-by-step instructins, see Running the installatin wizard. 2016 Pexip AS Versin 12.a May 2016 Page 16 f 21

Getting started with ther hypervisrs Getting started with ther hypervisrs Pexip Infinity currently ffers specific supprt fr VMware ESXi, Micrsft Hyper-V, KVM and Xen hypervisrs. Other hypervisrs and rchestratin layers may be used but are nt fficially supprted. If yu wish t deply Pexip Infinity using a nn-supprted hypervisr, we recmmend that yu cntact yur Pexip authrized supprt representative fr assistance. Sme basic guidance is given belw. Refer t yur hypervisr's dcumentatin fr cmplete instructins n hw t perfrm these tasks. Static IP addressing Pexip Infinity Management Ndes and Cnferencing Ndes supprt static IP addressing nly. Therefre the hypervisr r rchestratin layer must als supprt static IP addressing. Synchrnizing time All hst servers must be synchrnized with accurate time befre yu install the Pexip Infinity Management Nde r Cnferencing Ndes n them. NTP must be enabled n the Management Nde befre yu deply any Cnferencing Ndes. We strngly recmmend that yu cnfigure at least three distinct NTP servers r NTP server pls n all yur hst servers and the Management Nde itself. This will ensure that lg entries frm all ndes are prperly synchrnized. Installing the Management Nde VM T install a new instance f a Management Nde VM: 1. Dwnlad the Pexip Infinity OVA file (Pexip_Infinity_v12_generic_pxMgr_<release>.va) frm www.pexip.cm/sftwaredwnlad. 2. Use this file t create an instance f a Management Nde VM. Opening a cnsle windw t run the installatin wizard T run the installatin wizard, which cnfigures the Management Nde, yu must pen a cnsle windw n the Management Nde VM. Yu must then run the installatin wizard. Fr step-by-step instructins, see Running the installatin wizard. 2016 Pexip AS Versin 12.a May 2016 Page 17 f 21

Running the installatin wizard Running the installatin wizard When yu have pened a cnsle windw n the Management Nde VM, the fllwing prmpt will appear: pexipmcumgr lgin: T run the installatin wizard: 1. At the prmpt, enter the username admin. The display will read: Yu are required t change yur passwrd immediately (rt enfrced) Enter new UNIX passwrd: 2. Create a passwrd fr the Management Nde perating system by typing the passwrd, pressing enter, retyping the passwrd, and pressing enter again. 3. Ensure yu recrd the passwrd in a secure lcatin. After yu have finished running the installatin wizard yu will nt need the passwrd again unless yu need t access the Management Nde using SSH. Yu are presented with anther lgin prmpt: Running Pexip installatin wizard... [sud] passwrd fr admin: 4. Lg in again with the passwrd yu just created. The Pexip installatin wizard will begin. 5. Fllw the prmpts t set the fllwing cnfiguratin fr the Management Nde. If yu press enter, the default value will be applied: Setting Default value Multiple entries allwed? Can be changed via Pexip Infinity Administratr interface? IP address 192.168.0.100 * N N Netwrk mask 255.255.255.0 * N N Gateway 192.168.0.1 * N N Hstname <n default> N N Dmain suffix <n default> N N DNS servers 8.8.8.8 Yes, if separated by a space Yes NTP servers Tw f the fllwing: Yes, if separated by a space Yes 0.pexip.pl.ntp.rg 1.pexip.pl.ntp.rg 2.pexip.pl.ntp.rg 3.pexip.pl.ntp.rg Web administratin username admin N N Web administratin passwrd <n default> N Yes Enable incident reprting (yes/n) <n default> Yes 2016 Pexip AS Versin 12.a May 2016 Page 18 f 21

Running the installatin wizard Setting Default value Multiple entries allwed? Can be changed via Pexip Infinity Administratr interface? Send deplyment and usage statistics t Pexip (yes/n) <n default> Yes * These defaults apply nly if yur netwrk des nt have DHCP enabled. If DHCP is enabled, the defaults will be thse allcated by the DHCP server. The addresses yu enter using this wizard will be assigned as static IP addresses. The NTP server must be accessible by the Management Nde at the time the startup wizard is run. Installatin will fail if the Management Nde is unable t synchrnize its time with an NTP server. After they have been cnfigured, d nt attempt t change these settings by any ther means. T change these settings n serverbased deplyments, yu must re-run the installatin wizard. T change these settings n clud-based deplyments (AWS r Azure), yu must terminate the existing instance and deply a new Management Nde instance. The installatin will begin and the Management Nde will restart using the values yu have cnfigured. When the Management Nde has restarted the cnsle will display a lgin prmpt: <hstname> lgin: At this pint yu can clse the cnsle. All further cnfiguratin shuld nw be dne using the Administratr interface (if yu encunter SSL cnnectin errrs when using the Administratr interface, wait a few secnds t allw the relevant services t start befre trying again). Next steps After yu have run the installatin wizard, all further cnfiguratin shuld be dne using the Pexip Infinity Administratr interface. See Next steps after running the installatin wizard. 2016 Pexip AS Versin 12.a May 2016 Page 19 f 21

Next steps after running the installatin wizard Next steps after running the installatin wizard After yu have run the installatin wizard, all further cnfiguratin shuld be dne using the Pexip Infinity Administratr interface. Accessing the Pexip Infinity Administratr interface The Pexip Infinity Administratr interface is hsted n the Management Nde. T access this: 1. Open a web brwser and type in the IP address r DNS name that yu assigned t the Management Nde using the installatin wizard (yu may need t wait a minute r s after installatin is cmplete befre yu can access the Administratr interface). 2. Until yu have upladed apprpriate TLS certificates t the Management Nde, yur brwser may present yu with a warning that the website's security certificate is nt trusted. Yu shuld prceed, but uplad apprpriate TLS certificates t the Management Nde (and Cnferencing Ndes, when they have been created) as sn as pssible. The Pexip Infinity Cnferencing Platfrm lgin page will appear. 3. Lg in using the web administratin username and passwrd yu set using the installatin wizard. Yu are nw ready t begin cnfiguring the Pexip Infinity service and deplying Cnferencing Ndes. Befre yu can begin t use the Pexip Infinity service, yu must: cnfigure the Pexip Infinity platfrm Yu may als want t: integrate the Pexip Infinity platfrm with yur call cntrl system cnfigure the Pexip Distributed Gateway register devices directly t the Pexip Infinity platfrm Brief details f hw t perfrm these steps are given belw. Fr cmplete infrmatin n hw t cnfigure yur Pexip Infinity slutin, see the Pexip Infinity technical dcumentatin website at dcs.pexip.cm. Cnfiguring the Pexip Infinity platfrm Frm the Pexip Infinity Administratr interface, yu must: Task Add details f a VM manager (applies t VMware envirnments nly) (System cnfiguratin > VM Managers) Add licenses (Platfrm cnfiguratin > Licenses) Add a system lcatin (Platfrm cnfiguratin > Lcatins) Deply Cnferencing Ndes (Platfrm cnfiguratin > Cnferencing Ndes) Uplad TLS certificates (Platfrm cnfiguratin > TLS certificates) Add Virtual Meeting Rms and/r Virtual Auditriums (Service cnfiguratin > Virtual Meeting Rms) (Service cnfiguratin > Virtual Auditriums) Ntes This is the address f the applicatin t use when autmatically deplying yur Cnferencing Ndes. It is yur vcenter Server, r if yu are nt using vcenter, it is vsphere n the ESXi hst. Yu must install a system license with sufficient cncurrent call capacity fr yur envirnment befre yu can place calls t Pexip Infinity services. These are labels that allw yu t grup tgether Cnferencing Ndes that are in the same datacenter. These handle the call signaling and media and get their Virtual Meeting Rm settings frm the Management Nde. Yu must install TLS certificates n the Management Nde and each Cnferencing Nde. TLS certificates are used by these systems t verify their identity t clients cnnecting t them. Cnferences take place in Virtual Meeting Rms and Virtual Auditriums. Cnfiguratin includes any PINs required t access the cnference. 2016 Pexip AS Versin 12.a May 2016 Page 20 f 21

Next steps after running the installatin wizard Task Add ne r mre aliases fr each Virtual Meeting Rm and Virtual Auditrium (dne while adding the Virtual Meeting Rm r Virtual Auditrium) Make a test call Ntes A Virtual Meeting Rm r Virtual Auditrium can have mre than ne alias. Cnference participants can access a Virtual Meeting Rm r Virtual Auditrium by dialing any ne f its aliases directly. When yu have deplyed a Cnferencing Nde and cnfigured a Virtual Meeting Rm and an alias, yu can make a test call t check that yur system is wrking. An easy way t d this is by using the Infinity Cnnect Web App t dial the cnference alias. Integrating with a call cntrl system T integrate Pexip Infinity with yur call cntrl system, yu must cnfigure a trunk r neighbr zne twards each f the Cnferencing Ndes. Fr further infrmatin abut hw t cnfigure yur specific call management system t wrk with Pexip Infinity, see the fllwing dcumentatin: Pexip Infinity and Micrsft Lync / Skype fr Business Deplyment Guide Pexip Infinity and Cisc VCS Deplyment Guide Pexip Infinity and Cisc Unified Cmmunicatins Manager Deplyment Guide Pexip Infinity and Plycm DMA Deplyment Guide Cnfiguring the Pexip Distributed Gateway The Pexip Distributed Gateway service enables endpints t make calls t ther devices r systems that use different prtcls and media frmats. Fr mre infrmatin, see Registering devices t Pexip Infinity. Registering devices directly t the Pexip Infinity platfrm SIP and H.323 endpints, and sme Infinity Cnnect clients can register directly t Pexip Infinity Cnferencing Ndes. This allws Pexip Infinity t rute utbund calls t thse registered devices withut having t g via a SIP prxy r H.323 gatekeeper, r rely n DNS. Fr mre infrmatin, see Registering devices t Pexip Infinity. 2016 Pexip AS Versin 12.a May 2016 Page 21 f 21