AM
To: Kaufman
Cc: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Re: How to make a branch trigger persistent (still
being active after failure route is triggered)?
Hi
> Try quoting the pseudovariable?
>
>t_on_branch("$avp(broute_trigger)");
Does this mak
Hi
> Try quoting the pseudovariable?
>
>t_on_branch("$avp(broute_trigger)");
Does this make he variable more 'constant'? :-)
I already built a switch/case contruct around it on a
REARM_B_TRIGGER route which I now call in every failure route.
--
Mit freundlichen Grüssen
-Benoît Panizzon-
Try quoting the pseudovariable?
t_on_branch("$avp(broute_trigger)");
Kaufman
-Original Message-
From: Benoît Panizzon
Sent: Friday, December 16, 2022 10:28 AM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Re: How to make a branch trigger persistent (s
Unfortunately, I don't believe PVs can be interpolated into any route names in
this type of usage.
> On Dec 16, 2022, at 11:28 AM, Benoît Panizzon wrote:
>
> I tought I had found the solution:
>
> request_route
> {
>
> $avp(dispgroup) = 2001;
> $avp(broute_trigger) = "BR_TO_NATIONAL";
> t_on_
Hello Benoît,
Whatever you modify on a branch, is local to the branch.
The idea is that for parallel forking one might want to send out the
INVITE in different formats.
When the call fails, in the failure route you work on the original
INVITE and you can reformat the outgoing INVITE (it's like a f
Try to re-arm the branch route (t_on_branch(...)) in your failure_route.
> On Dec 16, 2022, at 10:57 AM, Benoît Panizzon wrote:
>
> Hi List
>
> Some time ago, during my learning curve with kamailio, I learned that a
> branch route is where you make modifications to callerId's.
>
> So I extensi
I tought I had found the solution:
request_route
{
$avp(dispgroup) = 2001;
$avp(broute_trigger) = "BR_TO_NATIONAL";
t_on_branch($avp(broute_trigger));
route(DISPATCHCALL);
[...]
$avp(dispgroup) = 2002;
$avp(broute_trigger) = "BR_TO_INT";
