ENG MOP - DMA 10.0 Deployment Guide PDF

ENG MOP – DMA v10.
0 Deployment Guide
Polycom DMA v10.0 Deployment Guide

November 2018
PSR Engineering
Confidential: Polycom and Certified Partner use only 1

ENG MOP – DMA v10.0 Deployment Guide
Version History
Version Date Comments Author
1.0 11/01/2018 DMA v10 Method of procedures (MOP) creation Barry Phearson
1.1 11/12/2018 Port Info added to beginning Upgrade Sections Barry Phearson

Contents
1.0 Prerequisites.................................................................................................................................... 4
2.0 Document Purpose, Scope and Process .......................................................................................... 7
3.0 What’s New in DMA 10 ................................................................................................................. 8
4.0 DMA 10.0 Specifications and Capabilities .................................................................................. 10
5.0 New Virtual DMA Deployment ................................................................................................... 12
VMWare - Install OVA File (15 Minutes) ......................................................................................... 12
Hyper-V - Install VHD File (15 Minutes) .......................................................................................... 24
6.0 DMA Network Configuration Utility (30 Minutes) ..................................................................... 38
7.0 DMA Upgrade Process (40 Minutes) ........................................................................................... 47
DMA 10.0 Port Information related to Upgrades: ............................................................................. 47
8.0 RPAD Upgrade Process (30 Minutes) .......................................................................................... 56
DMA 10.0 Port Information related to Upgrades: ............................................................................. 56
9.0 Product Activation Licensing (25 Minutes) ................................................................................. 65
DMA - CFS ........................................................................................................................................ 65
DMA – Flexera (Al-la-cart Licenses) ................................................................................................ 69
DMA – Flexera (Clariti Licenses) ...................................................................................................... 82
RPAD to DMA – CFS........................................................................................................................ 96
RPAD to DMA – Flexera (Al-la-cart Licenses) ............................................................................... 104
RPAD to DMA – Flexera (Clariti Licenses) .................................................................................... 110
10.0 DMA 10.0 Supported Configurations......................................................................................... 113
11.0 DMA 10.0 Feature Support Matrix ............................................................................................ 116
12.0 DMA 10.0 New Features ............................................................................................................ 118
Access Control List .......................................................................................................................... 118
Access Proxy .................................................................................................................................... 126
Clariti License Enhancements .......................................................................................................... 143
ContentConnect HA and Geo-Affinity............................................................................................. 146
DMA Edge Configuration Wizard ................................................................................................... 149
High Availability (Active: Active) ................................................................................................... 155
ITP Layout Option ........................................................................................................................... 158
Registration Policy ........................................................................................................................... 163
Registration Sharing ......................................................................................................................... 170
TIP v8 Support - Conference Template ........................................................................................... 172
TURN ............................................................................................................................................... 175
VPN Tunnel ..................................................................................................................................... 181
13.0 DMA 10.0 Channel - Product Videos......................................................................................... 191

1.0 Prerequisites
This document assumes that the components described in this section are set up for a typical
deployment and configured to work within the environment provided.
Appliance Requirements:
• Polycom Rack Server 630 (R630)
• Required Licenses for activation
VM Requirements:
• VMWare version 5.5 or higher
• Microsoft Hyper-V 2012 or newer
• Valid NTP configuration
Before deploying your Polycom RealPresence Virtual Edition software, review the following
planning guidelines for your deployment. Unless otherwise noted, use these guidelines for all
Polycom Virtual Editions.
Polycom recommends that a virtual environment administrator install the Virtual Edition
software. After the installation of a Virtual Edition, additional configuration should be
completed by someone who understands video conferencing.
Virtual Environment CPU Allocation

▪ Leave 2 cores unallocated, regardless of the number of cores present, how many licenses
are purchased, and what other virtual machines will be present.
▪ For VMware, do not allocate CPU core 0. Host operating system performance may be
affected if this core is assigned to the virtual machine.
▪ When possible, allocate cores on one CPU. This will enhance performance by reducing
CPU-to CPU communication times.
▪ Do not use processor oversubscription; maintain a 2:1 ratio of virtual CPU to physical CPU.
For example, a system with 8 physical cores can support up to 16 virtual processors divided
up into any combination among the virtual machines running on that host.
▪ When you are using Hyper-V, Polycom recommends disabling the Virtual Machine Queue
of the Network Interface Card (NIC). For more information, see
https://support.microsoft.com/en-us/kb/ 2902166

Note: CPU reservations can only be done after shutting down the virtual
machine.
Memory Allocation
In a Microsoft Hyper-V environment, you must not overprovision memory at the hypervisor
layer. Dynamic memory for virtual machines is not supported.
Disk
Hypervisors add overhead to disk operations. For best performance, ensure that the virtual
machine can achieve the recommended IOPS listed in the following table.
Capacity information such as storage space and memory vary according to Virtual Edition.
Please see release notes for your RealPresence Virtual Edition software for the minimum
capacity requirements for your product.
Additional Configuration Requirements:
Active Directory Information:

• Active directory information that is needed;
• Active Directory Server Address: Only FQDN of AD server is allowed
• Active Directory Machine Domain: the name of current Domain
• Active Directory Machine DNS Domain: the full name of Domain
• Active Directory Machine Name: The Machine name which is configured in AD server
• Active Directory Machine Password: the password matched with Machine Name
Server Information:
• IP address for the physical server

• IP Address for the Virtual Machine (VM)
• IP Mask for server and Virtual Machine
• IP Gateway
• DNS Server IP address
• Host Name – the name of the Virtual Machine
• NTP Information – used later in configuration

SIP Connection Information

• SIP server address - the IP address or full name of DMA
• SIP proxy port - port communicated with DMA by SIP (Usually port 5060)
• SIP Registrar port - it should match with DMA (Usually port 5060)
• SIP Domain suffix - the suffix of sip server
• SIP authentication Name and SIP password – name and password configured on DMA
RPAD or DMA Edge Information (FE Toolkit will require RPAD data for Edge Configuration)
• Internal address - Internal IP of access proxy settings in RPAD or DMA Edge.
• External Address: The external signal address of RPAD or DMA Edge.
• SIP proxy port - The SIP external port configured in RPAD or DMA Edge.
• SIP Registrar port - The SIP external port configured in RPAD or DMA Edge.
User name and Passwords:

Login credentials and rights for equipment in the environment:
• DMA administrative login name and password
• RMX administrative login name and password
• RPAD administrative login name and password
• Any other equipment in the environment that interacts with deployment
Field Engineer Equipment and Software:

• Laptop for testing and diagnostics
• Network Cable to connect Laptop to Customers Network
• Environment Software (In case upgrades are required)
o RMX Release 8.8 (requiring MPMRx Cards)
o DMA Release 10.0
o RPAD Release 4.2.5.2
• Polycom DMA Software Release 10.0
• Polycom DMA Release Notes
• Additional references for environment product documentation
• (Install, Quick Start, Admin Guide, Best Practice Deployment, Release Notes)
http://support.polycom.com.

2.0 Document Purpose, Scope and Process

2.1 Purpose
The purpose of this document is to provide the field with a flawless installation and integration
process for DMA release 10.0. This document provides detailed instructions on how to install
DMA product components and how to perform DMA specific product configuration. If a
solution component does not require special configuration to work with DMA, configuration
information for that component is not included.
2.2 Scope
This process guides PGS through the best practices to be followed for installing the DMA
product. This document does not cover installation of VMware/Hyper-V environments nor
other integration with third party software.
2.3 Process
The process outlined herein strives to minimize customer downtime with specific guidelines for
field personnel performing the DMA installation or upgrades.
1. Verify that DMA meets the specified minimum release
2. Verify that RPAD meets the specified minimum release
3. Verify that VMware is at release 5.0 or above/Hyper-V role on Windows Server
2012 R2 (reported supported 2008 and up)
4. Install/Upgrade Polycom DMA Core software
5. Install DMA Edge or upgrade RPAD to DMA Edge
6. Obtain Serial number, License Server IP address, RealPresence license
information
7. Configure Polycom DMA Core
8. Configure Polycom DMA Edge
9. Configure SRV record on DNS
10. Install HA (if required)
This process document does not provide details for the following:
1. Installing and Configuring VMware (See http://www.vmware.com for a 60-day
software trial)
2. Installing SfB server and Client environment (See http://www.microsoft.com for SfB
Installation Guide.)
3. Installing or upgrading RMX software (Go to http://support.polycom.com for the
RMX Administrative Guide)
4. Installing or upgrading RPAD software (Go to http://support.polycom.com for the
RPAD Administrative Guide)

Note: It is the customer’s responsibility to have a fully functional VMware or
Hyper-V environment.
3.0 What’s New in DMA 10
DMA 10.0 Release Highlights
From the TOI covered by Jeff Lutkus we had learned that the following was DMA 10.0 new
features. Further details pertaining to configuration is found in later chapters of this guide.
DMA 10.0 can be setup in two ways now:
a) in an Edge Configuration in the DMZ (like the existing RealPresence Access Director product)
b) in a Core configuration inside the enterprise (like the existing RealPresence DMA product)
Support for upgrading your existing RPAD from RPAD 4.2.x for Edge configuration, as well as a
standard DMA upgrade from DMA 9.x for use as a core configuration
Allows for a single combo box configuration where you can have a single DMA in Edge
configuration in the DMZ that also will host VMR calls. In this configuration there is no need of a
second DMA in the core configuration inside the enterprise
Support VPN tunnel for edge configuration
DMA 10.0 now has the new look and feel HTML5 UI for all configurations and allows you to
configure Horizontal or Vertical Menus
DMA 10.0 in Edge configuration is now also a full-fledged Gatekeeper/Registrar. All external
endpoint registrations terminate at the Edge DMA
DMA 10.0 now provides both active/active and active/passive High Availability in both Edge and
Core configurations
DMA 10.0 has the ACL (Access Lists) feature for both Edge and Core configurations
DMA 10.0 also provides VMR based licensing apart from existing Call Licensing.

