there is nothing to be done about this. Kannel does stop sending if it gets a
throttling error and resumes a little bit later.
This is part of the protocol and does not require any further config settings
On 03 Jul 2014, at 05:08, Алексей Мальгин alexey.mal...@gmail.com wrote:
Hello,
We
2014-07-03 10:16 GMT+04:00 Andreas Fink af...@list.fink.org:
there is nothing to be done about this. Kannel does stop sending if it
gets a throttling error and resumes a little bit later.
This is part of the protocol and does not require any further config
settings
Yup. Alexey, you should
This is the expected behaviour. It will retry a few seconds later.
You can see in the log that after every throttling error you got, it stops
sending for 2 seconds.
On 03 Jul 2014, at 09:44, Алексей Мальгин alexey.mal...@gmail.com wrote:
Thanks for the response!
there is nothing to be
Hi
You can set up the configuration file with sms-resend-freq ( in sec ) and
sms-resend-retry (number of retry ) in order to change the default value for
retry.
You can , by doing this , simulate a retry mechanism that you can find on
smsc server
br
Marc
_
De : devel
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
On 03 Jul 2014, at 09:47, marc.bazi...@orange.com wrote:
Hi
You can set up the configuration file with sms-resend-freq ( in sec ) and
sms-resend-retry (number of retry ) in order to change the default value for
retry.
You can , by doing this , simulate a retry mechanism that you can find
No all time. Some times it stops sending for 1 seconds , sometimes not stops at
all. Is there a way to set this interval to fixed value, 60 sec for example.
From: Andreas Fink [mailto:af...@list.fink.org]
Sent: Thursday, July 03, 2014 2:47 PM
To: Алексей Мальгин
Cc: spameden; devel Devel
Hi, Mark,
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: marc.bazi...@orange.com [mailto:marc.bazi...@orange.com]
Sent:
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: khaoula.zou...@sofrecom.com [mailto:khaoula.zou...@sofrecom.com]
Sent:
Marc,
Sorry for the mistake with name J
From: Алексей Мальгин [mailto:alexey.mal...@gmail.com]
Sent: Thursday, July 03, 2014 2:57 PM
To: 'marc.bazi...@orange.com'; 'devel@kannel.org'
Subject: RE: Throttling Error
Hi, Mark,
Thanks for the response!
It will resolve problem with
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
throtlling error is a type of error that include bandwith exceeding alert
but also message queue full on a handset ( for a specific message ). this is
due to error mapping done on such smsc supplier.
the retry are done when such type of error happened.
we did lot of test on lab , and on my point
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:af...@list.fink.org]
Sent: Thursday, July 03, 2014 3:03 PM
To: Алексей Мальгин
Cc: khaoula.zou...@sofrecom.com; devel
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
On 03 Jul 2014, at 10:21, marc.bazi...@orange.com wrote:
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
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 6 }
This way
modified, changed or falsified.
Thank you.
-- next part --
An HTML attachment was scrubbed...
URL:
http://www.kannel.org/pipermail/devel/attachments/20140703/e1f9f823/attachm
ent.html
-- next part --
A non-text attachment
Hi Alex,
I've considered this - but I'm worried about performance in and out of
serializing complex data structures as well as additional networking
overhead that will be added in this case.
Looking for minimal barrier and minimum performance regression :)
Cheers,
D
On 3 July 2014 09:27,
18 matches
Mail list logo
