List of possible Insights

• Potential Firewall Port Exhaustion Detected
  • Conditions:
    • No local network changes
    • One single audio stream (user did not suffer any type of disconnect)
    • Public facing / external NAT port changes during the call
      
• Audio stream was transferred between mobile and desktop versions of Teams
  
  
• More than 5  BSSIDs were used
  • More than 5 different (distinct) Wi-Fi AccessPoints

• TCP was used for Audio traffic
  • UDP is always recommended for performance, TCP is a fail back for unreliable connections or cases where UDP is blocked.
    
• Non-default Audio Ports Detected
  • Audio should use the local ports of 50000-50019.  Other ports could result in QoS policies failing to identify and prioritize the traffic.
    https://answers.microsoft.com/en-us/msteams/forum/all/microsoft-teams-ipports/b21fb0e0-1226-4bcf-b527-92c810bc7a87
    
    
• User Experienced Mid-Call Failure(s)
  • As reported by teams client and/or call records
    

• Mid-Call Network Disconnect/Reconnect
  • Windows OS detects a network change event during the call.
    
    

• Audio switched between wired and Wi-Fi In-Call
  • Teams Audio stream changes between Wi-FI and Wired connections during a call, and this change was not the result of a network change event
    
    

• Multiple Audio Segments were used
  • More than 1 distinct audio segment AND no signs of previously listed network or teams issues. (disconnect, midcall failure, etc)