Operation details for the route-to command

Last Updated : Oct 01, 2013 |

You can use the route-to command with or without coverage.

The following table summarizes the operation of the route-to command for each destination type and the conditions with the commands.

Condition

cov = n any step

cov = y any step

Invalid destination

Go to the next step or stop vector processing

Go to the next step or stop vector processing

VDN extension

Vector assigned

Go to a new vector

Go to a new vector

Vector has no steps

Stop vector processing

Call remains in a queue and the caller continues to hear feedback.

In the case where the route-to command fails and vector processing stops because of a busy station or a trunk group, you can implement retry in the vector.

For retry, include an unconditional goto step as the last step for a loopback to the route-to command.

To reduce processor occupancy, use an intermediate wait-time step with feedback and delay interval.

Stop vector processing

A call that Communication Manager routes to a VDN using route-to number with cov = y unconditionally functions similar to a directly dialed call instead of a VDN call. Therefore, the terminating station displays only the originating station information and does not show the VDN information. For other types of VDN calls, the terminating station displays the VDN name.

When Communication Manager routes a call to a VDN, Communication Manager ends vector processing of the previous vector and removes the call from the queues that the previous vector establishes for the call.

Station extension idle with all call appearances idle

Call Forwarding (CF) ALL Active or CF direct agent calls

Forward the call, move to the next step, or stop vector processing

Forward the call, send the call to the coverage point, or play a busy tone

Coverage

Direct agent calls

Ring an idle call appearance

Send the call to the coverage point

Extension all

Go to next step or stop vector processing

Send the call to the coverage point

Send All Calls (SAC)

Ring an idle call appearance

Send the call to the coverage point

None

Ring an idle call appearance

Deliver the call with coverage

Station extension active with idle two-way appearance

CF-ALL active

Forward the call, move to the next step, or stop vector processing

Forward the call, send the call to the coverage point, or play a busy tone

Station extension busy with no idle two way appearance

Extension in hunt group

Put the call in a queue, move to the next step, or stop vector processing

Put the call in a queue, send the call to the coverage point, or play a busy tone

CF-ALL Active or CF direct agent calls

Forward the call, move to the next step, or stop vector processing

Forward the call, send the call to the coverage point, or play a busy tone

Call waiting for analog station

Go to the next step or stop vector processing

Call continues to wait in a queue

Coverage

Extension active

Go to the next step or stop vector processing

Send the call to the coverage point

Extension busy

Send the call to the coverage point

All

Send the call to the coverage point

Send All Calls (SAC)

Send the call to the coverage point

None, hunt, forward, or coverage destination is unavailable

Play a busy tone

Extension with incompatible Class of Restriction (COR)

Go to the next step or stop vector processing

Terminating Extension Group (TEG)

All members are idle

Ring an idle call appearance

Deliver call with coverage

A member is active on TEG

Go to the next step or stop vector processing

Send the call to the coverage point or play a busy tone

No idle call appearance

Go to the next step or stop vector processing

Send the call to the coverage point or play a busy tone

Hunt group extension

Idle agent

Ring an idle call appearance

Deliver call with coverage

No idle agent

  • Cannot put the call in a queue: Go to the next step or stop vector processing

  • Put the call in a queue

Play a busy tone

Put the call in a queue

Extension on another node: Uniform Dialing Plan (UDP) DCS or non-DCS

Trunk available

Deliver the call

Deliver the call

Trunk unavailable

Go to the next step or stop vector processing

Put the call in a queue or play a reorder tone

No DCS buffer for routing

Deliver the call with or without the DCS message

Deliver the call with or without the DCS message

Trunk Access Code (TAC) destination

Trunk group no dial access

Go to the next step or stop vector processing

Route the call to a local attendant

Trunk available

Deliver the call

Deliver the call

Trunk unavailable

Go to the next step or stop vector processing

Put the call in a queue or play a reorder tone

Automatic Alternate Routing (AAR) or Alternate Route Selection (ARS) Feature Access Code (FAC) destination including subnet trunking

Trunk group no dial access

Try the next route

Route the call to a local attendant

Trunk available

Deliver the call

Deliver the call

Other routes are available

Deliver the call

Try the next route

All routes are busy

  • No pattern queuing

  • Queuing assigned

