Stipe Tolj wrote: > 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 You've catched me again, I'm not a C developer :-S
> > 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. When we connect to this new operator, we configure Kannel as usual. Couple of days later, operator is saying that we are leaving open connections with the SMSC. I then tried to understand why this happens (with my limited knowledge of smpp protocol), And I figure out that 'kannel opens an maintains ONE and ONLY connection with the SMSC, so I don't know where or when the connections are left open', as the operator is saying that the only content aggregator with this problem is us... > 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. This was my first feeling to this situation. Thanks! -- Manuel Fernando Aller
