Echo Request
See also API reference for Network Administration
An Echo Request message is used to perform a connectivity status check between RPP and the Participants. RPP attempts to send the Echo Request to the Participants from time to time (configured within the system) to ensure that it is available to receive messages. If there is no response received from the Participants, the RPP retries for a configured number of times before marking the Participant as inactive. The endpoint continues sending Echo Request until a response is received. The Participant is then marked as active, and any messages stored in the SAF queue are sent (if SAF is configured).
When a Participant is marked as inactive, it will prevent the Participant from sending or receiving any payment requests.
A system notification (Bank Availability Status) message will be sent to the other Active Participants on any change in status of a Participant.
Participants can also perform connectivity check to the RPP host by sending echo requests.
The Echo Request can also be used for the following purposes:
- Test to ensure Participant’s endpoint doesn’t use weak cipher suites
- Test to ensure Participant’s endpoint doesn’t use obsolete TLS (minimally TLS 1.2)
- Test to ensure Participant’s endpoint doesn’t support HTTP
- Test to ensure Participant’s endpoint supports non-expired SSL certificate and signature keys
Successful Echo Request
| Step | Sender | Receiver | Processes |
|---|---|---|---|
| 1 | Participant / RPP | RPP / Participant | Send an echo request |
| 2 | RPP / Participant | Participant / RPP | Upon receiving the echo request, response with an acknowledgement message |
Exception Conditions
| Condition | Actions | Alternatives |
|---|---|---|
Participant did not send acknowledgement to RPP host | RPP shall:
| - |