Identify the assigned calling service before comparing features
Record the organization, user, Webex App build, operating system, device, network and administrator owner. In Phone Services, Cisco documents distinct results for Unified CM, Webex Calling and Calling hosted by a Service Provider; no Phone Services entry means the organization is configured for Webex App calls only. Preserve that result and the time observed.
The same Calls surface can therefore front different call control, numbering, feature and support paths. Do not infer Webex Calling from the application name, a dial pad from a subscription label, or PSTN reachability from a successful Call on Webex session.
Separate application calls from work-number calling
Call on Webex uses Webex identities and can also use a video or SIP address; it is not automatically a work-number or public-network call. Cisco documents work-number calling through Unified CM, Webex Calling or a hosted service-provider configuration, with a feature comparison that varies by service and desktop or mobile client.
Record the selected identity, entered address or normalized number, line, calling service, feature entitlement, administrator policy and final route. An audio or video icon, contact card or call-history row does not prove which service carried the call.
Pin the platform, build and release boundary
The current download surface publishes Windows x64 and Arm64, separate macOS Intel and Apple-silicon packages, Linux DEB and RPM, and mobile downloads. The system-requirements page is the volatile authority for supported operating systems and web browsers. Record the exact artifact and build rather than copying one evergreen statement into a permanent compatibility claim.
Cisco documents meetings and free Call on Webex in supported browsers; that statement does not establish the same browser feature set as an assigned Webex Calling, Unified CM or service-provider desktop client. Keep web, desktop and mobile acceptance separate.
Map ringer, speaker, microphone and processing independently
Webex App exposes separate ringer, speaker and microphone choices on desktop, plus smart-audio processing. On supported macOS systems, operating-system Mic Modes can process audio before Webex App and can conflict with application processing. Record the physical device, operating-system selection, app selection, mute state and processing mode.
A successful speaker test proves local playback for the selected device, not call signaling or received media. A working microphone test proves local capture, not outbound packets or remote intelligibility. Keep meeting join audio, Call on Webex media and phone-service media tied to the exact observed session.
Interpret Health Checker, Diagnostics and administrator evidence narrowly
Cisco states that Health Checker cloud results show cloud status, not the client connection to the cloud. Its phone-services test is specific to Unified CM. Local Diagnostics separates general account data, configuration, recent audio, video and sharing statistics, and an export containing traces and diagnostic data. Treat each as one evidence layer.
Control Hub can provide post-call or meeting troubleshooting for supported services and roles, but its search window, fields and richness depend on service and client version. Correlate one call identifier, participants, timestamps, hops and media directions; redact network and identity data before sharing an exported ZIP.
Build an acceptance record for the assigned service
For one authorized pilot, test sign-in, phone-service state, one internal identity call, one permitted work-number call where entitled, inbound alert, answer, hold, transfer where assigned, two-way audio, device change, network change, voicemail or history where applicable, and clean sign-out or revocation. Confirm emergency calling and location only through the organization's approved procedure and keep an independent emergency method.
Document expected differences across desktop, mobile and web instead of forcing feature parity. No feature, availability, compatibility, emergency behavior, security outcome or call quality is claimed from the public documentation alone.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Supported calling options in Webex App ↗
- Webex App: find out what calling service you have ↗
- Webex App system requirements and support policy ↗
- Download the Webex desktop and mobile apps ↗
- Webex App: change your audio settings ↗
- Webex App: test your connection with the Health Checker ↗
- Webex App: troubleshoot connection issues with the Diagnostics tool ↗
- Webex App: error messages for Calling ↗
- Advanced diagnostics and troubleshooting in Control Hub ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.