Wapbox problems with new Nokia phones
Pekka Ahmavuo <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
I have tried to use wapbox (latest cvs-kannel) with Nokia 6310. Fetching a WML- page generates generated error message into the log file. I looked for some other user agents from the log files and tried to figure out how they worked. The following user agents seem to work: EricssonT20/R2A OK EricssonT65/R101 OK Nokia5510/1.0 (03.42) OK Nokia6210/1.0 (03.01) OK Nokia6250/1.0 (04.00) OK Nokia7110/1.0 (04.84) OK The following seem to have problems: MOT-D5/4.1.5 UP.Browser/4.1.23c NOK Nokia6310/1.0 (04.10) NOK Nokia8310/1.0 (03.05) NOK Nokia9110/1.0 NOK SIE-S35/3.0 UP/4.1.16m NOK ------------------------------------------------------------------------------ 002-02-26 16:09:18 [15] DEBUG: HTTP: Status line: <HTTP/1.1 200 OK> 2002-02-26 16:09:18 [8] INFO: WSP: Fetched <http://wap.mtampere.com/> (text/vnd. wap.wml, charset='') 2002-02-26 16:09:18 [1] DEBUG: WSP: machine 0x40309108, state CONNECTING_2, even t S-MethodResult.req 2002-02-26 16:09:18 [1] DEBUG: WSP: method 123, state PROCESSING, event S-Method Result.req 2002-02-26 16:09:18 [6] DEBUG: WTP: resp_machine 123, state RESULT_WAIT, event T R-Result.req. 2002-02-26 16:09:18 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:18 [1] DEBUG: WSP 21/123: New method state REPLYING 2002-02-26 16:09:18 [1] DEBUG: WSP 21: New state CONNECTING_2 2002-02-26 16:09:22 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:22 [6] DEBUG: WTP 122: New state RESULT_RESP_WAIT 2002-02-26 16:09:22 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:22 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:24 [4] DEBUG: Timeout-R elapsed. 2002-02-26 16:09:24 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent Timeout-R. 2002-02-26 16:09:24 [6] DEBUG: WTP 122: New state RESULT_RESP_WAIT 2002-02-26 16:09:25 [4] DEBUG: Timeout-R elapsed. 2002-02-26 16:09:25 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent Timeout-R. 2002-02-26 16:09:25 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:27 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:27 [6] DEBUG: WTP 122: New state RESULT_RESP_WAIT 2002-02-26 16:09:27 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:27 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:31 [4] DEBUG: Timeout-R elapsed. 2002-02-26 16:09:31 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent Timeout-R. 2002-02-26 16:09:31 [6] DEBUG: WTP 122: New state RESULT_RESP_WAIT 2002-02-26 16:09:32 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:32 [6] DEBUG: WTP 122: New state RESULT_RESP_WAIT 2002-02-26 16:09:32 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent RcvInvoke. 2002-02-26 16:09:32 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:32 [4] DEBUG: Timeout-R elapsed. 2002-02-26 16:09:32 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent Timeout-R. 2002-02-26 16:09:32 [6] DEBUG: WTP 123: New state RESULT_RESP_WAIT 2002-02-26 16:09:37 [6] DEBUG: WTP: resp_machine 122, state RESULT_RESP_WAIT, ev ent RcvAbort. 2002-02-26 16:09:37 [6] DEBUG: WTP 122: New state LISTEN 2002-02-26 16:09:37 [6] DEBUG: WTP: Destroying WTPRespMachine 0x40304e48 (122) 2002-02-26 16:09:37 [1] DEBUG: WSP: machine 0x40309108, state CONNECTING_2, even t TR-Abort.ind 2002-02-26 16:09:37 [1] DEBUG: WSP: method 123, state REPLYING, event Abort 2002-02-26 16:09:37 [1] DEBUG: WSP 21/123: New method state NULL_METHOD 2002-02-26 16:09:37 [1] DEBUG: Destroying WSPMethodMachine 123 2002-02-26 16:09:37 [1] DEBUG: WSP 21: New state NULL_SESSION 2002-02-26 16:09:37 [1] DEBUG: Destroying WSPMachine 0x40309108 2002-02-26 16:09:37 [6] DEBUG: WTP: resp_machine 123, state RESULT_RESP_WAIT, ev ent TR-Abort.req. 2002-02-26 16:09:37 [6] DEBUG: WTP 123: New state LISTEN 2002-02-26 16:09:37 [6] DEBUG: WTP: Destroying WTPRespMachine 0x40300450 (123) 2002-02-26 16:09:37 [6] INFO: WTP_RESP: resp_machine_find_or_create: abort recei ved, yet having no machine -pekka