Home > Lync > Lync 2013 with Polycom RMX1500 Integration

Lync 2013 with Polycom RMX1500 Integration

The following post shows how to configure and deploy Polycom RMX 1500 in Microsoft  Lync 2013 Environments.

Task 1 : Configure the RMX IP Network Service :

Using the Web browser, connect to the RMX.
In the RMX Management pane, expand the Rarely Used list and click IP Network Services.
In the IP Network Services pane, double-click the IP entry.
Make sure the IP Network Type is set to H.323 & SIP
Set the  Signaling Host IP Address and sub net mask.

2

Click DNS.

Enter the following related information :
MCU Host Name : rmx1500.seneej.com (enter here the hostname of the RMX)
DNS: Specify (enter here “Specify”)
Local Domain Name: seneej.com (enter here the domain name where Lync is hosted )
Primary DNS Server: 192.168.1.10 (enter here the IP address of the DNS server )

4A

After its prompt for reboot, then reboot RMX system.

Login  back o RMX web interface .In the IP Network Services pane, Click SIP Servers.
In the SIP Server field, select Specify.
In the SIP Server Type field, select Microsoft.
Enter the IP address of the Lync frond end  Server 2013 and the Server Domain Name.
If not selected by default, change the Transport Type to TLS

3

Task 2 : Add the Polycom RMX FQDN (SIP signaling IP address) in DNS as Static entry

Define the new A record under DNS server. The following example defines a record using rmx1500.seneej.com for the FQDN for the RMX SIP signaling domain and 192.168.1.100 as the IP address of the RMX signaling host.

1

Task 3 : Create trusted application Polycom RMX pools in lync

Login to lync frond end servers and open the Lync Server Topology Builder.
When prompted, save a copy of the topology.
Expand the appropriate site container, right-click the Trusted Application Servers folder, and select New Trusted Application Pool.
In the Define the Trusted Application Pool FQDN, enter the name of the FQDN of the application pool you want to create,

5

5 Click Next to add computers to this pool.
6 In the Define the computers in this pool step, enter the FQDN for the RMX SIP signaling domain and click Add.

6
When finished adding computers, click Next.
Select the appropriate Next hop pool and click Finish.
Select Action > Topology > Publish to verify and publish your topology changes.

Click Yes on the Missing Machine warning message.
When it publishes the topology, the Lync Server attempts to match the FQDN of the Trusted Application Computer to an existing Computer object in Active Directory and typically displays a Machine Missing warning, as shown next.

7

Click Yes to accept the warning and complete the topology publishing wizard. Because the RMX system is not a Windows domain-joined host, it does not need to exist in Active Directory. There is no need to either domain-join the host or re-run this step as described in the warning message.

Go in the “Lync Control Panel”, in “Topology” menu, in the “Status” section and verify that the RMX FQDN entry “rmx1500.seneej.com” is there in the list.

Task 4 : Use Lync PowerShell to Create the Trusted Application

Open the Lync Powershell terminal from any of frond end servers

Use the New-CsTrustedApplication command to set up a trusted application for the RMX system.

New-CsTrustedApplication -applicationId VideoProxy -TrustedApplicationPoolFqdn rmxvideo.seneej.com -port 5061

The parameters are defined as follows:
-Applicationld A descriptive name for the application. Must be unique within your Lync deployment.
-trustedApplicationPoolFQDN The FQDN of the application pool the entry defined previously.. In our example,rmxvideo.seneej.com

-port The SIP port. The default port number for SIP is 5061.

Task 5 :Set the Routing for the Polycom RMX System

open the Lync Power shell terminal.from any of frond end servers

Use the New-CsStaticRoute command to set up a static route for the RMX system.

$route=New-CsStaticRoute -TLSRoute -Destination “rmx1500.seneej.com” -port 5061 -matchuri “rmxvideo.seneej.com” -UseDefaultCertificate $true

In this example “rmx1500.seneej.com” is the RMX FQDN and “rmxvideo.seneej.com” is the trusted entry defined previously.

Set the routing configuration. By configuring the static route, matched URI dialing is enabled.

The following example sets the route to be global and publish the topology:

