RE: m-notification-ind (cont.)

2002-07-10 Thread Anders Lindh 


Thanks for decoding the OTA message, that kinda solved the case. It
turned out that my content wasn't really formatted correctly (lesson
learned: Java Strings aren't suitable for storing any binary data). I
just managed to get a notification through to the phone (it informs that
content is being fetched). I still can't se an actual fetch at out web
server, but that's a completely other problem. 

Regards,

- Anders


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On Behalf Of Aarno Syvänen
 Sent: 10. heinäkuuta 2002 9:39
 To: [EMAIL PROTECTED]
 Cc: 'Stipe Tolj'; [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: m-notification-ind (cont.)
 
 
 Anders Lindh kirjoittaa tiistaina, 9. heinäkuuta 2002, kello 18:14:
  I have a couple of questions regarding the tokenization, as I still 
  haven't managed to get this working.
 
  --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--
 
  Should the encoded headers be posted to the PPG as mime encoded or 
  not? In the example I've attached below, stuff isn't 
 submitted as mime 
  encoded, which atleast looks ok.
 
 Note that Content-Type is application something, not text something. 
 This means
 that it indeed must be binary.
 
 
 
  84bc
 
  This is the content-type, so it should be last (7.0 in 
  MMSEncapsulation).
 
 I think this one should be removed. It is MIME part 
 Content-Type, and it 
 is similar in all
 MMS messages (even in notification having only headers !). Pi 
 should add 
 it.  WAP-209, 7 refers, I think, to content type of MMS 
 message itself.
 
 
  8c82
  9831323500
  8d90
  8a80
  8e0164
  880481020100
  83yout URI00
 
  Anyway, here's my MMSEncapsulated doc:
 
  8c 82
  // X-MMS-Message-Type: m-notification-ind
  98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00//
  X-MMS-Transaction-Id: [EMAIL PROTECTED]
  8d 90
  // X-MMS-Version: 1.0
  8a 80
  // X-MMS-Message-Class: Personal
  8e 01 64
  // X-MMS-Size: 100
  88 06 80 04 3d 2b 32 4a
  // X-MMS-Expiry: an Absolute value, in the future
  83 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65 
 2e 63 6f 
  6d 2f 00 // X-MMS-Content-Location: http://www.flyerone.com/ 84 be
  // Content-type: application/vnd.wap.mms-message
 
 OK, but see comment about Content-Type earlier
 
  Text part:
 
 Is you got SI and SL right, then WSP headers should be OK (at 
 least for 
 SI and SL, that
 is). But after that strange things appear. What is your transfer 
 encoding ? Is this the
 message wapbox is sending to bearerbox.
 
  0f
 Push Id
  06
 PDU type: Push
  0d
 Headers part length, in octets (13)
  be
 Content-Type:  application/vnd.wap.mms-message
  96 7f 00 a9 7f 00
 Host: localhost
  af 84
 X-WAP-Application-Id: mms.ua
  8d c1 b4 80
 Content-Length:
 
 So following must be notification, Is this really binary encoded ?
  3f 3f 3f 39 39 39 39 40
  66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00 3f 90
  3f 3f 3f 01 64 3f 06 3f 04 3d 2b 2f 4a 3f 68 74 74 70 3a 2f 
 2f 77 77 
  77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 2f 00 3f be
 
  udh:
  06 05 04 0b 84 23 f0
 
 I remember that got through SL and SI, so udh is at least right.
 
  I haven't yet been able to decode this message, so I'd like some 
  feedback if it even remotely looks like something that 
 could work, or 
  if there's some obious flaw.
 
 You can try to send a direct binary to the phone. Only 
 mandatory header in WSP part is Content-Type, but now you 
 must add X-Wap-Application-Id, so that the right application 
 would handle the request. So add before the binary MMS notification:
 
 0f 06 03 ce af 84
 
 Aarno

RE: m-notification-ind (cont.)

2002-07-10 Thread Anders Lindh 


Solved the fetch problem. I used my operators (Sonera) default MMS
settings, which uses a different wap gateway than their default one.
This gateway (surprise, surprise) seems to block requests to other
hosts.

- Anders

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]] On Behalf Of Anders Lindh
 Sent: 10. heinäkuuta 2002 17:57
 To: 'Aarno Syvänen'
 Cc: [EMAIL PROTECTED]
 Subject: RE: m-notification-ind (cont.)
 
 
 
 Thanks for decoding the OTA message, that kinda solved the 
 case. It turned out that my content wasn't really formatted 
 correctly (lesson
 learned: Java Strings aren't suitable for storing any binary 
 data). I just managed to get a notification through to the 
 phone (it informs that content is being fetched). I still 
 can't se an actual fetch at out web server, but that's a 
 completely other problem. 
 
 Regards,
 
 - Anders
 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]] On Behalf Of Aarno Syvänen
  Sent: 10. heinäkuuta 2002 9:39
  To: [EMAIL PROTECTED]
  Cc: 'Stipe Tolj'; [EMAIL PROTECTED]; [EMAIL PROTECTED]
  Subject: Re: m-notification-ind (cont.)
  
  
  Anders Lindh kirjoittaa tiistaina, 9. heinäkuuta 2002, kello 18:14:
   I have a couple of questions regarding the tokenization, 
 as I still
   haven't managed to get this working.
  
   --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--
  
   Should the encoded headers be posted to the PPG as mime encoded or
   not? In the example I've attached below, stuff isn't 
  submitted as mime
   encoded, which atleast looks ok.
  
  Note that Content-Type is application something, not text something.
  This means
  that it indeed must be binary.
  
  
  
   84bc
  
   This is the content-type, so it should be last (7.0 in
   MMSEncapsulation).
  
  I think this one should be removed. It is MIME part
  Content-Type, and it 
  is similar in all
  MMS messages (even in notification having only headers !). Pi 
  should add 
  it.  WAP-209, 7 refers, I think, to content type of MMS 
  message itself.
  
  
   8c82
   9831323500
   8d90
   8a80
   8e0164
   880481020100
   83yout URI00
  
   Anyway, here's my MMSEncapsulated doc:
  
   8c 82
   // X-MMS-Message-Type: m-notification-ind
   98 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00  //
   X-MMS-Transaction-Id: [EMAIL PROTECTED]
   8d 90
   // X-MMS-Version: 1.0
   8a 80
   // X-MMS-Message-Class: Personal
   8e 01 64
   // X-MMS-Size: 100
   88 06 80 04 3d 2b 32 4a
   // X-MMS-Expiry: an Absolute value, in the future
   83 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65
  2e 63 6f
   6d 2f 00 // X-MMS-Content-Location: 
 http://www.flyerone.com/ 84 be 
   // Content-type: application/vnd.wap.mms-message
  
  OK, but see comment about Content-Type earlier
  
   Text part:
  
  Is you got SI and SL right, then WSP headers should be OK (at
  least for 
  SI and SL, that
  is). But after that strange things appear. What is your transfer 
  encoding ? Is this the
  message wapbox is sending to bearerbox.
  
   0f
  Push Id
   06
  PDU type: Push
   0d
  Headers part length, in octets (13)
   be
  Content-Type:  application/vnd.wap.mms-message
   96 7f 00 a9 7f 00
  Host: localhost
   af 84
  X-WAP-Application-Id: mms.ua
   8d c1 b4 80
  Content-Length:
  
  So following must be notification, Is this really binary encoded ?
   3f 3f 3f 39 39 39 39 40
   66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00 3f 90
   3f 3f 3f 01 64 3f 06 3f 04 3d 2b 2f 4a 3f 68 74 74 70 3a 2f
  2f 77 77
   77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 2f 00 3f be
  
   udh:
   06 05 04 0b 84 23 f0
  
  I remember that got through SL and SI, so udh is at least right.
  
   I haven't yet been able to decode this message, so I'd like some
   feedback if it even remotely looks like something that 
  could work, or
   if there's some obious flaw.
  
  You can try to send a direct binary to the phone. Only
  mandatory header in WSP part is Content-Type, but now you 
  must add X-Wap-Application-Id, so that the right application 
  would handle the request. So add before the binary MMS notification:
  
  0f 06 03 ce af 84
  
  Aarno

