| Loop: ThreadProcessInboundReceipts: Processing 4DDD3E79.rct |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 10, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| Erzhan Mamazhanov New member Username: Erzhankz Post Number: 1 Registered: 05-2011 |
Hi, I try to adjust NowSMS Gateway for work with SMS Сenter. The program incorrect processes "notices on delivery". In a file SMSDebug.log i see error and lines repeated 16:32:28:140 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:28:156 [10] ThreadProcessInboundReceipts: Receipt message id = 4b18758f not in database for SMPP - 192.168.4.62:8089 16:32:28:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:28:187 [10] ThreadProcessInboundReceipts: Receipt message id = 4b1888d1 not in database for SMPP - 192.168.4.62:8089 16:32:29:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:29:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:30:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:30:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:30:203 [8] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 192.168.4.62:8089 16:32:31:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:31:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:32:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:32:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:33:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:33:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct... 16:32:34:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E79.rct... 16:32:34:187 [10] ThreadProcessInboundReceipts: Processing 4DDD3E7A.rct...
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3201 Registered: 08-2008 |
Hi Erzhan, These debug messages are not actually a signal that the activity is looping. And the messages are not being processed as many times as the debug log indicates. The underlying problem is that the delivery receipt cannot be resolved. When this happens, NowSMS retries several times over a period of time (not as many times as suggested by the debug log ... most of those entries are indicative that it is not yet time to retry again), and eventually will give up. So the underlying question is ... why can't the delivery receipts be resolved? The answer to that one is actually quite simple. When you submitted the message, you didn't ask for a receipt. When no receipt is requested, NowSMS doesn't track the message ID, and won't be able to resolve a receipt message ID if one is received. As you've experienced, there are some service providers who return a delivery receipt even when one is not requested. To resolve this problem, you can configure NowSMS to request a delivery receipt. To do this, manually edit SMSGW.INI, and under the [SMPP - 192.168.4.62:8089] header, add: DefaultDelReceipt=Yes The above setting tells NowSMS to ask for a delivery receipt. If NowSMS knows a receipt is being requested, it tracks the message ID, so that the receipt can be processed. We have made changes for the next release of NowSMS so that it always tracks message IDs and is prepared to receive delivery receipts, regardless of whether or not they were requested. An interim release which includes this logic change is available at http://www.nowsms.com/download/nowsms20110523.zip. -- Des NowSMS Support | ||||
| Erzhan Mamazhanov New member Username: Erzhankz Post Number: 2 Registered: 05-2011 |
Thanks for the answer. Have established version 2011.05.23 We use 2way for creation of standard answers. When answers (delivery_natif) 2way come accepts them for a new sms and sends our standard answer. A vicious circle. Tried to add command ReceiveSMSCommand1=id:* c:\windows\system32\cmd.exe/c echo @@ Sender @@> text.txt After that messages jam in 2way queue. In additional our provider said about problem with delivery_notif. look at provaider log.txt
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3206 Registered: 08-2008 |
Yes, that would be a vicious cycle. You should not reply to delivery receipts. The echo command is just an example for testing. You would normally use a script with more intelligence. You cannot use redirection (e.g., > filename) in a 2-way command. If you want to throw the message away, define a command prefix of id:* and use the same echo command (or any other valid action), but UNcheck "Command returns response text". This way NowSMS will not try to return a response. -- Des NowSMS Support | ||||
| Erzhan Mamazhanov New member Username: Erzhankz Post Number: 3 Registered: 05-2011 |
Thanks we solved problem, DefaultDelReceipt=Yes id:* version 2010.05.24 is working with this parameters. P.S. Just for information, I meet problems with version 2011.05.23. The program showed that service is started, All Connection OK, But a web page opened through time also didn't open in general. No real connection with the SMSC. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3248 Registered: 08-2008 |
Follow-up. The 2011.05.23 version is not stable. It has been replaced with version 2011.06.08 at http://www.nowsms.com/download/nowsms20110608.zip. | ||||
all logs
