Hi Brett,

The error log you get is triggered when the internal function "next_branches" returns false (a negative code). This is when:
   - function called from wrong route type (like for a reply)
   - there are no more branches left
   - internal error

I guess in your case, the second case (when there are no more branches) is the trigger. And indeed, in this case, the error message is bogus - we need to fix that.

Regards,
Bogdan

Brett Nemeroff wrote:
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
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
OpenSIPS solutions and "know-how"



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to