Response Handling

Every SMPP request sent by an ESME expects a corresponding response from the SMSC. These responses confirm whether the request was successfully received, parsed, and processed - or if an error occurred.

This section describes classes that represent response PDUs for various SMPP operations. These include acknowledgments to binding operations such as BindReceiverResp, BindTransmitterResp, and BindTransceiverResp, which confirm the establishment of a session and assign it a specific role.

For message-related transactions, classes like SubmitSmResp, SubmitMultiResp, DeliverSmResp, DataSmResp, QuerySmResp, ReplaceSmResp, and CancelSmResp encapsulate the outcomes of message submission, delivery tracking, replacement, cancellation, and querying.

Additionally, session-level responses such as EnquireLinkResp and UnbindResp confirm connectivity checks and proper session termination.

Each of these classes provides access to response data, such as message IDs, error codes, and optional parameters. They serve as the final step in the request-response loop and are important for validating message delivery, tracking failures, and managing the session state programmatically.