Cisco CDR Reporting and Analytics
Overview
Details
Note that this isn't a package of content, but more a tank that you drive around in your data. You wont find a leftnav full of canned reports to click on (that "don't quite fit"). Instead you get an open flexible framework to investigate anything, drill down into anything, report on anything, over anything, by anything. (occasionally with hands-on help from Sideview Support. =)
Your team can have better day-to-day call flow visibility AND flexible reporting for CallManager.
- Quickly see all calls matching any search filters.
- Drilldown at any time to thoroughly investigate a particular call.
- Click your way to pretty much any report over any combination of fields.
That third bullet sounds a little crazy - what about some examples?
You can:
- create reports around concurrent calls and dropped calls.
- create a chart of usage stats about your hunt groups.
- see and share inbound/outbound call stats by agent.
- see inbound/outbound call stats by department.
- create custom call quality reports and dashboards (MOS, jitter, latency, packet loss).
- build utilization reports by device, device_type, sites, buildings, you name it.
- drilldown at any time from any report, back to the call view, to inspect and sanity check.
- but really, pretty much anything. Try it and see.
What are these, reports? dashboards? alerts?
Yes. For any of those use cases (and any you can dream up), you can:
- create graphs, charts, tables, and mapping visualizations of various kinds and package them into dashboards if you like.
- set up alerting around anything - dropped calls, quality, volume thresholds.
- share any and all of the above as dashboards with different teams and colleagues.
- automate dashboards you created, to send pdf’s of themselves out every day/week.
What about my report that I don't see listed here?
Contact us and we'll help you learn how to create what you need for your own “somewhat unusual” CallManager deployment. There are over 200 fields (Check them out here) and if you can in principle calculate the thing you need from some number of those fields, in some product or by hand, then there’s a way to have the app do it.
Can I try it out?
Yes you can download a free 90 day trial from this site right now, and set the whole thing up yourself with your own live data, in about 30 minutes. See our installation and setup docs here.
Pricing
The app is priced by the size of your CallManager deployment - specifically the total number of User Licenses and Unassigned Device Licenses that are in use, in CallManager itself. At and below 400 such licenses in use, the cost is only $1,200 per year, but we have a range of customers at all scales including beyond 50,000 licenses in use. Send us a screenshot of the total licenses in use from PLM, or a screenshot per cluster of the "License Usage Report" in CM Admin and we can let you know the exact cost.
Splunk Enterprise - do I need it?
Yes. The majority of our prospects are already Splunk Enterprise customers, and if this is you, this app will likely add only a negligible additional load to ingest the CallManager data that it needs. If you're not, Sideview is also a Splunk Reseller in North America so we can help you on that side.
How about Splunk Cloud?
Yes the app is vetted for Splunk Cloud. We do recommend that you contact us before proceeding though.
What versions of CUCM are supported?
CUCM 7.0 up to the current release 12.X
Release Notes
Version 5.0.9
Version 5.0.9 (April 12th, 2019)
> Improved error messaging when underprivileged users attempt to update
the app's license string, and when invalid licenses are submitted.
> Removed the embedded app TA_cisco_cdr, as this has now been released
separately on Splunkbase. NOTE - versions posted on Splunkbase did not
have have the TA's in them so this only reflects a change for users
downloading from the Sideview website.
> Fixed a bug where orig_device_type, dest_device_type and device_type
fields would not populate correctly for non-mgcp gateway devices.
> Implemented a small improvement for the device_type field on individual
call legs. If both types are the same, the field now only holds the single
distinct value
> Implemented a subtle fix to what the app calls its "union fields", (group,
name, subgroup, ip_addr and device_type) so that in the aggregated call
results, these fields now only list the distinct values.
> Improved the Groups lookup's handling of wildcarded numbers by havi
Version 5.0.8
Version 5.0.8 (March 12th, 2019)
> Improved the "to" and "from" fields so that if one of the geographical
fields like city OR state is blank, it does not fall all the way back to
displaying only country (this can happen with wireless numbers where there
is no city associated)
> Raising the minimum version asserted by the app, from Splunk Enterprise 6.2
to Splunk Enterprise 6.4, as our new license endpoint was found to be only
compatible with 6.4 and up.
> Fixed a bug when adding a dashboard panel to a shared dashboard not owned
by the current user. Previously this would fail with a confusing 404 error.
> Fixed a bug when creating a new dashboard entirely, where the dashboard
panel creation would fail with "ERROR 400 Cannot create an object with
empty or all whitespace name"
> When saving a new report, sharing the report with others now works properly.
> When creating a new dashboard for new dashboard panels, the UI now prompts
you if your desired dashboard name contains invalid charact
Version 5.0.7
Version 5.0.7 (March 1st, 2019)
> Fixed a critical bug for Cloud users and users downloading from Splunkbase
that effectively barred all non-admin users from the product.
> Health checks page can now be run even when product lacks a valid license.
> Filtered out unnecessary "Successfully loaded lookup file" UI messages.
> Added a warning to users who attempt to enter raw numeric terms into the
'search filters' field, as this is not supported and will return 0 results.
Version 5.0.6
Version 5.0.6 (February 27th, 2019)
> Fixed a common problem where license strings pasted into "Update License"
would fail if they had an extra leading or trailing space character.
> Improved the fix done in 5.0.5 around the "Sideview Utils not installed"
error case to no longer require a custom module.
Version 5.0.4
Version 5.0.4 (February 4th, 2019)
> Fixed a bug where if you were using * as a wildcard in your groups lookup
entries the Extension Detail page for matching numbers would fail to list
the name, group, subgroup information.
> Migration check added, to look for old saved reports that have ui_edit_view
specified but no ui_context. Since these will be unable to reload themselves
in the specified view they are now migrated to load in the default splunk
'report' view.
> the Setup Groups page now gives users the ability to download a copy of the
groups lookup as a csv or to open it directly in Excel.
> Fixed a bug around the "save report" buttons - the resulting reports would
reload fine in the Sideview UI but the underlying savedsearch stanza had an
extra "search" prepended to the SPL that would make it always return 0
results when run from core splunk interfaces and from the scheduler.