Re: kannel 1.2

> ...

I support everything said here, as I've had similar problems.

> >* another idea, not very clear, however .. I have several connections to
> >every smsc - because there are different numbers available for clients - and
> >I have several operators - for example in estonia 3 operators and 3
> >numbers - maybe a new parameter for smsc needs to be introduced - let's call
> >it service-group for now, which will bind together (ie have same value) for
> >all smsc connetions with similar service number. and then it should be
> >easily possible to add option to enable routing only within the service
> >groups.
> >* it could be useful to add aliases (or constants - whatever we call them)
> >into config files. 
> 
> This one might be controversial because it adds complexity to the program 
> for unclear benefits, but it seems elegant in some ways too.

I have the same problem. When I have 3 numbers - I also have 3 connections.
When these numbers go to the same operator - then there is no easy way
to distinct between the connections.

When I have three operators - for every single operator 3 numbers - I have
9 connections.

Applications unfortunately don't know to which operator or SMSC given
number belongs to. I might build all that logic into my applications but why?
As kannel is the perfect place where to take care of such things.

For now I solved it using multiple usernames-passwords (I use these to group
numbers/services - and the forced-smsc/denied-smsc logic to route
messages). For 3 it works. But when I get 4, 5, 10, 50 numbers. Then it kinda
starts becoming unmanageable (have to walk all the smsc connection lines to
add denied/accepted logic). Soon I might turn for custom alternative
configuration and generating kannel conf out of that using a perl script.

Regards,
Indrek