Thanks for the prompt answer!
I read the sqlbox FAQ but my understanding was that sqlbox sits in the
middle so that bearerbox and smsbox don't see each other. What confuses me
is sqlbox insert table. It is supposed to contain messages (MO/MT) not yet
processed by their destination handlers (bearerbox for MT, smsbox for MO).
So I realized that having beaerbox running with sqlbox connected to it would
accumulate MO messages until smsbox is started.
Is sqlbox insert table used only for manual inserts? E.g. if I want to
bypass http sendsms and insert sms directly into insert table? Does smsbox
use insert table? Does bearerbox?
Regards,
NGC
----- Original Message -----
From: "Mi Reflejo" <[EMAIL PROTECTED]>
To: "Nikola Goran Cutura" <[EMAIL PROTECTED]>
Sent: Wednesday, May 10, 2006 12:26 AM
Subject: Re: SQLBOX question
yes, there is an understanding problem.
from sqlbox FAQ:
Q.
Does sqlbox replace sms box or is It an additional module that must be run?
A.
sqlbox is an additional module. You now have to start kannel in the
following manner:
1st: bearerbox <conf-file>
2nd: sqlbox <conf-file>
3rd: smsbox <conf-file> and wapbox <conf-file>
A picture of the new situation (with sqlbox included is as follows):
http request <--> [ smsbox ] <--> [ sqlbox ] <--> [ bearerbox ] <--> sms
gateway
I hope this picture make things clear. In text: sqlbox is sitting in
between smsbox and bearerbox, passing all messages back and forth
between the two. As a side-effect, also the messages that are passed
back and forth are logged in the sent_sms table.
SMS routing can't be done without SMSBOX.
Regards,
Anselmo