Chat now with support
Chat with Support

Unified Communications Analytics 8.6.1 - Deployment Guide

Prerequisites for your installation Installing UC Analytics Configuring UC Analytics Adding data sources for Active Directory or Azure Active Directory Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
Permissions needed to collect Exchange on-premises or hybrid data Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365 Adding Exchange Online data sources for native Office 365 Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync Adding data sources, chargeback, and thresholds for Cisco Managing which insights can seen by users Configuring and managing subscriptions Making changes to your deployment Appendix A:Configuring Impersonation Appendix B:Configuring the Skype for Business or Lync Server Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events Appendix D:PowerShell cmdlets used by data sources Appendix E:Custom configurations and backup and recovery options Appendix F: Questions and answers about configuration

Permissions needed to collect Cisco data

Cisco is supported only if Active Directory is present and Cisco end-users are synchronized to Active Directory users using the SAM account name.

To collect data from Cisco, you add different data sources to gather information. You can create the following data sources:

•
Cisco Configuration: end-user data from the Cisco Unified Communications Manager (CUCM) and user data from Active Directory using LDAP
•
Cisco CDR Logs: Peer-to-peer session and conference details from the Cisco CDR (call detail records) log files.
UC Analytics does not directly access your Cisco CDR database. You must copy the CDR logs to a share location from which you want to gather the data. For example, you can configure the Cisco Unified Communications Manager server to automatically upload the CDR logs to the directory you specify.

Permissions needed for the Cisco configuration data source

You specify the credentials that are used to collect user data from Active Directory and the credentials used to collect end-user data from the Cisco Unified Communications Manager (CUCM) server.

•
The credential that is used to collect Active Directory (LDAP) user data must have read permissions on all the Active Directory user, group and contact objects.
•
The credential that is used to collect Cisco end-user data (including phone number and SAM account) must have read permissions on the Cisco Unified Communications Manager server. The credential must be a member of user group Standard AXL API Access.

There are different methods that Active Directory (LDAP) can be integrated with Cisco. UC Analytics requires that the SAM account name be used to synchronize the Cisco end-users and Active Directory users.

Permissions needed for the Cisco CDR logs data source

To configure the Cisco CDR logs data source, you require the following credentials and permissions:

•
You must specify a credential to access the Cisco server to collect Cisco configuration for the specified Cisco Unified Communications Manager (CUCM). The credential must be a member of user group Standard AXL API Access.
•
To access the directories that contain the CDR logs, you can enter specific Windows credentials or you can use the credential that is specified for the Data Engine service. The credential used to access the Cisco CDR logs must have read rights on all the file shares on which you have stored the log files.

Creating a data source for Cisco configuration

Creating a data source for Cisco configuration

By creating a Cisco configuration data collection, you can collect Cisco end-user information including Cisco phone numbers, device IDs, and the user information from Active Directory (LDAP).

For information about prerequisites, see Permissions needed for the Cisco configuration data source .

To set up a Cisco configuration collection
1
Click the gear icon on the home page side bar.
2
Click Data Collection.
3
Click + beside the name of the target environment.
4
Select the Cisco Configuration check box.
5
Enable the data collection for this data source.
 
* 
NOTE: If you have installed more than one Data Engine (Collector), you have the option to select a different computer that hosts a data collector.,
Modifying the collection schedule
By default the data collection is set to run every six hours, aligned to midnight UTC. You can modify the run interval or you can set the collection to run at a specific time on specific days.
6
Set the schedule for the data collection:
a
Click Execute job every: and select an hourly interval.
- OR -
b
Click Execute job at: and select the specific job run time, the number of days between each job run, and a start date.
Selecting data to collect
7
Select the types of data that you want to collect.
8
Specify the Windows credentials to be used for the LDAP connection to Active Directory or select the Use Data Engine service credential option.
9
Specify the Cisco Unified Communications Manager (Call Manager) server and credentials to collect Cisco data.
Advanced settings (not required for most deployments)
•
If you want to specify one or more explicit domain controllers instead of automatically discovering the domain controller, click Show Advanced Settings in the LDAP Collection Parameters section. For more information, see Specifying explicit domain controllers for LDAP connections . The domain controller must be a global catalog server.
 
* 
NOTE: If the Data Engine is in a different forest from the data to be collected, you must specify the domain controller you want to use for data collection. If you leave the default setting to automatically discover domain controller, the data collector selects a domain controller from the forest that hosts the Data Engine, not a domain controller from the forest from which you are collecting the data.
10
Click Save.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating