So you're suggesting simply have kannel forward everything to some
other service:
group = sms-service
keyword = default
get-url = http://localhost:55555/gotsms?text=%a&from=%p
This design makes sense of course (and will likely be the way I go).
However, I'm still not sure why kannel's regexp's are implemented the
way they are. Is it simply that no one is using the regexp feature
and they're just parsing the smses in their own software?
On Aug 31, 2007, at 8:55 PM, Rodrigo Cremaschi wrote:
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
