Set Up PCA

Cisco Prime Collaboration Assurance Overview

Cisco Prime Collaboration Assurance and Analytics provides real-time monitoring, proactive troubleshooting, and long term trending and analytics in one integrated product.

Cisco Prime Collaboration Assurance provides integrated service assurance management through a single, consolidated view of the Cisco voice, and video collaboration environment. It includes continuous, real-time monitoring and advanced troubleshooting tools for Cisco Unified Communications and Cisco TelePresence systems including the underlying transport infrastructures.

For more information about Cisco Prime Collaboration Assurance and Analytics, see the Cisco Prime Collaboration Assurance documentation: https://www.cisco.com/c/en/us/support/cloud-systems-management/prime-collaboration-assurance-12-1/model.html

Data Center Service Assurance Overview

Cisco HCS applications depend on the availability, performance, and capacity of the underlying data center infrastructure and data center service assurance is an important aspect of assuring HCS services. Cisco HCS utilizes Cloud Level Service Assurance (CLSA-VMDC) for data center service assurance utilizing Zenoss Cloud Service Assurance (Zenoss CSA). Features include:
  • Fault & Performance Adapters to data center devices and element managers.
  • Device discovery, inventory and availability for all data center components.
  • Data Center data aggregation, normalization and enrichment.
  • Fault and performance management of all data center components.
  • Device & service northbound SNMP notification.
  • REST API for provisioning domain manager and exposing assurance data to external systems.
  • Presentation (dashboards & reports)

For more information on CLSA see Data Center and Cloud Service Assurance.

Getting Started

You can invoke Prime Collaboration using the client browser.

To log in to the Prime Collaboration application:

Procedure

Step 1

Open a browser session from your machine.

Step 2

Enter https://IP Address

Note 

  • For Prime Collaboration Assurance, HTTPS has been enabled by default.

  • You can use either the IP address or the hostname of the Prime Collaboration Assurance server. We recommend that you use the hostname if you have configured it in DNS.

  • CLI is supported only through SSH; telnet is not supported. The port used for Prime Collaboration Assurance is 26.

Based on the browser you are using, one of the following appears:

  • In Windows Internet Explorer, the Certificate Error: Navigation Blocked window.

  • In Mozilla Firefox, the Untrusted Connection window.

These windows appear because Prime Collaboration uses a self-signed certificate.
Step 3

Remove the SSL certificate warning. For more information, see the Troubleshooting Cisco Prime Collaboration Guide: Troubleshooting Cisco Prime Collaboration.

The Prime Collaboration login page appears.

Step 4

In the Prime Collaboration login page, you must login as a globaladmin, using the same credentials that you have specified during the configuration.

The dashboard data is populated only after you perform tasks listed in the tables that follow.

Role Mapping for Prime Collaboration Assurance

Service providers deploying Cisco Hosted Collaboration Solution use role-based access control (RBAC) to restrict certain management actions to a specific set of users. Administrators at each level have access to the information in all hierarchy levels below them. Refer to “Role-Based Access Control" in the Cisco Hosted Collaboration Solution End-to-End Planning Guide for more information on Cisco HCS roles.

Prime Collaboration Assurance roles are hierarchical in the following order:

  1. Super Administrator—Includes all privileges of System Administrator, Network Administrator, Operator, and Help Desk, along with the Super Administrator permissions.

  2. System Administrator

  3. Network Administrator—Includes all privileges of Operator and Help Desk, along with the Network Administrator permissions.

  4. Operator—Read-only administrative access

  5. Help Desk

Cisco Unified Communications Domain Manager roles map to the Prime Collaboration Assurance roles shown in the following table. You can find Roles in Unified CDM 10.x/11.5(x) under Role Management > Roles. The three drop-down lists that are important in Unified CDM are Hierarchy Type, Service Assurance Role Type, and HCS Component Access.

Prime Collaboration Assurance roles are shown in this table in hierarchical order from top to bottom. The role shown in BOLD represents the highest role available.

Table 1. Role Mapping Between Cisco Unified CDM 10.x/11.5(x) and Prime Collaboration Assurance

Hierarchy Type in Unified CDM 10.x/11.5(x)

Service Assurance Role Type

HCS Component Access

Prime Collaboration Assurance Role

Notes

Provider

Administrator

Fulfillment and Service Assurance

Super Administrator, System Administrator, Network Administrator

Provider roles are always the top organization unit in the Unified CDM navigation tree.

The Provider roles can see all devices, including shared devices such as Session Border Controllers.

A Provider with this role has Administrative level access to Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Provider with this role has Administrative level access to Unified CDM and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Provider with this role has Administrative level access to Unified CDM and Hosted Collaboration Mediation-Fulfillment.

Operator

Fulfillment and Service Assurance

Operator, Help Desk

A Provider with this role has Administrative level read-only access to Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Provider with this role has Administrative level read-only access to Unified CDM and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Provider with this role has Administrative level read-only access to Unified CDM and Hosted Collaboration Mediation-Fulfillment.

Reseller

Administrator

Fulfillment and Service Assurance

Network Administrator

These roles can only see the customer information that belongs to your Reseller organization.

A Reseller with this role has Administrative level access to Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Reseller with this role has Administrative level access to Unified CDM and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Reseller with this role has Administrative level access to Unified CDM and Hosted Collaboration Mediation-Fulfillment.

Operator

Fulfillment and Service Assurance

Operator, Help Desk

A Reseller with this role has Administrative level read-only access to Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Reseller with this role has Administrative level read-only access to Unified CDM and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Reseller with this role has Administrative level read-only access to Unified CDM and Hosted Collaboration Mediation-Fulfillment.

Customer

Administrator

Fulfillment and Service Assurance

Network Administrator,

This role allows viewing your customer information.

A Customer with this role has Administrative level access to Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Customer with this role has Administrative level access to Unified CDM and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Customer with this role has Administrative level access to Unified CDM and Hosted Collaboration Mediation-Fulfillment.

Operator

Fulfillment and Service Assurance

Operator, Helpdesk

This role allows viewing your customer information.

A Customer with this role has Administrative level read-only access to Cisco Unified CDM, Hosted Collaboration Mediation-Fulfillment, and Prime Collaboration Assurance.

Service Assurance Only

A Customer with this role has Administrative level read-only access to Cisco Unified CDM, and Prime Collaboration Assurance.

Fulfillment Only

Not Applicable

A Customer with this role has Administrative level read-only access to Cisco Unified CDM, and Hosted Collaboration Mediation-Fulfillment.

Rules for Creating Domain Manager Adapter and Shared Data Repository Users

  1. Synchronize a DMA or SDR user into Cisco Unified CDM 10.x/11.5(x) using LDAP at the Provider hierarchy level. If you add the user manually in Cisco Unified CDM, the user is not pushed to Prime Collaboration Assurance.

  2. Assign each DMA user a Domain Manager Adapter (DMA) role. Check the role of the user in Unified CDM 10.x/11.5(x) (User Management > Users Base tab), then check the HCS Component Access field (in Role Management > Roles) to see if the user has an Assurance role. If the user is assigned a Fulfillment role only, then the user is not pushed to Prime Collaboration Assurance.

Changes to User Roles After an LDAP Sync

If you make role changes to the user after the user is synched into Unified CDM 10.x/11.5(x) using LDAP, the changes affect the DMA SDR as follows:

  • If the role change is from a DMA role to another DMA role, the SDR is updated with the new role name.

  • If the role change is from a DMA role to a non-DMA role, the SDR user is deleted.

  • If the SDR user is deleted, and the user is modified so that the user's role is changed to a DMA role again, the DMA SDR User is recreated with the DMA role.

  • If the user is moved to a different hierarchy level, rules are applied based on the role that the user is moving to.

  • If a site does not have any DMA roles, then the SDR user is deleted for any user that is moved to the Site hierarchy level.

  • For DMA roles, the user must be a Provider Administrator, Reseller Administrator, Customer Administrator, or Operator on Unified CDM 10.x/11.5(x). Site Operators are not pushed to DMA.

Cisco Prime Collaboration Assurance Integration for Small Contact Center Deployment Model

Customer Management for Prime Collaboration Assurance

Procedure

Step 1

Login to Prime using the URL https://<IP_address_of_Prime_Collaboration_application/ .

Step 2

Go to Administration > Customer Management.

Step 3

Click Add.

Step 4

In General Info tab, enter the Customer Name.

Step 5

Click Next and then Save.

Add Cluster

Procedure

Step 1

Log into HCM-F using administrator credentials.

Step 2

Choose Cluster Management > Cluster, and click Add New.

Step 3

Enter the cluster name.

Step 4

Choose the customer from the drop-down list.

Step 5

Choose CC for the cluster type from the drop-down list.

Step 6

Choose the cluster application version from the drop-down list.

Step 7

Choose PCA as the host name from the Application Monitoring the Cluster drop-down list.

Step 8

Click Save.

Add Contact Center Components

Customer Contact components includes Rogger, AW-HDS, Agent Peripheral Gateway, VRU Peripheral Gateway, CVP, CVP OAMP, and CVP RSA.

Procedure

Step 1

Log in to HCM-F using administrator credentials.

Step 2

Choose Application Management > Cluster Application.

Step 3

In the General Information section, configure the following.

  1. Click Add New.

  2. Choose UCCE from the Application Type drop-down list.

    Choose CVP for CVP, CVP OAMP, CVP RSA , choose UCCE for Rogger, AW-HDS, Agent Peripheral Gateway, or VRU Peripheral Gateway.

  3. Enter the host name of the CC component.

  4. Choose a cluster from the drop-down list.

  5. Click Save.

Step 4

In the Credentials section, configure the following.

  1. Click Add New.

  2. Choose SNMP _V2 from the Credential Type drop-down list.

  3. Enter the Community Srting configured on CC Component.

  4. Choose Read Only option for the access type.

  5. Click Save.

  6. Click Add New.

  7. Choose ADMIN from the Credential Type drop-down list.

  8. Enter the administrator credentials.

    For CVP, CVP OAMP, CVP RSA use User ID as wsmadmin and password configured for OAMP web UI

  9. Choose Read Only option for the Access Type .

  10. Click Save.

Step 5

In Network Addresses section, configure the following.

  1. Click Add New.

  2. Choose Application Space from the Network Space drop-down list.

  3. Enter the IPV4 Address and the hostname.

  4. Click Save.

  5. Click Add New.

  6. Choose Service Provider Space from Network Space drop-down list.

  7. Enter the NAT IPV4 Address and Hostname.

  8. Click Save.

    Note 
    Follow the same procedure to add AW-HDS, Agent Peripheral Gateway,VRU Peripheral Gateway, CVP, CVP OAMP, and CVP RSA. Cisco Unified IC is not supported.

Configure Prime Collaboration Assurance

Prime Collaboration Assurance is ready to accept customer data from HCM-F once installation is complete. For additional information on Prime Collaboration Assurance see Prime Collaboration Assurance.

Procedure

Step 1

Install your Prime Collaboration Assurance license.

  1. Obtain the license file from Cisco. The license is tied to MAC of the VM. It is recommended to use customized range (00:50:56:XX:YY:ZZ, Where XX is a valid hex number between 00 and 3F and YY and ZZ are valid hex numbers between 00 and FF), for easy re-use later.

  2. Login to the Prime Collaboration Assurance GUI.

  3. Go to System Administration > License Management.

  4. Click Add under License file, and follow the prompt to upload the license file.

    Note 

    • Cisco Prime Collaboration Assurance Licensing User Interface restricts the maximum license you can import on each profile (Small/Large/BE6k).

    • The Prime Collaboration Assurance GUI allows you to use the Prime Collaboration Analytics feature, if you are using Prime Collaboration Assurance 11.5 or later and purchased the Analytics license.

Step 2

Ensure SFTP credential matches with the values configured in HCM-F.

  1. Log into the Prime Collaboration Assurance GUI.

  2. Go to Reports > Inventory > Inventory Management > CUCM sFTP Credentials.

  3. Provide the same password as in HCM-F for smuser.

Step 3

Forward the Alarm to Northbound destinations, if needed.

  1. Log into the Prime Collaboration Assurance GUI.

  2. Go to Alarm & Report Administration > Notification Setup > Notification > Assurance Notification Criteria.

  3. Click Add, fill in general information including Criteria Name, select Alarm Severity > Alarm Status to be forwarded, then click Next.

  4. Click Add in the for Devices > Device Group. Choose Select Device or Include all Devices, Click Select, then Next.

  5. Check Northbound alarm type, (Trap, Email, Syslog), then provide needed information (such as IP and port number. SNMP typically uses port 162 and syslog typically uses port 514). Click Next.

  6. Click Save.

Configure System Parameters

Cisco Prime Collaboration allows you to configure system parameters for Cisco Prime Collaboration Assurance.

If you have deployed Cisco Prime Collaboration in MSP mode, the cluster (data) is displayed for a selected customer (selected from the global selection drop-down list).


