VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Browser microphone and audio-device troubleshooting

Isolate permissions, capture, transport and playback before changing the PBX.

Reviewed 2026-10-30WebRTC standards; browser and server behavior must be checked by versionIntermediateDocumentation based · not lab tested

Confirm that capture starts

A calling page needs an appropriate secure context and user permission to capture a microphone. Browser permission, operating-system privacy controls and the selected physical device can each prevent capture. A headset that works in another application does not establish that this website has access to it. Check the site's permission state, the application's selected input and whether the captured track is live and enabled. Record the browser's error name rather than reducing every failure to no audio. Avoid repeatedly prompting the user without explaining which permission or device needs attention.

Follow sound in each direction

If local capture shows activity but the remote party hears nothing, inspect outgoing media counters and the remote receive path. If incoming packets arrive but the local user hears silence, inspect output selection, volume, mute and playback restrictions. A muted microphone and a muted speaker are different failures. For Bluetooth equipment, operating-system profile changes can alter input availability and sound quality. Repeat with a known wired device to isolate that boundary, then return to the intended headset. Do not conclude that the SIP codec changed merely from a change in local playback quality.

Reproduce device transitions

Test unplug/replug, switching input during a call, browser reload and operating-system sleep. Confirm that the application handles a removed device and offers a usable replacement. Device labels or identifiers can behave differently before permission is granted and across browser sessions. Keep support notes limited to the relevant device names, permission state and counters. Do not collect microphone recordings by default. Once capture and playback are established, move to WebRTC transport troubleshooting with a clear statement of which direction fails.

Treat V52 enumeration and browser permission separately

The Studio V52 reference keeps USB enumeration, operating-system permission, browser or meeting-client selection and far-end receipt as separate evidence.

Keep V72 enumeration, permission and receipt distinct

The Studio V72 reference separates USB enumeration, OS or browser permission, meeting-client selection and far-end receipt.

Treat JsSIP getUserMedia failure as its own boundary

The JsSIP diagnostic keeps permission, SDP, ICE, RTP and playback separate.

Keep Zoom Phone local device and call-media evidence separate

The Zoom Workplace diagnostic distinguishes operating-system defaults, app selections, attachment, *8378 playback, external call media and remote audibility.

Keep NextivaONE microphone, speaker and ringer independent

The NextivaONE diagnostic distinguishes permissions, app selection, local tests and two-way call media.

Separate Teams mic, speaker and secondary ringer

The Teams Phone diagnostic distinguishes operating-system defaults, Teams selections, test-call playback and live-call media.

Separate Dialpad microphone, call output and ringtone output

The Dialpad app diagnostic distinguishes operating-system defaults, app choices, local tests and call-specific media.

Separate 8x8 microphone processing from live media

The 8x8 Work diagnostic distinguishes device choice, permission, noise suppression, gain control, packet flow and perceived audio.

Separate Vonage app audio choices from live media

The VBC diagnostic distinguishes operating-system and app devices, permission, echo playback, packet flow and perceived audio.

Separate Aircall device tests from live call media

The Aircall diagnostic distinguishes browser permission, operating-system and app devices, test playback, packet flow and what each party heard.

Watch the explanation

Jabra Evolve 65: re-pair a Link 370 USB adapterHeadset Advisor · Version-specific

This walkthrough uses Jabra Direct to discover a headset and pair it with a USB Bluetooth adapter. It helps separate two tasks that are often confused: pairing the headset to the adapter and choosing that adapter as the calling application’s audio device.

Read applicability and editorial notes →
Watch this video here

Shows Evolve 65 and also discusses Evolve2 65. These are different product generations; bundled adapter models and Jabra Direct screens can differ. Review used the available transcript and primary references; audio and screen readability remain unverified.

Open on YouTube ↗

The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.

Jabra Evolve2 40: connect USB audio and choose the right deviceJabra · Version-specific

