CUCM Sample Audit Report: Cisco CUCM with Cisco Audit Logs

Table of Content

Table of Contents

1 Report Information 2 Overview of Comparison Statistics 3 Cisco Audit Logs 4 Detected Changes 5 Detailed Comparison results per object 5.1 Subscribers (Detailed) 5.1.1 Comparison Statistics 5.1.2 Comparison Results 5.2 Administrative Users 5.2.1 Comparison Statistics 5.2.2 Comparison Results 5.3 Class of Service 5.3.1 Comparison Statistics 5.3.2 Comparison Results 5.4 Class of Service Membership 5.4.1 Comparison Statistics 5.4.2 Comparison Results 5.5 User Templates 5.5.1 Comparison Statistics 5.5.2 Comparison Results 5.6 Call Handler Templates 5.6.1 Comparison Statistics 5.6.2 Comparison Results 5.7 Contact Templates 5.7.1 Comparison Statistics 5.7.2 Comparison Results 5.8 Notification Templates 5.8.1 Comparison Statistics 5.8.2 Comparison Results 5.9 Custom Variables 5.9.1 Comparison Statistics 5.9.2 Comparison Results 5.10 Custom Graphics 5.10.1 Comparison Statistics 5.10.2 Comparison Results 5.11 Administrative Replaceable Images 5.11.1 Comparison Statistics 5.11.2 Comparison Results 5.12 Contacts 5.12.1 Comparison Statistics 5.12.2 Comparison Results 5.13 System Distribution Lists 5.13.1 Comparison Statistics 5.13.2 Comparison Results 5.14 System Call Handlers 5.14.1 Comparison Statistics 5.14.2 Comparison Results 5.15 Directory Handlers 5.15.1 Comparison Statistics 5.15.2 Comparison Results 5.16 Interview Handlers 5.16.1 Comparison Statistics 5.16.2 Comparison Results 5.17 Custom Recordings 5.17.1 Comparison Statistics 5.17.2 Comparison Results 5.18 Direct Routing Rules 5.18.1 Comparison Statistics 5.18.2 Comparison Results 5.19 Forwarded Routing Rules 5.19.1 Comparison Statistics 5.19.2 Comparison Results 5.20 Mailbox Stores 5.20.1 Comparison Statistics 5.20.2 Comparison Results 5.21 Mailbox Stores Membership 5.21.1 Comparison Statistics 5.21.2 Comparison Results 5.22 Mailbox Quotas 5.22.1 Comparison Statistics 5.22.2 Comparison Results 5.23 Quota Alert Text 5.23.1 Comparison Statistics 5.23.2 Comparison Results 5.24 Message Aging Policy 5.24.1 Comparison Statistics 5.24.2 Comparison Results 5.25 Aging Alert Text 5.25.1 Comparison Statistics 5.25.2 Comparison Results 5.26 Message Expiration 5.26.1 Comparison Statistics 5.26.2 Comparison Results 5.27 Branches 5.27.1 Comparison Statistics 5.27.2 Comparison Results 5.28 Connection Locations 5.28.1 Comparison Statistics 5.28.2 Comparison Results 5.29 VPIM Locations 5.29.1 Comparison Statistics 5.29.2 Comparison Results 5.30 Unified Messaging Services 5.30.1 Comparison Statistics 5.30.2 Comparison Results 5.31 Accounts Status 5.31.1 Comparison Statistics 5.31.2 Comparison Results 5.32 SpeechView Transcription Service 5.32.1 Comparison Statistics 5.32.2 Comparison Results 5.33 Error Codes 5.33.1 Comparison Statistics 5.33.2 Comparison Results 5.34 Partitions 5.34.1 Comparison Statistics 5.34.2 Comparison Results 5.35 Search Spaces 5.35.1 Comparison Statistics 5.35.2 Comparison Results 5.36 General Configuration 5.36.1 Comparison Statistics 5.36.2 Comparison Results 5.37 Cluster 5.37.1 Comparison Statistics 5.37.2 Comparison Results 5.38 Services 5.38.1 Comparison Statistics 5.38.2 Comparison Results 5.39 Authentication Rules 5.39.1 Comparison Statistics 5.39.2 Comparison Results 5.40 Roles 5.40.1 Comparison Statistics 5.40.2 Comparison Results 5.41 Restriction Tables 5.41.1 Comparison Statistics 5.41.2 Comparison Results 5.42 Licenses 5.42.1 Comparison Statistics 5.42.2 Comparison Results 5.43 License Files 5.43.1 Comparison Statistics 5.43.2 Comparison Results 5.44 Schedules 5.44.1 Comparison Statistics 5.44.2 Comparison Results 5.45 Holiday Schedules 5.45.1 Comparison Statistics 5.45.2 Comparison Results 5.46 Global Nicknames 5.46.1 Comparison Statistics 5.46.2 Comparison Results 5.47 Subject Line Formats 5.47.1 Comparison Statistics 5.47.2 Comparison Results 5.48 Attachment Descriptions 5.48.1 Comparison Statistics 5.48.2 Comparison Results 5.49 Enterprise Parameters 5.49.1 Comparison Statistics 5.49.2 Comparison Results 5.50 Service Parameters 5.50.1 Comparison Statistics 5.50.2 Comparison Results 5.51 Fax Server 5.51.1 Comparison Statistics 5.51.2 Comparison Results 5.52 LDAP Setup 5.52.1 Comparison Statistics 5.52.2 Comparison Results 5.53 LDAP Directory Configuration 5.53.1 Comparison Statistics 5.53.2 Comparison Results 5.54 LDAP Authentication 5.54.1 Comparison Statistics 5.54.2 Comparison Results 5.55 Phone Number Conversion 5.55.1 Comparison Statistics 5.55.2 Comparison Results 5.56 LDAP Custom Filter 5.56.1 Comparison Statistics 5.56.2 Comparison Results 5.57 SMTP Server 5.57.1 Comparison Statistics 5.57.2 Comparison Results 5.58 Smart Host 5.58.1 Comparison Statistics 5.58.2 Comparison Results 5.59 SMPP Providers 5.59.1 Comparison Statistics 5.59.2 Comparison Results 5.60 Conversations 5.60.1 Comparison Statistics 5.60.2 Comparison Results 5.61 Messaging 5.61.1 Comparison Statistics 5.61.2 Comparison Results 5.62 Intrasite Networking 5.62.1 Comparison Statistics 5.62.2 Comparison Results 5.63 Telephony 5.63.1 Comparison Statistics 5.63.2 Comparison Results 5.64 Reports 5.64.1 Comparison Statistics 5.64.2 Comparison Results 5.65 Connection Administration 5.65.1 Comparison Statistics 5.65.2 Comparison Results 5.66 TRAP 5.66.1 Comparison Statistics 5.66.2 Comparison Results 5.67 Disk Capacity 5.67.1 Comparison Statistics 5.67.2 Comparison Results 5.68 PCA 5.68.1 Comparison Statistics 5.68.2 Comparison Results 5.69 RSS 5.69.1 Comparison Statistics 5.69.2 Comparison Results 5.70 Cluster Configuration 5.70.1 Comparison Statistics 5.70.2 Comparison Results 5.71 Fax 5.71.1 Comparison Statistics 5.71.2 Comparison Results 5.72 Unified Messaging Services 5.72.1 Comparison Statistics 5.72.2 Comparison Results 5.73 API Settings 5.73.1 Comparison Statistics 5.73.2 Comparison Results 5.74 Phone System 5.74.1 Comparison Statistics 5.74.2 Comparison Results 5.75 Port Group 5.75.1 Comparison Statistics 5.75.2 Comparison Results 5.76 Port 5.76.1 Comparison Statistics 5.76.2 Comparison Results 5.77 Speech Connect Port 5.77.1 Comparison Statistics 5.77.2 Comparison Results 5.78 Trunk 5.78.1 Comparison Statistics 5.78.2 Comparison Results 5.79 SIP Certificate 5.79.1 Comparison Statistics 5.79.2 Comparison Results 5.80 SIP Security Profile 5.80.1 Comparison Statistics 5.80.2 Comparison Results


1 Report Information

The Comparison report identifies changes between two configuration reports. Optionally, if Cisco audit logs are provided to perform the comparison, the comparison report will contain the user id and timestamp of each change.

To generate a comparison report, specify the earlier (base) report and later (revised/changed) report as input. The base and revised reports must be generated using the same version of the Report Tool.

This comparison report has been generated out of the following base and changed reports, format settings and Cisco audit logs:

Report Information
Report date15/09/2015 4:12:11 PM
Report generated forCluster A - CUC v10
DescriptionCustomer
Comparing the following reports
Base ReportE:\reports\Report_For_Cluster A - CUC v10\CUC
\15Sep2015_1512\html\CUC_Report_Cluster A - CUC v10.htm
Base Report Time (UTC)15/09/2015 5:12:42 AM
Changed ReportE:\reports\Report_For_Cluster A - CUC v10\CUC
\15Sep2015_1610\html\CUC_Report_Cluster A - CUC v10.htm
Changed Report Time (UTC)15/09/2015 6:10:59 AM
Output ReportE:\reports\Report_For_Cluster A - CUC v10\CUC
\15Sep2015_1610\html\diff_20150915161045\CUC_Report_Cluster A - CUC v10.diff.htm
Cisco Audit Logs
Use Cisco Audit LogsYes
Path to Cisco Audit Log filesC:\auditlogs\CUC10
Number of relevant entries in path3
CUCM server timezone - Offset to UTC-7 hours
Comparison Settings
Include Unchanged Records
Include report information
Overview of comparison statistics
Include comparison statistics per object
Include objects without content
Include object descriptions
Include side navigation
Generate Word report
Report Settings
Visual styleBlu Light.css
Template HTMLComparisonTemplate.htm
Template WordBars_Phones_Green_Blue.doc
Report Tool Info
Report Tool Version11.0.1 / 1 Sept 2015
Report Tool LicenseLicensed [Ent 467890]

2 Overview of Comparison Statistics

This chapter summerizes the change(s) found for each configuration object in the base and revised report. The 'Status' column shows the overall comparison result which can be same, not same, not comparable or error. The record column shows how many items of this configuration object have been Updated, Added, Deleted or remain the Same. Within each record, there might be multiple fields (individual settings) be present which are affected by an update.

The 'Change Details' column may include one or multiple entries which contain the detailed information of the configuration change. Click on an an entry to navigate to the configuration object which highlights the change information in a yellow table. Configuration objects in green have been added, configuration objects in red and strikethrough have been deleted. A red and strikethrough value followed by a green value means that the value has been updated and the green value has replaced the value in red.

Comparison Statistics for all objects
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Subscribers (Detailed)same160160000000Compare ok 
Administrative Userssame9090000000Compare ok 
Class of Servicenotsame40310126096300Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
015/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 0: Added record with key 'COS2' Class of ServiceAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )
Class of Service Membershipnotsame4031050320Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
115/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 1: Added record with key 'COS2' Class of Service MembershipAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )
User Templatesnotsame8080176807680246Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
215/09/2015 3:27:24 PM15/09/2015 5:27:24 AMAuditLogChange 2: Deleted record with key 'TnATemplate3' User TemplatesAudit Log id 0 (UTC 15/09/2015 5:27:24 AM User: haroldapp )
Call Handler Templatessame1010000000Compare ok 
Contact Templatessame1010000000Compare ok 
Notification Templatessame2020000000Compare ok 
Custom Variablessame1010000000Compare ok 
Custom Graphicssame2020000000Compare ok 
Administrative Replaceable Imagessame7070000000Compare ok 
Contactssame2020000000Compare ok 
System Distribution Listsnotsame312003313200Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
316/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 3: Updated record 'allvoicemailusers' System Distribution Lists 
416/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 4: Updated field 'Distribution List Members::Distribution List Members' : TnATemplate3Change 3System Distribution Lists 
System Call Handlerssame5050000000Compare ok 
Directory Handlerssame5050000000Compare ok 
Interview Handlerssame1010000000Compare ok 
Custom Recordingssame2020000000Compare ok 
Direct Routing Rulessame4040000000Compare ok 
Forwarded Routing Rulessame3030000000Compare ok 
Mailbox Storessame3030000000Compare ok 
Mailbox Stores Membershipsame170170000000Compare ok 
Mailbox Quotasnotsame0000041300Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
5 - - DetectedChange 5: Updated field '::Send/Receive Quota' from Custom (MB) 52.4288 to Custom (MB) 47.18592 Mailbox Quotas 
Quota Alert Textsame1010000000Compare ok 
Message Aging Policysame4040000000Compare ok 
Aging Alert Textsame000001601600Compare ok 
Message Expirationsame0000020200Compare ok 
Branchessame1010000000Compare ok 
Connection Locationssame1010000000Compare ok 
VPIM Locationssame1010000000compare ok 
Unified Messaging Servicessame1010000000Compare ok 
Accounts Statussame1010000000compare ok 
SpeechView Transcription Servicesame0000040400Compare ok 
Error Codessame5050000000Compare ok 
Partitionssame2020000000Compare ok 
Search Spacessame2020000000Compare ok 
General Configurationsame000001101100Compare ok 
Clustersame1010000000Compare ok 
Servicessame760760000000Compare ok 
Authentication Rulessame4040000000Compare ok 
Rolessame100100000000Compare ok 
Restriction Tablessame6060000000Compare ok 
Licensessame150150000000Compare ok 
License Filessame1010000000compare ok 
Schedulessame6060000000Compare ok 
Holiday Schedulessame2020000000Compare ok 
Global Nicknamessame41204120000000Compare ok 
Subject Line Formatssame000001301300Compare ok 
Attachment Descriptionssame100100000000Compare ok 
Enterprise Parameterssame13701370000000Compare ok 
Service Parameterssame590590000000Compare ok 
Fax Serversame0000050500Compare ok 
Cross-Origin Resource Sharing (CORS)not_comparable----------Not comparable (Base object exists / changed object missing) 
LDAP Setupsame0000030300Compare ok 
LDAP Directory Configurationsame1010000000Compare ok 
LDAP Authenticationsame0000030300Compare ok 
Phone Number Conversionsame0000020200Compare ok 
LDAP Custom Filtersame1010000000Compare ok 
SMTP Serversame000001101100Compare ok 
Smart Hostsame0000000000compare ok 
SMPP Providerssame1010000000Compare ok 
Conversationssame580580000000Compare ok 
Messagingsame130130000000Compare ok 
Intrasite Networkingsame7070000000Compare ok 
Telephonysame160160000000Compare ok 
Reportssame9090000000Compare ok 
Connection Administrationsame9090000000Compare ok 
TRAPsame2020000000Compare ok 
Disk Capacitysame1010000000Compare ok 
PCAsame4040000000Compare ok 
RSSsame1010000000Compare ok 
Cluster Configurationsame2020000000Compare ok 
Faxsame3030000000Compare ok 
Unified Messaging Servicessame7070000000Compare ok 
API Settingssame3030000000Compare ok 
Phone Systemsame1010000000Compare ok 
Port Groupsame1010000000Compare ok 
Portsame2020000000Compare ok 
Speech Connect Portsame1010000000Compare ok 
Trunksame1010000000compare ok 
SIP Certificatesame2020000000Compare ok 
SIP Security Profilesame2020000000Compare ok 


3 Cisco Audit Logs

If Cisco audit logs have been provided, the following table lists the Cisco Audit log entries which have been found in the period between the base and revised report. Each Cisco audit log entry can be linked to a detected change of the configuration object and list the name of the responsible user and the time of the change.

Cisco audit logs need to be collected using Cisco Real Time Monitoring Tool (RTMT) from the Cisco UC servers. Within Report Tool, the path to the folder containing the Cisco audit logs files must be specified before generating the comparison report. In order to process the log files, the UTC time zone of the server must be provided.

If Cisco audit logs are not provided, the report will still contain all configuration changes but without additional auditing information such as userid and accurate timestamps. Aprroximative timestamps (from the database) will still be available for added and modified configuration objects, but not for deleted items. Therefore, to improve the accuracy for auditing purposes it is strongly recommended to collect and provide Cisco audit log files when generating comparison reports.

All changes found are listed in the summarized table below. The 'Detected Change' and 'Detected Config Object' columns contains a link to the detailed change of each configuration object. 'Detected' columns are the result of the comparison engine and link to the relevant Cisco Audit Log entry when matched. Clicking on a detailed change link will navigate to the detected change within the configuration object which are shown in a yellow highlighted box.

Entries which are marked as 'Possible duplicate of' are caused by multiple updates to the same object. For these objects, the responsible user and the time of change cannot be clearly determined and any change could have been performed by any of the involved users. If multiple add, delete or update actions have been performed to the same configuration object within the comparison period, only the last edit will be associated with the change.

Audit Log entries with links to detailed change
IDDate Time (Local)Date Time (UTC)Server TimeUser ID of changeDetected ChangesDetected Config ObjectAudit DetailsClient AddressNode IDcdrtime
015/09/2015 3:27:24 PM15/09/2015 5:27:24 AM22:27:24.338haroldappChange 2: Deleted record with key 'TnATemplate3'User TemplatesDeleted User Template with Alias=TnATemplate3 {objectId=baecc7c0-374a-4baf-9d4e-49a1dc41d527; }10.5.1.25CUC10521442294844
115/09/2015 3:27:32 PM15/09/2015 5:27:32 AM22:27:32.058haroldapp  Updated Quotas for all Mailbox Stores {send=12582912; receive=47185920; warn=11534336; }10.5.1.25CUC10521442294852
215/09/2015 3:27:40 PM15/09/2015 5:27:40 AM22:27:40.180haroldappChange 0: Added record with key 'COS2'
Change 1: Added record with key 'COS2'
Class of Service
Class of Service Membership
Created Class of Service with DisplayName=COS2 {updateBroadcastMessage=false; enableVideoMessaging=f ...10.5.1.25CUC10521442294860

4 Detected Changes

This chapter lists the configuration changes detected between the base and revised report. These are the changes that the UPLINX comparison algorithm has detected.

If Cisco audit logs are not provided, the report will only contain detected configuration changes. Timestamps are extracted from the database and will be available for added and modified configuration objects, but not for deleted items. If multiple add or update actions have been performed to one object during the comparison period, only the last edit will be associated with the change. Therefore, to improve the accuracy for auditing purposes it is strongly recommended to collect and provide the Cisco audit log files when generating comparison reports.

All changes found are listed in the summarized table below. The 'Detected Change' and 'Detected Config Object' columns contains a link to the detailed change of each configuration object. 'Detected' columns are the result of the comparison engine and list the relevant Cisco Audit Log entry when available. Clicking on a detailed change link will navigate to the detected change within the configuration object which are shown in a yellow highlighted box.

The 'Time Source' column can be one of the following values:

Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
015/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 0: Added record with key 'COS2' Class of ServiceAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )
115/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 1: Added record with key 'COS2' Class of Service MembershipAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )
215/09/2015 3:27:24 PM15/09/2015 5:27:24 AMAuditLogChange 2: Deleted record with key 'TnATemplate3' User TemplatesAudit Log id 0 (UTC 15/09/2015 5:27:24 AM User: haroldapp )
316/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 3: Updated record 'allvoicemailusers' System Distribution Lists 
416/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 4: Updated field 'Distribution List Members::Distribution List Members' : TnATemplate3Change 3System Distribution Lists 
5 - - DetectedChange 5: Updated field '::Send/Receive Quota' from Custom (MB) 52.4288 to Custom (MB) 47.18592 Mailbox Quotas 

5 Detailed Comparison results per object

This chapter summerizes the change(s) found for each configuration object in the base and revised report. It shows first the comparison statistics with changes found, followed by the detailed object differences.

5.1 Subscribers (Detailed)

Subscribers are Unity Connection users with voice mailboxes who will need to send and receive voice messages, and who may be able to use other Connection features such as Personal Call Transfer Rules and the Cisco Unity Inbox.

5.1.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Subscribers (Detailed)same160160000000Compare ok 

5.1.2 Comparison Results

No changes.

5.2 Administrative Users

For users who do not need to send or receive voice messages, but need to be given access to administer the system. A user account that is set up without a voice mailbox does not have a phone extension and is not counted as a licensed user.

Users without voice mailboxes typically require only administrative access to Connection. These users can have any of six predefined administrator roles assigned to them. Roles specify which tasks administrators can do in Cisco Unity Connection Administration.

5.2.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Administrative Userssame9090000000Compare ok 

5.2.2 Comparison Results

No changes.

5.3 Class of Service

In Cisco Unity Connection, some of the features that are available to users with voice mailboxes are controlled by class of service (COS), including features for which you need user licenses. You can update the settings in a COS to enable or disable features and functionality at any time. The changes that you make affect all COS members.

Because a COS defines limits and permissions for using Cisco Unity Connection, its settings should be appropriate for the group of users that you are adding. For example, a COS:

Keep in mind that if you change the COS that is specified on a user template page, any user accounts that have already been created based on that template are not reassigned to the new COS. In contrast, when you modify the settings in a COS, the changes affect both new and existing members, so you can update COS settings before and after you create user accounts. You can also reassign a user to a different COS at any time.

5.3.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Class of Servicenotsame40310126096300Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
015/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 0: Added record with key 'COS2' Class of ServiceAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )

5.3.2 Comparison Results

