Configure Region Settings Between VCS and CUCM

Introduction

This document describes the procedure to configure Region Settings on Video Communication Server (VCS) to communicate with a Cisco Unified Communication Manager (CUCM) or another VCS.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• VCS
• CUCM

Components Used

The information in this document is based on VCS.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Configure

In order to configure Region Settings, follow these steps.

Step 1. Log in to VCS and form a trunk.

Step 2. Navigate to Configuration > Zones > Zones as shown in the image:

Step 3. Select New.

Step 4. Change these fields accordingly:

Name: {Zone name}

Type: Neighbor

H.323 mode: Off

SIP Port: 5060 (Similar to the port number that you have given in Destination CUCM/VCS)

SIP Transport: TCP or UDP (TLS if encryption is supported by CUCM)

Step 5. Select Maintenance and set the authentication policy to Treat as authenticated and provide the location of the destination address for which you want to form a trunk with. Then, select Create Zone.

Step 6. Navigate to Configuration > Dial plan > Search rules.

Step 7. Select New.

Step 8. Enter the values of these fields accordingly and select Save when finished.

Rule name: {name}

Description: {description}

Priority: 2

Mode: Alias pattern match

Pattern type: Regex

Pattern string: {regex pattern which matches the destination URI pattern}

Pattern behavior: Replace

Replace string: {String the pattern has to be replaced with}

On successful match: Stop

Target: {Select the one which you created in step 4 and 5}

State: Enabled

Once the configuration is done for that side of the trunk, the endpoints that are registered to destination CUCM/VCS can be called.

Verify

There is currently no verification procedure available for this configuration.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.