The manufacturer’s captions walk through USB connection, selecting recording and playback devices, and choosing the headset in a softphone. This is a useful starting point when a wired headset is connected but calls still use the laptop microphone or speakers.

Read applicability and editorial notes →
Watch this video here

USB-A and USB-C Evolve2 40 variants; software and Teams-specific controls vary by edition. Review used the available transcript and primary references; audio and screen readability remain unverified.

Open on YouTube ↗

The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.

Explore all 12 related videos →

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · WebRTC standards; browser and server behavior must be checked by version

WebRTC troubleshooting by connection stage

Locate failures in capture, signaling, ICE, DTLS or playback using an ordered evidence trail.

Read guide →
Device reference · HP product, specification, user, administrator, room-planning and current release-note records reviewed October 21, 2026. Published camera, pickup, platform, port and certification statements are manufacturer records, not room acceptance. Exact regional SKU, package, host, meeting client, tenant, policy, cable, adapter, peripheral support, firmware path, availability, price, warranty and support status require confirmation. No Studio V52, host, room, mount, cable, adapter, display, network, account, tenant, application, camera, microphone, speaker, firmware, update, meeting, media stream or call was inspected or tested

HP Poly Studio V52 USB video bar

Evaluate Studio V52 as a medium-room USB camera, microphone and speaker peripheral while preserving host, meeting-app, port, management, room and staged-firmware boundaries.

USB video bar for medium rooms
HP maintained a live product page, specifications, current documentation and release notes at review. Regional orderability, package, firmware entitlement, warranty and remaining support were not established.

Read guide →
Diagnostic · HP product, specification, user, administrator, room-planning and current release-note records reviewed October 21, 2026. Published camera, pickup, platform, port and certification statements are manufacturer records, not room acceptance. Exact regional SKU, package, host, meeting client, tenant, policy, cable, adapter, peripheral support, firmware path, availability, price, warranty and support status require confirmation. No Studio V52, host, room, mount, cable, adapter, display, network, account, tenant, application, camera, microphone, speaker, firmware, update, meeting, media stream or call was inspected or tested

Poly Studio V52 camera, audio or firmware update fails

Separate V52 USB enumeration and host selection from room acoustics, management connectivity, version-specific firmware sequencing and meeting-media behavior.

Read guide →
Device reference · HP product, specification, hardware, administrator, privacy, room-planning and release-note records reviewed October 21, 2026. Published camera, pickup, platform, port, peripheral and certification statements are manufacturer records, not room acceptance. Exact regional SKU, package, host, client, tenant, cable, switch, injector, peripheral support, firmware path, availability, price, warranty and support status require confirmation. No Studio V72, host, room, mount, cable, switch, injector, display, network, account, tenant, application, camera, microphone, speaker, firmware, update, meeting, media stream or call was inspected or tested

HP Poly Studio V72 USB video bar

Evaluate Studio V72 as a large-room USB camera, microphone and speaker peripheral while preserving host, port, LLN-camera, expansion-audio, privacy, room and firmware boundaries.

Premium USB video bar for large rooms
HP maintained a live product page, specifications, current documentation and VideoOS Lite release notes at review. Regional orderability, package, firmware entitlement, warranty and remaining support were not established.

Read guide →
Diagnostic · HP product, specification, hardware, administrator, privacy, room-planning and release-note records reviewed October 21, 2026. Published camera, pickup, platform, port, peripheral and certification statements are manufacturer records, not room acceptance. Exact regional SKU, package, host, client, tenant, cable, switch, injector, peripheral support, firmware path, availability, price, warranty and support status require confirmation. No Studio V72, host, room, mount, cable, switch, injector, display, network, account, tenant, application, camera, microphone, speaker, firmware, update, meeting, media stream or call was inspected or tested

Poly Studio V72 camera, audio, peripheral or update fails

Separate V72 USB enumeration and application selection from unsupported ports, LLN or expansion topology, privacy state, room behavior, management reachability and version-specific updates.

Read guide →
Client integration guide · Current JsSIP project, documentation, UA and RTCSession APIs, cause catalogue, repository, changelog and published npm package reviewed October 23, 2026; the repository changelog contains a 3.13.9 heading while the npm latest tag remains 3.13.8 and the public versioned examples remain under 3.10.x, so repository, documentation and installed-package state are not treated as interchangeable; exact application, package lock, bundle, browser, origin, credential delivery, SIP service, PBX policy, WebSocket, registration, page lifecycle, permission, device, SDP, ICE, RTP and playback remain deployment specific; no package, dependency tree, application, browser, account, credential, socket, registration, SIP message, permission, device, media element, peer connection, packet, media stream or call was inspected or tested

JsSIP browser calling: package, transport, registration and media evidence

Operate a JsSIP integration without confusing repository, published package, WebSocket state, registration, RTCSession, browser permission, peer connection or audible media.

Read guide →
Troubleshooting · Current JsSIP project, documentation, UA and RTCSession APIs, cause catalogue, repository, changelog and published npm package reviewed October 23, 2026; the repository changelog contains a 3.13.9 heading while the npm latest tag remains 3.13.8 and the public versioned examples remain under 3.10.x, so repository, documentation and installed-package state are not treated as interchangeable; exact application, package lock, bundle, browser, origin, credential delivery, SIP service, PBX policy, WebSocket, registration, page lifecycle, permission, device, SDP, ICE, RTP and playback remain deployment specific; no package, dependency tree, application, browser, account, credential, socket, registration, SIP message, permission, device, media element, peer connection, packet, media stream or call was inspected or tested

JsSIP connects or registers but calls or audio fail

Trace one JsSIP failure from exact package and page lifecycle through WSS, REGISTER, INVITE, RTCSession, permission, SDP, ICE, RTP and media playback.

Read guide →
Client research · Current Zoom Phone user, Zoom Workplace phone-settings, desktop and mobile requirements, Workplace release notes, Phone FAQ, phone-statistics, problem-report, firewall, network-tool, sign-in and device-audio records were reviewed October 28, 2026. The release notes then listed Zoom Workplace 7.2.5 for October 30 with every platform build marked TBD; that future entry is not represented as released, downloadable, installed or generally available. Exact account, license, extension, direct number, role, app path, platform, installed build, release track, store approval, sign-in method, Phone-tab visibility, call handling, location, emergency address, notification, network, proxy, firewall, signaling, media, device selection, call result, analytics visibility and support handling remain tenant- and deployment-specific. No Zoom account, license, app, browser, device, credential, number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, problem report or support response was inspected or tested

Zoom Workplace for Zoom Phone: client, version and call-evidence boundaries

Evaluate Zoom Workplace desktop, mobile and web calling by exact Phone entitlement, app path, released build, identity, emergency location, network, device and media evidence.

Read guide →
Troubleshooting · Current Zoom Phone user, Zoom Workplace phone-settings, desktop and mobile requirements, Workplace release notes, Phone FAQ, phone-statistics, problem-report, firewall, network-tool, sign-in and device-audio records were reviewed October 28, 2026. The release notes then listed Zoom Workplace 7.2.5 for October 30 with every platform build marked TBD; that future entry is not represented as released, downloadable, installed or generally available. Exact account, license, extension, direct number, role, app path, platform, installed build, release track, store approval, sign-in method, Phone-tab visibility, call handling, location, emergency address, notification, network, proxy, firewall, signaling, media, device selection, call result, analytics visibility and support handling remain tenant- and deployment-specific. No Zoom account, license, app, browser, device, credential, number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, problem report or support response was inspected or tested

Zoom Workplace Phone tab is missing, calls fail or audio is wrong

Find the first failed boundary across Zoom Phone entitlement, app path and build, sign-in, Phone visibility, call handling, network, local devices, signaling and media.

Read guide →
Client research · Current first-party NextivaONE landing, setup, troubleshooting, calling, mobile, audio-device, log, feedback, login, update and network records plus separate NEXT release-note and desktop-app records were reviewed October 29, 2026. The inspected support material continued to expose NextivaONE and NEXT as separately named application families; this guide does not infer an undocumented migration, replacement, shared entitlement, feature parity or common release state. Exact account, tenant, license, user, extension, number, product family, application path, operating system, installed build, browser, sign-in method, service state, call handling, notification, background state, emergency location, network, local device, packet, media, feedback, log submission and support result remain deployment-specific. No Nextiva account, tenant, license, application, browser, device, credential, number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, feedback, log file or support response was inspected or tested

NextivaONE: application identity, client paths and call-evidence boundaries

Evaluate NextivaONE desktop, web and mobile calling without transferring NEXT product, release, entitlement, background, network or media evidence.

Read guide →
Troubleshooting · Current first-party NextivaONE landing, setup, troubleshooting, calling, mobile, audio-device, log, feedback, login, update and network records plus separate NEXT release-note and desktop-app records were reviewed October 29, 2026. The inspected support material continued to expose NextivaONE and NEXT as separately named application families; this guide does not infer an undocumented migration, replacement, shared entitlement, feature parity or common release state. Exact account, tenant, license, user, extension, number, product family, application path, operating system, installed build, browser, sign-in method, service state, call handling, notification, background state, emergency location, network, local device, packet, media, feedback, log submission and support result remain deployment-specific. No Nextiva account, tenant, license, application, browser, device, credential, number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, feedback, log file or support response was inspected or tested

NextivaONE sign-in, inbound ringing, call or audio fails

Find the first divergence across product family, account, client path, build, call handling, background delivery, network, local devices and media.

Read guide →
Client research · Current first-party Microsoft Teams client, Teams Phone setup, dial-pad, calling-policy, call-setting, mobile-notification, client-health, diagnostic-log, call-telemetry, emergency-policy and location-consent records were reviewed October 28, 2026. Teams desktop, web, mobile, VDI and desk-phone paths plus Calling Plans, Operator Connect, Teams Phone Mobile, Direct Routing and Shared Calling retain separate requirements and ownership. Exact tenant, cloud, user, license, voice enablement, number, PSTN option, policy, client path, build, sign-in, call handling, notification, location, network, device, packet, telemetry, log and support state remain deployment-specific. No Microsoft 365 tenant, Teams account, license, application, browser, device, credential, phone number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, telemetry record, log file or support response was inspected or tested

Microsoft Teams Phone client: entitlement, dial pad and call-evidence boundaries

Evaluate Teams Phone across desktop, web and mobile clients without collapsing licensing, PSTN connectivity, policy, routing, notification, device or telemetry evidence.

Read guide →
Troubleshooting · Current first-party Microsoft Teams client, Teams Phone setup, dial-pad, calling-policy, call-setting, mobile-notification, client-health, diagnostic-log, call-telemetry, emergency-policy and location-consent records were reviewed October 28, 2026. Teams desktop, web, mobile, VDI and desk-phone paths plus Calling Plans, Operator Connect, Teams Phone Mobile, Direct Routing and Shared Calling retain separate requirements and ownership. Exact tenant, cloud, user, license, voice enablement, number, PSTN option, policy, client path, build, sign-in, call handling, notification, location, network, device, packet, telemetry, log and support state remain deployment-specific. No Microsoft 365 tenant, Teams account, license, application, browser, device, credential, phone number, location, network, packet, call, media stream, emergency outcome, price, availability, compatibility, telemetry record, log file or support response was inspected or tested

Microsoft Teams Phone dial pad, ringing, call or audio fails

Find the first divergence across tenant, entitlement, voice enablement, client path, policy, PSTN routing, notification, local devices and media.

Read guide →
Client research · Current first-party Dialpad app requirements, download, web-app, update, profile, calling, notification, audio, network, System Test, troubleshooting, QoS, E911 and Dynamic E911 records were reviewed October 28, 2026. Native desktop, Chrome web, PWA, Chrome extension, iOS, Android, approved VDI, desk-phone and mobile-native-dialer paths retain separate requirements and ownership. Exact company, office, user, product, license, direct or shared line, number, caller ID, call handling, client path, package, build, browser, permission, location, network, device, packet, metric, log and support state remain deployment-specific. No Dialpad company, office, account, license, application, browser, device, credential, phone number, E911 address, network, packet, call, media stream, emergency outcome, price, availability, compatibility, System Test result, QoS record, log file or support response was inspected or tested

Dialpad app: client paths, calling identity and evidence boundaries

Evaluate Dialpad across desktop, Chrome, PWA and mobile clients without collapsing account assignment, line identity, routing, notification, device, network or quality evidence.

Read guide →
Troubleshooting · Current first-party Dialpad app requirements, download, web-app, update, profile, calling, notification, audio, network, System Test, troubleshooting, QoS, E911 and Dynamic E911 records were reviewed October 28, 2026. Native desktop, Chrome web, PWA, Chrome extension, iOS, Android, approved VDI, desk-phone and mobile-native-dialer paths retain separate requirements and ownership. Exact company, office, user, product, license, direct or shared line, number, caller ID, call handling, client path, package, build, browser, permission, location, network, device, packet, metric, log and support state remain deployment-specific. No Dialpad company, office, account, license, application, browser, device, credential, phone number, E911 address, network, packet, call, media stream, emergency outcome, price, availability, compatibility, System Test result, QoS record, log file or support response was inspected or tested

Dialpad app sign-in, ringing, call or audio fails

Find the first divergence across company assignment, client path, line identity, routing, notification, local devices, network and media evidence.

Read guide →
Client research · Current first-party 8x8 Work download and system-requirement, desktop lifecycle, desktop and Web sign-in, capability, presence, notification, audio, call-quality, network-utility, emergency-address, Nomadic 911, support and outage records were reviewed October 29, 2026. Desktop, Web, mobile, VDI, desk-phone, call-queue and forwarding paths retain separate requirements, entitlements and owners. The published download and lifecycle pages are version-sensitive; the running build and current support state must be checked at the time of an incident. Exact tenant, site, user, license, extension, number, caller identity, queue membership, client path, package, build, browser, operating system, permission, location, network, device, packet, metric, log and support state remain deployment-specific. No 8x8 tenant, license, account, application, browser, device, credential, extension, number, emergency address, network, packet, call, media stream, emergency outcome, price, availability, compatibility, Network Utility result, quality result, log file or support response was inspected or tested

8x8 Work apps: client paths, extension identity and evidence boundaries

Evaluate 8x8 Work across desktop, Web and mobile paths without collapsing tenant assignment, extension identity, capability, routing, notification, device, network or emergency evidence.

Read guide →
Troubleshooting · Current first-party 8x8 Work download and system-requirement, desktop lifecycle, desktop and Web sign-in, capability, presence, notification, audio, call-quality, network-utility, emergency-address, Nomadic 911, support and outage records were reviewed October 29, 2026. Desktop, Web, mobile, VDI, desk-phone, call-queue and forwarding paths retain separate requirements, entitlements and owners. The published download and lifecycle pages are version-sensitive; the running build and current support state must be checked at the time of an incident. Exact tenant, site, user, license, extension, number, caller identity, queue membership, client path, package, build, browser, operating system, permission, location, network, device, packet, metric, log and support state remain deployment-specific. No 8x8 tenant, license, account, application, browser, device, credential, extension, number, emergency address, network, packet, call, media stream, emergency outcome, price, availability, compatibility, Network Utility result, quality result, log file or support response was inspected or tested

8x8 Work sign-in, ringing, call or audio fails

