This is OK if SMSC does the re-ordering for congestion or some other reasons. But my concern is that messages should at least leave bbox in the same order by which they left the application.
Since kannel is not giving me a proper method to sequence the messages, I am forced to use SLEEP method in PHP programming. It is hanging my server horribly in the presence of big traffic, choking both HTTP web server connections as well as backend database. I would be happy to find some/any method to maintain the sequence of msgs in kannel in FIFO order. On Tue, Nov 12, 2013 at 7:38 PM, Rene Kluwen <rene.klu...@chimit.nl> wrote: > But having said the below, sms messages are not guaranteed to arrive in a > particular order. > > The remote smsc may still send out message 2 first, even when they > received message 1 first. > > > > *From:* users [mailto:users-boun...@kannel.org] *On Behalf Of *Rene Kluwen > *Sent:* dinsdag 12 november 2013 15:35 > *To:* ha...@aeon.pk; 'spameden' > *Cc:* 'kannel users' > *Subject:* RE: SQLBOX working - LIFO or FIFO > > > > There’s a ‘priority’ field in the Msg structure. > > I think it serves for the purpose that you want to. > > Just it’s you cannot set it in the send_sms table. Not sure why, but > probably the field was added later. > > It shouldn’t be difficult to add though if anyone wants to send in a patch. > > > > == Rene > > > > *From:* users [mailto:users-boun...@kannel.org <users-boun...@kannel.org>] > *On Behalf Of *ha...@aeon.pk > *Sent:* dinsdag 12 november 2013 15:28 > *To:* spameden > *Cc:* kannel users > *Subject:* Re: SQLBOX working - LIFO or FIFO > > > > Actually, if my understanding is correct (i.e. SQLBOX is already doing the > right thing by giving messages in FIFO order to bbox, but bbox is shuffling > the outgoing messages from within its buffer), then there is no point of > adding priority column. > > > > What do you say? > > > > On Tue, Nov 12, 2013 at 6:28 PM, spameden <spame...@gmail.com> wrote: > > For priority I'd suggest adding a column called priority (typically > int(3) integer between 0 and 999) and doing ORDER by that column. > > Do not forget to add an index as well or it might slow things down! > > 2013/11/12 ha...@aeon.pk <ha...@aeon.pk>: > > > Hi, > > > > Many thanks. I tried and tested it. It works fine for small chunks of > data > > (I can see SMS going out of bbox in a sequence they were entered in > send_sms > > table). However, for large amount of data (e.g. I sent a bulk of 20k SMS > via > > SQLBOX), it does not follow the same rule. Is it bearerbox which shuffles > > the order of the SMS present in its buffer (not SQLBOX)? Any > > thoughts/experiences? > > > > Is there any parameter tweak in send_sms by which I could raise the > priority > > of some SMS higher than others? > > > > Regards, > > > > > > > > On Mon, Nov 11, 2013 at 9:23 PM, spameden <spame...@gmail.com> wrote: > >> > >> Yes you can do this. > >> > >> Just alter gw/mysql_sqlbox.h and edit > >> > >> #define SQLBOX_MYSQL_SELECT_QUERY > >> > >> add there ORDER by sql_id ASC :) > >> > >> 2013/11/11 ha...@aeon.pk <ha...@aeon.pk>: > >> > Hi, > >> > > >> > Does SQLBOX work in LIFO or FIFO order? For me, it's working as LIFO > >> > which > >> > is bad if I intend to send sequential message (message 1 needs to go > >> > first, > >> > but since message 2 comes later, it goes out first). > >> > > >> > Is there a way to make it operate in FIFO sequence, like ID'ing the > >> > messages > >> > or something? > >> > > >> > Regards, > >> > Hamza > > > > > > >
