Of course you won't be able to pass a message id if you set the dlr-url on the .conf file, you need to set the message id on each message you send (as part of the dlr-url) just like "&myid=1234".
As usual, check the user guide, There's an example of dlr-url on the "SMS Delivery Reports" chapter. Regards, Alejandro On Mon, May 5, 2008 at 7:27 AM, Kaone Mathuba <[EMAIL PROTECTED]> wrote: > Hi, > > I get the concept of what is supposed to happen but my problem is the > syntax of the dlr-url to pass the message-id. From the manual I see it can > be passed to sendsms script but I also see it can be placed under > sendsms-user on the .conf file. On the latter I don't how it can be used to > pass parameters rather for receiving from the smsc. > > Can you please help me with an example of how to pass the dlr-url with > mesage-id to sendsms or anyhow you do it. > > Regards > > Kaone. > > > On 10/15/07, Alejandro Guerrieri <[EMAIL PROTECTED]> wrote: > > > > Looks fine, you'll have to specify dlr sql storage on core group also. > > > > The unique key for a primary key field is unneccesary I suppose, but > > won't hurt anyway (primary keys _are_ unique by definition). > > > > Kannel logs the message as sent when the SMSC accepts it. You'll also > > have to develop a script to handle DLR's of course. > > > > The process is as follows: > > > > - When you queue a message by any means (for example, inserting a row > > on send_sms or calling the sendsms interface), you should set dlr-mask > > (to tell which message status you want to "capture") and dlr-url > > (pointing to your dlr script). > > > > - You should include some sort of message_id identifier on your > > dlr-url field in order to be able to match your message against the > > dlr request. What I do is first insert the message on a table and use > > the insert-id from that table as message identifier to pass to the > > dlr-url. > > > > - When the message status changes, kannel calls the url script with > > the parameters properly loaded. The script will be called as many > > times as the message status changes. > > > > - Your script should update the table (or do whatever you want it to > > do). Since the message-id will be included you shouldn't have any > > problem matching against it. > > > > Hope it helps, > > > > Alejandro > > > > > > On 10/15/07, Michael Habashy <[EMAIL PROTECTED]> wrote: > > > I have been searching for stuff on dlr and sqlbox --unable to find any > > > thing. > > > I have used the config below for mysql config. > > > I have a couple of questions: > > > 1. Is there anyhting I am missing??? > > > 2. will kannel log the sms messege after it sends it ? or before? I > > just > > > want to know that kannel has sent the messege. I can always write a > > sql > > > query to see if the db was updated....if not ..i can try to send it > > anohter > > > way. > > > > > > > > > group = mysql-connection > > > > > > > > > id = mydlr > > > > > > host = localhost > > > > > > username = joey > > > > > > password = jtjjj > > > > > > database = sms > > > > > > max-connections = 1 > > > > > > group = dlr-db > > > > > > id = mydlr > > > > > > table = dlr > > > > > > field-smsc = smsc > > > > > > field-timestamp = ts > > > > > > field-destination = destination > > > > > > field-source = source > > > > > > field-service = service > > > > > > field-url = url > > > > > > field-mask = mask > > > > > > field-status = status > > > > > > field-boxc-id = boxc > > > > > > > > > CREATE TABLE `dlr` ( > > > `smsc` varchar(40) default NULL, > > > `ts` varchar(40) default NULL, > > > `destination` varchar(40) default NULL, > > > `source` varchar(40) default NULL, > > > `service` varchar(40) default NULL, > > > `url` varchar(255) default NULL, > > > `mask` smallint(6) default NULL, > > > `status` smallint(6) default NULL, > > > `boxc` varchar(40) default NULL, > > > `dlr_id` bigint(20) unsigned NOT NULL auto_increment, > > > `tsread` timestamp NOT NULL default CURRENT_TIMESTAMP, > > > PRIMARY KEY (`dlr_id`), > > > UNIQUE KEY `dlr_id` (`dlr_id`) > > > ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ; > > > > > > > > > > > > > > > > > > On 10/12/07, Alejandro Guerrieri <[EMAIL PROTECTED]> > > wrote: > > > > Michael, > > > > > > > > You can use sqlbox to enqueue MT messages, but it won't provide a > > > > native way to handle errors. > > > > > > > > In order to handle errors and delivery reports, you should use the > > DLR > > > > functionality on kannel. It could be used to save message delivery > > > > status on Kannel side or, if your SMSC supports it, to track the > > > > delivery of the messages up to the "real" phone terminals. > > > > > > > > Check on the user guide and list archives for more info about DLR's > > > > and sqlbox, I think that with some script "glue" and thos two > > elements > > > > you can achieve what you're looking for. > > > > > > > > Hope it helps, > > > > > > > > Alejandro > > > > On 10/12/07, Michael Habashy <[EMAIL PROTECTED]> wrote: > > > > > Can i send sms messeges from mysql ? > > > > > I would like to get a better way of tracking messeges that get > > sent out > > > via > > > > > kannel. > > > > > > > > > > There is no error handlign...that i can see in kannel to help > > that > > > along. > > > > > > > > > > thanks > > > > > mjh > > > > > > > > > > > > -- > > > > Alejandro Guerrieri > > > > Magicom > > > > http://www.magicom-bcn.net/ > > > > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > > > > > > > > > > > > > > > > > -- > > Alejandro Guerrieri > > Magicom > > http://www.magicom-bcn.net/ > > LinkedIn: http://www.linkedin.com/in/aguerrieri > > > > >
