Breaking News RealPresence Resource Manager 8.0

Transcription

1 V1.3 September 2013 Level 2 Breaking News RealPresence Resource Manager 8.0 Software Release Date: August 28, 2013

2 Disclaimer 2013 Polycom, Inc. All rights reserved. Polycom, Inc America Center Dr San Jose, CA USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc., is not responsible for printing or clerical errors. Information in this document is subject to change without notice. Page 2 of 16

3 Contents Module Overview... 4 Polycom RealPresence Resource Manager Version New Menu System... 5 Geo Redundancy... 6 Maximum Endpoints Increased to 50, Rule-based Dynamic Provisioning... 6 Provisioning Profiles... 7 Provisioning Rules... 7 Priority of Provisioning Rules... 8 Medeatalk Video Implementation Diagram... 9 Lab Exercise / Demonstration: Dynamic Provisioning Profiles and Rules Support for SVC Conferences Download and Linking of Direct Conference Templates Page 3 of 16

4 Module Overview This module provides an overview of the Polycom RealPresence Resource Manager 8.0 software release. Intended Audience This module is intended for students that are familiar with existing Polycom solutions and now want to learn about the Resource Manager Version 8.0 release. Prerequisites Students should have attended RealPresence Implementation, Configuration and Troubleshooting (Level 2) RPIIT202 training or have equivalent experience with Polycom video and infrastructure products. Lab Exercise / Demonstration Scenario A lab exercise has been provided with this training. Detailed instructions are provided for students that have access to the necessary Polycom equipment and a recorded demonstration can be viewed as well. Page 4 of 16

5 Polycom RealPresence Resource Manager Version 8.0 RealPresence Resource Manager version 8.0 offers many new features, including: More intuitive menu system Rules-based dynamic provisioning Direct import and synchronization of RMX conference templates Support for SVC conferences New Menu System Menu functions in this release have been re-organized according to function to provide a more intuitive user experience. The figure below illustrates the menu organization by providing the pages available to the pre-defined Administrator role: Page 5 of 16

6 The new RealPresence Resource Manager version 8.0 menu structure for an administrative user, as shown below, includes the addition of one new menu item: Network Topology. The items found under this new heading have simply been moved from the Admin menu option. This modification is more intuitive for the user and more closely follows the layout of the Polycom DMA 7000 system as well. Geo Redundancy The RealPresence Resource Manager system now supports cabled or non-cabled redundancy configurations. This means that it is possible to have the two RealPresence Resource Manager systems in different geographic locations if the following conditions are met: Network latency less than 100 ms Dedicated VLAN for communication between the servers (to emulate the cross-over cable) The network switch must support multicast packets Note: The Virtual IP address used for Resource Manager must be the same for clients in both locations. Maximum Endpoints Increased to 50,000 Polycom has significantly increased the maximum number of concurrent licensed active endpoints. From 10,000 in version 7.1 this is now increased to 50,000. Rule-based Dynamic Provisioning Previous releases of the CMA and Resource Manager systems applied provisioning details to dynamic endpoints through the use of two separate mechanisms: Dynamic Provisioning Profiles profiles were created and applied to different endpoints based on the endpoint s group membership Site Provisioning Profiles each site in the network topology had an associated Site Provisioning Profile which was then applied to all endpoints located in that site The RealPresence Resource Manager 8.0 system employs a completely new rule-based paradigm for the provisioning of dynamically managed endpoints. This change makes provisioning profiles more flexible and allows the administrator more control over when they are applied. Page 6 of 16

