Hello World,
I've got some questions regarding Kannel as a WAP-Gateway:
- I'm running Kannel on a Linux (SuSe 7.2) Box as WAP-Gateway and anything seems to be fine.
- Im using a Nokia6210 configured as described in the documentation.
Sometimes the connection hangs up with following errormessage:
- <<debug.txt>>
These errros seems to occur after some time (say a few minutes) regardless of the pages requested.
Any hints to get rid of this problem or anyone got the same ?
Mit freundlichem Gruß / kind regards
Horst Weimann
Software Development Group
Network Group
Siemens VDO Automotive AG
Infotainment Solutions
Philipsstrasse 1
35576 Wetzlar
Tel: +49 6441 370-9013
Fax: +49 6441 370-9042
mailto:[EMAIL PROTECTED]
2002-09-25 18:43:19 [7] INFO: WSP: Fetched <http://192.168.120.11/alpha/wml/do.wml> (text/vnd.wap.wml, charset='') 2002-09-25 18:43:19 [7] DEBUG: WSP: Setting Referer URL to <http://192.168.120.11/alpha/wml/do.wml> 2002-09-25 18:43:19 [1] DEBUG: WSP: machine 0x80df2f8, state CONNECTING_2, event S-MethodResult.req 2002-09-25 18:43:19 [1] DEBUG: WSP: method 51, state PROCESSING, event S-MethodResult.req 2002-09-25 18:43:19 [1] DEBUG: WSP 6/51: New method state REPLYING 2002-09-25 18:43:19 [1] DEBUG: WSP 6: New state CONNECTING_2 2002-09-25 18:43:19 [5] DEBUG: WTP: resp_machine 51, state RESULT_WAIT, event TR-Result.req. 2002-09-25 18:43:19 [5] DEBUG: WTP 51: New state RESULT_RESP_WAIT 2002-09-25 18:43:19 [4] DEBUG: Timeout-R elapsed. 2002-09-25 18:43:19 [5] DEBUG: WTP: resp_machine 48, state RESULT_RESP_WAIT, event Timeout-R. 2002-09-25 18:43:19 [5] DEBUG: WTP 48: New state RESULT_RESP_WAIT 2002-09-25 18:43:22 [4] DEBUG: Timeout-R elapsed. 2002-09-25 18:43:22 [5] DEBUG: WTP: resp_machine 49, state RESULT_RESP_WAIT, event Timeout-R. 2002-09-25 18:43:22 [5] DEBUG: WTP 49: New state RESULT_RESP_WAIT 2002-09-25 18:43:24 [4] DEBUG: Timeout-R elapsed. 2002-09-25 18:43:24 [4] DEBUG: Timeout-R elapsed. 2002-09-25 18:43:24 [4] DEBUG: Timeout-R elapsed. 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 44, state RESULT_RESP_WAIT, event Timeout-R. 2002-09-25 18:43:24 [5] DEBUG: WTP 44: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e44c0 (44) 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 47, state RESULT_RESP_WAIT, event Timeout-R. 2002-09-25 18:43:24 [5] DEBUG: WTP 47: New state RESULT_RESP_WAIT 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 45, state RESULT_RESP_WAIT, event Timeout-R. 2002-09-25 18:43:24 [5] DEBUG: WTP 45: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e0478 (45) 2002-09-25 18:43:24 [1] DEBUG: WSP: machine 0x80df2f8, state CONNECTING_2, event TR-Abort.ind 2002-09-25 18:43:24 [1] DEBUG: WSP: method 51, state REPLYING, event Abort 2002-09-25 18:43:24 [1] DEBUG: WSP 6/51: New method state NULL_METHOD 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMethodMachine 51 2002-09-25 18:43:24 [1] DEBUG: WSP: method 49, state REPLYING, event Abort 2002-09-25 18:43:24 [1] DEBUG: WSP 6/49: New method state NULL_METHOD 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMethodMachine 49 2002-09-25 18:43:24 [1] DEBUG: WSP: method 48, state REPLYING, event Abort 2002-09-25 18:43:24 [1] DEBUG: WSP 6/48: New method state NULL_METHOD 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMethodMachine 48 2002-09-25 18:43:24 [1] DEBUG: WSP: method 47, state REPLYING, event Abort 2002-09-25 18:43:24 [1] DEBUG: WSP 6/47: New method state NULL_METHOD 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMethodMachine 47 2002-09-25 18:43:24 [1] DEBUG: WSP: method 45, state REPLYING, event Abort 2002-09-25 18:43:24 [1] DEBUG: WSP 6/45: New method state NULL_METHOD 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMethodMachine 45 2002-09-25 18:43:24 [1] DEBUG: WSP 6: New state NULL_SESSION 2002-09-25 18:43:24 [1] DEBUG: Destroying WSPMachine 0x80df2f8 2002-09-25 18:43:24 [1] ERROR: WSP: Cannot find session machine for event. 2002-09-25 18:43:24 [1] DEBUG: Dumping WAPEvent 0x80de688 2002-09-25 18:43:24 [1] DEBUG: type = TR-Abort.ind 2002-09-25 18:43:24 [1] DEBUG: abort_code = 8 2002-09-25 18:43:24 [1] DEBUG: handle = 45 2002-09-25 18:43:24 [1] DEBUG: WAPAddrTuple 0x80de208 = <192.168.120.12:11864> - <0.0.0.0:9201> 2002-09-25 18:43:24 [1] DEBUG: ir_flag = 1 2002-09-25 18:43:24 [1] DEBUG: WAPEvent dump ends. 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 51, state RESULT_RESP_WAIT, event TR-Abort.req. 2002-09-25 18:43:24 [5] DEBUG: WTP 51: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e4000 (51) 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 49, state RESULT_RESP_WAIT, event TR-Abort.req. 2002-09-25 18:43:24 [5] DEBUG: WTP 49: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e18a0 (49) 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 48, state RESULT_RESP_WAIT, event TR-Abort.req. 2002-09-25 18:43:24 [5] DEBUG: WTP 48: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e3fa0 (48) 2002-09-25 18:43:24 [5] DEBUG: WTP: resp_machine 47, state RESULT_RESP_WAIT, event TR-Abort.req. 2002-09-25 18:43:24 [5] DEBUG: WTP 47: New state LISTEN 2002-09-25 18:43:24 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80df8d0 (47) 2002-09-25 18:43:24 [5] ERROR: WTP_RESP: resp_machine_find_or_create: WSP primitive to a wrong WTP machine 2002-09-25 18:43:32 [5] DEBUG: WTP: Created WTPRespMachine 0x80e0ab8 (52) 2002-09-25 18:43:32 [5] DEBUG: WTP: resp_machine 52, state LISTEN, event RcvInvoke. 2002-09-25 18:43:32 [5] DEBUG: WTP 52: New state INVOKE_RESP_WAIT 2002-09-25 18:43:32 [5] DEBUG: WTP: resp_machine 52, state INVOKE_RESP_WAIT, event TR-Abort.req. 2002-09-25 18:43:32 [5] DEBUG: WTP 52: New state LISTEN 2002-09-25 18:43:32 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80e0ab8 (52)
