Is it possible, I can receive a verification code from an external app/website page using my twilio free number... as a trial account user.
I haven't tried the process either, I'm believing I could be able to verify a telegram account, having received the verification code using my twilio free number
Related
I try to send SMS with Twilio account.
The program run as well, returning the status "queue" - but in the Twilio dashboard I see nothing. (any list of SMS messages.)
Does anyone know how to solve this?
For some reason, the SMS was not sent. After sending, the dashboard is updated immediately and you can see all the messages sent.
The problem may have been that I was not an administrator in the account. I opened a new account and the sending was immediately successful.
Is there a way to unverified a verified number in firebase account (phone authentication)?
There is more than two days I am trying to find a way to resend SMS code, in react-native-firebase but unfortunately I couldn't find a solution for that.
Now I think if I unverify a number or unauthenticate a number I maybe able send the SMS code again.
because as I tested firebase only send SMS code to unverified or unauthenticate number
As far as I know there is no way to set the phone number of a user account to unverified within the Firebase Authentication API. You may want to file a feature request for this.
Re-sending the verification code definitely isn't going to result in the account becoming unverified.
We tried to use the StackDriver Error Reporting notification features, but it seems that for any Project, when we turn on the notification, it always sent to the email associated with the developer account that we logged in. How can we change it to a different email account. (we use PageDuty, and we want this notification to send to a pagerduty sink email account)
Today, email notifications on new errors for a given project are enabled per user and can only be delivered to the email associated with his user's account.
As a workaround, and if possible, you could setup an email filter that would forward these emails.
I am the Stackdriver Error Reporting product manager.
It is not the first time we hear this feedback and we are working on improving the situation.
Is the Phone Verification API just a wrapper around TOTP to simplify the process, or are they meant for entirely different use cases?
Authy developer evangelist here.
The Phone Verification API is useful for one off verifications by SMS or a phone call. Great if all you need to do is make sure your user owns the phone number they have entered. You can read my write up of how to implement phone verification in Rails if you want to see more.
The TOTP API returns an Authy ID that you can then save and use to send verification codes to your user as part of the 2FA flow. When you then send the verification code to a user, Authy works out whether they have the Authy app or not and sends either a push notification or an SMS.
It's basically the same technology, however the TOTP case is a bit more complicated and intended for repeated uses.
I also wrote up how to implement TOTP 2FA with Authy and Rails if you want to see details on that.
Does that help at all?
I am using Twilio to send SMS to targeted phone numbers in my web app(which I am developing in asp.net). Twilio SMS is not being delivered to target phone numbers but its status is sent in my twilio account log. One more thing, when I send SMS to the number on which I activate my twilio account, message is delivered to that phone number. Can anyone please help me to sort out this?
Thanks to all who view my question. I solved the problem my self. The issue was by default twilio didn't allowed service for programmable SMS. I checked it to allow to get SMS and voice calls on all numbers.
Just run into this same issue but I've managed to resolve it by removing additional verified phone numbers (i.e. you need only 1 with the trial account).