On this page
Delivery receipts & overrides
Follow provider receipts and understand synthetic-success options.
Acceptance is not delivery#
A successful submit response means a message was accepted at that stage. Final DLR status comes later. Correlate the switch submit ID, outgoing provider message ID and incoming receipt.
Client controls#
Auto DLR and Success override change receipt behavior. Success override can cover selected error codes or all configured failures/timeouts. An override changes what is reported to the client; it does not prove that a handset received the message.
- Choose the required override mode.
- Add the exact error codes when using selected errors.
- Save and test one documented outcome.
- Compare the raw provider result with the reported DLR in the trace.
Manual DLR tools#
CDRs provides single and filtered manual-DLR actions plus a durable queue. Inspect the filter set and matched records before a bulk operation. Sending a DLR is an operational write, not a harmless report preview. Clearing log rows and clearing queued receipts are separate operations.
Voice relay#
Voice call outcomes are placed into the existing durable DLR path. The route's success policy and failure result determine the relay. Worker completion and receipt transmission are distinct stages.
Investigate missing receipts#
Check the provider's receipt settings, message-ID correlation, gateway timeout, client bind, manual-DLR queue and worker health. Use event traces for duplicate or ignored receipt handling. SMPP_STORE_IGNORED_DLR_ONCE and its cache controls limit repeated ignored-receipt storage.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.