Note
For details on the system configuration parameters for Cisco Prime Collaboration Assurance, refer to Cisco Prime Collaboration Assurance Advanced and Analytics Guide.

Credential Profiles Field Descriptions

After the devices are discovered, you can check the current Inventory table to verify that the credentials have been updated in the Cisco Prime Collaboration database.

The following table describes the fields on the Credential Profiles page.


Note

When you define IP address patterns in Prime Collaboration 10.5, use the Operate > Device Work Center > Manage Credentials menu path.

When you define IP address patterns in Prime Collaboration Assurance 11.0, use the Device Inventory > Inventory Management > Add > TMS and Associated Devices (Auto Discovery) menu path.

Table 2. Credential Profiles Field Descriptions

Field Name

Description

Profile Name

Name of the credential profiles.

For example:

  • CTS_MAN

  • CUCM

  • router_switches

Device Type

(Optional) The credential fields (such as SNMP, HTTP, CLI) are displayed, based on the device type that you have selected.

To reduce rediscovery time, we recommend that you select the device type when you create the credential profiles.

The default device type is "Any", if you do not select a device type while creating a credential profile.

See cisco.com for the list of device types.

For EX series, MX series, SX series, bare Codec devices, and all profiles with Codec, select the device type as TC_CE.

For EX series, MX series, SX series, DX series with CE image, bare Codec devices, and all profiles with Codec, select the device type as Codec.

For Cisco Virtualized Voice Browser devices, select Virtualized Voice Browser device type.

You can enter any credentials (SNMP, HTTP, CLI , MSI) to create an "Any" credential profile. You must create an "Any" credential profile to run auto-discovery (Ping Sweep and CDP discovery). However, you can run logical discovery also.

If your network has multiple subnets, then create an "Any" profile for each subnet.

IP Version

The IP address is version 4 or version 6.

IP Address Pattern

IP address of the devices for which the credentials are provided. You must:

  • Separate multiple IP addresses by the delimiter pipe (|).

  • Not use 0.0.0.0 or 255.255.255.255.

  • Not use question mark (?).

We recommend that you:

  • Enter the exact IP address for CTS-Manager, Cisco Unified CM, and Cisco TMS.

  • Enter the exact IP address for either CTS or network devices.

  • Do not use many wildcard expressions in the address patterns.

For example:

  • 100.5.10.*|100.5.11.*|100.5.20.*|100.5.21.*

  • 200.5.1*.*|200.5.2*.*|200.5.3*.*

  • 172.23.223.14

  • 150.5.*.*

Avoid using patterns such as 150.*.*.*, 192.78.22.1?, 150.5.*.*/24.

If you are unable to find a common pattern for the devices, enter *.*.*.*.

Minimize the use of wildcard character (*), while defining the IP address patterns in the credential profiles .

Inventory > Inventory management > Manage Credentials

Use of wildcard character may increase the discovery time.

See SNMPv2C to understand how the patterns are used.

General SNMP Options

SNMP Timeout - The default is 10 seconds.

SNMP Retries - The default is 2.

SNMP Version - Selecting an SNMP version is mandatory.

SNMPv2C

Used to discover and manage the device.

SNMP Read Community String

You can provide either SNMPv2C or SNMPv3 credentials. We recommend that you use different SNMP credentials for Cisco TelePresence systems and network devices.

Cisco Prime Collaboration searches the credential profiles, based on the IP address pattern. Cisco Prime Collaboration then chooses a profile for which the SNMP credentials match. There can be multiple matching profiles, that is, profiles with the same SNMP credentials. In such cases, Cisco Prime Collaboration chooses the profile that matches first.

Note 

If multiple profiles have the same SNMP credentials but different CLI credentials, Cisco Prime Collaboration might chose a profile that contains the correct SNMP credentials but incorrect CLI credentials for the device. If this occurs, the troubleshooting workflow might not work.

SNMP Write Community String

SNMPv3

Used to discover and manage the device.

SNMP Security Name - Enter a security name.

SNMP Authentication Protocol - select the supported protocol as SHA.

When you add new clusters from the HCMF 12.5.1 SU2 release and later application, the default SNMP Authentication Protocol that is supported for CUCM clusters and PCA integration is SHA. For existing clusters configured with MD5, the HCMF 12.5.1 SU2 application changes the default SNMP Authentication Protocol for CUCM clusters to SHA. For Expressway-E & C and Cisco Unity Connection clusters, you must manually select the default SNMP Authentication Protocol as SHA.

Note 

You can choose SHA only in the FIPS compliant setup.

SNMP Authentication Passphrase - Enter a passphrase.

SNMP Privacy Protocol - You can choose either AES, AES128, or DES.

SNMP Privacy Protocol - You can choose either AES128, or DES.

CLI

Used to access the device through CLI to discover media path for troubleshooting.

CLI Login Username and Password

The CLI credentials are used during the troubleshooting workflow. If the credentials are not entered or if the entered credentials are incorrect, the troubleshooting workflow feature may not work.

The CLI credentials are used to manage video test call and analyze call signaling through SIP Call Flow Analyzer.

HTTP

Used to access the device through HTTP to poll system status and meeting information.

HTTP Username and Password

Cisco Prime Collaboration first checks the access for HTTP. If the access attempt fails, then Cisco Prime Collaboration checks the access for HTTPS.

If you log in to Cisco TMS using the <domain/username> format, then ensure that you add the same <domain/username> value in the HTTPS Username field.

JTAPI

Used to retrieve the session status information from the Cisco Unified CM.

Used to retrieve the conference status information from the Cisco Unified CM.

(Optional) JTAPI Username and Password.

Note 

Password must not contain a semicolon (;) or equals (=).

The following devices are renamed in Credential Profiles Page:

  • CISCO INTERACTION MANAGER is renamed as WEB/EMAIL INTERACTION MANAGER

  • CUIC is renamed as INTELLIGENCE CENTER

  • CTS is renamed as CTS/IX ENDPOINT

  • CISCO UNIFIED COMMUNICATIONS MANAGER is renamed as COMMUNICATIONS MANAGER

  • C_SERIES CODEC is renamed as TC/CE ENDPOINT

  • E20 is renamed as E20 ENDPOINT

  • ISDN is renamed as ISDN GATEWAY

  • Conference Hardware is renamed as MULTIPOINT CONTROLLER

  • MXP is renamed as MXP ENDPOINT

  • ROUTER is renamed as ROUTER/VOICEGATEWAY

  • TPS is renamed as TELEPRESENCE SERVER

  • TELEPRESENCE CONDUCTOR is renamed as TELEPRESENCE CONDUCTOR