Set-CsStaticRoutingConfiguration -identity global -route @{Add=$route}

Then Publish Lync topology

Enable-CsTopology

The Polycom RMX system is now set as a trusted host, and calls from an Lync client to a SIP address in the Polycom RMX system’s domain will be routed through that system.

Task 6 :  Creating a Security Certificate for the Polycom RMX System

Its must install a internal/ external security certificate on the RMX system so that Lync Server trusts it.

Please follow below if have internal enterprise CA.

Login the Lync server and create a new certificate for RMX using the IIS Manager from the lync server

In the Features View, double-click Server Certificates under IIS, shown next.

8.

In the Actions pane (far right), select the Create Domain Certificate, shown next.

The Create Certificate wizard displays.

In the Distinguished Name Properties panel, shown next, complete all fields. Do not leave any fields blank. Do not leave any fields blank.

9

In the Common Name field, enter the FQDN of RMX FQDN. This name must match what is in the DNS.

Click Next.
In the Online Certification Authority panel, select a Certificate Authority from the list and enter a name that you can easily identify,

10
Click Finish.
You have created the certificate.

To use the Microsoft Management Console to export the created certificate:
1 Open Microsoft Management Console and add the Certificates snap-in, if it has not been added already.
a Choose File > Add/Remove Snap-in.
b Select Certificates from the Available Snap-ins area and click Add.
c On the Certificates snap-in dialog, select Computer Account and click Next.

d On the Select Computer dialog, select Local Computer.
e Click Finish.

2 Click OK.
3 Browse to Certificates (Local Computer) > Personal > Certificates.
4 Right-click the created certificate and select All Tasks > Export… to view the Certificate Export wizard.
5 In the Certificate Export wizard, do the following:
a In the Export Private Key panel, select Yes, export the private key.
b Click Next.
c In the Export File Format panel, shown next, select the option Include all certificates in the certification path if possible.

d Click Next.
e In the Password panel, enter a simple password.
f Click Next.

6 In the File to Export panel, enter a path where you want to save the new file, for example, c:\temp\cert.pfx.
7 Once the *.pfx file is on your PC, you can upload it to the Polycom  RMX system and install it, using below procedure

Importing Certificates in to the RMX Manager ( 8.1 firmware release and higher )

1 Open RMX Manager

2 Go to Setup -RMX secured Communication –Certification Repository

11

3 Highlight Personal Certificates and Click the Add button to open the Create Personal Certificate window and change the Certificate Method to PEM/PFX. Enter the Password which was used to protect the PFX package and then click Send Certificate

12

4 In the Install File window browse to the previously exported PFX certificate package and click Yes to upload the certificate, private key, and CA chain into the RMX.

5 If successful the response should be “Message file transferred successfully” and RMX Manager will request to reboot the RMX to apply the new certificate to the SIP services

Testing

Then check in the Signaling Monitor, in SIP Server and you should see the IP address of Lync server with status as “OK”.

Then go on a PC client and open Lync and enter for example the following SIP URI to call Meeting Room 1001 in RMX from Lync client: 1001@rmx1500.seneej.com

Advertisements
Categories: Lync
  1. September 24, 2014 at 6:44 pm

    Nice post but a few issues, if I may:
    1) The matchURI does not have to reflect the application pool name.

    2) The domain specified for the RMX interface matches the matchuri

    3) The sipuri entered into the Lync client should have a sipdomain that is specified as the matchuri not the destination FQDN

    The matchuri can also be the same sip domain used by Lync 😉 ….

    • seneej
      September 24, 2014 at 6:58 pm

      Thanks!

  2. Eric Chu
    November 24, 2014 at 9:18 am

    hi sennej

    rmxvideo.seneej.com , this need DNS record ? and what is this ip ? Thank you very much .

  3. June 11, 2015 at 7:52 pm

    Hi,
    Thanks for posting this article. I’m curious to understand the base requirements to setup a conferencing solution with Lync Online. I currently don’t have one in place and would like to setup a Polycom CX3000 with a Lync account and a phone line. would be nice to have a tv to project the video as well. any direction would be greatly appreciated.
    Thanks.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: