<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-size: 10pt;">><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">><br>
>On
Tue,
March
25,
2008
3:24
am,
Ovidiu
Sas
wrote:<br>>>
The
database
config
is
right
in
the
README
file.<br>>><br>>>
Here
are
the
trees:<br>>>
[..]<br>>>
I
agree
with
you
that
the
names
are
confusing
:)<br>>>
You
may
or
may
not
need
to
use
the
subscriber
tables,
based
on
what<br>>>
functions
are
you
using.<br>>>
In
the
example
that
I
gave
you,
you
don't
need
the
location
table.<br>>>
Instead,
you
force
a
routing
tree
(in
my
example
is
the
"default"<br>>>
tree).<br>><br>>Hi,<br>><br>>yes,
they
are
probably
still
a
few
things
in
the
whole
module
terminology<br>>that
are
not
adequate
explained,
even
if
the
documentation
has
already<br>>seen
quite
a
lot
of
work.
As
this
module
can
be
used
to
implement
pretty<br>>complex
scenarios,
the
documentation
shows
this
too,
unfortunately.<br><br>Complex scenarios? To change the carrier mid-call, you need to hard code it. Why isn't there a function which retrieves the next carrier from the database, rather than having to hard code it? There is also NO lcr at all. We absolutely need lcr. It also seems you are limited to a maximum of two carriers?<br><br>><br>>You
need
only
data
from
a
user
specific
table,
e.g.
subscriber
if
you
need<br>>to
implement
user
specific
routing.
e.g.
choose
carrier
A
for
one
user<br>>set,
carrier
B
for
another
one..
If
you
don't
need
this,
then
you
not
need<br>>to
load
data
from
this
table.<br><br>What about multiple carriers per user with LCR and multiple gateways?<br><br>><br>>You
have
a
list
of
carriers
in
your
routing
space,
and
each
of
them
can<br>>have
again
a
list
of
domains.
As
every
domain
can
route
also
to
many<br>>different
prefixes
(with
several
hosts
per
prefix),
this
module
refers
to<br>>them
as
"trees".<br><br>A list of carriers is fine, but how do I switch carriers without hard coding the carrier in the cr_tree_rewrite_uri() function? Using a simple example, using carrierroute, if we where calling say prefix 1303, we'd have to call cr_tree_rewrite_uri('Verizon'), and then if Verizon fails, and we do failover, call cr_tree_rewrite_uri('Teleglobe'). See the problem here? The carriers are hard coded in the openser.cfg file, and there's no LCR. What am I missing? It can't be that horrible.<br><br>><br>>If
you
want
to
implement
simple
LCR,
then
you
don't
need
the
functions<br>>that
allows
you
to
choose
a
carrier.
Again,
i
agree
that
the
actual<br>>interface
in
the
stable
branch
is
a
little
bit
cumbersome
to
use,
the
new<br>>interface
currently
in
development
will
be
hopefully
address
some
of
this<br>>issues.<br><br>The LCR module seems to suit our need better, but the number of routes is hard coded in the code to 256. Why is that? We use several carriers, and each has THOUSANDS of routes. Verizon for example has about 10,000 routes and Teleglobe has about 7,000 routes. Why is the limit so low? I increased the limit in lcr_mod.c, and increased the size of the private and shared memory, which allowed the lcr table to load, but what are the correct values? How do I know that it won't run out of memory? If that happens, do I just increase the private and shared memory?<br><br>Doug<br><br></div></div></div><br>
<hr size=1>Never miss a thing. <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a></body></html>