Cisco Unified Communications Manager Configuration
This chapter contains the configuration procedures you must perform to configure Unified Communications Manager. Perform the procedures on the Unified Communications Manager Publisher.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the configuration procedures you must perform to configure Unified Communications Manager. Perform the procedures on the Unified Communications Manager Publisher.
Step 1 |
Open Cisco Unified Communications Manager and log in. |
||
Step 2 |
Navigate to . |
||
Step 3 |
Fill in with the Fully Qualified Domain Name of your cluster.Example:
|
||
Step 4 |
Click Save. |
Step 1 |
Select Cisco Unified CM Administrator from the Navigation menu and click Go. |
Step 2 |
Select System > Cisco Unified CM Group. |
Step 3 |
Click Find. Then click Default. |
Step 4 |
Move the two subscribers from the Available panel to the Selected panel. |
Step 5 |
Click Save. |
Step 6 |
Click Reset. |
Step 7 |
On the Device Reset popup, click Reset. |
Step 8 |
Click Close. |
Step 1 |
Select . |
Step 2 |
Click Add New. |
Step 3 |
Select Conference Bridge Type of Cisco IOS Conference Bridge. |
Step 4 |
In the Conference Bridge name field, enter a unique identifier for the conference bridge name that matches the configuration on the gateway.
|
Step 5 |
Select a Device Pool. |
Step 6 |
Click Save. |
Step 7 |
Click Apply Config. |
Step 1 |
Select . |
Step 2 |
Click Add New. |
Step 3 |
In the Media Termination Point Name field, enter a unique identifier for the media termination that coincides with the configuration on the gateway.
|
Step 4 |
Select a Device Pool. |
Step 5 |
Click Save. |
Step 6 |
Click Apply Config. |
A transcoder is required for multicodec scenarios to convert a stream from a G.711 codec to a G.729 codec.
For more information about transcoder configuration in Unified Communications Manager and gateway, see the section "Configure Transcoders and Media Termination Points" in the System Configuration Guide for Cisco Unified Communications Manager at https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-installation-and-configuration-guides-list.html.
Step 1 |
In Unified Communications Manager Administration, select Media Resources > Transcoder. |
Step 2 |
Click Add New. |
Step 3 |
For Transcoder Type, select Cisco IOS enhanced media termination point. |
Step 4 |
In the Device Name field, enter a unique identifier for the transcoder name that coincides with the configuration on the gateway. In the following example, this is gw70xcode.
|
Step 5 |
In the Device Pool field, select the appropriate device pool. |
Step 6 |
Click Save. |
Step 7 |
Click Apply Config. |
The Ingress Gateway to Unified CVP outbound dial peer configuration uses the IPv4 address of Unified CVP as the session target.
Step 1 |
Select . |
Step 2 |
Add a Media Resource Group for Conference Bridges.
|
Step 3 |
Add a Media Resource Group for Media Termination Point.
|
Step 4 |
Add a Media Resource Group for Transcoder.
|
Step 5 |
Click Save. |
Step 1 |
Select . |
Step 2 |
Click Add New and enter a Name. |
Step 3 |
Add a Media Resource Group list and associate all of the media resource groups. Click Save. |
Step 4 |
Select Find. Select the appropriate device pool. . Click |
Step 5 |
From the Media Resource Group List drop-down list, choose the media resource group list added in Step 2. |
Step 6 |
Click Save. Click Reset. |
Step 1 |
In Cisco Unified CM Administration, select . |
||
Step 2 |
Click Add New. |
||
Step 3 |
Set a device name; for example, PCCEInternalDNs. |
||
Step 4 |
For Device Pool, select Default. |
||
Step 5 |
Select a Media Resource Group List from the list. |
||
Step 6 |
Click Save. |
||
Step 7 |
Click on Line [1] to configure the directory number associated with this route point. This directory number will be a pattern that is intended to match any of the internal Dialed Numbers you configure in Packaged CCE for internally routed calls. (For instance, for Transfers and Conferences).
|
||
Step 8 |
Select . |
||
Step 9 |
Select pguser created during Packaged CCE automated initialization. |
||
Step 10 |
Select the CTI Route Point from the list of Available Devices, and add it to the list of Controlled Devices. |
||
Step 11 |
Click Save. |
Locations-based call admission control (CAC) is used in the Unified CCE branch-office call flow model (also known as the Centralized Model). This means that all servers (Unified CVP, Unified CCE, Unified Communications Manager, and SIP Proxy server) are centralized in one or two data centers, and each branch office.
Configure Unified Communications Manager to use the Ingress gateway instead of Unified CVP as the originating location of the call. This configuration ensures that CAC can be properly adjusted based on the locations of the calling endpoint and the phone.
Important |
Do not define Unified CVP as a gateway device in Unified Communications Manager. |
In Cisco Unified CM Administration, define the Ingress gateways as gateway devices. Assign the correct location to the devices. |
Complete the following procedure to create a route group.
Step 1 |
In Unified Communications Manager, select . |
Step 2 |
Click Add New. |
Step 3 |
Enter a name for the route group; for example, CVP Route Group. |
Step 4 |
Using the Add to Route Group button, add all CVP Trunks as Selected Devices. |
Step 5 |
Click Save. |
Complete the following procedure to add a route list to the route group.
Step 1 |
In Unified Communications Manager, select . |
Step 2 |
Click Add New. |
Step 3 |
Enter a name for the route list; for example, CVP Route List. |
Step 4 |
Select a Cisco Unified Communications Manager Group. |
Step 5 |
Add the route group you created. |
Step 6 |
Click Save. |
Complete the following procedure to add a route pattern to the route list.
Step 1 |
In Unified Communications Manager, select . |
Step 2 |
Click Add New. |
Step 3 |
Enter a route pattern of 8881111000XXXX. |
Step 4 |
Select the route list that you created. |
Step 5 |
Keep all defaults in all panels |
Step 6 |
Click Save. |
Step 7 |
Click OK at the message about the Forced Authorization Code. You do not want a Forced Authorization Code. |
This option allows a dual-stack SIP trunk to offer both IPv4 and IPv6 media. Perform this procedure for IPv6-enabled deployments only.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Click Add New and enter the name of the SIP profile. |
Step 3 |
Check the Enable ANAT check box on the SIP Profile. |
Step 4 |
Save your changes. |
There are two Unified CVP Servers and each must be associated with a SIP trunk in Unified Communications Manager. The following procedure explains how to configure the SIP trunks, each targeting a different Unified CVP Server.
Actual site topology may necessitate the use of alternate SIP trunk plans, which are supported as long as both Unified CVP Servers are targeted by the configured SIP trunks.
Step 1 |
In Unified Cisco CM Administration, select Device > Trunk. |
Step 2 |
Click Add New. |
Step 3 |
From the Trunk Type drop-down list, choose SIP Trunk, and then click Next. |
Step 4 |
Enter the following in the Device Information section:
|
Step 5 |
Scroll down to the SIP Information section:
|
Step 6 |
Click Save. |
Step 7 |
Click Reset. |
Step 8 |
Repeat for all the remaining Unified CVP servers in the deployment. |