Hi David,
No, they were sent to CI with the country code prefix +. The number is entered in the CIV user profile with the prefix and fetched from there by the client. I wonder why is it showing you without the prefix...
I tried again just now with the following results:
First attempt: SMS received
Second attempt: SMS received
Third attempt: SMS not received. The correlation (4-digit prefix) was: 5084 (screenshot attached, you can see the number with +)
Can you please check for this one as well that it got successfully delivered from your SMS service provider or not? I would really appreciate and then think about how to trace it further, and meanwhile try sending to other numbers to see if it is a carrier problem with this number specifically. We use this scenario with CIV in our ISAM demonstrations to clients that's why it has to be reliable, so trying to figure it out..
Regards,
------------------------------
Jahanzaib Sarwar
------------------------------
Original Message:
Sent: Wed August 07, 2019 09:10 PM
From: David MOORE
Subject: IBM CIV Issue in SMS OTP
Hi Jahanzaib
We've been able to track down two instances of that phone number. Both on the 29th July and both were reported as successfully delivered by our SMS provider. We don't have the ability to track beyond that since this moves into the realm of the mobile phone number carrier. The logs reported the phone number without the "+" prefix for the country code. Was it sent to CI without the "+"?
------------------------------
David MOORE
Original Message:
Sent: Mon August 05, 2019 02:07 AM
From: Jahanzaib Sarwar
Subject: IBM CIV Issue in SMS OTP
Hi David,
Ok, but using a smart phone as an SMS gateway, I haven't encountered such issue, so I don't know whether it could be due to mobile carrier or not. Sure, the tenant name is js.ice.ibmcloud.com and the failing mobile number is +923345026062.
Best regards,
------------------------------
Jahanzaib Sarwar
Original Message:
Sent: Tue July 30, 2019 05:18 PM
From: David MOORE
Subject: IBM CIV Issue in SMS OTP
Hi Jahanzaib
The SMS issue described has been observed on occasion. There can be many causes. Sometimes it can be caused by an issue with the mobile carrier. Are you able to share your tenant name and perhaps an example or two of the failing mobile phone numbers?
------------------------------
David MOORE
Original Message:
Sent: Tue July 30, 2019 07:43 AM
From: Jahanzaib Sarwar
Subject: IBM CIV Issue in SMS OTP
Hello All,
We are exploring CIV 2FA capabilities and have developed a client that is using CIV to provide second factor authentication. The client uses CIV APIs for Email/SMS/Verify Push. All authentication mechanisms are working perfectly fine except SMS OTP. The SMS OTP is not always received. Some of the times the correlation (4-digit prefix code) is generated but the OTP is never received on the SMS.
What could cause this behavior? Has anyone else also experienced this with CIV?
Best regards,
------------------------------
Jahanzaib Sarwar
------------------------------