Java User’s Guide

8.7 Time Out Values and Result Codes

s

8.7Time Out Values and Result Codes

Timeouts:

•Closedown Timeout: 10 seconds

•Safety Timeout: 10 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, something is wrong with the format of the .jad file

•907 invalid JAR, the JAR file was not available under MIDlet-Jar-URL, files could not be extracted from JAR archive, or something else is wrong with the format of the file.

•908 incompatible configuration or profile

•909 application authentication failure, signature did not match certificate

•910 application authorization failure, tried to replace signed with unsigned version

•911 -not supported-

•912 Delete Notification

All HTTP packets (GET, POST) sent by the module contain the IMEI number in the User-Agent field, e.g.

User-Agent: <productname>/000012345678903 Profile/IMP-NG Configuration/CLDC-1.1

This eases device identification at the HTTP server.

8.8Tips 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 pro- cedure 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.

wm_java_usersguide_v12

Page 61 of 123

2008-02-25

Confidential / Released

 

 

Page 60 Page 62
Page 61
Image 61
Siemens AC65, TC65, XT75, XT65 manual Time Out Values and Result Codes, Tips and Tricks for Otap
Page 60 Page 62

AC65, XT65, XT75, TC65 specifications

The Siemens TC65 is a compact and powerful GSM/GPRS module designed for a wide range of mobile communication applications. With its robust features, the TC65 perfectly meets the growing demands for connectivity in various industries, including automotive, telematics, and industrial automation.

A standout feature of the TC65 is its compact size, allowing it to be easily integrated into various devices without compromising on performance. The module supports GSM (Global System for Mobile Communications) and GPRS (General Packet Radio Service), providing reliable and efficient voice and data transmission.

One of the key technologies incorporated in the TC65 is its integrated TCP/IP stack, which allows for seamless internet connectivity and enables application developers to create IoT solutions with ease. This capability is essential for remote monitoring, data logging, and other applications that require continuous data exchange.

The TC65 also boasts extensive multimedia capabilities, including support for SMS, MMS, and voice calls. This makes it suitable for applications that require not only data transmission but also communication features. Additionally, it supports various codecs for voice compression, ensuring high-quality audio in voice applications.

Enhanced security features are another highlight of the TC65. It incorporates comprehensive security protocols to safeguard data transmission, making it suitable for sensitive applications in finance, healthcare, and other critical sectors. The module also includes an integrated SIM application toolbox that supports the development of secure and customizable applications.

For developers, the TC65 offers an easy-to-use software development kit (SDK), simplifying the process of application development. This means that businesses can quickly create and deploy solutions tailored to their specific needs.

The module operates across a wide voltage range and is designed to tolerate challenging environmental conditions, making it ideal for industrial use. It supports various interfaces, including UART, GPIO, and I2C, enabling it to connect with a variety of peripherals and sensors, thus expanding its usability.

In summary, the Siemens TC65 combines compact design, versatile communication capabilities, advanced security features, and developer-friendly resources, making it an excellent choice for anyone looking to implement reliable and sophisticated GSM/GPRS communication in their applications. The TC65 is a valuable asset in the evolving landscape of connected devices and IoT solutions.
Top Page Image Contents