| Delivery reports for messages sent to SMSC through HTTP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 08, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Silvinho New member Username: Silvinho Post Number: 1 Registered: 03-2009 |
Hello, I am testing NowSMS to relay messages received through SMPP to a proprietary GSM gateway that works only on HTTP. The flow Customer > SMPP > NowSMS > HTTP > GSM Gateay works fine, but I need to send back delivery reports. Is it possible to trick NowSMS to receive delivery reports from GSM gateway? I can program it to call back a URL or upload specific files. I am open to any (advanced) solution! thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 599 Registered: 08-2008 |
Hi, Yes, there is a special interface that allows you to send back delivery reports. I'll summarise it here. But, you might also be interested in the following discussion thread: http://support.nowsms.com/discus/messages/1/15186.html It is not necessary to download any of the updates referenced in that thread, as all of those functions mentioned are now standard built-in features of NowSMS. A number of features to help better support the type of environment that you are describing were added in response to discussion at the above thread ... so you may find other relevant information there. To support delivery reports in this type of environment, here is how we expect it to work. 1.) When NowSMS submits the message via HTTP, we expect the HTTP response to include a message id somewhere in the HTTP response. The first step of the configuration is to tell NowSMS how to parse this message id from the HTTP response. Under the SMSGW.INI section that defines the HTTP SMSC connection, you need to add TrackHTTPReceipts=Yes. You also need to define MessageIDResponsePrefix=xxxxxx setting, where "xxxxxx" is some text for NowSMS to look for in the HTTP SMSC response. It is expected that the message id is the first non-blank text following this text string. The id is assumed terminated by a space, line break, period (.), comma (,) or semi-colon (;). 2.) For the SMSC to send back a receipt, it connects back to the NowSMS web interface in the same way as a user account would. It needs to include a username and password in the request (User= and Password= parameters). It must include a Phone= parameter to indicate who should receive the receipt (original sender). Then it should include ReceiptMessageId= to indicate the message id (should match what was returned in the HTTP response), and either ReceiptDelivered=Yes, ReceiptFailed=Yes, or ReceiptInTransit=Yes, to indicate the receipt type. When NowSMS sees the ReceiptMessageId= parameter, and one of the receipt type parameters, NowSMS will look up the message id, and route an SMPP format receipt to the appropriate submitter account (and although you must include a Phone= parameter in the request, NowSMS will remember the original sender and recipient and insert them into the receipt as appropriate). That other thread may have some additional helpful information, but that's a basic overview. -- Des NowSMS Support | |||
| Silvinho New member Username: Silvinho Post Number: 2 Registered: 03-2009 |
Fantastic. Thanks for quick reply! | |||
