Problem with Connection to Gateway

Moos Daniel <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <C53497FDB7FC0749AA80AF001048785001E1B85A@chzugexch03.zug.ch.abatos.com>
Hi @all

I have a little Problem with Kannel...
Kannel run on a PowerPC with a Embedded Linux! When I want to connect with
my Mobilephone to Kannel then I get nothing!
Here are the Log-Files from Bearerbox and Wapbox:

bash-2.05# cat /var/log/kannel/bearerbox.log
2004-03-11 14:41:38 [341] [0] INFO: Added logfile
`/var/log/kannel/bearerbox.log' with level `0'.
2004-03-11 14:41:38 [341] [0] INFO: SSL not supported, no SSL initialization
done.
2004-03-11 14:41:38 [341] [0] INFO: HTTP: Opening server at port 13000.
2004-03-11 14:41:38 [343] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to
pid 343.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 2
(gwlib/http.c:server_thread)
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 3
(gw/bb_http.c:httpadmin_run)
2004-03-11 14:41:38 [341] [0] DEBUG: starting UDP sender/receiver module
2004-03-11 14:41:38 [344] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread)
maps to pid 344.
2004-03-11 14:41:38 [341] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9200>
2004-03-11 14:41:38 [345] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run)
maps to pid 345.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 4
(gw/bb_udp.c:udp_receiver)
2004-03-11 14:41:38 [346] [4] DEBUG: Thread 4 (gw/bb_udp.c:udp_receiver)
maps to pid 346.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 5
(gw/bb_udp.c:udp_sender)
2004-03-11 14:41:38 [341] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9201>
2004-03-11 14:41:38 [347] [5] DEBUG: Thread 5 (gw/bb_udp.c:udp_sender) maps
to pid 347.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 6
(gw/bb_udp.c:udp_receiver)
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 7
(gw/bb_udp.c:udp_sender)
2004-03-11 14:41:38 [341] [0] DEBUG: starting wapbox connection module
2004-03-11 14:41:38 [348] [6] DEBUG: Thread 6 (gw/bb_udp.c:udp_receiver)
maps to pid 348.
2004-03-11 14:41:38 [349] [7] DEBUG: Thread 7 (gw/bb_udp.c:udp_sender) maps
to pid 349.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 8
(gw/bb_boxc.c:wdp_to_wapboxes)
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 9
(gw/bb_boxc.c:wapboxc_run)
2004-03-11 14:41:38 [341] [0] DEBUG: starting WDP router
2004-03-11 14:41:38 [350] [8] DEBUG: Thread 8 (gw/bb_boxc.c:wdp_to_wapboxes)
maps to pid 350.
2004-03-11 14:41:38 [341] [0] DEBUG: Started thread 10
(gw/bearerbox.c:wdp_router)
2004-03-11 14:41:38 [341] [0] INFO: ----------------------------------------
2004-03-11 14:41:38 [351] [9] DEBUG: Thread 9 (gw/bb_boxc.c:wapboxc_run)
maps to pid 351.
2004-03-11 14:41:38 [341] [0] INFO: Kannel bearerbox II version cvs-20040310
starting
2004-03-11 14:41:38 [341] [0] INFO: MAIN: Start-up done, entering mainloop
2004-03-11 14:41:38 [352] [10] DEBUG: Thread 10 (gw/bearerbox.c:wdp_router)
maps to pid 352.
2004-03-11 14:42:12 [351] [9] DEBUG: Started thread 11
(gw/bb_boxc.c:function)
2004-03-11 14:42:12 [362] [11] DEBUG: Thread 11 (gw/bb_boxc.c:function) maps
to pid 362.
2004-03-11 14:42:12 [362] [11] INFO: Client connected from <127.0.0.1>
2004-03-11 14:42:12 [362] [11] DEBUG: setting up systems for new wapbox
2004-03-11 14:42:12 [362] [11] DEBUG: Started thread 12
(gw/bb_boxc.c:boxc_sender)
2004-03-11 14:42:12 [363] [12] DEBUG: Thread 12 (gw/bb_boxc.c:boxc_sender)
maps to pid 363.
2004-03-11 14:49:15 [348] [6] DEBUG: datagram received
2004-03-11 14:49:15 [350] [8] DEBUG: Did not find previous routing info for
WDP, generating new
2004-03-11 14:49:15 [363] [12] DEBUG: send_msg: sending msg to box:
<127.0.0.1>
2004-03-11 14:49:15 [363] [12] DEBUG: boxc_sender: sent message to
<127.0.0.1>


bash-2.05# cat /var/log/kannel/wapbox.log
2004-03-11 14:42:11 [353] [0] INFO: Added logfile
`/var/log/kannel/wapbox.log' with level `-1'.
2004-03-11 14:42:11 [353] [0] INFO: Starting to log to file
/var/log/kannel/wapbox.log level -1
2004-03-11 14:42:11 [353] [0] DEBUG: no syslog parameter
2004-03-11 14:42:11 [353] [0] INFO:
------------------------------------------------------------
2004-03-11 14:42:11 [353] [0] INFO: Kannel wapbox version cvs-20040310
starting up.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 1
(wap/wsp_session.c:main_thread)
2004-03-11 14:42:12 [355] [1] DEBUG: Thread 1
(wap/wsp_session.c:main_thread) maps to pid 355.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 2
(wap/wsp_unit.c:main_thread)
2004-03-11 14:42:12 [356] [2] DEBUG: Thread 2 (wap/wsp_unit.c:main_thread)
maps to pid 356.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 3
(wap/wsp_push_client.c:main_thread)
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 4
(wap/timers.c:watch_timers)
2004-03-11 14:42:12 [357] [3] DEBUG: Thread 3
(wap/wsp_push_client.c:main_thread) maps to pid 357.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 5
(wap/wtp_resp.c:main_thread)
2004-03-11 14:42:12 [358] [4] DEBUG: Thread 4 (wap/timers.c:watch_timers)
maps to pid 358.
2004-03-11 14:42:12 [359] [5] DEBUG: Thread 5 (wap/wtp_resp.c:main_thread)
maps to pid 359.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 6
(gw/wap-appl.c:main_thread)
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 7
(gw/wap-appl.c:return_replies_thread)
2004-03-11 14:42:12 [360] [6] DEBUG: Thread 6 (gw/wap-appl.c:main_thread)
maps to pid 360.
2004-03-11 14:42:12 [353] [0] INFO: Connected to bearerbox at localhost port
13002.
2004-03-11 14:42:12 [361] [7] DEBUG: Thread 7
(gw/wap-appl.c:return_replies_thread) maps to pid 361.
2004-03-11 14:42:12 [353] [0] DEBUG: Started thread 8
(gw/heartbeat.c:heartbeat_thread)
2004-03-11 14:42:12 [364] [8] DEBUG: Thread 8
(gw/heartbeat.c:heartbeat_thread) maps to pid 364.

What is wrong? I become the Info: "Did not find previous routing info for
WDP, generating new"
My Settings on my Mobilphone are:

IP-Address: 192.168.10.2 (PPP-Host-IP)
Homepage: http://192.168.10.2
Port: 9201

Thanks a lot!

SIEMENS        HVAC Products
Siemens Building Technologies AG 
Daniel Moos
Tel. direkt: +41 41 724 4076
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.