icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

We are working on something new...

A Fresh New Splunkbase
We are designing a New Splunkbase to improve search and discoverability of apps. Check out our new and improved features like Categories and Collections. New Splunkbase is currently in preview mode, as it is under active development. We welcome you to navigate New Splunkbase and give us feedback.

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Cisco CDR Reporting and Analytics
SHA256 checksum (cisco-cdr-reporting-and-analytics_73.tgz) 318598540d31247ccda5a001738f592a9a02605a2583b412644fc8c33871e084 SHA256 checksum (cisco-cdr-reporting-and-analytics_721.tgz) 2ceb2bcd0786551a87a6f2d0660910c7711580da53cca1b61a18d6cc2dc06ae4 SHA256 checksum (cisco-cdr-reporting-and-analytics_71.tgz) 7ba08311ded3c516df49857c7212780c51347b0a60fd709bbe6c5455d0f09655 SHA256 checksum (cisco-cdr-reporting-and-analytics_70.tgz) 2db42a638c72bc7a56dbbe4c4204546828bc0bda065efe84f09bfae83da2b116 SHA256 checksum (cisco-cdr-reporting-and-analytics_661.tgz) 32c1a5d35c76f642f75cdffe234e0d3e35e6852a64865b72fd84ed0abbc727bd SHA256 checksum (cisco-cdr-reporting-and-analytics_660.tgz) 6f0c63adbc36874f751ea7762071890971a2597061e1e35e909a6112f5c7846a SHA256 checksum (cisco-cdr-reporting-and-analytics_653.tgz) dc082da6d9e0ab04ff1a35b88e2dafa891b183c7e4d2203013585c0ef2f2a929 SHA256 checksum (cisco-cdr-reporting-and-analytics_652.tgz) d75b0aac3be2e8a52317f7b47cbc2fe7527c1635fdddc727197ac9e020168654 SHA256 checksum (cisco-cdr-reporting-and-analytics_641.tgz) 9dfeec185c8655cc5c898426c4515fc204cd16a73224bea38c03c46c6db84a8f SHA256 checksum (cisco-cdr-reporting-and-analytics_64.tgz) c9fb3ba8c174ef45896f799b1c8dc6695117ba9c9e3f442e6ff074a41d3503e2 SHA256 checksum (cisco-cdr-reporting-and-analytics_639.tgz) 8615e09a799a5b4c98db3a4ae7f200d0bc0de927a19f2779ff3c0248eefc63e8 SHA256 checksum (cisco-cdr-reporting-and-analytics_638.tgz) e29a396849849ebd5e000171cdb070f991f4ef8fdbb6886c86388336a6f7fb66 SHA256 checksum (cisco-cdr-reporting-and-analytics_637.tgz) 9a73a96f8d9f0cb9f25709722e1f37dee7cd72f1080403d66fa7857a3f318a61 SHA256 checksum (cisco-cdr-reporting-and-analytics_636.tgz) d685c4f085fa585b4bbbcde64d34f7d67b05978c85b35ffe39d41e2be98b61e6 SHA256 checksum (cisco-cdr-reporting-and-analytics_635.tgz) 7f35c526ab9172e4fb6f21c9ae61434517d17b96302b018f8c9b5a8193d9c36b SHA256 checksum (cisco-cdr-reporting-and-analytics_634.tgz) 9370808c86ad36e5cd566b52fd526e98c5f585d95eacdd2db732ddf0ddbba161 SHA256 checksum (cisco-cdr-reporting-and-analytics_633.tgz) f7f4c5d07b26cac78b9bf79e57ab71cad8a1479b4be0542512f49e3ee0f439ad SHA256 checksum (cisco-cdr-reporting-and-analytics_63.tgz) cb4ee6a34e4c25c71e59ea79ea30eec46e16fa719db2067538f23ec40397b86e SHA256 checksum (cisco-cdr-reporting-and-analytics_622.tgz) f6e9cc12b38facb99fe309ad44c21ca7989200160db37f8f72af81bd792f5bb2 SHA256 checksum (cisco-cdr-reporting-and-analytics_621.tgz) d368efeeb96df507be430bb2893e3acc085a86573463ecb5ae7fdbcc37050c27 SHA256 checksum (cisco-cdr-reporting-and-analytics_62.tgz) 428775c8c074366f2e7537a2db316eb98440064335b4a4b76c7365c984e31ee8 SHA256 checksum (cisco-cdr-reporting-and-analytics_61.tgz) d2ee4dbac76d68611f1d6e73fcb4d97d1fb0e031e7bf7729181954589a24b55d SHA256 checksum (cisco-cdr-reporting-and-analytics_608.tgz) 99d8320e92e72516666ac3e72dbac32b0e52c76e56cebec40e2ba677b757dd0b SHA256 checksum (cisco-cdr-reporting-and-analytics_607.tgz) 9ac7b8197f4a85708b2f8355762941f371ad5f558e99145559e5eedbbe5ea0be SHA256 checksum (cisco-cdr-reporting-and-analytics_606.tgz) a4e829cb933d59c27b484c3fe3ef06c0613058ccc364bb541532ec5bebb1a2bd SHA256 checksum (cisco-cdr-reporting-and-analytics_605.tgz) bc71a1d7ea5481949417bcc21c456a9e0a3aae8f0359687ff788d54c2a3effb2 SHA256 checksum (cisco-cdr-reporting-and-analytics_604.tgz) d3e680c5222720702ed30b6a96ac50e3df3a731c2dbf9bcaddf9889184cd70e5 SHA256 checksum (cisco-cdr-reporting-and-analytics_603.tgz) 731f5dac467f0b5753710fa84e60d9b6486fbea2a289be279a19062c9aec037d SHA256 checksum (cisco-cdr-reporting-and-analytics_602.tgz) 1282b83df3d2c9852bdeadb1e2424a8864b3e6d827c41d6db0930d356a94493e SHA256 checksum (cisco-cdr-reporting-and-analytics_601.tgz) 1195f29eb741c664ad19921c8c6454ad921931d41728b07f3b9a524768209dd2 SHA256 checksum (cisco-cdr-reporting-and-analytics_60.tgz) 15a176a262378f5e7fb67fdb3f1f2563c462f68fb0e4a30d652571df663bb642 SHA256 checksum (cisco-cdr-reporting-and-analytics_539.tgz) 4fa9647f1e60e64d5e4494d22eacfe5fa023f5230b5b3abbbe641ca8836c35aa SHA256 checksum (cisco-cdr-reporting-and-analytics_538.tgz) 7ac3fa426dcab017643ff53fa2f3f3f6c554107ca434dde0db32c08f6eea9613 SHA256 checksum (cisco-cdr-reporting-and-analytics_537.tgz) 05aafd298c2646a4c0694876056ae5c43cc711e65418c72246cad11b119d5e25 SHA256 checksum (cisco-cdr-reporting-and-analytics_536.tgz) 7a6d3e1ed3e912820096fe1737c6a3a36ba8b19a462fd301fc9f673fd76c9f23 SHA256 checksum (cisco-cdr-reporting-and-analytics_535.tgz) 9ad6e9d06b1f67fb30ff87d72903beb1fbb30738f92f9bdfbc8f11c0ab206ead SHA256 checksum (cisco-cdr-reporting-and-analytics_534.tgz) 3a8d73e2c242b9a0a9df1954f37f77c166295b78c12af2229054cff54827888e SHA256 checksum (cisco-cdr-reporting-and-analytics_532.tgz) 58ba14b77f8360a82732b58e2f9d290d3712b55f6a7ad343ac2f39e0957ccff1 SHA256 checksum (cisco-cdr-reporting-and-analytics_531.tgz) 24bf35a829fc257c7396dd6fd583c1f41914d30ee874e4ff971fbff4cb0540ee SHA256 checksum (cisco-cdr-reporting-and-analytics_53.tgz) 5a0fd2b6d5d9410fab76504f156e664eee75a403a3d286e15357c1ea03e9e664 SHA256 checksum (cisco-cdr-reporting-and-analytics_526.tgz) da6e0c09c811f768a3a4692cc6a3dc743cc8ea4d858050325adb6a64722977eb SHA256 checksum (cisco-cdr-reporting-and-analytics_525.tgz) 11e648f968a510f3f35f00b334ab86b748723d1af1122d467b3ba19d5d891361
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

splunk

Cisco CDR Reporting and Analytics

Splunk Cloud
Overview
Details
This commercial app gives your team greatly increased visibility, monitoring, and reporting functionality around Cisco Unified Communications (aka CUCM / CallManager), whether you're a small organization with a hundred phones or one of the largest companies in the world.

Whether troubleshooting individual calls or building high level reporting, it helps you visualize and understand in all areas: agents, users, and huntgroups; concurrency and utilization; call flow; call quality; call volume; devices; failed calls; locations and sites; and audits and compliance.

Your team can trust it as their day-to-day tool for navigating call data from your Cisco CallManager deployment, and it can also become their main tool for building custom reports, alerts and dashboards around that data. This is true whether it’s a standard report you’d expect or a custom report that nothing else has been able to provide.

Note that this isn't a package of content, but more a tank that allows you to drive around in your data. You won’t find a leftnav full of canned CDR 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 =).

It is available as a free 90-day trial, and you can download and set it up today in less than 30 minutes.

Your team can have better day-to-day call flow visibility AND flexible reporting for Cisco Unified Communications

  • 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:

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,700 per year, but we have a range of customers at all scales from below 100 to above 150,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 or Splunk Cloud 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 14.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
  • Webex Cloud (specifically Webex Dedicated Instance) - essentially the same data as onprem CUCM is available and will work out of the box with the app.
  • CUBE CDR - This is an optional secondary data source. see docs for more details
  • Oracle SBC CDR - this is in a private beta at the moment but contact us to learn more.
  • 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 7.3
