Polycom RealPresence DMA for Microsoft Azure Cloud Environment
Product Information
Product Name: Polycom RealPresence DMA for Microsoft Azure Cloud Environment
Version: A
Manufacturer: Polycom
Address: 6001 America Center Drive San Jose, CA 95002, USA
Trademark: All other trademarks are property of their respective owners.
End User License Agreement: By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. The EULA for this product is available on the Polycom Support page for the product.
Patent Information: The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.
Disclaimer: While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document.
Customer Feedback: We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to DocumentationFeedback@polycom.com.
Polycom Support: Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.
Product Usage Instructions
Installation Instructions
To install the Polycom RealPresence DMA for Microsoft Azure Cloud Environment, please follow these steps:
- Refer to the Polycom RealPresence DMA Administrator Guide for detailed configuration options and deployment instructions.
- Create an Azure Image for the RealPresence DMA system.
- Deploy and configure the RealPresence DMA system in the Azure cloud environment using the Azure Image.
Azure Image Creation and Use
To create and use an Azure Image for the RealPresence DMA system, please follow these steps:
- Refer to the Polycom RealPresence DMA Administrator Guide for detailed instructions on creating an Azure Image.
- Once the Azure Image is created, deploy and configure the RealPresence DMA system in the Azure cloud environment using the Azure Image.
RealPresence DMA Deployment Wizard using the Ease of Deployment Cloud Service
To deploy the RealPresence DMA system using the Ease of Deployment Cloud Service, please follow these steps:
- Access the RealPresence DMA Deployment Wizard.
- Follow the on-screen instructions to configure and deploy the RealPresence DMA system in the Azure cloud environment.
Polycom RealPresence DMA for Microsoft Azure Cloud Environment Solutions Guide
Copyright© 2019, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc.
6001 America Center Drive San Jose, CA 95002
USA
Trademarks Polycom®, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries.
All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient’s personal use, without the express written permission of Polycom.
End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. The EULA for this product is available on the Polycom Support page for the product. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by email at OpenSourceVideo@polycom.com (for video products) or OpenSourceVoice@polycom.com (for voice products).
Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided “as is” without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages.
Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to DocumentationFeedback@polycom.com.
Polycom Support Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.
Overview
The Polycom RealPresence Distributed Media Application (DMA) system is a reliable and scalable video collaboration infrastructure solution you can deploy on-premises or in a cloud environment in edge, core, or combination configurations. For details on the configuration options and how to deploy and configure RealPresence DMA in the Azure cloud environment, see the Core and Edge Configuration Options section of the Polycom RealPresence DMA Administrator Guide.
Configurations
The following are the released Microsoft Azure configurations.
RealPresence DMA (CFS Licensing) in Azure with On-premises RPCS (optional) using Azure VNet/ExpressRoute Connection
This configuration includes the following:
- DMA edge/core/combo is running in Azure using CFS licensing
- There is an enterprise VNet or ExpressRoute connection to the Azure Cloud
- Endpoints in the enterprise are registered to edge/core/combo DMA in the cloud
- Optional on-premises RPCS for VMR calls
- Supported call scenarios (SIP/H.323):
- Endpoints in the enterprise can dial into a cloud VaaS service like Microsoft Teams using the Polycom RealConnect Teams Gateway service
- Endpoints in the enterprise can connect point-to-point calls between them
- Endpoints in the enterprise can connect with any outbound internet dialing
- Endpoints can connect to VMR calls using on-premise RPCS
RealPresence DMA (Clariti Licensing using On-prem RPRM) in Azure with On-premises RPCS (optional) with Azure VNet/ExpressRoute Connection
This configuration includes the following:
- DMA edge/core/combo is running in Azure using RealPresence Clariti licensing with on-premises RPRM
- There is an enterprise VNet or ExpressRoute connection to the Azure Cloud
- Endpoints in the enterprise are registered to edge/core/combo DMA in the cloud
- On-premise RPRM provides Licensing, Device Management, Site Topology Integration & Scheduling
- Optional on-premise RPCS for VMR calls
- Supported call scenarios (SIP/H.323):
- Endpoints in the enterprise can dial into a cloud VaaS service like Microsoft Teams using the Polycom RealConnect Teams gateway service
- Endpoints in the enterprise can connect point-to-point calls between them
- Endpoints in the enterprise can connect to any outbound internet dialing
- Endpoints can connect a VMR Calls using on-premise RPCS
RealPresence DMA (CFS Licensing) in Azure with Open Firewall Ports
This configuration includes the following:
- DMA edge is running in Azure using CFS licensing
- There is no on-premise firewall traversal device, but instead all the necessary ports are opened on the enterprise firewalls
- Endpoints in the enterprise are registered to DMA edge in the cloud
- Internet endpoints are registered to DMA edge in the cloud
- Supported call scenarios (SIP/H.323):
- Endpoints can dial into a cloud VaaS service like Microsoft Teams using the Polycom RealConnect Teams gateway service
- Endpoints can connect outbound internet dialing
- Endpoints can connect point-to-point calls between them
Installation Instructions
Azure Image Creation and Use
Prerequisites
The following are the prerequisites for the Azure installation:
- We assume that you are very familiar and trained in Microsoft Azure. For any information about Microsoft Azure refer to Microsoft Azure website
- We assume that any Azure-specific configuration like VPC is already available in your environment
General Steps Overview
- Obtain the Azure .vhd image file of DMA.
- Create a storage account in your Azure subscription.
- In your storage account, add a blob storage container that will be used to hold the .vhd image files in Azure (for example, vm-images).
- Get the URL for your blob storage container (e.g. https://mystorage.blob.core.windows.net/vm- images).
- If your image file is compressed (Zip or Gzip) expand to an .vhd file.
- Upload the .vhd file to your Blob container as a fixed sized .vhd image. To do this you will either:
- Need to convert the .vhd to a fixed size .vhd disk file and upload it using Azure CLI, Azure Az, etc. commands (see Hyper-V and/or Azure documentation for details).
- Recommended: Use a command like the Add-AzureRmVhd to upload and convert the dynamic .vhd to your Blob storage in a single step.
- Create an install image from the uploaded .vhd file. Once created, this image will be the base image for all your VM instances once you create them.
- To create the VM instances see Azure documentation for details.
When you create your instances:- a Select the image created in the above steps.
- b Select the correct size of your VM instance based on your DMA capacity needs. See the Virtual
Machine Size section below. - c The VM instance’s security settings must allow the appropriate ports and network-access to your VM from your desired network locations as required by the products and services that are required. DNS and NTP should be properly configured in the Azure environment to ensure proper network communication and discovery of host names. If the RealPresence DMA configuration has a public and private IP assigned by default, go to Network Settings > IPv4 and add the public IP address to the NAT field.
- d When you name your instance use an FQDN (fully qualified domain name) format for your name (for example, myinstance.mydomain) instead of a simple name (for example, myinstance). Some Poly products require a FQDN name to operate properly. This can be the same as or in addition to your optional Azure DNS name (see Azure documentation for details).
- e The above configuration will deploy the DMA in a single NIC configuration using DHCP. You can deploy a four NIC configuration to segregate WAN side and LAN side traffic, then follow the additional steps mentioned below. Note that static IP addresses will need to be reserved in Azure for a multiple Network interface configuration. DMA does not support DHCP When configuring multiple Network interfaces.
- Shut down the DMA instance before attaching additional Network interfaces.
- Click on the DMA instance to bring up the detailed view of that instance.
- Click on the Networking tab.
- Click Attach Network Interface.
- Click Create Network Interface, assign it a static private IP address on the appropriate subnet and give it the appropriate network security group.
- Repeat the above steps for adding additional interfaces.
- Start your DMA instance, and the NICs will show up in the network settings page.
- f Once you create the instances, they are autonomous machine instances that operate per normal Polycom product documentation. You can access the RealPresence DMA GUI using the default login (admin) and password (Polycom12#$). The administrator should change the default password. Refer to the product documentation for guidance on how to configure the product or configure the product using the DMA Deployment Wizard, see RealPresence DMA Deployment Wizard using the Ease of Deployment Cloud Service section below. For additional information see the RealPresence DMA documentation available on the support site.
Important Notes
- For a list of ports you must open on your internal and external firewall, see the Ports Summary section of the RealPresence DMA Security and Privacy Guide.
- While deploying DMA in Azure, a provisioning error message may appear on the console. This message can be ignored, as no functionality is impacted. The system continues in normal state.
- In-place product upgrades are not supported for cloud environments. If you need to upgrade, use your system’s backup and restore mechanism to restore the configuration to a new instance.
- Poly recommends that you use (purchase) a public static IP address if you want to have a public IP address. Otherwise, if your public IP address changes, you must update the NAT address configuration on the DMA local interface, which requires a system reboot. This process is not the preferred solution.
- RealPresence DMA does not support a High Availability (HA) configuration for Azure deployments.
- For connecting to DMA via SSH, there default login is dmaremote and password is
!/useResponsibly/! Poly recommends that you change the default password (SSH login as that user and alter the password) and/or the general SSH access to the instance using Azure security configurations. - RealPresence DMA supports both stand-alone licensing (using a CFS key) and licensing through the Polycom License Center (in configurations where you deploy an on-premises RealPresence Resource3 Manager).
Virtual Machine Size
Small Deployment
Azure Instance Type
| VM
Size |
Offering | Family | VCPUS | RAM (GiB) | Data Disks | Max IOPS | Temporary Storage | Premium Disk Support | Cost/ Month (Est) |
| A8_v2 | Standard | General purpose | 8 | 16 | 16 | 16×500 | 80 | No | $297.60 |
Support DMA Capacities
| Edge DMA | Combo DMA | Core DMA | |
| Concurrent Registrations per cluster | 1600 | 1600 | 1600 |
| HTTPS tunnel calls (RealPresence Web Suite SIP calls) | 200 | 200 | N/A |
| Number of clusters enabled for conference rooms | N/A | N/A | 3 |
| Number of concurrent SIP<->H.323 gateway calls | 200 | 200 | 200 |
| Number of contacts registered to a Skype for Business server per cluster | N/A | 25000 | 25000 |
| Number of MCUs enabled for conference rooms | N/A | 5 | 5 |
| Number of network usage data points retained per cluster | 8,000,000 | 8,000,000 | 8,000,000 |
|
Number of RealPresence DMA clusters in a supercluster |
N/A | N/A |
3 |
| Superclustering not supported | |||
| Number of sites | N/A | 100 | 100 |
| Number of subnets | N/A | 1000 | 1000 |
| Size of Active Directory supported | N/A | 1,000,000 users and 1,000,000 groups (You can import up to 10,000 groups) | |
| Throughput (Mbps) | 700 | 700 | N/A |
|
Total concurrent conference room (VMR) calls for a supercluster |
N/A | N/A |
600 |
| Superclustering not supported | |||
| Total concurrent conference room (VMR) calls per cluster | 200 | 200 | 200 |
|
Total point-to-point concurrent calls for a supercluster |
N/A | N/A |
600 |
| Superclustering not supported | |||
| Total point-to-point concurrent calls for a cluster | 200 | 200 | 200 |
Medium-Large Deployment
Azure Instance Type
| VM
Size |
Offering | Family | VCPUS | RAM (GiB) | Data Disks | Max IOPS | Temporary Storage | Premium Disk Support | Cost/ Month (Est) |
| B16ms | Standard | General purpose | 16 | 64 | 32 | 8640 | 128 | Yes | $495.50 |
Support DMA Capacities
| Edge DMA | Combo DMA | Core DMA | ||
| Concurrent Registrations per cluster | 5000 | 5000 | 1500 | |
| HTTPS tunnel calls (RealPresence Web Suite SIP calls) | 200 | 200 | N/A | |
| Number of clusters enabled for conference rooms | N/A | N/A | 3 | |
| Number of concurrent SIP<->H.323 gateway calls | 500 | 500 | 500 | |
| Number of contacts registered to a Skype for Business server per cluster | N/A | 25000 | 25000 | |
| Number of MCUs enabled for conference rooms | N/A | 64 | 64 | |
| Number of network usage data points retained per cluster | 8,000,000 | 8,000,000 | 8,000,000 | |
|
Number of RealPresence DMA clusters in a supercluster |
N/A | N/A |
10 |
|
| Superclustering not supported | ||||
| Number of sites | N/A | 500 | 500 | |
| Number of subnets | N/A | 5000 | 5000 | |
| Size of Active Directory supported | N/A | 1,000,000 users and 1,000,000 groups (You can import up to 10,000 groups) | ||
| Throughput (Mbps) | 700 | 700 | N/A | |
|
Total concurrent conference room (VMR) calls for a supercluster |
N/A | N/A | 3600 H.323 only
10800 SIP only1 |
|
| Superclustering not supported | ||||
|
Total concurrent conference room (VMR) calls per cluster |
1000 |
1000 |
1200 H.323 only
3600 SIP only |
|
|
Total point-to-point concurrent calls for a supercluster |
N/A | N/A |
50000 |
|
| Superclustering not supported | ||||
| Total point-to-point concurrent calls for a cluster | 1000 | 1000 | 5000 | |
RealPresence DMA Deployment Wizard using the Ease of Deployment Cloud Service
The Ease of Deployment cloud service (https://dma-config.plcm.vc/) provides a DMA Deployment wizard that streamlines configuration of a RealPresence DMA edge (or combination server) configured server
(DMA 10.x). The wizard asks questions about your network and unified communications environment, then produces a backup file you can upload onto the edge DMA server. It also produces a .csv file or HTML page that contains a list of IP addresses and ports that you must open on your firewall. After you install DMA in the Azure cloud, you can use this DMA Deployment Wizard to configure your DMA.
Documents / Resources
 |
Polycom RealPresence DMA for Microsoft Azure Cloud Environment [pdf] User Guide RealPresence DMA for Microsoft Azure Cloud Environment, RealPresence, DMA for Microsoft Azure Cloud Environment, Azure Cloud Environment, Cloud Environment |
