Re: Throttling Error

Alvaro Cornejo <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <CAO55aG_HdDag8zPTfXA9oByPaq0xpEwq71WUeezeB2U=siBkkQ@mail.gmail.com>
Hi

Eventhough, as told by Andreas, what you are being required is not
part of smpp specs, your best bet is to hack kannel code and generate
a patch for that.

Check code of smpp module to where it checks for throttling error and
add something like  IF (ThrottlingError) { sleep 60000 }

This way your smsc-smpp will sleep for the specified time whenever it
detects a throttling error. Note that this WILL DELAY AND SLOWDOWN
your queue to this smsc. I don't know kannel code so it might also
impact other parts of kannel.

Regards

Alvaro
|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
              Visitenos en www.perusms.com


On Thu, Jul 3, 2014 at 4:03 AM, Алексей Мальгин <[email protected]> wrote:
> The sms-resend-retry and sms-resend-freq parameters are not resolved the
> issue. Please look at the log in attachment. I need make kannel stop sending
> any submit_sm to SMSC, after getting 0x58 error. So submit_sm for messages
> “MQF”, “1”, “2”, ”3”, “4”, “5” shouldn’t be send, there needed delay for 60
> seconds. Then kannel should resend submit_sm for message “1”
> (sequence_number: 4), and next “MQF”, "1", "2",... How can I do this?
>
>
>
> I think there is a some misunderstanding of the issue, because my English is
> not well.
>
>
>
>
>
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, July 03, 2014 3:22 PM
> To: '??????? ???????'; 'Andreas Fink'
> Cc: 'devel Devel'
> Subject: RE: Throttling Error
>
>
>
> If you want to check this behaviour,
>
> turned off your mobile , a take a tcpdump trace , and send one message by
> one, until you get an error from the smsc, ( usually teh maximum message per
> subscriber on the smsc configuration are betwwen 10 and 25 ) depending the
> operator
>
> normally you will get an 0x000014 error message ( message queue full ) but
> often you will receive a 0x 000058 error that are throttling error for a
> message queue full situation.
>
> on this case, the retry parameter will allow you to manage the retry queue
> on kannel . if there is no paramter , kannel will take the default value (
> if i am not mistaken it is 10 attempts per minute )
>
> hope it help
>
> br
>
> Marc
>
>
>
> ________________________________
>
> De : devel [mailto:[email protected]] De la part de ??????? ???????
> Envoyé : jeudi 3 juillet 2014 12:08
> À : 'Andreas Fink'
> Cc : 'devel Devel'
> Objet : RE: Throttling Error
>
> I understand, but it’s required rule for passing the test with SMSC
> connection. When we will pass it, we will have this interval = 1 second.
>
>
>
>
>
> From: Andreas Fink [mailto:[email protected]]
> Sent: Thursday, July 03, 2014 3:03 PM
> To: Алексей Мальгин
> Cc: [email protected]; devel Devel
> Subject: Re: Throttling Error
>
>
>
> FYI, the standard doesnt say how long you have to wait until you retry after
> getting a Throttled error.
>
> It only says:
>
>
>
>             Throttling error (ESME has exceeded allowed message limits).
>
>             This type of error is usually returned where an ESME has
> exceeded a predefined messaging rate restriction applied by the operator.
>
>
>
> If you wait 60 seconds before retrying it will slow your sending down a hell
> of a lot.
>
> Its totally ok to retry a couple of seconds later to see if we still exceed
> "allowed message limits".
>
>
>
> There's nothing wrong with that. This is not an error. This is what it is
> meant to be.
>
>
>
>
>
> On 03 Jul 2014, at 09:58, Алексей Мальгин <[email protected]> wrote:
>
>
>
> Hi,
>
>
>
> Thanks for the response!
>
>
>
> It will resolve problem with resending interval, but how can I make kannel
> stop sending PDU for some time after this error? Not for this message, for
> all messages in queue.
>
>
>
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, July 03, 2014 2:46 PM
> To: Алексей Мальгин; [email protected]
> Subject: RE: Throttling Error
>
>
>
> Hello,
>
>
>
> I think this can be configured with this release using parameters :
> sms-resend-freq and sms-resend-retry.
>
> I give you an example : sms-resend-freq = 900 (15 mins) and sms-resend-retry
> = 10 : means that the retry will be done 10 times every 15 minutes after
> receiving the 0x0058 error code for throttling error.
>
>
>
> Hope this could help you..
>
> Regards,
>
>
>
> De : devel [mailto:[email protected]] De la part de ??????? ???????
> Envoyé : jeudi 3 juillet 2014 04:08
> À : [email protected]
> Objet : Throttling Error
>
>
>
> Hello,
>
>
>
> We need help with processing  Throttling Error. SMSC requires us to wait 60
> seconds and resend request. Can you help us to setup kannel well? Our config
> in attachment. Is it possible?
>
>
>
> We use Kannel 1.5.0 with sqlbox, smpp 3.4.
>
>
>
> _________________________________________________________________________________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
> ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
>
> Thank you.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.