7 Dynamic provisioning now consists of the following steps: 1. Create one or more dynamic provisioning profiles 2. Create one or more provisioning rules 3. Associate a provisioning profile with a rule Provisioning Profiles The RealPresence Resource Manager version 8.0 system includes four types of provisioning profiles, as outlined in the table below. Default profiles exist for both the Network Provisioning Profile (formerly the Site Provisioning Profile) and the Admin Config Profile (formerly User Group Provisioning Profile). These default profiles are applied to all endpoints until configured differently. Dynamic Provisioning Profile Network Provisioning Profile Admin Config Provisioning Profile Bundled Provisioning Profile Server Provisioning Profile Provisioning Rules Former Name Site Provisioning Profile User Group Provisioning Profile New (was formerly part of Provisioning Profile) Summary of Provisioned Settings Network settings such as security, quality of service and gatekeeper address Maximum and preferred call speeds, H.323 settings, calendaring settings, etc. Home screen settings, monitor display and camera settings, etc. Provisions a RealPresence Access Director system How Applied: Applied according to provisioning rules Applied according to provisioning rules Applied according to model and software version of the endpoint Used to provision a RPAD system Administrators now have the flexibility of a rule-based system to apply dynamic provisioning profiles. An administrator can create multiple rules and associate a profile with more than one rule at a time. A provisioning rule consists of one or more conditions that must be met before the dynamic provisioning profile can be applied. The version 8.0 Resource Manager does not include any default rules which means the two default provisioning profiles will be applied to all devices. Page 7 of 16

8 Priority of Provisioning Rules There is a numeric priority associated with each provisioning rule. The lower the priority number, the higher the priority of the rule. Each device can only be provisioned with one Network Provisioning Profile and one Admin Config Provisioning Profile. If a device meets the qualifications for more than one rule, it is this priority that will be used to determine which rule will be enforced. For example, a provisioning profile and rule may be created with settings for all Group Series endpoints in the organization. The Executive Staff endpoints, however, may require additional security and higher call speeds settings so a new provisioning profile and rule would be created for the Group Series endpoints that belong to the Executive Staff. It is important to ensure that the Executive Staff Provisioning Rule has a higher priority than the more generic Group Series rule for the corporate room systems. Provisioning Profiles and Rules Example The diagram below shows a RealPresence platform implementation for the fictional organization Medeatalk. This is a global organization using RealPresence Resource Manager to support a video infrastructure that includes a DMA supercluster and dynamically managed room system and personal devices around the world. One DMA cluster is located in the US to support the Western Region, which is comprised of North and South America. The second DMA cluster is located in Europe and supports the Eastern Region which is comprised of Europe and Asia Pacific. Three RealPresence Access Director devices have been geographically dispersed to support secure unified communications for the organization. Page 8 of 16

9 Medeatalk Video Implementation Diagram Resource Manager West DMA East DMA West RPAD East RPAD1 East RPAD2 To simplify this implementation two network provisioning profiles will be created. The West Region Network Provisioning Profile will provide dynamically managed endpoints with the west.dma.medeatalk.com H.323 gatekeeper and SIP server. The East Region Network Provisioning Profile will configure west.dma.medeatalk.com as the H.323 gatekeeper and SIP server. Provisioning rules will be put in place to ensure endpoints receive the proper provisioning profile, based on the device location. In addition, a new Admin Config provisioning profile should be created to support all of the Medeatalk room systems around the world. This profile will enable auto answer, raise the call speeds for received calls to 1920kbps and set the preferred call speed for outgoing calls to 1024kbps. Calendaring enabled will also be enabled. A provisioning rule can be created based on device type (i.e. Group Series or HDX) to apply this new profile. Dynamically managed desktop and mobile devices will be provisioned with the default Admin Config provisioning profile, which disables auto answer and provisions a lower preferred call speed. Page 9 of 16

