Re: No submit_sm_resp
Did you discover anything out of the ordinary? On Wed, Mar 6, 2013 at 9:22 PM, Rene Kluwen rene.klu...@chimit.nl wrote: So you do send a deliver_sm_resp. Just with an empty message id. Let me look at this closer. -Original Message- From: Jam Hitz [mailto:is.mu...@gmail.com] Sent: woensdag 6 maart 2013 18:40 To: Rene Kluwen Cc: Alexander Malysh; users@kannel.org Subject: Re: No submit_sm_resp Here is the Bearerbox Log (Please NOTE: Upon the recommendations of the telco, I have created 10 instances of saf_receiver_b SMSC as defined in the config). I shared my settings with the telco and they are also insisting that I raise window setting to 500 even though the documentation says maximum is 10). Inspite of all that, I still get like only 5 SMS/min (when I'm lucky) Another observation: in my bearerbox log, I am getting some interesting errors especially when restarting the daemon: 2013-03-06 20:20:41 [26334] [3] ERROR: System error 98: Address already in use [26385] [0] INFO: DLR rerouting for smsc id saf_receiver_b disabled. and lots of these: 2013-03-06 20:24:43 [26488] [17] DEBUG: sms_router: handling message (0x20bbc10 vs 0x12a4460) 2013-03-06 20:24:43 [26488] [17] DEBUG: Routing failed, re-queued. ...and lots of these (saf_7711 is the transmitter SMSC bind) WARNING: SMPP[saf_7711]: Not ACKED message found, will retransmit. SENT66sec. ago, SEQ84, DST12345398700 Here is my bearerbox log: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU 0x7f36dc000a30 dump: 2013-03-06 20:32:05 [26488] [9] DEBUG: type_name: enquire_link 2013-03-06 20:32:05 [26488] [9] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:05 [26488] [9] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:05 [26488] [9] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU 0x7f36e4000e40 dump: 2013-03-06 20:32:06 [26488] [8] DEBUG: type_name: enquire_link 2013-03-06 20:32:06 [26488] [8] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:06 [26488] [8] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:06 [26488] [8] DEBUG: sequence_number: 88 = 0x0058 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump: 2013-03-06 20:32:07 [26488] [15] DEBUG: type_name: enquire_link 2013-03-06 20:32:07 [26488] [15] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:07 [26488] [15] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:07 [26488] [15] DEBUG: sequence_number: 13 = 0x000d 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU 0x7f36de40 dump: 2013-03-06 20:32:08 [26488] [11] DEBUG: type_name: enquire_link 2013-03-06 20:32:08 [26488] [11] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:08 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:08 [26488] [11] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x0606) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 1 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x0606,0x0001,00) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x1501) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 13 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x1501,0x000d,32353437323235303036313200) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Got PDU: 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP PDU 0x7f36d0001500 dump: 2013-03-06 20:32:09 [26488] [11] DEBUG: type_name: deliver_sm 2013-03-06 20:32:09 [26488] [11] DEBUG: command_id: 5 = 0x0005 2013-03-06 20:32:09 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:09 [26488] [11] DEBUG: sequence_number: 2 = 0x0002 2013-03-06 20:32:09 [26488] [11] DEBUG: service_type: INSRV 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_ton: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_npi: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr: 254703842263 2013-03-06 20:32:09 [26488] [11] DEBUG: dest_addr_ton: 0 = 0x 2013-03-06 20:32:09 [26488] [11] DEBUG: dest_addr_npi: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: destination_addr: 7711 2013-03-06 20:32:09 [26488] [11] DEBUG:
Re: No submit_sm_resp
Rene, deliver_sm_resp is always without message_id. Alex Am 06.03.2013 um 19:22 schrieb Rene Kluwen rene.klu...@chimit.nl: So you do send a deliver_sm_resp. Just with an empty message id. Let me look at this closer. -Original Message- From: Jam Hitz [mailto:is.mu...@gmail.com] Sent: woensdag 6 maart 2013 18:40 To: Rene Kluwen Cc: Alexander Malysh; users@kannel.org Subject: Re: No submit_sm_resp Here is the Bearerbox Log (Please NOTE: Upon the recommendations of the telco, I have created 10 instances of saf_receiver_b SMSC as defined in the config). I shared my settings with the telco and they are also insisting that I raise window setting to 500 even though the documentation says maximum is 10). Inspite of all that, I still get like only 5 SMS/min (when I'm lucky) Another observation: in my bearerbox log, I am getting some interesting errors especially when restarting the daemon: 2013-03-06 20:20:41 [26334] [3] ERROR: System error 98: Address already in use [26385] [0] INFO: DLR rerouting for smsc id saf_receiver_b disabled. and lots of these: 2013-03-06 20:24:43 [26488] [17] DEBUG: sms_router: handling message (0x20bbc10 vs 0x12a4460) 2013-03-06 20:24:43 [26488] [17] DEBUG: Routing failed, re-queued. ...and lots of these (saf_7711 is the transmitter SMSC bind) WARNING: SMPP[saf_7711]: Not ACKED message found, will retransmit. SENT66sec. ago, SEQ84, DST12345398700 Here is my bearerbox log: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU 0x7f36dc000a30 dump: 2013-03-06 20:32:05 [26488] [9] DEBUG: type_name: enquire_link 2013-03-06 20:32:05 [26488] [9] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:05 [26488] [9] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:05 [26488] [9] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU 0x7f36e4000e40 dump: 2013-03-06 20:32:06 [26488] [8] DEBUG: type_name: enquire_link 2013-03-06 20:32:06 [26488] [8] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:06 [26488] [8] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:06 [26488] [8] DEBUG: sequence_number: 88 = 0x0058 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump: 2013-03-06 20:32:07 [26488] [15] DEBUG: type_name: enquire_link 2013-03-06 20:32:07 [26488] [15] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:07 [26488] [15] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:07 [26488] [15] DEBUG: sequence_number: 13 = 0x000d 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU 0x7f36de40 dump: 2013-03-06 20:32:08 [26488] [11] DEBUG: type_name: enquire_link 2013-03-06 20:32:08 [26488] [11] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:08 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:08 [26488] [11] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x0606) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 1 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x0606,0x0001,00) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x1501) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 13 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x1501,0x000d,32353437323235303036313200) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Got PDU: 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP PDU 0x7f36d0001500 dump: 2013-03-06 20:32:09 [26488] [11] DEBUG: type_name: deliver_sm 2013-03-06 20:32:09 [26488] [11] DEBUG: command_id: 5 = 0x0005 2013-03-06 20:32:09 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:09 [26488] [11] DEBUG: sequence_number: 2 = 0x0002 2013-03-06 20:32:09 [26488] [11] DEBUG: service_type: INSRV 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_ton: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_npi: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr: 254703842263 2013-03-06 20:32:09 [26488] [11] DEBUG: dest_addr_ton: 0 = 0x 2013-03-06 20:32:09 [26488] [11] DEBUG: dest_addr_npi: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: destination_addr: 7711 2013-03-06 20:32:09 [26488] [11]
RE: No submit_sm_resp
Right... So I don't see the problem here... -Original Message- From: Alexander Malysh [mailto:malys...@gmail.com] On Behalf Of Alexander Malysh Sent: donderdag 7 maart 2013 11:42 To: Rene Kluwen Cc: 'Jam Hitz'; users@kannel.org Subject: Re: No submit_sm_resp Rene, deliver_sm_resp is always without message_id. Alex Am 06.03.2013 um 19:22 schrieb Rene Kluwen rene.klu...@chimit.nl: So you do send a deliver_sm_resp. Just with an empty message id. Let me look at this closer. -Original Message- From: Jam Hitz [mailto:is.mu...@gmail.com] Sent: woensdag 6 maart 2013 18:40 To: Rene Kluwen Cc: Alexander Malysh; users@kannel.org Subject: Re: No submit_sm_resp Here is the Bearerbox Log (Please NOTE: Upon the recommendations of the telco, I have created 10 instances of saf_receiver_b SMSC as defined in the config). I shared my settings with the telco and they are also insisting that I raise window setting to 500 even though the documentation says maximum is 10). Inspite of all that, I still get like only 5 SMS/min (when I'm lucky) Another observation: in my bearerbox log, I am getting some interesting errors especially when restarting the daemon: 2013-03-06 20:20:41 [26334] [3] ERROR: System error 98: Address already in use [26385] [0] INFO: DLR rerouting for smsc id saf_receiver_b disabled. and lots of these: 2013-03-06 20:24:43 [26488] [17] DEBUG: sms_router: handling message (0x20bbc10 vs 0x12a4460) 2013-03-06 20:24:43 [26488] [17] DEBUG: Routing failed, re-queued. ...and lots of these (saf_7711 is the transmitter SMSC bind) WARNING: SMPP[saf_7711]: Not ACKED message found, will retransmit. SENT66sec. ago, SEQ84, DST12345398700 Here is my bearerbox log: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU 0x7f36dc000a30 dump: 2013-03-06 20:32:05 [26488] [9] DEBUG: type_name: enquire_link 2013-03-06 20:32:05 [26488] [9] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:05 [26488] [9] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:05 [26488] [9] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU 0x7f36e4000e40 dump: 2013-03-06 20:32:06 [26488] [8] DEBUG: type_name: enquire_link 2013-03-06 20:32:06 [26488] [8] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:06 [26488] [8] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:06 [26488] [8] DEBUG: sequence_number: 88 = 0x0058 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump: 2013-03-06 20:32:07 [26488] [15] DEBUG: type_name: enquire_link 2013-03-06 20:32:07 [26488] [15] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:07 [26488] [15] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:07 [26488] [15] DEBUG: sequence_number: 13 = 0x000d 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU 0x7f36de40 dump: 2013-03-06 20:32:08 [26488] [11] DEBUG: type_name: enquire_link 2013-03-06 20:32:08 [26488] [11] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:08 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:08 [26488] [11] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:08 [26488] [11] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x0606) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 1 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x0606,0x0001,00) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter tag (0x1501) 2013-03-06 20:32:09 [26488] [11] DEBUG: Optional parameter length read as 13 2013-03-06 20:32:09 [26488] [11] WARNING: SMPP: Unknown TLV(0x1501,0x000d,32353437323235303036313200) for PDU type (deliver_sm) received! 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP[saf_receiver_b]: Got PDU: 2013-03-06 20:32:09 [26488] [11] DEBUG: SMPP PDU 0x7f36d0001500 dump: 2013-03-06 20:32:09 [26488] [11] DEBUG: type_name: deliver_sm 2013-03-06 20:32:09 [26488] [11] DEBUG: command_id: 5 = 0x0005 2013-03-06 20:32:09 [26488] [11] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:09 [26488] [11] DEBUG: sequence_number: 2 = 0x0002 2013-03-06 20:32:09 [26488] [11] DEBUG: service_type: INSRV 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_ton: 1 = 0x0001 2013-03-06 20:32:09 [26488] [11] DEBUG: source_addr_npi: 1 = 0x0001 2013-03-06 20:32:09
Re: No submit_sm_resp
Hi, just some ideas 1) Are all the resources of the machine where kannel is runing ok? 2) How is the network connection quality to your provider? If I read it right, I see many enquire_link without response and the one enquire_link_resp took 4 secs (if they really belong to the same transaction): 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump: 2013-03-06 20:32:07 [26488] [15] DEBUG: type_name: enquire_link 2013-03-06 20:32:07 [26488] [15] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:07 [26488] [15] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:07 [26488] [15] DEBUG: sequence_number: 13 = 0x000d 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU dump ends. ... 2013-03-06 20:32:11 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Got PDU: 2013-03-06 20:32:11 [26488] [15] DEBUG: SMPP PDU 0x7f36ce40 dump: 2013-03-06 20:32:11 [26488] [15] DEBUG: type_name: enquire_link_resp 2013-03-06 20:32:11 [26488] [15] DEBUG: command_id: 2147483669 = 0x8015 2013-03-06 20:32:11 [26488] [15] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:11 [26488] [15] DEBUG: sequence_number: 13 = 0x000d 2013-03-06 20:32:11 [26488] [15] DEBUG: SMPP PDU dump ends. 3) If you are logging all the instances of saf_receiver_b to the same file (as it looks to me right now), please provide a clean log for one instance only (you can separate log-file = /var/log/kannel/bearerbox.log for each or just keep 1 instance running) 4) You say you have 10 instances of saf_receiver_b,that based on your config (enquire-link-interval = 5), are issuing in total 120 enquire_link/minute to the same provider, this without taking in consideration instances of saf_7711. Is that really necessary? Can you try to increase the value of enquire-link-interval. (Even if you use 1 connection try to set it to smth approx 60 seconds). 5) Have you tried to use active throttling with throughput = X (based on provider instruction) 6) Have you tried to increase the value of store-dump-freq = 1 On Thu, Mar 7, 2013 at 10:25 AM, Jam Hitz is.mu...@gmail.com wrote: Did you discover anything out of the ordinary? On Wed, Mar 6, 2013 at 9:22 PM, Rene Kluwen rene.klu...@chimit.nl wrote: So you do send a deliver_sm_resp. Just with an empty message id. Let me look at this closer. -Original Message- From: Jam Hitz [mailto:is.mu...@gmail.com] Sent: woensdag 6 maart 2013 18:40 To: Rene Kluwen Cc: Alexander Malysh; users@kannel.org Subject: Re: No submit_sm_resp Here is the Bearerbox Log (Please NOTE: Upon the recommendations of the telco, I have created 10 instances of saf_receiver_b SMSC as defined in the config). I shared my settings with the telco and they are also insisting that I raise window setting to 500 even though the documentation says maximum is 10). Inspite of all that, I still get like only 5 SMS/min (when I'm lucky) Another observation: in my bearerbox log, I am getting some interesting errors especially when restarting the daemon: 2013-03-06 20:20:41 [26334] [3] ERROR: System error 98: Address already in use [26385] [0] INFO: DLR rerouting for smsc id saf_receiver_b disabled. and lots of these: 2013-03-06 20:24:43 [26488] [17] DEBUG: sms_router: handling message (0x20bbc10 vs 0x12a4460) 2013-03-06 20:24:43 [26488] [17] DEBUG: Routing failed, re-queued. ...and lots of these (saf_7711 is the transmitter SMSC bind) WARNING: SMPP[saf_7711]: Not ACKED message found, will retransmit. SENT66sec. ago, SEQ84, DST12345398700 Here is my bearerbox log: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU 0x7f36dc000a30 dump: 2013-03-06 20:32:05 [26488] [9] DEBUG: type_name: enquire_link 2013-03-06 20:32:05 [26488] [9] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:05 [26488] [9] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:05 [26488] [9] DEBUG: sequence_number: 14 = 0x000e 2013-03-06 20:32:05 [26488] [9] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU 0x7f36e4000e40 dump: 2013-03-06 20:32:06 [26488] [8] DEBUG: type_name: enquire_link 2013-03-06 20:32:06 [26488] [8] DEBUG: command_id: 21 = 0x0015 2013-03-06 20:32:06 [26488] [8] DEBUG: command_status: 0 = 0x 2013-03-06 20:32:06 [26488] [8] DEBUG: sequence_number: 88 = 0x0058 2013-03-06 20:32:06 [26488] [8] DEBUG: SMPP PDU dump ends. 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP[saf_receiver_b]: Sending enquire link: 2013-03-06 20:32:07 [26488] [15] DEBUG: SMPP PDU 0x7f36ce90 dump: 2013-03-06
Kannel crash not in log files
Hi, When I run an instance directly from the promp (/smsbox myconfig.conf) if it fails to launch, or crashes, then I will see the error right away, for instance this smsbox startup: 2013-03-07 17:43:11 [31163] [0] ERROR: Group 'sendsms-user' may not contain field 'global-sender'. 2013-03-07 17:43:11 [31163] [0] ERROR: Error found on line 46 of file `../etc/smsbox_ns.conf'. 2013-03-07 17:43:11 [31163] [0] PANIC: Couldn't read configuration from `../etc/smsbox_ns.conf'. 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox(gw_panic+0x15b) [0x43abdb] 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox(main+0xf78) [0x40d7d8] 2013-03-07 17:43:11 [31163] [0] PANIC: /lib64/libc.so.6(__libc_start_main+0xf4) [0x351ec1d994] 2013-03-07 17:43:11 [31163] [0] PANIC: ./smsbox [0x40c1a9] but if instead I run it as--daemonize, and I specify in the config: log-file = /var/log/XYZ/kannel/smsbox_ns.log access-log = /var/log/XYZ/kannel/smsbox_ns.log log-level = 0 Then I don't see anything in the logs. Is there some way to get this logged while in daemon mode ? Thanks, Brian
Calculate Throughput of SMPP:
Hello, How to calculate throuphut of particular SMPP ? -- Thanks and regards, Himanshu Matta. 7566559950
