WapKannel Configuration

[Ivone Uribe]

Thanks Mark for you reply!

I have the service available and I verify that the ports 9201 and 9202 are 
up.

I'm using a Motorola Iden cellphone that are connect by the port: 9203,
But, I don't get the handset access to the home-deck configurating my kannel 
server.
Where can I set this port as 9203?

Well, I wrote my wapkannel.conf like this:

group=core
admin-port=13000
wapbox-port=13003
#admin-password=bar
#status-password=foo
#admin-deny-ip=""
wdp-interface-name="127.24.249.36"  (the ip of my kannel server)
log-file="var/log/kannel/bearerbox.log"
log-level=0
#box-deny-ip="*.*.*.*"
box-allow-ip="*.*.*.*" (all)
acces-log="var/log/kannel/acces.log"

group=wapbox
bearer_host=localhost
#map_url="* *"
device-home="http://172.24.249.34/prueba.asp"; (the default page )
log-file="tmp/wapbox.log"
log-level=0
syslog-level=3

Could anybody give me any idea how to get a solution?

Best Regards,
Ivonne







_
MSN. Más Útil cada Día. http://www.msn.es/intmap/

Motorola V66i does not work with kannel

[Xuan Baldauf]

Hello,
I'm trying to get a Motorola V66i to work with kannel, but without success.
The kannel setup works correctly with fakewap. This shows in the "wapbox.log"
if I want to connect from a V66i over GPRS:
2002-10-11 21:53:41 [5] DEBUG: WTP: Created WTPRespMachine 0x80d8620
(11)
2002-10-11 21:53:41 [5] DEBUG: WTP: resp_machine 11, state LISTEN,
event RcvInvoke.
2002-10-11 21:53:41 [5] DEBUG: WTP 11: New state INVOKE_RESP_WAIT
2002-10-11 21:53:41 [1] DEBUG: WSP: Created WSPMachine 0x80d8408
2002-10-11 21:53:41 [1] DEBUG: WSP: machine 0x80d8408, state NULL_SESSION,
event TR-Invoke.ind
2002-10-11 21:53:41 [1] DEBUG: WSP: decoding headers:
2002-10-11 21:53:41 [1] DEBUG: Octet string at 0x80d85c0:
2002-10-11 21:53:41 [1] DEBUG:   len:  30
2002-10-11 21:53:41 [1] DEBUG:   size: 31
2002-10-11 21:53:41 [1] DEBUG:   immutable: 0
2002-10-11 21:53:41 [1] DEBUG:   data: 80 94 80 69 6d 61
67 65   ...image
2002-10-11 21:53:41 [1] DEBUG:   data: 2f 77 62 6d 70 00
80 a1   /wbmp...
2002-10-11 21:53:41 [1] DEBUG:   data: 80 9d 80 95 80 b4
80 ae   
2002-10-11 21:53:41 [1] DEBUG:   data: 80 b0 83 99 c3 93
..
2002-10-11 21:53:41 [1] DEBUG: Octet string dump ends.
2002-10-11 21:53:41 [1] WARNING: Did not expect short-integer with
'Encoding-Version' header, skipping.
2002-10-11 21:53:41 [1] WARNING: Skipping faulty header.
2002-10-11 21:53:41 [1] DEBUG: WSP: decoded headers:
2002-10-11 21:53:41 [1] DEBUG: Accept: application/vnd.wap.wmlc
2002-10-11 21:53:41 [1] DEBUG: Accept: image/wbmp
2002-10-11 21:53:41 [1] DEBUG: Accept: image/vnd.wap.wbmp
2002-10-11 21:53:41 [1] DEBUG: Accept: image/gif
2002-10-11 21:53:41 [1] DEBUG: Accept: application/vnd.wap.wmlscriptc
2002-10-11 21:53:41 [1] DEBUG: Accept: application/vnd.wap.sia
2002-10-11 21:53:41 [1] DEBUG: Accept: application/vnd.wap.sic
2002-10-11 21:53:41 [1] DEBUG: Accept: application/vnd.wap.slc
2002-10-11 21:53:41 [1] DEBUG: Accept-Language: en
2002-10-11 21:53:41 [1] DEBUG: WSP: End of decoded headers.
2002-10-11 21:53:41 [5] DEBUG: WTP: resp_machine 11, state INVOKE_RESP_WAIT,
event TR-Invoke.res.
2002-10-11 21:53:41 [5] DEBUG: WTP 11: New state RESULT_WAIT
2002-10-11 21:53:41 [1] DEBUG: WSP 5: New state CONNECTING
2002-10-11 21:53:41 [1] DEBUG: WSP: machine 0x80d8408, state CONNECTING,
event S-Connect.res
2002-10-11 21:53:41 [5] DEBUG: WTP: resp_machine 11, state RESULT_WAIT,
event TR-Result.req.
2002-10-11 21:53:41 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:53:41 [1] DEBUG: WSP 5: New state CONNECTING_2
2002-10-11 21:53:48 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:53:48 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:53:48 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:53:55 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:53:55 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:53:55 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:01 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event RcvInvoke.
2002-10-11 21:54:01 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:02 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:02 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:02 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:09 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:09 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:09 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:16 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:16 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:16 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:21 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event RcvInvoke.
2002-10-11 21:54:21 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:23 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:23 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:23 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:30 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:30 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:30 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:37 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:37 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:37 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:41 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event RcvInvoke.
2002-10-11 21:54:41 [5] DEBUG: WTP 11: New state RESULT_RESP_WAIT
2002-10-11 21:54:44 [4] DEBUG: Timeout-R elapsed.
2002-10-11 21:54:44 [5] DEBUG: WTP: resp_machine 11, state RESULT_RESP_WAIT,
event Timeout-R.
2002-10-11 21:54:44 [5] DEBUG: WTP 11: New state LISTEN
2002-10-11 21:54:44 [5] DEBUG: WTP: Destroying WTPRespMachine 0x80d8620
(11)
2002-10-11 21:54:44 [1] DEBUG: WSP: machine 

Re: test_ppg - current status?

[Aarno Syvänen]

On Friday, October 11, 2002, at 05:58 PM, <[EMAIL PROTECTED]> wrote:

> Yippee! test_ppg works now, thanks very much.
> Now the real questions start ;-)
>
> 1. Is there a dependancy on running the test server on port 8080? I  
> changed the ppg-port in group = ppg to 8086, started the  
> test_http_server with -p 8086 but got the original xml parse error.  
> When I set these back to 8080 it works again. Did I miss something?

You have ppg server, kannel and http server kannel forwards push  
requests. Ppg is
a http server, too. Ppg-port is port where ppg is listening.  
Test_http_server's p option
defines port http server is listening. Your error message is strange,  
however; you
should get address already in use.

> 2. I use resin on the same machine on port 8080. Can I configure resin  
> to do the same job as the test_http_server?

Kannel http smsc has a configuration variable send-url. Kannel relays  
http requests
to this url. So only thing you must do is to change the send-url.

> 3. How do I do it for "real"? What I mean is, I have a web-interface  
> to both sendsms and sendota which passes the xml docs to sendota or  
> the payloads to sendsms. I now would like the same for wap push, sort  
> of like  
> http://localhost:8080/http://localhost:8080/cgi-bin/wap- 
> push.cgi?username=foo&password=bar&content=content.xml&control=control. 
> xml (i.e. the test_ppg command line expressed as a a url).

I presume you are sending SI or SL. They are normal binary SMs, only  
special thing
is the udh; you must tell the phone the port handling the message:

udh=%06%05%04%0b%84%23%f0

If you send sms yourself you should configure smsc accordingly.

>
> Thanks again for a great job.

You are wellcome.

Aarno

wap kannel configuration

[Ivone Uribe]

Hi all!

I'm not clear about map-url, map-url-max and device-home descriptions for 
wapbox configuration.
So, Please could anybody contribute any sample configuration for wapbox.conf 
with these points.

I would be grateful of any contribution.

Regards,
Ivonne :)



_
Únase al mayor servicio mundial de correo electrónico: 
http://www.hotmail.com/es

RE: Falcom GSM MODEM Support

[Oded Arbel]

It could be a modem problem or a sim problem - but I think its the later. have you 
tried sending a message with this sim using a phone ? have you tried to send a simple 
7bit text message through the modem ?

--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]

+972-9-9581711 (116)
+972-67-340014

::..
Rules for Academic Deans:
(1)  HIDE
(2)  If they find you, LIE
-- Father Damian C. Fandal



> -Original Message-
> From: Ion Amigdalou [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, October 13, 2002 10:47 PM
> To: [EMAIL PROTECTED]
> Subject: Falcom GSM MODEM Support
> 
> 
> Hi.
> I have a Falcom Modem A2D but I can not send an sms
> message since when the ^Z character is inserted after
> a PDU submit, the modem replies with >ERROR.
> Is there any workaround? Has anyone on the list used
> successfully a Falcom Modem?
> 
> Regards,
> Tim
> 
> __
> Do you Yahoo!?
> Faith Hill - Exclusive Performances, Videos & More
> http://faith.yahoo.com
> 
>