Paul Keogh wrote: > > > we discovered this while figuring out why MMS notifications haven't > > been working when using PPG to send the content. > > > > This push WSP headers must have the Content-type header as the first > > byte in the headers group. > > > > The 0x01 means "the length of the Content-type header", so 1 bytes > > follows. And then the encoding of the WSP cotent-type itself. > > > > Here's a WSP header decode that I got from an MMSC notification > server. The content type is encoded as > > 0x01 Transaction Id (S-Unit-MethodInvoke.req::Transaction Id) � variable > 0x06 Type: Push > 0x07 Header Len: 7 > 0xBE Content Type application/vnd.wap.mms-message > 0x8D Header Field Name: Content Length > 0x02 Header Field Length > 0x00, 0x68 Length of Content (of MMS Not.): 0x68=104 > 0xAF Header Field Name: X-WAP-Application-Id > 0x84 Value > ... > MMS Headers > ... > > How does this match with the byte encoding for your WSP headers > for the MMS notification ?
maybe Aarno may quote on this. At least we have seen that after injecting the byte the PPG send MMS notification have been working with both t68i and n7650, and previously not. 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
