Home
Microsoft

Specific Causes of Mid Call Failure update for Windows 7

HP has worked with Realtek to release a new set of drivers that help with some known failures we are seeing in tenants across the Skype for Business experience in Office 365.

If you have configurations of the following workstations and notebooks from HP in your environment, please see the links below to get the new firmware for your environment where PC's running Windows 7 and users using built-in audio devices for calls are possibly impacted with mid-call failures.

 

HP EliteBook 840 G2 Notebook PC

https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g2-notebook-pc/7343202

HP ZBook 15 G2 Mobile Workstation

https://support.hp.com/us-en/drivers/selfservice/hp-zbook-15-g2-mobile-workstation/6978814

HP EliteBook 820 G2 Notebook PC

https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-820-g2-notebook-pc/7343192

 HP EliteBook 1040 G2 Notebook PC

https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-folio-1040-g2-notebook-pc/7393377

 

You can use CQD online to monitor your deployment rates of the new drivers in your environment using the same methods available to you for identification of them. Starting with a CQD template  provided in the Skype Operations Framework (SOF) at https://www.skypeoperationsframework.com/Downloads?SelectedIDs=6_2_0_9 you can start to see what driver versions are in use when people are making and receiving audio calls.

Inside of the template, once imported, you can navigate down into "Devices - Microphone" and within find the report titled "Devices - Microphone Driver".

Mic-DriverReport.png

 

This is a table based report that renders all Drivers used by the Microphones on devices inyour environment that have been used during an audio stream.

The best way to use this report is then to edit it, and when editing, (1) sort the report by month; (2) add an inline filter by typing in the search box of the field "Second Capture Dev Driver" the word "Realtek", and then monitoring for the (3) count of calls being used per each (4) driver version you are trying to replace with the new one. See the picture below for an example:

MarkedUpReport.png

 

As you find drivers that are out of date, or as you believe users should be receiving new drivers on their machines, in the Search box for Second Capture Dev Driver, you can add a version string instead, such as "6.0.1.8108", and even work to add a dimension such as "Building Name" if you are controlling roll-out of the driver by site and will be using CQD to monitor the impact of the roll-out.

This should help you to find and identify drivers in use in your environment and as you deploy the updated drivers from HP, you can add filters for that version to see them in your environment.