From aa10e3dd8b537149c9859ce03e56f3a02ab08872 Mon Sep 17 00:00:00 2001
From: Anders Svensson <anders@erlang.org>
Date: Tue, 11 Dec 2012 10:56:57 +0100
Subject: Warn about applications/capabilities mismatches in doc

---
 lib/diameter/doc/src/diameter.xml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/lib/diameter/doc/src/diameter.xml b/lib/diameter/doc/src/diameter.xml
index f7d95844ba..7e50f338d3 100644
--- a/lib/diameter/doc/src/diameter.xml
+++ b/lib/diameter/doc/src/diameter.xml
@@ -719,6 +719,15 @@ passed to &call;, while for an
 incoming request the application identifier in the message
 header determines the application, the identifier being specified in
 the application's &dictionary; file.</p>
+
+<warning>
+<p>
+The capabilities advertised by a node must match its configured
+applications. In particular, <c>application</c> configuration must
+be matched by corresponding &capability; configuration, of
+Application-Id AVP's in particular.</p>
+</warning>
+
 </item>
 
 <tag><c>{restrict_connections, false
@@ -797,6 +806,16 @@ The list of Diameter applications to which the transport should be
 restricted.
 Defaults to all applications configured on the service in question.
 Applications not configured on the service in question are ignored.</p>
+
+<warning>
+<p>
+The capabilities advertised by a node must match its configured
+applications.
+In particular, setting <c>applications</c> on a transport typically
+implies having to set matching Application-Id AVP's in a
+&capabilities; tuple.</p>
+</warning>
+
 </item>
 
 <marker id="capabilities"/>
-- 
cgit v1.2.3