Has anyone successfully managed to use the Kannel WAP gateway with the
Mitsubishi Trium WAP browser?
I am seeing UDP packet flows but the browser eventually times out and
gives an error, although there is some sort of negotiation going on
between Kannel and the client:
18:22:43.947072 eth0 < trium.49200 > kannel.9201: udp 54
18:22:43.954045 eth0 > kannel.9201 > trium.49200: udp 14
18:22:49.205782 eth0 < trium.49200 > kannel.9201: udp 54
18:22:50.967717 eth0 > kannel.9201 > trium.49200: udp 14
18:22:53.964678 eth0 < trium.49200 > kannel.9201: udp 54
18:22:57.977716 eth0 > kannel.9201 > trium.49200: udp 14
18:23:00.033401 eth0 < trium.49200 > kannel.9201: udp 54
18:23:04.572002 eth0 < trium.49200 > kannel.9201: udp 54
18:23:04.987613 eth0 > kannel.9201 > trium.49200: udp 14
18:23:08.930829 eth0 < trium.49200 > kannel.9201: udp 54
18:23:11.997795 eth0 > kannel.9201 > trium.49200: udp 14
18:23:13.989725 eth0 < trium.49200 > kannel.9201: udp 54
18:23:19.007659 eth0 > kannel.9201 > trium.49200: udp 14
18:23:19.010429 eth0 < trium.49200 > kannel.9201: udp 54
18:23:26.017765 eth0 > kannel.9201 > trium.49200: udp 14
18:23:33.027784 eth0 > kannel.9201 > trium.49200: udp 14
18:23:40.037696 eth0 > kannel.9201 > trium.49200: udp 14
This is what I see in the wapbox debug output:
2001-12-18 18:22:43 [2] DEBUG: WSP: decoded headers:
2001-12-18 18:22:43 [2] DEBUG: Accept: application/vnd.wap.wmlc
2001-12-18 18:22:43 [2] DEBUG: Accept: text/plain
2001-12-18 18:22:43 [2] DEBUG: Accept: text/x-vCard
2001-12-18 18:22:43 [2] DEBUG: Accept: image/vnd.wap.wbmp
2001-12-18 18:22:43 [2] DEBUG: Accept: image/gif
2001-12-18 18:22:43 [2] DEBUG: Accept: application/vnd.wap.wmlscriptc
2001-12-18 18:22:43 [2] DEBUG: Accept-Charset: utf-8
2001-12-18 18:22:43 [2] DEBUG: Accept-Charset: iso-8859-1
2001-12-18 18:22:43 [2] DEBUG: Accept-Language: en
2001-12-18 18:22:43 [2] DEBUG: User-Agent: Mitsu/1.1.A (Mondo)
2001-12-18 18:22:43 [2] DEBUG: WSP: End of decoded headers.
2001-12-18 18:22:43 [2] DEBUG: WSP 3: New state CONNECTING
2001-12-18 18:22:43 [2] DEBUG: WSP: machine 0x40302fc8, state CONNECTING, event
S_Connect_Res
2001-12-18 18:22:43 [2] DEBUG: WSP 3: New state CONNECTING_2
2001-12-18 18:22:43 [5] DEBUG: WTP: resp_machine 3, state RESULT_WAIT, event
TR_Result_Req.
2001-12-18 18:22:43 [5] DEBUG: WTP_SEND: add_initiator_address
2001-12-18 18:22:43 [5] DEBUG: WTP 3: New state RESULT_RESP_WAIT
2001-12-18 18:22:49 [5] DEBUG: WTP: resp_machine 3, state RESULT_RESP_WAIT, event
RcvInvoke.
2001-12-18 18:22:49 [5] DEBUG: WTP 3: New state RESULT_RESP_WAIT
2001-12-18 18:22:50 [1] DEBUG: TimerTO_R elapsed.
2001-12-18 18:22:50 [5] DEBUG: WTP: resp_machine 3, state RESULT_RESP_WAIT, event
TimerTO_R.
2001-12-18 18:22:50 [5] DEBUG: WTP 3: New state RESULT_RESP_WAIT
2001-12-18 18:22:53 [5] DEBUG: WTP: resp_machine 3, state RESULT_RESP_WAIT, event
RcvInvoke.
2001-12-18 18:22:53 [5] DEBUG: WTP 3: New state RESULT_RESP_WAIT
2001-12-18 18:22:57 [1] DEBUG: TimerTO_R elapsed.
My setup is Kannel v1.0.3 (libxml2 v2.4.7) on single processor Redhat
Linux 6.2 i386 host.
The Kannel config works fine with other WAP clients such as Siemens SL45.
Thanks,
Dominic.
