Re: test_ppg problem

Hi,

On Friday, May 2, 2003, at 01:01 PM, Shridhar Raju wrote:

>
> Thanks Stipe & Aarno,
>
> As per your suggestion
>
> (Decoded MMS.txt)
> --asdlfjiuvwghasf
> Content-Type: application/vnd.wap.mms-message
> X-MMS-Message-Type: m-notification-ind
> X-MMS-Transaction-Id: 125
> X-MMS-Version: 1.0
> X-MMS-Message-Class: personal
> X-MMS-Message-Size: 100
> X-MMS-Expiry:  256; type=relative
> X-MMS-Content-Location: your URI
> --asdlfjiuvwghasf--

This seems to be ok, though expiry is only few minutes.

>
> (Encoded File MMS.txt, as seen in VIM editor)
> <8c><82><98>^A^B^E^@<8d><90><8a><80><8e>^Ad<88>^D<81>^B^A^@<83>http:// 
> www.fl
> yerone.com/ 
> ^@<84>¼<8c><82><98>^A^B^E^@<8d><90><8a><80><8e>^Ad<88>^D<81>^B^A
> ^@<83>htp://www.flyerone.com/ 
> ^@<8c><82><98>^A^B^E^@<8d><90><8a><80><8e>^Ad<8
> 8>^D<81>^B^A^@<83>http://www.flyerone.com/^@

You have it there, for some reasons, three times ;) (Perhaps you should  
say >> instead of > ?)

>
> Now the access.log shows
>
> 2003-05-02 14:36:25 Sent SMS [SMSC:FAKE] [SVC:] [ACT:] [from:1234]
> [to:+919848444808] [flags:0:2:0:0:0]
> [msg:123:00061ABE963139322E3136382E302E32333A3830383000AF848DDEB4808C82 
> 98010
> 205008D908A808E016488048102010083687474703A2F2F7777772E666C7965726F6E65 
> 2E636
> F6D2F0084BC8C8298010205008D908A808E016488048102010083687474703A2F2F7777 
> 772E6
> 66C7965726F6E652E636F6D2F00] [udh:7:0605040B8423F0]

You know, of course, that fake smsc is used only for testing purposes.  
You cannot really send anything
to anywhere with it.

>
> But if I don't include "Content Type: application/vnd.wap.mms-message"

You should, but it is http header, not mms header (it tells to the  
phone that the binary junk it is receiving is
actually a tokenized document.). But test_ppg does this for you.

>
> Access.log shows
>
> 2003-05-02 14:39:21 Sent SMS [SMSC:FAKE] [SVC:] [ACT:] [from:1234]
> [to:+919848444808] [flags:0:2:0:0:0]
> [msg:128:01061BBE963139322E3136382E302E32333A3830383000AF848D018CB4808C 
> 82980
> 10205008D908A808E016488048102010083687474703A2F2F7777772E666C7965726F6E 
> 652E6
> 36F6D2F0084BC8C8298010205008D908A808E016488048102010083687474703A2F2F77 
> 77772
> E666C7965726F6E652E636F6D2F008C829801]  
> [udh:12:0B05040B8423F00003010201]
> 2003-05-02 14:39:21 Sent SMS [SMSC:FAKE] [SVC:] [ACT:] [from:1234]
> [to:+919848444808] [flags:0:2:0:0:0]
> [msg:42:0205008D908A808E016488048102010083687474703A2F2F7777772E666C796 
> 5726F
> 6E652E636F6D2F00] [udh:12:0B05040B8423F00003010202]
>
> Which of the MMS header should be followed.

Content-Type: application/vnd.wap.mms-message and  
X-WAP-Application-Id:mms.ua are http headers
used for mms. Test_ppg adds them, if you use mms sending options.

>
> And regarding the WSP header, can some body point me to the right  
> resouces
> for further help.
>
> 01061BBE963139322E3136382E302E32333A3830383000AF848D018CB480
>
> 01 - ID

yep, push-id (identification of the push message)

> 06 - SL

No, this means pdu-type = unconfirmed push

> 1B - Len

Yeah, *headers* length.

> BE

Content-Type: application/vnd.wap.mms-message (though tokenized form  
causes p roblems with
Siemens S55, as it actually should)

> 963139322E3136382E302E32333A3830383000

Host: 192.168.0.23:8080. This should be dropped, even though it does  
not cause problems.

> AF84

X-WAP-Application-Id:mms.ua. This tells the phone, what application  
should handle the message.
(Both normal push and mms go to the push port).

> 8D018C

Content-Length: 140

> B480 - ????????

Push-Flag: 0. This is nice: 0 is 'reserved'. So this does work, but  
this should be dropprd anyway.

  (I will fix bugs mentioned in the next commit )

You will find content-types in http://www.wapforum.org/wina, Headers in  
wap-230, appendix A.
Chapter 8.2.4.1 in 230 is about Push pdus.

Aarno