Jakihiko created an issue (kamailio/kamailio#4756)
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, eg: **rtpengine-B**
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?
Note: I don't setup or trying to do anything with High availability. All
rtpengine are run independently without knowing others
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4756
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/[email protected]>
_______________________________________________
Kamailio - Development Mailing List -- [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!
