| Process involved in setting up |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| anandapadmanabha Unregistered guest |
If I want to set up a lab for testing for MMS. I have doubts on using the solution. Can the target device be configured to receive the WAP push indications, through a PC interface. Is it possible for PC to be configured to send the indication by SMS by adding an external hardware. Can you give some details about the hardware and cost of hardware in India. Do operators in India provide support for receiving WAP push message from outside? Is the nowSMS similar to Intromobile MMSIOT? Will this function like a stand alone MMSC for testing the MMS agent solution on phone hardware as well as on Destop SDK. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4658 Registered: 10-2002 |
We have a lot of customers that use NowSMS as an MMSC in lab environments. The most difficult issue to deal with in such an environment has to do with how "in the real world", the process of delivering an MMS to a handset begins with an MMS notification message that is delivered to the handset over SMS. (For more information on how MMS works, see http://www.nowsms.com/howmmsworks.htm) The parts of the protcol that are pure IP are relatively easy to deal with, but actually routing an SMS into a device in a lab environment is considerably more difficult. Companies like Anite (www.anitetelecoms.com) and Agilent (www.agilent.com), among others, make test equipment for simulating GSM/GPRS networks. And they support scripts so that when NowSMS needs to deliver an SMS, it can issue an HTTP request to the test equipment, which can then deliver the SMS to the device. You'll find a couple of threads out here, making reference to the Agilent solution: http://support.nowsms.com/discus/messages/1/5614.html http://support.nowsms.com/discus/messages/485/6963.html http://support.nowsms.com/discus/messages/485/6881.html Now, the MMS notification does not have to be delivered via SMS. The MMS notification is delivered via a WAP Push message. In today's networks, a WAP Push is generally delivered over SMS for a variety of reasons. But, if you can assign static IP addresses to your devices, you can define a table of phone number to IP address mappings, so that NowSMS will deliver MMS notifications for phone numbers in the table via IP instead of SMS. There is a brief discussion of this technique in the following thread: http://support.nowsms.com/discus/messages/485/4184.html Sending the MMS notification/WAP Push messages over SMS using a live operator network should not be a problem. The easiest way to do this is with a GSM modem connected to the NowSMS server (http://www.nowsms.com/whatisnowsms.htm#whatisgsmmodem). But this does require that you be on a GSM network (and I know India, like the US and China, has a large mix of CDMA and GSM). CDMA networks are more difficult to deal with. We do have several CDMA mobile operators who are using NowSMS as their MMSC, but we have not found a good way to do this for CDMA in a lab environment. Regarding other questions ... I have no experience with Intromobile, so I can't comment. As an MMSC, our product is actually in live production use for a number of mobile operators, it just happens to also be extremely flexible for also operating in lab environments, allowing you to do real world scenarios.
For delivering an MMS message to a desktop SDK, obviously the MMS notification (WAP Push) needs to be delivered via IP instead of SMS. So, for this, I refer you back to the link referenced above, which explains how to implement a table that maps logical phone numbers to IP addresses in order to support this type of scenario. -bn | |||
