Technical data

7. Client/Server interface imond
Using the imond command “timetable” you can have a look at it.
Here an example:
Supposing 3 circuits are defined:
CIRCUIT_1_NAME='Addcom'
CIRCUIT_2_NAME='AOL'
CIRCUIT_3_NAME='Firma'
Only the first two circuits have a default circuit defined, i.e. the corresponding variables
ISDN_CIRC_x_ROUTE have the value ’0.0.0.0’.
If the variables ISDN_CIRC_x_TIMES look like this:
ISDN_CIRC_1_TIMES='Mo-Fr:09-18:0.0388:N Mo-Fr:18-09:0.0248:Y
Sa-Su:00-24:0.0248:Y'
ISDN_CIRC_2_TIMES='Mo-Fr:09-18:0.019:Y Mo-Fr:18-09:0.049:N
Sa-Su:09-18:0.019:N Sa-Su:18-09:0.049:N'
ISDN_CIRC_3_TIMES='Mo-Fr:09-18:0.08:N Mo-Fr:18-09:0.03:N
Sa-Su:00-24:0.03:N'
it results in the following /etc/imond.conf being created:
#day hour device defroute phone name charge ch-int
Mo-Fr 09-18 ippp0 no 010280192306 Addcom 0.0388 60
Mo-Fr 18-09 ippp0 yes 010280192306 Addcom 0.0248 60
Sa-Su 00-24 ippp0 yes 010280192306 Addcom 0.0248 60
Mo-Fr 09-18 ippp1 yes 019160 AOL 0.019 180
Mo-Fr 18-09 ippp1 no 019160 AOL 0.049 180
Sa-Su 09-18 ippp1 no 019160 AOL 0.019 180
Sa-Su 18-09 ippp1 no 019160 AOL 0.049 180
Mo-Fr 09-18 isdn2 no 0221xxxxxxx Firma 0.08 90
Mo-Fr 18-09 isdn2 no 0221xxxxxxx Firma 0.03 90
Sa-Su 00-24 isdn2 no 0221xxxxxxx Firma 0.03 90
imond creates the following time table in memory – here the output of the imond command
“timetable”:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
--------------------------------------------------------------------------
Su 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
Mo 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2
Tu 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2
We 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2
Th 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2
Fr 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2
Sa 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
No. Name DefRoute Device Ch/Min ChInt
1 Addcom no ippp0 0.0388 60
2 Addcom yes ippp0 0.0248 60
3 Addcom yes ippp0 0.0248 60
268