[OpenSIPS-Users] Topology_hiding took down my carrier's switch

[Federico Alves]

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.
Please let me know if you have any other questions,  via private email.

On Thu, Jul 17, 2025, 5:53 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> The only thing you can do is (1) ask the carrier for an example of such
> bogus dialog and (2) investigate the SIP traffic to be sure that the BYE
> exchange with the carrier was correctly done...
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 27.06.2025 00:57, Federico Alves wrote:
> > So far my engineers use topology_hiding(), and the CallID from the
> > client was passing forward to the carrrier. So we switched to
> > topology_hiding("C") and worked as expected but the carrier's switch
> > collapsed after a while. They say that we leave many dialogs open thar
> > never close. Other than that, th3 calls work fine for us.
> > What are my engineers doing wrong?
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250717/5a595280/attachment.html>