Why Can’t a User Make or Receive Calls Even if the Console Appears Normal?

🧭 Overview

If a user is unable to make or receive calls—even though the EvoVoice console seems to be functioning correctly (e.g., the interface loads, buttons are clickable, and no visible errors are present)—there are several common causes to investigate. This guide outlines the step-by-step process to diagnose and resolve this issue.

🛠️ Step-by-Step Troubleshooting

✅ 1. Check if the User Is Logged Into the Softphone

The EvoVoice console alone doesn’t handle audio—users also need to be connected to a softphone (WebRTC, desktop app, or IP phone).

• Ask the user to confirm they see a “Connected” or “Registered” status on their softphone.

• If using a browser, ensure microphone permissions are enabled.

• Try restarting the softphone or browser session.

🔄 Fix: Reconnect the softphone, ensure microphone access, and confirm login status.

✅ 2. Ensure a Device/Endpoint Is Assigned

Calls won’t work if the user doesn’t have an active device or endpoint assigned.

• Navigate to Users > [User Name] > Devices tab.

• Verify that a softphone or physical device is properly assigned and active.

• Look for registration errors or disconnected endpoints.

🔄 Fix: Assign a device or re-register the current softphone if needed.

✅ 3. Verify the User's State Is Set to “Available”

Call routing behavior depends on user states like Available, Offline, or custom states (e.g., Call Forward, Lunch).

• Check the user’s state on the console or admin panel.

• Confirm it is set to Available to receive direct or routed calls.

🔄 Fix: Switch the state to Available to restore call functionality.

✅ 4. Review Call Flow Routing Rules or Schedules

A misconfigured call flow may prevent calls from being delivered or initiated.

• Check if the user is part of a ring group, time schedule, or call forwarding rule.

• Look for conditions that may bypass or block the user during specific times or states.

🔄 Fix: Adjust the call flow logic to include the user under the correct routing conditions.

✅ 5. Inspect Console Settings and Permissions

In some cases, the console UI may appear normal, but actions are restricted due to role limitations or a partial load.

• Ask the user to try the console in Incognito Mode or another browser.

• Admins should verify the user’s role and permissions under Users > Roles.

🔄 Fix: Clear browser cache, switch browsers, and validate user permissions.

✅ 6. Check for Account Suspension or Missing License

Even with console access, users can be blocked from voice services if:

• Their account is suspended, deactivated, or disabled.

• They are missing an EvoVoice license.

🔄 Fix: Re-enable the user account and assign the proper license under the Licensing section.

🧪 Optional: Run Technical Diagnostics (Admin Only)

If the issue persists:

• Check Call Logs under Reports for the user’s extension or ID.

• Look for failed call attempts, SIP errors, or registration failures.

• Use built-in Diagnostics tools if available in the admin dashboard.

🆘 Still Need Help?

If none of the steps resolve the issue:

• Contact Evo Support.

• Include the affected user’s name, extension, and timestamp of the last attempted call.

📌 Quick Reference Summary