| How could Now SMS/MMS help my project |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| John Gu |
Hi Bryce, I am working for a project in our company and I am not sure if your Now SMS/MMS would help me to work it out. On the serverside, I am going to send a sequence of MMS with a proprietary formatted file in it. For the client side, I want to use my own MMS client instead of the standard MMS client in the cell phone to receive the MMS and display it. I greatly appreciate if you could help me to clarify the following question: 1. Is it a must for my server to use your Now SMS/MMS in order to send MMS out? 2. Is it possible for me to use my own MMS client (a MIDlet) to receive the MMS instead of using the standard MMS client(build in the cell phone)? I know there is a new feature in MIDP 2.0 named Push Registry that might be used to active my own MMS client upon receiving a SMS (I assumed that could also be a MMS notification). I am still not sure if that requires special configuration in the MMS that would be sent by the server. Thanks. John | |||
| Bryce Norwood - NowSMS Support |
Hi John, I'd be very surprised if you were able to find a standard way to hook into the MMS notification and register your own MMS client. I haven't seen any standards in this area ... so if possible, it would be device specific. I think you'd want to use the push registry. I haven't actually implemented one of these applications before, but my understanding is that you register to listen (or have your application activated) for SMS messages receieved on a particular port. To send a message to the application, it is a matter of setting the UDH (user data header) in the SMS message to route the message to a particular port. A simple UDH for routing to a particular port would be this: 060504xxxxyyyy xxxx is the destination port in hex (on the receiving device) ... yyyy is the source port in hex. | |||
