From kiss.zoltan@adertis.hu Tue Jun 13 06:20:06 2023 From: Kiss =?utf-8?q?Zolt=C3=A1n?= To: sr-users@lists.kamailio.org Subject: [SR-Users] Re: Cannot achieve rtpengine HA Date: Tue, 13 Jun 2023 06:19:44 +0000 Message-ID: In-Reply-To: =?utf-8?q?=3CDB9PR05MB82037832F443461348166221E154A=40DB9PR05MB?= =?utf-8?q?8203=2Eeurprd05=2Eprod=2Eoutlook=2Ecom=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2081427179==" --===============2081427179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, You have to move the IP address of the original rtpengine node to the "failov= er" node also. All of the virtual interfaces must exist on both nodes and you have to enable= non local IP bind support in the Linux kernel to achive this. Regards, Zoltan From: Arsenijs Kabihno Sent: Monday, June 12, 2023 9:18 AM To: sr-users(a)lists.kamailio.org Subject: [SR-Users] Cannot achieve rtpengine HA Hello, We are trying to achieve rtpengine HA solely with kamailio and rtpengine modu= le. In the following example call goes to rtpengine node 10.5.0.183:22222 and the= n we stop rtpengine service on this node to simulate failure. Client is triggering re-INVITE, but, apparently, kamailio sticks to initially= selected rtpengine, producing the following errors: Jun 12 06:59:48 ap07stvp.xxxxxxx.xxx docker[9373]: 27(33) INFO: {2 2 INVITE j= dl9kq6fv51jcv1agk2e}