overview-summary.html

gsm modem 发送短信 闪信 WAP PUSH开发包

                <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>
<P>

<P>
<HR>


<!-- ======= START OF BOTTOM NAVBAR ====== -->
<A NAME="navbar_bottom"><!-- --></A>
<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
  <TR ALIGN="center" VALIGN="top">
  <TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> &nbsp;<FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="org/jsmsengine/package-summary.html"><FONT CLASS="NavBarFont1"><B>Package</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <FONT CLASS="NavBarFont1">Class</FONT>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="overview-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A>&nbsp;</TD>
  <TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1">    <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A>&nbsp;</TD>
  </TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
<strong>jSMSEngine API v2.0.9</strong><br><strong>Web:</strong><a href=http://www.jsmsengine.org>http://www.jsmsengine.org</a></strong></EM>
</TD>
</TR>

<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
&nbsp;PREV&nbsp;
&nbsp;NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
  <A HREF="index.html?overview-summary.html" target="_top"><B>FRAMES</B></A>  &nbsp;
&nbsp;<A HREF="overview-summary.html" target="_top"><B>NO FRAMES</B></A>  &nbsp;
&nbsp;<SCRIPT type="text/javascript">
  <!--
  if(window==top) {
    document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
  }
  //-->
</SCRIPT>
<NOSCRIPT>
  <A HREF="allclasses-noframe.html"><B>All Classes</B></A>
</NOSCRIPT>


</FONT></TD>
</TR>
</TABLE>
<A NAME="skip-navbar_bottom"></A>
<!-- ======== END OF BOTTOM NAVBAR ======= -->

<HR>

</BODY>
</HTML>