Re: problems with map-url of while executing wapbox

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization The Kannel Group
Message-ID <[email protected]>
Jayabharathi wrote:

> Hi,
> 
> I am using Kannel wap gateway for testing my MMS client.
> 
> For this I have installed Kannel gateway in a PC(IP address =  107.108.72.208)
> 
> 
> My test setup is like this
> 
> 
> MMS Client         <--------------------->    Kannel WAP GW     <------------------------> Now SMS/MMS (MMSC) 
> 
> 
> The config file contains the following,
> 
> group = core
> admin-port = 13000
> wapbox-port = 13002
> admin-password = bar
> wdp-interface-name = "*"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "127.0.0.1;107.108.72.207;107.108.72.14"
> 
> group = wapbox
> bearerbox-host = localhost
> log-file = "/tmp/wapbox.log"
> log-level = 1
> syslog-level = none
> http-interface-name = "107.108.72.14"
> map-url = "http://www.w3.org/* http://107.108.72.14/*"
> 
> 
> where in 107.108.72.14, My MMSC is running.
> 
> When I send a MMS message, the wap gateway is able to decode the message, started forming the http request and it fails in it.
> 
> the dump of the operation is attached to the mail.
> 
> Pls reply where am I doing wrong?

hmm, first of all your are using the 'http-interface-name' config directive 
wrong. This is intended for specify'ing the interface on your *local* machine 
which should be used for HTTP client requests. As far as I understand, this is a 
remote (mmsc) machine. So remove that line.

The 'map-url' seems ok to me. Just tried this for the distribution 
gw/wapkannel.conf adding one map-url statement to wapbox, producing:

...
2005-02-10 13:07:11 [4028] [6] INFO: Fetching <http://www.foobar.com/xy>
2005-02-10 13:07:11 [4028] [6] DEBUG: WSP: Mapping url <http://www.foobar.com/xy>
2005-02-10 13:07:11 [4028] [6] DEBUG: WSP: Matching <http://www.foobar.com/> 
with <http://www.foobar.com/>
2005-02-10 13:07:11 [4028] [6] DEBUG: WSP: URL Rewriten from 
<http://www.foobar.com/xy> to <http://wap.web.de/xy>
2005-02-10 13:07:11 [4028] [1] DEBUG: WSP: machine 0x10114790, state CONNECTED, 
event S-MethodInvoke.res
2005-02-10 13:07:11 [4028] [1] DEBUG: WSP: method 1, state REQUESTING, event 
S-MethodInvoke.res
2005-02-10 13:07:11 [4028] [1] DEBUG: WSP 0/1: New method state PROCESSING
2005-02-10 13:07:11 [4028] [1] DEBUG: WSP 0: New state CONNECTED
2005-02-10 13:07:11 [4028] [5] DEBUG: WTP: resp_machine 1, state 
INVOKE_RESP_WAIT, event TR-Invoke.res.
2005-02-10 13:07:11 [4028] [5] DEBUG: WTP 1: New state RESULT_WAIT
2005-02-10 13:07:11 [4028] [6] DEBUG: Started thread 9 (gwlib/fdset.c:poller)
2005-02-10 13:07:11 [4028] [9] DEBUG: Thread 9 (gwlib/fdset.c:poller) maps to 
pid 4028.
2005-02-10 13:07:11 [4028] [6] DEBUG: Started thread 10 
(gwlib/http.c:write_request_thread)
2005-02-10 13:07:11 [4028] [10] DEBUG: Thread 10 
(gwlib/http.c:write_request_thread) maps to pid 4028.
2005-02-10 13:07:11 [4028] [10] DEBUG: Parsing URL `http://wap.web.de/xy':
2005-02-10 13:07:11 [4028] [10] DEBUG:   Scheme: http://
2005-02-10 13:07:11 [4028] [10] DEBUG:   Host: wap.web.de
2005-02-10 13:07:11 [4028] [10] DEBUG:   Port: 80
2005-02-10 13:07:11 [4028] [10] DEBUG:   Username: (null)
2005-02-10 13:07:11 [4028] [10] DEBUG:   Password: (null)
2005-02-10 13:07:11 [4028] [10] DEBUG:   Path: /xy
2005-02-10 13:07:11 [4028] [10] DEBUG:   Query: (null)
2005-02-10 13:07:11 [4028] [10] DEBUG:   Fragment: (null)
2005-02-10 13:07:11 [4028] [10] DEBUG: HTTP: Opening connection to 
`wap.web.de:80' (fd=29).
...

which version of Kannel are you using?

 From your log, it looks like the WSP layer "doesn't see" the HTTP URL itself. 
Did you modify any Kannel WSP code internally?

Stipe

mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------
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.