Go to the next step or stop vector processing

  • No Pattern Queuing: Play a reorder tone

  • Queuing assigned: Queue to pattern

Attendant queue (dial 0)

Idle attendant

Ring an idle call appearance

Deliver the call with coverage

No idle attendant

  • Not in Night Service

  • In Night Service

Put the call in a queue

Put the call in a queue

Assigned destination

Deliver to Night Service

Deliver to Night Service

Unassigned destination

Put the call in a queue

Put the call in a queue

Individual attendant access

Idle attendant

Ring an idle call appearance

Deliver the call with coverage

Busy attendant

Put the call in a queue, go to the next step, or stop vector processing

Put the call in a queue or play a busy tone

Centralized Attendant Service (CAS) with caller at a branch location

Available Release Link Trunks (RLTs)

Ring an idle call appearance

Deliver the call with coverage

All RLTs busy

put the call in a queue, go to the next step, or stop vector processing

Put the call in a queue or play a busy tone

Inter-PBX attendant call

Trunk group controlled

Route to local attendant

Route the call to a local attendant

Trunk available

Deliver the call

Deliver the call

Trunk unavailable

Go to the next step or stop vector processing

Play a reorder tone

Look-Ahead Interflow (LAI): Feature active and routes over ISDN-PRI with one exception. Any route-to with cov = y step that routes over ISDN-PRI cancels LAI.

The exception occurs when a call reaches a vector with coverage to a VDN. Communication Manager does not forward calls but redirects calls that cover to a VDN.

For covered calls, a route-to command with coverage functions as if the coverage field option is n. Therefore, a route-to with coverage = y routes covered calls with LAI over ISDN facilities if LAI is active.

B-channel is available

Bearer (B) channel unavailable

Go to the next step or stop vector processing

Put the call in a queue or play a reorder tone

  • Accept call

Interflow succeeds. The originating Communication Manager server removes the call from any queue or feedback, such as music or ringback.

Call cut-through

  • Reject call

Go to the next step or stop vector processing

Play a busy tone or disconnect the call

Receiving Communication Manager with LAI.

  • Accept call

Interflow succeeds

Call cut-through

  • Reject call

Go to the next step at the receiving Communication Manager server or the originating Communication Manager server treats the call as rejected after a 2–minute time out

Play a busy tone or disconnect the call

  • if interflow-qpos

Determine if the queued call is eligible for interflow

Invalid destinations include the following:

  • Attendant Control of Trunk Group Access (ACTGA) destination

  • COR of the VDN. For example, origination restricted, Facility Restriction Level (FRL) of a VDN that is lower than that required for AAR or ARS pattern access

  • Empty, for example, zero collected digits or invalid route-to destination number

  • Incompatible calling and destination partitions

  • Incomplete number of digits for the AAR or ARS pattern

  • Maintenance busy station extension

  • Non AAR or ARS FAC

  • No routes assigned to the AAR or ARS pattern

  • Off-net forwarding destination

  • Unassigned extension number

The collected digits must match a valid ARS analysis string if:

  • Call routing includes a Trunk Access Code (TAC) destination

  • The TAC is for a Central Office (CO) or a Foreign eXchange (FX) trunk with a route-to with coverage = n step

If the collected digits do not match a valid ARS analysis string, Communication Manager treats the destination as invalid. For other trunk types with a route-to number or route-to digits with coverage = n step, the step succeeds, that is, Communication Manager ends vector processing when Communication Manager seizes the trunk.

For a route-to with coverage = y step, the step succeeds if Communication Manager assigns the TAC.

If you administer coverage as y, Communication Manager removes the call from vector processing when vector processing reaches the route-to step regardless of the facility or remote Communication Manager availability. Even if the destination is available, Communication Manager removes the call out of the queue and also removes any feedback, such as music or ringback.

If the receiving Communication Manager vector rejects the call, the busy command or forced disconnect command defines subsequent call treatment.

Communication Manager treats the call as if the destination is directly dialed. Treatment includes coverage, call forwarding, and incomplete call treatment, that is, busy, reorder, or intercept tones. The answering station sees only the caller name and the number, unless you administer Display VDN for Route-To DAC on the Vector Directory Number (VDN) screen as y.

Communication Manager treats a routed call with an adjunct routing link command in the same way as a routed call with a route-to with coverage = y command.