rtpproxy/rtpengine: document socket type if protocol is missing

Close #3154 (cherry picked from commit 90018c2)
OpenSIPS · Aug 16, 2023 · e4cd6ba · e4cd6ba
1 parent 9240b7a
commit e4cd6ba
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/modules/rtpengine/doc/rtpengine_admin.xml b/modules/rtpengine/doc/rtpengine_admin.xml
@@ -103,7 +103,9 @@
 		<title><varname>rtpengine_sock</varname> (string)</title>
 		<para>
 		Definition of socket(s) used to connect to (a set) &rtp; proxy. It may
-		specify a UNIX socket or an IPv4/IPv6 UDP socket.
+		specify a UNIX socket or an IPv4/IPv6 UDP socket. If the protocol part
+		(i.e. <quote>udp:</quote>) is missing, the socket is treated as a
+		UNIX socket.
 		</para>
 		<para>
 		<emphasis>

diff --git a/modules/rtpproxy/doc/rtpproxy_admin.xml b/modules/rtpproxy/doc/rtpproxy_admin.xml
@@ -198,6 +198,8 @@
 		<para>
 		Definition of socket(s) used to connect to (a set) RTPProxy. It may 
 		specify a UNIX socket, an IPv4/IPv6 UDP socket or an IPv4/IPv6 TCP socket.
+		If the protocol part (i.e. <quote>udp:</quote>) is missing, the socket is
+		treated as a UNIX socket.
 		</para>
 		<para>
 			The definition also supports to specify a different IP that will