lsserver

lsserver [-v loglevel] <-p provisionserver> <-s Authentication Mechanism>

Source code is available for the Linux operating system.

lsserver is a location server that uses the TRIP protocol to route.

• TRIP (RFC 3219) implementation.
• Allows integration of configurable local policy data.
• Includes a Decision Manager for the decision process.
• Can be started within a proxy server.
• Mutli-threaded.

-v loglevel
Specifies the log-level to be printed as the program is run.

The name of the Provision Server that provides the LS's policy data is a required command line argument. Data can be specified either by using a text configuration files or a MYSQL database. The choice between the text files and the database can be made at compile time with the macro USE_MYSQL in the makefile.

If a MYSQL database is used to provide local policy data, you can find the stucture of the database here.

The following files are needed if configuration files are being used to give policy data (* denotes the name of the PS- sample files can be viewed by clicking the link):

*Req.txt
Contains the information needed to launch the LS. Includes the host, the port the LS runs on, the mode it is capable of running in (send-only, receive-only, or send-and-receive), and the value of its ITAD.

*Peers.txt
Indicates the peer nodes of the LS. Peers are specified by their host and port.

*LocRoutes.txt
Specifies local routes to be injected into the Decision Process when the LS starts up.

*Protocol.txt
This contains the names of the protocols supported by the LS (SIP or H323).

*AddrFamily.txt
This contains the names of the address families supported by the LS (POTS or Routing Numbers).

*Timers.txt
These are the timer values the LS uses during routing. If one of the timers are not specified, a default value (based on BGP) is used.

*LocPolicy.txt
Contains local policies that the LS must enforce while routing. These policies are totally optional, and are represented by regular expressions. In this file the following things can be configured: (a) A local preference value to be used in intra-ITAD routing.
(b) A metric value to be used for routing.

Eva Nautiyal

Some of the files have been written by James Lee and Amit Kaul at Columbia University, Department of Computer Science.