26 Mar
2008
26 Mar
'08
12:40 a.m.
On Tue, March 25, 2008 3:24 am, Ovidiu Sas wrote:
The database config is right in the README file.
Here are the trees:
[..]
I agree with you that the names are confusing :)
You may or may not need to use the subscriber tables, based on what
functions are you using.
In the example that I gave you, you don't need the location table.
Instead, you force a routing tree (in my example is the "default"
tree).
Hi,
yes, they are probably still a few things in the whole module terminology
that are not adequate explained, even if the documentation has already
seen quite a lot of work. As this module can be used to implement pretty
complex scenarios, the documentation shows this too, unfortunately.
You need only data from a user specific table, e.g. subscriber if you need
to implement user specific routing. e.g. choose carrier A for one user
set, carrier B for another one.. If you don't need this, then you not need
to load data from this table.
You have a list of carriers in your routing space, and each of them can
have again a list of domains. As every domain can route also to many
different prefixes (with several hosts per prefix), this module refers to
them as "trees".
If you want to implement simple LCR, then you don't need the functions
that allows you to choose a carrier. Again, i agree that the actual
interface in the stable branch is a little bit cumbersome to use, the new
interface currently in development will be hopefully address some of this
issues.
Cheers,
Henning