Yep - agree with everyone about adding regexp however I also don't have the time needed to dedicate to such changes - so for the moment I'm moving more advanced keyword mapping out of Kannel and relying on the default service to pass all requests through to the external system.
Another point, though not directly related, is whether we currently have an option to pass through the ASCII string received to an external program unaltered. As far as I think at the moment there is no '%a - insert the message received from the user as ascii' in the options, just a use keyword and subsequent words (which is a problem if you have multiple spaces in messages. Quick to add but would be handy for me. Alex ----- Original Message ----- From: "Bruno Rodrigues" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 04, 2003 8:03 PM Subject: Re: [RFT] Kannel Keyword Handling > Alan McNatty <[EMAIL PROTECTED]> wrote: > > Hi Alex, > > > > Why not simply support reular expressions. I thought I'd read something > > somewhere about someone looking at building this in (ie: if supported > > compile in regexp support). If support is not available downgrade to > > simple keyword as we have now. > > +1 for regexp and as I said, I can help with this, but I don't have time > to implement myself > > > > To me though if you want to have the redirection all happen at the > > kannel level (rather than application layer above it) we really need > > support for config reload. That is, I can see you wanting to add/remove > > filters more often than you'd want to restart kannel. Here the ability > > to reload the config would be nice. > > I'm working on reload. I already have it for wapbox and I'll do it for > the other boxes > >
