Archive for the ‘Lync’ Category

Lync 2013 with Polycom RMX1500 Integration

August 31, 2014 4 comments

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.


Click DNS.

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


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


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 for the FQDN for the RMX SIP signaling domain and as the IP address of the RMX signaling host.


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 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.

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.


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 “” 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 -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,

-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 “” -port 5061 -matchuri “” -UseDefaultCertificate $true

In this example “” is the RMX FQDN and “” 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


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.


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.


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,

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


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


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


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:

Categories: Lync

Bypassing Lync Client for online meeting

July 22, 2014 Leave a comment

Normally automatically login with Lync clients when join to onlline meeting with Lync meeting URL.
How to force login to Lync Web Apps from the lync client installed pc’s

Just add the string ?sl=1 to the end of the Meeting URL.Here is an example

Categories: Lync Tags:

Lync 2013 Enterprise Pool Front-End Service don’t start

April 14, 2014 2 comments


There are two lync 2013 front end server in the pool and lync front end service is not stating in one of the server .The follwoing error are looged in the eventvwr.

Server startup is being delayed because fabric pool manager has not finished initial placement of users.

Currently waiting for routing group: 04D3F0D5-0BE1-5C12
Number of groups potentially not yet placed: 22.
Total number of groups: .
Cause: This is normal during cold-start of a Pool and during server startup.
If you continue to see this message many times, it indicates that insufficient number of Front-Ends are available in the Pool.
During a cold-start of a large Pool it can take upto an hour for the placement process to finish as it needs to populate all the Front-End databases with data from the Backup Store. If the Pool is running and the Front-End is just started, this is normal for some time. If this repeats for a long time, ensure that all the Front-Ends configured for this Pool are up and running. If multiple Front-Ends have been recently decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.


1) Open Lync server management shell as an administrator

2) Then type the below command

Reset-CsPoolRegistrarState -PoolFqdn ” frondendpool name” -ResetType FullReset

Replace ‘ frondendpool name’ with your lync 2013 frond end server pool.This will reset the pool fabric state and will start lync frond end sevices on afected server .

%d bloggers like this: