Avaya Scopia Streaming and Recording Server Installing Manual

Installing the Avaya Scopia® Streaming and Recording Server
Release 8.3.2
Issue 1
June 2015
2015 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website:
http://support.avaya.com or such successor site as
designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya.
“Hosted Service” means a hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information.
Hosted Service
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE LIMITED BY THE NUMBER AND TYPE OF LICENSES PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY TO USE FLEX LICENSES, WHICH WILL BE INVOICED ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL PARTNER FOR MORE INFORMATION ABOUT THE LICENSES FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND BILLING INFORMATION, AND OTHER IMPORTANT INFORMATION REGARDING THE HOSTED SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE (“AVAYA”).
Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. “Software” means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. “Designated Processor” means a single stand-alone computing device. “Server” means a Designated Processor that hosts a software application to be accessed by multiple users. “Instance” means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine (“VM”) or similar deployment.
License types
Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.
Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface
with the Software. Units may be linked to a specific, identified Server or an Instance of the Software.
Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database.
CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya’s prior consent and payment of an upgrade fee.
Named User License (NU). You may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. “Named User”, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya’s sole discretion, a “Named User” may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software.
Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as “shrinkwrap” or “clickthrough” license accompanying or applicable to the Software (“Shrinkwrap License”).
Copyright
Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Virtualization
Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered.
Third Party Components
“Third Party Components” mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use certain portions of the Software (“Third Party Terms”). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya’s website at:
support.avaya.com/Copyright or such successor site as designated
by Avaya. You agree to the Third Party Terms for any such Third Party Components.
THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
http://
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE
Note to Service Provider
The product or Hosted Service may use Third Party Components subject to Third Party Terms that do not allow hosting and require a Service Provider to be independently licensed for such purpose. It is your responsibility to obtain such licensing.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services.
Avaya Toll Fraud intervention
If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com.
Downloading Documentation
For the most current versions of Documentation, see the Avaya Support website: designated by Avaya.
Contact Avaya Support
See the Avaya Support website: or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website:
http://support.avaya.com (or such successor site as designated by
Avaya), scroll to the bottom of the page, and select Contact Avaya Support.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
HTTP://WWW.MPEGLA.COM.
http://support.avaya.com or such
http://support.avaya.com, or such successor site as
http://support.avaya.com for product
Contents
Chapter 1: Introducing Avaya Scopia® Streaming and Recording...................................... 5
Avaya Scopia® Streaming and Recording server........................................................................ 5
Example of a direct DMZ deployment.................................................................................. 8
Example of a reverse proxy deployment............................................................................ 10
Example of a distributed deployment................................................................................. 11
Example of a cloud deployment........................................................................................ 14
Scalability.......................................................................................................................  15
System requirements....................................................................................................... 16
Chapter 2: Installing the new streaming and recording server.......................................... 18
Installation checklist............................................................................................................... 18
Physically connecting the new server...................................................................................... 19
Starting the new server..........................................................................................................  20
Configuring the new server..................................................................................................... 21
Licensing checklist................................................................................................................  24
Setting the IP address of the recording component (Conference Point)................................ 25
Setting the IP address of the delivery component (Delivery Node).......................................  28
Restarting services.......................................................................................................... 29
Applying the license to the management component..........................................................  29
Applying the license to the recording component (Conference Point)................................... 30
Applying the license to the delivery component (Delivery Node or Virtual Delivery Node)......  31
Configuring external addresses for public interfaces................................................................. 33
Registering each of the components.......................................................................................  34
Unregistering each of the components..............................................................................  36
Chapter 3: Configuring components....................................................................................  37
Configuring delivery nodes..................................................................................................... 37
Configuring conference points................................................................................................  39
Specifying polling intervals and the network address................................................................  41
Adding and Modifying Scopia® Streaming and Recording servers in Scopia® Management........  42
Glossary................................................................................................................................... 44
4 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Chapter 1: Introducing Avaya Scopia
®
Streaming and Recording
Avaya Scopia® Streaming and Recording server
The Avaya Scopia® 8.3.2 solution introduces a new component, Avaya Scopia® Streaming and Recording server (Scopia® SR). Scopia® SR is the Avaya next generation HD streaming and recording platform, bringing significant enhancements to the Avaya Scopia® solution for streaming and recording. The Avaya Scopia® Streaming and Recording server replaces the Avaya Scopia Content Center Recording server (SCC) server.
Before you install Scopia® SR, you must make a number of decisions in order to ensure that the solution exactly matches the requirements of your deployment. For example, you must make a decision about scalability in accordance with the size of your enterprise. For a small enterprise, you can choose a single appliance which houses all of the Scopia® SR components. For a large enterprise, you can choose a distributed solution with multiple media nodes. Scopia® SR is highly flexible and easily adaptable, whatever your requirements. In addition, you must decide if you require a high degree of redundancy and whether you would like to enable external access and storage in the ‘cloud’.
®
If you would like users outside of the enterprise to access recordings, you can deploy Scopia® SR in a Demilitarized Zone (DMZ) or use a reverse proxy server. In this way, the Scopia® SR is similar to the Avaya Scopia® Web Collaboration server (WCS). If you would like users outside of the enterprise to access the videoconference, you must deploy the WCS in a DMZ or use a reverse proxy server. Scopia® SR and WCS also support a Network Address Translation NAT Firewall configuration in a DMZ deployment. NAT Firewall is an additional layer of security. It blocks unrequested inbound traffic.
For more information, see the Avaya Scopia® Solution Solution Guide, which is available on
support.avaya.com/.
https://
Components
The Scopia® SR consists of the following components:
• Scopia® SR Conference Point™ (CP)
• Scopia® SR Delivery Node™ (DN)
• Scopia® SR Virtual Delivery Node™ (VDN)
• Scopia® SR Manager
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 5
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
Scopia® SR Conference Point
You must configure a conference point to capture H.323 video content and deliver live and on demand webcasting. The Scopia® SR conference point includes an embedded transcoder to convert H.323 calls into Windows Media or .MP4 format.
Each conference point must be associated with a delivery node. A delivery node streams and optionally archives the content captured by the conference point and delivers it to client systems.
You can configure a conference point to be in a geographic location. This means that you can assign a location to one or more conference points which coincide with locations set for Scopia
®
MCUs in Scopia® Management. When a program starts, Scopia® Management includes the desired location, and a conference point close to the MCU can be selected. If there are no conference points matching the location passed by Scopia® Management, then any conference points without a location are treated as a single pool of conference points, and one of those is selected. If there are no conference points available, the call fails.
Each conference point has a limit to the number of simultaneous high definition or standard definition calls it can handle.
The CP includes the following features:
• Video conferencing H.323 capture and transcoding
• High definition support
• Scalability for up to 10 high definition (1080p) or 30 standard definition (480p) calls, which include an audio/video and data stream each
• G.711 and AAC-LC audio capture and transcoding
• H.263, H.263+, H.264 capture and transcoding
The media node or all-in-one server can include the CP and transcoder components. The H.323 video and audio and the optional H.239 stream received by the CP are sent to the internal encoder for transcoding into Windows Media™ format or H.264/AAC MP4/MPEGTS/HLS formats.
• Operating Systems: The transcoder runs on the Windows Server 2012 R2 64-bit operating system with Hyper-V (an add-on to Windows Server 2012 that allows a Linux operating system to run on the same server). The CP runs on the CentOS 6.6 64-bit operating system. Using virtualization software, this enables both applications to run two different operating systems on the same server.
• Licensing: The server requires a single media node license for the CP. The license defines the number of simultaneous H.323 connections. An H.323 connection includes audio, video, and an optional H.239 secondary stream.
• Transcoding H.323 audio and Video: The CP connects H.323 calls to the Scopia® MCUs (Multipoint Control Units). When it establishes a video connection, the CP sends the audio and video data from the MCU to the internal transcoder. The transcoder converts the data into a format that is suitable for streaming.
• Transcoding with H.239: H.239 is an ITU recommendation that allows for establishment of multiple channels within a single H.323 session. Existing videoconference equipment can be used to stream audio and video and a secondary channel can stream a slide presentation or another data stream to the viewers of a program. This function is typically used to stream slide presentations synchronized with live audio and video. If a program uses a secondary H.239 channel, the encoder inputs the second stream, decodes, scales and mixes it with the main
6 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
video input for transcoding/streaming. The streams are then sent to the DN for delivery to the distribution network. The dual stream can also be recorded as a single MP4 program.
• High definition support: The CP supports high definition video and higher rate streaming quality and bandwidth. The CP supports the following ITU recommendations:
- H.261 up to CIF Video
- H.262 up to CIF video
- H.263 up to CIF video
- H.264 up to 1080p video
- H.263+ up to 1024 x 768 H.239 data
- H.264 up to 1080p H.239 data
- G.711 audio
- AAC-LC audio
The CP negotiates up to H.264 Level 3.2 video at 1.92 Mbps, and accepts up to 1080p and down to H.261 QCIF along with G.711 or AAC-LC audio. The streaming resolution and bandwidth rate depend on what you select for the bitrate when creating the program and what the Scopia® MCU negotiates.
Scopia® SR Delivery Node
The DN provides on-demand and broadcast video delivery. Used alone or in a hierarchy of devices, the DN supports thousands of concurrent streams. The DN uses intelligent routing, content caching, and inherent redundancy to ensure transparent delivery of high-quality video.
Delivery nodes store all content that is created by the conference point and deliver the content to client systems. You must associate the conference point with the delivery nodes.
The Delivery Node Details dialog displays a list of Source Programs and Distributed Programs. Source programs are programs for which this delivery node is the main source for storage. Distributed programs are programs which other delivery nodes have forwarded to this delivery node.
Scopia® SR Virtual Delivery Node™ (VDN)
A virtual delivery node (VDN) delivers content to a global content delivery network (CDN) provider for cloud-based viewer playback. The appliance and the network of the CDN act as one delivery mechanism. Therefore, the VDN appliance and the CDN together create the Scopia® SR VDN solution.
Upon program creation, the publisher includes the options of distributing the program to delivery nodes and to the Scopia® SR VDN solution. VDN supports publishing recordings as well as live broadcast.
You can view the programs distributed to the VDN appliance and to be delivered to the CDN with the associated status of the program.
Scopia® SR currently only supports the HighWinds™CDN
Scopia® SR Manager
The Scopia® SR Manager provides a web-based interface to configure and manage streaming and recording software, devices, services, and users. The Scopia® SR Manager application resides on a single hardware platform and provides access to all content in the Scopia® SR environment.
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 7
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
There are two Scopia® SR Manager portals:
• Scopia® SR Manager Administrator Portal: Administrators use this portal to perform the following tasks:
- Configure and manage video communications devices
- Manipulate content
- Monitor user roles
- Create and set global policies
- Identify best practices and usage effectiveness through comprehensive reporting
- Allow access to the VDN for CDN deployment or programs
- Manage organizations, in a multi-tenant deployment (including what profiles, categories and CDN settings they can access)
- Create and manage viewer mappings to associate viewers with the appropriate distribution node location
• Scopia® SR Manager Viewer Portal: Viewers select the Recordings and Events tab on the main Avaya Scopia® Desktop page to access the viewer portal. Viewers can perform the following tasks:
- View programs
- Navigate categories
- View live or on-demand programs
Related Links
Example of a direct DMZ deployment on page 8 Example of a reverse proxy deployment on page 10 Example of a distributed deployment on page 11 Example of a cloud deployment on page 14 Scalability on page 15 System requirements on page 16
Example of a direct DMZ deployment
Figure 1: Direct DMZ Deployment on page 9 displays an example of a Scopia® SR deployment
that is situated directly in the demilitarized zone (DMZ). The deployment is a centralized or all-in-one solution, which means that all of the Scopia® SR components reside on a single server. An all-in­one solution is suitable for a small or medium deployment that does not require redundancy.
8 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
Figure 1: Direct DMZ Deployment
In a typical small deployment, all of the Scopia® SR components reside on a single server. The Scopia® SR Manager and the transcoder run directly on the host server. The conference point (CP), delivery node (DN), and, optionally, a virtual delivery node (VDN) run as virtual servers. VDNs enable enterprises to host recordings in the cloud.
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 9
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
Figure 2: Components in an All-In-One Deployment
Related Links
Avaya Scopia Streaming and Recording server on page 5
Example of a reverse proxy deployment
Figure 3: Reverse Proxy Deployment on page 11 displays an example of a Scopia® SR
deployment that includes a reverse proxy server. The deployment is a centralized or all-in-one solution.
10 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
Figure 3: Reverse Proxy Deployment
Related Links
Avaya Scopia Streaming and Recording server on page 5
Example of a distributed deployment
Figure 4: Distributed Deployment on page 12 displays an example of a distributed Scopia® SR
deployment. The deployment also uses a reverse proxy server. In this example, there are several delivery nodes (DNs) and/or conference points (CPs). This configuration enables Scopia® SR to host large numbers of recordings. A configuration with multiple media nodes can also provide redundancy.
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 11
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
Figure 4: Distributed Deployment
In a typical distributed deployment, the Scopia® SR Manager resides on a separate, dedicated server. The various media nodes can operate as CPs, DNs, or virtual delivery nodes (VDNs). VDNs enable enterprises to host recordings in the cloud.
12 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
Figure 5: Components in a Distributed Deployment
Related Links
Avaya Scopia Streaming and Recording server on page 5 Deployment choices for centralized and distributed solutions on page 13
Deployment choices for centralized and distributed solutions
The Scopia® SR server performs three functions:
• Content recording
• Content delivery
• Content management
Content delivery, in this context, refers to streaming.
When you run the configuration utility (or wizard), you choose between three deployment options for the Avaya Scopia® Streaming and Recording server (Scopia® SR). You can choose to house all three functions on a single server. Alternatively, you can choose to house the management function on one server and the recording and delivery functions on another server or servers. This configuration involving multiple servers is called a distributed system.
If you intend to house all three functions on a single server, you must run the configuration utility on that server. On the selection screen, you must choose All-in-One.
If you intend to install a distributed system, you must run the configuration utility on each server in the system. On the selection screen, you must choose whether the server will house the content management or the recording and delivery functions.
Related Links
Example of a distributed deployment on page 11 All-in-one on page 14 Content Management components only on page 14 Media Node only on page 14
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 13
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
All-in-one
If your Scopia® SRdeployment is an all-in-one system, all Scopia® SR components reside on a single server.
Related Links
Deployment choices for centralized and distributed solutions on page 13
Content Management components only
If your Scopia® SR deployment is a distributed system, the Scopia® SR components reside on multiple servers. You must install the content management components on one server and install the recording and delivery components on another server or servers.
For a distributed system, you must run the Scopia® SR Configuration Utility on each of the servers. When you are running the configuration utility on the server which will act as the content management server, you must select Content management components only on the Select Configuration dialog of the configuration wizard.
Related Links
Deployment choices for centralized and distributed solutions on page 13
Media Node only
If your Scopia® SR deployment is a distributed system, the Scopia® SR components reside on multiple servers. You must install the content management components on one server and install the recording and delivery components on another server or servers.
For a distributed system, you must run the Scopia® SR Configuration Utility on each of the servers. You can install the recording component on one server and the delivery component on another server. Alternatively, you can install both aspects on a single server. In this distributed configuration, these servers act as media nodes. When you are running the configuration utility on a server which will act a media node, you must select Media Node only on the Select Configuration dialog of the configuration wizard.
A media node that is used for the recording component is called a Conference Point (CP).
A media node that is used for the delivery component is called a Delivery Node (DN).
Related Links
Deployment choices for centralized and distributed solutions on page 13
Example of a cloud deployment
Figure 6: Cloud Deployment on page 15 displays an example of a Scopia® SR deployment that
hosts recordings in the cloud. The deployment is a centralized or all-in-one solution that uses a reverse proxy server. A cloud deployment uses a virtual delivery node (VDN) to host recordings remotely.
14 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
Figure 6: Cloud Deployment
Related Links
Avaya Scopia Streaming and Recording server on page 5
Scalability
Recording
Scopia® SR supports up to 10 high definition (1080p) or 30 standard definition (480p) recordings with H.239 simultaneously. The system negotiates high definition whenever possible.
The resolution negotiated is based on the configuration of the MCU service as well as the Scopia SR profile. By limiting the profile to 480p or less, you can do 30 simultaneous recordings (trading off higher quality recordings versus the ability to do more recordings).
Scopia® SR supports a mix of resolutions, and can do three standard definition calls for every one high definition call. So, for example, if the system is licensed for 10 concurrent recordings, you can do any of the combinations of calls in
Table 1: Call Combinations on page 16.
®
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 15
Comments on this document? infodev@avaya.com
Introducing Avaya Scopia® Streaming and Recording
Table 1: Call Combinations
High Definition Standard Definition
0 30
1 27
2 24
3 21
4 18
5 15
6 12
7 9
8 6
9 3
10 0
Playback
On a standalone media node configured for DN only, Scopia® SR supports up to 3,500 viewers at 720p / 768K for live broadcast or video on demand playback simultaneously.
On all-in-one servers or media nodes configured with DN and CP, Scopia® SR supports up to 1,500 viewers at 720p / 768K for live broadcast or video on demand playback simultaneously.
Related Links
Avaya Scopia Streaming and Recording server on page 5
System requirements
Before you log on to Scopia® SR Manager administration pages, your client system must meet the system requirements listed in Table 2: Requirements on page 16.
Table 2: Requirements
Component Requirement
Operating system • Mac OS X 10.7 (Lion) or later
• Windows Vista
• Windows 20XX
• Windows 7™ (32 and 64 Bit)
• Windows 8
Web browser • Microsoft Internet Explorer 8.0™ or later
16 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
• Mozilla Firefox 35™ or later (Mac or Windows)
• Chrome 30™ or later (Mac or Windows)
Table continues…
Comments on this document? infodev@avaya.com
Avaya Scopia® Streaming and Recording server
Component Requirement
• Safari 6™ or later (Mac)
JavaScript must be enabled.
Before you log on to Scopia® SR Manager user pages, your client system must meet the system requirements listed in Table 3: Requirements on page 17.
Table 3: Requirements
Component Requirement
Web browser • Microsoft Internet Explorer 8.0™ or later
• Mozilla Firefox 35™ or later (Mac or Windows)
• Chrome 30™ or later (Mac, Windows, or Android)
• Safari 6™ or later (Mac, iOS)
JavaScript must be enabled.
Operating system • Mac OS X 10.7 (Lion) or later
• Windows Vista
• Windows 20XX
• Windows 7™ (32 and 64 Bit)
• Windows 8
• iOS
• Android
Media Player Microsoft Windows Media Player™ Release 9.0, 10.0,
or 11.0 to view programs.
Silverlight Microsoft Silverlight™ player to view programs.
HTMLV5 Browsers A select number of browsers support video playback
directly for MP4 VoD files including:
• Internet Explorer 9, 10, 11
• Safari 6™ or later
• Chrome 30™ or later
IOS Tablet and Phones, Android Tablets and
Playback function for MP4 VoD files
Phones, Windows Phones/Tablets
Note:
To support non-Western language character sets, install the particular language pack on the client system from which you are accessing the Scopia® SR Manager. Refer to the operating system documentation for your system.
Related Links
Avaya Scopia Streaming and Recording server on page 5
June 2015 Installing the Avaya Scopia® Streaming and Recording Server 17
Comments on this document? infodev@avaya.com
Chapter 2: Installing the new streaming and
recording server
Installation checklist
Follow the steps in this checklist to install the Avaya Scopia® Streaming and Recording server (Scopia® SR).
Tip:
It is a good idea to print out this checklist and to mark each task as you complete it.
No. Task Description Notes
1 Learn more about the new
streaming and recording server and figure out your deployment type.
2 Connect the LAN cables,
keyboard, mouse, and monitor.
3 Start up the server. Starting the new server on
4 Configure the server using the
Avaya Scopia® Streaming and Recording server Configuration Wizard.
5 Set the IP addresses and apply
the licenses.
6 Configure the network that each
device will use to communicate with the Scopia® SR Manager.
Avaya Scopia® Streaming and Recording server on page 5
Physically connecting the new server on page 19
page 20
Configuring the new server on
page 21
Licensing the new server on
page 24
Configuring external addresses for public interfaces on page 33
You require the Microsoft Windows product key.
Before registering devices, you may want to set which network each device uses to communicate
Table continues…
18 Installing the Avaya Scopia
®
Streaming and Recording Server June 2015
Comments on this document? infodev@avaya.com
Loading...
+ 41 hidden pages