Note

You do not need to add credentials for Cisco Device, Polycom, Cisco Unified Communications Manager Express (Cisco Unified CME), and UC500 Series devices in Credential Profiles page.

Add a Device Credentials Profile

To add or clone a credential profile:

Procedure

Step 1

In the Cisco Prime Collaboration page, choose Device Inventory > Inventory Management from the Toggle Navigation pane.

In the Cisco Prime Collaboration page, choose Inventory > Inventory Management from the Toggle Navigation pane.

The Inventory Management page is displayed.
Step 2

In the Credentials Profile page, click Add and enter the necessary information described in the Credential Profiles Field Descriptions table.

Step 3

Click Save.

In your network, you may have configured the same SNMP credentials for all devices. In such cases, first create a new profile and later clone the existing profile. To clone, in the Credentials Profile page, select an existing profile and click Clone and after the required updates click Add/Update.

SSL Certificate Authentication for Device Discovery

For Cisco Prime Collaboration Release 11.1 and earlier

In Cisco Prime Collaboration Assurance, when a device is added, the SSL certificates are exchanged for credential validation by accessing a protected resource using HTTPS. During exchange, the SSL certificate is not stored in Cisco Prime Collaboration Assurance trust-store and communication with the device fails, at a later point of time. It is recommended that you manually import the SSL certificate to Cisco Prime Collaboration Assurance trust-store to access the device.

Cisco Prime Collaboration Assurance enables you to check the authenticity of the SSL certificate during its communication with the devices or applications over HTTPS. However, this is not mandatory as you can still continue to discover the devices without authenticating the certificate.

Cisco Prime Collaboration Assurance does not validate the certificates from the devices or applications it communicates by default.

To enable the SSL certificate authentication:

Procedure

Step 1

Choose System Administration > Certificate Management.

The Certificate Management page is displayed.
Step 2

In the Device Certificate Management tab, check the Enable SSL certificate authentication for device discovery check box.

Step 3

Click the Import Certificates button.

Step 4

Restart the Cisco Prime Collaboration Assurance server for the changes in trust manager to take effect. 

cm/admin# application stop cpcm
cm/admin# show application status cpcm
cm/admin# application start cpcm

Verify Device Credentials

For Cisco Prime Collaboration Release 11.5 and later

If device discovery fails because of incorrect credentials, you can test the credentials for the failed devices and rediscover those devices. Choose Inventory > Inventory Management > Discovery Jobs for a list of devices that were not discovered.


Note

Do not run this task when a discovery job is in progress.

To verify device credentials:

Procedure

Step 1

For Cisco Prime Collaboration Release 11.5 and later

Choose Inventory > Inventory Management.

The Inventory Management page is displayed.
Step 2

From the Credential Profiles page, select the profile name to use for testing the credentials, and click Verify.

Step 3

Enter a valid device IP address to test the credentials. You can verify only one device at a time, and you cannot enter expressions such as *.*.*.*, 192.2.*.*, and so on.

Step 4

Click Test. You can see an inprogress moving icon next to the test button till the task completes. The test results are displayed under the Test Credential Result pane.

If the verification fails, see the possible reasons listed in Credential Verification Error Messages.

Note 
All the nodes in the cluster may not be running all the protocols. For example, JTAPI may not be running on all the nodes. As a result, the credential validation test may fail for some of your nodes. After fixing the credentials issue, test the device credentials again and run the discovery for that device. After the devices are discovered, you can verify if the access information is updated in the Cisco Prime Collaboration Assurance database in the current Inventory table.

Credential Verification Error Messages

The credential verification error messages are tabulated below.

Table 3. Credential Verification Error Messages

Error Message

Conditions

Possible Solutions

SNMPv2

SNMP Request: Received no response from IP Address.

Failed for one of the following reasons:

  • Device response time is slow.

  • Device is unreachable.

  • Incorrect community string entered in the credential profile.

  • Verify the device connectivity.

  • Update the credential profile with the correct community strings.

SNMP timeout.

Either the device response time is slow or the device is unreachable.

  • Verify the device connectivity.

  • Increase the SNMP Timeout and Retries values in the credential profile.

Failed to fetch table due to: Request timed out.

Either the device response time is slow or the device is unreachable.

Increase the SNMP Timeout and Retries values in the credential profile.

SNMPv3

The configured SNMPv3 security level is not supported on the device.

Device does not support the configured SNMPv3 security level.

Change the SNMPv3 security level to the supported security level in the credential profile.

The SNMPv3 response was not received within the stipulated time.

Either the device response time is slow or the device is unreachable.

Verify the device connectivity.

SNMPv3 Engine ID is wrong.

Incorrect engine ID entered in the credential profile.

Enter the correct SNMPv3 engine ID in the credential profile.

SNMPv3 message digest is wrong.

Failed for one of the following reasons:

  • Either the SNMPv3 authentication algorithm or the device password is incorrect.

  • Network errors.

  • Verify that the correct SNMPv3 authentication algorithm and device password are set in the credential profile.

  • Check for network errors.

SNMPv3 message decryption error.

Cannot decrypt the SNMPv3 message.

Verify that the correct SNMPv3 authentication algorithm is entered in the credential profile.

Unknown SNMPv3 Context.

The configured SNMPv3 context in the credential profile does not exist on the device.

Verify that the configured SNMPv3 context is correct in the credential profile.

Unknown SNMPv3 security name.

Either the SNMPv3 username is incorrect in the credential profile or the SNMPv3 username is not configured on the device.

Verify that the correct SNMPv3 username is set in the credential profile and on the device.

CLI

Login authentication failed.

Incorrect credentials entered in the credential profile.

Verify and reenter the device CLI credentials in the credential profile.

Connection refused.

Either SSH or Telnet service may not be running on the device.

  1. Verify the device connectivity for the supported CLI (port).

  2. Verify whether the SSH or Telnet service is running on the device.

HTTP

Server returned HTTP response code: 401 for URL.

Either the HTTP service is not running or the URL is invalid.

  • Verify whether the HTTP or HTTPS service is running on the device.

  • Verify whether the URL is valid on the server.

Connection refused.

The HTTP or HTTPS service is not running.

Verify whether the HTTP or HTTPS service is running on the device.

HTTP check failed.

Incorrect HTTP credentials entered in the credential profile.

Verify and reenter the device HTTP credentials in the credential profile.

For Cisco Prime Collaboration Release 11.1 and earlier

MSI

Failed to access MSI.

Incorrect MSI credentials entered in the credential profile.

Verify and reenter the device MSI credentials in the credential profile.

