| MM7 |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through August 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Joel Bjerk Unregistered guest |
Hello, Does anyone know why the MM7Submit spec lists content as an optional parameter? Also, is there a way to specify the content location (URL)using MM7? Thanks, Joel | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2543 Registered: 10-2002 |
Joel, Can you direct me to what section of the specification you read this in? (And which spec ... you are talking about 3GPP TS 23.140, right?) There is a general statement about the structure that says "If a SOAP attachment is included it shall be encoed as a MIME part and shall be the second part of the HTTP Post message." But this is a general statement applying to all different MM7 transactions. Some MM7 transactions, like cancel or delivery report do not have content. But I would expect an MM7 Submit to include content. An MMSC would certainly be justified in rejecting a submit request with no content.
I'm not sure what you're asking here. Can you please clarify? -bn | |||
| Joel Bjerk Unregistered guest |
Hello Bryce, Since I'm new to MMS and may not be using the correct terminology I think this will be much clearer with an example: I am working on a VASP project with a requirement that the VASP must host and serve the MMS content. What I'd like to do is send a MMS notification with a specified URL for the content so the user (handset) could retrieve the content from the VASP instead of the MMSC. I would prefer to implement whatever the industry standard is so the VASP will work with most vendors’ MMSCs. However, I read the spec and it isn't clear to me if this type of behavior is supported by MM7 or MMSCs in general. Thanks, Joel | |||
