6 Dec
2004
6 Dec
'04
2:55 p.m.
the failure_route needs to be more complex than that -- you need to
introduce a new branch to the destination set.
-jiri
At 01:51 PM 12/6/2004, Steve Blair wrote:
Has anyone been able to get this suggestion to work? I
tried adding
the t_on_failure and t_relay_to_udp to my 0.8.14 stable system but
the call does not failover.
I tested it by reloading the primary gateway just before a call. Therefore
the gateway is unreachable not just unresponsive. I would have expected
the call to be relayed to my second gateway but that did not happen. Is
there more to making the failover work than just the suggestions listed
in the previous message?
Thanks,Steve
Andrei Pelinescu-Onciul wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
On Nov 25, 2004 at 16:44, Razvan Nemesiu
<forum(a)netconnect.ro> wrote:
--
ISC Network Engineering
The University of Pennsylvania
3401 Walnut Street, Suite 221A
Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001
fax: 215-898-9348
sip:blairs@upenn.edu
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hi,
I want to make a ser backup route.I have a route for examples that
forwards the calls to a specific ip destination.I want to make a backup
route to send those calls to another ip destination whenever the first ip
destination is not available (Not Found ,etc.).
Use a failure route.
E.g.:
t_on_failure("1");
t_relay_to_udp("ip1");
break;
...
failure_route[1]{
t_relay_to_udp("ip2");
};
Andrei
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers