AT&T 555-230-520 manual Multiple Outstanding Route Requests

Adjunct Routing

NOTE:

The operation described in the previous paragraph is similar to that for the route-to with coverage command.

Multiple Outstanding Route Requests

This feature allows multiple ASAI Route Requests for the same call to be active at the same time (simultaneously). The Route Requests can be over the same or different ASAI links.

The requests are all made from the same vector. They must be specified back- to-back, without intermediate (wait-time, announcement, goto, or stop) steps. If the adjunct routing commands are not specified back-to-back, current adjunct routing functionality will apply (that is, previous outstanding route requests will be cancelled when an adjunct routing vector step is executed).

The first Route Select response received by the switch will be used as the route for the call, and all other outstanding Route Requests for the call will be cancelled.

This capability increases the redundancy options available with ASAI. Prior to G3V3, adjunct routing applications that wanted to have a backup link tested if the primary link was down and then executed the adjunct routing for the backup link with a vector as shown in Figure 9-4.Note that the route request over link 1001 is cancelled when step 4 is executed (because of the intermediate step 3).

1.wait-time 0 seconds hearing ringback

2.adjunct routing link 1001

3.wait-time 6 seconds hearing ringback

4.adjunct routing link 1002

5.wait-time 6 seconds hearing ringback

6.route-to number 3465 with cov n if unconditionally (default routing)

Figure 9-4. Sample Adjunct Routing Vector with Redundancy

With Multiple Outstanding Route Requests, multiple adjuncts can process the route call request without waiting for the first route attempt to fail. An application can make use of this feature to distribute the incoming call load evenly across adjuncts, based on the adjunct’s current CPU load.

9-8Issue 4 September 1995