On Fri, Mar 20, 2009 at 4:26 PM, Juha Heinanen jh@tutpro.com wrote:
Iñaki Baz Castillo writes:
> - How to know which gws are down? The only I see is a NOTICE log: > --------- > NOTICE:lcr:gw_set_state: trunk "99.99.99.99:5060" from group: <2> is OFFLINE > --------- > Is not possible a MI command to list the down gateways?
lcr_gw_dump should include information if gw is down:
p = int2str((unsigned long)(*gws)[i].ping, &len); attr = add_mi_attr(node, MI_DUP_VALUE, "PING", 4, p, len); if (attr == NULL) goto err;
value 2 is offline.
> - Why ping_interval cannot be less than 180 seconds?
i don't know. the ping stuff was contributed by another author.
It should be configurable via a param
> - In case of failure_route and "next_gw()", is the used gw (failing gw) > automatically marked as down? (it would be useful so we don't need to > wait "fr_timer" seconds for each request during "ping_interval").
it might be possible to write a function that you could call (from failure route) to mark the current gw offline.
Or/and a function that will return the status of a particular gw. Before relaying, the script can check the availability of the gw and call the next_gw() if neccessary.
Regards, Ovidiu Sas