DMA 10.0 will support PCC (CSS) Geo-affinity, PCC (CSS) HA Support and DMA HA support for
PCC (CSS)
DMA 10.0 will support TIP v8 with RMX version 8.8
DMA 10.0 will support a new ITP layout
DMA 10.0 will provide new functionality to set conference thresholds per MCU to protect new
users from joining existing conferences on a busy MCU
DMA 10.0 will provide the capability to synchronize pooled conference names between RPRM,
DMA and RPCS.
DMA 10.0 will not count an extra DMA license for PCC (CSS)/Soft Blade call leg.
DMA 10.0 provides Local Burst capability for licensing
DMA 10.0 provides the ability to not count licenses multiple times if a call traverses a
supercluster
DMA 10.0 enforces RPCS Licensing in Clariti mode

4.0 DMA 10.0 Specifications and Capabilities
DMA 10.0 product release notes state the following details to help understand the maximum
values to expect with overall usage. As stated below; Because of the differences in hardware
and VM Environments, the performance information is provided for guidance purposes only
and does not represent a guarantee of any kind by Polycom.


5.0 New Virtual DMA Deployment
The following will demonstrate a deployment of DMA 10.0 in vSphere Web Client version 6.5.0.
The required DMA software OVA will be required prior to completion.
VMWare - Install OVA File (15 Minutes)
From VMs and Templates view, select location to deploy software. Right click and select Deploy
OVF Template. Click the Browse option to select the OVA typically named “plcm-rpp-dma-
10.0.0-xxxx-vmdk.ova” (xxxx reflects build number). Click next.

Provide Name to be displayed within vSphere. If not Modified, the name will be in following like
format (plcm-rpp-dma-10.0.0-6979-vmdk). Click Next.

Select your defined Resource within VM infrastructure. Click Next.
Review details of deployment and click Next.

Accept the EULA to proceed with install and click Next.
Select your storage and virtual disk format. Click Next

Select Network required and then click Next.
Click the finish button to allow the VM to be deployed.

In vSphere 6.5.0, all VM’s will need to be manually started. Version 6.7 will restore
automatically starting of VM’s. You can do this by selecting the VM and clicking a GREEN play
button. The GREY play button reflects a running VM seen here.
Use VM Console to set IP Address (5 Minutes)
Once the VM is started, use the Console pop-out option
From the pop-out window, use polycom as user name and password to login

You will be prompted to change this password. First one must enter existing password then
enter new and confirm new password. Notice no character indication is seen when entering
data.
Once successfully changed, you will see a warning message. Use the tab function to select Yes.

Use option 1 to change the Host Name
Enter new Hostname and select OK
Use option 2 to set the Network Settings

Select eth0 and click OK
Select option 1 to set the Static IP Address

Configure required IP information and select OK
Observe the restarting network service message
Review configured network settings

Use option 3 to set DNS information
Enter required information and click OK
From the main menu select Exit and allow the DMA to reboot.

Once finished, the DMA would be accessible from the defined IP address in the following
format: https://10.223.36.171:8443/dma/login
Default login information would be admin and Polycom12#$ for user name and password.

Hyper-V - Install VHD File (15 Minutes)
Extract the DMA software to a central location specific for this deployment. Hyper-V Manager
has defined default folder location as C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
Within this folder one should have subfolders to extract main files into to prevent problems in
the event of multiple deployments. The following for example:
From Hyper-V Manager select Action>Import Virtual Machine
Click Next to continue

Click Browse to locate folder housing the VHD files. DMA team typically names file “plcm-rpp-
dma-10.0” as seen in folder below. Select Folder
Click Next to proceed


NOTE: VERY IMPORTANT TO SELECT “COPY THE VIRTUAL MACHINE” This is to

allow a Unique ID which is used during license process and should be unique
with every deployment

Recommend the browsing option to use defined subfolders as seen below

Select the Virtual Switch network to be used with the DMA configuration. By Default, the VHD
will have all 4 NIC’s enabled. You can disable or associate different Virtual Switch networks if
defined in Hyper-V. For our documentation we have the one Virtual Switch network.


Once complete, Rename the Server and then select Start from the right-hand menu choices
Use Hyper-V Console to set IP Address (5 Minutes)
Use the Connect option to open console access and login using polycom as user name and
password of
Polycom. The password will not reflect characters indication for security reasons.

Select Yes

Expect to see general errors on the console window
Use Polycom Management Console to set the Host name and Network settings.
Change the host name with option 1 and select OK

Modify the Network Settings with option 2 and select OK
Select eth0 and OK

Observe the DHCP provided address and enter option 1 to set a static address for DMA
management
Provide the static IP Address (preferred) and select OK
DMA will ARP the address, reset network services and then display configuration with OK as
option

Set DNS Configuration using option 3
Provide configuration and select OK
Select option to 7 to reboot server and save all configured settings. Then attempt to access the
web UI via configured IP address. URL Format will be https://IP_Addrfess:8443/dma

If you need to access the console connection again, you will need to use the new password
configured when first connected and acknowledge that this server was already configured.
Otherwise just access the IP address in an internet browser about 4 minutes after the restart.

6.0 DMA Network Configuration Utility (30 Minutes)
During first time Setup of any new DMA you are asked to select either Core or Edge
Configuration. Also located on the first-time setup window, there is a Download Network
Configuration Utility.
Clicking on it downloads a zip file names usbGui_10.0.0.xxxx.zip. When you extract the file
locally, the dma7000-usb-gui.exe is used to configure system parameters. Out of habit, I right
click and open as Administrator.

The Node Selection is displayed to start system configuration. Select Node 1 and use the Edit
button to configure.
Select your initial deployment node type. Engineering has stated that Core must be configured
first.

Provide Host Name and Domain information then Add eth0-eth3 as required.


NOTE: DHCP can only be used once
Clicking Next will allow one to define Service per NIC

Routing will allow to add static routes common with split network configurations
Set the define NTP servers and GMT time specifics and click Done

Use the Upload and Apply Network Config to upload configuration

Browse the extracted folder created at the beginning of this process

The device will reboot

7.0 DMA Upgrade Process (40 Minutes)
DMA 10.0 Port Information related to Upgrades:

No port numbers can overlap in version 10.0 of the RealPresence DMA system. Prior versions of RPAD
and DMA did not check for port overlaps which could theoretically have resulted in dropped calls. After
upgrading, alerts for overlapping ports may display based on the system you upgraded (RealPresence
access Director version 4.2.x or RealPresence DMA version 9.0.x). You can use the formula described
below to adjust the port range settings so that you can clear the appropriate alert. You can shrink the
port range of the respective services depending on the number of call licenses you have. You would
keep the lower min and shrink the upper max of the port range based on the formula below. This way
you may not have to make network or firewall changes.
On a Fresh Install of DMA (in edge configuration), the following are the default ports for the respective
services. See screenshot below:

If you run the edge wizard and specify number of simultaneous calls required as x then the port ranges
will adjust to what is required for x number of simultaneous calls using the formula (mentioned in the
Upgrade section above). See screenshot below which uses 1000 simultaneous calls and has services
bound to eth0 only:

With DMA version 10.0, the Core DMA is required to be upgraded prior to any other Edge
device being deployed OR RPAD being upgraded. The Release note have further details about
supported upgrade paths but the following sums up our required version of 9.0.X prior to 10.0
NOTE: Prior to an upgrade, make as much free space as possible to prevent

AutoRestore function from restoring partial configuration and present one
with OOB features. Any massive amount of logging could create this issue.
Advise full backup (as always) and deletion of Archived Logs prior to upgrade.
Verify Software Versions
Login to DMA and Select Help>About RealPresence DMA to confirm required software version.

DMA Upgrade (35 Minutes)
Log into DMA running 9.X software version
Select Admin>Software Upgrade

Select Upload or Upload and Upgrade, double click on the required upgrade file, Confirm Action
selecting YES.
Monitor File Upload process

To manually load the Progress Page use URL format http://IP Address:8080/rppufstatus.html

Complete status reads 100%
Once completed (35 minutes) the login prompt for DMA will be seen. Login with credentials

Read and Accept the EULA to proceed. Also opt in or out to automatically send usage data to
improve this product. Click the blue question mark for further details on usage data.
Select Help>About RealPresence DMA to verify new software version.


8.0 RPAD Upgrade Process (30 Minutes)
DMA 10.0 Port Information related to Upgrades:

No port numbers can overlap in version 10.0 of the RealPresence DMA system. Prior versions of RPAD
and DMA did not check for port overlaps which could theoretically have resulted in dropped calls. After
upgrading, alerts for overlapping ports may display based on the system you upgraded (RealPresence
access Director version 4.2.x or RealPresence DMA version 9.0.x). You can use the formula described
below to adjust the port range settings so that you can clear the appropriate alert. You can shrink the
port range of the respective services depending on the number of call licenses you have. You would
keep the lower min and shrink the upper max of the port range based on the formula below. This way
you may not have to make network or firewall changes.
On a Fresh Install of DMA (in edge configuration), the following are the default ports for the respective
services. See screenshot below:

If you run the edge wizard and specify number of simultaneous calls required as x then the port ranges
will adjust to what is required for x number of simultaneous calls using the formula (mentioned in the
Upgrade section above). See screenshot below which uses 1000 simultaneous calls and has services
bound to eth0 only:

Verify required version
Login to RPAD and Select Help>About RPAD to confirm required 4.2 software version.
Also note for single or two-box tunnel systems, review the following information:
1. If you have a RPAD Dell Server R620, v2 or v3, you must perform a new installation of
the DMA EDGE on the server. The RPAD R620 servers cannot be upgraded.
2. If you will upgrade a RRPAD HA pair, you must disable HA on both systems before
upgrading.
3. Post upgrade, DMA 10.0 administrator user credentials will need to be added in the
registration sharing settings to complete the upgrade.
4. Port 8443 will be required for registration sharing between DMA EDGE and DMA CORE.
5. No changes to RPAD configured port ranges are required post upgrade however, the
DMA EDGE system will display a port overlap alert for the system ephemeral port range.
After upgrading, you need to change the DMA system’s ephemeral port range to
prevent port conflicts. You do not need to make changes to your firewall.
6. The RPAD SSH passwords for the following user accounts will be migrated to DMA EDGE:
➢ polycom ➢ root ➢ rpad (the rpad user will be converted to the dmaremote user but
the password will remain the same).
RPAD Upgrade Process (25 Minutes)

NOTE: Upgrading a RPAD to DMA EDGE is a major upgrade. Configuration
changes are required after upgrading to ensure that the DMA EDGE functions
like your RPAD.
NOTE: If you have a RealPresence Access Director Polycom Rack Server 620
(R620), v2 or v3 (shipped from January 2013 through June 2014), you must perform
a new installation of the RealPresence DMA system, version 10, on the server. The
RealPresence Access Director R620 servers cannot be upgraded.
Download the required UPG file which may be named like the following “rpad-4-2-x-to-dma-
10.0.0-7267-full”. From RPAD main menu, select Maintenance>Software Upgrade
Select either Upload or Upload and Upgrade option from the left menu. We will select Upload.

Browse for the required file and begin the upload
Notice the details on main page

From the left menu now select Upgrade.
URL changes while upgrading (Captured below). The Status URL is IP_Address:8080/status.html

Although I started upgrade process at 11:09, the Package Installer process started at 11:14 and
ended 11:22 thus total time 14 Minutes with reboot 20 Minutes. Refresh the browser and
observe RPAD is now DMA running in Edge Configuration.

Login with existing user credentials the accept the EULA agreement
Confirm from the Alert window that there was a successful restored backup or database
Recommended practice is to create a Full New Backup from the Admin>Backup and Restore
window

Licenses (if required) will need to be assigned as next step then finalize configuration and run
test calls. From the Alert mentioning port overlap use the following steps to edit the ephemeral
(short-lived) ports.
To edit system ephemeral ports:

1 Go to Admin > Server > Network Settings.
2 Click System Ephemeral Ports.
3 Revise the First port and/or the Last port as needed.
4 Click OK to save the changes.

9.0 Product Activation Licensing (25 Minutes)
Video of licensing process:

https://www.youtube.com/watch?v=lcwQFcx6uGI
http://mymedia.vc.polycom.com/userportal/video?v=U8ef385243f0a45999d0fcbde12f346a9
http://mymedia.vc.polycom.com/userportal/video?v=U9e76967d855e48869cbb25ac59adca7e
DMA - CFS
The Legacy mode of licensing is CFS and used with the physical Dell Server hardware. Use the
http://Support.polycom.com website to Login and Download or activate new licenses.
Select Activation/Upgrade
Select “All other Polycom Products”
If not logged in, you are prompted to do so

Select Activate Now
Enter Product Serial number which is typically the Dell Service Tag and select Next.
Accept the Export Restrictions agreement

Select the Upgrade Tab to locate the version 10.0 activation code.
From DMA Menu Select Admin>Server>Licenses

Enter Activation Primary key code received from the Polycom Support Portal and click Update.
Confirm license activation on main Dashboard or the License page to reflect License Calls.

DMA – Flexera (Al-la-cart Licenses)
Virtual Edition DMA is licensed via Polycom RealPresence Licensing Center or Flexera. Both
Clariti and the Standalone DMA virtual licenses require an onsite License server which is found
in our Polycom Resource Manager.
Customers will need to download and deploy RPRM so there is a system ID to apply all licenses
to. Proceed to log into the licensing center and from Product List, select RealPresence Resource
Manager Virtual Edition.

Next select RealPresence Resource Manager Virtual Edition as Platform Director is EOL and
considered Legacy.
NOTE: Depending on Licenses Sold to customer. Clariti licenses would use

RPRM VE but if customer only ordered DMA licenses, Platform Director is only
option to use to activate DMA. Both would require Virtual Deployments.
Click the 10.4.0 link as latest build at the time of this document.
Use the File Name Link to download all required files. Also download the DMA 10 (which is not
seen at the time of this document) and any other updates required. Have the local VM
Administration deploy the appropriate (VMWare or Hyper-V) file to their server.
NOTE: This was demonstrated here as unaware if documented in any other

guide. Also, I will be using AL-la-Cart style licensing rather than preferred Clariti
as testing a separate test case for RPAD to DMA conversion

Fast forward to Activations –

From the RPRM Server locate the Unique System Identifier found in License>Setup
Log into the Polycom Licensing Center and select Create Server on left menu pain

Enter the System ID for License Server and make sure you change ID Type to
PUBLISHER_DEFINED. The additional Alias and Site Name is helpful for organizational
needs/requirements.

Select Map Add-Ons to activate RPRM which will allow activations of other Polycom products
seen shortly.
Enter the Entitlement ID or Sales Order number for which required licenses are located, then
Search.

Select the quantity to add to the license server for license activation. RPRM would need at least
qty 1 RPRM Enable license to become activated. Typically, all items found on any new order
would be applied to the license server. There are only a few cases where items are used against
different License Server ID’s so confirm what is required for the deployment.
With all items mapped for our deployment, revisit the RPRM License page and select Update
The License Status will reflect that an update is in progress

Provided port 443 is open and not blocked in or out of network, Online activation will work fine
and typically take a few minutes. If for any reason blocked, Offline activation is required and is
not covered within this document. Most customer can do Online activation.
The status will change, and confirmation is seen. Click OK to continue.
As a new deployment, the logged in user (admin in our case) will require Device Administrator
role to continue. Edit the user, add the Device Administrator (or more roles) using the down
Add button illustrated below. Once complete, log off and back in to renew menus.

If the Add button is not seen on the Instance page, repeat previous actions. Click the Add
button

NOTE: Always make sure DMA CORE is added and license allocations is
completed prior to adding DMA EDGE. New deployments of DMA EDGE should
use the EDGE Configuration Wizard as license allocation is not necessary with
proper configuration – See Clariti License Enhancements section
From the Add Instance page, Select DMA Device Type and fields for that device type will be
visible. Fill in the first page, populate anything required on Service Integration or Servers page if
required, then Select the check box to Enable the licensing from this license server.

When added, confirm seen in Network Device>Instances page.

Next move to the License Allocation page
Clicking on the new DMA, the Allocation area opens to allow license to be provided. In this test
case we have 100 PT2PT and 100 VMR calls type licenses which we will provide. Enter the
values and click save and the REST API’s will license and license the DMA.

When all applied licenses are allocated to the DMA, the donut will be blue. 😊
Logging into the DMA, one can confirm license change from the Dashboard seen here

Also confirmed on the Licensing page via Admin>Server>Licenses

Follow the above steps for adding DMA EDGE to RPRM for monitoring. Virtual Edition DMA
EDGE servers will not require license allocation, but the DMA EDGE Wizard should be run to
advance and enable configuration to allow this functionality.
If this was a Migration of hardware RPAD, there will be licenses provided which should be
added to the server. DMA EDGE Wizard is also recommended in these deployments as it helps
set up the proper dial rules. See appropriate sections within this MOP for setup information.
DMA – Flexera (Clariti Licenses)
Virtual Edition DMA is licensed via Polycom RealPresence Licensing Center or Flexera. Both
Clariti and the Standalone DMA virtual licenses require an onsite License server which is found
in our Polycom Resource Manager.
Customers will need to download and deploy RPRM so there is a system ID to apply all licenses
to. Proceed to log into the licensing center and from Product List, select RealPresence Resource
Manager Virtual Edition.

Next select RealPresence Resource Manager Virtual Edition as Platform Director is EOL and
considered Legacy.
NOTE: Depending on Licenses Sold to customer. Clariti licenses would use

RPRM VE but if customer only ordered DMA licenses, Platform Director is only
option to use to activate DMA. Both would require Virtual Deployments.
Click the 10.4.0 link as latest build at the time of this document.

Use the File Name Link to download all required files. Also download the DMA 10 (which is not
seen at the time of this document) and any other updates required. Have the local VM
Administration deploy the appropriate (VMWare or Hyper-V) file to their server.
NOTE: This was demonstrated here as unaware if documented in any other

guide.

Fast forward to Activations –

From the RPRM Server locate the Unique System Identifier found in License>Setup
Log into the Polycom Licensing Center and select Create Server on left menu pain

Enter the System ID for License Server and make sure you change ID Type to
PUBLISHER_DEFINED. The additional Alias and Site Name is helpful for organizational
needs/requirements.

Select Map Add-Ons to activate RPRM which will allow activations of other Polycom products
seen shortly.
Enter the Entitlement ID or Sales Order number for which required licenses are located, then
Search.
Select the quantity to add to the license server for license activation. Typically, all items found
on any new order would be applied to the license server. There are only a few cases where

items are used against different License Server ID’s so confirm what is required for the
deployment.
With all items mapped for our deployment, revisit the RPRM License page and select Update
The License Status will reflect that an update is in progress

Provided port 443 is open and not blocked in or out of network, Online activation will work fine
and typically take a few minutes. If for any reason blocked, Offline activation is required and is
not covered within this document. Most customer can do Online activation.
The status will change, and confirmation is seen. Click OK to continue.
As a new deployment, the logged in user (admin in our case) will require Device Administrator
role to continue. Edit the user, add the Device Administrator (or more roles) using the down
Add button illustrated below. Once complete, log off and back in to renew menus.

If the Add button is not seen on the Instance page, repeat previous actions. Click the Add
button

NOTE: Always make sure DMA CORE is added and license allocations is
completed prior to adding DMA EDGE. New deployments of DMA EDGE should
use the EDGE Configuration Wizard as license allocation is not necessary with
proper configuration – See Clariti License Enhancements section
From the Add Instance page, Select DMA Device Type and fields for that device type will be
visible. Fill in the first page, populate anything required on Service Integration or Servers page if
required, then Select the check box to Enable the licensing from this license server.

When added, confirm seen in Network Device>Instances page.

Next move to the License Allocation page
Clicking on the new DMA, the Allocation area opens to allow license to be provided. In this test
case we have 10 PT2PT, 50 VMR-Hosted Calls and 36 Max number VMR’s based on license type
applied. Enter the values and click save and the REST API’s will license and license the DMA.

When all applied licenses are allocated to the DMA, the donut will be blue. 😊
Logging into the DMA, one can confirm license change from the Dashboard seen here

Also confirmed on the Licensing page via Admin>Server>Licenses

Follow the above steps for adding DMA EDGE to RPRM for monitoring. Virtual Edition DMA
EDGE servers will not require license allocation, but the DMA EDGE Wizard should be run to
advance and enable configuration to allow this functionality.
If this was a Migration of hardware RPAD, there will be licenses provided which should be
added to the server. DMA EDGE Wizard is also recommended in these deployments as it helps
set up the proper dial rules. See appropriate sections within this MOP for setup information.
RPAD to DMA – CFS
The RPAD appliance will require a Migration Order license to convert the existing RPAD into a
DMA on the Support Portal. The CFS License received is activated like all other CFS activations
by applying against the product serial number.

The SKUs for customers to order are:
RPAD Migration – License to migrate R620 server from RPAD to DMA10.

4250-76620-000
Current RPAD maintenance required.
4250-76630-000
4250-76220-000
4250-76230-000
The following will demonstrate process flow from our QA environment meant to emulate the
Production environment which at the time of this document, not available.
NOTE: RPAD should be activated and running version 4.2 prior to license
conversion to DMA. All RPAD licenses will be removed from the support portal
once completed.
Use the http://Support.polycom.com website to Login and Download or activate new licenses.
Select Activation/Upgrade
Select “All other Polycom Products”

If not logged in, you are prompted to do so
Select Activate Now
Enter Product Serial number which is typically the Dell Service Tag and select Next.

Accept the Export Restrictions agreement
Once logged in use the Upgrade Tab and validate 4.2 Upgrade key code was received. If not,
click the Get button and again make sure RPAD is running version 4.2 prior to upgrades.

With RPAD running 4.2 and covered under an Active Service Agreement, we are ready to apply
the migration license. Use the Activation tab and enter migration license number and Activate.
Activated with no errors will reflect “Activation successful, new keycode generated above”
message.

Note: The Displayed keycode on the main page should be version 10.0 DMA
and you can confirm when visiting the Upgrade Tab in the support portal.
For the benefit of this MOP, working with early versions within the QA
system we have version 9.0 which will be corrected by release date.

You can observe the activity that occurred on the Activation History tab.
Once DMA 10.0 keycode is retrieved, you will need to apply it to the new DMA Edge product.
The DMA Web UI is the same for activations at this point. Log into the DMA and from DMA
Menu Select Admin>Server>Licenses

Enter Activation Primary key code received from the Polycom Support Portal and click Update.
Confirm license activation on main Dashboard or the License page to reflect License Calls.

RPAD to DMA – Flexera (Al-la-cart Licenses)
Might be removed as not required thus no change required from Flexera – RPAD Licenses
would just not be required OR they could have the RPAD work with DMA 10.0 CORE directly.
For customers sold individual virtual type licenses (Non Clariti) the following will apply. The
features of DMA will be added to existing RPAD licenses globally. Customers would need to do
some manual work within RPRM for total completion.
For starters we should review the expected 2 changes. DMA Enable Feature is added to the
RPAD Enable license feature set.
DMA Max VMR Calls Feature is also added to the RPAD Enable license feature set.
There is no expected change for any other RPAD License such as RPAD HA as alternate
configurations can be created. E.G. Qty 2 DMA Edge Servers configured with HA (active/active
or active/passive).
Now to review a typical “Al-la-cart” type license server (Non Clariti) for which the customer was
sold RPRM, DMA and RPAD. We can see for the license server that we have all licenses (New
install or existing) applied to our defined license server.

We can see that from our defined License server that the licenses are applied to the required
devices. In our example we have RPAD with 50 calls license, DMA with 200 Calls and matching
RPRM with 200. (original planned install)
Since the RPAD License feature set change mentioned above, we can now see a total of 250 Call
licenses for DMA which adds the additional 50 to cover the DMA Edge server which will replace
the RPAD 50 call license.

Expected process from this point would be to upgrade RPAD to DMA 10.0 using required file
and process defined within this MOP – “RPAD Upgrade Process”.
Once RPAD is upgraded to DMA, it is time to modify instances within RPRM License server.
NOTE: RPAD Instance in RPRM must be deleted and New DMA EDGE Instance
added for allocation. DMA EDGE Does not require any licenses when DMA EDGE
Configuration Wizard is running, and proper dial rules are built to traverse the
EDGE Server
From the Instances page, select the RPAD Instance and use the delete button.

Use the add button to create new DMA Edge Server. Fill out the Device Type, and License
Configuration pages.

Confirm the addition
Move to License>Allocation area to apply the previous qty 50 licenses to the new DMA Edge
server and click save.

Confirm the allocation on the new DMA Edge Server. Seen on the dashboard or the licensing
page, the confirmed 50 will be displayed.

RPAD to DMA – Flexera (Clariti Licenses)
For customers sold Clariti licenses the following will apply. Most important, if a new install
verify that the CORE DMA is installed and licensed first.
There have been no changes made for Clariti licenses. Once RPAD is upgraded to DMA 10.0, the
RPAD instance is required to be deleted and DMA EDGE added to RPRM License Server.
Next, add new DMA EDGE 10.0 Instance by completing the Device Type and License
Configuration pages.

Confirm new entry and status
From the License>Allocation area you will see the new DMA EDGE server and note that there
are no licenses to map.

Next use the DMA EDGE Configuration Wizard and verify the necessary Dial Rules are built to
allow calls to work. See section related to Clariti Licenses under new features.

10.0 DMA 10.0 Supported Configurations
The DMA 10.0 supported configurations are subject to change until DMA 10.0 is released. As
MOP is being created prior to release, the following is targeted as supported. Any specific
configuration can be sent in through Yammer and confirmed as supported or not.



11.0 DMA 10.0 Feature Support Matrix
Since in DMA 10.0 all features are available in either edge or core configuration the
permutations to support in DMA 10.0 are enormous. So, the following table lists the
features/configurations that are going to be supported/tested in DMA 10.0. No code will be put
in to prevent unsupported features/configurations being used at this time. Obviously, no
support will be provided for those unsupported features/configurations. This way in future if
we need to support a combination it will be straight forward.
Important Note: The DMA 10.0 supported features are subject to change until DMA 10.0 goes
GA


12.0 DMA 10.0 New Features
Access Control List

ACL is a list of named Boolean expressions that get evaluated for each piece of signaling traffic
that hits the box (SIP and H323). DMA 10 has ACL Variables, Rules and Settings used to provide
configuration. Basic flow is to Create the Variables (single or regular expression) if needed,
Create the Rule, Create the ACL and then apply the ACL to the SIP and H.323 Settings.
To add a variable:
Go to Service Config > Access Control > ACL Variables.
Click the Add button.
Complete the following fields:
Variable name: Enter a name for the variable.
Description: Enter a brief description of the type of values the variable contains.
Service Type: Select SIP, H.323, or SIP and H.323.
Value: Click the Add button to enter a value to include in this variable, such as a string,
number, or regular expression.
Click OK to add the value to the list of values.
Add more values as needed.
Click OK.

INFO: Additional information on Regular Expressions found here:
https://www.regular-expressions.info/
To add an Access Control List rule:

Go to Service Config > Access Control > ACL Rules.

Rule Name: Enter a descriptive name for the rule.
You are prevented from using blank spaces in the name.
Description: Enter a summary of what the rule does.
Service Type: Select SIP, H.323, or SIP and H.323.
In the Condition field, click the Add button to add a condition for the rule and complete the
fields as described in the following table:
Field Description
Relation You can define multiple conditions for each rule you create.
When you define the first condition, the Relation field is not
active. When you add subsequent conditions, you can select
the relation for each condition.
•and – If a request meets all the conditions in the rule, the
action for the rule is applied to the request.
•or – If a request meets any one of the conditions in the rule,
the action for the rule is applied to the request.

Attribute Attributes depend on the Service Type (SIP, H.323, or SIP and
H.323) and specify the fields in the header of a SIP or H.323
request message.
Operator An operator compares the Attribute and Value fields of the

condition. For any attribute you choose, the operator you
select determines the available values for the condition.
Value The value for a condition is dependent on the attribute and

operator. You can select a predefined variable (a list of values)
or you can also enter a single value in this field.
Click OK to add the condition to the rule.

Select the condition, then click the Add button to add other conditions to the rule if needed.
Click OK to save the new rule and return to the ACL Rules page.
Add an Access Control List:

Go to Service Config > Access Control > ACL Settings.
Under Access Control Lists, click the Add ACL button.

ACL name: Enter a name for the Access Control List.
Description: Enter a brief description of the Access Control List.

Click OK to create the new ACL.
To add an Access Control List rule and action to an ACL:

Go to Service Config > Access Control > ACL Settings.
Under Access Control Lists, select the ACL to which you want to add an ACL rule.
Under Access Control Rules, click the Add Rule button.

Rule Name: Select the rule to add to the ACL.

Action: Select Deny or Allow as the action the RealPresence DMA system will perform on
a signaling message if the rule conditions are met.
Service Type: Automatically populated based on the rule.
Click OK to add the rule to the selected ACL.
Next simply apply ACL to SIP and H.323 Signaling
To assign an ACL to a SIP port:

Go to Service Config > SIP Settings.

Select the port to assign the ACL to and click the Edit button.
In the ACL field, select the ACL to assign to the port.
Click OK.
Click Update to save the settings.

To assign an ACL to an H.323 port:
Go to Service Config > H.323 Settings.
In the ACL field, select the ACL to assign to the port.


Access Proxy
Access Proxy Settings

The following are Edge server configurations and uses for each protocol defined in Access Proxy
Settings located Service Config>Access Proxy Settings
HTTPS Proxy - The access proxy feature enables external users to access different internal
HTTPS servers. The RealPresence DMA system accepts a request from a remote user, then
sends a new request on behalf of the user to the correct application server based on the HTTPS
reverse proxy settings you configure.
When the RealPresence DMA system is integrated with a Polycom RealPresence Resource
Manager system, access proxy enables remote endpoints to be provisioned and managed by
the RealPresence Resource Manager system. When the RealPresence DMA system receives a
login and provisioning request from an external endpoint, it sends the request to the HTTPS
provisioning server configured within the RealPresence Resource Manager system.
When you configure the HTTPS Proxy settings, you can add multiple HTTPS next hops. For each
next hop, you must apply a filter that’s based on the HTTPS request message header received
from the endpoint. The RealPresence DMA system uses the filter and other settings to send a
connection request to the correct internal HTTPS application server. Two filters are available:
Request-URI–The next hop is based on the Request-URI in the message header received
from the endpoint. Use the Request-URI filter only when adding a next hop to a
Polycom RealPresence Resource Manager system or a Polycom ContentConnect system.
Host header–The next hop is based on the host information in the message header received
from the endpoint. Use a host header filter when creating the next hop for various HTTPS

application servers, including both the RealPresence Web Suite Services Portal and
Experience Portal.
To add an HTTPS proxy:

Go to Service Config > Access Proxy Settings.
Click Add HTTPS Proxy.
In the Add HTTPS Proxy Settings window, complete the fields according to the following
table:
Setting Description
Name The unique name of this HTTPS proxy

configuration
Public IP address The public IP address of the RealPresence DMA

system network interface that receives access
proxy traffic (specified when you configure
network settings).
Private IP address The private access proxy IP address of the

RealPresence DMA system (specified when you
configure network settings). The system forwards
HTTPS requests from this IP address to the
requested application server.

Public listening port The public port at which the RealPresence DMA
system listens for HTTPS proxy traffic.
Default port: 443
Port range: 9950–9999
Note: The RealPresence DMA system
automatically redirects inbound access proxy
traffic on ports 443 and 389 to ports from the
configured Access Proxy Dynamic Port Ranges on
the access proxy public interface. The CentOS
operating system does not allow processes
without root ownership to listen on ports <1024.
Redirecting access proxy traffic on ports <1024 to
the dynamic ports enables the access proxy
process to function correctly.
Require client certificate from the When selected, the RealPresence DMA system
remote endpoint requests and verifies the certificate of the remote
endpoint.
Note: Before enabling this setting, an
administrator must install a Server SSL certificate
and trusted CA certificates on the RealPresence
DMA system. Remote clients must also install a
client certificate and trusted CA certificates.
Verify certificate from internal server When selected, the RealPresence DMA system
verifies the certificate from the internal HTTPS
server (the RealPresence Resource Manager
system, the Polycom ContentConnect system, or
RealPresence Web Suite).
DMA system and the RealPresence Resource
Manager system.
Next Hops The RealPresence DMA system sends requests to

the next hops you specify. For each next hop, you
need to apply a filter type that’s based on the
HTTPS request message header received from the
client. The filter types are Request-URI or Host
header. The RealPresence DMA system uses the
filter and other settings to send requests to the
correct internal HTTPS application server.

Add the Next Hops.
Click OK to save the HTTPS proxy.

LDAP Proxy - LDAP proxies can access different LDAP directory servers, such as the
RealPresence Resource Manager LDAP server or an Active Directory server.
If you configure more than one LDAP proxy with the same public IP address, you must assign a
port other than 389 to one of the proxies.
To add an LDAP proxy:

Click Add LDAP Proxy
In the Add LDAP Proxy Settings window, complete the fields according to the following
table:
Setting Description
Name The unique name of this LDAP proxy configuration

system network interface that receives
access proxy traffic (specified when you configure
network settings).

LDAP requests from this IP address to the

Public listening port The public port on which the RealPresence DMA
system listens for LDAP traffic.
Default LDAP port: 389
Next hop address The private IP address of the target LDAP server.
The RealPresence DMA system sends a new
request to the next hop IP address on behalf of
the remote client.
Next hop port The port on which the internal LDAP server listens.
Default LDAP port: 389
endpoint.
verifies the certificate from the internal LDAP
server.
Manager system.

Click OK to save the settings.
XMPP Proxy - XMPP proxies can access different XMPP servers, such as the RealPresence
Resource Manager XMPP server or a different network server that provides message, presence,
or other XMPP services.
To add an XMPP proxy:

Click Add XMPP Proxy.

In the Add XMPP Proxy Settings window, complete the fields according to the following
table:
Setting Description
Name The unique name of this XMPP proxy

configuration

network settings).

XMPP requests from this IP address to the
system listens for XMPP traffic.
Default XMPP port: 5222
Next hop address The private IP address of the target XMPP server.
The RealPresence DMA system sends a new
request to the next hop IP address on behalf of
the remote client.
Next hop port The port on which the internal XMPP application
server listens.
Default XMPP port: 5222

endpoint.
verifies the certificate from the internal XMPP
server.
Manager system.

HTTP Tunnel Proxy - An HTTP tunnel proxy enables SIP guest users to attend web-based video
conferences hosted by the Polycom RealPresence Web Suite. Some restrictive networks block
outgoing UDP-based traffic and can limit outgoing TCP traffic to ports 80 and 443. In these
situations, if a SIP guest client cannot establish a native SIP/RTP connection to a
RealPresence Web Suite video conference, the RealPresence DMA system can act as a web
proxy to tunnel the SIP guest call on port 80, 443, or on a port in the 9950-9999 range. Once the
SIP client is connected to a meeting, the RealPresence DMA system continues to tunnel TCP
traffic, including SIP signaling, media, and Binary Floor Control Protocol (BFCP) content.
The RealPresence Web Suite client uses auto-discovery to ensure that a SIP guest call is routed
through the HTTP tunnel proxy when necessary. When a RealPresence Web Suite SIP guest user
attempts to join a meeting, auto-discovery determines if standard SIP and media ports are
reachable for the call. If not, the call is routed through the HTTP tunnel proxy.

An HTTP tunnel proxy and an HTTPS proxy can both use port 443 on the same external access
proxy IP address. If you configure a port other than 443 as the external listening port for HTTP
tunnel proxy calls, these calls may fail if the SIP guest client’s network blocks outgoing traffic to
other ports.
The following conditions apply to the HTTP tunnel proxy:
Only one HTTP tunnel proxy can be configured.
The HTTP tunnel proxy does not support SVC video conferencing.
Use of an HTTP tunnel proxy is not supported with two RealPresence DMA systems deployed
in a VPN tunnel configuration.
Before you configure an HTTP tunnel proxy, complete the following steps:
Assign public access proxy IP addresses in network settings.
Add an HTTPS proxy and configure the RealPresence Web Suite Experience Portal as a next
hop.
To add an HTTP tunnel proxy:

Click Add HTTP Tunnel Proxy.
In the Add HTTP Tunnel Proxy Settings window, complete the fields according to the
following table:
Setting Description
Name The unique name of this HTTP Tunnel proxy.

network settings).

Public listening port The public port at which the RealPresence DMA
system listens for HTTPS proxy traffic.
Default HTTP port: 443 or 80
Click OK to save the HTTP tunnel proxy.
Passthrough Protocol – A passthrough proxy provides transparent relay of communication

requests through the RealPresence DMA system to internal application servers.

Caution: For security purposes, use of a passthrough proxy is not
recommended. However, if you choose to use this function, follow the
configuration instructions.
To add a Passthrough proxy:

Click Add Passthrough Proxy.
In the Add Passthrough Proxy Settings window, complete the fields according to the
following table:

Setting Description
Name The unique name of this passthrough proxy.

network settings).

configure network settings). The system
forwards passthrough requests from this IP
address to the requested application server.
system listens for passthrough traffic.
Default passthrough ports: 8080, 80, 443
Next hop address The internal IP address of the target application

server. The RealPresence DMA system sends a
new request to the next hop IP address on behalf
of the remote client.
Next hop port The port on which the internal application server
listens. Can be virtually any port that app server is
running on.
Port Range Settings - You can configure the range of dynamic source ports for access proxy
services. Access proxy dynamic ports are not related to the number of calls on a license and the
full range of ports is available by default. You can specify both the first and last port numbers to
limit the range for access proxy, however, changing the first port number in the range is not
recommended.
Dynamic port ranges configured for the RealPresence DMA system must be configured
correspondingly on your firewall.

Caution: The specific ports and port ranges you configure in the RealPresence
DMA system must match the ports configured on your firewall. If you change
any port settings within the system, you must also change them on your
firewall.
The following table summarizes dynamic source port information for the access proxy feature.
Service First Last Interfaces Number of Ports Reserved

Port Port
Access proxy 10000 13000 The network Variable
dynamic source interfaces to which Each dynamic mode client
ports access proxy uses three ports (HTTPS
services are provisioning, LDAP, and
assigned. XMPP presence). Each
RealPresence Web Suite
client and Polycom
ContentConnect client use
one port.
If you change the port range settings, the RealPresence DMA system validates the new settings
to ensure that no overlap occurs among any of the port range settings. Additionally, the system
checks the port ranges to confirm the following:
No first port number is less than 10000.
No last port number is greater than 60000.
To configure the access proxy port range:

Click Port Range Settings.

For Access proxy dynamic ports, enter the Last Port number for the port range.
Click OK.
Click Yes to confirm the settings.

To restore the default access proxy port range:
Click Port Range Settings.
Click Restore Defaults then Click OK.

Clariti License Enhancements
Clariti Local Burst
NOTE: Output values of calls are strictly dependent on hardware being used and
in what configuration. Common Server 220/230 has max of 200 calls in both
Core and Edge configuration. Common Server 620/630 max of 5000 calls in Core
and 1000 calls in Edge configuration.
Clariti Local Burst licenses are Flexera subscription-based licenses (not a CFS License option)
which will allow one to over subscribe resources on DMA. When added to the Clariti model
license server, the DMA license page will reflect value of true and a check mark that it is
enabled. The check mark is an active area to allow one to enable and disable usage. When
enabled, the maximum calls allowed or 5000 on Core and 1000 on Edge servers.
The License page is found Admin>Server>Licenses

With Clariti local burst Enabled (checked) the DMA would allow more than 1500 calls. With it
disabled (unchecked) call number 1501 will be denied on the above example. The Call Event
logs will reflect No License Available as failure reason. Also, if option is enabled and there are
active Local Burst calls and the administrator disables the option, the calls will remain active
until disconnected.
Licensed Concurrent VMR’s
Clariti Meeting (MTG) licenses were originally created to compete with Cisco in APAC. Typically,
a customer would have either Clariti User licenses OR Clariti MTG Licenses and not mix them.
When first introduced, the TOI requested that there should be a minimum quantity of 5 sold
when used. This minimum quantity of 5 concurrent VMR’s will allow 125 (25 per) licensed calls
per the 5 VMR’s. The 6th VMR call will reflect an alert error message of “DMA has reached its
max licensed concurrent VMRs”.
Call Events will also reflect a valid reason as seen below

License Consumption Enhancements
Within the configuration of External SIP Peers and/or External H.323 Gatekeepers, there is the
field “Type” which use to just list “Other” and “Microsoft” as choices. There are now two new
types added; “DMA Licensed” and “DMA Subordinate”. This addition was created to provide a
single call license usage for calls spanning multiple DMA devices in a called path. Typically, the
DMA Core servers would be considered the DMA Licensed boxes and the DMA EDGE servers
would act as the Subordinate.
This would be how DMA EDGE would not require licenses if configured with DMA Subordinate
as type. There will be other factors involved whereas DMA EDGE hardware servers will have
licenses yet not used if configured as mentioned above.

ContentConnect HA and Geo-Affinity
DMA 10.0 has completely rebuilt support for ContentConnect (PCC) and now treats it as any
other device for which DMA would interface with. Although the section looks like the previous
version of DMA 9.0, we can now add, edit, delete, enable and disable ContentConnect servers.
The Disable feature will not drop connection but prevent any further calls from using selected
server.
To access use Integrations>Polycom ContentConnect
To enable the load-balance function, check the check box and click update button on the bottom
left side of the page.
To add a server, use the Add option

Enter Content Server Name and Content server address as both are required. The address can be
IP or FQDN however the IP Address is preferred method of configuration.
From the monitoring page you can see if currently enable, maximum capacity, last heartbeat and
software version of the PCC Servers deployed. Likewise, if Load-balance is enabled or not.
ContentConnect HA with Load Balancing

DMA CORE systems can now provide integrated load balancing for Polycom ContentConnect
systems that are configured for high availability (HA).
When a ContentConnect system that's a member of an HA pair subscribes to the RealPresence

DMA CORE system, the DMA system will automatically add an enabled record to its list of
Available ContentConnect systems. The record identifies the ContentConnect system’s physical
IP address, not the virtual address of the HA cluster. Two records are needed for the HA pair of
ContentConnect systems - each record identifies the physical IP address for one of the systems.
However, the RealPresence DMA system will initially create only the record for the current
master ContentConnect system. When the current master fails over to the current slave, the
RealPresence DMA system will create a record for the new master.
To configure a ContentConnect HA pair for load balancing:

Go to Integrations > Polycom ContentConnect.
Complete one of the following actions:
• Initiate a failover from the current master ContentConnect system to the current slave
system. The RealPresence DMA system adds a record for the new master.
• Manually add the current slave system’s IP address as a ContentConnect system record in
the RealPresence DMA system.
Disable the two ContentConnect HA system records.
Click the Add button to add a third record that points to the virtual IP address of the
ContentConnect HA pair.
Geo-Affinity
The DMA system now provides geo-affinity for ContentConnect systems through MCU pool
configurations.
You can add both MCUs and ContentConnect systems to an MCU pool, then add the pool to a
pool order and assign it to a user conference room (VMR). When a call to the VMR lands on one
of the MCUs in the pool, the RealPresence DMA system will also look for ContentConnect
systems within the pool. If the pool has ContentConnect systems with available capacity, the
RealPresence DMA system will load balance among them by routing calls to the
ContentConnect system with the highest available capacity. If the pool does not contain any
ContentConnect systems, or if none have capacity, the RealPresence DMA system will look
within the pool order for an MCU that the call can land on. If the call successfully lands on an
MCU, the system looks for available ContentConnect systems that are in the same pool as the
MCU. If none are available, the RealPresence DMA system does not reselect an MCU but will
look for any available ContentConnect system, regardless of its geographic location. The MCU
selection is the highest priority.

DMA Edge Configuration Wizard
This is an Edge Configuration tool only. It will create default connections required for
communication with a Core-configured DMA. This includes a SIP Peer, H.323 Neighbor, and
Registration Sharing, in addition to configuring default dial rules and ACL’s to facilitate
communications.
To begin, select Integrations>DMA Edge Wizard
Enter the Management Host Name (FQDN) or IP address of the Core DMA. Use FQDN in event
of using Super Clustering as purpose is to set up Registration Sharing.

The Signaling host name needs to be an IP as we don’t specify use host name in the network
GUI. To enter this IP address, uncheck the “Core DMA uses the same IP address for
management and signaling” box. Click Next to continue.
Next section is to enter all addresses for Core DMA’s in use. HA pairs, this should be the VIP or
virtual IP address used for signaling. For superclusters, one IP should be entered for each
cluster. As stated in the GUI, this will be used to create sites needed for communicating with
the core DMA.

If you needed to add an IP, click the add button otherwise OK.
Enter new IP and click OK

Any additional Core DMA Signaling IP address can be edited or deleted. The main IP at this
stage cannot be edited or deleted.
The final screen provides you the configuration created and tells you to create matching items
manually on the Core DMA.

Click OK.
The manual Core Configuration is best handled within the Site Topology on the Core DMA.
Located within Service Config>Site Topology>Sites. We will use the default site in this example.

Selecting the Default site and clicking the edit button we can continue.
Click on the H.323 Routing and enter Edge IP and H.323 port information under “Allowed via
H.323-aware SBC or ALG area.

Click on the SIP Routing and enter Edge IP and H.323 port information under “Allowed via SIP-
aware SBC or ALG area. Click OK to continue.
This is the same type configuration which RPAD would have used in the past. All calls would
now traverse the DMA Edge Server.
High Availability (Active: Active)

There have been some differences between 9.0 and 10.0 and huge differences between RPAD
and DMA 10.0 specific to Edge and Core HA environment.
To access, select Admin>Server>High Availability Settings

NOTE: High Availability (HA) can be configured only after all network interfaces
have been fully defined. If HA is enabled, you must disable it to change the
network settings.
When you configure High Availability Settings, follow these requirements:
1. Assign static IP addresses to all interfaces that will be used as HA links or

that have services assigned on both nodes in the HA pair. Each node
must use the same interface for the same purpose (e.g., if eth0 has all
services assigned to it on node A, then eth0 on node B should have all
services assigned; if bond0 is an HA link on node A, it must also be an HA
link on node B). Each network interface on node A must be on the same
subnet as the corresponding interface on node B.
2. Assign a virtual hostname and virtual IP address to all interfaces with
assigned services.
3. All virtual hostnames and the system hostnames for both nodes in an
HA pair must be resolvable by DNS.
4. Configure HA on only one server. After the server reboots, click
"Configure Peer" to invite the other server to join the HA configuration.

High Availability (HA) UI has been completely redesigned for better clarity. The big difference is
the selection of Active: Passive vs. Active: Active. DMA 9.0 was Active: Passive only while RPAD
was Active: Active only. Now DMA 10.0 allows you to choose which you prefer.
Active: Passive > Has a Hot Standby sitting Idle, Uses less IP Addresses,
Active: Active > Allows increased throughput for Media, Uses additional IP addresses
The simplest configuration would use a single NIC thus the following screenshots reflect all the
Configured Services capable on both the CORE and EDGE defined DMA servers. Again, HA
settings should only be completed once all network settings have been defined as for example
the H.323 Signaling and SIP signaling might be configured on a separate NIC.

ITP Layout Option

Immersive Telepresence (ITP) layout is new and included in Conference Template (profile) of
both DMA 10.0 and RMX 8.8. We no longer require the need for the MLA Tool used in the past
with our ITP Systems when a RMX Flag is set correctly.
Supported in DMA 10.0 Core and Combination box configurations, the conference template
now has Telepresence Mode and Telepresence Layout mode.

Likewise, the same settings can be found in the RMX Conference Profile as seem here.


If the RMX Collaboration Server is licensed enabled for the Telepresence option, then the follow
would be expected behavior.
Telepresence Mode is available only when CP (Continuous Presence) conferencing mode is
selected.
Supports telepresence conference rooms joining the conference:
• Auto – A conference is automatically put into telepresence mode when a telepresence
endpoint (RPX, TPX, ATX, or OTX) joins. Recommended setting.
• On – Telepresence mode is on, regardless of whether a telepresence endpoint is
present.
Telepresence Layout Mode available only when CP (Continuous Presence) conferencing mode
is selected. Not available if Telepresence Mode is No.
Specifies the layout for telepresence conferences:
• Manual – Layout is controlled manually by a conference operator using the Multipoint
Layout Application (MLA) interface.

• Continuous Presence (MLA) – Tells the MLA to generate a multipoint view (standard
or custom).
• Room Switch – Tells the MLA to use Voice Activated Room Switching (VARS). The
speaker’s site is the only one seen by others.
• Speaker Priority – Ensures that the current speaker is always displayed in the video
layout. The previous speakers are also displayed if there is room in the layout. In this
mode, each endpoint in the conference reserves screens for displaying the active
speaker in the largest video layout cell available.
• Off – Telepresence mode is off, regardless of whether a telepresence endpoint is
present.
The Room Switch Telepresence layouts normally controlled by the MLA can be managed by the
MCU to
speed updating the conference layouts in large conferences with many endpoints.
Whether the MLA or the MCU controls the Room Switch Telepresence layouts is determined by
the
MANAGE_TELEPRESENCE_ROOM_SWITCH_LAYOUTS flag. This flag must be manually added
before
changing its value. No system reset is required.
The values are:
NO (Default) - The MCU does not manage Telepresence Room Switch Layouts and they
continue to be managed by the MLA.
YES - The MCU manages Telepresence Room Switch Layouts.
When the MCU controls the Telepresence, Room Switch layouts

(MANAGE_TELEPRESENCE_ROOM_SWITCH_LAYOUTS = YES) the display is affected according
to
the Telepresence Mode Settings in the Conference Profile as follows:
If the Telepresence Mode = ON
If no ITP endpoints are connected to the conference, the RMX Room Switch layout
applies, in
which case only the speaker is seen.
When a single participant using an ITP endpoint with either single or multiple screens
connects to the conference, the participant will see black screens.
If the Telepresence Mode = AUTO
If no ITP endpoints are connected to the conference, the RMX CP layout applies (unless
the
conference layout is defined).
When a single participant using an ITP endpoint with multiple screens connects to the
conference, the participant will see black screens.
When a single participant using an ITP endpoint with a single screen connects to the
conference,
the MCU will display a self-view of the participant.

When a TIP system with 3 screens joins a conference, the layout is updated on all screen
simultaneously.
When a Polycom ITP system with 2, 3, or 4 screens joins the conference, the layout is updated
on all
screens simultaneously.
Please visit the RMX or Collaboration server guides for more information
Registration Policy
DMA CORE or EDGE systems will allow multiple policies to control registration by endpoints.
DMA v10 comes with two default registration policies. These can be used as-is or you can edit
them. You can also define custom registration policies.
A registration policy must be assigned to all listening SIP and H.323 ports. When you initially
install your system, the default registration policy that’s applied to ports is based on your
system configuration – CORE or EDGE. You can keep your system’s default registration policy,
or you can create custom policies to fit your needs.
Each registration policy contains the following components:

● Compliance policy: Includes an executable script (using the JavaScript language) that
specifies the criteria for determining whether an endpoint is compliant or non-compliant with
the registration policy.
● Admission policy: Specifies the action the system takes when an endpoint is compliant or
non-compliant. You can choose from the following actions:
• Accept registration – The endpoint’s registration request is accepted, and its status
becomes Active.
• Block registration – The endpoint’s registration request is rejected, and its status
becomes Blocked. The system automatically rejects registration attempts (and
reregistration attempts) from blocked endpoints without applying the registration policy.
The status remains unchanged until you manually unblock the endpoints.
• Quarantine registration – The endpoint’s registration request is accepted, but its status
becomes Quarantined. It cannot make or receive calls. The system processes
registration attempts (and reregistration attempts) from quarantined endpoints but does
not apply the registration policy. An endpoint’s status remains either Quarantined if
registered or Quarantined (Inactive) if unregistered until you manually remove it from
quarantine.
• Reject registration – The endpoint’s registration request is rejected, and its status
remains not registered. It doesn’t appear in the Endpoints list. Whether it can make and
receive calls depends on the system’s rogue call policy. If the endpoint sends another
registration request, the system applies the registration policy to that request.

NOTE: Review the DMA Operations guide for additional Policy Scripting or
predefined variables.
Adding a Registration Policy

You can add a custom registration policy to control registration by endpoints. The policy can be
applied to new registrations or to re-registrations from endpoints with changed properties.
Not all registration policies must be assigned to a port. A registration policy with no port
assignment will be saved in your system but will not be used until you apply it to a port.
To add a registration policy:
Go to Service Config > Access Control > Registration Policies.

Complete the fields as described in the following table:


Click Debug this Script to test the script with various dial strings and other variables (optional).
Click Cancel to close the Script Debugging window.
Click OK to close the Add Registration Policy window.
Click Reapply all policies to unblocked/unquarantined endpoints.

The system evaluates all unblocked and unquarantined endpoints and applies the registration
policy that’s associated with the last port through which an endpoint registered.
Next you would need to assign the new registration Policy to a SIP or H.323 port.
NOTE: If you edit the registration policy assigned to a port during active calls, the
calls may be disrupted or terminated.
To assign a registration policy to a SIP port:

Go to Service Config > SIP Settings.

Select the port to assign the registration policy to and click the Edit button.
In the Registration policy field, select the policy to assign to the port.
Click OK.

To assign a registration policy to an H.323 port:

Go to Service Config > H.323 Settings.
In the Registration policy field, select the policy to assign to the port.

Registration Sharing
DMA v10 system supports sharing of endpoint registrations from an EDGE system to another
EDGE system (VPN tunnel) or to a CORE system.
DMA EDGE functions as a gatekeeper and all public endpoints will register via SIP or H.323
with the EDGE system. To enable calls from an EDGE to EDGE system or CORE system, and
vice-versa, you must configure registration sharing on the EDGE system(s). When you do so,
registrations received by the EDGE system are shared with the CORE system via the CORE
system’s REST API.
NOTE: You must also configure external H.323 neighbored gatekeepers and
external SIP peers to enable calls from the EDGE system to the CORE system.
With registration sharing enabled, an EDGE system will share the following information with
another EDGE system or a CORE system:
● New and refreshed registrations
● Terminated registrations
● Blocked registrations
● Deleted registrations
● Quarantined registrations
After registration sharing occurs, the Endpoints page on the DMA CORE system displays the
IP address of the EDGE system for shared endpoint registrations instead of the IP address of
the individual endpoints which is just like endpoints connected from behind RPAD.
NOTE: Shared registration information is available across a supercluster.

Registration sharing from DMA CORE system to an EDGE system is not
supported.
Configure registration sharing:

On DMA EDGE system, go to Service Config > Call Server Settings.

In Registration Sharing Settings (at the bottom of the page), select Share registrations with
another DMA.

TIP v8 Support - Conference Template
DMA 10.0 and RMX 8.8 now offers Cisco’s TIP (Telepresence Interoperability Protocol) version 8
support, which allows TIP endpoints to receive content at higher resolutions using the Binary
Floor Control Protocol (BFCP). Designed for use in low-bandwidth environments, BFCP enables
endpoints to provide users better coordinated access to conferencing resources. Also support
for transcoding (sending) content in a TIP virtual meeting room (VMR), so that all TIP endpoints
reserve the bandwidth required for the selected resolution and rate.
The TIP encoder endpoints in VMR conference support content transcoding. TIP encoder
supports
the following resolutions:
XGA 5fps @512K – (TIP Version 7 setting)
720p5 @768K
1080p5 @1Mbps
720p30 @2.25Mbps
1080P30@4Mbps
The TIP encoder works at one of the above resolutions only. Any TIP endpoint not supporting
the
selected rate and resolution are unable to receive the content.
TIP endpoints marked as legacy receive content when the Send Content to Legacy Endpoints

check box is selected but the endpoints don’t have the required capabilities to meet content
threshold
in a TIP VMR conference.
All TIP required conferences should use Continuous Presence and TIP compatibility set to Prefer
TIP(v8.1) in DMA Conference template. The setting is built into the conference template under
TIP compatibility section which is in Polycom MCU General Settings.
NOTE: If requiring support for TIP in conferences use only Prefer TIP option as
Video Only and Video and Content were legacy settings.
NOTE: The (v8.1) value in the description was an RMX version and not
specifically version 8 of TIP.

If Prefer TIP is selected, TIP content is used for endpoints that support TIP and non-TIP content
is used with non-TIP endpoints. This requires minimum line rate of 1024 kbps and HD resolution
(720 or better) in a CP (Continuous Presence) conference.
Likewise, a conference profile could be used in RMX. Selecting Prefer TIP on the Advanced tab
of the Conference Profile.

TURN
TURN Service was a feature from RPAD and now found in DMA EDGE configurations. It is
advised to use a separate network interface for TURN services. When DMA EDGE or
combination-configured system is deployed behind a NAT, the relayed transport address sent in
the allocation response to external endpoints and MCUs should always be the public IP address
mapped on your firewall that corresponds to the public IP address of the network interface you
assigned to TURN services. Internal endpoints and MCUs should point to the internal IP address
of the network interface.
When you enable the TURN server for the first time, you must add at least one TURN user
So that the TURN server will allow requests. If you disable the TURN server, all TURN users are
saved and will be available if you later re-enable the TURN server.
Configure TURN settings:

