Manuel Fernando Aller schrieb:
First of all, I don't think it was problem of kannel, but searching in the source code I can't find the specific code where kannel closes connection whith the smsc after sending an sms. As you can imagine, I'm not a c++ developer :-P
you don't have to. Kannel itself is C with POSIX.1 threads (pthreads), so no object orientation at all :p
I agree with Falko, we need more details. In fact the list would need to review a snippet of your bearerbox.log to verify what is going on exactly at the time you have experienced the connection misbehavior.
Another possibility is the so-called "silent TCP teardrop" effect, which means: a router node in the middle of the IP connection route drops the connected "silently". Which means both TCP communication endpoints still think the connection is valid, but the router has "cut it in the middle", without signaling the TCP connect dropping to any of the endpoints.
Typically this leads at some point to a re-connection establishment of the client, and if the server has a "limit" in terms of allowed connections, you run into trouble. I hope you got the picture.
So, the reasons can be various. And typically it's NOT Kannel's fault. So, please send some details to the list, so people can shade some light on your issue.
Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org -------------------------------------------------------------------
