Interesting Keep-Alive behaviorCould it be that your firewall is NATing and
drops the connection before the 120 seconds time ?
We had that problem once.
Kannel -> firewall still have the connection opened, but firewall -> smsc
connection was droped by NAT, so
when kannel tries to send anything (not just keepalive packets), firewall
doesn't have any connection to smsc.

Ask if they (firewall admins) have timeouts and/or try to set a keepalive
timeout in kannel smaller than firewall
timeout.
  ----- Original Message -----
  From: Ozkan ERENER
  To: [EMAIL PROTECTED]
  Sent: Wednesday, September 12, 2001 3:44 PM
  Subject: Interesting Keep-Alive behavior


  Hi -

  We've spotted a problem in between a Kannel GW and CMG SMSC. A firewall in
betwwen starts blocking packets from Kannel to the SMSC roughly 2 minutes
after a connection is established. Kannel recovers from this situation 5-7
minutes after firewall starts blocking. The keep alive parameter in .conf
file is set to 120 seconds.

  When the connection is blocked the bb logs the 31 messages but never
receives an ACK back.  It seems like the bbox keeps trying to send the 31
messages but wouldn't do anything if it's not acked. 5-7 minutes after bbox
logs an error about a connection time out and initiates the connections
again.

  I wonder how's that keep-alive parameter is interpreted? The connections
stay broke well after the 120 second duration.

  thanks a lot,
  Ozkan Erener
  VeriPark - www.veripark.com



Reply via email to