| Processing MMS with GSM modem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Jon Wilkins New member Username: Scadgetv Post Number: 1 Registered: 09-2005 |
Hi, I'm evaluating NowSMS mainly for RECEIVING of SMS and MMS (photo, video, sound) via a MultiTech GSM/GPRS Modem. It works fine for SMS text messages. It receives MMS photo messages but resizes them (I believe - I'm testing with a Nokia7610 and I'm assuming it is sending at full size but can't be sure if it is reduced on sending). I want to retain the images at their original maximum size. I've browsed the discussion board and seems to have something to do with UAProf.INI but the evaluation version I installed didn't create one and I don't know what should be in there. Even so, I don't want to reduce the image size because it will be posted on a website. It receives sound files ok. It won't receive video files at all. I get the usual additional SMS telling me that my phone doesn't support content of the type received. But, being a modem, I would imagine it could receive anything because the conversion of the video is done by NowSMS. Again I believe this may have something to do with UAProf.INI but can't figure it out. Based on some of the discussion threads I tried modifying the UAMAP.INI file to include *=default.xml and created a default.xml file with a UAProfile for a Nokia7610 which supports video but this didn't have any effect. So, I'm a bit stuck on my evaluation so any constructive advice to help resolve my problem would be greatly appreciated. Many thanks! Jon Wilkins | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4976 Registered: 10-2002 |
Hi Jon, This is a tricky issue. If I understand your configuration correctly, you are sending/receiving MMS messages through an operator MMSC. That is, you have MMS receive settings defined for pulling in received messages from the operator MMSC. In this case, it is the operator MMSC that is doing any resizing of the messages, and/or deciding what features/functionality you can support on the receiving end. We do similar things when NowSMS is the MMSC, which makes this confusing. The UAPROF.INI file that you refer to all has to do with configurations where NowSMS is the MMSC. But in this case, the operator MMSC is the MMSC, and it is performing similar logic ... but unfortunately we have to make some guesses about its logic. Basically, every phone reports its characteristics through an HTTP/WAP header. The "User-Agent:" string can contain a text identifier string for the device, and the "Profile:" header can contain a URL link that points to a document that contains a User-agent-profile (UAProf) document that describes the characteristics of the device. Based upon the UAProf document, the MMSC can determine the characteristics of the receiving device, and make decisions about whether or not to scale images. When NowSMS downloads a message from an operator MMSC, by default, we do not send this "Profile:" header. Therefore, the operator MMSC might decide that we are a very basic MMS client that only supports low resolution images. For this reason, we have a configuration option that allows you to insert a "Profile:" header, this is referenced in the following thread on our discussion board: http://support.nowsms.com/discus/messages/485/4510.html So you could select a URL for an existing UAProf from a commercial phone, or you could create your own. For the purposes of my testing, I have a custom UAProf that clearly states that we support large images, and as many different content types as I thought might be relevant. This UAProf URL is http://www.nowsms.com/nowsms.xml. So I inserted the following lines into my MMSC.INI under the [MMSC] header: HeaderProfile=http://www.nowsms.com/nowsms.xml HeaderUserAgent=NowSMS With these headers present, I would expect the operator MMSC to fetch this UAProf and determine that the device supports larger images and video. But you never know if the operator has a static database for your phone type, or if it is dynamic. So you might want to move SIMs around between phone and modem, and see if there are content type restrictions that are SIM based. I hope this helps. Which mobile operator? -bn | |||
