Contents

Introduction

How do I configure TMS and a TANDBERG Codian MCU to work together?

Related Information

Introduction

This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence MCU 4505, Cisco TelePresence Management Suite and Cisco TelePresence MCU MSE 8510 products.

Q. How do I configure TMS and a TANDBERG Codian MCU to work together?

A. Follow these instructions.

Preparing a Codian MCU for adding to TMS

1. In Network > Services ensure the SNMP port is enabled and set to port 161.

2. In Network > SNMP ensure the RO, RW and Trap community are set to public, private and public respectively.

3. In Settings > Gatekeeper ensure that H.323 gatekeeper usage is set to Required and that you have specified a suitable service prefix (see Numeric IDs in TMS below).

4. If required, configure your MCU's SIP Settings: go to Settings > SIP and ensure that SIP registration settings is set to Allow conference registration.

5. In Network > Port A, configure a host name for your MCU. (If TMS is to manage your MCU using port B, then configure the host name in Network > Port B).

Adding an MCU to TMS

1. In TMS go to Systems > Navigator and click Add systems.

2. Enter the IP address or DNS name of the Codian MCU.

3. If required, enter a username and password by clicking on Advanced settings and completing the fields.

4. Click Next.

5. TMS should find your system. If you see a message that an incorrect password has been supplied, select Edit system and enter/re-enter the username and password. Click Save.

6. You should be returned to a screen indicating that your system has been added. Click Finish adding systems.

Numeric IDs in TMS

For H.323, we recommend that you configure the Codian MCU to use a service prefix before adding the system to TMS.

When TMS creates a conference on an MCU it assigns a numeric ID to that conference. Where there is more than one MCU, TMS might assign the same numeric ID to more than one conference (on different MCUs); however, by specifying a unique Prefix for MCU registrations for each MCU (Settings > Gatekeeper), it is possible to ensure that registrations and connections do not fail.

Alternatively, change the numeric IDs that TMS uses when creating conferences. To do this:

1. Go to Systems and select the MCU in the left-hand pane

2. Click Settings and then Extended settings.

3. For First meeting Id specify the first numeric ID to be used on this MCU.

4. Specify the Meeting id step.

5. Click Save.

The number of meeting IDs that could potentially be used by TMS is equal to the port count of the MCU; for example, for a 4520 there are 40 video ports and 40 audio ports and therefore a maximum 80 meeting IDs. These should not overlap with those of other MCUs unless a service prefix has been specified.

Sometimes TMS will report that a gatekeeper registration from the MCU has failed, even though the MCU reports that all gatekeeper registrations have been successful.

Using TMS with SIP

For SIP it is recommended that you follow the above procedure of ensuring meeting IDs do not conflict between MCUs because service prefixes are not supported in SIP. It is also recommended that conference SIP registration is enabled. To do this:

1. In TMS, go to Systems and select the MCU in the left hand pane.

2. Click Settings and then Extended settings.

3. For Conference sip registration, select On.

4. Click Save

Related Information

- Technical Support & Documentation - Cisco Systems