It is correct that this is the queue at the SMSC that it is full, but I think
Kannel should have handled it differently.
We have this problem with the largest operator where I live. We have asked,
but they *will not* change the behaviour.
What happens is that the queue to a msisdn gets full. With this operator the
limit is at 100 messages to be delivered to to the msisdn.
This can easily occur with numbers becoming inactive, phones lost, automatic
appliances losing power, and so on.
Kannel treats "message queue full" as a temporary error, and will try the
message again. If you have a large outgoing queue, then this will clog up the
queue and create delays for the remaining messages.
If the reason you are getting the "message queue full" error is one of the
above, then it will not likely clear up anytime soon. So, you will continue to
get delays for your remaining queue.
I believe Kannel should treat "message queue full" as a permanent error, and
reject the message that caused it. You will get a status 16 error if using
delivery reports, and the remaining queue wont be delayed.
It is ofcourse up to the developers if they want to change this, but I've
included a tiny patch that works for us, and should fix the problem for Surya
> Thursdag 04 desember 2008 00:45:29 wrote Nikos Balkanas:
> This one is a keeper!
> ----- Original Message -----
> From: Alejandro Guerrieri
> To: Surya
> Cc: [email protected]
> Sent: Wednesday, December 03, 2008 6:53 PM
> Subject: Re: users Digest, Vol 31, Issue 1
>
>
> It's the SMSC queue which is full, not Kannel's.
>
> Talk to your SMSC provider and report the error, they're the only ones
> that can do something about it.
>
> Regards,
>
> Alejandro
>
>
> On Wed, Dec 3, 2008 at 1:26 PM, Surya <[EMAIL PROTECTED]> wrote:
>
> Thanks for the response.
>
>
>
> "SMSC returned error code 0x00000014 (Message Queue Full) in response
> to submit_sm."
>
>
>
> Is there a way to delete these messages? or any parameter in the
> kannel-config file which prevents the retry?
>
>
>
> Your help is appreciated.
>
> Thanks and Regards,
>
> Surya
>
>
>
>
>
>
> ---------------------------------------------------------------------------
>-
>
> From: Alejandro Guerrieri [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 01, 2008 10:01 PM
> To: Surya
> Cc: [email protected]
> Subject: Re: users Digest, Vol 31, Issue 1
>
>
>
> Surya,
>
> As the userguide clearly verses:
>
> "Optional the maximum number of outstanding (i.e. acknowledged) SMPP
> operations between an ESME and SMSC. This number is not specified
> explicitly in the SMPP Protocol Specification and will be governed by the
> SMPP implementation on the SMSC. As a guideline it is recommended that no
> more than 10 (default) SMPP messages are outstanding at any time."
>
> This means that kannel will open up to max-pending-submits messages
> without waiting for a response.
>
> Regards,
>
> Alejandro
>
> On Mon, Dec 1, 2008 at 1:59 PM, Surya <[EMAIL PROTECTED]> wrote:
>
>
> Thanks Alejandro,
>
>
> What exactly does max-pending-submits?
> Lets say, if max-pending-submits = 50, what will happen?
>
> Does it push 50 messages to the Bearerbox or
> Does it push 50 messages to the SMSC
>
> After pushing how much time Does it wait for? And what will happen in
> that time?
>
> Whats the role of throughput in this..
>
> Sorry too many questions.. what to do perplexed mind try to understand.
> Thanks in advance.
>
> Regards,
> Surya
> -----Original Message-----
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 30 Nov 2008 16:37:35 -0200
> From: "Alejandro Guerrieri" <[EMAIL PROTECTED]>
> Subject: Re: get mesage ID without DLR
> To: Surya <[EMAIL PROTECTED]>, "[email protected]" <[email protected]>
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="windows-1252"
>
> Surya,
>
> [This is only relevant to SMPP links, other SMSC's may have different
> behaviour]
>
> If the messages are already queued, there's not too much you can do
> about it: default kannel's priority is 0 (maximum) so you won't be able to
> prioritize anything.
>
> You can improve things a little in the future by setting the priority
> to a higher number for regular messages (valid values are 0 to 4, being 0
> the highest priority and 4 the lowest). For example, you could set 2 as
> default, and then use 0 or 1 when you want to speed things.
>
> Regarding your throughput, that "10" figure is a limit imposed by the
> SMSC I suppose. If not, you could play with some tweaking of the
> "throughput" and "max-pending-submits" parameters and see if you can get a
> better performance.
>
> Regards,
>
> Alejandro
>
> On Sun, Nov 30, 2008 at 3:47 PM, Surya <[EMAIL PROTECTED]> wrote:
> > Hi Alejandro,
> >
> >
> >
> > Message_id for billing, I actually mean that after successful
> > delivery of the message we can initiate the billing module?some kind
> > of it.
> >
> >
> >
> > %F would be the new parameter for the message_id, I guess. Hope Alex
> > Malyish completed his part.
> >
> >
> >
> > I have a big problem of the kannel queue, I can thousands of
> > messages are in the store file,
> >
> > Current throughput is 10. How do I set priority to the message to be
> > sent immediately.
> >
> >
> >
> > Can you share your experience on the kannel internal queue, as I just
> > went through this page.
> >
> > http://www.mail-archive.com/[email protected]/msg10857.html
> >
> >
> >
> > I know its different from the priority optional parameter of the
> > SMPP.
> >
> >
> >
> > And also how to the priority of the deliver_sm of the DLR message?
> > Any idea.
> >
> >
> >
> >
> >
> > Thanks in advance,
> >
> > Surya
> >
> >
> > ------------------------------
> >
> > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED]
> > *Sent:* Friday, November 28, 2008 11:18 PM
> >
> > *To:* Surya
> > *Subject:* Re: get mesage ID without DLR
> >
> >
> >
> > Surya,
> >
> > Yes, seems like everybody's using message_id for billing nowadays ;)
> >
> > Alex Malyish proposed a few tweaks that makes a lot of sens, will
> > copy to you as well when those changes are made.
> >
> > Regards,
> >
> > Alejandro
> >
> > On Fri, Nov 28, 2008 at 3:40 PM, Surya <[EMAIL PROTECTED]> wrote:
> >
> > Kudos!!!
> >
> >
> >
> > I believe you finally made it!!
> >
> > Many users face this problem of message id which is very critical for
> > all the billing purpose..
> >
> > Not only billing, we can also play with the messages, specially when
> > using SMPP.(Query, Cancel, Replace).
> >
> >
> >
> > Small request, I don't know the status of my subscription to devel
> > list, can you send me the patch.
> >
> > If they are updating the patch immediately, I'll be the first one to
> > use it.
> >
> > I have windows system which has internet, how to get the CVS check
> > out,
>
> I'm
>
> > trying to get the Tortoise CVS tool.
> >
> >
> >
> > Thanks and Regards,
> >
> > Surya
> >
> >
> > ------------------------------
> >
> > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED]
> > *Sent:* Friday, November 28, 2008 9:53 PM
> >
> >
> > *To:* Surya
> > *Subject:* Re: get mesage ID without DLR
> >
> >
> >
> > Surya,
> >
> > The patch was posted to devel a few hours ago, though it will still
> > suffer a few changes before being commited.
> >
> > Regards,
> >
> > Alejandro
> >
> > On Fri, Nov 28, 2008 at 4:30 AM, Surya <[EMAIL PROTECTED]> wrote:
> >
> > Hi Alex,
> >
> >
> >
> > Sorry, I don't mind waiting a day? work pressure sometimes wants
> > things to happen right now.
> >
> >
> >
> > Which parameter replaced %w.
> >
> >
> >
> > I also subscribed to the devel list.
> >
> >
> >
> > Thanks & Regards
> >
> > Surya
> >
> >
> >
> >
> > ------------------------------
> >
> > *From:* Alejandro Guerrieri [mailto:[EMAIL PROTECTED]
> > *Sent:* Friday, November 28, 2008 12:22 AM
> > *To:* Surya
> > *Subject:* Re: get mesage ID without DLR
> >
> >
> >
> > Surya,
> >
> > Will post the patch to the devel list when it's ready. To subscribe
> > to the list: http://www.kannel.org/lists.shtml
> >
> > The %w patch is a deprecated version of what I'm doing now. The new
> > patch will be quite similar, though the sms structure will differ. If
> > you can
>
> wait
>
> > one more day I'd recommend you to wait for the new patch to be
> > available.
> >
> > Regards,
> >
> > Alex
> >
> > On Thu, Nov 27, 2008 at 4:05 PM, Surya <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> >
> >
> > Can you forward the patch to me.. I'll try with %w
> >
> >
> >
> > I was going thorough this
> > http://www.mail-archive.com/[email protected]/msg13407.html
> >
> >
> >
> > How to subscribe to the Devel List ?
> >
> >
> >
> > Thanks and Regards,
> >
> > Surya
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
> http://www.kannel.org/pipermail/users/attachments/20081130/c212c028/attachm
>e nt-0001.html
>
> ------------------------------
>
> _______________________________________________
> users mailing list
> [email protected]
> http://www.kannel.org/mailman/listinfo/users
>
>
> End of users Digest, Vol 31, Issue 1
> ************************************
--
--------------------------------
Arne K. Haaje | www.drx.no
T: 69 51 15 52 | M: 92 88 44 66
--------------------------------
--- smsc_smpp.c~ 2008-12-04 12:49:41.000000000 +0100
+++ smsc_smpp.c 2008-12-04 12:49:41.000000000 +0100
@@ -717,7 +717,6 @@
static long smpp_status_to_smscconn_failure_reason(long status)
{
switch(status) {
- case SMPP_ESME_RMSGQFUL:
case SMPP_ESME_RTHROTTLED:
case SMPP_ESME_RX_T_APPN:
case SMPP_ESME_RSYSERR:
