Request message from a downstream peer is rejected
by a Local Node because no routes were available for routing the message. A No
Routes Available condition occurs when:
- A Route List was
selected via a Peer Routing Rule or implicit routing but its Operational Status
was Unavailable
- Implicit routing was
invoked and the peer's Operational Status was not Available and an alternate
implicit route was not provisioned for the peer
- Implicit routing was
invoked but failed to find a route list by matching the configured
realm/application ID (using the Realm Route table); or failed to select a valid
egress connection from the matched route list
The connection measurement is associated with the
connection from which the Request message was received.