RE: Throughput discussion

Hi REne , We faced to this behaviour for some smsc supplier, The error message is trhtolling error but in fact the smsc did map to this error when it faced to queue full error on smsc side. This queue full is receive on the “store and forward” feature from smsc. The DB were the sm is saved

RE: Throttling Error

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

RE: Throttling Error

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

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

RE: Handling throttling and message queue full errorsþþ

Hi Could you tell us which version are you using ? it can be failing due to the ACK mode configured on the smsc side , if it is early ack , the smsc will acknoledge whatever each message so as it won't have a throttling error , kannel won't do nothing. Smsc shoud be on late ack ( ack coming

RE: Handling throttling and message queue full errorsþþ

Hi Tolis Man Some smsc do mapping on 0x14 message queue full error and transform it into 0x58. For the 0x58 error , the behaviour , you describe is the one by default. you can change the behaviour by setting up two parameter sms-resend-freq and sms-resend-retry on group core part from

RE: bug reporting about the retry of message when smpp gateway receive error code from smsc

Hi Alexander , Still me We follow couple of advices and here's a brief summarize of the situation. By setting up both parameter sms-resend-freq and sms-resend-retry, we minimize the risk of crashing the smsc by avoiding the unlimited retry, we also don't loose couple of messages but we have to

RE: bug reporting about the retry of message when smpp gateway receive error code from smsc

Hi Alexander Thx for advice , i agree with you , the smsc ( Comverse supplier ) do some mapping of the queue full and replace it with a throttle error code. but this is not cleaver due to the fact that if the error code are throttling error , this means that the smsc has reach his limit

RE: bug reporting about the retry of message when smpp gateway receive error code from smsc

Hi George Thx for your advice, i will check your different points , it is quite good advice, BR Marc _ De : George Karagheaur [mailto:george.karaghe...@gmail.com] Envoyé : vendredi 24 janvier 2014 18:22 À : marc.bazi...@orange.com Cc : devel@kannel.org Objet : Re: bug reporting about

bug reporting about the retry of message when smpp gateway receive error code from smsc

Hi We faced to some trouble with application that use kannel. A subscriber has got a limited number of message on the smsc queue when he is unreachable. By example if a subscriber turned off his mobile and someone or something send him message , the sms will be placed on the inetrnal db from SMSC