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:atpsh-69e6453f-a4-4@foobar.pbx.com> 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
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 < sr-users@lists.kamailio.org> 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:atpsh-69e6453f-a4-4@foobar.pbx.com>
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 -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
I had the issue earlier today and it disappeared when I did a rebuild on the docker pulling the latest version. Hah, that explains it. I first through it was just randomly occurring but this explains it. I am now running 6.1.2 and haven’t encountered the issue since. /M From: Calvin E. via sr-users <sr-users@lists.kamailio.org> Date: Wednesday, 22 April 2026 at 20:15 To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org> Cc: Calvin E. <calvine@gmail.com> Subject: [SR-Users] Re: Topos and TLS CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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 <sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> wrote: Hi, How am I expected to handle TLS when using TOPOS? listen=tls:192.168.5.122:5061<http://192.168.5.122:5061> advertise foobar.pbx.com:5061<http://foobar.pbx.com:5061> modparam("topos", "storage", "db") modparam("topos", "contact_host", “foobar.pbx.com<http://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:atpsh-69e6453f-a4-4@foobar.pbx.com<mailto:sip%3Aatpsh-69e6453f-a4-4@foobar.pbx.com>> 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 -- sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org> To unsubscribe send an email to sr-users-leave@lists.kamailio.org<mailto:sr-users-leave@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender!
Hello, what version of Kamailio are you using? I saw some discussions recently about a regression that might be related and should be fixed in the latest master branch and 6.1.x. Cheers, Daniel On 22.04.26 17:37, Martin Nyström via sr-users 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:atpsh-69e6453f-a4-4@foobar.pbx.com>
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 -- sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
-- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com
participants (3)
-
Calvin E. -
Daniel-Constantin Mierla -
Martin Nyström