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 Server 5.1.1 Comparison Statistics 5.1.2 Comparison Results 5.2 Services 5.2.1 Comparison Statistics 5.2.2 Comparison Results 5.3 Cisco Unified CM 5.3.1 Comparison Statistics 5.3.2 Comparison Results 5.4 Cisco Unified CM Group 5.4.1 Comparison Statistics 5.4.2 Comparison Results 5.5 Presence Redundancy Groups 5.5.1 Comparison Statistics 5.5.2 Comparison Results 5.6 Phone NTP Reference 5.6.1 Comparison Statistics 5.6.2 Comparison Results 5.7 Date/Time Group 5.7.1 Comparison Statistics 5.7.2 Comparison Results 5.8 BLF Presence Group 5.8.1 Comparison Statistics 5.8.2 Comparison Results 5.9 Audio Codec Preference Lists 5.9.1 Comparison Statistics 5.9.2 Comparison Results 5.10 Region 5.10.1 Comparison Statistics 5.10.2 Comparison Results 5.11 Device Pool 5.11.1 Comparison Statistics 5.11.2 Comparison Results 5.12 Device Mobility Group 5.12.1 Comparison Statistics 5.12.2 Comparison Results 5.13 Device Mobility Info 5.13.1 Comparison Statistics 5.13.2 Comparison Results 5.14 DHCP Server 5.14.1 Comparison Statistics 5.14.2 Comparison Results 5.15 DHCP Subnet 5.15.1 Comparison Statistics 5.15.2 Comparison Results 5.16 LDAP System 5.16.1 Comparison Statistics 5.16.2 Comparison Results 5.17 LDAP Directory 5.17.1 Comparison Statistics 5.17.2 Comparison Results 5.18 LDAP Authentication 5.18.1 Comparison Statistics 5.18.2 Comparison Results 5.19 LDAP Custom Filter 5.19.1 Comparison Statistics 5.19.2 Comparison Results 5.20 SAML Single Sign-On 5.20.1 Comparison Statistics 5.20.2 Comparison Results 5.21 Cross-Origin Resource Sharing (CORS) 5.21.1 Comparison Statistics 5.21.2 Comparison Results 5.22 Location 5.22.1 Comparison Statistics 5.22.2 Comparison Results 5.23 Location Bandwidth Manager Group 5.23.1 Comparison Statistics 5.23.2 Comparison Results 5.24 Location Bandwidth Manager Intercluster Replication Group 5.24.1 Comparison Statistics 5.24.2 Comparison Results 5.25 Physical Location 5.25.1 Comparison Statistics 5.25.2 Comparison Results 5.26 SRST 5.26.1 Comparison Statistics 5.26.2 Comparison Results 5.27 MLPP Domain 5.27.1 Comparison Statistics 5.27.2 Comparison Results 5.28 Resource Priority Namespace Network Domain 5.28.1 Comparison Statistics 5.28.2 Comparison Results 5.29 Resource Priority Namespace List 5.29.1 Comparison Statistics 5.29.2 Comparison Results 5.30 Enterprise Parameters 5.30.1 Comparison Statistics 5.30.2 Comparison Results 5.31 Enterprise Phone Configuration 5.31.1 Comparison Statistics 5.31.2 Comparison Results 5.32 Service Parameters 5.32.1 Comparison Statistics 5.32.2 Comparison Results 5.33 Certificate 5.33.1 Comparison Statistics 5.33.2 Comparison Results 5.34 Phone Security Profile 5.34.1 Comparison Statistics 5.34.2 Comparison Results 5.35 SIP Trunk Security Profile 5.35.1 Comparison Statistics 5.35.2 Comparison Results 5.36 Application Server 5.36.1 Comparison Statistics 5.36.2 Comparison Results 5.37 Geolocation 5.37.1 Comparison Statistics 5.37.2 Comparison Results 5.38 Geolocation Filter 5.38.1 Comparison Statistics 5.38.2 Comparison Results 5.39 E911 Messages 5.39.1 Comparison Statistics 5.39.2 Comparison Results 5.40 AAR Group 5.40.1 Comparison Statistics 5.40.2 Comparison Results 5.41 Application Dial Rules 5.41.1 Comparison Statistics 5.41.2 Comparison Results 5.42 Directory Lookup Dial Rules 5.42.1 Comparison Statistics 5.42.2 Comparison Results 5.43 SIP Dial Rules 5.43.1 Comparison Statistics 5.43.2 Comparison Results 5.44 Route Filter 5.44.1 Comparison Statistics 5.44.2 Comparison Results 5.45 Route List and Route Group 5.45.1 Comparison Statistics 5.45.2 Comparison Results 5.46 Route Group 5.46.1 Comparison Statistics 5.46.2 Comparison Results 5.47 Local Route Group Names 5.47.1 Comparison Statistics 5.47.2 Comparison Results 5.48 Route List 5.48.1 Comparison Statistics 5.48.2 Comparison Results 5.49 Route Pattern (Condensed) 5.49.1 Comparison Statistics 5.49.2 Comparison Results 5.50 Hunt Pilot - List and Group 5.50.1 Comparison Statistics 5.50.2 Comparison Results 5.51 Line Group 5.51.1 Comparison Statistics 5.51.2 Comparison Results 5.52 Hunt List 5.52.1 Comparison Statistics 5.52.2 Comparison Results 5.53 Hunt Pilot 5.53.1 Comparison Statistics 5.53.2 Comparison Results 5.54 SIP Route Pattern (Condensed) 5.54.1 Comparison Statistics 5.54.2 Comparison Results 5.55 Access List 5.55.1 Comparison Statistics 5.55.2 Comparison Results 5.56 Time Schedule and Period 5.56.1 Comparison Statistics 5.56.2 Comparison Results 5.57 Partition 5.57.1 Comparison Statistics 5.57.2 Comparison Results 5.58 Calling Search Space 5.58.1 Comparison Statistics 5.58.2 Comparison Results 5.59 Intercom Route Partition 5.59.1 Comparison Statistics 5.59.2 Comparison Results 5.60 Intercom Calling Search Space 5.60.1 Comparison Statistics 5.60.2 Comparison Results 5.61 Intercom Directory Number 5.61.1 Comparison Statistics 5.61.2 Comparison Results 5.62 Intercom Directory Number - Unassigned 5.62.1 Comparison Statistics 5.62.2 Comparison Results 5.63 Intercom Translation Pattern 5.63.1 Comparison Statistics 5.63.2 Comparison Results 5.64 Client Matter Codes 5.64.1 Comparison Statistics 5.64.2 Comparison Results 5.65 Forced Authorization Code 5.65.1 Comparison Statistics 5.65.2 Comparison Results 5.66 Translation Pattern (Condensed) 5.66.1 Comparison Statistics 5.66.2 Comparison Results 5.67 Call Park 5.67.1 Comparison Statistics 5.67.2 Comparison Results 5.68 Directed Call Park 5.68.1 Comparison Statistics 5.68.2 Comparison Results 5.69 Call Pickup Group 5.69.1 Comparison Statistics 5.69.2 Comparison Results 5.70 Call Pickup Group - Group Members 5.70.1 Comparison Statistics 5.70.2 Comparison Results 5.71 Directory Number (Condensed) 5.71.1 Comparison Statistics 5.71.2 Comparison Results 5.72 Directory Numbers - Unallocated (Condensed) 5.72.1 Comparison Statistics 5.72.2 Comparison Results 5.73 Meet-Me Number/Pattern 5.73.1 Comparison Statistics 5.73.2 Comparison Results 5.74 Route Plan Report 5.74.1 Comparison Statistics 5.74.2 Comparison Results 5.75 Calling Party Transformation Pattern 5.75.1 Comparison Statistics 5.75.2 Comparison Results 5.76 Called Party Transformation Pattern 5.76.1 Comparison Statistics 5.76.2 Comparison Results 5.77 Transformation Profile 5.77.1 Comparison Statistics 5.77.2 Comparison Results 5.78 Mobility Enterprise Feature Access Number 5.78.1 Comparison Statistics 5.78.2 Comparison Results 5.79 Handoff Configuration 5.79.1 Comparison Statistics 5.79.2 Comparison Results 5.80 Mobility Profile 5.80.1 Comparison Statistics 5.80.2 Comparison Results 5.81 Logical Partitioning Policy 5.81.1 Comparison Statistics 5.81.2 Comparison Results 5.82 External Call Control Profile 5.82.1 Comparison Statistics 5.82.2 Comparison Results 5.83 HTTP Profile 5.83.1 Comparison Statistics 5.83.2 Comparison Results 5.84 CCD Hosted DN Group 5.84.1 Comparison Statistics 5.84.2 Comparison Results 5.85 CCD Hosted DN Pattern 5.85.1 Comparison Statistics 5.85.2 Comparison Results 5.86 CCD Advertising Service 5.86.1 Comparison Statistics 5.86.2 Comparison Results 5.87 CCD Partition 5.87.1 Comparison Statistics 5.87.2 Comparison Results 5.88 CCD Requesting Service 5.88.1 Comparison Statistics 5.88.2 Comparison Results 5.89 Blocked Learned Pattern 5.89.1 Comparison Statistics 5.89.2 Comparison Results 5.90 Advertised Patterns 5.90.1 Comparison Statistics 5.90.2 Comparison Results 5.91 Blocked Learned Numbers and Patterns 5.91.1 Comparison Statistics 5.91.2 Comparison Results 5.92 Partitions for Learned Numbers and Patterns 5.92.1 Comparison Statistics 5.92.2 Comparison Results 5.93 Learned Numbers 5.93.1 Comparison Statistics 5.93.2 Comparison Results 5.94 Learned Patterns 5.94.1 Comparison Statistics 5.94.2 Comparison Results 5.95 Learned Directory URIs 5.95.1 Comparison Statistics 5.95.2 Comparison Results 5.96 Imported Global Dial Plan Catalogs 5.96.1 Comparison Statistics 5.96.2 Comparison Results 5.97 Imported Directory URIs 5.97.1 Comparison Statistics 5.97.2 Comparison Results 5.98 Imported Patterns 5.98.1 Comparison Statistics 5.98.2 Comparison Results 5.99 Annunciator 5.99.1 Comparison Statistics 5.99.2 Comparison Results 5.100 Conference Bridge 5.100.1 Comparison Statistics 5.100.2 Comparison Results 5.101 Media Termination Point 5.101.1 Comparison Statistics 5.101.2 Comparison Results 5.102 MoH Sources 5.102.1 Comparison Statistics 5.102.2 Comparison Results 5.103 MoH Servers 5.103.1 Comparison Statistics 5.103.2 Comparison Results 5.104 VoH Servers 5.104.1 Comparison Statistics 5.104.2 Comparison Results 5.105 Transcoder 5.105.1 Comparison Statistics 5.105.2 Comparison Results 5.106 Media Resource Groups and Lists 5.106.1 Comparison Statistics 5.106.2 Comparison Results 5.107 Mobile Voice Access 5.107.1 Comparison Statistics 5.107.2 Comparison Results 5.108 Announcements 5.108.1 Comparison Statistics 5.108.2 Comparison Results 5.109 Cisco Voice Mail Port 5.109.1 Comparison Statistics 5.109.2 Comparison Results 5.110 Message Waiting 5.110.1 Comparison Statistics 5.110.2 Comparison Results 5.111 MWI On 5.111.1 Comparison Statistics 5.111.2 Comparison Results 5.112 Voice Mail Profile and Pilot 5.112.1 Comparison Statistics 5.112.2 Comparison Results 5.113 SAF Security Profile 5.113.1 Comparison Statistics 5.113.2 Comparison Results 5.114 SAF Forwarder 5.114.1 Comparison Statistics 5.114.2 Comparison Results 5.115 EMCC Feature Configuration 5.115.1 Comparison Statistics 5.115.2 Comparison Results 5.116 EMCC Intercluster Service Profile 5.116.1 Comparison Statistics 5.116.2 Comparison Results 5.117 Cluster View 5.117.1 Comparison Statistics 5.117.2 Comparison Results 5.118 Server Connection 5.118.1 Comparison Statistics 5.118.2 Comparison Results 5.119 Enrolled Group 5.119.1 Comparison Statistics 5.119.2 Comparison Results 5.120 Enrolled Pattern 5.120.1 Comparison Statistics 5.120.2 Comparison Results 5.121 Exclusion Group 5.121.1 Comparison Statistics 5.121.2 Comparison Results 5.122 Exclusion Number 5.122.1 Comparison Statistics 5.122.2 Comparison Results 5.123 Trust Group 5.123.1 Comparison Statistics 5.123.2 Comparison Results 5.124 Trust Element 5.124.1 Comparison Statistics 5.124.2 Comparison Results 5.125 Service 5.125.1 Comparison Statistics 5.125.2 Comparison Results 5.126 E.164 Transformation 5.126.1 Comparison Statistics 5.126.2 Comparison Results 5.127 Learned Route 5.127.1 Comparison Statistics 5.127.2 Comparison Results 5.128 Firewall 5.128.1 Comparison Statistics 5.128.2 Comparison Results 5.129 Intercompany Media Services Feature Configuration 5.129.1 Comparison Statistics 5.129.2 Comparison Results 5.130 Fallback Profile 5.130.1 Comparison Statistics 5.130.2 Comparison Results 5.131 Fallback Feature Configuration 5.131.1 Comparison Statistics 5.131.2 Comparison Results 5.132 VPN Profile 5.132.1 Comparison Statistics 5.132.2 Comparison Results 5.133 VPN Group 5.133.1 Comparison Statistics 5.133.2 Comparison Results 5.134 VPN Gateway 5.134.1 Comparison Statistics 5.134.2 Comparison Results 5.135 VPN Feature Configuration 5.135.1 Comparison Statistics 5.135.2 Comparison Results 5.136 Called Party Tracing List 5.136.1 Comparison Statistics 5.136.2 Comparison Results 5.137 ILS Configuration 5.137.1 Comparison Statistics 5.137.2 Comparison Results 5.138 Call Control Agent Profile 5.138.1 Comparison Statistics 5.138.2 Comparison Results 5.139 Directory Number Alias Lookup And Sync 5.139.1 Comparison Statistics 5.139.2 Comparison Results 5.140 CTI Route Point 5.140.1 Comparison Statistics 5.140.2 Comparison Results 5.141 Gatekeeper 5.141.1 Comparison Statistics 5.141.2 Comparison Results 5.142 Gateway Overview 5.142.1 Comparison Statistics 5.142.2 Comparison Results 5.143 MGCP Gateway 5.143.1 Comparison Statistics 5.143.2 Comparison Results 5.144 MGCP Gateway Endpoints 5.144.1 Comparison Statistics 5.144.2 Comparison Results 5.145 H.323 Gateway 5.145.1 Comparison Statistics 5.145.2 Comparison Results 5.146 Analog Gateway 5.146.1 Comparison Statistics 5.146.2 Comparison Results 5.147 Phone Filter 5.147.1 Comparison Statistics 5.147.2 Comparison Results 5.148 CTI Port (5) 5.148.1 Comparison Statistics 5.148.2 Comparison Results 5.149 Cisco 7821 (1) 5.149.1 Comparison Statistics 5.149.2 Comparison Results 5.150 Cisco 7861 (1) 5.150.1 Comparison Statistics 5.150.2 Comparison Results 5.151 Cisco 7945 (1) 5.151.1 Comparison Statistics 5.151.2 Comparison Results 5.152 Cisco 7975 (1) 5.152.1 Comparison Statistics 5.152.2 Comparison Results 5.153 Cisco 8841 (2) 5.153.1 Comparison Statistics 5.153.2 Comparison Results 5.154 Cisco 8851 (1) 5.154.1 Comparison Statistics 5.154.2 Comparison Results 5.155 Cisco 9951 (1) 5.155.1 Comparison Statistics 5.155.2 Comparison Results 5.156 Cisco DX650 (1) 5.156.1 Comparison Statistics 5.156.2 Comparison Results 5.157 Cisco Dual Mode for iPhone (1) 5.157.1 Comparison Statistics 5.157.2 Comparison Results 5.158 Cisco IP Communicator (1) 5.158.1 Comparison Statistics 5.158.2 Comparison Results 5.159 Cisco TelePresence 1000 (1) 5.159.1 Comparison Statistics 5.159.2 Comparison Results 5.160 Universal Device Template (2) 5.160.1 Comparison Statistics 5.160.2 Comparison Results 5.161 Subscribed Services 5.161.1 Comparison Statistics 5.161.2 Comparison Results 5.162 Speed Dials 5.162.1 Comparison Statistics 5.162.2 Comparison Results 5.163 Busy Lamp Field Speed Dials 5.163.1 Comparison Statistics 5.163.2 Comparison Results 5.164 Busy Lamp Field Directed Call Parks 5.164.1 Comparison Statistics 5.164.2 Comparison Results 5.165 Trunk - Overview 5.165.1 Comparison Statistics 5.165.2 Comparison Results 5.166 Trunk - Detailed 5.166.1 Comparison Statistics 5.166.2 Comparison Results 5.167 Remote Destination 5.167.1 Comparison Statistics 5.167.2 Comparison Results 5.168 Device Defaults 5.168.1 Comparison Statistics 5.168.2 Comparison Results 5.169 Firmware Load Information 5.169.1 Comparison Statistics 5.169.2 Comparison Results 5.170 Default Device Profile 5.170.1 Comparison Statistics 5.170.2 Comparison Results 5.171 Device Profile Filter 5.171.1 Comparison Statistics 5.171.2 Comparison Results 5.172 Cisco 6921 (1) 5.172.1 Comparison Statistics 5.172.2 Comparison Results 5.173 Cisco 7945 (4) 5.173.1 Comparison Statistics 5.173.2 Comparison Results 5.174 Cisco 7975 (4) 5.174.1 Comparison Statistics 5.174.2 Comparison Results 5.175 Cisco 8851 (2) 5.175.1 Comparison Statistics 5.175.2 Comparison Results 5.176 Subscribed Services 5.176.1 Comparison Statistics 5.176.2 Comparison Results 5.177 Speed Dials 5.177.1 Comparison Statistics 5.177.2 Comparison Results 5.178 Busy Lamp Field Speed Dials 5.178.1 Comparison Statistics 5.178.2 Comparison Results 5.179 Busy Lamp Field Directed Call Parks 5.179.1 Comparison Statistics 5.179.2 Comparison Results 5.180 Phone Button Template 5.180.1 Comparison Statistics 5.180.2 Comparison Results 5.181 Softkey Template 5.181.1 Comparison Statistics 5.181.2 Comparison Results 5.182 Phone Services 5.182.1 Comparison Statistics 5.182.2 Comparison Results 5.183 SIP Profile 5.183.1 Comparison Statistics 5.183.2 Comparison Results 5.184 Common Device Configuration 5.184.1 Comparison Statistics 5.184.2 Comparison Results 5.185 Common Phone Profile 5.185.1 Comparison Statistics 5.185.2 Comparison Results 5.186 Remote Destination Profile 5.186.1 Comparison Statistics 5.186.2 Comparison Results 5.187 Feature Control Policy 5.187.1 Comparison Statistics 5.187.2 Comparison Results 5.188 Recording Profile 5.188.1 Comparison Statistics 5.188.2 Comparison Results 5.189 SIP Normalization Script 5.189.1 Comparison Statistics 5.189.2 Comparison Results 5.190 SDP Transparency Profile 5.190.1 Comparison Statistics 5.190.2 Comparison Results 5.191 Network Access Profile 5.191.1 Comparison Statistics 5.191.2 Comparison Results 5.192 Wireless LAN Profile 5.192.1 Comparison Statistics 5.192.2 Comparison Results 5.193 Wireless LAN Profile Group 5.193.1 Comparison Statistics 5.193.2 Comparison Results 5.194 Wifi Hotspot Profile 5.194.1 Comparison Statistics 5.194.2 Comparison Results 5.195 Application User 5.195.1 Comparison Statistics 5.195.2 Comparison Results 5.196 End User (Condensed) 5.196.1 Comparison Statistics 5.196.2 Comparison Results 5.197 SIP Realm 5.197.1 Comparison Statistics 5.197.2 Comparison Results 5.198 Credential Policy Default 5.198.1 Comparison Statistics 5.198.2 Comparison Results 5.199 Credential Policy 5.199.1 Comparison Statistics 5.199.2 Comparison Results 5.200 Role 5.200.1 Comparison Statistics 5.200.2 Comparison Results 5.201 Access Control Group 5.201.1 Comparison Statistics 5.201.2 Comparison Results 5.202 UC Service 5.202.1 Comparison Statistics 5.202.2 Comparison Results 5.203 Service Profile 5.203.1 Comparison Statistics 5.203.2 Comparison Results 5.204 User Profile 5.204.1 Comparison Statistics 5.204.2 Comparison Results 5.205 Self-Provisioning 5.205.1 Comparison Statistics 5.205.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 3:13:58 PM
Report generated forCluster A - CUCM v10
DescriptionCustomer
Comparing the following reports
Base ReportE:\reports\Report_For_Cluster A - CUCM v10\CU
CM\15Sep2015_1310\html\CUCM_Report_Cluster A - CUCM v10.htm
Base Report Time (UTC)15/09/2015 3:10:05 AM
Changed ReportE:\reports\Report_For_Cluster A - CUCM v10\CU
CM\15Sep2015_1510\html\CUCM_Report_Cluster A - CUCM v10.htm
Changed Report Time (UTC)15/09/2015 5:10:07 AM
Output ReportE:\reports\Report_For_Cluster A - CUCM v10\CU
CM\15Sep2015_1510\html\diff_20150915151228\CUCM_Report_Cluster A - CUCM v10.diff.htm
Cisco Audit Logs
Use Cisco Audit LogsYes
Path to Cisco Audit Log filesC:\auditlogs\CUCM10
Number of relevant entries in path7
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
Serversame5050000000Compare ok 
Servicessame780780000000Compare ok 
Cisco Unified CMsame3030000000Compare ok 
Cisco Unified CM Groupsame5050000000Compare ok 
Presence Redundancy Groupssame1010000000Compare ok 
Phone NTP Referencesame1010000000Compare ok 
Date/Time Groupsame2020000000Compare ok 
BLF Presence Groupsame1010000000Compare ok 
Audio Codec Preference Listssame2020000000Compare ok 
Regionsame4040000000Compare ok 
Device Poolnotsame1311200507150600Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
015/09/2015 2:08:59 PM15/09/2015 4:08:59 AMAuditLogChange 0: Updated record 'DP_London' Device PoolAudit Log id 2 (UTC 15/09/2015 4:08:59 AM User: admin )
115/09/2015 2:08:59 PM15/09/2015 4:08:59 AMAuditLog-ParentChange 1: Updated field 'Roaming Sensitive Settings::Date/Time Group' from CMLocal to DTG-AddChange 0Device Pool 
Device Mobility Groupsame2020000000Compare ok 
Device Mobility Infosame1010000000Compare ok 
DHCP Serversame1010000000Compare ok 
DHCP Subnetsame1010000000Compare ok 
LDAP Systemsame3030000000Compare ok 
LDAP Directorysame1010000000Compare ok 
LDAP Authenticationsame0000030300Compare ok 
LDAP Custom Filtersame1010000000Compare ok 
SAML Single Sign-Onsame5050000000Compare ok 
Cross-Origin Resource Sharing (CORS)same1010000000Compare ok 
Locationsame5050000000Compare ok 
Location Bandwidth Manager Groupsame1010000000Compare ok 
Location Bandwidth Manager Intercluster Replication Groupsame1010000000Compare ok 
Physical Locationsame2020000000Compare ok 
SRSTsame1010000000Compare ok 
MLPP Domainsame1010000000Compare ok 
Resource Priority Namespace Network Domainsame2020000000Compare ok 
Resource Priority Namespace Listsame2020000000Compare ok 
Enterprise Parameterssame13701370000000Compare ok 
Enterprise Phone Configurationsame11201120000000Compare ok 
Service Parameterssame80708070000000Compare ok 
Certificatesame270270000000Compare ok 
Phone Security Profilesame15501550000000Compare ok 
SIP Trunk Security Profilesame2020000000Compare ok 
Application Serversame2020000000Compare ok 
Geolocationsame1010000000Compare ok 
Geolocation Filtersame1010000000Compare ok 
E911 Messagessame3030000000Compare ok 
AAR Groupsame4040000000Compare ok 
Application Dial Rulessame1010000000Compare ok 
Directory Lookup Dial Rulessame1010000000Compare ok 
SIP Dial Rulessame2020000000Compare ok 
Route Filtersame1010000000Compare ok 
Route List and Route Groupsame1010000000Compare ok 
Route Groupsame3030000000Compare ok 
Local Route Group Namessame2020000000Compare ok 
Route Listsame1010000000Compare ok 
Route Pattern (Condensed)same2020000000Compare ok 
Hunt Pilot - List and Groupsame1010000000Compare ok 
Line Groupsame2020000000Compare ok 
Hunt Listsame1010000000Compare ok 
Hunt Pilotsame1010000000Compare ok 
SIP Route Pattern (Condensed)same2020000000Compare ok 
Access Listsame1010000000Compare ok 
Time Schedule and Periodsame2020000000Compare ok 
Partitionsame280280000000Compare ok 
Calling Search Spacenotsame24122107216830Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
215/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 2: Updated record 'CSS_3' Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
315/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 3: Updated record 'CSS_3'Change 2Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
415/09/2015 2:09:12 PM15/09/2015 4:09:12 AMAuditLogChange 4: Added record with key 'CSS_5' Calling Search SpaceAudit Log id 3 (UTC 15/09/2015 4:09:12 AM User: admin )
Intercom Route Partitionsame4040000000Compare ok 
Intercom Calling Search Spacesame4040000000Compare ok 
Intercom Directory Numbersame160160000000Compare ok 
Intercom Directory Number - Unassignedsame150150000000Compare ok 
Intercom Translation Patternsame1010000000Compare ok 
Client Matter Codessame3030000000Compare ok 
Forced Authorization Codesame2020000000Compare ok 
Translation Pattern (Condensed)same2020000000Compare ok 
Call Parksame3030000000Compare ok 
Directed Call Parksame1010000000Compare ok 
Call Pickup Groupsame4040000000Compare ok 
Call Pickup Group - Group Memberssame4040000000Compare ok 
Directory Number (Condensed)same11301130000000Compare ok 
Directory Numbers - Unallocated (Condensed)same830830000000Compare ok 
Meet-Me Number/Patternsame3030000000Compare ok 
Route Plan Reportnotsame152115100912191100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
59/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 5: Updated record '5012' Route Plan Report 
69/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 6: Updated field 'Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 5Route Plan Report 
Calling Party Transformation Patternsame2020000000Compare ok 
Called Party Transformation Patternsame2020000000Compare ok 
Transformation Profilesame2020000000Compare ok 
Mobility Enterprise Feature Access Numbersame2020000000Compare ok 
Handoff Configurationsame1010000000Compare ok 
Mobility Profilesame3030000000Compare ok 
Logical Partitioning Policysame1010000000Compare ok 
External Call Control Profilesame1010000000Compare ok 
HTTP Profilesame6060000000Compare ok 
CCD Hosted DN Groupsame2020000000Compare ok 
CCD Hosted DN Patternsame1010000000Compare ok 
CCD Advertising Servicesame1010000000Compare ok 
CCD Partitionsame1010000000Compare ok 
CCD Requesting Servicesame1010000000Compare ok 
Blocked Learned Patternsame2020000000Compare ok 
Advertised Patternssame2020000000Compare ok 
Blocked Learned Numbers and Patternssame2020000000Compare ok 
Partitions for Learned Numbers and Patternssame4040000000Compare ok 
Learned Numberssame1010000000compare ok 
Learned Patternssame1010000000compare ok 
Learned Directory URIssame1010000000compare ok 
Imported Global Dial Plan Catalogssame1010000000compare ok 
Imported Directory URIssame1010000000compare ok 
Imported Patternssame1010000000compare ok 
Annunciatorsame3030000000Compare ok 
Conference Bridgesame3030000000Compare ok 
Media Termination Pointsame3030000000Compare ok 
MoH Sourcessame3030000000Compare ok 
MoH Serverssame3030000000Compare ok 
VoH Serverssame2020000000Compare ok 
Transcodersame3030000000Compare ok 
Media Resource Groups and Listssame1010000000Compare ok 
Mobile Voice Accesssame1010000000Compare ok 
Announcementssame130130000000Compare ok 
Cisco Voice Mail Portsame2020000000Compare ok 
Message Waitingsame2020000000Compare ok 
MWI Onsame1010000000compare ok 
Voice Mail Profile and Pilotsame7070000000Compare ok 
SAF Security Profilesame2020000000Compare ok 
SAF Forwardersame2020000000Compare ok 
EMCC Feature Configurationsame130130000000Compare ok 
EMCC Intercluster Service Profilesame3030000000Compare ok 
Cluster Viewsame2020000000Compare ok 
Server Connectionsame1010000000Compare ok 
Enrolled Groupsame1010000000Compare ok 
Enrolled Patternsame2020000000Compare ok 
Exclusion Groupsame2020000000Compare ok 
Exclusion Numbersame1010000000Compare ok 
Trust Groupsame2020000000Compare ok 
Trust Elementsame2020000000Compare ok 
Servicesame2020000000Compare ok 
E.164 Transformationsame2020000000Compare ok 
Learned Routesame1010000000compare ok 
Firewallsame2020000000Compare ok 
Intercompany Media Services Feature Configurationsame110110000000Compare ok 
Fallback Profilesame3030000000Compare ok 
Fallback Feature Configurationsame100100000000Compare ok 
VPN Profilesame1010000000compare ok 
VPN Groupsame1010000000compare ok 
VPN Gatewaysame1010000000compare ok 
VPN Feature Configurationsame6060000000Compare ok 
Called Party Tracing Listsame3030000000Compare ok 
ILS Configurationsame0000050500Compare ok 
Call Control Agent Profilesame2020000000Compare ok 
Directory Number Alias Lookup And Syncsame1010000000compare ok 
CTI Route Pointsame8080000000Compare ok 
Gatekeepersame2020000000Compare ok 
Gateway Overviewsame110110000000Compare ok 
MGCP Gatewaysame7070000000Compare ok 
MGCP Gateway Endpointssame4040000000Compare ok 
H.323 Gatewaysame1010000000compare ok 
Analog Gatewaysame110110000000Compare ok 
Phone Filtersame0000010100Compare ok 
CTI Port (5)same5050000000Compare ok 
Cisco 7821 (1)same1010000000Compare ok 
Cisco 7861 (1)same1010000000Compare ok 
Cisco 7945 (1)notsame110001211100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
715/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 7: Updated record 'SEP0021A02E05E0' Cisco 7945 (1) 
815/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 8: Updated field '::Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 7Cisco 7945 (1) 
Cisco 7975 (1)same1010000000Compare ok 
Cisco 8841 (2)same2020000000Compare ok 
Cisco 8851 (1)same1010000000Compare ok 
Cisco 9951 (1)same1010000000Compare ok 
Cisco DX650 (1)same1010000000Compare ok 
Cisco Dual Mode for iPhone (1)same1010000000Compare ok 
Cisco IP Communicator (1)same1010000000Compare ok 
Cisco TelePresence 1000 (1)same1010000000Compare ok 
Universal Device Template (2)same2020000000Compare ok 
Subscribed Servicessame7070000000Compare ok 
Speed Dialssame2020000000Compare ok 
Busy Lamp Field Speed Dialssame3030000000Compare ok 
Busy Lamp Field Directed Call Parkssame1010000000compare ok 
Trunk - Overviewsame100100000000Compare ok 
Trunk - Detailedsame100100000000Compare ok 
Remote Destinationsame3030000000Compare ok 
Device Defaultssame17701770000000Compare ok 
Firmware Load Informationsame15001500000000Compare ok 
Default Device Profilesame220220000000Compare ok 
Device Profile Filtersame0000010100Compare ok 
Cisco 6921 (1)same1010000000Compare ok 
Cisco 7945 (4)same4040000000Compare ok 
Cisco 7975 (4)same4040000000Compare ok 
Cisco 8851 (2)same2020000000Compare ok 
Cisco 8961 (1)not_comparable----------Not comparable (Base object exists / changed object missing) 
Subscribed Servicessame4040000000Compare ok 
Speed Dialssame1010000000compare ok 
Busy Lamp Field Speed Dialssame1010000000compare ok 
Busy Lamp Field Directed Call Parkssame1010000000compare ok 
Phone Button Templatesame16701670000000Compare ok 
Softkey Templatesame8080000000Compare ok 
Phone Servicessame160160000000Compare ok 
SIP Profilesame5050000000Compare ok 
Common Device Configurationsame2020000000Compare ok 
Common Phone Profilesame7070000000Compare ok 
Remote Destination Profilesame2020000000Compare ok 
Feature Control Policysame1010000000Compare ok 
Recording Profilesame1010000000Compare ok 
SIP Normalization Scriptsame8080000000Compare ok 
SDP Transparency Profilesame2020000000Compare ok 
Network Access Profilesame4040000000Compare ok 
Wireless LAN Profilesame5050000000Compare ok 
Wireless LAN Profile Groupsame2020000000Compare ok 
Wifi Hotspot Profilesame1010000000Compare ok 
Application Usernotsame2112000210220800Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
915/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLogChange 9: Updated record 'haroldapp' Application UserAudit Log id 4 (UTC 15/09/2015 4:09:36 AM User: admin )
1015/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 10: Updated field 'Permissions Information::Groups' : Standard CTI EnabledChange 9Application User 
1115/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 11: Updated field 'Permissions Information::Roles' : Standard CTI EnabledChange 9Application User 
End User (Condensed)same13701370000000Compare ok 
SIP Realmsame2020000000Compare ok 
Credential Policy Defaultsame3030000000Compare ok 
Credential Policysame2020000000Compare ok 
Rolesame370370000000Compare ok 
Access Control Groupnotsame2812700112111100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
1216/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 12: Updated record 'Standard CTI Enabled
(S)'
 Access Control Group 
