Technical Communication

TC1483

Product: Alcatel-Lucent OmniPCX Office

Subject:

Ed 01

Date : 24/05/2011
Nb. of pages: 5

Dynamic routing according time ranges on OmniPcx Office

1. How to program dynamic routing to different destinations, according

time ranges
This document describes an example on how we can program dynamic routing to different
destinations according time ranges. The principle is based on ARS tables, ARS time ranges and "local"
function.
Once this notion has been understood, this principle may be used for other needs and other different
types of call forwarding.
Example of use:
>> Program a dynamic routing to different extensions according time ranges;
- Dynamic routing of extension 119 to extension 100 for time ranges 8:00 to 12:00 and
14:00 to 18:00, Monday, Wednesday and Friday.
- Dynamic routing of extension 119 to extension 101 for time ranges 8:00 to 12:00 and
14:00 to 18:00, Tuesday and Thursday.
- Dynamic routing of extension 119 to extension 102 for all time ranges for Saturday and
Sunday, and time ranges 18:00 to 08:00 and 12:00 to 14h00 all other days.

2. Programming description:
- Add a line in "Internal numbering plan" table, in order to call a virtual destination "590", using
"secondary trunk group" function with "Base ARS" and "TMN Keep"
"590" as an example, may be any number to reach the "ARS" table.

- Add several lines in "ARS table prefixes" for prefix 590, to,the different destinations (extensions):
100, 101, 102, in our example: When we will call 590, the call will go to 100, 101 or 102:
Product: Alcatel-Lucent OmniPCX Office

1 /5

Article TC1483 Ed 01

- Add several virtual "destinations" in "Providers/Destination" table corresponding to the different

destinations according different time ranges; this table is used as references to access destinations;
name could be anything;
In our example, we simply enter names reminding the different extensions (destinations).

- Add trunk groups "trunk group lists" table corresponding to the different "Providers/destinations"
created in the previous step:
>>> Index "local" is used to send digits to "Internal Numbering Plan"

- Manage the "Day groups" (day's 1 to 7 and day groups1 to 7) in "Day groups" table:

In our example, Saturday and Sunday belongs to "day group 3", Monday, Wednesday and Friday
belong to "day group 1" and Tuesday and Thursday belong to "day group 2".
- Create the time ranges in "Hours" table (ARS time range table):

Product: Alcatel-Lucent OmniPCX Office

2 /5

Article TC1483 Ed 01

- In our example we manage 4 time ranges; for each time range we need to assign the "virtual
destination" (created in "Providers/destinations" table), corresponding to the "day's group":
- Time range 1 from 08:00 to 12:00
- For day's group "1": to "extension 100" defined in "day's group 1" (for Monday,
Wednesday and Friday)
- for day's group "2": to "extension 101", defined in "day's group 2" (for Tuesday and
Thursday)
- For day's group "3": to "extension 102" defined in "day's group 3" (for Saturday and
Sunday)
- Time range 2 from 12:00 to 14:00
- For day's group "1": to "extension 102" defined in "day's group 1" (for Monday,
Wednesday and Friday)
- For day's group "2": to "extension 102", defined in "day's group 2" (for Tuesday and
Thursday)
- For day's group "3": to "extension 102" defined in "day's group 3" (for Saturday and
Sunday)

Product: Alcatel-Lucent OmniPCX Office

3 /5

Article TC1483 Ed 01

- -Time range 3 from 14:00 to 18:00

- For day's group "1": to "extension 100" defined in "day's group 1" (for Monday,
Wednesday and Friday)
- For day's group "2": to "extension 101", defined in "day's group 2" (for Tuesday and
Thursday)
- For day's group "3": to "extension 102" defined in "day's group 3" (for Saturday and
Sunday)
- Time range 4 from 18:00 to 08:00
- For day's group "1": to "extension 102" defined in "day's group 1" (for Monday,
Wednesday and Friday)
- For day's group "2": to "extension 102", defined in "day's group 2" (for Tuesday and
Thursday)
- For day's group "3": to "extension 102" defined in "day's group 3" (for Saturday and
Sunday)
The last point to solve: any call forwarding to the virtual destiantion"590" will be refused,
because it is not a terminal (only immediate call forwarding will be accepted using OMC).
As a work around, we will use a speed dialling number "8000" for instance to be
programmed in "Common speed dialling" table referencing to "590":

Thanks to this speed dialling number "8000"we will be able to enable the "dynamic

routing": to 590:

Product: Alcatel-Lucent OmniPCX Office

4 /5

Article TC1483 Ed 01

Because the speed dialling number is considered as an external destination, we also have to
enable "external diversion" feature rights for terminal "119":

Note:
- Using this type of dynamic call forwarding, extension 119 will stop ringing after the time out
of dynamic routing: only the destination will ,ring.
- During tests, the jump from a time range to another must be done by the system itself:
adjust the system clock to 1 or 2 minutes before the next time range; when the time range has
changed, wait a minimum of 1 minute.
- This solution may be used for different type of call forwarding.

End of document

Product: Alcatel-Lucent OmniPCX Office

5 /5

Article TC1483 Ed 01