| Image resizing? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hello, We recently purchased a license for NowSMS and are having some issues with image sizes and MMS messages. In particular when we use NowSMS to send an MMS message with a large image (greater then 30 kb) to either the Sharp GX10 or the Samsung V200 phones the image does not appear to be resized correctly (smaller images work). A few questions: 1) Do you have a updated version that handles these new devices? We are on version v4.20 (b20030507) 2) I noticed a directory in the NowSMS installation called UAProf that seems to contain device profile information. How would I add a device profile for a new device? 3) Are there settings for image resizing on devices that NowSMS does not recognize? How would I adjust these settings? thanks. | |||
| Bryce Norwood - NowSMS Support |
Hi, It's probable that the phones you mention have size limitations. Indeed, the Sharp GX-10 has a 30KB limit on overall message size, not just individual image size. So, you're likely running into two problems: 1.) Some phones, like the Samsung V200, do not publish a "Profile:" header, which contains the user agent profile information about the device. 2.) Some WAP gateways, especially the Vodafone WAP gateway, do not forward the "Profile:" header, which contains the user agent profile about the device. (Vodafone desperately needs a new WAP gateway as they seem to be the only major operator that is not forwarding this information.) So, let me explain how this all works, and what you can do. Receiving an MMS message is a 2 step process. First the recipient receives an MMS notification message over the SMS channel ... this contains header information about the MMS message, along with a URL pointer for the recipient to fetch the message over HTTP or WAP. When the recipient device fetches the MMS message content, it makes an HTTP request (usually via a WAP gateway as a proxy). In this request, it can include some information in the HTTP/WAP headers about the type of device. The two headers of relevance are the "Profile:" and "User-Agent:" headers. The "Profile:" header points to an HTTP URL that contains profile information about the device. For each device/browser, the manufacturer publishes a "UAProf" (User Agent Profile) XML document that describes the supported characteristics of the device. The profile is published on the manufacturer's web site, and the client on the phone simply includes a "Profile:" header that points to the profile URL for that device. When the "Profile:" header is present, NowSMS automatically retrieves these documents (as long as NowSMS is not behind a firewall that blocks external HTTP access from the gateway), and maintains a local cache in the "UAProf" subdirectory of the gateway installation. New profiles are automatically cached the first time they are encountered by the gateway. A UAPROF.INI file is created automatically which maps the Profile URL to a locally cached copy of the UAProf document so that the gateway does not have to retrieve the UAProf document each time a client connects. For situations when the "Profile:" header is not present, NowSMS looks at the "User-Agent:" header. It then looks for a substring match between an entry in the UAMAP.INI file and the "User-Agent:" header to automatically assign a local "UAProf" file to be used for the device. For example, the default UAMAP.INI that we include with the gateway has User-Agent mappings for the strings "Nokia7650" and "Nokia3510" ... two popular early MMS phones that did not publish a UAProf file. [UAMap] Nokia3510=NOK3510.xml Nokia7650=NOK7650.xml If the gateway sees a substring match for the "User-Agent:" against one of these strings, then it uses the UAProf file defined in the UAMAP.INI file. For example, in the default UAMAP.INI file, a "User-Agent:" string that includes the text "Nokia7650" gets mapped to the NOK7650.xml UAProf document (located in the UAProf subdirectory). Some folks have decided to use a generic UAProf for phones that do not publish a "Profile:" header. There is another message thread on this discussion board that discusses this topic at: http://support.nowsms.com/discus/messages/12/419.html There is also a very useful web site that has links to different UAProf files: http://w3development.de/rdf/uaprof_repository/ Unfortunately, I have yet to see a UAProf file that covers the Samsung V200. I hope this helps. -bn | |||
