RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 1
ADMINISTRATORS’ GUIDE
RealPresence® CloudAXIS™ Suite
Software 1.3.1 | September 2013 | 3725-03273-003 Rev A
RealPresenc
Polycom, Inc
Copyright ©another lanwithout the
6001 AmerSan Jose, USA
Trademarks
Polycom®,service macountries. Atransmittedwritten per
End User L
By installinbe bound b
Patent Infor
The accomapplication
Open Sourc
This produthree (3) ycost to Polsource soft
Disclaimer
While Polymakes no wtypographi
Limitation o
Polycom athis documwithout notrespective (including winformation
Customer F
We are stricomments
Visit the Poproduct lice
ce® CloudAXIS™
c.
©2013, Polyconguage or forme express writte
rica Center DrivCA 95002
s
, the Polycom larks of PolycomAll other trademd in any form omission of Poly
icense Agreeme
g, copying, or by the terms an
rmation
mpanying produs held by Polyc
ce Software Use
ct may containyears after the lycom of shipptware code use
ycom uses reaswarranties or recal or other err
of Liability
nd/or its respecment for any pur
tice. The entiresuppliers be liawithout limitation), even if Polyc
Feedback
iving to improvto Documenta
olycom Supporenses, troubles
™ Suite Administ
m, Inc. All rightmat, or transmitten permission o
ve
ogo and the nam, Inc. and are marks are propr by any meansycom.
ent
otherwise usinnd conditions o
uct may be protcom, Inc.
ed in this Produ
n open source distribution da
ping or distributed in this produ
sonable efforts epresentationsrors or omissio
ctive suppliers rpose. Informat
e risk arising ouable for any diron, damages focom has been
e our documentionFeedback@
rt Center for Enshooting tips, s
trators’ Guide
ts reserved. Noted in any formof Polycom, Inc
ames and markregistered and
perty of their ress, for any purpo
g this product, of the End User
tected by one o
uct
software. Youate of the appliting the softwa
uct, contact Po
to include accus as to its accurns in the conte
make no repretion is provided
ut of its use remrect, consequeor loss of businadvised of the
ntation quality [email protected]
nd User Licensservice request
o part of this dom or by any meac.
ks associated wd/or common laspective ownerose other than
you acknowledr License Agree
or more U.S. a
u may receivecable product
are to you. To lycom by emai
urate and up-toracy. Polycom
ent of this docu
esentations abod “as is” withoumains with the rntial, incidenta
ness profits, bupossibility of s
and we apprecm.
e Agreements,s, and more.
ocument may bans, electronic
with Polycom paw marks in thers. No portion h the recipient's
dge that you haement for this p
nd foreign pate
the open souror software atreceive softwal at OpenSourc
o-date informatassumes no liament.
out the suitabilut warranty of arecipient. In no
al, special, punisiness interrup
such damages.
ciate your feedb
, software dow
be reproduced,c or mechanica
products are trae United Stateshereof may be
s personal use,
ave read, undeproduct.
ents and/or pen
rce software frt a charge not
are informationceVideo@polyc
tion in this docability or respo
ity of the informany kind and is o event shall Poitive, or other dption, or loss of.
back. Email yo
wnloads, produc
Softwar
, translated intol, for any purpo
ademarks and/s and various oreproduced or without the ex
erstand and ag
nding patent
rom Polycom ugreater than t
, as well as thecom.com.
ument, Polycomonsibility for any
mation containesubject to cha
olycom and/or damages whatsf business
ur opinions and
ct documents,
re 1.3.1
2
o ose,
/or other r xpress
gree to
up to the e open
m y
ed in ange its soever
d
RealPresenc
Polycom, Inc
Con
Abou
CoTerInfoTypWh
Ge1:
UnUn
MLeaCoGe
De2:
DeAccAccCo
LoSCCCCCLoCSMSUAC
CoCCCCC
ce® CloudAXIS™
c.
ntents
ut This Gui
nventions Urms and Writormation Elepographic Cohat’s in this G
etting Start
derstanding derstanding
Minimum Servarning Port Umpleting Settting Help an
eploying an
ploying the Scessing the cessing the nfiguring theogging In as tynchronizing
Configuring theConfiguring theConfiguring AdConfiguring SoConfiguring the
ocalizing the Customizing th
etting Date aManaging Cert
electing and Updating ServActivating LiceConfiguring Pr
nfiguring theConfiguring theConfiguring theConfiguring theConfiguring DMConfiguring the
™ Suite Administ
s
de ............
sed in this Gting Conventements .........onventions .Guide? .........
ted ............
the RealPreMinimum Re
ver RequiremeUsage ...........tup Workshend Support R
nd Configu
Services PorServices PorExperience Pe Services Pthe Super AdPortal Timing
e Connectione Connectiondditional Servocial Policies e ConnectionServices Port
he Email Temnd Time .......tificates ........Downloadingices Portal So
enses ............roxy Settings e Experiencee Server Sette Environmene Meeting HoMA Settings ..e VMR Settin
trators’ Guide
.................
Guide ............tions ...........................................................................
.................
sence Platfoequirementsents ...................................
eets ..............Resources ....
uring the P
rtal and Expertal ...............Portal ...........ortal .............min ...............g ................... to the LDAP to the SMTP
ver Settings ........................ to the DMA Stal .................
mplates .................................................... Log Levels ..oftware ...................................................
e Portal ........ings ..............nt General Seosts .....................................gs .................
.................
......................
......................
......................
......................
......................
.................
orm ................s ............................................................................................................
Portals ......
erience Porta..............................................................................................................Server .........
P Server .....................................................System and R............................................................................................................................................................................................................................ettings .............................................................................
.................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.................
al Packages.............................................................................................................................................................................................RPAD Server......................................................................................................................................................................................................................................................................................................
.................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................rs .........................................................................................................................................................................................................................................................................................................................
Softwar
.................
......................
......................
......................
......................
......................
.................
......................
......................
.....................
......................
......................
......................
.................
......................
......................
......................
......................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
......................
.....................
.....................
.....................
.....................
.....................
re 1.3.1
3
..... 6
....... 6
....... 6
....... 7
....... 8
....... 8
... 10
..... 10
..... 13
..... 15
..... 16
..... 18
..... 24
... 25
..... 25
..... 26
..... 28
..... 30
..... 30
..... 31
..... 32
..... 33
..... 35
..... 36
..... 39
..... 46
..... 47
..... 53
..... 54
..... 59
..... 61
..... 65
..... 71
..... 73
..... 74
..... 77
..... 80
..... 83
..... 87
RealPresenc
Polycom, Inc
CCVASUEImLo
Cre3:
UnCre
AA
EdEE
DeChRes
Pro4:
SecEA
Sec
Tro5:
UUCSUUUUOU
Ge6:
PoThe
A: Cr
ce® CloudAXIS™
c.
Configuring CoConfiguring AuViewing ExperApplying Expe
etting SystemUpdating Expe
xporting the Emporting the Eocalizing the
eating and
derstanding eating Accou
Adding Active Adding Local U
iting Accounditing Accounditing Locallyleting Accouanging Yoursetting a Pas
oviding Se
curing SIP Gnabling Gues
Additional Reccuring Web A
oubleshoo
User Cannot CUser Cannot LConfigured Co
uper Admins User Cannot SUser ReceivesUser ReceivesUser ReceivesObtaining ServUser Cannot D
etting Help
lycom and Pe Polycom C
reating a G
™ Suite Administ
onnection Setuthentication Prience Portal Lrience Portal
m Administratierience PortalExperience PExperience PExperience P
d Managing
Account Rounts ..............Directory Use
Users ............nts ................nts Created fry Created Useunts ..............r Password ..ssword ........
ecure Gues
Guest Accessst Access on YcommendationAccess ........
oting the Se
Create MeetinLaunch the Womponents are
and Admins Send Email Nos “Unable to Cs “External Ses “Video Resovices Portal LDownload Log
................
Partner ResouCommunity...
Google Talk
trators’ Guide
ttings ............Provider SettLog Files ......Configurationion UI Properl Software .....ortal Configuortal Configur
Portal .............
g User Acc
oles ....................................ers ..........................................................rom the Activeer Accounts ..................................................................
st Access .
s ....................Your Edge Prns for Greate.....................
ervices Po
ngs ................elcome Screee Not ResponCannot Add aotifications ....
Create a Conferver Not Set”ources Are Noog Files ........
gs on Internet
.................
urces ................................
k™ App ....
......................ings ....................................ns..................rties .....................................ration File .....ration File ...........................
counts ......
......................
......................
......................
......................
......................e Directory ............................................................................................
.................
......................roxy ..............r Security ............................
ortal ..........
......................en..................nding .............an Active Dire......................ference with a” Message .....ot Available” M......................t Explorer ......
.................
......................
......................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................ectory User .......................a Personal VM.....................Message ................................................
.................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.................
.....................
.....................
.....................
.....................
.....................MR” Message....................................................................................
.................
.....................
.....................
.................
Softwar
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.....................
.................
......................
......................
.....................
.....................
......................
.....................
.....................
......................
......................
......................
.................
......................
.....................
.....................
......................
.................
.....................
.....................
.....................
.....................
.....................e .......................................................................................................
.................
......................
......................
.................
re 1.3.1
4
..... 93
..... 97
..... 99
... 100
... 102
... 105
... 105
... 106
... 107
. 109
... 109
... 111
... 111
... 113
... 115
... 115
... 117
... 119
... 120
... 121
. 123
... 123
... 123
... 124
... 125
. 126
... 126
... 126
... 126
... 127
... 127
... 127
... 127
... 127
... 128
... 128
. 129
... 129
... 129
. 130
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 5
B: Creating a Facebook App ................................................................................ 139
C: DMA Factory Conference Settings Impact ..................................................... 144
D: CloudAXIS Restricted Shell ............................................................................. 147
Introduction ................................................................................................................................... 147 Usage ............................................................................................................................................. 147
Use Case - Login as 'caxis' via Console or via a SSH Connection ............................................. 147 Use Case - Change System Hostname ....................................................................................... 148 Use Case - Log Collection ........................................................................................................... 148 Use Case - Copying the generated logs to a different server ...................................................... 149 Use Case - Access Log Files ....................................................................................................... 149 Use Case - Changing Password of the 'caxis' User .................................................................... 149 Use Case - Configure System NTP Settings ............................................................................... 150 Use Case - Quick Sync System date-time with a Specific NTP server ....................................... 150 Use Case - Show Product Version .............................................................................................. 150 Use Case - Regeneration of Certificates ..................................................................................... 151 Use Case - Change System Timezone ........................................................................................ 151 Use Case - Restarting Services ................................................................................................... 152 Use Case - Set System Date Time .............................................................................................. 152 Use Case - View System Network Information ............................................................................ 153 Use Case - System Network Configuration is already set to use DHCP ..................................... 153 Use Case - Enabling DHCP in a machine where DHCP is not enabled ...................................... 154 Use Case - Configuring Static IP Address in a System where DHCP is in an 'Enabled' state .... 154 Use Case - Configuring Static IP Address in a system where DHCP is in a 'Disabled' state ...... 156 Use Case - Configuring Static IP Address in a system where DHCP is in a 'Disabled' state with the currently assigned IP address ................................................................................................ 158 Use Case - Attempting to configure manual DNS settings while DHCP is enabled in the system ..................................................................................................................................................... 160 Use Case - Using invalid network values ..................................................................................... 160 Use Case - Using an IP that is already assigned to a machine in the same network ................. 161 Use Case - Reboot System ......................................................................................................... 162 Use Case - Exit Restricted Shell .................................................................................................. 162 Use Case - Login Timeout: .......................................................................................................... 162
E: Third-Party Software ........................................................................................ 163
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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.
RealPresenc
Polycom, Inc
InforThis guide
Icons Use
Name
Note
Administr
Caution
Warning
Web Info
Timesave
Power Tip
Troublesh
Settings
ce® CloudAXIS™
c.
rmatione may include
d in this Guid
Ic
rator Tip
er
p
hooting
™ Suite Administ
n Eleme any of the fo
e
con Des
Theto b
Therela
Thecousuc
Theissuand
Theas d
Thea m
Theadm
Therele
Thebeh
trators’ Guide
mentsollowing icons
scription
e Note icon higbe successful in
e Administratorated tips.
e Caution icon uld potentially imccessful feature
e Warning icon ues that may cad/or affect phon
e Web Info icondocuments or d
e Timesaver icomethod or opera
e Power Tip icoministrators alre
e Troubleshootevant problem o
e Settings icon havior, to enabl
s to alert you
hlights informan accomplishin
r Tip icon highli
highlights informpact device pe configuration.
highlights an aause you to losne or network p
n highlights supdownloads on s
on highlights a ation.
on highlights faeady familiar w
ing icon highligor to refer you
highlights settie a specific fea
to important i
ation of interestng a procedure
ights technique
rmation you neperformance, a.
action you musse information operformance.
pplementary infsupport.polyco
faster or altern
ster, alternativwith the techniq
ghts informationto other releva
ings you may nature, or to acc
information.
t or important inor to understa
es, shortcuts, o
eed to know to aapplication func
st perform (or aor your configu
formation availom.com or othe
native method f
e procedures fues being disc
n that may helpant troubleshoo
need to choosecess customiza
Softwar
nformation neend a concept.
or productivity
avoid a hazardctionality, or
avoid) to prevenuration setup,
lable online suer locations.
for accomplish
for advanced cussed.
p you solve a oting resources
e for a specific ation options.
re 1.3.1
7
eded
d that
nt
ch
hing
.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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 and 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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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.
RealPresenc
Polycom, Inc
G1:
The Cloudaccess tobusiness server com
The Servicreate mesetting theprovides athat enabenabling uguide shocreate and
This chapthe ServicdeploymeDeploying
This cha
Und
Und
Lea
Com
Get
UndeThe Polycvideoconfoptional v
ce® CloudAXIS™
c.
Getting
dAXIS™ Suitea shared meand guests frmponents de
ces Portal eneetings by loge meeting paradministrativele the online vusers to interaows you how td manage us
pter gives youces Portal andent and configg and Configu
apter is orga
derstanding th
derstanding M
arning Port Us
mpleting Setu
tting Help and
Web
Note Polyc
erstancom RealPresference collabvendors. This
™ Suite Administ
g Sta
e extends andeeting and colrom outside thployed by the
nables users tgging into the rameters, ande capabilities video confereact with featuto deploy ander accounts.
an overview d the Experieguration. Wheuring the Porta
anized as fo
he RealPrese
Minimum Req
sage
up Worksheet
d Support Res
b Info: An On
that if you are com TechNet w
ding thsence Platformboration betwimplementati
trators’ Guide
rted
d enhances tlaboration ex
he business. Te business: th
to create and Services Por
d entering a lifor creating a
ence meetingsres such as c
d configure the
of the RealPnce Portal, an
en you are reaals.
ollows:
ence Platform
uirements
ts
sources
nline Version
reading this dowebsite at http:
he Ream is a produceen hardwareon may includ
he Polycom®xperience thatThe key compe Services Po
participate inrtal, selecting st of participa
and managings. The Expericontent sharine Services Po
resence Platfnd provides wady to deploy
m
of this Docu
ocument in PD//support.polyc
alPresect suite used te and softwarde one or mo
® RealPresent can include ponents of thortal and the
n online videothe type of m
ants to invite. g users and foience Portal png, group chaortal and Exp
form, lists theworksheets to
and configur
ument is Ava
DF format, an ocom.com/Polyc
ence Pto enable andre endpoints fore of the com
ce® Platformusers from the suite are twExperience P
o conference mmeeting they w
The Servicesor configuringprovides the mat, and privacyperience Porta
e deployment o complete bere the Service
ailable
nline version iscomService/ho
Platformd enhance stafrom Polycom
mponents liste
Softwar
m by providinghe hosting wo virtualized Portal.
meetings. Uswant to creates Portal also g the componemeeting interfy settings. Thal packages a
requirementsefore starting tes Portal, see
s available on tme/home.htm.
m andards-basem and other ed Table 1.
re 1.3.1
10
ers e,
ents face, his and
s for the
the
ed
RealPresenc
Polycom, Inc
Table 1: R
Required
Required
Required
Optional
Optional
Optional
*Atra
The Serviwith the fo
Dynadd
Domcom
Ligan ma
Simusee-m
HTTfromsup
Usereco
ce® CloudAXIS™
c.
RealPresence P
d or Optional
d
d
l
l
l
An Acme Packaversal.
ces and Expeollowing stand
namic Host Cdresses.
main Name Smponents to b
ghtweight DirLDAP-companagement an
mple Mail Traer notificationsmail.
TP Reverse Pm outside thepports the We
e the host namords point to t
Note:
The com
C
T
R
E
™ Suite Administ
Platform Com
Polycom P
Polycom D
RealPrese
RealPrese
RealPrese
RSS™ rec
ket Net-Net E
erience Portadard IT infras
Configuratio
System (DNSbe found and
rectory Acceatible directorynd authenticat
ansport Protos, including lo
Proxy Serve organization
eb Sockets pr
me selected (the same IP;
Diagram Leg
mponents in t
CloudAXIS C
Third-Party
RealPresenc
End-Points
trators’ Guide
ponents
Platform Com
DMA
ence Collabor
ence Resourc
ence Access
cording and s
Enterprise Ses
als interoperattructure elem
n Protocol (D
S) Server - Alreferenced u
ess Protocol y (e.g., a Micrtion.
ocol (SMTP) ogin informatio
r - Provides wal firewall. Footocol (RFC 6
(e.g., meet.cothe Reverse
end
the following
Component
Componen
ce Compon
Identified by
mponent
ration Server
ce Manager
Director™ so
streaming ser
ssion Director
te with the Rements that the
DHCP) Serve
llows the portsing domain n
(LDAP) Servrosoft Active
Server - Enaon and passw
web clients wior best results6455).
ontoso.com anProxy separa
diagram are s
ts Identified
nts Identified
nents Ident
y dark red.
Pu
Sigvirt
™ MC
Proend
olution* Fir
rver Me
r may alterna
ealPresence Pdeploying org
er - Allows the
tals and othernames rather
ver - Allows thDirectory serv
ables sending word reset/up
ith secure accs, a proxy ser
nd schedule.cates traffic ba
specified as f
d by light blue
d by orange.
tified by bright
urpose
gnaling, call ctualization.
CU for hosting
ovisioning anddpoints
rewall traversa
edia recording
ately be used
Platform comganization sh
e portals to o
r RealPresenr than IP addr
he portals to bver) to facilita
meeting invitdates, via
cess to the Crver should be
contoso.com)sed on the ho
follows:
e.
t red.
Softwar
control, and br
g conferences
d managing
al
g
to secure fire
ponents alonhould provide:
btain their IP
ce Platform resses.
be integratedate user
tations and ot
CloudAXIS pore used that
) where both Dost.
re 1.3.1
11
ridge
s.
ewall
g :
with
ther
rtals
DNS
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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® v14.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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
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
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 15
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.
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
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 16
Learning Port Usage This section lists the ports used to ensure successful network traversal for the Services Portal.
Figure 2: Port Usage Diagram
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 17
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.
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 18
Protocol/Function Communication Ports
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.
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 19
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.
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 URL 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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 20
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).
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.
See the Polycom DMA 7000 System Operations Guide for more detail on adding MCU Pool orders.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 21
System Configuration Information
My System Values Description
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.”
Common SIP Username (Optional) Enter a username to use to authenticate SIP sessions for users who have authenticated with the Services Portal.
Common SIP Password (Optional) Enter a password to use in conjunction with the Common SIP Username to authenticate SIP sessions for users who have authenticated with the Services Portal.
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 22
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.
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 23
System Configuration Information
My System Values Description
Auth Mode Options for this dropdown box include AUTH, NoAUTH, and SHARED.
For an access point that may be used by endpoints without access to SIP credentials, select NoAUTH.
For an access point that should be used by endpoints that have access to SIP credentials (e.g., authenticated web and RPM client users when the DMA settings have been configured with the Common SIP Username and Password described above), select AUTH.
For an access point that may be used by either class of endpoints, select SHARED.
Dial Prefix Use this optional field to specify a prefix to prepend to dialing information used when dialing this access point. This prefix can be used by the access point to route the call or to distinguish between callers who are able to authenticate themselves from those that require unauthenticated guest access.
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.
RealPresence® CloudAXIS™ Suite Administrators’ Guide Software 1.3.1
Polycom, Inc. 24
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
D2:
The ServiClient admPortal seccredentialthe configreceive acExperiencPortal is fo
This chapprerequisthe Servic
Dep
Acc
Acc
Con
Con
DeplPortaBefore yoServices P
Note that The instanusing the modifyingof your chenable it t
We also rbased on
If DHCP ismay altern
1 Usi
2 Log
3 Ent
c.
Deploy
ces Portal anministrative Gcond. Once thls and configu
gurations are cccess, they cace Portal to enound in the R
pter shows yoites and compces Portal and
ploying the Se
cessing the Se
cessing the Ex
nfiguring the S
nfiguring the E
oying al Packou begin, confPortal and Ex
when the pornce IP addresvSphere Clie your DHCP s
hoosing to theto obtain a ne
recommend ththe permane
s not availablnatively be co
ng the vSphe
gin using “cax
ter the followin
ying a
nd ExperienceGUI. Our recomhey are both dure the servercomplete, thean use the Senable confere
RealPresence
u how to depplete the Setud the Experie
ervices Porta
ervices Porta
xperience Po
Services Port
Experience P
the Sekages firm that you mxperience Por
rtal instancesss and the MAent. Polycom rserver’s confi
e respective inew address.
hat you modifent IP address
e in your envonfigured via
ere console, a
xis” for both yo
ng command
and C
e Portal requimmendation ideployed, log r settings thene Services Poervices Portalence interactio® CloudAXIS
loy and configup Worksheetnce Portal in
l and Experie
al
ortal
tal
Portal
ervices
meet the prerrtal .OVA files
boot up, theyAC address crecommends iguration to mnstance MAC
fy your DNS ss you have se
vironment, eacthe portal’s co
access the po
our username
to view the c
Config
re deploymenis to deploy thin to the Serv
n complete thortal is ready fl to create meon. Informatio
S™ Suite Use
gure the Servts provided, sthe following
ence Portal Pa
s Porta
requisites listes to your VMw
y will each attcan be determ
that the instamap the currenC address. The
server settingelected.
ch portal instaonsole. To do
rtal console
e and passwo
current networ
guring
nt on a VMwahe Services Pvices Portal w
he Experiencefor adding aneetings, add con on accesser Guide.
vices Portal. Bsee the steps
sections of th
ackages
al and
ed in Gettingware vSphere
tempt to obtamined by acceance IP assignt IP addressen, reboot the
s to assign a
ance’s IP addo this:
ord.
rk settings: sh
g the
are EXSi hostPortal first andwith the defaue Portal configd managing ucontacts, and ing and using
Before you befor deploying
his chapter.
Exper
Started, and e EXSi hosts.
in an IP addressing the insnments be m
s or another pe instance if n
domain nam
dress and net
how_network
Porta
t using a vSphd the Experieult super admgurations. Whusers. Once uuse the
g the Services
egin, confirm g and configu
ience
then deploy t
ess via DHCPstance informa
made permanereferred addrnecessary to
e to each inst
tworking settin
k_info
25
als
here nce in hen users
s
all ring
the
P. ation ent by ress
tance
ngs
Polycom, Inc
4 Entchang
Seewhe
AcceObtain thein the addServices PPasswordaction can
After accepassword
Note that activate th
c.
ter the followinge_network_
e more informere DHCP is i
Note:
The paThe ordthe ove
essinge Services Podress bar. ThePortal for used, and accept n be taken.
epting the EUs, see Chang
you have a 3he license, se
Troubl
If the Seconfirm
To che1 U
F2 L3 G
○○○
4 Ststill h
○○
Note:
An FQDFQDN y
ng command _settings
mation on this in a 'Disabled
Order of Dep
ckages may bder describederall process.
the Seortal FQDN pre Services Poe. For the first
the End Use
LA, change tging Your Pas
30-day trial of ee Activating t
leshooting: U
ervices Portam that the Ngin
ck the NginxUsing the vSpFQDN, accessLog in using “cGet status:
○ Enter the fo
○ Enter the fo
○ Enter the foart servers if having proble
○ Startup ser
○ Restart ser
Configuration
DN is requiredyou noted in t
to modify the
DHCP issue d' state.
ployment
be deployed, d in this docum
ervicesrovisioned viaortal login scre
Services Porr License Agr
he password ssword.
the service athe Services
RL (FQDN) D
al URL does nnx, Apache, o
x, Apache, orhere consoles the Servicescaxis” for both
ollowing to ge
ollowing to ge
ollowing to gethey are not r
ems with the l
rvers: servic
rvers: servic
n Note
d when configthe Setup Wo
e current netw
at Use Case
accessed, anment, howeve
s Portaa your DNS seeen will displartal login, entereement (EUL
for greater se
and licenses cPortal Licens
Does Not Res
not respond, oor all servers a
r all servers: or by connecs Portal consoh your userna
et the Nginx s
et the Apache
et the status orunning, and ink:
ces <SomeS
ces <SomeS
guring the Seorksheet for th
work settings:
- Configuring
nd configureder, is recomm
al erver, open aay, and you aer ‘admin’ for LA). Until the
ecurity. For in
can be activate.
spond
open the Servare running a
: cting via an Sole. ame and pass
status: servi
e status: serv
on all servers:restart them i
Server> sta
Server> res
rvices Portal.he Server Se
g Static IP Ad
d in any logicaended for tho
a browser, andare now readyr both your UsEULA is acce
nformation on
ted any time d
vices Portal loas follows:
SSH client to t
sword.
ce nginx s
vices tomca
: service -if they are run
art
start
. Enter the Seettings.
dress in a sys
al relative ordose unfamiliar
d enter the FQy to configuresername and epted, no furt
n changing
during the tria
ogin screen a
the Services P
status
at6 status
--status-alnning but you
ervices Portal
26
stem
er. r with
QDN the
ther
al. To
nd
Portal
s
ll u are
Polycom, Inc. 27
Polycom, Inc
AcceTo acces
Obt1FireconFQD
The
Ente2secdefa
c.
essings the Experi
tain the Experefox browser, nnection mustDN>:9445.
e Experience
er ‘admin’ for cond Login scault ‘admin’ to
the Exence Portal a
rience Portal and enter the
t be made to p
Portal login s
both the Usereen will appeo a new more
xperieadministrativ
FQDN provise FQDN in theport 9445 the
screen will dis
ername and Pear (see belo
e secure and p
nce Pove and provi
sioned via youe address ba
e full URL of th
splay.
Password (as w) and requepersonalized
ortal isioning inte
ur DNS servear. Because yohe server wou
in the above est that you immulti-charact
rface:
r, open eitherou must speculd be https://
example), anmmediately chter Username
r a Chrome ocify that the /<Server
nd click Loginhange from the and Passwo
28
r
n. A he ord.
Polycom, Inc
Clic3
c.
ck Save after
Note:
The FQPortal F
Note:
To acce https://
you enter you
Configuration
QDN is requireFQDN you en
Configuration
ess the Exper/<Server FQD
ur new Usern
n Note
ed when confntered in the S
n Note
rience Portal DN>. No addit
ame and Pas
figuring the ExSetup Worksh
directly as antional port nu
ssword.
xperience Poheet for the S
n end-user, enmber is need
ortal. Enter theerver Setting
nter the URL ded.
e Experience s
29
Polycom, Inc. 30
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
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 immediately change the password for security reasons. 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.
Polycom, Inc
Figure 3: S
SynchBoth the Sserver in o
To confi
1. Acc‘caxis’
2. SelDate T
3. SynSync S
Repea
c.
Super Admin T
Admin
When tanotherfor morsuper a
hronizinServices Portorder for Clou
Note
Chectime of sy
gure the sa
cess the CLI (for both your
ect your time Time in Appen
nc your serveSystem date-t
at the above 3
Tabs
n Tip: Creating
the Services Pr super adminre informationadmin accoun
g Portalal and the Ex
udAXIS Reco
e: NTP Date an
ck that the NTPof Instances is
ync.
ame time zo
(See Appendir Username a
zone by usinndix D for deta
r with the NTPtime with a Sp
3 steps on the
g Additional S
Portal is launcn account aften. Login with tnt for secure a
l Timingxperience Porrding to work
nd Time Zone
P date and times taken from EX
one and NTP
ix D: CloudAXnd Password
ng the CLI Coails.
P server by upecific NTP se
e other portal.
Super Admins
ched for the fer the configuhe new superaccess.
g rtal MUST be properly.
Verification
e zone of your XSi, and if that
P server
XIS Restricted.
mmand chan
sing the CLI erver in Appe
s
first time, we ruration is comr admin crede
configured to
EXSi host matis wrong, the S
d Shell) on ei
nge_timezon
Command ntendix D for de
recommend tmpleted. See C
entials, and d
o the SAME t
tches the PortaServices Porta
ther of the tw
ne. See Use C
tpdate. See Uetails.
that you creatCreating Accoelete the defa
ime zone and
al’s time. The dal scheduler can
wo portals usin
Case - Set Sy
Use Case - Q
31
te ounts ault
d NTP
default n go out
ng
ystem
Quick
Polycom, Inc
ConfigThe LDAPexternal ulogins. Thsuper admAdmin.
To config
1 Sele
2 Ent
○ S
○ Sr
c.
guring tP server enabuser account dhis section shomin before co
Note:
This seServer the con
gure the con
ect SETTING
er the followin
Server Ente
Secure Cherecommende
the Connbles the Servidefault roles, ows you how nfiguring this
Setup Works
ection specificConfiguration
nfiguration pro
nection to th
GS > CORE S
ng in the LDA
er the LDAP F
eck the checkd.
nection ces Portal to set external uto configure connection. F
heet
cally refers to n. Complete tocess and to o
he LDAP serv
SETTINGS > L
AP Settings sc
FQDN or IP a
kbox to establ
to the Limport externuser accountsconnection toFor more info
information ehe worksheetobtain inform
ver:
LDAP. The LD
creen:
address.
lish a secure
LDAP Senal user accous as active oro the LDAP seormation, see
entered in thet in advance aation about e
DAP Settings
connection. T
erver unts from an r inactive, anderver. You muLogging In a
e Setup Worksand use it as
each field.
s screen (sho
This is optiona
enterprise, edd authenticateust log in as as the Super
sheet for the a reference d
wn next) disp
al but
32
dit e user a
LDAP during
plays.
Polycom, Inc
○ P
○ BC
○ U
○ P
3 Clicrece
ConfigThe SMTPcreated, wthey creatconfigurinSMTP ser
To config
1 Selenex
c.
Port Enter t
BaseDN EnConfiguration
Username
Password E
ck UPDATE toently updated
guring tP server enabwhen their accted or have b
ng the connecrver. For more
Note:
This seSMTP Sduring t
Note:
The Seuntil ex
gure the con
ect SETTINGxt.
the LDAP por
nter the distingn.
Enter the LDA
Enter the logi
o finish the cod LDAP inform
the Connbles the Servcount details een invited to
ction to the SMe information
Setup Works
ection specificServer Configthe configura
Active Directo
ervices Portal xplicitly disable
nection to th
GS > CORE S
rt number (typ
guished name
AP services a
n password f
onfiguration, omation.
nection ices Portal to are updated,
o is updated oMTP server. Y, see Logging
heet
cally refers to guration. Comtion process a
ory Users
considers imed, and emai
he SMTP serv
SETTINGS > S
pically 636 for
e entered in t
account user
for the LDAP
or click RESE
to the Ssend email nwhen they ar
or cancelled. TYou must log g In as the Su
information emplete the woand to obtain
ported Activels are not sen
ver:
SMTP. The S
r secure and
the Setup Wo
ID for system
services acco
ET to populate
SMTP Senotifications tore invited to aThis section sin as a super
uper Admin.
entered in therksheet in ad information a
e Directory usnt when an Ac
SMTP Settings
389 for non-s
orksheet for th
m access to th
ount user ID.
e the fields w
erver o users whena meeting, or shows you thr admin befor
e Setup Worksvance and usabout each fie
sers to have ective Director
s screen disp
secure).
he LDAP Serv
he Active Dire
ith the most
n their accounwhen a meete steps for
re configuring
sheet for the se it as a refeeld.
enabled accoury user is impo
plays as show
33
ver
ectory.
nt is ting
the
erence
unts orted.
wn
Polycom, Inc. 34
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.
Polycom, Inc
ConfigThis sectiThe purpo
We
Me
Before yosee Loggi
To config
1 Sele(sho
2 Ent
○ M
○ W
3 Clicupd
c.
guring Aon describes ose of each s
eb Services P
eting Experi
ou begin, you ing In as the S
Note:
This seSettingconfigu
gure the add
ect SETTINGown next) dis
er the followin
MEA Server
WSP Server
ck UPDATE todated Server S
Additionhow to entererver is:
Portal (WSP)
ence Applica
must be loggSuper Admin
Setup Works
ection refers tos. Complete t
uration proces
itional serve
GS > CORE Ssplays.
ng informatio
Enter the E
Enter the S
o finish the coSettings infor
nal Server the locations
Server hosts
ation (MEA) S
ed in to the S.
heet
o specific infothe worksheess and to obta
r settings:
SETTINGS > S
n in the SERV
xperience Po
Services Porta
onfiguration, ormation.
er Settins of the Servic
s the Services
Server hosts
Services Porta
ormation enteet in advance,ain information
SERVER SET
VER SETTIN
ortal’s FQDN f
al’s FQDN fro
or RESET to
ngs ces Portal and
s Portal.
s the Experien
al as a super
ered in the Se and use it asn about each
TTINGS. The
NGS screen te
from Accessi
m Accessing
populate the
d Experience
nce Portal.
admin. For m
etup Workshees a reference field.
e SERVER SE
ext blocks:
ng the Exper
the Services
fields with the
e Portal serve
more informati
et for the Serduring the
ETTINGS scr
ience Portal
s Portal
e most recent
35
rs.
ion,
rver
een
tly
Polycom, Inc
ConfigUsers canSkype™, which soc
Skypag
Go
a Cei
b S
c ET
Fac
a
b
c
This sectiaccess in Google TaFacebookmore info
Note that settings. F
To confi
1 Sel
c.
guring Sn send conferFacebook, or
cial connector
ype™ - To enge.
ogle Talk™ -
Create a Gooenabled to shinformation pr
Select the Go
Enter the ClieTalk™ App.
cebook - Ena
Create a Facshare the con
Select the Fa
Enter the App
Note:
Accessplug-in option.
on shows youthe Services
alk™ app. Sek contacts, yormation.
you must logFor more info
gure social
ect SETTING
Social Prence invitatior Google Talkr(s) you want
nable access
- Enabling ac
ogle Talk™ aphare the contarivate.
oogle Talk™ c
ent ID and Clie
abling access
cebook app. Sntacts lists wh
acebook chec
p ID and the A
CloudAXIS S
sing any of theis downloadeFor more info
u how to enabPortal. Befor
ee Appendix Aou must first c
in to the Serrmation, see
l policies:
GS > SOCIAL
oliciesons in an instak™ accounts. to use:
to Skype™ c
cess to Goog
pp. See Appeacts lists while
checkbox in th
ent Secret, re
to Facebook
See Appendixhile keeping th
ckbox in the S
App Secret, re
Social Plug-in
e social conneed when a useormation, see
ble and disabre enabling acA: Creating a reate a Faceb
vices Portal aLogging In as
L POLICY. Th
ant message How you ena
ontacts, selec
gle Talk™ con
endix A: Create keeping the
he Social Pol
etrieved from
k contacts req
x B: Creating ahe username
Social Policy p
etrieved step
ectors also reer accesses t
e the RealPre
ble Skype™, Fccess to GoogGoogle Talk™book app. Se
as a super ads the Super A
e SOCIAL PO
to any onlineable access t
ct the Skype
ntacts require
ting a Googlee usernames,
licy page.
step 10 of Ap
uires the follo
a Facebook Aes, passwords
page.
4 of Append
equires the Clthe Experiencsence® Clou
Facebook, angle Talk™ co™ App for mo
ee Appendix B
dmin before enAdmin.
OLICY SETTI
e contacts listeto social conta
checkbox in t
es the followin
e Talk™ App. passwords, a
ppendix A: Cr
owing steps:
App. This apps, and other in
ix B: creating
loudAXIS Socce Portal menudAXIS™ Use
nd/or Google Tontacts, you more informatioB: Creating a
ntering the so
TINGS screen
ed in their acts depends
the Social Po
ng steps:
This app is oand other
reating a Goo
p is only enabnformation pr
a Facebook
cial Plug-in; thnu’s Contactser Guide.
Talk™ accoumust create a on. Before enaFacebook Ap
ocial policy
displays:
36
s on
olicy
only
ogle
bled to ivate.
App.
his
nt
abling pp for
Polycom, Inc
The
Clic4polithe from
Whsho
c.
e Skype™, Fa
ck the checkbcy options. SExperience P
m the Experie
en selecting Gown next.
acebook, and
oxes for SkypSelecting a chPortal; deseleence Portal.
Google Talk™
Google Talk
pe™, Google eckbox enabl
ecting disables
™ and/or Face
™ social optio
Talk™, and/oles users to as users from
ebook, the Ap
ons display.
or Facebook access the acaccessing the
pp ID and App
to select or dccount type’s ce account typ
p Secret text
eselect the socontact list fro
pe’s contact lis
boxes display
37
ocial om st
y as
Polycom, Inc
Ente5
○ G
»
»
○ F
»
»
4 Clic
c.
er the followin
Google Talk™
» App ID E
» App SecreApp
Facebook W
» App ID E
» App Secre
ck UPDATE.
ng:
™ When sel
Enter the Clien
et Enter the
When selectin
Enter the App
et Enter the
ecting Google
nt ID from ste
e Client Secre
ng Facebook,
ID from step
App Secret f
e Talk™, ente
ep 10 of Appe
et from step 1
enter the foll
4 of Appendi
from step 4 of
er the followin
endix A: Creat
0 of Appendix
lowing inform
ix B: Creating
f Appendix B:
ng information
ting a Google
x A: Creating
ation:
g a Facebook
: Creating a F
n:
e Talk App.
a Google Ta
k App.
Facebook App
38
alk™
p.
Polycom, Inc
ConfigServeThis secti
DMA systexternal lidirectly orRPAD extcommunic
You mustinformatio
To confi
Select
From t
Con
Cha
c.
guring ters
on explains h
tems enable tnks to the DM
r indirectly to ternally and pcate with the
log in to the on, see Loggin
Note:
This seConfiguconfigu
gure the co
SETTINGS >
this SETTING
nfigure a new
ange an exist
the Conn
how to enter c
the Services PMA that enablthe DMA. For
points to the DDMA from eit
Services Portng In as the S
Setup Works
ection specificuration. Compuration proces
onnection to
> DMA CONF
GS screen, yo
w DMA connec
ing one.
nection
configuration d
Portal to launles firewall trar example, anDMA from withther side of a
tal as a superSuper Admin.
heet
cally refers to plete the workss and to obta
o the DMA s
FIG. The SET
u can either
ction, or
to the D
details for you
ch online videaversal, and pn access poinhin the Polycofirewall.
r admin befor
information eksheet in advaain information
system:
TTINGS scree
DMA Sys
ur DMA syste
eo conferencepoints of presnt configured wom network e
re entering the
entered in theance, and usn about each
en displays:
stem an
em, RPADs, a
e meetings, Rsence enable with an FQDNenables the S
e server setti
e Setup Workse it as a refer field.
d RPAD
and access po
RPADs are you to route e
N that points tServices Porta
ngs. For more
sheet for the rence during t
39
D
oints.
either to the al to
e
DMA the
Polycom, Inc. 40
To configure a new DMA connection:
1. Click +ANOTHER DMA. The DMA CONFIGURATION screen with the following fields and text boxes displays.
2. Enter the appropriate data for each of the following SETTINGS/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.
○ Common SIP Username – (optional) Enter a username to use to authenticate SIP sessions for users who have authenticated with the Services Portal.
Polycom, Inc
○ CSPaRcaSa
○ D
○ A
○ O
○ O
○ GW
3. Clicof the s
c.
Common SIPSIP UsernamPortal. If a SIauthenticatedRealPresencechallenge whauthenticatedSIP gatekeepaccess to trus
For more infospecified herAuthenticatiothe Polycom
Default Adm
Admin Passw
Owner Doma
Owner Usern
Generate VMWhen selecte
ck + ADD ACscreen displa
Note:
An accewhere cconfigu
D
E
EP
IS
A
The cliesuch asSeries,
P Password -me to authentic
P username ad CloudAXIS ce Mobile v3.1en placing a c
d via the web per (typically tsted users of
ormation, seee should matc
on settings. FoDMA 7000 S
in - Enter the
word - Enter
ain - Enter the
name - Enter
MR range - Seed, two text bo
CESS POINTays next.
Access Point
ess point is aclients or end
urable as follo
Direct connec
Externally to a
Externally rouPresence Acc
SDN
Audio dial-in v
ent or end pos Polycom Reor a telephon
- (optional) Encate SIP sessand passwordclients that su and above) scall. The purpinterface to e
the DMA devithe organizat
Securing SIPch one of thoor more informystem Opera
e DMA system
the DMA sys
e domain of th
the user nam
elect to enter oxes display (
T to enter you
t
network locadpoints can cows:
ction to DMA
access the DM
ted via a SIP cess Director
via Public Sw
int could be thealPresence Mne.
nter a passwosions for userd are specifieupport this funso that they mpose of this fuestablish an ace). This, in ttion.
P Guest Accese configuredmation on thistions Guide.
m admin user
tem admin ac
he owner who
me of the own
the range of (see following
ur access poin
ation that is roonnect to part
MA via H.323
Session Boa(RPAD), or a
itch Telephon
he CloudAXISMobile, a hard
ord to use in rs who have aed here, thesenctionality (thmay respond unctionality is uthenticated turn, may allo
ess. The SIP ud on the DMAs, see the “De
name.
ccount passw
o creates the
ner who create
numbers allog partial scree
nt information
outed directly ticipate in a c
3 video border
ard Controller any third-party
ny Network (P
S Experiencedware applian
conjunction wauthenticatede credentials ae CloudAXISto a SIP auth to allow userand trusted S
ow more privil
username anA’s Inbound Device Authent
word.
meetings.
es the meetin
owed for geneen).
n. The ACCES
or indirectly tonference. Ac
r proxy
r (SBC), includy session boa
PSTN).
e Portal, a sepnce such as P
with the Comm with the Servare provided web client an
hentication rs who have SIP session toeged dialing
d password Device tication” sectio
ngs.
erating VMRs
SS POINT po
to the DMA frccess points
ding Polycomarder controlle
parate soft cliePolycom Grou
41
mon vices to nd
o the
on in
.
ortion
rom are
m Real er
ent up
Polycom, Inc
4. EntConfig
○ Lo
○ THC
○ Ds
○ A
○ Dwdu
Clic
5. Wh
c.
ter your accesuration as fol
Note:
Enter thinternal
Location - Enother property
Transport - FH323, ISDN, CloudAXIS w
Dialstring - Eshould be app
Auth Mode –
For an ac(e.g., autconfigureAUTH.
For an acNoAUTH
Select SHguests or
Dial Prefix - when dialing distinguish beunauthenticat
ck +ADD ACC
en all needed
ss point informlows:
Entering Acc
he APs in thel APs first. Als
nter a name fy which distin
From the dropor PSTN). At
will not function
Enter the dial propriate for t
– Select AUTH
ccess point ththenticated weed with the Co
ccess point thH.
HARED in anr where all wi
Use this optiothis access p
etween callersted guest acc
CESS POINT
d DMA Config
mation from th
ess Points (A
order that yoso, note that i
for this accessnguishes it fro
pdown box, sethis time, you
n.
string that anthe specified
H, NoAUTH, o
hat should be eb and RPM ommon SIP U
hat may be us
environmentll require auth
onal field to spoint. This pres who are ablcess.
T to enter anot
guration fields
he Setup Wor
AP)
ou want the Sit is mandator
s point that dem other acce
elect the protou must not ch
n endpoint shoaccess point
or SHARED.
used by endpclient users w
Username and
sed by endpo
t where all thehentication.
pecify a prefixefix can be usle to authentic
ther access p
s are complete
rksheet for th
Services Portary to add at le
escribes its gess points. Th
ocol associathange from th
ould use to ditransport typ
points that hawhen the DMAd Password d
ints without a
e CloudAXIS
x to prepend ted by the acccate themselv
point as neede
ed, select CO
he DMA Serve
al to use. For east one SIP A
geographic lochis is optional.
ted with the ahe “SIP” defau
ial the accesse (e.g., an EN
ave access toA settings havdescribed abo
access to SIP
clients will be
to dialing infocess point to ves from thos
ed.
ONFIGURE.
er Access Poi
example, entAP.
cation or som.
ccess point (Sult value or
s point. Your sNUM for H.32
o SIP credentive been
ove), select
credentials, s
e considered
ormation usedroute the call se that require
42
int
ter
me
SIP,
string 23).
ials
select
as
d or to
e
Polycom, Inc. 43
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 ad hoc meetings created on this DMA using CloudAXIS
Polycom, Inc. 44
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.
Polycom, Inc. 45
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).
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. By default, a 10 minute buffer time is set: the 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.
Polycom, Inc. 46
○ Allow use of JoinBridge - Select this checkbox to allow the display and use of the Join Bridge button. When selected, the Join Bridge button is visible on the Schedule a Meeting screen. If not selected, the Join Bridge 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.
Localizing the Services Portal Localize your Services Portal by uploading a language pack made available by Polycom.
To upload a language pack:
1. Select SETTINGS > LANGUAGE. The SETTINGS/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
3. Clic
4. To your br
You ca
CustoCustomizeannounce
To view a
Sele1
c.
ck CLOSE to
upload a newrowser, and c
an return to an
omizing e the email te
ements. View,
Note
Only
an email tem
ect SETTING
return to the
w language paclick UPGRAD
n earlier vers
the Emaemplates you , download an
e: Factory-defi
y super admins
plate:
GS > EMAIL. T
SETTINGS/L
ack, click on BDE.
ion of your La
ail Tempuse for creat
nd edit, or rep
ined Template
can edit factor
The SETTING
Language Pac
Browse … , s
anguage Pack
plates ing and sendplace any of y
es
ry-defined temp
GS/Customize
ck screen.
select the des
k by selecting
ing meeting ayour email tem
plates.
e email templ
sired languag
g REVERT TO
and user accomplates.
lates screen d
e pack file fro
O THIS VERS
ount managem
displays:
47
om
SION.
ment
Polycom, Inc
Clic2whe
Clic3
c.
ck View on anen you click V
ck CLOSE to
ny of the nine View for the M
return to the
existing emaMeeting Crea
Customize em
ail templates. Tate-Update Pa
mail template
The followingarticipants te
s screen.
g screen appeemplate:
ears (see sam
48
mple)
Polycom, Inc
To downl
Stay1to awin
Clic2
To replac
Edit1
Clic1scre
Clic2
Clic3acti
c.
load and edi
ying with the add that tempdow.
ck Save to com
ce an email te
t the downloa
Note
Edit
Note
The mod(http
ck Replace Teeen:
ck on Select T
ck Preview anvate this tem
Note
The ServWheRefebelow
Note
The ensucan
t an email te
Meeting Crelate to your b
mplete the do
emplate:
aded template
e: Template Ed
templates usin
e: HTML Know
person editing ify the referenc://velocity/apac
emplate to up
Template, an
nd Upload toplate.
e: HTML File a
template file invices Portal suben you modify terences/Directivw as being vali
e: Template Fi
template file siure that theseget the image
mplate:
ate-Update Pbrowser for ed
ownload.
e file in your p
diting
ng the HTML Ed
wledge
the template isces or directiveche.org)
pdate any exi
nd select the H
check the loo
nd Template M
ncludes both stabstitutes with inhe template, mves can be addid for the applic
le Size
ze is limited toe images are es from the U
Participants diting. An HTM
preferred text
ditor Sublime a
s assumed to bes, they should
isting templat
HTML file you
ok and feel of
Modification
andard HTML nstance-specificmake sure that vded, moved, orcable type of e
1MB per tempaccessible by
URL.
template asML file starts d
editor.
at http://www.su
be familiar withhave a basic u
te; the followin
u want to upd
f the template
instructions asc details when valid HTML synr removed, but mail message
plate. If any imy any user wh
our example,downloading
ublimetext.com
h basic HTML. understanding
ng options ap
ate from the b
e, and then cl
s well as Refere an individual entax is maintaionly the referemay be used.
mages are linkho may receiv
, click Downloin the browse
m/
If he or she inteof Apache Velo
ppear on your
browser wind
ick Upload to
ences/Directivee-mail is generned.
ences/directive
ked in the HTve the email. T
49
oad er
ends to ocity
r
ow
o
es that therated.
s defined
ML, The user
Polycom, Inc. 50
References/Directives in Email Templates
The email templates contain references/directives that are used to specify per instance information that can be included in the generated email. These references/directives are dynamically replaced with information specific to the specific meeting or user management operation being reported,
Apache Velocity calls variables/methods/conditional statements as “references” and “directives.” These start with a $ tag and a # tag (e.g., $Username, #if, #end).
Here is the list of references/directives used in emails concerning user and password management:
$FIRSTNAME - First name of the User for which the account was created or the password modified
$WSP_URL - URL of the Services Portal on which the account was created or the password modified
$USERNAME – The Username the User can use to log into the Services Portal
$PASSWORD – The Password the User can use to log into the Services Portal
Here is the list of references/directives used in emails concerning meeting invitations and cancellations:
$EVENT_STATUS_HEADING – This is set to either “Invitation” or “Update” appropriately depending on whether the email is being sent to announce a new scheduled meeting or one whose details have been modified
$EVENT_STATUS_BODY – This is set to either “created” or “updated” appropriately depending on whether the email is being sent to announce a new scheduled meeting or one whose details have been modified.
$CREATED_BY_NAME – This is the name of the user who has scheduled the meeting
$CREATED_BY_MAIL – This is the email address of the user who has scheduled the meeting
$EVENT_NAME – This is the name of the meeting as it was defined in the Services Portal
$EVENT_TIME_GMT – This is the scheduled start time of the meeting expressed relative to Greenwich Mean Time
$EVENT_DURATION – This is the scheduled duration of the meeting
$EVENT_DESCRIPTION – This is the agenda of the meeting as defined in the Services Portal
$VMR – This is the VMR number for the meeting
$HTTPS – This is the web URL for joining the meeting
$PARTICIPANT_CODE – This is the participant passcode required to join the meeting
$HOST_CODE – This is the host passcode required to join the meeting with chairperson privileges
#set( $geo = "null") #foreach( $endpoint in $endpoints ) #if($geo != $endpoint.getGeoZone()) #set( $geo = $endpoint.getGeoZone()) )#end #end - This construct in the template encloses an iterative loop that is walked so that all the applicable access points (“endpoints” in the script) can be listed in the invitation using the below directives
$endpoint.getGeoZone() – This is the location string associated with the current access point
Polycom, Inc
$ew
$e
Here are t
c.
endpoint.getTwith the curren
endpoint.getU
two sample im
Transport() – nt access poin
Url() – This is
mages pointe
This is the trant.
the dial string
d to the refer
ansport type (
g associated
rences/directiv
(“SIP”, “H.323
with the curre
ves:
3”, “PSTN”, et
ent access po
tc.) associate
oint
51
ed
Polycom, Inc
c.
52
Polycom, Inc
Resett
This sectiduring ins
Once a teRESET to
SettinThe ServiThis secti
To set the
1. Sel
c.
ting Emai
on shows youstallation.
emplate has bo revert to the
ng Date aces Portal uson shows you
Note:
This seTime Cthe con
e date and ti
ect PLATFOR
il Templa
u how an ema
been edited, ae ‘factory’ tem
and Timses a Networku how to set t
Setup Works
ection specificConfiguration. nfiguration pro
me:
RM SETTING
ates
ail template c
a RESET buttplate.
me k Time Protocthe date and t
heet)
cally refers to Complete the
ocess and to o
GS > DATE T
an be reset to
on displays n
col Server (NTtime for the S
information ee worksheet iobtain inform
IME. The DA
o the default t
next to it as sh
TP Server) foServices Porta
entered in then advance, aation about e
TE TIME scre
template that
hown in the fig
or basic clock al.
e Setup Worksand use it as aeach field.
een displays.
t was shipped
gure. Click
synchronizat
sheet for the a reference du
53
d
tion.
Date uring
Polycom, Inc
2. The
○ NS
○ TS
○ DS
3. Clic
ManagThe Servireceives aidentity of
This sectito view, dthe Servic
c.
e DATE TIME
NTP Server -Services Port
Time Zone - Services Port
Date & Time Services Port
ck UPDATE.
Note
If thesync
ging Ceces Portal reqa self-signed f the Services
on describes ownload, andces Portal.
E screen displ
- Enter the NTtal system. Th
Nothing needtal.
- Nothing neetal.
e: Time Synch
e Services Portchronize the tim
rtificatequires a secucertificate or
s Portal.
how to gened delete certif
ays with the f
TP server IP ahis value mus
ds to be enter
eds to be ent
ronization
tal is restarted me between the
s ure connectiona certificate s
rate self-signeicates; and ho
following text
address or FQst match the d
red in this field
ered in this fie
or data is migre NTP server a
n. When a sesigned by a th
ed certificatesow to upload
boxes:
QDN to synchdata supplied
d. This field d
eld. This field
rated from an oand the Portal.
ecure connecthird party Cert
s and certificathird-party sig
hronize the timto the Experi
displays the ti
d displays the
old server, click
tion is establisrtificate Autho
ate sign requegned and trus
me on the ience Portal.
me zone of th
time of the
k UPDATE to
shed, the broority verifying t
ests (CSRs); st certificates
54
he
owser the
how to
Polycom, Inc
Genera
This sectimust sendcertificate
Note that type, see
To gener
1 Seleman
c.
ating Cer
on shows youd the CSRs to
e. For uploadin
you must logUnderstandin
Cautio
Be surenew ceDeletin
Note:
The certhe usegeneragenerathe comCertific
rate certificat
ect PLATFORnagement scr
rtificates
u how to geneo a third partyng certificates
in as a supeng Account R
on: Overwrite
e you need a rtificate or CSg Certificates
Other Requir
rtificates creaer connection ted for the Exted CSR to a
mponents andates.
tes and CSR
RM SETTINGreen (see nex
and CSR
erate self-signy Certificate As, see Upload
r admin to creRoles.
Warning
new certificatSR overwritess.
rements
ated from CSRto the Servic
xperience PorCertificate A
d Services Po
s:
GS > CERTIFxt) displays.
Rs
ned certificateAuthority for a ding Certificat
eate certificat
te or CSR befs the previous
Rs generatedes Portal. A srtal and RealPuthority, and
ortal. For uplo
ICATE > Gen
es and certific digital signattes or Certific
tes and CSRs
fore followings. To check, s
d by the Servicseparate CSRPresence comthen upload tading to the S
nerate CSR/C
cate sign requture then uploate Chain.
s. To determin
g this procedusee Viewing,
ces Portal wilR needs to bemponents. Sethe signed ceServices Port
Certificate. A
uests (CSRs)oad the signe
ne your accou
ure. GeneratinDownloading
ll only authene externally end the externertificate and ktal, see Uploa
A certificate
55
). You d
unt
ng a , and
nticate
nally key to ading
Polycom, Inc. 56
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.
3 Click GENERATE.
Polycom, Inc
Viewin
Super admThis secti
To view,
1 Selshown
2 Sel
○ V
i.
ii.
iii
○ DcAC
c.
Note:
After geserver mgeneraTo rest
1. 2. 3.
ng, Down
mins use the on shows you
, download,
ect PLATFOR next, display
ect one of the
VIEW Click
After selecCERTIFIC
Paste the t
. Rename th
If the file
DELETE Clcertificates. WAuthority-signCSRs.
Restart Servi
enerating youmust be restating CSRs. art: Using your SLogin as a prRestart serve
loading, a
certificate listu how to view
, or delete c
RM SETTINGys any existing
e following op
to view and/o
cting VIEW, coCATE
text in to a tex
he extension
is a CSR, you
ick to delete tWebserver cerned certificate
ices Portal Se
ur certificate, tarted to recog
SH client, accrivileged admer: services
and Dele
t to confirm if w, download, a
certificates
GS > CERTIFg certificates.
ptions:
or download t
opy the entire
xt file
.cer.
u can now se
the certificatertificates can e. To generate
erver
the tomcat6 agnize the certi
cess the Servinistrator usins <SomeServ
ting Cert
a certificate iand delete ce
and CSRs:
ICATE > Cer
the certificate
e hash from --
nd the file to
e. This option only be regene a WebApp c
and nginx servificate. Note t
vices Portal Fng [caxis/caxiver> resta
tificates
s needed andertificates in th
rtificate list. T
. To downloa
---- BEGIN C
a third-party C
is only availanerated or upcertificate, se
rvers on the Sthat a restart
FQDN. s]. art
d to delete obhe Services P
The Certificat
ad:
ERTIFICATE
CA for signin
able to WebAploaded as a Cee Generating
Services Portais not needed
bsolete certificPortal.
te list screen,
E to ----- END
g.
pp-trust Certificate g Certificates
57
al d for
cates.
D
and
Polycom, Inc
Upload
The Servicertificateestablish Upload thserver, SMtrust certif
To uploa
1 Sel
2 Pe
a
i.
ii.
iii
c.
Cautio
Deletin
ding Cert
ces Portal enes signed by aa secure come trust certific
MTP server, aficates to the
ad certificat
ect PLATFOR
rform the follo
To upload a
Select the
Click the C
. Navigate to
on: Deleting T
g trust certific
tificates o
nables super aa Certificate Ammunication wcate for serveand DMA sysServices Por
tes:
RM SETTING
owing:
third-party sig
WebServer O
Choose File
o the certifica
Trust Certifica
cates can bre
or Certific
admin users tAuthority and with users anders that requirtem. This sec
rtal.
GS > CERTIF
gned certifica
Own option in
button.
ate or certifica
ates
ak the chain o
cate Chai
to upload twotrust certificatd verify the ide secure com
ction shows y
ICATE > Upl
tes
n the Type dro
ate chain, and
of certificate t
in
o types of requtes. Upload th
dentity informammunication syou how to up
oad Certifica
opdown menu
d select Open
trust.
uired certificahe signed ceration of Servicsuch as the Apload signed t
ate as shown
u.
n.
ates: third parrtificate to ces Portal se
Active Directorthird party and
n next.
58
rty
rvers. ry d
Polycom, Inc
iv
b
i.
ii.
iii
iv
SelectThe Serviselect a lothat can b
This sectidownload
To select
1 Sele
c.
v. Click UPLO
To upload a t
Select the
Click .
. Navigate to
v. Click UPLO
Note
UploExpl
Note:
After uprestarteTomcat To rest
1 UFQD2 Lo3 R
ting andces Portal log
og level, the Sbe downloade
on explains e the log file.
t a log level o
ect PLATFOR
OAD.
trust certificat
WebServer T
.
o the certifica
OAD.
e: Upload Cert
oading certificatorer 8 or 9, use
Restart Servi
ploading the ted to recognizt server need
art: sing the vSph
DN, access thog in using “c
Restart servers
d Downlg levels are lisServices Portaed.
each log level
or download
RM SETTING
te.
Trust option in
ate, and selec
tificates Brows
tes is only suppe another brow
ices Portal Se
third-party sigze the certificas to be restar
here console he Services Pcaxis” for boths by entering
oading sted by hieraral prints the s
, shows you h
the log file:
GS > LOGS. T
n the Type dro
ct Open.
ser Requirem
ported in Internwser (e.g., Chro
erver
gned certificatate. If you arerted.
or by connecortal console
h your usernathe command
Log Levrchy and disp
selected level
how to select
The logs leve
opdown men
ents
net Explorer 10ome or Firefox)
te, the NGINXe uploading a
cting via an SS.
ame and passd: services
vels played in a dro, along with a
a log level to
l options scre
u.
0 or higher. If yo) to upload cert
X and Tomcata trust certifica
SH client to th
sword. s <SomeServ
opdown menall the lower le
o print, and sh
een displays a
ou have Interntificates.
t servers musate, only the
he Services P
ver> resta
u. When you evels, to a log
hows you how
as shown nex
59
et
st be
Portal
art
g file
w to
xt.
Polycom, Inc
2 Selenex
3 Cho
○ A
○ T
○ D
○ I
○ W
○ E
○ O
4 Sele
○ C
○ C
c.
ect the Level xt.
oose one of th
ALL Turns o
TRACE Lo
DEBUG Log
INFO Logs
WARN Logs
ERROR Log
OFF Turns
Note:
When aexampl
ect one of the
Click UPDAT
Click DOWNL
dropdown me
he following lo
on all logging
gs finer-grain
gs fine-graine
messages tha
s potentially h
gs errors that
off the loggin
Log Level Hie
a log level is sle, selecting I
e following op
TE to begin pr
LOAD to dow
enu to display
og levels:
g.
ned informatio
ed information
at highlight th
harmful situat
t might still all
g.
erarchy
selected, all lenfo will print t
ptions:
inting from th
wnload the log
y all log level
on than Debug
n that are help
he progress of
tions.
ow the Servic
evels beneaththe Info, Debu
e selected lev
g file.
options, in hi
g. These logs
pful for debug
f the applicat
ces Portal to
h the selectedug, and Trace
vel.
ierarchical ord
s are also hel
gging.
ion at a coars
keep running
d level are alse levels.
der, as shown
pful for debug
se-grained lev
.
so printed. Fo
60
n
gging.
vel.
or
Polycom, Inc. 61
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
2. Ent
To validat
3. Ver
Read the
c.
ter the Admin
te the user rig
rify and Begin
final disclaim
Credentials
ghts, enter the
n Migration
mer, and click Y
e admin usern
YES when yo
name and pas
ou are ready t
ssword for th
to begin the m
e new Servic
migration.
ces Portal.
62
Polycom, Inc. 63
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
5. Mig
Wait for thsuccessfuconfigurat
6. Ver
When theand verify
c.
grating Setting
he User Interfully imported. tion before re
rifying Migratio
e Services Poy that the setti
Note:
Once thpoint to
gs and Databa
face to indicaOnce this im
ebooting itself
on
rtal VM has reings are corre
Verifying Mig
he data is suco the new Ser
ase
te that the infport has finis.
estarted, log ect.
gration
ccessfully migrvices Portal.
formation fromhed, the Serv
in with the ad
grated, make
m the old Servvices Portal w
dmin credentia
sure that the
vices Portal hwill take a whil
als from the o
DNS records
has been le to do an int
old Services P
s are updated
64
ternal
Portal,
d to
Polycom, Inc
ActivaLicense aThe Serviconfigure CloudAXI
Activate yavailable.
To activa
1. Ope
2. Selmode,
c.
ating Licactivation for t
ces Portal licthe Services S product use
your licenses
NoteThe licen
ate the Servic
en your Servi
ect PLATFORdisplays.
censes he Services Pense, which iPortal. The E
ers, must also
in either an o
e: Experience Experience Po
nses on the Se
ces Portal lic
ces Portal, an
RM SETTING
Portal and thes your CloudA
Experience Poo be activated
online or an of
Portal URLortal license Uervices Portal
cense from th
nd log in (“ad
GS > LICENS
e Experience AXIS productortal license, d.
ffline mode. O
URL must be c.
he online mo
min/admin”) a
E. The follow
Portal is dont license, muswhich lets yo
Online and off
configured be
ode:
as a super ad
wing screen, in
e through thest be activatedou determine t
fline license d
efore setting E
dmin as in the
n the default O
e Services Pod before you the number o
deactivation is
Experience Po
e following scr
Online Activa
65
ortal. can
of
s also
rtal
reen.
ation
Polycom, Inc. 66
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. 67
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
3 CopPortal
4 Sel
5 Senis founAdmin
6 Clic
Repeat st
7 Clic
To activa
Ope1
c.
py the ServiceActivation K
ect Downloa
nd the Activatnd just above istrator. An A
ck Choose Fi
teps 3 to 6 ab
ck ACTIVATE
ate the Exper
en the Experie
es Portal ActiKey: block on
d Activation
tion Request the Service P
Activation Res
le to select a
bove to activa
E to activate th
rience Portal
ence Portal, a
vation Key yon your screen.
Request File
File you havePortal Activatiponse File is
nd upload yo
te the Experie
he Services P
connection
and log in usi
ou received in.
e. The Activa
e just downloaion Key: field)automatically
ur Activation
ence Portal w
Portal license
to the Servic
ng ‘admin’ as
n an email, an
ation Request
aded, along w) in an email ty sent back to
Response Fi
while in the Of
.
ces Portal
s both your Us
nd Paste it int
t File downloa
with your Hostto your Polycoo you.
le.
ffline mode.
ser Name and
to the Service
ads.
t/Device ID (wom License
d Password.
68
e
which
Polycom, Inc
Whe2Gen
Firs3bein
Nex4acc
c.
en the Experineral Settings
st, in the Liceng used to pro
xt, in the Licencess the Licen
ience Portal os screen displ
nse Server Uocure your lic
nse Server Cnse Server.
opens, select lays.
URL field blockcensing inform
redentials fiel
Settings > E
k (see next scmation.
ld, enter the U
Environment
creen), enter
Username an
> General S
the URL of th
nd Password b
ettings. The
he Services P
being used to
69
Portal
o
Polycom, Inc
Clic5
Whe6
This
To view t
1. Sel
2. Clic
c.
ck Submit, and
en the Apply
s will display
the license in
ect Maintena
ck Go to get y
d then select
Configuration
the license in
nformation in
ance > Tools
your Experien
Maintenance
n screen displ
nformation for
n the Experie
> Get Licens
nce Portal lice
e > Tools > Ap
lays, click Go
r the Experien
ence Portal
se Info.
ense informati
pply Configur
o to apply the
nce Portal.
ion as in the f
ration.
configuration
following sam
n.
mple screen:
70
Polycom, Inc
Config
To config
1. Ope
2. Selbe con
c.
guring P
gure your pro
en the Service
ect Platform nfigured as eit
NoteFor S
Proxy Se
oxy settings
es Portal, and
Settings > Pther Authentic
e: Proxy SuppSoftware Rele
ettings
in the Servic
d log in (“adm
Proxy. By defcated or Non-
ort ease 1.3.1, we
ces Portal
min/admin”) as
fault, proxy co-authenticated
only support
s a super adm
onfigurations d.
HTTP Forward
min.
are not enabl
d Proxy.
led. A proxy c
71
can
Polycom, Inc. 72
Configuring a Non-Authenticated Proxy
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. 73
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. 74
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 DMA Settings
Configuring the VMR Settings
Configuring Connection Settings
Configuring Authentication Provider 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. 75
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
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.
License Server URL This is the URL of the Services Portal used to get the Licensing information.
License Server Credentials This is the Username and Password used to access the License server.
Polycom, Inc. 76
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.
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.
Polycom, Inc
ConfigThis sectiSettings a
To config
1 WitEnv
The
c.
Cautio
To enanot be a
guring ton will help y
applies to all s
gure the Gen
h the Systemvironment >
e screen displ
on: Log Level
ble more thanautomatically
the Enviou configure subcomponen
neral Settings
AdministratioGeneral Sett
lays a list of te
and Log Targ
n the default Ly deleted and
ronmenthe general snts within the
s:
on applicationtings as show
ext box fields
get Settings
Log Level andmay use all o
nt Genersettings in thespecified env
n open in youwn in the follo
s as shown in
d Log Targetsof the remaini
ral Settine Administratiovironment.
r browser, at owing screen
the next scre
s, be aware thing disk space
ngs on application
the Settingsexample.
eens.
hat the log filee on your driv
n. The Gener
s tab select
77
es willve.
al
Polycom, Inc. 78
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. Must be selected to enable the environment.
Shared Secret The shared secret key for the environment used for secure communications. This SHOULD NOT be modified by the user.
Polycom, Inc. 79
Field Name Value/Description
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.
Polycom, Inc. 80
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.
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. 81
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.
Authmatch 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.
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. 82
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.
Polycom, Inc
Field Na
Skin
5 Clic
ConfigThis secti
To config
1 Witand
The
c.
ame
ck Submit.
Note
To dadho
guring Don describes
gure the DMA
h the Systemd then Enviro
e DMA Setting
e: Lobby Rule
isable users frooc.cloudaxis loc
DMA Setthe steps use
A Settings
Administratioonment (defa
gs screen dis
Route
om directly diacal should be ^
ttings ed to configur
on applicationult.local) > A
plays (see fo
Value
The CSS smatching tMODIFIED
ling a VMR or J^$.
re the DMA s
n open in youAgents > DMA
llowing two sc
skin that will bthis Lobby RuD unless othe
Join Bridge fun
ettings in the
r browser, seA Settings a
creens).
be applied to ule. This SHOerwise specifie
nctionality, the
Administratio
elect the Settis shown next
meetings OULD NOT BEed.
Lobby Rule for
on application
ings tab at tht.
83
E
r Route
n.
e top,
Polycom, Inc. 84
Polycom, Inc. 85
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.
Table 18: 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.
Polycom, Inc. 86
Field Name Value/Description
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.
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
Target Credentials Enter your Username and Password to access this resource.
Enforce Certificate Validation Check this option to verify the DMA’s certificate as a security measure.
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.
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.
Polycom, Inc. 87
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).
The resultant Personal VMR screen displays a list of text fields. A partial Personal VMR screen with its initial data fields is shown next.
Polycom, Inc. 88
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 the value of any field that is not listed in Table 19.
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 and the agent start, the number of seconds to delay startup should be entered here. This is especially relevant on older, slower servers.
Polycom, Inc. 89
Field Name Value/Description
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. The correct type for VMR agents is static/polycom.mea.agent.wsp-static
Roles Describes which role type should be assigned to an agent. In the Role dropdown box, select ConferenceManager for your Personal VMR agent.
To add agent roles, click on the button.
Experience Portal URL This field is for future product functionality. For now, leave blank unless explicitly told to do otherwise.
Target Url The URL of the DMA or the Services Portal.
Target Credentials Enter your Username and Password to access this resource.
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.Description This describes what the template is about and for.
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. Click the button to add additional user roles and meeting exit URLs.
Polycom, Inc
Field Na
Templat
TemplatAccessP
TemplatAccessP
TemplatAccessP
TemplatAccessP
TemplatAccessP
TemplatAccessP
TemplatConferen
TemplatSharedC
Usernam
Templat
Templatautoope
Templatautoope
c.
ame
e.ExternalCo
e.ExternalCoPoints
e.ExternalCoPoints[#].DialS
e.ExternalCoPoints[#].Loca
e.ExternalCoPoints[#].POP
e.ExternalCoPoints[#].Tran
e.ExternalCoPoints[#].Auth
e.ExternalConceId
e.ExternalCoCredentials
me/Password
e.FeatureExt
e.FeatureExtn.query
e.FeatureExtn.value
nferences
nferences[#].
nferences[#].String
nferences[#].ation
nferences[#].PAddress
nferences[#].sport
nferences[#].enticationMo
nferences[#].
nferences[#].
ensions
ensions[#].me
ensions[#].me
de
enu.
enu.
Value/Des
The full diathe addresDMA/RPA
This shoulServices P
The addrethe same a
The transpotherwise.
This is theto your accselection hthe DMA C
This is theconnectioninstructed
Enter the sis set.
This is a fu
This is a fu
scription
al string for coss after the @
AD.
Note
The Dshouthe DPorta
ld match the lPortal for the
ess of the DMAas configured
port type shou.
e Authenticatiocess points. There should mConfig screen
e conference Ins to VMRs. Dto.
shared SIP cr
uture release
uture release
onnecting to V@ symbol to p
: Dial Prefix V
Dial Prefix partld match the A
DMA Config scral.
location of theDMA.
A/RPAD to bed on the Servi
uld be SIP un
on Mode you The Authenticmatch the Autn of the Servic
ID code for esDo Not chang
redentials if th
feature; do n
feature; do n
VMRs. Modifyoint to the
Value
t of this selectioAuth Mode valuereen of the Ser
e POP in the
e used; this isices Portal.
nless stated
want to assigcation Mode th Mode valueces Portal.
stablishing ge unless
he AUTH mod
not edit.
not edit.
90
y
on e in rvices
s
gn
e in
de
Polycom, Inc. 91
Field Name Value/Description
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.
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.RecordingAvailable Do not edit this variable.
Template.Settings.RequireDisplayName Do not edit this variable.
Polycom, Inc. 92
Field Name Value/Description
Template.Settings.RequireEmailAddress Do not edit this variable.
Template.Settings.VideoPreference Do not edit this variable.
Template.Settings.VideoPreference[#] Do not edit this variable.
Add additional fields by clicking on the button.
Click Submit.
Polycom, Inc. 93
Configuring Connection Settings This section provides the field names and value descriptions needed to configure the Services Portal Connection (WSPConf) settings in the Administration application.
1. 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 the initial data fields in the WSPConf Settings screen selection. Table 20 contains the complete list of these data field names with their value descriptions and includes nearly forty Template fields.
Polycom, Inc. 94
Table 20: 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.
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 URL of the DMA (including the port for API communication) or the URL of the Services Portal (for a scheduling or authentication agent). Example: https:// servicesportal.example.com
Target Credentials Enter your Username and Password to access this resource.
Enforce Certificate Validation Check this option to verify the DMA’s certificate as a security measure.
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 a future release feature; do not edit.
Template.LobbyRoute This is a future release feature; do not edit.
Polycom, Inc. 95
Template.Description This describes what the template is about and for.
Template.OrganizerUserEmail This is a future release feature; do not edit.
Template.ExitMeeting Actions
Template.ExitMeetingActions[#].Role
This is a future release feature; do not edit.
Template.ExitMeetingActions[#].Url This is a future release feature; do not edit.
Template.ExternalConferences
Template.ExternalConferences[#]. AccessPoints
This is a future release feature; do not edit.
Template.ExternalConferences[#]. AccessPoints[#].DialString
This is a future release feature; do not edit.
Template.ExternalConferences[#]. AccessPoints[#].Location
This is a future release feature; do not edit.
Template.ExternalConferences[#]. AccessPoints[#].POPAddress
This is a future release feature; do not edit.
Template.ExternalConferences[#]. AccessPoints[#].Transport
This is a future release feature; do not edit.
Template.ExternalConferences[#]. AccessPoints[#].AuthenticationMode
This is the Authentication Mode you want to assign to your access points. The Authentication Mode selection here should match the DMA value on the Services Portal.
Template.ExternalConferences[#]. ConferenceId
This is a future release feature; do not edit.
Template.ExternalConferences[#]. SharedCredentials
Username/Password
Enter the shared SIP credentials if the AUTH mode is set.
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. 96
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
This is a future release feature; do not edit.
Template.Settings. AuthenticatedUsersHostDomainJoinAs
This is a future release feature; do not edit.
Template.Settings. AuthenticatedUsersOtherDomainJoinAs
This is a future release feature; do not edit.
Template.Settings.DefaultSurfaceHeight This is a future release feature; do not edit.
Template.Settings.DefaultSurfaceWidth This is a future release feature; do not edit.
Template.Settings.HelpUrl This is a future release feature; do not edit.
Template.Settings.Locked This is a future release feature; do not edit.
Template.Settings.GeoLocation This is a future release feature; do not edit.
Template.Settings.RecordingAvailabled This is a future release feature; do not edit.
Template.Settings.RequireDisplayName This is a future release feature; do not edit.
Template.Settings.RequireEmailAddress This is a future release feature; do not edit.
Template.Settings.VideoPreference This is a future release feature; do not edit.
Template.Settings.VideoPreference[#] This is a future release feature; do not edit.
2. Click Submit when you have finished your configuration.
Polycom, Inc. 97
Configuring 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 in the next two screen samples:
Polycom, Inc. 98
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 21: 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.
Auto Restart Determines if the agent can be automatically restarted when the configuration updates. This can affect call stability and is enabled by default.
Polycom, Inc. 99
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 URL of the DMA (including the port for API communication) or the URL of the Services Portal (for a scheduling or authentication agent).
Target Credentials Enter the Username and Password of the target URL to access this resource.
Enforce Certificate Validation Check this option to verify the Services Portal’s certificate as a security measure.
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.
Allow login to persist Check this option to allow users to be remembered during login.
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.
Polycom, Inc. 100
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.
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.
Polycom, Inc. 101
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.
Polycom, Inc. 102
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. 103
Table 22: Admin UI Setting Fields
Field Name Value/Description
admins
admins[0]
Provides the credentials for admin UI settings. Requires a Username and Password.
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.
Polycom, Inc
Field Na
SSL Cer
certificat
port
securepo
To chang
1 SelePas
2 To c
c.
ame
rtificate Privat
tes[0].usage
ort
Cautio
Ensureentering
ge the System
ect Settings ssword) for ad
change the p
te Key
on: Verify SSL
that both theg and restarti
m Administra
> Admin UI. dmins[0] as s
assword, ente
L Certificate a
e SSL Certificng the server
ation applica
The Admin Uhown next.
er the new pa
Value/Des
Displays thgenerate t
Allows youin determinthe VM.
Default poPortal serv
Default seExperienceCHANGE
and Private K
ate and the Sr.
ation passwo
UI screen app
assword in the
scription
he raw text ofthe certificate
u to choose bning how the
ort setting for aver’s Admin U
cure port sette Portal serveTHIS
Key Validity
SSL Certificat
ord:
pears with two
e Password
f the private k’s CSR.
between servecertificate file
accessing theUI. DO NOT C
ting for acceser’s Admin UI
e Private Key
o text boxes (
field.
key used to
er and trustede pair is used
e Experience CHANGE THI
ssing the I. DO NOT
y are valid bef
Username an
104
droot by
IS.
fore
nd
Polycom, Inc. 105
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.
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
Polycom, Inc. 106
To export the Experience Portal configuration file:
1 Select Maintenance > Tools > Export Configuration.
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
The
2 Seleserv
3 Clic
LocalYou can lo
Upl
List
To upload
1 Sele
The
c.
e Import Conf
ect Choose Fver.
ck Upload. Th
Note
OnceconfiPorta
izing theocalize the Ex
oad a langua
t a language p
NoteExpethe a
d a language
ect Localizat
e Upload lang
figuration scre
File, and loca
he page will re
e: Configuratio
e the configuraiguration. Noteal are registere
e Experixperience Po
age pack
pack
e: Experience erience Portaladmin portal.
e pack:
tion > Upload
guage pack sc
een displays a
ate the setti
efresh.
on Application
ation is importee that the licensed to the same
ience Poortal. Localizat
Portal Localiz localization is
d language p
creen displays
as shown nex
ings.json c
n
d, apply the cose will be deactServices Porta
ortal tion capabiliti
zations currently on
pack as show
s:
xt.
configuration
onfiguration or rtivated if two dial server.
es include:
nly supported
wn next.
file you want
restart the servifferent Instanc
for the user e
t to import to t
ver to apply theces on the Expe
experience and
107
the
e erience
d not
Polycom, Inc. 108
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
C3:Acc
After succusers throadmin accmanage a
This chap
Und
Cre
Edit
Del
Cha
Res
UndeThe Servidifferent s
SupandFig
Admme
Usesho
c.
Creatincounts
cessfully deplough the Activcounts add anadmin and use
pter shows yo
derstanding A
eating Accoun
ting Accounts
eting Accoun
anging Your P
setting a Pass
erstances Portal su
set of capabili
per Admin d user accounure 4.
min Createetings. Admin
er Creates aown in Figure
Note:
Loggingfigures
ng ans
oying and cove Directory. Tnd manage suer accounts.
u the followin
Account Roles
nts
s
ts
Password
sword
ding Aupports three ties. See the
Creates and nts, but canno
s and managn accounts dis
and manages6.
Identifying Yo
g in to the Seis a good wa
nd Ma
nfiguring youThe account uper admin, aUser account
ng:
s
Accoundifferent accofollowing list
manages theot schedule m
es admin accsplay the tabs
s online video
our Role
rvices Portal y to confirm y
nagin
r Services Potypes you creadmin, and usts cannot add
nt Roleount roles. Eafor a brief de
e Services Pomeetings. Sup
counts, user as shown in Fi
o conference m
and comparinyour assigned
ng Us
ortal, create ueate depend oser accounts.d or manage a
es ach role deterscription of e
ortal settings aper admin acc
accounts, andgure 5.
meetings. Us
ng your availad role.
ser
ser accountson your accou Admin accouany accounts
rmines your aach role:
and other supcounts display
d online video
ser accounts d
able tabs with
locally or addunt role. Supeunts add and .
account type a
per admin, ady the tabs sho
o conference
display the ta
h the following
109
d er
and a
min, own in
bs
g
Polycom, Inc
Figure 4: S
Figure 5: A
Figure 6: U
c.
Super Admin
Admin Role Ta
User Role Tab
Role Tabs
abs
bs
110
Polycom, Inc
CreaThe Servilocally. Th
AddinThe LDAPwithout reServices Ponly if youEditing Ac
Adding A
1. Se
c.
ating Aces Portal en
his section sh
Note
The
ng ActiveP server confiequiring the adPortal assignsu need to chaccounts Creat
Note:
Before an adm
Active Directo
lect USER M
Accounnables super aows you how
e: Default Acco
following def
admin - Usadmin/adm
meaconf -(Username
meaauth -(Username
measys – (Username
Super admchanged aslevel of useadmin auth
e Directiguration enadministrator tos user roles to
ange the defauted from the A
Before You B
adding an Acmin or super a
ory users:
ANAGEMEN
nts admin and ad
w to add active
ounts
fault accounts
se for accessmin)
Use for confe/Password =
Use for authe/Password =
Use for license/Password =
mins should ens soon as poser to log in to horization.
tory Usebles access to explicitly creo all the Activult user role oActive Directo
Begin
ctive Directorydmin.
NT. The USER
dmin users to e directory us
s are required
ing the Servic
ference comm= meaconf/me
entication com= meaauth/me
se communic= measys/mea
nsure that thessible. Failurethe Services
ers o Services Poeate each Se
ve Directory aor to block theory.
y user accoun
RS screen dis
create accousers and how
d and cannot
ces Portal (U
munication witeaconf)
mmunication eaauth)
cations with thasys)
e passwords fe to change thPortal with th
ortal for all thervices Portal accounts. Adde user. To cha
nt, you must l
splays, shown
unts from the to create loca
be deleted:
sername/Pas
th the Experie
with the Expe
he Experience
for the above hese passwohese credenti
e users in theaccount. By
d a user from ange the defa
og in to the S
n next.
Active Directal accounts.
ssword =
ence Portal.
erience Porta
e Portal.
default accourds would alloals and with s
e Active Direcdefault, the Active Direct
ault user role,
Services Porta
111
tory or
al.
unts are ow any super
ctory
tory see
al as
Polycom, Inc
2. Clic
3. In thpress E
4. Pla
5. Clic
c.
ck + LDAP US
he Import ActEnter on you
ce a checkma
ck ADD.
Note:
Users athe role
SER. The Imp
tive Directory r keyboard.
ark in the che
Active Directo
added from the type, see Ed
port Active Di
y Users search
eckbox of eac
ory Default U
he Active Direditing Accoun
irectory Users
h box, enter t
h user you wa
ser Roles
ectory are assts.
s screen disp
he name of th
ant to add.
signed the use
lays, shown n
he user you w
er role by def
next.
want to add an
fault. To chan
112
nd
nge
Polycom, Inc
AddinThe Serviyou how t
Adding l
1 Sel
2 Clic
c.
ng Localces Portal ento create loca
Note:
Before super a
local users:
ect User Man
ck + User. Th
l Users nables super al accounts.
Before You B
adding a locaadmin.
:
nagement. Th
e Add a user
admin and ad
Begin
al user accou
he Users scre
r screen displa
dmin users to
nt, you must
een displays.
ays:
add other loc
log in to the S
cal users. Thi
Services Port
is section sho
tal as an adm
113
ows
in or
Polycom, Inc
3 Ent
○ F
○ L
○ U
○ E
○ C
○
○ D
c.
ter the followin
First Name
Last Name
User Name
Email Addre
Contact Num
Title Enter t
Department
ng in the Add
Enter the us
Enter the use
Enter a user
ss Enter the
mber Enter t
the user’s job
Enter the us
d a user scree
er’s first nam
er’s last name
rname for the
e user’s emai
the user’s pho
b title.
ser’s departm
en:
e.
e.
user.
il address.
one number s
ment.
starting with the area codee.
114
Polycom, Inc
○ C
○ U
»
»
»
4 ClicURL.
The ServiEditing Ac
EditiThe ServiDirectory fields (roleyou how t
EditinThis sectionly edit tthat only s
To edit a
1. Sel
c.
City Enter t
User Role C
» ROLE_SUthe user hand super DMA confi
» ROLE_ADthe user haccounts a
» ROLE_USassigned, meetings.
ck Add. An em
ces Portal enccounts and D
ng Acces Portal enor locally. Yoe type and ento edit both Ac
ng Accouon shows youthe role type asuper admin u
Note:
Before super a
user accoun
ect User Man
he user’s city
Click the Use
UPER_ADMINas super admadmin accou
iguration, and
DMIN This oas admin privand creating a
SER This opthe user has
mail is sent to
nables you to Deleting Acco
countsnables admin ou can accessnable/lock) in ctive Director
unts Creu how to edit and enable/lousers can cha
Before You B
you edit an aadmin.
nt created fro
nagement. Th
y.
r Role dropdo
N This optiomin capabilitieunts and confid certificate up
option is availavileges, whichand participat
ption is availastandard use
o the newly cr
edit or deleteounts.
s and super ad
s all fields in aan account im
ry and local ac
eated froan account c
ock options in ange a role ty
Begin
account, you m
om the Activ
he Users scre
own box, and
n is only avaies, which incluiguring and mploads.
able to adminh includes creting in video c
ble to both ader privileges a
reated user co
e the accounts
dmin users to a locally creatmported from ccounts.
om the Areated from taccounts imp
ype to super a
must log in to
ve Directory:
een displays,
choose one
ilable to supeudes creating
managing the
n and super aeating and maconference m
dmin and supand can only c
ontaining thei
s you create.
edit accountsted account, bthe Active Di
Active Dhe Active Direported from thadmin.
the Services
shown next.
of the followin
er admin usersg and managin
core settings
admin users. Wanaging user
meetings.
per admin usecreate and pa
ir username,
For more info
s created frombut you can oirectory. This
Directoryectory. To reihe Active Dire
s Portal as eit
ng options:
s. When assigng user, adm
s, social policy
When assigneand admin
ers. When articipate in
password, an
ormation, see
m the Active only access tw
section show
y iterate, you caectory. Also n
her an admin
115
gned, in, y,
ed,
nd
e
wo ws
an note
n or a
Polycom, Inc
2. Entscroll b
3. Clic
4. To
○ Rtss
○ Ruc
○ Rt
5. Clicrem
6. Clic
c.
ter the user’s bar.
ck the accoun
edit the User
ROLE_SUPEthe user has ssuper admin asystem config
ROLE_ADMIuser has admcreating and p
ROLE_USERthe user has s
ck to enter a cmove the chec
ck SAVE.
name in the s
nt’s icon. T
Role, click th
ER_ADMIN super admin accounts andguration, and
N This optiomin privileges,participating i
R This optionstandard use
check mark inck mark and d
search box, a
The Edit User
he dropdown b
This option iscapabilities, w
d configuring acertificate up
on is available which includin video confe
n is available r privileges an
n the Enable Udisable the us
and press Ent
r screen displa
box arrow and
s only availabwhich includeand managing
ploads.
e to admin anes creating a
erence meetin
to both admind can only c
User checkboser’s account.
ter on your ke
ays, shown n
d select one o
ble to super ades creating ang the core se
nd super admand managingngs.
n and super acreate and pa
ox and activat.
eyboard or se
ext.
of the followin
dmin users. Wnd managing uettings, social
min users. Wheg user and ad
admin users. articipate in m
te the user’s a
earch using th
ng options:
When assigneuser, admin, policy, DMA
en assigned, min accounts
When assigneetings.
account, or
116
he
ed, and
the s and
ned,
Polycom, Inc
EditinSuper admchange aldetermine
This secti
To edit a
1. Sel
2. Lockeyboa
c.
ng Localmin users canll of the fields e your accoun
on shows you
Note:
Before admin.
a local user
ect User Man
cate the accouard.
ly Creatn change all oin a locally c
nt type, see U
u how to edit
Before You B
you edit an a
r account:
nagement. Th
unt by enterin
ted Userof the fields inreated accou
Understanding
a locally crea
Begin
account, you m
he Users scre
ng the user’s n
r Accoun a locally crent except for
g Account Rol
ated user acco
must log in to
een displays:
name in the s
nts ated accountthe role in a sles.
ount.
the Services
search box an
t. Admin userssuper admin
s Portal as an
nd pressing E
s, meanwhileaccount. To
admin or sup
Enter on your
117
e, can
per
Polycom, Inc. 118
3. Click the account’s icon; the Edit User screen displays:
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
○ C
○ U
»
»
»
○ Ea
5. Clicpassw
DeleUsers withadmin accUnderstan
This secti
c.
City Edit the
User Role E
» ROLE_SUthe user hsuper admsystem co
» ROLE_ADuser has aand creatin
» ROLE_USthe user h
Enable User account or re
ck Save. An eord, and URL
ting Ah super admicounts can onnding Accoun
on shows you
Cautio
The foll
A
M
M
M
Super achangeuser to authoriz
Note:
Before admin.
e user’s city.
Edit the User
UPER_ADMINas super adm
min accounts anfiguration, a
DMIN This optadmin privilegng and partic
SER This optioas standard u
Click to entemove the che
email is sent tL.
ccounn accounts canly delete othnt Roles.
u how to dele
on: Default Ac
lowing defaul
Admin - Used
Meaconf - Us
Meaauth - Us
Measys – Use
admins shouled as soon as
log in to the Szation.
Before You B
you delete an
Role by selec
N This option min capabilitieand configurin
and certificate
tion is availabges, which incipating in vide
on is availabluser privileges
er a check maeck mark and
o the owner o
ts an delete otheer admin and
ete a user acc
ccounts
t accounts ar
d for accessin
sed for confer
sed for authen
ed for license
d ensure thats possible. FaServices Port
Begin
n account, yo
cting one of th
is only availaes, which inclung and manag uploads.
ble to admin aclude creatingeo conference
e to both adms and can on
ark in the Enadisable the u
of the edited u
er super admd user accoun
count.
re required an
ng the Service
rence commu
ntication comm
e communicat
t the passworilure to changtal with these
u must log in
he following o
able to super aude creating aging the core
and super admg and managine meetings.
min and superly create and
able User cheuser’s accoun
user account
min, admin, annts.) To determ
nd cannot be
es Portal.
nication with
munication w
tions with the
rds for the aboge these pass credentials a
to the Servic
options:
admin users. and managing
e settings, soc
min users. Wng user and a
r admin users participate in
eckbox and acnt.
containing th
nd user accoumine your acc
deleted:
the Experien
with the Exper
Experience P
ove default acswords wouldand with supe
ces Portal as
When assigng user, admincial policy, DM
When assignedadmin accoun
s. When assign meetings.
ctivate the us
he username
unts. (Users wcount type, se
ce Portal.
ience Portal.
Portal.
ccounts are d allow any lever admin
an admin or s
119
ned, n, and MA
d, the nts
gned,
er’s
,
with ee
vel of
super
Polycom, Inc
To delet
2 Sele
3 Locnam
4 Clic
5 Clic
ChanThis secti
To chang
1 Log
2 Clic
The
c.
e a user acc
ect the User
cate the accoume, username
ck the accoun
ck Delete.
nging Yon explains h
ge your pass
g into your Se
ck on the
e Change Pas
count:
Managemen
unt by enterine, email addre
nt’s icon; th
Your Phow to change
word:
ervices Portal
icon on the le
ssword scree
t tab; the Use
ng the user’s ness, type, role
he Delete this
Passwoe your passw
account. You
eft side of you
n appears as
ers screen dis
name in the se, and status
s User? scree
ord ord.
ur name appe
ur name as sh
shown next.
splays:
search box anall display as
en displays.
ears in the top
hown next.
nd pressing Es in the followi
p right corner
Enter. The useing screen:
of the screen
120
er’s
n.
Polycom, Inc
3 Ent
○ C
○ N
○ C
4 Clic
ReseThis secti
c.
er the followin
Current Pass
New Passwo
Confirm new
ck Change to
etting aon shows how
Cautio
Passworan acco
Note:
Before a super
ng in the Cha
sword Ente
ord Enter yo
w password
change your
a Passw an admin o
n: Before Rese
rds should onlyunt with an ina
Before You B
you reset a pr admin.
ange Passwor
er your curren
our new passw
Reenter you
r password.
swordor a super adm
etting a Passwo
y be reset for aactive email ad
Begin
password, you
rd screen:
t password.
word.
ur new passw
min can reset
ord
accounts with vddress will lock
u must log in t
word.
t a user’s pas
valid email addk out the user.
to the Service
sword.
dresses. Resett
es Portal as e
ting a passwor
either an adm
121
rd for
min or
Polycom, Inc
To reset
5 Clic
6 Locsea
7 Clic
8 Ent
The Servi
c.
t a passwor
ck User Mana
cate the user arch box, and
ck the accoun
er a new pas
ces Portal se
rd:
agement. The
in the NAME press Enter
nt’s icon. T
sword in the
ends the user
e Users scree
column, enteon your keyp
The Change th
Password fie
an email con
en displays as
er the user’s nad.
his user’s pas
ld’s window, a
ntaining the ne
s shown next
name from the
ssword? dialo
and click Cha
ew password
t.
e USERNAM
og box display
ange.
.
ME column into
ys.
122
o the
Polycom, Inc
P4:
This chapUnified Co
SecuEnabling SorganizatiCloudAXIyour orgait is used firewall. SregistratiogatekeepeCloudAXI
AuthenticaSIP UsernDMA Settweb interfsupportedThese endcredentialrestrictiveServices Pa meetingsubject to
Because tCloudAXIClient andaccess fro
EnablTo enablePolycom p
c.
Provid
pter shows yoommunication
uring SSIP guest accions and indivS web client fnization’s SIPby individuals
Similarly, the Ron and authener when it joinS Experience
ated SIP accename and Patings). In this face will haved endpoints (tdpoints will thls, and can en
e dial plan (sePortal web intg, will not be po the dial rules
the CloudAXIS Solution red Experience om other type
ling Guee guest accespublications.
Note:
It is impapplica
ding S
u how to provns infrastructu
SIP Gucess is the mviduals that afunctions by dP gatekeeper s who belong RealPresencentication capans a conferene Portal.
ess may be essword informcase, membe
e these SIP auhe CloudAXIS
hen attempt tonjoy the benee recommendterface, but aprovided the Ss for unauthen
IS web client quires SIP guPortal. H.323
es of endpoint
est Access via your org
Enabling End
portant to folloble DMA dev
Secure
vide invited guure while prev
est Acost convenienre not federatdefault in a gu(typically a Pto your organ
e® Mobile sofabilities, does nce in respons
enabled for vemation as parers of your orguthentication S web client ao authenticateefits of authendation below)re merely supSIP credentianticated endp
typically funcuest access fo3 guest accests.
ess on Yganization’s e
dpoint Authen
ow the recomvice as describ
e Gue
uests with coventing unwe
ccessnt way to enated with your uest mode; it
Polycom DMAnization and/oftware endpoinot register o
se to the user
erified membet of the Servicganization whcredentials aand Polycom e to the SIP gnticated dialing). Guest userspplied an exte
als and will alwpoints.
ctions in guestor external usss may also b
Your Edgedge proxy de
ntication
mmendation fobed in the foll
est Ac
ntrolled acceslcome intrusio
able video andorganization.neither regist
A device). Thisor connect froint for mobile or authenticatr clicking on t
ers of your orgces Portal DMho have autheutomatically aRealPresenc
gatekeeper (if g, which mays who have nernal e-mail aways dial as a
t mode per thsers wanting te provided at
ge Proxyevice, please
or enabling enlowing guides
ccess
ss to your orgon.
d audio acces. For this reaters nor authes may be trueom within you
devices, white with the tarthe Join Now
ganization byMA settings (senticated to thand securely ce Mobile v3.f challenged) y include acceot authentica
address whenan unauthenti
he above detato join meetint your discreti
y refer to one o
ndpoint authes:
s
ganization’s
ss from ason, the enticates itsee even if and wur organizationch has SIP rget SIP
w button from
y configuring tsee Configurihe Services Pprovided to 1 and above)using the sup
ess to a less ted to the
n attempting toicated SIP ca
ails, the ngs via the Weion to facilitat
of the followin
entication on t
123
lf with when nal
the
the ng
Portal
. pplied
o join aller
eb e
ng
the
Polycom, Inc. 124
See Chapter 2: Deploying the Basic RealPresence Access Director System Solution to Support Remote and Guest Users in the Deploying Polycom® Unified Communications in the RealPresence® Access Director™ System Environments Guide.
See Chapter 2: Deploying the Polycom—Acme Packet Solution to Support Remote and Guest Users in the Deploying Polycom® Unified Communications in an Acme Packet® Environment Guide.
Note that edge proxies, including the RealPresence Access Director, may require that authenticating and non-authenticating callers distinguish themselves by sending SIP requests to a different port or by using a special dialing prefix. To facilitate this, specify the correct Auth Mode when configuring access points in the Services Portal configuration (Configuring the Connection to the DMA System and RPAD Servers). It may be necessary or desirable to specify two different access points corresponding to the same edge device, one for AUTH users and one for NoAUTH users, with each access point entry specifying a different port number and/or dial prefix to use for the corresponding access case.
Additional Recommendations for Greater Security See the following recommendations to secure the privacy of your conferences and prevent misuse of your videoconferencing infrastructure:
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;
Polycom, Inc. 125
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).
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
T5:
This chapfor trouble
This sec
Use
Use
Con
Sup
Use
Use
Use
Obt
User CConfirm th
At l
TheinfoOpe
The
User CWhen entusers are port numbConfigurin
ConfigIf compon
c.
roubl
pter shows yoeshooting mis
ction contai
er Cannot Cre
er Cannot Lau
nfigured Com
per Admins a
er Cannot Se
er Receives “
er Receives “
taining Servic
Cannot he following if
east one DMA
e DMA’s owneormation on herations Guid
e DMA system
Cannot tering a meetiable to creat
bers and DMAng the Conne
gured Cnents are corr
lesho
u how to resoscellaneous is
ns troubles
eate Meetings
unch the Wel
mponents are
nd Admins C
nd Email Not
Unable to Cre
External Serv
ces Portal Log
Create Mf users are un
A system is m
er username ow to create
de on the Poly
m status is up
Launch ing, the welcoe a meeting bA system FQDection to the D
Componerectly configur
ooting
olve issues exssues.
shooting inf
s
come Screen
Not Respond
annot Add an
ifications
eate a Confer
ver Not Set” M
g Files
Meetingnable to creat
made primary
entered in thea username fycom Support
p.
the Weome screen labut are unableDN were enteDMA System a
ents arered but not wo
g the S
xperienced by
formation o
n
ing
n Active Direc
rence with a P
Message
s te a meeting:
y
e Services Pofor the DMA st site.
lcome Saunches with e to launch th
ered when conand RPAD Se
e Not Reorking, try reb
Servic
y end users a
on the follow
ctory User
Personal VMR
ortal also exissystem, see t
Screen video options
he welcome snfiguring the ervers.
espondinbooting the S
ces P
and how to ac
wing:
R” Message
sts in the DMAhe Polycom D
s for entering screen, confirmExperience P
ng ervices Porta
Portal
ccess your log
A system. FoDMA 7000 Sy
the meeting.m that the cor
Portal. See
al server.
126
g files
r ystem
If rrect
Polycom, Inc
SuperUser If Servicesproper LDServer.
Both the Sserver in o
To config
Acc1“cax
Sele2Dat
Syn3Syn
Rep
If the prob
User CIf users arcorrect pocontact yo
User RPersoSee if the Support.
User RIf receivinFQDN is eConfigurin
User RMessaThis errorexceededor to incre
c.
r Admin
s Portal AdmDAP server is
Services Portorder for Clou
gure the sam
cess the CLI (xis” as both y
ect your time te Time in Ap
nc your servernc System da
peat the abov
blem persists,
Cannot re unable to sort numbers liour IT adminis
Receiveonal VMR
virtual meeti
Receiveg the “Externentered in theng Additional
Receiveage r message disd. Contact youease the user
s and A
ins and Supeconfigured w
al and the ExudAXIS Reco
me time zone
see Appendixyour Usernam
zone by usinpendix D for d
r with the NTPte-time with a
ve three steps
, contact your
Send Emsend email nosted in Configstrator to conf
es “UnabR” Messng room exist
es “Exteral Server Not
e MEA ServerServer Settin
es “Video
splays if the liur Polycom recapacity.
Admins C
er Admins are with the correc
xperience Porrding to work
and NTP ser
x D: CloudAXme and Passw
g the CLI comdetails.
P server by ua Specific NTP
s on the other
r IT administra
mail Nototifications, coguring the Cofirm the value
ble to Crsage ts on the conf
rnal Sert Set” messagr textbox locangs.
o Resou
cense trial peepresentative
Cannot A
unable to adct values listed
rtal MUST be properly.
rver:
XIS Restrictedword.
mmand chang
sing the CLI cP server in Ap
r portal.
ator to confirm
tificationonfirm that theonnection to thes are correct
reate a C
figured DMA
rver Not ge after selecated on Servic
urces Ar
eriod has endto purchase a
Add an A
dd an Active Dd in Configuri
configured to
d Shell) on eit
ge_timezone
command ntpppendix D for
m the values
ns e proper SMThe SMTP Sert.
Confere
system. If it e
Set” Mecting Meet Noces Portal’s S
re Not A
ed or when thas license to
Active D
Directory usering the Conne
o the SAME ti
ther of the two
e. See Use C
pdate. See Ur details.
are correct.
TP server is crver. If the pro
nce with
exists, contac
essage ow, confirm thServer Setting
Available
he concurrentactivate your
Directory
r, confirm thatection to the L
ime zone and
o portals usin
ase - Set Sys
Use Case - Qu
configured witoblem persist
h a
ct Polycom
hat the correcgs screen. Se
e”
t license limit r CloudAXIS S
127
y
t the LDAP
d NTP
g
stem
uick
th the ts,
ct e
is Suite
Polycom, Inc. 128
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 Follow the steps provided on the UI and retry loading the logs
Polycom, Inc
G6:
PolyFor more Documen
To find all
For more at Polycom
The The PolycdiscussionCommunipersonnesoftware,
c.
Getting
com ainformation ats and Downl
l Polycom par
information om Strategic G
Polycocom Communn forums to sty, simply crel and participaand partner s
g Hel
nd Parabout installinloads at Polyc
rtner solutions
on solutions wGlobal Partner
om Conity gives you hare ideas an
eate a Polycoate in developsolutions topic
p
rtner Rg, configuringcom Support.
s, see Polyco
with a specificr Solutions.
mmunaccess to the
nd solve probm online accoper and suppocs.
Resourg, and admini.
om Strategic G
Polycom par
nity e latest devellems with youount. When loort forums to
rces stering Polyc
Global Partne
rtner, see the
loper and supur colleaguesogged in, youfind the lates
com products,
er Solutions.
Strategic Pa
pport informats. To register w can access P
st information
, refer to
rtner Solution
tion. Participawith the PolycPolycom suppon hardware
129
ns site
ate in com port ,
Polycom, Inc. 130
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
Polycom, Inc
Configurininstruction
Before yoyour teamsingle perthe comm
In additionbeing use
To create
1 Log
2 Opewith
3 Clic
c.
ng Social Polins.
ou begin, set um. Do not use rson. In case
mon account c
n, always maed.
Note:
A chanthe FQ
Note:
As you
e a Google Ta
g into the shar
en the Googleh menu option
ck the API Pro
icies. To get t
up a neutral ayour personaa person curr
credentials ca
intain one-to-
IP Address C
ge in the servDN points to t
Reference fo
create your G
alk™ app:
red Google ac
e APIs Consons displayed o
oject dropdow
the Client ID a
account with cal account to crently in chargn be passed
-one mapping
Change
ver’s IP doesthe changed
r Creating a G
Google app, y
ccount.
ole page and on the left, sh
wn menu, and
and Client Se
credentials thacreate the apge of the appon to the team
g between the
not require a IP.
Google App
you can use t
select Createhown next.
d select Creat
ecret, see step
at can be shapp. This helpsplication maintm.
e Services Po
new applicat
the Google De
e Project. Th
te as shown n
p 10 of the fo
ared among ds to avoid deptenance leave
ortal server an
tion to be crea
evelopers Pa
e Google AP
next.
ollowing
different persopendencies ones the compa
nd the applica
ated as long
age as a refer
PIs page open
131
ons in n a any,
ation
as
ence.
s
Polycom, Inc
The
4 Entexa
Thenexthe
c.
e Create Proje
er a name in ample shown
e Google APIsxt. If the nameRecent Proje
ect dialog box
the Enter thenext
s page dropde does not auects list.
x displays, sh
e name for yo
own menu natomatically di
own next.
ur project tex
ame should csplay, click th
xt entry box an
hange to the he dropdown
nd click Creat
name of yourbox arrow, an
te Project. A
r project as snd select it fro
132
An
hown om
Polycom, Inc
5 Sele
6 Clic
c.
ect API Acce
ck Create an
ess from the m
OAuth 2.0 C
menu options
lient ID… Th
s, shown next
he Create Clie
.
ent ID screen displays, shoown next.
133
Polycom, Inc. 134
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. 135
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. 136
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. 137
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
Polycom, Inc. 138
Configuring Social Policies.
Polycom, Inc. 139
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
Polycom, Inc
Configurin
Before yoamong difcurrently ithen be pa
Do not usaccount, s
Finally, albeing use
To create
1 Log
2 Opeat th
If yoRegcon
3 Sele
c.
ng Social Poli
ou begin, set ufferent personin charge of tassed on to t
se your personsee the Faceb
ways maintaied.
Note:
A chanthe FQ
Note:
As you
e a Facebook
g into the shar
en the Facebohe top of the
our Facebookgister as a Dntinue.
ect Create Ne
icies. To get t
up a neutral Fns in your teahe applicationhe team.
nal Facebookbook help pag
n one-to-one
IP Address C
ge in the servDN points to t
Reference fo
create your a
k app:
red Facebook
ook Developepage, click A
k account is neveloper. Se
ew App. The
the App ID an
Facebook devam. This helpsn maintenanc
k account to cge.
mapping bet
Change
ver’s IP doesthe changed
r Creating a F
app, you can
k account.
ers page. Thepps (shown n
not already regelect Register
e Create New
nd App Secre
veloper accous to avoid depce leaves the
create the app
tween the Ser
not require a IP.
Facebook Ap
use the Face
e Facebook Dnext).
gistered as a r as a Develo
App screen d
t, see step 4
unt with credependencies ojob, the comm
p. To verify if
rvices Portal
new applicat
p
ebook Develo
Developers sc
developer, yoper, comple
displays:
in the followin
entials that can a single pemon account
your account
server and th
tion to be crea
pers page as
creen displays
you will see ante the registra
ng instruction
an be shared rson. If a perscredentials c
t is a develop
he application
ated as long
s reference.
s. From the m
n option for ation process
140
ns.
son can
er
as
menu
s, and
Polycom, Inc
4 EntrecoSec
5 Sele
The
6 In th
7 Sele
c.
er a suitable ommended) acret as shown
ect Website w
e Site URL te
he Site URL
ect App on F
name in the Aand click Conn next. Make a
with Facebo
ext box appea
text box, ente
Facebook as
App Name texntinue. The Sa note of thes
ok as in the f
ars, shown ne
er https://<
shown next.
xt box (naminample App sc
se for configu
following scre
xt
<ServicesP
ng with the precreen displayring the Serv
een example.
PortalFQDN>
efix “CloudAXys with the Apvices Portal po
>/
XIS_” is pp ID and Appolicy.
141
p
Polycom, Inc
The
8 Ent
○ C
○ S
9 In th
You are no
c.
e Basic Info sc
er the followin
Canvas URL
Secure Canv
he Basic Info
ow ready to con
creen appear
ng:
L Enter htt
vas Width E
options secti
nfigure the Fac
rs:
p://<Servi
Enter https:
on (shown ne
cebook policy o
icesPortal
://<Servic
ext), enter the
on the server. S
FQDN>/
cesPortalFQ
e <ServicsP
See
QDN>/
PortalFQDN>
>
142
Polycom, Inc. 143
Configuring Social Policies.
Polycom, Inc. 144
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. 145
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. 146
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
D: C
IntroThe Polyceither a co
Exe
View
Col
Cha
Cha
Cha
Cha
Reg
Res
View
SCP
UsagSample U
Use CConne
Welcome
Type '?' focaxis@loc
Support
Cat
Find
Gre
c.
Cloud
oductiocom CloudAXonsole or via
ecute a limited
w log files
lect log files a
ange Hostnam
ange passwo
ange the time
ange NTP set
generate cert
start services
w product info
P files (restric
ge Use Cases of r
Case - Loection
AdmLogi
to the Polyco
or help calhost.locald
ed comman
t
d
ep
AXIS
on XIS Restricted
an SSH conn
d set of restric
as a .tar.gz pa
me
rd for the 'cax
e zone of the s
ttings
ificates
ormation (like
cted access) t
restricted
ogin as
min Tip: CLI Lon to the CLI w
om RealPrese
domain: ?
nds in the S
Rest
d Shell providenection and p
cted comman
ackage
xis' user
system
e Version num
to other mach
dshell are d
'caxis' v
ogin with ‘caxis’ as
ence CloudAX
Services Po
tricted
es a means foerform the be
nds
mber)
hines
described belo
via Cons
both your use
XIS Comman
rtal and Exp
d She
or you to log elow operation
ow for referen
sole or v
ername and p
d Line Interfa
perience Po
ell
in to CloudAXns:
nce.
via a SS
assword.
ace (CLI).
ortal:
XIS products
H
147
from
Polycom, Inc. 148
Pwd
Vi
regenerate_certificates (This command is only supported in the Services Portal.)
change_hostname
collect_logs
change_network_settings
change_ntp
show_network_info
change_password
show_product_info
change_timezone
ifconfig
reboot
service
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. 149
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. 150
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. 151
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. 152
[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. 153
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. 154
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. 155
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. 156
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. 157
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. 158
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. 159
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. 160
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. 161
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 a 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. 162
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 - 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
Use Case - Login Timeout:
Timeout. Logging off user.
Polycom, Inc. 163
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. 164
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. 165
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. 166
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. 167
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. 168
"""
====================================================================
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. 169
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. 170
* 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. 171
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. 172
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. 173
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. 174
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. 175
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. 176
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. 177
"""
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. 178
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. 179
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. 180
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. 181
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