On Wednesday, September 14, 2016 3:11:08 PM CDT Paul Smith wrote:
> Hi,
> I am struggling to figure out variable scope in branches and
> branch_failure_routes. Is there a way to store a variable in a branch
> route so that I can then read it from the branch failure route if that
> branch fails? A
Makes sense. I thought I was missing something. Hash table will work well.
Thanks Daniel.
> On 14 Sep 2016, at 15:36, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> there is no variable that is stored in the scope of the branch. What you can
> use is a hash table and compose the key from
Hello,
there is no variable that is stored in the scope of the branch. What you
can use is a hash table and compose the key from callid and branch index
variables with expires that is same as transaction lifetime (max
retransmission timeout).
And indeed you need to 'touch' the r-uri in order to s
Hi,
I am struggling to figure out variable scope in branches and
branch_failure_routes. Is there a way to store a variable in a branch route so
that I can then read it from the branch failure route if that branch fails?
Also does writing $ru in branch_failure_route append a branch?
For exampl
