Time Out Values And Result Codes; Notes - Siemens TC45 User Manual

Cellular engine
Hide thumbs Also See for TC45:
Table of Contents

Advertisement

TC45 TC45 JAVA User's Guide
Confidential / Released

8.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 -not supported-

8.8 Notes

· For security reasons it is recommended to use a SMS password. Otherwise the "delete"
operation can remove whole directories without any authentication.
· For extra security, setup 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 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 booked into the network to do OTAP. That means
that either the Java application has to enter the PIN or the PIN needs to be disabled. To
ensure that you can still do OTAP even, or especially, when the current Java application
does not work properly, disable the PIN during OTAP activities. This might not be
possible in all networks.
· The OTAP procedure might fail due to call collision, e.g. a incoming call when OTAP tries
to start a CSD connection.
TC45_JAVA User's Guide_V02
Page 44 of 72
30.06.2003

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents