Having the OTP field global in the file is no recommended and not a good implementation. Imagine two users request otps. The first user's OTP will be overwritten by the last user and they will receive invalid otp. Now scale that up to a mass production application. It becomes randomic if you will be able to validate or not. The good approach should be to create an otp field for each user and save the value there. Then, we the user enters the otp, you match the value from that particular user's otp field.
Following same process. I receive OTP to my mobile number which is also in Twilio account. but when i enter other's number they are not getting OTP [ RestException [Error]: The number is unverified. ] err is coming. What to do?
@@TechnicalRajni but for this we have to add sender which sender you use phone number? or alpha sender can you explain setup for this i am not geting sms in mobile after adding messagingservicesid
With this aproach you don't avoid Toll Fraud... If anyone find this route and send multiple requests do signup with fake numbers, you will spend a fortune in SMS.
@@TechnicalRajni But if it is a signup route, the user is not yet registered, the user needs to confirm the phone number to conclude the registration and then authenticate in the application. So in this case, one approach would be to add some rate limiter validation to prevent the user from sending multiple SMS in a short time interval, create a blacklist with the user's Public IP, add a CAPTCHA in the front-end, and even send a unique token along with your app request to identify that the request comes from your app and not from some other server or VPN.
Having the OTP field global in the file is no recommended and not a good implementation. Imagine two users request otps. The first user's OTP will be overwritten by the last user and they will receive invalid otp. Now scale that up to a mass production application. It becomes randomic if you will be able to validate or not. The good approach should be to create an otp field for each user and save the value there. Then, we the user enters the otp, you match the value from that particular user's otp field.
That's is good i also do that way it's just a demo for the implementation
twilio trial account can send otp to verified numbe what about remaining numbers??
payment karna padega
this working to masive users?
EXAMPLE
where did you get the message service id
Twilio dashboard account
Following same process.
I receive OTP to my mobile number which is also in Twilio account.
but when i enter other's number they are not getting OTP
[ RestException [Error]: The number is unverified. ] err is coming.
What to do?
In the test account this is the issue I think
does any body got the code file?
Is Twilio SMS gateway free? Where can I find its pricing?
Not free
charges?@@TechnicalRajni
Means plzzz make a whole process video
Its not complete
@@TechnicalRajni but maam iam getting error I have written same code as shown in the video
@@TechnicalRajni I think I am getting mistakes in file and module exporting plzzz help me it's urgent
@@SSCODanish file names and ping me on my email ☺️
to : I placed that req.body.number. but OTP is generated but not show on msg in my OTP.
check the error or add error handling
How to get messagingSeviceSid
Check your settings
Which option
check my twilio videos you will find how to get
Plzzz share whole process
i am not getting the point please explain what do u need
Bro they give me error
Send me screenshot
messagingservicesid how to get it
From twilio account
@@TechnicalRajni but for this we have to add sender which sender you use phone number? or alpha sender can you explain setup for this i am not geting sms in mobile after adding messagingservicesid
@@patelmonil7649 that is twilio settings
@@patelmonil7649 I faced same issues
Man, you just made a video without sharing or showing the main code, ?????????? seriously????????
No that's not possible 😔 definitely I show the code 😔 I will review the video again
Can you share the code ?
I will share some specific files from which u are getting issues
dont use its useless twilio trail account only sent sms to verified number which is yours only ,i wasted my time
@@yashvijaybombale6896 but if someone wants to use they can
With this aproach you don't avoid Toll Fraud... If anyone find this route and send multiple requests do signup with fake numbers, you will spend a fortune in SMS.
Then please add authentication to it
@@TechnicalRajni But if it is a signup route, the user is not yet registered, the user needs to confirm the phone number to conclude the registration and then authenticate in the application. So in this case, one approach would be to add some rate limiter validation to prevent the user from sending multiple SMS in a short time interval, create a blacklist with the user's Public IP, add a CAPTCHA in the front-end, and even send a unique token along with your app request to identify that the request comes from your app and not from some other server or VPN.
I have also one idea to use aws cognito to enhance the security
put the code link brother
please do ping me on my email
Is this free?
Some credit free to test after that paid
github link where
???
any issue you are facing