[SR-Users] Re: Sequential fork with different Call-Ids

2023-11-07 Thread Ben Kaufman via sr-users
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

[SR-Users] Re: Sequential fork with different Call-Ids

2023-11-07 Thread Yuriy G via sr-users
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

[SR-Users] Sequential fork with different Call-Ids

2023-11-07 Thread Vanderlei Torres Batistela via sr-users
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

[SR-Users] Re: 3xx is not relayed to the caller if there are 2 or more branches in the transaction

2023-11-07 Thread Михаил Горюцкий via sr-users
Unfortunately this didn't help me. The message is still only saved, but not forwarded. Judging by the code of the TM module, branch 0 of the transaction is “blind”. After t_should_relay_response() the message is saved in uac and that’s it... the processing process, as I understand it, is

[SR-Users] Redis issue when getting results in Kamailio

2023-11-07 Thread Ali Taher via sr-users
Hello all, I have redis database where the data is inserted in JSON format: #Redis Command JSON.GET Index1J:12345678 #Redis Result [ { "SupplierID": "7", "BCode": "987654", "Rate": 0.159 }, { "SupplierID": "7", "BCode": "765432", "Rate": 0.159 }, {