Re: Topos and TLS

6.1.2 was just released with the fix for this, 6.1.1 was dropping the port
and transport when contact mode is 0. Without upgrading you can mitigate by
setting contact mode to 1, but it will change the Contact in other ways
that may or may not be compatible with your peers.

On Wed, Apr 22, 2026 at 9:21 AM Martin Nyström via sr-users <
[email protected]> wrote:

> Hi,
>
> How am I expected to handle TLS when using TOPOS?
>
> listen=tls:192.168.5.122:5061 advertise foobar.pbx.com:5061
>
>
> modparam("topos", "storage", "db")
> modparam("topos", "contact_host", “foobar.pbx.com")
> modparam("topos", "dialog_expire", 10800)
>
>
> When using TLS, TOPOS sets the contact header as something like this for a
> 200 OK returned.
> Contact: <sip:[email protected]>
>
> Is this valid? Or should it not be foobar.pbx.com:5061;transport=TLS
>
> It appears some vendors blindly use the contact header and returns the ACK
> for an example to a non TLS endpoint, despite the dialog (INVITE) starting
> out as TLS.
>
>
>
>
>
> /M
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions --
> [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!
>

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [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!