My question is about google cloud Messaging system for sending huge amounts of sms to different targets but the text of messages is identical. Is there any spam filtering by google that may deny the delivery of my sms to those targets?
Related
I want to build a service of sms receiving online, so i got a sms gateway, gsm pool with 16 slots for sim cards.
I need it to be able to receive sms messages in multiple sim cards, for differente OTP services(Telegram, VK, FB), so every sim card should only receive one otp message at all, so i need various to make it work
Is there a way i can achieve it? Is there any software i can use?
There are several such websites that are using for receiving online OTP verification.
Here is the website I found helpful for me when sending and receiving SMS from different countries around the world https://anonymsms.com
If you sent out an SMS message from a SMS Gateway, will send it to the mobile network so how we get the perfect result for SMS delivery..? they send us the number of successfully send message but not in detail like sent Successful on this numbers and for this number are failure
It totally depends on what SMS gateway you use, what destinations you send to (even within a country there are differences between operators)
You have 3 options really, and these are country/SMS route dependant:
No DLR support
Network DLR (so you get updates if the NETWORK has received the SMS)
Handset DLR (you will get updates if the HANDSET has received the SMS)
The handset DLR is the most reliable, but in general, depending on DLR for delivery stats is not something you want to do too much. Operators fake these (antispam measures), SMS route suppliers sometimes fake them to be able to offer lower pricing (by not submitting 10% of the messages for example), etc.
Only way to be sure if an SMS is delivered is by using testing services.
There are a number of them around. If you use services like Messagebird or BudgetSMS.net, you can get the DLR updates pushed to your server, for further processing on your end (they are linked to the sent SMS itself)
Does CDMA support concatenated SMS?
If it is does which version of CDMA added support for it?
Which networks in the USA that use CDMA support concatenated SMS?
Thanks!
I wrote a blog post about this a while back:
https://www.smallbusinesstech.net/concatenated-sms/
Basically, Verizon only fully supports concatenated SMS within their own network. When sending out from Verizon to another network concatenated SMS works correctly. Concatenated SMS messages sent from another network to Verizon are delivered as individual SMS messages.
Sprint does not support concatenated SMS at all.
By "long" SMS, do you mean EMS? EMS is a series (varies by carrier), of SMS messages "stitched together". Your phone receives N messages and presents them to you as a single object.
However, as noted, this is both device and carrier specific. Your device is built to your carrier's specs for EMS. THe major US carriers support EMS, but the details vary.
I read that a GSM modem can only receive up to 30 SMS per minute. What would you do if you need to receive more than that? Is there another technology?
I think you might want something different to those answers listed at What are the best practices for building an SMS server
If you just have one service that is running where you want to receive many SMS then it would be most cost effective (and simplest) to avoid integrating with a mobile network operator and instead use a SMS aggregator. These often call themselves SMS gateways, but they are independent companies and not a mobile network operator's gateway.
An SMS aggregator acts as a middle man between you and the networks - they have agreements with many network operators and this interconnection means you can link with one aggregator and get access to almost every network in the world.
Aggregator's usually advertise for outbound SMS (where you are sending an SMS from your application to a user), but they all offer inbound SMS as well. Depending on your country you could opt for a premium number or free to receive number. A premium number would mean that the person sending the text message would pay extra money to send you a message - you may want this for a commercial service in order to bill the user. A premium number would also mean you receive a share of the money the user paid to send you the text message. A free to receive number would not cost the person sending the text message anything more than it would normally cost for them to send an SMS. Almost all aggregators will charge you a monthly rental for a free to receive inbound telephone number, but no additional charge per message received.
You can expect to integrate with an aggregator using HTTP or SMPP. HTTP is usually the easiest and the aggregator will want to know where to send the HTTP post when a message is received on your telephone number. Therefore you will need some sort of service that is running to receive the HTTP post from the aggregator, and possibly a way to reply to the user by sending another HTTP post back to the aggregator asking them to forward a message to the user confirming receipt of the inbound SMS message.
SMPP is a more robust protocol and is often used for high volume SMS applications - unless you already have SMPP experience or are sending many hundreds of thousands of messages you may want to avoid SMPP as it is difficult to implement until you have a lot of experience with SMS.
Some aggregators will provide their own platform where you don't need to have your own service running. For example you could setup a simple "autoresponder" on an aggregators website, this would receive the inbound message from the user, then autopmatically respond with a "thank you message". All interaction is done by the aggregator and you can log on periodically to download statistics or look at the messages people have sent.
Popular aggregators are:
InfoBip
Silverstreet
mBlox
If you do not have your own platform for managing the SMS interaction then either use the aggregator's own platform of install your own SMSC gateway. Some SMSC's are:
Kannel - Open Source, fairly difficult to install and manage.
NowSMS - Commercial software. Powerful, windows only, easy to use SMPP integration and has a 30 day free version. Allows GSM modems, HTTP and SMPP integration. Most expensive of these options but pricing is based on number of messages you want to send OUT per second / minute so if you're not planning on sending many out and only receiving them maybe this would be a viable option. There's a cheaper version where you can use one GSM modem (mobile phone) connected to a computer with a USB lead but as you will only have one GSM modem and no aggregator's you are limited to the speed at which your device can receive inbound SMS.
Ozeki - Commercial software. Lots of documentation available and the support team are very responsive. You can add local GSM modems or aggregator's using HTTP or SMPP.
I'm looking for the best practice, proper and "mobile carrier accepted" way of authorizing the sending of SMS/text messages to a cell phone number so that it can't be flagged as spam or abuse.
Basically, I want the user to enter in their cell phone number in my web app and then I want my web application to send some kind of SMS to them asking them to do something that tells the carrier and my app that they accept SMS messages from my web service. I do not want to spam - I only want people that want to receive the messages to their phone.
Also, I'm assuming that I can just SMTP to "email" text messages to their phone as well. Hopefully there's not a caveat to this method.
I have a little experience in this area and AFAIK there is no 'opt-in' list. However, carriers typically use the keyword DELETE to allow users to block messages.
Most carriers support a SMTP gateway addresses but you will need to know the carrier for each number. Here's a list to get you started. Also most messages received via a SMTP gateway will appear to come from different numbers on the users phone. (This is annoying for iPhone users who are accustomed to grouping of messages by individuals.)
If you are willing to pay per message services like EZTexting can take away some of the pain by doing the carrier lookup for you or sending your message via a direct, and more expensive, SMS gateway.
Here is a good overview :
http://www.acma.gov.au/webwr/consumer_info/frequently_asked_questions/spam_business_practical_guide.pdf
The US is actually behind with SMS regulations. We typically adhere to EU and Australian Legislation, which are stricter. The US will get there.
From a technical perspective:
You can use our Red API, just log on to www.redoxygen.com and select developers.