Technical information

LEAST COST ROUTING
133
LCR rules file
The LCR rules file (lcrrules.lst) is used to associate a country code and area code to a route name and is
located in the vsifax/lib directory.
The following is an example of an LCR rules file.
# Sample LCR rules file
#
# <dial_string-skeleton>:<route_owner>
#
# US rules (by area code)
#
[1]212???????:NewYork
019*:LondonUK
In the first entry of the previous example, the presence of a digit between brackets [ ] indicates that the digit is
optional. That is, any dial string that starts with or without a 1 followed by 212 followed by any seven digits will be sent
through the New York server.
The second entry indicates that any fax sent with the number 019 followed by any digits will be sent through the
London server.
Note
LCR is designed to allow all fax servers to share the same routing and LCR rules files. Once these files are set
up, they must be distributed and copied to all servers in a cluster.
See also
Refer to Command Reference in the Reference Addendum
documentation for additional information.
Using wildcards in the LCR rules file
Entering an asterisk (*) in the LCR rules file tells the system to match any value(s) in that portion of the dial string.
For example, in the file shown in LCR rules file
, the entry 019*:LondonUK tells the system that any dial string
starting with 019 will be routed to London.
Note
We strongly recommend that any entries using the * be placed at the end of the LCR rules file to eliminate the
possibility of routing a fax to the wrong location. For example, if 1*:LosAngeles were the first entry in the file
all the other entries starting with 1 would be ignored. This is because entering the * after the first digit tells the
system that all dial strings starting with a 1 followed by any digits should be routed to Los Angeles.
Question marks (?) can also be used as wild cards to represent exactly one digit. For example, the entry 1714555-
5??? would match any number starting with 1714555 and ending with four digits between 5000 and 5999. Similarly,
the entry 1714??????? would match any number starting with 1714 followed by 7 digits.
Verifying entries in the routes and LCR rules files
LCR requires that for every route in either of the files, a corresponding setup entry must be in the other file. For
example, if you set up an entry in the LCR routes file for the server in New York, you must also have the New York
entry in the LCR rules file. After you complete the setup of the Routes and LCR rules files you can use the following
command to verify that the two files are consistent. Enter:
vlcrchk -cv
This command compares the entries in the LCR routes file to the entries in the LCR rules file. If the system finds a
route entry that does not have a corresponding route in the other file, it will report it, allowing you to correct the
synchronization of the two files.
An additional check you can run is to verify the route name for a specific fax number by entering:
vlcrchk -n xxx-xxx-xxxx