Hi, I'm experiencing the same problem, and it's getting a critical issue.
Can anyone confirm if: 1) that's reported in the bug database? To me it seems this is not the same as bug #352, which is dated back to 2006 and relates to retries because of encoding options, not for being a multi-part message 2) that's solved in CVS ? 3) what's your temporary work-around in the meanwhile ? TIA -------- Forwarded Message -------- From: sheena sheena <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: users@kannel.org Subject: Re :RE: Re :Re: sms-resend-retry ignored Date: 16 Feb 2007 08:10:43 -0000 Hi Problem is about kannel retrying every sec even after setting retry interval of 1hour. sms-resend-retry and sms-resend-freq both go for toss. Needs to get this fixed as the smsc gets loaded if there some 10-20 nos getting retried 10msgs/sec. Regards sandesh K ÄçìÞôñçò Åõìïñöüðïõëïò wrote No problem … code 14 (Message Queue Full) is used by many operators to denote mailbox full, which means that the controller has the maximum allowed messages in queue for the specific user phone number. Switch on debug to see the phone number as well. Errors will disappear as soon as the user turns on his phone and receives the queued messages, or as soon as kannel stops retrying, in which case logging will stop. Dimitris Evmorfopoulos From: sheena sheena [mailto:[EMAIL PROTECTED] Sent: Thursday, February 15, 2007 10:31 PM To: [EMAIL PROTECTED] Cc: users@kannel.org Subject: Re :Re: sms-resend-retry ignored Hi Problem is observed in latest CVS cvs-20070129 versions. Regards Sandesh K 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:54 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2007-02-13 16:26:55 [4583] [6] ERROR: SMPP[xxxxxx]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. "Alejandro Guerrieri" wrote Adam, As a rule of thumb, if having problems with older versions of Kannel, first step it's to upgrade to latest CVS, since many errors are already corrected on CVS. If after upgrading the problem persists, then inform the list since it may be a previously unseen or undetected bug. Regards, Alejandro On 2/3/07, Adam Trueman wrote: > > > Hi, > > We have been having problems with the Message Queue Full error with Kannel > 1.4.0. Kannel used to send a lot of retry requests (about 10/sec) putting > unwanted load on SMSC and causing delays in the handling of other messages. > > With the introduction of sms-resend-retry and sms-resend-freq in Kannel > 1.4.1 the problem was expected to have been solved. So we have upgraded to > Kannel 1.4.1 stable release. These parameters do control the problem for > some time, but the problem appears a few hours after starting kannel. > > It appears that whenever Message Queue Full error occurs for a concatenated > message split in parts, sms-resend-retry and sms-resend-freq dont apply, > putting kannel again in the same state, generating a lot of retry requests > badly affecting the performance. > > Is there a solution to the problem? Any help is greatly appreciated. > > Thanks > Adam > > ________________________________ > Be a PS3 game guru. > Get your game face on with the latest PS3 news and previews at Yahoo! Games. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y m�viles desde 1 c�ntimo por minuto. http://es.voice.yahoo.com
