Content Server Deployment with VCS

Introduction

This document describes how to configure the Cisco Telepresence Video Communication Server (VCS) for integration with Telepresence Content Server (TCS) for H323 and SIP.

Integration of TCS and VCS is straightforward and you can follow the steps that are mentioned in this document for H323 or SIP or both call to TCS to record any conference.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this doument is based on these software and hardware versions:

TCS 7.x and 6.x

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, make sure that you understand the potential impact of any command.

Configure

Configurations

VCS Configuration

Step 1: Create Neighbor Zone for TCS (Require for Gateway or Trunk mode on TCS)

• Create Neighbor zone in VCS 

      To configure Neighbor zone in VCS, go to Configuration>Zones>Zones> Click New.

Note: For Lab TCS FQDN: tcsgn3-1.tplab1.local, VCS FQDN: vcs.tplab1.local

Step 2: Configure Search rule on VCS as per your dial plan

In order to configure Search rule on VCS, navigate to Configuration > Dial Plan > Search Rules

For example: In this lab configuration VCS send all call starts with 62 or 63 or tcsgn3  to TCS for recording. Create Regex as per your deployment and requirement to send call from VCS to TCS.

TCS Configuration

Step 1: Configure TCS for SIP Trunk (If require SIP call to TCS from VCS)

Note When TMS is used for schedule conference with recording in that case SIP URI won't be used and require H323 ID or E.164 to be configured on recording alias.

In order to configure SIP in TCS, navigate to Management > Configuration > Site Setting 

1. Enable SIP trunk on TCS configuration to receive multiple recording call from VCS at same time.
2. In Server address configure SIP address.
3. Select appropriate Transport protocol.

Step 2: Configure TCS for H323 in Gateway mode 

In order to configure H323 Gatekeeper in TCS, navigate to Management > Configuration > Site Setting 

For example. in this lab configuration TCS is configured with H323 prefix 62, will use all H323 URI and E164 starts with 62. Cofnfigure this prefix as per your dial-plan requirement.

1.  Enable Gatekeeper with VCS by "Gatekeeper Enabled" check.
2. Configure Gatekeeper addres as your VCS server.
3. Configure require H323 ID or E.164 or both as per requirement.
4. Change Registration to Gateway mode to record multiple call at one time as per License installed on TCS.

To check other parameter for configuration refer TCS admin guide TCS 6.0 Admin guide

Verify

Use this section in order to confirm that your configuration works properly

Step 1: Neighbor Zone is up and runs between VCS and TCS

This snapshot helps to confirm that VCS has active neighbor zone with TCS.

 Step 2: TCS shows H323 Gatekeeper Active

This snapshot helps to verify that TCS is actively connected to VCS for H323

Step 3: TCS shows SIP Trunk Active

This snapshot helps to confirm TCS SIP is active with VCS and ready to receive call from VCS.

Troubleshoot

There is no specific troubleshooting information available for this configuration.