Important Update about Microsoft Office Live Meeting
If your company is using Office Live Meeting, we have some important news to share with you. We’ve been working hard to get Skype for Business and Skype Meeting Broadcast ready with new conversation and meeting features, so we’re inviting you to begin the migration from Live Meeting to Skype for Business. We encourage you to begin the move from Live Meeting to Skype for Business as quickly as possible, completing the migration no later than December 31, 2017, at which time the existing Live Meeting service will be fully shut down.Simplified port requirements for Skype for Business Online
Note: This article applies only to Office 365 Worldwide (including Government Community Cloud). For guidance on Office 365 operated by 21 Vianet, Office 365 Germany, Office 365 U.S. Government DoD or Office 365 U.S. Government GCC High click on the respective links. We are happy to announce that the 50,000-59,999 port range (UDP and TCP) is no longer a requirement for Skype for Business endpoints to communicate with Skype for Business Online. Earlier this year we talked about making simplification for network connectivity for Skype for Business Online (see blog article here) and we recently updated our guidance and removed the mentioned port range as a requirement: Office 365 URLs and IP address ranges So which ports are required for clients? All clients need to be able to directly connect to Skype for Business Online on the following destination ports: (the IP addresses and FQDNs can be found in the Office 365 URLs and IP address ranges) TCP 80, 443 UDP 3478, 3479, 3480, 3481 Optional: UDP/TCP 50,000-59,999 Is there a minimum client version required to benefit from the port changes? This change applies to all clients supported against Skype for Business Online. No clients are excluded and there are no specific minimum version required (although we always recommend to run the latest version). Why are these ports not required anymore? To answer this question, it is important to understand first how the 50,000-59,999 ports were used in the first place. (To understand all the details of their purpose, we recommend watching Troubleshoot media flows in Skype for Business across online, server and hybrid.) Let's have the following example: User A wants to call User B For the sake of the example, the direct connection between User A and User B is blocked (e.g. User and User B are at different branch offices behind firewalls), so the media traffic cannot go directly peer to peer and needs to flow via Skype for Business Online There are now the following possible media paths The 50,000-59,999 port range can be leveraged to include only a single Relay Server in the media path Without the 50,000-59,999 port range, the traffic needs to travel via two Relay Server. As you can see, closing the 50,000-59,999 port range will force the traffic to travel via an additional hop. While logic tells us that usually we want to avoid additional hops under all circumstances, the analysis on call quality data has shown us, that this additional hop does not significantly affect call quality - since both these Relay Servers are homed on the Microsoft Network, all traffic between the Relay Servers is sent over a highly reliable pipe designed for real-time communication. Our organization has these ports open, should we close them? Having the 50,000-59,999 port range open can still have (some) benefits when it comes to call setup times and under some circumstances on call quality. However in our data analysis and pilot deployments with some customers these differences did not show significance. If you have the ports open today, it makes sense to leave them open. What does this change for hybrid between Skype for Business Server and Skype for Business Online? This change only applies to users who are homed in Skype for Business Online. If you have an on-premises deployment of Skype for Business, the requirements for your Edge Server to communicate to Skype for Business Online remain unchanged (and also for any Federation scenarios including Skype for Business on-premises). The A/V Edge Server in your environment will need to be configured liked this. Please note that the Source Port is only relevant, if your firewall requires a source port to be specified (and a lot of firewalls do not require this setting): Source IP Destination IP Source Port Destination Port A/V Edge service interface Any UDP 3478 UDP 3478 A/V Edge service interface Any TCP 50,000-59,999 TCP 443 Any A/V Edge service interface Any UDP 3478 Any A/V Edge service interface Any TCP 443 Full requirements for Skype for Business Edge Server can be found here: Edge Server environmental requirements in Skype for Business Server 2015. Does this change anything for Cloud Connector Edition? No, the requirements for Cloud Connector Edition (see Plan for Skype for Business Cloud Connector Edition) remain unchanged. Call to Action Celebrate about the simplified port requirements Update any design templates you might have For future deployments, open only TCP 80, 443 and UDP 3478, 3479, 3480, 3481 per new guideline (and, optionally, 50,000-59,999 UDP and TCP) If you have any questions or comments, please let us know in the community This post is brought to you by Skype Academy. Visit Skype Academy for technical trainings and readiness around the Skype Operations Framework.
Headset Mutes Automatically (16.3.240)
Since installing 16.3.240 update a couple days ago every time I start a new voice conversation my headset (Plantronics W740-m) automatically mutes itself. As soon as it does this once then the headset will mute itself in every other application that includes audio. If I reboot I can use other applications as normal but as soon as I start Skype for Business and initiate another call it is right back to the same behavior. This is unbelievably annoying. Anyone have a fix or is this something Microsoft will need a code change to address?
Appear offline in Skype for Business
Hello Community, Ever wondered if we can appear Offline in Skype for Business? Well, then you are at the right place. To enable "Appear Offline" add the below registry (create it if not present) [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Lync] "EnableAppearOffline"=dword:00000001
