<div dir="ltr">Hi Liviu,<br><br>Thanks for the patch. However I can't apply it as my OpenSIPS is installed as a binary package and not compiled from source. <br>I've also created an issue on GitHub to track this. <a href="https://github.com/OpenSIPS/opensips/issues/3276">https://github.com/OpenSIPS/opensips/issues/3276</a></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 8 janv. 2024 à 11:13, Liviu Chircu <<a href="mailto:liviu@opensips.org">liviu@opensips.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<div>On 26.12.2023 22:54, James Seer wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Aaaa the good old days before commit 4bd50335a
(2023-12-12 by Vlad Paiu), life was simpler when my vip network
interface and VIP itself were just one happy entity in HOMER's
eyes :P<br>
<br>
<div>This recent commit with its replication to HEP using the
advertised address has complicated things in homer heplify by
treating them as two different entities in the sip sequence
(precisely during ACKs CANCEL and BYEs). Any chance we could
make this an optional feature?<br>
</div>
</div>
</blockquote>
<p>Hi James,</p>
<p>First of all, VIP issue aside, there seems to be a bug in that
patch where the <i>sourceIP</i> and <i>sourcePort</i> are
changed to <i>destinationIP </i>and <i>destinationPort</i>
without a good reason (currently started a discussion with Vlad -
we'll get to the bottom of it). Maybe if this were tweaked, your
SIP flows would return back to looking normal?!</p>
<p>Nonetheless, if you have a 3.3 source tree to work with, try the
following patch onto your root sources directory and see if the
behavior improves by just fixing the bug instead of reverting the
patch:</p>
<p><font face="monospace">git apply <(base64 -d <<EOF |
gzip -dc<br>
H4sIAAAAAAAAA91Ry26DMBA8w1fsqUoCJpCSZ9U0HxD11lMUWcYPZBUwsk3US/+9hiQNOQT13Is9<br>
Hs/ujsdMCgEI5dICmZaKNQU3U6sJ5fqyRRSyRze+rBj/goTN6ex5nq2iKF2ss3XGkiUkcbxIUx8h<br>
9LizHwTBQPfdDtAsSVdhEkNwBY40llhJQVYWjKxxpx8Zqxt6JkqTw8QtIXRXWFZC4RraLeyqCp5j<br>
UZB87IP37YNbDbfYKPqJqSqasjIjYBk+kcIc0mP4i+c9vHBYaFW6eVkjROgjz3Mz0VbTU5S5YDBh<br>
THNj0Jaw07m58xgVvHq7mnW1rQgm46eB0sthc9MwY7GsQ4C/DhzQ1UrbzV3nlglvrWutrBq/+IHn<br>
3RwYTTsHd8SDwuF8l71MVz28dtiqfrpD7x/2/a//pY33GloSHyMHIitL3jLwCi0cvX/s9530B7QY<br>
9NXwAwAA<br>
EOF<br>
)</font></p>
<p>Best regards,<br>
</p>
<pre cols="72">--
Liviu Chircu
<a href="http://www.twitter.com/liviuchircu" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" target="_blank">www.opensips-solutions.com</a>
OpenSIPS Summit 2024 Valencia, May 14-17 | <a href="http://www.opensips.org/events" target="_blank">www.opensips.org/events</a></pre>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>