Which API can be used for sending and receiving SMSes in Series 40?
As J.N. has said, Series 40 devices are not based on Symbian OS.
For sending and receiving SMS, you'll need to use the Wireless Messaging API and the PushRegistry.
Related
I am sending a text to a mobile number (US phone number) using the Programmable Messaging Quickstart for C# with .NET Core example. The message is sent and received successfully but the STATUS in the response shows "queued".
Is there a sample callback in C# to obtain the final status after the text is sent?
You have 3 options, either of the first two are suggested.
Subscribe to statusCallbacks, which will alert your application of the delivery status of the send message.
Use Event Streams to subscribe to specific message delivery event types (this option provides the ability to select different types of message delivery events).
Less efficient and not very scalable, make a request to the /Messages endpoint to determine the final disposition of the sent message (via its unique message SID).
Best Practices for SMS Message Logging
I am trying to achieve 2 way messaging with a super sim. I have been able to successfully configure sms received on my virtual Twilio number to be delivered to my sim by Http post (with authentication).
I would like to find a way to send an SMS from the sim and receive the SMS at a specific phone number. I've tried several flows without any success. I was able to get this working on Make.com and retrieve the data structure of the webhook but I still cant get this working on Twilio.
Thank you for the reply.
The sim is in an iot device and I am able to achieve 2 way communication utilizing webhooks with make.com. What I would like to achieve is to utilize a virtual number with Twilio to be the associated number for the iot device.
I have successfully received incoming "SMS" messages (commands) to the iot device, using a studio flow. When an sms is received via my virtual number number on twilio, the studio flow fires an https Post with the appropriate payload, populated from the received webhook from the virtual number., in turn receiving the "SMS" on the iot device.
Now I would like to create a flow or something similar on Twilio, that would generate a Twilio webhook that would listen for SMS commands (replies) "sent from" my appropriate Super Sim.
On Make.com I am able to generate the webhook and analyze the data structure, successfully receiving the payload of the webhook, from my Sim Fleet. I would like to utilize only Twilio for the webhooks, if possible. Do you have any more suggestions? Thank you in advance.
The Twilio Super Sim is not intended for use in a phone and does not support voice or regular SMS.
The Super Sim does support sending and receiving command (machine to machine, M2M) messages over SMS which can be used to send instructions to the device or receive data from a device. In this case the sim card can send messages to the number 000 and those messages will be received by Twilio and turned into a webhook request.
There is some documentation for how to send command messages from the Super Sim from a Raspberry Pi 4 or Raspberry Pi Pico and an in depth article on AT Commands that you can use to control the Sim.
I'm still learning about SQS, I did some successful tests with SQS and a Ruby application with Shoryuken that picks up the messages. This works fine. We want to get 1000 IoT devices installed in people's homes. These devices will send events to the backend, which will be picked up. So far so good.
Now we also need to send messages back to the devices (less frequent, but still). Will I be able to use SQS for this too? How can I target the device?
Do I need to add a MessageAttribute to identity the destination? Or create a queue per device?
What are the best practises here?
SQS is definitely not the right tool to use for sending messages to individual devices, and while a queue per device may work, I would not recommend it (1000+ devices regularly polling for messages can get expensive).
Take a look at Amazon IoT, in particular the message broker component.
I'm trying to develop a solution, where iBeacon has to be used as an alerting mechanism. This iBeacon has to receive alerts or messages from a remote server and then publish the same to its nearables.
Is this a possible usecase where iBeacon has to receive request from a remote server? As a disclaimer, I new to this technology and let me know if my understanding is wrong.
I believe you are approaching this problem from the wrong angle. Essentially you would like to receive a message when you encounter certain iBeacon signals. iBeacons are "dumb" devices, meaning they can only broadcast a data packet, they cannot receive any information and cannot broadcast anything different than the iBeacon protocol packet.
That being said, if you had a remote server that stored these messages, you ask the server what the most recent message is associated with the beacon you have just encountered. That way you can change the messages dynamically on the server based on what you need your user to know.
So essentially, because each beacon can be uniquely identified based on UUID, major, minor, you can store your messages based on this so that you can ensure the user is receiving the correct message when they encounter the beacon by sending these identifiers up to your server in order to retrieve the message.
When my Twilio numbers receive an SMS longer than 160 chars, I get a call to my server with each 160 char fragment. Each server call is like a separate SMS. The order in which I receive them is random.
Does anyone have a solution to this other than manually assemble these fragments?
Does anyone know of a replacement to Twilio?. It should support:
sending and receiving SMS world wide.
sending and receiving SMSs that are longer than 160 chars. (i.e. deliver multiple messages in the right order)
easy python/django integration.
Checked out Plivo's API. Did not find a solution there for receiving long SMSs
Apparently nexmo does what I need.
It works all over the globe.
It solves the problem of long inbound SMSs