March 20, 2024

Unfortunately Splunkbase truncates release notes at only 1000 characters, which is not enough for a summary of this maintenance release.
Fortunately you can always read our release notes on our website - https://sideviewapps.com/documentation/cisco-cdr-reporting-analytics-release-notes

Version 7.2.1
Feb. 20, 2024

-- Fixed a problem that affected customers that use Search Head Clustering (SHC) when they updated from pre-7.2. The bug was that the devices lookup would end up with incorrect fields loaded. This issue is fixed such that customers updating from pre-7.2 to 7.2.1 or later will not be affected.
-- Fixed a bug for customers who have multiple "data types" loaded in the app. When a report was saved using "save report", the selected data_type(s) would not be saved correctly.
-- Fixed a bug for customers with multiple data_types enabled, where dashboard panels would be created without the proper drilldown logic to set the data_type pulldown in Investigate Calls back to the way it had been when the chart was saved.

Version 7.1
Dec. 15, 2023

-- Functionality -- Along with changes in Canary 1.7, the Cisco CDR app now supports dark mode.
-- Investigate Extensions, Investigate Groups and Investigate Gateways pages now have optional fields to list total/incoming/outgoing/tandem duration in minutes (as opposed to values like "08:53:44").
-- Fixed a bug around dashboards created with our "create dashboard panel" app. The app would add an XML declaration when creating new dashboards and this would work fine. However it would then trigger a bug in Splunk's SimpleXML Editor later, where the editor would add an encoding attribute to the declaration and this attribute would cause the dashboard-level 'dark mode' to never work for that dashboard.
-- Updated to the latest version of libphonenumbers, the python library the app uses to parse DN's to extract country code, area code etc for all phone numbers worldwide.
-- Pulled new NANPA data into the "npa-nxx-lata-clli-ocn-location.csv" lookup.

Version 7.0
Nov. 9, 2023

Unfortunately Splunkbase truncates release notes to only 1000 characters, which is not enough to summarize the changes in this release. However you can always view our release notes on our website at https://sideviewapps.com/documentation/cisco-cdr-reporting-analytics-release-notes

Version 6.6.1
Sept. 7, 2023

-- Functionality - Site Detail page now has a 'call quality' tab.
-- Further improvements and logic fixes to the action menu options in Investigate Calls.
-- Fixed a regression introduced in 6.6. where the Chart view would always show both the chart and the table regardless of which tab was selected.
-- Fixed a bug where the action menu options for the duration field on multileg calls would not work correctly.

Version 6.6.0
Aug. 29, 2023

Unfortunately Splunkbase truncates release notes to a relatively small number of characters, so we are unable to summarize our release notes adequately here.

Fortunately you can always see our full release notes on our website at https://sideviewapps.com/documentation/cisco-cdr-reporting-analytics-release-notes

Version 6.5.3
July 11, 2023

Unfortunately Splunkbase truncates release notes to only 1000 characters and that limit is not sufficient to summarize the fixes and improvements in this particular release. Fortunately you can always read our release notes on our website at https://sideviewapps.com/documentation/cisco-cdr-reporting-analytics-release-notes

Version 6.5.2
May 18, 2023
  • Fixed a regression that greatly lowered search efficiency when using the "number" field in Investigate Calls.
Version 6.4.1
Oct. 27, 2022

Unfortunately Splunkbase truncated release notes at only 1024 characters, and this is not sufficient to summarize the important changes in this release. You can however always read the release notes for Cisco CDR Reporting and Analytics over on the Sideview website here - https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.4
Sept. 29, 2022

Unfortunately Splunkbase still has a defect where it will not display release notes with more than 1024 characters, and that limit is not sufficient to describe the improvements in this release. Fortunately you can view the actual release notes on our website here
https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.3.9
June 25, 2022
  • Worked around a problem in Splunk that was dragging down performance in the Call Concurrency and Gateway Utilization page. Searches in that page are now approximately 6x faster and run with far fewer resources used.
Version 6.3.8
June 2, 2022

Splunkbase unfortunately truncates release notes for app updates, and the release notes for this particular version cannot be shortened to fit. Fortunately our release notes are always posted on our site at https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.3.7
May 10, 2022
  • Critical - Fixed a regression introduced in 6.3.6 that prevented the Chart view's "over nothing" mode from working properly.
  • Improvements to the Example Call Quality Dashboard to make the searches consistently screen out zero duration calls and calls that never connected.
Version 6.3.6
May 7, 2022

Critical - Fixed a bug where downloading the devices.csv from the Setup > Define Devices page, would give you a copy of the csv that was missing the required axlHost and axlPort columns.
- Fixed a bug where the "Call quality information (CMR)" panel on the Call Detail page did not actually report the new "quality" field.
- Added health checks to catch cases where after an app upgrade there can potentially still be scheduled searches regenerating the devices lookup or the groups lookup with columns matching the previous version's columns for that lookup.
- When you use "Save Report" or "Create Dashboard Panel" the newly created report or dashboard will now be in the "Saved Reports" or "Saved Dashboards" menu right away. Previously the newly created item would not be in the menu until the page had been refreshed. Note to get the new behavior you also need Canary
- Dashboard panels created by the app now have the version="1.1" attribute, to prevent warnings from being displayed by Splunk.

Version 6.3.5
April 1, 2022

Unfortunately Splunkbase truncates release notes to 1000 characters which is not enough to describe this release.
You can however always view the release notes for this app on the Sideview website at - https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.3.4
March 11, 2022

-- Functionality - the Investigate Sites page now has a control to filter by Cluster.
It also now has options to pick whether it should a) count calls with zero duration, and b) show rows for sites that have no calls at all in the given timerange.
-- Fixed a minor bug on the app homepage where the "Learn more about the product" panel would become invisible if any critical health checks failed.
-- Fixed a bug where users still running Splunk Enterprise 7.3 would be redirected to the homepage if they clicked links in the app's Navigation Bar while within SimpleXML dashboards or core Splunk pages.
-- Updated to the latest version of libphonenumbers, the python library the app uses to parse DN's to extract country code, area code etc for all phone numbers worldwide.

