Accounting callback timeout | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
Author | Message | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 104 Registered: 01-2008 |
How to increase a waiting time from accounting callback? As after 20 seconds of expectation, NowSMS returns "Error: Message Quota Exceeded". Whether probably after the waiting time expiration to return this error, and for example "Accounting callback timeout"? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2415 Registered: 08-2008 |
Hi Alexandre, 20 seconds is currently hard coded. Are you sure you want to increase this? Increasing it may cause other protocol timeout problems. -- Des NowSMS Support | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 106 Registered: 01-2008 |
Yes, because we see sometimes an error "Error: Message Quota Exceeded" also we do not understand because of what it has occurred, it would be desirable to increase a waiting time till 1 minute (or that it was possible manually in SMSGW.INI to specify an interval) but only that NowSMS returned not "Error: Message Quota Exceeded", and any other value, for example "Error: Callback timeout" | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2419 Registered: 08-2008 |
Can you run with the SMSDEBUG.LOG enabled? In recent versions, more information is logged in the debug log following a text string of "MessageAccountingReject:" Additionally, the HTTP error returned to clients contains additional information in the text of the reply indicating the source of the failure. | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 107 Registered: 01-2008 |
In SMSDEBUG.LOG i see: 11:42:35:207 [18] HttpResponseWait: Expected 0 bytes, got 0 bytes 11:42:35:207 [18] HttpResponseWait: 11:42:35:207 [18] RetrieveURL: timeout waiting for response 11:42:35:207 [18] WaitForSocketClose: WinSock reported ioctlsocket complete 11:42:35:207 [18] ThreadProcessConnection: Request processing complete 11:42:43:207 [18] ThreadProcessSMPPConnection: Processing SMPP connection from 192.168.1.214... In response i see: Error: Message Quota Exceeded | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2423 Registered: 08-2008 |
The additional information that I referenced earlier was added inthe 2010.06.28 update. However, it does sound like a timeout. We could make this timeout configurable, however, I would be concerned that accounting callbacks that sometimes take 20 seconds to process may lead to other unexpected protocol failures. (In particular with regard to async SMPP.) It would be better to resolve whatever issue is causing the accounting callback to process for so long. There is also a potential that your web server or script may be having a problem with NowSMS use of keep-alive sockets. You may want to try disabling them by adding AccountingKeepAlive=No under the [SMSGW] header of SMSGW.INI. (If NowSMS does encounter a timeout problem using a keep-alive socket, it automatically opens a new connection and tries again, so I'd be surprised if there was a problem in this area, but I am aware of one customer who had to disable accounting keep-alive sockets in their environment.) -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2425 Registered: 08-2008 |
The additional information that I referenced earlier was added inthe 2010.06.28 update. However, it does sound like a timeout. We could make this timeout configurable, however, I would be concerned that accounting callbacks that sometimes take 20 seconds to process may lead to other unexpected protocol failures. (In particular with regard to async SMPP.) It would be better to resolve whatever issue is causing the accounting callback to process for so long. There is also a potential that your web server or script may be having a problem with NowSMS use of keep-alive sockets. You may want to try disabling them by adding AccountingKeepAlive=No under the [SMSGW] header of SMSGW.INI. (If NowSMS does encounter a timeout problem using a keep-alive socket, it automatically opens a new connection and tries again, so I'd be surprised if there was a problem in this area, but I am aware of one customer who had to disable accounting keep-alive sockets in their environment.) -- Des NowSMS Support | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 109 Registered: 01-2008 |
Ok. Thanks. Well we will try to understand, because of what there are these timeout ` s. In new update NowSMS there will be a manual adjustment timeout? And very much it would be wanted, that instead of "Error: Message Quota Exceeded" other message came back at timeout, for example "Callback timeout" | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2435 Registered: 08-2008 |
Hi Alexandre, I've just done some testing in the update that I mentioned before, and can confirm that the text is changed. For example: Error: Error from Accounting Callback -- DNS Lookup failed for xxxxxxxxx Error: Error from Accounting Callback -- HTTP timeout error or invalid server response | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 113 Registered: 01-2008 |
This text update in new 2010-08-13 version ? So what about timeout configurable ? | |||
Alexandre Frequent Contributor Username: Alexd Post Number: 115 Registered: 01-2008 |
About text i see in new version big thanks! | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2443 Registered: 08-2008 |
Text update yes. Configurable timeout no. (Will it happen, I don't know yet. There is concern that an increased timeout value will lead to other unexpected protocol processing problems.) |