1316/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 13: Updated record 'Standard CTI Enabled
(S)'
Change 12Access Control Group 
UC Servicesame7070000000Compare ok 
Service Profilesame1010000000Compare ok 
User Profilesame2020000000Compare ok 
Self-Provisioningsame0000000000compare 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 2:08:30 PM15/09/2015 4:08:30 AM21:08:30.609admin  record in table device with key field name = 0021A02E05E0 updated10.5.1.25CUCM10521442290110
115/09/2015 2:08:44 PM15/09/2015 4:08:44 AM21:08:44.452admin  record in table device, with key field name = UDP_8861 deleted10.5.1.25CUCM10521442290124
215/09/2015 2:08:59 PM15/09/2015 4:08:59 AM21:08:59.825adminChange 0: Updated record 'DP_London'Device Poolrecord in table devicepool with key field name = DP_London updated10.5.1.25CUCM10521442290139
315/09/2015 2:09:12 PM15/09/2015 4:09:12 AM21:09:12.773adminChange 4: Added record with key 'CSS_5'Calling Search Spacerecord in table CallingSearchSpace with key field name = CSS_5 added10.5.1.25CUCM10521442290152
415/09/2015 2:09:36 PM15/09/2015 4:09:36 AM21:09:36.188adminChange 9: Updated record 'haroldapp'Application Userrecord in table applicationuser with key field name = haroldapp updated10.5.1.25CUCM10521442290176
515/09/2015 2:44:37 PM15/09/2015 4:44:37 AM21:44:37.081haroldappChange 2: Updated record 'CSS_3'
Change 3: Updated record 'CSS_3'
Calling Search Space
Calling Search Space
record in table CallingSearchSpace with key field name = CSS_3 updated10.5.1.25CUCM10521442292277
615/09/2015 2:44:39 PM15/09/2015 4:44:39 AM21:44:39.160haroldappPossible duplicate of 5 record in table CallingSearchSpace with key field name = CSS_3 updated10.5.1.25CUCM10521442292279

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 2:08:59 PM15/09/2015 4:08:59 AMAuditLogChange 0: Updated record 'DP_London' Device PoolAudit Log id 2 (UTC 15/09/2015 4:08:59 AM User: admin )
115/09/2015 2:08:59 PM15/09/2015 4:08:59 AMAuditLog-ParentChange 1: Updated field 'Roaming Sensitive Settings::Date/Time Group' from CMLocal to DTG-AddChange 0Device Pool 
215/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 2: Updated record 'CSS_3' Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
315/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 3: Updated record 'CSS_3'Change 2Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
415/09/2015 2:09:12 PM15/09/2015 4:09:12 AMAuditLogChange 4: Added record with key 'CSS_5' Calling Search SpaceAudit Log id 3 (UTC 15/09/2015 4:09:12 AM User: admin )
59/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 5: Updated record '5012' Route Plan Report 
69/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 6: Updated field 'Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 5Route Plan Report 
715/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 7: Updated record 'SEP0021A02E05E0' Cisco 7945 (1) 
815/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 8: Updated field '::Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 7Cisco 7945 (1) 
915/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLogChange 9: Updated record 'haroldapp' Application UserAudit Log id 4 (UTC 15/09/2015 4:09:36 AM User: admin )
1015/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 10: Updated field 'Permissions Information::Groups' : Standard CTI EnabledChange 9Application User 
1115/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 11: Updated field 'Permissions Information::Roles' : Standard CTI EnabledChange 9Application User 
1216/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 12: Updated record 'Standard CTI Enabled
(S)'
 Access Control Group 
1316/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 13: Updated record 'Standard CTI Enabled
(S)'
Change 12Access Control Group 

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 Server

The following Cisco Unified servers are present in the cluster:

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
Serversame5050000000Compare ok 

5.1.2 Comparison Results

No changes.

5.2 Services

The following services are present on this server:

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
Servicessame780780000000Compare ok 

5.2.2 Comparison Results

No changes.

5.3 Cisco Unified CM

The Cisco Unified Communications Manager (CUCM) cluster consists of the following servers:

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
Cisco Unified CMsame3030000000Compare ok 

5.3.2 Comparison Results

No changes.

5.4 Cisco Unified CM Group

A Cisco Unified Communications Manager (CUCM) group specifies a prioritized list of up to three Cisco Unified Communications Manager (CUCM)s.

The first Cisco Unified Communications Manager (CUCM) in the list serves as the primary Cisco Unified Communications Manager (CUCM) for that group, and the other members of the group serve as secondary and tertiary (backup) Cisco Unified Communications Manager (CUCM)s. Each device pool has one Cisco Unified Communications Manager (CUCM) group assigned to it. When a device registers, it attempts to connect to the primary (first) Cisco Unified Communications Manager (CUCM) in the group that is assigned to its device pool. If the primary Cisco Unified Communications Manager (CUCM) is not available, the device tries to connect to the next Cisco Unified Communications Manager (CUCM) that is listed in the group, and so on.

Cisco Unified Communications Manager (CUCM) groups provide important features for your system:

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
Cisco Unified CM Groupsame5050000000Compare ok 

5.4.2 Comparison Results

No changes.

5.5 Presence Redundancy Groups

A presence redundancy group is comprised of two or more IM and Presence Service nodes from the same cluster and provides both redundancy and recovery for IM and Presence Service clients and applications.

The following presence redundancy group are defined:

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
Presence Redundancy Groupssame1010000000Compare ok 

5.5.2 Comparison Results

No changes.

5.6 Phone NTP Reference

This table lists the NTP servers that you want the SIP phone to use to get its date and time.

Note: Cisco Unified Communications Manager cannot be configured as Phone NTP References.

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
Phone NTP Referencesame1010000000Compare ok 

5.6.2 Comparison Results

No changes.

5.7 Date/Time Group

Date/Time Groups define time zones for the various devices that are connected to Cisco Unified Communications Manager (CUCM).

Cisco Unified Communications Manager (CUCM) provides a default Date/Time Group called CMLocal that configures automatically when you install Cisco Unified Communications Manager (CUCM); however, Cisco recommends that you configure a group for each local time zone. CMLocal synchronizes to the active date and time of the operating system on the Cisco Unified Communications Manager (CUCM) server. After installing Cisco Unified Communications Manager (CUCM), you can change the settings for CMLocal as desired. Normally, you adjust the server date/time to the local time zone date and time.

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
Date/Time Groupsame2020000000Compare ok 

5.7.2 Comparison Results

No changes.

5.8 BLF Presence Group

Presence groups control the destinations that presence watchers can monitor.

To configure a presence group, create the group and assign one or more destinations and watchers to the same group.

Note : The system always allows presence requests within the same presence group. You must also specify the relationships to other presence groups by using one of the following permissions: Use System Default: use the Default Inter-Presence Group Subscription service parameter, Allow Subscription, Disallow Subscription.

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
BLF Presence Groupsame1010000000Compare ok 

5.8.2 Comparison Results

No changes.

5.9 Audio Codec Preference Lists

The Audio Codec Preference settings define the order of audio codec preference, both for calls within a region and for between regions.

Unified CM has two default Audio Codec Preference lists, one for lossy regions and another for low-loss regions. These are the Factory Default lossy, and the Factory Default low loss.

The following Audio Codec Preference lists are configured:

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
Audio Codec Preference Listssame2020000000Compare ok 

5.9.2 Comparison Results

No changes.

5.10 Region

Regions specify the bandwidth that is used for audio and video calls within a region and between existing regions. The audio codec determines the type of compression and the maximum amount of bandwidth that is used per audio call. The video call bandwidth comprises the sum of the audio bandwidth and video bandwidth but does not include overhead.

Cisco Unified Communications Manager (CUCM) allows addition of a maximum of 2000 regions.

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
Regionsame4040000000Compare ok 

5.10.2 Comparison Results

No changes.

5.11 Device Pool

Device pools define sets of common characteristics for devices. The device pool structure supports the separation of user and location information. The device pool now contains only device- and location-related information. The Common Profile window records all the user-oriented information. Ensure that each device is associated with a device pool and with a common profile for user-oriented information.

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
Device Poolnotsame1311200507150600Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
015/09/2015 2:08:59 PM15/09/2015 4:08:59 AMAuditLogChange 0: Updated record 'DP_London' Device PoolAudit Log id 2 (UTC 15/09/2015 4:08:59 AM User: admin )
115/09/2015 2:08:59 PM15/09/2015 4:08:59 AMAuditLog-ParentChange 1: Updated field 'Roaming Sensitive Settings::Date/Time Group' from CMLocal to DTG-AddChange 0Device Pool 

5.11.2 Comparison Results

Device Pool
NameDevice Pool Configuration
DP_London
Detected Change ID0
Detected ChangeUpdated record 'DP_London'
Detected ObjectDevice Pool
Detected Date (UTC)15/09/2015 4:08:58 AM
Detected Date (Local)15/09/2015 2:08:58 PM
Auditlog ID2
Audit Useradmin
Audit Detailsrecord in table devicepool with key field name = DP_London updated
Audit Server Time21:08:59.825
Child ID1
Device Pool Settings
Device Pool NameDP_London
CUCM GroupCMG_Sub1
Calling Search Space for Auto-registrationCSS_Autoreg
Adjunct CSS< None >
Reverted Call Focus PriorityDefault
Intercompany Media Services Enrolled GroupIntercompany_Media_Engine_Server_2
Local Route Group Settings
Standard Local Route Group 1< None >
Non Standard TEST group 1< None >
Roaming Sensitive Settings
Date/Time GroupCMLocal
DTG-Add
Detected Change ID1
Detected ChangeUpdated field 'Roaming Sensitive Settings::Date/Time Group' from CMLocal to DTG-Add
Detected ObjectDevice Pool
Detected Date (UTC)15/09/2015 4:08:58 AM
Detected Date (Local)15/09/2015 2:08:58 PM
Parent ID0
RegionG711
Media Resource Group List< None >
Location< None >
Network Locale< None >
SRST ReferenceDisable
Connection Monitor Duration
Single Button BargeDefault
Join Across LinesDefault
Physical Location< None >
Device Mobility Group< None >
Wireless LAN Profile Group< None >
Device Mobility Related Information
Device Mobility Calling Search Space< None >
AAR Calling Search Space< None >
AAR Group< None >
Calling Party Transformation CSS< None >
Called Party Transformation CSS< None >
Geo Location Configuration
Geo Location< None >
Geo Location Filter< None >
Incoming Calling Party Settings
National Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
International Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Unknown Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Subscriber Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Incoming Called Party Settings
National Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
International Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Unknown Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Subscriber Number (Prefix/Strip Digits/CSS)Default / 0 / < None >
Caller ID For Calls From This Phone
Calling Party Transformation CSSCSS_2
Connected Party Settings
Connected Party Transformation CSSCSS_2
Redirecting Party Settings
Redirecting Party Transformation CSSCSS_3

5.12 Device Mobility Group

Device mobility groups support the device mobility feature. Device mobility groups represent the highest level geographic entities in your network. Depending upon the network size and scope, your device mobility groups could represent countries, regions, states or provinces, cities, or other entities. For example, an enterprise with a worldwide network might choose device mobility groups that represent individual countries, whereas an enterprise with a national or regional network might define device mobility groups that represent states, provinces, or cities.

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
Device Mobility Groupsame2020000000Compare ok 

5.12.2 Comparison Results

No changes.

5.13 Device Mobility Info

The Device Mobility Info window specifies the subnets and device pools that are used for device mobility. When a phone registers with Cisco Unified Communications Manager, the system compares the IP address of the device to device mobility subnets that are specified in the Device Mobility Info window and associated with one of the device pools.

The matching subnet becomes the device's home subnet for the purpose of device mobility.

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
Device Mobility Infosame1010000000Compare ok 

5.13.2 Comparison Results

No changes.

5.14 DHCP Server

The following Dynamic Host Configuration Protocol (DHCP) servers are configured:

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
DHCP Serversame1010000000Compare ok 

5.14.2 Comparison Results

No changes.

5.15 DHCP Subnet

The following Dynamic Host Configuration Protocol (DHCP) subnets are configured:

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
DHCP Subnetsame1010000000Compare ok 

5.15.2 Comparison Results

No changes.

5.16 LDAP System

The LDAP system object allows to enable LDAP synchronization and to set up the LDAP server type and the LDAP attribute name for the user ID.

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
LDAP Systemsame3030000000Compare ok 

5.16.2 Comparison Results

No changes.

5.17 LDAP Directory

Synchronization of Cisco Unified Communications Manager (CUCM) with a corporate LDAP directory allows reuse of user data stored in the LDAP directory and allows the corporate LDAP directory to serve as the central repository for that information. Cisco Unified Communications Manager (CUCM) has an integrated database for storing user data and a web interface within Cisco Unified Communications Manager (CUCM) Administration for creating and managing user data in that database. When synchronization is enabled, that local database is still used, but the Cisco Unified Communications Manager (CUCM) facility to create user accounts becomes disabled. Management of user accounts is then accomplished through the interface of the LDAP directory.

The user account information is imported from the LDAP directory into the database located on the Cisco Unified Communications Manager (CUCM) publisher server. Information that is imported from the LDAP directory may not be changed by Cisco Unified Communications Manager (CUCM). Additional user information specific to the Cisco Unified Communications Manager (CUCM) implementation is managed by Cisco Unified Communications Manager (CUCM) and stored only within its local database. For example, device-to-user associations, speed dials, and user PINs are data that are managed by Cisco Unified Communications Manager (CUCM), and they do not exist in the corporate LDAP directory. The user data is then propagated from the Cisco Unified Communications Manager (CUCM) publisher server to the subscribers via the built-in database synchronization.

You can make changes to LDAP Directory information and LDAP Authentication settings only if synchronization from the customer LDAP directory is enabled in the Cisco Unified Communications Manager Administration LDAP System.

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
LDAP Directorysame1010000000Compare ok 

5.17.2 Comparison Results

No changes.

5.18 LDAP Authentication

The LDAP authentication feature enables Cisco Unified Communications Manager (CUCM) to authenticate end user passwords against a corporate LDAP directory instead of using the embedded database. This authentication is accomplished with an LDAPv3 connection established between the IMS module within Cisco Unified Communications Manager (CUCM) and a corporate directory server.

You can make changes to LDAP Directory information and LDAP Authentication settings only if synchronization from the customer LDAP directory is enabled in the Cisco Unified Communications Manager Administration LDAP System.

The following statements describe Cisco Unified Communications Manager (CUCM)'s behavior when authentication is enabled:

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
LDAP Authenticationsame0000030300Compare ok 

5.18.2 Comparison Results

No changes.

5.19 LDAP Custom Filter

The LDAP filter filters the results of LDAP searches when Cisco DirSync is in use. LDAP users that match the filter get imported into the Cisco Unified Communications Manager database, while LDAP users that do not match the filter do not get imported.

The filter must comply with the regular LDAP search filter standards specified in RFC 4515. Enclose the filter text within parentheses (). It is recommended to verify the LDAP search filter against the LDAP directory-searchbase by using the ldapsearch command.

You apply LDAP filters to LDAP directories.Before you can synchronize the LDAP directory, you must activate the Cisco DirSync service.

The following LDAP filters are defined:

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
LDAP Custom Filtersame1010000000Compare ok 

5.19.2 Comparison Results

No changes.

5.20 SAML Single Sign-On

The single sign on feature allows end users to log into a Windows client machine on a Windows domain, then use certain Cisco Unified Communications Manager applications without signing on again.

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
SAML Single Sign-Onsame5050000000Compare ok 

5.20.2 Comparison Results

No changes.

5.21 Cross-Origin Resource Sharing (CORS)

Cross-Origin Resource Sharing (CORS) is a mechanism to allow code running in a browser (JavaScript for example) to make requests to a domain other then the one from where it originated.

The following CORS domain are configured:

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
Cross-Origin Resource Sharing (CORS)same1010000000Compare ok 

5.21.2 Comparison Results

No changes.

5.22 Location

Locations are used to implement call admission control in a centralized call-processing system. Call admission control enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between the locations.

If you do not use call admission control to limit the audio and video bandwidth on an IP WAN link, an unlimited number of calls can be active on that link at the same time. This situation can cause the audio quality of each audio call and the video quality of each video call to degrade as the link becomes oversubscribed.

In a centralized call-processing system, a single Cisco Unified Communications Manager (CUCM) cluster provides call processing for all locations on the IP telephony network. The Cisco Unified Communications Manager (CUCM) cluster usually resides at the main (or central) location, along with other devices such as phones and gateways. The remote locations contain additional devices, but no Cisco Unified Communications Manager (CUCM). IP WAN links connect the remote locations to the main location.

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
Locationsame5050000000Compare ok 

5.22.2 Comparison Results

No changes.

5.23 Location Bandwidth Manager Group

The Location Bandwidth Manager Groups configure which Location Bandwidth Manager (LBM) services each Cisco Callmanager service communicate with.

Each Cisco Callmanager service must communicate with an LBM service to determine the availability of bandwidth for each call, and to deduct bandwidth for the duration of each call that is admitted.

The LBM Group Page allows the Cisco Callmanger service to communicate with selected LBM services, instead of communicating with the local LBM service.

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
Location Bandwidth Manager Groupsame1010000000Compare ok 

5.23.2 Comparison Results

No changes.

5.24 Location Bandwidth Manager Intercluster Replication Group

Location Bandwidth Manager Hub Group configuration enables an LBM service to participate directly in inter-cluster replication of configured and dynamic Location Bandwidth data. LBMs assigned an LBM Hub Group discover each other through their common connections and form a fully-meshed replication network. Other LBM services in a cluster with an LBM Hub participate indirectly in inter-cluster replication through the LBM Hubs in their cluster.

Use the LBM Hub Group Page to configure the LBM Hub service to find a location in the remote clusters to establish external communication

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
Location Bandwidth Manager Intercluster Replication Groupsame1010000000Compare ok 

5.24.2 Comparison Results

No changes.

5.25 Physical Location

Physical locations support the Device Mobility feature. Physical locations provide a means of distinguishing the parameters that relate to a specific geographical location from other parameters.

For example, a media resources server may serve a specific office or campus within the enterprise. When a device roams to another office or campus and reregisters with Cisco Unified Communications Manager, you want to have the media resources server at the roaming location serve the device. By defining the physical location according to availability of media services, you can assure efficient and cost-effective reassignment of services as devices move from one physical location to another. Depending upon the network structure and allocation of services, you may define physical locations based upon a city, enterprise campus, or building.

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
Physical Locationsame2020000000Compare ok 

5.25.2 Comparison Results

No changes.

5.26 SRST

A survivable remote site telephony (SRST) reference comprises the gateway that can provide limited Cisco Unified Communications Manager (CUCM) functionality when all other Cisco Unified Communications Manager (CUCM) servers for a device are unreachable.

Typically assigned to device pools, SRST references determine the gateways where calling devices search when they attempt to complete a call if Cisco Unified Communications Manager (CUCM) is unavailable.

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
SRSTsame1010000000Compare ok 

5.26.2 Comparison Results

No changes.

5.27 MLPP Domain

An MLPP domain specifies the collection of devices and resources that are associated with an MLPP subscriber. When an MLPP subscriber that belongs to a particular domain places a precedence call to another MLPP subscriber that belongs to the same domain, MLPP service can preempt the existing call that the called MLPP subscriber is on for a higher precedence call. MLPP service availability does not go across different domains.

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
MLPP Domainsame1010000000Compare ok 

