SMPP · DELIVERY
Delivery receipt status mapping
Correlate submit_sm responses with deliver_sm receipts and distinguish accepted messages from final delivery outcomes.
SMPP delivery receipts ↗Receipt lifecycle
submit_sm + registered_delivery↓
submit_sm_resp + message_id↓
Network delivery attempt↓
deliver_sm receipt↓
deliver_sm_resp acknowledgement
Fields to retain
- receipted_message_id or the id value in short_message
- message_state or stat
- network_error_code or err
- submit date and done date
- esm_class receipt indication
Normalized status mapping
| SMPP state | VonnexAI status | Type |
|---|---|---|
| SCHEDULED | Scheduled | Intermediate |
| ENROUTE / EN_ROUTE | Processing | Intermediate |
| DELIVERED / DELIVRD | Delivered | Final |
| EXPIRED | Expired | Final |
| DELETED | Deleted | Final |
| UNDELIVERABLE / UNDELIV | Undeliverable | Final |
Important distinction
Important
A successful submit_sm_resp means the platform accepted the message; it does not mean the handset received it. Use the final delivery receipt as the delivery outcome. Network error codes may be gateway- or carrier-specific.