> 8.8 | Tips and Tricks for OTAP

> • | For security reasons it is recommended that an SMS password be used. Otherwise the ìdeleteî operation can remove entire directories without any authentication.

> • | For extra security, set up a private CSD/PPP Server and set its phone number as a fixed parameter. This way, applications can only be downloaded from one specific server.

> • | As a side effect, OTAP can be used to simply reboot the module. Simply start an OTAP procedure with a parameter set which will not really do anything, such as a delete operation on a nonexistent directory.

> • | If you do not want to start OTAP by SMS let your Java application do it by issuing the AT^SJOTAP command. This triggers an install/update operation as described in Section 8.6.1 but without the SMS part.

> Note: If a malfunctioning Java application is loaded the SM method will still be needed for another update.

> • | The OTAP procedure cannot be tested in the debug environment

> • | Be aware that the module needs to be logged into the network to do OTAP. That means that either the Java application must enter the PIN, the PIN needs to be disabled or Autopin (see [1]) needs be used.

> • | The OTAP procedure might fail due to call collision, e.g. an incoming call when OTAP tries to start a CSD connection.