Enabling Skype for Business UI For Lync Server 2013 and Skype for Business Online

As you all might know by now, Microsoft have started rolling out the Skype for Business client over windows update as well as a standalone update. The patch is called KB2889923 and once installed, the client UI can be switched from Lync 2013 in to Skype for business, There are couple of ways to get this update. One is to run windows update on the client PC which will pick the update up from Microsoft. Add the other method is to download the standalone update package and install it on the client. The update can be downloaded from here I took the long path and ran windows update on my PC that picked up the update as expected and updated the client. Capture4

Once the client got updated, it will immediately complained that the System Administrator only allowed to use Lync UI and not the Skype for Business UI. Upon restarting the client, it reverted back to the Lync 2013 client,Capture1

So, to allow the Lync client to work instead of Skype for Business client, it needs to be enabled within the client policy which the user is assigned with. To have the “EnableSkypeUI” policy entry, the Lync Server 2013 platform should be running on no earlier than November 2014 CU update. Since Microsoft override the current CU with the new one in official download page, the latest Lync Server 2013 update can be downloaded from here. Once the server is up to date, create a new client policy as “Enable Skype UI” by running the command “New-CsClientPolicy -Identity “Skype UI Enabled“. The reason behind not enabling the feature for the Default client policy is that, if it enabled for default, it will get rolled out for the entire client fleet and it will end up in massive confusion. It’s always better to create a new User based client policy and assigned to users who suppose to have the feature turned on. Once the new client policy has been configured, run the command “Set-CsClientPolicy -EnableSkypeUI $True -Identity “Skype UI EnabledCapture

Now we have the client policy configured to enable Skype for Business UI, the policy need to be assigned for the users who required to have the feature turned on. This can be done either from the Lync Server Management Console,Capture5

Or can be done from Lync Server Management Shell by running “Grant-CsClientPolicy -Identity “User Name” -PolicyName “Skype UI EnabledCapture3

The user account is now enabled to have Skype for Business UI instead of the Lync 2013 client. It will take some time for client to pick up. Once it’s done. It will come up with an alert mentioning that the organization is rolling out Skype for Business and restart the client to enjoy the new features of the Skype for Business client.Capture2

Upon restarting the client. It will start as the Skype for business client and full features and functionality which designed to be delivered from client end will be available to use despite the fact that the back end server is still Lync Server 2013.Capture6

That’s all is there to know about rolling out the Skype for Business client within the organization that running with Lync Server 2013 back end servers. It’s all about planning the roll out properly and managing the client policies properly so that it will not end up in a confusion. The same setup is available for O365 Skype for Business (Lync) online. Please use the official Office Blog here which explains how to do the switch over from Lync 2013 to Skype for Business.


What’s new with Skype for Business Client

Microsoft released the preview version of Skype for Business client last week and by the look of it, it seems to have a make over session from Skype department. Even though it now comes with a flashy new skin, from under neath it hasn’t changed much from it’s predecessor.


At a glace, it has the same tabs that’s Lync client had except for more “Skype” like icons. In fact, the “Recent Calls”, “Dial Pad” and “Calendar” features are exactly as it is compared to the Lync client. The tabs are how how it should be and nothing much to improve in that front. There hasn’t much changed in “Options” apart from changing all the reference from “Lync” to “Skype for Business”.

Having said that, Microsoft have made some significant changes to the way that client reacts while on a call. They moved away from much confusing “Hover” concept on to more back to basic “Click” option which made life much easier for everyone. Now, transferring a call is just a matter of few clicks.


Another excellent feature that came from Skype, is the call control menu on desktop while the conversation window is minimised. The small window comes up with Mute and Hang up button when the main window is minimised and it change the picture based on the active speaker. It would have been excellent if Microsoft went an extra mile and add Call Transfer and Hold buttons in to it so that it looks more complete and would be ideal for a reception user.


Further more to the improvements, the Skype for Business client now have animated emotions just like Skype does and introduced new set of tones including a new ringing tone. The back end server i was testing the client with was, Lync Server 2013 server platform and there are no complaints about the functionality.

The other and most anticipated change would be the SILK codec activation. SILK is the codec that Skype use which enables it to sustain an audio call with a better call quality even the internet connection is not that good. Even in Lync 2013 client, SILK was there in the SDP list but, it didn’t participate in an active audio conversation. Even in a call between Skype and Lync 2013, it used G.722. In Skype for Business client, it’s all SILK. So to test this, I made a call between 2 Skype for Business preview clients and it does seems to be settling for SILK instead of G722 or RTA, unlike the typical Lync 2013 client would do.


So where is the full and final client coming from?. Unlike Lync 2013 client which came along side with Office 2013, Skype for Business client delivered as an update to the existing Lync 2013 client. This update scheduled to roll out in 14th April. The default UI for those who use Lync today will still be Lync 2013 even after running the update. If you want to change the UI to Skype for Business, then there is a switch available in Client policy that can enable the Skype for Business UI. It is already been published for Skype for Business online and still waiting for Skype for Business on premises.

For more information about the UI switch in Skype for Business online, visit Office Portal “Switching between the Skype for Business and the Lync client user interfaces”

In brief, it does look good that the Lync client and well presented. But underneath, old “Lync” spirit is pretty much alive and kicking with addition the of SILK. The Skype for Business server is rumoured to be out in early May and we all can look forward to an exiting time ahead. The Skype for Business Preview client can be downloaded from Microsoft Evaluation Centre.

Upgrading to Skype For Business Server 2015 form Lync Server platform

As all of you might know by now, “Lync Server” or the brand name “Lync” is going away and it’s successor is called “Skype for Business”. Despite the change of well known and adored product name, Skype for Business is set to achieve higher goals in UC world while keeping Microsoft’s “Mobile first, Cloud first” strategy alive. As the name suggests, it’s a mixture of great features and functionalists between Skype and Lync put together to become the ultimate collaboration platform in unified communications space.

Unlike upgrading from Lync Server 2010 to Lync Server 2013, Microsoft has made it easier by employing In-Place upgrade method rather than Side-By Side upgrade process. Also this would help to save the investment that made from coming out of Lync server 2010 to Lync server 2013 including the license cost. Since the Skype for Business server requires the same hardware specification as the Lync server 2013, it saves money on hardware front as well. The whole upgrade process does not require any user downtime if you’re running on top of Lync server 2013 platform. Have a look at below table for the in-place upgrade supportability; Capture

In Lync Server 2013 paired pool scenario, It recommended that to move the users in to the other pool and upgrade the base pool to Skype for Business Server. Once done, move the users back to the base pool and then upgrade the paired pool to Skype for Business Server. In a pool paired situation, both the pools must be upgraded one after another assuring the time both pools spend in different versions to the minimum.Capture

If the current platform runs on Lync server 2010, there are two options available to upgrade to Skype for Business Server. Number one and most practical would be straight forward Side-By Side upgrade process to Skype for Business Server. In this scenario, In-Place upgrade is not supported. The upgrade process need to be carefully planned and downtime notice has to be sent for users before the migration processCapture

The other option is to upgrade the existing Lync server 2010 platform to Lync server 2013 employing Side-By side upgrade methodology and then, In-Place upgrade the Lync server 2013 pool to Skype for Business server. I cannot work out such reason to follow this path other than upgrading the Lync server 2010 platform to Skype For Business server. This process require a significant downtime and time consuming.Capture

Moving in to the roles and services that supports In-Place Upgrade process within Lync server 2013 platform includes the Front end pools, Director pools and Edge pools. The Survivable Branch Appliances (SBA) appliances are not supported for In-Place Upgrade. This is something that the appliance providers should include in to the device (S4B Image) so that it can be configured with the Skype for Business Front end server pool. Survivable Branch Server (SBS) is supported for In-Place Upgrade. Capture

For the SQL back end supportability for enterprise pools, the existing back end pools will get updated by running the Update-CsDatabase command in the process of publishing the topology. In the process of running the deployment wizard in Front end servers, the local SQL express copy of SQL 2012 will upgraded in to SQL 2014. Below is the table that highlights overall SQL version compatibility within the migration process. Capture

This wraps up the upgrade consideration and recommendations when moving Lync Lync server platform to Skype for Business platform. The contents of this post are in courtesy of O365 Summit.

Putting Lync integration with Skype under the Microscope

The purpose of this article to explore the integration between Lync and Skype. This was enabled ages ago for Voice. And recently in November, Microsoft has announced the availability of Video between Lync and Skype. This was a feature that everyone’s waiting for. There were rumors that Microsoft will enable this feature on the upcoming Skype for Business server but luckily, it jumped the gun before that.Capture

The functionality was enabled couple of months ago in mid November and it worked for a while. And it got disabled due to some reason (could be bugs) till further notice. Now, it’s back once again. The integration only works with the Skype client version which can be downloaded from Skype web siteskypeversion

Since the acquisition of Skype, Microsoft mentioned the the voice coded that’s been used in Skype, is the most optimised voice codec to send voice over wide area network. The codec is called “Silk“. This codec was embedded to Lync’s SDP list by a Cumulative Update but, it’s not getting used so far. Below is a SDP list of an INVITE from Lync 2013 client to another Lync 2013 client. LynctoLync

Even though it’s offering Silk, the client settle with the MSRTA codec which is the heights on priority. The Silk codec is lost between the negotiation process.settle on

So getting back to the topic in hand and looking at a call between Skype and Lync, If the call originated with Skype, Skype surprisingly wants the call to be established over G722 as a priority even though Microsoft stated that it will be using Silk as a priority form going forward;

“This includes built-in security, with enterprise class encryption of both media and signaling using TLS and SRTP, enabled by default. It includes connectivity, with standards-based traversal of personal and corporate firewalls using STUN, TURN and ICE. It includes high quality, scalable video using the industry standard H.264 SVC codec. Finally, it includes the SILK audio codec as the default choice for Lync to Skype calls. SILK is used for billions of minutes of audio calls every day, and provides a phenomenal balance between audio quality, bandwidth utilization and power consumption”

Below is the snapshot of the SDP list that getting offered within the invite it self from from Skype to Lync;SkypetoLync

But, Lync client always uses MSrta codec. So the call between Lync and Skype will settle for MSrta that is the 3rd in priority even though Lync is capable of working with G722 which is the highest priority next to Silk.Lynctoskype settle

In the other hand, calling from Lync to Skype, Lync offers MSrta as a priority and Skype settle down with MSrta without any drama. Again, no Silk in the picture.Capture2

As for the Video, Microsoft has introduced H.264 SVC to support natively with Lync 2013 which allows the client to VC end points such as Polycom without having to use MSrtv as the video codec. For video integration between Lync and Skype, Microsoft have used H.264 SVC instead of the MSrtv. The SDP list that offered from Lync has the H.264UC as the priority and the call get established over H.264 SVC. Video

I was under the impression that Lync will use Silk when it’s communicating with Skype and it was confirmed by Microsoft that it will be the case. Unfortunately, it’s not. As clearly shown above, it use MSrta as audio and as promised, it use H.264 SVC as video.

So hopefully when Skype for Business comes out, it will use the full strength of Silk codec for audio and we could hope for a better voice quality than what we are getting now in the future.

Configuring Unified Contact Store (UCS) with Lync server 2013

One of the interesting features that supports when both the Lync server and Exchange server are on 2013 platform, is the Unified Contact Store. The purpose of the UCS is that to store a Lync enabled user’s contact in Exchange server instead of Lync server it self. One of the other benefit is that, to use Outlook to manage contacts instead of Lync 2013 client.

Usually the default contact list provider for Lync client is the Lync server. When you go in to the configuration information of the Lync client, you can see that Lync Server is right in front of the “Contact List Provider”Capture

After configuring UCS and enabling UCS for a user account, the default contact list provider will change to UCS as shown below. From that point onwards, the contact list if uploaded to Exchange server and will be managed by Exchange.Capture23

Going in to the configuration, the first step would be to configure the server to server authentication (oAuth) between Exchange server and Lync server. It must require a certificate that issued by a trusted issuing provider and configuring each other as partner application.

Certificate requirement

I have covered the certificate configuration steps in a previous article that described configuring integration between OWA and Lync server 2013. If this integration is in place, likely possibility is that the certificate configuration is already done. Else, you need to make sure that the Lync servers and Exchangers servers are having certificate that must be issued by a trusted issuing authority or an internal root certificate authority. It will not going to work if the Exchange is on self signed certificate.

Partner application configuration in Exchange Server 2013

Before configuring the partner application within Lync server, It requires to know the exchange auto discover URL. To get the auto discover URL, run the command;

Get-ClientAccessServer | Select-Object Name, AutoDiscoverServiceInternalUri | Format-List

and note down the URLCapture13

To configure the Lync server as a partner application for exchange, you need to run the below command in exchange management shell. Within EMS, navigate in to the “Scripts” folder and execute the EnterprisePartnerApplication.ps1 script with the switch -AuthMetaDataURL and -ApplicationType. So the complete command would looks like;

“C:\Program Files\Microsoft\Exchange Server\V15\Scripts\Configure-EnterprisePartnerApplication.ps1 -AuthMetaDataUrl ‘https://<Lync FE server\Pool FQDN>/metadata/json/1’ -ApplicationType Lync” Capture16

Once done, restart the IIS services on the CAS server and we are done with Exchange.Capture17

Partner application configuration in Lync Server 2013

Before going in to the partner application configuration, oAuth configuration need to be set with the exchange auto discover URL. The purpose of this is to get the Lync server to know where to find the auto discover URL. The command that need to be run on Lync management would be;Capture15

Now to move in to partner application configuration, within lync server, you need to configure the exchange server as a partner application. To do this, the command New-CsPartnerApplication including -MetaDataURL and -ApplicationTrustLevel. The MetaDataURL would be something like;


The full command that need to be run on Lync Server management shell would look like;

New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl “https://autodiscover.domain.com/autodiscover/metadata/json/1&#8221; Capture18

That’s all there is to do with the server side configuration. Now to enable UCS for clients and do some testing. UCS configuration is there inside the “UserServicePolicy”. Usually in a deployment there will be only “Default” user policy. It’s not recommended to go ahead and enable the UCS within the default policy. Best practice is to configure a custom policy and assign that to pilot users before rolling it up to production.

To configure a custom UserServicePolicy, run the command New-CsUserServicePolicy as mentioned below;Capture21

Now go ahead and enable the the pilot users for above configured user policy by running the command Grant-CsUserServicePolicy as mentioned below;Capture22

To test the exchange connectivity, run the command Test-CsExStorageConnectivity with the user SIP URI. It might take some time to get the changes to reflect to exchange.Capture19

And finally to test the UCS availability for the user account, run Test-CsUnifiedContactStore command as shown below;

Test-CsUnifiedContactStore -UserSipAddress testuser@domain.com -TargetFqdn lync.domain.com –UserCredential $credCapture

The result would be;Capture2

At this point, the test user is successfully enabled for UCS and in client configuration, it should change the “Contact List Provider” form “Lync Server” to “UCS”

Configure OWA integration between Lync Server 2013 and Exchange 2013

Integrating OWA with Lync Server 2013 will support IM and Presence when logged in to the OWA from internal LAN as well as from the Internet. By default, this integration is not in place even though both the platforms are in 2013 version. Having both platforms in 2013 version allows you to get more out of the integration. Apart from OWA integration, it supports UCS (Unified Contact Store) and Archiving in Exchange server so that you don’t need an additional SQL database instance for this. So in my setup, i have deployed an Exchange server 2013 in one box (Venguard-Pluto.ucetechie.com) and Lync Server 2013 Standard Edition (Venguard-Earth.ucetechie.com. When i fire up the OWA for the first time, i don’t see presence against my name;Capture1

To begin with the integration process, it’s pretty straight forward. All you have to do is;

  • Configure certificate in Exchange
  • Configure Exchange to allow IM and Presence
  • Configure Exchange web services to support Lync Server 2013
  • Configure Trusted Application pool in Lync Server 2013 to integrate Exchange CAS

Let’s jump in to Configure certificate in Exchange, If the Exchange services are configured with the self signed certificate, that need to changed to a CA generated certificate. It can be a certificate that was generated from a public trusted CA or it could be a certificate generated from an internal root CA. The bottom line is, the Lync server must trust the certificate that getting presented by the Exchange server. As you can see below, the certificate that I have in my exchange server is a certificate that was generated from an internal trusted root CA. It’s the same CA that issued the certificate for Lync Server. Note the Thumb Print of the certificate.Capture2

Below are the services that I enabled for this certificate. I’ve enabled it for all the services that I use within the Exchange server and discarded the Self Signed certificate. The primary services that this certificate need to be enabled for are, Exchange Web Services internal, Auto Discover and IIS)Capture3

Now, Configure Exchange to allow IM and Presence, Run the command, Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled $True -InstantMessagingType OCS. Thic command will configure the OWA virtual directory to support IM & P with Lync Server.Capture4

Configure the Mailbox policy to enable IM & P. By default, this feature is disabled. If you want certain users not to have this feature, you can configure a different mailbox policy apart from the default and enable IM & P for the new policy and leave the default as it is. I have configured the default policy to enable IM & P as mentioned belowCapture5

Next step is to Configure Exchange web services to support Lync Server 2013, Navigate to “C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa” in the CAS server and open the “Web.config” file with note pad. Keep in mind to take a backup copy before anything. Add the Keys, “<add key=”IMCertificateThumbprint” value=”EA5A332496CC05DA69B75B66111C0F78A110D22d”/>” “<add key=”IMServerName” value=”atl-cs-001.litwareinc.com”/>” Within the <appSettings> component as shown below. The “IMCertificateThumbprint” is the Exchange Server certificate Thumb Print and “IMServerName” is the FQDN of the Lync Server 2013 Front End server or Pool. If you have multiple CAS servers, you need to do this on them as well.Capture6

After the above change on the config file, you need to recycle the application pool of the OWA. You can do this by using the IIS admin console and navigate in to the OWA Application pool. Or, run the command C:\Windows\System32\Inetsrv\Appcmd.exe recycle apppool /apppool.name:”MSExchangeOWAAppPool”Capture7

Now, we are done with Exchange. Fire up the OWA and see that the page comes up and it behaves as expected. According to Microsoft, if both Lync and Exchange are on 2013 version, you should see the presence against your name and there’s nothing you need to do with Lync Server (Given that you have the EWS working fine internally as well as through the internet). But, I prefer configuring the Lync Server end so that the integration is complete. In Lync Server side, I need to Configure Trusted Application pool in Lync Server 2013 to integrate Exchange CAS Fire up the Lync Management Shell and run the command “Get-CsSite” to get the Site ID.Capture8

Create a Trusted Application pool as the Exchange CAS server using below command “New-CsTrustedApplicationPool -Identity -<Exchange CAS FQDN (as mentioned in the certificate)> -Registrar <Lync Server Pool or FE FQDN> -Site <Site ID> -RequiredReplication $False The key thing here is that making sure the certificate name and the CAS FQDN is the same in above command. It has to be same with the setup as well.Capture9

Configure a Trusted application as “OutlookWebAccess” using the command “New-CsTrustedApplication -ApplicatioID OutlookWebAccess – TrustedApplicationPoolFQDN -<Exchange CAS FQDN> -Port <Vacant Port number>. You can use any port number as you prefer as long as it’s not being used by any other application.Capture10

Publish the configuration by running “Enable-CsTopologyCapture11

It’s all done now. Open up the OWA and see if you can see the presence next to your name. Capture12

If it’s not appearing still, have a look at the Exchange server event logs in CAS server and see if you have TLS related errors. The usual culprit of this integration to break are the certificate related issues.                

October 2014 update for Lync for Mac 2011 (Version 14.0.10)

Microsoft has released the new version of Lync for Mac 2011. And this one is October 2014 update with version 14.0.10. The update file can be downloaded from,http://www.microsoft.com/en-us/download/details.aspx?id=36517

Before installing this update, there are couple of Prerequisites that need to be satisfied. And those are,

  • To run install the update file, there have to be an older version of Lync for Mac client installed on the computer
  • The computer must be running on Mac OS X version 10.5 or later

The most impotent thing with this update is that, This enables the most wanted “View call history” on the client requirement and several other features and bug fixes mentioned below,

  • 3007886 Update enables users to view call history in Lync for Mac 2011
  • 3007885 Update for Lync for Mac 2011 enables users to store conversation history on an Exchange server
  • 3007884 Location is not displayed in Lync for Mac 2011 when users join a wireless network
  • 3007883 Error “One or more selected contacts cannot receive your calls” when you forward calls in Lync for Mac 2011
  • 3007881 Delegation relationship is broken after a delegate signs in to Lync for Mac 2011
  • 3007879 Computer shutdown is not processed when Lync for Mac 2011 is running
  • 3007878 Update implements media resiliency mode in Lync for Mac 2011
  • 3007877 Dial pad disappears when a user who is not enabled for EV joins a video conference or a video call in Lync for Mac 2011
  • 2909659 Update enables users to interact with a contact from the call history in Lync for Mac 2011

Installation of this update is fairly straight forward. Download the .dmg file, mount the file in to mac OS and install the application.

Lync Server 2013 September Update (5.0. 8308.815) is now available

Microsoft has released the September update for Lync Server 2013 (5.0. 8308.815) last week. Just like the ones that came before this update, there are several bug fixes included in to this update. List of the bug fixes that had been addressed are stated below;

  • Update for Central Management Server
    2910244 Description of the cumulative update 5.0.8308.577 for Lync Server 2013 Central Management Server: January 2014
  • Update for Backup Service
    2910243 Description of the cumulative update 5.0.8308.577 for Lync Server 2013 Backup Service: January 2014
  • Update for Standard or Enterprise Edition server (Front End Servers and Edge Servers)
    2987510 September 2014 Cumulative Update 5.0.8308.815 for Lync Server 2013 (Front End Server and Edge Server)
  • Update for Unified Communications Managed API 4.0, Core Runtime 64-bit
    2995717 September 2014 Cumulative Update 5.0.8308.815 for Lync Server 2013, Unified Communications Managed API 4.0 Runtime
  • Update for Web Components server
    2995718 September 2014 Cumulative Update 5.0.8308.815 for Lync Server 2013, web components server
  • Update for Core Components
    2987511 September 2014 Cumulative Update 5.0.8308.815 for Lync Server 2013 core components
  • Update for Call Park Service
    2881703 Description of the cumulative update 5.0.8308.556 for the Lync Server 2013, Call Park service: October 2013
  • Update for Conferencing Announcement
    2881701 Description of the cumulative update 5.0.8308.556 for Lync Server 2013, Conferencing Announcement: October 2013
  • Update for Conferencing Attendant
    2995716 September 2014 Cumulative Update 5.0.8308.815 for Lync Server 2013, Conferencing Attendant
  • Update for Mediation server
    2881699 Description of the cumulative update 5.0.8308.556 for Lync Server 2013, Mediation Server: October 2013
  • Update for Administrative Tools
    2967485 August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013, Administrative Tools
  • Update for Web Conferencing server
    2937314 August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013, Web Conferencing Server
  • Update for Unified Communications Managed API 3.0 Workflow APIs
    2835438 Description of the cumulative update 5.0.8308.420 for Lync Server 2013, UCMA 3.0 Workflow APIs: July 2013
  • Update for Conferencing server
    2835434 Description of the cumulative update 5.0.8308.420 for Lync Server 2013, Conferencing Server: July 2013
  • Update for Persistent Chat server
    2835433 Description of the cumulative update 5.0.8308.420 for Lync Server 2013, Persistent Chat: July 2013
  • Update for Windows Fabric
    2967486 August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013

Download the Update Installer from “http://www.microsoft.com/en-us/download/details.aspx?id=36820” URL and follow the instructions.

Keep in mind to update the Back End databases and run Windows Fabric update on the Front End servers as well as the Edge servers.

Optimizing VVX deployment with pre configured configuration files.

While ago I posted an article explaining how to use the configuration files to deploy and configure VVX devices over a provisioning server. If anyone who used the .cfg files on the provisioning server might realize that, there are lot of parameters to be configured so the the device deployment can be streamlined and make it more user friendly in the process.

