1. Symptom or Need

When you try to manage an IVR or a Routing Point, you see the following error message:

• "Error loading voice routing DN, please try again later." This error prevents the opening or editing of IVR or Routing Point routing points, blocking the configuration of your voice flows.

2. Context / Scenarios

• Affected service: IVR - RP - Scripting - Routing Point.
• Platform: Wolkvox Manager.
• Scope: The problem can be local (affecting only one computer or user), or general (affecting the entire operation).

3. Answer / Solution

Initial information

To escalate the case, please keep the following information in mind:

• Name of the affected operation.
• Number of positions or agents affected.
• Percentage of affected.

Pre-scaling validations

• Temporary File Cleanup: Delete your operating system's temporary files (%temp%) and restart the Wolkvox Manager application. Sometimes corrupted files in the local cache prevent data from loading.
• Cross-test (User vs. Computer): Try logging in on a different computer using the credentials of the user experiencing the error. If the error only occurs on one computer, the problem may be local to that workstation.
• On the computer where the error occurs, try logging in with a different user to see if the problem also occurs with that user.
• Network change: If possible, connect the device to a different network or segment (for example, a guest network or mobile data) to rule out firewall blocks or corporate network restrictions.
• Version check: Verify that you have the latest update of Wolkvox Manager. Sometimes, trying an older version or reinstalling the current version resolves compatibility issues.
• System Resources: Ensure your equipment meets the technical requirements (available RAM and CPU). An overloaded system can disrupt the loading of critical services.
• Remember to verify compliance with the < Workstation Requirements >. Wolkvox Technical Requirements
• Check for updates installed on your computer.
• Update your Windows version if required.

4. Possible Causes

Local file corruption: Damaged operating system or application cache.

Outdated version: Incompatibility between the installed Manager version and recent updates.

Network Restrictions: The Firewall or Proxy might be blocking the port or address needed to load the DN.

Hardware Resources: Insufficient RAM or degradation of the user profile on the computer.

5. Considerations

Technical Requirements: It is important to validate compliance with the Technical Requirements for better platform performance and to avoid loading errors.

Alternative Solution : In cases where the error persists only on one computer after all cleanings, the computer could be considered with the IT team for formatting that workstation.

Escalation Information: If the error persists after performing these tests and/or validations, escalate the case to the service desk, informing them that temporary files have already been cleaned and tests have been carried out on other equipment.