📄 overview.html
字号:
<body>
Documentation pages for <strong>jSMSEngine API</strong>.
<br><br>
jSMSEngine is an API package which will allow you to send and receive SMS messages from your computer and mobile phone or GSM modem.
<br><br>
<strong>Examples applications.</strong>
<br>
In the distribution directory, you will find example applications, which will show you the basics of how to use jSMSEngine API. These are:
<ul>
<li><strong>SendMessage.java:</strong> This example shows you how to connect and send an SMS message from your GSM device.</li>
<li><strong>SendFlashMessage.java:</strong> This example shows you how to connect and send a flash SMS message from your GSM device.</li>
<li><strong>SendMessageWithPorts.java:</strong> This example shows you how to connect and send an SMS message from your GSM device, with the added feature of defining a source and destination port.</li>
<li><strong>ReadMessages.java:</strong> This example shows you how to connect and read messages from your GSM device (synchronous mode).</li>
<li><strong>ReadMessagesAsync.java:</strong> This example shows you how to connect and read messages from your GSM device (asynchronous mode).</li>
</ul>
In the distribution, you will also get <strong>jSMSServer</strong> application. Its a stand-alone application, which makes use of the jSMSEngine API package. It can also be used as a reference application if you want to see and check how jSMSEngine API works. Please read the README.txt and CHANGES.txt in jSMSServer directory for further information.</li>
</ul>
Please, see <a href="http://www.jsmsengine.org" target="_new">http://www.jsmsengine.org</a> for latest information.
<br><br><br>
<center><strong><h2>Revision History.</h2></strong></center>
<strong>Version 2.0.9 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: Code cleanup.</li>
<li><strong>jSMSEngine API</strong>: Added extra thread which calls isAlive() in regular intervals. This is done in order not to allow the physical comm connection to timeout and force a disconnection.</li>
<li><strong>jSMSEngine API</strong>: All method in AT Handlers now synced.</li>
<li><strong>jSMSEngine API</strong>: Fixed delay in disconnection.</li>
<li><strong>jSMSEngine API</strong>: Removed the reset() code (AT+CFUN) from all handlers except Wavecom. It seems it has created many problems.</li>
<li><strong>jSMSEngine API</strong>: Fixed incorrect parsing of Status Report messages (<a href="http://jsmsengine.org/forum/index.php?action=vthread&forum=4&topic=43">Bug Report</a>).</li>
<li><strong>jSMSEngine API</strong>: Added small delay after sending data to GSM device, to allow time for response.</li>
<li><strong>jSMSEngine API</strong>: Complete redesign of GSM Alphabet handling and character encoding routines. Graved and other special characters should work ok. Source code compilation should be smooth in all operating systems, with no need to remove code.</li>
<li><strong>jSMSEngine API</strong>: A new field is added in CMessage, RefNo. RefNo is the SMSC Reference Number which is returned on succesfull dispatch of a message. This value is stored in refNo field (accessed by public method CMessage.getRefNo()). Outgoing messages will set their refNo to the Reference Number returned by your SMSC. Status Report messages will set their refNo to the refNo of the original message sent. This way, a status report message can be matched with a previously dispatched message. Reference Number is not unique, as its values cycle between 1 and 255, but if you combine it with the recipient's number you will get a better "key" information to use in matching a status report message with its appropriate sent message.
<li><strong>jSMSEngine API</strong>: Bug in AT Handler decision code. This affected modem specific AT handlers.</li>
<li><strong>jSMSEngine API</strong>: Classes CMessage, CIncomingMessage, COutgoingMessage, CStatusReportMessage now implement the Serializable interface. <strong>Use this feature with care! There is no guarantee that these classes will not be modified in a future release.</strong></li>
</ul>
<br><br>
<strong>Version 2.0.8 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: The CService code for selecting the appropriate AT handler has changed from the arcane if-then structure to a more elegant solution based on reflection. Code contributed by Alessandro A. Garbagnati.</li>
<li><strong>jSMSServer</strong>: Modified the structure of the outgoing xml file and added new tags to cater for flash sms, source and destination ports and validity period information.</li>
<li><strong>jSMSServer</strong>: New configuration option, "phone.storage" allows you to set which is the storage your phone uses (MEM or SIM).</li>
<li><strong>jSMSServer (BUG)</strong>: When jSMSServer is set to GUI operation, two CUserThread objects were instantiated (<a href="http://jsmsengine.org/forum/index.php?action=vthread&forum=3&topic=17">Bug Report</a>)</li>
</ul>
<br><br>
<strong>Version 2.0.7 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li>Distributed bandled with Sun Java Comm v2.0 and RxTx as an option. Changed version number in order to avoid confusion.</li>
</ul>
<br><br>
<strong>Version 2.0.6 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: Switched to Regular Expression for parsing GSM responses.</li>
<li><strong>jSMSEngine API</strong>: Status Report Messages: Added DateSent and DateReceived fields processing.</li>
<li><strong>jSMSEngine API</strong>: Modifications in SonyEricsson AT Handler for R380s.</li>
</ul>
<br><br>
<strong>Version 2.0.5 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: <strong>** The project is now distributed under the GPL v2 license **</strong></li>
<li><strong>jSMSEngine API</strong>: <strong>** The distribution contains newly released binaries of RxTx version 2.1.7 for Windows, Linux and Solaris. If you are upgrading from a previous version of jSMSEngine API, please remember to upgrade your RxTx binaries as well! **</strong></li>
<li><strong>jSMSEngine API</strong>: Support for Validity Period setting. COutgoingMessage has a new method, <strong>setValidityPeriod(int)</strong> which sets the validity period in hours. Validity Period is relative, i.e. starts from the time the SMSC received the message.</li>
<li><strong>jSMSEngine API</strong>: Support for receiving multipart (concatenated) messages in 7bit encoding mode. Concatenated messages will be processed and reported as one big message by jSMSEngine API. Note that the process of the concatenated messages takes place in memory, so it *may* be possible to loose messages if jSMSEngine API is shutdown abnormally, during message processing.</li>
<li><strong>jSMSEngine API</strong>: Modified API method <strong>deleteMessage()</strong>. Now, it does not return any status.</li>
<li><strong>jSMSEngine API</strong>: Modifications in CSerialDriver.java for greater compatibility.</li>
<li><strong>jSMSEngine API</strong>: IMSI number is currently masked. You should uncomment the code in CService.java in order for IMSI reporting to work properly. This masking affects jSMSServer, examples and logs generated from the library. Not a bug or anything, but its a good thing to keep your IMSI private :) </li>
<li><strong>jSMSEngine API (BUG: 1424789)</strong>: In some cases, messages sent out were incorrectly encoded and an extra "@" character appeared as the last character at the recipient.</li>
<li><strong>jSMSServer (BUG)</strong>: An exception was thrown when the configuration item "phone.xml_out_queue" was defined but empty.</li>
<li><strong>jSMSServer</strong>: The table for outgoing messages is expected to have a few more fields: flash_sms, status_report, src_port, dst_port & validity_period. The values reflect the attributes of the message to be sent out. See README.txt in jSMSServer directory.</li>
<li><strong>jSMSServer (BUG)</strong>: If configurations items for XML queues were commented out (file jSMSServer.conf) exceptions were thrown, and the application automatically disconnected.</li>
</ul>
<br><br>
<strong>Version 2.0.4 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: Starting from v2.0.4, jSMSEngine relies exclusively on RxTx project for its serial communication implementation. SUN JavaComm will no longer be distributed together with jSMSEngine (this is a relief - I always worried if I did the correct thing distributing SUN JavaComm v2.0...). A good thing is that from now on, there is one distribution file available for both Win32 and Linux installations. This file contains RxTx components for Win32 and Linux. As far as the jSMSEngine is concerned, the code is exactly the same for both platforms.</li>
<li><strong>jSMSEngine API</strong>: A new method of using the ASYNC receive mode has been introduced. Its based on interfaces and listeners. Old method (based on received() subclassing) has been marked depracated. Please review example ReadMessagesAsync.java application.
<li><strong>jSMSEngine API (BUG)</strong>: Minor bug in CService.disconnect() generating errors during ASYNC receive mode.
</ul>
<br><br>
<strong>Version 2.0.3 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: Support for SMS messages with specific port addressing. For each outgoing message, you can define the Source and Destination port. Addressing is in 16bit mode only. Both ports (Source & Destination) should be defined. Please look at the "SendMessageWithPorts.java" example.</li>
<li><strong>jSMSEngine API</strong>: Support for flash SMS Messages. Please note that this kind of messaging is not supported by all phones. It is known to be supported by all Nokia models, a few Siemens and some other brands.</li>
<li><strong>jSMSEngine API</strong>: CIncomingMessage.java: setMessageEncoding() is called for incoming messages, so that the encoding information of the received message is available for these messages as well.
<li><strong>jSMSEngine API</strong>: Some minor modifications were made in CSerialDriver.java class.</li>
<li><strong>jSMSEngine API</strong>: Sony-Ericsson support: Modifications to the original code.</li>
<li><strong>jSMSEngine API (BUG)</strong>: jSMSEngine was leaving unterminated threads during ASYNC operation.</a> solved.</li>
<li><strong>jSMSServer</strong>: Added two configuration parameters "phone.batch_incoming" and "phone.batch_outgoing" which define the maximum number of inbound and outbound messages respectively. Each process cycle will read and send as many messages as these numbers define. Set to -1 for no-limit processing (NOT recommended - may congest GSM link).</li>
<li><strong>jSMSServer</strong>: Added configuration option "general.gui" to enable console mode as well as GUI mode.</li>
<li><strong>jSMSServer (BUG)</strong>: Wrong imports in source code.</li>
</ul>
<br><br>
<strong>Version 2.0.2 (Compiled packages with JDK 1.5.x)</strong>
<ul>
<li><strong>jSMSEngine API</strong>: <strong>Experimental</strong> support for Sony-Ericsson phones. Use "SonyEricsson" as manufacturer string for these modems. Please note that I don't have any SE device to test. I just integrated some code mentioned in the old SourceForge forums from friends who had access to SE models. If you encounter any problems, blame my poor implementation of their findings...</li>
<li><strong>jSMSEngine API</strong>: Bug in AT Hander code: redefinition of private variables. Strange, but this error would not always crash jSMSEngine...</li>
<li><strong>jSMSServer</strong>: New Console mode: When you set configuration option "general.gui=no" then jSMSServer is running in text/console mode. With "general.gui=yes", jSMSServer runs in graphical mode.</li>
</ul>
<br><br>
<strong>Version 2.0.1 (Compiled packages with JDK 1.5.x)</strong>
<br>
Bug fixing release.
<ul>
<li><strong>jSMSEngine API</strong>: API library crashed when used without the debug switch on.</li>
</ul>
<br><br>
<strong>Version 2.0.0 (Compiled packages with JDK 1.5.x)</strong>
<br>
<ul>
<li>This version has undergone some major design changes and it is <strong>NOT</strong> compatible with earlier versions. Key points are noted below:
<ul>
<li>ASCII/TEXT mode is <strong>no longer supported</strong>. Your GSM device must support the PDU mode in order to work. Most modern devices comply with PDU operation, so this won't be a major problem. ASCII mode was seldomly used and it is very problematic.</li>
<li>Most (if not all) methods of the main CService class no longer return error values but make use of exceptions. For this to work, some new exceptions are introduced: <strong>AlreadyConnectedException</strong>, <strong>CannotDisableIndicationsException</strong>, <strong>InvalidPinException</strong>, <strong>NoPduSupportException</strong>, <strong>NoPinException</strong>, <strong>NoResponseException</strong>, <strong>NotConnectedException</strong>. All are descendants of the <strong>jSMSEngineException</strong> exception.</li>
<li>jSMSServer is modified in order to comply with above changes. All of you who use jSMSEngine API in your own applications, should cater for the changes, by modifying your code accordingly.</li>
</ul>
You are kindly requested to move to the new version as soon as possible!
</li>
<li><strong>jSMSEngine API</strong>: Connect() method of jSMSEngine API now takes the manufacturer and model of the GSM device you are using as a parameter. This is closely related to custom AT handlers introduced. Please see bottom of page for more information on this.</li>
<li><strong>jSMSEngine API</strong>: I have added various stability enhancements, error handling, retry-on-error etc. Some features from the era of ASCII mode have been removed and this made jSMSEngine to respond faster. With the latest modifications, my Wavecom seems to run 24/7 for several days (with high traffic volume - some thousands of dispatched messages and tenths of incoming) without interruption.
<li><strong>jSMSServer</strong>: jSMSServer now support Microsoft SQL Server as a database.</li>
<li><strong>jSMSServer</strong>: Database schema has changed a bit: tables are renamed to "sms_in" and "sms_out" instead of "incoming" and "outgoing" respectively.</li>
<li><strong>jSMSServer</strong>: Messages sent are also saved in the database.</li>
</ul>
</body>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -