Quantcast
Channel: Lync 2013
Viewing all 145 articles
Browse latest View live

Skype & Lync Video Calling is working again with new Skype Build

$
0
0

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.

Skype v7.1.0.105 Download

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.

Skype v7.1.0.105 Version

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

Skype v7.1.0.105 Version About

Now Video Calling is available again

 

Example video call between Skype and Lync

Skype v7.1.0.105 Video Call

Codecs in use between Skype and Lync are

Audio : RT Audio
Video : H.264

Skype v7.1.0.105 Message Analyser

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


Cumulative Updates February 2015 for both Client & Server

$
0
0

Lync 2013

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

This update resolves the following issues:

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:

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

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

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

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

Cumulative Update for Lync 2013 Client : March 2015

$
0
0

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:

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.

Skype for Business @ Enterprise Connect

Lync 2013 for Windows Phone Updated

Viewing all 145 articles
Browse latest View live




Latest Images