Version 6.3.3
Feb. 11, 2022

-- Fixed a critical problem introduced in 6.3.2 that prevented several pages from working correctly, and caused 2 panels on the homepage to load empty.
-- In "Explore new reports" on the landing page there is now improved messaging when a particular report detects that an optional component that it requires, still needs to be set up.

Version 6.3
Feb. 5, 2022

Unfortunately Splunkbase truncates release notes to 1000 characters and this is not enough to adequately summarize the changes in this release. However you can always read our release notes on our website here:

https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.2.2
Jan. 7, 2022
  • Critical - Fixed a bug that prevented users from adding dashboard panels to dashboards that had been shared at the app level.
  • Fixed a bug where multileg calls that had legs dateTimeConnect="0" would have their legs sorted incorrectly.
  • Fixed a bug on the Extension Detail page. If you set a huntPilot filter and/or interact with the time_of_day chart to filter the calls displayed and then click "investigate calls", now when you get taken to the "Browse calls" page it includes the extra huntPilot and time_of_day filters.
  • Fixed a bug where clicking elements in certain charts on the Site/Extension/Device Detail pages would not work correctly when run in the Canary UI.
  • Fixed a regression where in the Browse Devices the "devices with no device_type assigned" filtering option stopped working.
  • The Canary app is now required even for users still running Splunk Enterprise 7.3
Version 6.2.1
Dec. 11, 2021

Unfortunately Splunkbase truncates release notes at only 1000 characters, which is not sufficient to summarize the fixes and improvements in this release. Fortunately you can always see the full release notes on our site here:

https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.2
Nov. 11, 2021

Unfortunately Splunkbase truncates the release notes for every release to just 1000 characters. Since 6.1 was a significant release, we are unable to condense our release notes down that far.

However note that you can always read our release notes by navigating to our site at https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.1
Oct. 7, 2021

Unfortunately Splunkbase truncates the release notes for every release to just 1000 characters. Since 6.1 was a significant release, we are unable to condense our release notes down that far.

However note that you can always read our release notes by navigating to our site at https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/documentation/release-notes/

Version 6.0.8
Aug. 25, 2021

Unfortunately Splunkbase truncates release notes at 1000 characters, and that is not enough space to summarize the notes for this release. However you can read our release notes on our website here - https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 6.0.7
Aug. 6, 2021

Unfortunately Splunkbase truncates release notes at 1000 characters which is not sufficient to contain this release's notes. Fortunately you can always read our release notes for the Cisco CDR Reporting and Analytics app on our website at https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 6.0.6
Aug. 4, 2021
  • Critical – Fixed a rare bug introduced in 6.0.5 as a part of the General Report optimizations. If you specified party numbers both in the number field and in the search terms field, the results would inadvertently filter out results where the party numbers were on different legs.
  • Fixed a bug where if you included only a single “*” character in certain fields in Browse Extensions and Browse Devices, the argument would get ignored. Most notably the hunt pilot field in Browse Extensions, ie to narrow to only calls with huntPilot involvement.
Version 6.0.5
July 13, 2021

Unfortunately Splunkbase truncates release notes to only 1000 characters which is significantly less than the length of the notes for this release. However you can always see our full release notes on our site here - https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 6.0.4
May 12, 2021
  • Functionality – The Browse Gateways page now has an expanded field list and a field picker the user can use to display optional fields.
  • Critical – Fixed a bug on the Device Detail page where the table titled “x calls to/from this device” wasnt displaying raw field values from call legs but instead an unintuitive summary of those fields.
  • Critical – Fixed a bug where the “add new row” functionality in Setup pages did not work properly. This bug was introduced in some changes in 6.0.
  • Fixed a relatively harmless problem in the call_quality_to_qos lookup that was generating an error message from Splunk for some users.
  • Fixed a bug where the field picker on the Browse Devices page would act strangely if both a) the “show devices with zero calls” option was on, and b) your timerange did not include any actual call data.
  • Removing the “stacked100” option from General Report’s “chart type” pulldown until Canary’s Chart module gets proper support for it.
Version 6.0.3
April 15, 2021
  • Critical - Fixed a longstanding bug that only just came to light, where if you are using the "number" field within General Report, it was impossible to build any reports on any quality fields.
  • Speed improvement on the Devices page. The "device types" pulldown now populates much more quickly than before.
  • Fixed a confusing bug introduced in 6.0.2 in a particular link label case for the new action menus in Browse Calls. When you have foo=bar in the search filters, instead of getting an option to "remove filter for foo=bar", the action menu item would say just "foo=bar".
  • Devices lookup now has 2 extra fields "className" and "subclassName". On upgrade the app will automatically migrate the existing Devices lookup file to add the new columns. Note that this change is really just for users of our Supporting AXL App for Cisco CDR.
Version 6.0.2
April 9, 2021
  • Critical - Fixed a bug where certain North American location fields like LATA, CLLI, OCN, CompanyType, Company Name and NumberType wouldn't populate in Browse Calls until you added one another location field to the field picker.
  • Functionality - Improved context menus in Browse Calls such that now clicking on party numbers will add the value to the "number" field instead of the "search filters" field. Also the type and cluster fields now have working menus.
  • Improvements to how full DN's are parsed such that some more common offnet prefixes will now be recognized out of the box.
  • Fixed a bug where party numbers that began with an offnet prefix of "9" followed by an area code that also began with 9 would not get any location fields populated.
  • Pulled new NANPA data into the "npa-nxx-lata-clli-ocn-location.csv" lookup.
  • Updated to the latest version of libphonenumbers, the python library the app uses to parse DN's to extract country code, area code etc for all phone numbers worldwide.
Version 6.0.1
March 20, 2021
  • Critical - Fixed a bug in Call Detail where the top right panel would only ever allow you to see a subset of the fields.
  • Functionality - Browse Calls will no longer display rows for which there is only a CMR record and no CDRs. This situation can happen sometimes especially in large deployments when there are calls in progress that have generated one or more CMR, but that have NOT yet generated any CDR. Such calls would appear as a "ghost call" on the first page of search results, ie with most or all fields empty. These apparently blank calls so regularly caused confusion that they're now suppressed in that view specifically.
  • Minor changes to avoid appinspect false positives
  • Reworked some health check searches to improve homepage load times
Version 6.0
Feb. 25, 2021

Unfortunately Splunkbase truncated release notes at only 1000 characters which is quite a bit less than the notes for this release. View our release notes online at https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Note however that if you are using Splunk 8.X you will also have to update to Canary 1.4 or higher.
Or if you are running Splunk 7.3.X you will need to update Sideview Utils to 1.3.12.

Version 5.3.9
Jan. 15, 2021

Unfortunately Splunkbase truncates release notes at 1024 characters and our notes for this release are longer than that.

To read the full release notes visit our site at: https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 5.3.8
Dec. 2, 2020
  • Patched a bug that only occurs in Splunk 8.1, where some of the SPL used by the "call concurrency and gateway utilization" page does something the 8.1 SPL parser doesn't like.
  • Changed how the app's homepage checks for indexed data. Formerly it used the metadata command, but since this command can be deliberately disabled for lower privilege users, that can in turn cause the check to fail erroneously. The end result was some lower-privilege users would only see a homepage telling them that they hadn't indexed any data yet. This is fixed now and the check uses a tstats search.
  • Fixed a typo in our health check responsible for finding unusual indexing lag, that had been preventing it from running properly.
  • Fixed a minor problem where if someone was trying out the app while running only a Splunk Free license in Splunk itself, our health checks for user/role capabilities would fail erroneously.
