Brett Nemeroff wrote:
> You should be able to track this with avps. What version are you running? I
> know that in at least the newer versions of opensips, this
> is definitely supported:http://www.opensips.org/Resources/DocsCoreVar14
> "The AVPS will be visible in all routes where any message (reply or request)
> of the transaction will be processed - branch_route , failure_route,
> onreply_route (for this last route you need to enable the TM parameter *
> onreply_avp_mode*)."
Thanks. I don't have the config or the logs at hand at this moment but I
tried something like this yesterday:
failure_route[1] {
if (!isflagset(31)) {
$avp(i:500) = 1; # Initialize counter of failed attempts
setflag(31);
} else {
$avp(i:500) = $avp(i:500) + 1; # OR:
# avp_op("$avp(i:500)", "add/1");
}
if ($avp(i:500) > 2) {
t_reply("503", "Couldn't complete the call");
exit;
}
if (next_gw()) {
t_on_failure("1");
t_relay();
} else {
t_reply("503", "No gateways");
exit;
};
}
As a result of incrementing AVP variable, no matter which way, the
OpenSIPS sends out some junk and then crashes... I'm using 1.4.4.
--
Sincerely,
Andrew Pogrebennyk
PortaOne, Inc., QA Engineer
andrew.pogreben...@portaone.com
Tel: +1-866-SIP VOIP (+1 866 747 8647) ext. 7133
Meet us on June 1-3 at ITW, Booth 802
Marriott Wardman Park Hotel, Washington, DC
http://www.internationaltelecomsweek.com/
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
