Forum Discussion

Maluks's avatar
Maluks
Iron Contributor
Jun 02, 2017
Solved

Skype call issues - Bad device state

Hi all,

 

during past two weeks I have noticed increased number of incidents regards Skype for business calls. Users are complaining that suddenly the other end stops hearing them. 

 

We have Skype for business is running on premises, Skype client version 15.0.4927.1000

 

While digging in the Skype for business server reporting I find something like this:

Capture device: Headset Microphone (5- Microsoft LifeChat LX-6000) 
Capture device driver: Microsoft: 6.1.7601.18208 
Render device: Headset Earphone (5- Microsoft LifeChat LX-6000) 
Render device driver: Microsoft: 6.1.7601.18208 
Microphone glitch rate: 1 per 5 minutes 
Speaker glitch rate: 291 per 5 minutes 
Microphone timestamp drift: 0,01126528% 
Speaker timestamp drift: 0,00931025% 
Microphone timestamp error: 0,0355660505592823 ms 
Speaker timestamp error: 0,17209330201149 ms 
Echo event cause: 
Voice switch cause: Bad device state 
Echo percent send: 3,09% 
Echo percent microphone in: 11,04% 
Send signal level: -26 dBov 
Receive signal level: -21 dBov 
Send noise level: -62 dBov 
Receive nosie level: -57 dBov 
Echo return: 
Initial signal level RMS: 125,749099731445 
Capture device: Transmit (Plantronics D100-M) 
Capture device driver: Microsoft: 6.1.7601.18208 
Render device: Receive (Plantronics D100-M) 
Render device driver: Microsoft: 6.1.7601.18208 
Microphone glitch rate: 14 per 5 minutes 
Speaker glitch rate: 618 per 5 minutes 
Microphone timestamp drift: 0,00761747% 
Speaker timestamp drift: 0,00914335% 
Microphone timestamp error: 0,0629489421844482 ms 
Speaker timestamp error: 0,107901096343994 ms 
Echo event cause: 
Voice switch cause: Bad device state 
Echo percent send: 1,55% 
Echo percent microphone in: 1,55% 
Send signal level: -19 dBov 
Receive signal level: -21 dBov 
Send noise level: -70 dBov 
Receive nosie level: -57 dBov 
Echo return: 
Initial signal level RMS: -53,501651763916 

I notice that each time speaker and microphone are glitching which ends in the result 

Voice switch cause: Bad device state 

According to MS explanation

Voice switch cause:
Reason why a call had to be placed into half duplex mode in order to prevent echo. In half duplex mode, communication can travel in only one direction at a time, similar to the way users take turns when communicating with a walkie-talkie. Select one of the following:
[All]
None
Bad timestamp
Echo
DNLP (dynamic nonlinear processor)
Low complexity
Bad device state
Post-AEC echo (acoustic echo cancellation)

This explains why the user "drops out" from the call and others stop hearing him, but this not help to resolve the issue.

Each time users were using headsets certified for Skype for business (Plantronics SAVI W410, Microsoft LifeChat LX-6000), we tried updating Skype for business client, headset firmware if available, audio drivers, but the next day users return saying that problem continues to exist. 

 

Any ideas on how to resolve this? It would be easy to say to change the headset for the user, but when you buy certified device for $100+, then you expect things to work.

 

19 Replies

  • Sri Todi's avatar
    Sri Todi
    Brass Contributor
    Run MSInfo32.exe to save the results. Now compare the drivers installed, and update to latest drivers. If you still have issues, it would be best to check for any application(s) that create Interrupt Requests (IRQ) to monitor your Speech/Audio abilities. Any audio engine ( not Cortana), may also be causing something similar.
  • Shekhar Mahajan's avatar
    Shekhar Mahajan
    Copper Contributor

    Hi Arunas, we are experiencing exactly the same issue. Infact our SfB installation is brand new.

    We are using Plantronics 740-M (SfB compatible) and mid call, the user can only hear but cannot be heard by others. The only way out is to disconnect and reconnect from the call.

    Happens with Lync Peer-peer, conference and Lync-PSTN calls as well.

     

    We do not have any workaround and our SfB go-live is on hold as this is a show-stopper for us!

     

    Per Microsoft: Cause:

    Typically, only new hardware that uses a USB 3.0 interface is affected by this issue.

    This issue occurs because Windows 7 doesn't provide native USB 3.0 driver support. Intel provides the USB 3.0 driver stack. This causes timing issues in combination with the Skype for Business audio drivers

     

    Workaround

    To work around this issue, delete the Intel USB 3.0 drivers and use Windows USB 2.0 drivers instead. It is recommended that you engage with the computer OEM and Intel for the correct removal procedure and a further resolution, including obtaining updated USB 3.0 drivers.

    Currently Dell is working together with Intel to fix the issue. Lenovo and HP computers are also affected

     

    Unfortunately, the workaround recommended is impractical as it disables the Bluetooth as well and causes additional issues.

     

    The last we were told is to wait for Intel!

     

    In our opinion, this seems to be a major show stopper in SfB's adoption and enterprise readiness. If people cannot reliably and consistently talk without fearing their call will get interrupted mid-way, its a collaboration breakdown.

     

    Anyone else has ran and figured a workaround, please share

     

  • I doubt this is an issue with headsets as you mentioned, there're users complaining about it. Perhaps you can try to isolate by measuring the quality without headset, check on the network signal (WIFI), network utilization, recent updates, etc.?

      • Wan Zhung Bong's avatar
        Wan Zhung Bong
        Brass Contributor
        Normally I don't focus if user is connecting outside the organization, there are too many factors that we can't control. I'll use the Lync Precall Diagnostics Tool on user's PC to test the overall network performance before and during the call; it's useful to verify if it is causing by network utilization.

        On the other side, I'll uninstall the updates and monitor the situation too.
  • I've seen something like this earlyer with a non-microsoft conferencing product. The problem was the onboard audio hardware. We disabled the on board audio and the problem was solved. Maybe you can give it a try.

Resources