If a client disconnects from open smppbox, bearerbox doesn't see the "smsbox" anymore, so no DLR's are sent nor need to be queued. They will stay in bearerbox until client connects again.
But well... if your smpp client disconnects whilst in the middle of sending/receiving, that explains a lot. =-= Rene -----Original Message----- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Wednesday, 18 August, 2010 12:56 To: Davit Mirzoyan; rene.klu...@chimit.nl; ad...@impexrur.pl; users@kannel.org Subject: Re: smppbox bulk sms: slow reception from a client Hi, Connecting/disconnecting is not the recommended kannel operation. In fact when bearerbox detects an smsbox disconnect (or smppbox) it will wait 30" before retrying. Right there is your delay problem. The issue seems to be an smppbox problem. I know it doesn't have a store. What happens if it receives a DLR when your client is disconnected? I hope it keeps a queue in memory, for when the client reconnects again. In such a case if smppbox restarts, it will loose all DLRs in queue. But it seems that when smppbox doesn't have any clients, it drops the connection to bearerbox. That will cause a large delay to bearerbox. BR, Nikos ----- Original Message ----- From: Davit Mirzoyan To: nbalka...@gmail.com ; rene.klu...@chimit.nl ; ad...@impexrur.pl ; users@kannel.org Sent: Wednesday, August 18, 2010 1:00 PM Subject: RE: smppbox bulk sms: slow reception from a client Dear Nikos, This is a very odd problem. Why would my connection between smppbox and bearerbox go down periodically. Do you think it can be from my ESME SMPP client? It connects to my smppbox sends messages, then disconnects and connects again every 1 minute for deliveries. But I don't think this has anything to do with sending bulk messages. Regards, Davit > From: nbalka...@gmail.com > To: rene.klu...@chimit.nl; ad...@impexrur.pl; users@kannel.org; > davit.mirzo...@hotmail.com > Subject: Re: smppbox bulk sms: slow reception from a client > Date: Wed, 18 Aug 2010 01:36:52 +0300 > > Hi, > > Unfortunately kannel's I/O logging is very inadequate. Socket id is not at > all useful. However, looking at the logs more carefully: > > > ERROR: Error writing 16 octets to fd 29: > > ERROR: System error 32: Broken pipe > > ERROR: Couldn't write Msg to box <127.0.0.1>, disconnecting > > DEBUG: Thread 19 (gw/bb_boxc.c:boxc_sender) terminates. > > ERROR: Error writing 16 octets to fd 29: > > ERROR: System error 32: Broken pipe > . > . > . > > > WARNING: smsbox_list empty! > > Shows that smsbox died (or whatever else was connected as smsbox). This is > a > serious warning, which means that SMS are not sent upstream and instead > accumulate in store until smsbox reconnects. smsbox router wakes up and > rechecks every 30". This probably is the cause of your delays. > > BR, > Nikos > ----- Original Message ----- > From: "Rene Kluwen" <rene.klu...@chimit.nl> > To: "'Tomasz'" <ad...@impexrur.pl>; <users@kannel.org>; "'Davit Mirzoyan'" > <davit.mirzo...@hotmail.com> > Sent: Wednesday, August 18, 2010 12:19 AM > Subject: RE: smppbox bulk sms: slow reception from a client > > > That's an interesting story. > Now 5000 msgs is different than just 10. But if it happens with 10 > messages > at a time, things might be more reproducible. > > == Rene > > -----Original Message----- > From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf > Of Tomasz > Sent: Tuesday, 17 August, 2010 23:11 > To: users@kannel.org > Subject: Re: smppbox bulk sms: slow reception from a client > > Hi, > > I've also had similar problem some time ago when I was sending some > bulk of 5.000 msgs. There was sometimes "Broken pipe" error and > several problems with some DLRs (PDU unpacking failed). I tried to > reproduce this problem but I was not able to get those errors anymore, > it was happening one time when there was a huge traffic. > > Tomasz. > > > > W Twoim li?cie datowanym 17 sierpnia 2010 (17:09:57) moΏna przeczytaζ: > > > > > > > Hi, > > > I kept playing around with the configuration files but still no > > luck. Today I tried to send 20 sms to smppbox but my smppbox or kannel > kept stalling again. > > My system receives some 6 sms from my client and than it stalls for > > 1 minute or so before it continues receiving the rest. Moreover, my > > client > does not > > receive all the deliveries back. It gets some 12 out of 20. I > > checked my log files and I noticed several error and warning messages. > > In > my smppbox.log I > > get the following error and warning messages periodically. > > > DEBUG: SMPP[ESME]: Sending PDU: > > DEBUG: SMPP PDU 0x910c7b0 dump: > > DEBUG: type_name: bind_receiver_resp > > DEBUG: command_id: 2147483649 = 0x80000001 > > DEBUG: command_status: 0 = 0x00000000 > > DEBUG: sequence_number: 1 = 0x00000001 > > DEBUG: system_id: "VMA" > > DEBUG: SMPP PDU dump ends. > > WARNING: SMPP: PDU NULL terminated string (service_type) has no NULL. > > DEBUG: Octet string at 0x910ae28: > > DEBUG: len: 12 > > DEBUG: size: 13 > > DEBUG: immutable: 0 > > DEBUG: data: 00 00 00 05 00 00 00 00 00 00 00 02 > ............ > > DEBUG: Octet string dump ends. > > ERROR: smppbox[ESME]: PDU unpacking failed. > > DEBUG: smppbox[ESME]: Failed PDU omitted. > > ERROR: Invalid SMPP PDU received. > > DEBUG: Thread 2 (smppbox.c:smpp_to_bearerbox) terminates. > > DEBUG: Started thread 3 (smppbox.c:function) > > > ERROR: SMPP: Unknown TLV `dlr_err', don't send. > > INFO: We received an SMS message. > > DEBUG: DLR[internal]: Looking for DLR smsc=ESME, ts=a4517482, > dst=+37494086408, type=1 > > WARNING: DLR[internal]: DLR from SMSC<ESME> for DST<+37494086408> not > found. > > > and in my kannel.log I get this message periodically > > > DEBUG: boxc_sender: sent message to <127.0.0.1> > > DEBUG: send_msg: sending msg to boxc: <ESME> > > DEBUG: boxc_sender: sent message to <127.0.0.1> > > ERROR: Connection to box <127.0.0.1> broke. > > EBUG: send_msg: sending msg to boxc: <ESME> > > ERROR: Error writing 16 octets to fd 29: > > ERROR: System error 32: Broken pipe > > ERROR: Couldn't write Msg to box <127.0.0.1>, disconnecting > > DEBUG: Thread 19 (gw/bb_boxc.c:boxc_sender) terminates. > > ERROR: Error writing 16 octets to fd 29: > > ERROR: System error 32: Broken pipe > > DEBUG: Thread 18 (gw/bb_boxc.c:function) terminates. > > DEBUG: send_msg: sending msg to boxc: <ESME> > > DEBUG: boxc_sender: sent message to <127.0.0.1> > > DEBUG: send_msg: sending msg to boxc: <ESME> > > DEBUG: boxc_sender: sent message to <127.0.0.1> > > INFO: Connection closed by the box <127.0.0.1> > > DEBUG: send_msg: sending msg to boxc: <ESME> > > DEBUG: Thread 17 (gw/bb_boxc.c:boxc_sender) terminates. > > WARNING: smsbox_list empty! > > > Most of all the error about the "Broken pipe" alerts me, I don't > > know what that means but it seems to be serious. > > I don't know if that can be the reason. > > > My current configuration is as follows: > > > **** smskannel.conf ****** > > > group = core > > admin-port = 13000 > > smsbox-port = 13001 > > admin-password = bar > > log-file = "/tmp/kannel.log" > > log-level = 0 > > box-deny-ip = "*.*.*.*" > > box-allow-ip = "127.0.0.1" > > > include = > > "/home/davit/workspace/kannel/gateway-revision-4837/gw/smsbox.conf" > > include = > > "/home/davit/workspace/kannel/gateway-revision-4837/gw/smsc.conf" > > > ****************************************** > > ******** smsc.conf ************* > > > group=smsc > > smsc=smpp > > smsc-id=17 > > interface-version=34 > > host=*********** > > port=***** > > system-id=***** > > smsc-password=****** > > system-type=default > > transceiver-mode=1 > > > ****************************************** > > ********* smsbox.conf *************** > > > group = smsbox > > bearerbox-host = 127.0.0.1 > > sendsms-port = 13013 > > log-level = 0 > > > group = smsbox-route > > smsbox-id = VMA > > smsc-id = 17 > > > ******************************************* > > ******** smppbox.conf ******************** > > > group = core > > > group = smppbox > > # our boxc type > > smppbox-id = box1 > > # the port to listen on for smpp connections > > smppbox-port = 16000 > > # we connect to the following host as a box > > bearerbox-host = 127.0.0.1 > > bearerbox-port = 13001 > > log-level = 0 > > log-file = smppbox.log > > our-system-id = VMA > > route-to-smsc = 17 > > # see sample smpplogins.txt > > smpp-logins = > > "/home/davit/workspace/kannel/smppbox-revision-41/gw/smpplogins.txt" > > > *************************************************** > > > and my smpplogins.txt > > > foo bar VMA 245.127.0.0.1 > > client-02 password-02 vma 127.0.0.1 > > > I would really appreciate any help and ideas. I don't know how to tackle > this problem ;) > > > Cheers, > > Davit > > > >> Date: Sat, 14 Aug 2010 21:14:04 +0200 > >> Subject: Re: smppbox bulk sms: slow reception from a client > >> From: rene.klu...@chimit.nl > >> To: davit.mirzo...@hotmail.com > >> CC: users@kannel.org > >> > >> Onlly 10 sms is nothing of course. I wouldn't even call it bulk sms. > >> > >> Is there anyone else with the same problems? Because if so, it seems a > >> serious enough issue to look into. > >> > >> -- Rene > >> > >> > >> > >> > >> > >> > Dear users, > >> > > >> > Has anybody tried to send bulk sms from a client via smpp to smppbox? > It > >> > seems that smppbox or bearerbox accepts bulk sms extremely slowly. My > >> > client is not able to inject bulk sms to my smppbox (10 sms or so). > Kannel > >> > keeps stalling while receiving the messages. I am using a smppbox > revision > >> > 43 that is connected to a gateway revision 4837. Has anybody come up > with > >> > such a problem? Any help is appreciated ;). > >> > > >> > Many thanks, > >> > > >> > Cheers, > >> > Davit > >> > > > > > >
