Dear Mesbahuddin,
the reason for running own WAP proxy is, that phone operator abandoned his WAP
proxy due low traffic (cutting costs?).
Patrick
______________________________________________________________
Od: "Mesbahuddin Malik" <[email protected]>
Komu: [email protected]
Datum: 03.01.2026 19:03
Předmět: Re: WAP setup issue
Hello ,Why are u trying WAP as that is obsolete. I have a good experience on
kannel long ago .Can u tell me the reason for using
WAP?RegardsMesbahwhatsapp(+8801833055942)
On Sat, Jan 3, 2026 at 11:27 PM <[email protected] <[email protected]>>
wrote:Hi list, happy New Year 2026.
I'am trying run application wapbox (as proxy for WAP 1.x cell phone) on
workstation (Debian). As other users:
https://www.kannel.org/pipermail/users/2009-February/005691.html
<https://www.kannel.org/pipermail/users/2009-February/005691.html>
https://www.kannel.org/pipermail/users/2013-November/020515.html
<https://www.kannel.org/pipermail/users/2013-November/020515.html>
https://www.kannel.org/pipermail/users/2019-June/023913.html
<https://www.kannel.org/pipermail/users/2019-June/023913.html>
I found some issues with running it.
The application runs as "service" (deb package from repo) and is managed by "kannel.conf"
file. I didn't find "wapkannel.conf" file mentioned in documentation.
My "kannel.conf" is something like:
group = core
admin-port = 9199
admin-password = bar
admin-deny-ip = "*.*.*.*"
admin-allow-ip = "127.0.0.1"
wapbox-port = 9200
wdp-interface-name = "127.0.0.1"
log-file = "/var/log/kannel/bearerbox.log"
box-deny-ip = "*.*.*.*"
box-allow-ip = "127.0.0.1"
group = wapbox
bearerbox-host = 127.0.0.1
http-interface-name = wlo1
log-file = "/home/user/Desktop/wapbox.log"
access-log = "/home/user/Desktop/wapaccess.log"
Some debug content:
$ bearerbox -v 0 kannel.conf
create log
[0] ERROR: Couldn't open logfile `/var/log/kannel/bearerbox.log'.
[0] ERROR: System error 13: Permission denied
[0] INFO: HTTP: Opening server at port 9199.
[0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)
[1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 5060.
[0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)
[0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run)
[3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 5060.
[0] DEBUG: starting UDP sender/receiver module
[2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 5060.
[2] DEBUG: HTTP: Including port 9199, fd 8 for polling in server thread
[0] INFO: Adding interface 127.0.0.1
[0] DEBUG: udpc_create: Bound to UDP <127.0.0.1:9200 <http://127.0.0.1:9200>>
[0] DEBUG: Started thread 4 (gw/bb_udp.c:udp_receiver)
[0] DEBUG: Started thread 5 (gw/bb_udp.c:udp_sender)
[5] DEBUG: Thread 5 (gw/bb_udp.c:udp_sender) maps to pid 5060.
[0] DEBUG: udpc_create: Bound to UDP <127.0.0.1:9201 <http://127.0.0.1:9201>>
[4] DEBUG: Thread 4 (gw/bb_udp.c:udp_receiver) maps to pid 5060.
[0] DEBUG: Started thread 6 (gw/bb_udp.c:udp_receiver)
[6] DEBUG: Thread 6 (gw/bb_udp.c:udp_receiver) maps to pid 5060.
[0] DEBUG: Started thread 7 (gw/bb_udp.c:udp_sender)
[7] DEBUG: Thread 7 (gw/bb_udp.c:udp_sender) maps to pid 5060.
[0] DEBUG: starting wapbox connection module
[0] DEBUG: Started thread 8 (gw/bb_boxc.c:wdp_to_wapboxes)
[8] DEBUG: Thread 8 (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 5060.
[0] DEBUG: Started thread 9 (gw/bb_boxc.c:wapboxc_run)
[0] DEBUG: starting WDP router
[9] DEBUG: Thread 9 (gw/bb_boxc.c:wapboxc_run) maps to pid 5060.
[0] DEBUG: Started thread 10 (gw/bearerbox.c:wdp_router)
[0] INFO: ----------------------------------------
[0] INFO: Kannel bearerbox II version 1.4.5 starting
[0] INFO: MAIN: Start-up done, entering mainloop
[10] DEBUG: Thread 10 (gw/bearerbox.c:wdp_router) maps to pid 5060.
$ netstat -a | grep 9200
tcp 0 0 0.0.0.0:9200 <http://0.0.0.0:9200> 0.0.0.0:*
LISTEN
udp 0 0 localhost:9200 0.0.0.0:*
bearerbox log says (get status):
connection to port 9199:
[2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.
[2] DEBUG: HTTP: Created HTTPClient area 0x702258000fe0.
[3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
[1] DEBUG: Timeout for fd:36 appears.
[1] DEBUG: HTTP: Destroying HTTPClient area 0x702258000fe0.
[1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'.
status:
Status: running, uptime 0d 0h 0m 53s
WDP: received 0 (0 queued), sent 0 (0 queued)
SMS: received 0 (0 queued), sent 0 (0 queued), store size -1
SMS: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec
DLR: received 0, sent 0
DLR: inbound (0.00,0.00,0.00) msg/sec, outbound (0.00,0.00,0.00) msg/sec
DLR: 0 queued, using internal storage
Box connections:
wapbox, IP 127.0.0.1 (on-line 0d 0h 0m 52s)
No SMSC connections
connection to port 9200 ("waiting for localhost"):
[9] INFO: Client connected from <127.0.0.1>
[9] DEBUG: Started thread 13 (gw/bb_boxc.c:function)
[13] DEBUG: Thread 13 (gw/bb_boxc.c:function) maps to pid 6158.
[13] DEBUG: setting up systems for new wapbox
[13] DEBUG: Started thread 14 (gw/bb_boxc.c:boxc_sender)
[14] DEBUG: Thread 14 (gw/bb_boxc.c:boxc_sender) maps to pid 6158.
...but no proxyiing at all. Connection (cellphone) from outside doesn't reach
wapbox (no log). May anybody help me run this? It looks like setup mistake.
Thanks.
Patrick K
