Stipe Tolj wrote: > Manuel Fernando Aller schrieb: >> >> 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... > > my suggetion: > > let the operator provide you logs which proof that. And you may have > the natural arrogance to tell them "We use Kannel, the most used SMS > gateway in the world!". Maybe they will re-think if it's up to the > SMPP cleint. Which is most likely not, but rather a network (TCP) > related issue.. ;) > > Stipe > Ok, the operator sent the output of netstat -n to me:
tcp 0 0 192.168.1.55:3000 10.10.2.10:55740 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:41852 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:40574 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:45049 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:43960 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:45496 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:56315 CLOSE_WAIT tcp 0 0 192.168.1.55:3000 10.10.2.10:57205 CLOSE_WAIT ..... ..... where 192.168.1.55 is the local ip for his smsc server, and 10.10.2.10 is my ip (yes, I've chage that!). So, the operator says I left TCP connections open. I do not connect with 192.168.1.55, I connect with a valid public IP, and evidently the firewall/router/whatever the operator have, redirects the connection to 192.168.1.55. I believe the problem is in the firewall/router/whatever. -- Manuel Fernando Aller