Version 5.3.7
Nov. 6, 2020
  • Fixed a bug around the ROOT_ENDPOINT key, where users could get redirected to malformed URLs that were missing a slash between the root endpoint and the locale.
  • Improved the health check for indexing lag to list the 95th percentile of the lag in the health check message directly.
Version 5.3.6
Oct. 29, 2020

Fixed a critical regression introduced in 5.3.5 that broke the app on 7.X versions of Splunk.

Version 5.3.5
Oct. 16, 2020

Fixed a problem where the app's own license checks would fail if the Splunk server was using the "root_endpoint" key. This would result in the license check failing when Splunk was set up in a reverse proxy configuration.

Version 5.3.4
Oct. 7, 2020
  • Fixed a bug on the Call Detail page where the panel displaying fields from individual call legs only let you choose selected fields from a subset of the available fields
  • Browse Extensions now allows you to pick a particular subset of your UCM Clusters, in addition to filtering by group/subgroup/name/number/huntGroup etc.
  • Minor changes to our default device_type extractions to catch some unusual cases in the field for instance where jabber device names occasionally have hyphens or other non-alphanumeric characters in them.
  • Call Detail page now has 'see search syntax' links allowing you to see and troubleshoot aspects of the raw CDR events or CMR events in the default Splunk UI
  • Minor modifications to some of our health checks to reduce false positives.
  • App now ships an app.manifest file which may help various things stay on the tracks in Splunk Cloud
Version 5.3.2
June 25, 2020
  • Hoopjumping for some less-than-ideal problems in the Splunk Cloud vetting process. This release deletes one line of python code that was already commented out. This line was causing the app to silently fail Cloud-Vetting for several months, for an erroneous and silly reason. Also compounding the problem greatly is that Splunk's vetting process gives zero feedback or messaging to the third party app developer such that we were unable to even learn about the existence of this failure until recently. We had assumed that Cloud was really bogged down with vetting again. Thanks to the internal resource who dug into the matter and was able to tell us the details.

Our apologies to all our customers and prospects who over the past few months were told erroneously that the recent releases of this app were not cloud compatible. Also thanks to the internal splunkers who are trying to fix these problems and improve these broken processes.

Version 5.3.1
June 3, 2020

Unfortunately Splunkbase still truncates release notes at 1000 characters, which is quite a lot shorter than the notes for this release.

Luckily you can read our full release notes for this and other releases on our website here -

https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 5.3
April 25, 2020

Unfortunately Splunkbase still truncates release notes at 1000 characters, which is quite a lot shorter than the notes for this release.

Luckily you can read our full release notes for this and other releases on our website here -

https://sideviewapps.com/apps/cisco-cdr-reporting-and-analytics/release-notes/

Version 5.2.6
March 20, 2020
  • Fixed a bug where the Cisco CDR app wouldn’t accept new licenses for the app if the Splunk Enterprise instance was only running the Splunk Free License.
  • Fixed a regression on the Gateway Utilization page. Essentially the fix in 5.2.4 for the “unwanted types showing up” bug had a flaw in it, that not only didn’t work but regressed the same behavior for the gateway side. There is now unit testing covering this to try and make sure it never happens again.
Version 5.2.5
March 12, 2020
  • Fixed a regression in the 'set up data inputs' wizard that only affected 8.X.
    (Note this functionality is only relevant to users who have a standalone splunk
    instance on one host, with not even any forwarders involved.)
  • Improved UI messaging for the 'set up data inputs' wizard so that if the user
    is not an admin user or they are, but they lack the admin-all-objects capability,
    they get an error telling them as much instead of a confusing "AuthorizationFailed"
    error message.
  • Switched over to using the new restmap.conf controller for the "upload csv" functionality
    for both Setup Groups and Setup Sites.
  • Some cleanup in our python logging.

Subscribe Share

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or registered trademarks of Splunk Inc. in the United States and other countries. All other brand names,product names,or trademarks belong to their respective owners.