I'm logging CDR Calls and when I open the Chronicall status there are calls. Yet when I open Call Detail View it is not showing any calls. Also, when I close out of Call Detail View and look at the Chronicall status it shows that there are 0 calls.
If you look under the tomcat logs you might see something like the following:
2019-03-14 13:50:31.047 [ERROR] Problem call: CDRCall(null)
This may follow with some OrientDB errors which is generally because one of the CDR Call Indexes has become corrupt and needs to be rebuilt from the Chronicall server.
You will need to do the following to help resolve this issue:
Stop the Chronicall Server Service
- Login into the OrientDB Database -
Please remember that we should not modify the database. Stick to SELECT queries. If an UPDATE query must be run, please be absolutely sure that the query is correct and have a database backup prepared in case the query fails.
CDR data is logged into a OrientDB database instead of postgres. You can access a SQL interface for this by accessing the server and going to http://localhost:9090/studio/index.html.
- Username is admin
- Password is ChR0n1c@ll1337
The Browse tab will let you enter SQL queries. Keep in mind that OrientDB tables and columns are case-sensitive.
The Schema tab will show you a list of the various tables. Click on the Query All button to do a short search of that table. This is a good way to find the names of the various columns.
- Go to Browse > Schema and scroll down until you find CDRCall, select it to get the following window:
3. Click "Rebuild" under the following index actions, this will take a minute to do automatically
(Keep in mind that it might not let you rebuild the uniqueCallIDIndex, that is okay):
4. After you rebuild them, start the Chronicall service, relaunch your Chronicall browser and you should now start to see calls saving in Call Detail View!