I'm trying to retrieve some WML documents through Kannel using a
microbrowser as a handset simulator. When I ask the microbrowser to retrieve
a URL (URI if you prefer) containing a valid WML document, I get one of the
following 2 responses:
* "Unknown Command:" followed by the original URL
* No response at all
My Software environment is Kannel 1.1.6 running on Debian Linux 3.0
('woody').
Im using "Deck-It WML Previewer 1.2.3" and "WinWAP 3.1 Pro" as the
MicroBrowsers on Win2000. I've run 'tcpdump' on the network port on which
the bearerbox is listening and have seen what seems to be a valid HTTP GET
request with the URL I placed in the MicroBrowser. The bearerbox log file
registers that a request was received, but the request does not register in
the wapbox log file. Additional information in the bearerbox log file
indicates, however, that a port has been setup between bearerbox and wapbox.
A portion of the bearerbox log file is duplicated below:
2002-06-27 16:48:10 [0] INFO: Added logfile `/var/log/kannel/bearerbox.log'
with level `0'.
2002-06-27 16:48:10 [0] INFO: ----------------------------------------
2002-06-27 16:48:10 [0] INFO: Kannel bearerbox II version 1.1.6 starting
2002-06-27 16:48:10 [0] DEBUG: HTTP: Opening server at port 13000.
2002-06-27 16:48:10 [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2002-06-27 16:48:10 [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
2002-06-27 16:48:10 [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run)
2002-06-27 16:48:10 [0] DEBUG: starting UDP sender/receiver module
2002-06-27 16:48:10 [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9200>
2002-06-27 16:48:10 [0] DEBUG: Started thread 4 (gw/bb_udp.c:udp_receiver)
2002-06-27 16:48:10 [0] DEBUG: Started thread 5 (gw/bb_udp.c:udp_sender)
2002-06-27 16:48:10 [0] DEBUG: udpc_create: Bound to UDP <0.0.0.0:9201>
2002-06-27 16:48:10 [0] DEBUG: Started thread 6 (gw/bb_udp.c:udp_receiver)
2002-06-27 16:48:10 [0] DEBUG: Started thread 7 (gw/bb_udp.c:udp_sender)
2002-06-27 16:48:10 [0] DEBUG: starting wapbox connection module
2002-06-27 16:48:10 [0] DEBUG: Started thread 8
(gw/bb_boxc.c:wdp_to_wapboxes)
2002-06-27 16:48:10 [0] DEBUG: Started thread 9 (gw/bb_boxc.c:wapboxc_run)
2002-06-27 16:48:10 [0] DEBUG: starting WDP router
2002-06-27 16:48:10 [0] DEBUG: Started thread 10 (gw/bearerbox.c:wdp_router)
2002-06-27 16:48:10 [0] INFO: MAIN: Start-up done, entering mainloop
2002-06-27 16:48:10 [9] DEBUG: Started thread 11 (gw/bb_boxc.c:function)
2002-06-27 16:48:10 [11] INFO: Client connected from <127.0.0.1>
2002-06-27 16:48:10 [11] DEBUG: setting up systems for new wapbox
2002-06-27 16:48:10 [11] DEBUG: Started thread 12 (gw/bb_boxc.c:boxc_sender)
2002-06-27 22:02:29 [2] DEBUG: HTTP: Creating HTTPClient for
`160.15.40.242'.
2002-06-27 22:02:29 [3] DEBUG: HTTP: Resetting HTTPClient for
`160.15.40.242'.
2002-06-27 22:03:50 [1] ERROR: Error reading from fd 38:
2002-06-27 22:03:50 [1] ERROR: System error 104: Connection reset by peer
2002-06-27 22:03:50 [1] DEBUG: HTTP: Destroying HTTPClient area 0x80c92b8.
2002-06-27 22:03:50 [1] DEBUG: HTTP: Destroying HTTPClient for
`160.15.40.242'.
2002-06-27 22:03:50 [1] ERROR: Error reading from fd 37:
2002-06-27 22:03:50 [1] ERROR: System error 104: Connection reset by peer
2002-06-27 22:03:50 [1] DEBUG: HTTP: Destroying HTTPClient area 0x80c9468.
2002-06-27 22:03:50 [1] DEBUG: HTTP: Destroying HTTPClient for
`160.15.40.242'.
2002-06-27 22:26:03 [2] DEBUG: HTTP: Creating HTTPClient for
`160.15.40.242'.
2002-06-27 22:26:03 [3] DEBUG: HTTP: Resetting HTTPClient for
`160.15.40.242'.
The lines with system/read errors correspond to times when I exited browser
sessions. I think these represent the termination of connections with the
microbrowsers.
The following lines from the wapbox log file indicate that connection was
established with the bearerbox.
2002-06-27 16:48:10 [0] DEBUG: HTTP: Opening server at port 8080.
2002-06-27 16:48:10 [0] DEBUG: Started thread 10 (gwlib/fdset.c:poller)
2002-06-27 16:48:10 [0] DEBUG: Started thread 11
(gwlib/http.c:server_thread)
2002-06-27 16:48:10 [0] DEBUG: Started thread 12
(gw/wap_push_ppg.c:ota_read_thread)
2002-06-27 16:48:10 [0] DEBUG: Started thread 13
(gw/wap_push_ppg.c:http_read_thread)
2002-06-27 16:48:10 [0] INFO: Connected to bearerbox at localhost port
13002.
2002-06-27 16:48:10 [0] DEBUG: Started thread 14
(gw/heartbeat.c:heartbeat_thread)
For completeness, below I've copied some information from
/etc/kannel/kannel.conf:
group = core
admin-port = 13000
admin-password = bar
admin-deny-ip = ""
admin-allow-ip = "VARIOUS VALID IP ADDRESS RANGES"
udp-deny-ip = ""
udp-allow-ip = "VARIOUS VALID IP ADDRESS RANGES"
box-deny-ip = ""
box-allow-ip = "VARIOUS VALID IP ADDRESS RANGES"
wapbox-port = 13002
wdp-interface-name = "*"
log-file = "/var/log/kannel/bearerbox.log"
log-level = 0
group = wapbox
bearerbox-host = localhost
log-file = "/var/log/kannel/wapbox.log"
log-level = 0
My goal is to retrieve and to properly display the WML pages on the
microbrowser screens. Right now my high-level problem appears to be a lack
of communication between bearerbox and wapbox for the initial HTTP request
from the microbrowsers. I suspect the solution to the problem lies between
the bearerbox log file and the kannel.conf file.
In addition, when I configure the browsers, the request port is set to 13000
(see line 4 of the bearerbox log file). When I reconfigure the browser to
use port number 9200 or 9201 as shown in lines 9 and 12 of the bearerbox log
file, the error message changes to "connection refused."
Any suggestions? Thank you in advance to one and all for your help.
Ira Rosen
