Model Features
The H.323 model suite supports the following H.323 features.
Table 57: H.323 Model Features
| Feature | Description | Support |
|---|---|---|
| H.323 Device | ||
| Terminals | Terminals provide both Application and IER support. | Supported |
| Gatekeeper | Based on Cisco IOS Gatekeeper. | Supported |
| Border Elements (BEs) | Border Elements will only provide basic RAS signaling and will not include the H.225 Annex G signaling. | Supported |
| Gateways | H.323 gateway design will incorporate the use of the SHOUTip device. | Supported |
| Multipoint Control Units (MCUs) | Allows for teleconference support. | Not Supported |
| H.323 Umbrella Protocols | ||
| H.225 Call Signaling | Supported | |
| H.225 Registration, Admission, and Status (RAS) | Supported | |
| H.225 Annex G | H.225 RAS signaling will be used instead. | Not Supported |
| H.245 Signaling | Not Supported | |
| Real-time Transport Protocol (RTP) | Use of Riverbed standard RTP models | Supported |
| Real-time Transport Control Protocol (RTCP) | RTCP is not supported in the Riverbed standard suite of models. | Not Supported |
| Node Parameters | ||
| Assigned Gatekeeper | Represents the IP address/hierarchical name of the assigned gatekeeper for the particular terminal or gateway. This attribute will only be placed on terminals and gateways. | Supported |
| Gatekeeper Address | Represents the IP address of the gatekeeper. This attribute will only be provided on gatekeeper and border element nodes. | Supported |
| Call Signaling Mode | Attribute will be placed on gatekeeper nodes. This attribute will specify whether “Direct Call Signaling” or “Gatekeeper-routed Signaling” will occur for calls setup through this particular gatekeeper. | Supported |
| Assigned Administrative Domain | Specifies which administrative domain the H.323 device will be placed inside. This attribute will be placed on all H.323 devices. | Supported |
| Max Number of Calls | Only allows the specified number of calls to pass through the particular H.323 terminal or gateway at a time. | Supported |
| Encoder Schemes | Provides CODEC information for the device | Supported |
| Frames per Packet | Provides CODEC information for the device | Supported |
| Hybrid Mode | Allows the user to represent voice packets using hybrid or explicit traffic. | Supported |
| SHOUTip Network Signaling Protocol | Attribute placed on gateways. Allows the user to choose which voice signaling protocol should be used to forward a particular call (i.e., H.323 or SIP). | Supported |
| Lower-layer Protocol Configuration Attributes | All necessary attributes from the Riverbed standard processes will be promoted for configuration by the user (RTP, UDP, and so on). | Supported |