Adjunct Routing

Accordingly, you should almost always include either a wait-timestep or an announcement step immediately after an adjunct routing step. Moreover, the switch cancels the route request if vector processing encounters a step containing one of the following commands:

adjunct routing (G3V2 and earlier releases.) G3V3 and later releases allow multiple outstanding adjunct route requests.

busy

check-backup split

converse-on split

queue-to main split

collect digits

disconnect

messaging split

route-to

NOTE:

Actually, if another adjunct routing step is encountered, the route request information is not lost. Although the initial route request is cancelled, a second route request is sent, and this route request includes the same information included in the first route request.

If a valid call route is received by the switch before one of the vector commands in the previous list is executed, the switch routes the call to the destination specified by the adjunct route. Otherwise, the route request is terminated without affecting vector processing.

Let’s return to our suggested strategy of including a treatment step after the adjunct routing step. Accordingly, here’s an example presented earlier that illustrates this approach:

1.adjunct routing link 1111

2.wait-time 60 seconds hearing music

3.route-to number 0 with cov n if unconditionally

4.disconnect after announcement 2000

Figure 9-3. Treatment Step Used as a Delay for Adjunct Routing

In Step 2 of this example, the wait-timecommand specifies a delay period of 60 seconds. As a result, the switch in this case will wait up to 60 seconds to receive a reply from the adjunct. On the other hand, replacing the wait-timecommand in Step 2 with an announcement command enables the switch to wait for no longer than the length of time it takes for the announcement to complete. Accordingly,

9-6Issue 4 September 1995

Page 137
Image 137
AT&T 555-230-520 manual Treatment Step Used as a Delay for Adjunct Routing