Step 5 — What Now?
You have now completed the core setup and you should have data coming in. So let’s make sure:
- Open our app’s Home tab and check that there are no errors and that the various panels are starting to populate with data.
- Navigate to Investigate > Calls and make sure there are calls showing and that they look more or less correct.
- If at this point something doesn’t appear to be working or doesn’t look right, navigate to Admin then Run health checks and let us know what you are seeing at email@example.com.
However if everything looks good, then Congratulations!
This is a great time to read our User Documentation if you haven’t already. Also if you are doing a 90 day trial of the app this is a great time to contact us to schedule a webex to drive the app around in your data wherever your questions take us.
There are a few high value things that are technically optional, but chances are your team will find at least one of them extremely useful.
- Set up the Groups Lookup
Search, filter, and report on your own departmental structure and have names that matched your Active Directory names, departments, and possibly other fields
- Set up the Sites Lookup
Give the app an idea of what subnets (defined in CIDR notation) map to which physical site/location names, and your team will get some very powerful abilities
- Define clusters and locales
If you have CUCM clusters outside of North America, you can modify how it parses full DN“s to account for regional dialing prefixes and patterns, just by designating the right locale for each CUCM Cluster.
For everyone, you can also give a more readable name to your clusters, or create groupings of them.
- Define quality thresholds
The quality field will work fine out of the box, but if call quality is a #1 concern you and your team may want to revisit the specific threshold definitions early on.
- Define custom device types
the app ships a set of extractions to catch most common device name prefixes like SEP and CSF. However Large CUCM deployments often have one or two core kinds of devices that deserve their own custom one.
If you have any comments at all about the documentation, please send them to firstname.lastname@example.org.