Freeze one failed attempt and the client boundary
Record timestamp and timezone, organization, user, application build, platform, device, network, foreground or background state, Phone Services result, line, destination form, direction, call identifier, error text or code, alert, answer, selected audio devices and final outcome. Redact credentials, personal numbers, exported traces and customer data.
Classify the first divergence as application sign-in, phone-service sign-in, registration, no dial control, policy or entitlement, address or number rejection, remote alert, answer, local capture, outbound media, inbound media or rendering. A connected phone-service indicator ends only the connection branch.
Confirm the assigned service and registration evidence
Open Phone Services and preserve whether the account uses Unified CM, Webex Calling, a hosted service provider or Webex App calls only. Compare the result with the administrator assignment and the intended destination. If the app shows a Calling error, retain the exact code and documented category before signing out or resetting state.
For Unified CM, use the Health Checker phone-services result to distinguish server connectivity while remembering that a green result does not prove line authorization or a completed call. For other modes, do not invent a Unified CM test or treat a generic cloud-status check as phone-service registration.
Trace the address, policy and call-control result
For Call on Webex, preserve the Webex identity or video address and whether the contact is searchable. For work-number calling, record the assigned line, normalized digits, calling service, dial control, permission, route and returned treatment. Compare desktop and mobile only against the service-specific feature table and administrator policy.
If no dial pad appears, first determine whether the account is assigned a phone-number calling service. If the request leaves the client, preserve the final response and first downstream owner rather than reinstalling the application or changing every network rule.
Prove capture, rendering and each media direction
Verify the ringer, speaker and microphone selections separately, including operating-system permission, physical mute, Bluetooth or USB path and any smart-audio or macOS Mic Mode processing. Run the documented local speaker and microphone tests and retain the device names and result.
Then correlate the failed call with offer and answer where accessible, codec, local and remote addresses, first packet in each direction, statistics and the remote party's observation. Local tests, packet counters and audible output are distinct evidence states; change only the first failed layer.
Use local and administrator diagnostics without overreading them
Capture Health Checker Internet, server-connection and applicable phone-services results, then open local Diagnostics for current configuration and recent audio statistics. Export only when authorized: Cisco warns that the diagnostic ZIP contains confidential network information. Record who received it, how it was protected and when it will be deleted.
Where the service and role support it, correlate the completed call in Control Hub by the same identity, number, timestamp and call identifier. A public status, green cloud result or administrator media score does not alone prove the workstation device path or user experience.
Retest the narrow repair and preserve service differences
Correct only the proven assignment, entitlement, authentication, route, device, permission, processing or network fault. Repeat the same authorized call and one negative control, confirm alert, answer, two-way audio and clean release, then remove temporary captures and broad exceptions.
Do not use an emergency number as a test destination, weaken certificate validation or publish trace bundles. No organization, account, client, phone service, administrator record, network, packet, media stream, emergency call or live call was inspected or tested for this diagnostic.
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.