you're reading...

Integrating the Polycom RMX with Microsoft Lync 2010 Server

I put this guide together for users who want to know how to integrate the Polycom RMX into their Lync 2010 environment.  These steps are based on a single server deployment of Lync.  It is intended for Lab/POC purposes only, not for full scale deployment.  You must contact your Polycom reseller to have Polycom professional services deploy this solution, so it is fully maintainable by Polycom.

Step One – Setting up the RMX DNS and FQDN settings

Log into the RMX bridge and go to the IP Network Services and double click on your Management Network Properties.


Double check that you have a correct MCU host name and specify your DNS server that Lync uses and input the local domain name and the DNS server address. Once you have entered these, you will be asked to reboot the RMX.  Click Yes to reboot now.


Step Two – Creating a Static DNS Entry for the RMX

While the RMX is rebooting, head over to your DNS server and create a static entry for the RMX Signalling Address – not the management address.  You can run a ping, traceroute or nslookup to check that the DNS entry is working ok.


Step Three – Creating a Trusted Application Pool for the RMX

Now log into the Lync Server and we are going to create a Trusted Application for the RMX in the Lync Topology Builder.  Right click the Trusted Application Servers and choose New Trusted application Pool.


The wizard will appear and enter the name you would like users to address virtual meeting rooms on the Polycom RMX bridge.  In my example below, I have chosen video.formula1.local as my name.  You could pick whatever you like such as bridge.fqdn, mcu.fqdn, conferencing.fqdn etc. Click Next


Next add in the FQDN of the RMX that was created earlier and click Add and then next. Then select the Front End Pool and hit Finish.



 You will then see the Pool created for the RMX.  The reason for doing it this way is because if you have multiple RMX’s in your network, then all the user has to do is dial a virtual meeting room and it will be routed to a next available RMX (using DMA).


Next we have to publish this new Topology.  Click next when the first window appears.


You will then see an error that the machine is missing, just click Yes to All to accept this.


You should then see that you topology has been successfully published. Click Finish.


Now we will go into the Lync Control Panel to check that the Topology has been published.


When users come to dial a virtual meeting room, they will be dialling 1001@video.formula1.local as an example.

Step 4 – Setting the RMX as a Trusted Host

Open up the Lync Powershell and type the following:


$route=New-CsStaticRoute -TLSRoute -Destination “f1rmx.formula1.local” -port 5061 -matchuri “video.formula1.local” -UseDefaultCertificate $true 

 Where the Destination matches your RMX FQDN and the MatchURI is the Trust Application Pool name.



Next we are going to set the route by typing


Set-CsStaticRoutingConfiguration -Identity global -Route @{Add=$route} 



Now we have to create the Trusted Application by entering the following:


New-CsTrustedApplication -ApplicationId rmxvideo -TrustedApplicationPoolFqdn video.formula1.local -port 5061 


You can use any ApplicationID as it is only for reference.


Once that has been done, we now need to enable this by typing Enable-CsTopology.  Now go to the Lync Control Panel and ensure that the RMX is listed as a Trusted Application under Topology > Trusted Application


Step 5 – Creating a Certificate for the RMX (using Self Sign Certs)

Open up the IIS Manager on the Lync server and select Server Certificates.  Right click a white area and select Create Domain Certificate


On the create certificate wizard, enter the details required.  For the common name, this must match the FQDN of the RMX that we created in step one.


Now select your online CA that is in your domain and provide a friendly name for the certificate and click Finish.


Now you should be able to see your certificate in the Server Certificates window.


You can now close IIS Manager and start MMC.  Add in the Certificates and select Computer Account and then select Local Computer.


Then expand Certificates > Personal > Certificates and you will see your certificates.


Right click on your RMX cert and choose Export


When the wizard opens up, select Next and then select Export Private Key and tick the box to Include all certificates in the certification path and Next.


Next you will need to provide a password for the certificate.  In my example I have just used polycom – all lowercase. Then select a location to save the certificate.  I placed mine on the desktop.  Make sure wherever your store the cert you are able to access it with the RMX web browser or RMX Manager. Click Finish. 


Once the certificate is saved, you can close MMC.  Now you need to create a text file called certPassword.txt and place it with the certificate. Enter the password you used when exporting the certificate.


 Step 6 – Setting the RMX SIP Settings

Open up the RMX console and navigate to IP Network Services > IP Network Service (or whatever your service is called).


Under the IP settings, change the dropdown menu to say H.323 & SIP.  Then head over to the SIP Server Settings.


Make sure you have SIP Server to Specify, SIP Server Type to Microsoft and the Transport type to TLS.  Then enter your FQDN of your Lync FE Server (mine is f1lync.formula1.local and then server domain.  In the Outbound Proxy server, enter your Lync server again.


Next change the Certificate Method to PEM/PFX and click on Send Certificate.  You will then be prompted to locate the certificate file and password file.  Control click and select both files.


Once both files are selected and then click Yes to proceed.  You should then get a message to say the 2 files were transferred successfully.


Once that is done, click OK to close the IP Network Services box.  You will then be prompted to restart the RMX.  Click Yes to do this. When the RMX comes back up, head over to Signalling Monitor and SIP Servers.  You should see that status as OK.  It could take a few minutes for the RMX to communicate with the Lync server.


Step 7 – Making a call from a Lync client to the RMX

Now it is time to try a call out to the RMX.  You can call one of the default meeting rooms, 1001, 1002, 1003 or 1004.  To make the call, in your Lync client, just type in the roomnumber@trustedapplicationpool.fqdn, so in my example I will dial 1001@video.formula1.local


Once the call is connected, you will see the RMX Welcome screen and hear the audio messages welcoming you to the conference.


That’s it; you now have scalable, flexible conference bridge, connected native to the Lync server, so expensive gateways or media servers.  In my next post, I will run through setting up meetings rooms on AD so users can search them easier and see presence.

Thanks to my colleague Brahim for some of the steps.



About Graham

Technology and motor sport junkie. http://www.about.me/grahamwalsh


28 thoughts on “Integrating the Polycom RMX with Microsoft Lync 2010 Server

  1. Graham, this post on Lync and Polycom Integration is simply superb. I have never come across such a precise step by step process showing snapshots from both POlycom and Lync interfaces.

    I configured my Polycom RMX 2000 with Lync 2010 for internal environment following the step by step process from your post and it worked error free.

    Recently i have opened the Lync Edge Server for remote access and i am facing a challenge in RMX integration with Edge. I configured the SIP ADVANCE by entering the userid created in AD with Lync Remote access configured. I used ICE environment as MS. POst reboot, my RMX says “Service Request Failed : Failure Response from the A/V Edge Server to the RMX Service Request” and “Failed to subscribe with the OCS, therefore the A/V Edge Server URI was not received”.

    Wanted to know, is my RMX trying to connect to the EDGE server from the INTERNET path? my RMX has a NAT to a Public IP, but not all the access is open. Do i have to open the communication between my RMX NAT (Public IP) and EDGE (Public IP)?


    Posted by Rony | May 29, 2012, 3:04 am
    • Thank Rony for the kind comments. I’ve not had a chance to do the ICE configuration guide just yet. Below are the details to get it working.

      As for the ICE user account, I know you mentioned it was enabled for Lync and Remote access, it also needs to be enabled for Enterprise Voice and Federated Access. Also the following ports should be opened:

      A/V Edge TCP port 443 and STUN/UDP port 3478 should be opened between A/V OCS Edge and RMX Signaling Server.

      A/V Edge SRTP: 443, 3478, 50000-59999 ports (Configurable range of ports. This is just an example) should be opened between A/V OCS Edge and the RMX media cards.

      Once that has been done, in the Lync/OCS Edge Server, you will need to authorise “rmx.company.com” as Domain Name, in order to be able to dial SIP URI address from outside. For example, to connect from outside a MOC client to the RMX meeting room 1002, you will need to dial from MOC client the following SIP URI “1002@rmx.company.com”.

      Posted by Graham Walsh | May 29, 2012, 7:10 am
    • Good afternoon to everyone. I have a concern and a problem in the integration curious that I have between a Polycom RMX 4000 and Lync Server 2010. Integration was performed correctly and the necessary static routes for these two environments to communicate seamlessly. But the strange thing is that after 7 days after no communication between the two environments. RMX computer is restarted or re-created static routes again and again no communication between the two platforms and returns within seven days to present the same problem. This is the error that throws me, when I do a trace from the Front-End Lync Server: Message expired in the outbound queue before It could be sent. If anyone knows how to solve this problem, we appreciate it. Thanks to all

      Posted by leomillos | September 16, 2013, 7:56 pm
      • Hi Leo

        I’ve personally not come across this problem before. It the RMX/Lync all fine say at day 4? Odd that it times out after 7 days, wonder if there is a setting in Lync to keep alive the static route. It would be worth opening a support ticket at support.polycom.com. You will need your RMX serial number and they can help troubleshoot as to why it is happening.



        Posted by Graham | September 17, 2013, 7:24 am
      • Hi Leo and Graham,

        We are having the same problem at two sites…

        Have either of you heard any more about this issue?

        We are getting SIPPROXY_E_ROUTING_MSG_SEND_EXPIRED from our Lync front end server.

        We reboot the RMX and all is fine until it stops working again.



        Posted by Graeme | October 1, 2013, 3:07 am
      • Hi Graeme

        What versions of software are you running on the RMX and Lync?



        Posted by Graham | October 4, 2013, 9:59 am
      • Hi Graham,

        The RMX 2000 is on and we’re on Lync 2010 at the moment…

        Polycom are looking into it but haven’t found anything so far.

        It’s odd in that it has got more frequent over time. At the start it would stay up for a week or so and now it crashes reliably every 2-3 days.



        Posted by Graeme | October 8, 2013, 7:04 am
      • The RMX versión is 7,8 or 7,7 the problema is the same with the two versions, lync 2010

        Posted by Hernando | October 7, 2013, 4:41 pm
      • Hi Graeme, I have the same problem, my email is elnaguar@hotmail.com, we share that we and you to try to solve the problem?

        Posted by Hernando | October 7, 2013, 4:56 pm
      • Hello Friends, as I commented in my case, the problem arises after 7 days running smoothly RMX team integration with Lync Server 2010. The version of the RMX 4000 was 7.8 and Lync Server 2010 cumulative updates encounters version 8. That problem may be occurring, which after 7 days stop working and the solution I have is to restart the computer again RMX or create static routes in Lync Server to run again for another 7 days. thanks

        Posted by leomillos | October 9, 2013, 5:01 pm
  2. I followed your guide to integrate RMX with Lync server 2010 and everything goes well. I am making a lab with lync and polycom products to show our clients a full solution.

    I work for a polycom platinum channel in mexico.

    thank you for this material.

    Posted by Mauricio | August 29, 2012, 4:47 pm
  3. Indeed a great article !!!!

    Posted by messagingschool | October 24, 2012, 4:43 pm
  4. Hi Graham, I am testing RMX 1500 with lync 2010 intigration. I am having problem to ping any fqdn from RMX ping test console. I have configured DNS sevrer in RMX which lync sevrer use . My lync and RMX is in different subnet but both can ping to each other by IP.I have DNS records for RMX and can reach from any sevrer in LAB

    Can you help me , what i am missing here in DNS configuration in RMX.

    You have imported certificate and password all together, its also giving me eror when i do it.

    Posted by messagingschool | October 26, 2012, 1:20 pm
    • Hi, I am not sure what the error might be. Is it possible to do a trace route from the RMX. The Ping utility might only be a H.323 ping (it is on the HDX platform).

      As for the certs, what error is coming up? Did you use the exact filenames and capital letters where needed?

      Posted by Graham | October 26, 2012, 4:28 pm
  5. Hi Graham,

    I have a second RMX I’d like to use with the same Lync server. Should this be possible? If so, which steps to repeat and which not?



    Posted by Luuk | January 3, 2013, 2:11 pm
  6. Graham, your process has worked great for 2 of our RMX’s many thanks for an easy to follow guide. I made a mistake on our third RMX how do i remove out the static routing configuration i get nervious from what i read i will remove the other routes too.

    Posted by Mark | January 24, 2013, 6:07 am
  7. Hi Graham,

    I have deployment RMX2000 v7.8 integration Lync 2010, but, the meeting room fails registred in sip.
    In RMX don´t have errors.
    Any suggestions?



    Posted by Rafael | September 23, 2013, 4:22 pm
  8. Hi all,

    We’ve been working with Polycom to resolve this issue and they have now made the following statement :

    “Issue due to RMX (SIP-task) lack of resource for building connections. This issue will be fixed in 8.1.7.”

    So it looks like there’s some light at the end of the tunnel.



    Posted by Graeme | October 16, 2013, 7:45 am
  9. Dear Graham, This is a Great Guide. I would like to know, is it Possible for two MS Lync Servers to share one RMX? Say, two organizations with Isolated Lync sharing one Common RMX in one of the organizations.

    Posted by Voltron | May 8, 2014, 7:08 am
  10. I have Skype for business server and lync 2010 server running side by side. Can I create trusted application on both sfb and lync pointing to single RMX. I know RMX can only register to one SIP server at a time. But I need to know if creating the trusted application on sfb will affect the already integrated Lync 2010.

    Posted by Tolu | December 10, 2015, 8:41 pm
  11. Hi Graham,
    I have a sfb server and lync 2010 server running side by side. I also have one rmx2000 which has been integrated with lync server 2010. Currently I’m testing realconnect with sfb. Can I run all required sfb configuration script to the RMX without affecting Lync Server. I know RMX can only register to one SIP server at a time, but is there any impact configuring sfb to point to single rmx.

    Posted by Tolu | December 10, 2015, 9:17 pm

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: