Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
DQOS Exam Certification Guide - Cisco press.pdf
12.7 Mб

Resource-Based CAC 589

fail whenever the single terminating gateway is too busy. In addition, in enterprise networks the probability of congestion is typically higher in the IP cloud than in the number of terminating POTS trunks. In the SP networks discussed earlier, congestion is more common in the terminating POTS trunks than in the IP cloud.

In spite of these limitations, RAI can still be used for enterprise networks provided the gateway to PBX connections at the remote sites consist of T1/E1 trunks. If a terminating gateway is too busy, it triggers a PSTN reroute instead of selecting an alternate gateway as in the SP network situation.

RAI Operation

The discussion of where and how RAI is used in SP and enterprise networks clearly shows that RAI is most useful in situations where multiple terminating gateways can reach the same destination, or called, phone number. However, RAI has value in any situation where there is a desire to prevent a call from being routed to a gateway that does not have the available POTS capacity to terminate the call.

When a gatekeeper receives an RAI unavailable indication from a gateway, it removes that gateway from its gateway selection algorithm for the phone numbers that gateway would normally terminate. An RAI available indication received later returns the gateway to the selection algorithm of the gatekeeper.

RAI is an optional H.323 feature. When you implement a network, therefore, it is prudent to verify that both the gateways and gatekeepers support this feature. Cisco gatekeepers support RAI. Cisco gateway support for RAI is detailed in a later section of this chapter.

RAI Configuration

RAI on the gateway is configured with high-water- and low-water-mark thresholds, as shown in Figure 8-19. When resource usage rises above the high-water mark, an RAI unavailable indication is sent to the gatekeeper. When resource availability falls below the low-water mark, an RAI available indication is sent to the gatekeeper. To prevent hysteresis based on the arrival or disconnection of a single call, the highand low-water marks should be configured 10 percentage points apart. (Hysteresis refers to the process of switching a feature on, then off, then on, and so on, over and over again, as would happen if the highand low-water marks were configured to very similar values.)

To configure RAI, use the following gateway configuration command:

resource threshold [all] [high %-value] [low %-value]

To configure an RAI unavailable resource message to be sent to the gatekeeper at a high-water mark of 90 percent and a RAI available resource message to be sent to the gatekeeper at a lowwater mark of 80 percent, enter the following command:

resource threshold high 90 low 80

590 Chapter 8: Call Admission Control and QoS Signaling

Figure 8-19 RAI Configuration



High Water Mark

Gateway Sends RAI Unavailable


Message to Gatekeeper

Low Water Mark

Gateway Sends RAI Available

Message to Gatekeeper



RAI Platform Support

The Cisco AS5300 access server has supported RAI since Cisco IOS Release 12.0(5)T. The Cisco 2600 and 3600 series routers have supported RAI for T1/E1 connections only, not for analog trunks, since Release 12.1.3T. The other Cisco IOS gateways do not yet support RAI as of Release 12.1(5)T or 12.2. The RAI calculation includes digital signal processors (DSPs) and DS0s, and may not be the same for all platforms. In current software, CPU and memory are not yet included in the RAI availability indication.

Table 8-13 evaluates the RAI mechanism against the CAC evaluation criteria described earlier in this chapter.

Table 8-13 RAI CAC Evaluation Criteria

Evaluation Criteria




VoX supported

VoIP only



Toll bypass or IP telephony

Toll bypass


Potentially IP telephony, but CM does not yet support RAI



Platforms and releases

Cisco AS5300 access server: Cisco IOS Release 12.0(5)T


Cisco 2600 and 3600 series routers T1/E1: Cisco IOS


Release 12.1(3)T



PBX trunk types supported




End to end, local, or IP cloud

Local at the terminating gateway (DSP and DS0 resources;


algorithm platform dependent)