FeedBurner makes it easy to receive content updates in My Yahoo!, Newsgator, Bloglines, and other news readers.
So at Ignite Albert Kooiman and I had the opportunity to re-unite and present some more details around the new Office 365 video interoperability service both Polycom and Microsoft are co-developing. This was a 300 level session where Albert and I started with a general overview and then went into more architectural details on this new service due for public preview later this year.
The session is embedded below and PowerPoint available for download here (this is not available on the event page right now)
Earlier this year Polycom and Microsoft jointly announced a new joint cloud video interoperability service. The goal here is giving Microsoft’s Skype for Business Online users a way to schedule meetings with the ability to easily add video room systems from vendors like Cisco, Polycom, LifeSize etc. You know, the kinds that either don’t play nice with Skype for Business or have direct Microsoft registration capabilities.
This sounds easy right? Well often this isn’t the case, you might need to deploy various boxes, go through a complex integration or even break the existing Skype for Business end-user workflow. This new service is geared toward making this easy, the technology is Polycom’s RealPresence Platform and the solution itself is RealConnect. This is all to be fully integrated with Office 365, hosted within Microsoft Azure and operated by Polycom.
Over the next few months more detailed information will be shared, next week Albert Kooiman and I will discuss this solution and also provide a demo of the experience, so don’t miss our Skype for Meeting Broadcast. Then at Ignite expect an even deeper dive on how this all works.
Webcast join details below:
Join Polycom and the Skype for Business team to hear and see a demo of the new Polycom cloud-based video interoperability service for Office 365 users. Built directly into the Skype for Business workflow, users can easily use this service to create an online meeting that Office 365 and other video endpoint users can join.
Join the Skype Meeting Broadcast, Friday, September 9, 2016, at 9:00 a.m. PST.
Speakers: Angela Donohue, Albert Kooiman, Adam Jacobs
Update: Recording from the Skype Meeting Broadcast is now posted online
Late last year Polycom released UCS 5.4.0 for their VVX portfolio, this was a major milestone as it introduced the ability to register to Skype for Business Online and Microsoft’s new Cloud PBX service. Whilst the VVX handsets are the first and (as I write) only 3PIP devices to support Microsoft’s online authentication mechanism “Org-ID”, the Lync Phone Edition handsets have supported this capability since their CU7 update.
Note: For those interested about Office 365 authentication, whilst Org-ID is the current mechanism, this is being transitioned to a new OAuth-based protocol – ADAL. Both are expected to work side-by-side until this transition is completed by Microsoft.
For more information on how to update your VVX to UCS 5.4.0 refer to a post by Jeff Schertz, here as I will spend time throughout the rest of this article to cover Skype for Business Online IP Phone Manageability.
3PIP IP Phones typically have their own way of being managed, in many cases via a vendor-specific XML files which in turn are provisioned via a centralized server – typically a secure Web or FTP server. Snom some time back introduced the ability to leverage Lync in-band policies by adding custom parameters via PowerShell, whilst this worked it very quickly became difficult to manage and does not address use cases whereby a phone requires a base configuration i.e. correct time/date and the phone itself isn’t signed-in.
We’ve also seen Event Zero take this further and provide a subscription-based solution, UC Commander, this can be hosted on-premises or in their cloud and gives you all the granular controls you might need (at a cost) within an extremely intuitive web-based graphical user interface.
With Microsoft’s Cloud PBX a base set of parameters can be configured via Online PowerShell, to connect to Skype for Business Online PowerShell, follow the following steps:
$credential = Get-Credential
$session = New-CsOnlineSession -Credential $credential
Get-CsIPPhonePolicy(see output below)
If anything doesn’t go to plan, refer to Microsoft TechNet documentation on Connecting to Skype for Business Online by using Windows PowerShell
So let’s take a look at these parameters and how to change them. First off you might notice that none of these share the same names as their vendor-specific counterpart, that’s due to the fact that some of these may become common between vendors. I’ll however focus on those that are specific to Polycom
|UserDialTimeoutMS||5000||Specifies the time in milliseconds to wait in On-Hook mode before dialing out automatically. If a user enters a phone number and does not click dial, the system will dial the number after the number of milliseconds specified. The default is 5000.|
|EnablePowerSaveMode||True||If enabled, phone goes to power savings mode (display turns off) based on values of the PowerSaveDuringOfficeHoursTimeoutMS and PowerSavePostOfficeHoursTimeoutMS parameters.|
|PowerSaveDuringOfficeHoursTimeoutMS||900000||Specifies the time in milliseconds to wait during office hours before turning on Power Save mode. The default is 900,000.|
|PowerSavePostOfficeHoursTimeoutMS||300000||Specifies the time in milliseconds to wait after office hours before turning on Power Save mode. The default is 300,000.|
|EnableOneTouchVoicemail||True||Specifies whether the Visual Voicemail feature in Skype for Business Online is enabled. If set to $true, the feature is enabled, otherwise $false.|
|EnableDeviceUpdate||True||Specifies whether the IP device will be updated by the Skype for Business Online service. If set to $true, IP devices will get firmware updates from the service, if $false the device will not be updated. The default is $true. Customers with an on-premises provisioning server are expected to change this to $false|
|EnableExchangeCalendaring||True||Specifies whether an IP device is enabled to connect to the Exchange Online calendaring service. If $true, users are able to connect to their Exchange calendars. If $false, users will not be enabled to connect to their calendars. The default is $true.|
||Specifies whether the Better Together Over Ethernet (BTOE) feature is enabled for users. If $true, and if the BTOE plugin is installed on the IP device, the user can tether the device to a PC and sign in to Skype for Business Online. The default is $
|LocalProvisioningServerUser||Blank||Specifies a username for the provisioning server.|
|LocalProvisioningServerPassword||Blank||Specifies the password for the provisioning server.|
|LocalProvisioningServerAddress||Blank||Specifies the address of the provisioning server for your organization.|
|LocalProvisioningServerType||FTP||Specifies the server type for the phone. The default is FTP.|
To change/set a parameter type:
Set-CsIPPhonePolicy -<ParameterName> <InputType>
For a full list of parameters refer to this TechNet document.
Update: Further testing suggests that there is in fact no TLS validation performed against the Match URI, instead the TLS validation is performed against the Trusted Application Pool name. In my example below both the Trusted Application Pool name and Match URI are the same. However if your Trusted Application Pool name is different to the Match URI you should follow the steps below but supplement the Match URI for the Trusted Application Pool name. Apologies for the confusion.
Lync and Skype for Business have a concept of configuring static routes, this is not to be confused with the networking equivalent, but more a way or routing SIP queries (for a specific domain) to either a PBX, CSTN Gateway or a 3rd party conferencing solution.
In this article I’m going to cover off the use case whereby a 3rd party conferencing solution has been deployed and the ability to dial “Virtual Meeting Rooms” is required. This is different to newer Skype for Business interoperability solutions, for example “RealConnect” first introduced by Polycom and then an imitation “Dual Home” by Acano.
For those that are deploying VMRs with Skype for Business (or already have this deployed and are upgrading to Skype for Business) read on…
Typically when 3rd party MCUs or conferencing components like Polycom DMA or Cisco VCS are deployed they’re configured within a Trusted Application Pool. Within the example below we have a Trusted Application Pool configured, with two Trusted Applications. Whilst the Trusted Application Pool is defined as “video.domain.com”, this has no bearing upon the SIP domain which could be entirely different.
For simplicities sake in this scenario my SIP domain is also “domain.com” and my “Match URI” i.e. the domain being leverage to trigger my static route will be “video.domain.com”.
So what’s new, why write this article at all? Previously, dating as far back to OCS and until Lync Server 2013, a Match URI could be configured without any TLS validation. So to use the above example I could generate a certificate for my Trusted Application Server with the FQDN of the server i.e. dma.domain.com and I was good to go.
However with Skype for Business the TLS route is now validated, so in the case above I need to generate a SAN that encompasses both the FQDN for my Trusted Application Server and the Match URI. Failure to do this will generate a “certificate trust with another server could not be established”.
Let’s step through this process, first off let’s recap on the goal. My Trusted Application Server is dma.domain.com and my Match URI is video.domain.com, I’m using a Windows Enterprise Certificate Authority and I need to generate my certificate.
Usually I’d use IIS to generate my certificates in this scenario, but we’re creating a SAN and whilst this is possible leveraging the certificates MMC snap-in – I like simplicity
So I’m going to use a free/excellent utility from my friends at DigiCert, they’re certificate utility for Windows is an easy way to create certificate signing requests (CSRs) – it’s also got my out of some tricky spots and performs certificate repair and troubleshooting.
Step 1. Create my certificate request
Open the certificate utility executable from one of your Front Ends and select the “Create CSR” dialogue on the top right (see below)
Step 2. Complete the certificate request
Ensure the certificate type is set to “SSL” and that your common name is duplicated and also specified within your subject alternative names.
Step 3. Generate and save to file
Step 4. Upload the certificate signing request file to your respective Windows CA, typically this can be performed via web enrollment by connecting to http://<CA.FQDN>/CertSrv. You will then be prompted to authenticate, once presented with this initial menu select -> Request a certificate -> Advanced certificate request.
Then paste as follows and ensure you change the certificate template to “Web Server” and click Submit.
Step 5. Download the certificate
Step 6. Complete the request and import the certificate
Click import on the top right, point to the certificate file and assign a friendly name for easy identification.
The certificate common name displays the Trusted Application Server FQDN (dma.domain.com) and the Subject Alternative Names contain both the Trusted Application Server FQDN (dma.domain.com) and the Match URI (video.domain.com).
Now proceed to upload the certificate to your 3rd party conferencing server and TLS errors are a thing of the past!
It’s great to see the momentum behind Lync (now Skype for Business). I’m specifically referring to businesses with long-time installments of PBX(s) are realizing the traditional telephony functionality which is now available within Microsoft Enterprise Voice (in this I’m referring to Skype for Business telephony). Admittedly there are some gaps, but these are now niche scenarios and are no doubt likely to be addressed as Microsoft preps they’re next server release – Skype for Business Server 2015.
Microsoft’s Third Party Interoperability Program or “3PIP”, plays a big part in this as Open SIP device manufacturers differentiate over the “Aries” or Lync Phone Edition handsets. An excellent example here is the Share Line Appearance or Boss-Admin functionality introduced in Lync 2010. By leveraging existing delegate functionality (typically set client-side) and additional SIP extensions sent server-side these phones can offer extended telephony scenarios.
These features can include:
Now in the case of traditional telephony administration typically the configuration for thereof would be performed by IT, so it’s not an unfamiliar request for customers to push back on the idea of offloading this to their end-users. To that end Microsoft has provided a command line tool which is included within the Lync Resource Kit (I’m sure in time this will receive the Skype moniker) – the tool is SEFAUtil.
SEFAUtil can be deployed on your existing Front End Server(s). It requires a Trusted Application Server configuration be setup (within Topology Builder) and some simple steps can be followed here.
Once this is configured the delegate configuration (including “Simring”) can be set for specific or groups of users. In the example below we’re going to configure Jennifer Parker as the “admin” for her “boss” Emmett Brown.
In this example my Pool name is “pool01.polycom-mslab02.local”, this should be adjusted accordingly depending upon your Pool name. I’m also executing this command within the Resource Kit directory, which for Lync 2013 is typically “C:\Program Files\Microsoft Lync Server 2013\ResKit”
.\SEFAUtil.exe /server:pool01.polycom-mslab02.local sip:email@example.com /adddelegate:firstname.lastname@example.org /simulringdelegates
(See example below)
Once this command is set a visual indication is typically seen on your phone, in the case below a Polycom VVX 500 has indicated to the “Admin” (Jennifer Parker) that she’s now capable of accessing the Boss-Admin feature-set on behalf of here “Boss” (Emmett Brown).
For more information on Polycom’s Boss-Admin feature refer to this blog post by a fellow Lync MVP Jeff Schertz and for Lync Resource Kit download information this can be obtained via the Microsoft website.
I thought I’d share a video I was asked to put together that illustrated Lync client behavior when a user is migrated from a Lync On-Premises deployment to Lync Online.
Prior to executing the PowerShell below I needed to complete a “Split-Domain” Lync deployment which I covered in a separate article here.
$creds=Get-Credential | Input tenant admin credentials
Move-CsUser -Identity <SIP URI> -Target sipfed.online.lync.com -Credential $creds -HostedMigrationOverrideUrl https://admin0a.online.lync.com/HostedMigration/hostedmigrationservice.svc | see my previous article for tenant specific URL identification
Get-CsUser -Identity <SIP URI> | Validate user migration
Move-CsUser -Identity <SIP URI> -Target <On-Premises Lync Pool Name> -Credential $cred -HostedMigrationOverrideURL https://admin0a.online.lync.com/HostedMigration/hostedmigrationservice.svc | see my previous article for tenant specific URL identification
It was almost a year ago when I wrote up a blog post on a new role within the next installment of Lync Server (now Skype for Business Server 2015) that Microsoft refers to as “VIS”. At that time information was limited. Microsoft had shown us a demo at Lync Conference 2014, but for the large part I was theorizing. Whilst the majority of my analysis was not far off, Microsoft have now lifted their NDA and they are now sharing with partners and customers more information on this new functionality.
So with this in mind, I’m going to share some more detail here and clarification around the video investments Microsoft have made as a part of this upcoming release due in 1H 2015.
Skype Video Federation
First up let’s talk about the bi-directional Skype consumer to Skype for Business video calling. This was originally enabled back in December following a blog post from the Skype Team. It’s gone through some minor teething troubles but nothing you wouldn’t expect when you open up a video workload from the largest telecommunications client in the world (with over 40% of the international call market share).
Microsoft have enabled this capability by leveraging a cloud gateway service, with video being offered via the V2 of this gateway (V1 offered IM/P and point-to-point voice calling). The major difference with V2 is that point-to-point video is now available, unlike the first gateway whereby media and signaling flow in all cases via this service (audio is transcoded), a common media and networking (ICE) stack can now be leveraged via Skype and Lync client updates. This means that now only signaling traverses the gateway and media can be negotiated directly, in most cases H.264 SVC for video and Silk for audio.
Remember content sharing and conference calling between Skype (consumer or business) and Lync is still not available. For deeper analysis Jeff Schertz has covered this here.
Clients supported include (taken from Microsoft slide):
|Platform||Lync / Skype for Business||Skype|
|Desktop||Skype for Business
Lync 2013 CU4 (audio with SILK)
Lync 2010 (audio only)
|7.1 and above|
|Windows 8 app||Lync for Windows 8–2.1 (audio with SILK)||Coming soon|
|Mobile (Windows Phone, iOS, Android)||Mobile 5.4 release (audio with SILK)||Coming soon|
|Web app||Not supported||Coming soon|
|MAC||Not supported||Coming soon|
So what is new here with Skype for Business? Today with Lync Server 2013, all Skype clients need to be registered with a Microsoft account, whereas the new server/client will permit you to add any user (Microsoft or Skype account registered).
Skype for Business Video Interoperability Server (VIS)
VIS is a new role that can be deployed on-premises, within Skype for Business Server 2015. It breaks the mold so far as the “brick” model is concerned and requires a dedicated server (or servers dependent upon scale). The primary focus for VIS is to allow net new Skype for Business customers to leverage their existing investment in Cisco VTCs (specifically those running TC 7.0 or higher and Microsoft has tested Cisco C40, Cisco C60, Cisco C90, Cisco MX200, Cisco MX300, Cisco EX60, Cisco EX90, Cisco SX20, the list will no doubt grow over time).
The feature-set on offer here wouldn’t be as extensive as say a Lync Optimized Room System (i.e. Lync Room System) or Qualified VTC (with native support), but in certain cases it might be “enough” or more to the point it will result in less of a burden when you’re making a business case to transition away from a Cisco UC platform to Microsoft.
Back at Lync Conference 2014 Microsoft demonstrated a direct registration operating mode, at launch an alternate mode (which may resonate more with customers) of CUCM SIP trunking is on offer. Whilst this requires existing Cisco infrastructure to remain in place (CUCM is leveraged here and not VCS), it’s likely that this will offer a smoother transition (until you turn all that Cisco stuff off, okay maybe the switches and routers are good for keeps ).
Calling capabilities include point-to-point calling (Skype for Business to CUCM not at release), and conference join (not via click-to-join, but instead escalation to conference via the Conference Auto Attendant and no drag/drop or CCCP). One last consideration here is that we are limited to VTCs within the organization i.e. Edge traversal isn’t possible.
Now let’s take a look at what is happening within the VIS component so we can understand things better. In the diagram below we can see signaling called out in grey and media in red (Cisco VTCs are registered to CUCM which is in turn trunked directly to VIS). One important take away is that in all cases both signaling and media need to traverse the VIS component – no media bypass. It’s easy to understand that signaling requires some manipulation (as we need to perform translation between Cisco and Microsoft SIP), but why media?
In my previous post I mentioned that whilst Microsoft have adopted H.264 SVC, it’s not the same as H.264 AVC and understandably nor is it the same as H.264 SVC from other vendors. H.264 SVC comes in multiple flavors (I won’t cover this here), but nevertheless heavy lifting is required to make these disparate media types interoperable. Furthermore the VIS server, if it is to provide a cohesive Lync 2013/Skype for Business client experience more than a single resolution type needs to be shared in a conference scenario (more on this below).
As I mentioned previously VIS isn’t a light-weight role, it’s not only taking an H.264 AVC video stream and making is H.264 SVC compliant (by updating PACSI NAL etc.), it’s also creating up to three simulcast (output) streams.
This is to offer a better experience for clients who are not capable of receiving the native resolution on offer by the Cisco VTC. Below is a potential real-world example whereby we can see the Cisco VTC sending 1080p and the AVMCU clients (Lync Room System, Skype for Business desktop and a Skype for Business tablet) receiving their requested resolution type:
You’ll notice in the example above no reference to VIS performing transcoding to RT-Video (VC-1), this is because this isn’t in scope here. This will ultimately result in any Lync 2010 clients not receiving video from a VTC (and vice-verse) for point-to-point or conference calling.
In conclusion Microsoft have made a significant investment in video interoperability in the next server edition. The take-away here is that this is significant for Cisco to Microsoft transitions – especially as VTC life spans are significantly longer than other endpoints deployed within enterprises.
With that in mind there are some limitations worth noting, for example H.323 isn’t in scope here (which is still widely deployed within enterprises). Another key point here is that the VTC will get a Lync 2010-style experience i.e. active speaker switching and content sharing is also a gap right now. For these reasons Microsoft continue to enhance existing Lync room systems and run a program for VTCs and MCU that are natively interoperable.
The Lync Room System folks have been busy as of late and a load of updates have been delivered over the last week (in time for Thanksgiving :)), first of all the 15.12 update.
This update includes a number of enhancements, notably:
There’s also an update to the Lync Room System Deployment Guide, some new items in here include:
Finally there’s also an update to the Lync Room System Portal here
Update: Overview of the new “Where is my join button” functionality.
One interesting new feature within the 15.12 update is a solution to the scenario whereby the organizer forgets to Lync-enable a meeting, previously I mentioned the conference policy update that an IT Admin can apply to prompt for Lync blobs (specifically whereby an LRS system is invited into the meeting) – see here. But this new feature in 15.12 will also go a step further to mitigate scenarios whereby the invite has already been sent, instead of the previous behavior when the calendar entry would say “Where is my join button”, a single click will prompt the end-user to send a new (this time Lync-enabled) invite from the LRS system itself. See picture below:
Once sent the meeting with start and other participant will get a new invite that they can click and join the meeting with. Note: This will not mitigate the need to update TNEF settings in Exchange, blobs would still be removed when the new invite is sent between Exchange Servers that do not have this setting specified correctly.
When scheduling a Lync meeting it’s important that you add your Lync meeting credentials to the Outlook invitation, this is a fairly obvious requirement and in the case whereby this isn’t added you could of course create an ad-hoc or “Meet Now” conference.
However when you’re using a Lync Room System forgetting to add these “blobs” to your invitation results in the lack of single click-to-join, therefore slowing down the time in which it takes to start the call. One thing however that I hadn’t noticed is that in CU2 for Lync Server 2013 Microsoft added a new conferencing policy setting that corrects the problem whereby an LRS resource is added to an invite but the “Create a new Lync meeting” button is omitted.
The setting is:
Set-CsConferencingPolicy -Identity Global -EnableOnlineMeetingPromptForLyncResources $true
By default this is set to false and needs to be enabled. Once enabled users will be prompted to add the Lync conference detail prior to sending the invitation (see below)
Hope this helps!
Back at Lync Conference 2014 Dustin Hannifin and I co-presented on the various video interoperability options available for Lync 2013.
I’m specifically calling out Lync 2013 as the video enhancements, specifically the addition of H.264 SVC, created challenges when integrating existing Lync 2010 video solutions. For those that want to know more on this subject I covered this in detail during our presentation – long story short whilst existing support for the RTVideo codec is still included various signaling changes require vendor specific updates.
Of the solutions available today there is an emphasis on all conferences taking place on a 3rd party MCU or bridge. Microsoft’s Video Interoperability Server (VIS) will bring some relief in this area, but in some cases this may not address all scenarios.
Many are already familiar with the Polycom RMX portfolio (don’t be deterred by cost at this point either, the entirety of this platform can now be virtualized and is also available in software), which previously was also limited to the same “meet on the bridge” scenario. But with the recent update a new capability (referred to as “RealConnect for Microsoft Lync” – don’t shoot the messenger I don’t work in marketing ) is made available. With this feature Lync clients continue to join the Lync Server (or AVMCU) and traditional video VTCs (not specific to Polycom), with an emphasis being on Cisco including their non-standard based “TelePresence Interoperability Protocol” (TIP), LifeSize and any other standards-based system) join the Polycom MCU. Both worlds are then cascaded or barbelled and Microsoft’s SVC is leveraged resulting in up to 5 of the active video participants being composed within the Polycom MCU layout, referred to as “Continuous Presence”.
RealConnect for Lync 2013 Overview
First up you’ll need to schedule the conference call, this achieved in the same way any other Lync conference is scheduled, specifically via a Lync Online Meeting invite – there’s one important attribute within the invitation and that’s the dial-in conferencing ID. This ID is leveraged by the VTC as a way of dialing into the call, so for those who haven’t deployed dial-in conferencing it’s a pre-requisite. Note for those that don’t already have this deployed or have the notion of enabling PSTN dial-in conferencing capabilities – that’s okay – a dummy number can be added, we’ll cover this later.
With the invitations sent to all those that are required to join the call, let’s go through the join process and UX. The animation below (credit to Jeff Schertz) illustrates the following steps:
We see the Lync clients (top right) joining the Lync conference (as per the usual process), resulting in an AVMCU call – with that Lync clients are now presented with “Gallery View” video (bottom right).
The solution is comprised of two mandatory Polycom infrastructure components:
Note: an additional software component is required for deployments where Lync to traditional VTC (and vice-versa) content is required.
I won’t cover the base Polycom RealPresence Platform steps, this is already well documented and this picks up from the point whereby both the DMA and RMX are already deployed and integrated via the Trusted Application process – one difference worth noting here is that creating a “Static Route” is no longer a requirement unless Lync to VMR calling is still a requirement.
The following content is an abridged version of the Polycom UC Deployment Guide for Microsoft Environments, this content was created by yours truly and edited by James Hill – the complete guide can be downloaded here.
Step 1. Enable Dial-in Conferencing:
1. Install the dial-in (PSTN) conferencing component for the Lync Front End server or Pool in the Lync 2013 Topology builder by going to Edit Properties > General > Features and Functionality.
2. Check Dial-in (PSTN) conferencing and click OK.
3. Publish the topology by right-clicking the central site name and clicking Publish Topology > Next > Finish.
Once published, the output displays as shown next.
After you change the topology, deploy the application on the Lync Server by running the Lync 2013 ‘bootstrapper’ process.
To deploy the application:
1. Open the command prompt on your Lync Front End server and execute the command:
%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
2. Install the associated service by opening the Lync Server Management Shell and executing Start-CSWindowsService.
Next, ensure that a dial-in conferencing region is configured. Typically, you need to configure multiple regions and assign local access numbers. In the following example, we add a default region in order to generate an H.323 or standard SIP number that users can dial into from any standards-based room system. The naming convention is not important but you must populate the dial-in conferencing region to complete the configuration.
To populate the dial-in conferencing region:
1. Open the Lync 2013 Server Control Panel and go to Voice Routing > Edit the Global Dial Plan > Dial-in conferencing region.
2. Specify a dial-in access number by going to Lync 2013 Server Control Panel > Conferencing > Dial-in Access Number > New and completing the following fields:
Step 2. Customize the Lync meeting invitation, add H.323/SIP dialing instructions:
If you want to customize the meeting invitation, you can add custom footer text to allow meeting participants to join a meeting using a standards-based video endpoint.
This example shows external addresses. If you want to show external addresses, you need to enable standards-based video Firewall traversal using, for example, a Polycom RealPresence Access Director.
Your Lync environment now includes Conference IDs in Lync-enabled meeting invitations.
Step 3. Configure DMA (SIP Peer):
Next, complete the Lync 2013 and DMA integration. Configure DMA network settings to match the Lync Server, specifically, Time and Domain. You need to configure the domain to match the extension you gave to the DMA DNS name.
Next, specify domain and time on the DMA system.
To specify domain and time on the DMA system:
1. In the DMA administrator screen go to Local Cluster > Network Settings > General System Network Settings.
2. Configure the time to synchronize with the same source as the Lync Server, typically one of your domain controllers, by going to Local Cluster > Time Settings. Specify an IP address for your time server as well as a time zone.
Next, add the Lync Server as an external SIP peer. To add the Lync 2013 Server as a SIP Peer:
3. In the DMA administrator console go to Network > External SIP Peers > Add. Complete the following fields:
You can leave the remaining fields blank.
4. In the left window, click Lync Integration.
5. In Maximum Polycom conference contacts to publish, enter the maximum number of VMRs you are publishing presence for. This field is not required for RealConnect. This example sets the maximum at 25,000, the recommended number.
6. Check Enable combined RealPresence-Lync scheduled conferences.
Step 4. Create a RealPresence Platform Lync account:
Next, assign a Lync account. This can be an existing account. However, Polycom recommends creating a dedicated Lync account that can be used to perform Conference ID to Lync Conference SIP URI resolution. In this case, the account can be a Lync account enabled for PC-to-PC telephony, as illustrated next.
Edit Lync Server User – RealPresence Platform Service Account
Step 5. Configure and enable the DMA Lync conference dial rule:
Next, create a conference template that is assigned to RealConnect Lync conferences.
To create a conference template:
1. Conference mode Set to AVC only. Mixed mode is not supported.
2. Enable the dial rule on DMA by going to the DMA administrator screen > Call Server > Dial Rules.
The Description field displays Dial by Lync conference ID.
3. Highlight the Dial by Lync conference ID and select Edit.
4. Check Enabled to enable the rule and the Conference template created in the previous step.
The available SIP peer(s) you assigned displays in Selected SIP peers.
5. Click OK.
Your RealConnect for Lync deployment is now complete!
Step 6. (Optional if not already configured) Ensure ICE is enabled on your RMX:
This configuration isn’t specific to RealConnect, however RMX 8.4 introduces a mandatory requirement, specifically where ICE needs to be enabled in all types of Lync deployment scenarios (with or without Edge deployed).
There are two supported methods, either user-based or a new method introduced in RMX 8.4 that leverages a UCMA option, with this we’re able to scale greater than 12 connections for remote worker/Federated scenarios. In the configuration example below we’re going to use the new approach which is now recommended.
To perform this configuration please refer to the new Trusted Application configuration within the sub-chapter Configure Lync Server for use with a Polycom RealPresence Collaboration Server System on page 61 of the Polycom UC Deployment Guide for Microsoft Environments here