[sr-dev] [kamailio/kamailio] mqtt: Add tls_alpn module option (PR #3261)

Andreas Granig notifications at github.com
Thu Oct 13 09:15:28 CEST 2022


@agranig commented on this pull request.



> @@ -324,6 +324,27 @@ modparam("mqtt", "ca_path", "/etc/ssl/certs")
 		<programlisting format="linespecific">
 ...
 modparam("mqtt", "tls_method", "tlsv1.3")
+...
+		</programlisting>
+		</example>
+	</section>
+	<section id="mqtt.p.tls_alpn">
+		<title><varname>tls_alpn</varname> (str)</title>
+		<para>
+        Used to set the TLS ALPN option for cases where one TLS port is used to share multiple services. Prominent
+        example is AWS IoT, where you have to set the <varname>tls_alpn</varname> to "mqtt" to be able to connect
+        via MQTT.
+		</para>
+		<para>
+		<emphasis>
+			Default value is NULL, where no ALPN is set on the TLS connection.

Is there actually good practice on how to document a param which has no default value (aka is NULL)? I'm finding quite some old modules having it documented like this, see https://www.kamailio.org/docs/modules/devel/modules/auth_db.html#auth_db.p.load_credentials for example.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3261#discussion_r994245839
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/pull/3261/review/1140196789 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20221013/7f6de6a6/attachment.htm>


More information about the sr-dev mailing list