Why does the VCS not respond to an H.323 RAS Bandwidth Request (BRQ) message from a neighbor?

Available Languages

Updated:April 23, 2015
Document ID:112521

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 does the VCS not respond to an H.323 RAS Bandwidth Request (BRQ) message from a neighbor?

A. H.323 BRQs inform gatekeepers of the bandwidth that is being used by an endpoint for a call. BRQs should only be sent from an endpoint to the gatekeeper to which it is registered (the BRQ includes an endpoint ID that is assigned to the endpoint by the gatekeeper registration process). BRQs are not used to share bandwidth information between two neighbors.

If you do have a system that is neighbored to the VCS and want it to be able to provide bandwidth information to the VCS, this can be achieved in the following ways:

  • (optionally) in LRQ messages (bandwidth 10240 = 1Mbps)

  • included in SETUP messages as the Information transfer rate: in the Bearer Capability. The rate represents a multiplier of 64kbps, so for example a rate of 136 will equal a bandwidth of 8704kbps (136*64kbps = 8704kbps)

  • included in the terminalCapabilitySet capability table and capability items as maxBitRate. NB: a maxBitRate of 5120 = 512kbps

Related Information

Revision History

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

Was this Document Helpful?

FeedbackFeedback

Contact Cisco