BRK2004 - Learn from large scale Skype for Business Voice deployments
It was clear, from the packed room at the “Learn from large scale Skype for Business Enterprise Voice deployments” session, that a lot of Microsoft Ignite attendees were interested in catching a glimpse into how different companies were tackling their Skype for Business Enterprise Voice deployments. Francois then discussed how Microsoft turned Skype for Business into a proven, mature, complete and comprehensive PBX replacement solution: “I am confident that we can succeed at any PBX replacement project; PBX replacement projects are complex and can be difficult, but I have yet to encounter a solution where the combination of Microsoft and our ecosystem was not able to meet the customer’s needs”. In support of that claim, Francois asked four companies to describe their Large Enterprise Voice Deployments. It was clear when these companies shared the details, that they were all convinced they had made the right choice with Skype for Business Server. Still, these customers presented complex use cases, much beyond the basic and simple “white collar” use case; these deployments were far from straightforward. Tremendous work and dedication were all a part of each of these deployments, and each was unique in its own way.Updates to Call Quality Dashboard (Oct 7th 2017) - Call Setup Failure Reason change
Hi, We have a made an update to the Call Quality Dashboard (CQD) https://cqd.lync.com affecting how calls that fail to establish are classified that may impact the data you see in CQD. Details: Calls are classified using the Call Setup Failure Reason dimension into the following categories (refer for here more details about dimension and measures exposed in CQD): Missing FW Deep Packet Inspection Exemption Rule - indicates that network equipment along the path likely prevented the media path from being established due to deep packet inspection rules. This may be due to proxy or firewall rules not being correctly configured. Missing FW IP Block Exemption Rule - indicates that network equipment along the path likely prevented the media path from being established to the Office 365 network. This may be due to proxy or firewall rules not being correctly configured to allow access to IP addresses and ports used for Skype for Business traffic. Other – indicates the media path for the call could not be established but the root cause could not be classified. Not Media Failure - indicates no issue was detected with the establishment of the media path. There was a specific type of failure caused by firewall or other equipment blocking access to specific ports that was being classified as Other. Starting with data on 11/6, we are now classifying these failures correctly as Missing FW IP Block Exemption Rule. Over the next few weeks we will be reprocessing data from before 11/6 using this same classification. So what does this mean for you: If you see a spike on 11/6 or beyond in these Missing FW IP Block Exemption Rule failures compared to previous days, it may indicate indicate that you have calls failing due to not having the complete IP address and port list open. Once the reprocessing is complete (target is 11/28) data before and after 11/6 will use the same classification. If you have questions, comments or concerns, please reply to this post. /william
