Microsoft has announced yet another name for they Unified Communications flag ship formerly known as Live Communications Server (LCS), Office Communications Server (OCS) or Lync.

The new name follows a few years after the Aquisition of Skype.  Lync Server Product Teams already were operating under the Skype Business group for a long time making this name change probably an expected move from Microsoft.  It further alings and thightens the integration with Skype and enables Universal Communications accross the board for everyone whether its business or consumers.

The magic of Skype and the power of Lync are coming together: Introducing Skype for Business. It's the experience you love and the security you trust, together, all in one place.

Lync Server being renamed to : Skype for Business (unofficial Hashtag is #Skype4B)

View the video on Youtube
https://www.youtube.com/watch?v=LUetykHsxqQ

More info at Office Blog
http://blogs.office.com/2014/11/11/introducing-skype-business/

Microsoft is pleased to announce that public support  for Windows Server 2012 R2 Web Application Proxy as a reverse proxy for Lync Server 2013 is now available on Microsoft Unified Communications Open Interoperability Program (UCOIP) Infrastructure Qualified for Lync site, along with the accompanying documentation, “Configuring The Windows Server 2012 Web Application Proxy As A Reverse Proxy For Lync Server 2013”  published here:  http://www.microsoft.com/en-us/download/details.aspx?id=44940

The Microsoft Unified Communications Open Interoperability Program (UCOIP) has a published list of technologies and third party server reverse proxy products  that are approved for interoperability with Lync Server.  The test efforts performed by the Skype Experience Validation team successfully adds Windows Server 2012 R2 Web Application Proxy to that list. 

The Configuration Guide describes the requirements, deployment considerations and configuration setting of Web Application Proxy for use with Lync Server 2013.   

Lync Server 2013 Cumulative Update KB 2809243
http://www.microsoft.com/en-us/download/details.aspx?id=36820

More info:

October 2014 Cumulative Update 5.0.8308.831 for Lync Server 2013 (Front End Server and Edge Server)
http://support.microsoft.com/kb/3001616

The cumulative update resolves the following issues:

• 3003346 Cannot see presence status or send instant messages when OWA is integrated with Lync Server 2013 instant messaging
• 3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
• 3003350 Cannot search users by using a keyword that differs from Lync Server 2013 AD DS display name format in a Lync client
• 3003357 Error "400 Bad Request" when a user whose display name contains double quotation mark calls a PSTN number in Lync 2013

October 2014 Cumulative Update 5.0.8308.831 for Lync Server 2013 core components
http://support.microsoft.com/kb/3003358

The cumulative update resolves the following issue:

• 3008181 Centralized Logging Service Agent Service cannot start after you install a September 2014 update for Lync Server 2013

First of all you need to get familiarized on how the codec selection is made in Lync, you can find that in a previous post available on this site:

What audio codecs does Lync actually use
http://www.pro-lync.be/blogs/lync2013/archive/2014/03/13/flashback-from-lync-conference-what-audio-codecs-does-lync-actually-use.aspx

Scenario: Lync Desktop Client calls the Lyn Mobile Client

Looking at the SIP Traces with our beloved SNOOPER tool you can clearly see the initial INVITE which is sent from the desktop client to the mobile client.  Then investigating the SDP shows that the Primary Codec would be RTAudio Wideband (x-msrta/16000) and for the Second on the codec list is the Skype Wideband Codec (SILK/16000)

 in the 183 Session Progress you can see the Lync Mobile client sending its SDP, the  Skype Wideband Codec (SILK/16000) is first in the list.  And if you look closely there is no RTAudio codec but G.711 & G.722 are also an option

 Then in the RE-INVITE you can see that the Desktop Client actually send the SILK Codec as the First Codec in the list to acknolage the SILK Codec to the Mobile Client

 Same in the response from Mobile Client

 Now looking at Message Analyser ans Analysing the Media Stream, we see that the RTP Stream has a Payload type of 104 which corresponds to Skype Wideband Codec (SILK/16000)

So we now know that the Lync Mobile client already uses the Skype Codec by default, one may wonder if the Lync Desktop client will change the priority ordering for some of the Codecs.  if it happens you will read about it on our site.

Greetings,
Johan

Now Microsoft finally released the Lync 2 Skype direct connectivity and enabled the capability for the Skype Client and the Lync Client to have Video conversations.

Video calling between Skype and Lync available now
http://blogs.office.com/2014/12/05/video-calling-skype-lync-available-now/

My first Video test between Skype & Lync

First of all the new Skype client looks gorgeous, that you Microsoft.

Sending Chat Messages still works as expected, but you can clearly see there is next to the Cal button the Video button

Calling via Audio still works

Now lets add Video and Enable the Video

Now we have Video both ways, that's soo cool

I also love the Quality dialog, there looks to be a bug as it says not receiving video what we clearly can

Another awesome feature is, when switching between applications we still have the small video window

This is the Lync side view, the default window size

The Full Screen size

 Let's take a closer look how this works under the covers

Please also look at these other posts that give you more insight into the deep technical details

http://www.pro-lync.be/blogs/lync2013/archive/2014/03/13/flashback-from-lync-conference-what-audio-codecs-does-lync-actually-use.aspx
http://www.pro-lync.be/blogs/lync2013/archive/2014/12/04/lync-mobile-amp-lync-desktop-media-uses-skype-code.aspx

What puzzels me is that the Skype Client actually sends G.722 codec as a preferred codec and the SILK (Skype) codec only as second and RTAudio as third in the INVITE. Not sure if this is the intention but this is the way it works now.

Lync responds as expected they way Lync always does and also sends RTAudio as Preferred, then G.722 and SILK is not even in the list of Codecs, quite not what you would expect.

In the RE-INVITE RTAudio is still top in the list so both clients are confirming the codec

Now I do want to check this with Message Analyser, I need to be sure this is true.

And yes indeed the RTAudio codec is being used between the new Skype client and the Lync client.  You can also clearly see we are sending the media directly between the clients as the source and destination addresses are on the same subnet unlike what Skype and Lync were doing before.

Maybe my testing is skewed because I have both Lync and Skype client installed on all of my machines, maybe to investigate later if it changes anything. Or Microsoft decided to put the Lync Media stack into the Skype client.  I guess more details will follow.

Either way I am very pleased that we have these capabilities between Lync and Skype finally :)

Greetings,
Johan

This update resolves the following issues:

• KB 3017596 Sharing session stops in Lync 2013 when the display resolution of a shared monitor is changed
• KB 3004595 E.164 normalized telephone numbers are not displayed in Lync 2013 contact cards or the "Call" menu

Known Issues : After you install this update, you may experience the issues that are described in the following Microsoft Knowledge Base articles:

• KB 2898357 Screen readers cannot read aloud keystrokes during a Lync 2013 application or desktop sharing session in Windows
• KB 2932389 Persistent Chat file transfer fails between an external user and an internal user in Lync 2013

The update is available for download from the Microsoft Download Center.

32-bit Download the 32-bit Lync update package now.
64-bit Download the 64-bit Lync update package now.

To install this Lync 2013 update, make sure that the following updates are installed.

Based on my finding in the previous post where I found out that RTAudio and RTVideo are offered by the Skype Desktop Client, I decided to test Lync 2010 and Office Communicator 2007 R2 with the new Skype/Lync interop

Important : All of the Clients have been tested on a Lync 2013 Server environment only, potentially having Lync 2010 Server and Offic Communication Server 2007 R2 as the Server backend might give different results but you can always have a Mixed environment and include Lync 2013 to get the sane interop going.

Video calling between Skype and Lync first look & the details on a surprising Audio codec being used
http://www.pro-lync.be/blogs/lync2013/archive/2014/12/05/video-calling-between-skype-and-lync-first-look-amp-the-details-on-a-surprising-codec-being-used.aspx

Lync 2010 : The interop between Skype & Lync 2010 works

Lets look at the details,  Skype sends exactly the same INVITE as to the Lync 2013 client, this is offcourse expected.  Skype offers G722, SILK & RTAudio amongst other codecs.

Now the Lync 2010 Client responds with a limited set of Codecs.  Lync 2010 will never send SILK unless the codecs stack will be changed in a possible later CU.

The Voice Call was  established in RTAudio as this is the mommon codec and highest on the Prioiry list.  Now lets look at Video as the Lync 2013 client uses H.264 for Skype interop, the Lync 2010 Client does not support H.264. 

The Skype client sends both H.264 and RTVideo in the SDP of INVITE message

The Lync 2010 Client only responds with RTVideo as this is one of the few codecs Lync 2010 supports, Lync 2010 Client will not send H.263 as this codec is not support on either Lync 2013 and Skype.

 Looking at Network Monitor you can clearly see the RTVideo codec being used

The following information is sent in the QoE Report going to the Lync Server from Lync 2010 also confirming RTAudio & RTVideo

This interop has been tested with the following information coming from the SIP Trace (Version of Lync and Gateway)

Lync Server 2013 Server infrastructure
User-Agent: UCCAPI/4.0.7577.4445 OC/4.0.7577.4446 (Microsoft Lync 2010)
User-Agent:: RTCC/6.0.0.0 LyncSkypeGateway2/1.0.214.0

Office Communicator 2007 R2 : The interop between Skype & Office Communicator 2007 R2  works

Starting the OCS 2007 R2 client (oh boy this has been a while since I used it)

Doing an Audio call between OCS & Skype Works

Doing a Video call between OCS & Skype works

Lets look at the details : The Skype client sends G7.22, SILK and RTAudio (and other codecs)

The Communicator 2007 R2 responds with RTAudio (It does not support G.722 or SILK)

Network Monitor shows RTAudio being used

The Same way as always the Skype Client sends H.264 & RTVideo codecs in the INVITE

And sure the OCS client only responds with RTVideo

Network monitor shows RTVIdeo being used

Also in the QoE report we see the RTVideo codec in there

The testing is based on the following info:

Lync Server 2013 Server infrastructure
User-Agent: RTCC/6.0.0.0 LyncSkypeGateway2/1.0.215.0
User-Agent: UCCAPI/3.5.6907.236 OC/3.5.6907.268 (Microsoft Office Communicator 2007 R2)

Conclusion:

Great to see there is Backward compatibility for the Skype connectivity to Legacy Lync clients like Lync 2010 and Office Communicator. I do hope all the other Skype clients on mobile, mac and others also to have the same capabilities of communicating with legacy clients, if that is not the case it will be pretty ugly to explain to customers.

This is the fifth month in a row for Microsoft to release and update to Lync Server 2013.  The full list of updates are

Download : Lync Server 2013 Cumulative Update KB 2809243
http://www.microsoft.com/en-us/download/details.aspx?id=36820

Updates:

December 2014 Cumulative Update 5.0.8308.857 for Lync Server 2013 (Front End Server and Edge Server)
The cumulative update resolves the following issue:

• KB 3018165 Agents in a response group cannot receive a call in a Lync Server 2013-based Lync client
• KB 3018167 External user cannot sign in to a Lync client by using a SIP address of a new domain in a Lync Server 2013 environment

December 2014 Cumulative Update 5.0.8308.857 for Lync Server 2013 Unified Communications Managed API 4.0 Runtime 
The cumulative update that improves the reliability, stability, and performance of Microsoft Lync Server 2013 Unified Communications Managed API 4.0 Runtime. The version number of this update is 5.0.8308.857.

December 2014 Cumulative Update 5.0.8308.857 for Lync Server 2013 web components server
The cumulative update that improves the reliability, stability, and performance of Microsoft Lync Server 2013 web components server. The version number of this update is 5.0.8308.857.

December 2014 Cumulative Update 5.0.8308.857 for Lync Server 2013 core components
The cumulative update that improves the reliability, stability, and performance of Microsoft Lync Server 2013 core components. The version number of this update is 5.0.8308.857.

It turns out to be a busy  December, Microsoft released quite a few updates to some of the Lync clients including another Cumulative Update for the Server

Lync Desktop Client received a Cumulative Update
http://www.pro-lync.be/blogs/lync2013/archive/2014/12/10/december-9-2014-update-for-lync-2013-kb2910927.aspx

Lync Mobile Clients for both Windows Phone & Android received new features

Lync Mobile for Windows Phone updated Voip Settings
More info here : http://blogs.office.com/2014/12/10/lync-windows-phone-update-settings-voice-calls/

Lync Mobile for Android got an update for Anonymous Join and Contact Management
More info here : http://blogs.office.com/2014/12/11/new-android-lync-features-anonymous-join-passive-authentication-contact-management/

And Lync Room System has a Dialer and can now Schedule Meetings from within the interface
More info here : http://blogs.office.com/2014/12/15/lync-room-system-feature-updates/

Great to see so many improvements:)

Microsoft Message Analyzer is the successor of Microsoft Network Monitor which I used a lot to troubleshoot Lync.  Now Microsoft has released an updated tool that gives you more options and allows you to analyse multiple sources at once.  Now I find the Message Analyser has quite some interesting features and is easy to use.

Go grab it here: Microsoft Message Analyzer v1.1
http://www.microsoft.com/en-us/download/details.aspx?id=44226

Well by default Microsoft Message Analyser does translate some of the Lync and Skype codecs but it does not work for any of the SILK or H.264 Codecs.  Would we not want to make sure Message Analyser displayed the codec instead of just the Dynamic Codec Value like you can see in the screenshot below.

I decided to have a look into Message Analyser and how it works.  It uses some .opn files to translate a whole bunch of Network Traffic.  One of these files is called RTP.opn which is excactly what I need to make sure that Message Analyser translates all Lync & Skype codecs.

To use this yourself you will have to download this file from this location:
Microsoft Message Analyser Custom RTP config file (RTP.opn)
https://gallery.technet.microsoft.com/Message-Analyser-Custom-bedbc034

You must replace the file in this specific path in order to make it work:
C:\Users\%username%\AppData\Local\Microsoft\MessageAnalyzer\OPNAndConfiguration\OPNs\Public

After this change you will have to start or restart Microsoft Message Analyser and do another trace.

Codecs included that are part of the Dynamic Range:

Codec 97   : "Audio, Codec: RED, ClockRate: 8000, P-Times: 20,40,60, Channels: 1";
Codec 103 : "Audio, Codec: SILK, ClockRate: 8000, P-Times: 20,40,60, Channels: 1";
Codec 104 : "Audio, Codec: SILK, ClockRate: 16000, P-Times: 20,40,60, Channels: 1";
Codec 111 : "Audio, Codec: Siren, ClockRate: 16000, P-Times: 20,40,60,100,200, Channels: 1";
Codec 112 : "Audio, Codec: G.722.1, ClockRate: 16000, P-Times: 20,40,60, Channels: 1";
Codec 114 : "Audio, Codec: RT Audio, ClockRate: 16000, P-Times: 20,40,60, Channels: 1";
Codec 115 : "Audio, Codec: RT Audio, ClockRate: 8000, P-Times: 20,40,60, Channels: 1";
Codec 116 : "Audio, Codec: G.726, ClockRate: 8000, P-Times: 20,40,60, Channels: 1";
Codec 117 : "Audio, Codec: G.722, ClockRate: 8000, P-Times: 20,40,60, Channels: 2";
Codec 118 : "Audio, Codec: Confort Noise, ClockRate: 16000, Channels: 1";
Codec 121 : "Video, Codec: RT Video, ClockRate: 90000";
Codec 122 : "Video, Codec: H.264, ClockRate: 90000";
Codec 123 : "Video, Codec: H.264 FEC, ClockRate: 90000";

This example shows a Lync Mobile client on Windows Mobile using SKYPE to talk to a Lync desktop client

This example shows a Skype client talking RT Audio and H.264 Video codecs to Lync

The one thing I could not figure out yet was to add Desktop Sharing to the RTP config, but Desktop Sharing uses TCP instead of UDP and the translation for RTP is not triggered by TCP right now.

Happy testing

Microsoft had temporarily disabled Skype & Lync video calling during the Christmas holidays.  Luckily Microsoft has released a new Skype version that enables this capability once again.

How to get this version?

Go to the Skype.com website and download a new version.

