Hello, priority value is in use for the "general" queue. I think as soon a SMS has been assigned to a SMSC queue, it is not possible to let them going faster. if you are using smpp, it could be done by using another smsc channel and some php code to assign high priority sms to this smsc. hope it helps regards
_____ From: Gustavo Mohme C. [mailto:[EMAIL PROTECTED] Sent: mercredi 10 septembre 2008 11:46 To: Daniel Camacho - PA Cc: [email protected] Subject: Re: Multiple connections Thanks everyone for the replies. What I did, following info.ubichip advice, was to set all the messages in the queue with a priority value of 3. All the other "emergency" messages had a priority of 0. Nevertheless, all the emergency messages where still queued at the bottom and only sent when kannel was done sending priority 3 messages. In other words, it seems kannel doesn't respect priority values. Am I doing something wrong? Regards, Gustavo 2008/9/10 Daniel Camacho - PA <[EMAIL PROTECTED]> Gustavo Mohme C. wrote: Hi All, I've been successfully using Kannel for over a month now and it's working rather well! Here is my scenario: I'm using the latest stable version of Kannel and connect to an SMSC using SMPP. I only have 1 SMPP connection at the moment. On an average day i send around 70,000 sms which I separate on two batches. The problem is that during the sending process(which in total takes around 5 hours each day), if someone sends an sms, it will be processed and queued until all the previous messages have been sent. This means that during 5 hours each day, users will not get an immeadiate reply. To solve this, I was thinking on asking my smsc for another connection and use two connections: 1 transmitter for sending daily sms and 1 transeiver for sending and replying sms. Is such a configuration possible? Is there a better solution to my problem? Any help would be greatly appreciated. Regards, Gustavo -- This message has been scanned for viruses and dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is believed to be clean. About the bottle neck in your waiting pool to process and send after the qeued batch is sent (hours). I solved this by doing some work arround. I created a table somewhere in the same databaseserver with (almost) the same "send" table structure. Almost becouse I manage my own "priority" field, and a "status" field for indicating if sent or not. I fill this table with the 70K sms with a priority of 3 and status of 0(not yet sent) A perl cron job runs every minute to select messages from this table and inserting them into the send table. "1" is the highest priority It reads for "ALL" the messages with a priority of 1, update its status to 1 (marking as sent), and insert "ALL' of them in the send table. Next it reads a chunk of 50 for the priority 2, update its status to 1 (marking as sent), and insert this chunk in the send table. Next ir reads a chunk of 25 for the priority 3, update its status to 1 (marking as sent), and insert this chunk in the send table. This will be done every minute (as my crontab allows me) untill all are gone. You can try different chunks per priority. Gerdaniels -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
