well, then do it in my way all the traffic in one db, and then from there route by sql regexp.
:) i do prefer simple things, they are reliable or, upgrade kannel version to the latest one regards -----Original Message----- From: Jovan Kostovski [EMAIL PROTECTED] Sent: 22 Ноември 2007 г. To: seik Subject:denied-receiver-prefix problem > Hi Seik, > Thank you for the reply, but as I said, I use Kannel version 1.3.1 not 1.4.1 > BTW in the solution that you suggested "allowed-receiver-prefix-regex" > should be replaced with "allowed-receiver-prefix-regex", and the regex > should not be quoted. > So the correct configuration for version 1.4.1 would be: > group = sms-service > keyword = default > get-url = > "http://localhost/smsservices/sms7410.php?amsisdn=%p&bmsisdn=%P&text=%a"; > allowed-receiver-prefix-regex = ^7410$ > max-messages = 0 > I'm searching for a solution for 1.3.1. > Any ideas? > Maybe some combination of "allowed-receiver-prefix" and > "denied-receiver-prefix", > butI need a clarification how they are handled. > As I said in the previous mail, when I configured the > "denied-receiver-prefix", > every amsisdn that was that was not configured as service number and was > not co listed there in "denied-receiver-prefix" was served by this handler. > The logical work flow would be: > If amsisdn starts with prefixes listed in "allowed-receiver-prefix" > and does not > contain prefix listed in "denied-receiver-prefix" should be serviced > by this handler > Is this "allowed-receiver-prefix"/"denied-receiver-prefix" handling a > malfunction in Kannel or it was projected to work > differently? > Can we this directives in combination? > Cheers, Jovan