5.27.2 Comparison Results

No changes.

5.28 Resource Priority Namespace Network Domain

Cisco Unified Communications Manager uses Resource Priority Namespace Network Domains to support Voice over Secured IP (VoSIP) networks by using Multilevel Precedence and Preemption (MLPP) for Session Initiation Protocol (SIP) trunks.

MLPP, with configured Resource Priority domains, prioritizes SIP-signaled resources and enables indications related to precedence and preempted calls. End users can establish secure calls when the calls traverse SIP trunks.

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
Resource Priority Namespace Network Domainsame2020000000Compare ok 

5.28.2 Comparison Results

No changes.

5.29 Resource Priority Namespace List

Cisco Unified Communications Manager uses Resource Priority Namespace Lists to configure a default group of Resource Priority Namespace Network Domains to add to a SIP profile for validating incoming Resource Priority Namespace Network Domains.

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
Resource Priority Namespace Listsame2020000000Compare ok 

5.29.2 Comparison Results

No changes.

5.30 Enterprise Parameters

Enterprise parameters provide default settings that apply to all devices and services in the same cluster. (A cluster comprises a set of Cisco Unified Communications Managers that share the same database.) When you install a new Cisco Unified Communications Manager, it uses the enterprise parameters to set the initial values of its device defaults.

You cannot add or delete enterprise parameters, but you can update existing enterprise parameters.

Please note that not all parameters are listed as not all parameters can be retrieved.

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
Enterprise Parameterssame13701370000000Compare ok 

5.30.2 Comparison Results

No changes.

5.31 Enterprise Phone Configuration

The Enterprise Phone Configuration defines parameters that will apply to all phones that support these parameters.

Parameters that you set in this window may also appear in the Common Phone profile window and the Device Configuration window for various devices. If you set these same parameters in these other windows too, the setting that takes precedence is determined in the following order: 1) Device Configuration window settings, 2) Common Phone Profile window settings, 3) Enterprise Phone Configuration window settings.

If the "Override Common Settings" box is not checked for any corresponding setting, the corresponding parameter setting does not take effect.

The following Enterprise Phone Configuration are configured:

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
Enterprise Phone Configurationsame11201120000000Compare ok 

5.31.2 Comparison Results

No changes.

5.32 Service Parameters

Service parameters provide default settings that apply to all devices and services in the same cluster. (A cluster comprises a set of Cisco Unified Communications Manager (CUCM)s that share the same database.) When you install a new Cisco Unified Communications Manager (CUCM), it uses the enterprise parameters to set the initial values of its device defaults.

If a subscriber parameter is not equal to the publisher parameter, the subscriber value will appear in red. If the value can not be retrieved (for example the subscriber server is not active but configured in the database, the subscriber value appears as error.

Please note that not all parameters are listed as not all parameters can be retrieved.

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
Service Parameterssame80708070000000Compare ok 

5.32.2 Comparison Results

No changes.

5.33 Certificate

A certificate is a message that contains the certificate holder name, the public key, and the digital signature of the certificate authority that is issuing the certificate. Certificate fields are read only.

The following certificates are installed on CUCM:

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
Certificatesame270270000000Compare ok 

5.33.2 Comparison Results

No changes.

5.34 Phone Security Profile

Cisco Unified Communications Manager Administration groups security-related settings for a phone type and protocol into security profiles to allow you to assign a single security profile to multiple phones. Security-related settings include device security mode, digest authentication, and some CAPF settings. You apply the configured settings to a phone when you choose the security profile in the Phone Configuration window.

Installing Cisco Unified Communications Manager provides a set of predefined, nonsecure security profiles for auto-registration. To enable security features for a phone, you must configure a new security profile for the device type and protocol and apply it to the phone.

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
Phone Security Profilesame15501550000000Compare ok 

5.34.2 Comparison Results

No changes.

5.35 SIP Trunk Security Profile

The SIP Trunk Security Profile object includes security-related settings such as transport type, device security mode, digest authentication settings, and authorization settings for incoming SIP messages. Security profiles must be applied to all SIP trunks that are configured.

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
SIP Trunk Security Profilesame2020000000Compare ok 

5.35.2 Comparison Results

No changes.

5.36 Application Server

The following Cisco application servers are known to the cluster:

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
Application Serversame2020000000Compare ok 

5.36.2 Comparison Results

No changes.

5.37 Geolocation

Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.

Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.

The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC.

You assign these geolocations to VoIP phones, VoIP gateways, IP trunks, device pools, and enterprise parameters.

You can define geolocation filters that select a subset of fields from geolocation and associate with VoIP gateways, IP trunks, device pools, and enterprise parameters

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
Geolocationsame1010000000Compare ok 

5.37.2 Comparison Results

No changes.

5.38 Geolocation Filter

Geolocation filters allow selection of specific fields from the 17 geolocation fields for the purpose of creating an identifier from the selected fields. Geolocation filters get configured manually and are assigned to devices.

The following logic determines the geolocation filter value:

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
Geolocation Filtersame1010000000Compare ok 

5.38.2 Comparison Results

No changes.

5.39 E911 Messages

The E911 Messages Configuration page displays the Agreement, Disclaimer, and Error messages. Optionally, you can edit the E911 messages to be displayed on off-premises devices.

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
E911 Messagessame3030000000Compare ok 

5.39.2 Comparison Results

No changes.

5.40 AAR Group

Automated alternate routing (AAR) provides a mechanism to reroute calls through the PSTN when a call is blocked due to insufficient location bandwidth. With automated alternate routing, the caller does not need to hang up and redial the called party.

Cisco Unified Communications Manager (CUCM) automatically attempts to reroute calls, due to insufficient bandwidth, through the PSTN or other network only when the AAREnable enterprise parameter is set to true. Cisco Unified Communications Manager (CUCM) uses the device-based AAR calling search space, which is assigned to Cisco IP Phone station devices and gateway devices, when it attempts to route the call to the gateway device that connects to the PSTN or other network.

Cisco Unified Communications Manager (CUCM) retrieves the prefix digits from the AAR dial prefix matrix table based on the AAR group value of the originating line/DN and gateway device and the AAR group value of the terminating line, and Cisco voice-mail port, to transform the derived alternate number.

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
AAR Groupsame4040000000Compare ok 

5.40.2 Comparison Results

No changes.

5.41 Application Dial Rules

The administrator uses dial rules configuration to add and sort the priority of dialing rules. Dial rules for applications such as Cisco Unified Communications Manager Assistant automatically strip numbers from or add numbers to telephone numbers that a user dials. For example, the dial rules automatically add the digit 9 in front of a 7-digit telephone number to provide access to an outside line.

For example, in Cisco Unified Communications Manager Assistant, the assistant can perform a directory search from the assistant console. The assistant can drag and drop the directory entry to the My Calls panel on the assistant console, which invokes a call to the number that is listed in the entry. The dial rules apply to the number that is listed in the entry before the call gets made.

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
Application Dial Rulessame1010000000Compare ok 

5.41.2 Comparison Results

No changes.

5.42 Directory Lookup Dial Rules

Directory lookup rules transform caller identification numbers into numbers that can be looked up in the directory. Each rule specifies which numbers to transform based on the beginning digits and length of the number. For example, you can create a directory lookup rule that automatically removes the area code and 2 prefix digits from a 10-digit telephone, which would transform 4085551212 into 51212. If Cisco Unified Communications Manager Attendant Console can match the number with a user in the speed-dial entries of the attendant or in the directory, the attendant console displays the name in the Call Detail window.

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
Directory Lookup Dial Rulessame1010000000Compare ok 

5.42.2 Comparison Results

No changes.

5.43 SIP Dial Rules

SIP dial rules are used to configure SIP phone dial plans and associate them with SIP phones.

Without SIP dial rules, the user must press the Dial softkey unless the phone supports KPML. SIP dial rules must get associated with a SIP phone, so the dial plans get sent to the device.

Pattern recognition is concerned only with automating the collection of user digit input, to be forwarded automatically to Cisco Unified Communications Manager (CUCM) without requiring inter-digit timeout or pressing the Dial key. All enforcement of class of service is handled by the various calling search spaces chosen from within Cisco Unified Communications Manager (CUCM).

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
SIP Dial Rulessame2020000000Compare ok 

5.43.2 Comparison Results

No changes.

5.44 Route Filter

Route filters, along with route patterns-hunt pilots, use dialed-digit strings to determine how a call is handled. Route filters only apply when you configure a pattern that contains the at (@) wildcard. When the route pattern-hunt pilot contains the @ wildcard, Cisco Unified Communications Manager routes calls according to the numbering plan that is specified in the Numbering Plan drop-down list box.

Route filters allow you to determine which route patterns-hunt pilots your users can dial; for example, whether your users can manually choose a long-distance carrier (by dialing 101 plus a carrier access code).

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
Route Filtersame1010000000Compare ok 

5.44.2 Comparison Results

No changes.

5.45 Route List and Route Group

A route group allows you to designate the order in which gateways and trunks are selected. It allows you to prioritize a list of gateways and ports for outgoing trunk selection. A Route Group can be added to any number of Route Lists.

A route list associates a set of route groups in a specified priority order. A route list then associates with one or more route patterns and determines the order in which those route groups are accessed. The order controls the progress of the search for available devices for outgoing calls.

A route list can contain only route groups. Each route list should have at least one route group. Each route group includes at least one device, such as a gateway, that is available.

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
Route List and Route Groupsame1010000000Compare ok 

5.45.2 Comparison Results

No changes.

5.46 Route Group

A route group allows you to designate the order in which gateways and trunks are selected. It allows you to prioritize a list of gateways and ports for outgoing trunk selection.

For example, if you use two long-distance carriers, you could add a route group, so long-distance calls to the less expensive carrier are given priority. Calls route to the more expensive carrier only if the first trunk is unavailable.

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
Route Groupsame3030000000Compare ok 

5.46.2 Comparison Results

No changes.

5.47 Local Route Group Names

A local route group name is a unique name that you assign to a local route group. The Local Route Group Names window allows you to add and configure multiple local route group names that you can customize and associate with route groups for a given device pool.

From Cisco Unified Communications Manager Release 10.0(1), a given device pool supports multiple local route groups.

The following local route group names are defined:

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
Local Route Group Namessame2020000000Compare ok 

5.47.2 Comparison Results

No changes.

5.48 Route List

A route list associates a set of route groups in a specified priority order. A route list then associates with one or more route patterns and determines the order in which those route groups are accessed. The order controls the progress of the search for available devices for outgoing calls.

A route list can contain only route groups. Each route list should have at least one route group. Each route group includes at least one device, such as a gateway, that is available. Based on device type, Cisco Unified Communications Manager can choose some, or all, ports as resources in each route group. Some devices, such as digital access, only allow you to choose all ports.

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
Route Listsame1010000000Compare ok 

5.48.2 Comparison Results

No changes.

5.49 Route Pattern (Condensed)

A route pattern comprises a string of digits (an address) and a set of associated digit manipulations that route calls to a route list or a gateway. Route patterns provide flexibility in network design. They work in conjunction with route filters and route lists to direct calls to specific devices and to include, exclude, or modify specific digit patterns.

If a gateway does not have a route pattern, it cannot place calls to the PSTN or to a PBX. To assign a route pattern to an individual port on a gateway, you must assign a route list and a route group to that port.


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
Route Pattern (Condensed)same2020000000Compare ok 

5.49.2 Comparison Results

No changes.

5.50 Hunt Pilot - List and Group

Hunt lists comprise ordered groupings of line groups. A line group may belong to more than one hunt list. Hunt pilots associate with hunt lists. A hunt list may associate with more than one hunt pilot.

Hunt pilots comprise sets of digits. They comprise lists of route patterns that are used for hunting. A hunt pilot can specify a partition, numbering plan, route filter, and hunt forward settings. A hunt pilot must specify a hunt list.


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
Hunt Pilot - List and Groupsame1010000000Compare ok 

5.50.2 Comparison Results

No changes.

5.51 Line Group

A line group allows you to designate the order in which directory numbers are chosen. Cisco Unified Communications Manager distributes a call to idle or available members of a line group based on a call distribution algorithm and on the Ring No Answer Reversion (RNAR) Timeout setting.

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
Line Groupsame2020000000Compare ok 

5.51.2 Comparison Results

No changes.

5.52 Hunt List

A Hunt List lists a set of Line groups in a specific order. A hunt list then associates with one or more hunt pilots and determines the order in which those line groups are accessed. The order controls the progress of the search for available directory numbers for incoming calls.

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
Hunt Listsame1010000000Compare ok 

5.52.2 Comparison Results

No changes.

5.53 Hunt Pilot

Hunt pilots comprise sets of digits. They comprise lists of route patterns that are used for hunting. A hunt pilot can specify a partition, numbering plan, route filter, and hunt forward settings. A hunt pilot must specify a hunt list.

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
Hunt Pilotsame1010000000Compare ok 

5.53.2 Comparison Results

No changes.

5.54 SIP Route Pattern (Condensed)


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
SIP Route Pattern (Condensed)same2020000000Compare ok 

5.54.2 Comparison Results

No changes.

5.55 Access List

An access list, which supports Cisco Unified Mobility, specifies a list that determines the phone numbers that the system can pass or block from being passed to remote destinations.


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
Access Listsame1010000000Compare ok 

5.55.2 Comparison Results

No changes.

5.56 Time Schedule and Period

A time schedule comprises a group of time periods. Time schedules get assigned to partitions. Time schedules determine the partitions where calling devices search when they are attempting to complete a call during a particular time of day.

A time period comprises a time range that is defined by a start time and end time. Time periods also specify a repetition interval either as days of the week or a specified date on the yearly calendar. Administrators define time periods and then associate the time periods with time schedules.

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
Time Schedule and Periodsame2020000000Compare ok 

5.56.2 Comparison Results

No changes.

5.57 Partition

A partition comprises a logical grouping of directory numbers (DNs) and route patterns with similar reachability characteristics. Devices that are typically placed in partitions include DNs and route patterns. These entities associate with DNs that users dial.

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
Partitionsame280280000000Compare ok 

5.57.2 Comparison Results

No changes.

5.58 Calling Search Space

A calling search space (CSS) comprises an ordered list of route partitions that are typically assigned to devices. Calling search spaces determine the partitions that calling devices search when they are attempting to complete a call.

When a calling search space is assigned to a device, the list of partitions in the calling search space comprises only the partitions that the device is allowed to reach.

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
Calling Search Spacenotsame24122107216830Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
215/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 2: Updated record 'CSS_3' Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
315/09/2015 2:44:37 PM15/09/2015 4:44:37 AMAuditLogChange 3: Updated record 'CSS_3'Change 2Calling Search SpaceAudit Log id 5 (UTC 15/09/2015 4:44:37 AM User: haroldapp )
415/09/2015 2:09:12 PM15/09/2015 4:09:12 AMAuditLogChange 4: Added record with key 'CSS_5' Calling Search SpaceAudit Log id 3 (UTC 15/09/2015 4:09:12 AM User: admin )

5.58.2 Comparison Results

Calling Search Space
NameDescriptionRoute Partitions for this Calling Search Space
CSS_3
Detected Change ID2
Detected ChangeUpdated record 'CSS_3'
Detected ObjectCalling Search Space
Detected Date (UTC)15/09/2015 4:44:37 AM
Detected Date (Local)15/09/2015 2:44:37 PM
Auditlog ID5
Audit Userharoldapp
Audit Detailsrecord in table CallingSearchSpace with key field name = CSS_3 updated
Audit Server Time21:44:37.081
Child ID3
CSS_3Directory URI
Global Learned E164 Numbers
Global Learned E164 Patterns
Global Learned Enterprise Numbers
Global Learned Enterprise Patterns
P_1
P_11
P_12
P_2
P_3
P_4
P_5
P_AutoReg
P_Brisbane
P_Brisbane_1
P_Brisbane_2
P_Brisbane_3
P_LoggedOut
P_Perth_1
P_Perth_2
P_Perth_3
P_Sydney_1
P_Sydney_2
P_Sydney_3
Cluster-Internal-PT
LC_INTERNAL_PART
P_Perth
P_Sydney
Partition_1
Detected Change ID3
Detected ChangeUpdated record 'CSS_3'
Detected ObjectCalling Search Space
Detected Date (UTC)15/09/2015 4:44:39 AM
Detected Date (Local)15/09/2015 2:44:39 PM
Parent ID2
Auditlog ID5
Audit Userharoldapp
Audit Detailsrecord in table CallingSearchSpace with key field name = CSS_3 updated
Audit Server Time21:44:37.081
CSS_5
Detected Change ID4
Detected ChangeAdded record with key 'CSS_5'
Detected ObjectCalling Search Space
Detected Date (UTC)15/09/2015 4:09:11 AM
Detected Date (Local)15/09/2015 2:09:11 PM
Auditlog ID3
Audit Useradmin
Audit Detailsrecord in table CallingSearchSpace with key field name = CSS_5 added
Audit Server Time21:09:12.773
  

5.59 Intercom Route Partition

An intercom partition contains a list of route patterns [directory number (DN) and route patterns]. Partitions facilitate call routing by dividing the route plan into logical subsets that are based on organization, location, and call type.

The following intercom route partitions are configured:

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
Intercom Route Partitionsame4040000000Compare ok 

5.59.2 Comparison Results

No changes.

5.60 Intercom Calling Search Space

An intercom calling search space comprises an ordered list of intercom route partitions that are typically assigned to devices. Intercom calling search spaces determine the partitions that calling devices search when they are attempting to complete a call.

The following intercom calling search spaces are configured:

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
Intercom Calling Search Spacesame4040000000Compare ok 

5.60.2 Comparison Results

No changes.

5.61 Intercom Directory Number

The following table lists all intercom lines (assigned and not assigned to any phones).

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
Intercom Directory Numbersame160160000000Compare ok 

5.61.2 Comparison Results

No changes.

5.62 Intercom Directory Number - Unassigned

The following table lists all unassigned intercom lines.

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
Intercom Directory Number - Unassignedsame150150000000Compare ok 

5.62.2 Comparison Results

No changes.

5.63 Intercom Translation Pattern

Cisco Unified Communications Manager uses intercom translation patterns to manipulate dialed digits before it routes a call. In some cases, the system does not use the dialed number. In other cases, the public switched telephone network (PSTN) does not recognize the dialed number.

The following intercom translation patterns are configured:

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
Intercom Translation Patternsame1010000000Compare ok 

5.63.2 Comparison Results

No changes.

5.64 Client Matter Codes

To use the Client Matter Codes feature, users must enter a client matter code to reach certain dialed numbers.

You enable or disable CMC through route patterns, and you can configure multiple client matter codes. When a user dials a number that is routed through a CMC-enabled route pattern, a tone prompts the user for the client matter code. When the user enters a valid CMC, the call occurs; if the user enters an invalid code, reorder occurs. The CMC writes to the CDR, so you can collect the information by using Cisco Unified Communications Manager (CUCM) CDR Analysis and Reporting (CAR), which generates reports for client accounting and billing.

You can implement CMC and FAC separately or together. For example, you may authorize users to place certain classes of calls, such as long distance calls, and also assign the class of calls to a specific client. If you implement CMC and FAC together, the user dials a number, enters the user-specific authorization code when prompted to do so, and then enters the client matter code at the next prompt. CMC and FAC tones sound the same to the user, so the feature tells the user to enter the authorization code after the first tone and enter the CMC after the second tone.

The CMC and FAC features work with all Cisco Unified IP Phone models and MGCP-controlled analog gateways.

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
Client Matter Codessame3030000000Compare ok 

5.64.2 Comparison Results

No changes.

5.65 Forced Authorization Code

When you enable FAC through route patterns, users must enter an authorization code to reach the intended recipient of the call. When a user dials a number that is routed through a FAC-enabled route pattern, the system plays a tone that prompts for the authorization code.

In Cisco Unified Communications Manager (CUCM) Administration, you can configure various levels of authorization. If the user authorization code does not meet or exceed the level of authorization that is specified to route the dialed number, the user receives a reorder tone. If the authorization is accepted, the call occurs.

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
Forced Authorization Codesame2020000000Compare ok 

5.65.2 Comparison Results

No changes.

5.66 Translation Pattern (Condensed)

The Cisco Unified Communications Manager (CUCM) uses translation patterns to manipulate dialed digits before it routes a call. In some cases, the system does not use the dialed number. In other cases, the public switched telephone network (PSTN) does not recognize the dialed number.

The following list is the condensed version of translation patterns:


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
Translation Pattern (Condensed)same2020000000Compare ok 

5.66.2 Comparison Results

No changes.

5.67 Call Park

The Call Park feature allows you to place a call on hold, so it can be retrieved from another phone in the Cisco Unified Communications Manager (CUCM) system (for example, a phone in another office or in a conference room).

If you are on an active call at your phone, you can park the call to a call park extension by pressing the Park softkey or the Call Park button. Someone on another phone in your system can then dial the call park extension to retrieve the call.


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
Call Parksame3030000000Compare ok 

5.67.2 Comparison Results

No changes.

5.68 Directed Call Park

Directed Call Park allows a user to transfer a call to an available user-selected directed call park number. Configure directed call park numbers in the Cisco Unified Communications Manager Directed Call Park Configuration window. Configured directed call park numbers exist cluster wide. You can configure phones that support the directed call park Busy Lamp Field (BLF) to monitor the busy/idle status of specific directed call park numbers. Users can also use the BLF to speed dial a directed call park number. A user can retrieve a parked call by dialing a configured retrieval prefix followed by the directed call park number where the call is parked

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
Directed Call Parksame1010000000Compare ok 

5.68.2 Comparison Results

No changes.

5.69 Call Pickup Group

Call Pickup allows you to answer a call that comes in on a directory number other than your own. When you hear an incoming call ringing on another phone, you can redirect the call to your phone by using this feature.

Cisco Unified IP Phones provide three types of call pickup:

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
Call Pickup Groupsame4040000000Compare ok 

5.69.2 Comparison Results

No changes.

5.70 Call Pickup Group - Group Members

This section lists the members of each Call Pickup Group.

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
Call Pickup Group - Group Memberssame4040000000Compare ok 

5.70.2 Comparison Results

No changes.

5.71 Directory Number (Condensed)

This section lists all Directory numbers configured (associated and unassigned directory numbers).

Directory numbers may be associated with devices such as phones, route points, CTI ports, and H.323 clients.


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
Directory Number (Condensed)same11301130000000Compare ok 

5.71.2 Comparison Results

No changes.

5.72 Directory Numbers - Unallocated (Condensed)

This section lists all Directory numbers configured which are not assigned to any device.

Directory numbers may be associated with devices such as phones, route points, CTI ports, and H.323 clients.

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
Directory Numbers - Unallocated (Condensed)same830830000000Compare ok 

5.72.2 Comparison Results

No changes.

5.73 Meet-Me Number/Pattern

Meet-Me conferences require an allocation of directory numbers. Cisco Unified Communications Manager (CUCM) Administration provides the Meet-Me conference directory number range to users, so they can access the feature.

Cisco Unified Communications Manager (CUCM) supports a maximum of 100 simultaneous meet-me conferences for each Cisco Unified Communications Manager (CUCM) server.


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
Meet-Me Number/Patternsame3030000000Compare ok 

5.73.2 Comparison Results

No changes.

5.74 Route Plan Report

The route plan report comprises a listing of all unassigned directory numbers (DN), call park numbers, call pickup numbers, conference numbers (Meet-Me numbers), directory numbers, route patterns, translation patterns, voice-mail ports, message-waiting indicators, and attendant console numbers in the system.

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
Route Plan Reportnotsame152115100912191100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
59/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 5: Updated record '5012' Route Plan Report 
69/09/2015 7:58:40 PM9/09/2015 9:58:40 AMDetectedChange 6: Updated field 'Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 5Route Plan Report 

5.74.2 Comparison Results

Route Plan Report
PatternPartitionUsageDeviceDevice TypeDescription
5012
Detected Change ID5
Detected ChangeUpdated record '5012'
Detected ObjectRoute Plan Report
Detected Date (UTC)9/09/2015 9:58:40 AM
Detected Date (Local)9/09/2015 7:58:40 PM
Child ID6
P_Sydney_2DeviceSEP0021A02E05E0Cisco 7945Phone of Bruce Wayne Updated at 17:36
Phone of Bruce Wayne Updated at 14:08
Detected Change ID6
Detected ChangeUpdated field 'Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08
Detected ObjectRoute Plan Report
Detected Date (UTC)9/09/2015 9:58:40 AM
Detected Date (Local)9/09/2015 7:58:40 PM
Parent ID5

5.75 Calling Party Transformation Pattern

The parameters in the Calling Party Transformation Patterns provide appropriate caller information using the Calling Party Transformation calling search space on the destination device. Be aware that calls through transformation patterns are not routable. When this pattern is matched, the call does not route to any device.

You use calling party transformation patterns with the calling party normalization feature.Configuring calling party normalization alleviates issues with toll bypass where the call is routed to multiple locations over the IP WAN. In addition, it allows Cisco Unified Communications Manager to distinguish the origin of the call to globalize or localize the calling party number for the phone user.

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
Calling Party Transformation Patternsame2020000000Compare ok 

5.75.2 Comparison Results

No changes.

5.76 Called Party Transformation Pattern

The parameters in the Called Party Transformation Patterns provide appropriate caller information by using the Called Party Transformation calling search space on the destination device. Be aware that calls through transformation patterns are not routable. When this pattern is matched, the call does not route to any device.

Called party transformations settings allow you to manipulate the dialed digits, or called party number, for outgoing calls. Examples of manipulating called numbers include appending or removing prefix digits (outgoing calls), appending area codes to calls dialed as seven-digit numbers, appending area codes and office codes to interoffice calls dialed as four- or five-digit extensions, and suppressing carrier access codes for equal access calls.

Configuration of called party transformations settings that are used in route lists occurs in the individual route groups that comprise the list. The called party transformations settings that are assigned to the route groups in a route list override any called party transformations settings that are assigned to a route pattern or translation pattern that is associated with that route list.

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
Called Party Transformation Patternsame2020000000Compare ok 

5.76.2 Comparison Results

No changes.

5.77 Transformation Profile

Cisco Intercompany Media Engine configuration comprises configuration of transformation profiles.

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
Transformation Profilesame2020000000Compare ok 

5.77.2 Comparison Results

No changes.

5.78 Mobility Enterprise Feature Access Number

The Mobility Enterprise Feature Configuration defines mobility enterprise feature access (EFA) numbers. These numbers can then associate with mobility profile(s) for use.

The DID number defines enterprise feature access and supports transfer, conference, resume, and two-stage dialing from smartphones. Each DID number is unique.

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
Mobility Enterprise Feature Access Numbersame2020000000Compare ok 

5.78.2 Comparison Results

No changes.

5.79 Handoff Configuration

The Handoff Mobility Configuration defines a handoff number and/or partition for dual-mode phones between the Wi-Fi and Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA) networks. The handoff feature requires this number.

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
Handoff Configurationsame1010000000Compare ok 

5.79.2 Comparison Results

No changes.

5.80 Mobility Profile

Mobility profiles specify profiles which configure Dial-via-Office Forward (DVO-F) or Dial-via-Office Reverse (DVO-R) settings for a mobile client. A mobility profile is then assigned to a user or to a group of users, such as the users in a region or location.

Mobility profiles can associate with a standalone Cisco Unified Mobile Communicator mobile identity or with a Cisco Unified Mobile Communicator-enabled dual-mode mobile identity. Standard, single-mode remote destinations cannot associate with a mobility profile.

Mobility profiles settings can be changed only by administrators: users cannot change the settings in a mobility profile.

The following mobility profiles are defined:

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
Mobility Profilesame3030000000Compare ok 

5.80.2 Comparison Results

No changes.

5.81 Logical Partitioning Policy

Logical partitioning specifies a call control feature in Cisco Unified Communications Manager that provides functionality, so communication between the following pairs of VoIP entities can be controlled:

No logical partitioning policy logic exists on endpoints. Be aware that logical partitioning is required to control such communication not only during basic call establishment but also during mid-call as a result of midcall features.

The Cisco Unified Communications Manager basic routing policy constructs of calling search spaces and partitions suffice to prevent forbidden basic calls from being established but are not sufficient to prevent forbidden calls from being created as a result of midcall features. In Cisco Unified Communications Manager, such midcall features are often termed Join and Redirect features, because these primitives often get used internally to affect these features.

Logical partitioning enhances Cisco Unified Communications Manager to handle such midcall scenarios. Configuration for logical partitioning remains independent of supplementary features, where the policy checking gets performed based on devices being joined or redirected to a supplementary feature.

5.81.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
Logical Partitioning Policysame1010000000Compare ok 

5.81.2 Comparison Results

No changes.

5.82 External Call Control Profile

Cisco Unified Communications Manager supports the external call control feature, which enables an adjunct route server to make call-routing decisions for Cisco Unified Communications Manager by using the Cisco Unified Routing Rules Interface. When you configure external call control, CUCM issues a route request that contains the calling party and called party information to the adjunct route server. The adjunct route server receives the request, applies appropriate business logic, and returns a route response that instructs Cisco Unified Communications Manager on how the call should get routed, along with any additional call treatment that should get applied.

The adjunct route server can instruct Cisco Unified Communications Manager to allow, divert, or deny the call, modify calling and called party information, play announcements to callers, reset call history so adjunct voicemail and IVR servers can properly interpret calling/called party information, and log reason codes that indicate why calls were diverted or denied.

5.82.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
External Call Control Profilesame1010000000Compare ok 

5.82.2 Comparison Results

No changes.

5.83 HTTP Profile

The Video Quality of Service (QoS) Reservation feature reserves bandwidth in a mobile network, through a third party HTTP service, when a mobile device makes a call. This reservation is only for VoIP calls made through Cisco Unified Communications Manager, not for other voice calls already classified by the mobile network as voice calls.

The following HTTP Profiles are defined:

5.83.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
HTTP Profilesame6060000000Compare ok 

5.83.2 Comparison Results

No changes.

5.84 CCD Hosted DN Group

Each hosted DN group covers one geophysical location advertising DN range.

Each hosted DN pattern must be unique. Each hosted DN pattern can only exist in one hosted DN group.

The following hosted DN groups are configured:

5.84.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
CCD Hosted DN Groupsame2020000000Compare ok 

5.84.2 Comparison Results

No changes.

5.85 CCD Hosted DN Pattern

Hosted DN patterns are directory number patterns that belong to the local call-control entity.

Hosted DN patterns are directory numbers pattern ranges for the local Cisco Unified Communications Manager cluster that you want to advertise to remote call-control entities. It is published by the CCD advertising service to the SAF forwarder.

The following Hosted DN patterns are configured:

5.85.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
CCD Hosted DN Patternsame1010000000Compare ok 

5.85.2 Comparison Results

No changes.

5.86 CCD Advertising Service

The Call control discovery (CCD) advertising service resides in Cisco Unified Communications Manager and advertises the PSTN failover configuration and hosted DN patterns along with the SAF trunk access information for the local Cisco Unified Communications Manager cluster to the remote call-control entities that use the SAF network.

You must enable SAF on the trunk in Cisco Unified Communications Manager Administration and assign SAF-enabled trunks to the CCD advertising and requesting services. You can configure as many CCD advertising services as you want. Only one hosted DN group can be associated with one CCD advertising service.

5.86.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
CCD Advertising Servicesame1010000000Compare ok 

5.86.2 Comparison Results

No changes.

5.87 CCD Partition

The call control discovery feature relies on a route partition, which are configured in this section. This route partition gets used exclusively by the call control discovery to ensure that all learned patterns get placed in digit analysis under the route partition. You assign this partition to the CCD requesting service.

If you want a user to make outbound calls to learned patterns that are advertised by remote call-control entities, ensure that the calling search space that you assign to the device contains the route partition that is assigned to the CCD requesting service.

5.87.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
CCD Partitionsame1010000000Compare ok 

5.87.2 Comparison Results

No changes.

5.88 CCD Requesting Service

Call control discovery (CCD) requesting service resides in Cisco Unified Communications Manager and allows the local Cisco Unified Communications Manager to listen for advertisements from remote call-control entities that use the SAF network.

Learned patterns (hosted DN patterns from remote call-control entities) get inserted into digit analysis on the local Cisco Unified Communications Manager. It performs load balancing for calls to learned patterns and handles withdrawals for Cisco Unified Communications Manager from the SAF network .

5.88.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
CCD Requesting Servicesame1010000000Compare ok 

5.88.2 Comparison Results

No changes.

5.89 Blocked Learned Pattern

The following learned patterns that remote call-control entities send to the local Cisco Unified Communications Manager are blocked:

5.89.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
Blocked Learned Patternsame2020000000Compare ok 

5.89.2 Comparison Results

No changes.

5.90 Advertised Patterns

Advertised patterns create summarized routing instructions for a range of enterprise alternate numbers or +E.164 alternate numbers and replicate that pattern throughout an ILS network such that all clusters within the ILS network know the pattern. Advertised patterns save you from having to configure routing information for each alternate number on an individual basis. Advertised patterns are never used by the local cluster on which they are configured. They are only used by remote clusters that learn the pattern through ILS.

5.90.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
Advertised Patternssame2020000000Compare ok 

5.90.2 Comparison Results

No changes.

5.91 Blocked Learned Numbers and Patterns

The Blocked Learned Pattern Configuration window supports the call control discovery feature by allowing you to purge and block learned patterns, for example, learned patterns that you no longer want to use. Any subsequent notifications with this information gets blocked and ignored.

To block or purge a pattern, the learned pattern must match all data that is configured.

5.91.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
Blocked Learned Numbers and Patternssame2020000000Compare ok 

5.91.2 Comparison Results

No changes.

5.92 Partitions for Learned Numbers and Patterns

Learned numbers and learned patterns must be assigned to a partition which cannot be the NULL partition. Define your own partitions or use the predefined default partitions. Cisco Unified Communications Manager comes installed with the following predefined partitions for learned alternate numbers and number patterns:

The following partitions are defined:

5.92.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
Partitions for Learned Numbers and Patternssame4040000000Compare ok 

5.92.2 Comparison Results

No changes.

5.93 Learned Numbers

Global dial plan data that Cisco Unified Communications Manager learns via ILS is stored in the local database. In addition to replicating locally configured data, ILS also replicates learned global dial plan data to the rest of the ILS network so that all data learned by one cluster is learned by all clusters in the ILS network.

The following numbers have been learned:

5.93.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
Learned Numberssame1010000000compare ok 

5.93.2 Comparison Results

5.94 Learned Patterns

Global dial plan data that Cisco Unified Communications Manager learns via ILS is stored in the local database. In addition to replicating locally configured data, ILS also replicates learned global dial plan data to the rest of the ILS network so that all data learned by one cluster is learned by all clusters in the ILS network.

The following patterns have been learned:

5.94.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
Learned Patternssame1010000000compare ok 

5.94.2 Comparison Results

5.95 Learned Directory URIs

Global dial plan data that Cisco Unified Communications Manager learns via ILS is stored in the local database. In addition to replicating locally configured data, ILS also replicates learned global dial plan data to the rest of the ILS network so that all data learned by one cluster is learned by all clusters in the ILS network.

The following Directory URIs have been learned:

5.95.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
Learned Directory URIssame1010000000compare ok 

5.95.2 Comparison Results

5.96 Imported Global Dial Plan Catalogs

Cisco Unified Communications Manager allows you to import global dial plan data from a CSV file into any hub cluster in an ILS network and ILS replicates the imported global dial plan data throughout the ILS network allowing you to interoperate Cisco Unified Communications Manager with a Cisco TelePresence Video Communications Server or a third-party call control system.