Find the first divergence across tenant assignment, client path, extension identity, capability, route, notification, local devices, network and media evidence.

Read guide →
Client research · Current first-party Vonage Business Communications desktop, web, mobile, compatibility, MSI, extension-setting, continuity, network, quality-tool, echo-test and emergency-service records were reviewed October 29, 2026. Desktop executable, browser, mobile, desk-phone and forwarding paths retain separate requirements, capabilities and owners. Published compatibility, download, network and release-cadence details are version-sensitive; the running build and current support state must be checked during an incident. Exact account, site, user, extension, number, plan, permission, device assignment, client path, package, build, browser, operating system, notification, emergency location, network, packet, metric, call record, case and support state remain deployment-specific. No Vonage account, application, device, credential, extension, number, location, network, packet, call, media stream, continuity event, emergency outcome, price, availability, compatibility, quality result, log file or support response was inspected or tested

Vonage Business Communications apps: client paths, extension identity and evidence

Evaluate Vonage Business Communications across desktop, web and mobile clients without collapsing account assignment, extension identity, routing, notification, device, network, continuity or emergency evidence.

Read guide →
Troubleshooting · Current first-party Vonage Business Communications desktop, web, mobile, compatibility, MSI, extension-setting, continuity, network, quality-tool, echo-test and emergency-service records were reviewed October 29, 2026. Desktop executable, browser, mobile, desk-phone and forwarding paths retain separate requirements, capabilities and owners. Published compatibility, download, network and release-cadence details are version-sensitive; the running build and current support state must be checked during an incident. Exact account, site, user, extension, number, plan, permission, device assignment, client path, package, build, browser, operating system, notification, emergency location, network, packet, metric, call record, case and support state remain deployment-specific. No Vonage account, application, device, credential, extension, number, location, network, packet, call, media stream, continuity event, emergency outcome, price, availability, compatibility, quality result, log file or support response was inspected or tested

Vonage Business app sign-in, ringing, call or audio fails

Find the first divergence across VBC assignment, client path, extension identity, route, notification, local devices, network, continuity and media evidence.

Read guide →
Client research · Current first-party Aircall Workspace download, product, desktop, web, mobile, device, headset, update, audio, inbound-call, network-diagnostic, emergency-address and support records were reviewed October 30, 2026. The download and support surfaces do not state every platform boundary identically, so the selected package, store listing, installed build and current administrator guidance must be checked together. Exact company, user, role, assigned number, caller identity, call distribution, client path, package, build, browser, operating system, permission, notification, emergency address, network, media region, packet, metric, recording, call ID, case and support state remain deployment-specific. No Aircall company, account, application, browser, device, credential, number, address, network, diagnostic, packet, call, media stream, recording, emergency outcome, price, availability, compatibility, support finding or restoration was inspected or tested

Aircall Workspace: client paths, number assignment and call evidence

Evaluate Aircall Workspace across desktop, web and mobile without collapsing company access, number assignment, call distribution, notification, local audio, network diagnostics or emergency evidence.

Read guide →
Troubleshooting · Current first-party Aircall Workspace download, product, desktop, web, mobile, device, headset, update, audio, inbound-call, network-diagnostic, emergency-address and support records were reviewed October 30, 2026. The download and support surfaces do not state every platform boundary identically, so the selected package, store listing, installed build and current administrator guidance must be checked together. Exact company, user, role, assigned number, caller identity, call distribution, client path, package, build, browser, operating system, permission, notification, emergency address, network, media region, packet, metric, recording, call ID, case and support state remain deployment-specific. No Aircall company, account, application, browser, device, credential, number, address, network, diagnostic, packet, call, media stream, recording, emergency outcome, price, availability, compatibility, support finding or restoration was inspected or tested

Aircall Workspace has no lines, does not ring or has bad audio

Find the first divergence across company access, number assignment, distribution, availability, notification, local devices, network diagnostics and call-specific media.

Read guide →