Closed GoogleCodeExporter closed 8 years ago
Original comment by team.m...@gmail.com
on 30 Oct 2014 at 4:54
I didnt understand what u meant by duplicate???
Pls give more light on this.
Regards
vishal
Original comment by visha...@gmail.com
on 31 Oct 2014 at 10:17
Hello,
The similar issue is answered here,
https://code.google.com/p/missed-call-otp/issues/detail?id=8&can=1
Additionally, As you are saying it is particularly observed on Reliance and
Idea networks. So I suspect, Operator identifies the CALLER ID sent by mOTP as
invalid.
The reason might be,
1. mOTP sends a missed call otp with 10 digit code starting with '1'
2. Operator would identify it to be a 'USA' phone number
3. But also sees the expected number of digits for a USA number is not met (
expects 11 digits but mOTP sends 10 digits ) and hence drops the call.
I would recommend a mOTP dedicated instance in this case to evaluate the use
case, where we can help you configure the mOTP format for R&D.
http://www.dial2verify.com/corp/Pay/mOTP
Original comment by rahc...@gmail.com
on 31 Oct 2014 at 3:14
Original issue reported on code.google.com by
visha...@gmail.com
on 30 Oct 2014 at 9:27