Provisioning SoftSIM (and staying provisioned) in production #92
Description
The description below is based on a message I sent to the support team, who opened a ticket on my behalf and requested me to post it here as well.
Context: Losing profile upon re-flashing (external profile)
When re-flashing the device the profile is lost. The documentation in your GitHub repository states that re-provisioning after every flash is not necessary when using a static profile.
However, using a static profile does not seem like a viable solution for my use case. This has to do with the large amount of devices and requirement for remote firmware updates.
If I have to use the static profile to allow the use of the SoftSIM, this would mean creating a firmware upgrade per device instead of allowing groups in the fleet to update at once.
Questions
Now my questions are as following:
- How do other customers of yours handle the provisioning of the SoftSIMs in production (or just a larger-than-development scale)?
- Is it possible to safely store the profile elsewhere on the device?
- How often can I use the same decoded profile for the same device to provision? During the integration of the profile in our existing code I had to re-provision several times and used the same profile each time. Am I correct to compare it to just replugging a physical SIM card?