<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: courier,monaco,monospace,sans-serif; font-size: 10pt;">><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">>Douglas
Garstang
writes:<br>><br>
>>
I'm
surprised
no
one
has
written
a
better
module
for
this.
In
the<br>
>>
realworld,
you
have
multiple
POPs,
your
carriers
also
have
multiple<br>
>>
POP's,multiple
gateways.
In
the
event
you
get
a
failure
with
one<br>
>>
carrier,
youprobably
want
to
switch
to
the
next
cheapest
carrier,
not<br>
>>
anothergateway
within
the
same
carrier
(as
it
will
probably
just
fail<br>>>
again).When
selecting
a
carrier
gateway,
you
need
to
choose
the
best<br>
>>
POP
touse
before
you
select
the
trunk.<br>><br>>it
might
be
possible
for
you
to
achieve
what
you
describe
using
existing<br>>lcr
module
by
having
only
one
gw
per
group
and
then
assign
priorities
in<br>>lcr
table
in
such
a
way
that
for
prefix
+xx
highest
priority
is
gw
group<br>>1
of
the
cheapest
carrier,
then
gw
group
1
of
second
cheapest
carrier,<br>>then
gw
group
2
of
cheapest
carrier
and
finally
gw
group
2
of
second<br>>cheapest
carrier
(assuming
two
carriers
serving
+xx).<br><br>Juha,<br><br>Thanks. I went through that option yesterday. As we have 6 instances of OpenSER running, I would need to have SIX routes defined in the lcr table for a single prefix. For example (IP's modified):<br><br><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">mysql> select * from lcr;</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">+----+--------+---------------+--------+----------+</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| id | prefix | from_uri | grp_id | priority |</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier
New,courier,monaco,monospace,sans-serif;">+----+--------+---------------+--------+----------+</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| 8 | 1303 | @203.84.213.8 | 1 | 1 | </span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| 9 | 1303 | @</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">203.84.214.8</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> | 2 | 1 | <br></span></font><font size="2"><span style="font-family: Courier
New,courier,monaco,monospace,sans-serif;">| 10 | 1303 | @</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">203.84.215.8</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> | 3 | 1 | <br></span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| 11 | 1303 | @</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">203.84.216.8</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> | 4 | 1 | <br></span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| 12 | 1303 |
@</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">203.84.217.8</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> | 5 | 1 | <br></span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">| 14 | 1303 | @</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">203.84.218.8</span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"> | 6 | 1 | </span></font><font size="2"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier
New,courier,monaco,monospace,sans-serif;">+----+--------+---------------+--------+----------+</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></font><br>.... All that .... six rows for a single prefix. Of course, we have thousands of routes for each of our providers... off the top of my head, we have about 17,000 routes between Teleglobe and Verizon... multiply that by 6 and you have almost 120,000 routes. Apart from the administrative hassle, can OpenSER handle 120,000+ routes in the lcr table ok?<br><br>Our providers also have sometimes have several gateways in a single POP. However, we don't want to actually try and route calls to every single gateway in a POP, just a few of them. The LCR module doesn't seem to have a way to skip to the next lcr route. Can it do that? If it can't, we have to try every single gateway in a POP before skipping to the next carrier, which just isn't feesible.<br><br>Doug.<br><br><br>--
juha<br><br></div><br></div></div><br>
<hr size=1>Looking for last minute shopping deals? <a href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping">
Find them fast with Yahoo! Search.</a></body></html>