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 or 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, to inspect and sanity check the calls themselves.
- 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 even 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). If you can in principle calculate the thing you need from some number of those fields, in some product or by hand, then we can show how to make the app do it.
Can I try it out?
Yes you can download the app from Splunkbase or from this site, and you can get a 90 day trial license string from this site. You can 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 from below 100 to above 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
What are the actual data sources that it uses?
- CUCM CDR - through Callmanager's own "external billing server" mechanism, CUCM will basically SFTP this data right to Splunk. See our install docs for full steps.
- CUCM CMR - these are the call quality records, and they come in via the same mechanism
- CUBE CDR - This is an optional secondary data source. see docs for more details
- Syslog - Although the App's UI does not currently integrate anything from the syslog events yet, we do have documentation on how to pull them in.
However if the data you're hoping to work with isn't in that list, Feel free to contact us anyway!.
Release Notes
Version 5.2.3
-- Fixed a typo in the concurrency searches if you did not have a split-by
field set. Improved test coverage to avoid regressions in this area in
the future.
-- Updated python to include latest version of libphonenumbers
-- Updated the "npa-nxx-lata-clli-ocn-location" lookup. This is the piece
that allows the app to take a north american number with just areacode
and exchange, and create fields with city, state, zip, CLLI, OCN,
CompanyType, latitude and longitude.
Version 5.2.2
-- Fixed some critical problems that were introduced with 5.2.1's new field
extractions for gateway, device_type and type fields. Chief among these was
a problem where FXO ports on MGCP gateways were getting misunderstood by
5.2.1 as calls to internal devices rather than outgoing calls.
-- Fixed a bug in the Call Concurrency and Gateway Utilization page that only
affected tandem calls, where the concurrency numbers for those gateways
would be undercounted.
-- Fixed an obscure bug where if you attempted to use one of the dateTime*
field as a search term, and you used it with a comparison operator like ">",
on multi-leg calls, the filtering would not work.
-- Fix made to our first-time-run and migration script to make it not error
out when run in python3 on splunk 8.
Version 5.2.1
Unfortunately Splunkbase still truncates release notes to only 1000 characters. To read the full release notes for 5.2.1 visit the release notes page on our website.
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/
Version 5.2
Splunkbase still truncates release-notes to 1024 characters so unfortunately to read the release notes you have to go to the following URL:
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/
Version 5.1.5
Splunkbase truncated release-notes to 1024 characters so unfortunately until that is fixed you have to go to the following URL to read the full release notes:
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/
Version 5.1.4
Splunkbase truncated release-notes to 1024 characters so unfortunately until that is fixed you have to go to the following URL to read the full release notes:
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/
Version 5.1.3
Version 5.1.3 (August 26th, 2019)
> Converted the encoding of a number of static file-based lookups from ascii
to UTF-8 to allow customers to more easily translate the english language
content there into a local language.
> Added a key to server.conf so that when admins update the sideview license
on any Clustered Search Head, that license change will be propagated to the
other SHC members.
> Improvements to the app_setup/migration script so that it better handles
unexpected cases where the clusters/devices/groups/cidr lookups on disk
are found to be empty. It will now detect this case and attempt to replace
the contents of the file with the corresponding *.default.csv file.
LIST IS NOT COMPLETE - UNFORTUNATELY SPLUNKBASE TRUNCATES RELEASE NOTES.
FOR FULL RELEASE NOTES SEE OUR WEBSITE.
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/
Version 5.1.2
Version 5.1.2 (July, 2019)
> Fixed a bug where when using max(concurrency) in the General Report view,
your "bins" setting would be ignored and a default bins ceiling of 400
would get used instead.
> Fixed a bug in Browse Extensions, and Browse Devices, where if you entered
values into a text field and then without changing anything else clicked
the submit button instead of hitting the enter key, the values you entered
would be ignored.
Version 5.1.1
Version 5.1.1 (July 11th, 2019)
> Made a change so that if the Splunk instance is a Search Head Cluster and
someone tries to post a new license string into the Update License page,
it takes no action and gives them a helpful error.
> Snuck in a semi-secret feature whereby concurrency reports can be done in a
limited fashion within General Report and Browse Calls.
> Updated the "npa-nxx-lata-clli-ocn-location" lookup.
> Updated python to include latest version of libphonenumbers
Version 5.1
Version 5.1 (June 2019)
> Major improvements to both functionality and usability of the Browse
Devices page.
> Devices lookup now can hold an additional column "productName". When
present this creates fields origProductName and destProductName.
> Device Detail page now has an additional tab that displays additional
summary details like unicodeLoginUserId values and numbers associated with
the device, as well as any values that our SA_cisco_cdr_axl app may have
pulled from CallManager via AXL.
Version 5.0.10
Version 5.0.10 (May 14th, 2019)
> Removed the CSR and SCSR field from the field gallery because we realized
that these fields don't actually exist in the CMR itself yet.
> Added CS_total and SCS_total as new fields on the calls, which are the
total seconds of concealed speech and the total seconds of severely
concealed speech, across ALL CMR associated with the given call.
> Added CSR_overall and SCSR_overall fields, which are respectively the
CS_total/duration_total, and SCS_total/duration_total.
As such these represent reliable concealed speech ratio metrics for any
devices reporting CS and SCS.
> Fixing a bug in the transfers and legs fields, where if you used them
as a split-by field in reporting, they would get very significantly
overcounted, as represented by the range numbers in the legend for the
split by values.
> Call Detail view now displays the time of any CMR that are present, either
by listing the value of its dateTimeStamp field or failing that, presenting
the ti
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.