Reposting, did anyone had time to check it out?
PS: I've a couple more unanswered patches, but will remind about them
later.
--
Alejandro Guerrieri
aguerri...@kannel.org
Begin forwarded message:
From: Alejandro Guerrieri aguerri...@kannel.org
Date: 11 de junio de 2009 12:10:17 GMT+02:00
Hi,
I'm currently benchmarking kannel/cvs-20090615 with 40 http smsc type generic
with a host 127.0.0.1 and 40 differents ports.
The thing is that the 30 firsts smsc are working and responding normaly
like this exemple:
#) telnet 127.0.0.1 7188
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape
: SMSC HTTP issue on many smsc
Hi,
I'm currently benchmarking kannel/cvs-20090615 with 40 http smsc type
generic
with a host 127.0.0.1 and 40 differents ports.
The thing is that the 30 firsts smsc are working and responding normaly
like this exemple:
#) telnet 127.0.0.1 7188
Trying 127.0.0.1
Dear Stipe,
Through my custom made benchmarking tool, I have discovered that the wtp layer
in kannel has a very serious issue:
Each request takes slightly longer than the previous one, with the result of
when it reaches 32768 requests, wapbox stalls completely. The number is very
regular,
Hi Al,
What's up?
Did configuration do the trick?
BR,
Nikos
- Original Message -
From: Nikos Balkanas nbalka...@gmail.com
To: Alvaro Cornejo cornejo.alv...@gmail.com; Alan McNatty
a...@catalyst.net.nz
Cc: devel@kannel.org
Sent: Wednesday, June 10, 2009 10:52 AM
Subject: Re: Kannel
Hi Nikos
I didn't make the test since the user guide states that ... After
number of messages has hit this value, Kannel began to discard
them...
I don't want messages to be discarded but queued...
Are they really discarded?
Regards
Alvaro
No, you missunderstood. SMS are discarded only when they hit the Queue
limit. This is the general Q, that should be left unbound, and stored in the
spool directory.
The individual smsc's queue is living in memory. Once this limit is reached,
the SMS is simply returned to the general Queue to
