Skype for Business Network Assessment (Requirement for Office 365)

-
The network assessment is very crucial with Office 365 voice implementations.

 This is valid if you run:
- PSTN Calling
- Cloud Connector Edition
- or any hybrid scenario

 I also recommend a choosing a partner how has the appropriated knowledge and can analyze your network entirely.

 Several tool and service are available measuring the network performance in the director the Office 365 datacenters. Either with or without the Express Route setup.
This should be part of the Microsoft Skype Operations Framework

 The most optimal tool is the IR Prognosis UC Assessor:
http://www.ir.com/skype-for-business-assessment



The Assessor is the right tool, for professional analysis and repots.

 -----------------------------------------------------------------------------------------------------

 A free tool is available too from Microsoft it was release September 2016

 https://www.microsoft.com/en-us/download/details.aspx?id=53885

Even if this tool also provide the rudimentary information, it is not simple in setup, neither it is capable providing a end-2-end monitoring.

You need a XML configuration file for you environment:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <startup>
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
    </startup>
    <appSettings>
      <add key="Relay.IP" value="13.107.8.20"/>

      <!-- At least one of the following two protocols must be configured   -->
      <!-- Configure only one if testing only one protocol                  -->
      <!-- If both are configured, UDP will be preferred if it is available -->
      <add key="Relay.UDPPort" value="3478"/>
      <add key="Relay.TCPPort" value="443"/>

      <!-- WMAFilePath configures the WMA file to be streamed -->
      <!-- WMAOutputFilePath contains the received audio -->
      <!-- If WMAOutputFilePath already exists,the existing file will be overwritten-->
      <add key="WMAFilePath" value="Tone.wma"/>
      <add key="WMAOutputFilePath" value="ReceivedAudioFile.wma"/>

      <add key="NumIterations" value="3"/>
      <add key="ResultsFilePath" value="results.tsv"/>
      <add key="Delimiter" value="  "/>
      <add key="IntervalInSeconds" value="5"/>    </appSettings>
</configuration>

The Analyzer : ResultsAnalyzer.exe results.tsv provides you with an output of test results.
As you can see it is not made for permanent analysis and it can be seen just as an indicator.

Result Output:

Skype for Business - Network Assessment Tool - Results Analyzer
Input file:           results.tsv
Total rows read:      10
Total rows skipped:   0
Total rows processed: 10
90th percentile values per metric:
Packet loss rate:     0.50 %
RTT latency:          70.5 ms
Jitter:               10.0 ms
Packet reorder ratio: 0.00 %
If this is a Skype for Business Client machine connecting to the Microsoft network Edge:
Packet loss rate:     PASSED
RTT latency:          PASSED
Jitter:               PASSED
Packet reorder ratio: PASSED
If this is a network Edge connecting to the Microsoft network Edge:
Packet loss rate:     PASSED
RTT latency:          FAILED
Jitter:               PASSED
Packet reorder ratio: PASSED



----------------------------------------------------
Other solution available:
EventZero and Nectar, which aren't yet available in Europe

Comments

Post a Comment

Popular posts from this blog

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar.
Read more