View Single Post
Posts: 1 | Thanked: 2 times | Joined on Dec 2009
#330
Originally Posted by frals View Post
The MMSC is where the MMS is fetched from. Basically there is a protocol for a device to tell the MMSC what capabilities and limitations it has, e.g. max size of images, what types of files it can handle etc. As fMMS does NOT implement that protocol your MMSC has no idea, and apparently defaults to a very small image size. Mine does the opposite and sends me everything without touching it.

How to fix this? Supply a patch containing the MMSUAProf/UAProf code and I'll be happy to integrate it into fMMS

[UAPROF]: “User Agent Profile version 2.0”, Open Mobile AllianceTM. URL: http://www.openmobilealliance.org
[MMSUAPROF]: “UAProf Schema for MMS Characteristics”, OMA-SUP-RDF_ccppschema_mms-V1_3, Open Mobile AllianceTM. URL: http://www.openmobilealliance.org
According to http://validator.openmobilealliance..../deli-faq.html:
x-wap-profile header item needs to be set to a link where UAProf of device is.
e.g. x-wap-profile: "URL_OF_UAPROF"

Supposedly, Nokia should be providing the UAProf file, as with all other Nokia devices. But since Nokia is not officially supporting N900 MMS, we'll have to find another way to host it.

I am looking forward to try this tonight and will test if I can control the image size received from MMSC.

BTW, this is the same approach used by SwirlyMMS (MMS for iPhone).
 

The Following 2 Users Say Thank You to ben.jamin For This Useful Post: