Message timeouts for applications that are added as data sources, such as Sh and Sy, have advanced configuration settings that allow specific response timeout values to be configured for that particular application. You can use service overrides to set the timeout in increments of 1 sec or you can set the time out in increments of 100 ms using Protocol Timer Profiles. You use the following service overrides to adjust the timeout wait for messages:
- DRADRMA.ResponseTimeout
- The amount of time when an MRA device considers a request timed out. The default is 5 seconds. To set the time out in increments of 100 ms, use Protocol Timer Profiles to set the timeout.
- DIAMETER.ResponseTimeout
- The amount of time when an MPE device considers a request timed out. The default is 5 seconds. To set the time out in increments of 100 ms, use Protocol Timer Profiles to set the timeout.
- SH.ResponseTimeout
- The amount of time when an Sh response is timed out. The default is 3 seconds.
- SY.ResponseTimeout
- The amount of time when an Sy response is timed out. The default is 3 seconds.
The amount of wait time in seconds before a response from an outstanding request times out between:
- MRA Site 1 and MRA Site 2
The DRADRMA.ResponseTimeout is used for requests to the MPE devices it manages and to the associated/backup MRA device. The DRADRMA.ResponseTimeout defaults to 5 seconds.
MRA Site 1 and MPE Site 1
Verify that the MRA device does not timeout requests before the MPE device returns an answer. When setting the DRADRMA.ResponseTimeout service override, the value for DRADRMA.ResponseTimeout must be greater than or equal to the DIAMTER.ResponseTimeout service override. The following are example of factors that can affect the MPE devices capability to provide a timely response:
- For Sh or Sy requests, the synchronous or on-demand lookup configuration for the data source in the MPE device.
- If direct reply is disabled for AF requests, you must consider the timeout of the Gx-RAR request
- When Sd is deployed, the Sd session must be established before making a reply to the Gx CCR-I request.
For example: If the DRADRMA.ResponseTimeout expert setting is set to 4 seconds, a reasonable DIAMTER.ResponseTimeout value is 3 seconds, and then data source time out value of SH.ResponseTimeout or SY.ResponseTimeout is 2 seconds. If we go to finer granularity as to message type level, we need to set protocol timer profile globally or per peer.
- MPE Site 1 and SPR/UDR
Verify that the MPE device does not timeout requests before the application (Sy or Sh) returns an answer. When setting the DIAMTER.ResponseTimeout service override, the value for DIAMTER.ResponseTimeout must be greater than or equal to the application service override (SH.ResponseTimeout or SY.ResponseTimeout).