Interactive Troubleshooter

Published: Sep 8, 2026

VoLTE Calls Dropping: Network Diagnostic Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

This interactive diagnostic tree systematically resolves Voice over LTE (VoLTE) call drops caused by IMS registration deregistration, Session Initiation Protocol (SIP) timer timeouts, eSRVCC handover failures, and QCI-1 Bearer misconfigurations.

Full Diagnostic Tree & Step-by-Step Overview

What specific pattern or timing defines your VoLTE call drops?

Calls drop precisely at specific elapsed times (e.g., 30s, 1m, or 15m into the call)
Calls drop instantly when moving between cell towers or transitioning indoors
Calls drop or fail immediately upon answering or initiating (No audio / Instant disconnect)
Calls drop exclusively when Wi-Fi Calling (VoWi-Fi) is enabled or toggling

What scenario best describes the predictable call termination timer?

Drop occurs at exactly 32 seconds or 64 seconds (SIP Session Refresh / ACK failure)
Drop occurs at 15 or 30 minutes due to RTP media stream silent timeout
Drop occurs intermittently accompanied by 'Server Error' or 'Network Busy' alerts

SIP Timer T1/T2 Timeout & Unacknowledged 200 OK Response

Solution:

Root Cause: SIP Session Refresh Handshake Failure (Timer T1/T2 Expiry)

In VoLTE communications, call signaling relies on Session Initiation Protocol (SIP) over an IP Multimedia Subsystem (IMS). When a call connects, the P-CSCF (Proxy-Call Session Control Function) sends a 200 OK message to the device, which must be acknowledged with a ACK packet. If strict carrier firewall policies, MTU fragmentation, or corrupt local IP routing tables block the ACK packet or intermediate UPDATE/INVITE refresh requests, SIP Timer T1 (500ms base retransmission) expires. Following 64-times retransmission scaling (Timer B/F expiry at ~32s), the IMS core forcefully terminates the call session by sending a BYE command.

Diagnostic Verification:

1On Android devices, navigate to Testing Menu by dialing *#*#4636#*#* -> Phone Information -> Tap three dots -> IMS Service Status.

2Confirm if IMS Registration toggles from *Registered* to *Not Registered* right as the call drops.

3Inspect cellular modem trace logs (if using QXDMLogger) for unacknowledged SIP 200 OK messages or SIP 408 Request Timeout responses.

Step-by-Step Fix:

1Reset IMS APN and Cellular Data Stack:

Android: Go to Settings -> Network & internet -> SIMs -> Access Point Names -> Tap the three dots -> Select Reset to default.

iOS: Go to Settings -> General -> Transfer or Reset iPhone -> Reset -> Reset Network Settings.

2Re-register IMS Profile on Core Network:

Toggle Airplane Mode ON for 30 seconds to send a SIP REGISTER de-registration string, then toggle OFF to force a clean P-CSCF handshake.

3Clear Carrier Services Cache (Android):

Go to Settings -> Apps -> See all apps -> Enable Show system.

Locate Carrier Services and IMS Service -> Select Storage & Cache -> Tap Clear Data and Clear Cache -> Reboot the phone.

Prevention & Long-Term Monitoring:

Ensure OS firmware remains updated to prevent baseband stack corruption that breaks SIP UDP/TCP socket keep-alive cycles.

Real-time Transport Protocol (RTP) Silence Suppress / NAT Timeout

Solution:

Root Cause: Carrier Carrier-Grade NAT (CGNAT) Binding Expiry on RTP Streams

VoLTE separates control signaling (SIP) from audio transmission (RTP/RTCP). Audio packets stream over dynamic UDP ports. If a call experiences prolonged periods of low noise or active silence suppression (VAD - Voice Activity Detection), and the device's local NAT mapping table or the carrier's CGNAT gateway has an aggressively short UDP idle timeout (e.g., 30 seconds), the NAT binding collapses. When speech resumes, the gateway drops incoming RTP packets as unknown traffic, triggering a media-timeout teardown after a preset interval.

Diagnostic Verification:

1Perform a test call where both parties continuously speak versus remaining completely silent; observe if silence triggers the drop faster.

2Check if the drop occurs specifically when muted on long conference bridges.

Step-by-Step Fix:

1Disable Adaptive Comfort Noise / Silence Suppression Features:

Open native Phone app -> Settings -> Accessibility or Call Settings -> Disable Noise Reduction or Enhanced Calling Audio features that mute baseline comfort noise generation.

2Toggle IMS Packet Precedence in Cellular Options:

iOS: Navigate to Settings -> Cellular -> Cellular Data Options -> Voice & Data. Toggle from 5G On / VoLTE to LTE (forces baseband modem to renegotiate QCI-1 dedicated bearer parameters).

3Request Network Line Reprovisioning:

Contact carrier support and request a reset of your line's VoLTE Provisioning Profile and PCRF (Policy and Charging Rules Function) QoS Rules.

Prevention & Long-Term Monitoring:

Unmute calls periodically during long conference holds to transmit active RTP keep-alive packets through carrier CGNAT gateways.

IMS Core P-CSCF Congestion & HSS Subscriber Throttling

Solution:

Root Cause: Proxy-CSCF Server Load Balancing Drop

When local cell site density experiences high congestion, the carrier's P-CSCF entry node offloads voice sessions. If the Home Subscriber Server (HSS) fails to re-allocate your subscriber profile to an adjacent S-CSCF (Serving-CSCF) instance due to database queue saturation, the IMS core drops the voice bearer, returning a SIP 503 Service Unavailable or SIP 500 Server Internal Error back to the UE (User Equipment).

Diagnostic Verification:

1Test if calls drop exclusively during peak usage hours (e.g., 4 PM - 7 PM) in high-density urban areas.

2Verify if switching network modes temporarily resolves the problem.

Step-by-Step Fix:

1Force Baseband Connection to Secondary LTE Carrier Aggregation Band:

Disable and re-enable Mobile Data in quick succession.

2Disable VoLTE Temporarily During Core Network Outages:

Android: Go to Settings -> Network & internet -> SIMs -> Toggle VoLTE / 4G Calling to OFF (forces calls to fallback to 3G/2G circuit-switched networks where supported).

iOS: Navigate to Settings -> Cellular -> Cellular Data Options -> Voice & Data -> Select LTE without VoLTE if option is exposed by carrier, or switch primary data to secondary SIM.

Prevention & Long-Term Monitoring:

Report recurrent SIP 503 drop locations to your carrier's engineering team with exact timestamps and cell ID locations.

What physical or environmental transition triggers the call disconnect?

Handover between cell towers while driving or walking (eSRVCC failure)
Transitioning from strong outdoor LTE to weak indoor 4G coverage
Shifting between 5G (VoNR) and 4G (VoLTE) network layers

Enhanced Single Radio Voice Call Continuity (eSRVCC) Handover Failure

Solution:

Root Cause: eSRVCC Target Cell Allocation & B2 Event Measurement Failure

When moving between cell sectors, the network uses Enhanced Single Radio Voice Call Continuity (eSRVCC) or Inter-RAT (Radio Access Technology) handover to transfer active packet-switched (PS) VoLTE sessions to neighboring LTE or legacy circuit-switched (CS) cells. If the eNodeB fails to receive the device's B2 Measurement Report (indicating LTE signal quality dropped below the threshold while target cell signal is adequate), or if target cell admission control rejects the voice bearer, the handover times out and drops the call.

Diagnostic Verification:

1Check signal metrics during movement: observe if Reference Signal Received Power (RSRP) drops below -115 dBm and Reference Signal Received Quality (RSRQ) drops below -12 dB prior to call drops.

2Review device logs for RRCConnectionRelease commands issued without a valid MobilityFromEUTRACommand target.

Step-by-Step Fix:

1Reset Baseband Radio Cache:

Dial *#*#4636#*#* on Android -> Phone Information -> Toggle Mobile Radio Power OFF, wait 10 seconds, then toggle back ON.

2Force Carrier PRL (Preferred Roaming List) / Configuration Sync:

iOS: Connect to Wi-Fi, go to Settings -> General -> About to prompt any pending carrier settings bundle downloads.

Android: Go to Settings -> System -> Reset options -> Reset Wi-Fi, mobile & Bluetooth.

3Swap SIM Card Slot (For Dual SIM Phones):

Move physical SIM card from Slot 2 to Slot 1, as Slot 1 typically routes through the primary RF transceiver array with superior antenna diversity.

Prevention & Long-Term Monitoring:

Keep phone cases clear of heavy metallic or magnetic accessories that impede baseband antenna beamforming during handover signaling.

QCI-1 Default Bearer Degradation Under Low RSRP Conditions

Solution:

Root Cause: Quality of Service Class Identifier (QCI-1) Bearer Preemption

