Post an MT message response to the client URL (if configured).
This callback is a vibes initiated request to the client to attempt delivery of carrier responses. The delivery of these messages is contingent on the client configuring the receiptOption tag on the original submission of the MT message.
NOTE: The client endpoint should properly store/record the response and then return an HttpResponse; 200 to acknowledge receipt. The client process should keep actual processing/logic as small as possible, for throughput and performance.
Main wrapper element indicating that this is a MtMessage Response
The unique identifier assigned to the MtMessage when it was submitted
The client defined identifier for the MtMessage if set while submitting the message.
Date the response was received in standard XML format
The processing stage at which the response was generated. The possible value are
Element that has the status of the MtMessage
Boolean on whether the status is an error.
Description of the status.
The error code if the status is an error status.
The internal error code if the status is an error status.