Troubleshooting CUBE “No Data Found” in Variphy’s CUBE Analytics

If CUBE CDR data is not visible in Variphy for the current or previous day(s), there could be a few possible causes. Here’s what you can do to troubleshoot in Variphy’s CUBE analytics when data cannot be found.

Step 1) Confirm that Variphy CDR Processing is enabled for the CUCM cluster.

Log in to Variphy. In the setup menu (gear icon), navigate to the Clusters section and select CUBE/IOS. 

Under CDR Processing, the status for the cluster should display “Enabled.”

If the status for the cluster is “Disabled,” enable CDR processing by clicking the settings icon on the right and switching the Enable Database Processing toggle button. Follow the steps in the modal dialog that appears.

Step 2) Confirm that Variphy is receiving CDR data files from CUBE into the proper directory.

For the CUBE cluster, identify the directory location for the saved data files.

Navigate to the directory to view the folder contents:

On Windows: Open Windows Explorer and head to the appropriate directory location.

On OVA/Linux: Open an SSH session via CLI or an sFTP client and navigate to the appropriate directory location.

cd /opt/variphy/data/cisco2901

Since the CUBE FTP CDR delivery is set to run hourly, there may be no files present. Check the ‘Last Modified’ date on the Progress and Processed directories. If it is not the current day, CUBE CDR files are not being delivered to the Variphy server’s expected data directory.

If running Variphy on Windows, check the FTP server logs on the application server.

If running the Variphy Linux OVA, check the VSFTPD (FTP server) logs on the application server using a CLI or an sFTP client (WinSCP, FileZilla, etc.).

sudo cat /var/log/vsftpd.log

One scenario is an FTP failure being logged (account credentials, home directory paths, etc.). However, it is more than likely the logging of CUBE’s hourly connections has ceased, meaning CUBE is not attempting to deliver CDR files using the built FTP configuration for Variphy.

You should now disable CDR processing on the CUBE cluster. Doing so will allow you to check the data directories on the application server to confirm CUBE is delivering CDR files to Variphy without the application processor ingesting the data on its routine.

Step 3) If CUBE CDR is not being delivered to Variphy, you must access the CUBE via an SSH session with a CLI.

You will need to run some checks, redefine the CDR delivery configuration, and bulk copy and delete the CDR files in CUBE flash.

Check the CUBE flash directory for CDR* files. With the existing FTP connection not functioning properly, CDR* data files will pile up in CUBE flash.

show flash:

Check the configuration of the CDR delivery job in CUBE.

sh run | begin gw-accounting file

Run a “push now” command from CUBE to Variphy.

file-acct flush with-close

Check the corresponding home data directory on the application server.

If the Variphy server and CUBE are communicating properly, a file should appear.. 

Restart the FTP push to run on its scheduled time frame by executing a “file-acct reset”. This does not reset the configurations; it only resets the automatic push of files.

file-acct reset

The hourly job should then resume. Check Variphy in one hour to confirm the delivery of new data. 

If a file does not show up within two minutes, it may be necessary to remove the CDR FTP job (GW-Accounting File) in CUBE and redefine it.

config t

no gw-accounting file This will remove the hourly CDR FTP job


sh run | begin gw-accounting file confirms the job has been removed by returning no results

Redefine the CDR FTP job in CUBE.


configure t

gw-accounting file

primary ftp username cisco2901 password Variphy!!

maximum cdrflush-timer 55

maximum fileclose-timer 60

cdr-format detailed

acct-template callhistory-detail


wr mem

Once the configuration is finished, check the application data directory for a delivered CDR file. If no CDR file shows up in the data directory, there may be a firewall or some security measures preventing delivery – FTP port 21.

Once CDR files are being delivered again, the hourly routine should resume.

However, you must still copy and delete the CDR files in CUBE’s flash over to Variphy. You do not want the CUBE flash filling up due to CDR files.

At this point, you will want to use the TCL (Tool Command Language) shell built into CUBE.

This will allow the bulk copy of CDR* files ONLY, not all of flash.

config t

file prompt quiet



set fileList [glob -directory flash: -nocomplain “cdr*”] creates a bulk list of CDR* files only.

foreach file $fileList {copy $file ftp://cisco2901:Variphy!!@} copy command delivers the CDR files from CUBE flash to Variphy’s FTP server.

file prompt alert: This command will reset the file prompting protection in the global configuration

OPTIONAL: You can use this command if you want to copy the files to a TFTP server uploaded to Variphy.

foreach file $fileList {copy $file tftp://}


FTP Copy DeliveryTFTP Copy Delivery

CUBE CDR* files from flash should have been copied over FTP to the data directory in the application server.

FTP Directory on Variphy serverFTP Directory on Variphy server

Optional (TFTP Server copy)

TFTP Home Directory

Now that you have copied all the CDR* files from CUBE flash over to Variphy, you must delete those files from CUBE flash.

delete /force flash:/cdr*

Confirm that all CDR* files that were copied over to Variphy are no longer in CUBE flash.

show flash:

Back on the CUBE cluster, switch the Enable Database Processing toggle on.

Give the application a few minutes to process missing files, then refresh your Variphy history searches, reports, and dashboard widgets. All missing data should then be present.

Check out our weekly workshop recording here for more details on Variphy’s Cisco CUBE Reporting.

Leave a Reply

Your email address will not be published. Required fields are marked *