|Message ID missing when stopping/starting NowSMS||Search|
|SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 11, 2011 » Message ID missing when stopping/starting NowSMS||« Previous || Next »|
Post Number: 51
Every morning at around 6:30, a daily task runs that restarts the NowSMS service. This is simply done to refresh the SMPP binds that we have running.
However, since we installed the 2010.11.04 version, every morning 1 or 2 messages that are submitted are returned with a blank Message ID.
From what we can see, the message has indeed been submitted, but the message ID is not returned upon the HTTP submission.
Any chance you guys can attempt to recreate the error and determine if there is something wrong?
|Des - NowSMS Support
Post Number: 2719
I know we've made changes to address issues where NowSMS does not respond qu ickly enough to a shut down request. My guess is that the HTTP response is b eing skipped because a shutdown has been requested.
While we investigate, I may have a workaround. If you look at SMSGW.INI, you will find a setting. I am away from a computer at present (lunch), but it i s something similar to ConfigurationUpdateLastRestart with a date time stamp . If you update this setting, NowSMS will shutdown and restart.
As I think about it, however, I believe that shutdown would behave the same w ay. We will need to investigate, but my guess is this related to being more responsive to a shutdown request.
-- Des (NowSMS Support)
|Des - NowSMS Support
Post Number: 2742
A follow-up. I've asked our engineers to take a closer look at this, but they don't agree with my theory.
If the message was accepted, there will be an HTTP response that include a message ID.
If the timing of the shutdown request is such that it is triggered during the processing of an HTTP request, NowSMS may decide to shutdown without sending the message. In this case, no message ID is returned ... but the text of the message does say "Message submitted".
They claim that no changes have been made in this area. It has always been this way, in order to allow the service to be stopped if someone has accidentally submitted a large number of messages and needs to stop it immediately. (As each recipient is processed, the shutdown request status is checked.)
Is it possible that you are getting a blank message ID but the message has not actually been submitted?