Time Out Values And Result Codes; Tips And Tricks For Otap - Siemens TC65 JAVA User Manual

TC65 JAVA User's Guide
Strictly confidential / Draft
9.7

Time Out Values and Result Codes

Timeouts:
• Closedown Timeout: 10 seconds
• Safety Timeout: 5 minutes
Result Codes: Supported status codes in body of the http POST request:
• 900 Success
• 901 Insufficient memory in filesystem
• 902 -not supported-
• 903 -not supported-
• 904 JAR size mismatch, given size in JAD file does not match real size of jar file
• 905 Attribute mismatch, one of the mandatory attributes MIDlet-name, MIDlet-version,
MIDlet-Vendor in the JAD file does not match those given in the JAR manifest
• 906 invalid descriptor
• 907 invalid JAR
• 908 incompatible configuration or profile
• 909 application authentication failure,
• 910 application authorization failure, tried to replace signed with unsigned version
• 911 -not supported-
• 912 -not supported-
All HTTP packets (GET, POST) send by the module contain the phone number or IMEI (if
number not present) of the SIM in the User-Agent field, e.g.
User-Agent: TC65/+4917266666 Profile/IMP-NG Configuration/CLDC-1.1
This is for easy device identification at the HTTP server.
9.8

Tips and Tricks for OTAP

• For security reasons it is recommended to use an SMS password. Otherwise the "delete"
operation can remove whole 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 special server.
• As a side effect, OTAP can be used to simply reboot the module. Just start an OTAP
procedure with a parameter set which does not really do anything, like a delete operation
on a nonexistent directory.
• If you don't want to start OTAP by SMS let your Java application do it by issuing the
at^sjotap command. That triggers a install/update operation as described in chapter 9.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 booked into the network to do OTAP. That means
that either the Java application has to enter the PIN, the PIN needs to be disabled or
Autopin (see AT Command Set [4]) has to be used.
• The OTAP procedure might fail due to call collision, e.g. a incoming call when OTAP tries
to start a CSD connection.
TC65 JAVA User's Guide_V01 Page 46 of 69
s
11.03.2005