Hi Tyler,
Yes it is. It's on the first part of the page (syntax section).
-Ronald
On Thu, Feb 24, 2011 at 4:35 PM, Tyler Merritt wrote:
> Is this construct in the scripting variables page and I just missed it?
>
> $(rs)
>
> I had no idea you could throw in stuff like that to the variables.
>
>
Hi Dave,
That makes sense. I'll try it out.
-Ronald
On Thu, Feb 24, 2011 at 5:13 AM, Dave Singer wrote:
> Ronald,
>
> The only time I've seen it be null in failure route is if there was no
> reply received,
> you might add a check to see if it was a local timeout:
>
> if ( t_local_replied("all"
Is this construct in the scripting variables page and I just missed it?
$(rs)
I had no idea you could throw in stuff like that to the variables.
On Thu, Feb 24, 2011 at 6:13 AM, Dave Singer wrote:
> Ronald,
>
> The only time I've seen it be null in failure route is if there was no
> reply recei
Ronald,
The only time I've seen it be null in failure route is if there was no reply
received,
you might add a check to see if it was a local timeout:
if ( t_local_replied("all") ) {
xlog("did not get any response");
} else {
xlog("$(ci): $C(rx)failure route: $(rs)
$(rr)$C(xx)\n");
}
Dave
Hi all,
I'm setting up opensips as a stateful proxy, and i have the following
snippet of code on the failure route:
failure_route[1] {
xlog("$(ci): $C(rx)failure route: $(rs)
$(rr)$C(xx)\n");
# Failure route routine...
}
The values of the call-id, response code and reason are normally t