In this article, I have shared a set of pre configured ans optimized .cfg files that can be used with any Lync server deployment. Granted that some of the parameters need to be changed according to the environment and I will explain what need to be changed and why.

There are 6 configurations files all together which address different segment of the device configuration.

Starting with Device.cfg. This configuration file set to configure following parameters in VVX device,

  • Set Device Base Profile as Lync
  • Change default administrator password (In version 5.1.1 Revision B, Device comes up with warning message if the Administrator password remains as default)
  • Enable Device update
  • Specify device update location
  • Time server configuration

The Feature.cfg file specify the common set of features on the device such as, Call lists, Miss call alerts, Contact Directory. In this file, the specified parameters are below,

  • Removed the “Corporate Directory” option on the device. Within “Directory”, the device will have “Lync Directory” option so that the contacts can be searched and called. In many cases, I have seen users get confused with two different set of directory options hence removing the “Corporate Directory” option
  • URI Dialling disabled. VVX generally have URI dialling enabled. When this feature is enabled, all inbound and outbound calls display as the full SIP URI (sip:+6123456789@contoso.com.au). Users who are used to have legacy PBX end points does not like this at all. They want to see just the number or the name without any other information

Sip-Interop.cfg is the most important one. This one controls the device registry intervals as well as the SIP Proxy server related parameters. In this configuration file, most of the parameters haven’t changed. But, the ones that were changed are below,

  • Device registration expiry interval. Default device registration expiry interval is 3600 seconds. If the devices is registered in an SBA, then if the SBA goes down, the devices still shows as signed in but, it actually be in an unknown condition till the registration expires. Have 3600 seconds is too much in that scenario. In this configuration file, the interval has changed to 120 seconds. This cannot be less than that. If it’s less, then users will experience the frequent device sign in and sign out.
  •   VOIP Server configuration. Here, the VOIP server interoperability is set to Lync 2010 and the transport method is set to TLS.
  • SDP early media disabled. I have noticed when this parameter is enabled, device sometimes does not provide a ringing tone to the end user. The dialled call will be blank till it get picks up.
  • Apply Digitmap Locally. Enabling this parameter will make the device to adhere to the Lync server normalization rules which are assigned to the user.

The Site.cfg file is configured to set daylight saving time in to the device. If the daylight saving is applicable, the start and stop times need to be configured,

  • SNTP address of the time Server
  • Daylight saving enable or disable. If enabled, start and stop times

Lync.cfg file configured to set BToE enabled. But, in version 5.1.1 Revision B, Polycom have set the BToE as disabled and given that the configuration file version is 5.2, this configuration file doesn’t really enable BToE on version 5.1.1 Revision B firmware. But, it can be used on Version 5.2.

The Cer.cfg is set to import the root CA in to the device. 90% of the devices that I have deployed were able to get the certificate without uploading manually. In case the device fail to pick up the certificate, copy and paste the hash file of the CA certificate in to the configuration parameter.

Finally, the Master configuration file 000000000000.cfg. All the above mentioned configuration files are specified in this master configuration file. When the device boots up, it will fetch the configuration mentioned on this files and get configured based on parameters which are configured on each sub configuration file.

The configuration files can be downloaded from, https://onedrive.live.com/redir?resid=6329AF91D1E5ADBC%21704

Follow my other article if you are new to the VVX setup. https://thamaraw.com/2014/04/02/configuring-the-provision-server-to-setup-polycom-vvx-devices-to-support-lync/

August 2014 Cumulative Update for Lync Phone Edition

Microsoft has released the August cumulative update for Lync Phone editions and unlike the ones that released before, this one has addressed some much anticipated features such as,

  • Update enables users who are not enabled for UC or EV to sign in to Lync Phone Edition telephone
  • The lock feature does not prevent users from making calls on a Lync Phone Edition telephone

After applying this update, Lync phone edition device can be signed in to a user who haven’t enabled fro Enterprise Voice. And getting one step closer to the PBX world by seeing the “Phone Lock” feature to not to allow dial outs while it’s locked. The emergency calls however will be able to dial out as long as it’s configured in location Policy. 

The update can be downloaded in http://support.microsoft.com/kb/2988181