- Diameter User Guide
- Configuring Diameter
- Diameter Peer Nodes
- Adding a Peer Node
- Selecting Peer Node Egress Pending Answer Timers
2.11.2.4 Selecting Peer Node Egress Pending Answer Timers
Use this task to select Peer Node Ingress Routing Option Sets.
- Click Diameter, and then Configuration, and then Peer Nodes.
- Select the Egress Pending Answer Timer to specify how long Diameter waits for a response from the Peer Node. When DRL selects a viable Connection for forwarding a Request message to an upstream Peer Node, it determines which Pending Answer Timer value to use based on the following precedence selection rules, highest to lowest priority. A Pending Transaction Timer limits the time that DRL waits for an Answer response after forwarding a Request message to an upstream Peer Node. When this time-limit is exceeded, DRL abandons Invoke Message Rerouting.
- If Transaction Configuration Set is selected on ingress Peer Node from which the Diameter Request was received, use Transaction Configuration Set and apply longest/strongest match search criteria for Diameter Request message parameters comparison and if a match is found, apply PAT assigned to Transaction Configuration Rule defined under this Transaction Configuration Set, if it exists.
- The Pending Answer Timer assigned to the Routing Option Set for the Ingress Peer, if it exists.
- The Pending Answer Timer assigned to the egress Peer Node to which the Request message is forwarded, if it exists.
- Default Pending Answer Timer.
If Pending Answer Timer is set to Not Selected, the Egress Pending Answer Timer configured for the Application ID contained in the message is used.A Pending Answer Timer with a value > 10 seconds is considered a Long Timeout Pending Answer Timer. Long Timeout Pending Answer Timers are intended for Diameter Applications that can have long transaction times (for example: SLg). Because Requests assigned to Long Timeout Pending Answer Timers might hold internal resources (for example, PTRs, PDUs) for extended periods, this traffic uses a separate PTR Pool from standard Diameter traffic. It is expected that a very small percentage (< 2%) of overall traffic would be assigned to Long Timeout Pending Answer Timers, and users should configure the smallest timeout value acceptable based on the overall transaction path.
- Click OK, Apply, or Cancel.