Rejected Diameter application request

Logged when a request from a peer cannot be handed to the Diameter server policy or forwarded, and Radiator Server answers it with the Result-Code in diameter_result_code. diameter_rejection_reason is:

• validation: the request fails the command, application, or AVP rules of its application.
• forwarding-admission: a Diameter backend cannot forward it, for example because of a routing loop.
• invalid-routing-avp: a Destination-Realm, Destination-Host, or Route-Record value cannot be decoded.
• empty-session-id: its Session-Id is empty.
• no-policy: the server has no policy for incoming requests.
• destination-host-not-local: its Destination-Host names another node, and it was not forwarded, either because the server has no peer group or because policy did not forward it.

Validation errors are answered with the RFC 6733 Result-Code for the failure and the offending AVP as Failed-AVP. destination-host-not-local and no-policy are answered with DIAMETER_UNABLE_TO_DELIVER (3002).

Check the attached error and the request with packet tracing, then correct the sending peer. For no-policy, configure the server's policy if the peer should send requests to Radiator Server. For destination-host-not-local, check which host the peer addresses, or forward such requests with a Diameter backend. See Diameter server.