SMSCMsgId

SMSCMsgId SearchSearch
Author Message
Andrew Katz
New member
Username: Akatz0813

Post Number: 2
Registered: 09-2005
Posted on Monday, January 23, 2006 - 11:33 pm:   

Hello, I am trying to have NowSMS send back the SMSCMsgId back via http. I do not believe that my SMSC provides any delivery receipts, but the information I need is in the response of the SMPP message.

I have attached snippit of my smppdebug.log at the bottom of this post. The entry in the smsdebug.log is:

2006-01-23 18:01:04,43D5602F.req,192.168.10.107,5555555555,OK -- SMPP - server.domain.com,SubmitUser=user;Sender=10000;SMSCMsgId=1j0j9u001v2iaq00vm44f2bvnn30;Text="Test2"

I have the following parameters set:

1. smsgw.ini, SMPP Section, DeliveryReceiptFlag=1
2. smsgw.ini, SMSGW Section, TrackSMPPReceipts=Yes

I have tried including ReceiptRequested=Yes in the request to NowSMS.

I am running version 5.51f.

How can I get this to work?

application/octet-streamSMPPDebug.log
smppdebug.log (1.0 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5449
Registered: 10-2002
Posted on Thursday, January 26, 2006 - 08:00 pm:   

Hi Andrew,

If I understand your question correctly ... unfortunately this ID is not available via HTTP.

When you submit the message to NowSMS via HTTP, NowSMS queues the message on the NowSMS server, and returns its own internal message ID in the HTTP response. At this time, the message delivery via SMPP has not yet been attempted, so no upstream SMPP message id is available at this point.

When the message is submitted to the upstream SMPP server, we do record the upstream message id in the SMSOUT-yyyymmdd.LOG file. However, there is not HTTP callback that occurs at this time. (We have been evaluating adding a new HTTP callback here for NowSMS 2006 ... but at this point, I am not sure whether or not this will make the initial release, as it is still in the development queue.)

Keep in mind that when the delivery receipt comes back from the SMSC ... if you have TrackSMPPReceipts=Yes enabled ... NowSMS will at this point translate the upstream SMPP message id back into the originally assigned NowSMS message ID. This way, when the delivery receipt gets routed back to your application, you see the NowSMS message id ... which matches up to the NowSMS message id that was returned when the message was originally submitted to NowSMS.

I would suggest updating from v5.51f (get http://www.nowsms.com/download/latestpatch.zip), because the TrackSMPPReceipts=Yes feature was very much a "work in progress" in that release, and a number of issues related to this functionality were resolved after that release.

-bn