Originally posted by Nancy Lehrer:
I'm researching the use of Push technology in MIDP 2.0 on the iDEN network to send notifications to our DispatchSuite application that new dispatch data is ready on the server. I am trying *real hard* to avoid reqiring static IPs for our application to work, so I want to use the SMS protocol for the push registration.
The payload of SMS message we need to send is really a non-issue. All we want to do tell the handset to wake up and use it normal http GET mechanisms to get any waiting messages from our server. So there may be a control bit or two, but size is of no consequence.
The question is: what is required to send an SMS message over the iDEN nextwork to our J2ME application?
Do email messages automatically get transfered into SMS messages. So, would an email message to firstname.lastname@example.org send using the JavaMail API translate to an SMS message when it gets to the phone? And what is the port that I should register from the phone?
Or do I need to use an "SMS broker" such as Simplewire and use the Simplewire SDK.
Thanks in advance for your knowledge,
Originally posted by Shawn Fitzgerald:
While jSMS is great if you have the ability to hook up a dedicated cellular device onto your server. But I like the ASP model where they handle scaling and load on the cellular network. Nokia has a great device (Cellular Terminal 31) an M2M device dedicated for jSMS type use.
Question: Have you tested any type of loads on jSMS? If so how does it perform? any idea of max# of messages/sec? Is there a way to have 2 or 3 devices managed by jSMS as a service
and have it handle load balancing?
Originally posted by Michael Yuan:
Email probably would not work since the message is delivered to the native Inbox not the AMS -- there is no port number associated with the message. That also rules out toolkits like jSMS.
Simplewire might work but I have not looked at their APIs for quite a while.
I think the most promising solution is JSR 212, which defines the server side messaging API. Since I am in the expert group, I can tell you that SMS port is quite likely to be supported. Before the JSR 212 comes out, a similar product I would recommend is the Nokia Mobile Server. It goes far beyond SMS messaging. Check it out!The downside of this approach is that the carrier must open their MMSC to you. That could be a real bummer since telecomms are not exactly developer friendly. But you can alsways try.
Another solution is to borrow the idea of jSMS: For small volmue applications, you can use a phone running WMA as the "gateway" device. It is placed at a always-on location and receives data from a network server. Then it pushes SMS messages (with port numbers) to wake up other handsets in the field. Just some ideas here. Let us know what works for you!
If you are sending messages through a web server, you don't need anything written in J2ME. Most carriers maintain a website for sending messages to their subscribers. For example, this is Sprint's: http://messaging.sprintpcs.com. This is Cingular's: http://www.cingularme.com/do/public. Here is Verizon's: http://www.vtext.com.
Originally posted by Hari Krishna:
I am new to J2ME. I have to send sms to GSM and CDMA mobiles. Please Explain the process to do this project. I have to send sms through web.
The happiness of your life depends upon the quality of your thoughts -Marcus Aurelius ... think about this tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your databasehttps://coderanch.com/t/704633/RavenDB-Open-Source-NoSQL-Database