well, you always could read the source from here http://www.kannel.org/~mconte/sqlbox/
and kannel users mailing list like this one: http://www.kannel.org/pipermail/users/2006-October/000859.html cheers -----Original Message----- From: Aaron Simmons [EMAIL PROTECTED] Sent: 21 Октомври 2007 г. To: [EMAIL PROTECTED] Subject:keyword-regex and matching spaces > Where is sqlbox documented? Is it a new feature? > On Aug 31, 2007, at 9:05 PM, seik wrote: >> exactly >> >> sqlbox to handle all the traffic >> ONE default service and the services routing rules are applied upon >> db insert >> >> much easier to implement any new service without touching kannel >> instance at all >> >> >> >> >> -----Original Message----- >> From: Rodrigo Cremaschi [EMAIL PROTECTED] >> Sent: 31 ?????? 2007 ?. >> To: seik >> Subject:keyword-regex and matching spaces >> >>> Hello Aaron, >> >>> This seems to be kind of a philosofical discussion, but at some >>> point in time, you will find much easier to modify a script than to >>> modify the config file and restart kannel just for a minor change. >> >>> Best regards, >> >>> Rodrigo >> >>> On 8/31/07, Aaron Simmons <[EMAIL PROTECTED]> wrote: >>>> I've run into a problem with keyword-regexp and matching spaces. >>>> Kannel won't match spaces. Though it doesn't appear to be >>>> documented >>>> (clearly?) in the Kannel User's Guide, its mentioned a couple >>>> times on >>>> this mailing list. >>>> >>>> My question is: why? Does Kannel throw out everything past the >>>> first >>>> space and only feed the first word to the regexp engine? I >>>> understand >>>> that the sms-service feature is designed to facilitate single- >>>> keyword >>>> matching, but still...this seems like an arbitrary limitation. >>>> >>>> For any kind of semi-complex patterns, the user has to send the sms >>>> off to a program that can handle regex's with spaces. Its >>>> doable, but >>>> its a pain. I'd rather have all of my logic in the conf file and >>>> not >>>> split between the conf file and some other scripts. >>>> >>>> >>>> >>>> Thanks, >>>> aaron >>>> >>>> >> >> >>
