Kamailio change rtpengine in mid-cal

I am encountering an issue regarding how Kamailio handles rtpengine node
failures mid-call, and I would like to clarify the expected behavior.

*The Scenario:* I have a setup with multiple rtpengines (e.g., 4 nodes) all
configured in the same pool with setid=0.

   1.

   An initial INVITE arrives, and Kamailio successfully selects
   *rtpengine-A* for the call.
   2.

   Later in the dialog, a re-INVITE occurs.
   3.

   Coincidentally, *rtpengine-A* is unavailable at that exact moment.
   4.

   Kamailio then automatically switches to a different rtpengine node in
   the set.

*The Question:* Based on my reading of an older issue (#2713
<https://github.com/kamailio/kamailio/issues/2713>), my understanding was
that Kamailio should *not* change the rtpengine node mid-call, as a new
node will not have the media state for the ongoing session.

Could you please confirm if my understanding is correct, or if Kamailio’s
default failover behavior for mid-call transactions has changed recently?


Thank you for your time and insights!

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!