Inicio WebEx Always Using Microphone

WebEx, compatible with both Windows and macOS, utilizes microphone access to detect other devices branded under WebEx, through a feature known as Ultrasound Detection. This often leads the operating systems to flag that the microphone is active and in use by WebEx, which in turn can conflict with the functionality of 'MuteMe' microphone detection.


Our technology, intended to alert users when their microphone is active, relies on detection mechanisms inherent within the operating system. Since WebEx's ultrasound detection is interpreted as regular audio collection by the operating system, our technology will indicate that the microphone is in use whenever this feature is active. It remains indistinguishable to us whether the microphone is being used by WebEx for Ultrasound Detection or for a conference call, due to this feature's operational reliance on the microphone.


An effective solution would be to disable the Ultrasound Detection feature within WebEx. This is particularly recommended for users who primarily use WebEx and don’t require integration with other Cisco-branded products that utilize this feature for pairing. It is our belief that, for the convenience of users, this feature should be disabled by default upon installation of WebEx.

To disable the Ultrasound Device Detection, follow the steps below:

  1. Launch the WebEx application and navigate to settings/preferences by clicking on either your initials or profile picture at the top left corner of the WebEx application.

  2. In the settings/preferences window, find and click on 'devices' located either at the top or on the left.

  3. Uncheck the Use Ultrasound checkbox, and then either close the preferences window or click on the advanced settings link and uncheck "using microphone for device detection".

Important Note:

Disabling this feature means WebEx will not automatically pair with some of the WebEx / Cisco branded products found in conference rooms.


Last Updated: 10:45PM - PST - September 24, 2023

Please let us know via the chatbot if this article helped or didn't help resolve your issue.