Attendant queue

A call that the route-to command processes can wait in an attendant queue and Communication Manager removes the call from vector processing. The route-to command can gain access to public and private networks.

If the route-to command dials the attendant and if the system is in Night Service, Communication Manager routes the call to the Direct Inward Dialing (DID) Listed Directory Number (LDN) night destination.

You can use the extension number that you assign to an attendant console as the command argument.

Automatic Alternate Routing (AAR) or Automatic Route Selection (ARS)

The route-to command can specify AAR or ARS access codes.

The route-to command can make AAR or ARS calls that implement subnet trunking, which is call routing over trunk groups that end in Communication Manager with different dial plans.

Authorization codes

Communication Manager disables authorization codes for routing calls through VDNs.

The route-to command fails and Communication Manager does not prompt for an authorization code in the following scenarios:

• Authorization codes are active for the system.

• A route-to command in a prompting vector gains access to AAR or ARS.

• The Facility Restriction Level (FRL) of the VDN does not have permissions to use the chosen routing preference.

Bridged appearance

If the destination of a route-to command is a station with bridged appearances, Communication Manager updates the button lamps associated with the bridged appearance.

Class of Restriction (COR)

When you apply COR checking to a route-to number or route-to digits step, Communication Manager uses the COR number of the latest VDN. Communication Manager uses the COR number to determine the time-of-day (tod) routing chart of the Partitioned Group Number (PGN). This PGN determines the route tables that Communication Manager must use on a call.

Coverage

For a call that covers or forwards to a VDN, the route-to with coverage y command functions similar to the route-to with coverage n command. For a covered or forwarded call, Communication Manager disables the coverage option because Communication Manager cannot redirect such a call further. Communication Manager forwards a route-to with coverage y command to a station that has call forwarding active.

When a route-to with coverage n command initiates a call over ISDN-PRI facilities and LAI is y, Communication Manager treats the call on a Look-ahead basis. However, if you use the route-to with coverage y command, Communication Manager interflows the call unconditionally.

Direct Outward Dialing (DOD)

If vector processing executes the route-to command and DOD is in effect, Communication Manager compares the COR numbers of the latest VDN and the called facility to determine whether Communication Manager can forward the call. If access is not permitted, the route-to command fails and vector processing continues to the next step.

The route-to command can also fail in the following scenario:

• When you assign a VDN with a COR that requires access codes.

Look-ahead Interflow (LAI)

For LAI, Communication Manager treats the route-to command as a call acceptance vector command or as a neutral vector command.

Communication Manager treats the command as a call acceptance vector command when one of the following is true:

• Command terminates to a valid local destination.

• Command seizes a non-PRI trunk.

• Command execution results in an LAI call attempt and the Communication Manager server at the far end accepts the call.

Communication Manager treats the command as a neutral vector command when one of the following is true:

• Termination is unsuccessful.

• Trunk is not seized.

• The Communication Manager server at the far end denies the LAI call attempt.

Messaging system

The route-to command can call a messaging system extension. If this happens, Communication Manager treats the call as a direct call to the messaging system, and the calling party can retrieve messages.

If the call covers to a VDN, the route-to command supports a remote messaging system interface to a local hunt group extension that is assigned as a remote messaging system hunt group. This hunt group forwards the call to the destination in a manner similar to when you assign the hunt group as a coverage point. Communication Manager treats the DCS link down condition for a call that covers to a VDN as a direct call to the messaging system.

Pickup group

If the route-to command calls a station that is a member of a Pickup group, any member of the group can receive the call.

Service Observing

You can use the route-to command to start Service Observing.

For more information, see Avaya Aura® Call Center Elite Feature Reference.

Tenant Partitioning

If you use Tenant Partitioning, Communication Manager checks the TN of the Vector Directory Number (VDN) during call processing. Communication Manager then determines whether to deliver calls to the route-to destination.

Communication Manager does not route calls to the destination in the following scenario:

• The TN matches, but the Facility Restriction Level (FRL) of the Class of Restriction (COR) assigned to the VDN has a value that is lower than the value of the destination FRL,

Instead, Communication Manager logs a denial event and vector processing moves to the next vector step.