Home Troubleshooting Issue: Console Not Showing Incoming Calls but Phones Ring

Issue: Console Not Showing Incoming Calls but Phones Ring

Last updated on Jun 26, 2025

Overview

This article addresses the issue where incoming calls ring on physical phones or softphones, but do not appear on the Evo Console. This affects receptionist workflows and call handling visibility, especially in multi-location setups.

Affected System

  • Evo Console

  • EvoVoice Softphone

  • Receptionist or Shared Extension Workflows

Reported Symptoms

  • Console UI does not display incoming calls

  • Callers ring on the phone but are not shown in the console

  • Receptionists are unable to answer from the console

  • Issue persists across multiple locations

Confirmed Cases

  • Issue affects Amata offices across multiple sites:

    • 77 W Wacker

    • 161-16 / 161-17

    • 150SW

  • Receptionists at different branches experienced same problem

Possible Causes

  1. Console Not Synced with SIP Events:

    • SIP INVITE not reaching the console’s listener

    • Console app not pulling or displaying active call events

  2. Softphone or Phone Answering Call First:

    • If a call is answered via SIP endpoint before console fetches it, console may not update

  3. Local PC Issue:

    • Console may be frozen, outdated, or running in a stale session

    • Background service crashed (if applicable)

  4. Duplicate Registrations Causing Conflict:

    • Console and softphone using the same SIP extension may compete for registration

  5. VPN/NAT Issues:

    • Console hosted behind VPN/firewall causing signal delay or rejection

    • SIP signaling packets dropped or misrouted

Troubleshooting Steps

🧪 Step 1: Restart Console

  • Fully close the console application and relaunch

  • Refresh call list or dashboard if available

🧪 Step 2: Test Softphone vs Console Visibility

  • Confirm that the softphone rings and can answer calls

  • Compare if console sees the same events or remains idle

🧪 Step 3: Confirm Extension Configuration

  • Check which SIP extension is assigned to the console

  • Ensure console does not share the same SIP extension as another live SIP client (like a softphone or phone)

🧪 Step 4: Check for Background Services

  • On some deployments, console relies on local listeners or real-time polling

  • Make sure background services are not disabled or blocked by antivirus/firewall

🧪 Step 5: Network Check

  • If the user is remote, check for active VPN or proxy

  • Disable VPN temporarily and see if console behavior changes

🧪 Step 6: Logs Collection

  • If console has internal logging enabled, export logs during an affected call

  • Request SIP server logs to confirm if console SIP messages are reaching the server

Resolution Steps

✅ Option 1: Ensure One Active SIP Device Per Extension

  • If console and phone share same SIP login, pick one or split into separate extensions

✅ Option 2: Clear Console Cache / Reinstall

  • Some outdated installs cache UI or events; a fresh install or clearing user data may fix

✅ Option 3: Disable VPN or Route SIP via Public IP

  • If console fails only when on VPN, reroute or exclude console traffic via split tunnel

✅ Option 4: Reconfigure Console Registration

  • Confirm SIP username/password match console settings

  • Reconnect with fresh credentials if session is stale

✅ Option 5: Server-Side Sync Check

  • Ensure the SIP server pushes or allows parallel visibility

  • Check if server is throttling or filtering calls to multiple endpoints for the same user

Prevention Tips

  • Never assign a shared receptionist extension to multiple active devices

  • Reboot consoles daily or use auto-refresh scripts where applicable

  • Keep console software updated to latest build

  • Monitor backend for real-time sync failures if hosted centrally