Additional

This section includes utility and support classes that assist with low-level protocol behavior and data structure representation. While not SMPP commands themselves, these components are important for enabling correct request and response handling across the protocol stack.

UnsucessfulSME represents a destination SME that failed during a SubmitMulti operation. It holds the error status code and the destination address, providing insight into why specific recipients did not receive the message.

Address encapsulates the TON (Type of Number), NPI (Numbering Plan Indicator), and address string values used throughout SMPP PDUs to identify the source and destination of messages. This class is shared across various operations like message submission, delivery, and response generation.

EmptyBody and EmptyBodyResp are base classes for PDUs that have no message body. They provide a simplified implementation for reading, writing, and managing headers and optional parameters, and are often extended by control or signaling commands that carry no payload, such as Unbind, EnquireLink, or GenericNack.

While these classes operate behind the scenes, they are essential to proper serialization, deserialization, and protocol compliance in the Mobius SMPP API.

Not Presented: Outbind
The Outbind command, though part of the SMPP specification, is intentionally excluded from the Mobius REST API. Outbind is a legacy command used in older SMPP environments where the SMSC initiated a connection to the ESME, typically in scenarios where the ESME did not have a static IP or could not maintain a persistent session.
Modern systems overwhelmingly favor ESME-initiated sessions using commands like BindTransmitter, BindReceiver, or BindTransceiver, which align better with RESTful and client-driven architectures. As such, Outbind is considered obsolete and unnecessary in this