RealPresence CloudAXIS Suite

Transcription

1 ADMINISTRATORS GUIDE Software February Rev. A RealPresence CloudAXIS Suite Polycom, Inc. Internal Use 1

2 Copyright 2014, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc America Center Drive San Jose, CA USA Trademarks Polycom, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom. End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by at OpenSourceVideo@polycom.com. Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided as is without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages. Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. your opinions and comments to DocumentationFeedback@polycom.com. Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more. Polycom, Inc. 2

3 Contents About This Guide... 6 Conventions Used in this Guide... 6 Terms and Writing Conventions... 6 Information Elements... 7 Typographic Conventions... 7 What s in this Guide?... 8 Get Started Understand the RealPresence Platform Understand the Minimum Requirements Minimum Server Requirements Understand Port Usage Complete the Setup Worksheets Get Help and Support Resources Deploy and Configure the Portals Deploy the Services Portal and Experience Portal Packages Use of Experience Portal Cookies Use of Services Portal Cookies Access the Services Portal Check an Unresponsive Portal URL (FQDN) Access the Experience Portal Configure the Services Portal Log In as the Super Admin Synchronize Portal Timing Configure the Connection to the LDAP Server Configure the Connection to the SMTP Server Configure Additional Server Settings Configure Social Policies Configure the Connection to the DMA System and RPAD Servers Localize the Services Portal View and Customize the Templates Set Date and Time Manage Certificates Select and Download Log Levels Update Services Portal Software Activate Licenses Configure HTTP Forward Proxy Settings Configure the Experience Portal Configure the Server Settings Configure the Environment General Settings Configure Certificates on Experience Portal Polycom, Inc. Internal Use 3

4 Configure the Meeting Hosts Configure DMA Settings Configure VMR Settings Configure Connection Settings Configure Authentication Provider Settings View Experience Portal Log Files Apply Experience Portal Configurations Set System Administration UI Properties Update the Experience Portal Software Export the Experience Portal Configuration File Import the Experience Portal Configuration File Localize the Experience Portal Create and Manage User Accounts Understand Account Roles Create Accounts Add Active Directory Users Add Local Users Edit Accounts Edit Accounts Created from the Active Directory Edit Locally Created User Accounts Delete Accounts Change Your Password Reset a Password Provide Secure Guest Access Secure SIP Guest Access Enable Guest Access on Your Edge Proxy Additional Recommendations for Greater Security Secure Web Access Troubleshoot the Services Portal User Cannot Create Meetings User Cannot Launch the Welcome Screen Configured Components are Not Responding Super Admins and Admins Cannot Add an Active Directory User User Cannot Send Notifications User Receives Unable to Create a Conference with a Personal VMR Message User Receives External Server Not Set Message User Receives Video Resources Are Not Available Message Obtain Services Portal Log Files User Cannot Download Logs on Internet Explorer User Cannot See All the Participants in Roster Get Help Polycom and Partner Resources The Polycom Community Polycom, Inc. 4

5 Create a Google Talk App Create a Facebook App DMA Factory Conference Settings Impact Restricted Shell Usage Use Case - Login as caxis via Console or via a SSH Connection Use Case - Change system hostname Use Case - Log collection Use Case - Copying the generated logs to a different server Use Case - Access log files Use Case - Changing the password of the caxis user Use Case - Configure system NTP settings Use Case - Quick sync system date-time with a specific NTP server Use Case - Show product version Use Case - Regeneration of certificates Use Case - Change system timezone Use Case - Restarting services Use Case - Set system date time Use Case - View system network information Use Case - System network configuration is already set to use DHCP Use Case - Enabling DHCP in a machine where DHCP is not enabled Use Case - Configuring static IP address in a system where DHCP is in an enabled state Use Case - Configuring static IP address in a system where DHCP is in a disabled state Use Case - Configuring static IP address in a system where DHCP is in a disabled state with the currently assigned IP address Use Case - Attempting to configure manual DNS settings while DHCP is enabled in the system Use Case - Using invalid network values Use Case - Using an IP that is already assigned to a machine in the same network Use Case - Reboot system Use Case - Exit restricted shell Use Case - Login timeout Third-Party Software Polycom, Inc. 5

6 1: About This Guide This administrators guide uses a number of conventions that can help you to understand information and perform tasks. Conventions Used in this Guide This administrators guide contains terms, graphical elements, and typographic conventions. Familiarize yourself with these tools to help you successfully perform tasks. Terms and Writing Conventions As you read this guide, you will notice that some terms and conventions are used repeatedly. Familiarize yourself with these terms and conventions so you understand how to perform administration tasks. Apache Tomcat An open source web server and application container for running the Services Portal application. Experience Portal The meeting conference interface. It is referred to in the user interface as the MEA (Meeting Experience Application). FQDN The acronym for Fully Qualified Domain Name. An example of an FQDN is dma.example.com. Network Time Protocol Server (NTP) The NTP server sets the time and date settings for the Services Portal. Nginx An HTTP server used to render static content and delegate requests to Apache Tomcat. Services Portal The back end of CloudAXIS for scheduling meetings, adding users, and adding contacts. It is referred to in the user interface as the WSP (Web Services Portal). Virtual Edition Designates that a CloudAXIS Suite component is a software-based virtual machine. Virtual meeting room (VMR) A virtual meeting space that users and endpoints can join to participate in a multiparty videoconference. VMRs are identified and addressed by numeric IDs. A VMR may be personal or temporary. A personal VMR (also known as a persistent VMR) remains in existence indefinitely and can be used for different individual meeting events over time. A temporary VMR is created for a specific meeting or time period and is deleted once the meeting or time period has ended. See also the Polycom DMA 7000 System Operations Guide on the Polycom Support site. VMR prefix Specifying a VMR prefix value allows the Services Portal and the Experience Portal to know where to direct requests concerning a particular VMR ID. For example, if DMA-1 had the dialing prefix specified as 1, and DMA-2 had no dialing prefix specified, all portal requests concerning VMRs with ID 1xxxx would be directed to DMA-1, and requests concerning any other VMR ID would be directed to DMA-2. Polycom, Inc. Internal Use 6

7 Information Elements This guide may include any of the following icons to alert you to important information. Icons Used in this Guide Name Icon Description Note The Note icon highlights information of interest or important information needed to be successful in accomplishing a procedure or to understand a concept. User Tip Administrator Tip The User Tip icon highlights helpful information for efficient use of the software product. The Administrator Tip icon highlights techniques, shortcuts, or productivity related tips. Caution Warning Web Info The Caution icon highlights information you need to know to avoid a hazard that could potentially impact device performance, application functionality, or successful feature configuration. The Warning icon highlights an action you must perform (or avoid) to prevent issues that may cause you to lose information or your configuration setup, and/or affect system performance. The Web Info icon highlights supplementary information available online such as documents or downloads on support.polycom.com or other locations. Timesaver The Timesaver icon highlights a faster or alternative method for accomplishing a method or operation. Power Tip The Power Tip icon highlights faster, alternative procedures for advanced administrators already familiar with the techniques being discussed. Troubleshooting The Troubleshooting icon highlights information that may help you solve a relevant problem or refer you to other relevant troubleshooting resources. Settings The Settings icon highlights settings you may need to choose for a specific behavior, to enable a specific feature, or to access customization options. Typographic Conventions The following listed typographic conventions are used in this guide to distinguish different types of in-text styles and font information. Polycom, Inc. 7

8 Typographic Conventions Convention Bold Italics Blue Text Courier Description Used to highlight user interface items, such as menu tabs, soft keys, field names, and directories. Also used to represent menu selections in the interface. Used to emphasize text, to show example values or inputs, to indicate screens, and to show titles of reference documents available from the Polycom Support website and other reference sites. Used for hyperlinks to other sections within this document and to external websites and documents. Used for code fragments and parameter names. What s in this Guide? This administrators guide is organized into six sections and five appendices. The first section, Get Started, introduces the Polycom RealPresence CloudAXIS Suite s Services Portal and Experience Portal. The sections that follow show you how to configure and deploy these portals and create and manage your user accounts. The end sections provide information on third-party apps and software and template settings. Get Started This section gives you a brief overview of the Services Portal and Experience Portal, deployment prerequisites, and setup worksheets to assist you with configuring the Services Portal and Experience Portal. Deploy and Configure the Portals This section shows you how to deploy and configure the Services Portal and the Experience Portal. Create and Manage User Accounts This section shows you how to create, edit, and delete Active Directory and local user accounts. Provide Secure Guest Access This section gives you suggestions for enabling secure access to users located outside of your organization s firewall. Troubleshoot the Services Portal This section gives you troubleshooting procedures to resolve common portal errors and situations. Get Help This section provides information on where to access CloudAXIS Suite product information on the Polycom website. Create a Google Talk App This section shows you how to create a Google Talk app to enable access to those contacts from the Experience Portal. Create a Facebook App This section shows you how to create a Facebook app to enable access to those contacts from the Experience Portal. DMA Factory Conference Settings Impact This section uses a table to show you how Distributed Media Application (DMA) factory conference template settings impact CloudAXIS web client behavior. Restricted Shell This section provides you with the information to log in to CloudAXIS products from either a console or via an SSH connection and perform various shell operations. Polycom, Inc. 8

9 Third-Party Software This section gives you the license details for third-party software mentioned in this guide. Polycom, Inc. 9

10 2: Get Started The CloudAXIS Suite extends and enhances the Polycom RealPresence Platform by providing access to a shared meeting and collaboration experience that can include users from the hosting business and guests from outside the business. The key components of the suite are two virtualized server components deployed by the business: the Services Portal and the Experience Portal. The Services Portal enables users to create and participate in online video conference meetings. Users create meetings by logging into the Services Portal, selecting the type of meeting they want to create, setting the meeting parameters, and entering a list of participants to invite. The Services Portal also provides administrative capabilities for creating and managing users and for configuring the components that enable the online video conference meetings. The Experience Portal provides the meeting interface that enables users to interact with features such as content sharing, group chat, and privacy settings. This guide shows you how to deploy and configure the Services Portal and Experience Portal packages and create and manage user accounts. This section gives you an overview of the RealPresence Platform, lists the deployment requirements for the Services Portal and the Experience Portal, and provides worksheets to complete before you start the deployment and configuration. When you are ready to deploy and configure the Services Portal, see Deploy and Configure the Portals. This section is organized as follows: Understand the RealPresence Platform Understand the Minimum Requirements Understand Port Usage Complete the Setup Worksheets Get Help and Support Resources Web Info: An Online Version of this Document is Available Note that if you are reading this document in PDF format, an online version is available on the Polycom TechNet website at Understand the RealPresence Platform The Polycom RealPresence Platform is a product suite used to enable and enhance standards-based videoconference collaboration between hardware and software endpoints from Polycom and other optional vendors. This implementation may include one or more of the components listed in the following table. Polycom, Inc. Internal Use 10

11 RealPresence Platform Components Required or Optional Polycom Platform Component Purpose Required Required RealPresence Distributed Media Application, Virtual Edition RealPresence Collaboration Server, Virtual Edition Signaling, call control, and bridge virtualization MCU for hosting conferences Optional RealPresence Resource Manager Provisioning and managing endpoints Optional RealPresence Access Director solution* Firewall traversal Optional RSS recording and streaming server Media recording *An Acme Packet Net-Net Enterprise Session Director may also be used to secure firewall traversal. Note: HTTPS Tunneling RealPresence Access Director 3.1 is required to enable HTTPS Tunneling functionality. The Services and Experience Portals interoperate with the RealPresence platform components (see the accompanying figure) along with the following standard IT infrastructure elements that the deploying organization should provide: Dynamic Host Configuration Protocol (DHCP) server Allows portals to obtain IP addresses. Domain Name System (DNS) server Allows the portals and other RealPresence Platform components to be found and referenced using domain names rather than IP addresses. Lightweight Directory Access Protocol (LDAP) server Allows the portals to be integrated with an LDAP-compatible directory (for example, a Microsoft Active Directory server) to facilitate user management and authentication. Simple Mail Transport Protocol (SMTP) server Enables sending meeting invitations and other user notifications, including login information and password reset/updates, via . HTTP Reverse Proxy Server Provides web clients with access to the CloudAXIS portals from outside the organizational firewall. For more information, see Secure Web Access. The accompanying diagram shows the components required for the Services and Experience Portals in the Real Presence platform. The diagram is color-coded as follows: CloudAXIS components Identified by light blue. Third-Party components Identified by orange. RealPresence components Identified by bright red. Endpoints Identified by dark red. Polycom, Inc. 11

12 Polycom RealPresence platform components The RealPresence Platform components work with the CloudAXIS Suite to enable users to create and participate in video conference meetings accessed from a web browser or other hardware and software video endpoints, including mobile devices running the Polycom RealPresence Mobile application. The meetings are scheduled in the Services Portal and joined via the Experience Portal. The Services Portal and Experience Portal run on one or more VMware ESXi 5.x hosts. Scheduling a meeting in the Services Portal requires user or admin account access (see Understand Account Roles). Participating in meetings, however, requires access only to the Experience Portal via a URL link sent in an or instant message and a downloaded plug-in. Users may be added to the Services Portal locally or through integration with an enterprise Lightweight Directory Access Protocol (LDAP) server. If LDAP integration is configured, enterprise users may use their network credentials to access and host meetings on the Services Portal and to log into the Experience Portal. To create a scheduled meeting, users log in to the Services Portal, select the Schedule option, choose their meeting options, list the participants they want to invite, and then click on the Schedule button. The Services Portal then contacts the DMA system to create a virtual meeting room (VMR) on an MCU for all participants to join and sends out notifications to each invited participant via the configured SMTP server. The invitation contains a URL but can also contain information for Session Initiation Protocol (SIP), H.323, and ISDN access. When the meeting takes place, the DMA system validates the VMR and routes the call to the destination RealPresence Collaboration Server. When a user creates a meeting that starts immediately (ad hoc), the user s Experience Portal launches and enables the user to begin inviting participants. The participants may be invited from an aggregated list of the meeting creator s Facebook or Google Talk contacts. Accessing Facebook or Google Talk contacts requires that the Services Portal administrator has enabled and provisioned app-user credentials on the relevant service. A user may then download and install a social plug-in to enable social integration by performing the following: Google Talk Log into Google Talk service via the Experience Portal. Polycom, Inc. 12

13 Facebook Log into Facebook service via the Experience Portal. All the meeting creator s contacts that are currently online populate the contacts list in the Experience Portal. When a contact is selected, a URL is sent to the contact on that particular social IM service. The invited participants click the URL or paste it in to their browser to gain access to the meeting. If a Polycom RSS server has been configured for the environment hosting the meeting, the creator of the meeting may select the record meeting option, which records all aspects of the meeting including all video streams, audio streams, and shared content. The Services Portal and the Experience Portal are each packaged in an.ova file that must be deployed on VMware ESXi hosts using vsphere tools (for example, VMware vcenter using the vsphere client). Before deployment, be sure all minimum requirements are met, as outlined in the next section. Understand the Minimum Requirements Before deploying the Services Portal and the Experience Portal, you must complete the setup worksheets and meet the requirements outlined in the Minimum Requirements table that follows. To complete the worksheets, see Complete the Setup Worksheets. Minimum Requirements Component RealPresence Platform Web browsers.ova One or more ESXi hosts VMware vsphere vcenter controller Dynamic Host Configuration Protocol (DHCP) Description Functioning RealPresence Platform with DMA and sufficient MCU capacity to meet your requirements. For more information, see Understand the RealPresence Platform. The following web browsers are supported: Microsoft Internet Explorer v8.0 or higher Mozilla Firefox v14.0 or higher Google Chrome v11.0 or higher Apple Safari v5.0.6 or higher Latest Experience Portal.OVA file, downloaded to your local machine from the Polycom support site. Latest Services Portal.OVA file, downloaded to your local machine from the Polycom support site. Must be version 5.0 or higher and support 64-bit VM installations. Using a vsphere client, you must be able to access and administer VMware ESXi hosts either directly or via a vcenter host controller. (Optional) A component of VMware s cloud computing virtualization operating system. Allows the portals to obtain their IP addresses. Polycom, Inc. 13

14 Component LDAP Server SMTP Server Edge Proxy HTTP Reverse Proxy End User License Agreement (EULA) Description (Optional) Enables Enterprise user s authentication using their network credentials. Note that currently the Services Portal supports integration only with a Microsoft Active Directory. This feature also enables administrators to import Enterprise LDAP server users. The administrator can edit the imported user s role or set the user status as inactive. For information on user roles, see Understand Account Roles. For information on changing imported user accounts, see Edit Accounts Created from the Active Directory. Enables the Services Portal to deliver meeting invites and other notifications such as user onboarding. If providing access to external guests via a firewall, a functioning firewall/network Address Translation (NAT) traversal element such as RealPresence Access Director or Acme Packet Net-Net Enterprise Session Director is required (see Understand the RealPresence Platform). This element should be provisioned to allow SIP guest access (required) and H.323 access (optional) to your DMA and MCUs. If providing access to external guests via a firewall, an HTTP reverse proxy or a NAT server is required. This element should be provisioned to allow HTTPS and web socket access to the Experience Portal and (if desired) HTTPS access to the Services Portal. For more information, see Secure Web Access. RPAD 3.0 or higher can also be configured as Reverse Proxy for the Experience Portal. RPAD 3.1 or higher can also be configured as Reverse Proxy for both the Experience Portal and Service Portal. Access the EULA for your product at Minimum Server Requirements The Services Portal and Experience Portal in the Polycom RealPresence CloudAXIS Suite are deployed as two virtual machine instances (one for the Services Portal and one for the Experience Portal). Each instance must meet the requirements in the following table. Server Components per VM Instance Component CPU Virtual cores Description Each instance must be hosted on a physical CPU with the following clockspeed characteristics: >=2.0 GHz (Intel Xeon E5 Series or better CPU) >=2.5 GHz (Intel Xeon 5500 Series or better CPU) Support 64-bit installations Each instance must have 4 virtual cores. Polycom, Inc. 14

15 Component RAM Accessible storage Description 4 GB 100 GB Understand Port Usage This section describes the ports used to ensure successful network traversal for the Services Portal. Inbound and outbound port usage depends on the communications protocol and the specific port being used See the following graphic for an example of port usage in a sample CloudAXIS network. Port usage in the CloudAXIS Services Portal The following table shows the inbound and outbound ports used in the CloudAXIS Services Portal. Port Usage Inbound and Outbound Protocol/Function Communication Inbound Ports HTTP/HTTPS From web clients to the Services and Experience Portals TCP 443. Port 80 is also enabled, but it redirects to 443. Provides web browser access to the User Interface (UI) and REST APIs. Polycom, Inc. 15

16 Protocol/Function Communication Inbound Ports HTTPS (Tunneling) SMTP LDAP XMPP (Extensible Messaging and Presence Protocol) SIP (Session Initiation Protocol) RTP/RTCP/SRTP/SRTCP (Real-time Transport Protocol/Real-time Control Protocol/Secure Real-time Transport Protocol/Secure Realtime Control Protocol) BFCP (Binary Floor Control Protocol) From web clients to RealPresence Access Director Between the Services Portal and the organization s SMTP server Between the Services Portal and the organization s LDAP server Between web clients and external social media services Between client endpoints and DMA or the intermediate Edge Proxy (RealPresence Access Director [RPAD] or Acme) Between client endpoints and the MCU or the intermediate Edge Proxy (RPAD or Acme) Between client endpoints and the MCU or the intermediate Edge Proxy (RPAD or Acme) TCP 443. Port 80 is also enabled, but it redirects to 443. Media is communicated through RealPresence Access Director. TCP 25 for non-secure (SMTP). TCP 587/465 for secure (SMTP-S). TCP 389 for non-secure (LDAP). TCP 636 for secure (LDAP-S). TCP The CloudAXIS Social Plug-in running on a host-user's PC uses this port to communicate with Google Talk and Facebook services to get contact presence information and deliver instant message invites (UDP/TCP) /5061 (TLS). 443 (TCP) for HTTPS Tunneling. SIP is the signaling protocol used by the CloudAXIS web client, RealPresence Mobile, and other SIP endpoints. CloudAXIS web client: UDP ports TCP port for HTTPS Tunneling. For the RTP/RTCP/SRTP/SRTCP port range used by other Polycom and third-party products, see the appropriate product documentation. RTP and SRTP are used to carry visual and audio media between web-based clients and the RMX. RTCP and SRTCP provide out-ofband statistics and control information for an associated RTP or SRTP flow (UDP/TCP) BFCP is the signaling protocol used by SIP clients to negotiate content sharing. Polycom, Inc. 16

17 Complete the Setup Worksheets Before you begin the Services Portal deployment, complete the fields in the My System Values column of each of the Setup Worksheets that follow. As you progress through the configuration, use the information in these worksheets as a reference. Setup Worksheet for the LDAP Server Configuration LDAP Options My System Values Description Server Secure Port Base DN Username Password Enter the FQDN or IP address of the LDAP server. Select to establish a secure connection to the LDAP server. Note: If Secure is selected, upload the trust certificate of the LDAP server in the Services Portal. See Upload Certificates or Certificate Chain. Enter the port number to connect to the LDAP server. Here are typical values: 389 for non-secure (LDAP) 636 for secure (LDAP-S) Specify the distinguished name (DN) of a subset of the Active Directory hierarchy. This determines the set of users that are able to schedule meetings via the Services Portal. Enter the LDAP service account user ID. Enter the login password for the service account user ID. Setup Worksheet for the SMTP Server Configuration Server Settings My System Values Description Server Secure Port Login ID Enter the FQDN or IP address of the SMTP server. Select to establish a secure connection to the SMTP server. After deployment, enter the port to use to connect to the SMTP server. Here are typical values: 25 for non-secure (SMTP) 587/465 for secure (SMTP-S) After deployment, enter the SMTP service account user ID. Polycom, Inc. 17

18 Server Settings My System Values Description Password Sender Mail ID Enter the login password for the service account user ID. Enter the ID to be used as the return address for notifications sent by the Services Portal. This will typically be configured as a null or no reply address. Setup Worksheet for the Server Settings SMTP Options My System Values Description MEA Server Enter the URL, including the FQDN assigned to the IP address of the Experience Portal. See Access the Experience Portal. This information is used in constructing the meeting links. Make sure that this domain name is accessible to all users of the solution, including any that may be located outside of the organization. WSP Server Enter the URL including the FQDN assigned to the IP address of the Services Portal. See Access the Services Portal. This domain name is used in constructing the login link to Services Portal. Make sure that this domain name is accessible to all users who will access the Services Portal. Setup Worksheet for the DMA Configuration System Configuration Information Name Host Port My System Values Description Enter a nickname to assign to the DMA system to distinguish it in the Services Portal configuration. Enter the FQDN or IP address of an individual DMA or the FQDN of the supercluster s virtual address if the DMA is part of a supercluster. Enter the TCP port number to use when communicating with the DMA system. Typically, you will specify port 8443 (corresponding to the HTTPS REST [representational state transfer] API for the DMA system). Polycom, Inc. 18

19 System Configuration Information VMR Prefix Default Admin Admin Password Owner Domain Common SIP Username Common SIP Password My System Values Description Enter the VMR prefix that corresponds to this DMA system. This is optional and for use in environments where dialing plans are used to assign different VMR IDs to be handled by a peered set of DMA systems. Specifying this value allows the portals to know where to direct API requests concerning a particular VMR ID. For example, if DMA-1 had the dialing prefix specified as 1 and DMA-2 had no dialing prefix specified, all portal requests for VMRs with ID 1xxxx would be directed to DMA-1 and requests concerning any other VMR ID would be directed to DMA-2. Note that the VMR prefix must match what is on the DMA. To set up this value, see the Polycom DMA 7000 System Operations Guide on the Polycom Support site. Enter a user account name with an administrative role that exists on the DMA system. Note that if the DMA system is configured to have multiple domains, make sure that the admin user account has access to all the domains and hence can search the VMRs of all users. This typically requires a domain account rather than a local DMA account. See the Polycom DMA 7000 System Operations Guide for more detail on adding MCU pool orders. Enter the password value defined on the DMA system for the Default Admin account. Enter the domain of the user account assigned for creating meetings in the DMA system. For local domains, enter LOCAL. (Optional) Enter a username to use to authenticate SIP sessions for users who have authenticated with the Services Portal. (Optional) Enter a password to use in conjunction with the Common SIP Username to authenticate SIP sessions for users who have authenticated with the Services Portal. Polycom, Inc. 19

20 System Configuration Information Owner Username Generate VMR From Range My System Values Description Enter the username assigned for creating meetings in the DMA system. The username must match the name of a user account defined on the DMA system. The user does not need to be an administrator. For information on how to create a username for the DMA system, see the Polycom DMA 7000 System Operations Guide on the Polycom Support site. This is a check box option. Selecting this box displays two text boxes for entering a range. This option is used by admins to allow the Service Portal to generate VMR IDs on the DMA randomly within a specified range. This allows admins to separate the temporary VMRs created specifically for CloudAXIS meetings from other VMRs on same DMA. Note that the range must be all positive numbers with a 10-digit maximum. The first text box is for the lowest number of the range and the second text box is for the highest. For example, if entering a range of 123 to 1234, the Services Portal will generate VMRs between 123 and Setup Worksheet for the DMA Server Access Point Configuration System Configuration Information Location My System Values Description Enter the location name assigned in the Services Portal to identify a particular access point available for dialing. A single location may have multiple transport protocols configured for it. Note that an access point is a network location that is routed directly or indirectly to the DMA from where clients or endpoints can connect to participate in a conference. Polycom, Inc. 20

21 System Configuration Information Transport My System Values Description Select the transport protocol associated with the location and dialstring. Select from SIP, H.323, TUNNEL, ISDN, and PSTN. For information on provisioning endpoints for SIP, see the Polycom RealPresence Resource Manager Operations Guide. For information on enabling SIP calls for mobile apps, see the help files on the Polycom RealPresence Mobile support page. Note: It is mandatory that the Experience Portal have at least one SIP AP configured. Dialstring Dialstrings (SIP URI, Tunnel URI, H.323 E.164 enum, PSTN phone number) are used by a video or audio endpoint to join a conference hosted by the DMA. Typically for SIP, TUNNEL, and H.323 callers, this string includes the address or domain name (preferred) of the edge traversal device (RPAD or Acme) provisioned to allow external access to this DMA. Auth Mode Dial Prefix Options for this drop-down box include AUTH, NoAUTH, and SHARED. For an access point that may be used by endpoints without access to SIP credentials, select NoAUTH. For an access point that should be used by endpoints that have access to SIP credentials (e.g., authenticated web and RPM client users when the DMA settings have been configured with the Common SIP Username and Password as described), select AUTH. For an access point that may be used by either class of endpoints, select SHARED. Use this optional field to specify a prefix to prepend to dialing information used when dialing this access point. This prefix can be used by the access point to route the call or to distinguish between callers who are able to authenticate themselves from those that require unauthenticated guest access. Polycom, Inc. 21

22 Setup Worksheet for the Date Time Configuration System Configuration Information NTP Server My System Values Description Enter the Network Time Protocol server FQDN or IP address. The Services Portal synchronizes time and date settings from this server. Entering the NTP will automatically populate the Date and Time fields. Note that the portals are configured to the UTC time zone, and this is not configurable. Get Help and Support Resources This administrators guide includes a Get Help section where you can find links to Polycom product and support sites and partner sites. You can also find information about The Polycom Community, which provides access to discussion forums you can use to discuss hardware, software, and partner solution topics with your colleagues. To register with the Polycom Community, you will need to create a Polycom online account. The Polycom Community includes access to Polycom support personnel, as well as user-generated hardware, software, and partner solutions topics. You can view top blog posts and participate in threads on any number of recent topics. Polycom, Inc. 22

23 3: Deploy and Configure the Portals The Services Portal and Experience Portal require deployment on a VMware EXSi host using a vsphere Client administrative GUI. Our recommendation is to deploy the Services Portal first and the Experience Portal second. Once they are both deployed, log in to the Services Portal with the default super admin credentials and configure the server settings then complete the Experience Portal configurations. When the configurations are complete, the Services Portal is ready for adding and managing users. Once users receive access, they can use the Services Portal to create meetings, add contacts, and use the Experience Portal to enable conference interaction. Information on accessing and using the Services Portal is found in the RealPresence CloudAXIS Suite User Guide. This section shows you how to deploy and configure the Services Portal. Before you begin, confirm all prerequisites and complete the Setup Worksheets provided, see the steps for deploying and configuring the Services Portal and the Experience Portal in the following subsections of this section. Deploy the Services Portal and Experience Portal Packages Access the Services Portal Access the Experience Portal Configure the Services Portal Configure the Experience Portal Note: Activate the Trial License Your 30-day trial of the service and licenses can be activated at any time during the trial. To activate the license, see Activate the Services Portal License. Deploy the Services Portal and Experience Portal Packages Before you begin, confirm that you meet the prerequisites listed in Get Started, and then deploy the Services Portal and Experience Portal.OVA files to your VMware vsphere EXSi hosts. Note that when the portal instances boot up, they will each attempt to obtain an IP address via DHCP. The instance IP address and the MAC address can be determined by accessing the instance information using the vsphere client. Polycom recommends that the instance IP assignments be made permanent by modifying your DHCP server s configuration to map the current IP address or another preferred address of your choosing to the respective instance MAC address. Then, reboot the instance if necessary to enable it to obtain a new address. We also recommend that you modify your DNS server settings to assign a domain name to each instance based on the permanent IP address you have selected. Polycom, Inc. Internal Use 23

24 Note: Order of Deployment The packages may be deployed, accessed, and configured in any logical relative order. The order described in this document, however, is recommended for those unfamiliar with the overall process. If DHCP is not available in your environment, each portal instance s IP address and networking settings may alternatively be configured via the portal s console. To configure the portal packages: 1 Using the vsphere console, access the portal console. 2 Log in using caxis for both your username and password. 3 Enter the following command to view the current network settings: show_network_info. 4 Enter the following command to modify the current network settings: change_network_settings. See more information on this DHCP issue at Use Case - Configuring Static IP Address in a system where DHCP is in a Disabled state. Note: Activate the Trial License Your 30-day trial of the service and licenses can be activated any time during the trial. To activate the license, see Activate the Services Portal License. Use of Experience Portal Cookies The Experience Portal uses the following cookies: ManualLogin This session cookie is a Boolean value used by the Experience Portal to determine if a login session was initiated by a user login or by an application integration or single signon. DisplayName This cookie is the name entered by a user when joining a meeting as an anonymous user, if the Remember Me function is enabled and the user checked the box during login. This cookie lasts for 14 days. Address This cookie is the address entered by a user when joining a meeting as an anonymous user, if the Remember Me function is enabled and the user checked the box during login. This cookie lasts for 14 days. Tags This cookie is reserved for future use. SSOData This cookie is a base64 encoded blob containing a session token and a username used to permit an enterprise user to re-login if the feature is enabled and the user checked the box at login. This cookie lasts for 14 days. Note that the session token itself will expire independently as dictated by the rules of the system that issued it. Polycom, Inc. 24

25 Use of Services Portal Cookies The Services Portal uses the following cookies: WSP Application This utilizes the usertoken=0b8a4f41-af5a d34-f583ab7b5d06; and loginuser=admin cookie for requesting secure Backend API calls. userrole=role_super_admin, ROLE_ADMIN, ROLE_USER Based on the user role, the Services Portal shows different customized user interfaces. For example, only an Admin can see admin related settings and other details. i18next en-us i18next library sets this cookie to handle Internalization for WSP portal. Access the Services Portal Access to the Services Portal is essential for scheduling meetings and for adding users and contacts. Before you configure the Services Portal for use, however, you will need to obtain an FQDN and enter it into your browser s address bar. To set up and access the Services Portal: 1 Obtain the Services Portal FQDN provisioned via your DNS server. (Enter the Services Portal FQDN you noted in the Setup Worksheet for the Server Settings.) 2 Open a browser and enter the FQDN in the address bar to open the Services Portal login screen. You are now ready to configure the Services Portal for use 3 For the first Services Portal login, enter admin for both your Username and Password 4 Accept the End User License Agreement (EULA). Until you accept the EULA, you won t be able to take further action. 5 After you accept the EULA, change the password for greater security. For information on changing passwords, see Change Your Password. Note: Services Portal Configuration An FQDN is required when configuring the Services Portal. Enter the Services Portal FQDN you noted in the Setup Worksheet for the Server Settings. Check an Unresponsive Portal URL (FQDN) If the Services Portal URL does not respond, open the Services Portal login screen and confirm that the nginx server, the Apache server, or all servers are running. To check either the nginx, Apache, or all servers: 1 Using the vsphere console or by connecting via an SSH client to the Services Portal FQDN, access the Services Portal console. 2 Log in using caxis for both your username and password. Polycom, Inc. 25

26 3 Get the status: Enter the following to get the nginx status: service nginx status Enter the following to get the Apache status: services tomcat6 status Enter the following to get the status on all servers: service status-all 4 Start servers if they are not running, and restart them if they are running but you are still having problems with the link: Startup servers: services <SomeServer> start Restart servers: services <SomeServer> restart Access the Experience Portal Access to the Experience Portal is essential as this portal provides the meeting interface, enabling users to interact with such features as content sharing, group chat, and privacy settings. Note: Experience Portal Configuration The FQDN is required when you configure the Experience Portal. Enter the Experience Portal FQDN you entered in the Setup Worksheet for the Server Settings. To access the Experience Portal administrative and provisioning interface: 1 Obtain the Experience Portal FQDN provisioned via your DNS server. 2 Open either a Chrome or Firefox browser, and enter the FQDN in the address bar. Because you must specify that the connection must be made to port 9445, the full URL of the server would be FQDN>:9445.The Experience Portal Login dialog will display. 3 Type admin for both the Username and Password, and click Login. 4 A second Login screen appears, asking that you immediately change from the default settings to a new, more secure and personalized multi-character username and password. Type in new values for Username and Password, and retype the password as indicated. 5 Click Save. The Experience Portal interface will display. Note: Experience Portal Access Configuration To access the Experience Portal directly as an end user, enter the URL in the format FQDN>. No additional port number is needed. Configure the Services Portal The Services Portal supports three types of accounts: super admin, admin, and user. Each account type provides a different level of access. Only super admin accounts have access to the Services Portal Polycom, Inc. 26

27 Settings and Platform Settings screens, and you must log in as a super admin to configure and update the Services Portal settings. For information on the account roles, see Understand Account Roles. If you are configuring the system for the first time, you will need to enable a few functionalities. To enable functionalities for first-time configurations: 1 Log in to the default super admin account. 2 In the Services Portal Settings screen, enter the LDAP, SMTP, core settings, and DMA system information. This information enables user management and video conference meeting creation and management functionalities. This section shows you the steps for configuring the Service Portal. Before you begin, you must deploy the Services Portal and Experience Portal packages as described in Deploy the Services Portal and Experience Portal Packages. Perform the first-time configuration steps in the following order: Log In as the Super Admin Synchronize Portal Timing Configure the Connection to the LDAP Server Configure the Connection to the SMTP Server Configure Additional Server Settings Configure Social Policies Configure the Connection to the DMA System and RPAD Servers Localize the Services Portal View and Customize the Templates Set the Date and Time Manage Certificates Select and Download Log Levels Log In as the Super Admin You must log in as a super admin to configure or update the Services Portal settings. The super admin account has special access to the Settings and Platform Settings tabs that display next. Super admin tabs Polycom, Inc. 27

28 For first-time configurations, log in with the default super admin credentials (Username/Password: admin/admin), and then immediately change the password for security reasons. Super admins can also reset passwords for local users. For information on changing passwords, see Change Your Password. For information on resetting passwords, see Reset a Password. Admin Tip: Creating Additional Super Admins When the Services Portal is launched for the first time, we recommend that you create another super admin account after the configuration is completed. See Create Accounts for more information. Login with the new super admin credentials, and delete the default super admin account for secure access. Synchronize Portal Timing Both the Services Portal and the Experience Portal must be configured to the same time zone and NTP server in order for CloudAXIS Recording to work properly. Note: NTP Date and Time Zone Verification Check that the NTP date and time zone of your EXSi host matches the Services and Experience Portals time. The default time of Instances is taken from EXSi, and if that is wrong, the Services Portal scheduler can go out of sync. The Services Portal time should also match the DMA. To configure the same time zone and NTP server: 1 Access the Command Line Interface (CLI) (see CloudAXIS Restricted Shell) on either of the two portals. Type caxis for both your Username and Password. 2 Select your time zone by using the CLI command change_timezone. For details on how to use the CLI command, see Use Case - Set System Date Time in Appendix D. 3 Sync your server with the NTP server by using the CLI command ntpdate. See Use Case - Quick Sync System date-time with a Specific NTP server for details. 4 Repeat steps 1 3 on the other portal. Configure the Connection to the LDAP Server The LDAP server enables the Services Portal to import external user accounts from an enterprise, edit external user account default roles, set external user accounts as active or inactive, and authenticate user logins. This section shows you how to configure connection to the LDAP server. You must log in as a super admin before configuring this connection. For more information, see Log In as the Super Admin. Polycom, Inc. 28