1 Report Information

1.1 Report Generation

This configuration report for the Cisco Unified Communications Manager (CUCM) cluster has the following details:

2 System

The following chapters describe the configuration items in the Cisco Unified Communications Manager Administration System menu:

• Server
• Service Status
• Cisco Unified Communications Manager
• Cisco Unified Communications Manager Group
• Presence Redundancy Groups (in CUCM 10.0 and later)
• Phone NTP Reference
• Date-Time Group
• Presence Group
• Regions
• Audio Codec Preference (in CUCM 9.0 and later)
• Device Pool
• Device Mobility Group
• Device Mobility Info
• DHCP Server
• DHCP Subnet
• Location (in CUCM 9.0 and later)
• Location Bandwidth Manager Group (in CUCM 9.0 and later)
• Location Bandwidth Manager Hub Group (in CUCM 9.0 and later)
• LDAP System
• LDAP Directory
• LDAP Authentication
• LDAP Custom Filter (in CUCM 9.0 and later)
• Presence Redundancy Groups (in CUCM 10.0 and later)
• Location
• Physical Location
• Survivable Remote Site Telephony
• MLPP Domain
• Enterprise Parameters
• Enterprise Phone Configuration (in CUCM 8.0 and later)
• Service Parameters
• Certificate
• Phone Security Profile
• SIP Trunk Security Profile
• Application Server
• License Unit Report
• Geo Location (in CUCM 9.0 and later)
• E911 (in CUCM 9.0 and later)

2.1 Server

The following Cisco Unified servers are present in the cluster:

2.2 Services

The following services are present on this server:

2.3 Cisco Unified CM

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

2.4 Cisco Unified CM Group

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

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

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

• Redundancy: This feature enables you to designate both primary and backup Cisco Unified Communications Managers for each group.
• Call processing load balancing: This feature enables you to distribute the control of devices across multiple Cisco Unified Communications Managers.

2.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 Groups are defined:

2.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.

2.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.

2.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.

2.9 Region Information

The following chapters describe the items in the Cisco Unified Communications Manager Administration 'Region Information' menu:

• Audio Codec Preference lists
• Regions

2.9.1 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:

2.9.2 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.

2.10 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.

2.11 Device Mobility

The Device Mobility feature dynamically changes important location settings, such as calling search space, region, date/time group, and SRST reference, for roaming devices. Cisco Unified Communications Manager uses device pool settings to implement new parameters when the phone roams away from its home location. Administrators no longer need to reconfigure location settings when a phone changes location.

The dynamically reconfigured location settings ensure that voice quality and allocation of resources are appropriate for the new phone location:

• When a mobile user moves to another location, call admission control (CAC) can ensure video and audio quality with the appropriate bandwidth allocations.
• When a mobile user makes a PSTN call, the phone can access the local gateway instead of the home gateway.
• When a mobile user calls the home location, Cisco Unified Communications Manager can assign the appropriate codec for the region.

2.11.1 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.

2.11.2 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.

2.12 DHCP

Dynamic Host Configuration Protocol (DHCP) server enables Cisco Unified IP Phones, connected to either the customer's data or voice Ethernet network, to dynamically obtain their IP addresses and configuration information. DHCP uses Domain Name System (DNS) to resolve host names both within and outside the cluster.

This section contains:

• DHCP Server
• DHCP Subnet

2.12.1 DHCP Server

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

2.12.2 DHCP Subnet

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

2.13 LDAP

Directory configuration for synchronization and authentication includes 5 objects:

• LDAP System
• LDAP Directory
• LDAP Authentication
• LDAP Custom Filter (CUCM 8.0 and later)
• LDAP Search (CUCM 11.5 and later)

The Cisco DirSync service ensures that the Cisco Unified Communications Manager database stores all user information. If you use an integrated corporate directory, for example Microsoft Active Directory or Netscape/iPlanet Directory, with Cisco Unified Communications Manager, the Cisco DirSync service migrates the user data to the Cisco Unified Communications Manager database. The Cisco DirSync service does not synchronize the passwords from the corporate directory.

LDAP authentication can be only used if synchronization with the customer LDAP directory is enabled and will then forward authentication requests to the LDAP. Passwords are never synced to the local database.

2.13.1 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.

2.13.2 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.

2.13.3 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:

• End user passwords are authenticated against the corporate directory.
• Application user passwords are authenticated against the Cisco Unified Communications Manager (CUCM) database.
• End user PINs are authenticated against the Cisco Unified Communications Manager (CUCM) database.

2.13.4 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:

2.13.5 LDAP Search

LDAP Search allows the configuration of LDAP search filters for users and groups.

2.14 SAML Single Sign-On

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

2.15 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 than the one from where it originated.

The following CORS domains are configured:

2.16 Location Information

Enhanced Location Call Admission Control (CAC) is a model-based CAC mechanism. The administrator creates a model of the network and how the network infrastructure handles the media. Through the Cisco Unified Communications Manager interface the administrator configures the Enhanced Location CAC mechanism based on the network model.

The following chapters describe the items in the Cisco Unified Communications Manager Administration 'Location Information' menu:

• Location
• Location Bandwidth Manager Group
• Location Bandwidth Manager Hub Group

2.16.1 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.

2.16.2 Location Bandwidth Manager Group

The Location Bandwidth Manager Groups set the Location Bandwidth Manager (LBM) services that each Cisco Callmanager service communicates 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.

2.16.3 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

2.17 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.

2.18 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.

2.19 MLPP

The Multilevel Precedence and Preemption (MLPP) service allows properly validated users to place priority calls. If necessary, users can preempt lower priority phone calls.

Precedence designates the priority level that is associated with a call. Preemption designates the process of terminating lower precedence calls that are currently using the target device, so a call of higher precedence can be extended to or through the device.

An authenticated user can preempt calls either to targeted stations or through fully subscribed time-division-multiplexing (TDM) trunks. This capability assures high-ranking personnel of communication to critical organizations and personnel during network stress situations, such as a national emergency or degraded network situations.

This chapter covers the following topics:

• MLPP Domain
• Resource Priority Namespace Network Domains
• Resource Priority Namespace Lists

2.19.1 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.

2.19.2 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.

2.19.3 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.

2.20 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.

2.21 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 a given setting, the corresponding parameter setting does not take effect.

The following Enterprise Phone Configurations are configured: