From 025f56212da3396c6e77d2ecdfbe184d85e1e20e Mon Sep 17 00:00:00 2001
From: Andreas Granig <andreas@granig.com>
Date: Tue, 4 Oct 2022 14:23:01 +0200
Subject: [PATCH] Document the mqtt-tls-alpn option

---
 daemon/rtpengine.pod | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/daemon/rtpengine.pod b/daemon/rtpengine.pod
index a7c0cb6ed..39674277e 100644
--- a/daemon/rtpengine.pod
+++ b/daemon/rtpengine.pod
@@ -995,11 +995,14 @@ to enable authentication.
 
 =item B<--mqtt-keyfile=>I<FILE>
 
+=item B<--mqtt-tls-alpn=>I<STRING>
+
 Enable TLS to connect to Mosquitto broker, optionally with client certificate
 authentication. At least B<cafile> or B<capath> must be given to enable TLS. To
 enable client certificate authentication, both B<certfile> and B<keyfile> must
 be set. All files must be in PEM format. Password-proteted files are not
-supported.
+supported. The B<tls-alpn> can be set (e.g. mqtt) if a service like AWS IoT
+Core shares the same TLS port for two different network protocols.
 
 =item B<--mqtt-publish-qos=>B<0>|B<1>|B<2>