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 from the mobile ) . I perform lot of test for this particular error code , and i can tell you that ii is working properly. Br Marc
_____ De : tolis man [mailto:vito...@hotmail.com] Envoyé : mardi 22 avril 2014 11:01 À : marc.bazi...@orange.com; devel@kannel.org Objet : RE: Handling throttling and message queue full errorsþþ Hello, On kannel core group these variables are set to: sms-resend-retry = 5 sms-resend-freq = 60 But when the Network Operator that requested this behavior tests, we fail to pass. The tests are ran by them using the auto-response we have setup for this smsc connection with sms-service group. Is there anything else I could try? Best Regards, _____ From: marc.bazi...@orange.com To: vito...@hotmail.com; devel@kannel.org Subject: RE: Handling throttling and message queue full errorsþþ Date: Wed, 16 Apr 2014 11:13:44 +0400 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 configuration file. By doing this you can build a look like retry mechanism that are generally located on smsc side. regarding the 0x14 error , well , try first to see if your smsc do not map the error , because for my situation these two error could not be separate due to the mapping of smsc. Now to treat differently these two errors , as it is temporarely error it should be manage on the same way. I don't know how to manage it on kannel side. Hope it help Br Marc _____ De : devel [mailto:devel-boun...@kannel.org] De la part de tolis man Envoyé : mardi 15 avril 2014 17:59 À : devel@kannel.org Objet : Handling throttling and message queue full errors Hello I have a question concerning some specific behaviour of kannel on 2 specific errors This behaviour is a requirement for one smsc connection, I have also posted this on commercial mailing list of kannel, unfortunately I didn't get any response. What I need to setup is: for the errors: 1. 0x58 Throttling Error 2. 0x14 Message Queue Full -- 1. The requirement says that when I receive a throttling error message (0x58), the needed behaviour is: Stop sending any Submit_sm for 60 seconds. Any more outgoing Submit_sm's must be placed to the queue. The message, which get an error must be placed 1st in the queue. After 60 seconds timeout, continue sending normally, according queue. 2. If I receive a Message Queue Full error (0x14), the needed behaviour is: Resend message. Try to resend it only 3-5 times. Every time you get an error, place message at very end of queue. -- The smsc connection I have setup is: group = smsc smsc = smpp source-addr-ton = 0 source-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 enquire-link-interval = 60 reconnect-delay = 90 throughput = 1 max-pending-submits = 1 wait-ack = 60 validityperiod = 4340 *It must be in synchronous mode too... I need to fix the behaviour of this connection for these two errors. Is there anyone who could help me on this? If so please email me. Thank you in advance, _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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.
