Number of Request messages received from a DSR Application that could not be routed.
Collection Interval
5 min
Peg Condition
When DRL successfully receives a Request message from the DSR Application that is rejected with an Answer response because either a Peer Routing Rule was not found or implicit routing could not be invoked.
The DSR Application is forwarding Request messages that cannot be routed to a peer. The following problems could exist:
A Peer Routing Rule could be missing of incorrectly configured.
The DSR Application could be incorrectly configured.
The Request message from a downstream peer was mis-routed to the DSR.
Measurement Scope
Server Group
Recovery
Verify the Peer Routing Rules on the Diameter > Configuration > Peer Routing Rules GUI screen and make any needed corrections.
Verify the DSR Application Id configuration on the Diameter > Configuration > Application Ids GUI screen and make any needed corrections.