Thanks for this, pretty sure lots of users will appreciate this! However, from first glance I can see few problems here:
1. with dlr_url, if you truncate table send_sms and reset snd_id counter it might stop working or update wrong items. e.g. insert with snd_id=1 when there are other records with the same dlr_url=1 in send_sms. I'd suggest generating dlr_url based on the current time with microseconds. 2. timestamp fields `snd_sentat` timestamp NOT NULL default CURRENT_TIMESTAMP COMMENT 'The time that the message is inserted', `snd_success` datetime default NULL COMMENT 'The time that the message was delivered to the hand set', `snd_failure` datetime default NULL COMMENT 'The time that the message failed', `snd_submitted` datetime default NULL COMMENT 'The time that the message is submitted to the smsc', `snd_buffered` datetime default NULL COMMENT 'The time that the message is buffered at the smsc', `snd_rejected` datetime default NULL COMMENT 'The time that the message was rejected', `snd_intermediate` datetime default NULL COMMENT 'Time of intermediate status', `snd_last` int(11) NOT NULL default '0', not really optimal for me, I'd use 3 fields: snd_sentat - when MT was inserted into database (i.e. planned) snd_submitted - when MT was actually submitted to the bearerbox (i.e. status=8) snd_last - when was last MT updated status (rejected / sent / etc) 3. add 'from' field to the snd table as well to manipulate with source address (it's needed in 99% chances) and also add smsc_id as optional parameter. 4. Did you test your solution? What's the actual speeds you're getting? MySQL's URLENCODE() implementation is not slowing it down? Many thanks. 2013/8/12 Rene Kluwen <[email protected]> > This post explains about using mysql triggers to keep track of dlr reports > without the need of smsbox or http calls:**** > > ** ** > > http://www.blogalex.com/archives/322**** > > ** ** > > Special thanks to Alejandro Guerrieri for letting me guest-blog on his > blog.**** > > ** ** > > == Rene**** > > ** ** >
