<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<book id="blst" xmlns:xi="http://www.w3.org/2001/XInclude">
    <bookinfo>
    	<title>prefix_route Module</title>
	<authorgroup>
	    <author>
		<firstname>Alfred E.</firstname>
		<surname>Heggestad</surname>
		<affiliation><orgname>Telio Telecom</orgname></affiliation>
	    </author>
	</authorgroup>
	<copyright>
	    <year>2007</year>
	    <holder>Alfred E. Heggestad</holder>
	</copyright>
	<copyright>
	    <year>2008</year>
	    <holder>Telio Telecom AS</holder>
	</copyright>
    </bookinfo>
    <toc></toc>

    <chapter>
	<title>Admin Guide</title>
    <section id="prefixroute.overview">
	<title>Overview</title>
	<para>
	The prefix_route module does routing based on a set of prefixes from the
	database. The prefix rule-set is loaded from the database into a binary
	tree in memory, either on startup or when issuing the "prefix_route.reload" RPC
	command. When calling the "prefix_route()" function from the ser.cfg
	configuration script, it will try to match the user part of the request URI
	with the best matching route. If a route is found, it will be used for
	further processing. If not found normal processing will continue.
	</para>
	<para>
	Development was sponsored by Telio Telecom.
	</para>
    </section>

    <xi:include href="prefix_route_params.xml"/>
    <xi:include href="prefix_route_functions.xml"/>
    <xi:include href="prefix_route_rpc.xml"/>
    <xi:include href="prefix_route_extra.xml"/>
    </chapter>
</book>

