Do you set dlr-mask and dlr-url when you send an SMS? I presume You don't (registered_delivery = 0).
Cezary -----Original Message----- From: Barry Murphy [mailto:[email protected]] Sent: 23 May 2010 13:31 To: Cezary Siwek Subject: RE: sqlbox Importance: Low I've tried this value not being set and also set to 1... would a debug help? 2010-05-24 00:29:09 [5952] [10] DEBUG: boxc_receiver: sms received 2010-05-24 00:29:09 [5952] [10] DEBUG: send_msg: sending msg to boxc: <asmsbox> 2010-05-24 00:29:09 [5952] [6] DEBUG: SMPP[internal]: Manually forced source addr ton = 1, source add npi = 1 2010-05-24 00:29:09 [5952] [6] DEBUG: SMPP[internal]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-24 00:29:09 [5952] [6] DEBUG: SMPP[internal]: Sending PDU: 2010-05-24 00:29:09 [5952] [6] DEBUG: SMPP PDU 0x8192990 dump: 2010-05-24 00:29:09 [5952] [6] DEBUG: type_name: submit_sm 2010-05-24 00:29:09 [5952] [6] DEBUG: command_id: 4 = 0x00000004 2010-05-24 00:29:09 [5952] [6] DEBUG: command_status: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: sequence_number: 5 = 0x00000005 2010-05-24 00:29:09 [5952] [6] DEBUG: service_type: NULL 2010-05-24 00:29:09 [5952] [6] DEBUG: source_addr_ton: 1 = 0x00000001 2010-05-24 00:29:09 [5952] [6] DEBUG: source_addr_npi: 1 = 0x00000001 2010-05-24 00:29:09 [5952] [6] DEBUG: source_addr: "64274912344" 2010-05-24 00:29:09 [5952] [6] DEBUG: dest_addr_ton: 1 = 0x00000001 2010-05-24 00:29:09 [5952] [6] DEBUG: dest_addr_npi: 1 = 0x00000001 2010-05-24 00:29:09 [5952] [6] DEBUG: destination_addr: "64274912344" 2010-05-24 00:29:09 [5952] [6] DEBUG: esm_class: 3 = 0x00000003 2010-05-24 00:29:09 [5952] [6] DEBUG: protocol_id: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: priority_flag: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: schedule_delivery_time: NULL 2010-05-24 00:29:09 [5952] [6] DEBUG: validity_period: NULL 2010-05-24 00:29:09 [5952] [6] DEBUG: registered_delivery: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: replace_if_present_flag: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: data_coding: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: sm_default_msg_id: 0 = 0x00000000 2010-05-24 00:29:09 [5952] [6] DEBUG: sm_length: 24 = 0x00000018 2010-05-24 00:29:09 [5952] [6] DEBUG: short_message: 2010-05-24 00:29:09 [5952] [6] DEBUG: Octet string at 0x81a2be0: 2010-05-24 00:29:09 [5952] [6] DEBUG: len: 24 2010-05-24 00:29:09 [5952] [6] DEBUG: size: 25 2010-05-24 00:29:09 [5952] [6] DEBUG: immutable: 0 2010-05-24 00:29:09 [5952] [6] DEBUG: data: 77 77 77 2e 77 65 62 73 6d 73 2e 63 6f 2e 6e 7a asdasdasd 2010-05-24 00:29:09 [5952] [6] DEBUG: data: 3a 20 61 73 64 61 73 64 : asd 2010-05-24 00:29:09 [5952] [6] DEBUG: Octet string dump ends. 2010-05-24 00:29:09 [5952] [6] DEBUG: SMPP PDU dump ends. 2010-05-24 00:29:10 [5952] [6] DEBUG: SMPP[internal]: Got PDU: 2010-05-24 00:29:10 [5952] [6] DEBUG: SMPP PDU 0x8192990 dump: 2010-05-24 00:29:10 [5952] [6] DEBUG: type_name: submit_sm_resp 2010-05-24 00:29:10 [5952] [6] DEBUG: command_id: 2147483652 = 0x80000004 2010-05-24 00:29:10 [5952] [6] DEBUG: command_status: 0 = 0x00000000 2010-05-24 00:29:10 [5952] [6] DEBUG: sequence_number: 5 = 0x00000005 2010-05-24 00:29:10 [5952] [6] DEBUG: message_id: "21532055" 2010-05-24 00:29:10 [5952] [6] DEBUG: SMPP PDU dump ends. 2010-05-24 00:29:17 [5952] [6] DEBUG: SMPP[internal]: Sending enquire link: 2010-05-24 00:29:17 [5952] [6] DEBUG: SMPP PDU 0x8195358 dump: Thanks Barry On Sun, 23 May 2010 13:21:47 +0100, "Cezary Siwek" <[email protected]> wrote: > I'm sure I have replied on this list to people having exactly the same > issue... few times. > > Re DLRs: > > Play with the 'msg-id-type' value in your SMPP SMSC section. > > Cezary > > > > -----Original Message----- > From: Barry Murphy [mailto:[email protected]] > Sent: 23 May 2010 12:57 > To: Cezary Siwek > Cc: Alejandro Guerrieri; Users > Subject: RE: sqlbox > > Thanks, that worked!!! Wonder why it wasnt in any other posts I looked at > with people having the same issue , ohh well, thanks again :) > > Next up, any idea why DLR records arent appearing into the database? It's > connecting but not inserting. :/ > > Thanks > Barry > > > On Sun, 23 May 2010 12:43:26 +0100, "Cezary Siwek" > <[email protected]> wrote: >> Try to set mysql port as another config value: >> port = 3306 >> >> >> -----Original Message----- >> From: Barry Murphy [mailto:[email protected]] >> Sent: 23 May 2010 12:40 >> To: Cezary Siwek >> Cc: Alejandro Guerrieri; Users >> Subject: RE: sqlbox >> Importance: Low >> >> Ok, >> >> So I tried adding :3306 to the IP Addres, still same error. I also tried >> changing the database name on the kannel dlr connection (which is same >> user/pass/database/host as the sqlbox) and got a database access denied, > so >> I know the kannel one is connecting and doing sql selects just fine. > It's >> just sqlbox that doesn't like it, though this still doesnt explain why I >> dont get any entries into my dlr table, only selects happening. >> >> thanks >> barry >> >> >> On Sun, 23 May 2010 12:36:07 +0100, "Cezary Siwek" >> <[email protected]> wrote: >>> Hi, >>> You must set the database port if you are connecting to an external >>> database. Otherwise sqlbox always tries to connect using unix socket. >>> >>> BR >>> Cezary >>> >>> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On >> Behalf >>> Of Barry Murphy >>> Sent: 23 May 2010 12:15 >>> To: Alejandro Guerrieri >>> Cc: Users >>> Subject: Re: sqlbox >>> >>> I'm running debian lenny on both sides, though the side with sqlbox is >>> version 5, so I wonder if it's because of a different type of auth >> method >>> or something... As I mention if I use CLI it works fine from the SQLBox >> to >>> the Actual mysql server, but the other way around it doesnt. >>> >>> Kannel: >>> group = mysql-connection >>> id = mydlr >>> host = 10.10.1.1 >>> username = 1123 >>> password = 1123 >>> database = 1123 >>> max-connections = 1 >>> >>> group = dlr-db >>> id = mydlr >>> table = dlr >>> 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 = boxc >>> >>> smsc:/etc/kannel# cat sqlbox.conf >>> group = sqlbox >>> id = sqlbox-db >>> smsbox-id = asmsbox >>> bearerbox-host = localhost >>> bearerbox-port = 13001 >>> smsbox-port = 13003 >>> sql-log-table = sqlbox_sent_sms >>> sql-insert-table = sqlbox_send_sms >>> log-file = "/var/log/kannel/kannel-sqlbox.log" >>> log-level = 0 >>> >>> group = mysql-connection >>> id = sqlbox-db >>> host = 10.10.1.1 >>> username = 1123 >>> password = 1123 >>> database = 1123 >>> max-connections = 1 >>> >>> Thanks >>> Barry >>> >>> >>> >>> On Sun, 23 May 2010 13:08:45 +0200, Alejandro Guerrieri >>> <[email protected]> wrote: >>>> Your connection string must be wrong, or there's some issue preventing >>> the >>>> sqlbox process to connect to the remote host. >>>> >>>> I'd check the firewall rules. Another explanation could be related to >>>> selinux if you're running on a RHEL/CentOS box and have it enabled. >>>> >>>> Anyhow, please post your sqlbox configuration (hide the >>>> host/user/password). >>>> >>>> Regards, >>>> >>>> Alex >>>> >>>> On Sun, May 23, 2010 at 12:57 PM, Barry Murphy <[email protected]> >> wrote: >>>> >>>>> Hi, >>>>> >>>>> Not sure if this is the right place to post, but hoping it is, if not >>>>> please reply offlist direct to me. I've just setup SqlBOX and managed >>> to >>>>> have it connect to a localhost mysql server, however when I configure >>> it >>>>> to >>>>> connect to a remote system it isn't working. My Kannel is using the >>> same >>>>> MySQL variables though its not complaining, even though it's not >>> actually >>>>> inserting anything into the dlr so I'm not 100% sure if it is working >>> or >>>>> not. A tcpdump on the remote sql server does show connection > attempts, >>>>> so I >>>>> know the TCP is working, the only think I can think of is that sqlbox >>> is >>>>> failing. if I use CLI from the host to the remote sql host I can >>> connect, >>>>> i.e. 'mysql -h remote.host.com -u -p database', this works fine. >>>>> >>>>> Any suggestions or ideas would be appreciated. I'd prefer not having >> to >>>>> run so many mysql hosts and rather use our central one that has > grunty >>>>> CPU's, Disks and backups. >>>>> >>>>> smsc:/etc/kannel# /usr/local/kannel/sbin/sqlbox >>>>> 2010-05-23 22:53:14 [2015] [0] INFO: Debug_lvl = -1, log_file = >> <none>, >>>>> log_lvl = 0 >>>>> 2010-05-23 22:53:14 [2015] [0] DEBUG: Kannel sqlbox version `1.4.3'. >>>>> Build `May 23 2010 06:03:57', compiler `4.1.2 20061115 (prerelease) >>>>> (Debian 4.1.1-21)'. >>>>> System Linux, release 2.6.18.8.xs5.5.0.13.442, version #1 SMP Wed Nov >>> 11 >>>>> 12:01:55 UTC 2009, machine i686. >>>>> Hostname localhost, IP 127.0.0.1. >>>>> Libxml version 2.7.7. >>>>> Compiled with MySQL 5.0.32, using MySQL 5.0.51a. >>>>> Using native malloc. >>>>> >>>>> 2010-05-23 22:53:14 [2015] [0] INFO: Starting to log to file >>>>> /var/log/kannel/kannel-sqlbox.log level 0 >>>>> 2010-05-23 22:53:14 [2015] [0] INFO: Added logfile >>>>> `/var/log/kannel/kannel-sqlbox.log' with level `0'. >>>>> 2010-05-23 22:53:14 [2015] [0] ERROR: MYSQL: can not connect to >>> database! >>>>> 2010-05-23 22:53:14 [2015] [0] ERROR: MYSQL: Can't connect to MySQL >>>>> server >>>>> on '120.131.1.2' (111) >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: SQLBOX: MySQL: database pool > has >>> no >>>>> connections! >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: >>>>> /usr/local/kannel/sbin/sqlbox(gw_panic+0xdc) [0x806c96c] >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: >>>>> /usr/local/kannel/sbin/sqlbox(sqlbox_init_mysql+0x3bf) [0x8050a6f] >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: >>>>> /usr/local/kannel/sbin/sqlbox(main+0x390) [0x804f660] >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: >>>>> /lib/libc.so.6(__libc_start_main+0xe5) [0xb7ad5455] >>>>> 2010-05-23 22:53:14 [2015] [0] PANIC: /usr/local/kannel/sbin/sqlbox >>>>> [0x804f191] >>>>> smsc:/etc/kannel# >>>>> >>>>> Thanks >>>>> Barry >>>>> >>>>>
