Content adaptation - GIF/JPEG

Content adaptation - GIF/JPEG SearchSearch
Author Message
Petr
Posted on Tuesday, October 07, 2003 - 04:48 pm:   

We are using wap multimedia message to deliver pictures to mobile phones, but we have problems with JPEG images, because exp. Samsung SGHS-300m doesn't support JPEG images in WAP mode (in MMS yes). We prepared UAProf XML file for this phone (Samsung doesn't support this features in HTTP request) and set this XML file to UAMAP.INI. I think this file is used correctly because NowSMS reduce size of images to correct value. But NowSMS doesn't convert JPEG to GIF (in XML file is only tag for image/gif not for image/jpeg) and when I directly send GIF image to phone - in WML file is as thumbnail (small) image in JPEG format not GIF and big image is GIF. When I set in XML file that this phone supports only WBMP image - small image and big image are both in correct WBMP format with correct MIME types (only with .jpg extension). NowSMS supports only GIF->JPEG conversion?
Bryce Norwood - NowSMS Support
Posted on Tuesday, October 07, 2003 - 05:08 pm:   

Petr,

I'd like to see an MMSCDEBUG.LOG for the phone retrieving your content.

Please manually edit MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Then restart the MMSC service.

Repeat your attempt, and either e-mail the MMSCDEBUG.LOG to nowsms@now.co.uk, or post the relevant bits here.

-bn
Petr
Posted on Wednesday, October 08, 2003 - 11:48 am:   

Hi Bryce,

thanks for your tip - DEBUG was very helpfull. It is simple: SGHS-300m sends in http header path to UAprof for Samsung V-200 (http://wap.samsungmobile.com/uaprof/V200_00.xml)!!! In HTTP_ACCEPT mobile doesn't send image/jpeg mime type (it is true, it doesn't support it in WAP session), but UAProf for V-200 has in WAP section image/jpeg mime type. That's the problem. When I delete image/jpeg mime type from XML, JPEG is correctly transformed to GIF, NowSMS works good. Due Samsung mistake is in this case my S300 profile in UAMAP.INI unuseable, UAPROF.INI is first.
Bryce Norwood - NowSMS Support
Posted on Wednesday, October 08, 2003 - 05:21 pm:   

Petr,

I'm glad that pointed to a solution. We've had considerable debates internally on this issue. Right now we look at both the UAProf and the "Accept:" header on the WAP content requests.

I'd normally be inclined to think that the "Accept:" header would be more accurate. However, we have observed corrupt "Accept:" headers from a number of WAP gateways, so we didn't want to rely on that alone.

-bn