Hello all,
I have a scenario on wich requires sequential fork (up to 30 possible destinations) with different Call-ID for each leg. I am using topoh module enabled, but it always puts the same Call-ID. Someone have a solution for this scenario?
Regards
In general - it is not how forking meant to be according rfc3261, and it is noylt a job for the sip Proxy. But, if you would like to have X parallel calls you probably can do some work around with UAC module. However: meeging management is on you then
On Tue, 7 Nov 2023, 19:04 Vanderlei Torres Batistela via sr-users, < sr-users@lists.kamailio.org> wrote:
Hello all,
I have a scenario on wich requires sequential fork (up to 30 possible destinations) with different Call-ID for each leg. I am using topoh module enabled, but it always puts the same Call-ID. Someone have a solution for this scenario?
Regards
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
The short answer is that Kamailio is a SIP proxy, and what you're describing is a Back to Back User Agent (B2BUA), so there's no easy direct way to do this. It's also worth noting that the default config for kamailio's max_branches is 12 and has an upper limit of 31.
A better question might be why you need a separate call-id for each call. Kamailio will generate a new branch parameter for the via's that it adds, so this shouldn't be necessary.
Regards, Kaufman.
From: Vanderlei Torres Batistela via sr-users sr-users@lists.kamailio.org Sent: Tuesday, November 7, 2023 11:36 AM To: sr-users@lists.kamailio.org Cc: Vanderlei Torres Batistela v.batistela@hotmail.com Subject: [SR-Users] Sequential fork with different Call-Ids
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.
Hello all,
I have a scenario on wich requires sequential fork (up to 30 possible destinations) with different Call-ID for each leg. I am using topoh module enabled, but it always puts the same Call-ID. Someone have a solution for this scenario?
Regards
Hi
I have a scenario on wich requires sequential fork (up to 30 possible destinations) with different Call-ID for each leg. I am using topoh module enabled, but it always puts the same Call-ID. Someone have a solution for this scenario?
AFAIK that is not possible as Kamailio, being a proxy, will never generate a new Call-ID.
I had the same issue. I have a core, which takes care or routing and gathering CDR for billing (using the dialog module) and a registrar which takes care of registration, location service and call forwarding.
Call Forwarding happens on the registrar for example on destination busy.
So if a call takes the route Core => Registrar (CFW engaged) => Core
I also would have loved to get a different CDR for that 2nd leg on the Core, so I have one to bill to the origin of the 1st leg and one to bill to the origin of the 2nd leg.
I had to add a 'leg_history' variable to my CDR where I keep track of how many legs are present and who originated which leg, so I can split this in multiple CDR in the rating backend.
Mit freundlichen Grüssen
-Benoît Panizzon-
-
Ben Kaufman -
Benoit Panizzon -
Vanderlei Torres Batistela -
Yuriy G