Real-Time Call Health now available in calls and meetings

By -

 Teams client is now making it much easier for troubleshooting call quality in real time. Microsoft have added a Call Health option menu to our ellipses (...) menu.

Once in a call and we click on this menu, we will see details for the following:

  • Network
  • Audio
  • Video
  • Screen Sharing
For each of these there is a sub menu under View more xxxx data > and in here we see a breakdown of each area. Depending on the type of call, you will see some data not shown (no Screen Sharing details if you are not sharing anything!!)



Network:

Teams Send Limit: This is the max limit Teams can send based on current network path conditions and utilisation. This is NOT your SIP speed limit.

Teams Receive Limit: This is the max limit Teams can receive based on current network path conditions and utilisation. This is NOT your SIP speed limit.

Round Trip Time: Response time between your system and Teams server. Lower is better.

Received Packet Loss: The results of a bad network. Lower is better.

Audio:


Sent Bitrate: The throughput of audio sent in kbps.

Sent Packets: The number of packets sent.

Round Trip Time: Response time between your system and Teams server. Lower is better.

Sent Codec: Audio processing of sent data.

Received Jitter: Distortion in audio. Lower is better.

Received Packet Loss: The results of a bad network. Lower is better.

Received Packets: The number of packets received.

Received Codec: Audio processing of received data.


Video:

Sent Frame Rate: Number of video frames sent. Higher is better.
 
Sent Width: Video resolution sent. Higher is better.

Sent Height: Video resolution sent. Higher is better.

Sent Bitrate: Bitrate depends on your network speed. Higher is better.

Round Trip Time: Response time between your system and Teams server. Lower is better.

Sent Packets: The number of packets sent.

Sent Codec: Codec used for encoding your video camera feed.

Video Processing: How you're converting camera footage into a digital signal.

Screen Sharing:





Sent Frame Rate: Number of video frames sent. Higher is better.
 
Sent Width: Video resolution sent. Higher is better.

Sent Height: Video resolution sent. Higher is better.

Sent Bitrate: Bitrate depends on your network speed. Higher is better.

Round Trip Time: Response time between your system and Teams server. Lower is better.

Sent Packets: The number of packets sent.

Sent Codec: Codec used for encoding your video camera feed.

Screen Share Send Processing: Indicates whether CPU or GPU is used for Encoding.

Received Frame Rate: Number of video frames received. Higher is better.

Received Width: Video resolution sent. Higher is better.

Received Height: Video resolution sent. Higher is better.

Received Bitrate: Bitrate depends on your network speed. Higher is better.

Received Packet Loss: The results of a bad network. Lower is better.

Received Packets: The number of packets received.

Received Codec: Screen sharing processing of received data.

Screen Share Received Processing: Indicates whether CPU or GPU is used for Encoding.


So with most metrics updated every 15 seconds, you can now get a much better picture of whats going on for the client in realtime. A very valuable troubleshooting tool, especially with people working from home on differing network types and speeds and others in the household possibly using network at the same time for gaming or streaming. The participant can see in real time if it is their network connection that is the problem.







Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without this response there is an issue,
Read more