All,
I'm routing calls using 3XX redirects. I serialize the branches. I
immediately call a next_branches() and arm a failure_route. In the failure
route I do something like:
if (!next_branches()) {
t_reply("503","Service Unavailable ");
exit;
}
To catch the end of the list of rollover options.
I see in my log:
Jan 29 09:23:50 sip1 /usr/local/sbin/opensips[21262]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:51 sip1 /usr/local/sbin/opensips[21271]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:52 sip1 /usr/local/sbin/opensips[21266]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:52 sip1 /usr/local/sbin/opensips[21269]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:52 sip1 /usr/local/sbin/opensips[21259]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:52 sip1 /usr/local/sbin/opensips[21263]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:53 sip1 /usr/local/sbin/opensips[21265]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:53 sip1 /usr/local/sbin/opensips[21253]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:54 sip1 /usr/local/sbin/opensips[21266]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:56 sip1 /usr/local/sbin/opensips[21262]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:57 sip1 /usr/local/sbin/opensips[21271]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:57 sip1 /usr/local/sbin/opensips[21267]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:57 sip1 /usr/local/sbin/opensips[21269]: ERROR:core:do_action:
next_branches failed
Jan 29 09:23:58 sip1 /usr/local/sbin/opensips[21252]: ERROR:core:do_action:
next_branches failed
Over and over. Is there some sort of test I should be doing prior to
calling next_branches? or is the log level just too high on that message?
Thanks!
-Brett
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
