Hey Rinor. Your idea about splitting MO, MT, DLR in separate tables is just great!
How do you do matching against MT's btw? Do you invoke everytime script or just update table via unique dlr_url id in the MT table? Would love to see your patch against SQLBox. I'm also wondering if you solved the issue of DLR missing when DB goes down. Thanks. 2013/2/14 Rinor Hoxha <rinorho...@gmail.com>: > Sure Willy, > I'll post them in one hour, the time to remove the sensitive information, > but I can tell you in advance there is nothing fancy on them. > > One scenario is the following: > 4xSMSbox -> 1xSQLbox -> 1xBEARERbox => 10xConnections to 4xMNOs. > (7xSMPPxTRANSCEIVER + 3 custom http connections to interface some smsc proxy > that is not included on default kannel smscs) > > 1 SMSbox handles services for 1 MNO. > Don't remember why I did that, probably because of the retry delay queue > issue on smsbox, but not really sure. > > Each SMSbox has one specific config file that includes a common file, for > all SMSboxes, that contains the users and the services. > > Kannel rev.5014 > Kannel code has a small modification to activate smpp relative_time_format > for validity (since some of MNOs refused to go with absolute_time_format). I > agree with the list, in some previous debates, that relative time should not > be used, but when you have to, kannel is there for you :) > relative-time-format = 1 is the customized directive for this. > > Sqlbox rev.49 > Sqlbox has a small modification in mysql to insert MO,MT,DLR in separate > TABLES - that could be done also with triggers, but on high load I didn't > wanted triggers so thought it was better to put it inside the code. > sql-log-table-split = 1 is the customized directive for this. > > This is in one production system, however the tests have been done also with > unmodified versions of those revisions. (keep in mind that the small changes > made to the code have nothing to do with the "mentioned issue"). Test were > done both on debian and windows. > > I'll provide more info later if needed/interested. > > Br, Rinor > > > On Thu, Feb 14, 2013 at 2:11 AM, Willy Mularto <sangpr...@gmail.com> wrote: >> >> May we know your Kannel and SQLBox version also please share your Kannel >> scenario configuration, including SQLBox position (Bearerbox-SQLBox-SMSBox >> or Bearbox-SMSBox-SQLBox or other?) >> >> >> >> Willy Mularto >> sangpr...@gmail.com >> >> On Feb 14, 2013, at 12:20 AM, Rinor Hoxha <rinorho...@gmail.com> wrote: >> >> I was concerned in the first time I read about this "issue", >> since I'm using sqlbox in different scenarios, with different load (1-20+ >> sms/sec) with at least 10 smsc connections (smpp and http), with 4 smsboxes, >> with delivery tracking, with/without sms services, with/without opensmppbox >> and the only times that sqlbox "failed" was because sql server reaching >> max connections (on very high load and bad programmed services) or services >> script issues or the MNO never sent dlr report or other issues not related >> to sqlbox itself. >> I tried myself on lab to make sqlbox "loose" sms, but it never happened. I >> went further and compiled a cygwin version on windows and it never happened. >> The last test was done on windows with rev.5014 with variable rate 6-30 sms >> with approx 300.000 sms with dlr=3. And everything was there. No matter if >> one or more than one smsboxes, routing works fine. >> Yes, it may be some room for improvement on sqlbox (as with any software), >> but not sure if it has a "bug" causing missing sms. >> I may be wrong, but that my 2 cents, since I see this "issue" coming up >> from time to time. If others think that there is really a bug, lets help >> each other and the programmer to fix it. >> >> Br, Rinor >> >> >> >> On Tue, Feb 12, 2013 at 8:14 PM, Rene Kluwen <rene.klu...@chimit.nl> >> wrote: >>> >>> Please indicate if you are using sqlbox or not. >>> >>> I’ve tried to debug this problem in the past, but I could not reproduce >>> this problem. >>> >>> >>> >>> >>> >>> From: Willy Mularto [mailto:sangpr...@gmail.com] >>> Sent: donderdag 7 februari 2013 14:05 >>> To: michael osakede >>> Cc: Rene Kluwen; kannel users@kannel.org >>> Subject: Re: Issue with bearerbox >>> >>> >>> >>> >>> Do you use current version with SQLBox configured to service MO? If yes >>> then it could be thee old bug still there. >>> >>> SlyDroid >>> >>> On Feb 7, 2013 7:44 PM, "michael osakede" <ire...@yahoo.com> wrote: >>> >>> Hi, >>> >>> >>> >>> I have setup an sms service >>> >>> >>> >>> group = sms-service >>> >>> keyword = default >>> >>> get-url = "http://localhost/insms/insms.php?sender=%p&text=%b&to=%P"; >>> >>> accept-x-kannel-headers = true >>> >>> max-messages = 3 >>> >>> concatenation = true >>> >>> catch-all = true >>> >>> accepted-smsc = "xxx;xxx1;xxx2;xxx3" >>> >>> omit-empty = true >>> >>> >>> >>> and corresponding SMPP connction with smsc-ids. >>> >>> >>> >>> I noticed that only about 40% of messages are routed to the sms service, >>> any idea why this is a problem? and is there anyway to check and see what >>> happened? >>> >>> >>> >>> >>> >>> Michael >>> >>> >> >> >> >
