I created a Powershell script that automates the configuration of Lync for integrating Polycom DMA/RMX. First, a couple disclaimers:
Use this tool at your own risk. While I’ve tested it to the best of my ability I do not take responsibility for any issues that may arise from its use.
This tool was not developed by Polycom and is not supported, sanctioned, or otherwise approved by Polycom.
A screenshot of the tool is below. The process that it’s using is largely documented in my previous post on creating static routes in Lync Server 2010, but I’ll give a brief description of each field here as well.
SIP Domain: This is the domain you would like to use for routing video calls. Polycom’s current documentation recommends using your Primary SIP domain, primary for ease of use and Edge server integration. However, you can use whatever you wish.
DMA/RMX FQDN: This is the FQDN you created for your DMA or RMX. It should match the A record you created for the signaling interface and the subject of the certificate you loaded on DMA/RMX.
Routing Container: You can create routes at the global level or the registrar level. Select the one you wish to use. Known limitation: By default only the Global routing container exists. If you want to associate a route with the registrar make sure you run new-csstaticroutingconfiguration –identity service:registrar:<registrarfqdn> before using this tool.
Application Pool FQDN: Lync needs an Application Pool for any static routes. You can enter any FQDN you wish – it does not need to match anything in DNS but it must be unique to the Lync Server topology.
Associated Registrar: All application pools must be associated with a registrar. Select any registrar you wish.
Site: All application pools must also be associated with a site. Select any site you wish.
Execute cmdlets: By default this tool will only output the cmdlets that it would have run. Check this box to actually run the cmdlets.
Updated version released 5/27/2011 (1.1):
VMR Presence/Registration: RMX 7.2 supports virtual meeting room and entry queue registration. If you want to use this and do not need SIP URI dialing (<vmr>@domain.com) then check this box.
Other changes: The “RequiresReplication” option is set to false on the TrustedApplicationPool since DMA/RMX do not participate in Lync replication. The output is now color coded to make it easier to differentiate between cmdlets.