Then any messages that bearerbox has received via SMPP in the period
while sqlbox and smsbox are starting are dumped to the store. However,
the problem is these messages seem to remain in the store, and never
get resubmitted to smsbox via sqlbox.
It looks something like this:
Box connections:
smsbox:smsbox, IP 127.0.0.1 (1 queued), (on-line 0d 0h 0m 44s)
*SMSBOX*
smsbox:smsbox, IP 127.0.0.1 (0 queued), (on-line 0d 0h 0m 42s)
*SQLBOX*
Alex,
I just did a quick experiment with 1.4.1 release. I have to say I
don't use sqlbox, but what I did was start bearerbox, send 4 messages
vi fakesmsc (1 at a time, disconnecting after each one so I could
change the message each time).
I then did a status and saw all 4 of them queued in bearerbox :-
SMS: received 4 (4 queued), sent 0 (0 queued), store size 4
I then connected smsbox and got all 4 messages instantly, so no
queueing of them in bearebox once connected.
Looking at the status you showed with them queued in smsbox, this
basically means that smsbox has not returned an ack to bearerbox. It
suggests to me that either sqlbox is not passing the ack back to
bererbox (assuming you are connecting smsbox to sqlbox and not
directly), or that smsbox is not sending it, possibly because it
can't pass the message on via http and you have it set to retry?
What I thought was more interesting from my test was that I received
the messages out of order from when they were sent, I sent 1,2,3,4
and actually received 2,3,4,1 at smsbx. For me this could be a real
issue as order of messages from users is important to me (they build
up a command, as opposed to being one-shot). Is there anyway to stop
bearerbox reordering the messages?
Regards
Ben