Class of Service
NameDetails
COS2
Detected Change ID0
Detected ChangeAdded record with key 'COS2'
Detected ObjectClass of Service
Detected Date (UTC)15/09/2015 5:27:39 AM
Detected Date (Local)15/09/2015 3:27:39 PM
Auditlog ID2
Audit Userharoldapp
Audit DetailsCreated Class of Service with DisplayName=COS2 {updateBroadcastMessage=false; enableVideoMessaging=f ...
Audit Server Time22:27:40.180
Class of Service
Display NameCOS2
Recorded Name
Allow User to Record NameY
Maximum Length (secs)30
Directory Listing
Allow Users to Choose to Be Listed in the DirectoryY
Greetings
Maximum Length (secs)90
Licensed Features
Allow Users to Access Voice Mail Using an IMAP Client and/or Single InboxN
Allow Users to Use the Web Inbox and RSS FeedsN
Allow Access to Advanced FeaturesN
Allow Users to Access SpeechView Transcription ServiceN
Enable Video
Allow Users to Playback and Record Video GreetingsN
Allow Outside CallersN
Features
Allow Users to Use Personal Call Transfer RulesN
Allow Users to Use the Messaging Assistant Y
Allow Users to Use Unified Client to Access Voice Mail N
Alternate Extensions
Allow Users to View Administrator-Defined Alternate ExtensionsN
Allow Users to Manage Their User-Defined Alternate ExtensionsN
Message Length
Maximum Length (secs)300
Message Options
Allow Users to Send Messages to System Distribution ListsY
Delete Messages Without Saving to Deleted Items FolderN
Users Can Reply to Messages from Other Users by Calling ThemN
Users Can Reply to Messages from Unidentified Callers by Calling ThemN
Require Secure MessagingPrivate
Private Distribution Lists
Maximum Lists Per User (1-99)25
Maximum Members Per List (1-999)99
Call Transfer
Allow Users to Change Call Screening OptionsN
Allow Users to Change Call Holding OptionsN
Restriction Tables
OutcallingDefault Outdial
TransfersDefault Transfer
FaxDefault Fax

5.4 Class of Service Membership

A COS is specified in each user template; thus, a user is assigned to the COS that is specified in the template on which the user account is based. If you find that the settings for a particular COS are no longer appropriate for an individual user or several users, you can reassign the users to another COS at any time. (Changing the COS that is specified in a template does not affect user accounts that have already been created.)

The following lists the users as members of COS:

5.4.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Class of Service Membershipnotsame4031050320Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
115/09/2015 3:27:40 PM15/09/2015 5:27:40 AMAuditLogChange 1: Added record with key 'COS2' Class of Service MembershipAudit Log id 2 (UTC 15/09/2015 5:27:40 AM User: haroldapp )

5.4.2 Comparison Results

Class of Service Membership
Class Of ServiceMembers
COS2
Detected Change ID1
Detected ChangeAdded record with key 'COS2'
Detected ObjectClass of Service Membership
Detected Date (UTC)15/09/2015 5:27:39 AM
Detected Date (Local)15/09/2015 3:27:39 PM
Auditlog ID2
Audit Userharoldapp
Audit DetailsCreated Class of Service with DisplayName=COS2 {updateBroadcastMessage=false; enableVideoMessaging=f ...
Audit Server Time22:27:40.180
< No records found >

5.5 User Templates

Each user that you add in Cisco Unity Connection is based on a template. Settings from the template are applied to the user as the new user is created or imported. (Changes to template settings do not affect existing users.)

Users with voice mailboxes are end users; users without voice mailboxes are system administrators.

Connection has the following User Template types

5.5.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
User Templatesnotsame8080176807680246Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
215/09/2015 3:27:24 PM15/09/2015 5:27:24 AMAuditLogChange 2: Deleted record with key 'TnATemplate3' User TemplatesAudit Log id 0 (UTC 15/09/2015 5:27:24 AM User: haroldapp )

5.5.2 Comparison Results

User Templates
NameDetails
TnATemplate3
Detected Change ID2
Detected ChangeDeleted record with key 'TnATemplate3'
Detected ObjectUser Templates
Detected Date (UTC)-
Detected Date (Local)-
Auditlog ID0
Audit Userharoldapp
Audit DetailsDeleted User Template with Alias=TnATemplate3 {objectId=baecc7c0-374a-4baf-9d4e-49a1dc41d527; }
Audit Server Time22:27:24.338
Basic Settings
Settings
Name
Display Name TnATemplate3
Display Name Generation First Name, Then Last Name
Phone
Outgoing Fax Server Fax Server
Partition cuc1052 Partition
Search Scope cuc1052 Search Space
Phone System PhoneSystem
Class of Service COS1
Active Schedule Weekdays
Set for Self-enrollment at Next Login Y
List in Directory Y
Send Non-Delivery Receipts on Failed Message Delivery Y
Skip Password When Calling From a Known Extension N
Use Short Calendar Caching Poll Interval N
Location
Address Address 1
Building Building 1
City City 1
State State 1
Country TW
Postal Code 1111
Time Zone System Default Time Zone
Language System Default Language
Department
Manager Manager 1
Billing ID BillID123
Generate SMTP Proxy Address From Corporate Email Address Y
Password Settings
Web Application
Web Applications Password Settings
Locked by Administrator N
User Cannot Change N
User Must Change at Next Sign-In Y
Does Not Expire N
Authentication Rule Recommended Web Application Authentication Rule
Voice Mail
Voice Mail Pin Settings
Locked by Administrator N
User Cannot Change N
User Must Change at Next Sign-In Y
Does Not Expire N
Authentication Rule Recommended Voice Mail Authentication Rule
Roles
Settings Remote Administrator
Technician
Mailbox Access Delegate Account
Audit Administrator
Transfer Rules
Settings
Rule Name Enabled Extension End Date
Alternate N    
Closed N    
Standard Y    
Message Settings
Settings
Maximum Message Length 300
Callers Can Edit Messages Y
Language That Callers Hear Inherit Language from Caller
Message Urgency
Message Urgency Mark Normal
Message Sensitivity
Message Sensitivity Mark Normal
Message Security
Mark Secure N
Play After Message Recording
Play After Message Recording System Default Recording
After Message Action
Type User with Mailbox
Action Primary
Attempt Transfer
Message Actions
Settings
Voicemail Accept the Message
Email Accept the Message
Fax Accept the Message
Delivery Receipt Accept the Message
Relay Address
Caller Input Keys
Settings
Caller Input Keys
Key Action Target Status
# Skip Greeting   Locked
* Send caller to Sign-In Locked
0 Send caller to Operator Unlocked
1 Ignore key   Unlocked
2 Ignore key   Unlocked
3 Ignore key   Unlocked
4 Ignore key   Unlocked
5 Ignore key   Unlocked
6 Ignore key   Unlocked
7 Ignore key   Unlocked
8 Ignore key   Unlocked
9 Ignore key   Unlocked
Wait for Additional Digits 1500
Prepend Digits to Dialed Extensions
Enabled N
Digits to Prepend
MailBox
Settings
Mailbox Settings
Respond to Requests for Read Receipts Y
Message Aging Policy Default System Policy
Mailbox Quotas
Type Use System Settings
Mailbox Store Information
Mailbox Store Display Name 1
Phone Menu
Settings
Touchtone Conversation Menu Style Full
Conversation Volume Medium
Conversation Speed Normal
Time Format
Time Format 12-Hour Clock
Conversation Style
Touchtone Conversation Classic Conversation
Finding Messages with Message Locator
Enable N
Message Locator Sort Order Last In, First Out
Enable Phone View N
When Responding to Menus
Times to Repeat Menu When User Does Not Respond 1
Wait for First Touchtone or Voice Command 5000
Wait for Additional Key Presses When Entering Names, Extensions, and Passwords 3000
Wait for Additional Key Presses When Entering Multiple Digit Menu Options 1500
After Logon, Play
User's Recorded Name Y
Alternate Greeting Notification N
User's New Messages Automatically Y
When Exiting the Conversation
Action Call Handler
Options Opening Greeting
Go Directly to Greetings
Playback Message Settings
Playback Message Settings
Message Volume Medium
Message Speed Normal
For New Messages, Play
Message Count Totals N
Voice Message Counts Y
Email Message Counts N
Fax Message Counts N
Receipt Message Counts N
For Saved Messages, Play
Saved Message Count Y
For Draft Messages, Play
Draft Message Count N
Before Playing Messages, Play
Message Type Menu N
New Message Play Order
Sort by Message Type Urgent Voice Messages
Normal Voice Messages
Urgent Faxes
Normal Faxes
Urgent Email
Normal Email
Receipts and Notices
Then By Newest first
Saved Message Play Order
Sort by Message Type Urgent Voice Messages
Normal Voice Messages
Urgent Faxes
Normal Faxes
Urgent Email
Normal Email
Receipts and Notices
Then By Oldest first
Deleted Message Play Order
Order Oldest first
Before Playing Each Message, Play
Sender's Information Y
Sender's ANI N
Include Extension N
Message Number Y
Time the Message was Sent N
Message Duration N
While Playing Each Message
Fast Forward Message by 5000
Rewind Message by 5000
When Disconnected or User Hangs Up During Message Playback
Create a Message Bookmark N
Mark a New Message New
After Playing Each Message, Play
Sender's Information N
Include Extension N
Sender's ANI N
Message Number N
Time the Message was Sent Y
Message Duration N
After Playing the After Message Menu
Automatically Advance to the Next Message N
When Deleting a Message
Confirm Deletions of New and Saved Messages N
Send Message Settings
Settings
Broadcast Messages
User Can Send Broadcast Messages to Users on This Server N
User Can Update Broadcast Messages Stored on This Server N
Message Addressing and Sending
Enter a Recipient By Spelling the Last Name Then First Name
Confirm Recipient by Name N
Continue Adding Names After Each Recipient N
Automatically Add Recipients to Addressing Priority List N
Allow Users to Save Draft Messages N
Retain Urgency Flag When Forwarding or Replying to Messages N
When a Call Is Disconnected or the User Hangs Up Send Message
Greetings
Settings
Greeting Enabled End Date Audio Source Video Source
Alternate N -- System Blank
Busy N -- System Blank
Error Y No End Date System Blank
Internal N -- System Blank
Off Hours N -- System Blank
Standard Y No End Date System Blank
Holiday N -- System Blank
Post Greeting Recording
Settings
Play Post Greeting Recording
Play Post Greeting Recording Do Not Play Recording
Post Greeting Recording
Post Greeting Recording Selection < None >
Notification Devices
Settings
Display Name Status Type Destination Phone System
Pager Disabled Pager   PhoneSystem
Work Phone Disabled Phone   PhoneSystem
Home Phone Disabled Phone   PhoneSystem
Mobile Phone Disabled Phone   PhoneSystem
SMTP Disabled SMTP    
HTML Disabled HTML    
Unified Messaging Accounts
Settings
< No records found >
Video Service Accounts
Settings
< No records found >

5.6 Call Handler Templates

Each call handler that you add in Cisco Unity Connection is based on a template. Settings from the template are applied to the call handler as the call handler is created. (Changes to template settings do not affect existing call handlers.)

Connection comes with the following predefined call handler templates, which you can modify but not delete:

Before you create call handlers, review the settings in the template that you plan to use and determine whether you need to make changes or create new templates. For each template, you will want to consider enabling the appropriate transfer, caller input, greetings, and message settings for the call handlers that you plan to create. If you change settings on a call handler template, the new settings will be in effect only for new call handlers that are created by using that template.

Deleting a call handler template will not affect any call handlers that were based on that template when they were created. Note that you cannot delete the default templates.

5.6.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Call Handler Templatessame1010000000Compare ok 

5.6.2 Comparison Results

No changes.

5.7 Contact Templates

Each contact that you add in Cisco Unity Connection is based on a template. Settings from the template are applied to the contact as the new contact is created or imported. (Changes to template settings do not affect existing contacts.)

5.7.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Contact Templatessame1010000000Compare ok 

5.7.2 Comparison Results

No changes.

5.8 Notification Templates

Intelligent Notifications deliver rich, customizable, and actionable voice message notifications. When connected to the corporate network, they provide users the ability to play, reply, forward, mark unread, and delete a specific message.

The following Notification Templates are configured:

5.8.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Notification Templatessame2020000000Compare ok 

5.8.2 Comparison Results

No changes.

5.9 Custom Variables

Custom variables give flexibility to populate content in an HTML notification. Administrators are allowed to create different custom variables that can be used while creating the HTML-based notification templates. For example, the custom variables can be used in case of defining a particular company's name, address, any numbers, or URLs.

5.9.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Custom Variablessame1010000000Compare ok 

5.9.2 Comparison Results

No changes.

5.10 Custom Graphics

Custom Graphics define graphic objects which can be inserted in an HTML notification. Administrators are allowed to create Custom Graphics that can be used while creating the HTML-based notification templates.

5.10.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Custom Graphicssame2020000000Compare ok 

5.10.2 Comparison Results

No changes.

5.11 Administrative Replaceable Images

Replaceable Images overwrite default images used by notifications to users.

The administrator has rights to replace the default images for the following status items:

These images can anytime reset to default through the Restore Default option given on the Search Replaceable Images page. The addition or deletion of any image is not allowed in the given default list.

5.11.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Administrative Replaceable Imagessame7070000000Compare ok 

5.11.2 Comparison Results

No changes.

5.12 Contacts

A system contact is an entity in the Connection database that does not have access to any Connection features such as voice messaging. A system contact may represent a person in your company who has a voice mail account on another system. A system contact might also represent a customer or vendor who does not need a voice mailbox, but has frequent contact with Connection users.

Keep in mind that directory access to system contacts is available only to internal users who are using the VUI (voice-recognition conversation), by using the Call-command from either the Connection main menu or from the internal directory. System contacts are not available to users who are using the TUI, or from the external directory.

Also note that system contacts are never accessible by external callers, from the directory, TUI, or VUI.

5.12.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Contactssame2020000000Compare ok 

5.12.2 Comparison Results

No changes.

5.13 System Distribution Lists

When a user addresses a message to a system distribution list, the local Cisco Unity Connection location parses the distribution list membership. The sending location first addresses messages to any VPIM users that are on the distribution list. Next, the sending location checks to see if there are any remote Connection users in the membership; if so, it sends a single message to each location that homes these remote users, addressed to the distribution list (the home locations each parse the message and deliver to their local users). Finally, the sending location checks for local users in the distribution list membership, and delivers the message to each of them.

Connection includes the following predefined system distribution lists: All Voice Mail Users, Undeliverable Messages, and All Voicemail-Enabled Contacts. Each Connection server in your organization has a distinct version of each of these lists. If you have not changed the names of these lists to be unique, during initial replication each server automatically adds the remote server name to the display name of any remote lists whose names overlap with local list names.

By default, the predefined lists on each Connection location have the same recorded voice name, and the All Voice Mail Users and All Voicemail-Enabled Contacts lists have the same extension at each location (the Undeliverable Messages list by default is not assigned an extension, because users do not typically address messages to this list). When setting up Digital Networking, you should consider modifying the recorded voice name of each All Voice Mail Users list and each All Voicemail-Enabled Contacts list; if you do not, users can hear a confusing list of choices when they address messages by name to one of these lists. When users address by extension to a list whose extension overlaps that of another list, they reach the first list that is located when Connection searches the partitions of the user search space in order.

Tip : Distribution lists can be nested such that a distribution list contains other lists. You can create one master All Voice Mail Users distribution list that contains the All Voice Mail Users list of each Connection location.

The following distribution lists are configured:

5.13.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
System Distribution Listsnotsame312003313200Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
316/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 3: Updated record 'allvoicemailusers' System Distribution Lists 
416/12/2014 2:22:43 PM16/12/2014 4:22:43 AMDetectedChange 4: Updated field 'Distribution List Members::Distribution List Members' : TnATemplate3Change 3System Distribution Lists 

5.13.2 Comparison Results

Distribution List
NameDetails
allvoicemailusers
Detected Change ID3
Detected ChangeUpdated record 'allvoicemailusers'
Detected ObjectSystem Distribution Lists
Detected Date (UTC)16/12/2014 4:22:43 AM
Detected Date (Local)16/12/2014 2:22:43 PM
Child ID4
Distribution List
Aliasallvoicemailusers
Display NameAll Voice Mail Users
Extension99991
Partitioncuc1052 Partition
Replicate to Remote Sites Over Intersite LinksY
Allow ContactsN
Accept messages from Foreign SystemN
Replicate to SRSV BranchesY
Distribution List Members
Distribution List MembersTnATemplate3
Detected Change ID4
Detected ChangeUpdated field 'Distribution List Members::Distribution List Members' : TnATempl ...
Detected ObjectSystem Distribution Lists
Detected Date (UTC)16/12/2014 4:22:43 AM
Detected Date (Local)16/12/2014 2:22:43 PM
Parent ID3
Alternate Names
Alternate Names

5.14 System Call Handlers

Interview handlers collect information from callers by playing a series of questions that you have recorded, and then recording the answers offered by callers. For example, you might use an interview handler to take sales orders or to gather information for a product support line.

You can specify who receives the messages for the interview handler, whether the message is marked for dispatch delivery, whether the message is marked urgent, and what action to take next on the call after a message is left.
When all the answers have been recorded, they are forwarded as a single voice message, with beeps separating the answers, to the recipient (user or distribution list) that you designate in the interview handler configuration.

5.14.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
System Call Handlerssame5050000000Compare ok 

5.14.2 Comparison Results

No changes.

5.15 Directory Handlers

Directory handlers provide directory assistance that callers can use to reach Cisco Unity Connection users who have mailboxes and who are listed in the directory.

When a caller searches for a user name or part of a name, a directory handler looks up the extension and routes the call to the appropriate user. Callers can also enter an extension to place a call from a directory handler; the extension is checked against the applicable outcalling restriction table if the caller is a user, or against the Default Outdial restriction table if the caller is an outside caller.
There are two types of directory handlers:

5.15.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Directory Handlerssame5050000000Compare ok 

5.15.2 Comparison Results

No changes.

5.16 Interview Handlers

Interview handlers collect information from callers by playing a series of questions that you have recorded, and then recording the answers offered by callers. For example, you might use an interview handler to take sales orders or to gather information for a product support line.

You can specify who receives the messages for the interview handler, whether the message is marked for dispatch delivery, whether the message is marked urgent, and what action to take next on the call after a message is left.
When all the answers have been recorded, they are forwarded as a single voice message, with beeps separating the answers, to the recipient (user or distribution list) that you designate in the interview handler configuration.

5.16.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Interview Handlerssame1010000000Compare ok 

5.16.2 Comparison Results

No changes.

5.17 Custom Recordings

Indicate whether Cisco Unity Connection plays a recording to callers before allowing them to leave a message for the user or call handler. You can also indicate whether all callers hear the recording or only unidentified callers:

Default: Do Not Play Recording.

5.17.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Custom Recordingssame2020000000Compare ok 

5.17.2 Comparison Results

No changes.

5.18 Direct Routing Rules

Direct rules handle calls from users and outside callers that are dialed directly to Connection. The predefined direct routing rules are:

5.18.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Direct Routing Rulessame4040000000Compare ok 

5.18.2 Comparison Results

No changes.

5.19 Forwarded Routing Rules

Forwarded rules handle calls that are forwarded to Connection from either a user extension or from an extension that is not associated with a user account (such as a conference room). The predefined forwarded routing rules are:

5.19.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Forwarded Routing Rulessame3030000000Compare ok 

5.19.2 Comparison Results

No changes.

5.20 Mailbox Stores

A mailbox store is a database for voice messages (who each message was sent to, when it was sent, the location of the WAV file on the hard disk, and so on).It points to an operating-system directory for voice message WAV files.

An administrator with the required permissions can create up to four additional mailbox stores. Each additional mailbox store includes:

Although there is one mailbox-store database for each mailbox store, there is only one directory database for the entire system. If you create an additional mailbox store and move the mailboxes for selected users to the new store, the directory information for the users remains in the directory database that was created when Connection was installed.

After you create a new mailbox store, you can either move existing mailboxes into the new store or you can create new mailboxes in the new store.

5.20.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Mailbox Storessame3030000000Compare ok 

5.20.2 Comparison Results

No changes.

5.21 Mailbox Stores Membership

This section lists the membership of user mailboxes within the mailbox stores:

5.21.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Mailbox Stores Membershipsame170170000000Compare ok 

5.21.2 Comparison Results

No changes.

5.22 Mailbox Quotas

To help control the size of user voice mailboxes, Cisco Unity Connection lets you specify quotas, or limits, on the maximum size of voice mailboxes. By default, Connection is configured with the following systemwide mailbox size quotas:

Quota Level Mailbox Size That Triggers Quota Action Action When Quota Is Reached Recording Time in Minutes Before Quota Is Reached
G.711 Mu-Law G.711 A-Law G.726 32 Kbps PCM 8 kHz G.729a
Warning 12 megabytes The user is warned that the mailbox is reaching the maximum size allowed. 25 25 50 50 200
Send 13 megabytes The user is prevented from sending any more voice messages. 27 27 54 54 217
Send/ Receive 14 megabytes The user is prevented from sending or receiving any more voice messages. 31 31 61 61 246

The following following systemwide mailbox size quotas are configured:

5.22.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Mailbox Quotasnotsame0000041300Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
5 - - DetectedChange 5: Updated field '::Send/Receive Quota' from Custom (MB) 52.4288 to Custom (MB) 47.18592 Mailbox Quotas 

5.22.2 Comparison Results

System-wide Mailbox Quotas
Send/Receive QuotaCustom (MB) 52.4288
Custom (MB) 47.18592
Detected Change ID5
Detected ChangeUpdated field '::Send/Receive Quota' from Custom (MB) 52.4288 to
Detected ObjectMailbox Quotas
Detected Date (UTC)-
Detected Date (Local)-

5.23 Quota Alert Text

The system will send mailbox quota alert emails to users once a mailbox quota has been reached. This section defines the subject line and body text fields for this alert email. Each language that is installed on the system has a separate mailbox quota alert.

The following mailbox quota alerts messages are defined:

5.23.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Quota Alert Textsame1010000000Compare ok 

5.23.2 Comparison Results

No changes.

5.24 Message Aging Policy

To help ensure that the hard disk where voice messages are stored does not fill up, you can configure Cisco Unity Connection message aging rules to automatically:

You can enable or disable these message aging rules, and you can specify a different number of days for each rule. You can also enable or disable the message aging policy; disabling the policy means that the rules are not enforced regardless of their settings.

If the message aging policy is enabled, and if one or more message aging rules are enabled, you can still disable message aging for individual users on the Voice Mailbox page. However, if the message aging policy is disabled, you cannot enable it for individual users.

5.24.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Message Aging Policysame4040000000Compare ok 

5.24.2 Comparison Results

No changes.

5.25 Aging Alert Text

For each message aging rule, you can specify whether Connection sends email alerts to users prior to taking the aging action that is associated with the rule. This gives users time to review and act on the applicable messages. You specify the number of days between the time that Connection sends the alert and the time that the message aging action takes place.

Alerts cannot be sent to users unless the Corporate Email Address field for each user contains a valid email address. Connection must also be configured to relay messages through an SMTP smart host.

You can customize the text in the email alerts or you can use the default text. The default subject line and body text are different for the alerts related to each aging rule, and they can be customized separately. All message aging policies use the same five rules.

5.25.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Aging Alert Textsame000001601600Compare ok 

5.25.2 Comparison Results

No changes.

5.26 Message Expiration

The Message Recording Expiration feature guarantees that a voice message that is stored on the Cisco Unity Connection server cannot be listened to after it reaches a set expiration date, regardless of whether the message has been forwarded to another Connection recipient. Message Recording Expiration is a systemwide setting, and thus cannot be applied only to a subset of users.

You set the number of days after which messages arrive that they will expire. At expiration, message recordings are automatically replaced with a decoy recording that says, 'The message has expired.'

Typically, message aging rules are sufficient for enforcing message-retention policies. Note, however, that when a message is forwarded, the forwarded message is considered a new message and its age is reset. If you are concerned that users may forward messages in an attempt to circumvent the message-retention policy, consider enabling the Message Recording Expiration feature. The message recording and transcription (if any) expire based on the date that the original copy of the message arrived, regardless of user forwarding.

By default, the Message Recording Expiration feature is not enabled.

If you enable the Message Recording Expiration feature, we recommend that you configure the expiration time frame to be two to three times longer than the message aging time frame. (For example, if all of your messages are marked secure by default and you have a message aging policy set to permanently delete all secure messages older than 60 days, configure message recordings to expire in 180 days.)

Note that the Message Recording Expiration feature does not apply to messages that have been forwarded to personal email addresses or to message recordings that have been saved locally to user workstations. To prevent users from saving local copies or forwarding voice messages to personal email addresses, consider configuring Connection to mark all messages as secure.

Connection applies the Message Recording Expiration feature to messages in the mailboxes of recipients that are homed on the Connection server. For example, if User A homed on Connection server A sends a message to User B homed on Connection server B, the message will be subject to message expiration only if the Message Recording Expiration feature is enabled on server B.

5.26.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Message Expirationsame0000020200Compare ok 

5.26.2 Comparison Results

No changes.

5.27 Branches

Cisco Unity Connection Survivable Remote Site Voicemail (Connection SRSV) is a backup voicemail solution that allows you to receive voice messages during WAN outages. This is a new feature starting with CUC version 9.1. It works in conjunction with Cisco Unified Survivable Remote Site Telephony (SRST) for providing voicemail service to a branch when the connectivity with the central Connection voicemail service is lost.

Connection SRSV is used in the centralized Cisco Unified Communications Manager and Cisco Unity Connection environment with multiple branch offices or small sites. It provides limited voicemail and auto-attendant features that remain in synchronization with the central Connection voicemail service so that when the WAN outage or failure occurs, the Connection SRSV solution can provide voicemail service to the subscribers at the branch.

The following branches are configured:

5.27.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Branchessame1010000000Compare ok 

5.27.2 Comparison Results

No changes.

5.28 Connection Locations

Central to how Digital Networking works is an object referred to as a Cisco Unity Connection location. Each Connection server (or cluster) on the network is represented by a single Connection location, which is created locally during installation and which cannot be deleted from the server itself. When you join the server (or cluster) to a Digital Network, a Connection location is created for the server (or cluster) on all other locations in the network, and these locations automatically begin to perform directory synchronization with the new location. If you remove the server (or cluster) from the Digital Network, the corresponding Connection location is removed from all other locations on the network, and its directory information is automatically removed from these locations (and vice versa). A Connection location can only belong to a single Digital Network. As soon as you join one server to a location on the Digital Network, any other locations on the network are notified of the new location and begin to exchange directory information with the new location.

All objects that you create on a particular location are said to be "homed" on that location. To modify the properties of an object or to delete the object, you must use the administration tools on the location that homes the object. Each location has its own directory of users and other objects, and replicates a subset of these objects and their properties to other locations; the collection of objects and object properties that are replicated among locations is referred to as the Connection directory.

In the context of Digital Networking, an object that is homed on a location is sometimes referred to as local for that location (for example, a local user) and an object that is homed on a different location is referred to as remote.

5.28.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Connection Locationssame1010000000Compare ok 

5.28.2 Comparison Results

No changes.

5.29 VPIM Locations

When you use the recommended approach of configuring a single Cisco Unity Connection location on the Digital Network as a bridgehead to handle all VPIM locations, the VPIM location data and all contacts at the VPIM location (including automatically created contacts) are replicated to other locations in the network. When a VPIM message is sent to or from a user at another Connection location, the message first passes to the bridgehead, which handles forwarding the message to the destination server.

The following VPIM locations are configured:

5.29.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
VPIM Locationssame1010000000compare ok 

5.29.2 Comparison Results

5.30 Unified Messaging Services

Unified messaging services are used to synchronize Cisco Unity Connection and Exchange mailboxes (single inbox) on Exchange servers.

The following Unified messaging services are configured to access Exchange server(s).

5.30.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Unified Messaging Servicessame1010000000Compare ok 

5.30.2 Comparison Results

No changes.

5.31 Accounts Status

The following table list the status of the unified messaging configuration of each Cisco Unity Connection user for Microsoft Exchange and for Unified Messaging and Cisco Unified MeetingPlace.

5.31.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Accounts Statussame1010000000compare ok 

5.31.2 Comparison Results

5.32 SpeechView Transcription Service

When the SpeechView feature is enabled, Cisco Unity Connection uses a third-party external transcription service to convert voice messages to text. When a voice message arrives, it is delivered to the mailbox of the recipient with a blank text attachment. When the completed transcription is returned by the transcription service, the text attachment is updated with the text of the transcription, or with an error message if there was a problem with the transcription. Only the first 500 characters of a message transcription are provided, so longer messages are truncated. However, users have access to the original recording in its entirety.

Connection sends the audio portion of a voice message to the transcription service, without details about the sender or recipients of the message. Communication between Connection and the external transcription service is secured by using S/MIME over SMTP.

To use SpeechView, users must belong to a class of service that enables transcriptions of voice messages. Members of the class of service can view the transcriptions of their messages by using an IMAP client that is configured to access their Connection messages. The original voice message remains attached to the transcribed text message.

The following are the settings for the Transcription Service for SpeechView:

5.32.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
SpeechView Transcription Servicesame0000040400Compare ok 

5.32.2 Comparison Results

No changes.

5.33 Error Codes

The following Nuance Transcription Error codes are configured:

5.33.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Error Codessame5050000000Compare ok 

5.33.2 Comparison Results

No changes.

5.34 Partitions

In Cisco Unity Connection, you create partitions as a way to group together objects to which callers and users can address messages or place calls while interacting with Connection. One or more partitions can be grouped together as members of a search space, and a partition can be a member of more than one search space. The following types of objects belong to a partition:

Extensions must be unique within a partition, although partitions can contain objects that do not have an associated extension (for example, some contacts and system distribution lists). The names of objects do not have to be unique within a partition. System contact phone numbers also do not need to be unique within a partition.

In general, objects can only be a member of a single partition, although a user can have a primary extension in one partition and an alternate extension in a different partition.

5.34.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Partitionssame2020000000Compare ok 

5.34.2 Comparison Results

No changes.

5.35 Search Spaces

Search spaces are used to define the search scope of objects (users, distribution lists, and so on) that a user or outside caller can reach while interacting with Cisco Unity Connection. For example, the search scope that is applied to a user identifies which users, distribution lists, or VPIM contacts the user can address messages to. The search scope that is applied to a user also identifies which users and system contacts the user can call by name dialing when using the voice-recognition conversation.

The following types of objects can use a search space for their search scope:

A search space is comprised of one or more ordered partitions. When Connection searches for an object on behalf of a caller, it searches the partitions in the order in which they are arranged in the search space. While extensions must be unique within a partition, they do not need to be unique within a search space, so you can use search spaces to handle dial plans that have overlapping extensions.

5.35.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Search Spacessame2020000000Compare ok 

5.35.2 Comparison Results

No changes.

5.36 General Configuration

This section contains the general global settings for Cisco Unity Connection:

5.36.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
General Configurationsame000001101100Compare ok 

5.36.2 Comparison Results

No changes.

5.37 Cluster

The Cisco Unity Connection cluster feature provides high availability voice messaging through two Connection servers that are configured in a cluster. Under normal conditions, the Connection servers are both active.

When one of the servers stops functioning (for example, when it is shut down for maintenance), the remaining server assumes responsibility for handling all incoming calls for the cluster. The remaining server also assumes responsibility for the database and message store, which are both replicated to the other server when the connection and its functionality are restored.

The following cluster member servers are configured:

5.37.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Clustersame1010000000Compare ok 

5.37.2 Comparison Results

No changes.

5.38 Services

The following services are present on this server:

5.38.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Servicessame760760000000Compare ok 

5.38.2 Comparison Results

No changes.

5.39 Authentication Rules

For Connection users who are not linked to user data in an LDAP directory, this authentication rule applies both to voice mail passwords and to web passwords.

For Connection users who are linked to user data in an LDAP directory, this authentication rule applies only to voice mail passwords. Web authentication and failed logon attempts will be handled by the LDAP directory, not by Connection.

The following Authentication Rules are configured:

5.39.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Authentication Rulessame4040000000Compare ok 

5.39.2 Comparison Results

No changes.

5.40 Roles

Cisco Unity Connection offers levels of privileges for administrator accounts, set according to a list of predefined roles. Roles specify which tasks administrators can do. Before you add administrator accounts, select the roles that are assigned to each account. You can change which roles are assigned to the accounts at any time.

Connection comes with the following predefined roles. You cannot make changes to the permissions that are associated with each predefined role.

While you can assign roles to users with voice mailboxes, we do not recommend it except when allowing access to the Cisco Unity Greetings Administrator. As a best practice, make sure that administrators have two accounts: one without a voice mailbox for administering Connection and another with a voice mailbox that they can use to access their personal mailbox.

5.40.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Rolessame100100000000Compare ok 

5.40.2 Comparison Results

No changes.

5.41 Restriction Tables

Restriction tables allow you to control which phone numbers users and administrators can use for:

For example, you can specify that users have calls transferred only to internal extensions or that faxes are delivered only to local phone numbers. Restriction tables are applied regardless of how a user or administrator accesses Cisco Unity Connection. They do not affect the phone numbers that users can dial when they are not logged on to Connection.

Each class of service specifies for its members a restriction table for call transfers, one for message notification, and one for fax deliveries. The restriction table can be the same for all three, or different for each. Because users without mailboxes (typically, administrators) are not assigned to a class of service, Connection applies the default restriction tables (default transfer, default outdial, or default fax) to actions taken by these types of users, including actions taken on behalf of other users.

The following Restriction Tables are configured:

5.41.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Restriction Tablessame6060000000Compare ok 

5.41.2 Comparison Results

No changes.

5.42 Licenses

This information shows the status of licensed features for the Connection server. For features that are licensed for a number of seats, the report displays the number of used and unused seats.

The following table defines the license parameters for Cisco Unity Connection features:

License Parameter Feature Description
LicAdvancedUserMax TTS and ASR (advanced) users Sets the maximum number of users who can use voice recognition.
LicIMAPSubscribersMax Users with IMAP access to voice messages Sets the maximum number of users who can use a third-party IMAP client to access voice messages.
LicMaxMsgRecLenIsLicensed Voice message recordings longer than 30 seconds allowed Depending on whether the parameter is present in any of the installed license files, determines the maximum length of recorded messages:
If the parameter is not present in any of the installed license files (the License Usage report shows a value of "No"), the maximum message length is 30 seconds regardless of the settings in Cisco Unity Connection Administration.
LicRealspeakSessionsMax Text to Speech sessions Sets the maximum number of simultaneous Text to Speech (TTS) sessions allowed on the Cisco Unity Connection server.
LicRegionIsUnrestricted U.S. English usage and personal call routing rules allowed Depending on whether the parameter is present in any of the installed license files, determines whether the English-United States language and personal call transfer rules are allowed:
If the parameter is not present in any of the installed license files (the License Usage report shows a value of "No"), the English-United States language and personal call transfer rules are not allowed.
If the parameter is present in any of the installed license files (the License Usage report shows a value of "Yes"), the English-United States language and personal call transfer rules are allowed.
LicServerBackend (not used) This parameter may be present in a license file but does not affect the Cisco Unity Connection server.
LicServerVoiceRec (not used) This parameter may be present in a license file but does not affect the Cisco Unity Connection server.
LicSubscribersMax Users with voice mailboxes Sets the maximum number of voice messaging users allowed in Cisco Unity Connection.
LicUCxnUpgrades License files from previous releases allowed Depending on whether the parameter is present in any of the installed license files, determines whether Cisco Unity Connection will use license files from an earlier version of Connection:

If the parameter is not present in any of the installed license files (the License Usage report shows a value of "No"), license files from an earlier version of Connection cannot be used.

If the parameter is present in any of the installed license files (the License Usage report shows a value of "Yes"), license files from an earlier version of Connection can be used.

LicUnityVoiceRecSessionsMax Voice recognition sessions Sets the maximum number of simultaneous voice recognition sessions (or ports) allowed on the Cisco Unity Connection server.
LicVMISubscribersMax Cisco Unity Inbox users Sets the maximum number of users who can be enabled to access the Cisco Unity Inbox. There is no restriction on the number of users who can access the Cisco Unity Inbox at one time.
LicVoicePortsMax Voice ports Sets the maximum number of Cisco Unity Connection voice messaging ports that can be installed on the Connection server.
LicVPIMIsLicensed VPIM Networking delivery locations allowed Depending on whether the parameter is present in any of the installed license files, determines whether VPIM Networking is allowed:
If the parameter is not present in any of the installed license files (the License Usage report shows a value of "No"), VPIM Networking is not allowed.
If the parameter is present in any of the installed license files (the License Usage report shows a value of "Yes"), VPIM Networking is allowed.

The following licenses are available:

5.42.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Licensessame150150000000Compare ok 

5.42.2 Comparison Results

No changes.

5.43 License Files

License files, which enable the features purchased by the customer, are required for configuring a new Cisco Unity Connection system and for adding or changing licensed features.

Multiple license files can be installed on a Cisco Unity Connection server. Each installed license file may enable one or more features. All of the installed license files combined enable the features that the customer wants.

Each license file (except for the demonstration license file) is registered to the MAC address of the network interface card (NIC) on the Cisco Unity Connection server.

5.43.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
License Filessame1010000000compare ok 

5.43.2 Comparison Results

5.44 Schedules

Schedules (and associated sets of holidays) are one of the variables that Cisco Unity Connection uses to manage calls: call handler transfer rules can be varied based on a schedule and schedules can be applied to routing rules to change call routing patterns for different time periods. Schedules also affect when some user and call handler greetings play.

Connection offers two predefined schedules: All Hours, and Weekdays, both of which can be modified. (By default, the Weekdays schedule is configured to observe standard hours from 8 a.m. through 5 p.m. Monday through Friday, and to observe the predefined Holidays schedule, which does not contain any dates or times.)

For each schedule that you create or modify, you can identify multiple ranges of hours and days that make up the standard and closed hours, and associate a holiday schedule that defines specific holiday dates and times:

5.44.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Schedulessame6060000000Compare ok 

5.44.2 Comparison Results

No changes.

5.45 Holiday Schedules

When a Holiday setting is in effect, Cisco Unity Connection plays holiday greetings (if enabled) and observes closed hours transfer rules. You can set up several years of holidays at a time. Because many holidays occur on different dates each year, confirm that the holiday schedule remains accurate annually.

5.45.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Holiday Schedulessame2020000000Compare ok 

5.45.2 Comparison Results

No changes.

5.46 Global Nicknames

The Global Nickname list is a comprehensive list of common nicknames that Cisco Unity Connection considers when a caller uses voice recognition to place a call or to address messages. For example, Connection considers "Bill," "Billy," and "Will" to be nicknames for the name "William."

If a user has an uncommon name or if others know the user by a different name (for example, a maiden name) consider adding these alternate names for the user. Alternate names improve the likelihood of Connection placing a call when callers ask for the user by name. You can add and remove nicknames from this list by using Cisco Unity Connection Administration.

The following nicknames are configured:

5.46.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Global Nicknamessame41204120000000Compare ok 

5.46.2 Comparison Results

No changes.

5.47 Subject Line Formats

Message subject lines are visible when users view and listen to messages in the Cisco Unity Inbox, an IMAP client, an RSS client, or any other visual client that displays the message subject. Subject lines are not presented to users when they listen to voice messages by phone. You can configure both the wording and the information that is included in the subject line of voice messages, including localizing the subject line according to the language of the recipient.

The subject lines of the following message types can be defined:

Subject lines for call handler messages use the definition of outside caller messages or user to user messages, depending on whether the call handler message is from an outside caller or a user.

5.47.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Subject Line Formatssame000001301300Compare ok 

5.47.2 Comparison Results

No changes.

5.48 Attachment Descriptions

When Cisco Unity Connection is integrated with a third-party message store, Connection uses Text to Speech (TTS) to describe message attachments for users who check their messages on the phone. For example, an attachment with the extension .jpg is described as 'an image.'

The following TTS description(s) for message attachments are configured:

5.48.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Attachment Descriptionssame100100000000Compare ok 

5.48.2 Comparison Results

No changes.

5.49 Enterprise Parameters

Enterprise parameters for Cisco Unity Connection provide default settings that apply to all services in Cisco Unified Serviceability.

The following list contains all Enterprise Parameters:

5.49.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Enterprise Parameterssame13701370000000Compare ok 

5.49.2 Comparison Results

No changes.

5.50 Service Parameters

Service parameters for Cisco Unity Connection allow you to configure different services in Cisco Unified Serviceability.

The following list contains all Service Parameters:

5.50.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Service Parameterssame590590000000Compare ok 

5.50.2 Comparison Results

No changes.

5.51 Fax Server

Cisco Unity Connection can integrate with the Cisco Fax Server so that users can do the following while on the phone or while using the Cisco Unity Inbox:

Inbound faxes are sent to the fax extension for the user. The Cisco Fax Server uses its email gateway to route the fax through SMTP to the user mailbox on the Connection server. The Text to Speech (TTS) feature cannot read faxes.

5.51.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Fax Serversame0000050500Compare ok 

5.51.2 Comparison Results

No changes.

5.52 LDAP Setup

If the check box 'Enable Synchronizing from LDAP Server' is enabled, Cisco Unity Connection gets basic information on Connection users from the LDAP directories that you specify on the LDAP Directory Configuration page. Data is synchronized only for the Connection users that you created by importing users from the LDAP directory. Connection does not automatically create new Connection users when new users are added to the LDAP directory.

If you want to use LDAP authentication, you must enable LDAP synchronization.

5.52.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
LDAP Setupsame0000030300Compare ok 

5.52.2 Comparison Results

No changes.

5.53 LDAP Directory Configuration

Cisco Unity Connection LDAP directory configurations specify which users in the LDAP directory are imported into Connection. For each LDAP directory configuration, a user search base is specified, which is the position in the LDAP directory tree where Connection begins its search for user accounts.

Connection imports all users in the tree or subtree (domain or OU) specified by the search base. A Connection server or cluster can only import LDAP data from subtrees with the same directory root, for example, from the same Active Directory forest.

5.53.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
LDAP Directory Configurationsame1010000000Compare ok 

5.53.2 Comparison Results

No changes.

5.54 LDAP Authentication

Connection web applications authenticate user names and passwords against the user name and web application password in the Connection database if LDAP Authentication is enabled.

When users sign in to Connection by phone, Connection always authenticates based on the voicemail password in the Connection database, never based on any value in the LDAP directory.

5.54.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
LDAP Authenticationsame0000030300Compare ok 

5.54.2 Comparison Results

No changes.

5.55 Phone Number Conversion

If you want to map phone numbers in the LDAP directory to extensions in Connection but the phone numbers do not match the extensions, you can add a regular expression and a replacement pattern that together convert the phone numbers into extensions.

5.55.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Phone Number Conversionsame0000020200Compare ok 

5.55.2 Comparison Results

No changes.

5.56 LDAP Custom Filter

LDAP Custom Filters allow for additional control over which LDAP users are imported into Cisco Unity Connection. subset of LDAP user accounts to become Connection users

When creating LDAP directory configurations in Connection, both a user search base and an LDAP filter must be specified. As applicable, create filters that integrate with the user search bases that you will specify for the maximum of five LDAP directory configurations that you can create.

Each filter must adhere to the LDAP filter syntax specified in RFC 4515, 'Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters.'

5.56.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
LDAP Custom Filtersame1010000000Compare ok 

5.56.2 Comparison Results

No changes.

5.57 SMTP Server

By using SMTP, Cisco Unity Connection can send text notification to notify users that they have received a new message or calendar event. Text notifications can be sent to any device that supports SMTP, for example, email addresses, cell phones, and text pagers.

To enable Connection to send text notifications by using SMTP, your Connection server must be configured to relay messages through a smart host. If Connection is configured to deliver text notifications but has not been configured to relay messages to a smart host, the notification attempt fails and the notification is put in the Connection SMTP Server badmail folder.

When a Connection user receives a new message, Connection can send a text notification to an email address. (When you set up this type of notification, you can configure Connection to include a link to the Cisco PCA in the body of the email message. On the Edit Notification Device page for the user, check the Include a Link to Cisco PCA in Message Text check box.)

5.57.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
SMTP Serversame000001101100Compare ok 

5.57.2 Comparison Results

No changes.

5.58 Smart Host

Digital Networking uses SMTP to transmit both directory information and messages between Cisco Unity Connection servers.

If any pair of servers in the Digital Network cannot transmit and receive SMTP messages directly (for example, because a firewall separates the servers), you must configure these servers to route these messages through an SMTP smart host.

5.58.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Smart Hostsame0000000000compare ok 

5.58.2 Comparison Results

5.59 SMPP Providers

Cisco Unity Connection can use the Short Message Peer-to-Peer (SMPP) protocol to send message notifications in the Short Message Service (SMS) format to cell phones and other SMS-compatible devices when users receive new messages. An advantage of using SMS is that the user device often receives message notifications much faster than when using SMTP.

5.59.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
SMPP Providerssame1010000000Compare ok 

5.59.2 Comparison Results

No changes.

5.60 Conversations

A Cisco Unity Connection conversation is a set of prerecorded prompts and menu options that callers hear as they interact with Connection by phone. It is organized into two main conversations-one for outside callers and one for Connection users. This chapter details the Connection conversation global settings.

5.60.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Conversationssame580580000000Compare ok 

5.60.2 Comparison Results

No changes.

5.61 Messaging

This section contains parameters for Cisco Unity Connection to relay messages for users to another SMTP server.

5.61.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Messagingsame130130000000Compare ok 

5.61.2 Comparison Results

No changes.

5.62 Intrasite Networking

Each Cisco Unity Connection server (or cluster) has a maximum number of users that it can serve. When the messaging needs of your organization require more than one Connection server or cluster, or you need a way to combine multiple Connection directories or to internetwork Connection with Cisco Unity, you can link Connection servers or clusters together to form sites, and link a Connection site with another Connection site or with a Cisco Unity site to form a Cisco Voicemail Organization.

The following Intrasite Networking settings are configured:

5.62.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Intrasite Networkingsame7070000000Compare ok 

5.62.2 Comparison Results

No changes.

5.63 Telephony

This section contains the advanced global settings for phone system integrations.

5.63.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Telephonysame160160000000Compare ok 

5.63.2 Comparison Results

No changes.

5.64 Reports

Cisco Unity Connection is automatically set to gather and store data from which you can generate reports.

This section contains the advanced global settings for the reports generation:

5.64.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Reportssame9090000000Compare ok 

5.64.2 Comparison Results

No changes.

5.65 Connection Administration

This section contains the administrator global settings for the Connection Cluster:

5.65.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Connection Administrationsame9090000000Compare ok 

5.65.2 Comparison Results

No changes.

5.66 TRAP

This section contains the advanced global settings for Telephone Record and Play (TRAP):

5.66.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
TRAPsame2020000000Compare ok 

5.66.2 Comparison Results

No changes.

5.67 Disk Capacity

This section contains the advanced global settings for the disk:

5.67.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Disk Capacitysame1010000000Compare ok 

5.67.2 Comparison Results

No changes.

5.68 PCA

The Cisco Personal Communications Assistant (PCA) is a website that provides users with access to the Cisco Unity web tools, which allow users to manage messages and personal preferences in Connection. The web tools available in the Cisco PCA include:

This section contains the advanced global settings for the Cisco Personal Communications Assistant (PCA):

5.68.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
PCAsame4040000000Compare ok 

5.68.2 Comparison Results

No changes.

5.69 RSS

As an alternative to checking messages by phone or using the Cisco Unity Inbox or an IMAP client, users can retrieve voice messages by using an RSS reader. In order to use the RSS Feed feature, users must be assigned to a class of service that is configured to allow them to use the Cisco Unity Inbox and RSS Feeds, and the Connection Inbox RSS Feed service must be activated and started.

RSS (most commonly translated as "Really Simple Syndication" but sometimes "Rich Site Summary") is a family of web feed formats used to publish frequently updated works (such as blog entries, news headlines, audio, and video) in a standardized format.

This section contains the advanced global settings for RSS:

5.69.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
RSSsame1010000000Compare ok 

5.69.2 Comparison Results

No changes.

5.70 Cluster Configuration

This section contains the advanced global settings for the Connection Cluster:

5.70.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Cluster Configurationsame2020000000Compare ok 

5.70.2 Comparison Results

No changes.

5.71 Fax

Cisco Unity Connection can integrate with the Cisco Fax Server so that users can do the following while on the phone or while using the Cisco Unity Inbox.

This section contains the advanced global settings for the fax:

5.71.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Faxsame3030000000Compare ok 

5.71.2 Comparison Results

No changes.

5.72 Unified Messaging Services

This section contains the advanced global settings for External Services:

5.72.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Unified Messaging Servicessame7070000000Compare ok 

5.72.2 Comparison Results

No changes.

5.73 API Settings

Applications that use the Cisco Unity Connection Messaging Interface (CUMI) can access secure message recordings (audio attachments) for playback.

These settings affect all client applications that use CUMI to access messages. This includes several Connection client applications, such as the Cisco Unity Connection Web Inbox and Cisco ViewMail for Microsoft Outlook.

The following CUMI API settings are configured:

5.73.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
API Settingssame3030000000Compare ok 

5.73.2 Comparison Results

No changes.

5.74 Phone System

The phone system pages in Cisco Unity Connection Administration identify the phone systems that Cisco Unity Connection integrates with. In Connection Administration, a phone system has one or more port groups, which in turn have voice messaging ports.

5.74.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Phone Systemsame1010000000Compare ok 

5.74.2 Comparison Results

No changes.

5.75 Port Group

Port groups hold most of the integration configuration settings and some or all of the voice messaging ports for Cisco Unity Connection.

While most phone system integrations need only one port group, multiple port groups may be needed in the following circumstances:

5.75.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Port Groupsame1010000000Compare ok 

5.75.2 Comparison Results

No changes.

5.76 Port

Voice messaging ports provide the connections for calls between Cisco Unity Connection and the phone system. You can add voice messaging ports after the phone system has been created. The number of voice messaging ports that you add cannot bring the total number of voice messaging ports for all port groups to more than the maximum number of voice messaging ports that are enabled by the Connection license files.

The voice messaging ports let Cisco Unity Connection receive calls (for example, to record a message) and let Connection make calls (for example to send message notifications or to set MWIs).

Each voice messaging port can belong to only one port group. Port groups, when there are several, each have their own voice messaging ports. The total voice messaging ports belonging to all port groups must not exceed the maximum number of voice messaging ports that are enabled by the Connection license files.

5.76.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Portsame2020000000Compare ok 

5.76.2 Comparison Results

No changes.

5.77 Speech Connect Port

Speech Connect uses voice-enabled directory handlers that allow both employees and outside callers to say the name of an employee and instantly get connected, without having to navigate an audio-text tree, and without knowing the extension of the employee. For easy access for employees, you can configure a Speech Connect speed dial on user phones.

5.77.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Speech Connect Portsame1010000000Compare ok 

5.77.2 Comparison Results

No changes.

5.78 Trunk

When multiple phone systems are integrated with Cisco Unity Connection, you may want to set up a phone system trunk so that calls on one phone system can be transferred to extensions on another phone system. Phone system trunks are accessed by dialing extra digits (for example, dialing 9) before dialing the extension.

5.78.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
Trunksame1010000000compare ok 

5.78.2 Comparison Results

5.79 SIP Certificate

The SIP certificate is used only by SIP trunk integrations with Cisco Unified CM 7.0 and later, and is required for authentication of the Cisco Unity Connection voice messaging ports.

The following SIP certificates are present:

5.79.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
SIP Certificatesame2020000000Compare ok 

5.79.2 Comparison Results

No changes.

5.80 SIP Security Profile

The SIP security profile is used only by SIP trunk integrations with Cisco Unified CM 7.0 and later, and is required for authentication of the Cisco Unity Connection voice messaging ports.

The following SIP security profiles are present:

5.80.1 Comparison Statistics

Comparison Statistics
ObjectRecords
U=Updated
S=Same
A=Added
D=Deleted
Fields
U=Updated
S=Same
A=Added
D=Deleted
StatusChange Details
NameBase ExistsChanged ExistStatusTotalUSADTotalUSADComparison InfoChange Details
SIP Security Profilesame2020000000Compare ok 

5.80.2 Comparison Results

No changes.
Table of Contents [Hide TOC]