Delivery status | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
Author | Message | |||
Dani Riera New member Username: Drieran Post Number: 3 Registered: 05-2005 |
Hi, I'm working with mblox and I need to know the delivery status of a sms. SMPP specification can control where the delivery notification/report when registered_delivery field is set. How I can activate this in NowSMS and how I can access to this report ? If this is not possible I need to join the status of file SMSOUT-2005xxxxx with my database, but here my question is how to join. If when I submit the sms via http I can get the ID used in nowsms will be great. Somebody can help me ? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4769 Registered: 10-2002 |
Hi Dani, When submitting a message via HTTP, you need to include the parameter "&ReceiptRequested=Yes" in the HTTP request. When submitting to an SMPP server, this will set the "registered_delivery" flag. Now, where it gets more complex ... When you submit via HTTP, NowSMS will include the message id it assigns in the HTTP response. (If you do not see this, then you need an update ... but more on this in a moment.) The next problem is that the receipt will typically come back in, but it will have the message id that was assigned by your provider, instead of NowSMS' id. There is a setting described in the following thread: http://support.nowsms.com/discus/messages/1/9063.html This setting enables tracking of the SMPP message ids, so that when a receipt comes back in, the id in the receipt will get converted back to the one originally assigned by NowSMS. This support is new, and it is not very well described yet. The latest update is v5.51d, which can be downloaded at http://www.nowsms.com/download/latestpatch.zip. v5.51 needs to be installed first, and then this ZIP gets applied to update a v5.51 installation. -bn | |||
David Derr New member Username: Davovad Post Number: 1 Registered: 08-2005 |
I have followed the instructions above and elsewhere to get Delivery Receipts: -Version v5.51d is installed -&ReceiptRequested=Yes is in the HTTP request -DeliveryReceiptFlag=1 is set under [SMPP] in the smsgw.ini file -&message_id=@@MESSAGEID@@ is set in the ReceiveSMSCommand Yet, the message id that is reported back to me from the http response differs from the message id I see in the @@MESSAGEID@@ value. Have I missed something? BTW - the link above (http://support.nowsms.com/discus/messages/1/9063.html ) doesn't seem to go to a discussion related to Delivery Receipts | |||
Dani Riera New member Username: Drieran Post Number: 6 Registered: 05-2005 |
I putted also in smsgw.ini TrackSMPPReceipts=Yes but the message id differs already. Any solution ? | |||
David Derr New member Username: Davovad Post Number: 2 Registered: 08-2005 |
I tried adding TrackSMPPReceipts=Yes as well and still am not seeing an ID that correlates to the ID that I received from the original send. I think, based on the other threads I have been reading, that the matching nowsms id will not be set in the @@MESSAGEID@@ parameter that is set in the action of the 2-way setup, but rather the id of the message after id: in the return receipt will be replaced with the nowsms id of the original message that the recipt belongs to. I am not sure of this though, so some confirmation by Bryce or anyone who has successfully set this up would be appreciated. Thanks again. -David | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4812 Registered: 10-2002 |
I must have cut & pasted incorrectly on the above referenced link. It should have been: http://support.nowsms.com/discus/messages/1/9540.html There is also discussion here: http://support.nowsms.com/discus/messages/1/10825.html http://support.nowsms.com/discus/messages/1/10644.html Regarding some of the questions above:
Right. To be honest, we're still trying to figure out the best way to implement this feature. And we hadn't fully thought out how to handle the 2-way commands. But I like the idea of having a replaceable parameter contain the receipted_message_id. (The purpose of the @@MESSAGEID@@ parameter was something different. We added it because someone was having problems with their script returning errors, which causes NowSMS to retry. And they wanted a way to ensure that the same message wasn't processed more than once.) We're planning an update to address the issue discussed here (SMSC does not supported receipted_message_id parameter and puts the id in the text only): http://support.nowsms.com/discus/messages/1/10644.html So I'm going to see if we can also include an @@RECEIPTMESSAGEID@@ parameter in 2-way commands for receipts. -bn | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4816 Registered: 10-2002 |
Follow-up: We're planning to post an update within the next 24 hours that adds support for a @@RECEIPTMESSAGEID@@ parameter for allowing delivery notification receipts to be processed in 2-way scripts. I've posted some more details in the following thread: http://support.nowsms.com/discus/messages/1/10825.html And I plan on posting an additional follow-up here when the update is available for download. -bn | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4819 Registered: 10-2002 |
Follow-up: An update has been posted which addresses the issue described above. Download link for update (v5.51e): http://www.nowsms.com/download/latestpatch.zip Related threads: http://support.nowsms.com/discus/messages/1/10862.html http://support.nowsms.com/discus/messages/1/10644.html http://support.nowsms.com/discus/messages/1/10825.html |