You will most likely get this version : 7.1.0.105 (at the time of writing)
If you get a different version then you should try to download once again with another browser to get another version.

Install Skype and make sure you are using the correct version.

Now Video Calling is available again

Example video call between Skype and Lync

Codecs in use between Skype and Lync are

Audio : RT Audio
Video : H.264

Happy testing.

More info here:
http://www.pro-lync.be/blogs/lync2013/archive/2014/12/05/video-calling-between-skype-and-lync-first-look-amp-the-details-on-a-surprising-codec-being-used.aspx

http://www.pro-lync.be/blogs/lync2013/archive/2014/12/11/skype-amp-lync-interop-also-works-with-legacy-lync-clients.aspx

http://www.pro-lync.be/blogs/lync2013/archive/2015/01/15/howto-display-all-lync-amp-skype-codecs-in-microsoft-message-analyser.aspx

Lync 2013

February 10, 2015 update for Lync 2013 (KB2920744)
http://support.microsoft.com/kb/2920744

This update resolves the following issues:

• KB 3032399 Update improves users’ ability to select partial instant messages from conversation history windows in Lync 2013
• KB 3032396 Incorrect conversation window opens when you double-click a contact in Lync 2013

Lync Server 2013

Updates for Lync Server 2013
http://support.microsoft.com/kb/2809243

February 2015 Cumulative Update 5.0.8308.871 for Lync Server 2013 (Front End Server and Edge Server) resolves the following issues:

• KB 3034784 Lync Server 2013-based client crashes or disconnects from a meeting when an anonymous user ends audio lines of a call
• KB 3034783 LS Storage Service event 32054 after you enable Lync 2013 Mobility in an Exchange 2010 environment
• KB 3034782 Non-clickable hyperlinks setting does not work in a conversation with external users in a Lync Server 2013-based client
• KB 3034779 Lync Monitoring report does not show names under "Sites and Subnet" column
• KB 3034778 Rtcsrv.exe crashes when invalid address book normalization rules are defined in Lync Server 2013

February 2015 Cumulative Update 5.0.8308.871 for Lync Server 2013 Core Management Server resolves the following issues

• Location monitoring report does not show regions and site names in a Lync Server 2013 environment

February 2015 Cumulative Update 5.0.8308.871 for Lync Server 2013 web components server resolves the following issues

• Lync Server 2013 Control Panel crashes when you access the Route tab under the Voice Routing tab

February 2015 Cumulative Update 5.0.8308.871 for Lync Server 2013 core components  resolves the following issues

• KB 3034776 Memory leak occurs in w3wp.exe, MediationServerSvc.exe, and sqlservr.exe in a Lync Server 2013 environment
• KB 3034781 Central Management Store file replication is slow or incomplete in a Lync Server 2013 environment

February 2015 Cumulative Update 5.0.8308.871 for Lync Server 2013 Response Group Service resolves the following issues

• Lync Server 2013-based RGS agent receives a toast for a second waiting call after agent accepts the first waiting call

Once again Microsoft updates Lync 2013, it has not been longer than a month before the last update came out.

This update KB2956174 resolves a list of issues. The version number of this update is 15.0.4701.1000. Check out the Known issues that may occur after you install this update and the prerequisites before you install the update

This update resolves the following issues:

• KB 3040496 Lync 2013 does not show who changes content in a shared whiteboard in an online meeting
  Note After you apply this update, you can see who changes content by resting the mouse pointer over the changed content
• KB 3040495 Cannot scroll down text that is more than two pages in whiteboard in Lync 2013
  When this issue occurs, you can only see text in two pages in whiteboard in Microsoft Lync 2013. 
  Note You cannot scroll down the text by using either a keyboard or a mouse scroll button
• KB 3040494 "We couldn't connect to the presentation" error occurs when an anonymous user shares a desktop in a meeting in Lync 2013
  This issue occurs when a user joins a meeting that is created in a non-federated organization from the network of the user's organization. The user's organization does not have a direct IP/TCP connection route to the Edge infrastructure of the non-federated organization.
  When this issue occurs, the user receives the following error message: We couldn't connect to the presentation because of network issues.Additionally, the user cannot start audio or video in a meeting in Lync 2013.
  This issue occurs because Lync 2013 does not use a configured HTTP proxy server to connect to the Edge infrastructure of the non-federated organization. Instead, Lync 2013 tries to directly connect to the Edge infrastructure incorrectly
• KB 3040493 Lync Online users cannot search contacts in Lync 2013 in an environment that has a proxy server deployed
  This issue occurs because Microsoft Lync 2013 sets a proxy server but does not set the proxy exception list for the Microsoft Office Online Sign-in Assistant service (MSOIDSVC). Therefore, MSOIDSVC tries to connect an Active Directory Federation Services (ADFS) server through the proxy server. However, the proxy server cannot connect an ADFS server through an external Internet network.
• KB 3040491 Meeting does not start if you click a meeting URL in a meeting invitation email message when Lync 2013 is signing in
  Note When this issue occurs, a meeting will not start even after Microsoft Lync 2013 has finished signing in
• KB 3040489 Text labels for toll and toll-free numbers disappear in a meeting invitation when you create the meeting in Lync 2013
  When this issue occurs, a toll and toll-free number are displayed as follows:
  
  Join by phone:
   +<123456>
   +<654321>
  
  Note When you create a meeting in Microsoft Lync 2010, the toll and toll-free numbers will be displayed as follows:
  Toll-free number: +<123456>
  Toll number: +<654321>
• KB 3040488 Outlook 2010 freezes, and then crashes when it runs together with Lync 2013
  This issue occurs because, when ucaddin.dll tries to repair meetings, it encounters a problem
• KB 3040487 "We found a problem with you Lync Meeting. Please leave Lync client running for 15 mins" error occurs in Lync 2013
  This issue may occur when you use a date format based on locales instead of the "MM/DD/YY" format, or when your computer just comes back from sleep.Note This update will remove the error message that is mentioned in title.

After you install this update, you may experience the issues that are described in the following Microsoft Knowledge Base articles:

• KB 2898357 Screen readers cannot read aloud keystrokes during a Lync 2013 application or desktop sharing session in Windows
  Consider the following scenario:
  • You install an update for Microsoft Lync 2013 that is dated October 8, 2013 on a computer that is running Windows.
  • You are running screen reader software on the computer.
  • You start an application or desktop sharing session by using Lync 2013.
  In this scenario, the screen reader software cannot read aloud keystrokes that are from the local user’s keyboard in the session.
  Note When this issue occurs, the screen reader will work if you restart it. This issue occurs because of a limitation in Windows.
  To work around this issue, you must set the DWORD registry value of DisableMouseConflictReduction to 1 in the following registry path:
  HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Lync
• KB 2932389 Persistent Chat file transfer fails between an external user and an internal user in Lync 2013
  Assume that a user (user A) installs Microsoft Office 2013 Service Pack 1 (SP1) on a Lync 2013 client. Then, user A tries to send a file to another user (user B) in a Persistent Chat room by using the client. In this situation, user A may encounter the following issues:
  • If user A is an external user and user B is an internal user, user A cannot send the file. Additionally, user A will receive error ID 70.
  • If user A is an internal user and user B is an external user, user A cannot send the file. Additionally, user A will receive the following error message:
    error in transfer
  This issue occurs because the Persistent Chat server does not provide the external web services URL
  To work around this issue, you must publish an A record to point to the public IP address of the router on the external Domain Name System (DNS) side. The router port must be forwarded to the external IP of Threat Management Gateway.
  Note This workaround does not apply to all environments. For example, the internal DNS name may not be publishable in external DNS in some environments.

Next week is going to be exiting as Microsoft will do some announcements on Skype for Business :)

Follow on Twitter
https://twitter.com/SkypeBusiness

More info on Facebook
https://www.facebook.com/video.php?v=10152821623341884&set=vb.123768126883&type=2&theater

Microsoft Updated the Lync 2013 Mobile client for Windows Phone to version : 5.9.1359.0

This version only includes bug fixes

What’s new in version 5.9:
- Bug fixes

More info:
https://www.windowsphone.com/en-us/store/app/lync-2013/d85d8a57-0f61-4ff3-a0f4-444e131d8491