wap gateway

I use the kannel just the same way like Wap Gateway does and  everything
works fine except for one thing. The Wap Gateway quite often "questions the
telephone".
Maybe I'll explain it more precisely.
At the first connection with the Wap Gateway it looks like this:

>From the packages:

09:22:41.858333 gsm.operator.49569 > kannel.9201: udp 61
09:22:41.860523 kannel.9201 > gsm.operator.49569: udp 4 (DF)
09:22:43.439871 gsm.operator.49569 > kannel.9201: udp 566
09:22:43.441842 kannel.9201 > gsm.operator.49569: udp 3 (DF)
09:22:44.449922 gsm.operator.49569 > kannel.9201: udp 3
09:22:44.457938 kannel.9201 > gsm.operator.49569: udp 30 (DF)
09:22:45.410972 gsm.operator.49569 > kannel.9201: udp 3
09:22:46.307521 gsm.operator.49569 > kannel.9201: udp 61
09:22:46.401088 kannel.9201 > gsm.operator.49569: udp 219 (DF)
09:22:47.146901 gsm.operator.49569 > kannel.9201: udp

And from the logs:

2003-12-29 09:22:41 [7] DEBUG: datagram received
2003-12-29 09:22:41 [9] DEBUG: Did not find previous routing info for WDP,
generating new
2003-12-29 09:22:41 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:41 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:41 [12] DEBUG: boxc_receiver: got wdp from wapbox
2003-12-29 09:22:41 [8] DEBUG: udp: sending message
2003-12-29 09:22:43 [7] DEBUG: datagram received
2003-12-29 09:22:43 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:43 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:43 [12] DEBUG: boxc_receiver: got wdp from wapbox
2003-12-29 09:22:43 [8] DEBUG: udp: sending message
2003-12-29 09:22:44 [7] DEBUG: datagram received
2003-12-29 09:22:44 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:44 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:44 [12] DEBUG: boxc_receiver: got wdp from wapbox
2003-12-29 09:22:44 [8] DEBUG: udp: sending message
2003-12-29 09:22:45 [7] DEBUG: datagram received
2003-12-29 09:22:45 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:45 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:46 [7] DEBUG: datagram received
2003-12-29 09:22:46 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:46 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:46 [12] DEBUG: boxc_receiver: got wdp from wapbox
2003-12-29 09:22:46 [8] DEBUG: udp: sending message
2003-12-29 09:22:47 [7] DEBUG: datagram received
2003-12-29 09:22:47 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:22:47 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:22:57 [12] DEBUG: boxc_receiver: heartbeat with load value 0
received

If the next connection takes place after less than 30 seconds it looks like
this:

Packages:

09:23:05.215167 gsm.operator.49569 > kannel.9201: udp 61
09:23:05.306003 kannel.9201 > gsm.operator.49569: udp 219 (DF)
09:23:06.308183 gsm.operator.49569 > kannel.9201: udp 3

Logs:

2003-12-29 09:23:05 [7] DEBUG: datagram received
2003-12-29 09:23:05 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:23:05 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>
2003-12-29 09:23:05 [12] DEBUG: boxc_receiver: got wdp from wapbox
2003-12-29 09:23:05 [8] DEBUG: udp: sending message
2003-12-29 09:23:06 [7] DEBUG: datagram received
2003-12-29 09:23:06 [13] DEBUG: send_msg: sending msg to box: <127.0.0.1>
2003-12-29 09:23:06 [13] DEBUG: boxc_sender: sent message to <127.0.0.1>

However if  we wait more than 30 seconds the connection between the
telephone and the Wap Gateway is the same as at the first time,  so
unfortunately it is longer (more packages). As a result we send more data
and pay more. I must add that it doesn't matter if the second page  that we
are visitting is the same or another one.

So My question is: "How make this time of "remembering" information about
the telephone longer than 30 seconds e.g. 24 hours?"

I'm looking forward to hearing from you

Andrzej Kalemba :)