Hi i am building a website which needs to send sms.
Scenario is User will create his/her account using his/her mobile no.
After that he can send sms through website to any mobile number.
When the end user receive the sms the sender no should be the same the number with which he registered.
I want to code it in C#
The similar thing has been done and the code has been released for a 3rd party SMS Gateway called Way2SMS here at Code Globe. http://www.codeglobe.in/index.php?option=com_content&view=category&layout=blog&id=30&Itemid=36
Related
I am using an Identity and Access Management(IAM) vendor who provide a Multi-Factor Authentication (MFA) Service (using SMS and other channels). They use Twilio as their SMS service provider and what I see currently is a behaviour (described in the scenario below) from my IAM provider which is strange and wondering what the underlying Twilio API's behavior is.
I am unable to see this info from the Twilio API docs hence seeking assistance.
Scenario:
Customer uses IAM to login and my IAM provider using Twilio sends a OTP
The OTP comes through but in my test case, I trigger the resend OTP process
In both the steps, I get the right message (the template and senderID that we have configured in the IAM tool)
If I now trigger the OTP resend process a second time (3rd OTP in total for the same number), we receive a message which has AUTHMSG as the senderid and uses a default template message (which is different from what we have configured).
I am working with my IAM vendor to understand what is happening here and I am trying to see if Twilio is playing a part in this (trying to do some smarts as they think that there is some SMS delivery issue - which is the message I am in a way communicating by hitting the resend OTP multiple times)
Is AUTHMSG a senderID that is owned by Twilio? I don't believe so but I am trying to better understand this space.
SenderID is a construct that varies from country to country. Some Contries mandate that users register it with the local regulators while in other countries there is no explicit registration process.
I am worried that if my customers receive this message, they are going to be confused and suspect a Spam/Phishing kind of an activity.
I attempted a similar exercise with PayPal and they were consistent in their SMS OTP Resend. The message was always the same. Unlike my IAM provider, PayPal sends OTP from multiple mobile numbers. In my tests I observed them sending OTPs from two distinct mobile numbers.
Would be glad if someone could assist and provide info in this space.
I will continue to work with my IAM provider and their support channel to see what is happening here.
When using Twilio Verify in a country that supports alphanumeric sender IDs, Twilio uses the AUTHMSG sender ID and registers it with countries around the world that require this, to ensure the best deliverability of OTP messages.
I think you will need to work with your IAM provider, and work out how they have implemented sending OTP messages to see what is going on here. If it is unclear, then you or the IAM provider may also have to contact Twilio support.
I need to do a feature to read the OTP from SMS and fill my field.
The only way today to do it is using SMS Retriever API from Google?
Nothing without a 3rd party lib?
I mean, Apple has it native.
We are avoiding using Retriever API because we don't want to change the SMS template we have.
Is there something that I can do about it?
The only alternative that is available now is to use SMS consent API, other than that it's not possible to detect the SMS now.
You can check about this by following the below link
https://developers.google.com/identity/sms-retriever/user-consent/request
I'm applying from Twilio to use their WhatsApp API service they are providing to build a WhatsApp auto-reply bot. But the problem here is that they want us to use the phone number they provide to us which we need to buy from them.
I tried using the URL 'https://api.whatsapp.com/send?phone=15551234567' but it just redirects to a page to send a message which I need to click 'Send' in order for it to submit our message. Besides that, we need to be able to trigger the application that a message is received from a recipient so we still need to access the API.
So how exactly is it I want to build a Whatsapp Auto Reply service to the public if Twilio provides it's own phone number only to reply. I want to reply using phone numbers that my clients register with me which is their own phone numbers.
As we know Whatsapp API is not open for public but how other Whatsapp Auto Reply apps are able to use our phone number to auto-reply to our recipients?
Would love some feedback or solutions from StackOverflow community. Thanks.
Twilio developer evangelist here.
Currently the Twilio documentation on using numbers on WhatsApp says:
Currently, we are unable to enable WhatsApp on non-Twilio numbers; support for this is coming soon and we will update these docs once available.
So this is just a current limitation and will be changed in the future.
That would be a great notification method. Since the Google not sending anymore SMS reminder, and the other portals doing that for charge; That would be nice to have a small application which is create a (fake) incoming SMS from the Google Calendar events (including all days event) in a certain (pre-set) time.
Any ideas?
Based from this documentation, Google still sends SMS reminder. However, the are only available for G Suite customers. Requests to set SMS reminders for other account types are ignored. If you are a G Suite customer, you may check this page on how to turn on SMS notifications.
My client requires an sms to be sent to him, whenever an invoice is made on his system by any of the employees. I have no idea how to configure it. Do I need to buy any sms-server service?
How to integrate into my application?
Any help will be highly appreciated.
Thanks
I am not sure what country you are in. But in the UK i use this provider.
They have excellent examples
I can send SMS from my webserver, my Windows .NET Form application, a iPhone app if i wanted to. This is possible because it uses a simple HTTP Request API, so even using JavaScript AJAX from the client will work.
Just search for SMS Gateway and find your countries advisability. Look at a few and decide which one suits your needs and also the costs involved.
My Provider charger per sms.. no signup fees, no contracts, just top up.
Using a mobile phone is more involved, but obviosly it has the benefit that you control every aspect of sending, receiving and processing data.
for example 1, 2, 3
You can even buy a module from china just designed to interface via Serial to send/recieve SMS, and even use the GPRS to get/send HTTP request.
There is two option
1) have to buy service from provider or
2) you have to connect your mobile with pc and send msg using AT command
A lot of carriers will allow SMS via e-mail. This may be a better option for you.
Here is a list of the e-mail address formats for a number of carriers.