9 thoughts on “best practice for DE910 provisioning”
Hi,
I’m looking for the best practice for DE910 provisioning sequence for Verizon network. I’ve already been looking to the Software User Guide provisioning section but my question is :
Should I do the OTASP provisioning session each and every time I power up the module? Because once it is done, we don’t NEED it anymore.
Is there a command which would tell me it has been done already? I’ve seen the Current Lock Status of the MODEM command. Is it the right one? Is there a better one?
Thanks
Phil
Hi,
No need to perform the OTASP session every time you power up. Just the first time.
Make sure you also perfom the DMU key update as part of your OTASP procedure the first time you power up. Issue at#cgact=1,1. This is described in the SW User’s guide, so you have most likely already seen that.
You can check at#modem? after the OTASP session. If the MDN (phone number) is present, your modules has been provisioned.
BR,
Rose-Marie
Thanks for the reply,
Even if it is not supposed to happen, I didn’t think about the MDN because doing some test with Verizon, we asked them to reset our registration in their servers and the MDN was still there after even though I wasn’t able to connect. I need to do the provisioning again even if the MDN is present.
As I said, it is not supposed to happen in normal life situation but we need to keep that in mind.
Phil
Is at#cgact the same as at#sgact ?
Is this command (activating the PDP context) necessary when provisioning with a voice only plan?
Steve O.
Hello Steven,
For activating PDP context you just need to use at#sgact.
at+cgact is not supported in the DE910.
Let us know if you have any further questions.
Cheers
Nick
2nd part – "Is this command (activating the PDP context) necessary when provisioning with a voice only plan?"
To put it another way, in addition to performing the OTASP, is the DMU (key update) a required part of provisioning a voice only (no data) plan? Or is it only required to provision for data (IP) use?
Steve O.
Hello Steven,
2nd part – "Is this command (activating the PDP context) necessary when provisioning with a voice only plan?"
No
To put it another way, in addition to performing the OTASP, is the DMU (key update) a required part of provisioning a voice only (no data) plan? No
Or is it only required to provision for data (IP) use? Yes to get DMU Key you have to do sgact.
Cheers
Nick
I’ve a similar problem. The documentation indicates not to run provisioning every time. How do you know if provisioning has already run? I tried AT#MODEM? but that takes a long time to return when run first.
My general sequence is :
Send AT+CREG?
Wait for +CREG: 0,1 or +CREG: 0,5 (usually get several +CREG: 0,0 first)
Send AT#MODEM?
Wait for #MODEM: , …..
IF NOT Run Provisioning
The system generally times out before #MODEM: returns.
When it finally returns it is correct.
If run without AT#MODEM? provisioning seems to work OK.
What am I doing wrong?
Hello Charles,
You can check with two ways.
AT#MODEM?
For this command you will check to see if the MDN and MSID is set
And
AT$QCMIPGETP
For this command you will check the Share Secrets are set. They will be unset if not provisioned.
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
Hi,
I’m looking for the best practice for DE910 provisioning sequence for Verizon network. I’ve already been looking to the Software User Guide provisioning section but my question is :
Should I do the OTASP provisioning session each and every time I power up the module? Because once it is done, we don’t NEED it anymore.
Is there a command which would tell me it has been done already? I’ve seen the Current Lock Status of the MODEM command. Is it the right one? Is there a better one?
Thanks
Phil
Hi,
No need to perform the OTASP session every time you power up. Just the first time.
Make sure you also perfom the DMU key update as part of your OTASP procedure the first time you power up. Issue at#cgact=1,1. This is described in the SW User’s guide, so you have most likely already seen that.
You can check at#modem? after the OTASP session. If the MDN (phone number) is present, your modules has been provisioned.
BR,
Rose-Marie
Thanks for the reply,
Even if it is not supposed to happen, I didn’t think about the MDN because doing some test with Verizon, we asked them to reset our registration in their servers and the MDN was still there after even though I wasn’t able to connect. I need to do the provisioning again even if the MDN is present.
As I said, it is not supposed to happen in normal life situation but we need to keep that in mind.
Phil
Is at#cgact the same as at#sgact ?
Is this command (activating the PDP context) necessary when provisioning with a voice only plan?
Steve O.
Hello Steven,
For activating PDP context you just need to use at#sgact.
at+cgact is not supported in the DE910.
Let us know if you have any further questions.
Cheers
Nick
2nd part – "Is this command (activating the PDP context) necessary when provisioning with a voice only plan?"
To put it another way, in addition to performing the OTASP, is the DMU (key update) a required part of provisioning a voice only (no data) plan? Or is it only required to provision for data (IP) use?
Steve O.
Hello Steven,
2nd part – "Is this command (activating the PDP context) necessary when provisioning with a voice only plan?"
No
To put it another way, in addition to performing the OTASP, is the DMU (key update) a required part of provisioning a voice only (no data) plan? No
Or is it only required to provision for data (IP) use? Yes to get DMU Key you have to do sgact.
Cheers
Nick
I’ve a similar problem. The documentation indicates not to run provisioning every time. How do you know if provisioning has already run? I tried AT#MODEM? but that takes a long time to return when run first.
My general sequence is :
Send AT+CREG?
Wait for +CREG: 0,1 or +CREG: 0,5 (usually get several +CREG: 0,0 first)
Send AT#MODEM?
Wait for #MODEM: , …..
IF NOT Run Provisioning
The system generally times out before #MODEM: returns.
When it finally returns it is correct.
If run without AT#MODEM? provisioning seems to work OK.
What am I doing wrong?
Hello Charles,
You can check with two ways.
AT#MODEM?
For this command you will check to see if the MDN and MSID is set
And
AT$QCMIPGETP
For this command you will check the Share Secrets are set. They will be unset if not provisioned.
Cheers
Nick