How to Fix ‘We Couldn’t Complete the Call’ Error in Microsoft Teams

Attempting to initiate or answer a one-on-one voice call or join a scheduled group conference in Microsoft Teams only to receive the immediate prompt: “We couldn’t complete the call. With your network connection, there’s an issue with the call setup” prevents critical collaboration. The call typically rings for a fraction of a second before dropping, or disconnects immediately upon answering. In Microsoft Teams, real-time media sessions rely on the Interactive Connectivity Establishment (ICE), Session Traversal Utilities for NAT (STUN), and Traversal Using Relays around NAT (TURN) protocols running over User Datagram Protocol (UDP). When network firewalls block Teams media port ranges, local Teams client caches corrupt, or SIP calling licenses expire, Teams cannot negotiate call handshakes. This tutorial outlines how to diagnose media routing failures and restore clear calling in Teams.

What Triggers the ‘We Couldn’t Complete the Call’ Error in Teams?

Voice and video transmission require symmetric communication across Microsoft Azure media relays. Common failure causes include:

  • UDP Port Blocking by Firewalls or Routers: Enterprise or home firewalls blocking UDP ports 3478 through 3481, forcing call setup to time out.
  • Corrupted Microsoft Teams Client Cache: Damaged temporary token data in the local Teams cache directory preventing ICE candidate exchange.
  • Strict Corporate VPN or Proxy Tunneling: VPN software forcing real-time UDP media packets through high-latency TCP inspection proxies.
  • Outdated Teams Application Build: Running legacy Teams versions that fail to authenticate against updated Microsoft 365 calling infrastructure.
  • Conflicting Audio Endpoint Drivers: Default audio devices becoming disabled, unplugged, or locked in exclusive mode by other applications.

Step 1: Clear the Microsoft Teams Local App Cache

Clearing corrupted cached calling tokens is the fastest and most reliable resolution for client-side call setup failures.

  1. Right-click the Teams icon in the taskbar notification tray and select Quit.
  2. Press Win + R to open the Run dialogue box.
  3. For New Microsoft Teams (work or school):
    • Paste: %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
    • Press Enter, select all files and folders inside (Ctrl + A), and delete them.
  4. For Classic Microsoft Teams:
    • Paste: %appdata%\Microsoft\Teams
    • Press Enter, delete all files and folders within the directory.
  5. Relaunch Microsoft Teams, sign back in if prompted, and test initiating a call.

Step 2: Check Firewall and Open Essential Teams UDP Ports

Microsoft Teams requires direct outbound UDP connectivity to Microsoft 365 IP addresses for audio and video media streams.

  1. Teams prioritises User Datagram Protocol (UDP) for media streams:
    • UDP Ports 3478, 3479, 3480, and 3481 must be allowed outbound across your local router and Windows Firewall.
  2. To verify Windows Defender Firewall rules:
    • Press Win + R, type control firewall.cpl, and press Enter.
    • Click Allow an app or feature through Windows Defender Firewall.
    • Click Change settings, scroll down to Microsoft Teams, and verify that both Private and Public checkboxes are enabled.
    • Click OK.

Step 3: Bypass or Split-Tunnel Corporate VPN and Proxies

Routing real-time media streams through encrypted corporate VPN tunnels often triggers packet fragmentation and ICE negotiation failure.

  1. If you are connected to a third-party or corporate VPN (such as Cisco AnyConnect, GlobalProtect, or NordVPN), temporarily disconnect from the VPN.
  2. Attempt the Teams call while connected directly to your local broadband or mobile hotspot connection.
  3. If the call succeeds without the VPN, your network administrator must configure VPN Split Tunneling to bypass Microsoft 365 Teams media endpoints (e.g. *.teams.microsoft.com).

Step 4: Verify Default Microphone and Speaker Device Settings

If Teams cannot establish an active hardware handshake with an audio device, call setup is aborted automatically.

  1. In Microsoft Teams, click the Settings and more (…) button beside your profile avatar and select Settings.
  2. Click on the Devices tab.
  3. Under Audio devices, verify that your active Speaker and Microphone are properly selected from the dropdown menus.
  4. Click the Make a test call button.
  5. Follow the automated prompts to record a short message and listen to the playback. If the test call completes successfully, your local hardware and audio stack are functioning properly.

Step 5: Flush DNS and Reset Network Sockets

Stale DNS records can route Teams calling requests to decommissioned regional Azure media relays.

  1. Press Win + S, type cmd, and select Run as administrator.
  2. Execute the following commands sequentially:
    ipconfig /flushdns
    netsh int ip reset
    netsh winsock reset
  3. Restart your computer to finalise the socket stack refresh.

Teams Call Setup Troubleshooting Overview

Observed Symptom Underlying Cause Corrective Measure
Call drops after 1 second UDP port 3478-3481 blocked by router/firewall Open UDP ports or allow Teams in Windows Firewall
Error repeats across all contacts Corrupted local Teams client cache Delete contents of LocalCache\Microsoft\MSTeams
Fails only when connected to office VPN VPN proxy inspecting UDP media packets Configure VPN split-tunneling for Teams endpoints
Immediate “Call setup issue” prompt Audio endpoint not initialised Verify audio devices & run Make a test call

Resolving network port blockages and refreshing client cache tokens ensures clear, reliable voice and video calls in Microsoft Teams.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.