| Need some ideas ... |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| -=[The Informer]=- |
Hi all, I'm currently developing a mobile services and entertainment site. I've downloaded and am building the site around NowSMS/MMS GW. Currently I'm facing a small problem. I hope that this is the right place to post this and that some one can help. The problem is this, sending the notification with the URL of the MMS message file via SMS is simple thanks to NowSMS. But will the user be able to view the location of the file and the encapsulated elements inside of it? This is critical because if so, what keeps him from giving this URL to someone else who will then be able to download the message free of charge. And if this is the case, do I have to create a mechanism that will store the message in a temporary location and delete it as soon as he downloads it. Thanks in advance. | |||
| Bryce Norwood - NowSMS Support |
It would be difficult, but it could be possible. You'd basically want the URL to be deleted after retrieval (something that we are looking at implementing in a future release). However, keep in mind that even this is not foolproof. Someone could setup their own gateway, and have your service send a message to their gateway, where they could receive a local copy of it. I almost hate to mention that fact ... but even OMA DRM is not a significant deterrent to this possibility. -bn | |||
| -=[The Informer]=- |
Thanks for the reply Bryce. But I'm not sure if I understand this right. You mean even when I use the built-in MMSC to compile an MMS message from a number of files that I post, the output will remain in the MMSCDATA folder even after the message is downloaded by the recepient? And by "in future releases" you mean that even version 5 of NowSMS/MMS GW doesn't do that? | |||
| -=[The Informer]=- |
One other thing. When compiling the message from posted files. Is there a way to limit the size of the overall resulting MMS? Or do I have to do it programmaticly before sending the files to the MMSC? | |||
| Bryce Norwood - NowSMS Support |
Yes. It is a complex reason. Unless the mobile phone recipient has their MMSC setting configured to point to the same NowSMS Gateway (and this is usually note the case), there is not a 100% way of being sure that the recipient has downloaded the message. The NowSMS MMSC only knows that a download was attempted via a WAP gateway, but it does not know whether or not that attempt was ultimately successful.
Right. We recognise that we should have some configuration criteria to expire a message after so many attempts, or after so many minutes following the first attempt.
You would have to do that. We don't enforce a size limit (although I do think that would be a good idea). | |||
| A H New member Username: The_informer Post Number: 1 Registered: 10-2003 |
This is -=[The Informer]=- again. I registered in the discussion board. So, I don't know what my nickname will be. Anyway. You are right about the DRM and OMA Forward-Lock, both only prevent the user of a terminal (mobile phone) only from forwarding the content. And yes, you have to encapsulate each element in the MMS message that you want to prevent forwarding for. My question is, does the MMS composer utility provided with NowSMS/MMS support those locked file formats when submitting the content to the MMSC? I also want to allow the users of my site to compose their own MMS messages. Should I forward the request that includes the submitted files to the MMSC directly and what status code for the response should I expect upon success? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1006 Registered: 10-2002 |
Not yet. So far, I haven't seen any MMS clients that support the forward-lock using the OMA standard. (Quite a few phones have shipped with forward lock supported in the WAP browser, but forward-lock in MMS has been a little slower.) We're waiting to perform some tests ... supposedly the Nokia 6600 supports forward-lock in MMS. We'll need to do some tests with it, and any other phones that are supporting the OMA forward-lock. Unfortunately, if a phone does not understand forward-lock, it will not understand the content at all, and your application will typically not be notified of this. | |||
