Standards-aware sessions
AxonSMS handles transmitter, receiver and transceiver binds, sequence numbers, enquire_link heartbeats, unbind flows and matching response PDUs.
Two client delivery directions
A Panel Owner can connect to a dedicated AxonSMS receiver account, or AxonSMS can bind to the client's public SMPP host using encrypted credentials.
Delivery evidence
Messages are marked accepted only after a successful matching submit_sm_resp or deliver_sm_resp. Failed attempts enter a durable retry workflow visible to operators.
Frequently asked questions
Which bind type should I use?
Transceiver is the usual choice. A transmitter bind is also supported for outbound submit_sm delivery; receiver binds are used when a client connects to AxonSMS for deliver_sm.
Does SMPP support Unicode?
Yes. Non-ASCII content is encoded using UCS-2 data coding.
Build your SMS operation with AxonSMS
Request an account or speak with support about current inventory and integration requirements.
Get started