2023-12-08 06:25 AM
Hello,
After having purchased a B-L462E-CELL1 eval kit with pre-provisioned Truphone eSIM and having followed the UM2743 eSIM activation steps, I still don't see the eSIM marked as activated on the Truphone IoT Dashboard after one day.
Truphone support contacted, but no efficient help as of now.
Do you have any returns about such user experience concerning B-L462E-CELL1 and Truphone ?
Solved! Go to Solution.
2023-12-12 12:12 AM
Thanks for your answer, Kaouthar.
But I had already checked that Truphone was the right operator, so It wasn't the cause of the issue.
The thing is that Truphone IoT platform didn't activate the eSIM, despite the respect of the activation procedure.
After having finally managed to reach the Truphone technical support, they eventually resolved the issue and activated the SIM.
2023-12-11 04:48 AM
Hello @EAlai.1 ,
Please try to follow the steps described in this wiki page "Cellular X-CUBE-CELLULAR How To" and precisely in 1.2.13How to activate the eSIM with B-L462E-CELL1 Section.
I hope this help you to solve the issue.
Thank you.
Kaouthar
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2023-12-12 12:12 AM
Thanks for your answer, Kaouthar.
But I had already checked that Truphone was the right operator, so It wasn't the cause of the issue.
The thing is that Truphone IoT platform didn't activate the eSIM, despite the respect of the activation procedure.
After having finally managed to reach the Truphone technical support, they eventually resolved the issue and activated the SIM.
2023-12-12 12:23 AM - edited 2023-12-12 12:27 AM
Hi @EAlai.1 ,
Glad to know that the issue is solved
Thanks for sharing the solution, it might help community member who have the same problem.
Thank you for your contribution.
Kaouthar
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-03-19 07:56 AM
Probably having exactly the same issue, which email did you use to contact them?