Re: Feature request: storing incoming/outgoing messages in database

Hi,

heh, one thing I can say: If you have need in such interface then just 
implement it and send us patch :)

On Tuesday 28 October 2003 17:06, Rory Campbell-Lange wrote:
> I've hacked the dlr mechanism to do an update rather than a delete.
> Pretty simple to do -- even though I don't know C!
>
> I'd be very keen for Kannel to dispense with the http interface
> altogether and only supply database connectivity. Working with Postgres
> triggers and foreign keys etc would make managing multiple users etc
> very simple. However that would make it a different project, and Kannel
> works very well as it does at the moment.
>
> One issue that this does bring up, though, is that having native db
> support (I'd recommend Postgresql here, again, due to its excellent
> reliablity and BSD-style license) seems vital for persistant and unique
> message ids across all SMSC groups.
>
> To persist with the db paradigm further:
>
>           +------------------------------------------+
>
>           |      +--------+         +----------+     |
>
>  sms in/  |      |        |         |          |     |    user's db
>       <---+----->| kannel +<------->| postgres +<----+--->
>    out    |      |        |         |          |     |    interface
>
>           |      +--------+         +----------+     |
>
>           +------------------------------------------+
>
> This would mean replacing the kannel interface with the user's db
> interface. I suppose this is no more complex than the existing work you
> have to do with cgi or whatever to support multiple kannel users over
> the internet.
>
> Cheers!
> Rory
>
> On 28/10/03, [email protected] ([email protected]) wrote:
> > Hi,
> >
> > Right now I'm using kannel towards Telenor (Norwegian telco running
> > Logica CMG SMSC) and it works fine (when you remember to specify
> > interface-version=33, that part took some time to figure out :-P).
> >
> > Actually the only part of kannel I use is the smpp parsing/sending,
> > "forwarding" of the message to a URL, and sending a message through the
> > SMPP SMSC.
> >
> > In this context I'm wondering if the following extensions have been
> > thought of:
> >
> > 1. Store incoming messages into a sdb supported database (like you do
> > with dlr's) ?
> >
> > 2. Have a thread in smsbox that checks a table in a database for messages
> > that are to be sent to a smsbox compatible protocol.
> >
> > With regards,
> > Ken A. Rederg?rd

-- 
Best regards / Mit besten Grüßen aus Düsseldorf

Dipl.-Ing.
Alexander Malysh
___________________________________________

Centrium GmbH
Vogelsanger Weg 80
40470 Düsseldorf

Fon: +49 (0211) 74 84 51 80
Fax: +49 (0211) 277 49 109

email: [email protected]
web: www.centrium.de
msn: [email protected]
icq: 98063111
___________________________________________

Please avoid sending me Word, Excel or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html