pexip infinity administrator guide v4 a

Pexip Infinity

Administrator Guide

Software Version 4

Document Version 4.a

April 2014

Pexip Infinity Administrator Guide

© 2014 Pexip AS Version 4.a April 2014 of 213

Contents

About the Pexip Infinity platform 12

Introduction 13

Pexip Infinity version 4 features and specifications 14

Pexip Infinity screen layouts 19

Standard Pexip layout 19

1+21 layout 20

Changing aspect ratios 21

Presentations 21Pexip Infinity 21

Endpoints 21

Main video 21

Pexip Infinity components 22

Overview 22

Management Node 22

Conferencing Node 23

Pexip Mobile App 23

Pexip Web App 23

Virtual Meeting Rooms and Virtual Auditoriums 23

Virtual Receptions 23

Pexip Distributed Gateway 24

Host servers 24

Hypervisors 24VM Managers 24

Pexip Infinity architecture 25

Conference distribution 25Locally distributed 25

Globally distributed 25

Locally and globally distributed 26

Bandwidth management 26Bandwidth usage 26

Downspeeding 28

Bandwidth restrictions 28

Internal encryption 28

Endpoints 29

Using a gatekeeper to route calls to Pexip Infinity conferences 29

Load balancing 29

Redundancy 29



Management Node 29

Conferencing Node 29

Scalability 29

Handling of media and signaling in locally distributed conferences 29Example 30

Getting started 31

Prerequisites 32

Hardware requirements 32

Hypervisors 33VMware vSphere ESXi 33

VMware versions 33

VMware editions 33

Microsoft Hyper-V 33

Other hypervisors and orchestration layers 33

Network requirements 33Call control 33

Lync server 34

Implementing a dial plan 35

Using a standard format for aliases 35

Routing calls to the local Conferencing Node 35

Further information 35

Overview of installation 36

About the Pexip Infinity software files 37

Pexip Infinity software files 37

Other files generated by the Pexip Infinity 37

Configuring VMware 38

Synchronizing time 38Using the desktop client 38

Using the web client 38

Enabling automatic startup 39


Using the desktop client 39

Disabling EVC 40

Configuring Hyper-V 41

Synchronizing time 41

Creating an external virtual switch 41

Installing the Management Node 42

Deploying the Management Node template 42



Deployment using VMware 42

Using the vSphere desktop client 42

Using the vSphere web client 43

Deployment using Microsoft Hyper-V 44

Deployment using other hypervisors 44

Running the installation wizard 44Opening a console window 44

Opening a console window in vSphere 44

Opening a console window in Hyper-V 45

Running the installation wizard 45

Re-running the installation wizard 46

Using the Pexip Infinity web interface 48

Accessing the Management Node web interface 48

Session timeout 48

Getting help 48Field-level help 48

Context-sensitive help 48

Contacting support 48

Managing the Pexip Infinity 49

Enabling DNS 50

Enabling NTP on the Management Node 51

Enabling SNMP 52

About Pexip Infinity SNMP support 52

Adding SNMP NMSs 53

Enabling SNMP on the Management Node 53

Enabling SNMP on Conferencing Nodes 54

Using a syslog server 55

About VM Managers 56

Adding VM Managers 57

About system locations 58

Intelligent routing 58

Configuring external services 58H.323 gatekeepers, SIP proxies and Lync servers 58

TURN servers 58

SNMP NMSs 58

Adding system locations 59

About H.323 gatekeepers and SIP proxies 60



About Lync servers 61

About TURN servers 62

Editing the Management Node 63

Enabling automatic startup 65



About Conferencing Nodes 66

About maintenance mode 66

Deploying new Conferencing Nodes 67

Prerequisites 67

Deployment types 67

Automatically deploying a new Conferencing Node 68

Manually deploying a Conferencing Node on an ESXi host 71

Manually deploying a Conferencing Node on a Hyper-V host 73

Deploying a Conferencing Node using a VM template and configuration file 74Prerequisites 75

Deployment process 75

Assigning hostnames and FQDNs 77

Adding SNMP information 77

Enabling automatic startup 78Hyper-V 78

ESXi 78



Editing existing Conferencing Nodes 79

SIP TLS FQDN 80

Changing IP address 80

Deleting Conferencing Nodes 81

About licenses 82

License allocation 82

Viewing existing licenses 82

Adding licenses 82

Manually activating a stored license request 83

Deactivating a license 83

Repairing a license 83

Content of the license request XML file 84

Insufficient versus invalid licenses 84

Managing TLS certificates 85

About TLS certificates 85



Process for encrypting communication using TLS 85

Uploading TLS certificates 86

Viewing existing TLS certificates 86

Downloading existing TLS certificates 86

About trusted CA certificates 86

Downloading trusted CA certificates 86

Uploading trusted CA certificates 87

Managing Virtual Meeting Rooms, Virtual Auditoriums and Virtual Receptions 88

About Pexip Infinity services 89

About Virtual Meeting Rooms 90

Viewing all Virtual Meeting Rooms 91

Creating and editing Virtual Meeting Rooms 92

About Virtual Auditoriums 95

Creating and editing Virtual Auditoriums 96

About the Virtual Reception 99

Creating a Virtual Reception 99

Example 100Step 1: Create a Virtual Reception 100

Step 2: Add aliases to Virtual Meeting Rooms and Virtual Auditoriums 101

About aliases 103

Restrictions 103

Case insensitivity 103

Ignoring IP addresses 103

Using IP addresses as aliases 104

Ignoring protocol prefixes 104

Search rules and alias transforms 104

ENUM 104

Domains 105

Using multiple aliases 106

Adding additional aliases 106

Examples 106

Viewing all aliases 107

Creating and editing aliases 108

About PINs, hosts and guests 109

Using the same PIN for all participants 109

Using PINs to differentiate between hosts and guests 109Guest privileges 109

Host privileges 109

Host and guest PINs 110



Creating a hosted Virtual Meeting Room or Virtual Auditorium 110

How to combine Host PINs and Guest PINs for differing levels of security 110

Changing the layout seen by participants 112

Host view 112

Guest view 112

Changing from a Virtual Meeting Room to a Virtual Auditorium and vice versa 113

Customizing video and voice prompts using themes 114

File requirements 114Images 114

Sounds 114

Downloading an existing theme 114

Creating a new theme 115

Automatically generating the PIN entry screens 115

Contents of the default theme .ZIP file 117Audio files 117

Image files 118

Automatically dialing out to a participant from a conference 120

Manually dialing out to a participant from a conference 122

Using the Administrator interface 122

Using the Pexip Web App 123

Using the Pexip Mobile App 123

Restricting call bandwidth 125

Muting a participant's audio 126




Disconnecting a participant 128




Bulk importing of Virtual Meeting Rooms and Virtual Auditoriums 129

Preparing the CSV file 129Format 129

Duplicates 131

Restrictions 131

Examples 131

Importing the CSV file 131

Exporting Virtual Meeting Room configuration 132

Using the Pexip Distributed Gateway service 133



How it works 134

Adding Gateway Routing Rules 135

Example 136

Viewing status 137

Viewing current conference status 138

Participants 138

Backplanes 139Backplane media streams 140

Graph 140

Viewing participant status 141

Participant details 141Media streams 144

Viewing Conferencing Nodes 147

Viewing historical information about conferences 148

Viewing historical information about participants 150

Viewing Conferencing Node usage statistics 153

Viewing graphs 153

Viewing source data 153

About the support log 154

File size 154

Viewing the support log 154

About the administrator log 156

Log size 156

Viewing the administrator log 156

Maintenance 157

Setting and changing usernames and passwords 158

Pexip Infinity web interface 158

Changing the Management Node operating system password 158

Conferencing Node operating system password 158

Forgotten passwords 158

Upgrading the Pexip Infinity 159

About the automatic upgrade process 159

When to upgrade 159

Upgrading from version 3 to version 4 159Error messages during upgrade 160

Upgrading from version 2 to version 4 160

Upgrading from version 1.0 to version 4 160

Upgrading configuration-only deployments 161



Definition of upgrade statuses 161

Recovering from a failed upgrade 161

Checking the installed version 162Management Node 162

Conferencing Nodes 162

Migrating Conferencing Nodes between host servers 163

Prerequisites 163

Manual migration 163

Automatic migration 163

Taking a Conferencing Node out of service 164

Backing up and restoring configuration 165

Management Node 165

Conferencing Nodes 165

Downloading a diagnostic snapshot 166

File contents 166

File size 166

Automatically reporting errors 167

Content of incident reports 167

Enabling and disabling automatic sending of incident reports 167


Obtaining Virtual Meeting Room URLs 169

Accessing a Virtual Meeting Room or Virtual Auditorium 170

During a conference 171

Using the Pexip Web App to share your screen 172

Enabling screen sharing in Chrome 172

Sharing your screen when using the Pexip Web App as your video endpoint 173

Sharing your screen when using another video endpoint 173

Viewing a list of other conference participants 174

Adding a participant to the conference 174

Muting other participants 175

Disconnecting other participants 176

Using the Pexip Web App to make a point-to-point call 177


About the Pexip Mobile App 179

Setting up DNS records for Pexip Mobile App use 180

Example 180

Installing the Pexip Mobile App 181



Pexip Mobile App for iOS 181

Pexip Mobile App for Android 181


Allowing access to your Contacts 182

Accessing the Virtual Meeting Room or Virtual Auditorium 183Pre-configuring a domain 184

Entering the conference PIN 184

Viewing the list of conference participants 185

Viewing a presentation on your device 185

Using the Pexip Mobile App to decide what gets shown on your endpoint 186Viewing the presentation on your mobile device only 186

Viewing the presentation on your mobile device and video endpoint 186

Adding a participant to the conference 187

Muting a participant 188


Appendices 189

Glossary 190

Pexip Infinity port usage 193

Management Node 193Inbound 193

Outbound 193

Conferencing Node 195Inbound 195

Outbound 195

Encryption methodologies 198

Pexip nodes 198

Endpoints 198

Supported RFCs 199

Advanced VMware ESXi administration 201

Supported vSphere versions 201

Supported vSphere editions 201

Management Node network requirements 201

Permissions in vCenter Server (or on ESXi hosts) 201

Host server requirements 202CPU 202

RAM 202

GPU 202

Disk 202

Multitenancy 202



General recommendations 202

Impact on virtual environment 203CPU 203

Memory 203

Storage 203

Network 203

Traffic shaping 203

NIC teaming 203

vMotion 203

Distributed Resource Scheduler (DRS) 204

Enhanced vMotion Compatibility (EVC) 204

vSphere High Availability 204

vSphere Fault Tolerance 205

Using Multiway with Pexip Infinity 206

Example scenario 206

Configuring endpoints using xConfiguration commands 206E20 206

MXP 206

T150 206

Deployments without VCS Conference Factory 206Endpoint configuration 206

Pexip Infinity configuration 207

Deployments using VCS Conference Factory 207Endpoint configuration 207

VCS configuration 207

Pexip Infinity configuration 208

Troubleshooting 209

License information 213

Pexip Infinity license 213

Third party licenses 213

Pexip Infinity Administrator Guide About the Pexip Infinity platform


About the Pexip Infinity platformIn this section:

Introduction 13

Pexip Infinity version 4 features and specifications 14

Pexip Infinity screen layouts 19

Changing aspect ratios 21

Pexip Infinity components 22

Pexip Infinity architecture 25



IntroductionPexip Infinity is a distributed conferencing platform. It provides any number of users with their own personal Virtual Meeting

Rooms, as well as larger Virtual Auditoriums, where they can hold conferences and share presentations. Participants can join over voice, video and mobile from virtually any type of endpoint. Virtual Meeting Rooms and Virtual Auditoriums exist simultaneously in

multiple locations allowing participants to share the same high-quality conferencing experience regardless of distance.

The Pexip Infinity platform includes a Virtual Reception IVR service, which allows all participants to dial a single number to access

the Pexip Infinity, and then use the DTMF tones on their endpoint to enter the number of the specific Virtual Meeting Room or

Virtual Auditorium they wish to join. The platform also includes the Pexip Distributed Gateway, which interworks calls between different protocols, therefore providing you with a truly interoperable conferencing service.

The complementary Pexip Mobile App allows conference participants to control the conference and view presentations from their

own personal devices. The Pexip Web App is a browser-based video client that extends these features to also allow conference participants to access any Virtual Meeting Room or Virtual Auditorium within the Pexip Infinity deployment directly from a web

browser without any special downloads or plugins. The Pexip Web App can also be used to make outbound point-to-point calls when

used in conjunction with the Pexip Distributed Gateway. Conference participants can also use the Pexip Web App to share their

screen, whether or not they are using it as their video client.

Pexip Infinity’s unique distributed architecture is purely software-based and virtualized, running on industry-standard servers, meaning it can be deployed quickly and simply with the flexibility to scale as required.



Pexip Infinity version 4 features and specifications

Pexip InfinityPlatform features

The Pexip Infinity platform is efficiently designed to use industry-standard servers from any vendor to

provide high-quality, scalable and efficient conferencing.

The platform includes:

l Choice of Standard Pexip layout or new 1+21 layout (see Pexip Infinity screen layouts for more

information).

l Management using industry-standard tools, including VMware vSphere and Microsoft Hyper-V, and

the ability to deploy onto generic hypervisors and orchestration layers.

l Virtual Meeting Rooms providing personal meeting spaces for everyone within the organization.

l Virtual Auditoriums designed to hold larger lecture-style conferences.

l Virtual Reception IVR (Interactive Voice Response) service.

l Pexip Distributed Gateway to interwork calls between protocols.

l Ability to rebrand with your own images and voice prompts.

l Upscaling all connected participants to provide a seamless experience to all.

l Ability to seamlessly increase capacity by deploying new, updated, or additional hardware

resources.

l Efficient distribution to reduce bandwidth consumption over expensive WANs.

l Simple conference management and interaction through the Pexip mobile application (for

conference participants) and the administrator interface (for administrators).

l Easy integration with existing SIP and H.323 call control solutions including Cisco UCM, Cisco VCS,

Polycom CMA, Polycom DMA, Avaya Aura, Microsoft Lync 2010 and 2013, and others.

l Interoperability allows for connections of industry-standard protocols (SIP, H.323), those up and

coming (HTML5, WebRTC), and simple data sharing with mobile devices via the Pexip application.

l Full support for individual transcoding and transrating.

l Ability to respond dynamically to fluctuating network conditions by downspeeding and

upspeeding individual participants, and support for endpoint-based packet loss recovery and

adaptation methodologies (such as packet loss concealment and dynamically adapting bandwidth),

thereby protecting the user experience in the event of information loss.

l Management API supporting configuration, status reporting and call control.

l Custom TLS certificates.

l DTLS support.

l SNMP v2c support.

l IPv4 and IPv6 support.

l Industry-leading resilience and redundancy capabilities. The Pexip Infinity leverages the

advantages of virtual machines and its own intelligent virtual backplane to allow customers to

deploy the platform in the way that is most appropriate for them without needing to consume

additional software licenses or purchase dedicated hardware.

l A flexible licensing model that allows pooling of resources and increases in capacity in response to

current requirements.



Pexip Web App(browser-based WebRTC client) features

l No special downloads or plugins required.

l Allows participants to join a Virtual Meeting Room or Virtual Auditorium using a web browser as

their video endpoint.

l Allows participants to share their screen, whether or not they are using it as their video endpoint

(currently Chrome only).

l Provides conference control to host participants.

l Can be used to make point-to-point calls in conjunction with the Pexip Distributed Gateway.

l Supported in Google Chrome version 27 and later, and Mozilla Firefox version 20 and later.

Pexip Mobile Appmobile application features

Access security l Optional guest PIN to limit who can access the conference information.

l Optional host PIN to limit who can control the conference.

Intuitive conference control

l Mute/unmute existing participants.

l Invite new participants to the join the conference.

l Remove existing participants from the conference.

Localized presentation viewing

l View presentations on your own mobile device, regardless of whether you are a video or audio-

only participant.

l Decide where you want to view the presentation based on personal preference: on your mobile

device, on the video system, or both.



Audio and Videospecifications

Bandwidth l Connections from 16 kbps per participant (G.722.1, audio-only), up to 6 Mbps per participant (will

vary depending on the deployment environment, video resolutions, etc.).

Video, Audio and Call Control Standards

l H.323, SIP, WebRTC, Microsoft Lync.

l H.263, H.263++, H.264, H.264 SVC (UCIF Profiles 0, 1), VP8, RDP, RTV.

l Resolutions from QCIF to 720p (1280 x 720), 4:3 and 16:9 aspect ratios.

l Frame rates up to 30 fps.

l G.711(a/µ), G.722, G.722.1 (licensed from Polycom®), Siren14™ (licensed from Polycom®),

G.722.1C (licensed from Polycom®), G.729, G.729A, G.729B, MPEG-4 AAC-LD, Opus.

l MPEG-4 video technology licensed by Fraunhofer IIS.

l Wideband audio mixing.

l Automatic gain control.

l Control individual audio via mobile applications.

l Support for AES (128-bit key size) and DTLS SRTP encryption.



Host hardwarerequirements

CPU l Intel Xeon Penryn or AMD 2012 or later CPU generations (we recommend Intel Xeon Sandy

Bridge or Ivy Bridge processors, 2.7 GHz or higher).

l We recommend a minimum of 6- to 8-core, and not less than 4-core.

RAM

Dependent on the number of CPUs, but generally:

l Minimum 2 GB of RAM per conferencing node, plus 2 GB per host.

l We recommend 1 GB (or more) RAM per physical core.

GPU

l Host servers do not require any specific hardware cards or GPUs.

Multiple VMs sharing the same hardware

l Pexip Infinity Conferencing Nodes and Management Nodes may share the same physical host.

l Pexip nodes may also share the same physical host with other virtual machines.

l Pexip virtual machines must be configured with reserved CPU and memory resources, i.e. Pexip

virtual machines do not support oversubscription.

Multitenancy

A Pexip installation can manage multiple tenants (customers) in various ways:

l Single Management Node, multiple domains, shared Conferencing Nodes

A single installation with one Management Node and one or more Conferencing Nodes is used by

all customers. Call control or DNS sends calls for all domains to the shared Conferencing Nodes.

Does not provide dedicated capacity per customer.

l Single Management Node, multiple domains, dedicated Conferencing Nodes

One or more Conferencing Nodes per customer. Allows for dedicated capacity per customer.

l Dedicated Management Node and dedicated Conferencing Nodes per customer instance

Allows for close customer network integration, using VLANs, hosted on a shared server farm with

multiple VLANs. The dedicated Management Node allows for customer self-management.

Network

l Gigabit ethernet connectivity is strongly recommended.

l In general, you can expect 0.5-3 Mbps per port, depending on call control setup.



Capacity The Pexip Infinity Platform can connect up to two High Definition 720p30 ports per CPU core. (Based

on Intel Sandy Bridge at 2.7 GHz; 1.1 GHz per port plus 20% headroom.)

Hypervisor requirements

VMware l The Pexip Infinity platform supports VMware vSphere ESXi 4.1, 5.0, 5.1, and later.

l We recommend at least the Standard edition.

l The Enterprise and Enterprise Plus editions have additional features that can be taken advantage of by Pexip Infinity in larger deployments.

l The Pexip Infinity platform will run on the free edition of vSphere Hypervisor. However, this edition has a number of limitations that mean we do not recommend its use except in smaller

deployments, or test or demo environments. Notably, automatic deployment of Conferencing

Nodes is not supported.

Microsoft Hyper-V

l The Pexip Infinity platform supports Microsoft Hyper-V in the form of Microsoft Hyper-V Server

2012 and later, and Windows Server 2012 and later.

Other hypervisors and orchestration layers

l Conferencing Nodes can be provisioned with a configuration document generated independently

of a generic VM image. This permits deployment of Pexip Infinity onto unsupported hypervisors as

well as onto supported hypervisors that are managed by an orchestration layer.



Pexip Infinity screen layoutsThe Standard Pexip layout consists of a main video plus up to 7 live thumbnail images in a single row along the bottom of the

screen. Virtual Meeting Rooms always use the Standard Pexip layout.

Virtual Auditoriums can use the same Standard Pexip layout as Virtual Meeting Rooms, but also offer the option of a 1+21 layout, which consists of a slightly smaller main video plus up to 21 live thumbnail images in 3 rows at the bottom of the screen. For more

information on selecting this option, see Changing the layout seen by participants.

For all layouts:

l Audio-only participants are represented by a telephone icon with their caller ID (if available) superimposed.

l Video callers who are on hold are represented by a frozen black-and-white image.

l If there are more participants than there are thumbnails available, the last thumbnail displays the number of additional

participants not currently visible.

l A full list of participants is available using the Pexip Mobile App or Pexip Web App.

Standard Pexip layout

Standard Pexip layout: main video plus a single row of thumbnails (in this case showing live videos, the audio icon and the additional participants icon)



1+21 layout

1+21 layout: main video plus three rows of thumbnails (in this case showing live videos, the audio icon and the additional participants icon)



Changing aspect ratiosEndpoints send and display video images and presentations in various aspect ratios, most commonly 16:9 and 4:3. If there is a

difference between the aspect ratios of the sending and receiving endpoints, then the endpoint and/or the Pexip Infinity may crop

the image or add black vertical or horizontal mattes (also known as letterboxing and pillarboxing). How and when aspect ratios are

changed depends on a number of factors, but the general principles are described below.

Presentations

Pexip Infinity

In general, the Pexip Infinity prefers to send presentations as 720p (which has an aspect ratio of 16:9) for calls where the bandwidth

is sufficient and the endpoint supports it. But if this is not feasible, all alternative resolutions have an aspect ratio of 4:3.

If a change of aspect ratio is required, the Pexip Infinity will add mattes (in order to not remove anything important from the

presentation). It will never crop presentations.

This means that depending on circumstances, the presentation may be sent as either 16:9 or 4:3. The decision is made without

knowing about the actual display on the endpoint, so in some cases the endpoint may need to change the aspect ratio again.

Endpoints

If the aspect ratio of the presentation image being sent from the Pexip Infinity does not match the display aspect ratio on the

endpoint screen, the endpoint will typically add another letter/pillarbox to make it fit. Generally endpoints will not crop the image.

Main video If required, the Pexip Infinity will change the aspect ratio of main video by cropping the image (in order to avoid black bars in the

thumbnail images).

If the aspect ratio of the main video image being sent from the Pexip Infinity does not match the display aspect ratio on the

endpoint screen, the endpoint will typically add another letter/pillarbox to make fit. Generally endpoints will not crop the image.



Pexip Infinity components

Overview

The Pexip Infinity conferencing platform is a virtual entity that consists of a Management Node and one or more securely

interconnected Conferencing Nodes. Both are software applications that you deploy remotely as Virtual Machines (VMs) on host

servers around the globe. You can add, remove or move Conferencing Nodes according to your conferencing requirements.

Conferences take place in Virtual Meeting Rooms and Virtual Auditoriums, which each have one or more associated aliases and which exist on all Conferencing Nodes simultaneously. Conference participants access a Virtual Meeting Room or Virtual Auditorium

by dialing any one of its aliases directly, or via the Virtual Reception IVR service. This connects them to the Virtual Meeting Room

or Virtual Auditorium on their nearest Conferencing Node. A single such conference can take place across one, two, or more

Conferencing Nodes with no difference in conference experience from the participants' perspective.

Conference participants can access Virtual Meeting Rooms and Virtual Auditoriums from virtually any endpoint, including the Pexip

Web App, Pexip Infinity's built-in video client, which they can also use to share their screen with other conference participants.

While in a conference, participants can use the Pexip Web App or the Pexip Mobile App to control the conference and view presentations.

The Pexip Distributed Gateway service interworks calls between protocols, allowing users to make calls from virtually any type of

endpoint (including SIP, H.323, Lync and WebRTC).

Pexip Infinity deployment showing Management Node and four Conferencing Nodes with participants connected locally

Management NodeThe Management Node is the administrative interface of the Pexip Infinity platform. It hosts the Pexip Infinity web interface, from

which administrators can:



l create and manage Conferencing Nodes

l create and configure Pexip Infinity services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions and the Pexip

Distributed Gateway) which are pushed out to all the Conferencing Nodes

l view conference status across all Conferencing Nodes

l dial out to participants from a Virtual Meeting Room, and disconnect participants from a Virtual Meeting Room.

The Management Node does not handle any media or signaling.

The Management Node is deployed using a virtual machine management application such as VMware's vCenter Server, or Microsoft

Hyper-V.

Conferencing NodeThe Conferencing Nodes provide the capacity for conferences, and handle the media and signaling. All Conferencing Nodes support

an identical set of Virtual Meeting Rooms, which are provided to them by the Management Node.

Conferencing Nodes are deployed from the Pexip Infinity Management Node.

For more information, see About Conferencing Nodes.

Pexip Mobile AppThe Pexip mobile application (Pexip Mobile App) allows conference participants to control aspects of the conference and view

presentations from their own mobile device. For more information, see About the Pexip Mobile App.

Pexip Web AppConference participants can access any Virtual Meeting Room or Virtual Auditorium within your Pexip Infinity deployment using

Pexip Infinity's built-in web-based video client, which does not require any special downloads or plugins. Conference participants

can also use the web client to share their screen, whether or not they are using it as their video client. Host participants can also

control the conference. For more information, see Using the Pexip Web App.

Virtual Meeting Rooms and Virtual AuditoriumsConferences take place in Virtual Meeting Rooms and Virtual Auditoriums.

When creating Virtual Meeting Rooms and Virtual Auditoriums, you define the aliases that are used to access the Virtual Meeting

Room, and any PINs that are required. You can configure up to 100,000 Virtual Meeting Rooms and Virtual Auditoriums, and each

can have up to 500 aliases.

All Virtual Meeting Rooms and Virtual Auditoriums exist on all Conferencing Nodes. When a Conferencing Node receives a call to a

particular Virtual Meeting Room or Virtual Auditorium alias, it creates a conference instance based on that service's settings.

When a second endpoint places a call to an alias that belongs to the same Virtual Meeting Room or Virtual Auditorium, the call is

placed into the existing conference instance.

For more information, see About Virtual Meeting Rooms and About Virtual Auditoriums.

Virtual ReceptionsA Virtual Reception allows you to set up one or more direct dial telephone numbers or IP addresses that participants can dial to

access a single, central IVR service. From here, participants can use DTMF tones to select the Virtual Meeting Room or Virtual

Auditorium they wish to join. It provides an alternative means to access Pexip Infinity services for participants who cannot dial

aliases directly.



For more information, see About the Virtual Reception.

Pexip Distributed GatewayThe Pexip Distributed Gateway service interworks calls between protocols, allowing users to make calls from virtually any type of

endpoint (including SIP, H.323, Lync and WebRTC) and interworking these to SIP, H.323 or Lync.

For more information, see Using the Pexip Distributed Gateway service.

Host serversBoth the Management Node and Conferencing Nodes are virtual machines (VMs) that run on industry-standard host servers. A

Management Node can run on the same host server as a Conferencing Node. Other Conferencing Nodes can run on host servers in

the same or different locations, allowing you to create a globally distributed system.

You can have two Conferencing Nodes running on the same host server, for example to ensure service continuity during upgrade of

one of the Conferencing Nodes. However, you must ensure that your hardware is not over-committed - see Hardware requirements for more information.

HypervisorsEach host server runs a hypervisor, an application which manages virtual machines and the physical hardware on which they are

hosted. Pexip Infinity version 4 includes specific support for the following hypervisors:

l VMware vSphere ESXi (4.1, 5.0 and later)

l Microsoft Hyper-V (Microsoft Hyper-V Server 2012 and later, or Windows Server 2012 and later)

Other hypervisors and orchestration layers may be used but are not officially supported. If you wish to deploy Pexip Infinity using a

non-supported hypervisor, we recommend that you contact your authorized Pexip representative for assistance.

VM Managers

A VM Manager is an application that allows you to connect to one or more VMware vSphere ESXi hypervisors when Automatically

deploying a new Conferencing Node. VM Managers supported by version 4 of Pexip Infinity are vCenter Server and vSphere.

l vCenter Server is an application used to manage groups of host servers (and therefore ESXi hypervisors) through a single

interface.

l vSphere on the host server is used when managing a single host server (and therefore ESXi hypervisor).

For more information see About VM Managers.



Pexip Infinity architecture

Conference distributionAll Pexip Infinity services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions and the Pexip Distributed Gateway) exist

on all Conferencing Nodes. When a user dials in to a Virtual Meeting Room, or Virtual Auditorium a conference instance is created. This conference can exist across one or more Conferencing Nodes. Where two or more Conferencing Nodes are involved, they send

the call media between each other over a secure IPsec virtual backplane.

When you first deploy a Conferencing Node, you select its System Location, which is a user-defined parameter that tells the Pexip

Infinity where the Conferencing Node is physically located. Conferences that involve more than one Conferencing Node can be

locally distributed, globally distributed, or both, depending on the system location of each of the Conferencing Nodes involved. Each

of these distribution scenarios are described in more detail below.

Locally distributed

Locally distributed conference with two Conferencing Nodes across two host servers in the same location

Locally distributed conferences exist across two or more Conferencing Nodes in the same physical location (i.e. with the same

system location selected) (see the diagram above).

Having more than one Conferencing Node in a single location allows you to increase capacity and provide redundancy.

To improve efficiency, no more than three Conferencing Nodes in a single location will handle the media for a particular

conference instance. For more information, see Handling of media and signaling in locally distributed conferences.

Globally distributed

Globally distributed conferences exist across two or more Conferencing Nodes in different physical locations (i.e. with different

system location selected). This allows participants in different regions to access the conference from their local Conferencing Node.

Call media is sent between the Conferencing Nodes on behalf of all the endpoints connected to them, thus minimizing WAN

bandwidth usage between locations.



Locally and globally distributed

Locally and globally distributed conference with four Conferencing Nodes across four host servers in three locations

Conferences can also be locally and globally distributed at the same time, if two or more Conferencing Nodes in one location and

at least one other Conferencing Node in a different location are involved. In such cases, one Conferencing Node in each location will

act as the proxy for any other Conferencing Nodes in the same location. Call media for each location will be sent between the

proxies only, thus minimizing WAN bandwidth usage between locations.

Bandwidth management

Bandwidth usage

The Conferencing Node to which the current speaker is connected sends an HD video stream of the current speaker, plus a lower-

resolution thumbnail (a smaller image at the bottom of the screen which shows the participant's video) of each of the other

participants connected to it.

The Conferencing Node to which the previous speaker is connected sends an HD video stream of the previous speaker, plus lower-

resolution thumbnails of each of the other participants connected to it.

All other Conferencing Nodes send lower-resolution thumbnails of each of the participants connected to it.



Bandwidth usage when current and previous speakers are connected to different Conferencing Nodes

As shown in the diagram above, if the current and previous speakers are connected to different Conferencing Nodes, there is one

HD stream in each direction between the two nodes, plus one smaller stream for every participant being shown in a thumbnail.

Bandwidth usage when current and previous speakers are connected to the same Conferencing Node

As shown in the diagram above, if the current and previous speakers are connected to the same Conferencing Node, that

Conferencing Node sends an HD video stream of the current speaker plus lower-resolution thumbnails of each of the other

participants, to all other Conferencing Nodes. The other Conferencing Nodes send lower-resolution thumbnails of the other

participants.



This architecture means that there are major bandwidth savings when compared with traditional MCU deployments where all

conference participants regardless of location connect to the same MCU and individual HD and thumbnail video streams are sent

between the MCU and every endpoint.

Significant bandwidth savings are achieved due to fewer and smaller video streams being sent between locations.

Note that:

l One HD stream uses about 1.6 Mbps.

l One thumbnail stream uses about 64-192 kbps.

l A presentation stream (not shown in the diagrams above) uses an additional 1.6 Mbps from the presenter.

l The Pexip Infinity supports up to 6 Mbps per participant (this will vary depending on the deployment environment, video

resolutions, etc.).

Downspeeding

The Pexip Infinity will automatically downspeed and upspeed individual calls in response to fluctuating network conditions.

Bandwidth restrictions

Administrators can individually restrict the bandwidth available to participants accessing each Virtual Reception, Virtual Meeting

Room and Virtual Auditorium. For more information, see Restricting call bandwidth.

Internal encryptionAll communication between the Management Node and Conferencing Nodes, and between two Conferencing Nodes, is encrypted

using IPsec.

For more information, see Encryption methodologies.



EndpointsThe Pexip Infinity does not act as a registrar or gatekeeper, so your endpoints should register with a call management system.

Using a gatekeeper to route calls to Pexip Infinity conferencesThe Pexip Infinity does not register with a gatekeeper as an MCU.

To ensure that calls can be routed to the Pexip Infinity, your gatekeeper or call management system must be configured with

appropriate neighbor/zone relationships towards the Pexip Infinity Conferencing Nodes. These zones must be set up so that when an

endpoint places a call to a Pexip Infinity alias, the call is routed to the endpoint's local Conferencing Node(s) as a first preference.

Other non-local Conferencing Nodes can be used as secondary choices to provide redundancy.

For more information and examples using a Cisco VCS, see the Pexip Infinity and Cisco VCS Deployment Guide.

Load balancingLoad balancing between Conferencing Nodes in a single location is achieved via your call management system. You should configure

it so that calls from each configured set of endpoints are routed to a configured set of conferencing nodes. You should configure

DNS SRV records to identify all Conferencing Nodes in a location. For more information, see the Pexip Infinity and Cisco VCS

Deployment Guide.

Redundancy

Management Node

The Management Node is used to create Conferencing Nodes, configure conference settings, manage licenses and collate system

logs. It does not handle any call processing, so if it were to become unavailable the Pexip Infinity service would be unaffected.

However:

l you would not be able to make changes to services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions and the

Pexip Distributed Gateway)

l logging would be affected

l after 14 days licenses would cease to be allocated and the Pexip Infinity service would no longer allow calls.

Conferencing Node

You should ensure that your call control system is set up so that, in the event of a Conferencing Node failing, new calls to the

conference will be routed to another available Conferencing Node.

If multiple Conferencing Nodes are configured in a single location, new calls to a conference can be routed by the call control to

only those nodes that are currently available. To achieve this, you must configure the call control system with all possible

Conferencing Nodes (either explicitly or through DNS records), and for liveness checks to be carried out. For more information, see

the Pexip Infinity and Cisco VCS Deployment Guide.

Note that there is no live fail-over; calls in progress on a Conferencing Node that fails will be lost, and participants will need to

redial the Virtual Meeting Room or Virtual Auditorium alias in order to reconnect to the conference.

ScalabilityTo increase capacity of the Pexip Infinity, simply deploy one or more new Conferencing Nodes from the Management Node.

Handling of media and signaling in locally distributed conferencesMedia and signaling for a single call may take different paths within a location, as follows:

http://www.pexip.com/technical-documentation





l When an alias that belongs to a Virtual Meeting Room, Virtual Auditorium or Virtual Reception is dialed from an endpoint, the

call will be placed to whichever Conferencing Node the call control system directs the call to. This Conferencing Node will

always continue to handle the signaling for that call, regardless of where the media is routed.

l If the conference does not already exist in this location, Pexip Infinity will check the loading of all Conferencing Nodes in the location and will allocate the conference to the Conferencing Node that currently has the most available capacity. The media

for the call will go directly to that Conferencing Node, but the signaling will continue to be handled on the Conferencing Node

to which the endpoint connected.

l If this is a call to a conference already running on another Conferencing Node within the same location, the media will be

set up on the node where the conference is running, but the signaling will be handled on the node to which the endpoint

connected.

l If the Conferencing Node on which the conference is running reaches capacity, Pexip Infinity will allocate a secondary (and a

then a tertiary) node within that location to handle media for that conference, and automatically create a local backplane

between these Conferencing Nodes so all participants are part of the same conference, with the same layout.

l Currently up to three Conferencing Nodes within one location can be involved in media handling for one conference.

l When all three Conferencing Nodes handling the media have reached capacity, no further calls can be placed to that

conference from endpoints connected to nodes within that location. Other endpoints connected to Conferencing Nodes in

other locations may still connect to the conference, assuming that there is sufficient capacity in that location.

Example

Example of media and signaling in a locally distributed conference

1. Alice dials [email protected] and is connected to Conferencing Node USConf01.

2. Pexip Infinity determines that another Conferencing Node within that location, USConf02, has the most capacity and so sets up

the conference on that node. Alice's signaling is handled by USConf01 and the media is being sent directly to USConf02.

3. Bob dials [email protected]. He is connected to USConf02. The conference is already running on that Conferencing

Node, so USConf02 handles both the media and the signaling for Bob.

4. Carol dials [email protected]. She is connected to USConf03. Her signaling is handled by USConf03 but the media is

routed directly to USConf02, where the conference is running.

5. Dave dials [email protected]. He is connected to USConf01. Pexip Infinity determines that USConf02 is now out of

capacity, and USConf03 has the most available capacity. Dave's media is routed to USConf03,but USConf01 continues to handle his signaling.

Pexip Infinity Administrator Guide Getting started


Getting startedIn this section:

Prerequisites 32

Implementing a dial plan 35

Overview of installation 36

About the Pexip Infinity software files 37

Configuring VMware 38

Configuring Hyper-V 41

Installing the Management Node 42

Using the Pexip Infinity web interface 48



PrerequisitesThis section outlines the systems and configuration required before you can begin to deploy Pexip Infinity in your network.

Hardware requirementsHost servers must meet the following hardware requirements:

Management Node Conferencing Node

Recommended

Required minimum forStandard Definition (SD)

Required minimum forHigh Definition (HD) Recommended

Server manufacturer Any manufacturer

Processor make* Any l Intel Xeon Penryn

l AMD 2012

l Intel Xeon 5500

series dual

processor (Nehalem

architecture)

l AMD 2012

l Intel Xeon E5-

2600/4600 series

(Sandy Bridge-EP

architecture) or

later

Processor instruction

set

Any l SSE4.1 l SSE4.2

l AVX

l AVX2

Processor architecture 64-bit 64-bit 64-bit 64-bit

Processor speed 2.0 GHz 2.0 GHz 2.0 GHz or faster 2.7 GHz or faster

No. of physical cores* 2 4 cores per socket 4 cores per socket 8 cores per socket

Processor cache no minimum 15 MB 15 MB 20 MB or greater

(2.5 MB L3 cache per

core)

Total RAM* 2 GB 512 MB per core 512 MB per core 1024 MB per core

RAM makeup Any All channels must be populated with a DIMM.

Hardware allocation The host server must not be over-committed in terms of either RAM or CPU. In other words, the

Conferencing Nodes and Management Nodes each must have dedicated access to their own RAM and

CPU cores.

Storage space required 100 GB 50 GB 50 GB 50 GB

GPU No specific hardware cards or GPUs are required.

Network Gigabit ethernet connectivity from the host server.

Hypervisor l VMware ESXi 4.1 or

later

l Microsoft Hyper-V

2012 or later

l VMware ESXi 4.1 or

later

l Microsoft Hyper-V

2012 or later


later

l Microsoft Hyper-V

2012 or later


later

* This does not include the processor and RAM requirements of the Hypervisor.



For further information, see the Pexip Infinity Server Design Guide.

HypervisorsPexip Infinity currently offers specific support for VMware ESXi and Microsoft Hyper-V hypervisors. Other hypervisors and

orchestration layers may be used but are not officially supported. If you wish to deploy Pexip Infinity using a non-supported

hypervisor, we recommend that you contact your authorized Pexip representative for assistance.

VMware vSphere ESXi

VMware versions

Version 4 of Pexip Infinity supports VMware vSphere ESXi 4.1, 5.0 and later, although we recommend ESXi 5.1. You must have a

suitable VMware environment already installed. For information on configuring a VMware environment specifically for use with

Pexip Infinity, see Configuring VMware and the Appendix on Advanced VMware ESXi administration.

VMware editions

The Pexip Infinity platform will run on the free edition of vSphere Hypervisor. However, this edition has a number of limitations

(limited support from VMware, no access to vCenter or vMotion, no access to VMware API, and a maximum of 32 GB RAM). In

particular, the lack of access to the VMware API means that all Conferencing Nodes will have to be deployed manually (see

Deployment types). For this reason we do not recommend its use except in smaller deployments, or test or demo environments.

The minimum edition of VMware that we recommend is the vSphere Standard edition. This does not have the limitations of the

free edition. If you do not already use VMware in your enterprise, the vSphere Essentials Kit is a simple way to get started and will

provide you with Standard edition licenses for 3 servers (with 2 CPUs each) plus a vCenter license.

For larger deployments, you may wish to use the Enterprise edition which includes additional features relevant to the Pexip Infinity platform, such as DRS (Distributed Resource Scheduler). DRS allows you to automatically move virtual machines between different

physical host servers to balance the amount of load across the virtual machines (VMs) and the hosts.

The Enterprise Plus edition includes further additional features relevant to the Pexip Infinity platform that could be of benefit to

larger deployments. These include Storage DRS and Distributed Switch.

For a comparison of the VMware editions, see http://www.vmware.com/products/datacenter-virtualization/vsphere/compare-

editions.html.

Microsoft Hyper-V

Version 4 of Pexip Infinity supports Microsoft Hyper-V in the form of Microsoft Hyper-V Server 2012 and later, or Windows Server

2012 and later. You must have a suitable Hyper-V environment already installed. For information on configuring a Hyper-V

environment specifically for use with Pexip Infinity, see Configuring Hyper-V.

Other hypervisors and orchestration layers

Pexip Infinity Management Nodes and Conferencing Nodes support static IP addressing only. The static IP addressing must be

configured in both the Infinity node and the hypervisor or orchestration layer, so the latter must also support this.

Network requirements

Call control

If your deployment includes a call control system, it must be configured to route calls to the Pexip Infinity appropriately. The exact

configuration will depend on your deployment and dial plan, but in general calls placed from an endpoint to a Virtual Meeting

Room alias should be routed to the endpoint's local Conferencing Nodes. For more information, see Implementing a dial plan and

Pexip Infinity-Cisco VCS Deployment Guide.


http://www.vmware.com/products/datacenter-virtualization/vsphere/compare-editions.html




Lync server

If your deployment includes Microsoft Lync, you must set up static routes to domains used by Pexip Infinity aliases. For more

information, see Pexip Infinity-Microsoft Lync Deployment Guide.




Implementing a dial planBefore you deploy the Pexip Infinity platform in your network, you must consider your dial plan and ensure that calls to Virtual

Meeting Room, Virtual Auditorium and Virtual Reception aliases, and calls that are to be interworked using the Pexip Distributed

Gateway, will be routed to the appropriate Conferencing Nodes.

Using a standard format for aliasesWe recommend that you use a standard format for all Virtual Meeting Room and Virtual Auditorium aliases within your Pexip Infinity

deployment. A simple way to do this would be to have a set prefix such as meet., followed by a user name, followed by your

domain. For example:

l [email protected] (for Alice's VMR)

l [email protected] (for Bob's VMR)

l [email protected] (for the sales team's Virtual Auditorium)

l [email protected] (for the Virtual Reception)

Using this standard format will then make it simple to configure your call management system to route calls matching the format to

the appropriate Conferencing Nodes.

Routing calls to the local Conferencing NodeWhen your call management system receives a call to a Virtual Meeting Room, Virtual Auditorium or Virtual Reception alias, it must

then decide where to route the call.

A single conference can take place across one, two or more Conferencing Nodes with no difference in conference experience from

the users' perspective. We recommend that in the first instance, calls are routed to the Conferencing Node that is geographically

nearest to the endpoint that placed the call. This reduces the WAN bandwidth used for the conference, because endpoints are only

making local calls. If more than one Conferencing Node is involved, only one set of media has to be sent between the two locations.

We recommend that you set up rules on your call management system so that calls originating from a particular location (defined by

zone, subzone or IP address range) and placed to a Pexip Infinity alias are routed to a specific Conferencing Node. To build on the

previous example, we have configured subzones on our call management system which group together endpoints in a particular

physical location, and we have then set up the following call routing rules:

Source Alias Destination zone

Oslo subzone meet.*@example.com.* Norway Conferencing Node

New York subzone meet.*@example.com.* Americas Conferencing Node

Boston subzone meet.*@example.com.* Americas Conferencing Node

In this case, users in Oslo, New York and Boston could all call [email protected] and be routed to the same conference.

Further informationFor further information about how to configure your specific call management system to work with the Pexip Infinity, see the

following documentation:

l Pexip Infinity and Cisco VCS Deployment Guide




Overview of installationBelow is a list of the individual tasks that you must complete in order to deploy the Pexip Infinity platform. Each step provides a link

to the section of this guide that provides full information about how to complete that task.

Task Notes

Download the appropriate Pexip Infinity software files

The files you need will depend on the hypervisor you are using and whether your

Conferencing Nodes will be deployed manually or automatically.

Configure VMware

Configure Hyper-V

This guide assumes that you have a suitable VMware or Hyper-V environment already

up and running. These sections outline the specific configuration of each application

that is required to support a Pexip Infinity deployment.

Deploy the Management Node During this step you install and configure an instance of a Pexip Infinity Management

Node using the tools available in VMware or Hyper-V.

Configure DNS

Configure NTP

This will ensure that your system will function correctly within your network.

Add VM Managers This will provide you with a quick way of selecting VM Managers, used if you intend

to deploy new Conferencing Nodes automatically onto vSphere ESXi hosts.

Add locations Locations allow you to group your Conferencing Nodes together according to their

physical location to allow more efficient routing of media streams.

Add licenses You must install a system license and sufficient concurrent port licenses before you

can place calls to Pexip Infinity Virtual Meeting Rooms.

Add Conferencing Nodes During this step you use the Pexip Infinity web interface, which resides on the

Management Node, to create Conferencing Nodes on host servers.

Configure Virtual Meeting Rooms

Configure Virtual Auditoriums

During these steps you set up details of the Virtual Meeting Rooms and Virtual

Auditoriums on the Pexip Infinity, including the aliases that will be dialed to access

them.

Configure a Virtual Reception This is an optional step where you set up details of a Virtual Reception. This is used to

provide access to Virtual Meeting Rooms and Virtual Auditoriums for participants who

are unable to dial their aliases directly, and/or to provide local telephone numbers

that audio-only participants can dial to access conferences.

Configure Pexip Distributed Gateway service

This is an optional step where you set up the Gateway Routing Rules that determine

which calls get interworked between protocols.



About the Pexip Infinity software filesThe Pexip Infinity platform is entirely software-based, and is deployed by installing the files provided by Pexip onto your hypervisor

to create Virtual Machines (VMs), which you then configure appropriately for your environment.

The files you need will depend on the hypervisor you are using and whether your Conferencing Nodes will be deployed manually or

automatically.

Pexip Infinity software filesThe Pexip Infinity version 4 release includes the following files:

File name Use

pexipmcumgr.ova Used to deploy a generic Management Node VM using VMware or other hypervisors except Hyper-V.

For more information, see Installing the Management Node.

pexipmcumgr.zip Used to deploy a generic Management Node VM using Hyper-V.

For more information, see Installing the Management Node.

pexip-conferencing-

node.ova

Used to manually deploy a generic Conferencing Node VM using hypervisors other than VMware or

Hyper-V.

For more information, see Deploying a Conferencing Node using a VM template and configuration

file.

upgrade.tar Used when upgrading the Pexip Infinity from version 2 or later.

For more information, see Upgrading the Pexip Infinity.

Other files generated by the Pexip Infinity

When deploying a Conferencing Node manually or automatically, the Pexip Infinity generates a file that contains a template for a

generic VM, and Conferencing Node-specific configuration details. When this file is uploaded into VMware or Hyper-V, it creates a

new Conferencing Node VM and configures it with the details you provided at the time of deployment.



Configuring VMwareThis section describes the VMware configuration required in order to support basic deployments of the Pexip Infinity. It is assumed

that you have a VMware environment already installed.

For details on the versions and editions of VMware that are supported by the Pexip Infinity, see VMware vSphere ESXi.

For more details on VMware and information on advanced VMware ESXi administration, see Advanced VMware ESXi

administration.

If an ESXi host is being managed by vCenter Server, all administration must be performed via vCenter Server. Do not log in

directly to the ESXi host; configuration changes made in this way may be lost. To ensure that ESXi hosts being managed by vCenter

Server are accessible via vCenter Server only and are not directly accessible, you should put them in Lockdown mode. Lockdown

mode forces all operations to be performed through vCenter Server.

Synchronizing time

All host servers must be synchronized with accurate time before you install the Pexip Infinity Management Node or

Conferencing Nodes on them.

NTP must be enabled on the Management Node before you deploy any Conferencing Nodes.

We strongly recommend that you configure at least three distinct NTP servers or NTP server pools on all your host servers and

the Management Node itself. This will ensure that log entries from all nodes are properly synchronized.

Using the desktop client

To synchronize time on the host server using the vSphere desktop client:

1. Log in to the VM Manager (vCenter Server or the ESXi host).

2. From the left-hand panel, select the host server on which the software image is to be installed.

3. Select the Configuration tab.

4. From the Software pane on the left-hand side, select Time Configuration.

5. On the top right of the page, select Properties. The Time Configuration dialog box appears.

6. In the NTP Configuration section, check NTP Client Enabled.

7. Select Options.

The NTP Daemon (ntpd) Options dialog box appears.

8. From the left-hand panel, select General. Under Startup Policy, select Start and stop with host.

9. Select OK.

10. Select Options again.

The NTP Daemon (ntpd) Options dialog box appears.

11. From the left-hand panel, select NTP Settings. Under NTP Servers, we strongly recommend that you configure at least 3

distinct NTP servers or NTP server pools to ensure that log entries from all nodes are properly synchronized.

12. Check Restart NTP service to apply changes, and then select OK.

Using the web client

To synchronize time on the host server using the vSphere web client:



1. Log in to the VM Manager (vCenter Server).

2. From the left-hand panel, select vCenter > Hosts and Clusters and navigate to the host server on which the software image is

to be installed.

3. Select the Manage tab.

4. From the pane on the left-hand side, select Time Configuration.

5. On the top right of the page, select Edit. The Edit Time Configuration dialog box appears.

6. Select Use Network Time Protocol (Enable NTP client).

7. From the NTP Service Startup Policy drop-down menu, select Start and stop with host.

8. In the NTP Servers field, we strongly recommend that you enter at least 3 distinct NTP servers or NTP server pools to ensure

that log entries from all nodes are properly synchronized.

9. Select OK.

To verify that NTP has been enabled correctly:


2. From the Software pane on the left-hand side, select Time Configuration.

3. Ensure that value in the Date & Time field is correct.

Enabling automatic startupAfter deploying a new Management Node or Conferencing Node from VMware, you must enable automatic startup of that virtual

machine (VM). In VMware, automatic startup is disabled by default for every new VM. This means that if the host server is powered

down for any reason, when it restarts the VM will not restart and must be started manually.

You can only enable automatic startup after the Management Node or Conferencing Node has been deployed.


To enable automatic startup using the vSphere web client:


2. From the left-hand panel, select vCenter > Hosts and Clusters and navigate to the host server on which the Management Node

or Conferencing Node VM is installed.


4. From the pane on the left-hand side, select VM Startup/Shutdown.

5. At the top right of the page, select Edit.

6. Select the relevant Conferencing Node or Management Node VM and use the up arrow to move it to the Automatic Startup section.

7. Select OK.


To enable automatic startup using the vSphere desktop client:


2. From the left-hand panel, select the host server on which the Management Node or Conferencing Node VM is installed.


4. From the Software pane on the left-hand side, select Virtual Machine Startup/Shutdown.

5. At the top right of the page, select Properties.



6. Select the relevant VM and use the Move Up button to move it to the Automatic Startup section.

7. Select OK.

Disabling EVCWe strongly recommend that you disable EVC (Enhanced vMotion Compatibility) for any ESXi clusters hosting Conferencing Nodes

that include a mix of old and new CPUs. If EVC is enabled on such clusters, the Pexip Infinity platform will run more slowly because

the Conferencing Nodes will assume they are running on older hardware.

For more information, see Enhanced vMotion Compatibility (EVC).

To disable EVC:

1. Log in to vCenter Server using either the vSphere desktop or web client.

2. Display the cluster in the inventory.

3. Right-click the cluster and select Edit Settings.

4. In the left panel, select VMware EVC.

The dialog box displays the current EVC settings.

5. Select Change EVC Settings.

6. Select Disable EVC.



Configuring Hyper-VThis section describes the Hyper-V configuration required in order to support basic deployments of the Pexip Infinity. It is assumed

that you have a Hyper-V environment already installed.

Synchronizing time

All host servers must be synchronized with accurate time before you install the Pexip Infinity Management Node or


NTP must be enabled on the Management Node before you deploy any Conferencing Nodes.

We strongly recommend that you configure at least three distinct NTP servers or NTP server pools on all your host servers and

the Management Node itself. This will ensure that log entries from all nodes are properly synchronized.

In Hyper-V, all time synchronization is configured using the Active Domain Controller. You must ensure that all VMs and host servers

are using the same time. Consult your Hyper-V documentation for information on how to do this in your environment.

Creating an external virtual switchYou must create an external virtual switch on the host server to allow VMs on that host to access external network resources. To do

this:

1. Log in to Hyper-V.

2. Right-click on the host server and select Virtual Switch Manager....The Virtual Switch Manager window opens.

3. Select External and then Create Virtual Switch.

4. Enter a Name for the switch.

5. Either accept the default options, or select the options appropriate for your environment.

6. Select Apply.



Installing the Management NodeInstallation of the Management Node is a two-step process:

1. Deploying the Management Node template. This creates a new instance of a generic Management Node VM.

2. Running the installation wizard. This allows you to configure the Management Node VM appropriately for your deployment.

Each of these steps is described below.

Deploying the Management Node templatePexip provides two different template files for use when creating a Management Node VM:

l an .ova file for Deployment using VMware and Deployment using other hypervisors except Hyper-V

l a .zip file for Deployment using Microsoft Hyper-V.

The deployment process creates a new, unconfigured instance of a Pexip Infinity Management Node Virtual Machine.

Deployment using VMware





Using the vSphere desktop client

To install a new instance of a Pexip Infinity Management Node using the vSphere desktop client:

1. Download the pexipmcumgr.ova file from the link provided to you by your Pexip representative.


3. Select File > Deploy OVA Template....

You will be taken to the Source page.

4. Browse to the location of the pexipmcumgr.ova file and select Next >.

You will be taken to the OVF Template Details page.

5. Select Next >.

You will be taken to the End User License Agreement page.

6. Read the license agreement, and if you agree to the terms select Accept and then Next >.

You will be taken to the Name and Location page.

7. Enter an appropriate name for the Management Node. This name will be used in the VMware interface to identify this

Management Node virtual machine (VM).

8. Select Next >.

You will be taken to the Resource Pool page.

9. Select the resource pool for the Pexip Infinity Management Node.

10. Select Next >.

You will be taken to the Disk Format page.

11. Select Thick Provision.

12. Select Next >.

You will be taken to the Network Mapping page.



13. Select the appropriate mappings and select Next >.

You will be taken to the Ready to Complete page.

14. Review the information and select Power on after deployment.

15. Select Finish.

A window will appear showing the deployment progress. When deployment is complete this will say Completed Successfully. You

can then Close the window.

Using the vSphere web client

To install a new instance of a Pexip Infinity Management Node using the vSphere web client:

1. Download the pexipmcumgr.ova file from the link provided to you by your Pexip representative.


3. Select vCenter > VMs and Templates.

4. Click on the Actions menu and select Deploy OVF Template....

You will be taken to the Select source page.

5. Browse to the location of the pexipmcumgr.ova file and select Next >.

You will be taken to the Review details page.

6. You may see the following warning:

Check the Accept extra configuration options box and select Next.

You will be taken to the Accept EULAs page.

7. Read the license agreement, and if you agree to the terms select Accept and then Next >.

You will be taken to the Select name and folder page.

8. Enter an appropriate Name for the Management Node. This name will be used in the VMware interface to identify this

Management Node virtual machine (VM).

9. Select the folder or datacenter within which the Management Node will be located.

10. Select Next.

11. Select the resource pool in which to run the template.

12. Select Next.

You will be taken to the Select storage page.



13. Select the virtual disk format and datastore to be used.

14. Select Next.

You will be taken to the Setup networks page.

15. Select the VM Network and configuration, and select Next.

You will be taken to the Ready to complete page.

16. Review the settings and select Power on after deployment.

17. Select Finish.

Progress will be shown in the Recent Tasks tab to the right of the screen. When the template has been deployed successfully, a

green tick will appear.

Deployment using Microsoft Hyper-V

To deploy a new instance of a Pexip Infinity Management Node using Hyper-V:

1. Download the pexipmcumgr.zip file from the link provided to you by your Pexip representative, and extract the files.

2. Log in to Hyper-V.

3. Right-click on the host server and select Import Virtual Machine....This will start the Import Virtual Machine wizard.

4. On the Locate Folder page, Browse to the folder containing the extracted files and select Next.

You will be taken to the Select Virtual Machine page.

5. The wizard will automatically detect the folder and file containing the Management Node VM. Confirm that this is correct and

select Next.

You will be taken to the Choose Import Type page.

6. Select the type of import most appropriate for your environment (if you are unsure, select Restore the virtual machine).

Select Next.

7. Depending on the import type you have chosen, you may be asked for further information. Follow the prompts as required.

When the setup is complete, you will be taken to the Completing Import Wizard page.

8. Review the summary and select Finish.

When the Management Node VM has been created successfully, it will appear in the list of Virtual Machines.

Deployment using other hypervisors

Pexip Infinity currently supports deployments using ESXi or Hyper-V hypervisors only. If you wish to use any other type of hypervisor

or orchestration layer, you can use the pexipmcumgr.ova file to create a generic instance of the Management Node and then

configure it by Running the installation wizard. However, we recommend that you first contact your authorized Pexip

representative for advice.

Running the installation wizard

Opening a console window

To run the installation wizard, which configures the Management Node, you must open a console window on the Management Node

VM.

Opening a console window in vSphere

1. Using either the vSphere desktop or web client, log into the Management Node's VM Manager (vCenter Server or, for stand-

alone deployments, the ESXi host).



2. Power on the new Management Node VM (if it is not already powered on).

3. Right-click on the new Management Node VM and select Open Console.

Opening a console window in Hyper-V

1. Log into Hyper-V.

2. Start the new Management Node VM (if it is not already running).

3. Right-click on the new Management Node VM and select Connect....

Running the installation wizard

When you have opened a console window on the Management Node VM, the following prompt will appear:

pexipmcumgr login:

To run the installation wizard:

1. At the prompt, enter the username admin. The display will read:

You are required to change your password immediately (root enforced)

Enter new UNIX password:

2. Create a password for the Management Node operating system by typing the password, pressing enter, retyping the password,

and pressing enter again.

3. Ensure you record the password in a secure location. After you have finished running the installation wizard you will not use it

again unless you need to SSH in to the Management Node.

You will eventually be presented with another login prompt:

Running Pexip installation wizard...

[sudo] password for admin:

4. Log in again with the password you just created.

The Pexip installation wizard will begin.

You can re-run the installation wizard manually at any point - see Re-running the installation wizard

5. Follow the prompts to set the following configuration for the Management Node. If you press enter, the default value will be

applied:



Setting Default value Multiple entries allowed? Can be changed via Pexip Infinity web interface?

IP address 192.168.0.100 * No No ‡

Network mask 255.255.255.0 * No No ‡

Gateway 192.168.0.1 * No No ‡

Hostname <no default> No No ‡

Domain suffix <no default> No No ‡

DNS server 8.8.8.8 Yes, if separated by a space Yes

NTP server † Two of the following:

o 0.pexip.pool.ntp.org




Yes, if separated by a space Yes

Web administration

username

admin No No ‡

Web administration password <no default> No Yes

Enable incident reporting

(yes/no)

<no default> Yes

* These defaults apply only if your network does not have DHCP enabled. If DHCP is enabled, the defaults will be those

allocated by the DHCP server. The addresses you enter using this wizard will be assigned as static IP addresses.

† The NTP server must be accessible by the Management Node at the time the startup wizard is run. Installation will fail if the

Management Node is unable to synchronize its time with an NTP server.

‡ After they have been configured, do not attempt to change these settings by any other means. To change these settings,

you must re-run the installation wizard.

The installation will begin and the Management Node will restart using the values you have configured.

When the Management Node has restarted the console will display a login prompt:

<hostname> login:

At this point you can close the console. All further configuration should now be done Using the Pexip Infinity web interface.

Re-running the installation wizardIf you enter the wrong information during initial configuration using the installation wizard, or if you exit the wizard before

completing all the steps, you can re-run it. However, this will overwrite any existing Management Node configuration and lose all

connections to existing Conferencing Nodes. Therefore, if you re-run the installation wizard after deploying any Conferencing Nodes,

you must delete any existing Conferencing Nodes from VMware and then redeploy them from the updated Management Node.

To re-run the installation wizard:



1. Open a console window on the Management Node VM.

2. At the login prompt, enter the password created in step 2 of Running the installation wizard. If you did not get as far as creating a new password, you will be asked to create one now.

3. Type installwizard.

The Pexip installation wizard will begin.



Using the Pexip Infinity web interface

Accessing the Management Node web interfaceAfter you have run the installation wizard, all further configuration should be done using the Pexip Infinity web interface, which is

hosted on the Management Node. To access this:

1. Open a web browser and type in the IP address or DNS name that you assigned to the Management Node using the installation

wizard (you may need to wait a minute or so after installation is complete before you can access the web interface).

2. Until you have uploaded appropriate TLS certificates to the Management Node, your browser may present you with a warning

that the website's security certificate is not trusted. You should proceed, but upload appropriate TLS certificates to the Management Node (and Conferencing Nodes, when they have been created) as soon as possible.

The Pexip Infinity Conferencing Platform login screen will appear.

3. Log in using the web administration username and password you set using the installation wizard.

You are now ready to begin configuring the Pexip Infinity service and deploying Conferencing Nodes.

As a first step, we strongly recommend that you configure at least 2 additional NTP servers or NTP server pools to ensure that log

entries from all nodes are properly synchronized. For details, see Enabling NTP on the Management Node.

For further information on the next steps, see Managing the Pexip Infinity.

Session timeoutPexip Infinity web interface sessions will time out after 30 minutes of inactivity.

Getting helpThere are two types of help integrated into the Pexip Infinity web interface:

Field-level help

By default, most configuration fields will show an explanation of the field underneath the input area. You can turn these

explanations on or off by clicking on the icon on the bottom right of the page.

Context-sensitive help

From any page, clicking on the Help link at the top right of the page will open a new browser window showing the online Pexip

Infinity Administrator Guide, which will be opened to the section that relates to the page you are on. From there you can use the

table of contents on the left-hand side of the help window to navigate and view the entire guide. There is also a search box at the

top right of the browser window which you can use to search for individual words or phrases.

The Pexip Infinity Administrator Guide is also available in PDF format from the Pexip website at www.pexip.com/administrator-

guide.

Contacting support

If the information you require is not available in the Administrator Guide, contact your authorized Pexip representative for

assistance.

http://www.pexip.com/administrator-guide

Pexip Infinity Administrator Guide Managing the Pexip Infinity


Managing the Pexip InfinityIn this section:

Enabling DNS 50

Enabling NTP on the Management Node 51

Enabling SNMP 52

Using a syslog server 55

About VM Managers 56

About system locations 58

About H.323 gatekeepers and SIP proxies 60

About Lync servers 61

About TURN servers 62

Editing the Management Node 63

About Conferencing Nodes 66

Deploying new Conferencing Nodes 67

Editing existing Conferencing Nodes 79

Deleting Conferencing Nodes 81

About licenses 82

Managing TLS certificates 85



Enabling DNSAt least one DNS server must be added to your system.

DNS is required when using hostnames instead of IP addresses when setting up NTP servers, syslog servers and VM Managers to be

used by the Pexip Infinity. It is also used for call routing that depends on FQDNs.

To add, edit or delete DNS servers, go to System configuration > DNS servers.

The available options are:

Option Description

Address The IP address of the DNS server.



Enabling NTP on the Management NodeAll host servers must be synchronized with accurate time before you install the Pexip Infinity Management Node or


You must enable NTP on your Management Node before deploying any Conferencing Nodes.

The Pexip Infinity uses NTP servers to obtain accurate system time. This is necessary to ensure correct operation, including

configuration replication and log timestamps.

Pexip Infinity uses the UTC timezone across the entire platform.

We strongly recommend that you configure at least 3 distinct NTP servers or NTP server pools to ensure that log entries from all

nodes are properly synchronized.

To add, edit or delete NTP servers, go to System configuration > NTP servers.


Option Description

Address The IP address or hostname of the NTP server.



Enabling SNMP

About Pexip Infinity SNMP supportThe Pexip Infinity Management Node and Conferencing Nodes can be monitored using SNMP.

You enable and disable SNMP support on each node individually. You can optionally nominate an SNMP Network Management

System (NMS) to which trap notifications will be sent, as follows:

l If you have enabled SNMP on the Management Node, you can then nominate the NMS that will receive notifications from it.

For instructions see Enabling SNMP on the Management Node.

l If you have enabled SNMP on a Conferencing Node, you must configure its system location with the NMS to which its

notifications will be sent. The NMS will receive notifications for all Conferencing Nodes in that location that have had SNMP

enabled. For instructions see Enabling SNMP on Conferencing Nodes.

Pexip Infinity supports the basic RFC 1213 MIB-II tree (1.3.6.1.2.1) with read-only functionality. This includes full or partial support

for:

l system_mib

l interfaces

l snmp_mib

l at

l ip

l icmp

l udp

l tcp

l RFC 1514/RFC 2790 MIB-II host MIB

When SNMP has been enabled on a Conferencing Node or Management Node, SNMP traps will be sent to the selected SNMP NMS

in a number of scenarios including, in this release, in the following situations:

Trap OID Description

cold start 1.3.6.1.6.3.1.1.5.1 Emitted when the snmpd service running on the node starts or restarts (due to snmp being

reconfigured and/or due to the conferencing node rebooting).

authentication

failure

1.3.6.1.6.3.1.1.5.5 Generated, for example, when any attempt to query SNMP values is made using an incorrect

community string.

warm start 1.3.6.1.6.3.1.1.5.2 Generated when any software component fails unexpectedly (and coincides with the

generation of a Pexip Incident Report).

The SNMP support in this release of the Pexip Infinity is built on top of the popular net-snmp open source implementation and

therefore inherits some of the same behaviors (for example, generating a coldstart rather than warmstart on reconfiguration). For

this reason you may also see some net-snmp-specific traps, such as the nsNotifyShutdown trap (OID 1.3.6.1.4.1.8072.4.0.2) when the snmpd daemon shuts down.



Adding SNMP NMSsIf you want SNMP notifications to be sent to a SNMP Network Management System (NMS) from a Management Node or

Conferencing Node, you should add the details of the NMS to the Pexip Infinity before you enable SNMP on the node.

To do this:

1. Navigate to Platform configuration > SNMP NMSs and select Add SNMP Network Management System.

2. Complete the required fields:

Option Description

Name The name used to refer to this SNMP Network Management System

Description An optional description of the SNMP Network Management System.

Address The IP address or hostname of the SNMP Network Management System.

Port The SNMP port of the Network Management System.

SNMP trap community The SNMP trap community name.

3. Select Save.

The NMS will now be available for selection on the Edit Management Node page when Enabling SNMP on the Management

Node, and the Edit System Location page when Enabling SNMP on Conferencing Nodes.

Enabling SNMP on the Management NodeTo enable SNMP on the Management Node:

1. Navigate to Platform configuration > Management Node and select the Management Node.

You will be taken to the Edit Management Node page.

2. From the SNMP mode drop-down menu, select SNMPv2c read-only.

3. If you want SNMP traps to be sent from the Management Node to a particular SNMP Network Management System (NMS),

select the NMS from the SNMP NMS drop-down menu.

If you have not already added the SNMP NMS, you can do so now by clicking .

4. Update the other SNMP fields as required.

5. Select Save.



Enabling SNMP on Conferencing NodesTo enable SNMP on a Conferencing Node:

1. Navigate to Platform configuration > Conferencing Nodes and select the Conferencing Node.

You will be taken to the Edit Conferencing Node page.

2. From the SNMP mode drop-down menu, select SNMPv2c read-only.

3. Update the other SNMP fields as required.

4. Select Save.

5. If you want SNMP traps to be sent from the Conferencing Node to a particular SNMP Network Management System (NMS):

a. Navigate to Platform configuration > Locations.

b. Select the Location to which the Conferencing Node belongs.

You will be taken to the Edit System Location page.

c. From the SNMP NMS drop-down menu, select the Network Management System to which traps will be sent. This will

apply to all Conferencing Nodes in this location that have had SNMP enabled.

If you have not already added the SNMP NMS, you can do so now by clicking .

d. Select Save.



Using a syslog serverThe Management Node acts as a syslog server, collating the logs from itself and each Conferencing Node to produce the Pexip

Infinity support log. The support log includes the administrator log.

However, you can also use a remote syslog server to collect copies of each system's logs. The advantage of this is that, should the

Management Node become unavailable, logging would still continue on the syslog server. Furthermore, you can use the Pexip

Infinity Management API to process the syslog entries to obtain specific information about real-time events, tailored to your

requirements. For more information, see the Pexip Infinity Management API guide.

When a remote syslog server is used, the Management Node and each of the Conferencing Nodes sends its logs directly to the syslog

server using the syslog protocol over UDP. The Management Node will still continue to collate logs from all the nodes, and it is

these logs that will be shown from the web interface.

To add, edit or delete the syslog servers used by this Pexip Infinity, go to System configuration > Syslog servers.


Option Description

Address The IP address or hostname of the remote syslog server.

Port The UDP port on the remote syslog server.




About VM ManagersA VM Manager is an application that allows you to connect to one or more VMware vSphere ESXi hypervisors. The Pexip Infinity logs

in to the selected VM Manager when automatically deploying Conferencing Nodes. It does not log in at any other time, and the

credentials used to log in to the VM Manager are not stored by the Pexip Infinity.

Pexip Infinity version 4 supports VMware vSphere ESXi 4.1 and 5.x hypervisors. The VM Managers used to connect to these

hypervisors are either:

l vCenter Server, an application that allows you to use a single interface to manage one or more host servers running ESXi.

l ESXi directly on the host, used when managing a single host server running ESXi.

You can also log in to a VM manager directly. To connect to vCenter Server, use either the vSphere desktop or web client; to

connect directly to an ESXi host you can only use the vSphere desktop client.

Overview of Pexip Infinity, vSphere clients, VM Manager and ESXi host connectivity

When creating a Conferencing Node for automatic deployment on an ESXi host, you are asked to select the VM Manager to be used.

If the ESXi host on which you wish to deploy the Conferencing Node is managed by vCenter Server, you must select that vCenter Server as the VM Manager. Do not attempt to deploy the conferencing node directly onto the ESXi host (by selecting the ESXi host

as the VM manager).

The Add VM Manager page allows you to create a list of VM Managers in advance of creating your Conferencing Nodes. You can also

add a VM Manager during the process of creating a Conferencing Node.



Adding VM Managers

To add, edit or delete VM Managers, go to System configuration > VM Managers.


Option Description

Name The name that you will use to refer to this VM Manager.

Description An optional field where you can provide more information about the VM Manager.

Address The IP address or hostname of the VM Manager.

If you are using vCenter Server, this will be the IP address or hostname of the vCenter Server.

If you are not using vCenter Server, this will be the IP address or hostname of ESXi on the host server.







About system locationsSystem locations are labels that allow you to group Conferencing Nodes together according to where they are physically located.

System locations serve two purposes:

l They enable the Pexip Infinity to make intelligent decisions about routing.

l External services such as H.323 gatekeepers, SIP proxies, Lync Servers, TURN servers and SNMP NMSs are configured on a per-location basis, and will be used by all Conferencing Nodes in that location.

Intelligent routingGrouping Conferencing Nodes by location allows the Pexip Infinity to make intelligent decisions about routing. For example, if a

single conference is taking place across groups of Conferencing Nodes in two different locations, then the Pexip Infinity will

nominate one Conferencing Node in each location to act as the proxy for that location. Media streams will be sent between each

proxy only, rather than multiple streams being sent between each of the Conferencing Nodes at each of the locations.

When grouping Conferencing Nodes into different locations, you should consider the amount of packet loss within your network. If

there is a chance of packet loss due to network congestion between different groups of Conferencing Nodes by design, then they

should be assigned separate system locations even if they are in the same physical location.

Configuring external services

H.323 gatekeepers, SIP proxies and Lync servers

When setting up a system location you can optionally specify the H.323 gatekeeper, the SIP proxy and the Lync server to be used for

outbound calls from that location. These are the call control systems that will be used when:

l a conference participant uses the Pexip Mobile App to add another participant to the call

l the administrator manually dials out to a participant from a Virtual Meeting Room

l a participant is automatically dialed out to from a Virtual Meeting Room

l a third party uses the API to place a call to a participant

l the Pexip Distributed Gateway is used to interwork a call.

For more information, see About H.323 gatekeepers and SIP proxies and About Lync servers.

TURN servers

If your deployment includes endpoints that use ICE (such as Lync clients, the Pexip Web App, or other WebRTC clients), and these

endpoints will be connecting to a Conferencing Node from outside your firewall, you must also specify a TURN server. When a

Conferencing Node receives a call from an ICE client, it will send a request to the TURN server to allocate bindings to be used by

that client. The client will use these bindings to route its call media through the firewall to the Conferencing Node. For more

information, see About TURN servers.

SNMP NMSs

If you have enabled SNMP support on one or more Conferencing Nodes in a particular location, you must also select the SNMP

Network Management System (NMS) to which SNMP traps will be sent. The selected NMS will be used for all Conferencing Nodes in

this location that have SNMP support enabled. For more information, see Enabling SNMP.



Adding system locations

To add, edit or delete system locations, go to Pexip Infinity > System locations.


Option Description

Name The name you want to give to this physical location.

Description An optional field where you can provide more information about the location.

H.323

gatekeeper

The H.323 gatekeeper to be used for outbound H.323 calls from this location. For more information, see About

H.323 gatekeepers and SIP proxies.

SNMP NMS The Network Management System to which SNMP traps for all Conferencing Nodes in this location will be sent. For

more information, see Enabling SNMP.

SIP proxy The SIP proxy to be used for outbound SIP calls from this location. For more information, see About H.323

gatekeepers and SIP proxies.

Lync server The Lync server to be used for outbound MS-SIP calls from this location. For more information, see About Lync

servers.

TURN

server

The TURN server to be used when ICE clients (including Lync clients and the Pexip Web App) located outside the

firewall connect to a Conferencing Node in this location. For more information, see About TURN servers.

MTU (Maximum Transmission Unit) - the size of the largest packet that can be transmitted via the network interface for

this system location. Whether you need to specify a value here will depend on the settings of your firewall rules.

DSCP value

for media

The DSCP value for media traffic sent from Conferencing Nodes in this system location. This is an optional setting

used to prioritize different types of traffic in large, complex networks.

DSCP value

for

signaling

The DSCP value for signaling traffic sent from Conferencing Nodes in this system location. This is an optional setting

used to prioritize different types of traffic in large, complex networks.



About H.323 gatekeepers and SIP proxiesAll System locations can have a nominated H.323 gatekeeper and/or a SIP proxy. These are the call control systems that will be

used to route outbound H.323 and SIP calls from that location on behalf of the Pexip Infinity.

Pexip Distributed Gateways can also have a nominated H.323 gatekeeper and/or a SIP proxy for each Gateway Routing Rule. These

are the call control systems that will be used to route calls that have been interworked by the Pexip Distributed Gateway to H.323

and SIP respectively.

The H.323 gatekeepers and SIP proxies configured here are used for outbound calls from the Pexip Infinity. They do not

determine the systems used to route inbound calls to the Pexip Infinity. The Pexip Infinity will not automatically register with any

systems configured here. To route inbound calls from a gatekeeper or SIP proxy, you must configure these systems with neighbor

zones that direct calls to the to the Pexip Infinity. For more information see Using a gatekeeper to route calls to Pexip Infinity

conferences.

Outbound calls are made from the Pexip Infinity when:






When a Pexip Mobile App or Pexip Web App user who is connected to a particular Conferencing Node adds another participant, the

call will be routed to the H.323 gatekeeper or SIP proxy associated with the system location to which that Conferencing Node

belongs.

If you do not specify an H.323 gatekeeper or SIP proxy for a system location, Pexip Mobile App and Pexip Web App users connected

to Conferencing Nodes in that location may still be able to dial in other participants. To enable this, the App user must enter an IP

address or FQDN (and for the latter, DNS must be configured properly), thus allowing the Pexip Infinity to dial the participant

directly.

To add, edit or delete an H.323 gatekeeper, go to Platform configuration > H.323 Gatekeepers.

To add, edit or delete a SIP proxy, go to Platform configuration > SIP Proxies.

After adding the details of the H.323 gatekeeper or SIP proxy, you must ensure you then add it to the relevant location (go to

Platform configuration > Locations and select the relevant location).



About Lync serversAll System locations and Pexip Distributed Gateways can have a nominated Lync server. This can be a Front End Server, a Director,

or (if the Conferencing Node is in the DMZ) an Edge Server. The nominated Lync server will be used for outbound MS-SIP calls.

Outbound calls are made from the Pexip Infinity when:






To add, edit or delete Lync servers, go to Platform configuration > Lync Servers.


Option Description

Name The name used to refer to this Lync server in the Pexip Infinity web interface.

Description An optional description of the Lync server.

Address The IP address or hostname of the Lync server.

Port The IP port on the Lync server to which the Conferencing Node will connect.

Transport The IP transport used to connect to the Lync server.



About TURN serversAll System locations and Pexip Distributed Gateways can have a nominated TURN server.

If your deployment includes endpoints that use ICE (such as Lync clients, the Pexip Web App, or other WebRTC clients) and these

endpoints will be connecting to a Conferencing Node from outside your firewall, you must configure at least one TURN server.

You do not need to configure a TURN server if your deployment only includes:

l ICE clients that will connect from inside the network, and/or

l Lync 2010 clients connecting via a VCS Control.

The TURN server must be standards-based (supporting RFC 5766), for example a VCS Expressway.

Microsoft A/V Edge Server does not currently support RFC 5766 and therefore cannot be used with the Pexip Infinity solution.

The TURN server must have a public IP address, and must be located either on the public internet or in a DMZ.

You must nominate one TURN server per location. The same TURN server can be used for more than one location or Pexip

Distributed Gateway.

When a Conferencing Node receives a call from an ICE client, it will send a request to the TURN server to allocate bindings to be

used by that client. The client will use these bindings to route its call media through the firewall to the Conferencing Node. The

Conferencing Node will allocate up to four TURN bindings per call (made up of two TURN bindings per media stream for both audio

and video).

To add, edit or delete TURN servers, go to Platform configuration > TURN Servers.


Option Description

Name The name used to refer to this TURN server in the Pexip Infinity web interface.

Description An optional description of the TURN server.

Address The IP address of the TURN server.

Port The IP port on the TURN server to which the Conferencing Node will connect.

Username

Password

The credentials of a valid account on the TURN server that can be used to create bindings.

After adding the details of the TURN server, you must ensure you then add it to the relevant location (go to Platform

configuration > Locations and select the relevant location).

http://tools.ietf.org/html/rfc5766



Editing the Management NodeThe Management Node is a virtual machine which controls the Pexip Infinity service. It is used to deploy and manage one or more

Conferencing Nodes, and configure the Pexip Infinity services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions, and

the Pexip Distributed Gateway) that exist on those Conferencing Nodes. It also collates status and logging information about

conferences across all Conferencing Nodes.

Initial configuration of the Management Node was provided at the time the software image was initially installed using the installation wizard, but if necessary you can edit some of this information afterwards.

All changes to the configuration of the Management Node should be done using the Pexip Infinity web interface. Do not make any

changes by any other means such as VMware or SSH; doing so may cause the Pexip Infinity service to fail. In particular you must not

change the IP address of the Management Node.

To edit details of a Management Node, go to Platform configuration > Management Node.




Option Description

Name The name used to refer to this Management Node. It is made up of the DNS Hostname and Domain

suffix that were assigned to the Management Node when the Pexip Infinity software image was

initially installed using the installation wizard.

Description An optional field where you can provide more information about the Management Node.

This will default to the Name but you can change it here.

SNMP mode Off: SNMP is disabled. You will not be able to use SNMP to query the Pexip Infinity for its status.

SNMPv2c read-only: the most basic MIB-II tree (1.3.6.1.2.1) will be supported with read-only

functionality.

For more information on Pexip Infinity and SNMP, see Enabling SNMP.

SNMP community The SNMP group to which this virtual machine belongs.

SNMP system contact The contact details (for example, email address) of the person responsible for this particular machine.

SNMP system location A description of the virtual machine's location.

SNMP NMS The Network Management System to which SNMP traps will be sent from the Management Node.

Enable incident

reporting

Incident reporting URL

If incident reporting is enabled, reports will be sent to the specified URL.

For more information, see Automatically reporting errors.

Media port range start* The start value for the range of ports that Conferencing Nodes use for media.

Media port range end* The end value for the range of ports that Conferencing Nodes use for media.

Signaling port range

start*

The start value for the range of ports that Conferencing Nodes use for signaling.

Signaling port range

end*

The end value for the range of ports that Conferencing Nodes use for signaling.

IPv6 address The IPv6 address for this Management Node.

Gateway IPv6 address The IPv6 address of the default gateway.

* If you change any of these values, each Conferencing Node must be rebooted before the changes will take effect.

Other details of the Management Node that cannot be changed are also shown on this page for your information, as follows:

Option Description

IP address The IPv4 address of the Management Node.

Network mask The IPv4 network mask of the Management Node.

Gateway The IPv4 address of the default gateway.

Hostname The DNS hostname of this Management Node.

Domain The DNS domain of this Management Node.



If you have to change any of the settings in the table above, you must do so by Re-running the installation wizard.

Enabling automatic startupAfter deploying a new Management Node or Conferencing Node from VMware, you must enable automatic startup of that virtual













7. Select OK.









7. Select OK.



About Conferencing NodesThe Pexip Infinity platform comprises one Management Node and one or more Conferencing Nodes.

Conferencing Nodes are virtual machines that provide the capacity for conferences. They handle the media and signaling.

The Pexip Infinity platform can have Conferencing Nodes that are located across one or more system locations and managed by one

or more VM Managers.

A Conferencing Node can co-exist on the same host server as a Management Node.

All Conferencing Nodes get the same service configuration from the Management Node. This means that participants throughout

your organization can access the same Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions and the Pexip Distributed

Gateway even though they might be connected to different Conferencing Nodes.

Each Conferencing Node must have a unique:

l Name

l IP address

l Hostname

l DNS name (hostname and domain)

Conferencing Nodes may have the same or different:

l SNMP settings

About maintenance modeWhen a Conferencing Node goes into maintenance mode, it will not accept any new calls. Any existing calls on that Conferencing

Node will not be affected. After all existing calls have terminated, this will result in a Conferencing Node that is live and contactable

but will not be handling any calls.

A Conferencing Node will go into maintenance mode for one of three reasons:

1. The system administrator has elected to put the Conferencing Node into maintenance mode. This is done from the Pexip

Infinity web interface by navigating to Platform configuration > Conferencing Nodes, selecting the relevant Conferencing

Node, and selecting the Enable maintenance mode checkbox.

This setting will persist after a reboot.

2. The Pexip Infinity is being upgraded, during which time each Conferencing Node in turn is automatically put into maintenance

mode and upgraded. For more information, see Upgrading the Pexip Infinity.

3. The Conferencing Node has been installed on a system that does not meet the CPU instruction set requirements. In such a case:

o after initial deployment, the following message will appear in the admin log:

CPU instruction set is not supported; system will be placed in maintenance mode

o each time the Conferencing Node rejects a call, the following message will appear in the admin log:

Message="Participant failed to join conference." Reason="System in maintenance mode"

o any manual changes to the Enable maintenance mode will have no impact - the Conferencing Node will remain in

maintenance mode regardless of this setting.



Deploying new Conferencing NodesConferencing Nodes must always be created using the Pexip Infinity web interface. Do not use VMware, Hyper-V or any other

tools to clone instances of existing Conferencing Node virtual machines (VMs).

Prerequisites l All host servers must be synchronized with accurate time before you install the Pexip Infinity Management Node or


l You must enable NTP on the Pexip Infinity Management Node before you deploy any Conferencing Nodes.

Deployment typesTo create a new Conferencing Node, first a generic instance of a Conferencing Node VM is created, and then it is configured with

the details of the specific Conferencing Node being deployed.

This process has been automated (or partly automated) for environments using VMware ESXi or Microsoft Hyper-V hypervisors, which

are supported in Pexip Infinity. However, Pexip also provide the Conferencing Node VM template and the ability to generate a

Conferencing Node-specific configuration file for deployment in other environments using non-supported hypervisors or

orchestration layers.

The different deployment options are described in the table below. A Pexip Infinity deployment can contain Conferencing Nodes

created using any combination of these methods.



Deployment type Description

Automatic (ESXi 4.1 and

5.x)

The Pexip Infinity deploys the Conferencing Node VM on a host server running VMware vSphere ESXi

4.1 or higher.

Choose this option if you want to deploy the Conferencing Node immediately, and there is network

connectivity to the host server on which the Conferencing Node is to be deployed.

For more information, see Automatically deploying a new Conferencing Node.

Manual (ESXi 5.x) The Pexip Infinity generates an .ova file that you must then manually deploy on a host server running

VMware vSphere ESXi 5.0 or higher, in order to create the Conferencing Node VM.

Choose this option if the Management Node does not have existing connectivity to the host server

on which the Conferencing Node is to be deployed, or you do not want to deploy the Conferencing

Node immediately.

For more information, see Manually deploying a Conferencing Node on an ESXi host.

Manual (ESXi 4.1) The Pexip Infinity generates an .ova file that you must then manually deploy on a host server running

VMware vSphere ESXi 4.1 in order to create the Conferencing Node VM.

Choose this option if the Management Node does not have existing connectivity to the host server

on which the Conferencing Node is to be deployed, or you do not want to deploy the Conferencing

Node immediately.

For more information, see Manually deploying a Conferencing Node on an ESXi host.

Manual (Hyper-V 2012) The Pexip Infinity generates a file that you must then manually deploy on a host server running either

Microsoft Hyper-V Server 2012 and higher, or Windows Server 2012 and higher, in order to create

the Conferencing Node VM.

Choose this option for all deployments that use Hyper-V.

For more information, see Manually deploying a Conferencing Node on a Hyper-V host.

Configuration-only The Pexip Infinity generates a file containing the configuration of the Conferencing Node. You then

upload this file to a generic Conferencing Node that has been created from the Pexip-supplied VM

template, in order to configure it with the appropriate settings.

Choose this option for any deployments that do not use ESXi or Hyper-V hypervisors.

For more information, see Deploying a Conferencing Node using a VM template and configuration

file.

Automatically deploying a new Conferencing NodeTo automatically deploy a new Conferencing Node on to a VMware ESXi host:

1. Go to Platform configuration > Conferencing Nodes and select Add Conferencing Node.

2. From the Deployment type field, select Automatic.

3. Select Next.

4. You are now asked to log in to the VM Manager via which the Conferencing Node virtual machine is to be created, by

completing the following fields:



Option Description

VM Manager Select the VM Manager via which this Conferencing Node VM will be created.

If the VM Manager does not appear in the drop-down list, you can add it by clicking at the right of the

field.

Username

Password

Enter a valid username and password to log in to the selected VM Manager.

5. When you have completed these fields, click Next.

There may be a slight delay while the Pexip Infinity locates and logs in to the VM Manager, and obtains information from it.

6. You are now asked to nominate the resource pool on the VM Manager where the Conferencing Node VM will be created, by

completing the following field:

Option Description

Resource path Select the path of the resource pool in which the Conferencing Node will be created.

The options available in the drop-down menu reflect what is currently configured in the VM

Manager. To add a new path, you must do so using vCenter Server (or the ESXi host if you are

not using vCenter Server) prior to creating the Conferencing Node.

7. When you have completed this field, click Next.

8. You are now asked to provide the VM Manager with parameters relating to the Conferencing Node, by completing the following

fields:

Option Description

Host network Select the host network on which this Conferencing Node will be deployed.

The options shown here are the vSphere switches that have been configured on the VM

Manager on which this Conferencing Node is being deployed.

Host datastore Select the datastore on the host server to be used by this Conferencing Node.

The options shown here are the datastores that have been configured on the VM Manager via

which this Conferencing Node is being deployed.


10. You are now asked to provide the VM Manager with information regarding the CPUs and memory of the Conferencing Node, by

completing the following fields:



Option Description

Number of virtual CPUs to

assign

Enter the number of virtual CPUs to assign to the Conferencing Node. We do not recommend

that you assign more virtual CPUs than there are physical cores on a single processor on the

host server. For example, if the host server has 2 processors each with 8 physical cores, we

recommend that you assign no more than 8 virtual CPUs.

System memory (in

megabytes)

Enter the amount of RAM (in megabytes) to assign to the Conferencing Node. The number

entered must be a multiple of 4.

We recommend 1 GB RAM for each CPU.


12. You are now asked to provide the network configuration to be applied to the Conferencing Node, by completing the following

fields:

Option Description

Name Enter the name that will be used to refer to this Conferencing Node in the Pexip Infinity web

interface.

Description An optional field where you can provide more information about the Conferencing Node.

IP address Enter the IP address to be assigned to this Conferencing Node when it is created in VMware.

Network mask Enter the IP network mask to be assigned to this Conferencing Node.

Gateway IP address Enter the IP address of the default gateway to be assigned to this Conferencing Node.

Hostname

Domain

Enter the hostname and domain to be assigned to this Conferencing Node. Each Conferencing

Node and Management Node must have a unique hostname.

The Hostname and Domain together make up the Conferencing Node's DNS name or FQDN. We

recommend you assign valid DNS names to all your Conferencing Nodes. For more information,

see Assigning hostnames and FQDNs.

System location Select the physical location of this Conferencing Node.

If the system location does not already exist, you can create a new one here by clicking to

the right of the field. This will open up a new window showing the Add system location page.

For further information see About system locations.

Enable maintenance mode While maintenance mode is enabled, this Conferencing Node will not accept any new

conference instances. For more information, see About maintenance mode.

The maintenance mode setting will persist after a reboot.

SSH password Enter the password to be used when logging in to this Conferencing Node's Linux operating

system over SSH. The username will always be admin.

Logging in to the operating system is required when changing passwords or for diagnostic purposes only, and should generally be done under the guidance of Pexip support. In particular,

do not change any configuration using SSH - all changes should be made using the web

interface.



13. When you have completed these fields, click Finish.

You will be taken to the Deploying Conferencing Node page. After a short time the progress bar will show that the Conferencing

Node VM has been deployed successfully and the Status will say Deployment succeeded.

Go to Platform configuration > Conferencing Nodes to return to the list of Conferencing Nodes.

Manually deploying a Conferencing Node on an ESXi host

The manual deployment process generates an .ova file that must then be manually deployed from within VMware on to an ESXi

host.

This file is specific to the Conferencing Node being deployed, so it cannot be used to deploy multiple Conferencing Nodes.

The file is also single-use, so it cannot be used to re-deploy the same Conferencing Node at a later date. To re-deploy the

Conferencing Node, you must first delete it from the Pexip Infinity Management Node and from VMware, and then deploy a new

Conferencing Node with the same configuration as the deleted node.

To manually deploy a new Conferencing Node on to a VMware ESXi host:


2. From the Deployment type field, select Manual.

3. Select Next.

4. You are now asked to provide information regarding the CPUs and memory of the Conferencing Node, by completing the

following fields:

Option Description


assign

Enter the number of CPUs to assign to the Conferencing Node. We do not recommend that

you assign more virtual CPUs than there are physical cores on a single processor on the host

server. For example, if the host server has 2 processors each with 8 physical cores, we


System memory (in

megabytes)




5. Select Next.


fields:



Option Description


interface.


IP address Enter the IP address to be assigned to this Conferencing Node when it is created in VMware.



Hostname

Domain



The Hostname and Domain together make up the Conferencing Node's DNS name or FQDN.

We recommend you assign valid DNS names to all your Conferencing Nodes. For more

information, see Assigning hostnames and FQDNs.



the right of the field. This will open up a new window showing the Add system location

page. For further information see About system locations.






Logging in to the operating system is required when changing passwords or for diagnostic purposes only, and should generally be done under the guidance of Pexip support.


You will be taken to the Manually Deploy Conferencing Node page.

8. Select Download Conferencing Node.

A file with the name pexip-<hostname>.<domain>.ova will be downloaded.

9. When you wish to deploy the Conferencing Node VM, use a vSphere client to log in to vCenter Server (or the ESXi host directly,

if it is not managed in vCenter Server) and select File > Deploy OVF template.... Follow the on-screen prompts to deploy the

.ova file.



If you receive the following warning, check the Accept extra configuration options box:

Manually deploying a Conferencing Node on a Hyper-V hostTo manually deploy a new Conferencing Node on to a Hyper-V host:


2. From the Deployment type field, select Manual (Hyper-V 2012).

3. Select Next.

4. You are now asked to provide information regarding the CPUs and memory of the Conferencing Node VM, by completing the

following fields:

Option Description

Number of CPUs to assign Enter the number of CPUs to assign to the Conferencing Node. We do not recommend that

you assign more virtual CPUs than there are physical cores on a single processor on the host

server. For example, if the host server has 2 processors each with 8 physical cores, we


System memory (in

megabytes)




5. Select Next.


fields:



Option Description


interface.


IP address Enter the IP address to be assigned to this Conferencing Node when it is created.



Hostname

Domain


















8. Select Download Conferencing Node.

A zip file with the name pexip-<hostname>.<domain>.zip will be downloaded.

9. When you wish to deploy the Conferencing Nodes:

a. Copy the zip file to the server running Hyper-V and unzip it.

You will see a subfolder called Virtual Machines, containing an XML file which contains the configuration for the

Conferencing Node VM.

b. Open the Hyper-V Manager and select Import Virtual Machine....

c. Follow the on-screen prompts to deploy the Conferencing Node VM. When prompted, select the Virtual Machines folder and the Hyper-V manager will automatically discover the XML file.

Deploying a Conferencing Node using a VM template and configuration fileCreating a new Conferencing Node is a two-step process:



1. A generic instance of a Conferencing Node VM is created using a template provided by Pexip.

2. The VM is configured with the details of the specific Conferencing Node being deployed.

This process has been automated (or partly automated) for environments using VMware ESXi or Microsoft Hyper-V hypervisors, which

are supported in Pexip Infinity. However, Pexip also provide the Conferencing Node VM template and the ability to generate a

Conferencing Node-specific configuration file for you to deploy yourself using non-supported hypervisors or orchestration layers.

Prerequisites

l The Conferencing Node must be deployed in a VM environment that supports address assignment by DHCP.

l You must know the IP address that will initially be assigned to the Conferencing Node. You will use this IP address to connect to

the VM in order to upload the configuration file, but this configuration file may then assign a new IP address to the

Conferencing Node.

Deployment process

To create a new Conferencing Node using the VM template:

1. Within your chosen environment, download the VM template file pexip-conferencing-node.ova from the link provided to you

and use it to create a generic instance of a Conferencing Node.

Ensure you are using a VM template with the same Pexip Infinity software version as that which is currently running on the

Management Node. If the Management Node has been upgraded, you will need to download the Conferencing Node VM

template corresponding to that software version. For more information, see Upgrading configuration-only deployments.


3. From the Deployment type field, select Configuration only.

4. Select Next.


fields:



Option Description


interface.


IP address Enter the IP address to be assigned to this Conferencing Node when it is created.



Hostname

Domain


















7. Select Download Conferencing Node Configuration.

A zip file with the name pexip-<hostname>.<domain>.xml will be downloaded.

8. Browse to https://<conferencing-node-ip>:8443/ and use the form provided to upload the configuration file to the

Conferencing Node VM.

The Conferencing Node will apply the configuration and then reboot. When it has rebooted, it will connect to the Management

Node in the usual way.

9. Within your hypervisor, configure the Conferencing Node VM with information regarding the CPUs and memory to be assigned

to it, as follows:



Option Description


assign

Enter the number of virtual CPUs to assign to the Conferencing Node. We do not recommend

that you assign more virtual CPUs than there are physical cores on a single processor on the

host server. For example, if the host server has 2 processors each with 8 physical cores, we


System memory (in

megabytes)




Assigning hostnames and FQDNsEach Conferencing Node and Management Node within your deployment must have a unique hostname.

Hostnames can be made of a combination of numbers, letters, and the - character, and are case-insensitive. Hostnames cannot be

entirely numeric.

The hostname and the domain together make up the system's DNS name or FQDN.

We recommend that you assign valid DNS names or FQDNs to all your Conferencing Nodes. Doing so will make managing your

deployment easier, for example by:

l allowing you to route calls more easily

l allowing you to use more manageable TLS certificates

l allowing you to effectively change the IP address of a Conferencing Node (by re-deploying a new system using the same DNS

name but a different IP address)

l making the system easier to access for the purposes of troubleshooting.

To assign a DNS name to a Conferencing Node, enter a valid Hostname and Domain combination when first creating the

Conferencing Node.

Adding SNMP information

For information on Pexip Infinity and SNMP, see Enabling SNMP.

After the Conferencing Node has been created, you can edit the following optional fields:

Option Description



functionality.


SNMP system contact The contact details (for example, email address) of the person responsible for this particular

machine.




Enabling automatic startup

Hyper-V

By default, virtual machines deployed using Hyper-V will be configured to restart automatically if they were running when the host

server was shut down or powered off. We recommend that you leave this setting as is.

ESXi

After deploying a new Management Node or Conferencing Node from VMware, you must enable automatic startup of that virtual













7. Select OK.









7. Select OK.



Editing existing Conferencing NodesTo edit or delete an existing Conferencing Node, go to Platform configuration > Conferencing Nodes and click on the name of the

Conferencing Node.

Any changes to the configuration of the Conferencing Node should be done using the Pexip Infinity web interface. Do not make any

changes using other tools (such as VMware or Hyper-V); doing so may cause the Conferencing Node to fail.

When editing existing Conferencing Nodes, the following information can be changed:

Option Description

Name The name used to refer to this Conferencing Node in the Pexip Infinity web interface. Each

Conferencing Node must have a unique name.




functionality.

For more information on Pexip Infinity and SNMP, see Enabling SNMP.


SNMP system contact The contact details (for example, email address) of the person responsible for this particular

machine.


Enable maintenance mode While maintenance mode is enabled, this Conferencing Node will not accept any new conference

instances. For more information, see About maintenance mode.


SIP TLS FQDN An identity for this Conferencing Node, used in signaling SIP TLS Contact addresses. For more

information, see SIP TLS FQDN.

Other details of the Conferencing Node that cannot be changed are also shown on this page for your information, as follows:

Option Description

IP address The IP address of this Conferencing Node.

Network mask The IP network mask for this Conferencing Node.

Gateway IP address The IP address of the default gateway.

Hostname

Domain

The DNS hostname and domain of this Conferencing Node. Together these make up the machine's

FQDN, or DNS Name in VMware.

For more information, see Editing existing Conferencing Nodes.

System location The physical location of this Conferencing Node.



SIP TLS FQDN

If your deployment includes Microsoft Lync, you must configure each Conferencing Node with a SIP TLS FQDN. However, for

security purposes we recommend that all deployments use SIP TLS FQDNs.

The FQDN in the SIP TLS FQDN field is used in SIP signaling over TLS, and specifies the identity that the Conferencing Node service will use when identifying itself to the systems connecting to it.

The SIP TLS FQDN:

l must match one of the identities returned in the certificate for the SIP TLS port, and

l must have an entry DNS

so that the identity of the Conferencing Node can be verified by the systems connecting to it.

The SIP TLS FQDN can be the same as the Conferencing Node's FQDN (made up of its Hostname and Domain).

If the SIP TLS FQDN field is left blank, the IP address of the Conferencing Node will be used in SIP TLS signaling, and, depending on your call control configuration, this may result in calls failing.

For more details on the use of domain certificates in SIP, see section 4 of RFC 5922.

Changing IP addressIf you need to change the IP address of a Conferencing Node, you should:

1. Add a new Conferencing Node with the new IP address.

2. Make any necessary changes to your call control system so that calls are routed to the new Conferencing Node.

3. Put the existing Conferencing Node into maintenance mode.

4. When all calls on the existing Conferencing Node have terminated, delete the existing Conferencing Node.

There is no limit on the number of Conferencing Nodes that you can add to the Pexip Infinity platform, and all Conferencing Nodes

have identical conference configuration obtained from the Management Node. Adding a Conferencing Node with the new IP address

and then deleting the Conferencing Node with the old IP address therefore ensures service continuity.

Do not attempt to change the IP address of a Conferencing Node using utilities available in external tools (such as VMware or Hyper-

V) because this will cause Pexip Infinity services to fail.

http://tools.ietf.org/html/rfc5922#section-4



Deleting Conferencing NodesWhen deleting a Conferencing Node, you must first remove its details from the Pexip Infinity platform using the Pexip Infinity web

interface, and then delete it from the hypervisor.

The steps are as follows:

1. Put the Conferencing Node into maintenance mode and wait until all calls on it have terminated.

2. From the Pexip Infinity web interface, go to Platform configuration > Conferencing Nodes.

3. Select the Conferencing Node(s) to be deleted, and from the Action drop-down menu select Delete selected Conferencing

Nodes.

4. Select Go and on the following page confirm that you want to delete the selected Conferencing Nodes by selecting Yes, I'm

sure.

5. Log in to the VM Manager, shut down the deleted Conferencing Node and then power it off.

6. Right-click on the Conferencing Node and select Delete from Disk (VMware) or Delete (Hyper-V).



About licensesBefore you can place calls to Pexip Infinity services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions and the Pexip

Distributed Gateway), you must install a license.

