| MMS Transcoding |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi I was wondering if NowMMS can transcode / render content to suit a particular device type as it handles MM1, or if this is something that leading MMSCs can do. When the HTTP request is made to the webserver containing the .mms file, isn't user agent info provided? If so, can the gateway transcode the SMIL then recompile the .mms binary to suit that particular device? (in theory at least) Otherwise, how could NowSMS integrate with an external transcoding engine? Thanks in advance | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1552 Registered: 10-2002 |
The MMSC in NowSMS looks at the "Profile:" header and uses that information to determine characteristics of the device and perform some transcoding. | |||
| Anonymous |
Great, thanks for the reply. Are you able to elaborate on the type of transcoding that's performed? eg. image size / type / SMIL ... Also, how many profiles are stored and how easily & frequently can they be updated? Thx Nick | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1583 Registered: 10-2002 |
Nick, We primarily deal with image size and type (which can result in SMIL references needing to be updated). We also filter out types that are not supported by the device. We'll store a profile for each different device that connects. (Different versions of firmware often have different profile files.) Once we've downloaded the file once, we won't redownload (which is usually not a problem unless you are dealing with prototype phones). The following threads might help elaborate a little bit more: http://support.nowsms.com/discus/messages/1/453.html http://support.nowsms.com/discus/messages/1/673.html http://support.nowsms.com/discus/messages/485/844.html http://support.nowsms.com/discus/messages/1/313.html -bn | |||
