Least Cost Routing
Program 50-900 ~ 919 LCR Exception/Override Code Route Plan Assignment
5-12
Strata DK40 Programming Manual Spring 1999
Route Plan Overview
Four different programs are used in conjunction to define the separate LCR route plans.
The Strata DK40 will support up to 8 route plans. They are
. The
purpose of the plan scheme is to provide the system with directions for routing all possible
calls, made by all possible users at all possible times of day. 8 separate plans provide the
customer flexibility enough to route different dialling codes and exception/override codes
over different line groups.
Initialised data assigns all codes dialled to Plan 8. As soon as any codes are assigned in
Programs 51 for Plans 1 ~ 7 these will be removed from route Plan 8. Likewise, any phone-
number not specified in Routes 1 ~ 7 automatically stays in route Plan 8.
Tables for Programs 51, 53 and 54 have room to enter the data for LCR Route Plan Numbers
1 ~ 8. The following instructions reveal how to fill in the individual tables. Each of the
following program tables must be completed for all plans.
You must first establish what type of calls each station group (
Program 56
) will need to
make and which carriers they are to follow. Once the codes to be dialled are grouped these
are entered into
which establishes your Route Plans.
You then need to take into consideration the different times of day the calls are likely to
be made and if any savings can be made by routing the calls over different carriers (
). Once the schedules have been set up, the number dialled, by way of
the Route Plan, the time of day and the station group is routed out over one or more of the
Route Definitions. This facilitates that in the eventuality of one carrier being busy, by having
allocated a second route definition, the user could make the call using an alternative carrier.
For example if the code 01932 was allocated to Route Plan 1, and a user belonging to station
group 1 was to dial 01932-XXXXXX they could be told as Route Definition 1, to first try the
lines in group 1 using modified digits table 1, but if this route was busy, having been allocated
Route Definition 2 also, use the lines in group 2 which also use modified digits table 1. So
although the usual lines for outgoing access were busy, this allowed them to use other lines
but still be routed out over the same carrier.
Equally if it was more likely for the carrier to be busy the system could be set up so that if
Route Definition 1 of Route Plan 1 sent calls out using trunk group 1 and modified digits
table 1, Route Definition 2 of route Plan 1 could still use the trunks in group 1, but route the
call out using modified digits table 2 which accessed an alternative carrier.
If the stations were not to be given an alternative Route Definition to follow, but cost savings
could be made using different carriers for different times of the day Schedule 1 of Route plan
1 could follow Route Definition 1 i.e. access the lines in group 1 and the carrier as accessed
by modified digits table 1 whereas Schedule 2 for Route Plan 1 could follow Route Definition
2 i.e. could still access the lines in group 1 but a different carrier by using a different modified
digits table e.g. Modified Digits Table 2.
