Kannel is suffering

>3) This solution cannot be abstracted and used for all SMSC interfaces
>   (unless all you want is the 'ts' field reported for every SMSC).

It appears to me, that progress of the Kannel project is severely hindered by
a group of people, which think that the lowest common denominator of all
features are  the only things, that can be implemented.

If Kannel is not going to deteriorate into an academic exercise of 'pure'
design, we need a changed view of this. There are real world needs, which must
be covered. 
It is not acceptable, that because a feature is not available in all
protocols, it should not be available in any.

The core of Kannel must of course be a generic engine, but there must be a
framework, so that protocol-specific features can be added to this engine with
minimal impact to others.

I think the 'guardians of the sacred treasury' should do some rethinking and
find out how this framework can be implemented. This would benefit Kannel
tremendously.

- Jørgen Thomsen