Hi Doug,
if you have:
rewritehostport("192.168.10.7:5060"); t_on_failure("2"); t_relay();
failure_route[2] { rewritehostport("192.168.10.7:5060"); append_branch(); t_relay(); }
you do serial forking - try first destination and if fails, o for the second one.
for:
rewritehostport("192.168.10.7:5060"); append_branch("192.168.10.7:5060"); t_relay()
you do parallel forking - the request will be sent in the same time to all destinations.
regards, bogdan
Douglas Garstang wrote:
I'm having a terrible time trying to get failure routes to work. Can someone point me to some USEFUL examples please? The examples that come with OpenSER are trivial. They all use append_branch("sip:user@domain") which in the real world is barely useful. I need to try sending messages to a specified host with the current user's URI.
For example, is this the correct usage for trying to connect in sequence to multple destinations?
rewritehostport("192.168.10.7:5060"); append_branch(); t_on_failure("2"); t_relay();
failure_route[2] { rewritehostport("192.168.10.7:5060"); append_branch(); t_relay(); }
The second route is never tried. In general, what should I be doing here? Which is correct?
rewritehostport(ip-addr) append_branch() t_relay()
or maybe... append_branch(ip-addr) t_relay()
or maybe... append_branch(ip-addr1) append_branch(ip-addr2) t_relay()
Do you get my point? The docs are really bad and don't cover exactly how this stuff is supposed to be implemented! if I do a google search on this stuff, I get almost no matches. There's no books either. I'm out of ideas.
I'm just trying to connect to multiple destinations in sequence....
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users