<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">In such cases, just change the TH prefix, to
avoid confusion between the instances:<br>
<a class="moz-txt-link-freetext" href="https://opensips.org/html/docs/modules/3.6.x/topology_hiding.html#param_th_callid_prefix">https://opensips.org/html/docs/modules/3.6.x/topology_hiding.html#param_th_callid_prefix</a><br>
<br>
Regards<br>
</font>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
<div class="moz-cite-prefix">On 17.07.2025 19:53, Federico Alves
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAC9cSOAZgOi5Ak26ENcPhUK_UZE8=sxO=Nq3reLvu8kAg8rO2g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">What happens is rhis: everybody uses the topplogy
hiding module with the default encryption password. If found
that 2 opensips boxes where the source does topology hiding,
cannot talk to the second box if both boxes have the same
encryption password. The second box will decode the call ID and
respond using the first box client-side call ID. The whole SIP
protocol breaks down. I took down the largest hosted switch
provider in the US.
<div dir="auto">Please let me know if you have any other
questions, via private email.</div>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Thu, Jul 17, 2025, 5:53 PM
Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org"
moz-do-not-send="true" class="moz-txt-link-freetext">bogdan@opensips.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
The only thing you can do is (1) ask the carrier for an
example of such <br>
bogus dialog and (2) investigate the SIP traffic to be sure
that the BYE <br>
exchange with the carrier was correctly done...<br>
<br>
Regards,<br>
<br>
Bogdan-Andrei Iancu<br>
<br>
OpenSIPS Founder and Developer<br>
<a href="https://www.opensips-solutions.com"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.opensips-solutions.com</a><br>
<a href="https://www.siphub.com"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.siphub.com</a><br>
<br>
On 27.06.2025 00:57, Federico Alves wrote:<br>
> So far my engineers use topology_hiding(), and the CallID
from the <br>
> client was passing forward to the carrrier. So we
switched to <br>
> topology_hiding("C") and worked as expected but the
carrier's switch <br>
> collapsed after a while. They say that we leave many
dialogs open thar <br>
> never close. Other than that, th3 calls work fine for us.<br>
> What are my engineers doing wrong?<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">Users@lists.opensips.org</a><br>
> <a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>