Cisco Collab: How to configure Region Settings Between VCS and CUCM

Before understand this topic, you should have knowledge of VCS -Video Communication Server and Cisco Unified Communication Manager (CUCM)  The below mentioned procedure is basically created on the demo basis and can have changes accordingly. 

All network engineers who are working to get CCIE Collaboration, this is an important topic to understand.

Today I am going to talk about the procedure to configure Region Settings on Video Communication Server (VCS) to communicate with a Cisco Unified Communication Manager (CUCM) or another VCS.

Below is the basic network design showing the Cisco Unified Communication Manager (CUCM) architecture and network design of VCS call control with the Cisco Unified Communication Manager (CUCM) cluster.

Fig 1.1
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.

Step 1. Log in to VCS and form a trunk.
Step 2. Navigate to Configuration > Zones > Zones as shown in the image

Fig 1.2
Step 3. Select New

Fig 1.3
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)

Fig 1.4
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.

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

Fig 1.6
Step 7. Select New

Fig 1.7
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

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