Forwarding Delivery Reports to Client

Forwarding Delivery Reports to Client SearchSearch
Author Message
SARB JIT SINGH GUGNANI
New member
Username: Ssinghg

Post Number: 1
Registered: 05-2004
Posted on Thursday, May 20, 2004 - 02:02 pm:   

How do I route the delivery report of the sms being delivered or failure report to the end client (sender)? I get a sms regarding the delivery of the sms at the gateway, but am NOT able to figure out how to route it further to the actual sender. Help!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2656
Registered: 10-2002
Posted on Tuesday, May 25, 2004 - 06:50 pm:   

Normally with SMPP return receipts, the message arrives addressed to the sender of the original message ... with the recipient of the original message as the sender. (So, sender of original message becomes recipient of the delivery notification, and the recipient of the original message becomes the sender of the delivery notification.)

In that case, you configure the "SMS Users" account in NowSMS so that the account is configured to receive messages for the sender address it is using. NowSMS then knows to route messages that are received in reply (such as the delivery notification), to the appropriate "SMS Users" account.

So if your "SMS Users" account is submitting messages from a particular sender address ... delivery notifications then come in as being addressed to that sender address. And you can define that sender address in the "Recipient address(es) to route to this user" under the "SMS Users" account, so that NowSMS routes any received messages back to the SMPP client.

At least that is how it normally works.

We have recently encountered a system where the SMPP delivery receipts are coming back with the original sender still listed as the sender, and the original recipient still listed as the recipient. This is being discussed in the following thread on the discussion board here:

http://support.nowsms.com/discus/messages/1/4409.html

If the approach that I described above does not work for you, then I would like to see your log files to see if you encountering the same routing issue.

-bn