If you haven’t already done so, go to Admin > Server > Network Settings > Services and
assign a Private (LAN) and Public (WAN) interface to TURN Services.
It’s recommended that you assign TURN services to only a single NIC thus you may need to
select a separate interface from the bottom of the Network Settings page. Select it and use the
edit button to enable.

Validate all IPv4 and or IPv6 settings, then click OK. System will restart.
Once restarted, go to Service Config > TURN Settings. Note that if you do not see TURN
Settings, you may be on a CORE configured server and not a DMA EDGE

Select Enable TURN server.
Complete the fields as described in the following table. Note that not all fields are editable from
the TURN Settings page. You can use the Port Range Settings to make changes as needed.
Add a TURN User

The TURN server requires authentication of all relay allocation requests. When the TURN server
receives an unauthorized initial allocation request from a WebRTC or MCU client, the TURN
server responds with its realm and the TURN user credentials a WebRTC client or MCU (TURN
user) must use to authenticate further requests with the TURN server. The credentials include
the username and password to be used with the realm of the TURN server.
You need to configure one TURN user to enable WebRTC clients to request TURN services for
RealPresence Web Suite mesh or bridge conferences. Once you configure the TURN user, you
must share the credentials with the system administrator for the RealPresence Web Suite
system, who will complete further configurations for that product.
To add a TURN user:

Go to Service Config > TURN Settings.
Under TURN Users, click the Add button.
Complete the following required fields:

Username: the username that a WebRTC client uses to authenticate requests to the TURN
server. Maximum of 20 characters.
Realm: the domain name of the DMA EDGE TURN server. When you configure one user
for the RealPresence Web Suite WebRTC clients and MCUs, the Realm should be the same as
the Default Authentication Realm you configured in TURN Settings. Maximum of 20 characters.
Password: the password that a WebRTC client uses in combination with the username to
authenticate its TURN requests. Maximum of 20 characters.
Confirm Password: Re-enter the password to confirm.

Click OK to add the TURN user.

Click Update to save the TURN Users settings. Confirmation seen on the top of page.
The TURN service relay dynamic source ports start at 60002 and end 65535 yet are configurable
via the Port Range Settings. It is recommended to keep the same range, but you can change port
numbers. The number of ports required to support WebRTC calls can vary so allowing the range
will not hinder supported calls. Not first port number can be less than 1024 or greater than
65535.


VPN Tunnel
DMA EDGE systems supports VPN tunneling to other DMA EDGE systems using OpenVPN.
Once you configure a VPN tunnel, all communication goes through the tunnel. If the tunnel
goes down, no communication can occur until you disable, delete or rebuild the VPN tunnel on
both DMA EDGE systems.
Use of a VPN tunnel will decrease overall call capacity from approximately 1000 concurrent
calls to approximately 500 concurrent calls, depending on call settings and use.
NOTE: If you have more than one network interface (for example, signaling and
media), you need to set up multiple VPN tunnels, with one tunnel for each
service on each different network interface between the two edge systems. The
private IP address on the outside edge system must point to the public IP address
on the inside edge system. Configure like-to-like network interfaces, that is,
signaling to signaling, media to media.
Add a VPN tunnel:
Go to Integrations > VPN Tunnel Settings.


Click OK to save the tunnel settings.

Click Configure Remote DMA and enter the following information:
Remote management IP address – the IP address of the management interface on the remote
RealPresence DMA edge-configured system.
Admin username – The administrator username used to log into the management interface of
the remote edge-configured system.
Admin password – The administrator password used to log into the management interface of
the remote edge-configured system.

Click OK to automatically configure the VPN tunnel settings on the remote system.
The VPN Status column on the VPN Tunnel Settings page of both edge systems should display
Connected, which means that the tunnel is not only established but that automated test
network traffic is being successfully sent over the tunnel and back.
NOTE: If local firewall does not allow traversal of REST API traffic, you will need
to manually configure the VPN tunnel. Recommended to add VPN Tunnel on
local EDGE server then manually configure VPN tunnel on remote. This process
will involve copying VPN Tunnel Key from local and adding to remote. DMA
Operations guide has further details.

NOTE: When you create a VPN tunnel between your RealPresence DMA edge
systems, you need to set up access proxy settings that enable the VPN tunnel to
support provisioning.
To enable endpoint provisioning through a VPN tunnel:
When you configure a VPN tunnel between your RealPresence DMA EDGE systems, you need
to set up access proxy settings that enable the VPN tunnel to support provisioning.
On the outside DMA EDGE system, go to Service Config > Access Proxy Settings.
Add an HTTPS proxy and specify 443 as the Public listening port.

Configure a next hop with the following settings:

Type – Request URI
System – Polycom Management System
IP address – IP address of the inside edge system
Port – 9950 or an available port that access proxy on the inside edge system can listen on. Do
not use port 443.
Add an LDAP proxy with the following settings:

Public listening port – 389

Next hop address – IP address of the inside edge-configured system
Next hop port – 9951 or an available port that access proxy on the inside edge system can listen
on. Do not use port 389.
Add an XMPP proxy with the following settings:


Next hop address – IP address of the inside edge-configured system
Next hop port – 9952 or an available port that access proxy on the inside edge system can listen
on. Do not use port 5222.
On the inside DMA EDGE system, go to Service Config > Access Proxy Settings.

Add an HTTPS proxy and specify 9950 as the Public listening port.

Configure a next hop with the following settings:

Type – Request URI
System – Polycom Management System
IP address – IP address of the Polycom RealPresence Resource Manager system
Port – 443
Add an LDAP proxy with the following settings:

Next hop address – IP address of the RealPresence Resource Manager system
Next hop port – 389
Add an XMPP proxy with the following settings:

Next hop address – IP address of the RealPresence Resource Manager system
Next hop port – 5222
Thus, both sides of the tunnel will have ports mapped to each other:
443 9950
386 9951
5222 9952
13.0 DMA 10.0 Channel - Product Videos
There has been a DMA 10 Channel built within the corporate Media Server and All DMA 10
videos have been posted there. They should all be downloadable and if there are any issues
with the channel, please let me know.

DMA 10.0 Channel is at the following URL:
http://mymedia.vc.polycom.com/userportal/channel?v=5ac66578e4b088e958f0a896

PSR Polycom is now on YouTube at the following channel:

https://www.youtube.com/channel/UCR4E6hBJwzhZzUcYJ2iPXgQ/videos
Don’t forget to Subscribe!

NOTE:
NOTE:

ENG MOP - DMA 10.0 Deployment Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ENG MOP - DMA 10.0 Deployment Guide PDF

Uploaded by

Copyright:

Available Formats

ENG MOP – DMA v10.

Polycom DMA v10.0 Deployment Guide

Confidential: Polycom and Certified Partner use only 1

Confidential: Polycom and Certified Partner use only 2

Confidential: Polycom and Certified Partner use only 3

Virtual Environment CPU Allocation

Confidential: Polycom and Certified Partner use only 4

Additional Configuration Requirements:

Active Directory Information:

• IP address for the physical server

Confidential: Polycom and Certified Partner use only 5

SIP Connection Information

User name and Passwords:

Field Engineer Equipment and Software:

Confidential: Polycom and Certified Partner use only 6

2.0 Document Purpose, Scope and Process

Confidential: Polycom and Certified Partner use only 7

3.0 What’s New in DMA 10

DMA 10.0 Release Highlights

Support VPN tunnel for edge configuration

Confidential: Polycom and Certified Partner use only 8

DMA 10.0 will support TIP v8 with RMX version 8.8

DMA 10.0 will support a new ITP layout

DMA 10.0 provides Local Burst capability for licensing

DMA 10.0 enforces RPCS Licensing in Clariti mode

Confidential: Polycom and Certified Partner use only 9

4.0 DMA 10.0 Specifications and Capabilities

Confidential: Polycom and Certified Partner use only 10

Confidential: Polycom and Certified Partner use only 11

5.0 New Virtual DMA Deployment

Confidential: Polycom and Certified Partner use only 12

Confidential: Polycom and Certified Partner use only 13

Review details of deployment and click Next.

Confidential: Polycom and Certified Partner use only 14

Select your storage and virtual disk format. Click Next

Confidential: Polycom and Certified Partner use only 15

Select Network required and then click Next.

Click the finish button to allow the VM to be deployed.

Confidential: Polycom and Certified Partner use only 16

Use VM Console to set IP Address (5 Minutes)

Once the VM is started, use the Console pop-out option

Confidential: Polycom and Certified Partner use only 17

Confidential: Polycom and Certified Partner use only 18

Enter new Hostname and select OK

Use option 2 to set the Network Settings

Confidential: Polycom and Certified Partner use only 19

Select eth0 and click OK

Select option 1 to set the Static IP Address

Confidential: Polycom and Certified Partner use only 20

Observe the restarting network service message

Review configured network settings

Confidential: Polycom and Certified Partner use only 21

Enter required information and click OK

Confidential: Polycom and Certified Partner use only 22

Confidential: Polycom and Certified Partner use only 23

From Hyper-V Manager select Action>Import Virtual Machine

Click Next to continue

Confidential: Polycom and Certified Partner use only 24

Click Next to proceed

Confidential: Polycom and Certified Partner use only 25

Confidential: Polycom and Certified Partner use only 26

NOTE: VERY IMPORTANT TO SELECT “COPY THE VIRTUAL MACHINE” This is to

Confidential: Polycom and Certified Partner use only 27