| SMPP Server throttling SMS rate |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Don Rosen New member Username: Dr10 Post Number: 5 Registered: 10-2008 |
We've set up NoSMS as an SMPP server so our application can communicate with it via SMPP connection. Have also set up this user account to throttle outgoing SMS to 5/minute. The idea is that the app can send a batch of mesages which NowSMS will then queue and send at 5/min. However NowSMS seems to be throttling the input as well, as it takes 12 or so seconds for NowSMS to respond to our application that a message has been queued. If we don't wait for this response before sending the next SMS only three messages are queued (all that shows in SMSWeb and SMSout logs. What are we missing? | |||
| Don Rosen New member Username: Dr10 Post Number: 6 Registered: 10-2008 |
Note that there's no problem through normal http account in sending large number of messages which get queued and sent at our 20/min license rate. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1355 Registered: 08-2008 |
Hi Don, You've defined the throttling in the setup of the "SMS Users" account, then it slows down the rate at which messages are accepted over the SMPP connection. There is some buffering, as the submit acknowledgements are delayed, and I would expect more than 3 messages to be buffered. But most SMPP clients are going to time out if they don't get a response within "x" seconds ("x" often being hard coded into the app). If an app submits 3 messages in this scenario, it is going to get a submit response for the first one in 12 seconds, the next in 24 seconds, the next in 36 seconds. That would exceed the timeout in many apps. For a speed this slow, having the app submit in synchronous mode (wait for response) would be advisable. This setting is better for higher speeds where you're trying to limit an app to 1 per second. -- Des NowSMS Support | |||
