|Weird Problem, Delivery Report ID sometimes unknown||Search|
|SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 08, 2009 » Weird Problem, Delivery Report ID sometimes unknown||« Previous || Next »|
Post Number: 7
I must say your support is the best i`ve had online and would love to use your product even more.
Weirdly enough, when a SMS is being sent via your HTTP page. The report received back from the service provider is id:unknown.
The weridest thing is that, When i send a message via my PHP script i have written. Using the http://localhost:8800?Phonenumber=1231232&Message=1231231 (i`m using the prewritten function sendSMS that your site has provided with a few modifications to database.
And the Report received back contains the IDwhatever was sent messageID) compared to unknown.
This was experienced with the SAME GSM modem and the same server. Any ideas why the php script works with reports and the script that is installed by default doesn't work? Just want to clarify this so i don't get it complicated and mixed up before i change a new GSM modem.
|Des - NowSMS Support
Post Number: 533
The only thing I can think of is that in some versions there was a problem with receipt tracking when the modem driver name included a "#" character. (This happens when you install more than one modem with the same driver, which is actually quite a common configuration issue.) This effected NowSMS 2006.
Another issue that could effect things is that NowSMS only saves tracking information if it thinks a delivery receipt is being requested. If it receives a receipt for a message for which no receipt was requested, then the id will be "unknown".
So if you're sending an SMS from our web interface, by default, NowSMS is not going to think that a delivery receipt is being requested, and it won't record the tracking information ... unless you have ReceiptRequested=Yes under the [SMSGW] header of SMSGW.INI. That setting causes NowSMS to default to requesting a delivery receipt for all messages submitted via HTTP.
If this doesn't explain the problem, then I'd like to see an SMSDEBUG.LOG showing the two message submissions, and the resulting delivery receipts. That should provide some additional clues.