WTP time out!

"huangcy" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <006f01c35d74$402ce760$8500a8c0@wqs>
hi,list:
    I run Kannel1.3.1 as wap gateway on redhat linux 9.0.
When I use a Kyocera mobile(KZ-820/1.0UP.Browser),It always timeout.
but When i Use Nokia Mobile or SaSung Mobile it works well.
is it the problem of Kannel or is there sth wrong with Kyocera Mobile?

the debug info as follows:
.....
.....
2003-08-05 14:16:14 [1] DEBUG: Octet string dump ends.
2003-08-05 14:16:14 [1] INFO: Returning to code page 1 (default).
2003-08-05 14:16:14 [1] DEBUG: WSP: decoded headers:
2003-08-05 14:16:14 [1] DEBUG: Accept: application/vnd.wap.wmlc; type=1108
2003-08-05 14:16:14 [1] DEBUG: Accept: application/vnd.wap.wmlc
2003-08-05 14:16:14 [1] DEBUG: Accept: application/vnd.wap.wmlscriptc
2003-08-05 14:16:14 [1] DEBUG: User-Agent: kyocera-KZ-820/1.0 UP.Browser/4.1.26c4
2003-08-05 14:16:14 [1] DEBUG: Accept-Language: zhch
2003-08-05 14:16:14 [1] DEBUG: Accept: image/png
2003-08-05 14:16:14 [1] DEBUG: Accept: image/vnd.wap.wbmp
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.ringtone; content-type=application/x-qcp; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.ringtone; content-type=application/x-pmd; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.wallpaper; content-type=image/png; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.picture; content-type=image/png; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.audio; content-type=application/x-qcp; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.audio; content-type=application/x-pmd; size=102400
2003-08-05 14:16:14 [1] DEBUG: Accept: application/x-mmc.title; charset=utf-8; size=40
2003-08-05 14:16:14 [1] DEBUG: Accept-Charset: utf-8
2003-08-05 14:16:14 [1] DEBUG: WSP: End of decoded headers.
2003-08-05 14:16:14 [1] DEBUG: WSP 22: New state CONNECTING
2003-08-05 14:16:14 [1] DEBUG: WSP: machine 0x8100128, state CONNECTING, event S-Connect.res
2003-08-05 14:16:14 [1] DEBUG: WSP 22: New state CONNECTING_2
2003-08-05 14:16:14 [5] DEBUG: WTP: resp_machine 51, state RESULT_WAIT, event TR-Result.req.
2003-08-05 14:16:14 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT
2003-08-05 14:16:21 [4] DEBUG: Timeout-R elapsed.
2003-08-05 14:16:21 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event Timeout-R.
2003-08-05 14:16:21 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT
2003-08-05 14:16:23 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event RcvInvoke.
2003-08-05 14:16:23 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT
2003-08-05 14:16:28 [4] DEBUG: Timeout-R elapsed.
2003-08-05 14:16:28 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event Timeout-R.
2003-08-05 14:16:28 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT
2003-08-05 14:16:35 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event RcvInvoke.
2003-08-05 14:16:35 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT
2003-08-05 14:16:35 [4] DEBUG: Timeout-R elapsed.
......
.....
-08-05 14:17:17 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event Timeout-R.
2003-08-05 14:17:17 [5] DEBUG: WTP 51: New state LISTEN
2003-08-05 14:17:17 [1] DEBUG: WSP: machine 0x8100128, state CONNECTING_2, event TR-Abort.ind
2003-08-05 14:17:17 [1] DEBUG: WSP 22: New state NULL_SESSION
2003-08-05 14:17:17 [1] DEBUG: Destroying WSPMachine 0x8100128
2003-08-05 14:17:17 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80f9fc0 (51)
2003-08-05 14:17:30 [5] INFO: WTP_RESP: resp_machine_find_or_create: abort received, yet having no machine
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.