Why am I having trouble neighboring my TANDBERG VCS with the TANDBERG Codian built-in gatekeeper?

Available Languages

Updated:April 23, 2015
Document ID:112391

Bias-Free Language

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.

Introduction

This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence IP VCR 2210, Cisco TelePresence VCR MSE 8220, Cisco TelePresence MCU 4505, Cisco TelePresence Video Communication Server Expressway and Cisco TelePresence MCU MSE 8510 products.

Q. Why am I having trouble neighboring my TANDBERG VCS with the TANDBERG Codian built-in gatekeeper?

A. A very few devices such as the TANDBERG VCS send an endpoint identifier element in the LRQ. Prior to the Codian MCU version 2.3, the built-in gatekeeper checked this endpoint identifier element, and thinking the device was an endpoint, rejected the request if the identifier was not registered.

From MCU version 2.3(1.0) onwards that check is no longer performed. If you are having difficulty neighboring to a built-in gatekeeper on a Codian MCU, upgrade the MCU to the latest version which is available on the web site.

Related Information

Revision History

Revision Publish Date Comments
1.0
23-Apr-2015
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco