Route-to number command

Last Updated : Sep 08, 2012 |

The following syntax rules apply when you use vector variables with the route-to number command.

route-to number

up to 16 digits (0-9)

<digits>[A-Z, AA-ZZ]

<digits>*<digits>A

<digits>#<digits>A

<digits>~p<digits>A

<digits>~m<digits>A

<digits>~s<digits>A

<digits>~w<digits>A

<digits>~W<digits>A

~r<digits>A

~r+<digits>A

with cov y or n

if

digit

>, >=, <>, =, <=

0-9 or #

interflow-qpos

<, =, <=

1-9

unconditionally

<digits> notation for 0 or other digits in the range of 0-9.

A vector variable [A-Z, AA-ZZ] can be entered. Also shown by an A notation.

~r invokes Network Call Redirection (NCR) over the incoming trunk.

~r+ invokes NCR with E.164 numbering notation for incoming SIP trunking when required by the service provider.

Requirements and considerations

The requirements and considerations for using vector variables with the route-to command are as follows:

  • A variable can be used in the number field as the destination address for the route-to command. When the route-to number [A -Z, AA-ZZ] step is executed, the current numerical value or assignment of up to 16 digits is used for the destination. The variable is defined in the Variables for Vectors screen.

  • A variable can be used in place of digits with all the possible special characters and digits entered before the variable.

  • If the vector variable or resultant destination is not defined or is invalid, the route-to step fails, a vector event 38 (variable not defined) is logged, and vector processing continues at the next vector step. The destination number retrieved from the string of digits of the current value of the variable must be a valid destination as defined by the Communication Manager dial plan. Otherwise, the route-to command fails the vector event is logged, and vector processing continues at the next step.