I've read auto sms is not possible, if you send a SMS through an app you need user interaction like pressing a button.
But if my phone shows up at a particular position based on gps and a stored record that has that gps info, would that not be the user interaction I need and the sms just get sent?
From the code I've seen if button pressed run this code and send SMS.
What I'd be doing basically is
If I arrive at this location send SMS. From my view this is not exactly Auto SMS, its sms based on certain variables but without user interaction.
Is this possible, am I making any sense lol
As a workaround, you could use one of the SMS services available to send a SMS. If you would like a free solution, you can use the carrier email-sms to send a SMS. You just have to send an email at this point in your code.
Related
I already have a SIM card with a company that allows tethering and A2P.
I want to be able to send an SMS with a unique sender ID (company name) using that sim card.
Is this possible and if so, what should I purchase and how do I set it up?
It is NOT possible to alter the senderid when sending SMS using a SIM card + modem. The senderid will simply be the number belonging to that SIM.
If you want to have a custom (alpha) senderid, your only option is using a professional A2P SMS gateway. But even then it is not always possible, as not all countries allow alpha senderids. They might get overwritten to a short/longcode, or the operators require senderid whitelisting (basically, you need to request "access" to an alpha senderid, by sending your personal/company details and SMS content details to the operators. This is done to battle SPAM messages)
Yes this is possible.
Most of the time you don't need any SIM card as you'll be using some sort of API, most of the time a HTTPS/JSON or HTTPS/XML API. If you intend to use a SIM to send SMSes, having a dedicated sender ID will be most probably impossible: using a SIM will make your request arrive through the "regular" signaling link just as "any subscriber" that sends an SMS from his mobile, while using an API will make you use the SMPP links to the SMS-C where specific configuration can be done on per client basis. If I misunderstood something, please sent a comment.
Anyway, you have to have an agreement with your SMS API provider or telco to use a dedicated ID
In my application, I have about 50 users that need to send and receive SMS. How would I integrate this using Twilio? Do I need a number per user so that when they revive an SMS, I can show it to a specific user only?
The link below shows how to receive SMS, but I need help storing/displaying the SMS to the correct user only.
Laravel/Twilio Receiving SMS
We have been recently asked to add ability to send and receive MMS to our FLEX application. Our initial plan was to use our existing functionality instead i.e. send an SMS with a subject line. When the client responses to the message with an MMS (because the SMS will become an MMS when the client attaches the required picture) the message will be routed to MMSC who has been requested to forward that message to us an email (because again our application already has ability to receive and process emails built in).
Based on my research I've found that:
1. If you add a subject line to an SMS, the SMS automatically because an MMS meaning we will need to add ability to interact with the MMS gateway. I'm fine with this.
Now my question is, if we send an MMS with a specific subject line, when that the client receives and responds to the MMS, will the subject line be automatically carried back to us like it is done on emails? The information that we will be carrying on that subject line is very important for the correct routing of that reply. Secondly, does anyone know of a website that already has MMS sending functionality. I would like to test this before going further with my design.
I have code written up in Processing that works as a serial monitor for my Arduino Fio. I have a few sensors on the Fio that output a warning message when a value surpasses a threshold. How do I get warning statements sent to a phone number as a text message as well?
If you need to send email to just a particular phone (i.e. your own) or a small set of phones known in advance, many carriers have an email SMS gateway. For example, to SMS the Verizon phone 304-555-1212, just send email to 3045551212#vtext.com
See: http://en.wikipedia.org/wiki/List_of_carriers_providing_Email_or_Web_to_SMS
Here is an example on how to send email from Processing: http://www.shiffman.net/2007/11/13/e-mail-processing/
Twitter is a good place to start with this. Your thing -> twitter. Twitter -> SMS (or other clients). Otherwise, it gets expensive and more complicated.
I'm trying to figure out how to set up an SMS service where users can communicate with people on phones that are not participating in my service. "TextFree" on iPhone does something like what I want to do. They let you sign up, then you can send messages for "free" to other friends that aren't part of the service.
It looks like when you sign up for TextFree, they assign you an email address [user#textfree.us]. People outside the service without MMS capabilities can't send an SMS to this user. The user must first send an SMS to them, starting a conversation. I think this is what they're doing:
Textfree signs up for an account with a bulk SMS provider, and is assigned a single phone #, like "123".
Joe signs up for TextFree, gets assigned email: joe#textfree.us.
Mary wants to send Joe an sms, but can't because she doesn't know what # to direct the sms to.
Joe sends an sms to Mary using textfree. This really just makes an http request to some textfree server. The server gets the request, and the destination # (Mary's phone).
The server sends the sms out using their bulk sms api provider.
Mary receives the sms, and sees the originator phone # as "123".
Mary replies to the sms, using this phone #, "123".
Their sms provider receives the message, and forwards it to textfree's http server.
Textfree now has to resolve that the sms received by Mary's phone # is destined for Joe (not sure how this can be done), so it can be delivered to Joe's account.
I think that all makes sense and seems feasible, I'm just not sure about that last step, how they could figure out which conversation sms' belong to. If all outside users are directing their sms to phone #123, how could I figure out which internal user the message is destined for? Is there some way to embed a unique identifier in an SMS, so that when the external user replies to the SMS, some unique ID can be embedded in there to provide that type of context to read on the reply side of things?
Long question, thanks for any thoughts!
As for the last part of your question (unique ID in SMS):
I know of no mechanism that could help you here. When replying to a short message phones only set the sender address as destination and the user is free to type the text. The headers in a short message PDU are solely for the basic transport parameters (encoding, sender-ID, ...). There is a way to define so called user data headers, but for this to be of any use for you, you'd have to be in control of most of the devices that are involved in the message delivery, including the handsets... So basically the only way I see to correlate messages with each other reliably is the use of some ID within the message text.
An alternate approach would be to rent a bunch of numbers and assign these permanently (I assume some subscription model here) to your users. This way you could use these as identification numbers within your service and forward the messages to their real phone numbers (or even a completely different media like email / instant messenger).