Imported data includes only global dial plan data that is imported manually into Cisco Unified Communications Manager. Imported global dial plan data does not include data that was learned through ILS.

The following global dial plan data has been imported:

5.96.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
Imported Global Dial Plan Catalogssame1010000000compare ok 

5.96.2 Comparison Results

5.97 Imported Directory URIs

Cisco Unified Communications Manager allows you to import Directory URIs from a CSV file into any hub cluster in an ILS network and ILS replicates the imported data throughout the ILS network allowing you to interoperate Cisco Unified Communications Manager with a Cisco TelePresence Video Communications Server or a third-party call control system.

Imported data includes only data that is imported manually into Cisco Unified Communications Manager. Imported data does not include data that was learned through ILS.

The following Directory URIs have been imported:

5.97.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
Imported Directory URIssame1010000000compare ok 

5.97.2 Comparison Results

5.98 Imported Patterns

Cisco Unified Communications Manager allows you to import patterns from a CSV file into any hub cluster in an ILS network and ILS replicates the imported data throughout the ILS network allowing you to interoperate Cisco Unified Communications Manager with a Cisco TelePresence Video Communications Server or a third-party call control system.

Imported data includes only data that is imported manually into Cisco Unified Communications Manager. Imported data does not include data that was learned through ILS.

The following patterns have been imported:

5.98.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
Imported Patternssame1010000000compare ok 

5.98.2 Comparison Results

5.99 Annunciator

An annunciator, an SCCP device that uses the Cisco Media Streaming Application service, enables Cisco Unified Communications Manager to play prerecorded announcements (.wav files) and tones to Cisco Unified IP Phones and gateways. The annunciator, which works with Cisco Multilevel Precedence and Preemption (MLPP), enables Cisco Unified Communications Manager to alert callers as to why the call fails. Annunciator can also play tones for some transferred calls and some conferences.

5.99.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
Annunciatorsame3030000000Compare ok 

5.99.2 Comparison Results

No changes.

5.100 Conference Bridge

A conference bridge is a resource that joins multiple participants into a single call. It can accept any number of connections for a given conference, up to the maximum number of streams allowed for a single conference on that device. There is a one-to-one correspondence between media streams connected to a conference and participants connected to the conference. The conference bridge mixes the streams together and creates a unique output stream for each connected party. The output stream for a given party is the composite of the streams from all connected parties minus their own input stream. Some conference bridges mix only the three loudest talkers on the conference and distribute that composite stream to each participant (minus their own input stream if they are one of the talkers).

Software conference bridges automatically get added when a Cisco Unified Communications Manager server gets added. You can update software conference bridges, but you cannot delete them.

A hardware conference bridge has all the capabilities of a software conference bridge. In addition, some hardware conference bridges can support multiple low bit-rate (LBR) stream types such as G.729, GSM, or G.723. This capability enables some hardware conference bridges to handle mixed-mode conferences. In a mixed-mode conference, the hardware conference bridge transcodes G.729, GSM, and G.723 streams into G.711 streams, mixes them, and then encodes the resulting stream into the appropriate stream type for transmission back to the user. Some hardware conference bridges support only G.711 conferences.

All conference bridges that are under the control of Cisco Unified Communications Manager (CUCM) use Skinny Client Control Protocol (SCCP) to communicate with Cisco Unified Communications Manager (CUCM). Cisco Unified Communications Manager (CUCM) allocates a conference bridge from a conferencing resource that is registered with the Cisco Unified Communications Manager (CUCM) cluster. Both hardware and software conferencing resources can register with Cisco Unified Communications Manager (CUCM) at the same time, and Cisco Unified Communications Manager (CUCM) can allocate and use conference bridges from either resource. Cisco Unified Communications Manager (CUCM) does not distinguish between these types of conference bridges when it processes a conference allocation request.

5.100.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
Conference Bridgesame3030000000Compare ok 

5.100.2 Comparison Results

No changes.

5.101 Media Termination Point

A Media Termination Point software device allows Cisco Unified Communications Manager to relay calls that are routed through SIP or H.323 endpoints or gateways. You can allocate a media termination point device because of DTMF or RSVP requirements. When a media termination point is allocated for RSVP, you can insert it between any type of endpoint device, including SIP or H.323 devices.

Media termination point, a Cisco software application, installs on a server during the software installation process. You must activate and start the Cisco IP Voice Media Streaming App service on the server on which you configure the media termination point device.

5.101.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
Media Termination Pointsame3030000000Compare ok 

5.101.2 Comparison Results

No changes.

5.102 MoH Sources

The integrated Music On Hold (MOH) feature allows users to place on-net and off-net users on hold with music that is streamed from a streaming source. The Music On Hold feature allows two types of hold:

Music On Hold also supports other scenarios where recorded or live audio is needed.

5.102.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
MoH Sourcessame3030000000Compare ok 

5.102.2 Comparison Results

No changes.

5.103 MoH Servers

The music on hold server uses the Station Stimulus (Skinny Client) messaging protocol for communication with Cisco Unified Communications Manager. A music on hold server registers with the Cisco Unified Communications Manager as a single device and reports the number of simplex, unicast audio streams that it can support. The music on hold server advertises its media type capabilities to the Cisco Unified Communications Manager as G.711 mu-law and a-law, G.729a, and wideband. Cisco Unified Communications Manager starts and stops music on hold unicast streams by sending skinny client messages to the music on hold server.

A music on hold server handles up to 500 simplex, unicast audio streams. A media resource group includes one or more music on hold servers. A music on hold server supports 51 audio sources, with one audio source that is sourced from a fixed device that uses the local computer audio driver, and the rest that are sourced from files on the local music on hold server.

5.103.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
MoH Serverssame3030000000Compare ok 

5.103.2 Comparison Results

No changes.

5.104 VoH Servers

The Video on Hold feature is for video contact centres where customers calling into the video contact centre are able to watch a specific video after initial consultation with the agent at the contact centre. In this case, the agent selects the video stream that gets played to the customer while the customer is on hold.

The media content server is an external device that can store and stream audio and video content under Unified Communications Manager control using SIP as the signal protocol.

5.104.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
VoH Serverssame2020000000Compare ok 

5.104.2 Comparison Results

No changes.

5.105 Transcoder

The Cisco Unified Communications Manager invokes a transcoder on behalf of endpoint devices when the two devices are using different codecs and would normally not be able to communicate. When inserted into a call, the transcoder converts the data streams between the two disparate codecs to enable communications between them.

The Media Resource Manager (MRM) has responsibility for resource registration and resource reservation of transcoders within a Cisco Unified Communications Manager cluster. Cisco Unified Communications Manager simultaneously supports registration of both the Media Termination Point (MTP) and transcoder and concurrent MTP and transcoder functionality within a single call.

5.105.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
Transcodersame3030000000Compare ok 

5.105.2 Comparison Results

No changes.

5.106 Media Resource Groups and Lists

Media resource group lists specify a list of prioritized media resource groups. An application can select required media resources from among the available resources according to the priority order that is defined in the media resource group list. Media resource group lists, which are associated with devices, provide media resource group redundancy.

Media resource groups define logical groupings of media servers. You can associate a media resource group with a geographical location or a site as desired. You can also form media resource groups to control the usage of servers or the type of service (unicast or multicast) that is desired.

5.106.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
Media Resource Groups and Listssame1010000000Compare ok 

5.106.2 Comparison Results

No changes.

5.107 Mobile Voice Access

Mobile Connect allows users to manage business calls using a single phone number and pick up in-progress calls on the desktop phone and cellular phone. Mobile Voice Access is the associated integrated voice response (IVR) system, which allows users to turn Mobile Connect on or off and to initiate calls from a cellular phone or other remote phone as if the call were initiated from the desktop phone.

The Mobile Voice Access window contains settings for localized user IVR prompts.

5.107.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
Mobile Voice Accesssame1010000000Compare ok 

5.107.2 Comparison Results

No changes.

5.108 Announcements

When you install Cisco Unified Communications Manager, Cisco-provided announcements and tones install, and the Find and Lists Announcements window in Cisco Unified Communications Manager Administration displays these announcements and tones, which can be used for basic calls, external call control, or MLPP, depending on the announcement. Cisco Unified Communications Manager allows you to use the Cisco-provided announcements as is, insert customized announcement .wav files, assign a locale for the announcement, change the description for the announcement, or change the message or tone that you want an announcement to play.

The following announcements and tones are installed:

5.108.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
Announcementssame130130000000Compare ok 

5.108.2 Comparison Results

No changes.

5.109 Cisco Voice Mail Port

The optional Cisco Unity (Connection) software, available as part of Cisco Unified Communications Solutions, provides voice-messaging capability for users when they are unavailable to answer calls.

This section contains the Cisco Unity voice-mail ports which are setup as virtual phones for the Cisco for the Cisco Unity (Connection) server.

5.109.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
Cisco Voice Mail Portsame2020000000Compare ok 

5.109.2 Comparison Results

No changes.

5.110 Message Waiting

The Message Waiting Configuration defines a message waiting on or message waiting off directory number that a directory-connected based voice-messaging system uses to determine whether to set or clear a message waiting indication for a particular Cisco Unified IP Phone.

5.110.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 Waitingsame2020000000Compare ok 

5.110.2 Comparison Results

No changes.

5.111 MWI On

On the following devices the Message Waiting lamp is switched on:

5.111.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
MWI Onsame1010000000compare ok 

5.111.2 Comparison Results

5.112 Voice Mail Profile and Pilot

Voicemail profiles contain the Pilot extension and MWI settings for any voicemail system and are assigned to phone extensions. The pilot extension is used to forward a call to the voicemail system and can be an individual extension or the pilot point of a hunt-list which contains voicemail extensions.

5.112.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
Voice Mail Profile and Pilotsame7070000000Compare ok 

5.112.2 Comparison Results

No changes.

5.113 SAF Security Profile

In the SAF Security Profile Configuration window, you configure a SAF security profile so that a secure connection occurs between the SAF forwarder and the Cisco Unified Communications Manager. When you configure a SAF forwarder in the SAF Forwarder Configuration window, you must choose a SAF security profile to apply to the SAF forwarder.

Cisco Unified Communications Manager uses digest authentication (SHA1) to communicate with the SAF forwarder.

The call control discovery feature leverages the Service Advertisement Framework (SAF) network service, a proprietary Cisco service, to facilitate dynamic provisioning of inter-call agent information.

5.113.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
SAF Security Profilesame2020000000Compare ok 

5.113.2 Comparison Results

No changes.

5.114 SAF Forwarder

A SAF forwarder, a Cisco router that you configure for call control discovery/SAF, handles the publishing requests from Cisco Unified Communications Manager for the call control discovery feature. In addition, the SAF forwarder handles advertising requests from remote call-control entities for the call control discovery feature.

5.114.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
SAF Forwardersame2020000000Compare ok 

5.114.2 Comparison Results

No changes.

5.115 EMCC Feature Configuration

The following table contains all EMCC feature parameters:

5.115.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
EMCC Feature Configurationsame130130000000Compare ok 

5.115.2 Comparison Results

No changes.

5.116 EMCC Intercluster Service Profile

EMCC intercluster service profile allows to activate the Cisco Extension Mobility Cross Cluster feature, to activate PSTN access and assign a SIP trunk to it, to activate the RSVP agent and assign a SIP trunk to it.

5.116.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
EMCC Intercluster Service Profilesame3030000000Compare ok 

5.116.2 Comparison Results

No changes.

5.117 Cluster View

This section defines the EMCC Remote Clusters. EMCC Remote Clusters are used to allow users from this home cluster to roam to the remote cluster as visitors and login with Extension Mobility.

Cluster ID: Ensure that this cluster ID matches the enterprise parameter value of the cluster ID of the other cluster(s).

Fully Qualified Name: Use the IP address of the remote cluster or a domain name that can resolve to any node on the remote cluster.

5.117.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 Viewsame2020000000Compare ok 

5.117.2 Comparison Results

No changes.

5.118 Server Connection

Use the Intercompany Media Engine Server Connection Configuration window to specify information about the Cisco Intercompany Media Engine (Cisco IME) server to which Cisco Unified Communications Manager connects.

This information nables Cisco Unified Communications Manager to connect to the Cisco IME server to initiate VAP messaging. The interface between servers allows Cisco Unified Communications Manager to publish its configured direct inward dialing (DID) patterns and to learn new routes.

After Cisco Unified Communications Manager establishes a connection, CUCM sends a VAP Register message to the Cisco IME server. This message contains the username that associates with the application user that the Application User field specifies. The Cisco IME server checks the credentials against the configured VAP username and password

5.118.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
Server Connectionsame1010000000Compare ok 

5.118.2 Comparison Results

No changes.

5.119 Enrolled Group

You specify the numbers that you want to participate in Cisco Intercompany Media Engine (Cisco IME) by creating enrolled groups and patterns. Enrolled groups are a collection of enrolled patterns. These patterns define the set of +E.164 numbers that make and receive Cisco IME calls. Cisco IME publishes these numbers to the IME distributed cache. By doing so, Cisco IME makes these numbers available for other enterprises to learn through Cisco IME. Numbers within your enterprise must also match a pattern in an enrolled group in order to make Cisco IME calls. You can create an enrolled group for each of your campuses or sites to facilitate incremental deployment of Cisco IME, starting with certain sites or campuses and extending the deployment as usage grows.

After you create the enrolled group, you create the enrolled patterns, assign the patterns to a group, and associate the group with a Cisco IME service. If you want to disable Cisco IME for certain phones in the enterprise, you can unassign the enrolled group for those phones from the Cisco IME service.

5.119.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
Enrolled Groupsame1010000000Compare ok 

5.119.2 Comparison Results

No changes.

5.120 Enrolled Pattern

Cisco Intercompany Media Engine (Cisco IME) enrolled patterns define the set of +E.164 numbers that make and receive Cisco IME calls. Cisco IME publishes these numbers to the IME distributed cache. By doing so, Cisco IME makes these numbers available for other enterprises to learn through Cisco IME. The patterns must specify valid direct inward dialing numbers (DIDs) that the enterprise owns. Numbers within your enterprise must match a pattern that is found in an enrolled group in order to make Cisco IME calls.

To eliminate the need for day-to-day provisioning of specific numbers as individual phones are added to and removed from the system, you can add a pattern that represents a large group of numbers for a given site. The enrolled pattern can include numbers that you have not assigned to a phone. Numbers that are not associated to a phone cannot be validated.

After you create enrolled patterns, you associate them to an enrolled group and assign the enrolled group to a Cisco Intercompany Media Engine service. You can disable or enable Cisco IME from calling certain phones in the enterprise by disassociating or associating the enrolled group to the Cisco IME service.

5.120.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
Enrolled Patternsame2020000000Compare ok 

5.120.2 Comparison Results

No changes.

5.121 Exclusion Group

Exclusion groups contain a list of numbers that you want to prevent from using Cisco Intercompany Media Engine (Cisco IME), including numbers of analog devices and fax machines. You create the exclusion group first and then you create exclusion numbers that you associate with a particular exclusion group. Then, you associate the exclusion group to the Cisco IME service.

5.121.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
Exclusion Groupsame2020000000Compare ok 

5.121.2 Comparison Results

No changes.

5.122 Exclusion Number

Use the Intercompany Media Services Exclusion Number Configuration window to define numbers, sets of numbers, prefixes, or set of prefixes that you do not want to use Cisco Intercompany Media Engine (Cisco IME), even if these numbers occur within a list of numbers that is included in the Cisco IME enrolled pattern.

5.122.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
Exclusion Numbersame1010000000Compare ok 

5.122.2 Comparison Results

No changes.

5.123 Trust Group

Cisco Intercompany Media Engine (Cisco IME) trust groups contain a list of domains and prefixes that are trusted (or not trusted) by the Cisco IME service that associates with the trust group. Cisco Unified Communications Manager can only place Cisco IME calls to domains or prefixes that are trusted.

Configuration of trust groups is optional. If you do not create trust groups, Cisco IME trusts all calls by default.

5.123.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
Trust Groupsame2020000000Compare ok 

5.123.2 Comparison Results

No changes.

5.124 Trust Element

Cisco Intercompany Media Engine (Cisco IME) trust elements specify prefixes or domain that you want to trust or not trust. You include the trust elements in a trust group. Cisco Unified Communications Manager can only place Cisco IME calls to domains or prefixes that are trusted. You cannot receive Cisco IME calls from a number whose prefix or domain is specified in an untrusted element.

This section describes how to create trust elements and how to associate the trust elements with a trust group. After you create the trust elements, you associate trust groups with an Cisco IME service to trust or not trust the prefixes or domains that the trust group specifies.

5.124.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
Trust Elementsame2020000000Compare ok 

5.124.2 Comparison Results

No changes.

5.125 Service

Use the Intercompany Media Service Configuration window to configure and activate the Cisco Intercompany Media Engine (Cisco IME) service. To configure the Cisco IME service in Cisco Unified Communications Manager Administration, you associate various components that you have already configured, including trusted groups, enrolled groups, and exclusion groups. You indicate the Cisco IME server with which you want Cisco Unified Communications Manager to communicate. Communications between the Cisco Unified Communications Manager and the Cisco IME servers begin after you configure and activate the Cisco IME service.

To begin load balancing so that the system work spreads across multiple Cisco Intercompany Media Engine servers, create more than one Cisco Intercompany Media Engine service with different Cisco Intercompany Media Engine servers and move some of the enrolled groups from the old Cisco Intercompany Media Engine service to the new service.

5.125.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
Servicesame2020000000Compare ok 

5.125.2 Comparison Results

No changes.

5.126 E.164 Transformation

Cisco Intercompany Media Engine (Cisco IME) E.164 transformations convert calling numbers and called numbers on both the originating and terminating (incoming and outgoing) sides to +E.164 format after a PSTN call terminates. Cisco IME E.164 transformations do not impact call routing or digit analysis in Cisco Unified Communications Manager. The transformations allow the following actions to occur:

You associate Cisco IME E.164 transformations with a PSTN access trunk. If the transformation does not yield valid calling and called numbers on the incoming and outgoing sides of the call, no VCR upload takes place, and Cisco IME processing stops for that call.

5.126.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
E.164 Transformationsame2020000000Compare ok 

5.126.2 Comparison Results

No changes.

5.127 Learned Route

The following is a list of the Intercompany Media Services learned routes:

5.127.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
Learned Routesame1010000000compare ok 

5.127.2 Comparison Results

5.128 Firewall

Use the Intercompany Media Services Firewall Configuration window to configure the IP address and port of the ASA mapping service. You need to configure this information if you have implemented an off-path deployment model in which normal Internet-facing traffic does not flow through the same adaptive security appliance (ASA) as the Cisco Intercompany Media Engine (Cisco IME) traffic.

During an outbound call attempt, the SIP invite message must be routed to the offpath Cisco IME enabled ASA. Cisco Unified Communications Manager sends a request to the ASA for a mapping of the global IP/port of the remote enterprise (found in the Cisco IME learned route) to an internal IP/port on the Cisco IME enabled ASA. Cisco Unified Communications Manager then initiates a SIP Invite that routes to this internal IP/port. The Cisco IME enabled ASA performs NAT, mapping to the global IP/port of the remote enterprise from the IME learned route. The offpath Cisco IME enabled ASA proxies this signaling session and initiates a TLS session to this global IP/port (the Cisco IME enabled ASA of the remote enterprise).

5.128.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
Firewallsame2020000000Compare ok 

5.128.2 Comparison Results

No changes.

5.129 Intercompany Media Services Feature Configuration

The following values are configured for the Intercompany Media Services feature parameters.

5.129.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
Intercompany Media Services Feature Configurationsame110110000000Compare ok 

5.129.2 Comparison Results

No changes.

5.130 Fallback Profile

The fallback profile defines several values that the Cisco Unified Communications Manager uses to fallback Cisco Intercompany Media Engine (Cisco IME) calls to the PSTN. The fallback profile defines the quality of service level at which Cisco Unified Communications Manager attempts a mid-call fallback as well as the fallback number that the Cisco Unified Communications Manager uses to invoke the PSTN call.

When a user makes a call to a number that is linked to a fallback profile, the Cisco Unified Communications Manager of the calling party receives a fallback directory number that is configured on the Cisco Unified Communications Manager of the called party. The Cisco Unified Communications Manager uses the fallback number for the PSTN call when the ASA triggers a fallback to the PSTN.

5.130.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
Fallback Profilesame3030000000Compare ok 

5.130.2 Comparison Results

No changes.

5.131 Fallback Feature Configuration

The following Fallback feature parameters apply to mid-call fallback of Cisco Intercompany Media Engine:

5.131.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
Fallback Feature Configurationsame100100000000Compare ok 

5.131.2 Comparison Results

No changes.

5.132 VPN Profile

The VPN Profile settings are assigned to the Cisco Unified IP Phone by using the Common Phone Profile Configuration window.

5.132.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
VPN Profilesame1010000000compare ok 

5.132.2 Comparison Results

5.133 VPN Group

A VPN Group contains VPN gateways which are used to create the VPN connection.

You can add up to a maximum of three VPN gateways to a VPN group. The total number of certificates in the VPN group cannot exceed 10.

5.133.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
VPN Groupsame1010000000compare ok 

5.133.2 Comparison Results

5.134 VPN Gateway

The following VPN gateways (Cisco Adaptive Security Appliance (ASA)) are configured on CUCM.

The VPN Gateway URL is the URL for the main VPN concentrator in the gateway. Note : You must configure the VPN concentrator with a group-URL and use this URL as the gateway URL.

You can assign up to 10 certificates to a VPN Gateway, and you must assign at least one certificate to each gateway. Only certificates that are associated with the Phone-VPN-trust role display in the available VPN certificates list. To configure a VPN gateway, you must first upload the VPN concentrator certificates and then configure the VPN gateway.

5.134.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
VPN Gatewaysame1010000000compare ok 

5.134.2 Comparison Results

5.135 VPN Feature Configuration

VPN Feature Configuration contains default settings for the VPN feature that are used when a VPN Profile is not associated Common Phone Profile. If a VPN Profile is associated with a Common Phone Profile, the VPN Feature Configuration settings will not be used.

5.135.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
VPN Feature Configurationsame6060000000Compare ok 

5.135.2 Comparison Results

No changes.

5.136 Called Party Tracing List

Called Party Tracing allows you to configure a directory number or list of directory numbers that you want to trace. You can request on-demand tracing of calls using the Session Trace Tool.

5.136.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
Called Party Tracing Listsame3030000000Compare ok 

5.136.2 Comparison Results

No changes.

5.137 ILS Configuration

When the Intercluster Lookup Service (ILS) is configured on multiple Unified CM clusters, ILS updates Cisco Unified Communications Manager with the current status of remote clusters in the ILS network. The ILS cluster discovery service allows Cisco Unified Communications Manager to learn about remote clusters without the need for an administrator to manually configure connections between each cluster.

The ILS URI Replication feature enables ILS to exchange directory URI catalogs with the other clusters in an ILS network. URI Replication provides support for intercluster URI dialing.

Although ILS is activated and runs on individual cluster nodes, the configuration settings are applied on a cluster-wide basis. After ILS is configured on a cluster node, those settings are propagated out to the other cluster nodes. The length of time that it takes for ILS settings to be propagated to other cluster nodes depends on the synchronization value that you enter.

5.137.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
ILS Configurationsame0000050500Compare ok 

5.137.2 Comparison Results

No changes.

5.138 Call Control Agent Profile

When you associate a Call Control Agent (CCA) profile to a directory number and if ESN and E164 masks are configured on that directory number, then the directory number will be synchronized to the corresponding fields in the external LDAP server that you have configured.

5.138.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 Control Agent Profilesame2020000000Compare ok 

5.138.2 Comparison Results

No changes.

5.139 Directory Number Alias Lookup And Sync

The Directory Number Alias Lookup and Sync setup enables you to route the commercial calls to an alternate number. Routing the commercial calls to an alternate number reduces the commercial cost of calling an external number. You must configure the LDAP server for Directory Number Alias Sync (sync server) if you need to synchronize users from Cisco Unified Communications Manager database to the sync server. You must configure the LDAP server for Directory Number Alias Lookup (lookup server) if you need to route the commercial calls to an alternate number.

5.139.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 Number Alias Lookup And Syncsame1010000000compare ok 

5.139.2 Comparison Results

5.140 CTI Route Point

A CTI route point virtual device can receive multiple, simultaneous calls for application-controlled redirection. You can configure one or more lines on a CTI route point that users can call to access the application. Applications can answer calls at a route point and can also be redirected to a CTI port or IP phone.


5.140.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
CTI Route Pointsame8080000000Compare ok 

5.140.2 Comparison Results

No changes.

5.141 Gatekeeper

An endpoint gatekeeper is configured to manage all RAS procedures for calls to, from, and between H.323 clients, MCUs, and H.320 video gateways. The endpoint gatekeeper directs all such calls to the appropriate Cisco Unified Communications Manager (CUCM) cluster so that Cisco Unified Communications Manager (CUCM) can perform all of the H.225 call routing and H.245 media negotiations.

An infrastructure gatekeeper is configured to manage all dial plan resolution and bandwidth restrictions (call admission control) between Cisco Unified Communications Manager (CUCM) clusters, between a Cisco Unified Communications Manager (CUCM) cluster and a network of H.323 VoIP gateways, or between a Cisco Unified Communications Manager (CUCM) cluster and a service provider's H.323 VoIP transport network.


5.141.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
Gatekeepersame2020000000Compare ok 

5.141.2 Comparison Results

No changes.

5.142 Gateway Overview

Cisco Unified Communications Manager (CUCM) supports several types of voice gateways.

The following gateway devices are present:

5.142.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
Gateway Overviewsame110110000000Compare ok 

5.142.2 Comparison Results

No changes.

5.143 MGCP Gateway

Cisco IP telephony gateways enable Cisco Unified Communications Manager (CUCM) to communicate with non-IP telecommunications devices.

MGCP gateways provide full support for the hold, transfer, and conference features through the MGCP protocol. Because MGCP is a master/slave protocol with Cisco Unified Communications Manager (CUCM) controlling all session intelligence, Cisco Unified Communications Manager (CUCM) can easily manipulate MGCP gateway voice connections.

5.143.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
MGCP Gatewaysame7070000000Compare ok 

5.143.2 Comparison Results

No changes.

5.144 MGCP Gateway Endpoints

MGCP Gateway Endpoints are the line interfaces of the MGCP gateways.

This section is linked to the previous section MGCP gateway. The gateway, module and slot configurations are documented there.

5.144.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
MGCP Gateway Endpointssame4040000000Compare ok 

5.144.2 Comparison Results

No changes.

5.145 H.323 Gateway

Cisco IP telephony gateways enable Cisco Unified Communications Manager (CUCM) to communicate with non-IP telecommunications devices.

Cisco IOS H.323 gateways must be configured by using the Cisco IOS command-line interface (CLI). Compared to MGCP gateways, H.323 gateways maintain the dial plan and route pattern and can perform number translations autonomously.

5.145.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
H.323 Gatewaysame1010000000compare ok 

5.145.2 Comparison Results

5.146 Analog Gateway

Cisco IP telephony gateways enable Cisco Unified Communications Manager (CUCM) to communicate with non-IP telecommunications devices.

The Cisco Analog Phone Gateways allow on-premise analog telephones, fax machines, modems, voice-messaging systems, and speakerphones to register with one Cisco Unified Communications Manager (CUCM) cluster.


5.146.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
Analog Gatewaysame110110000000Compare ok 

5.146.2 Comparison Results

No changes.

5.147 Phone Filter

This report has been generated with the following filter applied.If there is a filter configured, not all objects may be be listed.

5.147.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 Filtersame0000010100Compare ok 

5.147.2 Comparison Results

No changes.

5.148 CTI Port (5)

5.148.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
CTI Port (5)same5050000000Compare ok 

5.148.2 Comparison Results

No changes.

5.149 Cisco 7821 (1)

5.149.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
Cisco 7821 (1)same1010000000Compare ok 

5.149.2 Comparison Results

No changes.

5.150 Cisco 7861 (1)

5.150.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
Cisco 7861 (1)same1010000000Compare ok 

5.150.2 Comparison Results

No changes.

5.151 Cisco 7945 (1)

5.151.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
Cisco 7945 (1)notsame110001211100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
715/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 7: Updated record 'SEP0021A02E05E0' Cisco 7945 (1) 
815/09/2015 2:08:29 PM15/09/2015 4:08:29 AMDetectedChange 8: Updated field '::Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08Change 7Cisco 7945 (1) 

5.151.2 Comparison Results

Cisco 7945
PhoneBase settingsLines
SEP0021A02E05E0
Detected Change ID7
Detected ChangeUpdated record 'SEP0021A02E05E0'
Detected ObjectCisco 7945 (1)
Detected Date (UTC)15/09/2015 4:08:29 AM
Detected Date (Local)15/09/2015 2:08:29 PM
Child ID8
ModelCisco 7945
DescriptionPhone of Bruce Wayne Updated at 17:36
Phone of Bruce Wayne Updated at 14:08
Detected Change ID8
Detected ChangeUpdated field '::Description' from Phone of Bruce Wayne Updated at 17:36 to Phone of Bruce Wayne Updated at 14:08
Detected ObjectCisco 7945 (1)
Detected Date (UTC)15/09/2015 4:08:29 AM
Detected Date (Local)15/09/2015 2:08:29 PM
Parent ID7
ProtocolSCCP
Device PoolDP_Sydney
CSS< None >
MRGL< None >
LocationHub_None
AAR Group
Button Template7945 SCCP - with SURL
Softkey Template< None >
Owner User IDbwayne
# Extension Partition CSS Linetext Alerting Name External Mask Pickup Grp max/busy VM Profile CF All CF Busy CF NoAnswer CFNA [secs]
Line 1 5012 P_Sydney_2 CSS_Sydney   Bruce Wayne 0290005XXX   4/2 < None > / < None > / < None > / < None >  

5.152 Cisco 7975 (1)

5.152.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
Cisco 7975 (1)same1010000000Compare ok 

5.152.2 Comparison Results

No changes.

5.153 Cisco 8841 (2)

5.153.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
Cisco 8841 (2)same2020000000Compare ok 

5.153.2 Comparison Results

No changes.

5.154 Cisco 8851 (1)

5.154.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
Cisco 8851 (1)same1010000000Compare ok 

5.154.2 Comparison Results

No changes.

5.155 Cisco 9951 (1)

5.155.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
Cisco 9951 (1)same1010000000Compare ok 

5.155.2 Comparison Results

No changes.

5.156 Cisco DX650 (1)

5.156.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
Cisco DX650 (1)same1010000000Compare ok 

5.156.2 Comparison Results

No changes.

5.157 Cisco Dual Mode for iPhone (1)

5.157.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
Cisco Dual Mode for iPhone (1)same1010000000Compare ok 

5.157.2 Comparison Results

No changes.

5.158 Cisco IP Communicator (1)

5.158.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
Cisco IP Communicator (1)same1010000000Compare ok 

5.158.2 Comparison Results

No changes.

5.159 Cisco TelePresence 1000 (1)

5.159.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
Cisco TelePresence 1000 (1)same1010000000Compare ok 

5.159.2 Comparison Results

No changes.

5.160 Universal Device Template (2)

5.160.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
Universal Device Template (2)same2020000000Compare ok 

5.160.2 Comparison Results

No changes.

5.161 Subscribed Services

The following table lists the subscribed IP services and parameters for each phone:

5.161.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
Subscribed Servicessame7070000000Compare ok 

5.161.2 Comparison Results

No changes.

5.162 Speed Dials

The following Speed Dials are configured per phone:


5.162.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
Speed Dialssame2020000000Compare ok 

5.162.2 Comparison Results

No changes.

5.163 Busy Lamp Field Speed Dials

The following Busy Lamp Field Speed Dials are configured per phone:

5.163.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
Busy Lamp Field Speed Dialssame3030000000Compare ok 

5.163.2 Comparison Results

No changes.

5.164 Busy Lamp Field Directed Call Parks

The following Busy Lamp Field Directed Call Parks are configured per phone:

5.164.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
Busy Lamp Field Directed Call Parkssame1010000000compare ok 

5.164.2 Comparison Results

5.165 Trunk - Overview

The following is an overview of the configured trunks on this system.

Click on the name (leftmost column in the overview) for detailed information.

5.165.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
Trunk - Overviewsame100100000000Compare ok 

5.165.2 Comparison Results

No changes.

5.166 Trunk - Detailed

A trunk device configures a logical route to a gatekeeper (that is, the wholesale network or an intercluster trunk with gatekeeper control), to an intercluster trunk without a gatekeeper, or to a SIP network. The following trunk types are available:

5.166.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
Trunk - Detailedsame100100000000Compare ok 

5.166.2 Comparison Results

No changes.

5.167 Remote Destination

Remote destinations represent the cellular (or other phones) that are able to accept transfers from the user's desktop phone and can be used to initiate calls using Mobile Voice Access.

5.167.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
Remote Destinationsame3030000000Compare ok 

5.167.2 Comparison Results

No changes.

5.168 Device Defaults

Device defaults set the default characteristics of each type of device that registers with a Cisco Unified Communications Manager (CUCM). The device defaults for a device type apply to all auto-registered devices of that type within a Cisco Unified Communications Manager (CUCM) cluster.

When a device auto-registers with a Cisco Unified Communications Manager (CUCM), it acquires the device default settings for its device type. After a device registers, you can update its configuration individually to change the device settings.

5.168.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
Device Defaultssame17701770000000Compare ok 

5.168.2 Comparison Results

No changes.

5.169 Firmware Load Information

The Firmware Load Information in Cisco Unified Communications Manager locates devices that are not using the default firmware load for their device type.

Each device can have an individually assigned firmware load that overrides the default.

5.169.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
Firmware Load Informationsame15001500000000Compare ok 

5.169.2 Comparison Results

No changes.

5.170 Default Device Profile

Use the default device profile for whenever a user logs on to a phone model for which no user device profile exists. To create a default device profile for each phone model that supports Cisco Extension Mobility, use the Default Device Profile Configuration window. The maximum number of default device profiles cannot exceed the number of phone models that support Cisco Extension Mobility.

For example, a user logs on to a Cisco Unified IP Phone 7960, for which there is a user device profile. The user device profile for the user gets downloaded to the phone to which the user logged on. Later, the same user logs on to a Cisco Unified IP Phone 7940, for which he does not have a user device profile. In this case, the default device profile for the 7940 gets downloaded to the phone.

A default device profile comprises the set of attributes (services and/or features) that are associated with a particular device. Device profiles include device type, user locale, phone button template, softkey template, multilevel precedence and preemption (MLPP) information, and IP phone services.

5.170.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
Default Device Profilesame220220000000Compare ok 

5.170.2 Comparison Results

No changes.

5.171 Device Profile Filter

This report has been generated with the following filter applied.If there is a filter configured, not all objects may be be listed.


5.171.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
Device Profile Filtersame0000010100Compare ok 

5.171.2 Comparison Results

No changes.

5.172 Cisco 6921 (1)

5.172.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
Cisco 6921 (1)same1010000000Compare ok 

5.172.2 Comparison Results

No changes.

5.173 Cisco 7945 (4)

5.173.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
Cisco 7945 (4)same4040000000Compare ok 

5.173.2 Comparison Results

No changes.

5.174 Cisco 7975 (4)

5.174.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
Cisco 7975 (4)same4040000000Compare ok 

5.174.2 Comparison Results

No changes.

