Why is VCS clustering better than the H.225 Alternate Gatekeeper mechanism?

Available Languages

Download Options

  • PDF     (4.5 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (83.7 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (69.4 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:January 13, 2021
Document ID:112789

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 Cisco TelePresence Video Communication Server Expressway.

    Q. Why is VCS clustering better than the H.225 Alternate Gatekeeper mechanism?

    A. VCS clustering is an active model where all VCSs in the cluster are always available for service. In the alternate gatekeeper model, the failover gatekeeper is essentially a hot-standby which can take up to 20 minutes to become active if the control gatekeeper fails.

    VCS clusters can be distributed across datacenters therefore increasing service reliability.In the alternate gatekeeper model, both gatekeeper and alternate gatekeeper (2 box solution) need to be on the same subnet and therefore the same site.

    VCS clusters allow you to load share by distributing the workload across different peers. It is very easy to add additional capacity by adding another VCS.

    Related Information

    Revision History

    Revision Publish Date Comments
    1.0
    13-Jan-2021
    Initial Release

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco