In that case, I'm not sure what to suggest other
than keeping your own
data (keyed by Call-ID, say) in 'htable', for
instance.
I'm guessing this will be necessary, I will give it a try.
Thanks again
On Sun, Apr 24, 2016 at 5:25 PM, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
> That's a good point. I didn't think about the scenario too carefully. When
> a timeout triggers a failure_route, it's a branch failure--rather more
> abstract than a transaction timeout. So, transaction variables may not be
> in scope for it.
>
In that case, I'm not sure what to suggest other
than keeping your own
> data (keyed by Call-ID, say) in 'htable', for
instance.
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
> 1447 Peachtree Street NE, Suite 700
> Atlanta, GA 30309
> United States
>
> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> Web:
http://www.evaristesys.com/,
http://www.csrpswitch.com/
>
> Sent from my BlackBerry.
> Original Message
> From: Marrold
> Sent: Sunday, April 24, 2016 12:21
> To: Kamailio (SER) - Users Mailing List
> Reply To: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] Using flags in t_branch_timeout() section of
> failure_route{}
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>