Hello,
by using rtpengine_manage() only in a branch_route when one has in mind that is about engaging rtpengine for an outgoing request (e.g., INVITE, UPDATE, ...), then it should not be anything complex, imo.
I actually think is a rather bad practice that rtpengine functions (being _manage()/_offer()/_answer()) are used anywhere else than a branch_route for outgoing requests. For example, using it inside request_route compromises any sane serial/parallel forking.
If you have mixed calls with initial as well as late SDP offer, I think using _offer()/_answer() functions can lead to a more complex configuration file rather than being careful where rtpengine_manage() is used.
Cheers, Daniel
On 25.06.25 13:48, Alex Balashov via sr-users wrote:
Hi Johannes,
I have run into this issue as well; rtpengine_manage() can't resolve its context in certain complex cases (e.g. async), and one must revert to more explicit _offer() / _answer() calls.
I actually tend to avoid rtpengine_manage() nowadays except in very, very simple scenarios, because it's easier not to think about it. :-)
-- Alex
On Jun 25, 2025, at 7:32 AM, Johannes Westhuis via sr-users sr-users@lists.kamailio.org wrote:
Hi Daniel,
thanks for pointing that out. I stopped using rtpengine_manage and instead used rtpengine_offer and it seems to solve the problem.
Best Regards, Johannes __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org 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!
-- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com, https://www.csrpswitch.com Tel: +1-706-510-6800
Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org 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!