I have been working with a customer that uses Polycom RealConnect for Skype for Business (http://www.polycom.com/content-collaboration/content-sharing/realconnect.html) This is a fantastic technology which allows for a seamless integration of various video endpoints to one-click join Lync/Skype Meetings. We had originally setup the interoperability against a Lync 2013 Server Pool. After building out a new Skype for Business 2015 pool we wanted to move this interoperability (interop) to the new pool so we could upgrade the Lync 2013 pool and avoid any outages.
Technically speaking there is no way to simply move the interop between two Lync or Skype for Business Pools. The interop is based on the Skype UCMA Trusted Application model and moving trusted pools between pools is not something you can do in the product today. So you must effectively delete the interop and then recreate it on the new target pool. This will involve some very careful planning and a maintenance window or you will have unhappy users sitting in meeting rooms that won’t be able to join meetings
Initial setup
The focus of this article is what happens under the cover on the Microsoft Skype for Business side of the equation. To help illustrate what is going on I am providing the initial setup that was done.
The Polycom RealConnect interop will require the following configuration items in Lync/Skype:
- a Trusted Application Pool
- at least one Trusted Application Computer
- a Trusted Application
- at least one Trusted Application Endpoint (one per Trusted Application Computer)
So the following configuration had been done on the Lync 2013 Server side to initially get the integration working:
New-CsTrustedApplicationPool -Identity polycom.contoso.com -Registrar Registrar:Lyncpool01.contoso.com -site 2 –ComputerFqdn PolycomDMA01.contoso.com -ThrottleAsServer $true -TreatAsAuthenticated $true -RequiresReplication $false
New-CsTrustedApplicationComputer –Identity PolycomRMX01.com -Pool polycom.contoso.com
New-CsTrustedApplicationComputer –Identity PolycomRMX02.contoso.com -Pool polycom.contoso.com
Enable-CsTopology
New-CsTrustedApplication -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com -port 5061
New-CsTrustedApplicationEndpoint -sipaddress sip:PolycomRMX01@contoso.com -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com
New-CsTrustedApplicationEndpoint -sipaddress sip:PolycomRMX02@contoso.com -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com
Get-CsTrustedApplication | fl ServiceGruu
The ServiceGRUU is then used on the Polycom side as well as the Lync pool name to complete the interop. (I don’t cover this in this here but perhaps that is another post!)
Moving the Interop to the new pool
Now is the fun part. We are going to delete the interop and re-create on the new Skype for Business Pool! Once again, this will break the integration so please plan accordingly and do this during a maintenance window.
#Remove Endpoints
Remove-CsTrustedApplicationEndpoint -Identity sip:Polycomrmx01@contoso.com
Remove-CsTrustedApplicationEndpoint -Identity sip:Polycomrmx02@contoso.com
#Remove the Trusted Application
Remove-CsTrustedApplication polycom.contoso.com/urn:application:dmaproxy
#Remove Computers
Remove-CsTrustedApplicationComputer -Identity Polycomdma01.contoso.com
Remove-CsTrustedApplicationComputer -Identity Polycomrmx01.contoso.com
Remove-CsTrustedApplicationComputer -Identity Polycomrmx02.contoso.com
#Remove Pool
Remove-CsTrustedApplicationPool TrustedApplicationPool:polycom.contoso.com
Now recreating Interop on the New Pool
# New Trusted Pool at LDC
New-CsTrustedApplicationPool -Identity polycom.contoso.com -Registrar Registrar:SFBpool01.contoso.com -site 3 -ComputerFqdn PolycomDMA01.contoso.com -ThrottleAsServer $true -TreatAsAuthenticated $true -RequiresReplication $false
# New Trusted App Computers
New-CsTrustedApplicationComputer -Identity PolycomDMA01.contoso.com -Pool polycom.contoso.com
New-CsTrustedApplicationComputer –Identity PolycomRMX01.contoso.com -Pool polycom.contoso.com
New-CsTrustedApplicationComputer -Identity PolycomRMX02.contoso.com -Pool polycom.contoso.com
Enable-CsTopology
#Create New Trusted Application
New-CsTrustedApplication -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com -port 5061
#Create New Trusted Endpoints
New-CsTrustedApplicationEndpoint -sipaddress sip:PolycomRMX01@contoso.com -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com
New-CsTrustedApplicationEndpoint -sipaddress sip:PolycomRMX01@contoso.com -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com
New-CsTrustedApplicationEndpoint -sipaddress sip:PolycomRMX02@contoso.com -ApplicationId dmaProxy -TrustedApplicationPoolFqdn polycom.contoso.com
#GRUU for Polycom
Get-CsTrustedApplication | fl ServiceGruu
The new GRUU is given the to Polycom team and is used along with the new Skype pool name to setup the integration from the Polycom RealConnect side.
Comments