| 'content-id' value encoding |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Liang |
Hi all, Offically, the 'content-id' value shall be 'quoted-string' according to WAP-230-WSP. That is, the value shall have a 'octet 34' char in the front of the string. Last week, somebody gave me some MMS bodys rxed from an unknown server. All these MMS's 'c-id' values were without 'octet 34'. And he told me that some kinds of Japaness phone can handle this kind of MMS correctly. So, my question is, have the encoding method for 'cid' been changed? and how does a MMS gateway relay this kind of MMS, drop it or just forward it in despite of its content? BRs, Liang | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi Liang, You're right that officially the Content-ID field should always start with an 0x22 (decimal 34, quote) character. How an MMS gateway relays this type of message depends on the gateway. I would expect most gateways to relay such a message, as if they perform a syntactical check on the message, I doubt they'd analyze the message content to that level of detail. Typically they might just look for major structural errors. In our implementation, we'd forward it along. If we had to reformat the message for any reason (for example, content conversion), when we rebuilt the message, we'd automatically insert the quote character into the content-id. (In our own message parsing, we decided that if the quote character was missing, we'd still parse the content-id as if it were there, as we figured that the mandated quote was a "strange" requirement. -bn | |||
| Liang |
Hi Bryce, Thanks for your help very much. BRs, Liang | |||
