| Throttling |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Kiran K New member Username: Kirank Post Number: 3 Registered: 11-2009 |
How can i set up or prevent Throttling/ Queue Full exceptions. Nowsms has the retry option. I need to implement the same from our side too. So what i can do . How many sms can be send in one smpp connection. Does nowsms store the message from our side and send it in specific intervals or send at the same timw when we push ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1469 Registered: 08-2008 |
Hi Kiran, I assume that this is a continuation of the following thread: http://support.nowsms.com/discus/messages/1/41988.html NowSMS does not create these exceptions. These are errors being returned by your SMS provider. The only way that you can avoid these exceptions is to follow the rules put forth by your provider. And you need to ask your provider what those rules are, as there is no way to really discover them. You can make some guesses and experiment by tuning settings, but you should ask them. Here are the informational links that I posted in response to your other throttling question:
I'll try to provide a little bit more clarification so that you can understand how to apply the information in those links. Why does a throttling error occur, and what does it mean? It means that you are sending SMS messages to your provider faster than they will allow you to. This could be a technical limitation of your provider, but it is more likely a COMMERCIAL limitation ... meaning that they have imposed a limit against your account. That is why I say that if you do not know what this limit is, you should ask your provider, because they are the one who have set a limit. When you know your limit, or want to make guesses about this limit, the link above about SMSC speed limits can tell you how to configure NowSMS to limit the speed at which it sends messages over a particular connection. You can also adjust retry settings for when throttling errors do occur. The "Message Queue full" error, or ESME_RMSGQFUL can have multiple meanings, as different providers can return this error code for different reasons. These are the reasons that we have observed: This can indicate that the SMPP server has too many queued messages and temporarily cannot accept any more messages at all. In this case, you can only wait until the server catches up by retrying later. It can also indicate that the SMPP server has too many messages pending for the specified recipient and will not accept any more messages for this recipient until it is able to deliver messages that are already in the queue to this recipient. In this case, you can only wait until the server can deliver pending messages to that recipient, and retry later. Again, your provider should be able to explain in more detail why this error is being returned, and if there is any action it is possible for you to take. Usually with message queue full errors, all you can do is retry later. It is a queue at the provider that is full ... not a queue on the NowSMS system. -- Des NowSMS Support | |||
