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

Softphone uses the wrong speaker, headset or microphone

Separate the connected device, operating-system defaults, per-app route, softphone selection, browser permission and active call path after docking, Bluetooth or USB changes.

Reviewed 2026-10-30Current Microsoft Windows audio-device and per-app routing guidance, Apple macOS input and output guidance and AVAudioSession route-change documentation, Android AudioManager reference, and W3C Media Capture and Audio Output specifications reviewed October 6, 2026; no computer, mobile device, dock, USB interface, Bluetooth device, browser, softphone, operating-system policy, PBX, media path or live call was inspected or testedIntermediateDocumentation based · not lab tested

Name the wrong path before resetting devices

Preserve one affected call and record what is wrong: ringtone on an unexpected speaker, remote speech on the wrong output, microphone from the wrong input, or a route that changes only after docking, reconnecting USB, joining Bluetooth, sleep or resume. Record time, operating system, softphone and browser builds, connected devices, saved selections, active selections and the transition immediately before the symptom.

A device can be paired or connected without being the active call route. System sounds, a local recording, softphone ringtone, received call audio and transmitted microphone media can also use different controls. Do not treat sound from one of those paths as proof of another, and do not reinstall or clear the client until the route evidence and provisioned account are preserved.

Separate operating-system defaults from per-app routing

Microsoft's current Windows guidance exposes output and input devices in Sound settings and identifies the Volume mixer when one application is silent while system audio works. Record the default output, default input, any communications-role device and the softphone's per-app assignment. A working browser video or Windows alert can still use a different route from a desktop softphone.

Apple's macOS guidance similarly provides separate Sound output and input selections. Check the actual device name and input level rather than assuming the most recently connected headset became the default. If the operating system cannot play an approved test sound or show input level on the intended device, stop at that layer; SIP, RTP and codec changes cannot select a missing local route.

Read the softphone's active route, not only its preference

After the operating-system path works, inspect the softphone's current speaker, microphone and ringtone selections. Some clients offer explicit devices while others follow the operating-system default. A saved label can point to a device that was removed and recreated with a new identifier after a dock, USB or driver transition.

Change only one selection and confirm whether it applies immediately or on the next call. Keep hardware mute, application mute, input gain and output level separate. If the intended microphone works in the operating system but the softphone captures a different input, follow the silent-microphone diagnosis before altering media addresses or PBX policy.

Treat Bluetooth, USB and dock changes as route events

Apple documents audio-route changes when an input or output is added or removed, including wired headphones, Bluetooth headsets and USB audio interfaces, and exposes both the current and previous route to applications. Android likewise distinguishes available communication devices from the device selected for a communication use case. These are application-platform capabilities, not proof that one softphone handles every transition correctly.

Reproduce the problem with a bounded sequence: start with built-in audio, connect the approved device, place a call, disconnect it during an authorized test, reconnect it and place another call. Record the route at each stage and whether media became private or moved to a loudspeaker. Avoid repeated pairing resets or driver replacement until the first route change that diverges is known.

Preserve browser permission and output-selection boundaries

For a browser softphone, Media Capture and Streams makes the available input list permission and policy sensitive. The Audio Output Devices specification adds user-mediated selection of a non-default output and binding that approved device to a media element. The default output has a different permission boundary, and support remains dependent on the exact browser and application implementation.

Record the page origin, browser build, permission state, enumerated device labels, selected input, selected output, remote media element and playback result. A device missing from a webphone menu does not alone prove hardware failure, and a successful SIP session does not prove the remote track was bound to the intended output. Do not grant broad microphone access to unrelated origins or claim universal browser output selection from the existence of the specification.

Keep ringtone, conversation and privacy behavior separate

A receptionist may deliberately send ringtone to a desk speaker while keeping conversation audio on a headset. That can be useful, but it also means a ringtone test cannot accept the call-media route. Confirm inbound alert, answer, remote speech, local speech, hold, resume, transfer and hangup on the intended devices. Repeat with another application briefly using the microphone only when policy permits.

Test privacy explicitly after a headset or Bluetooth device is removed. The expected result may be pause, a visible prompt or a controlled fallback; automatic movement to a loudspeaker can expose call audio. Record the approved fallback for the organization and client rather than assuming one operating system's media-player convention defines VoIP-call behavior.

Correct one owner and verify recovery

Correct only the demonstrated boundary: disabled operating-system device, wrong default or per-app assignment, softphone device preference, stale device identifier, browser permission or output selection, unsupported client build, driver or firmware owned by the endpoint team, or an application route-change defect. Preserve the previous setting and rollback. Do not change NAT, codecs, SIP credentials or PBX routing when local route evidence already explains the symptom.

Repeat the affected call and a known-good control with the intended input, output and ringtone paths. Verify connect and disconnect, dock or undock, sleep and resume, application restart, mute and unmute, hold and resume, transfer where required, both speech directions and privacy after device removal. No computer, mobile device, dock, USB interface, Bluetooth device, browser, softphone, operating-system policy, PBX, media path or live call was inspected or tested for this guide.

Do not use conversation output selection to explain a missing browser ringtone

The browser no-ring diagnostic first proves INVITE arrival, visible alert state and ringtone playback policy. After answer, return here to prove the selected remote-audio output and actual listener result.

Continue from device selection into headset call control

After the intended microphone and speaker are proven, use the wireless-headset control diagnostic when answer, end, hold or mute state still differs between the physical headset and softphone.

Check all three VoIPstudio audio destinations

The VoIPstudio desktop client documents separate microphone, call-audio and ringer controls. The service-specific guide and diagnostic keep ringing, capture and rendered call audio from standing in for one another.

Check Webex ringer, speaker and microphone independently

Webex App exposes separate desktop choices and can receive operating-system processing before the app. The calling guide keeps local tests separate from observed call media.

Use the MicroSIP audio-device note as a bounded clue

The 3.22.19 notes add detection of memory corruption associated with problematic audio devices or drivers. The MicroSIP guide keeps that publisher statement separate from evidence that one device is incompatible, selected or repaired.

Separate PhonerLite global audio state from its SIP profile

PhonerLite stores selected sound devices in global configuration, not the SIP profile. The local-state diagnostic proves which PhonerLite.ini and device selection are active.

Select all three V52 peripherals explicitly

The V52 diagnostic checks operating-system and meeting-app camera, microphone and speaker selection before network or hardware replacement.

Select all three V72 host devices explicitly

The V72 diagnostic verifies operating-system and meeting-client camera, microphone and speaker selection before replacing hardware.

Use JsSIP peer-connection and media-element evidence

The JsSIP diagnostic separates receiver tracks, stream attachment and audible playback.

Bind a Jitsi Desktop audio result to the exact legacy package

Use the Jitsi Desktop workflow to record OS, Java runtime, selected devices, permissions and media before and after one controlled change.

Verify the Wave platform’s selected devices

The Grandstream Wave diagnostic keeps operating-system, browser and client device selection separate from negotiated media.

Verify RingCentral microphone, speaker and ringer independently

The RingCentral diagnostic preserves operating-system, application and headset-control ownership.

Verify Zoom microphone, speaker and ringer independently

The Zoom Workplace diagnostic records operating-system defaults, Zoom selections, device attachment and the exact call result.

Verify all three NextivaONE audio outputs

The NextivaONE diagnostic records microphone, speaker and ringer plus operating-system defaults and local tests.

Verify every Teams audio output separately

The Teams Phone diagnostic records primary device, microphone, speaker, secondary ringer and call-specific media.

Verify every Dialpad audio output separately

The Dialpad app diagnostic records microphone, call output, ringtone output, notification volume, Bluetooth and live media.

Verify every 8x8 audio boundary separately

The 8x8 Work diagnostic records operating-system and app devices, permission, processing and call-specific media.

Verify every VBC audio boundary separately

The VBC diagnostic records operating-system and app devices, permission, headset path, echo playback and call-specific media.

Verify each Aircall audio boundary separately

The Aircall diagnostic records operating-system and Workspace devices, browser permission, headset path, device tests and call-specific media.

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

Troubleshooting · Current Microsoft Windows microphone permission and troubleshooting guidance, Apple macOS and iPhone microphone controls, Android permissions, RFC 3264 offer/answer, RFC 3550 RTP and Asterisk PJSIP troubleshooting documentation reviewed October 6, 2026; no workstation, mobile device, microphone, headset, softphone, operating-system policy, SIP account, PBX, packet capture, protected-media path or call was inspected or tested

Softphone microphone is silent: prove capture before RTP

Separate operating-system permission, selected input, client mute and capture, SDP direction, outbound RTP and remote decode when callers cannot hear a softphone user.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

VoIP call connects but has no audio

Separate endpoint audio selection from a media path that fails in both directions.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

One-way VoIP audio

Trace the missing direction from advertised media address to receiving endpoint.

Read guide →
Guide · Primary desktop-softphone and operating-system documentation reviewed through October 10, 2026; app, audio-device and PBX interoperability not lab tested

Desktop softphones: SIP accounts and workstation operations

Evaluate installable clients on Windows, macOS and Linux with evidence for audio, registration, encryption and configuration ownership.

Read guide →
Guide · Primary mobile-softphone, operating-system, push and signaling documentation reviewed through October 9, 2026; app, device and PBX interoperability not lab tested

Mobile softphones: background calling and emergency boundaries

Research iOS and Android client behavior across push notifications, changing networks and account location.

Read guide →
Guide · Current SIP.js release, migration, repository, Simple User, mobile and security-policy documentation plus MDN, W3C and Asterisk references reviewed October 8, 2026; no package, application, browser, mobile wrapper, PBX, permission, notification path, media path or call was inspected or laboratory-tested

Browser webphones: microphone permission and audible-call checks

Trace browser calling through secure origin, capture policy, device selection, SIP session, remote media and playback before changing the network.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

Find RTP streams and interpret loss and jitter

Separate captured packet statistics from what the receiving listener actually experienced.

Read guide →
Troubleshooting · Current first-party SIP.js call-receive, user-agent, media and mobile guidance plus MDN, Chrome and WebKit playback, AudioContext and visibility documentation reviewed October 9, 2026; browser autoplay behavior is policy- and state-sensitive, the SIP.js mobile statement is limited to compatible foreground web applications, and no package, application, origin, browser, tab, operating system, user gesture, media element, audio context, WebSocket, registration, INVITE, device, PBX, ringtone, notification, media path or call was inspected or tested

Browser softphone receives the INVITE but does not ring

Separate WSS and registration, INVITE delivery, visible call state, ringtone playback policy, user activation, answer and remote media before changing SIP routing.

Read guide →
Device category · Current Jabra Evolve3 85 product, RevA manual and support material, current Yealink WH64 Hybrid product, datasheet and call-control documentation, and Bluetooth SIG Hands-Free Profile 1.10 reviewed October 14, 2026; the sources document headset controls and host connection capabilities but do not prove application integration, negotiated profile, mute synchronization, range, audio quality, platform certification, compatibility, availability or a completed call on any deployment, and no headset, adapter, host, application, account, radio link, media path or live call was inspected or tested

Business wireless headsets: host, radio and call-control boundaries

Choose and accept a business Bluetooth or DECT headset by exact host path, application integration, call-control behavior, mute ownership, multipoint policy, management owner and measured user workflow.

Read guide →
Troubleshooting · Current Jabra Evolve3 85 product, RevA manual and support material, current Yealink WH64 Hybrid product, datasheet and call-control documentation, and Bluetooth SIG Hands-Free Profile 1.10 reviewed October 14, 2026; the sources document headset controls and host connection capabilities but do not prove application integration, negotiated profile, mute synchronization, range, audio quality, platform certification, compatibility, availability or a completed call on any deployment, and no headset, adapter, host, application, account, radio link, media path or live call was inspected or tested

Wireless headset buttons or mute state do not match the softphone

Find the first divergence among the physical control, radio or adapter, host device, vendor service, selected softphone integration, application state and remote audio result.

Read guide →
Client research · Current VoIPstudio download, Desktop Softphone, user-introduction, endpoint-administration and network-troubleshooting documentation reviewed October 16, 2026; the public download surface lists Windows, Windows MSI, macOS Intel, macOS Silicon and Linux paths but does not publish one common desktop build number, and no package, workstation, operating-system permission, user account, endpoint record, VPN, firewall, WebRTC test, SIP Test, MTR result, packet, protected session, media stream or live call was inspected or tested

VoIPstudio Desktop Softphone: account, audio and network evidence

Evaluate the service-specific Windows, macOS and Linux desktop client without treating an online icon, selected device or WebRTC test as proof of a completed two-way call.

Read guide →
Troubleshooting · Current VoIPstudio download, Desktop Softphone, user-introduction, endpoint-administration and network-troubleshooting documentation reviewed October 16, 2026; the public download surface lists Windows, Windows MSI, macOS Intel, macOS Silicon and Linux paths but does not publish one common desktop build number, and no package, workstation, operating-system permission, user account, endpoint record, VPN, firewall, WebRTC test, SIP Test, MTR result, packet, protected session, media stream or live call was inspected or tested

VoIPstudio Desktop is online but the call or audio fails

Separate application login, endpoint registration, call signaling, selected devices, WebRTC reachability and two-way media before changing credentials or network policy.

Read guide →
Client research · Current Cisco Webex App calling-option, assigned-service, system-requirement, download, audio-setting, Health Checker, local Diagnostics, Calling-error and Control Hub troubleshooting documentation reviewed October 16, 2026. Call on Webex, Unified CM, Webex Calling and Calling hosted by a Service Provider remain distinct calling services with different feature and evidence boundaries. Platform, client build, entitlement, dial plan, emergency behavior, signaling and media protection, availability and compatibility remain deployment or observation specific. No organization, account, client, phone service, device, network, packet, media stream, administrator view or call was inspected or tested

Webex App calling: service modes, clients and evidence

Qualify Webex App as an assigned calling client by service, platform, entitlement, identity, device path, diagnostic evidence and observed call rather than by its shared interface alone.

Read guide →
Troubleshooting · Current Cisco Webex App calling-option, assigned-service, system-requirement, download, audio-setting, Health Checker, local Diagnostics, Calling-error and Control Hub troubleshooting documentation reviewed October 16, 2026. Call on Webex, Unified CM, Webex Calling and Calling hosted by a Service Provider remain distinct calling services with different feature and evidence boundaries. Platform, client build, entitlement, dial plan, emergency behavior, signaling and media protection, availability and compatibility remain deployment or observation specific. No organization, account, client, phone service, device, network, packet, media stream, administrator view or call was inspected or tested

Webex App phone service connects but calls or audio fail

Find the first divergence among assigned calling service, entitlement, registration, address or number, call control, selected devices and both media directions.

Read guide →
Client research · MicroSIP project, current-version pointer, stable downloads, help, troubleshooting and FAQ pages reviewed October 17, 2026. The current-version pointer and primary download table listed 3.22.19 for the regular and Lite editions with an October 3, 2026 release date. Package listing, installed build, active account, call authorization, negotiated signaling and media, Windows audio path and audible outcome remain separate evidence. No package, installation, Windows host, Wine environment, account, credential, PBX, provider, network, VPN, audio device, driver, SIP exchange, media stream, protected session, emergency workflow or live call was inspected or tested

