Image Resizing with MMS WAP Push

Image Resizing with MMS WAP Push SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Image Resizing with MMS WAP Push « Previous || Next »
Author Message
Unregistered guest
Posted on Sunday, December 28, 2003 - 05:06 pm:   

I have downloaded the trial version of nowsms v.5 and everything seems fine. I am using the MMS Wap Push feature and it fits my requirements.

The problem is with the resize issue. I have downloaded the UAProf for my Nokia3650 and NowSMS seems to take the device screen size from the the N3650r100.xml document, but when converting to the nokia screen size it saves the converted jpg file to the C:\PROGRA~1\NowSMS\MMSCDATA\TEMP\Xmas3.jpg folder and sends the original file (C:\PROGRA~1\NowSMS\MMSCDATA\20031228\20\6900AADD\Xmas3.jpg) instead of the file that is converted. Any clues as to why?

Here's a portion of the MMSCDebug.log

20:31:18:600 [6] GetImageAttributes: C:\PROGRA~1\NowSMS\ImageBin\identify.exe -format "%wx%h" C:\PROGRA~1\NowSMS\MMSCDATA\20031228\20\6900AADD\Xmas3.jpg
20:31:18:671 [6] GetImageAttributes: 350x263

20:31:18:671 [6] ConvertWAPContentFileForUAProf: Xmas3.jpg Image attributes 350 x 263
20:31:18:671 [6] ConvertImage: C:\PROGRA~1\NowSMS\ImageBin\convert.exe C:\PROGRA~1\NowSMS\MMSCDATA\20031228\20\6900AADD\Xmas3.jpg -resize 176x208 C:\PROGRA~1\NowSMS\MMSCDATA\TEMP\Xmas3.jpg
20:31:18:831 [6] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\20031228\20\6900AADD\Xmas3.jpg
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1475
Registered: 10-2002
Posted on Wednesday, December 31, 2003 - 05:43 pm:   

Hi Osborne,

I ran some tests here, and it is normal for the "Sending" line to reference the wrong filename in the mmscdebug.log.

However, you should also see two lines like this:

13:30:24:918 [6] ConvertWAPContentFileForUAProf: Image chexbig.jpg too large (720x486), resized to fit in 176x208
13:30:24:918 [6] ConvertWAPContentFileForUAProf: WAP Content file size before conversion: 68404 bytes, after conversion: 5969 bytes

If you don't see that file size before/after conversion line, then I would be suspicious that no conversion is actually taking place.

Do you see these other lines in your mmscdebug.log?
Unregistered guest
Posted on Saturday, January 03, 2004 - 08:45 am:   

Hi Bryce,

Thank you for replying.

Unfortunately those two lines do not appear in my mmscdebug.log which means that the conversion is not taking place. Another confirmation is that when I see the image on my Nokia3650 the image appears fine (this is due to the device feature)but image details option reports the original size of the image with original dimentions (w X h), hence the image being sent is the original image but not the converted one.

Another problem that I faced was that I had to manually download the UAProf file for Nokia3650 although its mentioned on this discussion forum that when a device connects to the nowsms server, the server automatically downloads the UAProf for the requesting device.

Hoping to find a solution for the resize issue and the UAProf download issue.

Unregistered guest
Posted on Saturday, January 03, 2004 - 09:02 am:   

Just wanted you to know that the UAProf file is C:\PROGRA~1\NowSMS\UAPROF\N3650r100.xml

This is the contents of the UAMAP.ini file:

The last entry was manually recorded.

Hope this is not the cause of the image non-coversion
Unregistered guest
Posted on Saturday, January 03, 2004 - 09:17 am:   

Hi Bryce,

This is the contents of the 6900AADD.WML file:

<?xml version="1.0" encoding="utf-8"?>
<card title="Multimedia Message">
<img src="/20031228/20/6900AADD/Xmas3-1-small.jpg" alt="Image"/>
<a href="/20031228/20/6900AADD/Xmas3.jpg">Download image Xmas3.jpg</a>

Here it is clear that the wml file is created with a wml tag <a href> that is pointing to the original image file instead of C:\PROGRA~1\NowSMS\MMSCDATA\TEMP\Xmas3.jpg, which does not exits.

FYI: C:\PROGRA~1\NowSMS\MMSCDATA\TEMP\ folder does not exists.

Is this folder created and then deleted after conversion?

Unregistered guest
Posted on Monday, January 05, 2004 - 11:12 am:   

Hi Bryce,

RESIZE Working !

All I had to do was create a folder TEMP under MMSCDATA folder. For some reason the folder is not created after the software installation V5.0

UAProf files being downloaded automatically ... has not been solved ... I will have to get in another device model to conduct some tests, if you have any answers ... please throw them in my direction.

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1505
Registered: 10-2002
Posted on Monday, January 05, 2004 - 02:59 pm:   

Hi Osborne,

That is EXCELLENT detective work. I don't think I would have figured that out.

But I can see that there is a problem that this TEMP directory is automatically created by content conversion that is performed on MMS files, but it is not automatically created for the multimedia push.

The directory doesn't get deleted, so creating it will do the trick.

For the UAProf files, is there a chance that you're on Vodafone in the UK? There is a problem that Vodafone's WAP gateway does not pass through the device "Profile:" header. The "Profile:" header contains the URL for the UAProf file.

It's in a hex dump in the MMSCDEBUG.LOG ... but you should see the headers coming in on the request in that information. Do you see a "Profile:" header?
Frank Xiong
New member
Username: Chunyunx

Post Number: 10
Registered: 01-2004
Posted on Thursday, February 19, 2004 - 06:18 am:   

I have a question about this image resizing procedure, before resizing, should MMSC judge user agent then use UAprof to finish this procedure?

Thanks for reply in advance
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1938
Registered: 10-2002
Posted on Saturday, February 21, 2004 - 02:51 am:   

I can't speak for all, but our MMSC does.

I should point out that this particular thread is not really about MMS. It is about a function in our Now SMS/MMS Gateway which reformats MMS messages as a WAP push with links to the multimedia objects.

When those objects are retrieved, the UAProf for the client is decided if the content needs to be reformatted.

We do similar things with MMS messages received from the MMSC.
Posted on Friday, March 26, 2004 - 09:12 pm:   

I have been having this problem of UAPROFILE not being downloaded automatically as well when I upgraded to 5.0 from 4.x, has this been solved?
I checked the debug and it does get the profile: or x-wap-profile: in the header with proper URL of uaprofile. SO the problem is not from the Wap gateway but somehow in systems that were upgraded from 4.x

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2208
Registered: 10-2002
Posted on Monday, March 29, 2004 - 04:09 pm:   

It is doubtful that an upgrade from NowSMS v4.x to v5.x would introduce any problems with UA Profile parsing.

What is happening is that newer devices have introduced more variations in the encoding of the UAProf header.

For example, the encoding of the UAProf header as "X-Wap-Profile:" instead of "Profile:" has just started with phones that use an HTTP based protocol instead of WSP protocol. Versions of NowSMS prior to v5.50 will only look for the "Profile:" header, and will not recognise the "X-WAP-Profile:" header.

At the time of this message posting, v5.50 is still in beta. Information on the v5.50 beta release can be found at:

Another problem that has been experienced recently with UAProf headers is that some devices put "quotes" around the URL value. That is legal encoding, but earlier versions of NowSMS did not understand that. I believe that the "quotes" problem was addressed in v5.01.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics