Embed Size (px)
Citation preview
Polycom, Inc. 1
ADMINISTRATORS’ GUIDE
RealPresence® CloudAXIS™ Suite
Software 1.3.0 | July 2013 | 3725-03273-002 Rev A
Polycom, Inc. 2
Copyright ©2013, 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.
6001 America Center Drive San Jose, CA 95002 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 email at [email protected].
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. Email your opinions and comments to [email protected].
Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.
Polycom, Inc. 3
Contents
About This Guide ...................................................................................................... 6
Conventions Used in this Guide ..................................................................................................... 6 Terms and Writing Conventions ..................................................................................................... 6 Information Elements ....................................................................................................................... 7 Typographic Conventions ............................................................................................................... 8 What’s in this Guide? ....................................................................................................................... 8
Getting Started .................................................................................................... 10 1:
Understanding the RealPresence Platform.................................................................................. 10 Understanding Minimum Requirements ...................................................................................... 13
Minimum Server Requirements ..................................................................................................... 14 Learning Port Usage ....................................................................................................................... 15 Completing Setup Worksheets ..................................................................................................... 17 Getting Help and Support Resources ........................................................................................... 23
Deploying and Configuring the Portals ............................................................ 24 2:
Deploying the Services Portal and Experience Portal Packages .............................................. 24 Accessing the Services Portal ...................................................................................................... 25 Accessing the Experience Portal .................................................................................................. 26 Configuring the Services Portal .................................................................................................... 26
Logging In as the Super Admin ...................................................................................................... 27 Synchronizing Portal Timing .......................................................................................................... 27 Configuring the Connection to the LDAP Server ........................................................................... 28 Configuring the Connection to the SMTP Server ........................................................................... 29 Configuring Additional Server Settings .......................................................................................... 30 Configuring Social Policies ............................................................................................................ 31 Configuring the Connection to the DMA System and RPAD Servers ............................................ 34 Localizing the Services Portal ........................................................................................................ 40 Setting Date and Time ................................................................................................................... 41 Managing Certificates .................................................................................................................... 42 Selecting and Downloading Log Levels ......................................................................................... 46 Updating Services Portal Software ................................................................................................ 48 Activating Licenses ........................................................................................................................ 53 Configuring Proxy Settings ............................................................................................................ 58
Configuring the Experience Portal ............................................................................................... 60 Configuring the Server Settings ..................................................................................................... 61 Configuring the Environment General Settings ............................................................................. 63 Configuring the Meeting Hosts ....................................................................................................... 66 Configuring the Services Portal Connection Settings .................................................................... 70 Configuring the VMR Settings ........................................................................................................ 74 Configuring the Services Portal Authentication Provider Settings ................................................. 79 Configuring the DMA Settings ........................................................................................................ 81
Polycom, Inc. 4
Applying Experience Portal Configurations ................................................................................... 85 Setting System Administration UI Properties ................................................................................. 86 Updating Experience Portal Software ............................................................................................ 89 Exporting the Experience Portal Configuration File ....................................................................... 89 Importing the Experience Portal Configuration File ....................................................................... 90 Localizing the Experience Portal .................................................................................................... 91
Creating and Managing User Accounts ......................................................... 93 3:
Understanding Account Roles ...................................................................................................... 93 Creating Accounts .......................................................................................................................... 95
Adding Active Directory Users ....................................................................................................... 95 Adding Local Users ........................................................................................................................ 96
Editing Accounts ............................................................................................................................ 99 Editing Accounts Created from the Active Directory ...................................................................... 99 Editing Locally Created User Accounts ........................................................................................ 101
Deleting Accounts ........................................................................................................................ 103 Changing Your Password ............................................................................................................ 104 Resetting a Password .................................................................................................................. 105
Providing Secure Guest Access ...................................................................... 107 4:
Securing SIP Guest Access ......................................................................................................... 107 Enabling Guest Access on Your Edge Proxy .............................................................................. 107 Additional Recommendations for Greater Security ...................................................................... 107
Securing Web Access .................................................................................................................. 108
Troubleshooting the Services Portal .............................................................. 110 5:
User Cannot Create Meetings ..................................................................................................... 110 User Cannot Launch the Welcome Screen.................................................................................. 110 Configured Components are Not Responding ............................................................................. 110 Super Admins and Admins Cannot Add an Active Directory User .............................................. 111 User Cannot Send Email Notifications ......................................................................................... 111 User Receives “Unable to Create a Conference with a Personal VMR” Message ...................... 111 User Receives “External Server Not Set” Message ..................................................................... 111 User Receives “Video Resources Are Not Available” Message .................................................. 112 Obtaining Services Portal Log Files ............................................................................................. 112 User Cannot Download Logs on Internet Explorer ...................................................................... 112
Getting Help ...................................................................................................... 113 6:
Polycom and Partner Resources ................................................................................................ 113 The Polycom Community............................................................................................................. 113
A: Creating a Google Talk™ App ......................................................................... 114
B: Creating a Facebook App ................................................................................ 121
C: DMA Factory Conference Settings Impact ..................................................... 125
Polycom, Inc. 5
D: CloudAXIS Restricted Shell ............................................................................. 128
Introduction ................................................................................................................................... 128 Usage ............................................................................................................................................. 128
Use Case - Login as 'caxis' via Console or via a SSH Connection ............................................. 128 Use Case - Change System Hostname ....................................................................................... 129 Use Case - Log Collection ........................................................................................................... 129 Use Case - Copying the generated logs to a different server ...................................................... 130 Use Case - Access Log Files ....................................................................................................... 130 Use Case - Changing Password of the 'caxis' User .................................................................... 130 Use Case - Configure System NTP Settings ............................................................................... 131 Use Case - Quick Sync System date-time with a Specific NTP server ....................................... 131 Use Case - Show Product Version .............................................................................................. 131 Use Case - Regeneration of Certificates ..................................................................................... 132 Use Case - Change System Timezone ........................................................................................ 132 Use Case - Restarting Services ................................................................................................... 133 Use Case - Set System Date Time .............................................................................................. 133 Use Case - View System Network Information ............................................................................ 134 Use Case - System Network Configuration is already set to use DHCP ..................................... 134 Use Case - Enabling DHCP in a machine where DHCP is not enabled ...................................... 135 Use Case - Configuring Static IP Address in a System where DHCP is in an 'Enabled' state .... 135 Use Case - Configuring Static IP Address in a system where DHCP is in a 'Disabled' state ...... 137 Use Case - Configuring Static IP Address in a system where DHCP is in a 'Disabled' state with
the currently assigned IP address ................................................................................................ 139 Use Case - Attempting to configure manual DNS settings while DHCP is enabled in the system
..................................................................................................................................................... 141 Use Case - Using invalid Network values .................................................................................... 141 Use Case - Using an IP that is already assigned to some machine in the same network .......... 142 Use Case - Installation of PAP (Polycom Auxiliary Package) ...................................................... 143 Use Case - Forced Installation of PAP (Polycom Auxiliary Package) ......................................... 144 Use Case - Reboot System ......................................................................................................... 144 Use Case - Exit Restricted Shell .................................................................................................. 144 Use Case - Login Timeout: .......................................................................................................... 145
E: Third-Party Software ........................................................................................ 146
Polycom, Inc. 6
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 a few typographic conventions.
Familiarizing yourself with these tools will help you to successfully perform tasks.
Terms and Writing Conventions As you read this guide, you will notice the same terms and conventions are used repeatedly. Make sure
you 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 to run the Services Portal
application.
Experience Portal The meeting conference interface. Also referred to as MEA.
Services Portal The backend for scheduling meetings, adding users, and adding contacts. Also
referred to as WSP.
NGINX An HTTP Server used to render static content and delegate requests to Apache Tomcat.
FQDN Fully Qualified Domain Name. Example of an FQDN: dma.example.com
Network Time Protocol Server (NTP) The NTP server sets the time and date settings for the
Services Portal
VMR Virtual Meeting Rooms (VMR) A virtual meeting space that users and endpoints can join
to participate in a multi-party 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. Also see the Polycom DMA 7000 System Operations Guide on the Polycom
Support site.
VMR Prefix Specifying a VMR prefix value allows the Services Portal and 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. 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.
Administrator Tip
The Administrator Tip icon highlights techniques, shortcuts, or productivity
related tips.
Caution
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.
Warning
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 phone or network performance.
Web Info
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 to 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.
Polycom, Inc. 8
Typographic Conventions A few typographic conventions, listed next, are used in this guide to distinguish types of in-text
information.
Typographic Conventions
Convention Description
Bold Highlights interface items such as menus, soft keys, file names, and directories.
Also used to represent menu selections and text entry to the phone.
Italics Used to emphasize text, to show example values or inputs, and to show titles of
reference documents available from the Polycom Support Web site and other
reference sites.
Blue Text Used for cross references to other sections within this document and for hyperlinks
to external sites and documents.
Courier Used for code fragments and parameter names.
What’s in this Guide? This administrators’ guide is organized into five chapters and four appendices. The first chapter, Getting
Started, introduces Polycom RealPresence CloudAXIS Services Portal and Experience Portal. The
chapters that follow show you how to configure and deploy these portals and create and manage your
user accounts. The appendices provide you with information on third-party apps and software and
template settings.
Chapter 1: Getting Started This chapter 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.
Chapter 2: Deploying and Configuring the Portals This chapter shows you how to deploy and
configure the Services Portal and the Experience Portal.
Chapter 3: Creating and Managing User Accounts This chapter shows you how to create, edit, and
delete Active Directory and local user accounts.
Chapter 4: Providing Secure Guest Access This chapter gives you suggestions for enabling secure
access to users located outside of your organization’s firewall.
Chapter 5: Troubleshooting the Services Portal This chapter gives you troubleshooting procedures
to resolve common portal errors situations.
Appendix A: Creating a Google Talk™ App This appendix shows you how to create a Google Talk
app to enable access to those contacts from the Experience Portal.
Appendix B: Creating a Facebook App This appendix shows you how to create a Facebook app to
enable access to those contacts from the Experience Portal.
Appendix C: DMA Factory Conference Settings Impact This appendix uses a table to show you how
DMA factory conference template settings impact CloudAXIS web client behavior.
Polycom, Inc. 9
Appendix D: CloudAXIS Restricted Shell This appendix 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.
Appendix E: Third-Party Software This appendix gives you the license details for third-party software
mentioned in this guide.
Polycom, Inc. 10
Getting Started 1:
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,
enabling 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 chapter 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 starting the
deployment and configuration. When you are ready to deploy and configure the Services Portal, see
Deploying and Configuring the Portals.
This chapter is organized as follows:
Understanding the RealPresence Platform
Understanding Minimum Requirements
Learning Port Usage
Completing Setup Worksheets
Getting 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 http://support.polycom.com/PolycomService/home/home.htm.
Understanding 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 Table 1.
Polycom, Inc. 11
Table 1: RealPresence Platform Components
Required or Optional Polycom Platform Component Purpose
Required Polycom DMA Signaling, call control, and bridge
virtualization.
Required RealPresence Collaboration Server™ 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 alternately be used to secure firewall
traversal.
The Services and Experience Portals interoperate with the RealPresence Platform components along
with the following standard IT infrastructure elements that the deploying organization should provide:
Dynamic Host Configuration Protocol (DHCP) Server Allows the portals to obtain their 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 (e.g., 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
e-mail.
HTTP Reverse Proxy Server Provides web clients with secure access to the CloudAXIS portals
from outside the organizational firewall. For best results, a proxy server should be used that
supports the Web Sockets protocol (RFC 6455).
Use the host name selected (e.g., meet.contoso.com and schedule.contoso.com) where both DNS
records point to the same IP; the Reverse Proxy separates traffic based on the host.
Note: Diagram Legend
The components in the following diagram are specified as follows:
CloudAXIS Components Identified by light blue.
Third-Party Components Identified by orange.
RealPresence Components Identified by bright red.
End-Points Identified by dark red.
Polycom, Inc. 12
Figure 1: Polycom RealPresence Platform
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 Understanding Account Roles). Participating in
meetings, however, only requires access to the Experience Portal via a URL link sent in an email 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 email notifications to each invited participant via the configured SMTP
server. The invitation contains a URL, but can also contain information for 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, Google Talk™, and/or Skype™ contacts. Accessing Facebook or
Polycom, Inc. 13
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.
Facebook Log into Facebook service via the Experience Portal.
Skype™ Run the Skype software, log in to the Skype service via the Skype software, instruct the
Portal to integrate with the Skype session and allow that integration in the Skype client.
All of 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 which must be
deployed on VMware ESXi hosts using vSphere tools (e.g., VMware vCenter using the vSphere client).
Before deployment, be sure all minimum requirements are met as outlined in the next section.
Understanding Minimum Requirements Before deploying the Services Portal and the Experience Portal, you must complete the setup worksheets
and meet the requirements in Table 2. To complete the worksheets, see Completing Setup Worksheets.
Table 2: Minimum Requirements
Component Description
RealPresence Platform Functioning RealPresence Platform with DMA and sufficient MCU
capacity to meet your requirements. For more information, see
Understanding the RealPresence Platform.
Web Browsers The following web browsers are supported:
Microsoft Internet Explorer® v8.0 or higher
Mozilla Firefox® v11.0 or higher
Google Chrome™ v11.0 or higher
Apple Safari v5.0.6 or higher
.OVA 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.
One or more ESXi hosts 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.
Polycom, Inc. 14
Component Description
VMware vSphere vCenter
controller
Optional
Dynamic Host Configuration
Protocol (DHCP)
Allows the portals to obtain their IP addresses.
LDAP Server (Optional) Enables Enterprise user’s authentication using their
network credentials. Note that currently the Services Portal only
supports integration 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
Understanding Account Roles. For information on changing
imported user accounts, see Editing Accounts Created from the
Active Directory.
SMTP Server Enables the Services Portal to deliver email meeting invites and
other notifications such as user onboarding.
Edge Proxy If providing access to external guests, a functioning firewall/NAT
traversal element such as RealPresence Access Director or Acme
Packet Net-Net Enterprise Session Director is required (see
Understanding the RealPresence Platform). This element should be
provisioned to allow SIP guest access (required) and H.323 access
(optional) to your DMA and MCUs.
HTTP Reverse Proxy If providing access to external guests, a functioning HTTP reverse
proxy is required. This element should be provisioned to allow
HTTPS and web socket access to the Experience Portal and HTTPS
access to the Services Portal (optional).
End User License Agreement
(EULA)
Access the EULA for your product at
http://support.polycom.com/PolycomService/home/home.htm
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.
Polycom, Inc. 15
Table 3: Server Components per VM Instance
Component Description
CPU Each instance must be hosted on a physical CPU with the following
clock-speed 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
Virtual Cores Each instance must have 8 virtual cores.
RAM 8 GB
Accessible Storage 100 GB
Learning Port Usage This section lists the ports used to ensure successful network traversal for the Services Portal.
Figure 2: Port Usage Diagram
Polycom, Inc. 16
Table 4: Port Usage Inbound
Protocol/Function Communication Ports
HTTP/HTTPS From web clients to the Services
and Experience Portals.
TCP 443. 80 is also enabled but
redirects to 443.
Provides web browser access to
the User Interface (UI) and
REST APIs.
Table 5: Port Usage Outbound
Protocol/Function Communication Ports
SMTP Between the Services Portal and
the organization’s SMTP server TCP 25 for non-secure
(SMTP).
TCP 587/465 for secure
(SMTP-S).
LDAP Between the Services Portal and
the organization’s LDAP server. TCP 389 for non-secure
(LDAP).
TCP 636 for secure
(LDAP-S).
XMPP Between web clients and external
social media services. TCP 5222
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.
SIP Between client endpoints and DMA
or the intermediate Edge Proxy
(RPAD or Acme.)
5060 (UDP/TCP) /5061 (TLS)
SIP is the signaling protocol
used by the CloudAXIS Web
Client, RealPresence Mobile,
and other SIP endpoints.
Polycom, Inc. 17
Protocol/Function Communication Ports
RTP/RTCP/SRTP/SRTCP Between client endpoints and the
MCU or the intermediate Edge
Proxy (RPAD or Acme).
CloudAXIS Web Client: UDP
ports 3230 – 3237
For the
RTP/RTCP/SRTP/SRTCP port
range used by other Polycom
and third-party products, please
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-
of-band statistics and control
information for an associated
RTP or SRTP flow..
BFCP Between client endpoints and the
MCU or the intermediate Edge
Proxy (RPAD or Acme)
3238 (UDP/TCP)
BFCP is the signaling protocol
used by SIP clients to negotiate
content sharing.
Completing Setup Worksheets Before you begin the Services Portal deployment, complete the fields in the My System Values column of
each of the Setup Worksheets. As you progress through the configuration, use the information in these
worksheets as a reference.
Table 6: Setup Worksheet for the LDAP Server Configuration
LDAP Options My System Values Description
Server Enter the FQDN or IP address of the LDAP
Server.
Secure 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 Service
Portal. See Uploading Certificates or
Certificate Chain.
Polycom, Inc. 18
LDAP Options My System Values Description
Port Enter the port number to connect to the LDAP
Server. Typical values:
389 for non-secure (LDAP).
636 for secure (LDAP-S).
BaseDN 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.
Username Enter the LDAP service account user ID.
Password Enter the login password for the service
account user ID.
Table 7: Setup Worksheet for the SMTP Server Configuration
Server Settings My System Values Description
Server Enter the FQDN or IP address of the SMTP
Server.
Secure Select to establish a secure connection to the
SMTP Server.
Port After deployment, enter the port to use
connect to SMTP Server. Typical values:
25 for non-secure (SMTP).
587/465 for secure (SMTP-S).
Login Id After deployment, enter the SMTP service
account user ID.
Password Enter the login password for the service
account user ID.
Sender Mail Id Enter the email 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.
Polycom, Inc. 19
Table 8: Setup Worksheet for the Server Settings
SMTP Options My System Values Description
MEA Server https:// Enter the URL, including the FQDN assigned
to the IP address of the Experience Portal.
See Accessing 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 https:// Enter the UR,L including the FQDN assigned
to the IP address of the Services Portal. See
Accessing 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.
Table 9: Setup Worksheet for the DMA Configuration
System Configuration
Information
My System Values Description
Name Enter a ‘nickname’ to assign to the DMA
system to distinguish it in the Services Portal
configuration.
Host 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.
Port Enter the TCP port number to use when
communicating with the DMA system.
Typically, you will specify port 8443
(corresponding to the https REST API for the
DMA system).
Polycom, Inc. 20
System Configuration
Information
My System Values Description
VMR Prefix 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.
Default Admin 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.
Also note that the DMA system must have an
MCU Pool order named ‘Factory Pool Order’.
See the Polycom DMA 7000 System
Operations Guide for more detail on adding
MCU Pool orders.
Admin Password Enter the password value defined on the DMA
system for the Default Admin account.
Owner Domain Enter the domain of the user account
assigned for creating meetings in the DMA
system. For local domains, enter “LOCAL.”
Polycom, Inc. 21
System Configuration
Information
My System Values Description
Owner Username 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.
Generate VMR From
Range
This is a checkbox option. Selecting this box
displays two text boxes for entering a range.
This option is used by admins to allow the
Service Portal to randomly generate VMR IDs
on the DMA 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 1234.
Table 10: Setup Worksheet for the DMA Server Access Point Configuration
System Configuration
Information
My System Values Description
Location 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. 22
System Configuration
Information
My System Values Description
Transport Select the transport protocol associated with
the location and dialstring. Select from SIP,
H.323, 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, 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 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.
Table 11: Setup Worksheet for the Date Time Configuration
System Configuration
Information
My System Values Description
NTP Server 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.
Polycom, Inc. 23
Getting Help and Support Resources This administrators’ guide includes a Getting 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. 24
Deploying and Configuring the Portals 2:
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 chapter 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 sections of this chapter.
Deploying the Services Portal and Experience Portal Packages
Accessing the Services Portal
Accessing the Experience Portal
Configuring the Services Portal
Configuring the Experience Portal
Deploying the Services Portal and Experience
Portal Packages Before you begin, confirm that you meet the prerequisites listed in Getting 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.
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 do this:
1 Using the vSphere console, access the portal console
2 Login 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
Polycom, Inc. 25
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: 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.
Accessing the Services Portal Obtain the Services Portal FQDN provisioned via your DNS server, open a browser, and enter the FQDN
in the address bar. The Services Portal login screen will display, and you are now ready to configure the
Services Portal for use. For the first Services Portal login, enter ‘admin’ for both your Username and
Password, and accept the End User License Agreement (EULA). Until the EULA is accepted, no further
action can be taken.
After accepting the EULA, change the password for greater security. For information on changing
passwords, see Changing Your Password.
Note that you have a 30-day trial of the service and licenses can be activated any time during the trial. To
activate the license, see Activating the Services Portal License.
Troubleshooting: URL (FQDN) Does Not Respond
If the Services Portal URL does not respond, open the Services Portal login screen and confirm that the Nginx, Apache, or all servers are running as follows:
To check 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. 3 Get 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
Note: Configuration Note
An FQDN is required when configuring the Services Portal. Enter the Services Portal FQDN you noted in the Setup Worksheet for the Server Settings.
Polycom, Inc. 26
Accessing the Experience Portal To access the Experience Portal administrative and provisioning interface, obtain the Experience Portal
FQDN provisioned via your DNS server, open a browser, and enter the FQDN in the address bar. You
must specify that the connection be made to port 9445. Thus, the full URL of the server would be
https://<Server FQDN>:9445.
The Experience Portal login screen will display. Enter ‘admin’ for both your Username and Password, and
click LOGIN to access the Experience Portal.
Note: Configuration Note
The FQDN is required when configuring the Experience Portal. Enter the Experience Portal FQDN you entered in the Setup Worksheet for the Server Settings
Note: Configuration Note
To access the Experience Portal directly as an end-user, enter the URL https://<Server FQDN>. No additional port number is needed.
Configuring 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
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 Understanding Account Roles.
For first-time configurations, log in to the default super admin account and enter the LDAP, SMTP, core
settings, and DMA system information in the Services Portal Settings screen. 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 Deploying the Services Portal and
Experience Portal Packages.
Perform the first-time configuration steps in the following order:
1 Logging In as the Super Admin
2 Synchronizing Portal Timing
3 Configuring the Connection to the LDAP Server
4 Configuring the Connection to the SMTP Server
5 Configuring Additional Server Settings
6 Configuring Social Policies
7 Configuring the Connection to the DMA System and RPAD Servers
8 Configuring Conference Settings
Polycom, Inc. 27
9 Setting Date and Time
10 Managing Certificates
11 Selecting and Downloading Log Levels
Logging 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. For first-time
configurations, log in with the default super admin credentials (Username/Password: admin/admin), and
then change the password for security. Super admins can also reset passwords for local users. For
information on changing passwords, see Changing Your Password. For information on resetting
passwords, see Resetting a Password.
Figure 3: Super Admin Tabs
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 Creating Accounts for more information. Login with the new super admin credentials, and delete the default super admin account for secure access.
Synchronizing Portal Timing
Both the Services Portal and the Experience Portal MUST be configured to the SAME timezone and NTP
server in order for CloudAXIS Recording to work properly.
To configure the same time zone and NTP server
1. Access the CLI (See Appendix D: CloudAXIS Restricted Shell) on either of the two portals using
‘caxis’ for both your Username and Password.
2. Select your time zone by using the CLI Command change_timezone. See Use Case - Set System
Date Time in Appendix D for details.
Polycom, Inc. 28
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 in Appendix D for details.
Repeat the above 3 steps on the other portal.
Configuring 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 Logging In as the Super
Admin.
Note: Setup Worksheet
This section specifically refers to information entered in the Setup Worksheet for the LDAP Server Configuration. Complete the worksheet in advance and use it as a reference during the configuration process and to obtain information about each field.
To configure the connection to the LDAP server:
1 Select SETTINGS > CORE SETTINGS > LDAP. The LDAP Settings screen (shown next) displays.
2 Enter the following in the LDAP Settings screen:
○ Server Enter the LDAP FQDN or IP address.
Polycom, Inc. 29
○ Secure Check the checkbox to establish a secure connection. This is optional but
recommended.
○ Port Enter the LDAP port number (typically 636 for secure and 389 for non-secure).
○ BaseDN Enter the distinguished name entered in the Setup Worksheet for the LDAP Server
Configuration.
○ Username Enter the LDAP services account user ID for system access to the Active Directory.
○ Password Enter the login password for the LDAP services account user ID.
3 Click UPDATE to finish the configuration, or click RESET to populate the fields with the most
recently updated LDAP information.
Configuring the Connection to the SMTP Server
The SMTP server enables the Services Portal to send email notifications to users when their account is
created, when their account details are updated, when they are invited to a meeting, or when a meeting
they created or have been invited to is updated or cancelled. This section shows you the steps for
configuring the connection to the SMTP server. You must log in as a super admin before configuring the
SMTP server. For more information, see Logging In as the Super Admin.
Note: Setup Worksheet
This section specifically refers to information entered in the Setup Worksheet for the SMTP Server Configuration. Complete the worksheet in advance and use it as a reference during the configuration process and to obtain information about each field.
Note: Active Directory Users
The Services Portal considers imported Active Directory users to have enabled accounts until explicitly disabled, and emails are not sent when an Active Directory user is imported.
To configure the connection to the SMTP server:
1 Select SETTINGS > CORE SETTINGS > SMTP. The SMTP Settings screen displays as shown
next.
Polycom, Inc. 30
2 Enter the following in the SMTP Settings screen:
○ Server Enter the SMTP FQDN or IP address.
○ Secure Check the checkbox to establish a secure SMTP-S/SSL connection. This is optional
but recommended if the SMTP server supports secure connection.
○ Port Enter the SMTP port number (typically 25 for non-secure SMTP and 587 or 465 for
SMTP-S) .
○ Login Id Enter the SMTP service account user ID. This is not required for non-secure
connection.
○ Password Enter the service account user ID login password. This is not required for non-
secure connection.
○ Sender Mail Id Enter the email ID used to send notifications.
3 Click UPDATE to finish the configuration or RESET to populate the fields with the most recently
updated SMTP information.
Configuring Additional Server Settings
This section describes how to enter the locations of the Services Portal and Experience Portal servers.
The purpose of each server is:
Web Services Portal (WSP) Server hosts the Services Portal.
Meeting Experience Application (MEA) Server hosts the Experience Portal.
Polycom, Inc. 31
Before you begin, you must be logged in to the Services Portal as a super admin. For more information,
see Logging In as the Super Admin.
Note: Setup Worksheet
This section refers to specific information entered in the Setup Worksheet for the Server Settings. Complete the worksheet in advance, and use it as a reference during the configuration process and to obtain information about each field.
To configure the additional server settings:
1 Select SETTINGS > CORE SETTINGS > SERVER SETTINGS. The SERVER SETTINGS screen
(shown next) displays.
2 Enter the following information in the SERVER SETTINGS screen text blocks:
○ MEA Server Enter the Experience Portal’s FQDN from Accessing the Experience Portal.
○ WSP Server Enter the Services Portal’s FQDN from Accessing the Services Portal.
3 Click UPDATE to finish the configuration, or RESET to populate the fields with the most recently
updated Server Settings information.
Configuring Social Policies
Users can send conference invitations in an instant message to any online contacts listed in their
Skype™, Facebook, or Google Talk™ accounts. How you enable access to social contacts depends on
which social connector(s) you want to use:
Skype™ To enable access to Skype™ contacts, select the Skype checkbox in the Social Policy
page.
Google Talk™ Enabling access to Google Talk™ contacts requires the following steps:
a Create a Google Talk™ app. See Appendix A: Creating a Google Talk™ App. This app is only
enabled to share the contacts lists while keeping the usernames, passwords, and other
information private.
Polycom, Inc. 32
b Select the Google Talk™ checkbox in the Social Policy page.
c Enter the Client ID and Client Secret, retrieved from step 10 of Appendix A: Creating a Google
Talk™ App.
Facebook Enabling access to Facebook contacts requires the following steps:
a Create a Facebook app. See Appendix B: Creating a Facebook App. This app is only enabled to
share the contacts lists while keeping the usernames, passwords, and other information private.
b Select the Facebook checkbox in the Social Policy page.
c Enter the App ID and the App Secret, retrieved step 4 of Appendix B: creating a Facebook App.
Note: CloudAXIS Social Plug-in
Accessing any of the social connectors also requires the CloudAXIS Social Plug-in; this plug-in is downloaded when a user accesses the Experience Portal menu’s Contacts option. For more information, see the RealPresence® CloudAXIS™ User Guide.
This section shows you how to enable and disable Skype™, Facebook, and/or Google Talk™ account
access in the Services Portal. Before enabling access to Google Talk™ contacts, you must create a
Google Talk™ app. See Appendix A: Creating a Google Talk™ App for more information. Before enabling
Facebook contacts, you must first create a Facebook app. See Appendix B: Creating a Facebook App for
more information.
Note that you must log in to the Services Portal as a super admin before entering the social policy
settings. For more information, see Logging In as the Super Admin.
To configure social policies:
1 Select SETTINGS > SOCIAL POLICY. The SOCIAL POLICY SETTINGS screen displays:
The Skype™, Facebook, and Google Talk™ social options display.
Polycom, Inc. 33
Click the checkboxes for Skype™, Google Talk™, and/or Facebook to select or deselect the social 2
policy options. Selecting a checkbox enables users to access the account type’s contact list from
the Experience Portal; deselecting disables users from accessing the account type’s contact list
from the Experience Portal.
When selecting Google Talk™ and/or Facebook, the App ID and App Secret text boxes display as
shown next.
Enter the following: 3
○ Google Talk™ When selecting Google Talk™, enter the following information:
» App ID Enter the Client ID from step 10 of Appendix A: Creating a Google Talk App.
» App Secret Enter the Client Secret from step 10 of Appendix A: Creating a Google Talk™
App
○ Facebook When selecting Facebook, enter the following information:
» App ID Enter the App ID from step 4 of Appendix B: Creating a Facebook App.
» App Secret Enter the App Secret from step 4 of Appendix B: Creating a Facebook App.
4 Click UPDATE.
Polycom, Inc. 34
Configuring the Connection to the DMA System and RPAD
Servers
This section explains how to enter configuration details for your DMA system, RPADs, and access points.
DMA systems enable the Services Portal to launch online video conference meetings, RPADs are
external links to the DMA that enables firewall traversal, and points of presence enable you to route either
directly or indirectly to the DMA. For example, an access point configured with an FQDN that points to the
RPAD externally and points to the DMA from within the Polycom network enables the Services Portal to
communicate with the DMA from either side of a firewall.
You must log in to the Services Portal as a super admin before entering the server settings. For more
information, see Logging In as the Super Admin.
Note: Setup Worksheet
This section specifically refers to information entered in the Setup Worksheet for the DMA Configuration. Complete the worksheet in advance, and use it as a reference during the configuration process and to obtain information about each field.
To configure the connection to the DMA system:
Select SETTINGS > DMA CONFIG. The DMA Config Settings screen displays:
From this SETTINGS screen, you can either
configure a new DMA connection, or
change an existing one.
To configure a new DMA connection:
1. Click +ANOTHER DMA. The DMA CONFIGURATION screen with the following fields and text
boxes display next.
Polycom, Inc. 35
2. Enter the appropriate data for each of the following DMA CONFIGURATION screen fields. All fields
marked with an asterisk (*) REQUIRE you to enter data.
○ Name Enter the name of this DMA system.
○ Host Enter the DMA system interface FQDN.
○ Port Enter “8443” as the DMA system communication port.
○ VMR Prefix Enter the VMR dialing prefix corresponding to this DMA system (4-digit
maximum). This is optional. Note that a personal VMR can only be used for CloudAXIS
meetings if it exists on one of the DMA systems referenced in the Services Portal configuration,
and if the correct DMA system hosting the VMR can be determined using the prefix
configuration. If only one DMA system is configured, all VMRs are assumed to have provisioned
on it, and no prefix configuration is necessary.
○ Default Admin Enter the DMA system admin user name.
○ Admin Password Enter the DMA system admin account password.
○ Owner Domain Enter the domain of the owner who creates the meetings.
○ Owner Username Enter the user name of the owner who creates the meetings.
○ Generate VMR range Select to enter the range of numbers allowed for generating VMRs.
When selected, two text boxes display (see following partial screen).
Polycom, Inc. 36
3. Click + ADD ACCESS POINT to enter your access point information. The ACCESS POINT screen
is shown next.
Note: Access Point
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. Access points are configurable as follows:
Direct connection to DMA.
Externally to access the DMA via H.323 video border proxy.
Externally routed via a SIP Session Board Controller (SBC), including Polycom Real Presence Access Director (RPAD), or any third-party session boarder controller.
ISDN.
Audio dial-in via Public Switch Telephony Network (PSTN).
The client or end point could be the CloudAXIS Experience Portal, a separate soft client such as Polycom RealPresence Mobile, a hardware appliance such as Polycom Group Series, or a telephone.
4. Enter your access point information from the Setup Worksheet for the DMA Server Access Point
Configuration as follows:
Note: Entering Access Points (AP)
Enter the APs in the order that you want the Services Portal to use. For example, enter internal APs first. Also, note that it is mandatory to add at least one SIP AP.
○ Location Enter a name for this access point that describes its geographic location or some
other property which distinguishes it from other access points. This is optional.
○ Transport From the dropdown box, select the protocol associated with the access point (SIP,
H323, ISDN, or PSTN). At this time, you must not change from the “SIP” default value or
CloudAXIS will not function.
Polycom, Inc. 37
○ Dialstring Enter the string that an endpoint should use to dial the access point. Your dial string
should be appropriate for the specified access point transport type (e.g., an ENUM for H.323).
Click +ADD ACCESS POINT to enter another access point as needed.
5. When all needed DMA Configuration fields are completed, select CONFIGURE at the bottom of the
screen.
To update an existing DMA connection:
1. Click the icon of the DMA Host you want to configure to the down position. A DMA CONFIG
SETTINGS screen with the following fields displays. (See the following two partial screen examples.)
With two exceptions, this screen contains the fields and data that you supplied when you first
configured a DMA connection. Two new fields - MCU Pool Order and Conference Template –
appear when you want to update your DMA connection:
MCU Pool Order Click on the dropdown menu, and select from the list of MCU pool orders
available on DMA. This feature is used by the users hosting or joining meetings using
CloudAXIS
Conference Template Click on the dropdown menu, and select from the list of Conference
templates available on DMA. This feature is applied to all scheduled and adhoc meetings
created on this DMA using CloudAXIS
Polycom, Inc. 38
After making selections from the dropdown boxes of the two fields, verify the contents of the other
screen fields. After any necessary configuration changes have been made, select CONFIGURE.
Configuring Conference Settings
This section shows you how to set and control the visibility and functionality of meeting features.
To configure conference settings:
1. Select SETTINGS > CONFERENCE SETTINGS. The CONFERENCE SETTINGS screen
displays (see next).
Polycom, Inc. 39
2. Enter the following in the CONFERENCE SETTINGS screen options:
○ Passcode mandatory If selected, an attendee passcode must be set for all meetings before
they are started.
○ AdHoc meeting duration Enter the duration (in minutes) of Meet Now meetings. A default
value of 120 displays; minimum settable time is 15 minutes.
○ Buffer time before meeting starts Enter a buffer time (in minutes). All meetings become
active prior to the start of the meeting within the buffer time. A default value of 20 displays;
minimum settable time is 1 minute.
○ Buffer time after meeting ends Enter a buffer time (in minutes). All meetings will be active
after the meeting ends for the buffer time. No default value displays; minimum settable time is 0
minutes.
○ Allow use of PersonalVmr Select to allow the use of a Personal VMR. When selected, the
Use Personal VMR text and checkbox will appear on the Schedule a Meeting screen.
○ Allow use of JoinBridge Select this checkbox to allow the display and use of the Join Bridge
button. When selected, the JoinBridge button is visible on the Schedule a Meeting screen. If
not selected, the JoinBridge button does not display.
○ Expose Passcode Select this checkbox to display the passcode in the email invites and
URLs. If not selected, it is assumed that the passcode is to be communicated by the Host
through some out-of-band means for greater security.
3. Click SET.
Polycom, Inc. 40
Localizing the Services Portal
Localize your Services Portal by uploading a language from a list of available languages.
To upload a language pack:
1. Select SETTINGS > LANGUAGE. The LANGUAGE PACK screen displays:
2. Click the VIEW Supported languages hyperlink to see a list of the languages that are supported
and available on your Services Portal.
Polycom, Inc. 41
3. Click CLOSE to return to the Language Pack screen.
4. To upload a new language pack, click on Browse … , select the desired language pack file from
your browser, and click UPGRADE.
You can return to an earlier version of your Language Pack by selecting REVERT TO THIS VERSION.
Setting Date and Time
The Services Portal uses a Network Time Protocol Server (NTP Server) for basic clock synchronization.
This section shows you how to set the date and time for the Services Portal.
Note: Setup Worksheet)
This section specifically refers to information entered in the Setup Worksheet for the Date Time Configuration. Complete the worksheet in advance, and use it as a reference during the configuration process and to obtain information about each field..
To set the date and time:
1. Select PLATFORM SETTINGS > DATE TIME. The DATE TIME screen displays.
2. The DATE TIME screen displays the following text boxes:
○ NTP Server Enter the NTP server IP address or FQDN to synchronize the time on the
Services Portal system. This value must match the data supplied to the Experience Portal.
○ Time Zone Nothing needs to be entered in this field. This field displays the time zone of the
Services Portal.
○ Date & Time Nothing needs to be entered in this field. This field displays the time of the
Services Portal.
3. Click UPDATE.
Polycom, Inc. 42
Managing Certificates
The Services Portal requires a secure connection. When a secure connection is established, the browser
receives a self-signed certificate or a certificate signed by a third party Certificate Authority verifying the
identity of the Services Portal.
This section describes how to generate self-signed certificates and certificate sign requests (CSRs); how
to view, download, and delete certificates; and how to upload third-party signed and trust certificates to
the Services Portal.
Generating Certificates and CSRs
This section shows you how to generate self-signed certificates and certificate sign requests (CSRs). You
must send the CSRs to a third party Certificate Authority for a digital signature then upload the signed
certificate. For uploading certificates, see Uploading Certificates or Certificate Chain.
Note that you must log in as a super admin to create certificates and CSRs. To determine your account
type, see Understanding Account Roles.
Caution: Overwrite Warning
Be sure you need a new certificate or CSR before following this procedure. Generating a new certificate or CSR overwrites the previous. To check, see Viewing, Downloading, and Deleting Certificates.
Note: Other Requirements
The certificates created from CSRs generated by the Services Portal will only authenticate the user connection to the Services Portal. A separate CSR needs to be externally generated for the Experience Portal and RealPresence components. Send the externally generated CSR to a Certificate Authority, then upload the signed certificate and key to the components and Services Portal. For uploading to the Services Portal, see Uploading Certificates.
To generate certificates and CSRs:
1 Select PLATFORM SETTINGS > CERTIFICATE > Generate CSR/Certificate. A certificate
management screen (see next) displays.
Polycom, Inc. 43
2 Enter the following in the certificate management screen:
○ Operation Type Select the Operation Type dropdown box, and choose one of the following:
» CSR Generates a Certificate Signing Request (CSR). Send the CSR to a Third Party
Certificate Authority for a digital signature then upload the signed certificate to the server. For
uploading, see Generating Certificates and CSRs.
» Certificate Generates a self-signed certificate.
○ Type Select the dropdown box, and select WebServer.
○ Organization Enter your organization name.
○ Organizational Unit Enter your organization unit information.
○ Country Enter the two letter ISO code for your organization’s country.
○ State Enter your state with full spelling.
○ Location Enter your organization’s city or location.
○ Sub Alternate name Enter the list of host names protected by this certificate. The host names
must be separated by commas.
Polycom, Inc. 44
3 Click GENERATE.
Note: Restart Services Portal Server
After generating your certificate, the Services Portal server must be restarted to recognize the certificate. Note that a restart is not needed for generating CSRs. To restart:
1. Using your SSH client, access the Services Portal FQDN. 2. Login as a privileged administrator using [caxis/caxis].
3. Restart server: services <SomeServer> restart
Viewing, Downloading, and Deleting Certificates
Super admins use the certificate list to confirm if a certificate is needed and to delete obsolete certificates.
This section shows you how to view, download, and delete certificates in the Services Portal.
To view, download, or delete certificates and CSRs:
1 Select PLATFORM SETTINGS > CERTIFICATE > Certificate list. The Certificate list screen,
shown next, displays any existing certificates.
2 Select one of the following options:
○ VIEW Click to view and/or download the certificate.
To download:
i. After selecting VIEW, copy the entire hash from ----- BEGIN CERTIFICATE to ----- END
CERTIFICATE.
ii. Paste the text in to a text file.
iii. Rename the extension .cer.
If the file is a CSR, you can now send the file to a third-party CA for signing.
Polycom, Inc. 45
○ DELETE Click to delete the certificate. This option is only available to WebApp-trust
certificates. Webserver certificates can only be regenerated or uploaded as a Certificate
Authority signed certificate. To generate a WebApp certificate, see Generating Certificates and
CSRs.
Caution: Deleting Trust Certificates
Deleting trust certificates can break the chain of certificate trust.
Uploading Certificates or Certificate Chain
The Services Portal enables super admin users to upload two types of required certificates: third party
certificates signed by a Certificate Authority and trust certificates. Upload the signed certificate to
establish a secure communication with users and verify the identity information of Services Portal servers.
Upload the trust certificate for servers that require secure communication such as the Active Directory
server, SMTP server, and DMA system. This section shows you how to upload signed third party and
trust certificates to the Services Portal.
To upload certificates:
1 Select PLATFORM SETTINGS > CERTIFICATE > Upload Certificate as shown next.
2 Perform the following:
a To upload a third-party signed certificates
Polycom, Inc. 46
i. Select the WebServer Own option in the Type dropdown menu.
ii. Click the icon.
iii. Navigate to the certificate or certificate chain, and select Open.
iv. Click UPLOAD.
b To upload a trust certificate.
i. Select the WebServer Trust option in the Type dropdown menu.
ii. Click the icon.
iii. Navigate to the certificate, and select Open.
iv. Click UPLOAD.
Note: Restart Services Portal Server
After uploading your certificate, the NGINX and Tomcat servers must be restarted to recognize the certificate. To restart:
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.
3 Restart servers by entering the command: services <SomeServer> restart
Selecting and Downloading Log Levels
The Services Portal log levels are listed by hierarchy and displayed in a dropdown menu. When you
select a log level, the Services Portal prints the selected level, along with all the lower levels, to a log file
that can be downloaded.
This section explains each log level, shows you how to select a log level to print, and shows you how to
download the log file.
To select a log level or download the log file:
1 Select PLATFORM SETTINGS > LOGS. The logs level options screen displays as shown next.
Polycom, Inc. 47
2 Select the Level dropdown menu to display all log level options, in hierarchical order, as shown
next.
3 Choose one of the following log levels:
○ ALL Turns on all logging.
○ TRACE Logs finer-grained information than Debug. These logs are also helpful for debugging.
○ DEBUG Logs fine-grained information that are helpful for debugging.
○ INFO Logs messages that highlight the progress of the application at a coarse-grained level.
○ WARN Logs potentially harmful situations.
○ ERROR Logs errors that might still allow the Services Portal to keep running.
○ OFF Turns off the logging.
Note: Log Level Hierarchy
When a log level is selected, all levels beneath the selected level are also printed. For example, selecting Info will print the Info, Debug, and Trace levels.
4 Select one of the following options:
○ Click UPDATE to begin printing from the selected level.
○ Click DOWNLOAD to download the log file.
Polycom, Inc. 48
Updating Services Portal Software
To deploy an updated version of Services Portal software, do the following:
Obtain the new Services Portal software OVA file
Deploy the file using the instructions in “Deploying the Services Portal and Experience Portal
Packages”
Use the instructions that follow to migrate the provisioning and state information from the existing
server running the older software to this new instance
Migration Process
Before you begin the upgrade process, verify that you have already loaded the correct certificates on the
VM that you wish to migrate the settings to, i.e., the new Services Portal. No action needs to be taken on
the older Services Portal during this migration process.
To migrate your settings:
1. Accessing the Migration Interface
In the Services Portal, navigate to PLATFORM SETTINGS, and click MIGRATE.
Polycom, Inc. 49
2. Enter the Admin Credentials
To validate the user rights, enter the admin username and password for the new Services Portal.
Polycom, Inc. 50
3. Verify and Begin Migration
Read the final disclaimer, and click YES when you are ready to begin the migration.
Polycom, Inc. 51
4. Enter the Old Services Portal’s Information
Enter the hostname (FQDN), admin username, and admin password for the Services Portal from which
you want to migrate the settings and database. Select MIGRATE when finished.
Polycom, Inc. 52
5. Migrating Settings and Database
Wait for the User Interface to indicate that the information from the old Services Portal has been
successfully imported. Once this import has finished, the Services Portal will take a while to do an internal
configuration before rebooting itself.
6. Verifying Migration
When the Services Portal VM has restarted, log in with the admin credentials from the old Services Portal,
and verify that the settings are correct.
Note: Verifying Migration
Once the data is successfully migrated, make sure that the DNS records are updated to point to the new Services Portal.
Polycom, Inc. 53
Activating Licenses
License activation for the Services Portal and the Experience Portal is done through the Services Portal.
The Services Portal license, which is your CloudAXIS product license, must be activated before you can
configure the Services Portal. The Experience Portal license, which lets you determine the number of
CloudAXIS product users, must also be activated.
Activate your licenses in either an online or an offline mode. Online and offline license deactivation is also
available.
Note: Experience Portal URL The Experience Portal license URL must be configured before setting Experience Portal licenses on the Services Portal.
To activate the Services Portal license from the online mode:
1. Open your Services Portal, and log in (“admin/admin”) as a super admin as in the following screen.
2. Select PLATFORM SETTINGS > LICENSE. The following screen, in the default Online Activation
mode, displays.
Polycom, Inc. 54
3. Activate your Services Portal license by entering your three Activation Keys in the appropriate
Activation Key block. (These Activation Keys will have been sent to you in an email after your
purchase of a CloudAXIS product.)
For example, you will receive your activation key information in the following format in an email.
4. Click ACTIVATE, and your screen will refresh with the License activated successfully message as
in the following sample display.
Polycom, Inc. 55
To deactivate any of your licenses, click on the Deactivate option in the appropriate Activation Key
field.
5. (Optional) Click + ACTIVATE MORE USERS to activate an additional 100 users,
To activate the Services Portal license from the offline mode:
1 Select PLATFORM SETTINGS > LICENSE
2 Select Offline Activation from the Mode: dropdown box. The following screen displays:
Polycom, Inc. 56
3 Copy the Services Portal Activation Key you received after purchasing your CloudAXIS product,
and Paste it into the Service Portal Activation Key: block on your screen.
4 Select Download Activation Request File. The Activation Request File downloads.
5 Send the Activation Request File you have just downloaded, along with your Host/Device ID (which
is found just above the Service Portal Activation Key: field) in an email to your Polycom License
Administrator. An Activation Response File is automatically sent back to you.
6 Click Choose File to select and upload your Activation Response File.
Repeat steps 3 to 6 above to activate the Experience Portal while in the Offline mode.
7 Click ACTIVATE to activate the Services Portal license.
Polycom, Inc. 57
To activate the Experience Portal connection to the Services Portal
1. Open the Experience Portal, and log in using ‘admin’ as your User Name and Password.
2. When the Experience Portal opens, select Settings > Environment > General Settings.
3. In the License URL field block (See next screen.), enter the Services Portal information along with
the User Name and Password.
4. Click Submit, and then select Maintenance > Tools > Apply Configuration.
5. When the Apply Configuration screen displays, click Go to apply the configuration.
Polycom, Inc. 58
This will display the license information for the Experience Portal.
To view the license information in the Experience Portal
1. Select Maintenance > Tools > Get License Info.
2. Click Go to get your Experience Portal license information as in the following sample screen:
Configuring Proxy Settings
To configure your proxy settings in the Services Portal
1. Open the Services Portal, and log in (“admin/admin”) as a super admin.
2. Select Platform Settings > Proxy. By default, proxy configurations are not enabled. A proxy can
be configured as either Authenticated or Non-authenticated.
Note: Proxy Support For Software Release 1.3.0, we only support HTTP Forward Proxy.
Configuring a Non-Authenticated Proxy
Polycom, Inc. 59
1. In the Proxy Settings screen (see next), enter the proxy Server IP address and Port information.
2. Click UPDATE.
Configuring an Authenticated Proxy
1. In the Proxy Settings screen, enter the proxy Server IP address and Port information.
2. Select the Yes checkbox for the Authentication Proxy field. User Id and Password fields will
display. Enter your information for these two fields, and select UPDATE.
Polycom, Inc. 60
Disabling a Proxy
1. Select the No checkbox for Authentication Proxy.
2. Delete the entries in the Server and Port fields.
3. Select UPDATE.
Configuring the Experience Portal Before configuring the Experience Portal, you must have the address for the DMA/conference provider,
deploy the Experience Portal, and activate the Experience Portal license. For deploying the Experience
Portal, see Deploying the Services Portal and Experience Portal Packages. For activating the Experience
Portal license, see the previous section in this manual.
When the Experience Portal server is online, opening the URL https://<Experience Portal
FQDN>:9445 in your default browser will launch the Experience Portal Administration application and
enable you to configure the Experience Portal server.
The Administration application has a number screens, each containing fields that require specific values.
This section is divided by screen name and uses tables with field names and value descriptions to help
you configure the Experience Portal. The Experience Portal configurations are saved in the
settings.json file, which can be exported and saved as a backup or imported to another Experience
Portal server.
Polycom, Inc. 61
This section explains how to set the Experience Portal configurations with the Experience Portal
Administration tool and is divided as follows:
Configuring the Server Settings
Configuring the Environment General Settings
Configuring the Meeting Hosts
Configuring the Services Portal Connection Settings
Configuring the VMR Settings
Configuring the Services Portal Authentication Provider Settings
Configuring the DMA Settings
Viewing Experience Portal Log Files
Applying Experience Portal Configurations
Setting System Administration UI Properties
Updating Experience Portal Software
Exporting the Experience Portal Configuration File
Importing the Experience Portal Configuration File
In order to deploy an updated version of Experience Portal software you must do the following:
Obtain the new Experience Portal software OVA file
Deploy this file using the instructions in Deploying the Services Portal and Experience Portal
Packages
Use the instructions that follow to migrate the provisioning and state information from the existing
server using the older software to this new instance.
Configuring the Server Settings
This section has a table with field names and value descriptions to help you configure the server settings
in the System Administration application. This configuration applies to the entire server instance across all
configured environments.
To configure the Server Settings:
1 With the System Administration application open in your browser, select Settings > Server as in
the following example screen portion.
The screen displays a list of text box fields as in the following Server screen.
Polycom, Inc. 62
2 The Server Fields table, shown next, contains a list of fields found in the System Administration
application’s Server screen. The value descriptions for each field listed in the table can help you to
determine the values you need to enter in the Server screen.
Table 12: Server Fields
Field Name Value/Description
License Key The license for the Experience Portal server.
Log Level Determines what levels of logging show up in the log
files. Available options: trace, error, debug, and info.
See Understanding Log Settings below.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings below.
3 Click Submit.
Understanding Log Settings
This section provides essential information on the Log Level and the Log Target settings.
To set Log Levels, add the desired levels to the Log Level text field. These added levels must be
separated by a comma with no spaces between them. Only Log Levels in the field will be written out to
the Log Targets.
Polycom, Inc. 63
Table 13: Log Levels
Log Level Value/Description
Error Shows only error tagged messages that indicate that a
serious issue has occurred on the server. This is the
default Log Level.
Info Shows informational messages, with minimal detail, that
highlight the progress of the application.
Debug Shows informational messages, with more detail, that
highlight the progress of the application.
Trace Shows informational messages, with maximum detail, that
highlight the progress of the application.
To set Log Targets, add the desired targets to the Log Target text field. These targets must be separated
by a comma with no spaces between them. Only Log Targets in the field will get the Log Level
information sent to them.
Table 14: Log Targets
Log Target Value/Description
Console Sends the log data to the CLI interface for real-time
analysis. The log data sent to the target is defined by the
Log Level.
File Sends the log data to the log files available in the
Administration System user interface. The log data sent to
the target is defined by the Log Level; this is one of the
default Log Targets.
Syslog Sends the log data to a syslog server. The log data sent to
the target is defined by the Log Level; this is one of the
default Log Targets.
Caution: Log Level and Log Target Settings
If you want to enable more than the default Log Level and Log Targets, be aware that the log files will not be automatically deleted and may use all of the remaining disk space on your drive.
Configuring the Environment General Settings
This section has a table with field names and value descriptions to help you configure the general settings
in the Administration application. The General Settings applies to all subcomponents within the specified
environment.
Polycom, Inc. 64
To configure the General Settings:
1 With the System Administration application open in your browser, at the Settings tab select
Environment > General Settings as shown in the following screen example.
The screen displays a list of text box fields as shown in the next screens.
Polycom, Inc. 65
2 The General Settings Fields table, shown next, contains a list of fields found in the System
Administration application’s General Settings screen. Use the value descriptions for each field listed
in the table to determine the values you need to enter in the General Settings screen. After all
values are entered, select Submit.
Table 15: General Settings Fields
Field Name Value/Description
description Enter a short description of the environment.
enabled Controls whether or not the environment is enabled.
Shared Secret The shared secret key for the environment used for
secure communications. This SHOULD NOT be
modified by the user.
Polycom, Inc. 66
Field Name Value/Description
License URL The Services Portal URL is used to retrieve the
license information. Enter in this format
https://username:password@<services portal FQDN>
A local user named measys is created in Services
Porta,l and measys is the default password. Use that
user to authenticate and retrieve the license
information from the Services Portal.
SSL Proxy Type This is the method used to proxy internally from the
internal URL port to the host. In TCP mode, traffic is
routed to host 0. Do not modify from TCP default
unless instructed to.
Secure External Address The address that external users will use to connect to
the Experience Portal.
External Address (non-secure) The non-secure address that external users will use to
connect to the Experience Portal. By default, reroutes
to the secure address.
Secure Internal Address The address that internal users will be forwarded to
when trying to connect to the Experience Portal.
Internal Address (non-secure) The non-secure address that internal users will get
when trying to connect to the Experience Portal. By
default, reroutes to the secure address.
certificates
certificates[0].certificate
certificates[0].key
certificates[0].usage
The raw text of the SSL identity certificate for the
environment.
The raw text of the private key used to generate the
certificate’s CSR.
Select server or trustedroot from the dropdown menu
to determine how the certificate file pair is used by the
VM.
Configuring the Meeting Hosts
This section uses a table with field names and value descriptions to help you configure the Meeting Host
settings in the Administration app. The Meeting Host is the service responsible for serving the user
interface to the end-user and acts as a broker between all components in the system.
Polycom, Inc. 67
To configure the Meeting Hosts:
1 With the System Administration application open in your browser, select Settings > Environment
> Meeting Hosts as shown next.
The screen displays a list of text box fields in two areas of the Meeting Hosts screen. Note that the
top half of this screen, shown next, contains the fields listed in the Meeting Hosts Fields section and
the authmatch section. The bottom half of the screen contains the fields listed in the Lobby Rule
Fields table.
2 The Meeting Hosts Fields table, shown next, contains a list of fields found in the System
Administration app’s Meeting Hosts screen. Use the value descriptions for each field listed in the
table to determine the values you need to enter in the fields at the top of the Meeting Hosts screen
text boxes. See step 3 for the fields listed under authmatch.
Polycom, Inc. 68
Table 16: Meeting Hosts Fields
Field Name Value/Description
Default Skin Enter the CCS skin to be applied to the meeting UI.
This SHOULD NOT BE MODIFIED unless otherwise
specified.
Log Level Determines what levels of logging will show up in the
log files. Available options: trace, error, debug, and
info. See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings.
3 The authmatch lists rules made up of three fields: Match, Property, and Realm. The rules can be
dragged into a specific order. The authentication matching stops when it matches the first rule. The
authmatch field descriptions follow:
○ Match Enter a regular expression that you want the property to match to for authentication. For
example, if you only want to authenticate users with a Polycom.com email address, you would
use the regular expression “[email protected]$”.
○ Property This is the data type that you want to apply the Match regular expression to. Based
on the user information entered, at least one rule is needed for UserAddress, SSOSource, and
SSOUsername.
○ Realm The target authentication realm is the SERVICES PORTAL server that you want to
authenticate the rule against. For UserAddress and SSOSource, this can be a pointer to the
WSPAuth Realm list using the $#, with $1 referencing the first element in the list, and so on. For
the SSOUsername, you should explicitly enter the SERVICES PORTAL address.
4 Lobby Rules are used to determine the meeting experience behavior when an attendee joins a
meeting. This can include aspects such as the visual skin they see. The Lobby Rule Fields table
contains a list of fields listed under the Meeting Hosts screen’s Lobby Rules section, shown next.
Use the value descriptions for each field listed in the table to determine the values to enter in the
Lobby Rule screen. Note that multiple Lobby Rules can be set. Drag the Lobby Rules to determine
the order of rules. The meeting matching stops when a match is made.
Polycom, Inc. 69
Table 17: Lobby Rule Fields
Field Name Value
Match Enter a regular expression for the matching VMRs
that you want to allow access to this lobby. For ad
hoc meetings (i.e., Meet Now), you should use a
catch-all expression similar to ^[0-9]+ to allow any
VMR number to work.
Property This is what you want to apply the rule to, and can be
either the lobby code or the host.
Route This is the internal route for the lobby code match.
Unless there is an explicit reason, this route
SHOULD NOT be modified.
Skin The CSS skin that will be applied to meetings
matching this Lobby Rule. This SHOULD NOT BE
MODIFIED unless otherwise specified.
Polycom, Inc. 70
Field Name Value
Skin The template that will be applied to meetings
matching this Lobby Rule. This SHOULD NOT BE
MODIFIED unless otherwise specified.
5 Click Submit.
Configuring the Services Portal Connection Settings
This section provides the field names and value descriptions needed to configure the Services Portal
Connection (WSPConf) settings in the Administration application.
5 With the System Administration application open in your browser, make the following selections as
shown below: Settings > Environment > Agents > WSPConf Settings.
The following screen sample shows only the beginning portion of the long list of text box fields in
the WSPConf Settings selection. Table 16 contains the complete list of these text field names with
their value descriptions, including nearly forty Template fields.
6 The WSPConf Settings screen contains the Target Url field. In this field, enter the Services Portal
URL including an existing super admin username and password. Note that the default existing
account is meaconf/meaconf. Do not change any other fields in this screen.
Format:
https://<username>:<password>@<Services Portal Domain>
Example:
https://meaconf:[email protected]
7 Click Submit.
Polycom, Inc. 71
Table 18: Conference Manager Agent on WSP Fields
Field Name Value/Description
Run Locally Specifies whether the DMA agent is running on this
server or on a remote
Startup Delay If there is a need to slow down the time between
when the server starts and this agent starts, the
number of seconds to delay startup should be
entered here. This is especially relevant on older,
slower servers.
Log Level Determines what levels of logging show up in the log
files. Available options: trace, error, debug, and info.
See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings.
Polycom, Inc. 72
Auto Restart Determines if the agent can be automatically
restarted when the configuration updates. This can
affect call stability and is enabled by default.
Agent Type Describes the type of agent this is. For WSPConf,
the correct agent type is wsp-
conferences/polycom.mea.agent.wsp-conferences.
Roles Describes which one of multiple role types should be
assigned to an agent. Select Conference Manager
for WSPConf.
Experience Portal URL This field is for future product functionality. For now,
leave blank unless explicitly told to do otherwise.
Target URL This is the full URL of the Services Portal in the
format https://<admin username>:<admin password>
@<WSP address>.
Enforce Certificate Validation Check this option to verify the DMA’s certificate as a
security measure, On by default.
Routes This is a list of routes from the Lobby Codes that the
agent has access to. The routes in this list are
separated by commas, and there are NO spaces
between any of the list elements. By default, this list
should not be changed.
Template
Template.LobbyCode
This is the lobby code to be used. Leave it at its
default value unless explicitly told otherwise.
Template.LobbyRoute This is the lobby route to be used when accessing a
bridge meeting.
Template.OrganizerUserEmail After the @ symbol, this is the email domain that
allows users access to the VMRs
Template.ExitMeeting Actions
Template.ExitMeetingActions[#].Role
The user role to which the exit point will be assigned.
2 is for Participant, 3 is for Presenter.
Template.ExitMeetingActions[#].Url The address that users exiting the meeting will be
taken to.
Polycom, Inc. 73
Template.ExternalConferences
Template.ExternalConferences[#].
AccessPoints
Template.ExternalConferences[#].
AccessPoints[#].DialString
The fill dialstring for connecting to VMRs. Should
only have to modify the address after the @ symbol
to point to the DMA.
Template.ExternalConferences[#].
AccessPoints[#].Location
This should match the location of the POP in the
Services Portal for the DMA.
Template.ExternalConferences[#].
AccessPoints[#].POPAddress
This is the address of the DMA to be used and is the
same as configured on the Services Portal.
Template.ExternalConferences[#].
AccessPoints[#].Transport
The transport type should be SIP unless stated
otherwise.
Template.ExternalConferences[#].
ConferenceId
This is the conference ID code for establishing
connections to VMRs. Do Not change unless
instructed to.
Template.FeatureExtensions
Template.FeatureExtensions[#].menu.
autoopen.query
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
autoopen.value
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
frameid
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
menulocation
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
menurank
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
menuname
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
permissions
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
permissions[#]
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
resourcelocation
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
titleKey
This is a future release feature; do not edit.
Polycom, Inc. 74
Template.FeatureExtensions[#].menu.title This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.type This is a future release feature; do not edit.
Template.Settings.
AllowAnonymousParticipants
Controls whether anonymous participants are
allowed into VMRs.
Template.Settings.
AuthenticatedUsersHostDomainJoinAs
Controls the role a domain authenticated user is
given when joining a VMR.
Template.Settings.
AuthenticatedUsersOtherDomainJoinAs
Controls the role a non-domain authenticated user is
given when joining a VMR.
Template.Settings.DefaultSurfaceHeight Do not edit this variable.
Template.Settings.DefaultSurfaceWidth Do not edit this variable.
Template.Settings.HelpUrl This is a future release feature; do not edit.
Template.Settings.Locked Do not edit this variable.
Template.Settings.GeoLocation Do not edit this variable.
Template.Settings.RecordingAvailabled Do not edit this variable.
Template.Settings.RequireDisplayName Do not edit this variable.
Template.Settings.RequireEmailAddress Do not edit this variable.
Template.Settings.VideoPreference Do not edit this variable.
Template.Settings.VideoPreference[#] Do not edit this variable.
Configuring the VMR Settings
This section includes a table with field names and value descriptions to help you configure the VMR
settings in the Administration application.
To configure the Personal VMR Settings
1 With the System Administration application open in your browser, select the following menu path:
Settings > Environment > Agents > VMR Settings (see following screen).
Polycom, Inc. 75
The resultant Personal VMR screen displays a list of text box fields. A partial screen with the initial
text fields is shown next.
2 The Personal VMR Settings Fields table that follows contains the complete list of text fields found
on the Personal VMR Settings screen. Use the value descriptions for each field listed in the table to
determine the values you need to enter in the Personal VMR Settings screen. Do not enter or
change values of any fields that are not listed in the table.
Polycom, Inc. 76
Table 19: Personal VMR Settings Fields
Field Name Value/Description
Run Locally Specifies whether the DMA agent is running on this
server or on a remote
Startup Delay If there is a need to slow down the time between
when the server starts and this agent starts, the
number of seconds to delay startup should be
entered here. This is especially relevant on older,
slower servers.
Log Level Determines what levels of logging show up in the log
files. Available options: trace, error, debug, and info.
See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings.
Auto Restart Determines if the agent can be automatically
restarted when the configuration updates. This can
affect call stability and is enabled by default.
Agent Type Describes the type of agent this is. For VMR agents,
the correct agent type is
static/polycom.mea.agent.wsp-static
Roles Describes which one of multiple role types should be
assigned to an agent. Select ConferenceManager for
VMR agent.
Experience Portal URL This field is for future product functionality. For now,
leave blank unless explicitly told to do otherwise.
Target URL This is blank.
Enforce Certificate Validation Check this option to verify the DMA’s certificate as a
security measure, On by default.
Routes This is a list of routes from the Lobby Codes that the
agent has access to. The routes in this list are
separated by commas, and there are NO spaces
between any of the list elements. By default, this list
should not be changed.
Template
Template.LobbyCode
This is the lobby code to be used. Leave it at its
default value unless explicitly told otherwise.
Polycom, Inc. 77
Field Name Value/Description
Template.LobbyRoute This is the lobby route to be used when accessing a
bridge meeting.
Template.OrganizerUserEmail After the @ symbol, this is the email domain that
allows users access to the VMRs
Template.ExitMeeting Actions
Template.ExitMeetingActions[#].Role
The user role to which the exit point will be assigned.
2 is for Participant, 3 is for Presenter.
Template.ExitMeetingActions[#].Url The address that users exiting the meeting will be
taken to.
Template.ExternalConferences
Template.ExternalConferences[#].
AccessPoints
Template.ExternalConferences[#].
AccessPoints[#].DialString
The fill dialstring for connecting to VMRs. Should
only have to modify the address after the @ symbol
to point to the DMA/RPAD.
Template.ExternalConferences[#].
AccessPoints[#].Location
This should match the location of the POP in the
Services Portal for the DMA.
Template.ExternalConferences[#].
AccessPoints[#].POPAddress
This is the address of the DMA/RPAD to be used
and is the same as configured on the Services
Portal.
Template.ExternalConferences[#].
AccessPoints[#].Transport
The transport type should be SIP unless stated
otherwise.
Template.ExternalConferences[#].
ConferenceId
This is the conference ID code for establishing
connections to VMRs. Do Not change unless
instructed to.
Template.FeatureExtensions
Template.FeatureExtensions[#].menu.
autoopen.query
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
autoopen.value
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
frameid
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
menulocation
This is a future release feature; do not edit.
Polycom, Inc. 78
Field Name Value/Description
Template.FeatureExtensions[#].menu.
menurank
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
menuname
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
permissions
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
permissions[#]
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
resourcelocation
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.
titleKey
This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.title This is a future release feature; do not edit.
Template.FeatureExtensions[#].menu.type This is a future release feature; do not edit.
Template.Settings.
AllowAnonymousParticipants
Controls whether anonymous participants are
allowed into VMRs.
Template.Settings.
AuthenticatedUsersHostDomainJoinAs
Controls the role a domain authenticated user is
given when joining a VMR.
Template.Settings.
AuthenticatedUsersOtherDomainJoinAs
Controls the role a non-domain authenticated user is
given when joining a VMR.
Template.Settings.DefaultSurfaceHeight Do not edit this variable.
Template.Settings.DefaultSurfaceWidth Do not edit this variable.
Template.Settings.HelpUrl This is a future release feature; do not edit.
Template.Settings.Locked Do not edit this variable.
Template.Settings.GeoLocation Do not edit this variable.
Template.Settings.RecordingAvailabled Do not edit this variable.
Template.Settings.RequireDisplayName Do not edit this variable.
Template.Settings.RequireEmailAddress Do not edit this variable.
Template.Settings.VideoPreference Do not edit this variable.
Template.Settings.VideoPreference[#] Do not edit this variable.
Click Submit.
Polycom, Inc. 79
Configuring the Services Portal Authentication Provider
Settings
This section uses a table with field names and value descriptions to help you configure the Services
Portal Authentication Provider (WSPAuth) settings in the System Administration application.
To configure the WSPAuth Settings
1 With the System Administration application open in your browser, select the Settings tab at the top,
and then > Environment > Agents > WSPAuth Settings as in the following screen.
The screen displays a list of text box fields as shown next.
Polycom, Inc. 80
2 The WSPAuth Settings Fields table that follows contains a list of fields found in the System
Administration application’s WSPAuth Settings screen. Use the value descriptions for each field
listed in the table to determine the values you need to enter in the WSPAuth Settings screen.
Table 20: WSPAuth Settings Fields
Field Name Value/Description
Run Locally Specifies whether the DMA agent is running on this
server or on a remote server in accordance with the
future roadmap. For this release, this option should
ALWAYS be checked.
Startup Delay If you must slow down the time between when the
server starts and this agent starts, the number of
seconds to delay startup should be entered here.
This is especially relevant on older, slower servers.
Log Level Determines what levels of logging will show up in the
log files. Available options: trace, error, debug, and
info. See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings.
Auto Restart Determines if the agent can be automatically
restarted when the configuration updates. This can
affect call stability and is enabled by default.
Agent Type Describes the type of agent this is. For WSPAuth,
the correct agent type is wsp-authentication/
polycom.mea.agent.wsp-authentication.
Roles Describes which one of multiple role types should be
assigned to an agent. Select Authentication Provider
for WSPAuth.
Experience Portal URL This field is for future product functionality. For now,
leave blank unless explicitly told to do otherwise.
Target URL This is the full URL of the Services Portal in the
format https://<admin username>:<admin password>
@<WSP address>.
Enforce Certificate Validation Check this option to verify the Services Portal’s
certificate as a security measure, Off by default.
Polycom, Inc. 81
Realms This is a comma-separated list of realms from the
AuthMatch page that are defined as valid for this
agent. By default, includes the Services Portal
address and the email domain of users who will be
logging in with Presenter rights.
Click Submit.
Configuring the DMA Settings
This section contains a table with field names and value descriptions to help you configure the DMA
settings in the Administration application.
To configure the DMA Settings
1 With the System Administration application open in your browser, select the Settings tab at the top,
and then Environment (default.local) > Agents > DMA Settings as shown next.
A partial DMA Settings screen with its initial fields displays next.
Polycom, Inc. 82
2 The DMA Settings Fields table contains a list of the fields found in the System Administration
application’s DMA Settings screen. Use the value descriptions for each field listed in the table to
determine the values you need to enter in the DMA Settings screen.
Polycom, Inc. 83
Table 21: DMA Settings Fields
Field Name Value/Description
Run Locally Specifies whether the DMA agent is running on this
server or on a remote server in accordance with the
future roadmap. For this release, this option should
ALWAYS be checked.
Startup Delay If there is a need to slow down the time between when
the server starts and this agent starts, the number of
seconds to delay startup should be entered here. This
is especially relevant on older, slower servers.
Log Level Determines what levels of logging show up in the log
files. Available options: trace, error, debug, and info.
See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog See Understanding
Log Settings.
Auto Restart Determines if the agent can be automatically restarted
when the configuration updates. This can affect call
stability and is enabled by default.
Agent Type Describes the type of agent this is. For the DMA, the
correct agent type is realpresence-platform/
polycom.ccs.agent.rp-platform.
Roles Describes which one of multiple role types should be
assigned to an agent. For the DMA, select
ExternalConferenceProvider.
Experience Portal URL This field is for future product functionality. For now,
leave blank unless explicitly instructed to do otherwise.
Target URL This is the full URL of the DMA in the format
https://<admin username>:<admin password>
@<DMA address>:8443/api/rest
Enforce Certificate Validation Check this option to verify the DMA’s certificate as a
security measure, Off by default.
Routes This is a list of routes from the Lobby Codes that the
agent has access to. The routes in this list are
separated by commas, and there are NO spaces
between any of the list elements. By default, this list
should not be changed.
Polycom, Inc. 84
Field Name Value/Description
listenurl This is the port and REST API information that the
server needs to communicate with the DMA. DO NOT
change unless explicitly instructed to.
Prefixes Enter the DMA prefix if one has been previously
configured.. Enter 0 if no prefix is used.
3 Click Submit.
Viewing Experience Portal Log Files
This section explains how to access, view, and clear your Experience Portal log files.
To access the Experience Portal log files
1 Select Maintenance > Logs > List of log files as shown next.
The List of log files screen appears.
2 Click Go.
A list of hyperlinked logs appears as shown in the following screen sample. Note the Sort by
dropdown box near the top of the screen for selecting a sorting mechanism.
Polycom, Inc. 85
3 Select any hyperlink from the list of logs to view that specific log, or right-click the hyperlink and
select Save link as.. to save that log file to another location.
To delete Experience Portal log files:
1 Select Maintenance > Logs > Clear logs.
When selected and the Go button is pressed, the older log files are cleared from the hard drive.
Applying Experience Portal Configurations
The Experience Portal must be restarted to apply your configuration settings. Restart the Experience
Portal either through the Administration tool or by rebooting the VMware console. This section explains a
restart through the Administration tool using Apply Configuration and Restart Server.
The preferred method for applying the Experience Portal configuration from the Administration tool is to
select Maintenance > Tools > Apply Configuration as in the following screen sample. Apply
configuration allows you to apply any configuration changes that have been saved from the Settings
pages. This executes the start.sh script in the Experience Portal folder on the server.
Polycom, Inc. 86
A second method for applying the Experience Portal configuration from the Administration tool is to select
Maintenance > Tools > Restart Server as shown next.
Restart Server issues the command to restart the OS to the VM. This is similar to both the VMware
command to restart the VM, and to the Linux command to reboot.
Setting System Administration UI Properties
This section explains how to set (and change) the properties of your System Administration user
interface. The Admin UI menu item applies to all subcomponents.
To access the Admin UI:
1 With the System Administration application open in your browser, select Settings > Admin UI as
shown next.
The next screen will display a list of text box fields as shown in the following partial sample screen. All of
the fields that appear in the full Admin UI are listed in the Admin UI Settings Fields table.
Polycom, Inc. 87
Table 22: Admin UI Setting Fields
Field Name Value/Description
admins
admins[0]
Provides the default internal authentication settings.
DO NOT CHANGE.
Polycom, Inc. 88
Field Name Value/Description
admins[1] Provides the credentials for the Admin UI.
admins[#] Provides additional administrator credentials. This
optional field only appears each time the +
certificates button is pressed.
certificates
SSL Certificate
Displays the raw text of the SSL identity certificate
for the server.
SSL Certificate Private Key
Displays the raw text of the private key used to
generate the certificate’s CSR.
certificates[0].usage Allows you to choose between server and trustedroot
in determining how the certificate file pair is used by
the VM.
Log Level Determines what levels of logging show up in the log
files. Available options: trace, error, debug, and info.
See Understanding Log Settings.
Log Target Determines where the log output is sent. Available
options: console, file, and syslog. See Understanding
Log Settings.
port Default port setting for accessing the Experience
Portal server’s Admin UI.
secureport Default secure port setting for accessing the
Experience Portal server’s Admin UI
Caution: Verify SSL Certificate and Private Key Validity
Ensure that both the SSL Certificate and the SSL Certificate Private Key are valid before entering and restarting the server.
To change the System Administration application password:
1 Select Settings > Admin UI. The Admin UI screen appears with two text boxes: admins[0] and
admins[1], shown next.
Polycom, Inc. 89
2 The admins[1] text box contains <username>:<password>. To change the password, delete the
value on the right of the colon and enter a new value, shown next.
3 Click Submit. The password changes.
Updating Experience Portal Software
In order to deploy an updated version of Experience Portal software you must do the following:
Obtain the new Experience Portal software OVA file
Deploy it using the instructions found in “Deploying the Services Portal and Experience Portal
Packages,”
Use the instructions that follow to migrate the provisioning and state information from the existing
server running the older software to this new instance.
Exporting the Experience Portal Configuration File
Your configurations are saved in the Experience Portal’s settings.json file. This file can be exported
from your Experience Portal server and enables you to import the file into another Experience Portal
server or to save it as a backup. The file will be downloaded and saved based on your browser’s settings.
Polycom, Inc. 90
This section explains how to export the Experience Portal settings file. For importing, see Updating
Experience Portal Software
In order to deploy an updated version of Experience Portal software you must do the following:
Obtain the new Experience Portal software OVA file
Deploy it using the instructions found in “Deploying the Services Portal and Experience Portal
Packages,”
Use the instructions that follow to migrate the provisioning and state information from the existing
server running the older software to this new instance.
Exporting the Experience Portal Configuration File
To export the Experience Portal configuration file:
1 Select Maintenance > Tools > Export Configuration as .
2 Click Go.
The setting.json configuration file downloads.
Importing the Experience Portal Configuration File
The Experience Portal’s settings.json file can be imported to your Experience Portal server. This
enables you to transfer the Experience Portal configuration settings to another Experience Portal server.
This section explains how to import the Experience Portal settings file. For exporting, see Updating
Experience Portal Software.
To deploy an updated version of Experience Portal software:
Obtain the new Experience Portal software OVA file
Deploy the software using the instructions found in Deploying the Services Portal and Experience
Portal Packages.
Use the following instructions to migrate the provisioning and state information from the existing
server running the older software to this new instance.
To import the Experience Portal:
1 Select Maintenance > Tools > Import Configuration as shown next.
Polycom, Inc. 91
The Import Configuration screen displays as shown next.
2 Select Choose File, and locate the settings.json configuration file you want to import to the
server.
3 Click Upload. The page will refresh.
Localizing the Experience Portal
You can localize the Experience Portal. Localization capabilities include:
Upload a language pack
List a language pack
Note: Experience Portal Localization Experience Portal localization is currently only supported for the user experience and not the admin portal.
To upload a language pack:
1 Select Localization > Upload language pack as shown next.
The Upload language pack screen displays:
Polycom, Inc. 92
2 Click Choose File to select a specific language pack. Navigate to where you have downloaded the
desired language pack, and click Upload to upload the language pack file.
To list a language pack
1 Select Localization > List language pack. The List language pack screen displays:
2 Click Go to list your selected language pack.
Polycom, Inc. 93
Creating and Managing User 3:
Accounts
After successfully deploying and configuring your Services Portal, create user accounts locally or add
users through the Active Directory. The account types you create depend on your account role. Super
admin accounts add and manage super admin, admin, and user accounts. Admin accounts add and
manage admin and user accounts. User accounts cannot add or manage any accounts.
This chapter shows you the following:
Understanding Account Roles
Creating Accounts
Editing Accounts
Deleting Accounts
Changing Your Password
Resetting a Password
Understanding Account Roles The Services Portal supports three different account roles. Each role determines your account type and a
different set of capabilities. See the following list for a brief description of each roll:
Super Admin Creates and manages the Services Portal settings and other super admin, admin,
and user accounts, but cannot schedule meetings. Super admin accounts display the tabs shown in
Figure 4.
Admin Creates and manages admin accounts, user accounts, and online video conference
meetings. Admin accounts display the tabs shown in Figure 5.
User Creates and manages online video conference meetings. User accounts display the tabs
shown in Figure 6.
Note: Identifying Your Roll
Logging in to the Services Portal and comparing your available tabs with the following figures is a good way to confirm your assigned roll.
Polycom, Inc. 94
Figure 4: Super Admin Role Tabs
Figure 5: Admin Role Tabs
Figure 6: User Role Tabs
Polycom, Inc. 95
Creating Accounts The Services Portal enables super admin and admin users to create accounts locally or from the Active
Directory.
This section shows you how to add active directory users and how to create local accounts.
Adding Active Directory Users
The LDAP server configuration enables access to Services Portal for all the users in the Active Directory
without requiring the administrator to explicitly create each Services Portal account. By default, the
Services Portal assigns user roles to all the Active Directory accounts. Add a user from Active Directory
only if you need to change the default user role or to block the user. To change the default user role, see
Editing Accounts Created from the Active Directory.
Note: Before You Begin
Before adding an Active Directory user account, you must log in to the Services Portal as an admin or super admin.
Adding Active Directory users:
1 Select USER MANAGEMENT. The USERS screen displays, shown next.
2 Click + LDAP USER. The Import Active Directory Users screen displays, shown next.
Polycom, Inc. 96
3 In the Import Active Directory Users search box, enter the name of the user you want to add and
tap Enter.
4 Place a checkmark in the checkbox of each user you want to add.
5 Click Add.
Note: Active Directory Default User Roles
Users added from the Active Directory are assigned the user role by default. To change the role type, see Editing Accounts.
Adding Local Users
The Services Portal enables super admin and admin users to add other local users. This section shows
you how to create local accounts.
Note: Before You Begin
Before adding a local user account, you must log in to the Services Portal as an admin or super admin.
Adding local users:
1 Select User Management. The Users screen displays.
Polycom, Inc. 97
2 Click + User. The Add a user screen displays, shown next.
Polycom, Inc. 98
3 Enter the following in the Add a user screen:
○ First Name Enter the user’s first name.
○ Last Name Enter the user’s last name.
○ User Name Enter a username for the user.
○ Email Address Enter the user’s email address.
○ Contact Number Enter the user’s phone number with area code.
○ Title Enter the user’s job title.
○ Department Enter the user’s department.
Polycom, Inc. 99
○ City Enter the user’s city.
○ User Role Click the User Role dropdown box, and choose one of the following options:
» ROLE_SUPER_ADMIN This option is only available to super admin users. When assigned,
the user has super admin capabilities, which includes creating and managing user, admin,
and super admin accounts and configuring and managing the core settings, social policy,
DMA configuration, and certificate uploads.
» ROLE_ADMIN This option is available to admin and super admin users. When assigned,
the user has admin privileges, which includes creating and managing user and admin
accounts and creating and participating in video conference meetings.
» ROLE_USER This option is available to both admin and super admin users. When
assigned, the user has standard user privileges and can only create and participate in
meetings.
4 Click Add. An email is sent to the newly created user containing their username, password, and
URL.
The Services Portal enables you to edit or delete the accounts you create. For more information, see
Editing Accounts and Deleting Accounts.
Editing Accounts The Services Portal enables admin and super admin users to edit accounts created locally and from the
Active Directory. You can access all fields in a locally created account but you can only access two fields
in an account imported from the Active Directory: the role type and the enable/lock option. This section
shows you how to edit both local and Active Directory accounts.
Editing Accounts Created from the Active Directory
This section shows you how to edit an account created from the Active Directory. Note that you can only
edit the role type and enable/lock options in accounts imported from the Active Directory. Also note that
the only super admin users can change a role type to super admin.
Note: Before You Begin
Before you edit an account, you must log in to the Services Portal as either an admin or a super admin.
To edit a user account created from the Active Directory:
1. Select User Management. The Users screen displays, shown next.
Polycom, Inc. 100
2. Enter the user’s name in the search box and tap Enter or search using the scroll bar.
3. Click the account’s icon. The Edit User screen displays, shown next.
4. To edit the User Role, click the dropdown box arrow and select one of the following options:
○ ROLE_SUPER_ADMIN This option is only available to super admin users. When assigned,
the user has super admin capabilities, which includes creating and managing user, admin, and
super admin accounts and configuring and managing the core settings, social policy, DMA
system configuration, and certificate uploads.
○ ROLE_ADMIN This option is available to admin and super admin users. When assigned, the
user has admin privileges, which includes creating and managing user and admin accounts and
creating and participating in video conference meetings.
○ ROLE_USER This option is available to both admin and super admin users. When assigned,
the user has standard user privileges and can only create and participate in meetings.
5. Click to enter a check mark in the Enable User checkbox and activate the user’s account, or
remove the check mark and disable the user’s account.
6. Click SAVE.
Polycom, Inc. 101
Editing Locally Created User Accounts
Super admin users can change all fields in a locally created account. Admin users can change all fields in
a locally created account except for the roll in a super admin account. To determine your account type,
see Understanding Account Roles.
This section shows you how to edit a locally created user account.
Note: Before You Begin
Before you edit an account, you must log in to the Services Portal as an admin or super admin.
To edit a local user account:
1. Select User Management. The Users screen displays, shown next.
2. Locate the account by entering the user’s name in the search box and tapping Enter.
Polycom, Inc. 102
3. Click the account’s icon; the Edit User screen displays, shown next.
4. Edit any of the following fields in the Edit User screen:
○ First Name Edit the user’s first name.
○ Last Name Edit the user’s last name.
○ User Name Edit a username for the user.
○ Email Address Edit the user’s email address.
○ Contact Number Edit the user’s phone number with area code.
○ Title Edit the user’s job title.
○ Department Edit the user’s department.
Polycom, Inc. 103
○ City Edit the user’s city.
○ User Role Edit the User Role by selecting one of the following options:
» ROLE_SUPER_ADMIN This option is only available to super admin users. When assigned,
the user has super admin capabilities, which include creating and managing user, admin, and
super admin accounts and configuring and managing the core settings, social policy, DMA
system configuration, and certificate uploads.
» ROLE_ADMIN This option is available to admin and super admin users. When assigned, the
user has admin privileges, which include creating and managing user and admin accounts
and creating and participating in video conference meetings.
» ROLE_USER This option is available to both admin and super admin users. When assigned,
the user has standard user privileges and can only create and participate in meetings.
○ Enable User Click to enter a check mark in the Enable User checkbox and activate the user’s
account or remove the check mark and disable the user’s account.
5. Click Save. An email is sent to the owner of the edited user account containing the username,
password, and URL.
Deleting Accounts Users with super admin accounts can delete other super admin, admin, and user accounts. Users with
admin accounts can only delete other admin and user accounts. To determine your account type, see
Understanding Account Roles.
This section shows you how to delete a user account.
Caution: Default Accounts
The following default accounts are required and cannot be deleted:
admin Used for accessing the services portal.
meaconf Used for conference communication with the Experience Portal.
meaauth Used for authentication communication with the Experience Portal.
Note: Before You Begin
Before you delete an account, you must log in to the Services Portal as an admin or super admin.
To delete a user account:
2 Select the User Management tab; the Users screen displays, shown next.
Polycom, Inc. 104
3 Locate the account by entering the user’s name in the search box and tapping Enter. The user’s
name displays with the username, email address, type, role, and status, shown next.
4 Click the account’s icon; the Delete this User? screen displays.
5 Click Delete.
Changing Your Password This section explains how to change your password.
To change your password:
1 Log into your Services Portal account. Your name appears in the top right corner of the screen.
2 Click on the icon on the left side of your name as shown next.
The Change Password screen appears as shown next.
Polycom, Inc. 105
3 Enter the following in the Change Password screen:
○ Current Password Enter your current password.
○ New Password Enter your new password.
○ Confirm new password Reenter your new password.
4 Click Change to change your password.
Resetting a Password This section shows how an admin or a super admin can reset a user’s password.
Caution: Before Resetting a Password
Passwords should only be reset for accounts with valid email addresses. Resetting a password for an account with an inactive email address will lock out the user.
Note: Before You Begin
Before you reset a password, you must log in to the Services Portal as either an admin or a super admin.
To reset a password:
5 Click User Management. The Users screen displays as shown next.
Polycom, Inc. 106
6 Locate the user in the NAME column, enter the user’s name from the USERNAME column into the
search box, and press Enter on your keypad.
7 Click the account’s icon. The Change this user’s password? dialog box displays.
8 Enter a new password in the Password field’s window, and click Change.
The Services Portal sends the user an email containing the new password.
Polycom, Inc. 107
Providing Secure Guest Access 4:
This chapter shows you how to provide invited guests with controlled access to your organization’s
Unified Communications infrastructure while preventing unwelcome intrusion.
Securing SIP Guest Access Enabling SIP guest access is the most convenient way to enable video and audio access from
organizations and individuals that are not federated with your organization. For this reason, the
CloudAXIS web client always functions in a guest mode; it neither registers nor authenticates itself with
your organization’s SIP gatekeeper (typically a Polycom DMA device). This is true even if and when it is
used by individuals who belong to your organization and/or connect from within your organizational
firewall. Similarly, the RealPresence® Mobile software endpoint for mobile devices, which has SIP
registration and authentication capabilities, does not register or authenticate with the target SIP
gatekeeper when it joins a conference in response to the user clicking on the Join Now button from the
CloudAXIS Experience Portal.
Because the CloudAXIS web client functions in guest mode, the CloudAXIS Solution requires SIP guest
access for users wanting to join meetings via the Web Client and Experience Portal. H.323 guest access
may also be provided at your discretion to facilitate access from other types of endpoints.
Enabling Guest Access on Your Edge Proxy
To enable guest access via your organization’s edge proxy device, please refer to one of the following
Polycom publications.
Note: Enabling Endpoint Authentication
It is important to follow the recommendation for enabling endpoint authentication on the applicable DMA device as described in the following guides.
See Chapter 2: Deploying the Basic RealPresence Access Director System Solution to Support
Remote and Guest Users of the Deploying Polycom® Unified Communications in RealPresence®
AccessDirector™ System Environments Guide.
See Chapter 2: Deploying the Polycom—Acme Packet Solution to Support Remote and Guest User
of the Deploying Polycom® Unified Communications in an Acme Packet® Environment Guide
Additional Recommendations for Greater Security
See the following recommendations to secure the privacy of your conferences and prevent misuse of your
videoconferencing infrastructure:
Polycom, Inc. 108
Use temporary rather than persistent (personal) VMRs when creating meetings that include
untrusted guests. This is the default Services Portal behavior used whenever the Use Personal
VMR has not been selected. Using temporary VMRs helps ensure that guests will only be able to
access the particular conference session you are inviting them to.
Use the passcode option when creating meetings to provide an additional level of access control.
Use the Services Portal DMA Config Option “Generate VMR From Range” to generate temporary
conferencing IDs in a wide, random range, thus making them more difficult to access by random
dialing.
Restrict guest users to a subset of your dialing plan. By provisioning a dialing rule for unauthorized
calls on your DMA device, you can limit guests to particular dial identifiers or ranges for which you
prefer to provide access. For example, the following preliminary script restricts guest users to the
dial ID range of 100,000 to 999,999 which could be configured to be the same auto-generation
range used by the Services Portal to create temporary VMRs:
// These values should correspond to the min and max room ID settings.
// specified in the Services Portal DMA Config Option “Generate VMR
// From Range”
var maxGeneratedRoomId = 100000;
var maxGeneratedRoomId = 999999;
var number = parseInt(DIAL_STRING.replace(/^sip:([^@]*)@?(.*)/i,"$1"));
if (NaN != number && number > minGeneratedRoomId && number <
maxGeneratedRoomId)
{
return;
}
return NEXT_RULE;
For more instructions on how to configure preliminary dialing scripts
on the DMA device, see the Polycom DMA 7000 System Operations guide on
the Polycom Support site.
Securing Web Access Conferences take place in the Experience Portal. Providing conference access to guest users joining from
outside your organization’s firewall requires allowing the Experience Portal to be accessed from the public
internet. Access to the Services Portal, however, is only required for users who create and host
conferences, which are typically members of your organization. Providing direct external access to the
Services Portal component is left to the administrator’s discretion.
There are at least two different options for providing access from external networks:
1. Configure NAT functionality in your organizational firewall, or another edge device, to map
HTTPS port 443 from the external IP address assigned for the Experience Portal to its internal IP
address. Do the same for the Services Portal (if desired).
2. Use a Reverse Proxy product to provide external HTTPS access to the Experience Portal. Do
the same for the Services Portal (if desired).
Polycom, Inc. 109
The proxy selected should support the following features:
○ Traffic routing based on HTTP host headers (required only when routing a single external IP
address to multiple internal web applications).
○ Forwarding of the Web Sockets protocol (RFC 6455).
Polycom, Inc. 110
Troubleshooting the Services Portal 5:
This chapter shows you how to resolve issues experienced by end users and how to access your log files
for troubleshooting miscellaneous issues.
This section contains troubleshooting information on the following:
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 Email Notifications
User Receives “Unable to Create a Conference with a Personal VMR” Message
User Receives “External Server Not Set” Message
Obtaining Services Portal Log Files
User Cannot Create Meetings
Confirm the following if users are unable to create a meeting:
At least one DMA system is made primary
The DMA’s owner username entered in the Services Portal also exists in the DMA system. 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.
The DMA system status is up.
There is an MCU Pool order named "Factory Pool Order" in the DMA system.
User Cannot Launch the Welcome Screen
When entering a meeting, the welcome screen launches with video options for entering the meeting. If
users are able to create a meeting but are unable to launch the welcome screen, confirm that the correct
port numbers and DMA system FQDN were entered when configuring the Experience Portal. See
Configuring the Connection to the DMA System and RPAD Servers.
Configured Components are Not Responding
If components are correctly configured but not working, try rebooting the Services Portal server.
Polycom, Inc. 111
Super Admins and Admins Cannot Add an Active Directory
User
If Services Portal Admins and Super Admins are unable to add an Active Directory user, confirm that the
proper LDAP server is configured with the correct values listed in Synchronizing Portal Timing
Both the Services Portal and the Experience Portal MUST be configured to the SAME timezone and NTP
server in order for CloudAXIS Recording to work properly.
To configure the same time zone and NTP server
1. Access the CLI (See Appendix D: CloudAXIS Restricted Shell) on either of the two portals using
‘caxis’ for both your Username and Password.
2. Select your time zone by using the CLI Command change_timezone. See Use Case - Set System
Date Time in Appendix D for details.
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 in Appendix D for details.
Repeat the above 3 steps on the other portal.
Configuring the Connection to the LDAP Server. If the problem persists, contact your IT administrator to
confirm the values are correct.
User Cannot Send Email Notifications
If users are unable to send email notifications, confirm that the proper SMTP server is configured with the
correct port numbers listed in Configuring the Connection to the SMTP Server. If the problem persists,
contact your IT administrator to confirm the values are correct.
User Receives “Unable to Create a Conference with a
Personal VMR” Message
See if the virtual meeting room exists on the configured DMA system. If it exists, contact Polycom
Support.
User Receives “External Server Not Set” Message
If receiving the “External Server Not Set” message after selecting Meet Now, confirm that the correct
FQDN is entered in the MEA Server textbox located on Services Portal’s Server Settings screen. See
Configuring Additional Server Settings.
Polycom, Inc. 112
User Receives “Video Resources Are Not Available”
Message
This error message displays if the license trial period has ended or when the concurrent license limit is
exceeded. Contact your Polycom representative to purchase as license to activate your CloudAXIS Suite
or to increase the user capacity.
Obtaining Services Portal Log Files
Obtain your Services Portal log files to troubleshoot any issues you experience. To configure your log
level and download your logs, see Selecting and Downloading Log Level.
User Cannot Download Logs on Internet Explorer
Start the Registry Editor. For a ‘per user’ setting, locate the following registry key:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\InternetSettings
For a ‘per computer’ setting, locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\InternetSettings
On the Edit menu, click Add Value and add the following value:
“BypassSSLNoCacheCheck”=Dword:00000001 Exit the Registry Editor.
Polycom, Inc. 113
Getting Help 6:
Polycom and Partner Resources For more information about installing, configuring, and administering Polycom products, refer to
Documents and Downloads at Polycom Support.
To find all Polycom partner solutions, see Polycom Strategic Global Partner Solutions.
For more information on solutions with a specific Polycom partner, see the Strategic Partner Solutions site
at Polycom Strategic Global Partner Solutions.
The Polycom Community The Polycom Community gives you access to the latest developer and support information. Participate in
discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom
Community, simply create a Polycom online account. When logged in, you can access Polycom support
personnel and participate in developer and support forums to find the latest information on hardware,
software, and partner solutions topics.
Polycom, Inc. 114
A: Creating a Google Talk™ App
Enabling access to Google Talk™ contacts from the Experience Portal requires creating a Google Talk™
app, selecting the Google Talk™ checkbox in the Services Portal’s Social Connector configuration
screen, and entering the app’s Client ID and Client Secret in the respective Social Connector
configuration screen text boxes. To access the Services Portal social connector configuration screen, see
Configuring Social Policies. To get the Client ID and Client Secret, see step 10 of the following
instructions.
Before you begin, set up a neutral account with credentials that can be shared among different persons in
your team. Do not use your personal account to create the app. This helps to avoid dependencies on a
single person. In case a person currently in charge of the application maintenance leaves the company,
the common account credentials can be passed on to the team.
In addition, always maintain one-to-one mapping between the Services Portal server and the application
being used.
Note: IP Address Change
A change in the server’s IP does not require a new application to be created as long as the FQDN points to the changed IP.
Note: Reference for Creating a Google App
As you create your Google app, you can use the Google Developers Page as a reference.
To create a Google Talk™ app:
1 Log into the shared Google account.
2 Open the Google APIs Console page and select Create Project. The Google APIs page opens
with menu options displayed on the left, shown next.
3 Click the API Project dropdown menu, and select Create as shown next.
Polycom, Inc. 115
The Create Project dialog box displays, shown next.
4 Enter a name in the Enter the name for your project text entry box and click Create Project. An
example shown next
The Google APIs page dropdown menu name should change to the name of your project as shown
next. If the name does not automatically display, click the dropdown box arrow, and select it from
the Recent Projects list.
Polycom, Inc. 116
5 Select API Access from the menu options, shown next.
6 Click Create an OAuth 2.0 Client ID… The Create Client ID screen displays, shown next.
Polycom, Inc. 117
7 Enter the following:
○ Product Name Enter your product name. Naming with the prefix “CloudAXIS_” is
recommended.
○ Product Logo Enter the URL to your product logo.
○ Home Page URL Enter the URL to your home page.
8 Click Next. The Client ID Settings options display, shown next.
Polycom, Inc. 118
9 Select the following
○ Application Type Select Web-Application.
○ Your Site or Hostname Enter the Services Portal’s FQDN
10 Click Create Client ID. The Authorized API Access screen displays, shown next
Polycom, Inc. 119
Note the Client ID and Client secret; these are both needed for the policy configuration. It is
important to note that your client secret is always kept secret.
11 In the Authorized API Access screen, click Edit settings, the Edit Client Settings screen displays,
shown next.
Polycom, Inc. 120
12 In the Authorized Redirect URIs text box, enter
https://<ServicesPortalFQDN>/wsp/oauth/callback-google and click Update.
You are now ready to configure the Google Talk™ policy on the server. See Configuring Social Policies.
Polycom, Inc. 121
B: Creating a Facebook App
Enabling access to Facebook contacts from the Experience Portal requires creating a Facebook app,
selecting the Facebook checkbox in the Services Portal’s Social Connector configuration screen, and
entering the App ID and App Secret in the respective Social Connector configuration screen text boxes.
To access the Services Portal social connector configuration screen, see Configuring Social Policies. To
get the App ID and App Secret, see step 4 in the following instructions.
Before you begin, set up a neutral Facebook developer account with credentials that can be shared
among different persons in your team. Do not use your personal Facebook account to create the app.
This helps to avoid dependencies on a single person. In case a person currently in charge of the
application maintenance quits the job, the common account credentials can be passed on to the team. To
verify if your account is a developer account, see the Facebook help page.
Also, always maintain one-to-one mapping between the Services Portal server and the application being
used.
Note: IP Address Change
A change in the server’s IP does not require a new application to be created as long as the FQDN points to the changed IP.
Note: Reference for Creating a Facebook App
As you create your app, you can use the Facebook Developers page as reference.
To create a Facebook app:
1 Log into the shared Facebook account.
2 Open the Facebook Developers page. The Facebook Developers screen displays. From the menu
at the top of the page, click Apps (shown next).
If your Facebook account is not already registered as a developer, you will see an option for
Register as a Developer. Select Register as a Developer, complete the registration process, and
continue.
3 Select Create New App, the Create New App screen displays, shown next.
Polycom, Inc. 122
4 Enter a suitable name in the App Name text box (naming with the prefix “CloudAXIS_” is
recommended) and click Continue. The Sample App screen displays with the App ID and App
Secret as shown next. Make a note of these for configuring the Services Portal policy.
5 Select Website with Facebook, shown next
The Site URL text box appears, shown next
Polycom, Inc. 123
6 In the Site URL text box, enter https://<ServicesPortalFQDN>/
7 Select App on Facebook, shown next.
The Basic Info screen appears, shown next.
8 Enter the following:
○ Canvas URL Enter http://<ServicesPortalFQDN>/.
○ Secure Canvas Width Enter https://<ServicesPortalFQDN>/.
9 In the Basic Info options, shown next, enter the <ServicsPortalFQDN>.
Polycom, Inc. 124
You are now ready to configure the Facebook policy on the server. See Configuring Social Policies.
Polycom, Inc. 125
C: DMA Factory Conference Settings
Impact
The Polycom DMA system uses conference templates and global conference settings to manage
conference behavior. This table describes the impact of the DMA system’s factory conference template
settings on the CloudAXIS web client operations. For information on setting up a DMA system conference
template, see the Polycom DMA 7000 System Operations Guide on the Polycom Support site.
Table21: Conference Template Settings Impact
Feature Subfeature Subfeature Description Web Client Behavior
General Settings Profile Settings Use existing profile N/A
RMX profile name N/A
Conference Settings
Conference Mode
Only AVC is supported.
This can be set to 'AVC
only' or 'Mixed AVC and
SVC'. For both options,
the web client will use
AVC.
Cascade for bandwidth Works as documented
Video Switching Works as documented
H.264 High Profile Works as documented
Resolution Works as documented
Line Rate Fixed rate in web client
Audio Only Not tested
Advanced Settings
Encryption Tied to the url scheme
– OFF for http / ON for
https
LRP Works as documented
Video Quality People Video Definition
Video Quality Works as documented
Max resolution Works as documented
Video Clarity Works as documented
Polycom, Inc. 126
Feature Subfeature Subfeature Description Web Client Behavior
Auto Brightness Works as documented
Content Video
Definition
Content Settings Works as documented
Content Protocol Works as documented
Video Settings
Presentation Mode Works as documented.
Send content to legacy
endpoints
No Impact
Same layout Works as documented
Lecture view switching Works as documented.
Auto layout Works as documented
Layout Works as documented
Telepresence Mode Works as documented
Telepresence layout
mode
Works as documented
Audio Settings
Echo suppression Works as documented
Keyboard noise
suppression Works as documented
Audio Clarity Works as documented
Skins Works as documented
Conference IVR
Override default service Advanced – see the
DMA guide.
Conference IVR
Service
May require use of
DTMF pad in menu.
Polycom, Inc. 127
Feature Subfeature Subfeature Description Web Client Behavior
Conference requires
chairperson
Enterprise users should
be admitted to the
conference; they will
need to use DTMF to
enter the chair pin
again to start the video
portion of the call.
Anonymous users
without the chair pin
must wait in the web
outer lobby.
Recording
Record Conference
Must be set to
'Immediately’ or 'Upon
Request' to enable
recording.
Recording Link Must be configured to
enable recording.
Audio only Works as documented
Indication of recording
Works as documented
Note If enabled, a
recording indication will
appear in both the
video feed and in the
web client GUI
Polycom, Inc. 128
D: CloudAXIS Restricted Shell
Introduction The Polycom CloudAXIS Restricted Shell provides a means for you to log in to CloudAXIS products from
either a console or via an SSH connection and perform the below operations:
Execute a limited set of restricted commands
View log files
Collect log files as a .tar.gz package
Change Hostname
Change password for the 'caxis' user
Change the time zone of the system
Change NTP settings
Regenerate certificates
Restart services
View product information (like Version number)
SCP files (restricted access) to other machines
Usage Sample Use Cases of restrictedshell are described below for reference.
Use Case - Login as 'caxis' via Console or via a SSH
Connection
Admin Tip: CLI Login Login to the CLI with ‘caxis’ as both your username and password.
Welcome to the Polycom RealPresence CloudAXIS Command Line Interface (CLI).
Type '?' for help
Supported commands:
Cat
Find
Grep
Polycom, Inc. 129
Ls
Pwd
Vi
regenerate_certificates
change_hostname
collect_logs
change_network_settings
change_ntp
show_network_info
change_password
show_product_info
change_timezone
ifconfig
reboot
service
openssl
scp
tail
ntpdate
cd
echo
exit
Use Case - Change System Hostname [email protected]: change_hostname
Current System Hostname: localhost.localdomain
Do you want to change the system hostname? [y/n]: y
New System Hostname: polycom-cloudaxis
Hostname changed successfully.
Use Case - Log Collection caxis@polycom-cloudaxis: collect_logs
Log collection completed successfully.
Location of log file:
/home/caxis/log/plcm_caxis_logs_2013_03_26_16_59_50.tar.gz
Polycom, Inc. 130
Use Case - Copying the generated logs to a different server caxis@polycom-cloudaxis:
scp/home/caxis/log/plcm_caxis_logs_2013_03_26_16_59_50.tar.gz
[email protected]:/var/log/cloudaxis_logs
The authenticity of host '10.250.92.60 (10.250.92.60)' can't be
established.
RSA key fingerprint is fd:fd:94:17:62:87:37:5f:59:7b:f8:ad:c2:4a:47:40.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.250.92.60' (RSA) to the list of known hosts.
[email protected]'s password:
plcm_caxis_logs_2013_03_26_16_59_50.tar.gz 100% 155KB 154.7KB/s 00:00
Use Case - Access Log Files caxis@polycom-cloudaxis: ls -Rm /var/log/
/var/log/:
ActivateSecurity.sh.log, ConsoleKit, K99vm_network_fix.log,
S02vm_network_fix.log, anaconda.ifcfg.log, anaconda.log,
anaconda.program.log, anaconda.storage.log, anaconda.syslog,
anaconda.yum.log, audit,
boot.log, btmp, caxis-edge-service-portal-db-config.pg.log, caxis-edge-
service-portal-fts.log, caxis-restricted-shell, caxis-restricted-shell-
fts.log, cron, cups, dmesg, dmesg.old, dracut.log, exim, lastlog,
maillog, messages, nginx, ntpstats, pgsql, secure, spooler, tallylog,
tomcat6, wtmp
/var/log/caxis-restricted-shell:
caxis-2013_03_26_15_29_01.log, caxis-2013_03_26_16_41_50.log, caxis-
2013_03_26_16_55_27.log
/var/log/cups:
/bin/ls: cannot open directory /var/log/exim: Permission denied
/var/log/nginx:
access.log, error.log
/var/log/ntpstats:
/var/log/tomcat6:
catalina.2013-03-26.log, catalina.out, cloudaxis_wsp.log, host-
manager.2013-03-26.log, localhost.2013-03-26.log, manager.2013-03-26.log,
migration.log, tomcat6-initd.log
Use Case - Changing Password of the 'caxis' User caxis@polycom-cloudaxis: change_password
Do you want to change the password for the 'caxis' user? [y/n]: y
New Password (not dispalyed on screen for security):
Changing password for user caxis.
passwd: all authentication tokens updated successfully.
Polycom, Inc. 131
Password for the 'caxis' changed successfully.
Use Case - Configure System NTP Settings caxis@polycom-cloudaxis: change_ntp
List of NTP servers configured in the system:
0.centos.pool.ntp.org
1.centos.pool.ntp.org
2.centos.pool.ntp.org
Do you want to change the list of NTP servers? [y/n]: y
Specify a space separated list of new NTP servers after the prompt below.
Please wait ...
List of new NTP servers: 0.north-america.pool.ntp.org 1.north-
america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-
america.pool.ntp.org
Checking if the new NTP servers are reachable ...
0.north-america.pool.ntp.org: reachable.
1.north-america.pool.ntp.org: reachable.
2.north-america.pool.ntp.org: reachable.
3.north-america.pool.ntp.org: reachable.
Do you want to continue updating the system NTP configuration? [y/n]: y
Verifying NTP datetime sync with the server in the new list ...
0.north-america.pool.ntp.org: successful.
1.north-america.pool.ntp.org: successful.
2.north-america.pool.ntp.org: successful.
3.north-america.pool.ntp.org: successful.
System NTP configuration updated successfully.
Use Case - Quick Sync System date-time with a Specific NTP
server caxis@polycom-cloudaxis: ntpdate -u 1.oceania.pool.ntp.org
26 Mar 12:47:56 ntpdate[12378]: adjust time server 27.54.95.11 offset
0.020587 sec
Use Case - Show Product Version caxis@polycom-cloudaxis: show_product_info
Product Version: 1.1.0.46-112007
Polycom, Inc. 132
Use Case - Regeneration of Certificates caxis@polycom-cloudaxis: regenerate_certificates
Certificate regenerated successfully.
Webserver and associated services should be restarted for the certificates
to take effect.
Do you want to restart the webserver? [y/n]: y
Restarting the Webserver. Please wait ...
Stopping tomcat6: [ OK ]
Starting tomcat6: [ OK ]
Stopping nginx: [ OK ]
Starting nginx: [ OK ]
Certificate regenerated and restarted the required services successfully.
Use Case - Change System Timezone caxis@polycom-cloudaxis: change_timezone
Current System Timezone: America/Denver
Do you want to change the system timezone? [y/n]: y
Select a timezone from the list below and specify the number listed within
the [].
Press the Return key to display the list ..
Pressing the return key will display a sorted list of time-zones (paginated) to choose from.
[1]: Africa
[2]: Africa/Abidjan
[3]: Africa/Accra
[4]: Africa/Addis_Ababa
[5]: Africa/Algiers
[6]: Africa/Asmara
[7]: Africa/Asmera
[8]: Africa/Bamako
[9]: Africa/Bangui
[10]: Africa/Banjul
[11]: Africa/Bissau
[12]: Africa/Blantyre
--More--
[..truncated to conserve space on the wiki page..]
--More--
[590]: US/Central
[591]: US/Eastern
[592]: US/East-Indiana
[593]: US/Hawaii
[594]: US/Indiana-Starke
[595]: US/Michigan
Polycom, Inc. 133
[596]: US/Mountain
[597]: US/Pacific
[598]: US/Samoa
[599]: UTC
[600]: WET
[601]: W-SU
[602]: Zulu
Choose a timezone (specify the number within []): 590
Timezone updated successfully.
Use Case - Restarting Services caxis@polycom-cloudaxis: service tomcat6 restart
Stopping tomcat6: [ OK ]
Starting tomcat6: [ OK ]
Use Case - Set System Date Time caxis@localhost: change_system_datetime
Current System Date and Time: Mon Jun 24 20:27:27 UTC 2013
Do you want to change the system Date and Time? [y/n]: y
Note: Timezone of the system will not be changed. Use 'change_timezone'
command to change the system timezone.
New System Date Time (format: Mon Jun 24 20:27:30 UTC 2013): Mon Jun 17
20:27:27 UTC 2013
System date and time set to '' successfully.
caxis@localhost: change_system_datetime
Current System Date and Time: Mon Jun 17 20:27:36 UTC 2013
Do you want to change the system Date and Time? [y/n]: n
caxis@localhost: change_system_datetime
Current System Date and Time: Mon Jun 17 20:27:43 UTC 2013
Do you want to change the system Date and Time? [y/n]: y
Note: Timezone of the system will not be changed. Use 'change_timezone'
command to change the system timezone.
New System Date Time (format: Mon Jun 17 20:27:47 UTC 2013):
Cannot apply empty date and time value.
Please specify new system date and time using the format: Mon Jun 17
20:27:47 UTC 2013 and try again.
caxis@localhost:
Polycom, Inc. 134
Use Case - View System Network Information [email protected]: show_network_info
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.117"
SUBNET_MASK="255.255.252.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Use Case - System Network Configuration is already set to
use DHCP caxis@polycom-cloudaxis: change_network_settings
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="polycom-cloudaxis"
IPv4="10.250.88.107"
SUBNET_MASK="255.255.252.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Do you want to disable DHCP and configure static network settings? [y/n]: n
Do you want to change the DNS settings of the system? [y/n]: n
Polycom, Inc. 135
Use Case - Enabling DHCP in a machine where DHCP is not
enabled [email protected]: change_network_settings
System Network Settings:
DHCP Status="Not Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.109"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
IPADDR=10.250.88.109
NETMASK=255.255.255.0
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Do you want to enable DHCP? [y/n]: y
DHCP enabled successfully.
Do you want to change the DNS settings of the system? [y/n]: n
Do you want to restart network for the network settings changes to take
effect? [y/n]: n
Use Case - Configuring Static IP Address in a System where
DHCP is in an 'Enabled' state [email protected]: change_network_settings
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.109"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
Polycom, Inc. 136
DNS Information:
DOMAIN=""
DNS Servers:
Do you want to disable DHCP and configure static network settings? [y/n]: y
Static IP Address: 10.250.88.107
Static Subnet Mask Address: 255.255.255.0
Gateway Address: 10.250.88.1
DHCP is disabled and static network settings configured successfully.
Do you want to change the DNS settings of the system? [y/n]: y
Search Domain: polycom.com
Primay DNS Address: 172.21.6.161
Secondary DNS Address: 172.21.5.204
Do you prefer to configure the Tertiary DNS Address? [y/n]: n
Updating the DNS setting in the system. Please wait ...
DNS configuration updated successfully.
Do you want to restart network for the network settings changes to take
effect? [y/n]: y
Note: You may lose connectivity if you are logged in via a SSH connection
and if the IP address of the system changes as part of network restart.
Restarting network interface for the DHCP changes to take effect.
You may experience intermittent connectivity failure while the system
network inteface is being restarted ...
Shutting down interface eth0:
-- Network Connectivity to 10.250.88.109 is lost here as the new IP address
would have come to effect --
-- Connecting to new IP - 10.250.88.107 - via a SSH connection --
ssh 10.250.88.107 -l caxis
Warning: Permanently added '10.250.88.107' (RSA) to the list of known
hosts.
[email protected]'s password:
Welcome to the Polycom RealPresence CloudAxis Command Line Interface
Type '?' for help
[email protected]: show_network_info
System Network Settings:
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.107"
Polycom, Inc. 137
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
IPADDR=10.250.88.107
NETMASK=255.255.255.0
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Use Case - Configuring Static IP Address in a system where
DHCP is in a 'Disabled' state [email protected]: change_network_settings
System Network Settings:
DHCP Status="Not Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.109"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN=""
DNS Servers:
Do you want to enable DHCP? [y/n]: n
Do you want to update the static network settings? [y/n]: y
Static IP Address: 10.250.88.107
Static Subnet Mask Address: 255.255.255.0
Gateway Address: 10.250.88.1
DHCP is disabled and static network settings configured successfully.
Do you want to change the DNS settings of the system? [y/n]: y
Search Domain: polycom.com
Polycom, Inc. 138
Primay DNS Address: 172.21.6.161
Secondary DNS Address: 172.21.5.204
Do you prefer to configure the Tertiary DNS Address? [y/n]: n
Updating the DNS setting in the system. Please wait ...
DNS configuration updated successfully.
Do you want to restart network for the network settings changes to take
effect? [y/n]: y
Note: You may lose connectivity if you are logged in via a SSH connection
and if the IP address of the system changes as part of network restart.
Restarting network interface for the DHCP changes to take effect.
You may experience intermittent connectivity failure while the system
network inteface is being restarted ...
Shutting down interface eth0:
-- Network Connectivity to 10.250.88.109 is lost here as the new IP address
would have come to effect --
-- Connecting to new IP - 10.250.88.107 - via a SSH connection --
ssh 10.250.88.107 -l caxis
Warning: Permanently added '10.250.88.107' (RSA) to the list of known
hosts.
[email protected]'s password:
Welcome to the Polycom RealPresence CloudAxis Command Line Interface
Type '?' for help
[email protected]: show_network_info
System Network Settings:
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.107"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
IPADDR=10.250.88.107
NETMASK=255.255.255.0
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
Polycom, Inc. 139
172.21.6.161
172.21.5.204
Use Case - Configuring Static IP Address in a system where
DHCP is in a 'Disabled' state with the currently assigned IP
address [email protected]: change_network_settings
System Network Settings:
DHCP Status="Not Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.109"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN=""
DNS Servers:
Do you want to enable DHCP? [y/n]: n
Do you want to update the static network settings? [y/n]: y
Static IP Address: 10.250.88.109
10.250.88.109 is pingable. Not recommended for use as it may cause a
conflict.
Do you still prefer to use the same IP? [y/n]: n
Please use an unused IP. Network settings are partially configured. Please
try again.
Static IP Address: 10.250.88.109
10.250.88.109 is pingable. Not recommended for use as it may cause a
conflict.
Do you still prefer to use the same IP? [y/n]: y
Static Subnet Mask Address: 255.255.255.0
Gateway Address: 10.250.88.1
DHCP is disabled and static network settings configured successfully.
Do you want to change the DNS settings of the system? [y/n]: y
Search Domain: polycom.com
Polycom, Inc. 140
Primay DNS Address: 172.21.6.161
Secondary DNS Address: 172.21.5.204
Do you prefer to configure the Tertiary DNS Address? [y/n]: n
Updating the DNS setting in the system. Please wait ...
DNS configuration updated successfully.
Do you want to restart network for the network settings changes to take
effect? [y/n]: y
Note: You may loose connectivity if you are logged in via a SSH connection
and if the IP address of the system changes as part of network restart.
Restarting network interface for the DHCP changes to take effect.
You may experience intermittent connectivity failure while the system
network inteface is being restarted ...
Shutting down interface eth0:
-- Network Connectivity to 10.250.88.109 is lost here as the new IP address
would have come to effect --
-- Connecting to new IP - 10.250.88.109 - via a SSH connection --
ssh 10.250.88.109 -l caxis
Warning: Permanently added '10.250.88.109' (RSA) to the list of known
hosts.
[email protected]'s password:
Welcome to the Polycom RealPresence CloudAxis Command Line Interface
Type '?' for help
[email protected]: show_network_info
System Network Settings:
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.109"
SUBNET_MASK="255.255.255.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
IPADDR=10.250.88.107
NETMASK=255.255.255.0
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
Polycom, Inc. 141
172.21.6.161
172.21.5.204
Use Case - Attempting to configure manual DNS settings
while DHCP is enabled in the system caxis@polycom-cloudaxis: change_network_settings
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="polycom-cloudaxis"
IPv4="10.250.88.107"
SUBNET_MASK="255.255.252.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Do you want to disable DHCP and configure static network settings? [y/n]: n
Do you want to change the DNS settings of the system? [y/n]: y
Found that DHCP is enabled in the system. The DHCP client may overwrite
your changes during network restart or system reboot.
Changing system DNS configuration change is not supported in this stage.
Please 'disable' DHCP and try again.
Use Case - Using invalid Network values [root@polycom-cloudaxis caxis]# bash
/opt/polycom/caxis/restrictedshell/utils/network/change_network_settings --
logfile /tmp/log
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="polycom-cloudaxis"
IPv4="10.250.88.107"
SUBNET_MASK="255.255.252.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
Polycom, Inc. 142
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Do you want to disable DHCP and configure static network settings? [y/n]: y
Static IP Address: 1234.5.6.7
Invalid IP address - 1234.5.6.7. Please specify a valid one.
Static IP Address: 10.250.88.108
Static Subnet Mask Address: 700.800.900.0
Invalid Subnet Mask Address - 700.800.900.0. Please specify a valid one.
Static Subnet Mask Address: 255.255.255.0
Gateway Address: 10.250.88.1
DHCP is disabled and static network settings configured successfully.
Restarting network interface for the DHCP changes to take effect.
You may experience intermittent connectivity failure while the system
network inteface is being restarted ...
Shutting down interface eth0:
-- Connectivity will be lost here if you are using the machine via a SSH
connection as the IP address would have changed --
Use Case - Using an IP that is already assigned to some
machine in the same network [email protected]: change_network_settings
System Network Settings:
DHCP Status="Enabled"
HOSTNAME="localhost.localdomain"
IPv4="10.250.88.117"
SUBNET_MASK="255.255.252.0"
DEFAULT_GATEWAY="10.250.88.1"
DEVICE="eth0"
BOOTPROTO="dhcp"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
Polycom, Inc. 143
DNS Information:
DOMAIN="polycom.com"
DNS Servers:
172.21.6.161
172.21.5.204
Do you want to disable DHCP and configure static network settings? [y/n]: y
Static IP Address: 10.250.88.117
10.250.88.117 is pingable. Cannot use it as it would may cause conflicts.
Please use a non-used IP. Network settings are partially configured. Please
try again.
Static IP Address: 10.250.88.197
....
Use Case - Installation of PAP (Polycom Auxiliary Package) [email protected]: install_pap
---- Polycom Auxiliary Package Installer ----
Location of the PAP file:
Server: 10.250.92.60
Username: root
Absolute path of the PAP file: /tmp/enable-root-account/plcm-caxis-aux-
pkg-enable-root-account-1.0.0.5-112589.pap
Verifying if plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap is
already installed. Please wait ...
Attempting to download plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-
112589.pap from 10.250.92.60 as root. Please wait ...
[email protected]'s password:
plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap 100% 4916 4.8KB/s
00:00
Installing plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap.
Please wait ...
plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap - install -
completed successfully.
Polycom, Inc. 144
Use Case - Forced Installation of PAP (Polycom
Auxiliary Package)
[email protected]: install_pap
---- Polycom Auxiliary Package Installer ----
Location of the PAP file:
Server: 10.250.92.60
Username: root
Absolute path of the PAP file: /tmp/enable-root-account/plcm-caxis-aux-
pkg-enable-root-account-1.0.0.5-112589.pap
Verifying if plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap is
already installed. Please wait ...
plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap is already
installed in the system.
Do you prefer to attempt a forced installation of plcm-caxis-aux-pkg-
enable-root-account-1.0.0.5-112589.pap? [y/n]: y
Attempting to download plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-
112589.pap from 10.250.92.60 as root. Please wait ...
[email protected]'s password:
plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-112589.pap 100% 4916 4.8KB/s
00:00
Attempting an upgrade of plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-
112589.pap. Please wait ...
Forced Installation of plcm-caxis-aux-pkg-enable-root-account-1.0.0.5-
112589.pap completed successfully.
Use Case - Reboot System caxis@polycom-cloudaxis: reboot
Broadcast message from root@polycom-cloudaxis
(/dev/pts/0) at 12:50 ...
The system is going down for reboot NOW!
Use Case - Exit Restricted Shell caxis@polycom-cloudaxis: exit
Polycom, Inc. 145
Use Case - Login Timeout:
Timeout. Logging off user.
Polycom, Inc. 146
E: Third-Party Software
This chapter provides the copyright statements for third-party software products that have been
incorporated into the Polycom® RealPresence
® CloudAXIS
™ Suite application distribution.
Table 2: Third-Party Software
Product License Location
CentOS CentOS
Nginx Nginx
Node js Node js
CentOS
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program
Polycom, Inc. 147
or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
Polycom, Inc. 148
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM
Polycom, Inc. 149
AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
One line to give the program's name and an idea of what it does.
Copyright (C) yyyy name of author
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public
License. Of course, the commands you use may be called something other than `show w' and `show c'; they
could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
signature of Ty Coon, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is
what you want to do, use the GNU Lesser General Public License instead of this License.
Nginx
Copyright Joyent, Inc. and other Node contributors. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
Polycom, Inc. 150
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
====
This license applies to all parts of Node that are not externally maintained libraries. The externally maintained libraries used by Node are:
- V8, located at deps/v8. V8's license follows:
"""
This license applies to all parts of V8 that are not externally maintained libraries. The externally maintained libraries used by V8 are:
- PCRE test suite, located in test/mjsunit/third_party/regexp-pcre.js. This is based on the test suite from PCRE-7.3, which is copyrighted by the University of Cambridge and Google, Inc. The copyright notice and license are embedded in regexp-pcre.js.
- Layout tests, located in test/mjsunit/third_party. These are based on layout tests from webkit.org which are copyrighted by Apple Computer, Inc. and released under a 3-clause BSD license.
- Strongtalk assembler, the basis of the files assembler-arm-inl.h, assembler-arm.cc, assembler-arm.h, assembler-ia32-inl.h, assembler-ia32.cc, assembler-ia32.h, assembler-x64-inl.h, assembler-x64.cc, assembler-x64.h, assembler-mips-inl.h, assembler-mips.cc, assembler-mips.h, assembler.cc and assembler.h.
This code is copyrighted by Sun Microsystems Inc. and released under a 3-clause BSD license.
- Valgrind client API header, located at third_party/valgrind/valgrind.h
This is release under the BSD license.
These libraries have their own licenses; we recommend you read them, as their terms may differ from the terms below.
Copyright 2006-2012, the V8 project authors. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- C-Ares, an asynchronous DNS client, located at deps/cares. C-Ares licensefollows:
"""
Copyright 1998 by the Massachusetts Institute of Technology.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is"without express or implied warranty.
"""
- OpenSSL located at deps/openssl. OpenSSL is cryptographic software writtenby Eric Young ([email protected]) to provide SSL/TLS encryption. OpenSSL's license follows:
Polycom, Inc. 151
"""
====================================================================
Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This product includes cryptographic software written by Eric Young ([email protected]).
This product includes software written by Tim Hudson ([email protected]).
"""
HTTP Parser, located at deps/http_parser. HTTP Parser's license follows:
"""
http_parser.c is based on src/http/ngx_http_parse.c from NGINX copyright Igor Sysoev.
Additional changes are licensed under the same terms as NGINX and copyright Joyent, Inc. and other Node contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"""
- Closure Linter is located at tools/closure_linter. Closure's license follows:
"""
Copyright (c) 2007, Google Inc.
All rights reserved.
Polycom, Inc. 152
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- tools/cpplint.py is a C++ linter. Its license follows:
"""
Copyright (c) 2009 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- lib/punycode.js is copyright 2011 Mathias Bynens http://mathiasbynens.be/ and released under the MIT license.
"""
* Punycode.js <http://mths.be/punycode>
* Copyright 2011 Mathias Bynens <http://mathiasbynens.be/>
* Available under MIT license <http://mths.be/mit>
"""
- tools/gyp. GYP is a meta-build system. GYP's license follows:
"""
Copyright (c) 2009 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Polycom, Inc. 153
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- Zlib at deps/zlib. zlib's license follows:
"""
zlib.h -- interface of the 'zlib' general purpose compression library
version 1.2.4, March 14th, 2010
Copyright (C) 1995-2010 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly
Mark Adler
"""
- npm is a package manager program located at deps/npm.
npm's license follows:
"""
Copyright 2009-2012, Isaac Z. Schlueter (the "Original Author")
All rights reserved.
MIT +no-false-attribs License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Distributions of all or part of the Software intended to be used by the recipients as they would use the unmodified Software, containing modifications that substantially alter, remove, or disable functionality of the Software, outside of the documented configuration mechanisms provided by the Software, shall be modified such that the Original Author's bug reporting email addresses and urls are either replaced with the contact information of the parties responsible for the changes, or removed entirely.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Polycom, Inc. 154
Except where noted, this license applies to any and all software programs and associated documentation files created by the Original Author, when distributed with the Software.
"Node.js" and "node" trademark Joyent, Inc. npm is not officially part of the Node.js project, and is neither owned by nor officially affiliated with Joyent, Inc.
Packages published in the npm registry are not part of npm itself, are the sole property of their respective maintainers, and are not covered by this license.
"npm Logo" created by Mathias Pettersson and Brian Hammond, used with permission.
"Gubblebum Blocky" font
Copyright (c) 2007 by Tjarda Koster, http://jelloween.deviantart.com included for use in the npm website and
documentation, used with permission.
This program uses "node-uuid", Copyright (c) 2010 Robert Kieffer, according to the terms of the MIT license.
This program uses "request", Copyright (c) 2011 Mikeal Rogers, according to the terms of the Apache license.
This program uses "mkdirp", Copyright (c) 2010 James Halliday, according to the terms of the MIT/X11 license.
"""
- tools/doc/node_modules/marked. Marked is a Markdown parser. Marked's license follows:
"""
Copyright (c) 2011-2012, Christopher Jeffrey (https://github.com/chjj/)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"""
- test/gc/node_modules/weak. Node-weak is a node.js addon that provides garbage collector notifications. Node-weak's license follows:
"""
Copyright (c) 2011, Ben Noordhuis <[email protected]>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
"""
- src/ngx-queue.h. ngx-queue.h is taken from the nginx source tree. nginx's license follows:
"""
Copyright (C) 2002-2012 Igor Sysoev
Copyright (C) 2011,2012 Nginx, Inc.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Polycom, Inc. 155
THIS SOFTWARE IS PROVIDED BY AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- wrk is located at tools/wrk. wrk's license follows:
"""
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of
Polycom, Inc. 156
their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, providedthat such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks.
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Polycom, Inc. 157
Node js Copyright Joyent, Inc. and other Node contributors. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
====
This license applies to all parts of Node that are not externally maintained libraries. The externally maintained libraries used by Node are:
- V8, located at deps/v8. V8's license follows:
"""
This license applies to all parts of V8 that are not externally maintained libraries.The externally maintained libraries used by V8 are:
- PCRE test suite, located in test/mjsunit/third_party/regexp-pcre.js.This is based on the test suite from PCRE-7.3, which is copyrighted by the University of Cambridge and Google, Inc.The copyright notice and license are embedded in regexp-pcre.js.
- Layout tests, located in test/mjsunit/third_party.These are based on layout tests from webkit.org which are copyrighted by Apple Computer, Inc. and released under a 3-clause BSD license.
- Strongtalk assembler, the basis of the files assembler-arm-inl.h, assembler-arm.cc, assembler-arm.h, assembler-ia32-inl.h, assembler-ia32.cc, assembler-ia32.h, assembler-x64-inl.h,assembler-x64.cc, assembler-x64.h, assembler-mips-inl.h, assembler-mips.cc, assembler-mips.h, assembler.cc and assembler.h.
This code is copyrighted by Sun Microsystems Inc. and released under a 3-clause BSD license.
- Valgrind client API header, located at third_party/valgrind/valgrind.h
This release is under the BSD license.
These libraries have their own licenses; we recommend you read them as their terms may differ from the terms below.
Copyright 2006-2012, the V8 project authors. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- C-Ares, an asynchronous DNS client, located at deps/cares. C-Ares license follows:
"""
Polycom, Inc. 158
Copyright 1998 by the Massachusetts Institute of Technology.
* Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
* M.I.T. makes no representations about the suitability of * this software for any purpose.It is provided "as is" without express or implied warranty.
"""
- OpenSSL located at deps/openssl. OpenSSL is cryptographic software written by Eric Young ([email protected]) to provide SSL/TLS encryption. OpenSSL's license follows:
"""
====================================================================
Copyright (c) 1998-2011 The OpenSSL Project.All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This product includes cryptographic software written by Eric Young ([email protected]).This product includes software written by Tim Hudson ([email protected]).
"""
- HTTP Parser, located at deps/http_parser. HTTP Parser's license follows:
"""
http_parser.c is based on src/http/ngx_http_parse.c from NGINX copyright Igor Sysoev. Additional changes are licensed under the same terms as NGINX and copyright Joyent, Inc. and other Node contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
Polycom, Inc. 159
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"""
- Closure Linter is located at tools/closure_linter. Closure's license follows:
"""
Copyright (c) 2007, Google Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- tools/cpplint.py is a C++ linter. Its license follows:
"""
Copyright (c) 2009 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- lib/punycode.js is copyright 2011 Mathias Bynens http://mathiasbynens.be/ and released under the MIT license.
"""
Punycode.js <http://mths.be/punycode>
Copyright 2011 Mathias Bynens <http://mathiasbynens.be/>
Available under MIT license <http://mths.be/mit>
"""
- tools/gyp. GYP is a meta-build system. GYP's license follows:
Polycom, Inc. 160
"""
Copyright (c) 2009 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- Zlib at deps/zlib. zlib's license follows:
"""
zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.4, March 14th, 2010
Copyright (C) 1995-2010 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty.In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly
Mark Adler
"""
- npm is a package manager program located at deps/npm. npm's license follows:
"""
Copyright 2009-2012, Isaac Z. Schlueter (the "Original Author")
All rights reserved.
MIT +no-false-attribs License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
Distributions of all or part of the Software intended to be used by the recipients as they would use the unmodified Software, containing modifications that substantially alter, remove, or disable functionality of the Software, outside of the documented configuration mechanisms provided by the Software, shall be modified such that the Original Author's bug reporting email addresses and urls are either replaced with the contact information of the parties responsible for the changes, or removed entirely.
Polycom, Inc. 161
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Except where noted, this license applies to any and all software programs and associated documentation files created by the Original Author, when distributed with the Software. "Node.js" and "node" trademark Joyent, Inc. npm is not officially part of the Node.js project, and is neither owned by nor officially affiliated with Joyent, Inc. Packages published in the npm registry are not part of npm itself, are the sole property of their respective maintainers, and are not covered by this license.
"npm Logo" created by Mathias Pettersson and Brian Hammond, used with permission.
"Gubblebum Blocky" font
Copyright (c) 2007 by Tjarda Koster, http://jelloween.deviantart.com included for use in the npm website and
documentation, used with permission.
This program uses "node-uuid", Copyright (c) 2010 Robert Kieffer, according to the terms of the MIT license.
This program uses "request", Copyright (c) 2011 Mikeal Rogers, according to the terms of the Apache license.
This program uses "mkdirp",Copyright (c) 2010 James Halliday, according to the terms of the MIT/X11 license.
"""
- tools/doc/node_modules/marked. Marked is a Markdown parser. Marked's
license follows:
"""
Copyright (c) 2011-2012, Christopher Jeffrey (https://github.com/chjj/)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"""
- test/gc/node_modules/weak. Node-weak is a node.js addon that provides garbage collector notifications. Node-weak's license follows:
"""
Copyright (c) 2011, Ben Noordhuis <[email protected]>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
"""
- src/ngx-queue.h. ngx-queue.h is taken from the nginx source tree. nginx's
license follows:
"""
Copyright (C) 2002-2012 Igor Sysoev
Copyright (C) 2011,2012 Nginx, Inc.
Polycom, Inc. 162
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
"""
- wrk is located at tools/wrk. wrk's license follows:
"""
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License.
Polycom, Inc. 163
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent noticesstating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks.
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
Polycom, Inc. 164
9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