MicroSIP: account mode, call path and protected-media boundaries

Keep the active SIP account, Local Account, dial plan, Call Manager, signaling address, media address and Windows audio path separate when deploying MicroSIP.

Read guide →
Troubleshooting · MicroSIP project, current-version pointer, stable downloads, help, troubleshooting and FAQ pages reviewed October 17, 2026. The current-version pointer and primary download table listed 3.22.19 for the regular and Lite editions with an October 3, 2026 release date. Package listing, installed build, active account, call authorization, negotiated signaling and media, Windows audio path and audible outcome remain separate evidence. No package, installation, Windows host, Wine environment, account, credential, PBX, provider, network, VPN, audio device, driver, SIP exchange, media stream, protected session, emergency workflow or live call was inspected or tested

MicroSIP registers but a call or audio fails

Follow the active account, transformed destination, SIP dialog, advertised addresses, negotiated media and Windows audio device in order before changing NAT or codecs.

Read guide →
Troubleshooting · Current first-party PhonerLite product, 3.46 stable and 3.47 beta release, profile, configuration-location, provisioning, audio-device, logbook, recording and transcription documentation reviewed October 18, 2026. Executable package, resolved configuration directory, active profile, credential-bearing sipper.ini, registration, call history, recording file, sound device and completed call remain separate evidence. No package, signature, Windows host, profile, credential, PBX, file, recording, transcription, headset, protected session or live call was inspected or tested

PhonerLite profile, history or settings are missing after an update

Trace the running package, write context, resolved data directory, files and active profile before restoring credentials, history, contacts, audio settings or recording links.

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 · The official Jitsi Desktop repository, release archive, legacy download and setup pages, historical product site, Jitsi security clarification, Jitsi Meet Electron repository and jit.si account end-of-life notice were reviewed October 23, 2026. Jitsi Desktop, Jitsi Meet and Jitsi Meet Electron are separate products. The Desktop repository says the SIP/XMPP client is not actively developed and that builds depend on community contributions. GitHub release labels are non-monotonic: 2.8.5426 carries the Latest badge, 2.10.5550 is a later-numbered release, and 2.11.5633 is marked pre-release. Exact artifact, tag, operating system, package channel, Java runtime, account, registrar, transport, certificate result, negotiated media and completed call remain separate evidence. Historical feature or security claims do not establish present support, vulnerability status, service compatibility or encryption. The old jit.si account service ended June 1, 2016. No installer, package, checksum, signature, operating system, Java runtime, account, credential, registrar, PBX, DNS answer, firewall, NAT path, certificate, microphone, speaker, headset, SDP, RTP stream, encrypted session, emergency workflow, price, availability, compatibility, support response or call was inspected or tested

Jitsi Desktop: legacy SIP client, release and security boundaries

Treat Jitsi Desktop as a community-maintained legacy SIP/XMPP client, distinct from Jitsi Meet, and bind every installer, account, certificate and media result to exact evidence.

Read guide →
Troubleshooting · The official Jitsi Desktop repository, release archive, legacy download and setup pages, historical product site, Jitsi security clarification, Jitsi Meet Electron repository and jit.si account end-of-life notice were reviewed October 23, 2026. Jitsi Desktop, Jitsi Meet and Jitsi Meet Electron are separate products. The Desktop repository says the SIP/XMPP client is not actively developed and that builds depend on community contributions. GitHub release labels are non-monotonic: 2.8.5426 carries the Latest badge, 2.10.5550 is a later-numbered release, and 2.11.5633 is marked pre-release. Exact artifact, tag, operating system, package channel, Java runtime, account, registrar, transport, certificate result, negotiated media and completed call remain separate evidence. Historical feature or security claims do not establish present support, vulnerability status, service compatibility or encryption. The old jit.si account service ended June 1, 2016. No installer, package, checksum, signature, operating system, Java runtime, account, credential, registrar, PBX, DNS answer, firewall, NAT path, certificate, microphone, speaker, headset, SDP, RTP stream, encrypted session, emergency workflow, price, availability, compatibility, support response or call was inspected or tested

Jitsi Desktop SIP registers but call, audio or certificate fails

Find the first mismatch in legacy-client identity, exact release, current SIP account, DNS and network path, certificate validation, call signaling, audio device or negotiated media.

Read guide →
Client research · Grandstream Wave release index plus Desktop 1.35.6, Web 1.0.35.7, Android 1.0.35.7 and iOS 1.35.7 release notes dated September 21, 2026, together with current product, desktop, mobile, web and UCM documentation reviewed October 7, 2026; no app, browser, UCM, identity provider, AI service, WhatsApp integration, RemoteConnect service, account, device, network, recording, transcript, remote-control session or call was inspected or tested

Grandstream Wave: UCM-bound desktop, mobile and web client

Evaluate Wave as a Grandstream UCM ecosystem client, keeping each platform, login path, RemoteConnect boundary and background-delivery result separate.

Read guide →
Troubleshooting · Grandstream Wave product, release-index, Desktop, Mobile, Web, FAQ and UCM RemoteConnect documentation plus the September 21, 2026 Android 1.0.35.7 and iOS 1.35.7 release notes were reviewed October 27, 2026. Wave platform, UCM family and firmware, extension policy, user-portal password, QR or identity-provider flow, RemoteConnect plan and region, mobile operating-system restrictions, browser permissions, signaling, media and emergency behavior remain deployment-specific. No app, browser, UCM, credential, QR code, identity provider, RemoteConnect account, subscription, device, notification, packet, call, media stream, price, availability or compatibility was inspected or tested

Grandstream Wave login, background call or audio fails

Find the first divergence across Wave platform and build, UCM identity, RemoteConnect, mobile background delivery, browser permissions, call signaling and media.

Read guide →
Client research · RingCentral RingEX app system requirements, download and release records, sign-in and app troubleshooting, network, calling, audio, quality-analytics and emergency-response-location documentation were reviewed October 27, 2026. The download page then listed desktop 26.3.30 dated September 30, while the release-notes page scheduled 26.4.10 for October 28 through November 3; that later window is not represented as installed or generally available on the review date. Exact tenant, RingEX subscription, user, extension, number, role, desktop, web, mobile or VDI build, update lane, authentication, call handling, notification policy, emergency location, network, signaling, media and analytics visibility remain account- and deployment-specific. No organization, account, app, browser, virtual desktop, credential, phone service, number, location, network, notification, packet, call, media stream, price, availability or compatibility was inspected or tested

RingCentral App: RingEX client, release and call-evidence boundaries

Evaluate RingCentral App desktop, web, mobile and VDI paths by exact RingEX assignment, build, update lane, identity, notification, call routing, emergency location and media evidence.

Read guide →
Troubleshooting · RingCentral RingEX app system requirements, download and release records, sign-in and app troubleshooting, network, calling, audio, quality-analytics and emergency-response-location documentation were reviewed October 27, 2026. The download page then listed desktop 26.3.30 dated September 30, while the release-notes page scheduled 26.4.10 for October 28 through November 3; that later window is not represented as installed or generally available on the review date. Exact tenant, RingEX subscription, user, extension, number, role, desktop, web, mobile or VDI build, update lane, authentication, call handling, notification policy, emergency location, network, signaling, media and analytics visibility remain account- and deployment-specific. No organization, account, app, browser, virtual desktop, credential, phone service, number, location, network, notification, packet, call, media stream, price, availability or compatibility was inspected or tested

RingCentral App sign-in, ringing, call or audio fails

Locate the first failed boundary across RingEX assignment, app track and build, identity, call handling, notification or push, network, signaling, media and emergency-location state.

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 →