Logs and Troubleshooting

The Logs page provides application and security information required for routine troubleshooting.

Logs support pagination and search so operators can narrow a busy log history.

CDR files are not arriving

Check:

1. The SFTP receiver is enabled.
2. TCP port 22 is reachable from CUCM.
3. CUCM has the correct host, credentials and /incoming path.
4. Windows Firewall or another security product is not blocking the connection.
5. The Windows host address has not changed.

Files arrive but calls are not searchable

Check:

1. Ingestion logs for parsing or processing errors.
2. The search date, time and timezone.
3. The number format stored by CUCM.
4. The active retention window.
5. That the expected CDR file was processed successfully.

Web interface is unavailable

Check:

• The application is running.
• TCP port 3080 is listening.
• Windows Firewall permits access.
• The browser is using the correct host and port.

For local testing, try:

http://localhost:3080

User cannot sign in

Confirm the account exists, is enabled and has the expected role.

An administrator can reset the user's password using the user-management workflow.

Update fails

Review the updater output and application logs. Common causes include:

• Application files being locked by another process.
• An incomplete release package.
• Missing runtime components in a package.
• Insufficient permissions or disk space.

If the update cannot be validated, use rollback rather than repeatedly modifying the installed application in place.

Escalation information

When raising an issue, capture:

• Application version.
• Windows version.
• Approximate time of the problem.
• Relevant log entries.
• Whether the problem affects ingestion, search, reporting, login or updating.
• Whether the issue can be reproduced.