@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.
It's a bit of a rabbit hole. https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatch... is one of the most famous ones I guess. Any good example how to properly document a non-set behavior, so it's consistent?