10 Two server provisioning profiles will be created to support the three RPAD systems shown in the diagram above. A West Region configuration will configure the North American RPAD system with the West DMA as the H.323 gatekeeper and SIP Server. An East Region RPAD server provisioning profile will be configured to provide those two RPADs with the DMA East information. The required provisioning profiles are shown in the table below: Profile Name Provisioning Profile Summary of Settings Type West Region Network Gatekeeper = West DMA Quality of Service Settings Remote Access Password AES Encryption = When Available East Region Network Gatekeeper = East DMA Quality of Service Settings Remote Access Password AES Encryption = When Available Room Systems Admin Config Auto Answer = Yes Mute Auto Answer Max Call Speed = 2048 Preferred Call Speed = 1024 Enable Calendaring West Region RPAD Server Gatekeeper = West DMA East Region RPAD Server Gatekeeper = East DMA Default Admin Config Admin Config Auto Answer = No Max Call Speed = 1024 Preferred Call Speed = 768 Provisioning rules must now be created to correctly apply these provisioning profiles. Rule Name Condition Endpoint Profiles Server Profiles West Region Site = Americas West Region West Region RPAD East Region Room Systems Site = Europe OR Site = Middle East OR Site = Asia Pacific Device Type = Group Series OR Device Type = HDX East Region Room Systems East Region RPAD Page 10 of 16

11 Lab Exercise / Demonstration: Dynamic Provisioning Profiles and Rules View the accompanying video from the course registration page to see a demonstration of the following lab exercise or use your own equipment to complete the lab exercise. When finished with lab exercise / demonstration return to this point in the courseware. Exercise Summary (20 Minutes) Objective During this lab you will use the RealPresence Resource Manager 8.0 to create provisioning profiles and provisioning rules to support the West Region scenario described earlier. The steps will include: Login to RealPresence Resource Manager as an administrative user Create a provisioning profile for the West Region to provision dma.west.medeatalk.com as the H.323 gatekeeper and SIP registrar Create a Room Systems Provisioning Profile with the following settings: o Auto Answer Point-to-Point Calls = yes o Mute Auto-Answer o Maximum Speed for Receiving Calls = 1920 o Preferred Speed for Placing Calls = 1024 o Enable Calendaring Create a West Region RPAD Server Provisioning Profile to provision dma.west.medeatalk.com as the H.323 gatekeeper and SIP registrar Create a West Region Provisioning Rule to apply the West Region provisioning profile and the West RPAD Server Provisioning Profile for endpoints in the North America or South America sites Create a Room Systems Provisioning Rule for endpoints in conference rooms that will apply the appropriate profile for all members of the Conference Rooms user group What You Will Learn After completing the exercises you will be able to: Create Admin Config Provisioning Profiles Create Network Provisioning Profiles Create RPAD Server Provisioning Profiles Create appropriate Provisioning Rules to correctly apply Provisioning Profiles Page 11 of 16

12 Detailed Lab Steps Create Provisioning Profiles 1. Login to a RealPresence Resource Manager system running version 8.0 with an administrative account and navigate to Endpoint > Dynamic Management > Provisioning Profiles 2. Take the action to Add and create a new profile with the following properties: General Info Profile Name: West Region Network Profile Provisioning Profile Type: Network Provisioning Profile H.323 Settings Enable H.323 Gatekeeper Address: dma.west.medeatalk.com SIP Settings Enable SIP Proxy Server: dma.west.medeatalk.com Registrar Server: dma.west.medeatalk.com Security Settings AES Encryption: When Available Click OK to save the new profile 3. Take the action to Add and create a new profile with the following properties: General Info Profile Name: Room Systems Profile Provisioning Profile Type: Admin Config Provisioning Profile System Settings Auto Answer Point-to-Point Calls: Yes Gatekeeper Address: dma.west.medeatalk.com H.323 Settings Maximum Speed for Receiving Calls: 1920 Preferred Speed for Placing Calls: 1024 Calendaring Settings Enable Calendaring Meeting Reminder Time: 10 Click OK to save the new profile 4. Navigate to Endpoint > Dynamic Management > RPAD Server Provisioning Profile Page 12 of 16

13 5. Take the action to Add and create a new profile with the following properties: General Info Profile Name: West Region RPAD Profile Provisioning Profile Type: Server Provisioning Profile RPAD Settings 2 Enable H.323 Gatekeeper Address: dma.west.medeatalk.com Enable SIP Proxy Server: dma.west.medeatalk.com Registrar Server: dma.west.medeatalk.com Click OK to save the new profile Create Provisioning Rules 6. Navigate to Endpoint > Dynamic Management > Provisioning Rules 7. Take the action to Add a new provisioning rule with the following properties: General Info Name: West Region Provisioning Rule Description: Network and RPAD Provisioning for the West Region 8. Click the Add button to create a new condition: Type: Site Attribute: Site Operator: = Value: Americas Click OK to create the second condition 9. Navigate to Endpoint Provisioning Profile and highlight the West Region Network Profile. Click the down arrow icon to move this profile to the Selected Profiles section 10. Navigate to Server Provisioning Profile and highlight the West Region RPAD Profile. Click the down arrow icon to move this profile to Selected Profiles 11. Click OK to create the new Provisioning Rule 12. Navigate to Endpoint > Dynamic Management > Provisioning Rules Page 13 of 16

14 13. Take the action to Add a new provisioning rule with the following properties: General Info Name: Room Systems Provisioning Rule Description: Endpoint Provisioning for Room Systems in Conference Rooms 14. Click the Add button to create a new condition: Type: Device Attribute: Device Type Operator: = Value: Group Series Click OK to create the condition and then highlight this condition to click Add again: Type: Device Attribute: Device Type Operator: = Value: HDX Click OK to create the condition 15. Navigate to Endpoint Provisioning Profile and highlight the Room Systems Profile. Click the down arrow icon to move this profile to Selected Profiles 16. Click OK to create the new Provisioning Rule End of practical exercise Page 14 of 16

15 Support for SVC Conferences This version of the RealPresence Resource Manager system supports scheduling and managing SVC conferences that are supported with the RealPresence Platform products, including the latest generation of Polycom MCUs and RealPresence room, personal desktop and mobile endpoints. Polycom RealPresence Collaboration Server 800s MCUs (v8.0 and higher) and Polycom RMX systems (v8.1 and higher) support mixed-mode (SVC+AVC) conferences. Both SVC and AVC endpoints can join the conference and each gets the appropriate experience: SVC endpoints get SVC mode and get a video stream for each AVC participant; AVC endpoints get a single Continuous Presence (CP) video stream of the participants (both AVC and SVC) supplied by the MCU. Download and Linking of Direct Conference Templates In version 8.0 Direct Conference Templates can be created only by downloading existing conference templates from Polycom MCUs that have been added to the RealPresence Resource Manager. Creating a Direct conference template is now a three step process: 1. Navigate to Conference > Direct Conference Templates and take the action to Add 2. Select an MCU from the presented list of connected MCUs and click the button to View Profile 3. Highlight one of the existing Conference Profiles from the list and take one of the two available actions: a. Download Profile this will download the conference profile to the RPRM system and these conference settings will be sent to the selected MCU when the scheduled conference is initiated using this profile b. Use Routing Name this will download the conference profile and the associated Routing Name to the RPRM system so that this specific conference profile will be used when the scheduled conference is initiated A Direct Conference Template that was created using the Download Profile option can be considered a standalone template. Once created, the Resource Manager Direct Conference Profile is completely separate from the RMX conference profile. The settings contained in this template will be sent from the Resource Manager directly to whichever RMX was specified in the conference reservation. The originally selected RMX conference profile does not need to exist on the RMX being used for the conference. A Direct Conference Template that was created with the Use Routing Name option could be considered a linked template, as the Resource Manager will start the scheduled conference using this specific conference template on the RMX. It is important to note that if a conference profile does not exist on the selected RMX with that exact routing name, the scheduled conference will not launch. Page 15 of 16

16 It should also be noted that once the Direct Conference Template has been created there are a limited number of attributes that can be modified: Name Description Supported MCUs (RMX, MGC, RMX + MGC) Always Use MCU Dial Options (Dial-In+Dial-Out, etc.) Template availability for selected roles Viewing the details of the conference template can be done by highlighting the appropriate template and opening the informational panes on the right side of the interface. Page 16 of 16