Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Caring of messageId in case of delivery report transit #23
When SMSC GW is a transit point for SMPP messages (ESME1 -> SMSC GW -> ESME2), there is a possibility for delivery report transit back to originator (ESME2 -> SMSC GW -> ESME1). In this case we need to replace messageId field in the message content of receipt to the value that SMSC GW has returned to ESME1 in the submit_sm_response.
To achieve it we need to setu extra tables in cassandra database (a table per a day). If SMSC GW is configured to provide a receipt transit, at the step of delivering messages into ESME (RxSmpp) SMSC GW will check if a message contains a receipt request and store message data into a database.
referenced this issue
Aug 12, 2016
We need to add an extra SMSC GW server level config parameter:
incomeReceiptsProcessing - processing of incoming delivery receipts from remote SMSC GW: replacing of messageId in a receipt by a local messageId