diff options
author | Anders Svensson <[email protected]> | 2017-06-11 16:47:12 +0200 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2017-06-13 13:50:06 +0200 |
commit | 5f6d83776c38539e396bae345914be575aceea8d (patch) | |
tree | aa609f1521dcf8308ef08b4ee130c8cb944eb4e4 /scripts | |
parent | 77052371aacf68ad4698f75d5a06f7cb2420a66c (diff) | |
download | otp-5f6d83776c38539e396bae345914be575aceea8d.tar.gz otp-5f6d83776c38539e396bae345914be575aceea8d.tar.bz2 otp-5f6d83776c38539e396bae345914be575aceea8d.zip |
Fix/simplify setting of one Failed-AVP
When setting the Result-Code/Failed-AVP of an outgoing answer from an
errors list either returned from or not discarded by a handle_request
callback, more than the AVP paired with the Result-Code in question
could be set in Failed-AVP.
RFC 6733:
7.5. Failed-AVP AVP
The Failed-AVP AVP (AVP Code 279) is of type Grouped and provides
debugging information in cases where a request is rejected or not
fully processed due to erroneous information in a specific AVP. The
value of the Result-Code AVP will provide information on the reason
for the Failed-AVP AVP. A Diameter answer message SHOULD contain an
instance of the Failed-AVP AVP that corresponds to the error
indicated by the Result-Code AVP. For practical purposes, this
Failed-AVP would typically refer to the first AVP processing error
that a Diameter node encounters.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions