|
@@ -52,15 +52,20 @@
|
|
major version. Internal structures can be incompatible between different
|
|
major version. Internal structures can be incompatible between different
|
|
major versions and can lead to crashes or unexpected behaviour.
|
|
major versions and can lead to crashes or unexpected behaviour.
|
|
</para>
|
|
</para>
|
|
- <example>
|
|
|
|
- <title>KDMQ Request Example</title>
|
|
|
|
|
|
+ <section>
|
|
|
|
+ <title>KDMQ Request</title>
|
|
<para>
|
|
<para>
|
|
- This request is generated for DMQ peers availability notifications.
|
|
|
|
- Other messages can be produced by various modules, with different R-URI
|
|
|
|
- username and body content, such as <emphasis>htable</emphasis>,
|
|
|
|
- <emphasis>dialog</emphasis> or <emphasis>usrloc</emphasis> modules.
|
|
|
|
|
|
+ KDMQ messages can have different format and content for R-URI username, headers
|
|
|
|
+ and body, being specific to each component that leverages DMQ to replicate
|
|
|
|
+ data, such as <emphasis>htable</emphasis>, <emphasis>dialog</emphasis>
|
|
|
|
+ or <emphasis>usrloc</emphasis> modules.
|
|
</para>
|
|
</para>
|
|
- <programlisting format="linespecific">
|
|
|
|
|
|
+ <para>
|
|
|
|
+ Next request is generated by DMQ module for peers availability notifications.
|
|
|
|
+ </para>
|
|
|
|
+ <example>
|
|
|
|
+ <title>KDMQ Request Example</title>
|
|
|
|
+ <programlisting format="linespecific">
|
|
...
|
|
...
|
|
|
|
|
|
KDMQ sip:[email protected]:5090 SIP/2.0
|
|
KDMQ sip:[email protected]:5090 SIP/2.0
|
|
@@ -82,6 +87,7 @@ sip:192.168.40.17:5060;status=active
|
|
</programlisting>
|
|
</programlisting>
|
|
</example>
|
|
</example>
|
|
</section>
|
|
</section>
|
|
|
|
+ </section>
|
|
|
|
|
|
<section>
|
|
<section>
|
|
<title>Dependencies</title>
|
|
<title>Dependencies</title>
|