How to Resolve an Unresponsive ‘Flush Call’ Button and Incorrect Live Call Display in the Activity Tab?

When using Evo Voice’s debug tools, some users may encounter an issue where:

• The ‘Flush Call’ button does not respond when clicked, and

• The Activity tab continues to show live calls that have already ended, causing confusion during troubleshooting or system monitoring.

Here’s how to resolve this issue.

🔍 Possible Causes

These issues typically stem from one or more of the following:

1. Stuck or orphaned call session in the backend SIP system

2. Browser-side cache issues or console desync

3. UI not updating due to session timeout or frontend rendering delay

4. Backend database not cleared due to failed signaling or improper call termination

✅ Step-by-Step Troubleshooting

1. Refresh Console View or Debug Interface

• First, try performing a manual refresh of the debug or Activity tab.

• Use Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to force a hard refresh.

• This ensures the page reloads without using cached data.

⚠️ A regular refresh (F5) may not clear stale session states.

2. Clear Browser Cache (Debug Mode)

• If the interface remains unresponsive:

  • Open the browser’s Developer Tools (F12 or Option + Cmd + I)

  • Go to the Network tab and check Disable cache (while Dev Tools is open)

  • Reload the page again using hard refresh

This helps eliminate UI glitches due to JavaScript memory state or outdated session data.

3. Check for SIP Session Lock or Hung Calls

• Navigate to the SIP Debug or Call Logs tab and verify if the call is still listed as active even after the flush attempt.

• If the SIP session ID still shows as active:

  • The call might not have been terminated properly.

  • Contact Evo Support to force-clear the session from the backend or initiate a manual flush using administrative tools.

4. Use Backend Flush (Admin Access Only)

If the “Flush Call” button in the UI is non-functional:

• An Evo admin or engineer can access the backend to manually flush or clear stale call sessions.

• This may involve clearing Redis cache entries, SIP session states, or triggering cleanup via API.

5. Report for Persistent Cases

If this issue occurs repeatedly, collect the following and report to Evo Support:

• Timestamp of the affected call

• Caller's number or internal ID

• Screenshot/video showing:

  • The Activity tab with the ghost/live call

  • The unresponsive Flush Call button

• Your browser and OS version

This allows the engineering team to:

• Check if there’s a bug in session cleanup

• Determine if the issue is frontend-only or linked to backend signaling

✅ Summary

To resolve an unresponsive Flush Call button and incorrect live call display:

1. Hard refresh the debug interface

2. Clear browser cache (in Dev Tools)

3. Verify the SIP session backend (for stuck calls)

4. Contact Evo Support to force flush the call if needed

5. Report details if the issue is recurring