Hi,
The only way for bearerbox to remove the DLR from store is to receive an
upstream ACK (smsbox or sqlbox). That is the architectural spec. If this is
not happenning, sqlbox has a bug. You could check for that in maximum detail
bb (and sqlbox) logs. If there is a problem with routing or boxc ids in bb,
you should get a lot of warnings like "Warning: smsbox-list empty!", which
will also build up DLR store queue.
BR,
Nikos
----- Original Message -----
From: "Toby Phipps" <[email protected]>
To: "'Rene Kluwen'" <[email protected]>; <[email protected]>
Sent: Sunday, August 08, 2010 3:26 PM
Subject: RE: Life without smsbox
Just a follow-up - I also tried setting "smsbox-id = sqlbox" in the
"sqlbox"
section, and sqlbox starts but I get the same results, which is that the
bearerbox store size increments by one for each DLR received, as viewed in
the status output. For example:
SMS: received 0 (0 queued), sent 13 (0 queued), store size 85
Right now, my sqlbox.conf looks like this:
group = sqlbox
id = sqlbox
smsbox-id = sqlbox
bearerbox-port = 13100
bearerbox-host = localhost
# smsbox-port = 13200
sql-log-table = smsgw_kannel_sms_result
sql-insert-table = smsgw_kannel_sms_queue
log-file = /usr/local/kannel/log/sqlbox.log
log-level = 0
group = mysql-connection
id = sqlbox
host = localhost
username = <removed>
password = <removed>
database = <removed>
max-connections = 3
As you can see, the smsbox-port is commented out, meaning that I don't
want
sqlbox to try to talk to smsbox. I've tried with this line commented out,
or
uncommented (but pointed to a non-listening port). Both result in the same
behaviour,
Any more ideas anyone? I'm about to start delving into the source...
Thanks,
Toby.
