| ReceiptMessageId not found in our local database |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | ||||
| Francesco Fiacchi New member Username: Cybrokers Post Number: 1 Registered: 06-2017 |
Dear Sirs, We have the following situation: Incoming SMPP from customers Outgoing HTTP to provider HTTP string to provider: SENDER=@@SENDER@@&PhoneNumber=@@PHONENUMBER@@&Text=@@TEXT@@&MessageID=@@MESSAGEI D@@ To send DLR back to provider, when we have a message delivered situation from the provider, we send back to NowSMS the following string: http://192.168.1.123:8800/?User=test&Password=test123&ReceiptMessageID=59164A62& Re ceiptDelivered=yes&PhoneNumber=441234567 Problem is, NowSMS sometimes sends back to the customer the SMPP code 201, other times (TOTALLY RANDOMLY) gives to us the error "ReceiptMessageId not found in our local database". We cannot forecast when the problem comes up, practically 30% of messages gives to us 201 and the other 70% the error. How can we solve this? Thanks and regards! | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5853 Registered: 08-2008 |
Hi Francesco, There is nowhere that NowSMS generates an Error 201...especially with regard to SMPP. Where exactly are you seeing this error? The only scenario that I could imagine is that your HTTP service is returning an HTTP status code 201 (Created). You don't mention what version of NowSMS you are using. I know current versions accept any 200-series response as success...but it is possible that some older versions required HTTP status code 200 (OK). Regarding the other issue, I wonder if the problem is related..........let me explain.... Perhaps NowSMS sends URL request, but does not see a success response. NowSMS thinks the request has failed and does not add the message id to its tracking database, so it will not accept any status reports for the message ID. I would suggest looking through the SMSOUT-yyyymmdd.LOG. Do you see an OK record for these problem message IDs? I'd also ask about the version again. Older versions may be very particular, as this area of functionality is one that evolved over time in response to customer feedback. -- Des NowSMS Support | ||||
| Francesco Fiacchi New member Username: Cybrokers Post Number: 2 Registered: 06-2017 |
Dear Des, To start with, thanks for your response. The version is the last one, I downloaded the 30 days trial almost a couple of weeks ago, so I still have some time to figure out how to solve this issue! All the information exchanged through NowSMS and the HTTP server is in the post above: practically I use NowSMS as a "SMPP proxy" between the customers (all SMPP), my HTTP service and my provider (HTTP as well). I receive an HTML from the provider that is a sort of DLR, the HTML is processed by my HTPP service and I send back to the NowSMS http://192.168.1.123:8800/?User=test&Password=test123&ReceiptMessageID=59164A62& Re ceiptDelivered=yes&PhoneNumber=441234567 (practically I send this GET as it was a request in the browser's address bar). As posted before, sometimes the SMPP customer (or myself through another SMPP client) I have a 201 SMPP status code, other times I get just the 200 and when I send the same string, I get the following messages from NowSMS: "ReceiptMessageId not found in our local database" (I get this messages when I paste the URL above to the browser's address bar). What really bothers me, is that I get this error 70% of times but w/o some kind of order and/or logic. Thanks and regards!  | ||||
| Francesco Fiacchi New member Username: Cybrokers Post Number: 3 Registered: 06-2017 |
Attached a log. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5855 Registered: 08-2008 |
Hi Francesco, I'm trying to understand this 201 SMPP status code. It is not a code NowSMS will generate, and it is not a defined SMPP status code. I assume the text "201. Success: Message received on handset" is coming from the HTTP service. 200 and 201 look like HTTP status codes. The best way to resolve the issue is for me to get a more detailed look at how NowSMS is interacting with your service. To do this, we will need to enable the debug logs. On the "Serial #" page, check the box to enable the SMSDEBUG.LOG, and press Apply. Repeat your tests. I'd like to see the following log files: SMSDEBUG.LOG SMPPDEBUG.LOG SMSWEB-yyyymmdd.LOG SMSOUT-yyyymmdd.LOG SMSIN-yyyymmdd.LOG Please email them to nowsms@nowsms.com with Attention: Des on the subject line, and post a reply here to alert me that they've been sent. Also, please explain which tests worked for you, and which did not, as this will help me better understand your setup. -- Des NowSMS Support | ||||
LOG