5.175 Cisco 8851 (2)

5.175.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
Cisco 8851 (2)same2020000000Compare ok 

5.175.2 Comparison Results

No changes.

5.176 Subscribed Services

The following table lists the subscribed IP services and parameters for each Device Profile:

5.176.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
Subscribed Servicessame4040000000Compare ok 

5.176.2 Comparison Results

No changes.

5.177 Speed Dials

The following Speed Dials are configured per Device Profile:


5.177.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
Speed Dialssame1010000000compare ok 

5.177.2 Comparison Results

5.178 Busy Lamp Field Speed Dials

The following Busy Lamp Field Speed Dials are configured per Device Profile:

5.178.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
Busy Lamp Field Speed Dialssame1010000000compare ok 

5.178.2 Comparison Results

5.179 Busy Lamp Field Directed Call Parks

The following Busy Lamp Field Directed Call Parks are configured per Device Profile:

5.179.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
Busy Lamp Field Directed Call Parkssame1010000000compare ok 

5.179.2 Comparison Results

5.180 Phone Button Template

Cisco Unified Communications Manager (CUCM) includes several default phone button templates. When adding phones, you can assign one of these templates to the phones or create a new template.

Creating and using templates provides a fast way to assign a common button configuration to a large number of phones. For example, if users in your company do not use the conference feature, you can create a template that reassigns this button to a different feature, such as speed dial.

5.180.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 Button Templatesame16701670000000Compare ok 

5.180.2 Comparison Results

No changes.

5.181 Softkey Template

Softkey templates include softkey settings that are associated with applications such as Cisco Unified Communications Manager (CUCM) Assistant or call-processing features such as Cisco Call Back on the Cisco Unified IP Phones.

Cisco Unified Communications Manager (CUCM) supports two types of softkey templates: standard and nonstandard. Standard softkey templates in the Cisco Unified Communications Manager (CUCM) database contain the recommended selection and positioning of the softkeys for an application.

5.181.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
Softkey Templatesame8080000000Compare ok 

5.181.2 Comparison Results

No changes.

5.182 Phone Services

Cisco Unified IP Phone Services comprise XML applications that enable the display of interactive content with text and graphics on Cisco Unified IP Phones.

IP Phone Services are either statically assigned by the administrator to phones or device profiles or users can subscribe to IP Phone Services on the CCM user pages.

5.182.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 Servicessame160160000000Compare ok 

5.182.2 Comparison Results

No changes.

5.183 SIP Profile

A SIP profile comprises the set of SIP attributes that are associated with SIP trunks and SIP endpoints. SIP profiles include information such as name, description, timing, retry, call pickup URI, and so on. The profiles contain some standard entries that cannot be deleted or changed.

5.183.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 Profilesame5050000000Compare ok 

5.183.2 Comparison Results

No changes.

5.184 Common Device Configuration

A common device configuration comprises user-specific service and feature attributes. Ensure that each device is associated with a common device configuration for user-oriented information.

Note: The Device Pool window now contains only location-related information. The Common Device Configuration window records all the user-oriented information.

5.184.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
Common Device Configurationsame2020000000Compare ok 

5.184.2 Comparison Results

No changes.

5.185 Common Phone Profile

Cisco Unified Communications Manager uses common phone profiles to define phone attributes that are associated with Cisco Unified IP Phones. Having these attributes in a profile instead of adding them individually to every phone decreases the amount of time that administrators spend configuring phones and allows the administrator to change the values for a group of phones. Common phone profiles specify the following attributes:

5.185.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
Common Phone Profilesame7070000000Compare ok 

5.185.2 Comparison Results

No changes.

5.186 Remote Destination Profile

Remote destination profiles (RDPs) are associated with directory numbers (for example, the DN of a user's IP phone) and with remote destinations (for example, the mobile phone number of a user). The RDP controls the interaction between the IP phone and the external numbers (for example, a mobile phone) configured as remote destinations.

Note: Remote destinations cannot be configured with on-cluster DNs as destination numbers.


5.186.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
Remote Destination Profilesame2020000000Compare ok 

5.186.2 Comparison Results

No changes.

5.187 Feature Control Policy

Feature Control Policies allows you to enable or disable a particular feature and thereby control the appearance of certain features and softkeys that display on the phone. You can configure multiple policies on Cisco Unified Communications Manager Administration. After you configure a Feature Control Policy, you must associate that policy to an individual phone, a group of phones, or to all phones in the system.

The appearance of softkeys on Cisco Unified IP Phones is customized by using softkey templates. When you disable a feature by using Feature Control Policies, the softkeys for the disabled feature do not appear in any call state.

Cisco Unified Communications Manager uses the following order of precedence (Device Configuration has the highest precedence) for Feature Control Policies settings: Device Configuration, Common Phone Profile, Enterprise Parameter Configuration.


5.187.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
Feature Control Policysame1010000000Compare ok 

5.187.2 Comparison Results

No changes.

5.188 Recording Profile

To provision line appearances of agents for call recording, administrators create one or more call recording profiles. The administrator then selects a recording profile for a line appearance.

5.188.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
Recording Profilesame1010000000Compare ok 

5.188.2 Comparison Results

No changes.

5.189 SIP Normalization Script

This section defines SIP normalization and transparency scripts.

SIP trunks can connect to a variety of endpoints, including PBXs, gateways, and service providers. Each of these endpoints implements the SIP protocol a bit differently, causing a unique set of interoperability issues. To normalize messages per trunk, Cisco Unified Communications Manager allows you to add or update scripts to the system and then associate them with one or more SIP trunks. The normalization scripts that you create allow you to preserve, remove, or change the contents of any SIP headers or content bodies, known or unknown.

Transparency refers to the ability to pass information from one call leg to the other. REFER transparency allows Cisco Unified Communications Manager to pass on REFER requests to another endpoint rather than acting on them. REFER transparency is key in call center applications, where the agent sending the REFER (initiating the transfer) resides in a geographic area remote from both of the other call parties.

After you configure a script in Cisco Unified Communications Manager, you associate the script with a SIP trunk by configuring the Normalization Script fields in the Trunk Configuration window. You can only associate one script per trunk, but you can associate the same script to multiple trunks.

5.189.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 Normalization Scriptsame8080000000Compare ok 

5.189.2 Comparison Results

No changes.

5.190 SDP Transparency Profile

The Session Description Protocol Transparency for Declarative Parameters allows the administrator to specify declarative SDP attributes that are not natively supported by Cisco Unified Communications Manager (Unified Communications Manager) to be passed from the ingress call leg to the egress call leg.

If the Unified Communications Manager receives attributes that are not explicitly identified by the administrator to send to the egress leg, Unified Communications Manager drops the attribute from the outgoing SDP similar to previous versions of Unified Communications Manager.

5.190.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
SDP Transparency Profilesame2020000000Compare ok 

5.190.2 Comparison Results

No changes.

5.191 Network Access Profile

A Network Access Profile contains information about VPN connectivity and HTTP proxy settings. It is assigned to a Wireless LAN Profile.

5.191.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
Network Access Profilesame4040000000Compare ok 

5.191.2 Comparison Results

No changes.

5.192 Wireless LAN Profile

The Wireless LAN Profile feature removes the need for users to configure Wi-Fi parameters on their phones by allowing the administrator to configure Wi-Fi profiles for them. The user devices can automatically download the Wi-Fi configuration from the Cisco Unified Communications Manager TFTP server, and the configuration is then applied to these devices.

The following Wireless LAN Profiles are configured:

5.192.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
Wireless LAN Profilesame5050000000Compare ok 

5.192.2 Comparison Results

No changes.

5.193 Wireless LAN Profile Group

After you create one or more Wireless LAN Profiles, you can add them to a Wireless LAN Profile Group.

A Wireless LAN Profile Group can be added to a device pool or device-level configuration.

5.193.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
Wireless LAN Profile Groupsame2020000000Compare ok 

5.193.2 Comparison Results

No changes.

5.194 Wifi Hotspot Profile

The Wi-Fi Hotspot Profile feature allows users to use their desk phones to provide a Wi-Fi Hotspot, so that they can connect a Wi-Fi device such as a tablet or a mobile phone to the network through the desk phone. The desk phones can automatically download the Wi-Fi Hotspot configuration from the Cisco Unified Communications Manager, and the configuration is then applied to these devices.

The following Wi-Fi Hotspot Profiles are configured:

5.194.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
Wifi Hotspot Profilesame1010000000Compare ok 

5.194.2 Comparison Results

No changes.

5.195 Application User

Application users are all users associated with other Cisco IP Communications features or applications, such as Cisco Attendant Console, Cisco IP Contact Center Express, or Cisco Unified Communications Manager Assistant. These applications need to authenticate with Cisco Unified Communications Manager (CUCM), but these internal "users" do not have an interactive login and serve purely for internal communications between applications.

5.195.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
Application Usernotsame2112000210220800Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
915/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLogChange 9: Updated record 'haroldapp' Application UserAudit Log id 4 (UTC 15/09/2015 4:09:36 AM User: admin )
1015/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 10: Updated field 'Permissions Information::Groups' : Standard CTI EnabledChange 9Application User 
1115/09/2015 2:09:36 PM15/09/2015 4:09:36 AMAuditLog-ParentChange 11: Updated field 'Permissions Information::Roles' : Standard CTI EnabledChange 9Application User 

5.195.2 Comparison Results

Application User
User IDInformation
haroldapp
Detected Change ID9
Detected ChangeUpdated record 'haroldapp'
Detected ObjectApplication User
Detected Date (UTC)15/09/2015 4:09:35 AM
Detected Date (Local)15/09/2015 2:09:35 PM
Auditlog ID4
Audit Useradmin
Audit Detailsrecord in table applicationuser with key field name = haroldapp updated
Audit Server Time21:09:36.188
Child ID10, 11
Application User Information
BLF Presence GroupStandard Presence group
Accept Presence SubscriptionN
Accept Out-of-dialog REFERN
Accept Unsolicited NotificationN
Accept Replaces HeaderN
Device Information
Controlled Devices
CTI Controlled Device Profiles
Permissions Information
GroupsStandard CTI Enabled
Detected Change ID10
Detected ChangeUpdated field 'Permissions Information::Groups' : Standard CTI Enabled
Detected ObjectApplication User
Detected Date (UTC)15/09/2015 4:09:35 AM
Detected Date (Local)15/09/2015 2:09:35 PM
Parent ID9
RolesStandard CTI Enabled
Detected Change ID11
Detected ChangeUpdated field 'Permissions Information::Roles' : Standard CTI Enabled
Detected ObjectApplication User
Detected Date (UTC)15/09/2015 4:09:35 AM
Detected Date (Local)15/09/2015 2:09:35 PM
Parent ID9

5.196 End User (Condensed)

End users are all users associated with a physical person and an interactive login. This category includes all IP Telephony users as well as Cisco Unified Communications Manager (CUCM) administrators when using the User Groups and Roles configuration (equivalent to the Cisco Multilevel Administration feature in prior Cisco Unified Communications Manager (CUCM) versions). The following is a condensed table with the most important end user settings.


5.196.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
End User (Condensed)same13701370000000Compare ok 

5.196.2 Comparison Results

No changes.

5.197 SIP Realm

The SIP Realm provides the trunk-side credentials when Cisco Unified Communications Manager gets challenged by a trunk peer.

When you configure digest authentication for SIP trunks, Cisco Unified Communications Manager challenges the identity of the SIP user agent that connects to the trunk every time the trunk sends a SIP request to Cisco Unified Communications Manager; the SIP user agent, in turn, can challenge the identity of Cisco Unified Communications Manager. For Cisco Unified Communications Manager to respond to a challenge from the SIP user agent, you must configure the SIP realm for Cisco Unified Communications Manager.


5.197.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 Realmsame2020000000Compare ok 

5.197.2 Comparison Results

No changes.

5.198 Credential Policy Default

The Credential Policy Default window provides options to change the default credential policy assignment for a user and credential type (for example, end user PINs).

At installation, Cisco Unified Communications Manager assigns the system Default Credential Policy to end user passwords, end user PINS, and application user passwords. The system applies the application password that you configured at installation to all application users. You can assign a new default credential policy and configure new default credentials after installation.

5.198.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
Credential Policy Defaultsame3030000000Compare ok 

5.198.2 Comparison Results

No changes.

5.199 Credential Policy

A Credential Policy comprises a set of rules that controls access to a system or network resource. A credential policy defines password requirements and account lockouts for user accounts. Credential policies that are assigned to user accounts control the authentication process in Cisco Unified Communications Manager. After you add a credential policy, you can assign the new policy as the default policy for a credential type or to an individual application or end user.

5.199.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
Credential Policysame2020000000Compare ok 

5.199.2 Comparison Results

No changes.

5.200 Role

Roles allow to configure end users and application users with different levels of privilege. Administrators with full administration privilege configure roles and user groups. In general, full-access administration users configure the privilege of other administration users and end users to Cisco Unified Communications Manager Administration and to other applications.

Roles comprise groups of resources for an application. At installation, default standard roles get created for various administrative functions. You may, however, create custom roles that comprise custom groupings of resources for an application.

Different levels of privilege exist for each application. For the Cisco Unified Communications Manager Administration application, two levels of privilege exist: read privilege and update privilege.

5.200.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
Rolesame370370000000Compare ok 

5.200.2 Comparison Results

No changes.

5.201 Access Control Group

User groups comprise lists of application users and end users. A user may belong to multiple user groups. After you add a user group, you then add users to a user group. Afterward, you may proceed to assign roles to a user group. If a user belongs to multiple user groups, the MLA permission enterprise parameter determines the effective privilege of the user.

Users with full access configure roles, user groups, and access privileges for roles. In general, full-access users configure the access of other users to Cisco Unified Communications Manager Administration. User groups comprise lists of application users and end users. A user may belong to multiple user groups. After you add a user group, you then add users to a user group. Afterward, you may proceed to assign roles to a user group. If a user belongs to multiple user groups, the MLA permission enterprise parameter determines the effective privilege of the user.

5.201.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
Access Control Groupnotsame2812700112111100Compare ok
Detected Changes
IDServer Time (Local)Server Time (UTC)Time SourceDetected ChangeParentDetected Config ObjectRelevant Cisco Audit Log
1216/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 12: Updated record 'Standard CTI Enabled
(S)'
 Access Control Group 
1316/12/2014 2:01:50 PM16/12/2014 4:01:50 AMDetectedChange 13: Updated record 'Standard CTI Enabled
(S)'
Change 12Access Control Group 

5.201.2 Comparison Results

Access Control Group
Name
(Standard)
Role AssignmentAssigned Application Users
(Standard)
Assigned End Users
Standard CTI Enabled
(S)
Detected Change ID12
Detected ChangeUpdated record 'Standard CTI Enabled(S)'
Detected ObjectAccess Control Group
Detected Date (UTC)16/12/2014 4:01:50 AM
Detected Date (Local)16/12/2014 2:01:50 PM
Child ID13
Standard CTI Enabledharoldapp
Detected Change ID13
Detected ChangeUpdated record 'Standard CTI Enabled(S)'
Detected ObjectAccess Control Group
Detected Date (UTC)16/12/2014 4:01:50 AM
Detected Date (Local)16/12/2014 2:01:50 PM
Parent ID12
User_template (User,Template)
User_templateNoMob (User,TemplateNoMob)
agent1 (agent1,UCCX)
akutcher (Ashton,Kutcher)
aps03 (aps,03)
aps04 (aps,04)
aps_user_template (APS,UserTemplate)
bwayne (Bruce,Wayne)
bwillis (Bruce,Willis)
epage (Ellen,Page)
jparsons (Jim,Parsons)
mbuser18 (mbuser18,last)
mbuser19 (mbuser19XX,LastYY)
mkunz (Michael,Kunz)
supervisor1 (supervisor1,UCCX)

5.202 UC Service

Unified Communications (UC) services contain settings for voicemail, conferencing, CTI, and IM and Presence which are grouped into service profiles that are associated with end users. UC service settings are then downloaded by devices of users for seamless integration with the configured UC services.

The following Unified Communications (UC) services are configured:

5.202.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
UC Servicesame7070000000Compare ok 

5.202.2 Comparison Results

No changes.

5.203 Service Profile

Service Profiles that are associated with end users and are deployed to user devices. Each Service Profiles contains several Unified Communications (UC) services which defines settings for voicemail, conferencing, CTI, and IM and Presence. UC service settings are downloaded by devices of users for seamless integration with the configured UC services.

The following Service Profiles are configured:

5.203.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 Profilesame1010000000Compare ok 

5.203.2 Comparison Results

No changes.

5.204 User Profile

The Self-Provisioning feature allows an end user or administrator to add an unprovisioned phone to a Cisco Unified Communications Manager system with minimal administrative effort. A phone can be added by plugging it into the network and following a few prompts to identify the user.

With appropriately configured User Profiles, end users can provision their own devices. These User Profiles may be shared by a group of users that share the same characteristics. The User Profile contains the following settings:

5.204.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 Profilesame2020000000Compare ok 

5.204.2 Comparison Results

No changes.

5.205 Self-Provisioning

The Self-Provisioning feature allows an end user or administrator to add an unprovisioned phone to a Cisco Unified Communications Manager system with minimal administrative effort. A phone can be added by plugging it into the network and following a few prompts to identify the user.

This feature enhances the out-of-box experience for end users by allowing them to directly add their desk phone or soft client without contacting the administrator. It simplifies administrator deployments by allowing them to add desk phones on behalf of an end user. The feature lets administrators and users deploy a large number of devices without interacting directly with the Cisco Unified Communications Manager Administration GUI, but from the device itself. The feature relies on the administrator preconfiguring a number of templates and profiles, so that when the phone attempts to self-provision, the necessary information is available in the system for it to create a new device.

5.205.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
Self-Provisioningsame0000000000compare ok 

5.205.2 Comparison Results

Table of Contents [Hide TOC]