Cisco gatekeeper update protocol

This is the procedure:. The Cisco Gatekeeper verifies the request by the endpointIdentifier in order to locate the endpoint in the registration database. It locates the call record through the use of the callReferenceValue in order to find a call associated with the endpoint with the same callReferenceValue.

If it locates the call record, it then computes the change in bandwidth, then adds or subtracts from the global zone bandwidth, as necessary. It does the same for any proxy or gateway resources in use. This is the unidirectional bandwidth for a Cisco G. If the endpoints in the call chose to use a more efficient codec, this was not reported to the Cisco Gatekeeper.

Initially, kb is reserved. If the endpoints in the call select a more efficient codec, the Cisco Gatekeeper is notified of the bandwidth change. Note: Configure the Cisco H. See the debugs captured from a Cisco Gatekeeper in a cluster.

After you receive these messages, the Cisco Gatekeeper updates the other gatekeepers in the cluster about this bandwidth change. Note: These commands are used in order to capture this output: debug h asn1 , debug ras , debug gatekeeper gup asn1 , debug gatekeeper gup events. It then sends the LRQ to Z2.

The H. ITSPB gets connected. ITSP gets connected. Use the OIT to view an analysis of show command output. Issue the show running config begin gatekeeper command to verify the gatekeeper configuration:.

You can also use the show gatekeeper zone status command to verify the gatekeeper configuration:. Issue the show gatekeeper performance stats command to view RAS information, including via-zone statistics:. If the invia is a local zone, this counter identifies the number of LRQs terminated by the local invia gatekeeper. If the invia is a remote zone this counter identifies the number of LRQs that were forwarded to the remote invia gatekeeper.

Usually caused by a misspelled gatekeeper name. If the outvia is a local zone, this counter identifies the number of LRQs terminated by the local outvia gatekeeper. This counter applies only in configurations where no invia gatekeeper is specified.

If the outvia is a remote zone, this counter identifies the number of LRQs that were forwarded to the remote outvia gatekeeper. Identifies the number of originating ARQs handled by the local gatekeeper if the outvia is that local zone. Auto discovery enables an endpoint to discover its gatekeeper through a multicast Gatekeeper Request GRQ message. Because endpoints do not have to be statically configured for gatekeepers, this method has less administrative overhead.

A gatekeeper can be configured to respond only to certain subnets. It never remains silent. If a gatekeeper is not available, the gateway periodically attempts to rediscover a gatekeeper. If a gateway discovers the gatekeeper has gone off-line, it ceases to accept new calls and attempts to rediscover a gatekeeper. Active calls are not affected. Registration occurs after the discovery process.

Every gateway can register with only one active gatekeeper. There is only one active gatekeeper per zone. Admission messages between endpoints and gatekeepers provide the basis for call admissions and bandwidth control. Gatekeepers authorize access to H. See the Gatekeeper to Gateways Call Flow section of this document for more information. Location Request messages are commonly used between inter-zone gatekeepers in order to get the IP addresses of different zone endpoints.

This table defines the RAS location request messages:. See the Gatekeeper to Gateways Call Flow section for more information. The gatekeeper can use the RAS channel in order to obtain status information from endpoints. You can use the RAS in order to monitor whether the endpoint is online or off-line. This table defines the RAS status information messages:. However, bandwidth can change during the call. This table defines the RAS bandwidth control messages:.

Direct Endpoint Signaling —This method directs call setup messages to the terminating gateway or endpoint. These sections only present Directed Call Signaling call flow scenarios. Also, assume the gateways have already completed discovery and registration with their gatekeepers. A major functionality of gatekeepers is to keep track of other H. When many H. In such large VoIP installations it is possible to configure a centralized directory gatekeeper that contains a registry of all the different zones and coordinates LRQ-forwarding processes.

No full mesh is needed between inter-zone gatekeepers with directory gatekeepers. Note: A directory gatekeeper is not an industry standard, but is a Cisco implementation. This diagram illustrates the concept of VoIP Network scaling with gatekeepers and directory gatekeepers:.