| Delay in the MT sent in response to an MO |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Shiby Varghese New member Username: Shiby Post Number: 10 Registered: 01-2007 |
Sir, How to handle the following scenario... In the case of applications that respond with an MTSMS in response to an MOSMS, example: information request services by SMS; a delay in the response MTSMS shall be configured. That is to say, the application shall not send an SMS in response to the originating cell phone for a configurable amount of time. Initially, that time shall be 8 seconds. Thanks and regards Shiby | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 121 Registered: 12-2006 |
Hi Shiby, There is no function in NowSMS to force a delay in response. All I could suggest ... for a short delay like 8 seconds ... would be to implement a delay in the HTTP response for the 2-way command. Just don't delay more than 120 seconds, as NowSMS will time out waiting for the command to complete. If you do implement a delay in this way, however, if you receive a large volume of messages, the messages will queue for processing by the 2-way command, and delays will increase. (You could pass the @@MSGDATE@@ and @@MSGTIME@@ parameters to your 2-way command, which will tell you the date and time at which NowSMS received the message.) To prevent unnecessary blockage, you can also configure NowSMS to allocate more concurrent threads for 2-way command processing, so that NowSMS will process multiple inbound messages simultaneously. To configure this, edit SMSGW.INI, and under [SMSGW], add 2WaySMSThreadCount=##, where ## is the number of threads to allocate. Please note that this response is not a perfect suggestion, as there is simply no function in NowSMS to force the type of delay that you describe. -- Malcolm Now Wireless Support | |||
