Lync 14.3.3 seems to work for me. Using the same version of Lync on a MacPro and an iMac, both running macOS Sierra DP 4. Version: 14.4.1 (14.4.1). To the internet, but not when connected to VPN or the office LAN.
Take Away: The communication problem between VPN clients and external clients result from a missing persistent route to the branch office’s subnet. The Access Edge server resides between the DMZ and the Perimeter network. The Access Edge has a gateway on the DMZ interface. The gateway is not configured on the Perimeter interface for traffic restriction purposes.
The Access Edge server is configured to communicate with the data center subnet. There is not a persistent route that forwards traffic to the VPN branch office subnet.
The Front End Server provides most Lync server functionality. Instant messaging (IM) provides text-based messages.
Both two-party and multiparty IM sessions are supported. A participant in a two-party IM conversation can add a third participant to the conversation at any time. When this happens, the Conversation window changes to support conferencing features. Lync clients send and receive instant messages using Instant Messaging Multipoint control unit (IMMCU). IMMCU is a Lync Front End service that provides instant message communication between Lync clients.
Peer-to-peer communication (and multi-party IM) is only possible when the Lync server and IMMCU is active and available. Lync clients use SIP and TLS TCP protocols to communicate. Lync server-to-server communication use SIP and MTLS protocols. External Lync clients communicate from a dynamic source port.
The external traffic is received on inbound port 443 on the public interface of the Lync Access Edge server. Access Edge forwards the packets to the Lync Front End server from its internal interface using SIP/MTLS:5061. Lync Front End receives then delivers packets through the LAN (and VPN) to the branch office client using SIP.MTLS:5061.
Lync client communication is often referred to as peer-to-peer. Technically, the two clients communicate in a one to one conversation, with the Instant Messaging multipoint control unit (IMMCU) in the middle. The IMMCU is a component of Front End Server. Placing the IMMCU in the required communication workflow allows call detail recording and other features that the Front End Server enables. Communication is from a dynamic source port on the client to the Front End Server port TLS/TCP/5061 (assuming the use of the recommended transport layer security). By design, peer-to-peer communication (as well as multi-party IM) is possible only when Lync Front End server and the IMMCU is active and available. ICE uses 2 protocols to determine the network path between Lync clients.
Session Traversal Utilities for NAT (STUN) reflects Lync client’s NAT IP and public IP. The process provides IP topology to promote network path candidates. Traversal Using Relay NAT (TURN) allocates media ports on the external AV edge interface. The key difference between STUN and TURN is that media travels directly between both endpoints when STUN is used, and media is proxied through the Access Edge server when TURN is used.
Candidates consist of an IP address and available UDP or TCP port. ICE considers all potential network paths as candidates. The ICE framework uses the following preferred hierarchy to promote candidates: 1. UPD direct occurs when ICE determines both Lync clients communicate using only host (or local candidate) IP addresses. UDP Direct assumes no firewall or Natting is used between Lync clients.
Clients that reside within the same broadcast domain or reside on the same subnet. Example may be two Lync clients used at an office or at the same hotel.
August 20, 2014 by Upon looking at visitor statistics for this blog one of the reoccurring trends is the amount of traffic to articles like after Microsoft releases a new round of Lync updates. It can sometimes be difficult to successfully navigate through the various updates which follow different release schedules which are sometimes bundled together with other Office releases, so hopefully this article can bring some additional clarity to the subject. This article will continually be updated to serve as both a source of new update information as well as a history of all past updates for both client and server platforms. Releases for will continue to be tracked in their original articles so this article will only cover the Microsoft-released server and client releases.
The ‘’ tag can be used as a quick route to all of these articles. Keeping this data up-to-date and accurate is an ongoing process feel free to leave comments regarding any errors or dead links. One thing to understand is that for some products Microsoft will continue to leave multiple previous versions online on their download sites, while others (namely Lync Phone Edition) are removed an only the latest cumulative releases are provided. Lync 2013 Server Updates Download As Microsoft only provides the latest releases for the server components then the following two links are always updated with the most recent information and can be used as a definitive source of the latest server updates. – Comprehensive KB article listing for all server components. – Direct link to Microsoft Download page for server packages Typically one does not need worry about the individual components as the LyncServerUpdateInstaller.exe is the ideal package to download and run on any servers.
This tool will locate and upgrade only the applicable components on each Lync server it is executed on locally. Installation At this point in the product cycle there is no real value in documenting the steps which have been already covered on various other websites for basic installations (like and ) to more complex articles covering Enterprise Edition pools with. The important points to understand are the following:.
Use the LyncServerUpdateInstaller referenced above to make life easy. Start inside-out and work from Front End servers toward Edge servers.
Do not forget to and the backend SQL database for each Enterprise Edition pool that is patched Component History For occasions when working with the individual packages is desired then the following table covers each cumulative update release with links to the original Knowledge Base articles for each new component. This matrix provides a visual aid to when and how often some of the various Lync components are updated as cumulative releases will typically not refresh every single server component. The official package version numbers will always be in the format of 5.0.8308.xxx but the 5.0 has been truncated fro the following table for spacing purposes. (would be lost without your website.!!) hope you can advise have a large deployment of Lync IM and Presence for all, and limited Telephony. Now at Lync 2007, shortly going to 2013 or Skype. Came across some CX700`s in our stores they have Version 3.5.6907.35(2.1) loaded they wont pull down latest version of software when connected, rebooted or put in the test/quarintine area is there an intermediate version of software I need to push before going to the latest version.4463 Many thanks Martin.
![Receiver Receiver](/uploads/1/2/5/4/125448262/466711478.jpg)
The idea that no previous version is downloadable is ridiculous. This suggests that new versions always have at least the same functionality as previous ones. Only an incredibly naive or arrogant Microsoft staffer would actually think this is the case (Maybe I just answered my own question!) Right now I have the “repeatedly asks for Calendar credentials” bug but no way to downgrade to the previous version. The fixes shown on Microsoft’s support KB are not applicable or don’t work. I need to move backwards from Lync 14.1.1 for Mac somehow. Hi Jeff, Sorry if this question is off topic, you seem to be very versed in Lync/SFB so hopefully you can assist. We currently have a full deployment of Lync Server 2013 on prem and all clients are running the full Lync client.
The majority of our users run Office 2013 Pro Plus. My question is can we update the clients to the SFB client or do we really need to purchase new licensing? It seems very odd to me that MS would roll out an Office Update that automatically upgrades the client to SFB which would then as a result put us out of compliance. Thank You for your time. Thanks for the great info. I needed to do Lync 2013 to SFB 2015 upgrade. One note about getting previous updates (CU’s) You can use your table to get individual KB’s from the MS Update Catalog at.
I needed to be at CU 8 to install on a temporary Lync 2013 Standard edition to migrate the CMS database to while we simultaneously performed a Lync to Skype upgrade and remote SQL DB migration from SQL 2012 cluster to SQL 2014 AG. I couldn’t find anywhere, all links led to the MS “LyncServerUpdateInstaller.exe” with the only option to install the latest.
Without your info I would have had to perform an update on my 3 front ends and 2 Edges first.