diff options
Diffstat (limited to 'lib/diameter/doc/src/diameter.xml')
| -rw-r--r-- | lib/diameter/doc/src/diameter.xml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/lib/diameter/doc/src/diameter.xml b/lib/diameter/doc/src/diameter.xml index 663c9cc785..bfb6da41b5 100644 --- a/lib/diameter/doc/src/diameter.xml +++ b/lib/diameter/doc/src/diameter.xml @@ -539,7 +539,7 @@ that matches no peer.</p> <p> The <c>host</c> and <c>realm</c> filters cause the Destination-Host and Destination-Realm AVPs to be extracted from the -outgoing request, assuming it to be a record- or list-valued +outgoing request, assuming it to be a record-, list- or map-valued <c>&codec_message;</c>, and assuming at most one of each AVP. If this is not the case then the <c>{host|realm, &dict_DiameterIdentity;}</c> filters must be used to achieve the desired result. @@ -970,13 +970,14 @@ occur in the message in question.</p> </item> <tag> -<marker id="record_decode"/><c>{record_decode, boolean()}</c></tag> +<marker id="record_decode"/><c>{record_decode, boolean() | map}</c></tag> <item> <p> Whether or not to decode message and grouped AVPs to records in the <c>msg</c> field of diameter_packet records and <c>value</c> field of -diameter_avp records respectively. -If <c>false</c> then the fields are set to the same value.</p> +diameter_avp records respectively, or to an alternate format. +If false then the fields are set to the same value. +See also &codec_message;.</p> <p> Defaults to <c>true</c>.</p> |