Hi Thank you! I finally got things working. Few notes I hope someone fixes.
1. Documentation is bit old, for example table 7.2 is outdated. I'am using modem, so nowdays at2 smsc module. It does support dlr! 2. getting fully functional DLR setup for me was lack of smsc-id parameter for my smsc config group! This was actually easy to realize from the config I attached 3. I think that software maintenance is a job that should be done by sw vendor, so here, this community should maintenance this product. This really isn't statage now. development release is six years old, and last stable build more than two years. Those figures indicate that this product is still dead. 4. what is role of this sqlbox? it's quite handy peace of cake. could it be adopted in the kannel? I'm not using OpenSMPP but it is also tight outside plugin, At least documentation should be arranged so that it is easy to configure whole system. 5. binary releases, I'm using debian, and debian people have been nice and compiled kannel to us. As they do with sqlbox. sqlbox nicely works with planty of different sql engines, only thing is that you cannot choose by config witch backend to use. This makes binary releases quite useless. Using binary releases is my choice: this gives me peace of mind, that sw is secure and maintenanced properly. This really isn't true now, whom to blame? Thanks again for your help, I got this thing up and running. Finally my choice is going to be selfmade peace of sw that save outgoing messages and handles DLR requests. This allows me to use binary packages, and postgresql, no selfcompiled sqlbox or bit quirky database triggers. I leave that sqlbox there to store alternative message log for me. Yours, jarno > Also have a read: > http://www.kannel.org/pipermail/users/2013-August/020120.html > > 2016-03-22 18:27 GMT+03:00 spameden <spame...@gmail.com>: > >> ok, personally I'm using option 2 without any dlr.php or any other sort >> of >> scripts, so I end up with MT records in database with status field where >> field is filled with resulting status. >> >> Here are couple of ways to resolve what you need: >> >> 1. Set up trigger (as Rene already suggested) to update tables you need >> or update records in sent_sms based on the information coming from the >> DLR from >> your upstream SMSC operators. >> >> 2. Modify sent_sms table, add status column and modify sqlbox code to >> UPDATE MT records right after DLR comes to the kannel setting the status >> from dlr_mask. I'd also suggest auto-generating dlr_url based on the >> current time so you would match correct entry. >> >> 3. You can use sqlbox with smsbox and set up a dlr_url hook to the >> external script. >> >> >> >How do I implement DLR status? Is my only option to archive this to >> create >> >a script that writes delivery status to my sent_sms table? If so, how >> to >> >add an ID that is stored to db? >> >> For this there is dlr_url field or dlr_url GET variable in sendsms >> query. >> For delivery script handling examples please search mailing lists or >> make >> yourself one (there is some examples in documentation I believe). >> >> 2016-03-22 17:53 GMT+03:00 <j...@evonet.fi>: >> >>> Actually I can't >>> All I find is notes to check kannel.org. And I cannot figure out how to >>> do >>> this on those documents? As you said its been raised many times, is the >>> documentation good? If this sis just trivial thing how the hell I am >>> so >>> stupid I cannot understand. >>> >>> thanx for your help >>> >>> >>> >>> > This question has been raised too many times. Can you search a bit on >>> > mailing lists? >>> > >>> > There are multiple solutions out there for your issue. >>> > >>> > 2016-03-22 17:18 GMT+03:00 <j...@evonet.fi>: >>> > >>> >> Hi >>> >> >>> >> I have working setup that sends sms messages just fine. Message is >>> >> copied >>> >> to sent_sms table as expected. >>> >> >>> >> How do I implement DLR status? Is my only option to archive this to >>> >> create >>> >> a script that writes delivery status to my sent_sms table? If so, >>> how >>> to >>> >> add an ID that is stored to db? in case I use smsbox's http >>> interface >>> to >>> >> receive user data. >>> >> >>> >> Or can I configure sqlbox to do this for me? Some discussion left an >>> >> impression to me, that this is possible, but I can't find >>> documentation >>> >> from kannel.org that helps me with this. >>> >> >>> >> If sqlbox can do it great, if not I think it's bit useless sw. >>> >> >>> >> and as an extra option how to configure sqlbox to save incoming >>> sms:s >>> to >>> >> database? is it possible? and is there a way to use database to >>> >> configure >>> >> incoming sms rules, so that sql box would do the tricks... >>> >> >>> >> thx, Jarno >>> >> >>> >> -- kannel.conf >>> >> group = core >>> >> admin-port = 13000 >>> >> admin-password = <changed> >>> >> admin-deny-ip = "192.168.100.1" # deny outside gw >>> >> admin-allow-ip = "127.0.0.*;192.*.*.*" >>> >> smsbox-port = 15001 >>> >> log-file = "/var/log/kannel/bearerbox.log" >>> >> box-deny-ip = "*.*.*.*" >>> >> box-allow-ip = "127.0.0.1" >>> >> >>> >> group = smsbox >>> >> bearerbox-host = 127.0.0.1 >>> >> bearerbox-port = 15002 >>> >> sendsms-port = 15015 >>> >> global-sender = "SERVICE_PROVIDER" >>> >> log-level = 0 >>> >> log-file = "/var/log/kannel/smsbox.log" >>> >> >>> >> + incoming message groups >>> >> >>> >> --sqlbox.conf-- >>> >> group = sqlbox >>> >> id = sqlbox-db >>> >> smsbox-id = sqlbox >>> >> bearerbox-host = localhost >>> >> bearerbox-port = 15001 >>> >> smsbox-port = 15002 >>> >> smsbox-port-ssl = false >>> >> sql-log-table = sent_sms >>> >> sql-insert-table = send_sms >>> >> log-file = "/var/log/kannel/kannel-sqlbox.log" >>> >> log-level = 0 >>> >> >>> >> + mysql configuration >>> >> >>> >> >>> >> >>> > >>> >>> >>> >> >
