Re: Queue Size from status page
[4912] [6] DEBUG: type_name: submit_sm 2010-08-17 17:38:23 [4912] [6] DEBUG: command_id: 4 = 0x0004 2010-08-17 17:38:23 [4912] [6] DEBUG: command_status: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: sequence_number: 6 = 0x0006 2010-08-17 17:38:23 [4912] [6] DEBUG: service_type: NULL 2010-08-17 17:38:23 [4912] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-08-17 17:38:23 [4912] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-08-17 17:38:23 [4912] [6] DEBUG: source_addr: 2010-08-17 17:38:23 [4912] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-08-17 17:38:23 [4912] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-08-17 17:38:23 [4912] [6] DEBUG: destination_addr: XXX 2010-08-17 17:38:23 [4912] [6] DEBUG: esm_class: 3 = 0x0003 2010-08-17 17:38:23 [4912] [6] DEBUG: protocol_id: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: priority_flag: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: schedule_delivery_time: NULL 2010-08-17 17:38:23 [4912] [6] DEBUG: validity_period: NULL 2010-08-17 17:38:23 [4912] [6] DEBUG: registered_delivery: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: data_coding: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-08-17 17:38:23 [4912] [6] DEBUG: sm_length: 4 = 0x0004 2010-08-17 17:38:23 [4912] [6] DEBUG: short_message: lost 2010-08-17 17:38:23 [4912] [6] DEBUG: SMPP PDU dump ends. 2010-08-17 17:38:23 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput limit exceeded (1.00,0.05) 2010-08-17 17:38:24 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput (0.00,0.05) 2010-08-17 17:38:24 [4912] [6] DEBUG: SMPP[SMSC-XXX]: Got PDU: 2010-08-17 17:38:24 [4912] [6] DEBUG: SMPP PDU 0x232f260 dump: 2010-08-17 17:38:24 [4912] [6] DEBUG: type_name: submit_sm_resp 2010-08-17 17:38:24 [4912] [6] DEBUG: command_id: 2147483652 = 0x8004 2010-08-17 17:38:24 [4912] [6] DEBUG: command_status: 0 = 0x 2010-08-17 17:38:24 [4912] [6] DEBUG: sequence_number: 6 = 0x0006 2010-08-17 17:38:24 [4912] [6] DEBUG: message_id: 20081717383633022 2010-08-17 17:38:24 [4912] [6] DEBUG: SMPP PDU dump ends. 2010-08-17 17:38:24 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput (0.00,0.05) 2010-08-17 17:38:25 [4912] [16] DEBUG: boxc_receiver: sms received 2010-08-17 17:38:25 [4912] [16] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput (0.00,0.05) 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP[SMSC-XXX]: Sending PDU: 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP PDU 0x232f260 dump: 2010-08-17 17:38:25 [4912] [6] DEBUG: type_name: submit_sm 2010-08-17 17:38:25 [4912] [6] DEBUG: command_id: 4 = 0x0004 2010-08-17 17:38:25 [4912] [6] DEBUG: command_status: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: sequence_number: 7 = 0x0007 2010-08-17 17:38:25 [4912] [6] DEBUG: service_type: NULL 2010-08-17 17:38:25 [4912] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-08-17 17:38:25 [4912] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-08-17 17:38:25 [4912] [6] DEBUG: source_addr: 2010-08-17 17:38:25 [4912] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-08-17 17:38:25 [4912] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-08-17 17:38:25 [4912] [6] DEBUG: destination_addr: XXX 2010-08-17 17:38:25 [4912] [6] DEBUG: esm_class: 3 = 0x0003 2010-08-17 17:38:25 [4912] [6] DEBUG: protocol_id: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: priority_flag: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: schedule_delivery_time: NULL 2010-08-17 17:38:25 [4912] [6] DEBUG: validity_period: NULL 2010-08-17 17:38:25 [4912] [6] DEBUG: registered_delivery: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: data_coding: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-08-17 17:38:25 [4912] [6] DEBUG: sm_length: 6 = 0x0006 2010-08-17 17:38:25 [4912] [6] DEBUG: short_message: muppet 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP PDU dump ends. 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput limit exceeded (1.00,0.05) 2010-08-17 17:38:25 [4912] [6] DEBUG: SMPP[SMSC-XXX]: throughput limit exceeded It seems like I have been able to send 5 messages in 5 seconds which 1 msg/sec and I set it to 0.05. I could be missing the obvious. Regards, 2010/8/18 Nikos Balkanas nbalka...@gmail.com Don't worry, bearerbox does smsc load balance, and everything else been equal it will send through SMSc with mallest queue. BR, Nikos - Original Message - From: brett skinner To: Rene Kluwen Cc: Users Sent: Tuesday, August 17, 2010 8:04 PM Subject: Re: Queue Size from status page What does the queue size for the bearerbox represent? I thought this was the total in the system and would
Re: Queue Size from status page
like I have been able to send 5 messages in 5 seconds which 1 msg/sec and I set it to 0.05. I could be missing the obvious. Regards, 2010/8/18 Nikos Balkanas nbalka...@gmail.com Don't worry, bearerbox does smsc load balance, and everything else been equal it will send through SMSc with mallest queue. BR, Nikos - Original Message - From: brett skinner To: Rene Kluwen Cc: Users Sent: Tuesday, August 17, 2010 8:04 PM Subject: Re: Queue Size from status page What does the queue size for the bearerbox represent? I thought this was the total in the system and would be the summation of the individual SMSCs? Maybe I should start off with the goal. What we are trying to do is to make sure that we don't give Kannel too much work to do. So we want to be able to back off until the queue size (the number of SMSs it still needs to send on to SMSCs) has fallen to a certain level and then submit again until it reaches an upper level and then back off again. Which queue size should I be using for this? Regards, On Tue, Aug 17, 2010 at 6:05 PM, Rene Kluwen rene.klu...@chimit.nl wrote: I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox… and one in the smsc driver as well. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of brett skinner Sent: Tuesday, 17 August, 2010 17:32 To: Users Subject: Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
RE: Queue Size from status page
I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox. and one in the smsc driver as well. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of brett skinner Sent: Tuesday, 17 August, 2010 17:32 To: Users Subject: Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
Re: Queue Size from status page
What does the queue size for the bearerbox represent? I thought this was the total in the system and would be the summation of the individual SMSCs? Maybe I should start off with the goal. What we are trying to do is to make sure that we don't give Kannel too much work to do. So we want to be able to back off until the queue size (the number of SMSs it still needs to send on to SMSCs) has fallen to a certain level and then submit again until it reaches an upper level and then back off again. Which queue size should I be using for this? Regards, On Tue, Aug 17, 2010 at 6:05 PM, Rene Kluwen rene.klu...@chimit.nl wrote: I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox… and one in the smsc driver as well. == Rene *From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On Behalf Of *brett skinner *Sent:* Tuesday, 17 August, 2010 17:32 *To:* Users *Subject:* Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
Re: Queue Size from status page
Hi Thanks Rene. Yes I have been using the XML page. Mostly because I am lazy and use some 3rd party Java libraries to parse the XML. :) Regards, On Tue, Aug 17, 2010 at 7:16 PM, Rene Kluwen rene.klu...@chimit.nl wrote: Bearerbox passes messages through from smsbox to the smsc driver, handling them in its own queue. The queue size you want is probably the one that your messages get stuck in. In this case the smsc queue. What I advise you is to request the xml status feed from bearerbox. Parse that file… and add all the queue sizes together. You will end up with the figure you probably want to. == Rene *From:* brett skinner [mailto:tatty.dishcl...@gmail.com] *Sent:* Tuesday, 17 August, 2010 19:05 *To:* Rene Kluwen *Cc:* Users *Subject:* Re: Queue Size from status page What does the queue size for the bearerbox represent? I thought this was the total in the system and would be the summation of the individual SMSCs? Maybe I should start off with the goal. What we are trying to do is to make sure that we don't give Kannel too much work to do. So we want to be able to back off until the queue size (the number of SMSs it still needs to send on to SMSCs) has fallen to a certain level and then submit again until it reaches an upper level and then back off again. Which queue size should I be using for this? Regards, On Tue, Aug 17, 2010 at 6:05 PM, Rene Kluwen rene.klu...@chimit.nl wrote: I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox… and one in the smsc driver as well. == Rene *From:* users-boun...@kannel.org [mailto:users-boun...@kannel.org] *On Behalf Of *brett skinner *Sent:* Tuesday, 17 August, 2010 17:32 *To:* Users *Subject:* Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
RE: Queue Size from status page
Well. that is exactly why the xml status page was created. So no hard feelings :=). == Rene From: brett skinner [mailto:tatty.dishcl...@gmail.com] Sent: Tuesday, 17 August, 2010 19:27 To: Rene Kluwen Cc: Users Subject: Re: Queue Size from status page Hi Thanks Rene. Yes I have been using the XML page. Mostly because I am lazy and use some 3rd party Java libraries to parse the XML. :) Regards, On Tue, Aug 17, 2010 at 7:16 PM, Rene Kluwen rene.klu...@chimit.nl wrote: Bearerbox passes messages through from smsbox to the smsc driver, handling them in its own queue. The queue size you want is probably the one that your messages get stuck in. In this case the smsc queue. What I advise you is to request the xml status feed from bearerbox. Parse that file. and add all the queue sizes together. You will end up with the figure you probably want to. == Rene From: brett skinner [mailto:tatty.dishcl...@gmail.com] Sent: Tuesday, 17 August, 2010 19:05 To: Rene Kluwen Cc: Users Subject: Re: Queue Size from status page What does the queue size for the bearerbox represent? I thought this was the total in the system and would be the summation of the individual SMSCs? Maybe I should start off with the goal. What we are trying to do is to make sure that we don't give Kannel too much work to do. So we want to be able to back off until the queue size (the number of SMSs it still needs to send on to SMSCs) has fallen to a certain level and then submit again until it reaches an upper level and then back off again. Which queue size should I be using for this? Regards, On Tue, Aug 17, 2010 at 6:05 PM, Rene Kluwen rene.klu...@chimit.nl wrote: I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox. and one in the smsc driver as well. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of brett skinner Sent: Tuesday, 17 August, 2010 17:32 To: Users Subject: Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
Re: Queue Size from status page
Hi Brett Then you should look at a per SMSC queue. Not all SMSCs have the same thoughput. I do have AT and SMPP smsc's so the later is by far faster so the same queue size behaves different for each smsc. I do parse the admin page for getting each smsc's queue using the same xml parser that uses the monitoring tool that came with kannel (contrib folder), and do a 5 min estimates of the queue, based on the real throughtput I get on my smsc. That way I feed that calculated amount of messages to kannel on a per smsc base Hope helps Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Tue, Aug 17, 2010 at 12:04 PM, brett skinner tatty.dishcl...@gmail.com wrote: What does the queue size for the bearerbox represent? I thought this was the total in the system and would be the summation of the individual SMSCs? Maybe I should start off with the goal. What we are trying to do is to make sure that we don't give Kannel too much work to do. So we want to be able to back off until the queue size (the number of SMSs it still needs to send on to SMSCs) has fallen to a certain level and then submit again until it reaches an upper level and then back off again. Which queue size should I be using for this? Regards, On Tue, Aug 17, 2010 at 6:05 PM, Rene Kluwen rene.klu...@chimit.nl wrote: I think you guessed the answer yourself already. You have to add the queue sizes. Queue size in bearerbox is one. Then you have a queue size in smsbox… and one in the smsc driver as well. == Rene From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of brett skinner Sent: Tuesday, 17 August, 2010 17:32 To: Users Subject: Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
Re: Queue Size from status page
Hi, There are many queues used in kannel. There is the global store, backed up in the filesystem, and there is a queue in every smsc driver. Top entry is the global store. Lower entry is the per smsc queue. FAKE smsc is a special case smsc, which may not totally follow regular flow. It won't process the SMS (keep them in its queue) until the fakesmsc client connects to it. AFAIK it is the only exception to global store. Read more about it in the User's guide. BR, Nikos - Original Message - From: brett skinner To: Users Sent: Tuesday, August 17, 2010 6:32 PM Subject: Queue Size from status page Hi I have looked through the user guide for further explanation of the various queue sizes from the status page but I have found none. Please view the attached jpg. I have circled two queue sizes in red. I have been using the top queue size because I was under the impression that this was the queue size for all messages waiting to be sent out by Kannel. The bottom queue size appears to be the only one that moves. In order to test this I had to attach a fake smsc, set the throughput to 1 and bombarded it with messages. Am I correct and there should be a total queue size for Kannel? Or do I have to go through each individual SMSC and add the queue sizes together? Regards,
