User`s manual

Mediant 1000
H.323 User's Manual 24 Document #: LTRT-83401
1.1.3 H.323 Features
The Mediant 1000 H.323 gateway is built on and implements the RadVision™ H.323
version 4.2 protocol stack. The gateway complies with H.323 Version 4.0 ITU standard,
H.245 Version 10 and H.225 Version 4.
1.1.3.1 Gatekeeper
Registers to known Gatekeeper.
Supports Gatekeeper registration with prefixes.
Supports sending of Unregister request before reset.
Uses routed or direct mode calls.
Supports the Alternative Gatekeepers mechanism, used to obtain the IP addresses of
alternative Gatekeepers.
Uses redundant Gatekeepers (if redundant Gatekeepers are defined).
Supports Automatic Gatekeeper Discovery (using IP Multicast).
Works also without a Gatekeeper using the internal routing table with or without dialing
plan rules.
Can fallback to internal routing table if there is no communication with the
Gatekeepers.
Supports the "TimeToLive" parameter. The gateway sends Registration requests up to
"TimeToLive" expiration.
Supports Info Request Response (IRR) messages for KeepAlive.
Supports the mapping of destination (Alias) numbers in ACF message by the
Gatekeeper.
Supports Gatekeeper ID configuration (per Gatekeeper IP) for different Gatekeepers.
Supports Lightweight Registration.
Supports RAI (Resource Available Indication) messages, informing Gatekeeper that
the gateway’s resources are below a threshold.
Supports registration types: E.164, H323-ID and PartyNumber.
Supports Pre-granted ARQ.
Supports H.235 Security, Annex D Procedure 1 (authentication with a Gatekeeper).
1.1.3.2 Call Setup
Can use the Normal Connect procedure.
Can use the Fast Connect procedure with or without immediately opening H.245
channel.
Can use Tunneling.
Can negotiate a coder from a list of given coders for Normal or Fast Connect
procedures.
Can open an H.245 channel when using Fast Connect.
Supports Early H.245 procedure, enabling opening of an H.245 channel before a
Connect message is received. Can be used for sending out-of-band DTMF digits
before a call is answered.
Can represent SourceNumber and DestinationNumber through: E.164, H323-ID and
PartyNumber.
Can configure (in the manipulation tables) or map (according to H.225 V.4 Table 18)
the representation of the Src/Dest number types in H.323 messages.