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

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.

Reviewed 2026-10-28Current 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 testedIntermediateDocumentation based · not lab tested

Freeze one tenant, client path and symptom

Record tenant and cloud, user or resource-account type, Teams Phone license, Enterprise Voice state, assigned number, effective calling policy, PSTN option, desktop, web, mobile or VDI path, operating system or browser, app-reported build, network, local and UTC time, direction, destination and the first visible symptom. Redact credentials, tokens, precise location and unrelated participant data.

Separate missing Calls app, missing dial pad, rejected outbound setup, provider attempt routed elsewhere, no visible alert, silent ringer, answer failure, answered call without audio, wrong device, poor media and missing telemetry. Do not merge meeting, internal Teams, PSTN, desk-phone and mobile-native-dialer results.

Prove dial-pad entitlement and policy before reinstalling

For a missing dial pad, check the assigned Teams Phone plan, online homing, Enterprise Voice enablement and effective Make private calls policy independently. Then establish the selected PSTN connectivity option and number or Shared Calling state. Preserve provisioning errors and recent-change time.

A license alone does not prove voice enablement, policy, number or carrier connectivity. Microsoft notes that changes can take time to reach the client, so record the client restart and observation time rather than repeatedly changing assignments or reinstalling the app.

Trace inbound handling, notification and the answering endpoint

For one controlled non-emergency inbound call, inspect forwarding, simultaneous ring, voicemail, delegation, call groups, queues, quiet time, mobile notification permission, call-notification choices and per-device ringtone. Record the service target, notification, visible alert, primary audio device, secondary ringer, answer action and final answering endpoint.

Mobile call notifications can behave differently from other notification types. A badge, history row, voicemail or successful answer elsewhere does not prove that the affected client received an alert or produced an audible ring.

Compare the exact client build and network path

Record whether the result came from Windows, macOS, a supported desktop browser, iOS, Android or an approved VDI path. Do not transfer desktop Linux, mobile-browser, ordinary web or VDI expectations between paths. Confirm the running build and update owner rather than relying on an available package or dashboard version row.

Compare one controlled call on one alternate network only after preserving the original result. Another-network success narrows the boundary but does not identify the original firewall, proxy, VPN, ISP or Wi-Fi system as the cause.

Separate device selection, packet flow and perceived media

Record operating-system defaults plus Teams microphone, speaker, camera and secondary ringer. A Teams test call on Windows or Mac desktop can confirm a bounded local playback path, but it does not prove PSTN route selection, the remote endpoint or two-way media for the failed call.

For the affected call preserve call identifiers, both packet directions, codec and endpoint telemetry where authorized, decoding and what each party heard. Completed call telemetry may not appear immediately, and a classifier or issue flag is an investigation signal rather than proof of one user experience or root cause.

Correct one owner and preserve support evidence safely

Assign the first divergence to one owner: tenant, identity, license, voice enablement, number, policy, PSTN option, client path, build, call handling, notification, network, local device, signaling, media, telemetry or support. Change one controlled variable and repeat the same non-emergency number, client path, network and direction plus one unaffected control.

Request remote logs only with the required role and organizational authority. Bound local or remote collection to the incident, account for multi-account data, sanitize exports and transmit through the approved channel. Keep request, Pending state, downloaded artifact, support finding and verified restoration separate. No tenant, client, network, call, media, telemetry, log or support response was inspected or tested.

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

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 →
Provider research · Current first-party Microsoft Teams Direct Routing planning, configuration, certified-SBC, number-translation, media-bypass, health, monitoring and emergency-calling documentation reviewed October 9, 2026; no tenant, license, user, number, carrier, trunk, SBC, certificate, DNS record, firewall, voice route, translation rule, SIP exchange, media stream, emergency workflow, message, availability, compatibility, price or call was inspected or tested

Microsoft Teams Direct Routing: tenant, SBC and carrier boundaries

Map a Teams Phone call through tenant policy, a certified SBC and a separately selected PSTN carrier without merging their licensing, routing, media or emergency responsibilities.

Read guide →
Troubleshooting · RFC 8599 SIP push, current Apple PushKit, Android background-service and Firebase guidance, vendor push architectures including MizuDroid's direct, gateway and service paths reviewed October 9, 2026; no device, application, token, gateway, SIP account, registration, INVITE, alert, media path, battery result or call was inspected or tested

Softphone rings only when open: trace registration and push wake-up

Separate foreground registration, push-token state, proxy ownership, APNs or FCM delivery, application wake-up, refreshed SIP reachability and the retained INVITE.

Read guide →
Troubleshooting · Current 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 tested

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.

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 · RFC 3261 dialog handling, RFC 4028 session refresh and current Asterisk res_pjsip timer controls reviewed September 30, 2026; no call, host or network event tested

VoIP calls drop at unpredictable times

Classify the first terminating event and correlate each dialog leg with media, transport, device and infrastructure evidence.

Read guide →
Guide

Firewall rules for VoIP

Define management, signaling and media access separately using actual deployment requirements.

Read guide →
Guide

PBX logs and packet captures: useful evidence with limited exposure

Collect enough to diagnose a call while protecting identities, secrets and audio.

Read guide →