Re: Query on last wsp_headers.c patch
Paul Keogh wrote: > > Hi Stipe, > > Could you give us some details on the last wsp_headers.c patch ? > > cvs diff -r 1.4 wsp_headers.c (in directory D:\dev\gateway\wap\) > Index: wsp_headers.c > === > RCS file: /home/cvs/gateway/wap/wsp_headers.c,v > retrieving revision 1.4 > retrieving revision 1.5 > diff -r1.4 -r1.5 > 2848a2849 > > octstr_append_char(packed, 0X01); > > What exactly does the 0x01 value represent here ? 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. [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: Query on last wsp_headers.c patch
> 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 0x01Transaction Id (S-Unit-MethodInvoke.req::Transaction Id) variable 0x06Type: Push 0x07Header Len: 7 0xBEContent Type application/vnd.wap.mms-message 0x8DHeader Field Name: Content Length 0x02Header Field Length 0x00, 0x68 Length of Content (of MMS Not.): 0x68=104 0xAFHeader Field Name: X-WAP-Application-Id 0x84Value ... MMS Headers ... How does this match with the byte encoding for your WSP headers for the MMS notification ?
Re: Query on last wsp_headers.c patch
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 > > 0x01Transaction Id (S-Unit-MethodInvoke.req::Transaction Id) variable > 0x06Type: Push > 0x07Header Len: 7 > 0xBEContent Type application/vnd.wap.mms-message > 0x8DHeader Field Name: Content Length > 0x02Header Field Length > 0x00, 0x68 Length of Content (of MMS Not.): 0x68=104 > 0xAFHeader Field Name: X-WAP-Application-Id > 0x84Value > ... > 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
