Cisco CVP

If you are using Cisco Contact Center then you are generating the application logs from Cisco Customer Voice Portal (CVP), and although these events might be a little arcane, they hold a great deal of detail about how calls are flowing in UCCE, with detail around SIP, IVR and ICM parts of your calls. As with almost everything Sideview does, this is a very ​“bottom up” way of looking at UCCE but it can be very powerful for both fast root-cause analysis and also large scale reporting and monitoring.

Furthermore when you stitch together the whole call from the SBC through SVP and ICM and CallManager, the CVP fields can be an essential piece of the puzzle. Stitching all this together for individual calls may sound amazing but… we actually mean also stitching them together en masse across huge numbers of calls and long time ranges (Welcome to Splunk!). 

The core of the ​“stitching” is ​“ciscoguid” and yes we can extract these critical guids across CUBE, Oracle SBC, CVP, ICM (from database inputs), and CUCM itself. 

One Note: This is a very new integration, in that it only released in August 2026. The bad news on that, is that as of this writing the TA_​cisco_​cvp app is not particularly complex. The good news is that our team is going to be iterating on it so when you send any feedback in, large or small, it will absolutely influence the course and the pace of the app’s evolution. Plus we’d love to hear from you.

Installation

Our TA_​cisco_​cvp is simply available on Splunkbase. Install it on your Indexers, or if you have a simple ​“standalone” Splunk deployment with indexing and search both happening on one host, install it on that instance. 

From that point on you can ingest data with sourcetype=“cvp” and it will be indexer according to the app’s index-time configurations.

Note that the app has no search-time configuration (see it’s sister app ​“SA_​cisco_​ucce” aka Sideview’s ​“Supporting App for Cisco UCCE”, releasing soon. Contact us if you have questions