Registration, Admission and Status
Encyclopedia
H.323
defines packet-based multimedia communications systems that use a RAS (Registration, Admission and Status) channel to carry messages used in the H.323 Gatekeeper
discovery and endpoint registration processes. Details of the messages and procedures are defined in H.225.0
.
RAS is also an IT term used in the same instances as telephony with the same functions of authentication before accessibility to certain functions.
Gatekeeper request, reject, and confirm messages (GRx)
Registration request, reject, and confirm messages (RRx)
Unregister request, reject, and confirm messages (URx)
Admission request, reject, and confirm messages (ARx)
Bandwidth request, reject, and confirm message (BRx)
Disengage request, reject, and confirm (DRx)
Location request, reject, and confirm messages (LRx)
Info request, ack, nack, and response (IRx)
Nonstandard message
Unknown message response
Request in progress (RIP)
Resource availability indication and confirm (RAx)
Service control indication and response (SCx)
Admission confirm sequence (ACS)
Figure 4 - A high-level communication exchange between two endpoints (EP) and two gatekeepers (GK)When an endpoint is powered on, it will generally send either a gatekeeper request (GRQ) message to "discover" gatekeepers that are willing to provide service or will send a registration request (RRQ) to a gatekeeper that is predefined in the system’s administrative setup. Gatekeepers will then respond with a gatekeeper confirm (GCF). If a GRQ has been sent the endpoint will then select a gatekeeper with which to register by sending a registration request (RRQ), to which the gatekeeper responds with a registration confirm (RCF). At this point, the endpoint is known to the network and can make and place calls.
When an endpoint wishes to place a call, it will send an admission request (ARQ) to the gatekeeper. The gatekeeper will then resolve the address (either locally, by consulting another gatekeeper, or by querying some other network service) and return the address of the remote endpoint in the admission confirm message (ACF). The endpoint can then place the call.
Upon receiving a call, a remote endpoint will also send an ARQ and receive an ACF in order to get permission to accept the incoming call. This is necessary, for example, to authenticate the calling device or to ensure that there is available bandwidth for the call.
Figure 4 depicts a high-level communication exchange between two endpoints (EP) and two gatekeepers (GK).
H.323
H.323 is a recommendation from the ITU Telecommunication Standardization Sector that defines the protocols to provide audio-visual communication sessions on any packet network...
defines packet-based multimedia communications systems that use a RAS (Registration, Admission and Status) channel to carry messages used in the H.323 Gatekeeper
H.323 Gatekeeper
An H.323 Gatekeeper serves the purpose of Call Admission Control and translation services from E.164 IDs to IP addresses in an H.323 telephony network. Gatekeepers can be combined with a gateway function to proxy H.323 calls and are sometimes referred to as Session Border Controllers...
discovery and endpoint registration processes. Details of the messages and procedures are defined in H.225.0
H.225.0
H.225.0 is part of the H.323 family of telecommunication protocols.The main objective of H.225.0 is the definition of messages and procedures for:* Call Signaling: establish, control and end an H.323 call...
.
RAS is also an IT term used in the same instances as telephony with the same functions of authentication before accessibility to certain functions.
RAS Signaling
Endpoints use the RAS protocol in order to communicate with a gatekeeper. Likewis e, gatekeepers use RAS to communicate with peer gatekeepers. RAS is a fairly simple protocol composed of just a few messages. Namely:Gatekeeper request, reject, and confirm messages (GRx)
Registration request, reject, and confirm messages (RRx)
Unregister request, reject, and confirm messages (URx)
Admission request, reject, and confirm messages (ARx)
Bandwidth request, reject, and confirm message (BRx)
Disengage request, reject, and confirm (DRx)
Location request, reject, and confirm messages (LRx)
Info request, ack, nack, and response (IRx)
Nonstandard message
Unknown message response
Request in progress (RIP)
Resource availability indication and confirm (RAx)
Service control indication and response (SCx)
Admission confirm sequence (ACS)
Figure 4 - A high-level communication exchange between two endpoints (EP) and two gatekeepers (GK)When an endpoint is powered on, it will generally send either a gatekeeper request (GRQ) message to "discover" gatekeepers that are willing to provide service or will send a registration request (RRQ) to a gatekeeper that is predefined in the system’s administrative setup. Gatekeepers will then respond with a gatekeeper confirm (GCF). If a GRQ has been sent the endpoint will then select a gatekeeper with which to register by sending a registration request (RRQ), to which the gatekeeper responds with a registration confirm (RCF). At this point, the endpoint is known to the network and can make and place calls.
When an endpoint wishes to place a call, it will send an admission request (ARQ) to the gatekeeper. The gatekeeper will then resolve the address (either locally, by consulting another gatekeeper, or by querying some other network service) and return the address of the remote endpoint in the admission confirm message (ACF). The endpoint can then place the call.
Upon receiving a call, a remote endpoint will also send an ARQ and receive an ACF in order to get permission to accept the incoming call. This is necessary, for example, to authenticate the calling device or to ensure that there is available bandwidth for the call.
Figure 4 depicts a high-level communication exchange between two endpoints (EP) and two gatekeepers (GK).