Download Enterprise Messaging Gateway - User's Guide

Delivery receipts (DLR)
The keyword FORCE_DLR on the other hand overrides any DLR message
option already set. When FORCE_DLR=1 is used on a connector where messages are received the DLRs received or generated will be forwarded back to the
client, while if FORCE_DLR=1 is used on a connector where messages are sent
the received DLRs will only be used to update the message status and then
silently dropped.
Please note that DLRs silently dropped will not appear in the corresponding connector log but will only show up in the pdu log for the connector.
9.3 Routing DLRs
For incoming DLRs routing decisions are made a little differently than for normal messages.
It is evaluated in the following order with the highest priority first:





ROUTEDLR specified for user (in users file or in DB) who sent the original
message for which DLR was requested
ROUTEDLR specified on original message
ROUTEDLR specified on connector where DLR is received/generated
ROUTEDLR specified by general keyword in server.cfg
DLR is routed back to the connector where the original message was received
DLRs can optionally be redirected from one connector to another via connector
keyword REDIRECT.
9.4 DLRs and buffered status
Some SMSCs send a DLR when the message has been accepted or if the message is buffered in the SMSC due to handset being switched off for example.
Such a DLR will not be propagated through EMG but will only update the “bufferedstatus” field in the routelog table within EMG. When using EMG with a
database this field can be queried in order to determine if and why a message has
been buffered.
The message status will remain as “RELAYED” even after a DLR with a buffered status has been received.
Enterprise Messaging Gateway - User’s Guide 5.2.7
53