SARK UCS/MVP Change Route Panel

SARK UCS/MVP Change Route Panel is the place where Route entities are modofied.

Active:

Description - Dropdown which determines the Route's state. If the route is made inactive it will take no part in the configuration.
Permissable values - YES/NO.
Default - YES

Primary Path:

Description - Drop down of all trunks on the system. Selected trunk will be the primary choice for this route.
Permissable values - Any valid trunk.
default - None.

Secondary Path:

Description - Drop down of all trunks on the system. Selected trunk will be the secondary choice for this route.
Permissable values - Any valid trunk.
default - None.

Tertiary Path:

Description - Drop down of all trunks on the system. Selected trunk will be the tertiary choice for this route.
Permissable values - Any valid trunk.
default - None.

Quarternary Path:

Description - Drop down of all trunks on the system. Selected trunk will be the quarternary choice for this route.
Permissable values - Any valid trunk.
default - None.

Route Name:

Description - Unique name by which this route is known.
Permissable values - Any valid contiguous single alphanumeric string.
Default - Required.

Route Dial Plans:

Description - One or more dial plans to which this Route is sensitive.
Permissable values - Any valid Asterisk dial string. Multiple strings may be specified, separated by whitespace.
Default - required
Example - _0XXXXXXXXXX _00XXXXXXXXXXXX

Alternate:

Description - Alternate number to be dialled after route failure.
Permissable values - Any valid national or local telephone number.
Default - none
Explanation - The alternate route serves the following purpose. Let's asume that we are attempting to route a local extension between remote offices but the internet links have failed. The alternate, if present, will be used to attempt a dial using the external (POTS) number of the remote location. The AGI will load the alternate number into the DNID and return control to Asterisk in the appropriate context for the cluster (or default if no cluster is specified). The call will then be recusively dealt with through the normal routing system based upon the DNID. If a POTS line is available to the route then it will be used. If there are stili no routes to the destination then the call will be dropped and a congestion tone generated.

Description:

Description - Free form description for this entry.
Permissable values - Any valid alphanumeric string.
Default - required

Cluster:

Description - Which Cluster this Route is a member of.
Permissable values - Any value from the dropdown.
default - default cluster.