Restrictions
If you could send an SMS within a program on the iPhone, you'll be able to write games that spam people in the background. I'm sure you really want to have spams from your friends, "Try out this new game! It roxxers my boxxers, and yours will be too! roxxersboxxers.com!!!! If you sign up now you'll get 3,200 RB points!!"
Apple has restrictions for automated (or even partially automated) SMS and dialing operations. (Imagine if the game instead dialed 911 at a particular time of day)
Your best bet is to set up an intermediate server on the internet that uses an online SMS sending service and send the SMS via that route if you need complete automation. (ie, your program on the iPhone sends a UDP packet to your server, which sends the real SMS)
iOS 4 Update
iOS 4, however, now provides a viewController
you can import into your application. You prepopulate the SMS fields, then the user can initiate the SMS send within the controller. Unlike using the "SMS:..." url format, this allows your application to stay open, and allows you to populate both the to and the body fields. You can even specify multiple recipients.
This prevents applications from sending automated SMS without the user explicitly aware of it. You still cannot send fully automated SMS from the iPhone itself, it requires some user interaction. But this at least allows you to populate everything, and avoids closing the application.
The MFMessageComposeViewController class is well documented, and tutorials show how easy it is to implement.
iOS 5 Update
iOS 5 includes messaging for iPod touch and iPad devices, so while I've not yet tested this myself, it may be that all iOS devices will be able to send SMS via MFMessageComposeViewController. If this is the case, then Apple is running an SMS server that sends messages on behalf of devices that don't have a cellular modem.
iOS 6 Update
No changes to this class.
iOS 7 Update
You can now check to see if the message medium you are using will accept a subject or attachments, and what kind of attachments it will accept. You can edit the subject and add attachments to the message, where the medium allows it.
iOS 8 Update
No changes to this class.
iOS 9 Update
No changes to this class.
iOS 10 Update
No changes to this class.
iOS 11 Update
No significant changes to this class
Limitations to this class
Keep in mind that this won't work on phones without iOS 4, and it won't work on the iPod touch or the iPad, except, perhaps, under iOS 5. You must either detect the device and iOS limitations prior to using this controller, or risk restricting your app to recently upgraded 3G, 3GS, and 4 iPhones.
However, an intermediate server that sends SMS will allow any and all of these iOS devices to send SMS as long as they have internet access, so it may still be a better solution for many applications. Alternately, use both, and only fall back to an online SMS service when the device doesn't support it.
I have not done this myself but I have worked in a simlar area.
There are two ways to send the WAP SMS Message (basically a binary Wireless Datagram Protocol (WDP) formatted binary SMS message)
- By Phone using the WAP api.
- Using a SMS gateway.
A SMS Gateway allows you to send sms messages from the internet. If you search on the web for SMS gateways you should get lots of them. Pick one that supports sending Binary SMS Messages.
As part of the WDP header you have to specificy a port number, which is the port number they go on about.
Before you send the sms message, you need to check with your cellular provider that they support binary sms messages, not all cellular networks do.
The rest of it is pretty much following the Microsoft Example:
- Create the registry setting.
- A WDP SMS messages arrives at the WDP layer on port WDPport1.
- The WDP layer checks if the application is registered with the WDP
layer on Port Number WDPport1. In this
case, no application is registered.
- The application checks the registry to determine if any application is
registered for WDP messages on Port
WDPport1., The application finds that
Chess.exe application is registered.
- If Chess.exe is loaded, the application launches Chess.exe.
- The chess application opens "ListenerWnd" Listener Window Class.
- "ListenerWnd" receives a message with DWORD value
- Chess.exe recognizes this message as an indication that a WDP message is
awaiting on port WDPport1 and
registers WDPport1 as it's own with
the WDP layer.
- Chess.exe receives and processes the awaiting WDP message.
- Chess.exe closes.
Best Answer
To receive an SMS in native code(source can be found here). This only catches the latest received SMS:
For C# look at MessageInterceptor, though I am not familiar with the method to read the message itself.
You can also download OpenNetCF SDF 1.4 source code and fill in the missing functionality of the receive part (it's commented out).