7 Jan
2009
7 Jan
'09
7:11 p.m.
On Wednesday 07 January 2009, Juan Asencio wrote:
Hi Juan,
yes, you need to do this in the cfg. You can use a static setup, like having
three different failure_routes that goes over three domains. Another option
is to load the failure routes from the DB, then you would need only one
failure route, but need to setup this in the DB. Take a look to the example
1.18 in the cr README about how to use the cr_next_domain function.
Cheers,
Henning
you don't
need to combine all carriers together. If you want to priorize
over different carriers, then i'd suggest you also use them in cr. For
example something like this:
- carrier premium; domain 0, 1, 2; GWs a1, a2, a3, b1, b2, b3..
- carrier standard; domain 0, 1, 2; GWs A1, A2, A3, B1, B2, B3..
Then you could use different domains to implement your failover over the
different GWs. And also of course do your prefix matching to route your
calls to the best GW.
If you want to use only one carrier, then you also could just load the
domain with DB avpops from some table, and just give the AVP to the
cr_route function. You don't need to use the cr_user_carrier function,
this is provided mainly for convinience and backward compatiblity.
[..]
So to do the failover over the different gw's, has to be done on the
configuration file? As [fail route xx]..