Re: m-notification-ind (cont.)

2002-07-10 Thread Stipe Tolj 

Anders Lindh wrote:
 
 Solved the fetch problem. I used my operators (Sonera) default MMS
 settings, which uses a different wap gateway than their default one.
 This gateway (surprise, surprise) seems to block requests to other
 hosts.

yeahhh :)) they are usually sooo convinient :))

Stipe

[EMAIL PROTECTED]
---
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

Re: m-notification-ind (cont.)

2002-07-09 Thread Aarno Syvänen 

Anders Lindh kirjoittaa maanantaina, 8. heinäkuuta 2002, kello 13:52:Hi,

 I've been struggling with the PPG and m-notification-ind messages, but
 haven't been able to get the handset to react to the indication. There's
 probably something I'm missing, so I'd appreciate if someone could lend
 their eyes and check through the used material. The notification is
 received by the handset, but apparently silently ignored. No fetch is
 occuring at http://www.flyerone.com/.


 I submit this to the PPG:

 Headers:
 content-type: multipart/related; boundary=wFwKoCsDInFRxqmburDFMeqxu;
 type=application/xml
 x-wap-application-id: x-wap-application:mms.ui

This should be x-wap-application:mms.ua

 connection: keep-alive
 content-length: 656

 content:
 2002-07-08 13:28:34 [14] DEBUG:   data: 0d 0a 2d 2d 4b 62 66 66
 ..--Kbff
 2002-07-08 13:28:34 [14] DEBUG:   data: 51 73 46 51 69 5a 4f 6f
 QsFQiZOo
 2002-07-08 13:28:34 [14] DEBUG:   data: 66 6c 56 43 57 75 4a 46
 flVCWuJF
 2002-07-08 13:28:34 [14] DEBUG:   data: 65 63 46 76 52 0d 0a 43
 ecFvR..C
 2002-07-08 13:28:34 [14] DEBUG:   data: 6f 6e 74 65 6e 74 2d 74
 ontent-t
 2002-07-08 13:28:34 [14] DEBUG:   data: 79 70 65 3a 20 61 70 70   ype:
 app
 2002-07-08 13:28:34 [14] DEBUG:   data: 6c 69 63 61 74 69 6f 6e
 lication
 2002-07-08 13:28:34 [14] DEBUG:   data: 2f 78 6d 6c 0d 0a 3c 3f
 /xml..?
 2002-07-08 13:28:34 [14] DEBUG:   data: 78 6d 6c 20 76 65 72 73   xml
 vers
 2002-07-08 13:28:34 [14] DEBUG:   data: 69 6f 6e 3d 22 31 2e 30
 ion=1.0
 2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 65 6e 63 6f 64 69   
 encodi
 2002-07-08 13:28:34 [14] DEBUG:   data: 6e 67 3d 22 49 53 4f 2d
 ng=ISO-
 2002-07-08 13:28:34 [14] DEBUG:   data: 38 38 35 39 2d 31 22 3f
 8859-1?
 2002-07-08 13:28:34 [14] DEBUG:   data: 3e 0d 0a 3c 70 61 70 3e
 ..pap
 2002-07-08 13:28:34 [14] DEBUG:   data: 3c 70 75 73 68 2d 6d 65
 push-me
 2002-07-08 13:28:34 [14] DEBUG:   data: 73 73 61 67 65 20 70 75   ssage
 pu
 2002-07-08 13:28:34 [14] DEBUG:   data: 73 68 2d 69 64 3d 22 31
 sh-id=1
 2002-07-08 13:28:34 [14] DEBUG:   data: 32 33 34 40 66 6c 79 65
 234@flye
 2002-07-08 13:28:34 [14] DEBUG:   data: 72 6f 6e 65 2e 63 6f 6d
 rone.com
 2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 64 65 6c 69 76 65   
 delive
 2002-07-08 13:28:34 [14] DEBUG:   data: 72 2d 62 65 66 6f 72 65
 r-before
 2002-07-08 13:28:34 [14] DEBUG:   data: 2d 74 69 6d 65 73 74 61
 -timesta
 2002-07-08 13:28:34 [14] DEBUG:   data: 6d 70 3d 22 32 30 30 32
 mp=2002
 2002-07-08 13:28:34 [14] DEBUG:   data: 2d 30 37 2d 30 38 54 31
 -07-08T1
 2002-07-08 13:28:34 [14] DEBUG:   data: 30 3a 33 33 3a 33 32 5a
 0:33:32Z
 2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 64 65 6c 69 76 65   
 delive
 2002-07-08 13:28:34 [14] DEBUG:   data: 72 2d 61 66 74 65 72 2d
 r-after-
 2002-07-08 13:28:34 [14] DEBUG:   data: 74 69 6d 65 73 74 61 6d
 timestam
 2002-07-08 13:28:34 [14] DEBUG:   data: 70 3d 22 32 30 30 32 2d
 p=2002-
 2002-07-08 13:28:34 [14] DEBUG:   data: 30 37 2d 30 38 54 31 30
 07-08T10
 2002-07-08 13:28:34 [14] DEBUG:   data: 3a 32 38 3a 33 32 5a 22
 :28:32Z
 2002-07-08 13:28:34 [14] DEBUG:   data: 20 73 6f 75 72 63 65 2d
 source-
 2002-07-08 13:28:34 [14] DEBUG:   data: 72 65 66 65 72 65 6e 63
 referenc
 2002-07-08 13:28:34 [14] DEBUG:   data: 65 3d 22 46 6c 79 65 72
 e=Flyer
 2002-07-08 13:28:34 [14] DEBUG:   data: 4f 6e 65 20 4c 74 64 22   One
 Ltd
 2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 61 64 64 72 65 73
 addres
 2002-07-08 13:28:34 [14] DEBUG:   data: 73 20 61 64 64 72 65 73   s
 addres
 2002-07-08 13:28:34 [14] DEBUG:   data: 73 2d 76 61 6c 75 65 3d
 s-value=
 2002-07-08 13:28:34 [14] DEBUG:   data: 22 57 41 50 50 55 53 48
 WAPPUSH
 2002-07-08 13:28:34 [14] DEBUG:   data: 3d 2b 33 35 38 34 30 35
 =+358405
 2002-07-08 13:28:34 [14] DEBUG:   data: 31 33 34 32 36 35 2f 54
 134265/T
 2002-07-08 13:28:34 [14] DEBUG:   data: 59 50 45 3d 50 4c 4d 4e
 YPE=PLMN
 2002-07-08 13:28:34 [14] DEBUG:   data: 40 66 6c 79 65 72 6f 6e
 @flyeron
 2002-07-08 13:28:34 [14] DEBUG:   data: 65 2e 63 6f 6d 22 20 2f   e.com
 /
 2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 71 75 61 6c 69 74
 qualit
 2002-07-08 13:28:34 [14] DEBUG:   data: 79 2d 6f 66 2d 73 65 72
 y-of-ser
 2002-07-08 13:28:34 [14] DEBUG:   data: 76 69 63 65 20 70 72 69   vice
 pri
 2002-07-08 13:28:34 [14] DEBUG:   data: 6f 72 69 74 79 3d 22 6d
 ority=m
 2002-07-08 13:28:34 [14] DEBUG:   data: 65 64 69 75 6d 22 20 2f   edium
 /
 2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 2f 70 75 73 68 2d
 /push-
 2002-07-08 13:28:34 [14] DEBUG:   data: 6d 65 73 73 61 67 65 3e
 message
 2002-07-08 13:28:34 [14] DEBUG:   data: 3c 2f 70 61 70 3e 0d 0a
 /pap..
 2002-07-08 13:28:34 [14] DEBUG:   data: 0d 0a 2d 2d 4b 62 66 66
 ..--Kbff
 2002-07-08 13:28:34 [14] DEBUG:   data: 51 73 46 51 69 5a 4f 6f
 QsFQiZOo
 2002-07-08 13:28:34 [14] DEBUG:   data: 66 6c 56 43 57 75 4a 46
 flVCWuJF
 2002-07-08 13:28:34 [14] DEBUG:   data: 65 63 46 76 52 0d 0a 43
 ecFvR..C
 2002-07-08 13:28:34 [14] DEBUG:   data: 6f 6e 74 65 6e

Re: m-notification-ind (cont.)

2002-07-09 Thread Stipe Tolj 

Aarno,

you seem to be familiar with the MMS encoding, can you write a short
text file that contains a PPG request with a M.notification-ind and
the corresponding data hex representation, so we others can see how
the beasts look like. 

I have certain immagination, but yet it does not clear up for me in my
clouded head ;)

Stipe

[EMAIL PROTECTED]
---
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
---
wapme.net - wherever you are

m-notification-ind (cont.)

2002-07-08 Thread Anders Lindh 

Hi,

I've been struggling with the PPG and m-notification-ind messages, but
haven't been able to get the handset to react to the indication. There's
probably something I'm missing, so I'd appreciate if someone could lend
their eyes and check through the used material. The notification is
received by the handset, but apparently silently ignored. No fetch is
occuring at http://www.flyerone.com/. 


I submit this to the PPG:

Headers:
content-type: multipart/related; boundary=wFwKoCsDInFRxqmburDFMeqxu;
type=application/xml
x-wap-application-id: x-wap-application:mms.ui
connection: keep-alive
content-length: 656

content:
2002-07-08 13:28:34 [14] DEBUG:   data: 0d 0a 2d 2d 4b 62 66 66
..--Kbff
2002-07-08 13:28:34 [14] DEBUG:   data: 51 73 46 51 69 5a 4f 6f
QsFQiZOo
2002-07-08 13:28:34 [14] DEBUG:   data: 66 6c 56 43 57 75 4a 46
flVCWuJF
2002-07-08 13:28:34 [14] DEBUG:   data: 65 63 46 76 52 0d 0a 43
ecFvR..C
2002-07-08 13:28:34 [14] DEBUG:   data: 6f 6e 74 65 6e 74 2d 74
ontent-t
2002-07-08 13:28:34 [14] DEBUG:   data: 79 70 65 3a 20 61 70 70   ype:
app
2002-07-08 13:28:34 [14] DEBUG:   data: 6c 69 63 61 74 69 6f 6e
lication
2002-07-08 13:28:34 [14] DEBUG:   data: 2f 78 6d 6c 0d 0a 3c 3f
/xml..?
2002-07-08 13:28:34 [14] DEBUG:   data: 78 6d 6c 20 76 65 72 73   xml
vers
2002-07-08 13:28:34 [14] DEBUG:   data: 69 6f 6e 3d 22 31 2e 30
ion=1.0
2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 65 6e 63 6f 64 69   
encodi
2002-07-08 13:28:34 [14] DEBUG:   data: 6e 67 3d 22 49 53 4f 2d
ng=ISO-
2002-07-08 13:28:34 [14] DEBUG:   data: 38 38 35 39 2d 31 22 3f
8859-1?
2002-07-08 13:28:34 [14] DEBUG:   data: 3e 0d 0a 3c 70 61 70 3e
..pap
2002-07-08 13:28:34 [14] DEBUG:   data: 3c 70 75 73 68 2d 6d 65
push-me
2002-07-08 13:28:34 [14] DEBUG:   data: 73 73 61 67 65 20 70 75   ssage
pu
2002-07-08 13:28:34 [14] DEBUG:   data: 73 68 2d 69 64 3d 22 31
sh-id=1
2002-07-08 13:28:34 [14] DEBUG:   data: 32 33 34 40 66 6c 79 65
234@flye
2002-07-08 13:28:34 [14] DEBUG:   data: 72 6f 6e 65 2e 63 6f 6d
rone.com
2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 64 65 6c 69 76 65   
delive
2002-07-08 13:28:34 [14] DEBUG:   data: 72 2d 62 65 66 6f 72 65
r-before
2002-07-08 13:28:34 [14] DEBUG:   data: 2d 74 69 6d 65 73 74 61
-timesta
2002-07-08 13:28:34 [14] DEBUG:   data: 6d 70 3d 22 32 30 30 32
mp=2002
2002-07-08 13:28:34 [14] DEBUG:   data: 2d 30 37 2d 30 38 54 31
-07-08T1
2002-07-08 13:28:34 [14] DEBUG:   data: 30 3a 33 33 3a 33 32 5a
0:33:32Z
2002-07-08 13:28:34 [14] DEBUG:   data: 22 20 64 65 6c 69 76 65   
delive
2002-07-08 13:28:34 [14] DEBUG:   data: 72 2d 61 66 74 65 72 2d
r-after-
2002-07-08 13:28:34 [14] DEBUG:   data: 74 69 6d 65 73 74 61 6d
timestam
2002-07-08 13:28:34 [14] DEBUG:   data: 70 3d 22 32 30 30 32 2d
p=2002-
2002-07-08 13:28:34 [14] DEBUG:   data: 30 37 2d 30 38 54 31 30
07-08T10
2002-07-08 13:28:34 [14] DEBUG:   data: 3a 32 38 3a 33 32 5a 22
:28:32Z
2002-07-08 13:28:34 [14] DEBUG:   data: 20 73 6f 75 72 63 65 2d
source-
2002-07-08 13:28:34 [14] DEBUG:   data: 72 65 66 65 72 65 6e 63
referenc
2002-07-08 13:28:34 [14] DEBUG:   data: 65 3d 22 46 6c 79 65 72
e=Flyer
2002-07-08 13:28:34 [14] DEBUG:   data: 4f 6e 65 20 4c 74 64 22   One
Ltd
2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 61 64 64 72 65 73
addres
2002-07-08 13:28:34 [14] DEBUG:   data: 73 20 61 64 64 72 65 73   s
addres
2002-07-08 13:28:34 [14] DEBUG:   data: 73 2d 76 61 6c 75 65 3d
s-value=
2002-07-08 13:28:34 [14] DEBUG:   data: 22 57 41 50 50 55 53 48
WAPPUSH
2002-07-08 13:28:34 [14] DEBUG:   data: 3d 2b 33 35 38 34 30 35
=+358405
2002-07-08 13:28:34 [14] DEBUG:   data: 31 33 34 32 36 35 2f 54
134265/T
2002-07-08 13:28:34 [14] DEBUG:   data: 59 50 45 3d 50 4c 4d 4e
YPE=PLMN
2002-07-08 13:28:34 [14] DEBUG:   data: 40 66 6c 79 65 72 6f 6e
@flyeron
2002-07-08 13:28:34 [14] DEBUG:   data: 65 2e 63 6f 6d 22 20 2f   e.com
/
2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 71 75 61 6c 69 74
qualit
2002-07-08 13:28:34 [14] DEBUG:   data: 79 2d 6f 66 2d 73 65 72
y-of-ser
2002-07-08 13:28:34 [14] DEBUG:   data: 76 69 63 65 20 70 72 69   vice
pri
2002-07-08 13:28:34 [14] DEBUG:   data: 6f 72 69 74 79 3d 22 6d
ority=m
2002-07-08 13:28:34 [14] DEBUG:   data: 65 64 69 75 6d 22 20 2f   edium
/
2002-07-08 13:28:34 [14] DEBUG:   data: 3e 3c 2f 70 75 73 68 2d
/push-
2002-07-08 13:28:34 [14] DEBUG:   data: 6d 65 73 73 61 67 65 3e
message
2002-07-08 13:28:34 [14] DEBUG:   data: 3c 2f 70 61 70 3e 0d 0a
/pap..
2002-07-08 13:28:34 [14] DEBUG:   data: 0d 0a 2d 2d 4b 62 66 66
..--Kbff
2002-07-08 13:28:34 [14] DEBUG:   data: 51 73 46 51 69 5a 4f 6f
QsFQiZOo
2002-07-08 13:28:34 [14] DEBUG:   data: 66 6c 56 43 57 75 4a 46
flVCWuJF
2002-07-08 13:28:34 [14] DEBUG:   data: 65 63 46 76 52 0d 0a 43
ecFvR..C
2002-07-08 13:28:34 [14] DEBUG:   data: 6f 6e 74 65 6e 74 2d 74
ontent-t
2002-07-08 13:28:34 [14] DEBUG:   data: 79 70 65 3a 20 61 70 70   ype:
app
2002-07-08 13:28:34 [14] DEBUG:   data: 6c 69 63 61 74 69 6f 6e
lication
2002-07-08 13:28:34 [14] DEBUG:   data: 2f 76 6e 64 2e 77 61 70