Hi Nikos, I'm referring to MO traffic. It only affects incoming SMS. We run separate TX and RX and operator does not offer transceiver mode. We don't have any logs that indicate slow speed, though traffics backs up at operator's end. When I call them, they insist that it is my application that is not 'picking' messages fast enough from their SMSC. Funny thing is the inhouse app clears the messages in a heartbit.
-----Original Message----- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Thursday, April 14, 2011 12:38 PM To: Rapture; us...@vm1.kannel.org Subject: Re: Slow RX incoming Hi, Kannel doesn't "retrieve" SMS from the operator. Operator sends them to kannel. Throughput doesn't affect incoming traffic, only outgoing and not *_resp pdus. Are you referring to MO traffic or MT (DLRs)? It is difficult to help you without any kind of logs. Since there is back log at your operator, what do his logs say? There is an issue with separate Tx/Rx connections in kannel. If only 1 of the 2 drops, while the other is working, kannel doesn't realize it to reconnect both ends. You might try transceiver mode for that. BR, Nikos ----- Original Message ----- From: Rapture To: users@kannel.org Sent: Thursday, April 14, 2011 8:27 AM Subject: Slow RX incoming Hi guys, We've been running a campaign averaging 350,000 messages a day. Lately I noticed kannel does not retrieve them as fast as it needs to hence a backlog builds on the operator's end. This is only affecting one of the operators. On calling them, they insisted that it is Kannel which determines how many RX messages to pull. I tried an old SMPP client software I'd written in Delphi and it cleared all the backlog in less than 5 mins and continues to do so in real time. All data is dumped into the same mysql table. I've tried using throughput in kannel with no success. I've even opened upto 15 channels to the same operator without success. What could be the issue? How can I speed up my intake of messages? Distraught, TR
