10 Oct
2023
10 Oct
'23
1:08 p.m.
Probably better to use an xavp with the ruri as the key.
-----Original Message-----
From: Alex Balashov via sr-users <sr-users(a)lists.kamailio.org>
Sent: Tuesday, October 10, 2023 9:53 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: Alex Balashov <abalashov(a)evaristesys.com>
Subject: [SR-Users] Re: Serial Forking with differing next hop for each branch?
CAUTION: This email originated from outside the organization. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
On 10 Oct 2023, at 10:17, Barry Flanagan via sr-users
<sr-users(a)lists.kamailio.org> wrote:
On 10/10/2023 15:09, Ben Kaufman wrote:
This is good if $du is the _only_ branch-specific attribute you need to change besides
R-URI, but would be poor solution if you need support for arbitrary, shifting parameters.
Most call routing systems eventually evolve such.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com/
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to
sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
Would this work: use append_branch() in the
request_route, then in your failure route:
$var(temp_ru) = $ru;
t_next_contacts();
$du = $ru;
$ru = $var(temp_ru);
Unfortunately not, because the $du next hop can be different for each branch, but $ru can
be the same.
Gives me an idea though - perhaps when I call append_branch I can add a tag to the $ru
like ';nexthop=XXX.XXX.XXX.XXX:PPPP' and then extract that in my failure route.