Thanks For Downloading!Review the documentation below and follow any custom installation steps. If no install steps are listed, most Splunk Apps and Add-ons can be installed as follows: Windows: Decompress the downloaded file using a tool like 7-Zip and place the resulting folder into Unix/Linux: Decompress the downloaded file using a tool like DescriptionNOTE: the new 2.0 version of this app is now available as a 90 day trial from the Sideview website. We strongly recommend doing your trial with the 2.0 version which has many improvements over 1.2.7. Note that to try out 2.0 you will also have to get a 90 day trial version of Sideview Utils 2.0. Get the new 2.0 version from the Sideview site today. The Splunk for Cisco CDR app provides powerful reporting, analytics and simple visibility into the call detail records and call quality information generated by Cisco Unified Communications Manager, aka Cisco CallManager. What are my most active extensions or busiest clusters? What do my MOS scores look like throughout the workday? How many calls have failed due to lack of bandwidth? There are so many questions to ask that we can't possibly know ahead of time what you're going to need. So instead of throwing dozens of prepackaged reports and dashboards at you, this app focuses on allowing you to generate any chart you need with just a few clicks. It also lets you move easily from call to call, and from extension to extension when you need to troubleshoot complex problems. You can more screenshots and details about this app on our website. And don't forget to check out our newly expanded installation and setup documentation. Versions and Release Notes
Version 1.2.2 (current version - updated Feb 17, 2012)
release notes:
Had to fix a mistake in how the setup screens redirected you through the flow.
Version 1.2.1
(updated Feb 15, 2012)
release notes:
The installation docs have been completely rewritten, *very* significantly expanded,
and mostly moved to our website. See for yourself at http://sideviewapps.com/apps/splunk-for-cisco-cdr/docs/
While the in-app documentation has also been completely updated, it largely directs the user to the website documentation.
Version 1.2
(updated Feb 02, 2012)
release notes:
> significant changes and rewrites to fix bugs and issues with Splunk 4.3.
> significant changes and rewrites based on more search language performance
testing at high data volumes.
> lots of improvements and minor bugfixes to the custom reporting view.
> new simpler more usable homepage
> customers can now specify a custom index during app setup.
> fixed various bugs in the call_detail view, in cases where there was more
than one finalCalledPartyNumber
> fixed a bug where you couldn't actually run any reports if clusterId or
callManagerId was specified as a field.
> added a cluster lookup, related wizard page to regenerate it from indexed
data, and filtering pulldowns in Browse and Report views
> Fixed a bug where the automatic redirect to the qos threshold page wouldn't
work properly.
> Added a JobStatus module to both Browse and Report views, so customers can
now pause and cancel searches inline.
> Added save controls to the Browse page, so it effectively becomes a "simple
call report", operating on just the CDR data.
Version 1.1
(updated Jan 27, 2012)
release notes:
- major rewrite of browse and report views, including major changes to search
language used in macros. These changes were to workaround serious performance
problems seen in larger data sets.
- added a 'call legs' section to the call_detail view.
- fixed a bug where the app would not warn the user correctly when the
Sideview Utils app was not installed
- fixed a bug around IP address conversions.
- numerous other small fixes and improvements.
Version 1.0.9
(updated Nov 30, 2011)
release notes:
Added functionality around a lookup that adds group names and user names into the records.
Incorporated guided setup around this feature into the existing setup wizard.
Note that this can also be used to generate reports about *all* extensions regardless of activity. I only added a hint about this to the app itself, but once you get the hang of it it's quite straightforward.
Version 1.0.8
(updated Oct 25, 2011)
release notes:
CallManager CDR and CMR data has several fields which are IP Address values, however it encodes these values as integers. The app now has functionality to automatically convert the integers back into IP Addresses.
Specifically, when you use any of the ip address fields in reports, as either the 'split-by' field or as the x-axis field, it will correctly display the values as IP addresses.
Also on the call_detail view, when those fields are displayed in the rightmost panel they will appear as IP addresses now.
Version 1.0.7
(updated Oct 20, 2011)
release notes:
> added a new lookup for video codec types,
> fixed a bug in "browse" and "report" views where the search filter would
not filter overall calls, but individual CDR and CMR rows. The filtered results
will make a lot more sense now to end-users.
> added a new field called 'call_connected', which is True or False or null.
The value is derived by looking at the overall call release cause codes.
(null represents records where no call was attempted)
> made a new field called callID that is the callID plus the callManagerId,
separated by a "."
> the report view's main reporting pulldown now defaults to 'distinct calls'
instead of dumping the user at 'distinct count of authorizationLevel' and
hoping they figure it out.
> The flow around the contact form has been slightly improved.
> added back-button and forward-button support to the "browse" view.
> re-running guided setup will no longer force you to contact sideview a
second time.
> Upped required version of Sideview Utils to pick up other bugfixes.
Version 1.0.6
(updated Sep 28, 2011)
release notes:
The app now includes a view for Quality of Service reporting, and the app has a setup screen offering configurable thresholds for QoS by numberOfPacketsLost, jitter and latency.
Also the functionality whereby the appname and app version was sent to sideviewapps.com has been completely removed in this version. Instead during the initial app setup screens you are asked to send us your name and a brief note.
Version 1.0.5
(updated Sep 19, 2011)
release notes:
> Fixed a problem where the reports could be misleading when you imported data from more than one CallManager
> Added initial version of a scripted lookup that will enable new Quality-of-service reporting features. (docs and user interface will come soon. Email me if you want to try it out now)
> Rewrote and reworked the guided setup copy.
Version 1.0.4
(updated Sep 02, 2011)
release notes:
- fixed a bug on call_detail where as soon as you drilled down to any other
call you'd only see results from a single second. The call_detail view is
much more usable and interesting now.
- Added 'see raw search syntax' links in various places so customers can see
how the real searches work.
- Made those links take you to a new custom view that is a little more
comfortable than splunk's normal 'advanced charting view'.
- added lookups for call release cause codes, as well as redirect reason codes.
Now those descriptions are automatically created as fields for each call.
- Fixed a bug where changing some TimeRangePickers would not do anything.
- Improved the error detection to not flag configurations where trivial
off-hook calls generate CDR's.
|
"Price: 90-day Free Trial"
I can't find the real price anywhere. Could you please mention it somewhere?
Sorry I didn't notice this comment until now. It does say to email me at nick [at] sideviewapps.com if you're interested in pricing, but it's not hard to miss that. Please accept my apologies for not noticing this comment here, but feel free to email me going forward. Currently the pricing for the app depends on the number of clusters.
Doesn't work on Newer CUCMs.
I'd love to hear from you at nick@sideviewapps.com. Please send any details you can share, like sample rows from your cdr and cmr files. The set of sample data that I have does not span the entire range of older CallManager versions and newer CUCM versions so I'm sure you're right. However I'm also sure that it will be easy to fix the problem once I know what it is. Cheers.
I have seen one customer on CUCM 7.X whose CMR files did not have any dateTimeStamp field and this indeed caused some problems we had to work around. However I've also seen another customer also on CUCM 7.X, whose CMR files did contain that header. I suspect that the problem lies in some tweaky configuration in CallManager. If you can send any details I'm pretty confident it can be fixed or at least worked around.
