The adjunct routing link command provides a means for an adjunct ASAI processor to specify the call destination. Communication Manager provides information in an ASAI route request message. The ASAI adjunct uses the message to access a database and determines a route for the call. In a typical application, the ASAI adjunct can use the dialed number, CPN/BN, or digits collected using Call Prompting or CINFO to access customer information. The adjunct then determines the call route. A maximum of 16 digits collected from the last collect digits command can be passed.

An adjunct specified in an adjunct routing link command can route a call to an internal number, an external number, a split, a VDN, an announcement extension, or a specific agent. An adjunct can also provide priority ringing, priority queuing and specify that a route to an agent be done as a DAC.

When a call encounters an adjunct routing link command, Communication Manager sends an ASAI message to the specified adjunct requesting a call route. The following list identifies the contents of the message:

• Calling number information: The ISDN-PRI or R2-MFC signaling facilities provide the CPN/BN. If the call originates from a local Communication Manager extension, the extension is the calling number.

• Originating line information (II-digits): The ISDN-PRI facilities provide a two-digit code to indicate the originating line type.

• Called number: The originally called extension if a call is forwarded to a VDN, or the first VDN through which the call is routed if the call is not forwarded to the VDN.

• Routing VDN: Last VDN that routed the call to the vector that contains the adjunct routing link command.

• Call identifier: An ASAI identifier that permits the ASAI adjunct to track multiple calls using either event notification or third-party call control.

• Look-Ahead Interflow (LAI) information (if any): Includes the original VDN display information, the priority level of the call at the originating Communication Manager, and the time that the call entered vector processing.

• Digits collected using Call Prompting (if any): The most recent collect digits command collects the digits. The digits can be CINFO digits but, ASAI does not indicate the type of digits collected.

• User-to-User Information (if any): The ASAI user-provided data associated with the call. If provided by ASAI, the data is provided in a 3rd-Party-Make-Call, Auto-Dial, or Route-Select message. If provided over ISDN, the data is in the SETUP message that delivers the call to Communication Manager.

The wait-time hearing i-silent command allows the adjunct to decide whether to accept an incoming ISDN-PRI call. When this step is encountered after an adjunct routing link step, Communication Manager does not return an ISDN PROGress message to the originating Communication Manager. This is important for Network ISDN features and the LAI feature.

If the call is queued, the adjunct routing link step is ignored, and vector processing continues with the next vector step. If the ASAI link specified in the adjunct routing link step is down, the step is skipped.

An ASAI link failure can change the subsequent treatment, that is, how announcement or wait-time steps (if any) in the vector, are processed. In some instances, such processing is influenced by the position that the treatment steps occupy in the vector. In other instances, the positioning of the commands and their relationship to specific goto commands come to effect. For example, any announcement or wait-time step that immediately follows an adjunct routing link step, with its ASAI link down, is skipped.

The field IC Adjunct Routing should be disabled on the CTI Link screen unless the CTI application requires it enabled. Then, program the associated vectors as instructed for that application.

When IC Adjunct Routing is disabled, only the first announcement or wait-time step encountered is skipped after a sequence of adjunct route steps fails. The following paragraphs apply when IC Adjunct Routing is disabled.

The second step after the adjunct routing link step is often implemented as a default treatment, for example, a route-to an attendant. If the ASAI link is down, the default step executes immediately. Otherwise, the step executes if the application does not respond with a route within the time period specified by the wait-time step.

Alternatively, if a goto step follows an adjunct routing link step, Communication Manager executes the goto step and skips various treatment steps according to their position in the vector and the conditional determination of the goto step. Specifically, if the goto step succeeds and the branch is taken, Communication Manager skips the announcement or wait-time step, which is the first non-goto step branched by the goto step.

Alternately, if the goto step fails and the branch is not taken, Communication Manager skips the announcement or wait-time step that immediately follows the goto step, if the application is down.

After Communication Manager sends a route request to the ASAI adjunct, vector processing continues with the vector steps that follow.

The step that follows the adjunct routing link step, determines the maximum length of time Communication Manager waits for the ASAI adjunct to reply with a call route. Accordingly, you must always include a wait-time or an announcement step immediately after an adjunct routing link step. Moreover, Communication Manager cancels the route request if vector processing encounters a step containing any of the following commands:

• busy

• check split

• collect digits

• converse-on split

• disconnect

• messaging split

• queue-to split

• route-to

Multiple adjunct routing steps can follow each other in sequence. Each step activates a separate adjunct route request. Any intervening vector command (or blank step) between two adjunct routing link commands cancels any previous route-to requests.

If the server receives a valid call route before one of the vector commands in the previous list is executed, the server uses a route-select message to route the call to the destination specified by the adjunct route. If the call route received is invalid, the route request is terminated without affecting vector processing.

The adjunct can also decide to not route a call by rejecting the route request sent by the server, or the link or application can go down. Upon receiving a route request rejection, or detection of a link or application failure, the server terminates the announcement or wait-time step executed for the call and continues with the next vector step.

When the server receives a call route from the ASAI adjunct, the server first validates the route as follows:

1. The server verifies if the VDN’s Class of Restriction (COR) permits the call to be terminated at the adjunct-supplied destination.

2. The server verifies if the adjunct-supplied information, that is, the destination number, ACD split, and Trunk Access Code (TAC)/Alternate Automatic Routing (AAR)/Automatic Route Selection (ARS) access code, for the route is valid. This includes checking if the destination is compatible with the dial plan and that the options specified by the adjunct are correct.

3. If the ASAI adjunct specifies the Direct Agent Call (DAC) option, the destination number, that is, the agent must be logged in to the adjunct-specified ACD split.

4. If the call destination is external, the server verifies if the trunk is available for the call.

If any of the conditions are not met, the route validation fails, and the server performs the following actions:

1. Discards the route.

2. Notifies the ASAI adjunct that the route is invalid.

3. Continues with vector processing.

If the route is valid, the server performs the following actions:

1. Terminates vector processing immediately.

2. Notifies the ASAI adjunct that the route is accepted.

3. Routes the call to the destination specified by the ASAI adjunct.

When the call is routed, the caller hears the normal call progress tones and feedback. However, if the call is routed to an extension with no available call appearances and no coverage path, the caller hears a busy tone. Any other features such as Send-All-Calls or Call Forwarding that can be in effect at the adjunct-supplied destination interact with the routed call.

The adjunct routing link command has no interaction with answer supervision.

If adjunct routing is used with ISDN-PRI, an adjunct routing link command followed by a wait-time hearing silence step signals the originating server that the receiving server has accepted the call, even though answer supervision is not provided. To prevent this from occurring, use the wait-time hearing i-silent command after the adjunct routing link step.