Re: Bug in wsp_server_method_states.def

Hi, all

It is funny, but problem was discussed already in list:
http://www.mail-archive.com/[email protected]/msg02191.html

And we got +1 from Stipe already for fixing this!


Paul Keogh wrote:
>>hmm, did you use a specific handset for this where it corrupts?!
>>
> 
> 
> I don't believe it is handset specific.
> 
> 
>>This thing works for me with various devices and does not 
>>corrupt MMS messages. 
>>Can you explain a bit more in details, please?!
> 
> 
> Sure. The MM1 M-Send.req is carried by a WSP POST request which is
> issued by the device. The MMS message is WBXML encoded, so its quite
> possible
> that the last byte of this encoding is 0x00, depending on what the user
> has put into the MMS message. 
> 
> The offending code in wsp_server_method_states.def looks at the last
> byte
> of the POST data and truncates it if it is == 0x00. So the MMS message
> gets truncated and hence corrupted. I've done a round trip test against
> an MMSC and the test fails with the code in and succeeds with it out.
> 
> Anyway, regardless of the scenario, does it make any sense that the WSP
> layer chops off the last byte of its POST data just because it is ==
> 0x00 ?
> 
> No, of course it does'nt.
> 
> 


-- 
Vjacheslav Chekushin                                mailto:[email protected]
Latvian Mobile Phone Company                        http://www.lmt.lv
VAS Technologies Division                           +371 7773436
                                                     +371 9248284 (mobile)