I'm just thinking of something. What if you fill in the field "boxc_id" the value that you have with sqlbox-id = .... (in group = sqlbox). Does that make a difference?
== Rene -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nikos Balkanas Sent: Wednesday, 04 August, 2010 00:03 To: Toby Phipps; [email protected] Subject: Re: Life without smsbox Hi, You are most wellcome. 1) That is the correct way to do it. For bearerbox, sqlbox is just another smsbox, that needs to be configured in. sendsms-port is not relevant in this case, but bearerbox never reads this value anyway. 2) I imagine that this has to do with sqlbox configuration, and its trying to route DLRs to a connected smsbox, that doesn't exist. There are people with much more experience than me with sqlbox. I would imagine that you could easily test the setting you propose. There are a couple of useful tools under test/ such as test/drive_smpp. I even submitted recently a test/fakesmpp that could be used for no-cost testing. BR, Nikos ----- Original Message ----- From: Toby Phipps To: [email protected] Sent: Tuesday, August 03, 2010 8:17 PM Subject: Life without smsbox Hello all, I recently received good advice on this list (thanks Nikos!) that I was fine without running smsbox given that I'm using sqlbox for both queuing MT and for handling MO/DLR. However, I've run into a couple of issues with this config that I'm hoping on some advice on, specifically: 1. I need to set "smsbox-port" in the core group as this is the port that sqlbox will connect to bearerbox on. However, if I include that parameter but exclude the smsbox group, bearerbox crashes on start complaining that smsbox-port is set but without a smsbox group. I've worked around this by just including a minimal smsbox group in the config even though no smsbox process is ever started. Any issues with this or a better approach? 2. Messages are still being queued for smsbox processing. If I look at the status output, I get "smsbox:(none), IP 127.0.0.1 (8 queued), (on-line 0d 0h 5m 58s)". These are all DLRs that have happily been processed by sqlbox and don't need to be queued for any further processing. Is there an easy way to stop this queueing for the non-running sqlbox happening? I'm considering setting "sms-incoming-queue-limit" to something small, or even zero, but I'm not sure if this will do the trick, and I'm concerned that it might backfire and cause MO/DLR to be dropped if sqlbox can't keep up with message spikes at any point in time. Anyone got any advice on how to configure this cleanly with just bearerbox, sqlbox and my smpp connections? Thanks, Toby.