VoLTE traffic is prioritized over regular web data using a dedicated EPC (Evolved Packet Core) bearer assigned QCI-1 (guaranteed bit rate for conversational voice). When moving indoors into weak coverage zones (RSRP worse than -120 dBm), packet loss on the QCI-1 bearer exceeds the 1% threshold defined by 3GPP standards. The eNodeB modem drops the low-quality voice bearer to prevent signaling channel starvation.

Diagnostic Verification:

1Monitor indoor LTE RSRP values via native diagnostic screens (iOS: Dial *3001#12345#* -> Serving Cell Measurements; Android: Settings -> About Phone -> SIM Status).

2Note if data throughput remains functional while voice drops completely.

Step-by-Step Fix:

1Enable Wi-Fi Calling (VoWi-Fi) for Indoor Coverage Offload:

iOS: Navigate to Settings -> Cellular -> Wi-Fi Calling -> Toggle Wi-Fi Calling on This iPhone to ON.

Android: Navigate to Settings -> Network & internet -> SIMs -> Wi-Fi Calling -> Toggle ON and set Calling Preference to Call over Wi-Fi.

2Enforce LTE-Only Network Mode (To Prevent Unnecessary 3G/2G Hunting Drops):

Android: In *#*#4636#*#*, set Set Preferred Network Type to LTE only or NR/LTE.

Prevention & Long-Term Monitoring:

Reference the official Apple Support VoLTE Setup Guide to ensure carrier voice feature availability on your hardware.

EPS Fallback / VoNR to VoLTE Handshake Breakdown

Solution:

Root Cause: Evolved Packet System (EPS) Fallback Inter-System Handover Drop

On 5G Standalone (SA) networks, if the 5G core (5GC) or local gNodeB does not support native VoNR (Voice over New Radio), initiating or receiving a call triggers EPS Fallback. The network redirects the modem from the 5G core back to the 4G Evolved Packet Core (EPC) to establish a VoLTE session. If the N2/S1 interface handover between AMF (Access and Mobility Management Function) and MME (Mobility Management Entity) fails to resolve target IP routing in time, the connection snaps.

Diagnostic Verification:

1Check if the status bar icon reads 5G immediately before placing a call, then switches to LTE or 4G at the exact moment the call drops.

2Verify if 5G Standalone is currently enabled in settings.

Step-by-Step Fix:

1Temporarily Disable 5G Standalone Mode:

iOS: Go to Settings -> Cellular -> Cellular Data Options -> Voice & Data -> Select 5G Auto or LTE (disables pure Standalone 5G voice routing).

Android: Go to Settings -> Network & internet -> SIMs -> Toggle 5G Standalone to OFF.

2Force Device to Attach Directly to LTE Packet Core:

Select LTE as the Preferred Network Type to bypass the EPS Fallback transition process completely while making important calls.

Prevention & Long-Term Monitoring:

Leave 5G network mode on 5G Auto so the OS dynamically manages frequency band stability based on real-time signal conditions.

What behavior occurs when initiating or receiving the VoLTE call?

Call connects, but there is complete silence on both ends for 5-10 seconds before dropping
Immediate 'Call Ended' or 'Call Failed' notice on dial screen without ringback tone
Call drops instantly when toggling Speakerphone, Bluetooth, or Mute options

Sip SDP Media Negotiation & One-Way Audio Audio Server Mismatch

Solution:

Root Cause: Session Description Protocol (SDP) Codec Mismatch (AMR-WB vs AMR-NB)

VoLTE utilizes HD Voice codecs, primarily AMR-WB (Adaptive Multi-Rate Wideband) and EVS (Enhanced Voice Services). During call setup, the two endpoints exchange SDP bodies inside SIP INVITE and SIP 200 OK messages to negotiate audio codecs, payload types, and port numbers. If a carrier gateway or receiving device misinterprets the EVS/AMR-WB codec parameters, no RTP audio socket is constructed. Finding no incoming audio packets, the OS media framework drops the call.

Diagnostic Verification:

1Place a call to a landline vs another VoLTE HD Voice subscriber; if landline calls connect normally but mobile-to-mobile calls drop into silence, codec negotiation is failing.

2Verify if turning off HD Voice/VoLTE fixes the dead-air behavior.

Step-by-Step Fix:

1Reset IMS Service Cache on Device:

Android: Open Settings -> Apps -> Carrier Services -> Tap Force Stop, then clear Storage and Cache.

2Re-provision Line Provisioning Flags:

Dial *#*#4636#*#* -> Phone Information -> Toggle VoLTE Provisioned switch OFF and ON (if switchable on your OS build).

3Toggle Wi-Fi Calling to Override IMS Audio Path:

Connect to Wi-Fi, enable Wi-Fi Calling, and place the call to force audio routing through an IPsec tunnel straight to the ePDG (Evolved Packet Data Gateway).

Prevention & Long-Term Monitoring:

Keep device OS updated to maintain compatible vendor implementations of EVS voice codec headers.

Missing IMS APN Configuration / QCI Bearer Rejection

Solution:

Root Cause: Missing IMS APN Profile or Carrier Account Subscription Block

Unlike standard data browsing which routes over a default APN (e.g., internet), VoLTE requires a dedicated ims APN with specific system flags (APN Type: ims). If an APN profile was wiped during a SIM swap, OS upgrade, or manual APN edit, the phone attempts to send SIP INVITE packets over the general internet APN. The gateway rejects these unauthenticated packets, dropping the call attempt instantly.

Diagnostic Verification:

1Open Access Point Names settings (Settings -> Network & internet -> SIMs -> Access Point Names).

2Check if an entry named IMS exists alongside your standard internet APN.

Step-by-Step Fix:

1Manually Add IMS APN Profile (If Missing on Android):

In APN settings, tap + (Add APN).

Set Name: IMS

Set APN: ims

Set APN Type: ims

Set APN Protocol: IPv4/IPv6

Set APN Roaming Protocol: IPv4/IPv6

Tap three dots -> Save.

2Update Carrier Settings Profile (iOS):

Go to Settings -> General -> About. If an update prompt appears, tap Update to restore missing IMS configurations.

3Contact Carrier Subscriber Management:

Request the agent verify that the SOC Code for VoLTE feature provisioning is active on your billing account.

Prevention & Long-Term Monitoring:

Never delete system-generated APN entries marked ims or ia when modifying default cellular data configurations.

Audio HAL Driver Crash During Transceiver Re-routing

Solution:

Root Cause: OS Audio Hardware Abstraction Layer (HAL) Thread Crash

When toggling outputs (e.g., switching from earpiece to Bluetooth SCO socket or Speakerphone), the OS Audio HAL daemon must re-route the active PCM audio stream. If a third-party application, corrupted equalizer plugin, or driver memory leak locks the audio hardware interface, the HAL thread crashes (audioserver process termination). The baseband modem detects a broken PCM buffer pipe from the application processor and drops the active VoLTE call.

Diagnostic Verification:

1Check if calls drop exclusively when connecting to Bluetooth headsets or enabling speakerphone.

2On Android, capture a logcat buffer via developer tools and search for audioserver or AudioFlinger crash stack traces during the drop.

Step-by-Step Fix:

1Unpair and Clear Bluetooth Audio Devices:

Go to Settings -> Connected devices -> Bluetooth -> Forget connected audio hardware.

Reset Bluetooth settings via Settings -> System -> Reset options -> Reset Wi-Fi, mobile & Bluetooth.

2Disable Third-Party Equalizers & Call Recorders:

Uninstall apps that hook into the system audio recorder or equalizer layer (e.g., Wavelet, Call Recorders, Cube ACR).

3Reboot into Safe Mode (Android):

Press and hold the power button, long-press Restart -> Select Reboot to Safe Mode. Test a VoLTE call to confirm third-party software interference.

Prevention & Long-Term Monitoring:

Avoid installing system-wide audio modifier apps that lack compliance with current Android/iOS background audio service rules.

What specific Wi-Fi Calling (VoWi-Fi) interaction causes the call drop?

Call drops when walking away from Wi-Fi router (Wi-Fi to VoLTE handover drop)
Call drops when stepping into Wi-Fi range (VoLTE to Wi-Fi handover drop)
Call drops intermittently while sitting still on a stable Wi-Fi connection

ePDG IPSec Tunnel Teardown Prior to LTE QCI-1 Establishment

Solution:

Root Cause: Premature ePDG IPSec Tunnel Termination

When connected to Wi-Fi Calling, voice traffic is encapsulated in an IPSec tunnel routed to the carrier's Evolved Packet Data Gateway (ePDG). As you walk away from the router and Wi-Fi RSSI drops below -75 dBm, the OS must perform an inter-technology handover to VoLTE. If the Wi-Fi interface abruptly collapses before the baseband completes the LTE Attach and QCI-1 bearer reservation, the IPSec tunnel collapses, severing the voice stream.

Diagnostic Verification:

1Perform a test call next to your Wi-Fi router and walk toward the edge of coverage; observe if the call drops at the exact moment Wi-Fi disconnects in the status bar.

2Inspect Wi-Fi RSSI metrics in your router admin console during movement.

Step-by-Step Fix:

1Change Cellular Preference to 'Cellular Preferred':

Android: Go to Settings -> Network & internet -> SIMs -> Wi-Fi Calling -> Set Calling Preference to Call over mobile network / Cellular Preferred (ensures VoLTE remains primary and only offloads to Wi-Fi in absolute dead zones).

iOS: Disable Wi-Fi Calling if your indoor cellular coverage is sufficient (RSRP better than -105 dBm).

2Optimize Router Fast Roaming Settings:

Access home router administration portal and enable 802.11r (Fast Transition) and 802.11k / 802.11v to speed up Wi-Fi disassociation decisions.

Prevention & Long-Term Monitoring:

Set Wi-Fi Calling preference to 'Cellular Preferred' to minimize unnecessary inter-technology interface hopping.

IKEv2 Authentication Failure / UDP Port 4500 Blockade

Solution:

Root Cause: Router Firewall Blocking UDP Port 500/4500 (IKEv2/IPSec)

When transitioning an active VoLTE call onto a Wi-Fi network, the device attempts to establish an IKEv2 security association with the carrier's ePDG over UDP Port 500 (IKE) and UDP Port 4500 (IPSec NAT-Traversal). If local router firewalls, SIP ALG (Application Layer Gateway) inspection engines, or strict ISP security filters block UDP 4500, IPSec handshake fails, terminating the voice session during handover.

Diagnostic Verification:

1Test Wi-Fi calling on a public network versus your home network. If drops occur strictly on one router, network port blocking is present.

2Check router configuration settings for active SIP ALG controls.

Step-by-Step Fix:

1Disable SIP ALG on Local Router:

Log into your Wi-Fi router administrative dashboard (typically 192.168.1.1 or 192.168.0.1).

Navigate to Advanced Settings -> WAN / Firewall / NAT Tracking -> Locate SIP ALG and set to Disabled.

2Ensure UDP Ports 500 and 4500 are Unrestricted:

Verify firewall rules permit outbound UDP traffic on ports 500 and 4500.

3Reset Device Network Cache:

Reset device network settings to flush stale IKEv2 security association keys.

Prevention & Long-Term Monitoring:

Keep SIP ALG permanently disabled on consumer routers, as it frequently corrupts modern IMS/SIP header packet structures.

Wi-Fi Router Bufferbloat & High Packet Jitter

Solution:

Root Cause: Bufferbloat-Induced Packet Jitter Exceeding De-jitter Buffer Thresholds

Voice over IP requires extremely low packet delay variation (jitter < 30ms). On congested home Wi-Fi networks, large background downloads fill deep router queues (Bufferbloat), delaying incoming VoWi-Fi voice packets. When packet jitter exceeds the adaptive de-jitter buffer limit inside the device media engine, the system experiences packet starvation and drops the IMS session.

Diagnostic Verification:

1Run a bufferbloat test (e.g., Waveform Bufferbloat Test) over Wi-Fi while monitoring ping latency spikes under load.

2If latency jumps from 15ms to 200ms+ under load, bufferbloat is directly impacting call stability.

Step-by-Step Fix:

1Enable Quality of Service (QoS) / Smart Queue Management (SQM) on Router:

Access router admin portal -> Go to QoS or Traffic Management.

Enable SQM or prioritize the device IP / MAC address as a High Priority Voice Device.

2Shift Smartphone Connection to 5GHz / 6GHz Wi-Fi Frequency Band:

Connect to the 5GHz Wi-Fi band instead of congested 2.4GHz bands to eliminate co-channel RF interference from neighboring routers and micro-appliances.

3Re-evaluate Wi-Fi Calling Usage:

If internet queue latency cannot be mitigated, switch Wi-Fi Calling to Cellular Preferred mode.

Prevention & Long-Term Monitoring:

Deploy network routers with active Smart Queue Management (SQM) algorithms (such as FQ-CoDel or CAKE) to maintain low latency under heavy home bandwidth usage.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website