Hi again, I updated to the latest version (Revision: 4975) after recompiling kannel/opensmpp I notice that opensmppbox is not storing the 'DLR' requests on the configured mysql table, so when I manually reply or try to send the DLR back to the ESME they are processed but they are not sent, on the logs I get something like :
2012-05-16 15:57:39 [38724] [1] DEBUG: DLR[mysql]: Looking for DLR smsc=clientx, ts=913e96e8, dst=31503, type=1 2012-05-16 15:57:39 [38724] [1] DEBUG: sql: SELECT `mask`, `service`, `url`, `source`, `destination`, `box_id` FROM `dlr_2201` WHERE `smsc`=? AND `ts`=? LIMIT 1 2012-05-16 15:57:39 [38724] [1] WARNING: DLR[mysql]: DLR from SMSC<clientx> for DST<31503> not found. 2012-05-16 15:57:39 [38724] [1] WARNING: opensmppbox: msg_to_pdu: no msg corresponding dlr, ignoring 2012-05-16 15:57:39 [38724] [1] WARNING: msg_to_pdu failed, sending negative ack It reads/queries the configured table (dlr_2201) but doesn't writes to it. my flow is something like: esme ---> opensmppbox(mysql DLR) ---> kannel[mysl DLR (generic http)] ---> smsc I can receive the sms from the esme connected to opensmppbox and send the sms trough the smsc, Something strange that I notice, is that the DLR request instead of been stored on the table that is specified on the opensmppbox dlr configuration for the esme 'dlr_2201', are been stored on Kannel's DLR table. After I send the SMS from the generic http to the smsc the DLR table for Kannel is used as usual and properly stores the dlr-url, but later when I want to resend the DLR , cannel accept it but DLR never goes back to ESME Any ideas ? Another thing is that on on the logs I don't see and 'insert' from opensmppbox trying to store the 'DLR' request on the DB. this is the configuration configuration that I currently have: group = core dlr-storage = mysql group = opensmppbox bearerbox-host = 127.0.0.127 bearerbox-port = 13001 opensmppbox-port = 2201 log-level = 0 log-file = "/var/log/kannel/opensmppbox/box2201.log" our-system-id = box2201 route-to-smsc = www smpp-logins = "/home/LAB/kannel/clients.txt" use-systemid-as-smsboxid = true group = mysql-connection id = mydlr host = 127.0.0.1 username = kannel password = kannel database = kannel max-connections = 3 group = dlr-db id = mydlr table = dlr_2201 field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = box_id thanks in advance On Wed, May 16, 2012 at 12:54 AM, Rene Kluwen <[email protected]> wrote: > At this point, there is no other solution. > But as said, I will look into the matter. > > == Rene > > -----Original Message----- > From: Nicolas de Bari Embriz Garcia Rojas [mailto:[email protected]] > Sent: Wednesday, 16 May, 2012 01:39 > To: Rene Kluwen > Cc: [email protected] > Subject: Re: our-system-id or opensmppbox-id as an Escape Code > > Hi, using a second generic http smsc solve the problem but that is > exactly what I want to avoid, before having to create a second smsc, > changing the user to avoid duplicity could be easier, but before > trying to convince the client to use a different username I would like > to found a simpler alternative. > > thanks in advance. > > On Wed, May 16, 2012 at 12:12 AM, Rene Kluwen <[email protected]> wrote: >> A possible solution that I am thinking of at first glance is to use two >> separate generic http smsc's for each opensmppbox. >> Those smsc's share the same group=smsc settings, except for 1 parameter > that >> you can distinguish with. >> >> I will give this more thoughts. It's an interesting issue. >> >> == Rene >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf >> Of Nicolas de Bari Embriz Garcia Rojas >> Sent: Wednesday, 16 May, 2012 01:03 >> To: [email protected] >> Subject: our-system-id or opensmppbox-id as an Escape Code >> >> Hi all, any idea of how to identify an opensmpp box instance that >> routes traffic to a generic http smsc so that on the send-url >> parameters I could distinguish from which opensmppbox the request came >> from, maybe using an escape code % ? >> >> Currently I have two opensmppbox instances listening on different >> ports, the two of them connect to the same bearerbox server and route >> the messages to a single generic http smsc, so far I have been using >> for distinguish traffic sources, the escape code %n (the sendsms-user >> or sms-service name) but the problem that I am facing now, Is that >> would like to distinguish trafic in a case where an user exists on >> both opensmppboxes (smpplogins). >> >> Any idea of how to deal with that ? >> >> opensmppbox1:2345. >--- >> \ >> \ ----> bearerbox http smsc >> / >> opensmppbox2:2345. >---/ >> >> the smpp logins on both opensmppbox have a common username entry >> 'funyclient secret VMA x.x.x.x' >> >> Any ideas would be appreciated. >> >> >> > > >