The license allows use of the Pexip Infinity software, and specifies the total number of endpoint participants that can be accessing

any Pexip Infinity service (Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions or the Pexip Distributed Gateway) across

the entire Pexip Infinity deployment at any one time.

The Pexip Web App consumes one port license per connection, as per any other endpoint.

Participants who are sending or receiving presentations do not require any additional licenses. However, if a participant is using the

Pexip Web App in presentation-only mode, this will consume a license.

Pexip Mobile App users do not require or consume licenses.

License allocationWhen a Conferencing Node receives a request from a participant to join a Virtual Meeting Room, Virtual Auditorium or Virtual

Reception, or to interwork a call using the Pexip Distributed Gateway, it contacts the Management Node to see whether there is a

license available. If so, the call will be allowed and one concurrent port license will be allocated to that participant for the duration

of the call. When the call is terminated, the license will be returned to the pool.

If there are no licenses available, or the existing license is not valid, the participant will be advised that they are not permitted to

join the conference along with the reason why, and a corresponding message will appear in the support log.

In some cases your licenses may include an overdraft. This is intended to cover instances where the number of concurrent users

temporarily exceeds the number of available licenses.

If the Conferencing Node is unable to contact the Management Node, the call will be permitted on the assumption that a license is

available. After the Management Node has been out of contact for 14 days, all calls will be rejected.

Viewing existing licenses

To see what licenses are currently installed on your system, go to Platform configuration > Licenses.

The Licensing section lists the licenses that have been activated successfully.

The Stored license request section lists the licenses that were not activated automatically, and are awaiting manual activation.

Adding licensesTo add a new license:

1. On the Pexip Infinity web interface, go to Platform configuration > Licenses.

2. Select Add License.

3. In the License entitlement key field, enter the activation key provided by your authorized Pexip representative.

4. Leave the Manually activate checkbox clear (unless you have been instructed to select this option by your Pexip support representative).

5. Select Save.

The Pexip Infinity will automatically generate an XML file containing the license request (for more information, see Content of the

license request XML file). It will then attempt to contact the Pexip licensing server and send it this file in order to activate the



license. To enable this, you must have an active internet connection from the Management Node, and your firewall must be

configured to allow a connection from the Management Node to pexip.flexnetoperations.com (64.14.29.85) on HTTPS (port 443).

l If the license is activated successfully, you will be returned to the Licensing page and will see the new license under the

Licensing section.

l If the activation attempt is unsuccessful (for example, if the Management Node was unable to establish a connection to the

Pexip licensing server), or you selected Manually activate, the license will be saved as a Stored license request. You must

then activate it manually.

Manually activating a stored license requestTo manually activate a stored license request:

1. Go to Platform configuration > Licenses.

The Stored license request section lists the licenses that were not able to be activated automatically, and are awaiting manual

activation.

2. Select the license you wish to activate.

3. Select Export stored license request.

This generates an XML file containing the request (for more information, see Content of the license request XML file).

4. Download the XML file and send it to your authorized Pexip representative for activation. They will respond with an XML

activation file.

5. When you receive the XML file, go back to Platform configuration > Licenses, select the stored license request, and select

Complete stored license request.

6. Browse to the location of the XML activation file you have received.

7. Select Save.

The license should now be activated and appear in the Licensing section.

Deactivating a licenseYou may need to deactivate a license, for example if you want to migrate licenses between Management Nodes. To do this:

1. Select the license you wish to deactivate.

2. Select Return license.

The Pexip Infinity will attempt to contact the Pexip licensing server to automatically deactivate the license.

l If successful, the license will no longer appear in the list of Licenses.

l If unsuccessful, you must manually deactivate the license by following the same steps in Manually activating a stored license

request.

Repairing a license

If it appears that a license has become corrupt (for example if the Management Node MAC address has changed), a Repair button

will appear under the license information. To reactivate the license, select Repair and then follow the steps outlined in Adding

licenses.



Content of the license request XML fileDuring both automatic and manual license activation, the same license request XML file is set to the Pexip licensing server. The

content of this file includes:

l the license request information (i.e. the detail of what is being requested)

l opaque machine identifiers (computed from various information sources, but not exposing the actual values).

Insufficient versus invalid licenses

If your Pexip Infinity is reporting insufficient licenses, this means that there are valid licenses installed on the system, but at the

point at which a participant tried to join a conference, the number of ports for which there are concurrent licenses had been

exceeded. To remedy this, either wait until one or more existing conferences have completed, thus freeing up some port licenses,

or add more port licenses to your system.

If your Pexip Infinity is reporting an invalid license, this could mean that:

l the license has not been activated

l the existing license has expired

l the existing license has become corrupt.

For more information, go to the Licenses page (Platform configuration > Licenses or contact your authorized Pexip representative for assistance.



Managing TLS certificates

About TLS certificatesTLS certificates are used by the Management Node and each Conferencing Node to verify their identity to clients connecting to

them over HTTPS (web) or SIP TLS. These clients include:

l video endpoints

l web browsers

l third party video network infrastructure devices.

Communication between the Management Node and Conferencing Nodes, and between Conferencing Nodes, does not rely on

TLS certificates; instead it uses an IPsec tunnel. For more information see Encryption methodologies.

The clients must trust the identity of the Certificate Authority (CA) that signed the TLS certificate. The Pexip Infinity platform ships

with default self-signed certificates for the Management Node and each Conferencing Node. Because these certificates are self-

signed, they will not be trusted by clients. We therefore recommend that you replace these certificates with your own certificates

that have been signed by either an external CA or a trusted internal CA.

Process for encrypting communication using TLS

Overview of process for encrypting communication using TLS

In general, to achieve encrypted communication using TLS the following must happen:

1. The CA issues a signed certificate which is uploaded to the server.

2. When a client needs to communicate with the server, it sends a request to the server asking it to provide identification.

3. The server sends back a copy of its TLS certificate and its public key.

4. The client checks whether the CA that issued the certificate is one that it trusts.

5. If the CA is trusted, and if the certificate is otherwise valid, the client creates a session key encrypted with the server's public

key and sends it to the server.



6. The server decrypts the session key. It then uses the session key to encrypt an acknowledgment which it sends to the client in

order to initiate the encrypted communication.

7. The server and the client now encrypt all communication using the session key.

Uploading TLS certificatesTo upload a new TLS certificate for the Management Node or a Conferencing Node:

1. From the Pexip Infinity web interface, navigate to Platform configuration > TLS Certificates.

2. For the selected Management Node or Conferencing Node, select Upload Certificate.

You will be taken to the Upload Certificate page.

3. From the Certificate File section, select Choose File and select the file containing the new TLS certificate.

This file must be a text file in PEM format and must be valid for the hostname or FQDN of the Management Node or

Conferencing Node to which it relates. Certificate files will typically have a .CRT or .PEM extension.

4. From the Private Key File section, select Choose File and select the file containing the private key for the certificate.

This file must be a text file in PEM format. Private key files typically have a .KEY or .PEM extension.

5. Select Save.

There will be a delay of up to 1 minute while the files are synchronized to the relevant Management Node or Conferencing Node.

Viewing existing TLS certificatesTo view information about the existing TLS certificate:

1. Navigate to Platform configuration > TLS Certificates.

2. For the selected Management Node or Conferencing Node, select View Certificate.

Downloading existing TLS certificatesTo download the existing TLS certificate:


2. For the selected Management Node or Conferencing Node, select Download Certificate.

About trusted CA certificatesIn order for a server's TLS certificate to be trusted by a client, the client must be configured to trust the Certificate Authority (CA)

that signed the server certificate. Many CAs do not sign with their root certificate, but instead with an intermediate certificate.

Clients, however, may only trust the root CA. Therefore the server (in this case the Management Node or Conferencing Node) is

often required to present a full certificate chain along with their TLS server certificate.

A Trusted CA Certificate is a file containing all the required CA certificates, one after each other, in PEM format. Such a file can be

uploaded to the Pexip Infinity. If required by the server certificate, they are added to HTTPS and SIP/TLS connection handshakes.

Downloading trusted CA certificatesTo download the existing file containing the trusted CA certificates:


2. Select Download Trusted CA Certificates.



Uploading trusted CA certificatesTo upload a new file containing the trusted CA certificates:

1. Before you start, we recommend that you download and save the existing certificate file - see Downloading trusted CA

certificates.

2. From the Pexip Infinity web interface, navigate to Platform configuration > TLS Certificates.

3. Select Upload Trusted CA Certificates.

You will be taken to the Upload Trusted CA Certificates page.

4. Select Choose File and select the file containing the new TLS certificate.

5. Select Save.

Pexip Infinity Administrator Guide Managing Virtual Meeting Rooms, Virtual Auditoriums and Virtual Receptions


Managing Virtual Meeting Rooms, Virtual Auditoriums and Virtual ReceptionsIn this section:

About Pexip Infinity services 89

About Virtual Meeting Rooms 90

Viewing all Virtual Meeting Rooms 91

Creating and editing Virtual Meeting Rooms 92

About Virtual Auditoriums 95

Creating and editing Virtual Auditoriums 96

About the Virtual Reception 99

About aliases 103

Using multiple aliases 106

Viewing all aliases 107

Creating and editing aliases 108

About PINs, hosts and guests 109

Changing the layout seen by participants 112

Customizing video and voice prompts using themes 114

Automatically dialing out to a participant from a conference 120

Manually dialing out to a participant from a conference 122

Restricting call bandwidth 125

Muting a participant's audio 126


Bulk importing of Virtual Meeting Rooms and Virtual Auditoriums 129

Exporting Virtual Meeting Room configuration 132



About Pexip Infinity servicesThe Service configuration menu allows you to manage the conference services offered by Pexip Infinity. These services include:

l Virtual Meeting Rooms: personal meeting spaces in which you can hold conferences.

l Virtual Auditoriums: larger meeting spaces optimized for use by a small number of hosts and a large number of guests.

l Virtual Receptions: these provide a way for conference participants who cannot dial Virtual Meeting Room and Virtual

Auditorium aliases directly, to access these services from a central point using DTMF tones.

Conference participants access these services by dialing one of the service's aliases. You can change the audio and video prompts

presented to participants when they are accessing these services by applying Themes.

In addition, the Pexip Infinity offers:

l Pexip Distributed Gateway: a service that interworks calls between different protocols. This allows endpoints within your deployment to make conference calls and point-to-point calls to other endpoints that do not use the same protocol.



About Virtual Meeting RoomsA Virtual Meeting Room is a personal virtual meeting space that is always available for use.

Each Virtual Meeting Room has one or more aliases associated with it. Participants access the Virtual Meeting Room by dialing any

one of its aliases - this will route them all to the same conference. For more information, see About aliases, Using multiple

aliases, Creating and editing aliases, and Creating and editing Virtual Meeting Rooms.

Participants can access Virtual Meeting Rooms from any video endpoint, or by using Pexip Infinity's built-in web-based video client -

for more information see Using the Pexip Web App.

Virtual Meeting Rooms can be PIN-protected, and you can also assign host and guest privileges to conference participants. For more

information, see About PINs, hosts and guests.

Administrators manage Virtual Meeting Rooms from the Pexip Infinity web interface. For more information, see Creating and

editing Virtual Meeting Rooms.

There is no limit on the number of Virtual Meeting Rooms that can be configured on your Pexip Infinity platform. The number of

participants who can access a particular Virtual Meeting Room, and the number of Virtual Meeting Rooms that can be in use at the

same time, are limited by the size of your Pexip Infinity deployment.



Viewing all Virtual Meeting RoomsTo view a list of all existing Virtual Meeting Rooms, go to Service configuration > Virtual Meeting Rooms.

From here you can:

l View details of a particular Virtual Meeting Room, including all the aliases associated with it. To do this, click on the Virtual

Meeting Room name. This takes you to the Edit Virtual Meeting Room page. From here you can change the Virtual Meeting

Room details and add, edit and delete aliases.

l Add a new Virtual Meeting Room. To do this, click Add Virtual Meeting Room.



Creating and editing Virtual Meeting RoomsVirtual Meeting Rooms are used to host Pexip Infinity conferences. Each Virtual Meeting Room has one or more aliases associated

with it, and participants access the conference by dialing one of these aliases.

When creating a new Virtual Meeting Room, you must provide at least one alias that will be used to access it. You can also

optionally configure PINs for the conference.

To create a new Virtual Meeting Room, go to Service configuration > Virtual Meeting Rooms and click Add Virtual Meeting

Room.

If you have a large number of Virtual Meeting Rooms to add, you can import their configuration from a CSV file. See Bulk

importing of Virtual Meeting Rooms and Virtual Auditoriums.

You can also manage Virtual Meeting Rooms using the Pexip Infinity API. For more information, see the Pexip Infinity

Management API documentation.

To edit an existing Virtual Meeting Room, or to view its details (including all the aliases associated with it), go to Virtual Meeting

Room configuration > Virtual Meeting Rooms and click on the name of the Virtual Meeting Room.

Any changes you make to Virtual Meeting Room or Virtual Auditorium configuration will be replicated to all conference nodes

within 60 seconds and will be applied to any subsequent conferences in that Virtual Meeting Room or Virtual Auditorium. If there

are any conferences already in place that use the Virtual Meeting Room or Virtual Auditorium, any attempts to join it after the

configuration has been replicated may be affected by the new configuration settings.

We do not recommend changing Virtual Meeting Room or Virtual Auditorium configuration while a conference is in progress

because this will lead to an inconsistent user experience.

When adding or editing Virtual Meeting Rooms, the options are:




Option Description

Name The name used to refer to this Virtual Meeting Room.

Description A description of the Virtual Meeting Room.

Host PIN This optional field allows you to set a secure access code that must be entered by Virtual Meeting Room

participants before they can join the conference.

If Allow Guests is set to Yes, then the Host PIN will apply to the conference host(s) only.

For more information, see About PINs, hosts and guests.

l PINs must use the digits 0-9 only.

l PINs must be between four and ten digits long.

Allow Guests Yes: the conference will have two types of participants, Hosts and Guests. You must enter a Host PIN to

be used by the Hosts. You can optionally enter a Guest PIN; if you do not enter a Guest PIN, Guests can

join without a PIN, but the meeting will not start until the first Host has joined.

No: all participants will have host privileges.

Guest PIN This optional field allows you to set a secure access code that must be entered by Virtual Meeting Room

guests before they can join the conference.


l Guest PINs must use the digits 0-9 only.

l Guest PINs must be between four and ten digits long.

l If you configure a Guest PIN, you must also configure a host PIN.

l Guest PINs must not be the same as the host PIN.

l Guest PINs must have the same number of digits as the host PIN.

Theme The theme for use with this Virtual Meeting Room. For more information, see Customizing video and

voice prompts using themes.

If you leave this blank, the default Pexip theme will be used.

Advanced options

Automatically dialed

participants

When a conference begins in this Virtual Meeting Room, a call will be placed automatically to any

participants selected here. To add an automatically dialed participant that is not already on the list, select

the icon to the right of the selection fields.

For more information, see Automatically dialing out to a participant from a conference.

Maximum inbound

call bandwidth (kbps)

Enter a value in this field to limit the bandwidth of media being received by the Pexip Infinity from each

individual participant dialed in to this Virtual Meeting Room. For more information see Restricting call

bandwidth.

Maximum outbound


Enter a value in this field to limit the bandwidth of media being sent from the Pexip Infinity to each

individual participant dialed in to this Virtual Meeting Room. For more information see Restricting call

bandwidth.



Option Description

Aliases

Alias: #1

Alias The string that, when received by the Pexip Infinity, will cause it to route the call to the associated

service (Virtual Meeting Room, Virtual Auditorium or Virtual Reception).

The alias entered here must match exactly the string received by the Pexip Infinity. Wildcards and regular

expressions are not supported.

In most cases, the alias received by the Pexip Infinity will be the same as the alias that the conference

participant dialed from their endpoint, but there are some exceptions, described in About aliases.

Description An optional description of the alias. This is useful if you have more than one alias for a service.

Add another Alias Select this option if you want the Virtual Meeting Room to be accessible by more than one alias. For

more information, see Using multiple aliases.



About Virtual AuditoriumsA Virtual Auditorium is a meeting space that is optimized for use by a small number of hosts and a large number of guests, for

example:

l a lecture, where the lecturer joins as the host and all the students join as guests

l an internal team meeting, where the department heads join as hosts and all the managers join as guests.

Virtual Auditoriums differ from Virtual Meeting Rooms in that:

l Administrators can configure the Virtual Auditorium so that guests only see hosts, and not any other guests.

l Administrators can configure the Virtual Auditorium so that hosts and guests can see up to 22 other participants, in a 1+21

screen layout.

Virtual Auditoriums use PINs to protect access, and to differentiate between host and guest participants. For more information, see

About PINs, hosts and guests.

To add, edit or delete a Virtual Auditorium, navigate to Service configuration > Virtual Auditoriums. For more information, see

Creating and editing Virtual Auditoriums.

Each Virtual Auditorium has one or more aliases associated with it. Participants access the Virtual Auditorium by dialing any one of

its aliases - this will route them all to the same conference. For more information, see About aliases, Using multiple aliases, and

Creating and editing aliases.

Participants can access Virtual Auditoriums from any video endpoint, or by using Pexip Infinity's built-in web-based video client - for

more information see Using the Pexip Web App.

Administrators manage Virtual Auditoriums from the Pexip Infinity web interface. For more information, see Creating and editing

Virtual Auditoriums.

There is no limit on the number of Virtual Auditoriums that can be configured on your Pexip Infinity platform. The number of

participants who can access a particular Virtual Auditorium, and the number of Virtual Auditoriums that can be in use at the same

time, are limited by the size of your Pexip Infinity deployment.



Creating and editing Virtual AuditoriumsLarger Pexip Infinity conferences can be hosted in Virtual Auditoriums. Each Virtual Auditorium has one or more aliases associated

with it, and participants access the conference by dialing one of these aliases.

When creating a new Virtual Auditorium, you must provide at least one alias that will be used to access it. You have the option of

configuring host and guest PINs for the conference.

To create a new Virtual Auditorium, go to Service configuration > Virtual Auditoriums and click Add Virtual Auditorium.

You cannot convert an existing Virtual Meeting Room into a Virtual Auditorium. Instead, you must create a new Virtual

Auditorium and reassign the existing aliases to it. For more information, see Changing from a Virtual Meeting Room to a Virtual

Auditorium and vice versa.

You can manage Virtual Auditoriums using the Pexip Infinity API. For more information, see the Pexip Infinity Management API documentation.

To edit an existing Virtual Auditorium, or to view its details (including all the aliases associated with it), go to Service configuration

> Virtual Auditoriums and click on the name of the Virtual Auditorium.

Any changes you make to Virtual Meeting Room or Virtual Auditorium configuration will be replicated to all conference nodes

within 60 seconds and will be applied to any subsequent conferences in that Virtual Meeting Room or Virtual Auditorium. If there

are any conferences already in place that use the Virtual Meeting Room or Virtual Auditorium, any attempts to join it after the

configuration has been replicated may be affected by the new configuration settings.

We do not recommend changing Virtual Meeting Room or Virtual Auditorium configuration while a conference is in progress

because this will lead to an inconsistent user experience.

When adding or editing Virtual Auditoriums, the options are:




Option Description

Name The name used to refer to this Virtual Auditorium.

Description A description of the Virtual Auditorium.

Host PIN This optional field allows you to set a secure access code that must be entered by participants before they

can join the conference.

If Allow Guests is set to Yes, then the Host PIN will apply to the conference host(s) only.




Allow Guests Yes: the conference will have two types of participants, Hosts and Guests. You must enter a Host PIN to

be used by the Hosts. You can optionally enter a Guest PIN; if you do not enter a Guest PIN, Guests can

join without a PIN, but the meeting will not start until the first Host has joined.

No: all participants will have host privileges.

Guest PIN This optional field allows you to set a secure access code that must be entered by guests before they can

join the conference.







Host view The maximum number of participants that hosts will see, and the layout used to show them. For more

information, see Changing the layout seen by participants.

Guest view Whether guests will see other guests, the maximum number of participants they will see, and the layout

used to show them. For more information, see Changing the layout seen by participants.

Theme The theme for use with this Virtual Auditorium. For more information, see Customizing video and voice

prompts using themes.

If you leave this blank, the default Pexip theme will be used.

Advanced options


participants

When a conference begins in this Virtual Auditorium, a call will be placed automatically to any

participants selected here. To add an automatically dialed participant that is not already on the list, select

the icon to the right of the selection fields.




Option Description

Maximum inbound


Enter a value in this field to limit the bandwidth of media being received by the Pexip Infinity from each

individual participant dialed in to this Virtual Auditorium. For more information see Restricting call

bandwidth.

Maximum outbound



individual participant dialed in to this Virtual Auditorium. For more information see Restricting call

bandwidth.

Aliases

Alias: #1

Alias The string that, when received by the Pexip Infinity, will cause it to route the call to the associated

service (Virtual Meeting Room, Virtual Auditorium or Virtual Reception).



In most cases, the alias received by the Pexip Infinity will be the same as the alias that the conference

participant dialed from their endpoint, but there are some exceptions, described in About aliases.


Add another Alias Select this option if you want the Virtual Auditorium to be accessible by more than one alias. For more

information, see Using multiple aliases.



About the Virtual ReceptionA Virtual Reception allows participants to use DTMF tones to select the Virtual Meeting Room they wish to join. It provides an

alternative means to access Virtual Meeting Rooms for participants who cannot dial VMR aliases directly.

Generally, in order to access a Virtual Meeting Room, participants dial one of the Virtual Meeting Room's alias directly from their

endpoint. However, some conference participants may not be able to do this. Reasons might include:

l The participant's endpoint might not support dialing by URI - they can only dial by IP address.

l The participant might be using an audio-only PSTN telephone and can only make calls to direct dial numbers.

l Your enterprise might have a limited number of direct dial numbers that can be used for audio participants, and you do not

want to allocate one per VMR.

l Your enterprise uses local, toll-free telephone numbers that audio-only users can dial to access your VMRs and you don't want

to have one of these for every VMR in your enterprise.

To allow for such cases, Pexip Infinity enables you to set up a single direct dial number or IP address that participants can dial to

access a single, central Virtual Reception. From here they can use the DTMF tones on their endpoint to enter the number of the

specific VMR they want to join.

To implement this you must:

1. Create and configure your Virtual Reception.

2. Ensure that every Virtual Meeting Room that you want to be accessible from the Virtual Reception has an alias that consists of

digits only. For more information, see Creating and editing Virtual Meeting Rooms.

3. Provide conference participants with the combination of Virtual Reception alias followed by the Virtual Auditorium or Virtual

Meeting Room number that they must dial to access the conference.

Creating a Virtual ReceptionTo create a Virtual Reception:

1. Navigate to Service configuration > Virtual Receptions.

2. Select Add Virtual Reception.

The following options are available:



Option Description

Name Enter the name you will use to refer to this Virtual Reception.

Description An optional field where you can add details about the Virtual Reception.

Theme Select the to apply to this Virtual Reception. For more information, see Customizing video and voice

prompts using themes.

If you leave this blank, the default Pexip theme will be used..

Advanced options

Maximum inbound

call bandwidth

(kbps)

Enter a value in this field to limit the bandwidth of media being received by the Pexip Infinity from

each individual participant dialed in to this Virtual Reception. For more information see Restricting call

bandwidth.

Maximum

outbound call

bandwidth (kbps)


individual participant dialed in to this Virtual Reception. For more information see Restricting call

bandwidth.

Aliases

Alias: #1

Alias Enter the alias that participants will dial to access the Virtual Reception.

Description An optional description of the alias. This is useful if the Virtual Reception has more than one alias.

Add another alias Select this option if you want the Virtual Reception to be accessible by more than one alias. For more


3. Ensure that every Virtual Meeting Room and Virtual Auditorium that you want to be accessible from this Virtual Reception has

an alias in the form of a number. To do this:

a. Navigate to either Service configuration > Virtual Meeting Rooms or Service configuration > Virtual Auditoriums.

b. Select the name of the Virtual Meeting Room or Virtual Auditorium.

c. In the Aliases section at the bottom of the page, enter the number to be used to access this Virtual Meeting Room or

Virtual Auditorium from the Virtual Reception.

d. Select Save.

ExampleIn this example we want to allow conference participants to access any of our Virtual Meeting Rooms or Virtual Auditoriums as

audio-only participants using a telephone (to allow for situations where they do not have access to a video endpoint), by making a

local, toll-free telephone call to one of the numbers we have provisioned.

Step 1: Create a Virtual Reception

In order to support this, we create the following Virtual Reception:



Option Input Notes

Name Toll-free Virtual Reception access This single Virtual Reception will be accessible globally

by local toll-free numbers.

Description Allow users to dial a local

telephone number and then select

a VMR.

Aliases

Alias: #1

Alias

Description

15556789

US toll-free number

The first alias is the telephone number that participants

in the US will dial to access the Virtual Reception.

Alias: #2

Alias

Description

441116789

UK toll-free number

The second alias is the telephone number that

participants in the UK will dial to access the Virtual

Reception.

Alias: #3

Alias

Description

612226789

Australia toll-free number

We continue to add as many aliases as we need, one for

each local telephone number that can be used.

Now whenever conference participants dial any of the numbers shown above they will be taken to the same central Virtual

Reception.

Step 2: Add aliases to Virtual Meeting Rooms and Virtual Auditoriums

Next, we need to ensure that our Virtual Meeting Rooms and Virtual Auditoriums are accessible from the Virtual Reception. To do

this, we add a new, unique numeric alias to each. In this example, we want conference participants to be able to access Alice's

Virtual Meeting Room by entering 25423 on their keypad, and the All Hands Virtual Auditorium by entering 25499, so we edit these services as follows:

Alice's VMR



Option Input Notes

Name Alice's VMR

Description Alice's personal meeting room

Aliases

Alias: #1

Alias

Description

[email protected]

URI for Alice's VMR

This is the existing alias for Alice's VMR.

Alias: #2

Alias

Description

25423

Number for Alice's VMR when accessing via the

Virtual Reception.

We add this new alias to the existing VMR

configuration.

All Hands Virtual Auditorium

Option Input Notes

Name All Hands

Description Virtual Auditorium for All Hands conference

Aliases

Alias: #1

Alias

Description

[email protected]

URI for All Hands conference

This is the existing alias for the All Hands

conferences.

Alias: #2

Alias

Description

25499

Number for All Hands when accessing via

the Virtual Reception.

We add this new alias to the existing Virtual

Auditorium configuration.

Now Alice can tell participants to join her VMR by doing any of the following:

l dialing [email protected]

l from the US, dialing 15556789 and then entering 25423

l from the UK, dialing 441116789 and then entering 25423.

Likewise, participants can join an All Hands conference by doing any of the following:

l dialing [email protected]

l from the US, dialing 15556789 and then entering 25499

l from the UK, dialing 441116789 and then entering 25499.



About aliasesEvery Virtual Meeting Room (VMR), Virtual Auditorium and Virtual Reception has one or more aliases associated with it.

When the Pexip Infinity receives a call to a Virtual Meeting Room or Virtual Auditorium alias, it creates a conference instance and

routes the call to that conference. Any further calls received to any of the aliases belonging to the same Virtual Meeting Room or

Virtual Auditorium are routed to the same conference instance, for the duration of that particular conference. If the service has

more than one alias, participants can dial any one of the aliases and be routed to the same conference instance. For more


Virtual Receptions also have one or more aliases associated with them. In these cases, when the participant dials a Virtual

Reception alias they will be taken to the Virtual Reception IVR service, from which they can use a DTMF keypad to enter the

number of the Virtual Meeting Room or Virtual Auditorium they wish to join. This number must correspond to a numeric-only alias

of the Virtual Meeting Room or Virtual Auditorium in question. For more information, see About the Virtual Reception.

In most cases, the alias received by the Pexip Infinity will be the same as the alias that the conference participant dialed from their

endpoint, but there are some exceptions, described in Search rules and alias transforms and ENUM.

For the purposes of clarity, when discussing aliases in this guide we will assume that the alias dialed by the endpoint user is the

same as the alias received by the Pexip Infinity.

Restrictions

An alias can include a domain but this is optional (see Domains). Aliases can be made up of:

l numbers

l letters

l dashes

l dots

l a combination of the above.

In certain circumstances an alias can also be in the form of an IP address - for more information see Using IP addresses as aliases.

Aliases do not support wildcards or regular expressions.

Case insensitivityThe aliases that you configure on the Pexip Infinity are not case-sensitive, and the Pexip Infinity treats all incoming aliases as not

case-sensitive.

For example, this means that:

l a user who dials meet.alice will match against a Virtual Meeting Room with an alias of Meet.Alice

l a user who dials Meet.Alice will match against a Virtual Meeting Room with an alias of meet.alice

Ignoring IP addressesThe Pexip Infinity ignores any IP address or IP address and port combination appended to an alias. This is because some SIP

endpoints will automatically add the IP address of their proxy to the URI that is dialed by the user.

For example, a Virtual Meeting Room with a single alias of meet.alice will be matched when an endpoint dials any of:

l meet.alice

l meet.alice@<IPaddress>



l meet.alice@<IPaddress>:<port>

Using IP addresses as aliasesIn order to support users who can only dial by IP address, you can give a Virtual Reception, Virtual Meeting Room or Virtual

Auditorium an alias that is the same as the IP address of one of your Conferencing Nodes.

In this case, when a user dials the IP address, they will be routed directly to the Conferencing Node in question. The Pexip Infinity

will then check to see if the IP address matches any of the aliases configured on it; if so, the call will be routed to the associated

Virtual Reception, Virtual Meeting Room or Virtual Auditorium.

In most cases you would use this feature to assign a Conferencing Node IP address as an alias for a Virtual Reception, so that users

could then select which Virtual Meeting Room or Virtual Auditorium they wish to join. For more information, see About the Virtual

Reception.

Ignoring protocol prefixesThe Pexip Infinity ignores relevant URI schemes included in an alias, as in the case where a SIP endpoint automatically prefixes the

URI dialed by the user with sip:. The ignored prefixes are:

l sip:

l sips:

l h323:

This is because the protocol used for the call does not matter to the Pexip Infinity.

For example, a Virtual Meeting Room with a single alias of meet.alice will be matched when an endpoint dials any of

l sip:meet.alice@IPaddress

l sips:meet.alice@IPaddress

l h323:meet.alice

Search rules and alias transformsSome call control systems (for example the Cisco VCS) support the use of search rules and alias transforms. In these cases, the alias

that was dialed by the endpoint user and received by the call control system may be changed by the call control system in some

way before it is passed on to the Pexip Infinity. Often this is done in larger deployments to support complex dial plans.

For example, the call control system might have a rule that replaces the domain example.com with example.net. This means

that when a user dials [email protected], the call is routed to [email protected]. Therefore it is this

latter alias that must be configured on the Pexip Infinity in order to match it with a Virtual Meeting Room.

ENUMThe ENUM system allows users to dial an E.164 number (for example a telephone number) which is then mapped using DNS to a SIP

URI. For more information, see RFC 3761.

For example, your dial plan could be set up so that when a user dials 555 0123, the call is routed via ENUM to meet.alice.

If your dial plan uses ENUM, the resulting SIP URIs must be included as aliases on the Pexip Infinity in order to match them with a

Virtual Meeting Room.

https://www.ietf.org/rfc/rfc3761.txt



DomainsDomains are optional in aliases. However, when a call is received to an alias in the form of a URI that includes a domain, the domain

is not ignored.

For example, if a Virtual Meeting Room is configured with an alias of meet.alice, users can dial meet.alice or

meet.alice@<IPaddress> to access the meeting room. However, if they dial [email protected] they will not

be able to access the Virtual Meeting Room because the Virtual Meeting Room alias does not include the domain.

When a SIP endpoint user dials an alias that does not include a domain (for example meet.alice), the SIP endpoint will

automatically add its own domain to the alias (making it for example [email protected]). So even if the Virtual

Meeting Room is configured with an alias of meet.alice and this alias is dialed by a participant from a SIP endpoint, the

participant will not be able to join the conference. (H.323 endpoints do not add domains.)

In the absence of a call control system to strip the domain part of the alias, you could instead add to the Virtual Meeting Room a

second alias of [email protected] so that participants can dial meet.alice from either a SIP or H.323 endpoint and

access the same conference.



Using multiple aliasesIt is likely that you will want to enable conference participants to dial different numbers to access the same Virtual Reception. There may also be cases where you want different conference participants to be able to dial different aliases but still end up in the

same Virtual Meeting Room or Virtual Auditorium. Some example deployments where this might be the case are given below.

To achieve this, you can add any number of aliases to a single Virtual Meeting Room, Virtual Auditorium or Virtual Reception.

Adding additional aliases

To add an additional alias to a Virtual Meeting Room, Virtual Auditorium or Virtual Reception while you are creating it, select Add

another Alias.

To add another alias to an existing Virtual Meeting Room, Virtual Auditorium or Virtual Reception:

1. Navigate to:

o Service configuration > Virtual Meeting Rooms,

o Service configuration > Virtual Auditoriums, or

o Service configuration > Virtual Receptions.

2. Select the name of the service you wish to add the alias to.

3. In the Aliases section at the bottom of the page, enter the new alias in the empty Alias field.

4. Select Save.

Examples l If some of your endpoints do not support URI dialing, you could set up a Virtual Meeting Room for Alice with one alias of

meet.alice.jones and another alias of 555 25423. This would give conference participants two different methods of accessing

the same conference.

l If your deployment includes a Virtual Reception, every Virtual Meeting Room and Virtual Auditorium that you want to be

accessible from the Virtual Reception will need to have a numeric-only alias (so that participants can enter the number using

DTMF), in addition to any aliases in the form of a URI. So to continue with our example, you could add a third alias to Alice's

VMR of 25423, which is the number that participants would enter from the Virtual Reception. For more information, see About

the Virtual Reception.

l If you use an ISDN gateway to support telephone participants, you could set up Alice's Virtual Meeting Room with aliases of

meet.alice.jones and an appropriate E.164 number.

l If you do not have or do not wish to use a call control system to transform aliases, you could set up Alice's Virtual Meeting

Room with aliases of meet.alice.jones and [email protected] to support internal and external dialing, and

dialing from both SIP and H.323 endpoints.



Viewing all aliasesTo view a list of all existing aliases for all services (Virtual Meeting Rooms, Virtual Auditoriums and Virtual Receptions), go to Service

configuration > Aliases.

From here you can:

l Sort the list of aliases alphabetically by Alias or by Service name.

l Search for a particular alias.

l Edit an alias. To do this, click on the alias. This takes you to the Change Alias page. From here you can edit details of the alias,

including changing the service with which it is associated.

l Add a new alias. To do this, click Add Alias. You will be asked to select the service with which this alias is to be associated.



Creating and editing aliasesAliases are the strings that users dial to access Pexip Infinity services - Virtual Meeting Rooms, Virtual Auditoriums and Virtual

Receptions. Each alias is associated with a single service, but a service can have more than one alias - for more information, see

Using multiple aliases.

To add a single alias to an existing service, go to Service configuration > Aliases and click Add Alias. This will take you to the Add

Alias page.

You can also add a new alias while creating or editing a service. For further information, see Creating and editing Virtual Meeting

Rooms, Creating and editing Virtual Auditoriums, and About the Virtual Reception.

When adding or editing aliases from the Add Alias page, the options are:

Option Description

Service Select the name of the Virtual Meeting Room, Virtual Auditorium or Virtual Reception that will be accessed when

participants dial this alias.

Alias The string that, when received by the Pexip Infinity, will cause it to route the call to the associated service (Virtual

Meeting Room, Virtual Auditorium or Virtual Reception).



In most cases, the alias received by the Pexip Infinity will be the same as the alias that the conference participant

dialed from their endpoint, but there are some exceptions, described in About aliases.




About PINs, hosts and guestsFor added security, you can set up your Pexip Infinity Virtual Meeting Rooms and Virtual Auditoriums with PIN numbers. You can use

the same PIN for all participants, or you can use PINs to differentiate between hosts and guests. When a participant dials the

alias of a Virtual Meeting Room or Virtual Auditorium that has a PIN, they are presented with an Interactive Voice Response (IVR)

screen where they are asked to enter the PIN number. They must enter the correct PIN before they can join the conference.

Using the same PIN for all participants

All participants in a conference that uses a single PIN will have the same host privileges. (To create a PIN-protected conference

where participants have different levels of privileges, see Using PINs to differentiate between hosts and guests.)

Participants have 3 attempts to enter a correct PIN. After the third unsuccessful attempt, they will hear a message advising them

that the PIN is invalid, and their call will be disconnected.

The first participant to enter the PIN successfully will be shown their own self view until another participant joins the conference.

All PIN entry attempts, successful and unsuccessful, are logged in the administrator log.

To set a PIN number on a Virtual Meeting Room:

1. Go to Service configuration > Virtual Meeting Rooms.

2. Select the Virtual Meeting Room.

3. In the Host PIN field, enter the PIN number to be used.

4. In the Allow Guests drop-down list, select No.

Note that:



Using PINs to differentiate between hosts and guestsYou can set up your Pexip Infinity Virtual Meeting Rooms and Virtual Auditoriums so that they are "hosted". Hosted Virtual Meeting

Rooms and Virtual Auditoriums have two different types of participants: hosts and guests. Hosts and guests both dial the same alias,

but only those participants who enter the Host PIN will have privileges to control the conference; everyone else is a guest and can only view the conference.

Guest privileges

l If any guests enter the conference before a host has arrived, they will be shown a holding screen and hear a message advising

them that they are waiting for the conference host.

l A minute or so after the last host has left, any remaining guests will be automatically disconnected. (During this time, Virtual

Auditorium guests being shown the Hosts only view will be able to see other guests.)

In addition, if the conference is held in a Virtual Auditorium:

l The Pexip Infinity administrator may configure the Virtual Auditorium so that guests can see the hosts only, and not see any

other guests. For more information, see Changing the layout seen by participants.

Host privileges

l If the first participant to join the conference is a host, they will be shown their own self view until another host or guest joins

the conference.



l A minute or so after the last host has left, any remaining guests will be automatically disconnected.

l Hosts can use the Pexip Mobile App or Pexip Web App to disconnect participants from the conference.

l Hosts can use the Pexip Mobile App or Pexip Web App to add participants to the conference.

l Hosts can use the Pexip Mobile App or Pexip Web App to mute and unmute an individual participant.

If the conference is hosted in a Virtual Auditorium:

l The Pexip Infinity administrator may configure the Virtual Auditorium so that hosts can see up to 22 other participants, in a

1+21 screen layout. For more information, see Changing the layout seen by participants.

Host and guest PINs

You can create two types of hosted conference:

l the host must enter a PIN but guests do not, or

l both hosts and guests must enter a PIN.

Participants have 3 attempts to enter a correct PIN. After the third unsuccessful attempt, they will hear a message advising them

that the PIN is invalid, and their call will be disconnected.

All PIN entry attempts, successful and unsuccessful, are logged in the administrator log.

Creating a hosted Virtual Meeting Room or Virtual Auditorium

To create a hosted Virtual Meeting Room or Virtual Auditorium:

1. Go to either:

o Service configuration > Virtual Meeting Rooms

o Service configuration > Virtual Auditoriums.

2. Select the Virtual Meeting Room or Virtual Auditorium.

3. In the Host PIN field, enter the PIN number to be used by the hosts.

4. In the Allow Guests drop-down list, select Yes.

5. If you want to require guests to enter a PIN, in the Guest PIN field, enter the PIN number to be used.

If you leave this field blank, anyone who dials the alias of the Virtual Meeting Room or Virtual Auditorium will be able to access

the conference as a guest. However, the conference will not start until the first host has joined and in the meantime all guests

will continue to be shown the holding screen.

Note that:

l All PINs must use the digits 0-9 only.

l All PINs must be between four and ten digits long.

l Host PINs and Guest PINs must be different.

l Host PINs and Guest PINs must have the same number of digits.

l You cannot configure a Guest PIN unless you have already configured a Host PIN.

How to combine Host PINs and Guest PINs for differing levels of security

The table below shows how to use Host PINs and Guest PINs to achieve various levels of security for your Virtual Meeting Rooms

and Virtual Auditoriums:



Access Roles Host PIN Allow Guests Guest PIN

Anyone - no

PIN required

All participants have the same host privileges. Leave blank Select No Leave blank

All

participants

must enter

the same PIN

All participants have the same host privileges. Enter the

PIN

Select No Leave blank

Hosts must

enter a PIN

but guest do

not

Participants who enter the PIN have host privileges.

The conference will not begin until they have joined,

and will finish a minute or so after the last host leaves.

All other participants have guest privileges and do not need to enter a PIN. They will see a holding screen

until the first host joins.

Enter the

PIN

Select Yes Leave blank

Hosts and

guests must

enter

different PINs

Participants who enter the Host PIN have host

privileges. The conference will not begin until they

have joined, and will finish a minute or so after the last

host leaves.

Participants who enter the Guest PIN have guest

privileges and will see a holding screen until the first host joins.

Enter the

PIN

(must be

different

from the

Guest PIN)

Select Yes Enter the PIN*

(must be different

from the Host PIN)

* If you configure a Guest PIN, you must also configure a Host PIN.



Changing the layout seen by participantsAll Pexip Infinity Virtual Meeting Rooms use the Standard Pexip layout, with a large main video image and up to 7 smaller live

thumbnail images across the bottom of the screen. The same layout is shown to all participants, whether they are hosts or guests.

Pexip Infinity Virtual Auditoriums can be configured to show different views to hosts and guests, with either or both being shown

the 1+21 layout instead of the Standard Pexip layout.

You cannot convert an existing Virtual Meeting Room into a Virtual Auditorium. Instead, you must create a new Virtual

Auditorium and reassign the existing aliases to it. For more information, see Changing from a Virtual Meeting Room to a Virtual

Auditorium and vice versa.

To select which layouts will be shown to hosts and guests, navigate to Service configuration > Virtual Auditoriums and select the Virtual Auditorium you wish to change.

The options available are:

Host view l Large main speaker and up to 7 other participants (1+7 layout)

This option uses the Standard Pexip layout to show host and guest participants. The current speaker (or previous speaker, for

those currently speaking) is shown in the main video and up to 7 other participants are shown in the live thumbnails at the

bottom of the screen. Hosts are shown in the leftmost thumbnails (order of who spoke most recently, from left to right) and any

remaining thumbnails are used to show guests (again shown in order of who spoke most recently, from left to right).

l Small main speaker and up to 21 other participants (1+21 layout)

This option also shows both host and guest participants. It is the same as the previous option, except the main speaker is shown

slightly smaller in order to accommodate up to 21 other participants in 3 rows of live thumbnails at the bottom of the screen.

Again, all host participants are shown first (starting from the top left thumbnail) and any remaining thumbnails are used to show

guests.

Guest view l Hosts only (1+7 layout)

With this option, guest see the host participants only; they do not see any of the other guests, even if a guest is speaking*. If

there is just one host participant, the host's image is shown in full screen; if there is more than one host participant, the

Standard Pexip layout is used, with the currently speaking host shown in the main video and all other host participants shown in

the thumbnails. Thumbnails are shown in order of who spoke most recently, from left to right.

* If all hosts have left the conference, guests will be able to see other guests until the conference is automatically disconnected

(after about a minute), or until a host rejoins.

l Hosts and guests (1+21 layout )

With this option, guests see both host and guest participants, but guests are never shown in the main video - even if they are

the current speaker. The main video shows the currently speaking host, and is slightly smaller in order to accommodate the

other hosts and guest participants - up to 21, in 3 rows of live thumbnails at the bottom of the screen. Host participants are

shown first, starting from the top left thumbnail (in order of who spoke most recently) and any remaining thumbnails are used

to show guests (again in order of who spoke most recently).



Changing from a Virtual Meeting Room to a Virtual Auditorium and vice versaWhile it is not possible to change an existing Virtual Meeting Room to a Virtual Auditorium (and vice versa), you can change the

service to which an alias is routed. For example, if your sales team already have a Virtual Meeting Room with an alias

[email protected] and you want these conferences to take advantage of the new features available to a Virtual Auditorium

instead, then:

1. Set up a new Virtual Auditorium (Service configuration > Virtual Auditoriums > Add Virtual Auditorium) with the appropriate

configuration, but do not configure any aliases.

2. Save the new Virtual Auditorium.

3. Go to the Aliases page (Service configuration > Aliases) and select the alias of the existing Virtual Meeting Room.

4. From the Service name drop-down list, select the name of the new Virtual Auditorium.

5. Repeat for all aliases belonging to the existing Virtual Meeting Room.

All calls made to any of the aliases that previously belonged to the Virtual Meeting Room will now be routed to the Virtual

Auditorium. The Virtual Meeting Room will still exist, but will not have any aliases, so no calls can be made to it.



Customizing video and voice prompts using themesThe Themes feature allow you to change the voice prompts and/or images provided to participants when they are accessing a

Virtual Meeting Room, Virtual Auditorium or Virtual Reception. You might change the theme if, for example, you want to use your

company's own logo or color scheme, or you want to change the language used in the voice prompts.

Each conference theme is made up of a specific set of sound and image files. You can replace any or all of these files with your

own sounds and images in order to create a new theme. Alternatively you can automatically generate the images used for the PIN

entry screens based on a background image and color of your choosing.

File requirements

The full set of files that comprise a theme is given in the section Contents of the default theme .ZIP file. All files must meet the

requirements specified below.

Images

All images must be:

l .JPG format (RGB mode only)

l 1920x1080 pixels

Points to note:

l Ensure that the images display acceptably on both 16:9 endpoints and 4:3 endpoints (if applicable). For example, check that any

details on the far left or far right of the image are visible in both formats (for this reason we recommend keeping the image

fairly central).

Sounds

All sounds must be:

l .WAV format

l RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 48000 Hz

Points to note:

l mono and 48000Hz are essential - audio files that do not meet these requirements will fail to upload.

l The volume level of the audio recording is important - use the default Pexip Infinity prompts as a guide.

l Some endpoints may take a few seconds after a call connects before they are able to receive audio. For this reason, we have

included a 2-second pause at the start of any audio files that may be played when a user first connects to Pexip Infinity. We

recommend that you include a similar pause; use the default Pexip Infinity files as a guide.

Downloading an existing themeYou can download all the files that make up an existing theme. You may wish to do this in order to view or edit the content of the

files.

To download all the files that make up an existing theme:

1. Navigate to Service configuration > Themes.

2. Either:

o to download a copy of the default set of files that are shipped with Pexip Infinity, select Download default theme

o to download a copy of the files that make up a custom theme, select the theme and then select Download theme.



A file with a .ZIP extension will be downloaded. You can now view these files, or replace one or more of them to create a new

theme.

Creating a new themeYou can create a new theme, or edit an existing theme, by uploading a .ZIP file containing the files you want to replace.

The .ZIP file does not need to contain the complete set of files;

l if you are creating a new theme, files from the default theme will be used in place of any missing files

l if you are editing an existing theme, files from that theme will be used in place of any missing files.

To create or edit a theme:

1. Ensure that all new sound and image files meet the specified File requirements.

2. Save all new sound and image files in a new folder. Each new file must be saved with the same file name and extension as the

file being replaced.

3. Create a .ZIP file of the new folder.

4. Navigate to Service configuration > Themes and either:

o to add a new theme, select Add new theme.

o to edit an existing theme, select the theme you wish to edit.

5. In the Name field, enter the name of the new theme (or leave as is if you are editing an existing theme).

6. In the Theme field, select Chose file and navigate to the .ZIP file you have just created.

7. In the Service field, select the Virtual Meeting Rooms, Virtual Auditoriums and Virtual Receptions that will use this new theme.

8. Select Save.

9. Allow a minute or so for the new theme to be replicated out to all Conferencing Nodes.

You can now test the theme by dialing in to one of the services ( Virtual Meeting Room, Virtual Auditorium or Virtual Reception) to

which it has been applied.

Automatically generating the PIN entry screens

To save you from having to create 13 separate images for each of the PIN entry screens (i.e. all Image files with a file name

beginning with pin_entry_), Pexip Infinity's themes feature allows you to select a background image and foreground color, and then

automatically generates the required images for you.

You could use this option if you want to use the new images as part of an entirely new theme, or if you want to edit the PIN entry

screens only.

The background image must be:

l .JPG format

l 1920x1080 pixels.

The PIN entry indicators will:

l begin 634 pixels from the top of the background image

l be 70 pixels in diameter

l have 14 pixels of space between each indicator.

You must ensure that the PIN entry indicators use a color that makes them clearly visible when overlaid on the background image.



To change the PIN entry screen images:

1. Navigate to Service configuration > Themes.

2. Select Generate theme.

3. In the Background image field, select Choose file and select the image you want to appear behind the PIN entry indicators.

4. In the Foreground color field, enter the hexadecimal value of the color you want to use for the PIN entry indicators.

5. Select Generate.

6. A <image name>.ZIP file will be downloaded. This file will contain the 13 new PIN entry images.

7. If you want to add any other new files to this theme:

a. unzip the downloaded .ZIP file to a new folder

b. add the new files to the new folder

c. create a .ZIP file of the new folder.

8. Navigate back to Service configuration > Themes and select Add Theme.

9. In the Name field, enter the name you want to give to this new theme.

10. In the Theme field, select Chose file and navigate to the .ZIP file you have just created.

11. In the Virtual Meeting Rooms field, select the VMR(s) that will use this new theme.

12. Select Save.

13. Allow a minute or so for the new theme to be replicated out to all Conferencing Nodes.

You can now test the theme by dialing in to one of the VMRs to which it has been applied.



Contents of the default theme .ZIP file

Audio files

File name Content

2sd-invalid-number-three-times-disconnect_

48kHz_mono.wav

"You have entered an invalid number three times. I will now disconnect the call."

2sd-not-entered-valid-number-disconnect-

call_48kHz_mono.wav

"You have not entered a valid number. I will now disconnect the call."

2sd-number-not-valid-try-again_48kHz_

mono.wav

"That number is not valid. Please try again."

2sd-number-pound-key_48kHz_mono.wav "Please enter the number you wish to connect to, followed by the pound key."

2sd-please-hold-connect-you_48kHz_

mono.wav

"Please hold while I try to connect you."

conf-call-will-be-disconnected_48kHz_

mono.wav

"Your call will be disconnected."

conf-capacity_exceeded_48kHz_mono.wav "The conferencing system capacity has been exceeded."

conf-getpin_48kHz_mono.wav "Please enter the conference PIN number."

conf-insufficient_licenses_48kHz_mono.wav "There are insufficient conferencing system licenses available."

conf-invalid_license_48kHz_mono.wav "The conferencing system license is invalid."

conf-invalidpin_48kHz_mono.wav "The PIN is invalid for this conference."

conf-leaderhasleft_48kHz_mono.wav "The host has left the conference."

conf-placeintoconf_48kHz_mono.wav "Welcome to the conference."

conf-waitforleader_48kHz_mono.wav "Waiting for the conference host to join."

conf-waithostpin_48kHz_mono.wav "Waiting for the conference host to join. If you are the conference host, please

enter the conference PIN number now."



Image files

File name Content

pin_entry_0_digits_image.jpg*











pin_entry_correct_image.jpg*

pin_entry_incorrect_image.jpg*



File name Content

capacity_exceeded_image.jpg

insufficient_license_image.jpg

invalid_license_image.jpg

transfer.jpg

two_stage_dialing.jpg

two_stage_dialing_conf_number_invalid_image.jpg

waiting_for_conference_leader_image.jpg

* These files can be automatically generated using a background image and foreground color of your choice.



Automatically dialing out to a participant from a conferenceThe Pexip Infinity allows you to configure a Virtual Meeting Room or Virtual Auditorium so that one or more participants are

automatically dialed out to whenever a conference using that service starts.

You can also manually dial out to participants from a Virtual Meeting Room or Virtual Auditorium, on an ad-hoc basis. For more

information, see Manually dialing out to a participant from a conference.

The Pexip API can also be used by third party applications to dial out to a participant. For more information, see the Pexip

Infinity Management API documentation.

When a participant has been added to a Virtual Meeting Room or Virtual Auditorium as an automatically dialed participant, a call is

placed to the participant's endpoint from the Virtual Meeting Room or Virtual Auditorium as follows:

Meeting type Participant automatically dialed...

No PIN when the first participant joins the conference

Guests not allowed; participants must enter a PIN when the first participant has entered a valid PIN

Guests allowed; Hosts must enter a PIN but Guests do not when the first participant joins the conference

Guests allowed; Hosts and Guests must enter a PIN when the first participant has entered a valid PIN

If and when the call is answered, the participant will join the conference as either a host or guest, depending on which role you

selected when adding them as an automatically dialed participant. They will not be required to enter a PIN even if one is required

for that role.

In most cases, the call to the automatically dialed participant will be placed from the same Conferencing Node being used by the

participant who initiated the conference.

When the endpoint is called, the automatically dialed participant will see the call as coming from one of the Virtual Meeting Room

or Virtual Auditorium's aliases. This means that if the participant misses the call, they can easily return it by dialing the alias that

appears on their endpoint.

At the end of the conference, if all other participants have disconnected and only one automatically dialed participant remains, the

conference will be terminated by the Pexip Infinity. This is to prevent automated systems (such as recording devices) that are

unable to terminate a call themselves from keeping the conference alive indefinitely. However, if two or more participants remain

in the conference and they are all automatically dialed participants, the conference will not be terminated by the Pexip Infinity. An

exception to this rule is in a conference with guests - all guest participants (whether ADPs or not) will be disconnected one minute

after the last host disconnects.

For this reason, we recommend that each Virtual Meeting Room or Virtual Auditorium has no more than one such automated

system as an automatically dialed participant.

To configure a Virtual Meeting Room or Virtual Auditorium to automatically dial out to a participant when a conference starts:

1. Navigate toService configuration > Automatically dialed participants.

2. Select Add Automatically Dialed Participant.

You will be taken to the Add Automatically Dialed Participant page.




3. Complete the following fields:

Field Description

Participant

alias

The alias of the participant that is to be dialed when a conference starts. If you select a Protocol of SIP, this

must be a valid SIP alias.

Description An optional description of the automatically dialed participant.

Protocol The signaling protocol to use when dialing the participant.

Role The level of privileges the participant will have in the conference. For more information, see About PINs, hosts

and guests.

Service Select the names of the Virtual Meeting Rooms and Virtual Auditoriums from which this participant will be

dialed automatically whenever a conference using that service starts.

4. Select Save.



Manually dialing out to a participant from a conferenceThe Pexip Infinity allows you to manually dial out to participants from a conference, on an ad-hoc basis. When you dial out to a

participant in this way, a call is placed to their endpoint from the Virtual Meeting Room or Virtual Auditorium. If and when they

answer the call, they will join the conference as either a host or guest, depending on the option that you selected.

There are three ways you can manually add a participant to a conference: Using the Administrator interface, Using the Pexip Web

App, and Using the Pexip Mobile App. Each of these options are described below.

You can also configure a Virtual Meeting Room or Virtual Auditorium so that one or more participants are dialed out to

automatically whenever a conference starts. For more information, see Automatically dialing out to a participant from a

conference.

The Pexip API can also be implemented by third party applications to dial a participant into a conference. For more information,

see the Pexip Infinity Management API.

Using the Administrator interfaceYou can use the Pexip Infinity Administrator web interface to dial out to a participant from a Virtual Meeting Room or Virtual

Auditorium. If and when the call is answered, that endpoint will join the conference.

To dial out to a participant using the Pexip Administrator interface:

1. Select the Virtual Meeting Room or Virtual Auditorium to dial the participant from. You can do this in any of the following ways:

o Navigate to Service configuration > Virtual Meeting Rooms and select the name of the Virtual Meeting Room.

o Navigate to Service configuration > Virtual Auditoriums and select the name of the Virtual Auditorium.

o If the conference that you wish to dial out from is already in progress, navigate to Status > Conferences and select the name of the Virtual Meeting Room or Virtual Auditorium being used.

2. At the bottom left of the screen, select Dial out to participant.

3. Complete the following fields:

Field Description

System

location

Select the system location from which the call will be placed. If there is more than one Conferencing Node in

that location, the Pexip Infinity will chose the most appropriate.

The system location will determine the H.323 gatekeeper or SIP proxy to be used to route the call.

Conference

alias

This lists all the aliases that have been configured for the selected Virtual Meeting Room or Virtual Auditorium.

The participant will see the incoming call as coming from the selected alias.

Destination

alias

The alias of the endpoint that you want to dial.

Protocol Select either SIP, H.323, or if the endpoint is a Lync client, select MS-SIP.

Role Select whether you want the participant to join the conference as a host or guest.

4. Select Dial out to participant.

A message Initiated dial out to participant will appear at the top of the screen.

To confirm whether the participant has joined the conference:




1. Navigate to Status > Conferences.

2. Select the name of the Virtual Meeting Room or Virtual Auditorium.

3. Select the Participants tab.

The participant will appear in the list.

Using the Pexip Web AppIf you have Host privileges, you can use the Pexip Web App to dial out to participants from the Virtual Meeting Room or Virtual

Auditorium you are in. When you use this feature, a call is placed to the participant and if and when they answer the call, they will

join the conference as a guest participant (or as a normal participant, if the conference has no PIN). Participants joining the

conference in this way will not go through the IVR screen and will not have to enter a PIN.

To dial out to a participant using the Pexip Web App:

1. From within a Virtual Meeting Room or Virtual Auditorium, select the icon at the top left of the screen.

2. Select Add a new participant.

3. At the prompt, enter the address of the person you want to dial and select OK.

A call will be placed from the Virtual Meeting Room or Virtual Auditorium to the participant. If and when the participant answers

the call they will join the conference and appear on the roster list.

Using the Pexip Mobile AppIn order to use this feature:

l You must have host privileges.

l In some cases, your administrator must have enabled this functionality. See About H.323 gatekeepers and SIP proxies for more

information.

l You must have agreed to allow the Pexip Mobile App to access your contacts.

You can use the Pexip Mobile App to dial out to participants from the Virtual Meeting Room or Virtual Auditorium you are in. When

you use this feature, a call is placed to the participant and if and when they answer the call, they will join the conference as a guest

participant (or as a normal participant, if the conference has no PIN). Participants joining the conference in this way will not go

through the IVR screen and will not have to enter a PIN.

To dial out to a participant using the Pexip Mobile App:

1. From within a Virtual Meeting Room or Virtual Auditorium, select the icon on the left of the Participants section.

The following screen will appear:

.



2. Select from the available options:

o to call some already in your Contacts, select Contacts

o to call someone you have recently called from the Pexip App, select Recents

o to call anyone else, select Enter Manually and enter the number or URI to dial.

3. On the confirmation screen, select Dial.





Restricting call bandwidthThe Pexip Infinity allows you to restrict the amount of bandwidth being used by individual participants dialed in to a Virtual Meeting

Room, Virtual Auditorium or Virtual Reception. Bandwidth restrictions are configured on each individual Virtual Meeting Room,

Virtual Auditorium and Virtual Reception and apply to all participants dialing in to that service.

If a Virtual Reception has bandwidth limits, these will only apply to participants while they are in the Virtual Reception. When their

call is successfully transferred to their selected Virtual Meeting Room or Virtual Auditorium, any bandwidth restrictions for that

service will then apply.

There are two options: inbound and outbound. You can place restrictions on neither, one or both.

Option Description

Maximum inbound call bandwidth (kbps) Limits the bitrate of media received by the Pexip Infinity from a participant.

Leave blank if you do not want to apply any restrictions.

Maximum outbound call bandwidth (kbps) Limits the bitrate of media sent from the Pexip Infinity to a participant.

Leave blank if you do not want to apply any restrictions.

To restrict the bandwidth of calls to a particular service:

1. Navigate to:

o Service configuration > Virtual Meeting Rooms.

o Service configuration > Virtual Auditoriums, or

o Service configuration > Virtual Receptions.

2. Either select the name of the service you wish to edit, or click Add.

3. In the Advanced options section, select Show.

4. Enter the desired values in the Maximum inbound call bandwidth (kbps) and/or Maximum outbound call bandwidth (kbps) fields.

5. Select Save.



Muting a participant's audioThere are three ways you can mute the audio being sent from a participant: Using the Administrator interface, Using the Pexip

Web App and Using the Pexip Mobile App. When a participant's audio has been muted, the Pexip Infinity will still receive their

audio stream but will not add it to the mix being sent to all other participants.

The Pexip API can also be implemented by third party applications to mute a participant. For more information, see the Pexip

Infinity Management API.

Using the Administrator interfaceTo use the Pexip Infinity Administrator web interface to mute a participant's audio:

1. Select the participant. You can do this in two ways:

o Navigate to Status > Participants and select the participant to mute.

o Navigate to Status > Conferences and select the Virtual Meeting Room or Virtual Auditorium that the participant is in.

From the Participants tab, select the participant to mute.

2. At the bottom right of the screen, select Mute.

Using the Pexip Web AppYou must have host privileges to use this feature.

It is possible to mute a participant's audio using the Pexip Web App. Note that this will not mute the participant's speakers, so they

will still hear all other unmuted participants, but what they say will not be heard.

When the Pexip Web App has been used to mute a participant, the Audio administratively muted? column of the Conference

status page of the Pexip Infinity web interface will show YES.

Participants will not be aware that they have been muted or unmuted.

Participants can mute and unmute themselves using the Pexip Mobile App or Pexip Web App, but only if they have host privileges.

A Pexip Web App user can unmute a participant previously muted by another Pexip Mobile App or Pexip Web App user.

To use the Pexip Web App to mute a participant's audio:

1. From the roster list on the left of the screen, click on the down arrow to the right of the name of the participant you wish to

mute.

2. Select Mute participant.

The word Muted will appear under their name.

3. To unmute the participant, click on the down arrow again and select Unmute participant.

Using the Pexip Mobile AppYou must have host privileges to use this feature.

It is possible to mute a participant's audio using the Pexip Mobile App. Note that this will not mute the participant's speakers, so

they will still hear all other unmuted participants, but what they say will not be heard.

When the Pexip Mobile App has been used to mute a participant, the Audio administratively muted? column of the Conference







A Pexip Mobile App user can unmute a participant previously muted by another Pexip Mobile App or Pexip Web App user.

To mute or unmute a conference participant's audio:

1. Select the participant.

2. To mute the participant, turn Enable audio from participant to OFF.

3. To unmute the participant, turn Enable audio from participant to ON.



Disconnecting a participantThere are three ways you can disconnect a participant from a conference: Using the Administrator interface, Using the Pexip Web

App, and Using the Pexip Mobile App. Each of these options is described below.

The Pexip API can also be implemented by third party applications to disconnect a participant from a conference. For more

information, see the Pexip Infinity Management API.

Using the Administrator interfaceTo use the Pexip Infinity Administrator web interface to disconnect a participant from a conference:

1. Select the participant. You can do this in two ways:

o Navigate to Status > Participants and select the participant to disconnect.

o Navigate to Status > Conferences and select the Virtual Meeting Room or Virtual Auditorium that the participant is in.

From the Participants tab, select the participant to disconnect.

2. At the bottom right of the screen, select Disconnect.

Using the Pexip Web AppYou must be a host participant in the conference to use this feature.

To use the Pexip Web App to disconnect a participant:

1. Click on the down arrow to the right of the participant's name.

2. Select Disconnect participant.

Using the Pexip Mobile AppYou must have host privileges to use this feature.

To remove a participant from the conference:


2. Select .




Bulk importing of Virtual Meeting Rooms and Virtual AuditoriumsIf you want to configure your Pexip Infinity platform with a large number of Virtual Meeting Rooms and Virtual Auditoriums, you can

import the configuration for all Virtual Meeting Rooms or Virtual Auditoriums in one go from a CSV file.

This feature allows you to import basic configuration only. It does not allow you to import configuration for themes,

automatically dialed participants or bandwidth limitations. When importing Virtual Auditoriums, the default Host view and Guest

view will be used.

Preparing the CSV file

Format

You must create two separate CSV files - one for Virtual Meeting Room data and one for Virtual Auditorium data. Both files must use

the following format:

name,description,pin,allow_guests,guest_pin,alias_alias,alias_description

where:



name The name used to refer to this Virtual Meeting Room or Virtual Auditorium.

description An optional description of the Virtual Meeting Room or Virtual Auditorium.

pin This optional field allows you to set a secure access code that must be entered by participants before they can join

the conference.

If a Guest PIN has also been set, then the PIN will apply to the conference host(s) only.




allow_

guests

Determines whether the conference will allow participants with guest privileges.

True: the conference will have two types of participants, hosts and guests. You must also include a pin to be used by

the hosts. You can optionally enter a guest_pin; if you do not enter a guest_pin, guests can join without a PIN, but the meeting will not start until the first host has joined.

False: all participants will have the same host privileges.

If this field is left blank it will default to False.

guest_pin This optional field allows you to set a secure access code that must be entered by guests before they can join the

conference.







alias_alias The string that, when received by the Pexip Infinity, will cause it to route the call to the associated service (Virtual

Meeting Room, Virtual Auditorium or Virtual Reception).



In most cases, the alias received by the Pexip Infinity will be the same as the alias that the conference participant

dialed from their endpoint, but there are some exceptions, described in About aliases.

alias_

description

An optional description of the alias. This is useful if you have more than one alias for a service.

For Virtual Meeting Rooms and Virtual Auditoriums with more than one alias, you must repeat the first 5 fields, and use the

remaining 2 alias-related fields to define each individual alias:

name1,description1,pin1,allow_guests,guest_pin1,alias_alias1,alias_description1name1,description1,pin1,allow_guests,guest_pin1,alias_alias2,alias_description2



Duplicates

If any records in the CSV file have the same name field but different description, pin, allow_guests, or guest_pin fields, only one Virtual Meeting Room (or Virtual Auditorium) with that name will be created. This Virtual Meeting Room (or Virtual Auditorium) will

use the last record that was imported.

If any records in the CSV file have the same name as an existing Virtual Meeting Room (or Virtual Auditorium), the existing

configuration will be overwritten by the imported Virtual Meeting Room (or Virtual Auditorium) configuration.

Restrictions

l The name field cannot be blank.

l All non-blank fields must contain valid data, for example the pin field must only contain digits.

l If non-ASCII characters are used, the file must be encoded as UTF-8 text.

Examples

To import a Virtual Meeting Room called alice with a single alias of meet.alice, and a second Virtual Meeting Room called bob with

aliases meet.bob and meet.bobby, you would create the following CSV file:

alice,,,,,meet.alice,bob,,,,,meet.bob,bob,,,,,meet.bobby,

To import Virtual Meeting Rooms for Alice, Bob and Charlie that each have different host and guest PINs you would created the following CSV file:

alice,,1234,True,6789,meet.alice,bob,,4567,True,9876,meet.bob,charlie,,5432145,True,5556789,meet.charlie,

Importing the CSV fileTo import the data in the CSV file to the Pexip Infinity:

1. On the Pexip Infinity web interface, navigate to either:

o Service configuration > Virtual Meeting Rooms or


1. Select Import.

2. Choose the CSV file to import and select Save.



Exporting Virtual Meeting Room configurationIt is possible to export your Virtual Meeting Room or Virtual Auditorium configuration data to a CSV file. This CSV file will be in the

same format required when Bulk importing of Virtual Meeting Rooms and Virtual Auditoriums.

This feature exports basic configuration only. It will not export configuration for themes, automatically dialed participants,

bandwidth limitations, or (for Virtual Auditoriums) Host view and Guest view selections.

To export Virtual Meeting Room data:

1. On the Pexip Infinity web interface, go to either:

o Service configuration > Virtual Meeting Rooms or


2. Select Export. You will be taken to the Export Virtual Meeting Room configuration page.

3. Select Download.

4. Follow your browser's prompts to save or open the file.

Pexip Infinity Administrator Guide Using the Pexip Distributed Gateway service


Using the Pexip Distributed Gateway serviceThe Pexip Distributed Gateway service allows you to support different call protocols within your deployment. It receives incoming

WebRTC, SIP, Lync (MS-SIP) or H.323 calls and interworks them, placing them as an outbound call using your choice of SIP, Lync (MS-

SIP) or H.323. For example, you can use the Pexip Distributed Gateway to enable users of Pexip Infinity's built-in WebRTC endpoint

to place a point-to-point call to a SIP endpoint, or you can use it to enable Microsoft Lync users in your enterprise to make calls to,

and receive calls from, virtually any other type of endpoint.

The Pexip Distributed Gateway is configured as a series of Gateway Routing Rules which specify which calls should be interworked

and to where.



How it works 1. The Pexip Infinity receives an incoming call via one of its Conferencing Nodes.

2. It checks whether the destination alias belongs to any Pexip Infinity Virtual Meeting Rooms, Virtual Auditoriums or Virtual

Receptions; if so, it will direct the call to that service.

3. If the alias does not belong to any of the above services, Pexip Infinity will then check through the Pexip Distributed Gateway's

Gateway Routing Rules to see if the alias matches any rules specified there. If so, it will instruct the Conferencing Node that

received the incoming call to place an outgoing call to the destination alias using the selected protocol.



Adding Gateway Routing RulesTo add, edit or delete a Gateway Routing Rule:

1. Navigate to Service configuration > Distributed Gateway.

2. Either:

o to add a new rule, select Add Gateway Routing Rule, or

o to edit an existing rule, click on the rule.

When specifying a Gateway Routing Rule, the options are:

Option Description

Name The name you will use to refer to this rule.

Description An optional description of the rule.

Match WebRTC

Match SIP

Match Lync (MS-SIP)

Match H.323

Select the protocol(s) of the incoming call to which the rule should apply.

Originating system location Use this optional field if you want the rule to apply only if the call is received via a

Conferencing Node in the specified location.

If you leave this field blank, the rule will be applied to calls from all locations.

Priority Assign a relative priority to this rule, from 1 to 200. Rules are checked in order of

priority, starting with 1 and working down the list until a match is found.

Destination alias regex match A regular expression that specifies the alias that is being dialed.

Pexip Distributed Gateway supports case-insensitive Perl-style regular expression

patterns.

Destination alias regex replace string The regular expression string used to transform the originally dialed alias (if a match

was found).

If you do not want to change the alias, leave this field blank.

Protocol The protocol used to place the outgoing call.

H.323 Gatekeeper* You can optionally specify the H.323 Gatekeeper that will be used to place the

outgoing call.

SIP Proxy* You can optionally specify the SIP Proxy that will be used to place the outgoing call.

Lync server* You can optionally specify the Lync server that will be used to place the outgoing call.

TURN server* You can optionally specify the TURN server that will be used to place the outgoing call

(SIP only).

* If you do not select a specific H.323 Gatekeeper, SIP Proxy or Lync server, the Conferencing Node will attempt to use DNS to

locate an appropriate system via which to route the call.

The H.323 Gatekeeper, SIP Proxy, Lync server or TURN server configured for the Conferencing Node's system location are not automatically used by the Pexip Distributed Gateway; however the Pexip Distributed Gateway can use any of these same systems.



ExampleIn our example organization,every employee has their own video endpoint with an alias in the format

[email protected], and their own Virtual Meeting Room with an alias in the format

[email protected].

In most cases, employees will use their standalone SIP or H.323 endpoints to call others within the organization, but sometimes

they want to use the Pexip Web App (Pexip Infinity's built-in browser-based WebRTC client) to make a point-to-point call.

In order to support this, we set up the following Pexip Distributed Gateway Routing Rule:

Option Input Notes

Name WebRTC to SIP

Description Allow WebRTC users to call

SIP endpoints directly

[ü] Match WebRTC

[ ] Match SIP

[ ] Match Lync (MS-SIP)

[ ] Match H.323

In this example, we only want the rule to apply to calls from

WebRTC clients.

Originating system location <none selected> We want this rule to apply throughout our deployment.

Priority 10

Destination alias Regex match [email protected] This regular expression will match any destination alias with

the domain example.com.

Destination alias regex replace

string

<blank> We have left this blank because we do not want to amend the

alias.

Protocol SIP The call will be interworked to SIP.

H.323 Gatekeeper <not applicable>

SIP Proxy <none specified> We have not selected a SIP proxy, so DNS will be used to

locate an appropriate SIP proxy to place the call.

Lync server <not applicable>

TURN server <none specified>

This rule means that if a WebRTC user dials any alias with the domain @example.com (e.g. [email protected]), the call

will be routed over SIP. We do not need to worry about this rule applying to VMR aliases with the same domain (e.g.

[email protected]) because the Pexip Distributed Gateway's Gateway Routing Rules are only applied after checking

whether there are any VMRs with that alias.

Pexip Infinity Administrator Guide Viewing status


Viewing statusIn this section:

Viewing current conference status 138

Viewing participant status 141

Viewing Conferencing Nodes 147

Viewing historical information about conferences 148

Viewing historical information about participants 150

Viewing Conferencing Node usage statistics 153

About the support log 154

About the administrator log 156



Viewing current conference statusTo see a list of all the conferences currently in progress, navigate to Status > Conferences.

No active conference instances indicates that there are currently no conferences in progress on the Pexip Infinity platform.

Conference instance no longer active indicates that the conference whose details you were viewing has now finished.

To view historical information on conferences after they have finished, see Viewing historical information about conferences.

The pages showing conference status information do not refresh automatically - you must refresh them manually.

Each conference will have the following information available:

Field Description

Service

name

The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Pexip Distributed Gateway being

used. For the Pexip Distributed Gateway, the name will be followed by a unique identifier to distinguish between

separate calls.

Duration For Virtual Meeting Rooms and Virtual Auditoriums: the length of time since the first participant joined the

conference.

For Virtual Receptions: the length of time that this instance of the service has been in continuous use (note that this

could involve more than one participant if their usage overlapped).

For Pexip Distributed Gateway: The length of time since the call was received by the Pexip Distributed Gateway.

Participant

count

The number of participants currently in the conference or using the service.

To view more information about the conference, click on the Virtual Meeting Room name. You will then see 3 tabs for the selected

conference: Participants, Backplanes and Graph.

Participants

The Participants section lists all the participants that are currently in the conference.

For more details about a particular participant, including media stream statistics, click on the Participant alias. This will take you to

the Participant details page.



Field Description

Participant alias The URI of the endpoint used to join the conference or access the service.

Duration The length of time since this participant joined the conference or accessed the service.

Display name The name that has been configured on the participant's endpoint.

System location The system location of the Conferencing Node to which the endpoint is connected.

Signaling node The IP address of the Conferencing Node to which the endpoint is connected. This Conferencing Node

will be handling the call signaling but may or may not be handling the media (for more information, see

Handling of media and signaling in locally distributed conferences).

Media node The IP address of the Conferencing Node that is handling the call media for this endpoint (for more

information, see Handling of media and signaling in locally distributed conferences).

Role Host indicates that either:

l the conference has no PINs configured (in which case all participants will have a role of Host)

l the participant accessed the conference using the PIN.

Guest indicates that the participant accessed the conference using the Guest PIN.

Unknown indicates that the participant is at the PIN entry screen and has not yet successfully entered a PIN.


Is presenting Indicates whether the endpoint is currently sending a presentation stream.

Is muted Indicates whether the endpoint's audio has been muted using the Pexip Mobile App or by a third party

using the Pexip API.

Backplanes

The Backplanes section provides information about the media streams being transmitted between Conferencing Nodes for the

selected conference. Backplane links are unidirectional, so for a conference involving two Conferencing Nodes there will be two

backplane links: one from node A to node B, and another from node B to node A.

Field Description

Media node The IP address of the Conferencing Node that is transmitting media.

For details about the media streams being sent over a particular backplane link, click on the Media

node's IP address.

Remote media node The IP address of the Conferencing Node that is receiving media.

System location The system location of the Conferencing Node that is transmitting media.

Duration The length of time since the connection was established.

Type Geographic indicates that the two Conferencing Nodes are in different system locations.

Local indicates that the two Conferencing Nodes are in the same system location.



Backplane media streams

Field Description

Type Indicates whether the information is for an Audio, Video, or Presentation stream.

Tx codec The format used by the transmitting Conferencing Node to encode and decode the media stream being

transmitted.

Tx bitrate (kbps) The quantity of data currently being sent from the transmitting Conferencing Node to the recipient

Conferencing Node for this particular media stream.

Tx resolution The display resolution of the image being sent from the transmitting Conferencing Node.

Tx packets sent The total quantity of packets sent from the transmitting Conferencing Node to the recipient Conferencing

Node since the start of the conference.

Tx packets lost The total quantity of packets sent from the transmitting Conferencing Node but not received by the

recipient Conferencing Node.

Tx jitter (ms) The variation in the expected periodic arrival of packets being sent from the transmitting Conferencing Node

to the recipient Conferencing Node, in milliseconds.

GraphThis section displays a graphical view of the media connections for this conference, showing all endpoints, the Conferencing Nodes

to which they are connected, and the backplane links between Conferencing Nodes.

To view details of a particular participant, double-click on the participant node.



Viewing participant statusTo see a list of all the current conference participants across all services (Virtual Meeting Rooms, Virtual Auditoriums, Virtual

Receptions and the Pexip Distributed Gateway), navigate to Status > Participants. This shows a list of all participants; to view a

particular participant's details, click on the Participant alias.

To view historical information on participants after a conference has finished, see Viewing historical information about

participants.

Participant detailsThe following information about each participant is available:



Field Description

Participant

alias

The URI of the endpoint that is participating in the conference.

Service

name

The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Pexip Distributed Gateway that

the participant is accessing. For the Pexip Distributed Gateway, the name will be followed by a unique identifier to

distinguish between separate calls.

Duration The length of time since this participant joined the conference or accessed the service.

Display

name

The name that has been configured on the participant's endpoint.

Source alias For participants that have dialed in to the conference themselves, this is the alias of the endpoint being used.

For participants that have been dialed out to manually or automatically, this is the alias of the Virtual Meeting

Room or Virtual Auditorium from which they were dialed.

Destination

alias

For participants that have dialed in to the conference or service themselves, this is the alias that they dialed.

For participants that have been dialed out to manually or automatically from a Virtual Meeting Room or Virtual

Auditorium, this is the alias of the endpoint that was dialed.

System

location

The system location of the Conferencing Node to which the participant is connected.

Signaling

node

The IP address of the Conferencing Node to which the endpoint is connected. This Conferencing Node will be

handling the call signaling but may or may not be handling the media (for more information, see Handling of

media and signaling in locally distributed conferences).

Media node The IP address of the Conferencing Node that is handling the call media for this endpoint (for more information,

see Handling of media and signaling in locally distributed conferences).

Service type Virtual Meeting Room, Virtual Auditorium, Virtual Reception, or Gateway: the participant has successfully accessed the service indicated.

PIN collection IVR: the participant is currently accessing the Interactive Voice Response screens (where they are asked to enter a valid PIN).

Waiting for Host: the participant is being shown a holding screen while they wait for a conference host to join.

Insufficient Capacity Screen: the participant is being shown a holding screen indicating that they cannot join the conference due to a lack of capacity on the Pexip Infinity.

Insufficient Licenses Screen: the participant is being shown a holding screen indicating that they cannot join the

conference due to a lack of available licenses on the Pexip Infinity. For more information, see Insufficient versus

invalid licenses.

Invalid License Screen: the participant is being shown a holding screen indicating that they cannot join the conference because there are no valid licenses available on the Pexip Infinity. For more information, see

Insufficient versus invalid licenses.




l the conference has no PINs configured (in which case all participants will have a role of Host)



Unknown indicates that the participant is at the PIN entry screen and has not yet successfully entered a PIN.


Is

presentation

stream

supported

Indicates whether the endpoint is able to support a separate media stream for presentations negotiated by H.239

or BFCP.

Is presenting Indicates whether the endpoint is currently sending a presentation stream.

Is muted Indicates whether the endpoint's audio has been muted using the Pexip Mobile App or by a third party using the

Pexip API.

Protocol The communication protocol being used by the endpoint.

Bandwidth

(kbps)

The maximum bandwidth, in kbps, that can be used between the Conferencing Node and the endpoint. This is the

total of the maximum signaled bandwidth of the of all the media streams (video, audio and presentation).

Encryption Indicates whether the media stream being sent to and from the Conferencing Node towards the endpoint is

encrypted.

Vendor Information about the endpoint's manufacturer and software.

Remote

address

The IP address of the system from which signaling from this endpoint is being sent and received. This may be the

endpoint itself, or it may be a call control system if one is in use in your network.

Remote port The port on the system from which signaling from this endpoint is being sent and received.

Call ID A unique identifier that can be used to trace the call in the administrator log and support log.

Calls made via the Virtual Reception generate two separate participant calls but these both have the same Call

ID.

Use of the Pexip Distributed Gateway generates two separate participant calls with 2 separate Call IDs.



Media streams



Type Indicates whether the information is for the Audio, Video, or Presentation stream.

Tx codec The format used by the Conferencing Node to encode the media stream being sent to the endpoint.

Off indicates that no decodable media for this stream has been received in the last 10 seconds or so from the codec.

For example, for a Pexip Web App being used for presentation only, there will be no video transmitted.

Off stage indicates that the participant is currently not being shown in the main video or thumbnails, so the Pexip

Infinity is not attempting to decode the media stream.

If this field is blank, this may mean that the Pexip Infinity has negotiated what codec it is going to use but it is yet to

receive any media from the endpoint to determine what codec it is actually sending.

Tx bitrate

(kbps)

The quantity of data currently being sent from the Conferencing Node to the endpoint, in kilobits per second.

Tx

resolution

The display resolution of the image being sent from the Conferencing Node to the endpoint.

Tx packets

sent

The total quantity of packets sent from the Conferencing Node to the endpoint since the start of the conference.

Tx packets

lost

The total quantity of packets sent from the Conferencing Node but not received by the endpoint.

This value is reported to the Conferencing Node by the endpoint. Endpoints that do not support RTCP are not able to

supply this information, so the value will always be 0.

Tx jitter

(ms)

The variation in the expected periodic arrival of packets being sent from the Conferencing Node to the endpoint, in

milliseconds.

This value is reported to the Conferencing Node by the endpoint. Endpoints that do not support RTCP are not able to

supply this information, so the value will always be 0.

Rx codec The format used by the Conferencing Node decode the media stream being sent from the endpoint.

Off indicates that no decodable media for this stream has been received in the last 10 seconds or so from the codec.

For example, for a Pexip Web App being used for presentation only, there will be no video transmitted.

Off stage indicates that the participant is currently not being shown in the main video or thumbnails, so the Pexip

Infinity is not attempting to decode the media stream.

If this field is blank, this may mean that the Pexip Infinity has negotiated what codec it is going to use but it is yet to

receive any media from the endpoint to determine what codec it is actually sending.

Rx bitrate

(kbps)

The quantity of data currently being received by the Conferencing Node from the endpoint, in kilobits per second.

Rx

resolution

The display resolution of the image being received from the Conferencing Node by the endpoint.

Rx

packets

received

The total quantity of packets received by the Conferencing Node from the endpoint since the start of the conference.



Rx

packets

lost

The total quantity of packets sent from the endpoint but not received by the Conferencing Node.

Rx jitter

(ms)

The variation in the expected periodic arrival of packets being received by the Conferencing Node from the endpoint,

in milliseconds.



Viewing Conferencing NodesTo see a list of all Conferencing Nodes currently configured on this Pexip Infinity, navigate to Status > Conferencing Nodes.

Each Conferencing Node has the following information available:

Field Description

Name The name of the Conferencing Node.

Click on the name to view detailed status information.

Address The IP address of the Conferencing Node.

System location The physical location of the Conferencing Node.

Deployment status Deployment succeeded indicates that the Conferencing Node has been automatically deployed.

Deployment failed indicates that an automatic deployment has not been successful.

Manual indicates that the Manual option was selected when the Conferencing Node was deployed (for

more information see Deployment types. Even if the manual deployment was successful, this field will

still say Manual; however you can see from the Last contacted and Last updated fields whether the Conferencing Node is now up and running and receiving configuration updates.

Other statuses indicate that an automatic deployment is currently in progress.

Version The version number of the Pexip Infinity software that is currently installed on this Conferencing Node.

Last contacted (UTC) The date and time that the Conferencing Node last contacted the Management Node. In general,

Conferencing Nodes should contact the Management Node every minute or so.

Timestamps always use UTC.

Last updated (UTC) The last time that the Conferencing Node's configuration was updated.

Timestamps always use UTC.

Maximum audio calls An estimate of the total number of simultaneous audio-only calls this Conferencing Node can handle

the media for (assuming it is not being used for any other types of call at that time.)

Maximum standard

definition video calls

An estimate of the total number of simultaneous standard-definition (SD) video calls this Conferencing

Node can handle the media for (assuming it is not being used for any other types of call at that time.)

Maximum high

definition video calls

An estimate of the total number of simultaneous high-definition (HD) video calls this Conferencing Node

can handle the media for (assuming it is not being used for any other types of call at that time.)

Media load An estimate of how much of its total capacity the Conferencing Node is currently using.



Viewing historical information about conferencesTo see a list of all the completed conferences on the Pexip Infinity platform, navigate to Status > Conference history. This shows a list of the most recent completed conferences (up to a limit of 5,000). To view details of a particular conference, click on the

Service name.

To view information on conferences currently running on Pexip Infinity, see Viewing current conference status.

The following information is available for each completed conference:



Field Description

Service name The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Pexip

Distributed Gateway that was used. For the Pexip Distributed Gateway, the name will be

followed by a unique identifier to distinguish between separate calls.

Click on the service name to view more information.

Start time (UTC) The date and time that the first participant connected to the service.

End time (UTC) The date and time that the last participant's call ended.

Duration The length of time that the conference or service was in use.

Participant count The total number of participant calls made to this conference. Note that if a single participant

disconnects from the conference and then reconnects to it, this will be counted as two

participant calls.

Participants

Participant alias The name that was configured on the participant's endpoint.

Click on the Participant alias to view information about the participant. This will take you to the

Participant history page.

Start time The date and time that the participant's call reached Pexip Infinity.

End time The date and time that the participant's call ended.

Duration The length of time that the participant was connected to Pexip Infinity. This includes time

connected to the Virtual Meeting Room or Virtual Auditorium, but also includes any time spent

at the Virtual Reception or PIN entry screens.

Display name The name that was configured on the participant's endpoint.

System location The system location of the Conferencing Node to which the participant was connected.


l the conference had no PINs configured (in which case all participants had a role of Host)



Unknown indicates one of the following:

l the participant reached the Virtual Reception but did not proceed to a Virtual Meeting

Room or Virtual Auditorium

l the participant reached the PIN entry screen but did not successfully enter a PIN

l the call was to the Pexip Distributed Gateway.




Viewing historical information about participantsTo see a list of all the calls made to the Pexip Infinity platform (including calls to Virtual Meeting Rooms, Virtual Auditoriums, Virtual

Reception and the Pexip Distributed Gateway), navigate to Status > Participant history. This shows a list of all calls made to the

5,000 most recent completed conferences. To view details of a particular call, click on the Participant alias.

To view information on participants currently connected to the Pexip Infinity, see Viewing participant status.

The following information is available:



Field Description

Participant alias The URI of the endpoint that placed the call.

Click on the participant alias to view detailed information about the call.

Service name The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Pexip

Distributed Gateway that the participant was connected to. For the Pexip Distributed Gateway,

the name will be followed by a unique identifier to distinguish between separate calls.

Start time (UTC) The date and time that the participant's call reached Pexip Infinity.

End time (UTC) The date and time that the participant's call ended.

Duration The length of time that the participant was connected to Pexip Infinity. This includes time

connected to the Virtual Meeting Room or Virtual Auditorium but also includes any time spent

at the Virtual Reception or PIN entry screens.

Display name The name that was configured on the participant's endpoint.

Conference alias The alias that the participant dialed to access the service.

System location The system location of the Conferencing Node to which the participant was connected.

Remote address The IP address of the system from which signaling from this endpoint was being sent and

received. This may be the endpoint itself, or it may be a call control system if one is in use in

your network.

Remote port The port on the system from which signaling from this endpoint was being sent and received.

Signaling node The IP address of the Conferencing Node to which the endpoint was connected. This

Conferencing Node was handling the call signaling but may or may not have been handling the

media (for more information, see Handling of media and signaling in locally distributed

conferences).

Media node The IP address of the Conferencing Node that was handling the call media for this endpoint (for

more information, see Handling of media and signaling in locally distributed conferences).


l the conference had no PINs configured (in which case all participants had a role of Host)



Unknown indicates one of the following:

l the participant reached the Virtual Reception but did not proceed to a Virtual Meeting

Room

l the participant reached the PIN entry screen but did not successfully enter a PIN

l the call was to the Pexip Distributed Gateway.




Service type Indicates whether the participant was connected to a Virtual Meeting Room, Virtual Auditorium,

Virtual Reception or the Pexip Distributed Gateway.

Protocol The communication protocol used by the endpoint.

Bandwidth (kbps) The maximum bandwidth, in kbps, that was available for use between the Conferencing Node

and the endpoint. This is the total of the maximum signaled bandwidth of the of all the media

streams (video, audio and presentation).

Encryption Indicates whether the media stream being sent to and from the Conferencing Node towards the

endpoint was encrypted.

Vendor Information about the endpoint's manufacturer and software.

Call ID A unique identifier that can be used to trace the call in the administrator log and support log.

Calls made via the Virtual Reception generate two separate participant calls but these both

have the same Call ID.

Use of the Pexip Distributed Gateway generates two separate participant calls with two separate

Call IDs.

Disconnect reason The reason that the call was disconnected. This is provided by either the endpoint or the Pexip

Infinity, depending on how the call was terminated.



Viewing Conferencing Node usage statistics

Viewing graphsTo view the daily usage statistics on:

l the total number of minutes used per Conferencing Node, and

l the highest number of concurrent ports used per Conferencing Node,

navigate to Status > Usage statistics.

These graphs will show statistics for up to the past 100 days, even if you have rebooted or upgraded your system during that time.

Each day represents usage for the 24-hour period from midnight UTC.

If there is no information available, for example if your system has been deployed in the last 24 hours, you will see the following

message:

Information not yet available. This can take up to 1 hour.

Viewing source data

To view the source data used to create each graph, click on the View source data link below the graph. This will take you to a page showing the source data in CSV format.

The source data will go back for the same amount of time as the administrator log, from which they are extracted. For more

information, see About the administrator log.



About the support logThe Management Node collates the logs from itself and all Conferencing Nodes and compiles these into the support log.

You can also use a syslog server to collate logs remotely. For details see Using a syslog server.

The support log records all events occurring across the Pexip Infinity deployment, including:

l configuration changes on the system

l conferences starting and ending

l participants joining and leaving conferences

l participants presenting in conferences

l SIP, H.323 and BFCP signaling

l DNS lookups.

Log timestamps always use UTC.

The information in the support log is retained during reboot and upgrade.

For more information on interpreting the support log, see the Pexip Infinity Management API documentation.

File sizeThe support log has a maximum size of 500 MB, after which it will be overwritten, starting with the oldest entries. However, only

the most recent 10 MB will be available via the Pexip Infinity web interface.

Viewing the support log

To view the support log, navigate to Status > Support log.

The log appears in the format:

syslog_time system originating_time level name details

where:




Field Description

syslog_time In the format:

year-month-dayThour:minute:second.millisecondUTC_offset

The time that the event was logged by syslog on the originating system.

system The IP address or host name of the system that sent the log message.

originating_time In the format:

year-month-day hour:minute:second,millisecond

The time at which the event occurred on the originating system.

level The severity of the event.

The levels, in order of increasing severity, are:

l DEBUG

l INFO

l WARNING

l ERROR

name The system module producing the log output.

details Information about the event, as a series of name=value pairs.



About the administrator logThe administrator log is a subset of the support log. It contains information about events occurring during the normal use of the

system which may be of interest to a system administrator, notably:

l Conferencing Node deployment and communication status

l configuration changes on the system

l conferences starting and ending

l participants joining and leaving conferences

l participants presenting in conferences

Log timestamps always use UTC.

The information in the administrator log is retained during reboot and upgrade.

Log sizeThe administrator log has a maximum size of 0.5 GB, after which it will be overwritten, starting with the oldest entries. However,

only the most recent 10 MB will be available via the Pexip Infinity web interface.

Viewing the administrator log

To view the administrator log, navigate to Status > Administrator log.

The log appears in the format:

syslog_time system originating_time level name details

where:

Field Description

syslog_time In the format:

year-month-dayThour:minute:second.millisecondUTC_offset

The time that the event was logged by syslog on the originating system.

system The IP address or host name of the system that sent the log message.

originating_time In the format:

year-month-day hour:minute:second,millisecond

The time at which the event occurred on the originating system.

level The severity of the event.

The levels, in order of increasing severity, are:

l DEBUG

l INFO

l WARNING

l ERROR

name The system module producing the log output.

details Information about the event, as a series of name=value pairs.

Pexip Infinity Administrator Guide Maintenance


MaintenanceIn this section:

Setting and changing usernames and passwords 158

Upgrading the Pexip Infinity 159

Migrating Conferencing Nodes between host servers 163

Taking a Conferencing Node out of service 164

Backing up and restoring configuration 165

Downloading a diagnostic snapshot 166

Automatically reporting errors 167



Setting and changing usernames and passwordsThere are a number of different components of the Pexip Infinity that require a username and password:

l Pexip Infinity web interface

l Management Node operating system

l Conferencing Node operating system

Information on how to set and change these is given below.

Pexip Infinity web interface

A username and password are required for logging in to the Pexip Infinity web interface. These are the web administration

username and web administration password that were set during installation using the installation wizard.

The username cannot be changed after being set, but the password can.

To change the password used to log in to the Pexip Infinity web interface:

1. Log in to the Pexip Infinity web interface.

2. At the top right of the screen, select Change password.

3. Enter the existing password, and then enter the new password twice.

4. Select Change my password.

You will see a message:

Password change successful

Your password was changed.

Changing the Management Node operating system password

The Management Node virtual machine (VM) runs on a Linux operating system. The username is admin and cannot be changed.

The password for the Management Node operating system was set during installation using the installation wizard.

The password can be changed by logging in to the Management Node operating system over SSH and running the standard UNIX

command passwd.

Conferencing Node operating system password

Conferencing Nodes run on a Linux operating system. The username for each Conferencing Node operating system is admin and cannot be changed.

The password was set during Deploying new Conferencing Nodes when configuring the SSH password field.

The password can be changed by logging in to the Conferencing Node operating system over SSH and running the standard UNIX

command passwd.

Forgotten passwords

If you have forgotten the password for the Pexip Infinity web interface, re-run the installation wizard, being sure to change only

the Web administration password setting.

If you have forgotten the password used to log in to a Conferencing Node or Management Node operating system, contact your

authorized Pexip representative for assistance.



Upgrading the Pexip Infinity

About the automatic upgrade processWhen you initiate an upgrade of the Pexip Infinity software from version 2 or later, the following steps occur automatically, in

order.

1. The Management Node software is upgraded, after which the Management Node will automatically reboot.

2. The first Conferencing Node is put into maintenance mode, meaning all further incoming calls to it will be rejected.

3. When all calls have cleared from the first Conferencing Node, its software is upgraded and the system is rebooted. This process

should take around 2 minutes to complete, but may take longer depending on the speed of the connection between the

Management Node and Conferencing Node over which the files are transferred.

If all calls have not cleared after 1 hour, the first Conferencing Node will be taken out of maintenance mode and put at the

back of the queue of systems to be upgraded. A further attempt to upgrade the first Conferencing Node will be made after all

other systems have been upgraded (or had upgrade attempts made).

4. After the first Conferencing Node has been upgraded successfully (or has been put back in the queue for a later upgrade

attempt) and is again available, the second Conferencing Node is put into maintenance mode.

5. The process continues with each subsequent Conferencing Node being put into maintenance mode, and, after all calls have

cleared, being upgraded and then rebooted.

6. If the upgrade of the Management Node and all Conferencing Nodes has not completed successfully after 24 hours, the process

will stop and all systems will be left in their existing upgrade state. This is designed to prevent situations where one

Conferencing Node cannot be upgraded, which would otherwise leave the system in a permanent state of upgrading.

If the upgrade process does not complete successfully and stops after 24 hours, you may have a mix of upgraded and non-upgraded

systems. You will then need to repeat the upgrade process. During a repeat upgrade, only those systems that have not already been

upgraded will be included in the upgrade process.

During the 24-hour period from when an upgrade has been initiated, you can not re-initiate an upgrade using the web interface. If

you must re-initiate an upgrade during this time, you must reboot the Management Node and then start the process again.

When to upgradeWhile the upgrade is in progress, some Conferencing Nodes will be running the newer version of the software and some will be

running the older version. These Conferencing Nodes will be incompatible until they are all again running the same version. This

means that there may be instances where two endpoints dial the same Virtual Meeting Room alias but if they are routed to

different Conferencing Nodes that are running different versions of the software, the two endpoints will be in different conferences.

For this reason, we recommend upgrading at a time of minimal usage.

Upgrading from version 3 to version 4To upgrade the Pexip Infinity software from v3 to v4:

1. Before starting the upgrade, we recommend that you use your hypervisor's snapshot functionality to take a full snapshot of the

Management Node. You may also wish to take snapshots of each Conferencing Node, although depending on the size and

complexity of your deployment it may be easier to simply redeploy these from the Management Node in the unlikely event

that this is required.

2. From the Pexip Infinity web interface, go to Utilities > Upgrade.

3. Select Choose File and browse to the location of the upgrade file.



4. Select Upgrade. There will be a short delay while the upgrade package is uploaded.

After the upgrade package has been uploaded, you will be presented with a confirmation page showing details of the existing

software version and the upgrade version.

5. To proceed, select Upgrade .

You will be taken to the Upgrade status page, showing the current upgrade status of the Management Node and all

Conferencing Nodes. For a definition of each status, see Definition of upgrade statuses.

This page will automatically refresh every 5 seconds.

When the upgrade has completed, all systems will show a status of No upgrade in progress and have the appropriate Installed

version.

No additional actions are required to upgrade the Management Node or Conferencing Nodes individually.

Error messages during upgrade

The following Error-level messages are expected during an upgrade from v3 to v4 and do not require any action:

2014-03-03T12:12:01.924+00:00 <manager_hostname> 2014-03-03 12:12:01,924 Level="ERROR" Name="administrator.system.configuration" Message="Node configuration failed." Node="<worker_hostname>" Resource="File[/etc/certs/privatekey.pem]"

2014-03-03T12:12:01.924+00:00 <manager_hostname> 2014-03-03 12:12:01,924 Level="ERROR" Name="administrator.system.configuration" Message="Node configuration failed." Node=""<worker_hostname>" Resource="File[/etc/certs/server.pem]"

2014-03-03T12:12:02.400+00:00 <manager_hostname> 2014-03-03 12:12:02,399 Level="ERROR" Name="administrator.system.connectivity" Message="Unable to contact node." Node="<node_ip_fqdn>"

Upgrading from version 2 to version 4To upgrade the Pexip Infinity version 2 software to any other version, you must first upgrade to version 3. To do this:

1. Download the Pexip Infinity v3 upgrade file (contact your authorized Pexip representative for the link to this file).

2. Follow the steps outlined in Upgrading from version 3 to version 4, but when asked to Choose File browse to the location of

the v3 upgrade file.

3. Verify that the upgrade has completed successfully.

4. Download the Pexip Infinity v4 upgrade file.

5. Follow the steps outlined in Upgrading from version 3 to version 4, and when asked to Choose File browse to the location of

the v4 upgrade file.

Upgrading from version 1.0 to version 4To upgrade the Pexip Infinity version 1.0 to any other version, you must delete the existing Conferencing Nodes and Management

Node and then re-install them, as follows:

1. Export Virtual Meeting Room configuration.

2. Make a note of all Management Node configuration (go to Platform configuration > Management Node to view this information).

3. Put all Conferencing Nodes into maintenance mode.



4. After all calls have cleared from each Conferencing Node, from VMware:

a. Power Off the machine.

b. Select Delete from Disk.

5. After all Conferencing Nodes have been deleted, from VMware:

a. Select the Management Node.

b. Power Off the machine.

c. Select Delete from Disk.

6. Deploy the OVA file containing the newer version of the Pexip Infinity software. (For full instructions, see Installing the

Management Node.)

7. Re-activate your existing licenses.

8. Re-deploy each Conferencing Node.

9. Import the Virtual Meeting Room configuration.

Upgrading configuration-only deployments

The automatic upgrade process described above will update the Management Node and all Conferencing Nodes, including

Conferencing Nodes that have been created using the configuration only deployment type.

However, if after the upgrade you wish to deploy new configuration-only Conferencing Nodes, you must download and use a version

of the Conferencing Node VM template that matches the version of the Management Node that you have upgraded to. Creating a

new Conferencing Node from a VM template containing a different version of the Pexip Infinity software than that which is running

on the Management Node is not supported and will not work. For more information, see Deploying a Conferencing Node using a

VM template and configuration file

Definition of upgrade statuses

During an upgrade, the Upgrade status page will report the status of each system as follows:

Status Description

No upgrade in progress This is the default state that occurs before a node is upgraded, or after a node has

rebooted after an upgrade.

Waiting for calls to clear The Conferencing Node is in maintenance mode and is waiting for existing conferences to

complete.

Timeout waiting for calls to clear Not all conferences cleared after 1 hour. This node is removed from maintenance mode

and the upgrade will be attempted again later.

Preparing to upgrade The system is preparing to upgrade.

Upgrade in progress The upgrade is currently in progress.

Rebooting The upgrade has completed and the system is rebooting.

Could not communicate with

conferencing node

This error will be reported if the Conferencing Node cannot be contacted.

Recovering from a failed upgradeTo recover your system after a failed upgrade:



1. Restore the Management Node from the VMware snapshot that you took using your hypervisor at the start of the upgrade

process.

2. Restore the individual Conferencing Nodes by either:

a. redeploying each Conferencing Node manually from the Management Node - see Deploying new Conferencing Nodes

b. restoring the hypervisor snapshot of each Conferencing Node that was taken at the start of the upgrade process.

Checking the installed version

Management Node

To view which software version is running on the Management Node, click on the About link at the top right corner of the Pexip Infinity web interface.

Conferencing Nodes

To view which software version is running on individual Conferencing Nodes, navigate to Status > Conferencing Nodes. The

software version number will be shown in the Installed version column.



Migrating Conferencing Nodes between host serversUsing the tools available in VMware, it is possible to move Conferencing Nodes from one host server to another. You can do this

while a conference is in progress, without interrupting the conference.

Possible reasons for moving a Conferencing Node include:

l if the existing host server is running low on capacity or is experiencing performance issues

l if a conference instance is about to become too large for the existing host server to support it

l if you want to automatically schedule the redistribution of applications among your host servers so that you can provide certain

applications with increased or decreased capacity at certain times, according to business requirements

The Pexip Infinity supports VMware's vMotion for the live migration of Conferencing Nodes.

We do not recommend migrating Conferencing Nodes while a conference is in progress unless absolutely necessary, because

participants will see a few seconds of frozen video. If possible, we recommend waiting until the Conferencing Node is idle. This can

be achieved by putting the Conferencing Node into maintenance mode - see Taking a Conferencing Node out of service.

Prerequisites l The source and target servers must be on a network with a minimum of 1 Gbps capacity.

l The source and target servers must be enabled for vMotion and use the same shared storage.

Manual migration

1. In the VMware inventory view, right-click on the Conferencing Node and select Migrate. The Migrate Virtual Machine window will appear.

2. Select Change host then select Next.

3. Select the destination host server or cluster and then select Next.

4. Select the destination resource pool and then select Next.

5. Select the priority and then select Next.

6. Check the details of the migration, and if they are all correct, select Finish.

Automatic migrationVMware's Distributed Resource Scheduler (DRS) can be used to automatically redistribute virtual machines (VMs) across host servers

in a specified resource pool, according to the changing resource requirements of the individual VMs. You can elect to migrate

Conferencing Nodes at a specific time, or in response to specific resource requirements.

In most cases DRS will not move a busy Conferencing Node and will instead move other VMs off that host server. In cases where DRS

does move a Conferencing Node while a conference is running on it, the participants will see a few seconds of frozen video just as

they are moved to the new host server.

DRS is set up and managed entirely via the VMware interface. Refer to VMware's latest Resource Management documentation for

full instructions.

For more information on DRS, see http://www.vmware.com/products/datacenter-virtualization/vsphere/drs-dpm.html.

http://www.vmware.com/products/datacenter-virtualization/vsphere/drs-dpm.html



Taking a Conferencing Node out of serviceIf you need to take a Conferencing Node out of service, you must first ensure that it is not hosting any conferences.

To do this:

1. Go to Platform configuration > Conferencing Nodes.

2. Select the Conferencing Node.

3. Select Enable maintenance mode.

While maintenance mode is enabled, this Conferencing Node will not accept any new conference instances.

4. Wait until any existing conferences on that Conferencing Node have finished. To check, go to Status > Conferences.

You can now take the Conferencing Node out of service.




Backing up and restoring configurationThe Management Node and all Conferencing Nodes must be running the same Pexip Infinity software version to ensure correct

functionality. For this reason, you should perform regular backups, particularly before Upgrading the Pexip Infinity.

Management Node

To backup and restore your Virtual Meeting Room configuration, see Exporting Virtual Meeting Room configuration and Bulk

importing of Virtual Meeting Rooms and Virtual Auditoriums.

To backup all other Management Node configuration, you can use your hypervisor's own backup tools, or any other third-party tool

that supports VM backups, to create a full snapshot of the Management Node at that point. This can then be re-deployed at a later

date if required.

Conferencing NodesConferencing Nodes do not need to be backed up because they receive all their configuration information from the Management

Node and can simply be redeployed if necessary.

However, if your Conferencing Nodes are geographically spread out and redeploying them would consume significant bandwidth or

take a significant length of time, they can also be backed up with your hypervisor's backup tools.



Downloading a diagnostic snapshotIf you are experiencing issues with your Pexip Infinity service, you may be asked by your Pexip support representative to provide

them with a snapshot of your system to assist them in diagnosis of the issue.

To download the diagnostic snapshot:

1. On the Pexip Infinity web interface, go to Utilities > Diagnostic snapshot.

2. Either:

o to download all available data, select Download full snapshot

o to download up to 24 hours of data, select Download 24-hour snapshot

3. Follow your browser's prompts to save the file.

File contentsThe diagnostic snapshot is a collection of logs and incident reports and contains information such as IP addresses, conference names,

aliases, Pexip Infinity configuration and system logs. Some of this information may be sensitive to your company, so the snapshot

should be saved and handled securely.

File sizeWhen each log reaches its maximum size, the oldest data is overwritten.

The maximum file size of each log in the snapshot is as follows:

l Administrator: 0.5 GB

l Support: 0.5 GB

l Internal developer-specific logs: 2 GB

The diagnostic snapshot will also include all available incident reports:

l the full snapshot will contain up to 28 days of incident reports, with a cap at 5 GB

l the 24-hour snapshot will contain incident reports from the last 24 hours.



Automatically reporting errorsIn order to allow continual monitoring and improvement of the Pexip Infinity platform, we encourage customers to send us details

of any incidents that occur in their products. When this feature is enabled, incident reports are sent automatically to a secure web

server owned and managed by Pexip.

We collate and analyze this information in order to identify issues with the software that can be resolved in future product releases.

The information we receive will not be used for any other purpose.

The feature is enabled and disabled on a Pexip Infinity platform-wide basis, but when enabled each Management Node and

Conferencing Node will send their individual incident reports directly to the incident reporting server.

You must therefore ensure that your IP routing and firewall configuration will allow outbound communications from each of these

systems to the nominated URL. Reports are sent to https://acr.pexip.com over TLS to port 443.

Content of incident reports

The exact content of each incident report will vary depending on the nature of the problem, but all reports will include:

l the date and time that the incident occurred

l the FQDN of the system on which the incident occurred

l the IP address of the system on which the incident occurred

l information about the Pexip Infinity software version

l details of the internal software processes running at the time the incident occurred.

The incident reporting server will also annotate each report with the IP address from which it was received (generally this will be

the public IP address of the sender's network). This information is not contained in the original incident report.

The incident reports may also include:

l system configuration information

l stack traces.

The incident reports will never include:

l system logs.

Enabling and disabling automatic sending of incident reports

Automatic sending of incident reports is enabled or disabled in the first instance when Installing the Management Node.

To enable or disable the automatic submission of incident reports after the installation wizard has been run:

1. On the Pexip Infinity web interface, go to Platform configuration > Management Node.

2. Select the Management Node for the Pexip Infinity you want to enable for incident reporting. You will be taken to the Edit

Management Node page.

3. Select or deselect the Enable incident reporting box as required.

4. Select Save.

Pexip Infinity Administrator Guide Using the Pexip Web App


Using the Pexip Web AppThe Pexip Web App is a web-based video client that can be used directly from a supported browser without any special downloads

or plugins. It is available from all Pexip Infinity deployments and administrators do not need to do anything to enable it.

The Pexip Web App allows users to:

l access any Virtual Meeting Room or Virtual Auditorium within the Pexip Infinity deployment

l share their screen, whether or not they are using it as their main video client

l view a list of other conference participants

l (for Host participants) mute and disconnect other participants

l (for Host participants) add participants to the conference

l in conjunction with the Pexip Distributed Gateway, make a point-to-point call to another endpoint, regardless of protocol.

The Pexip Web App is currently supported in Google Chrome version 27 and later, and Mozilla Firefox version 20 and later.



Obtaining Virtual Meeting Room URLsIf you wish to provide conference participants with a URL that they can click to access a Virtual Meeting Room or Virtual Auditorium,

use one of the following formats:

l To direct users to the Pexip Web App login page, use:

https://<address> or

https://<address>/webapp l To direct users to the Pexip Web App login page and pre-fill the Virtual Meeting Room or Virtual Auditorium alias, use:

https://<address>/#/<alias> or

https://<address>/webapp/#/<alias> l To direct users to the Pexip Web App login page and pre-fill the Virtual Meeting Room or Virtual Auditorium alias and the user's

name, use:

https://<address>/#/<alias>/<name>

https://<address>/webapp/#/<alias>/<name> l To takes users directly into a Virtual Meeting Room or Virtual Auditorium, use:

https://<address>/#/<alias>/<name>/join

https://<address>/webapp/#/<alias>/<name>/join

where:

l <address> is the IP address or domain name of the Conferencing Node or reverse proxy

l <alias> is one of the aliases for the Virtual Meeting Room or Virtual Auditorium the user will join

l <name> is the name of the user who is joining the conference.

For example, if the domain name of your reverse proxy is conference.example.com, and the Virtual Meeting Room alias is

meet.alice, the URL for Bob to join it directly would be conference.example.com/webapp/#/meet.alice/Bob/join.

Note that clicking on this URL will open the link in the user's default browser, which must be Chrome version 27 and later, or

Firefox version 20 and later.



Accessing a Virtual Meeting Room or Virtual AuditoriumTo access a Virtual Meeting Room or Virtual Auditorium using the Pexip Web App:

1. Open a supported browser window (Google Chrome version 27 and later, or Mozilla Firefox version 20 and later).

2. Do one of the following in the address bar:

o Enter the link to the Virtual Meeting Room or Virtual Auditorium that was provided to you by your system administrator or

the conference organizer.

o Enter the IP address or domain name of your nearest Conferencing Node or reverse proxy, followed by /webapp/.

For example, if the domain name of your reverse proxy is rp.example.com, you would enter rp.example.com/webapp/.

You will be presented with the log in screen.

3. In the Person or conference to dial field, enter the alias of the Virtual Meeting Room or Virtual Auditorium you wish to join.

4. Enter Your name. When you join the conference, this name will be shown in the roster list on the left of the screen. (The

roster list shows the names of all participants, and appears in the Pexip Web App and the Pexip Mobile App).

5. Select the Bandwidth you want to use for the call. The default is 576 kbps, but you may want to select a higher or lower value

depending on the speed of your internet connection.

6. Select Join.

7. If the Virtual Meeting Room is PIN-protected, you will be prompted to enter an appropriate host or guest PIN. Enter the PIN

and select Join.

8. If prompted, allow the browser to use your camera and microphone.

o For Chrome users, the first time you connect to a particular Conferencing Node you may see a message under the address

bar saying that it wants to use your camera and microphone. Select Allow.

o For Firefox users, you must click on the icon at the top left of the address bar and select the camera and microphone

to use and then Share Selected Devices.

After a few moments you will be connected to the conference.



During a conferenceWhile the conference is in progress you can perform the following actions:

Select the microphone and camera to use 1. At the far right of the address bar (Chrome) or far left (Firefox), select the

icon.

2. Select the desired microphone and camera from the drop-down menus.

View the video image full screen Select Enable fullscreen.

Change the volume of the audio coming

from the conference

(Available in Chrome only)

1. Right-click the video window and select Show controls.

2. Drag the slider on the right to adjust the volume.

Mute the audio coming from the

conference

Right-click the video window and select Mute.

Stop sending your audio to other

participants

Select Mute my audio.

Send your audio to other participants Select Enable my audio.

Stop sending your video to other

participants

Select Hide my video.

Send your video to other participants Select Enable my video.

Stop showing your video to yourself Select Hide selfview.

View the video of yourself being sent to

other participants

Select Show selfview.

View a presentation being shown by

another participant

When a participant starts a presentation, the following pop-up window will appear:

A participant started sharing content. Would you like to view their presentation?

To view the presentation, select OK.

The presentation will appear in the video window.

You can toggle between viewing the presentation and viewing the participants by

selecting Hide presentation and View presentation respectively.

Share your screen with all other

participants

(Available to Chrome users only - you must first enable screen sharing.)

Select Present screen.

Stop sharing your screen Select Stop screen sharing.

Disconnect from the conference At the top right of the screen, select .



Using the Pexip Web App to share your screenYou can use the Pexip Web App to share what's on your screen with other conference participants. You can do this if you are already

using the web client as your video endpoint for the conference, but even if you are using another video endpoint, you can open and use the Pexip Web App just to share your screen.

This feature is currently supported in Google Chrome only, and before it can be used you must change Chrome's default setting to

enable screen sharing.

Enabling screen sharing in ChromeBy default, Chrome disables the ability to share your screen. You must enable this setting, as follows:

1. In Chrome, open a new tab.

2. In the address bar, enter chrome://flags/#enable-usermedia-screen-capture:

This will take you to a page where you can change experimental settings in Chrome. Ensure you read the warning at the top of

the page before you proceed.

3. Scroll down to Enable screen capture support in getUserMedia(). (this should be highlighted in yellow):

4. Select Enable.

5. From the bottom of the page, select Relaunch Now:

Chrome will close and reopen all tabs.

You are now ready to share your screen.



Sharing your screen when using the Pexip Web App as your video endpoint

1. Use the Pexip Web App to access the Virtual Meeting Room or Virtual Auditorium by following the steps in Accessing a Virtual

Meeting Room or Virtual Auditorium, above.

2. Select Present screen.

A confirmation window will appear.

3. Select Yes to confirm that you want to share your screen.

Sharing your screen when using another video endpointIf you are in a Virtual Meeting Room or Virtual Auditorium using an endpoint other than the Pexip Web App and you want to share

your screen:

1. Open a new browser window in Chrome.

2. Do one of the following in the address bar:

o Enter the link to the Virtual Meeting Room or Virtual Auditorium that was provided to you by your system administrator or

the conference organizer.

o Enter the IP address or domain name of your nearest Conferencing Node or reverse proxy, followed by /webapp/.

For example, if the domain name of your reverse proxy is rp.example.com, you would enter rp.example.com/webapp/.

You will be presented with the log in screen.

3. In the Person or conference to dial field, enter the alias of the Virtual Meeting Room or Virtual Auditorium you wish to join.

4. Enter Your name.

5. Select the Bandwidth to use. The default is 576 kbps.

6. Select Present Screen Only.

7. Select Join.

8. If the Virtual Meeting Room or Virtual Auditorium is PIN-protected, you will be prompted to enter an appropriate host or guest

PIN. Enter the PIN and select Join.

9. A confirmation window will appear.

10. Select Yes to confirm that you want to share your screen.

The main area of the page will display a icon to indicate that the Pexip Web App is sending the screen image (rather than

sending video from your webcam).



Viewing a list of other conference participantsWhen using the Pexip Web App, the left-hand side of the screen will display a list of all other conference participants. You can scroll

through this list, or use the search box at the top of the list, to view other participants. This is particularly useful when there are

more participants than can be shown on the screen at any one time.

Adding a participant to the conferenceIf you have Host privileges, you can use the Pexip Web App to dial out to participants from the Virtual Meeting Room or Virtual

Auditorium you are in. When you use this feature, a call is placed to the participant and if and when they answer the call, they will

join the conference as a guest participant (or as a normal participant, if the conference has no PIN). Participants joining the

conference in this way will not go through the IVR screen and will not have to enter a PIN.

To dial out to a participant using the Pexip Web App:

1. From within a Virtual Meeting Room or Virtual Auditorium, select the icon at the top left of the screen.

2. Select Add a new participant.

3. At the prompt, enter the address of the person you want to dial and select OK.





Muting other participantsIf you have Host privileges, you can mute the audio from any of the other participants. To do this:


2. Select Mute participant.

When the Pexip Web App has been used to mute a participant, the Audio administratively muted? column of the Conference




Disconnecting other participantsIf you have Host privileges, you can disconnect any of the other participants from the conference. To do this:


2. Select Disconnect participant.



Using the Pexip Web App to make a point-to-point callIf you have set up an appropriate Pexip Distributed Gateway, users in your deployment can use the Pexip Web App to make a

point-to-point call to another endpoint. To do this:

1. Open a browser window and enter the address of the Pexip Web App that has been provided to you by your Administrator.

2. In the Person or conference to dial field, enter the address of the person you want to call.

3. Enter Your name.

4. Select Join.

When the call connects, you will see the person you called in the main video. The roster list will be empty because there are no

other participants in this call.

Pexip Infinity Administrator Guide Using the Pexip Mobile App


Using the Pexip Mobile AppIn this section:

About the Pexip Mobile App 179

Setting up DNS records for Pexip Mobile App use 180

Installing the Pexip Mobile App 181




About the Pexip Mobile AppThe Pexip Mobile App is released separately to the Pexip Infinity, and may have been updated since this Administrator Guide

was released. For the most up-to-date Pexip Mobile App user documentation, see www.pexip.com/technical-documentation.

The Pexip Mobile App for iOS and Android provides

conference participants with a consistent interface

from which they can control conferences and view

presentations, all from their own personal device.

From the Pexip Mobile App all conference

participants can:

l View which participants are currently "on stage"

(i.e. whose images are being displayed to other

participants), and their position (main video or

thumbnail).

l View a list of all the participants on the call -

useful when there are more participants than

can be shown in the thumbnails along the

bottom of the screen.

l View the presentation on their personal device.

o Video participants can elect to use their video endpoint just for viewing other participants, essentially providing them

with a dual-screen video system.

o Audio-only participants will be able to view the presentation on their personal device, enhancing their conference experience.

l Decide where they want to view the presentation: on their mobile device, on the video endpoint, or both.

l Zoom in on the presentation on their device, allowing them to see details that would otherwise not be visible from a distance

on the screen.

In addition, host participants can:

l Invite new participants to join the conference.

l Mute and unmute participants.

l Disconnect participants.




Setting up DNS records for Pexip Mobile App useIn order for conference participants to be able to connect to conferences using the Pexip Mobile App, you must provide an SRV

lookup on all domains used in Virtual Meeting Room aliases.

For each domain, the Pexip Mobile App currently supports a single SRV record for _pexapp._tcp.<domain>, which tells the Pexip Mobile App which host to contact. This will typically be a reverse proxy (for deployments where Conferencing Nodes are located

within a private network), but it can also be a public-facing Conferencing Node.

The SRV record for _pexapp._tcp.<domain> should always reference port 443 on the host.

If multiple SRV records are returned by the SRV lookup on _pexapp._tcp.<domain>, the Pexip Mobile App will attempt to contact

the first host in the list, which may or may not be the preferred host. If this attempt fails, no further attempts will be made to

contact other hosts on the list.

If the Pexip Mobile App is unable to locate the host (i.e. reverse proxy or Conferencing Node) through DNS SRV discovery because

either:

l the SRV lookup on _pexapp._tcp.<domain> does not return any records, or

l the Pexip App cannot contact the first host on the list that is returned in the SRV lookup,

it will fall back to performing a DNS A-record lookup for the domain in question. If successful, it will attempt to connect to port 443

on the IP address returned from this A-record lookup.

Example

In our example deployment, we have created the following _pexapp._tcp.example.com DNS SRV record:

_pexapp._tcp.example.com. 86400 IN SRV 1 100 443 proxy.example.com.

This points to the DNS A-record proxy.example.com, port 443 (HTTPS), with a priority of 1 and a weight of 100. In other words, it

tells the Pexip Mobile App to send its HTTP requests to host proxy.example.com (our reverse proxy server) on TCP port 443.

In this example, when a user attempts to access [email protected]:

l The Pexip Mobile App will attempt an SRV lookup on _pexapp._tcp.example.com.

o If the SRV lookup succeeds, it will return the record shown above, and the Pexip Mobile App will attempt to contact

proxy.example.com (our reverse proxy server) on TCP port 443.

o If the SRV lookup fails, the Pexip Mobile App will attempt to connect to http://example.com:443.

For more information on setting up reverse proxies, see the Pexip Infinity Reverse Proxy Deployment Guide.

Ultimately it is the responsibility of your network administrator to set up SRV records correctly so that the Pexip Mobile App knows

what system to connect to.




Installing the Pexip Mobile App

Pexip Mobile App for iOSThe Pexip Mobile App requires iOS 5.1 or later and is optimized for iPhone 5. It is compatible with:

l iPhone 3GS

l iPhone 4

l iPhone 4S

l iPhone 5

l iPod touch (3rd generation)

l iPod touch (4th generation)

l iPod touch (5th generation)

l iPad.

The Pexip Mobile App is available for free from the Apple Store at https://itunes.apple.com/us/app/pexip/id667867771. Follow the instructions to download and install the Pexip Mobile App to your device.

Pexip Mobile App for AndroidThe Pexip Mobile App for Android will be released shortly.

https://itunes.apple.com/us/app/pexip/id667867771



Using the Pexip Mobile App

Allowing access to your ContactsThe first time you use the Pexip Mobile App, you will be asked whether you want to allow it to access your contacts:

If you select OK, your contacts will be accessed:

l to display participants' images and names (if they are one of your contacts)

l when you use the Pexip Mobile App to dial out to another participant from a conference.

If you select Don't Allow, when you attempt to add a participant you will see a message:

This app does not have access to your contacts.

If you have previously denied access to your contacts, you can change this setting at a later time as follows:

1. On your iOS device, go to Settings > Privacy > Contacts.

2. Turn the setting for pexip to ON.



Accessing the Virtual Meeting Room or Virtual AuditoriumTo access a Virtual Meeting Room or Virtual Auditorium from your mobile device, do one of the following from the Pexip Mobile

App main page:

l In the Enter Conference URI field, enter the Virtual Meeting Room or Virtual Auditorium alias and then select JOIN.

l To join a Virtual Meeting Room or Virtual Auditorium that you've previously joined, select the button to the right of the

Enter Conference URI field. From the list that appears, select the alias of the Virtual Meeting Room or Virtual Auditorium you

wish to join.



Pre-configuring a domain

If you frequently use Virtual Meeting Rooms and Virtual Auditoriums that have aliases with the same domain, you can configure the

Pexip Mobile App so that you only need to enter the initial part of the alias. For example, if you often access Virtual Meeting Rooms

with the aliases [email protected], [email protected] and [email protected], you could configure the

Pexip Mobile App with a Domain of example.com, so that you only need to enter meet.alice, meet.bob or meet.sales in the URI field in order to join the Virtual Meeting Room.

If you have set up a preconfigured domain, you can still enter Virtual Meeting Room and Virtual Auditorium aliases that use a

different domain. Just enter the full URI in the URI field - the pre-configured domain will be ignored.

To preconfigure the Pexip Mobile App with a domain:

1. Select Connection settings.

2. In the Domain field, enter the domain.

3. Select Done.

Entering the conference PINSome Virtual Meeting Rooms and Virtual Auditoriums are PIN-protected:

You must enter the conference PIN before you can access the conference. If you do not know the PIN, contact the meeting

organizer.



Viewing the list of conference participants

The Participants on stage section lists all the participants whose images are being shown either in the main image or in live

thumbnail images.

The Participants section underneath lists all participants, including the Participants on stage. They appear in the order in which they joined, with the most recent at the top of the list.

To search for a particular participant, select the icon on the right of the screen.

Viewing a presentation on your deviceWhen one of the conference participants is showing a presentation (also known as sharing their screen):

l The icon appears at the top right of the Pexip Mobile App screen.

l The following message appears:

o To view the presentation on your mobile device, select View.

o If you select No, the presentation will not be shown on your mobile device. However, you can still view the presentation

from your device later by selecting the icon.

While viewing the presentation, you can use standard gestures to zoom in and out of the presentation.

To close the presentation view, touch the screen. A Done button appears in the top right corner; select this and the presentation view will close.



Using the Pexip Mobile App to decide what gets shown on your endpointWhen one of the conference participants is showing a presentation, you can use the Pexip Mobile App to either:

l View the presentation on your mobile device, and view conference participants on your video endpoint.

l View the presentation on both your mobile device and your video endpoint.

Viewing the presentation on your mobile device only

To view the presentation on your device, and show the conference participants on your video endpoint:

1. From the list of participants, select your endpoint.

2. Turn View presentation on endpoint to Off.

3. If the presentation is not already showing on your device, select the icon.

Viewing the presentation on your mobile device and video endpoint

To view the presentation on your mobile device and your video endpoint at the same time:

1. From the list of participants, select your endpoint.

2. Turn View presentation on endpoint to On.

3. If the presentation is not already showing on your device, select the icon.



Adding a participant to the conferenceIn order to use this feature:

l You must have host privileges.

l In some cases, your administrator must have enabled this functionality. See About H.323 gatekeepers and SIP proxies for more

information.

l You must have agreed to allow the Pexip Mobile App to access your contacts.

You can use the Pexip Mobile App to dial out to participants from the Virtual Meeting Room or Virtual Auditorium you are in. When

you use this feature, a call is placed to the participant and if and when they answer the call, they will join the conference as a guest

participant (or as a normal participant, if the conference has no PIN). Participants joining the conference in this way will not go

through the IVR screen and will not have to enter a PIN.

To dial out to a participant using the Pexip Mobile App:

1. From within a Virtual Meeting Room or Virtual Auditorium, select the icon on the left of the Participants section.

The following screen will appear:

. 2. Select from the available options:

o to call some already in your Contacts, select Contacts

o to call someone you have recently called from the Pexip App, select Recents

o to call anyone else, select Enter Manually and enter the number or URI to dial.

3. On the confirmation screen, select Dial.





Muting a participantYou must have host privileges to use this feature.

It is possible to mute a participant's audio using the Pexip Mobile App. Note that this will not mute the participant's speakers, so

they will still hear all other unmuted participants, but what they say will not be heard.

When the Pexip Mobile App has been used to mute a participant, the Audio administratively muted? column of the Conference




A Pexip Mobile App user can unmute a participant previously muted by another Pexip Mobile App or Pexip Web App user.

To mute or unmute a conference participant's audio:


2. To mute the participant, turn Enable audio from participant to OFF.

3. To unmute the participant, turn Enable audio from participant to ON.

Disconnecting a participantYou must have host privileges to use this feature.

To remove a participant from the conference:


2. Select .

Pexip Infinity Administrator Guide Appendices


AppendicesIn this section:

Glossary 190

Pexip Infinity port usage 193

Encryption methodologies 198

Supported RFCs 199

Advanced VMware ESXi administration 201

Using Multiway with Pexip Infinity 206

Troubleshooting 209

License information 213



Glossary

Term Definition

Alias The string that, when received by a Conferencing Node, will trigger the creation of a conference

instance (or if one already exists, will cause the call to be routed to the appropriate conference).

Each alias is associated with a service (Virtual Meeting Room, Virtual Auditorium or Virtual Reception),

which defines the type and settings (such as PIN) for the conference that is created.

In most cases, the alias received by the Conferencing Node will be the same as the alias that the

conference participant dialed from their endpoint, but there are some exceptions (for more

information see About aliases).

Depending on the dial plan, multiple aliases can be used throughout a network to access the same

service.


participant

A participant who will have a call placed to them from a Virtual Meeting Room or Virtual Auditorium

whenever a conference using that service starts.


Backplane A link between the Management Node and a Conferencing Node, or between two Conferencing Nodes,

used to transmit Pexip control messages. Backplanes between Conferencing Nodes also transmit

conference audio, video, and data packets. All packets are secured through authentication and

encryption designed to protect the privacy of the data.

For more information, see Encryption methodologies.

Conference instance A conference with active participants that exists on one or more Conferencing Nodes. A unique

conference instance is created when the first participant dials a Virtual Meeting Room or Virtual

Auditorium alias and lasts until the last participant disconnects.

Conferencing Node A virtual machine (VM) that provides the capacity for conferences, handling the media processing and

call signaling.

For more information, see About Conferencing Nodes.

Core One single physical processing unit.

Intel Xeon E5 typically has 8 cores (10, 12 or more in newer versions)

Distributed conference A conference instance that exists across two or more Conferencing Nodes. It can be locally distributed,

globally distributed, or both:

Locally distributed conferences exist across two or more Conferencing Nodes in the same location.

Globally distributed conferences exist across two or more Conferencing Nodes in physically different

locations.

Locally and globally distributed conferences exist across two or more Conferencing Nodes in one

location and at least one other Conferencing Node in a different location.



Term Definition

Endpoint A device capable of participating in a conference. The endpoint's capabilities can vary from audio-only

to full audio, video, and data sharing support.

Host A conference participant who has privileges to control aspects of the conference. For more information,

see About PINs, hosts and guests.

Host server The physical hardware on which the virtual Management Node and Conferencing Nodes reside. For

more information, see Host servers.

Hypervisor An application that is used to create and manage virtual machines. For more information on the

hypervisors supported by Pexip Infinity, see Hypervisors.

IVR

(Interactive Voice

Response)

IVR technology allows participants to use a DTMF keypad to interact with Pexip Infinity services to:

l select which Virtual Meeting Room or Virtual Auditorium they wish to join. For more information,

see About the Virtual Reception.

l enter a PIN, for those Virtual Meeting Rooms that have restricted access. For more information,

see About PINs, hosts and guests.

Management Node A virtual machine (VM) on which the Pexip Infinity software is installed. This machine hosts the Pexip

Infinity web interface. It is used to create one or more Conferencing Nodes and configure information

about the conferences that can exist on those Conferencing Nodes.

NUMA node The combination of a processor (consisting of one or more cores) and its associated memory.

Pexip Mobile App The Pexip mobile application. Using the Pexip Mobile App, conference participants can view

presentations and control aspects of the conference.

Pexip Infinity A virtual conferencing platform that encompasses a single Management Node and its associated

Conferencing Node(s). Together they provide a coherent conferencing service to a single organization.

Pexip Infinity software The files that are used to deploy the Management Node on to the physical virtual machine (VM)

infrastructure.

Pexip Web App A web-based video client included as part of all Pexip Infinity deployments. For more information, see

Using the Pexip Web App.

Port Within the Pexip Infinity, a port equates to a single endpoint connected to a conference. For more

information, see About licenses.

Port can also refer to the virtual data connections used for network traffic between devices. For more

information on the ports used by the Management Node and Conferencing Nodes to connect to other

devices, see Pexip Infinity port usage.



Term Definition

Processor The hardware within a computer that carries out the basic computing functions. Can consist of multiple

cores.

Proxy In a globally distributed conference, one Conferencing Node in each location will act as the proxy for

any other Conferencing Nodes in the same location. Each proxy will funnel traffic between physical

locations. This will prevent full mesh bandwidth occupation, minimizing bandwidth consumption and

ensuring optimal WAN utilization.

RAM Also referred to as "memory". The hardware that stores data which is accessed by the processor core

while executing programs.

Socket The socket on the motherboard where one processor is installed.

System location A label that allows you to group Management Nodes and Conferencing Nodes together according to

where they are physically located. For more information, see About system locations.

Thumbnail A smaller window at the bottom of the main picture which displays the live video stream from a

conference participant.

Virtual Machine

(VM)

A software implementation of a computer, which runs on a host server and is implemented and

managed using a hypervisor. The Management Node and Conferencing Nodes are virtual machines.

Virtual Auditorium A meeting space that is optimized for use by a small number of hosts and a large number of guests. For

more information, see About Virtual Auditoriums.

Virtual Meeting Room A personal virtual meeting space. For more information, see About Virtual Meeting Rooms.

Virtual Reception A central IVR service from which participants can select the Virtual Meeting Room or Virtual Auditorium

they wish to join. For more information, see About the Virtual Reception.

VM Manager An application that allows you to connect to one or more VMware vSphere ESXi Hypervisors (which

manage host servers and their virtual machines). VM Managers supported by version 4 of Pexip Infinity

are vCenter Server and vSphere.

l vCenter Server is an application that is used to manage one or more host servers running ESXi,

through a single interface.

l vSphere on the host is used when managing a single host server running ESXi.

For more information see About VM Managers.



Pexip Infinity port usageThe diagrams and tables below show the ports used when the Management Node and Conferencing Node connect to other devices.

Management Node

Inbound

Protocol Source-Port Dest-Port Direction Description Device

TCP 1024-65535 22 In SSH * SSH client

TCP 1024-65535 80 In HTTP * Web browser/

API interface

TCP 1024-65535 443 In HTTPS Web browser/

API interface

UDP 0-65535 161 In SNMP ‡ SNMP server

UDP 500 500 In ISAKMP (IPsec) Conferencing Node

ESP IP Protocol 50 IP Protocol 50 In IPsec Conferencing Node

Outbound


TCP 55000-65535 53 Out DNS DNS server

TCP 55000-65535 443 Out HTTPS vCenter Server and any ESXi host on which workers may be

deployed *

TCP 55000-65535 443 Out HTTPS Pexip Licensing server

(pexip.flexnetoperations.com, 64.14.29.85) *

TCP 55000-65535 514 Out Syslog † Syslog server

UDP 55000-65535 53 Out DNS DNS server

UDP 123 123 Out NTP NTP server

UDP 500 500 Out ISAKMP

(IPsec)

Conferencing Node

UDP 55000-65535 514 Out Syslog ‡ Syslog server

ESP IP Protocol

50

IP Protocol

50

Out IPsec Conferencing Node

* Not required for correct operation.

† Currently unused but expected to be in future.

‡ Only applies if the relevant feature is configured.

Note also that the ephemeral and media port ranges are subject to change.



Management Node port usage



Conferencing Node

Inbound


TCP 0-65535 40000-49999 ** In RDP Endpoint/

Call control system

TCP 1024-65535 22 In SSH * SSH client

TCP 1024-65535 80 In HTTP Web browser/

API interface

TCP 1024-65535 443 In HTTPS Web browser/

API interface/

Pexip Mobile App

TCP 1024-65535 1720 In H.323

(H.225 signaling)

Endpoint/

Call control system

TCP 1024-65535 5060 In SIP Endpoint/

Call control system

TCP 1024-65535 5061 In SIP/TLS Endpoint/

Call control system

TCP 1024-65535 33000-39999 ** In H.323

(Q.931/H.245 signaling)

Endpoint/

Call control system

UDP 0-65535 161 In SNMP ‡ SNMP server

UDP 500 500 In ISAKMP (IPsec) Management Node/

Conferencing Node

UDP 0-65535 1719 In H.323

(RAS signaling)

Endpoint/

Call control system

UDP 0-65535 5060 In SIP Endpoint/

Call control system

UDP 0-65535 40000-49999 ** In RTP/RTCP Endpoint/

Call control system

ESP IP Protocol 50 IP Protocol 50 In IPsec Management Node/

Conferencing Node

Outbound


TCP 55000-65535 53 Out DNS DNS server




TCP 55000-65535 514 Out Syslog † Syslog server

TCP 1024-65535 1720 Out H.323 Endpoint/

Call control system

TCP 33000-39999 ** 5060 Out SIP Endpoint/

Call control system

TCP 33000-39999 ** 5061 Out SIP/TLS Endpoint/

Call control system

TCP 33000-39999 ** <any> Out H.323 Endpoint/

Call control system

UDP 50000-65535 53 Out DNS DNS server

UDP 123 123 Out NTP NTP server

UDP 500 500 Out ISAKMP (IPsec) Management

Node/

Conferencing

Node

UDP 50000-65535 514 Out Syslog ‡ Syslog server

UDP 33000-39999 ** 1719 Out H.323 Endpoint/

Call control system

UDP 33000-39999 ** 5060 Out SIP Endpoint/

Call control system

UDP 40000-50000 ** 0-65535 Out RTP/RTCP Endpoint/

Call control system

ESP IP Protocol 50 IP Protocol 50 Out IPsec Management

Node/

Conferencing

Node

* Not required for correct operation.

** This can be configured using the Media port range start/end and Signaling port range start/end options. For more information,

see Editing the Management Node.

† Currently unused but expected to be in future.

‡ Only applies if the relevant feature is configured.

Note also that the ephemeral and media port ranges are subject to change.



Conferencing Node port usage



Encryption methodologies

Pexip nodesThe backplane (the link between the Management Node and a Conferencing Node, or between two Conferencing Nodes) uses an

IPsec tunnel with the following settings:

l 256-bit AES-CBC for encryption

l SHA 512 hashing for integrity checking

l a 4096 bit Diffie-Hellman modulus for key exchange.

No other ciphers, hashes or moduli are permitted.

These settings apply to both the initial channel set up for key exchange (ISAKMP) and the secondary channel over which application

data is transported (ESP).

EndpointsEncrypted connections between the Pexip Infinity and endpoints use:

l AES 128-bit encryption for media

l TLS for SIP call control (for more information, see Managing TLS certificates)

l SRTP for SIP media

l H.235 for H.323 media



Supported RFCsPexip Infinity supports the following RFCs:

l RFC 1889 RTP: A Transport Protocol for Real-time Applications

l RFC 2190 RTP Payload Format for H.263 Video Streams

l RFC 2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)

l RFC 2782 DNS RR for specifying the location of services (DNS SRV)

l RFC 2790 Host Resources MIB

l RFC 2976 The SIP INFO Method

l RFC 3261 SIP: Session Initiation Protocol

l RFC 3263 Locating SIP Servers

l RFC 3264 An Offer/Answer Model with SDP

l RFC 3550 RTP: A Transport Protocol for Real-Time Applications

l RFC 3581 Symmetric Response Routing

l RFC 3605 RTCP attribute in SDP

l RFC 3711 The Secure Real-time Transport Protocol (SRTP)

l RFC 3840 Indicating User Agent Capabilities in SIP

l RFC 3890 A Transport Independent Bandwidth Modifier for SDP

l RFC 3984 RTP Payload Format for H.264 Video

l RFC 4320 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction

l RFC 4321 Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction

l RFC 4566 SDP: Session Description Protocol

l RFC 4568 SDP: Security Descriptions for Media Streams

l RFC 4574 The Session Description Protocol (SDP) Label Attribute

l RFC 4582 The Binary Floor Control Protocol

l RFC 4583 SDP Format for BFCP Streams

l RFC 4585 Extended RTP Profile for RTCP-Based Feedback

l RFC 4587 RTP Payload Format for H.261 Video Streams

l RFC 4629 RTP Payload Format for ITU-T Rec. H.263 Video

l RFC 4733 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals

l RFC 4796 The SDP Content Attribute

l RFC 5168 XML Schema for Media Control

l RFC 5245 Interactive Connectivity Establishment (ICE)

l RFC 5389 Session Traversal Utilities for NAT (STUN)

l RFC 5577 RTP Payload Format for ITU-T Recommendation G.722.1

l RFC 5763 Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport

Layer Security (DTLS)

l RFC 5766 Traversal Using Relays around NAT (TURN)

l RFC 6026 Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests

l RFC 6416 RTP Payload Format for MPEG-4 Audio/Visual Streams



l draft-ietf-bfcpbis-rfc4582bis-10.txt

l draft-ietf-bfcpbis-rfc4583bis-08.txt

l draft-ietf-avt-rtp-h264-params-01.txt

l draft-ietf-payload-rtp-opus-01.txt

l draft-ietf-payload-rtp-vp8-10.txt

l draft-ietf-mmusic-sdp-g723-g729-04.txt



Advanced VMware ESXi administrationSimple deployments of the Pexip Infinity should not require any special VMware knowledge or configuration beyond that described

in Configuring VMware.

This section describes some important requirements for advanced VMware ESXi administration when used with the Pexip Infinity. It

assumes that you are already familiar with VMware. For more information on VMware ESXi in general, see

http://www.vmware.com/products/vsphere/esxi-and-esx/overview.html.





Supported vSphere versionsVersion 2 of the Pexip Infinity platform supports VMware vSphere ESXi 4.1, 5.0 and higher, although we recommend ESXi 5.1.

Supported vSphere editions

The Pexip Infinity platform will run on the free edition of vSphere Hypervisor. However, this edition has a number of limitations

(limited support from VMware, no access to vCenter or vMotion, no access to VMware API, and a maximum of 32 GB RAM). In

particular, the lack of access to the VMware API means that all Conferencing Nodes will have to be deployed manually (see

Deployment types). For this reason we do not recommend its use except in smaller deployments, or test or demo environments.

The minimum edition of VMware that we recommend is the vSphere Standard edition. This does not have the limitations of the

free edition. If you do not already use VMware in your enterprise, the vSphere Essentials Kit is a simple way to get started and will

provide you with Standard edition licenses for 3 servers (with 2 CPUs each) plus a vCenter license.

For larger deployments, you may wish to use the Enterprise edition which includes additional features relevant to the Pexip Infinity platform, such as DRS (Distributed Resource Scheduler). DRS allows you to automatically move virtual machines between different

physical host servers to balance the amount of load across the virtual machines (VMs) and the hosts.

The Enterprise Plus edition includes further additional features relevant to the Pexip Infinity platform that could be of benefit to

larger deployments. These include Storage DRS and Distributed Switch.

For a comparison of the VMware editions, see http://www.vmware.com/products/datacenter-virtualization/vsphere/compare-

editions.html.

Management Node network requirementsWhen deploying Conferencing Nodes, the Management Node connects to the vCenter Server (or the ESXi host directly) on port 443

(https).

This communication port must be open when creating new Conferencing Nodes.

Permissions in vCenter Server (or on ESXi hosts)A valid username and password for the vCenter Server or ESXi host must be entered every time a new Conferencing Node is created.

For security and tracking reasons, these credentials will not be stored by the Management Node.

The account used to log in to vCenter Server or the ESXi host from the Management Node must have sufficient permissions to

create virtual machines (VMs) on the folder or resource group where the Conferencing Node will be deployed. The permissions

listed below are required as a minimum (in vCenter Server, these permissions should be set on Datacenter level or higher):

http://www.vmware.com/products/vsphere/esxi-and-esx/overview.html

http://www.vmware.com/products/datacenter-virtualization/vsphere/compare-editions.html



l Datastore > Allocate space

l Datastore > Browse datastore

l Network > Assign network

l Resource > Assign virtual machine to resource pool

l vApp > Import

l Virtual Machine > Configuration > Add new disk

l Virtual Machine > Interaction > Configure CD media

l Virtual Machine > Interaction > Power On

The Administrator role includes all the above permissions (in addition to many others).

Host server requirements

CPU

The Pexip Infinity platform requires at a minimum Intel Xeon Penryn processors, or AMD processors manufactured in 2012 or later.

However, we recommend Intel Xeon Sandy Bridge and processors with an AVX instruction set.

We recommend a minimum of 6- to 8-core CPUs. Conferencing Nodes can also be deployed on 4-core CPUs, although this will

increase the application overhead. We do not recommend less than 4 cores.

RAM

2 GB of RAM per Conferencing Node. This is in addition to the requirements of the host operating system, so for example a

dedicated host server with one Conferencing Node will require a minimum of 4 GB.

GPU

Host servers do not require any specific hardware cards or GPUs.

Disk

Either direct attached storage or shared storage can be used. The primary disk activity will be logging.

Multitenancy

This version of the Pexip Infinity requires a dedicated VMware host for supported deployments.

Multitenancy with other applications may be supported in the future, and is possible in a test environment as long as other

applications on the same host server are not consuming significant CPU and the Pexip Infinity can be given reserved memory.

General recommendationsThe Pexip Infinity can take advantage of advanced CPU features, so for optimal performance we recommend that you run

Conferencing Nodes on your newer host servers.

CPUs with a large cache (15-30 MB+) are recommended over CPUs with a smaller cache (4-10 MB), especially when running 10 or

more participants per conference.

To protect the overall quality of the conference, we highly recommend that any hardware resources allocated to a Conferencing

Node are reserved specifically for its own use.



Impact on virtual environment

CPU

The CPU is the most critical component in a successful deployment of the Pexip Infinity.

Newer Intel (or AMD) CPUs typically provide more features which the Pexip Infinity will utilize to give better performance. We

therefore recommend that you deploy the Pexip Infinity on newer hardware, and move applications that are not so time-critical (for

example, mail servers, web servers, file servers) to your older hardware.

Memory

The memory specified for the Pexip Infinity deployment should not be shared with other processes, because the Pexip Infinity

accesses memory at a high speed when active. However, the amount of memory needed is quite small compared to the workload,

and increasing the memory beyond the recommended scope will not significantly increase performance.

Storage

Apart from storing the Pexip Infinity application, the disk activity during operation will mainly be used for logging. There is therefore

no need to deploy your fastest or newest SSD drives for this application, as most of the real-time activity happens in memory.

Standard disk access as required for most servers should be used to get good logging performance.

Network

Gigabit ethernet connectivity from the host server is strongly recommended, because Conferencing Nodes are sending and receiving

real-time audio and video data, and any network bottlenecks should be avoided. The amount of traffic to be expected can be

calculated based on the capacity of the servers, but typically 100 Mbps network links can easily be saturated if there is a large

number of calls going through a given Conferencing Node. In general, you can expect 1-3 Mbps per port, depending on call control

setup.

Traffic shapingAny shaping of the Conferencing Node traffic that can potentially limit its flow should not be used without considerable planning. If

bandwidth usage to or from a Conferencing Node is too high, this should be addressed in the call control, as shaping it on the

Conferencing Node level will most likely reduce the experience for the participants.

NIC teamingVMware NIC teaming is a way to group several network interface cards (NICs) to behave as one logical NIC. When using NIC teaming

in ESXi, we recommend you load balance using originating Virtual Port ID due to its low complexity (it does not steal CPU cycles

from the host). Source MAC hash is also usable; we do not recommend IP hash because of the CPU overhead for a lot of media

packets.

vMotionConferencing Nodes (and the Management Node) can be moved across host servers using vMotion. If they are idle there will not be

any significant impact. If a Conferencing Node is busy with conferences, it will be possible to move it depending on host resources,

bandwidth etc. When moving the last bit of the Conferencing Node, ESXi will stall the VM on the old host server, send an RARP, and

reactivate the Conferencing Node on the new host server. This may result in a few seconds of frozen video to and from participants

on this Conferencing Node. For this reason we do not recommend moving Conferencing Nodes while a conference is in progress

unless absolutely necessary.

For instructions on using vMotion to move a Conferencing Node, see Migrating Conferencing Nodes between host servers.



For more information on vMotion in general, see http://www.vmware.com/products/datacenter-

virtualization/vsphere/vmotion.html.

Distributed Resource Scheduler (DRS)

Storage DRS should not significantly impact the Pexip Infinity.

Host DRS will in most scenarios work fine, because VMware will consider the cost of moving theConferencing Node against the cost

of moving other VMs. If a Pexip Infinity is busy hosting a conference with a lot of participants, it is likely that VMware will decide to

move other VMs off the host server. If other VMs are also very busy, and VMware decides to use vMotion to move the Conferencing

Node while a conference is running on it, the participants will see a few seconds of frozen video just as they are moved to the new

host servers.

For more information on DRS, see http://www.vmware.com/products/datacenter-virtualization/vsphere/drs-dpm.html.

Enhanced vMotion Compatibility (EVC)When EVC (Enhanced vMotion Compatibility) is enabled across a cluster of host servers, all servers in that cluster will emulate the

lowest common denominator CPU. This allows you to move VMs between any server in the cluster without any problems, but it

means that if any servers in that cluster have newer-generation CPUs, their advanced features can not be used.

Because Conferencing Nodes use the advanced features of newer-generation CPUs, (for example AVX on newer Intel CPUs), we

recommend that you disable EVC (Enhanced vMotion Compatibility) for any clusters hosting Conferencing Nodes where the cluster

includes a mix of new and old CPUs.

If you enable EVC on mixed-CPU clusters, the Pexip Infinity platform will run more slowly because it will cause the Conferencing

Nodes to assume they are running on older hardware.

If you enable EVC, you must select the Penryn-compatible EVC mode as a minimum. This is the lowest EVC mode that supports the

SSE4.1 instruction set, which is required to run the Pexip Infinity platform.

When enabling EVC or lowering the EVC mode, you should first power off any currently running VMs with a higher EVC mode

than the one you intend to enable.

When disabling EVC or raising the EVC mode, any currently running VMs will not have access to the new level until they have

been powered off and on again.

For instructions on disabling EVC, see Disabling EVC.

For more information on EVC in general, see http://pubs.vmware.com/vsphere-

51/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-9F444D9B-44A0-4967-8C07-693C6B40278A.html.

vSphere High AvailabilityvSphere High Availability (HA) can be configured so that, in the case of an ESXi host failure, it will automatically start the VM on

another host in the cluster. This is supported for both Management Node and Conferencing Nodes and will provide protection

against hosts failing.

Loss of a Conferencing Node in such circumstances will result in any participants connected to that node being disconnected. They

will have to redial the Virtual Meeting Room alias to rejoin the conference.

Momentary loss of the Management Node will not affect running conferences.

For more information on HA, see http://www.vmware.com/products/datacenter-virtualization/vsphere/high-availability.html.

http://www.vmware.com/products/datacenter-virtualization/vsphere/vmotion.html

http://www.vmware.com/products/datacenter-virtualization/vsphere/drs-dpm.html

http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-9F444D9B-44A0-4967-8C07-693C6B40278A.html

http://www.vmware.com/products/datacenter-virtualization/vsphere/high-availability.html



vSphere Fault ToleranceFor zero downtime, the Management Node can be protected with vSphere Fault Tolerance (FT), because it is only using a single

virtual CPU.

For more information on FT, see http://www.vmware.com/products/datacenter-virtualization/vsphere/fault-tolerance.html.

http://www.vmware.com/products/datacenter-virtualization/vsphere/fault-tolerance.html



Using Multiway with Pexip InfinityMultiway™ is a Cisco TelePresence feature that allows an endpoint user to transfer an established point-to-point call to an MCU, so

that more participants can join the conference.

If your deployment includes endpoints that support Cisco TelePresence Multiway, you can configure these endpoints to use Pexip

Infinity Virtual Meeting Rooms for Multiway conferences.

The exact configuration required to support Multiway will depend on whether or not you use the VCS Conference Factory

application (an application on the VCS which dynamically generates a unique conference alias for each Multiway conference).

For full information on Multiway, see the Cisco TelePresence Multiway Deployment Guide

(http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_TelePresence_Multiway_

Deployment_Guide_X7_XC1-2.pdf).

Example scenarioThe sections below describe how to enable the following example scenario:

l Alice makes a point-to-point call to Bob.

l They want to include Charlie in the conversation, so Alice puts Bob on hold, calls Charlie, and then Joins the calls together.

l All 3 participants are dialed in to a Virtual Meeting Room on the Pexip Infinity.

Configuring endpoints using xConfiguration commandsThe xConfiguration commands used to enable Multiway vary depending on the endpoint. Below are example commands for some

more common endpoints, showing how to configure them with the alias [email protected].

E20

xConfiguration SystemUnit MultiwayURI: "[email protected]"

MXP

xConfiguration Multipoint Mode: Multiway

xConfiguration Multipoint MultiwayURI: "[email protected]"

T150

xConfiguration Multipoint MultiwayURI: "[email protected]"

Deployments without VCS Conference FactoryIn a non-Conference Factory deployment, each endpoint must be configured with its own Multiway alias, which must match a

Virtual Meeting Room alias. When point-to-point calls are escalated to a Multiway conference, all endpoints call this alias and are

routed to the same Virtual Meeting Room.

Endpoint configuration

The endpoint that initiates the join must support Multiway and be configured with a Multiway alias that matches a Virtual Meeting

Room alias in the Pexip Infinity. In this example, we have configured Alice's endpoint to use her personal Virtual Meeting Room alias

of [email protected] as her Multiway alias.

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_TelePresence_Multiway_Deployment_Guide_X7_XC1-2.pdf



Pexip Infinity configuration

No additional configuration is required on the Pexip Infinity, beyond ensuring that at least one appropriate Virtual Meeting Room

exists that can be used for Multiway conferences.

A Virtual Meeting Room used for Multiway does not need to be reserved specifically for Multiway. It can be a user's personal Virtual

Meeting Room, as in this example.

If a Virtual Meeting Room that is being used for Multiway has a PIN configured, all participants must know the PIN and be able to

enter it from their endpoint in order to access the conference.

In this example scenario we had already created a personal Virtual Meeting Room for Alice which uses the alias

[email protected], and we will use this Virtual Meeting Room for her Multiway calls. If you want to create a new Virtual

Meeting Room:

On the Pexip Infinity web interface, go to Virtual Meeting Room configuration.

1. Select Add Virtual Meeting Room.

2. In the Name field, enter Alice.

3. Enter a PIN, if required.

4. In the Alias field, enter [email protected].

5. Select Save.

The Virtual Meeting Room is now configured and available for use whenever [email protected] is dialed, including when it

is dialed as part of a Multiway escalation.

Deployments using VCS Conference FactoryThe VCS Conference Factory application dynamically generates a unique conference alias for the Multiway conference. When the

VCS Conference Factory application is used for Multiway, all endpoints must be configured with the same Multiway alias. When this

alias is dialed by the initiating endpoint, it creates a query to the VCS for the alias that will be used for the conference. The VCS

generates an alias based on its Conference Factory configuration, and all endpoints then dial this alias to access the Virtual Meeting

Room. This means that all possible aliases that could be generated by the VCS must be configured on the Pexip Infinity and each

must be associated with a unique Virtual Meeting Room.

Endpoint configuration

All endpoints must be configured with the same Multiway alias. In this example, they are all configured to use the alias

pexip.multiway.

VCS configuration

In this example, we will configure the VCS to generate aliases in the range [email protected] to

[email protected] whenever a Multiway call is initiated.

Note that a range of 9 is for example purposes only and is too small for most deployments.

On the VCS, go to the Conference Factory page (Applications > Conference Factory) and configure it as follows:



Mode On

Alias pexip.multiway

Template multiway%%@example.com

Number range start 1

Number range end 9

Pexip Infinity configuration

On the Pexip Infinity, we create 9 Virtual Meeting Rooms specifically for use by Multiway, and to each we assign one of the 9

aliases.

We could do this manually for each alias by going to Virtual Meeting Room configuration > Virtual Meeting Room and selecting

Add Virtual Meeting Room. However, we can also use the Pexip Infinity's importing configuration feature, so instead we select

Import, and import the following CSV file:

multiway1,,,,,[email protected],









This creates a Virtual Meeting Room with the name multiway1 and an alias of [email protected]; another with the name

multiway2 and an alias of [email protected]; and so on for all 9 aliases.



Troubleshooting

Symptom Possible cause Resolution

During upgrade, one or more

Conferencing Nodes are stuck with a

status of "waiting for calls to clear",

but there are no active calls

reported on the Management Node.

A bug in v3 of the software means that in

some circumstances a SIP call will not clear

properly from the Conferencing Node.

Reboot the Conferencing Node.

A Conferencing Node does not

accept calls even though it has been

powered on and is contactable on

the network.

If time is not properly synchronized

between the Management Node and the

host server, certificates issued by the

Management Node may be invalidated by

Conferencing Nodes within the same Pexip

Infinity deployment. As a result, the

Conferencing Nodes will not communicate

properly with the Management Node,

causing calls to fail.

Ensure all virtual machines (VMs) (i.e. the

Management Node and all Conferencing

Nodes) within the Pexip Infinity platform,

and the host servers on which they are

running, are using accurate times according

to the public or private standard NTP clock.

We strongly recommend that you configure

at least 3 distinct NTP servers or NTP server

pools in each instance to ensure proper

synchronization.

To synchronize time on the Pexip Infinity:

1. Synchronize time on host servers (for

instructions see Configuring VMware

or Configuring Hyper-V).

2. Enable NTP on Management Node.

3. Reboot all VMs.

Log timestamps appear to be

inaccurate or log entries appear to

be out of sequence.

Time is not properly synchronized between

the Management Node, Conferencing

Nodes and their host servers, causing

different systems to use different

timestamps. This could be because:

l Insufficient NTP servers or NTP pools

have been configured on a host server

or the Management Node (we

recommend a minimum of 3).

l One or more NTP servers are

unreachable or have inaccurate time

themselves.

l NTP is otherwise not configured

according to our recommendations.

As above.




Presentations do not display full

screen

If the presentation being shared is either:

l an application that is not in full-screen

mode

l a full screen image that is being sent

from a non-standard aspect ratio screen

then the image being sent may have a non-

standard aspect ratio. In order to send the

image inside a standard resolution window

(for example 640x480 [4:3]) or 1280x720

[16:9]), the endpoint may add horizontal or

vertical mattes (also known as letterboxing

or pillarboxing respectively).

Ensure that presenters always either:

l share their entire screen, or

l share individual applications when they

are in full-screen mode only.

Images are not displaying as

expected:

l they are being cropped

l they have black bars at the top

or sides

Endpoints send and display video images

and presentations in various aspect ratios,

most commonly 16:9 and 4:3. If there is a

difference between the aspect ratios of the

sending and receiving endpoints, then the

endpoint and/or the Pexip Infinity may crop

the image or add vertical or horizontal

mattes.

For more information, see Changing aspect

ratios.

A new Management Node or

Conferencing Node doesn't work. It

was created by cloning it through

VMware.

You cannot use cloning to create

Management Nodes and Conferencing

Nodes.

Create all Management Nodes according to

the instructions in Installing the

Management Node.

Create all Conferencing Nodes by following

the instructions in Deploying new

Conferencing Nodes.

I entered the wrong information

while running the installation wizard.

Re-run the installation wizard by following

the instructions in Re-running the

installation wizard




How do I register the Pexip Infinity

to a gatekeeper?

You don't. Instead, you configure your call

control system to route calls to the Pexip

Infinity. See Using a gatekeeper to route

calls to Pexip Infinity conferences.

Participants cannot join a conference

due to insufficient capacity.

l When users attempt to join a

conference they get a message

saying "Participants cannot join a

conference due to insufficient

capacity."

l The admin log is reporting

"Participant failed to join

conference" and "resource

unavailable".

All Conferencing Nodes that are able to

take the media for this call are at capacity.

l Deploy more Conferencing Nodes in

this location.

l Move existing Conferencing Nodes

onto more powerful servers.

l Allocate more virtual CPUs for

Conferencing Nodes on existing servers

(if there are sufficient CPU cores). Note

that the Conferencing Node will have

to be rebooted for this to take effect.

The participant has dialed in to the

Conferencing Node while it is still starting

up and an internal capacity-checking tool is

running.

The Administrator should place the

Conferencing Node into maintenance mode

if it is expected to be powered off and on.

If the Conferencing Node is not in

maintenance mode while the capacity-

checking tool is running the participant

should wait a few moments and then

attempt to join the conference.


due to an invalid license.




conference due to an invalid

license."



conference" and "no valid

license available".

l The license has not been activated.

l The existing license has expired.

l The existing license has become

corrupt.

For more information, see About licenses.

l Check the status of your licenses from

the Licensing page (Platform

configuration > Licenses).

l Contact your authorized Pexip

representative for assistance.





due to insufficient licenses.




conference due to insufficient

licenses."



conference" and "license limit

reached".

There are not enough port licenses

available on the system at this time. For

more information, see About licenses.

l Wait until one or more of the existing

conferences have finished and the

licenses have been returned to the

pool.

l Contact your authorized Pexip

representative to purchase more

licenses.

Users can't enter a conference PIN

from a T150 running L5.1.

There was a bug in the L5.1 software which

meant that DTMF tones weren't being sent

properly over SIP.

Do one of the following:

l upgrade the T150 to L6.1

l use H.323 (not SIP)

l interwork to SIP via a VCS.



License information

Pexip Infinity license

The full text of the Pexip Infinity license is available from the Pexip website under www.pexip.com/Infinity-License.

Third party licensesThe full text of all licenses for third-party software used in the Pexip Infinity platform is available from the Pexip Infinity web

interface by selecting the About link at the top right of the page and then selecting Third Party Software. It is also available from

the Pexip website under www.pexip.com/3rd-Party-Licenses.

http://www.pexip.com/Infinity-License

http://www.pexip.com/3rd-Party-Licenses

pexip infinity administrator guide v4 a

Documents

document version4