Delete a Device Credential Profile

You can delete only unused credential profiles. We recommend that you do not delete the credential profile of a device that is being managed in the Cisco Prime Collaboration Assurance application.

To delete a credential profile:

Procedure

Step 1

Choose Device Inventory > Inventory Management.

For Cisco Prime Collaboration Release 11.5 and later

Choose Inventory > Inventory Management

Step 2

In the Inventory Management page, click Manage Credentials. The credentials for a device that appears first on the list are displayed by default.

Step 3

Select the profile name and click Delete.

Update CDR Data Source Credentials

Cisco Prime Collaboration collects SCS ( number of seconds where loss is greater than 5%) from Cisco Unified CM clusters or Cisco Prime Virtual Network Analysis Module (Prime vNAM). It sends SNMP traps when the voice quality of a call fails to meet a user-defined quality threshold.

Cisco Unified CM calculates the MOS value for an entire call using the Cisco Voice Transmission Quality (CVTQ) algorithm. At the termination of a call, Cisco Unified CM stores the data in Call Detail Records (CDRs) and Call Management Records (CMRs) (for more information on CDR and CMR, see the Cisco Unified Communications Manager Call Detail Records Administration Guide.

To provide the credentials for Unified Communications Manager publisher servers, you must:

  • Provide Cisco Prime Collaboration with credentials.

  • Keep the credentials up-to-date. (Any time you update credentials on a Unified Communications Manager publisher server, you must also update the corresponding credentials in Cisco Prime Collaboration.)

To update credentials, choose Inventory Management > CUCM SFTP Credentials. You can now change the smuser password and view the updates.

For Cisco Prime Collaboration Release 11.5 and later

To update the credentials, choose Alarm & Report Administration > CDR Source Settings > Manage Call Quality Data Sources.

For Cisco Prime Collaboration Release 12.1 SP3 and later

To update the credentials, choose Inventory > Inventory Management > Configure NAM

Configure Unified Communications Applications


Note
You must add the IP address B field to the Unified Communications Server in the domain manager during fulfillment. This field needs to match the Unified Communications Manager local IP address. If this field is not provided, Unified Communications Manager on-boarding will fail with the following error message: Verify name configured in System -> Server matches either the hostname or IP configured in HCM-F for Service Provider or Application Space Address.

Component

Interface

Adjacent Product

Prime Collaboration Assurance

SNMP

Syslog AXL

RTMT

CDR

CMR

Unified Communications Manager

Prime Collaboration Assurance

SNMP

Syslog

RTMT

Unity Connection

Prime Collaboration Assurance

SNMP

Syslog

RTMT

Unified Communications Manager IP

Prime Collaboration Assurance

SNMP

CLI

Router, Switches

Prime Collaboration Assurance

SNMP

Servers

Deployment Service Assurance flow on a per-customer basis.

Procedure

Step 1

Prepare per-customer device for onboarding.

  1. Install or provision Unified Communications Manager, Unity Connection, IM and Presence Service, Customer Premise Equipment and provision the Unified Communications Manager Cluster, VMWare server, IM and Presence server and CPE devices in the domain manager.

  2. Perform an HCM-F customer synchronization to import device data into the Shared Data Repository (SDR).

  3. Configure SNMP and Syslog settings on Unity Connection and IM and Presence, and SNMP settings on CPE (Note: SNMP/Syslog/billing server settings for Unified Communications Manager can be done by CHPA automatically.)

Step 2

On-board devices to Prime Collaboration Assurance via HCM-F.

  1. Ensure necessary credentials are configured for each device.

  2. Add Prime Collaboration Assurance to HCM-F as a Management application.

  3. Add the SFTP credentials to Prime Collaboration Assurance.

  4. Add the customer to Prime Collaboration Assurance as a Monitoring application.

Step 3

Verify each device is at the managed state and monitored by Prime Collaboration Assurance.

Step 4

Configure Assurance Notification Criteria to send alarms to the Northbound interface (optional).

Note 
Prime Collaboration provides three types of NBI notification: SNMP trap, e-mail, and syslog. CISCO-EPM-NOTIFICATION-MIB defines the forwarded SNMP trap message format. Prime Collaboration Assurance supports SNMP version 1 (SNMPv1) and SNMPv2 traps for polling and receiving. Prime Collaboration Assurance forwards traps as SNMPv2 traps. However, trap processing with SNMPv3 is not supported in Prime Collaboration. Syslog messages have a limitation of 1,024 characters (including the heading). Any syslog-based event details may not contain the full information due to this syslog limitation. If the syslog message exceeds this limitation, it is truncated to 1,024 characters by thesyslog sender.

Monitor HCM-F

This section covers steps on monitoring the HCM-F APP node using Prime Collaboration Assurance as a third-party device.

Note

Prime Collaboration supports third-party devices whose manageability depends on MIB-II support.

To monitor HCM-F using Prime Collaboration Assurance perform the following steps:
  1. To ensure that the HCM-F to be monitored has the correct SNMP community-string configured login through SSH, then use the following commands: 
    utils snmp config 1/2c community-string list
  2. If the correct community-string is not listed, use the following command to add a new community-string: 
    utils snmp config 1/2c community-string add
  3. In Prime Collaboration Assurance add HCM-F under the provider.

    Select Operate -> Device Work Center, Add Device.

    Select the provider as Customer; IP address, SNMP credential.

    Note
    If multiple providers were configured in Unified Communications Domain Manager 8.1(x), then select All_Service_Provider as Customer.
  4. Ensure that the HCM-F device is fully discovered and in a Managed state.

Monitor PLM


Note

All_Service_Provider is a name to differentiate from any particular customer. You can make any name you want. Create this first in Cisco Unified Communications Domain Manager or if using Unified Communications Domain Manager 8.1(x) create in HCM-F.

  1. Ensure that the PLM to be monitored has the correct SNMP community-string configured.
  2. Add PLM under the customer All_Service_Providers through Add Device, Provide customer, IP, SNMP v2c community string, and HTTP credentials.
  3. Verify that PLM has reached the managed state. PLM should be discovered as NonCisco.

Monitoring Components and Devices with Prime Collaboration Assurance

Procedure

Step 1

Login to the Prime Collaboration Assurance GUI and select the customer you want to monitor. (You can monitor the 360 degree view of all the components - including partitioned Unity Connection - which are managed for Alarms, Connectivity, Ping, and Hardware.)

Step 2

Monitor the clusters under the Operations tab by selection Inventory > Device Status Summary.

Step 3

Click on the customer name and use the Topology view to view the deployment topology.

Step 4

Monitor the correlation rules of the managed devices under the Alarm and Report Adminstration > Event Customization / Notification Customization tab.

Step 5

Under the UC Performance Monitor tab, you can use the dashboard to monitor the different types of services and of the devices and clusters.

Manage Customers

This section applies only if you have deployed Cisco Prime Collaboration Assurance in MSP mode.

The MSP mode provides multiple customer views. This option is used in managed service provider environments. This view enables you to manage networks and to host services of multiple customers that are being managed by Cisco Prime Collaboration Assurance. You can associate devices to customer.

You can choose if you want all existing managed endpoints or subscribers registered to a publisher inherit the customer name from the publisher. For more information, see Add Devices -Auto Discovery.

Add Customers

To add a customer:

Procedure

Step 1

Choose Assurance Administration > Customer Management.

For Cisco Prime Collaboration Release 11.5 and later

Choose Alarm & Report Administration > Customer Management
Step 2

From the Customer Management page, click Add.

Step 3

In the General Info page, enter the required details, and click Next.

Step 4

In the Devices/Device Group page, select the appropriate devices, and click Save. A message appears asking you to confirm the assigning of customers to the selected device(s). If you want to associate the registered endpoints to the customer to which the publisher or seed device such as Unified CM or VCS is associated, select the Assign Registered Endpoints also check box. A message notifies that the devices are associated with the customer.

Global Customer Selection

On the Cisco Prime Collaboration Assurance home page, you can select customers and filter information accordingly. Rest your mouse over the quick view icon next to the Customer field at the top-right corner of the Cisco Prime Collaboration Assurance user interface. You can select one or more customers for which you want to see data for. You can also select multiple customers at the same time by selecting All Customers to see aggregate information for all customers. By default, data is displayed for all the customers.

If you have logged in Cisco Prime Collaboration Assurance as a user associated with particular customers in Cisco Prime Collaboration Assurance, you can select the option All My Customers from the global customer selection list. You can further select specific customer(s) from your All My Customers group.

If you have logged in Cisco Prime Collaboration Assurance as a user or globaladmin associated with all customers available in Cisco Prime Collaboration Assurance, you can select the option All Customers from the global customer selection list. You can further select specific customer(s) from your All Customers group.

The Cisco Prime Collaboration Assurance user interface filters and shows only the information for the selected customer(s) from the global selection field, across all features such as Inventory Management, and Alarms and Events page.

Note
The Enterprise dashboards (End-Users Impact, Endpoints Utilization, Infrastructure, Topology, Contact Center Topology, depending on the licenses you have) in Cisco Prime Collaboration Assurance do not filter content by default through the global customer selection field. If you select another customer through global selection the user interface will refresh and the home page showing the Customer Summary dashboard appears. To change the customer you need to click the customer name from the Customer Summary dashboard.

For more information on how user roles will also determine the information available to you, see Cisco Prime Collaboration Assurance-Advanced User Roles.

Cisco Prime Collaboration Assurance-Advanced User Roles

User roles are used to define the authorizations of tasks that users can access.

You can be assigned one of the following roles:

  • For Cisco Prime Collaboration Release 11.5 and later

    Report Viewer—Can view and export the reports only. The homepage of Report Viewer is CDR & CMR Reports. The global user interface components like Search, Device Status Summary, Alarms, and Get Advanced are not available for the Report Viewer user role. You can view all the reports except the following:

    • Launch CUCM Reports

    • Administrative Reports

    • Scheduled Reports

  • Helpdesk — Views and accesses network status information only and cannot perform any action on a device or schedule a job that reaches the network.

  • Operator — Performs all Helpdesk tasks and tasks related to the network data collection. Cannot perform any Inventory Management operations such as adding, discovering, or importing devices. Also, an operator cannot configure thresholds for Alarms and Events.

  • Network administrator — Performs all Operator tasks and tasks that result in a network configuration change like credential management, threshold settings, and so on.

  • System administrator — Performs the Assurance user interface-related administration tasks such as backup and restore, maintaining log files, configuring users, and so on.

  • Super administrator — Can perform tasks that both system administrator and network administrator can perform.

Helpdesk is a preselected role that is assigned to every user in Cisco Prime Collaboration Assurance.

For Cisco Prime Collaboration Release 11.5 and later

Report Viewer is a preselected role that is assigned to every user in Cisco Prime Collaboration Assurance.

The roles selected for a user, determines the access to data of other users. For example, a user with the Super Admin role can view all other users, however a user with the Network Administrator role cannot view the users with higher roles such as Super Administrator, or System Administrator, but can look at other user's data whose role is of Operator or Helpdesk.

If you have deployed Cisco Prime Collaboration Assurance in MSP Mode, you can look at customers belonging to another user of the same role, only if you are associated with the customer(s).

If you have deployed Cisco Prime Collaboration Assurance in ENT Mode, you can look at domains belonging to another user of the same role, only if you are associated with the domain(s).

Note: The User Management submenu is not available to the following roles:

For Cisco Prime Collaboration Release 11.5 and later

  1. Report Viewer
  2. Helpdesk
  3. Operator

For Cisco Prime Collaboration Release 11.6 and later

The default user role selection is removed from Cisco Prime Collaboration Assurance.

Note

If Report Viewer user role is selected, the system does not allow the user to choose any other roles and vice versa.

For Cisco Prime Collaboration Release 12.1 SP3 and later

The following roles are supported to provide multiple levels of authorization:

  1. Network Administrator - Performs all Operator tasks and tasks that result in a network configuration change like credential management, and so on

  2. System Administrator - Performs the user interface-related administration tasks.

  3. Super Administrator - Performs tasks that both system administrator and network administrator can perform.

Add a User

You can add a user and assign predefined static roles. The user has access to the Cisco Prime Collaboration Assurance web client only and cannot log in to the Cisco Prime Collaboration Assurance server through the CLI.

To add a user:

Procedure

Step 1

Choose System Administration > User Management.

Step 2

In the User Management page, click Add.

Step 3

In the Add User page, enter the required user details.

Note that because the LDAP server performs authentication, it should have the same user ID as Cisco Prime Collaboration Assurance. For more information, see Configure an LDAP Server.

If you select the LDAP User option, the Password and Confirm Password fields are not displayed.

Step 4

Select the appropriate Cisco Prime Collaboration Assurance roles.

Step 5

Click Save.

To edit user details, select a user at System Administration > User Management and make the necessary changes.

For Cisco Prime Collaboration Release 11.6 and later

To exclude Report Viewer user role from the assigned roles, you have to manually deselect the Report Viewer option and click Save.

As part of your regular system administration tasks, you sometimes must delete users from the Cisco Prime Collaboration Assurance database. However, you cannot delete the Cisco Prime Collaboration Assurance web client default administrator globaladmin.

To delete a user, select the user from System Administration > User Management and click Delete. Any jobs that are scheduled in the deleted user name continue to run until canceled.

Modify User Roles

When the contact information, role, or account status of a user changes, the administrator must edit the corresponding details in the system.

To edit user details, select a user at System Administration > User Management and make the necessary changes.

For Cisco Prime Collaboration Release 11.6 and later

To exclude Report Viewer user role from the assigned roles, you have to manually deselect the Report Viewer option and click Save.

As part of your regular system administration tasks, you sometimes must delete users from the Cisco Prime Collaboration Assurance database. However, you cannot delete the Cisco Prime Collaboration Assurance web client default administrator - globaladmin.

To delete a user, select the user from System Administration > User Management and click Delete. Any jobs that are scheduled in the deleted user name continue to run until they are cancelled.

Configure an LDAP Server

You can configure Cisco Prime Collaboration Assurance to connect to a Lightweight Directory Access Protocol (LDAP) server, to access user information stored in the LDAP server.

You must create an LDAP user from the User Management page to enable the user to log in using LDAP credentials. To add a user, see Add a User and to edit or delete a user, see Modify User Roles.

Cisco Prime Collaboration Assurance supports one primary LDAP server and one backup LDAP server.

To configure LDAP server:

Procedure

Step 1

Choose System Administration > LDAP Settings.

Step 2

In the LDAP Settings page, enter values for all the fields. See Table LDAP Server Configuration for the field descriptions.

Note 

  1. If Cisco Prime Collaboration Assurance must use SSL encryption, check the Use SSL check box and specify port 636.

    For Cisco Prime Collaboration Release 12.1

    LDAP configuration with SSL enabled is not supported.

  2. In case of invalid login, a message indicating that "Invalid Username or Password. Please try again or check LDAP server configuration if you are a LDAP user" appears. This message is applicable for both local and LDAP users.

Step 3

Click Test Connection to check the connectivity to the LDAP server.

Step 4

Upon successful connection, click Apply Settings and restart Cisco Prime Collaboration Assurance Server to log in using LDAP.

Note 

To restart Cisco Prime Collaboration Assurance server, login as root and execute the following commands:

1. Stop the processes:
root@<hostname>~#/opt/emms/emsam/bin/cpcmcontrol.sh stop
2. Check the status of the processes - Verify whether the processes have stopped:
root@<hostname>~#/opt/emms/emsam/bin/cpcmcontrol.sh status
3. Restart the processes:
root@<hostname>~#/opt/emms/emsam/bin/cpcmcontrol.sh start

LDAP Configuration Parameters

For example, Consider Microsoft Active Directory.

Table 4. LDAP Server Configuration

Field

Description

Server IP address

Enter the LDAP server name or IP address.

Optionally enter the Backup LDAP server IP address.

Server Port

Enter the Port number on which the LDAP requests for the server is received.

Non-secure port: 389

Secure SSL port: 636

Optionally enter the Backup LDAP server Port number.

Note 

If the LDAP server is configured to use a non-standard port, that port should be entered here as well.

Admin Distinguished Name

Admin Distinguished Name is the distinguished name to use.

For example in the preceding image there is a user whose name is John Doe in the LDAP directory, so the Admin Distinguished Name will be as follows:

  • CN = John Doe

  • OU = Campus

  • OU = AdminBLR

  • OU = ABC

  • DC = eta

  • DC = com

Admin Password

Enter the password for the LDAP server authentication and reconfirm the password.

Note 

Do not use the pound sign (#) in the password, because the connectivity to the LDAP server fails if the LDAP user password contains the pound sign (#).

LDAP User Search Base

Enter the user search base. LDAP server searches for users under this base.

Search Base is as follows:

  • DC = eta

  • DC = com

Note 

LDAP authentication fails if you enter special characters in the search base.


Note

  1. Cisco Prime Collaboration Assurance supports login to PCA with CN or sAMAccountName or uid attributes of an LDAP user as applicable.

  2. uid attribute of an LDAP user should be unique.

  3. The ampersand (&) character in Distinguished Names (DN) is not allowed in LDAP parameter value.

    To connect to LDAP, enter the following LDAP parameter value - 
    ?CN=hq-prime,OU=Service Access Groups,DC=Megafon,DC=ru?

For a list of supported LDAP servers, see Supported Devices for Cisco Prime Collaboration Assurance.

Update Call Detail Records NAM Credentials

Cisco Prime Collaboration Assurance collects SCS ( number of seconds where loss is greater than 5%) from Cisco Unified CM clusters or Cisco Prime Virtual Network Analysis Module (Prime vNAM). It sends SNMP traps when the voice quality of a call fails to meet a user-defined quality threshold.

Cisco Unified CM calculates the MOS value for an entire call using the Cisco Voice Transmission Quality (CVTQ) algorithm. At the termination of a call, Cisco Unified CM stores the data in Call Detail Records (CDRs) and Call Management Records (CMRs) (for more information on CDR and CMR, see the Cisco Unified Communications Manager Call Detail Records Administration Guide.

To provide the credentials for Unified Communications Manager publisher servers, you must:

  • Provide Cisco Prime Collaboration Assurance with credentials.

  • Keep the credentials up-to-date. (Any time you update credentials on a Unified Communications Manager publisher server, you must also update the corresponding credentials in Cisco Prime Collaboration Assurance.)

To update the credentials, choose CDR Source Settings > Manage Call Quality Data Sources.

For Cisco Prime Collaboration Release 11.5 and later

To update the credentials, choose Alarm & Report Administration > CDR Source Settings > Manage Call Quality Data Sources.

For Cisco Prime Collaboration Release 12.1 SP3 and later

To update the credentials, choose Inventory > Inventory Management > Configure NAM.

Call Classification

Cisco Prime Collaboration Assurance uses call classification to categorize calls in Call Detail Record (CDR) reports.

Cisco Prime Collaboration Assurance determines whether a call fits in system-defined call categories by analyzing the following data:

  • Details from CDRs

  • Device types of the source and target endpoints

  • Direction of the call (incoming or outgoing)

  • Protocol (H.323, MGCP, or SIP)


    Note

    CDR reports older than seven days are purged.

The following table lists system-defined call category types and names, and describes the calls included in the category type.

Category Type Description Category Name
Voicemail Calls to or from voicemail. Unity Voicemail—Calls that meet system-defined criteria for a voicemail call, such as calls to and from Cisco Unity and Cisco Unity Connection.
Note 

You can add user-defined category names to this category type.

Conference Calls to or from a conferencing system. Conference Bridge—Calls that meet system-defined criteria for a call involving a conference bridge.
Note 

You can add user-defined category names to this category type.

ICT Calls to or from an intercluster trunk (ICT).

  • ICT GK Controlled—ICT calls that are gatekeeper controlled.

  • ICT Non-GK Controlled—ICT calls that are not gatekeeper controlled.

VG/Trunk-Outgoing Calls to a voice gateway or a trunk; only OffNet calls are included.
Note 

User-defined dial plans are applied to calls in the VG/Trunk-Outgoing call category.

  • MGCP Gateway Outgoing—Calls to an MGCP voice gateway.

  • H.323 Gateway Outgoing—Calls to an H.323 voice gateway.

  • H.323 Trunk Outgoing—Calls to an H.323 trunk.

    SIP Trunk Outgoing—Calls to a SIP trunk.

VG/Trunk-Incoming Includes calls from a voice gateway or a trunk; only OffNet calls are included.

  • MGCP Gateway Incoming—Calls from an MGCP voice gateway.

  • H.323 Gateway Incoming—Calls from an H.323 voice gateway.

  • H.323 Trunk Incoming—Calls from an H.323 trunk.

    SIP Trunk Incoming—Calls from a SIP trunk.

Tandem A tandem call occurs when both endpoints are voice gateways or trunks. Tandem.
OnNet Trunk Calls where one endpoint is a trunk and the call is not an OffNet call.

For example, the trunk could be used to connect to WebEx or to a PBX.

  • OnNet H.323 Trunk.

  • OnNet SIP Trunk.

Internal Calls that do not fall into any of the above categories. For example, calls where one endpoint is an IP phone and the other endpoint is a voice gateway and the call is not an OffNet call. Internal.
Unknown For system-related reasons, Prime Collaboration could not determine the device type of the endpoints. Unknown.

Cisco Prime Collaboration Assurance places a call in the user-defined call category if:

  • The call has already been categorized as an Internal, VG/Trunk-Outgoing, or OnNet Trunk call.

  • A user-defined dial plan is assigned to the cluster in which the call occurred.

Configure SFTP Settings

If you are using Unified Communications Manager to monitor calls, you must configure SFTP settings.

To configure SFTP settings:

Procedure

Step 1

Choose Assurance Administration > CDR Source Settings > CUCM SFTP Credentials.

For Cisco Prime Collaboration Release 11.5 and later

Choose Alarm & Report Administration > CDR Source Settings > CUCM SFTP Credentials.

For Cisco Prime Collaboration Release 12.1 and later

Choose Inventory > Inventory Management > CUCM/SFTP Credentials.

For Cisco Prime Collaboration Release 12.1 SP3 and later

Choose Inventory > Inventory Management. Click on CUCM SFTP Credentials tab.

Step 2

Enter the required information. For field descriptions, see the table for SFTP Settings Page - Field Descriptions.

Step 3

Click Save.

A popup message window is displayed to confirm whether you want to update the SFTP credentials across all the managed Unified Communications Manager publishers.

Note 

Cisco Prime Collaboration Assurance is added as a billing server in the managed Unified Communications Manager publishers.

Step 4

Click Yes.

SFTP Settings Page - Field Descriptions

For Cisco Prime Collaboration Release 12.1 SP3 and later

The following table describes the fields in the SFTP Settings page.

Table 5. SFTP Settings Page - Field Descriptions

Fields

Description

Username

You cannot change the username from smuser.

This same username, smuser, must be configured in Cisco Unified Communications Manager.

Password

During fresh installation, ensure that the CUCM SFTP Credential is not set by default. You must set the CUCM SFTP password in Inventory Management -> CUCM SFTP Credentials tab.

If credentials is not set, user will not be allowed to add PCA as a CDR Destination in CUCM during device discovery. The application must alert the user to set the CUCM SFTP password stating, "Please configure CUCM SFTP credentials to enable this feature. It can be configured under CUCM SFTP Credentials Tab".

Note 

If you want to add PCA as a CDR destination in CUCM, while initiating device discovery, select the “Add the Prime Collaboration server as a CDR Destination in the Unified CM servers" check box in Discover Devices -> Device Discovery tab under Auto-Configuration option. For more information, see the section on “Discovery Methods”.

For Cisco Prime Collaboration Release 12.1 SP3 and earlier

The default password is smuser. If you change the password here, you must also change the password for smuser in Cisco Unified Communications Manager.

Re-enter Password

Enter Password to confirm.

For Cisco Prime Collaboration Release 12.1 SP3 and earlier

The following table describes the fields in the SFTP Settings page.

Table 6. SFTP Settings Page - Field Descriptions

Fields

Description

Low-Volume Schedule Hours

<day> <timerange>

For each day of the week, timerange indicates the hours during which Cisco Prime Collaboration Assurance processes fewer records. During the low-volume schedule, Cisco Prime Collaboration Assurance performs database maintenance.

Miscellaneous

Wait for Diagnostic Report (min)

Number of minutes that Cisco Prime Collaboration Assurance continues to search, when there is a large volume of data, before displaying the matching records found for a diagnostic report.

Report Data Retention Period (days)

Number of days that data is retained in the Cisco Prime Collaboration Assurance database before being purged.

SFTP

Username

You cannot change the username from smuser.

This same username, smuser, must be configured in Cisco Unified Communications Manager.

Change password check box

For Cisco Prime Collaboration Release 12.1 SP3 and later

During fresh installation, ensure that the CUCM SFTP Credential is not set by default. You must set the CUCM SFTP password in Inventory Management -> CUCM SFTP Credentials tab.

If credentials is not set, user will not be allowed to add PCA as a CDR Destination in CUCM during device discovery. The application must alert the user to set the CUCM SFTP password stating, "Please configure CUCM SFTP credentials to enable this feature. It can be configured under CUCM SFTP Credentials Tab".

Note 

If you want to add PCA as a CDR destination in CUCM, while initiating device discovery, select the “Add the Prime Collaboration server as a CDR Destination in the Unified CM servers" check box in Discover Devices -> Device Discovery tab under Auto-Configuration option. For more information, see the section on “Discovery Methods”.

For Cisco Prime Collaboration Release 12.1 SP3 and earlier

The default password is smuser. If you change the password here, you must also change the password for smuser in Cisco Unified Communications Manager.