I am using GCM server. I have gone through google and GCM official docs. But I am not able to know about the number of messages or requests that can be made per day against an API key.
Is there is any limit on number of messages that can be send to or from android apps and Third party application server using GCM.
Thanks and advance.
Related
I have some questions:
How to send a message to Whatsapp using Spring Boot? Is there an API ready to be used?
Is the traffic of the message, whether for receiving or sending, is paid? If so, how does the payment for this service, charged by characters or bit size of the information?
I found this article: whatsappmate article online, it seems like you can register your phone number with the API gateway but there will be a limitation to the number of messages you can send.
Also, there is a Whatsapp service from Twilio which is not free. You can check out their pricing here. I have used their APIs for SMS and VOICE calls and they were rich. So, I could expect their WHATSAPP API to be richer also.
I'm testing out the service and it appears that sandboxed applications do not support incoming replies even if the reply is from a verified number. Can I get that confirmed?
If that is not the case, my second question is how Sinch handles self-signed certs for the endpoint on non standard SSL ports ... in my case self-signed on 8443.
Lastly, a gripe. As a developer I look for immediate feedback when errors occur with my integrations. I'm not really willing to wait 24 hours for a CSV to see what happened. Any roadmap here to timely error feedback?
To handle incoming replies you need to rent a number like most providers, you can rent a number in the dashboard https://www.sinch.com/dashboard/#/numbers assign it to your app and configure your callback for SMS.
To handle incoming sms, check out the documentation here:
https://www.sinch.com/docs/sms/#smsmessagingcallbackapi
And if you have multiple numbers assigned to you app you can set the from id in the body of the request
{
“from”:”your rentednumber”,
“message”:”hello world”
}
You can always check the status for a particular message using the API here
https://www.sinch.com/docs/sms/#checkmessagestatus as you probably know long code delivery is only carrier delivery and not handset delivery.
If you mail me at christian#sinch.com I can hook you up with some more credits to rent a number.
can someone tell me what is the maximum number of push notification that can be sent through mspn in windows phone in a day. Or is it unlimited? If there is any limit, please answer following questions as well
Maximum number of notification that can be sent to mspn from cloud service per day
Maximum number of notification that can be sent to a single device per day
Additional cost per notification after the limit is reached
From: http://msdn.microsoft.com/en-us/library/ff402558(v=vs.92).aspx.
We recommend setting up an authenticated web service to send your notifications to the Microsoft Push Notification Service, because communication occurs over an HTTPS interface for better security. Authenticated web services do not have a daily limit on the number of push notifications they can send. Unauthenticated web services, on the other hand, are throttled at a rate of 500 push notifications per subscription per day
I need to send and receive SMS messages, but not on a phone. Sending is somewhat easy, as there are oodles of gateways that can be used. The challenge that I'm running into is handling responses received.
Can anyone point in me in the right direction of services or devices that can handle 2 way SMS short of an actual phone.
SMS GATEWAY ME is an android app that you can download for free.
I like it because it's free and easy to use. All you do is send a HTTP post to their server and it sends out a message from your phone.
You can set up rules on the site to get it to forward incoming messages to your server using HTTP / Email as well.
There are some 2 way SMS gateways out there. A quick search found this one: http://www.txtimpact.com/api.asp all I did was google for 2-way sms gateway.
Here's an example that uses Wammu under Linux:
http://www.techytalk.info/send-receive-sms-using-gsm-modem-phone-ubuntu/
Here's another link:
http://www.developershome.com/sms/smsLinux.asp
And:
http://www.developershome.com/sms/
Good luck!
We are building a web app that should be able to receive SMS messages and store the information contained in it in database.
Which methods have you used? Which service providers are out there that can assist?
http://www.clickatell.com/ are massive and it works exactly like it says on the tin. You pay for a phone number and sms messages sent to that end up hitting a URL on your site to deliver them just like someone posting a form.
I'd recommend using a service such as TextMarks. TextMarks is free, and lets you pick a keyword for your service that allows users to route messages to you through TextMarks' shared short code, 41411. The only catch here is that they reserve 20 characters in each message for short advertisements to pay for their services.
If you ever outgrow their ad-sponsored services, you can upgrade to a premium version that doesn't include ads.
Another (cheaper) alternative is to have your users send text messages to an email address like sms#yourapp.com. Then you can have a background thread that's looking at the email account and puts the messages into the database.
I've implemented and tested this approach with major US carriers with everything from smart phones to pay-as-you-go "crappy" phones without a hitch.
When the user sends the SMS to your email address you get the SMS email gateway address (e.g. 8055551234#vtext.net) so you can send response messages.
The only downside is that it's a bit more difficult to find the "send to email address" options on most phones, but it is (basically) free for you. This is especially helpful for reducing costs while testing out workflows. Those ~3 cents for each SMS add up pretty quickly, especially during automated testing.
When you want to support SMS numbers you can configure most SMS gateways to send an email to an address, so you won't have to change your infrastructure to support a "real" SMS messages.
I haven't done it yet, but I guess you could also setup an Asterisk system on your server, then get a regular VOIP acccount (which Asterisk hooks into) and configure the Asterisk server to forward all SMS to your application. This article might help setting up the Asterisk server.
I've had experience using MX Telecom as an SMS Gateway. Essentially they posted data to our web service every time we received an incoming SMS. The application in question was also sending SMS messages as well and we just did an http GET to a web page of theirs.
I can't speak to the business end (i.e. cost), as I was just in charge of implementing the features - but working with an SMS gateway is really very simple from a development perspective.
+1 on sebastian i was jsut writting pretty much the same
if you are working with ruby you might want to have a look at adhearsion
You can use SMS gateway software which will receive SMS messages through a GSM modem or 3G dongle connected to a PC and POST them to your website via HTTP. Eg: this software