From 3fc1da644a6b375fc45ea17cbcf81643f70db545 Mon Sep 17 00:00:00 2001
From: Charles Chance <charles.chance@sipcentric.com>
Date: Tue, 23 Jan 2018 20:51:31 +0000
Subject: [PATCH] presence: added enable_dmq parameter to module docs

---
 src/modules/presence/doc/presence_admin.xml | 32 +++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/src/modules/presence/doc/presence_admin.xml b/src/modules/presence/doc/presence_admin.xml
index 0bedc377417..aa10dff34c9 100644
--- a/src/modules/presence/doc/presence_admin.xml
+++ b/src/modules/presence/doc/presence_admin.xml
@@ -62,6 +62,11 @@
 				<emphasis>tm</emphasis>.
 			</para>
 			</listitem>
+			<listitem>
+			<para>
+				<emphasis>dmq (only if replication is enabled)</emphasis>.
+			</para>
+			</listitem>
 			</itemizedlist>
 		</para>
 	</section>
@@ -897,6 +902,33 @@ modparam("presence", "retrieve_order_by", "priority, received_time")
     </example>
 </section>
 
+<section id="presence.p.enable_dmq">
+	<title><varname>enable_dmq</varname> (integer)</title>
+	<para>
+		If set to 1, will enable DMQ replication of presentities between nodes. Use this instead of a shared DB
+		to share state across a cluster and update local watchers in realtime (subs_db_mode < 3) or on next
+		notifier run (subs_db_mode = 3).
+	</para>
+	<para>
+		<emphasis>
+			If this parameter is enabled, the DMQ module must be loaded first - otherwise, startup will fail.
+		</emphasis>
+	</para>
+	<para>
+		<emphasis>
+			Default value is 0.
+		</emphasis>
+	</para>
+	<example>
+		<title>Set <varname>enable_dmq</varname> parameter</title>
+		<programlisting format="linespecific">
+			...
+			modparam("presence", "enable_dmq", 1)
+			...
+		</programlisting>
+	</example>
+</section>
+
 </section>
 
 <section>