Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192
There are mandatory and optional configuration details. It is advisable to never use any of
the default mandatory items. Three examples of this are the call manager group, region, and
location. The device pool and region do not need to be specified, but they are mandatory.
The default values will not work in most environments, but they can be modified. Instead
of modifying the default values, these elements can be copied, renamed, and reconfigured.
Rename the elements in a way that allows the administrator to clearly define the goal of the
configuration element. A device pool named NYC-CCMG is probably a Cisco Communications
Manager group for the New York City office. Endpoint configuration elements that
this chapter covers include the following:
■ CUCM Group
■ Regions
■ Locations
■ Date/Time Group
■ CUCM Group
■ Regions
■ Locations
■ Phone NTP Reference
■ Presence Group
■ Device Pool
■ Security Profile
■ Softkey Templates
■ Phone Button Templates
■ SIP Profile (SIP Phones Only)
■ Common Phone Profile
Device Pool
Device pools define common characteristics that can be applied to many devices. The
device pool structure supports the separation of user and location information. The device
pool contains only device- and location-related information. The Common Device Profile
Configuration window records all the user-oriented information such as type of softkey
188 Chapter 9: CUCM Configuration
template that is used and locale information. The Common Device Profile was introduced
in CallManager 5.0. Each device must be associated with a device pool and with a common
device configuration.
The following mandatory components must be assigned to a device pool:
■ CUCM group
■ Date/time group
■ Region
■ Softkey template
■ SRST reference
The device pool combines all the individual configuration settings into a single logical construct.
The device pool can then be assigned to devices, such as IP phones, gateways, and
trunks. To create, modify, or delete a device pool in CUCM, use the CUCM Administration
web page and navigate to System > Device Pool. ClickAdd New to display a configuration
screen similar to the one shown in Figure 9-1.
Figure 9-1 Device Pool Configuration
Endpoint Basic Configuration Elements 189
Phone Network Time Protocol Reference
The phone Network Time Protocol (NTP) references can be configured in CUCM
Administration to ensure that a SIP phone gets its date and time directly from an NTP
server. The SIP phone will use the date header in the SIP 200 OK response message to the
phone’s SIP REGISTER if an NTP server is unavailable. SCCP phones obtain time
information within the SCCP signaling.
The phone NTP reference must be selected in a date/time group to become active. A
hierarchy of phone NTP references can be configured in the date/time group.
The date/time group configuration is referenced from a device pool, and the device pool is
assigned to a device at the device configuration page. The date/time group configuration
descriptions are as follows:
■ IP Address: Enter the IP address of the NTP server that the SIP phone should use to
get its date and time.
■ Description: Enter a description for the phone NTP reference. CUCM Administration
automatically propagates the information in the IP Address field to the Description
field, but it can be edited.
■ Mode: From the drop-down list box, choose the mode for the phone NTP reference.
The values available are as follows:
—Directed Broadcast: This is the default NTP mode; in this mode, the
phone accesses date/time information from any NTP server but gives the
listed NTP servers (1st = primary, 2nd = secondary) priority. For example,
if the phone configuration contains NTP servers where A = primary
NTP server and B = secondary/backup NTP server, the phone uses the
broadcast packets (derives the date/time) from NTP server A. If NTP
server A is not broadcasting, the phone accesses date/time information
from NTP server B. If neither NTP server is broadcasting, the phone
accesses date/time information from any other NTP server. If no other
NTP server is broadcasting, the phone derives the date/time from the
CUCM 200 OK response to the REGISTER message.
—Unicast: In this mode, the phone sends an NTP query packet to the
specified NTP server. If the phone gets no response, the phone accesses
date/time information from any other NTP server. If no other NTP servers
respond, the phone derives the date/time from the CUCM 200 OK
response to the REGISTER message.
CUCM currently does not support the multicast and anycast NTP modes. If either of these
modes is selected, CUCM defaults to the directed broadcast mode.
190 Chapter 9: CUCM Configuration
To create or modify a phone NTP reference in CUCM, use the CUCM Administration web
page. Navigate to System > Phone NTP Reference. Click Add New to display the same
configuration screen shown in Figure 9-2. Phone NTP references can be added, deleted, or
modified from the Phone NTP Reference Configuration page.
Figure 9-2 Phone NTP Reference
Date/Time Groups
Date/time groups are used to define the time zone a device should use for the local time the
end user will be in. Each device is assigned to a device pool, and each device pool has one
assigned date/time group.
Installation of CUCM automatically configures a default date/time group that is called
CMLocal. CMLocal synchronizes to the active date and time of the operating system on the
server where CUCM is installed. After installing CUCM, the settings of CMLocal can be
changed.
To create, modify, or delete a date/time group in CUCM, use the CUCM Administration
web page and navigate to System > Date/Time Group. Click Add New to display a
configuration screen similar to the one displayed in Figure 9-3.
Endpoint Basic Configuration Elements 191
Figure 9-3 Date/Time Group Configuration
Cisco Unified CM Group
A CUCM group specifies a prioritized list of up to three CUCMs.
The first CUCM in the list serves as the primary CUCM for that group, the next member of
the list (from the top) serves as the secondary CUCM, and the third the tertiary (third)
CUCM.
If the primary CUCM in the CUCM group is not available, the device tries to register to the
second CUCM that is listed in the group, and on the third if the secondary is unavailable.
The Cisco IP Phone always maintains an active TCP 2000 (SCCP) connection open to two
CUCMs. Keepalives are sent every 30 seconds to each CUCM to guarantee reachability.
CUCM groups provide important features for the CUCM system:
■ Redundancy: Up to three CUCM servers can be defined for each CUCM group. The
Cisco IP Phone has five CUCM references, but only three of them can be populated by
the CUCM group.
■ Call processing load balancing: The administrator can control active device
registrations by configuring multiple CUCM groups and using different primary
servers for each group. This distributes the control of devices and call-processing load.
192 Chapter 9: CUCM Configuration
For most systems, there is a need for multiple CUCM group configurations, and a single
CUCM can be assigned to multiple groups to achieve better load distribution and redundancy.
Different CUCM groups are configured in different device pools that collect phone
configuration settings.
To create, modify, or delete a group in CUCM, use the CUCM Administration web page
and go to System > Cisco Unified CM Group. Click Add New to display a configuration
screen similar to the one displayed in Figure 9-4.
Figure 9-4 CUCM Group
Regions
Regions are used to specify the audio and video codec that is used per call within and
between regions. The configured audio codec determines the type of audio compression
used per audio call.
The video call bandwidth comprises the sum of the audio and video bandwidth of the
video call.
NOTE The default audio codec for all calls through CUCM specifies G.711. If there is
no plan to use any other audio codec, it is not required to change region configuration.
CUCM allows a maximum of 500 regions.
Endpoint Basic Configuration Elements 193
To create, modify, or delete a region in CUCM, use the CUCM Administration and navigate
to System > Region. Click Add New to display a configuration screen similar to the one in
Figure 9-5. Choose a destination region, and then select the audio codec and video call
bandwidth as appropriate between the regions.
Figure 9-5 Regions
Locations
Use locations to implement call admission control (CAC) in a centralized call-processing
system. CAC enables the administrator to limit the number of audio and video calls placed
over the WAN. WAN availability is limited only by the amount of bandwidth that is
available for audio and video calls configured in the priority queue (PQ) of the quality
of service (QoS) configuration.
In a centralized call-processing system, a single CUCM cluster provides call processing for
all locations on the IP telephony network. The 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 CUCM. IP WAN links connect the remote
locations to the main location.
CUCM has no concept of bandwidth limitations without a CAC mechanism. CUCM
believes that bandwidth is infinite, causing a condition where 100 G.711 phone calls could
be routed over a T1 link that has QoS provisioned to accommodate 7 phone calls. Devices
NOTE If CAC is not used to limit the audio and video bandwidth on IP WAN links, an
unlimited number of calls can be active on that link at the same time. This situation can
cause the quality of all audio and video calls to degrade as the link becomes
oversubscribed.
194 Chapter 9: CUCM Configuration
can be provisioned into different locations, and then the interlocation bandwidth would
limit the number of calls that can be routed over the WAN links. When a call is rejected
from being routed over the WAN, the call can be rerouted over the PSTN links, and a toll
charge would probably apply. When the call is rerouted, the end user will see a No
Bandwidth, Re-Routing message on the LCD display of the phone.
To create, modify, or delete a location in CUCM, use the CUCM Administration web page
and go to System > Location. Click Add New to display a configuration screen similar to
the one displayed in Figure 9-6. Choose the location and configure the amount of audio and
video bandwidth available to that particular location. These configurations should align to
the PQ bandwidth that the data network team has provisioned across the IP WAN links.
Figure 9-6 Locations
Phone Security Profile
The Phone Security Profile window includes security-related settings such as device
security mode, Certificate Authority Proxy Function (CAPF) settings, digest authentication
settings (for SIP phones only), and encrypted configuration file settings. A security profile
must be applied to all phones that are configured in CUCM Administration. Administrators
can make use of existing security profiles that have security disabled.
Device Settings 195
To create, modify, or delete a security profile in CUCM, use the CUCM Administration web
page and go to System > Security Profile > Phone Security Profile. Click Add New, and
then select the phone type from the Phone Security Profile Type drop-down menu. Click
Next. Select the phone security profile protocol from the drop down-menu (SCCP or SIP)
and click the Next button. A configuration screen similar to that shown in Figure 9-7 will
display. Security parameters are covered in more detail in Cisco IP Telephony Part 2.
No comments:
Post a Comment