I've set up Cognito and ensured that SNS limits are in place.
Verification SMS is being sent to Android phones, however, it's not being sent to iPhones.
The CloudWatch logs show the SMS was successfully sent.
Any suggestions?
AFAIK SMSs are platform agnostic. You shouldn't have this problem based on OS. It could more likely be related to limits itself. Sometimes AWS uses resources from a different region for SMS delivery which is not the region your services are running. e.g. if your service is deployed in ap-south-1 then AWS uses ap-southeast-1 (Singapore) for SMS delivery. You need to make sure if both the regions have appropriate limits available.
It is also worth checking your carrier settings and phone spam block settings.
Related
So I need to programmatically receive text messages from a shortcode. Twilio does not support this. Anybody know a service like Twilio but that is able to receive SMS messages from a short code sender?
Just to be clear. I need to receive a text message from a shortcode to a 10 digit number, not send from a shortcode.
Most services (Twilio, call fire) that let you send from a shortcode can not receive a text message from a shortcode
This can’t be done, shortcodes are unique to each carrier network, when a short code is available across multiple carriers it is implemented on each carrier separatly.
Also shortcodes are not international so 54321 could be used in both the UK and US by totally separate services.
SMS providers like Twilio and Vonage connect to the carriers in the same way as the shortcodes do, they are both an application connection. The carriers do not permit app to app messaging through their network so a shortcode app will only ever be able to send to a real subscriber with a SIM card.
You might find some providers that offer an SMS API by using banks of hosted SIM cards but this can be very flakey and you are usually sharing the number. The other option might be to look at hosting your own SIM card in a usb single or such and recieve the SMS that way.
Actually, Twillio does support this now, although with a big disclaimer that it "cannot guarantee that every short code globally will be able to reach Twilio numbers"
https://support.twilio.com/hc/en-us/articles/223181668-Can-Twilio-numbers-receive-SMS-from-a-short-code-?_ga=2.202438166.641482548.1608644940-210958917.1588771372
I think this article might be just what you're looking for https://help.nexmo.com/hc/en-us/articles/216487658-Inbound-SMS-on-dedicated-US-short-code
You should be able to receive SMS messages on a dedicated US Shortcode.
I have created a backend system which utilizes Twilio. The backend and the VoIP clients are both localised in Europe. The system sometimes experiences 32011 errors (Error communicating with your SIP communications infrastructure). Which I believe is mainly caused by the fact that the
twilio voice sip domain is located at Virginia US.
The problem is that according to this post: Twilio: Localized SIP URIs
,there is no way to change the region or create a voice domain at de1 region.
Is there any solution to this problem, by keep using twilio?
More details concerning this error may be found at the link below:
https://www.twilio.com/docs/api/errors/32011
With SIP domains, your clients are probably not shutting down their SIP clients when they are closing their laptops. This would remove their existing registration entry.
You can set the client SIP Registration timer to the minimum of 600 seconds (a setting on your SIP clients), which will timeout their registration entires after 10 minutes rather then the default 1 hour, which will reduce the frequency of that error message.
I am looking for any sort of iPhone function for sending messages that can be accessed by an Alexa skill that is able to send SMS text messages, as well as read SMS text messages of a user. I know that these skills are already present, however, I am looking to do this in combination with numerous other features which I have already finished.
Any help would be much appreciated. Thanks!
Alex Skills normally run as Amazon Lambda functions. Lambda functions can call other AWS services (from the cloud, not from the phone).
Amazon SNS can send an SMS message. Here is an example using the AWS Command-Line Interface (CLI):
aws sns publish --phone-number +XXXX --message "Hello!"
However, if you are looking to send messages from the phone itself, or read messages that are already on the phone, then you will need to write an iPhone app than can use the iOS APIs to send/receive messages. This would not, however, be an 'Alex Skill' since it is running on the phone.
is there a way receive an E-Mail in an iOS app, for example to get a notification if an E-Mail on an specified Account comes in?
If no ist is at least possible to read-access the mailstore?
Is there a Lib, to interpret the content of an email.
Due to Apple's sandboxing regulations, you cannot access the built-in Mail program's properties from your app.
You could use a 3rd-party API to connect to a email service (e.x. Gmail) directly through their server, and not Apple's mail program.
You cannot access the built-in Mail program's settings or properties.
You can, however, make network connections from your app, and could easily use a web service API to check the mail on a remote mailbox.
Amazon Web Services have an SDK for iOS which supports the Amazon Simple Notification Service (SNS).
Does this mean it would be possible to use SNS to send push notifications to a running iOS app? So for example you could make an real-time instant messaging app.
Is this right, or have I misunderstood what SNS does? It just seems to me that you would need to open a connection/socket in order to recieve push notifications from your server. How does the SDK actually work?
Update:
I've since asked this question on the AWS Mobile Development Forum: https://forums.aws.amazon.com/thread.jspa?threadID=81089&tstart=0
Apparently there is an article coming out (probably here: http://aws.amazon.com/articles/SDKs/iOS) shortly to explain everything.
Update 2
The article: http://aws.amazon.com/articles/9156883257507082
According to Apple documentation "Local notifications and push notifications are ways for an application that isn’t running in the foreground to let its users know it has information for them.".
So, technically speaking, any data, including notifications, received when the application is running in the foreground are not "Push Notifications" and can't be a reason for rejecting the application. They're simply data being consumed that way or the other by the application.
In this specific case you are not asking about Push Notifications per Apple's documentation, rather about a technology used to deliver data to the application when the application is running and user is interacting with it. It happens that the name Amazon SNS is similar to Push Notification.
In any case Apple wouldn't be able to see what is the technology behind delivering data to your application, whether it is Amazon SNS or anything else. All they can see is that the application may have some additional ports open when it's running, and that of course would be absolutely legal. In fact, many applications communicate with their back-end servers using sockets (not HTTP requests), and that is the same technology as used by Apple to deliver their Push Notifications.
According to the Amazon documentation, they in turn uses the APNS method and provide a much simpler frontend for Apple, Android and Kindle. A realtime instant messaging app could be considered as workable since by using the Amazon SNS platform, you could even consider the application to be available for all.
I mean by utilizing the Amazon SNS, the communication could be done between iOS and Android devices and to kindle also provided the applications are written accordingly. Though the Amazon documents do not provide a comprehensive example, there are bits and pieces. Also there is an upcoming event on the Aug 29 which could be seen from the Amazon SNS page.