overview-summary.html

开源的手机短信开发包！包括例子程序和比较详细的文档

        <br><br>
        <strong>Version 1.2.5 (Compiled packages with JDK 1.4.2 (05))</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Increased initial "wait-for-response" time to 2000ms after connecting in order to allow phone to respond (functionality added for Siemens M50, but may lead to greater compatibility for other phones as well).</li>
                <li><strong>jSMSServer</strong>: Autoforward feature. Each message received may be automatically forwarded to a specific phone number. Extra option "forward_number"is added in configuration file jSMSServer.conf.</li>
                <li><strong>jSMSEngine API - Bug</strong>: When operating in ASCII mode, an empty message could hung the processing of further messages. This bug appeared only in ASCII mode - PDU could handle empty messages fine. This bug was observed from a friend using a Wavecom modem but apparently affects mobile phones as well...</li>
                <li><strong>jSMSEngine API</strong>: Added code for better handling of modem responses when PIN is required.</li>
                <li><strong>jSMSEngine API</strong>: Added special code for Ericsson phones (indications and storage parameters). This should lead to better compatibility with Ericsson devices.</li>
        </ul>
        <br><br>
        <strong>Version 1.2.4 (Compiled packages with JDK 1.4.2 (04))</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Modified code in order to allow both international and local phone numbers as destinations for an outgoing message.</li>
                <li><strong>jSMSEngine API</strong>: Added log capabilities (using JDK's log facilities).</li>
                <li><strong>jSMSEngine API</strong>: Added the command "+++" (switch to command mode) before accessing the phone. This ensures greater compatibility.</li>
                <li><strong>jSMSEngine API - Bug</strong>: When using a phonebook group entry as a destination, the expansion procedure did not retain the original message encoding.</li>
        </ul>
        <br><br>
        <strong>Version 1.2.2</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Delivery notification messages (already stored in mobile's memory) are now ignored, and will not cause any trouble in the operation of the API.</li>
                <li><strong>jSMSEngine API</strong>: Some compatibility issues were risen with the SIM PIN functionality. If the API does not work right for you, just set the SIM PIN to nothing / null. The API will then bypass all the code fragment which handles the SIM PIN request / response, in order to bypass possible compatibitity problems.</li>
                <li><strong>jSMSServer</strong>: The application was showing incorrect statistics about incoming messages.</li>
                <li><strong>jSMSServer</strong>: The automatic reconnect feature was not functioning properly.</li>
                <li><strong>jSMSEngine API</strong>: Minor modification to handle extended characters in incoming messages, like the Euro sign.</li>
        </ul>
        <br><br>
        <strong>Version 1.2.1</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Modified GSM alphabet handling in order to represent some characters which were not handled correctly.</li>
                <li><strong>jSMSEngine API</strong>: The API now supports the alphanumeric representation of the Originator.</li>
                <li><strong>jSMSEngine API & jSMSServer</strong>: Support for providing the SIM PIN code to the GSM device, if this is requested by it.</li>
        </ul>
        This version contains portions of code contributed by <strong>George Karadimas</strong> and <strong>Jose M. Puyal</strong>, who I would like to thank for their time.
        <br><br><br><br>
        <strong>Version 1.2</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Added support for Siemens phones (S55 and ME45 - probably all Siemens phones work like these two). These phones have a different behaviour when they receive an SMS - they save it in their memory (RAM) and not in the SIM card. When jSMSEngine was used with such phones, no incoming messages could be read. Now, when the core engine sees that it has to deal with a Siemens phone, it issues the proper command which sets the memory (RAM) of the phone as the current receiving memory. All Siemens phones should work like that. No user intervention is required. <strong>Many thanks</strong> to <strong>George Karadimas</strong> who pointed out this difference in behaviour, and to <strong>Sebastian Hardy</strong> who was kind enough to help me all the way, by testing the intermediate debug versions of jSMSEngine API with his Siemens phone. This was the most difficult issue to figure out, since I don't have access to Siemens phones in order to do my own testing.</li>
                <li><strong>jSMSEngine API</strong>: Introduced the asynchronous mode of reception. Please have a look at "ReadMessagesAsync.java" example for information.</li>
                <li><strong>jSMSEngine API</strong>: Changed the synchronization between the various callable methods of jSMSEngine, in order to ensure correct operation with the new asynchronous mode of operation.</li>
                <li><strong>jSMSEngine API</strong>: Modified the way SMSC number is defined and used, in order to cover some incompatibilies. There are three ways to define the SMSC number: 1) to define the actual SMSC Number, i.e setSMSCNumber("[phone]"). 2) To set it to empty, i.e. setSMSCNumber(""). 3) 2) To set it to null, i.e. setSMSCNumber(null). <b>Please note</b> that each case creates a different PDU block when sending messages, which may or may not be accepted by your phone. If you have trouble sending messages, try all three ways to see which one works with your specific model. This special behaviour was first observed during tests with a Siemens S55, which needed the "empty" call to work.</li>
                <li><strong>jSMSServer</strong>: Fixed the following bug: When the database link is active, any outgoing messages were dispatched correctly but were not shown on the jSMSServer window.</li>
                <li><strong>jSMSServer</strong>: Fixed the calculation regarding the display of signal strength which was wrong.</li>
        </ul>
        <br><br>
        <strong>Version 1.1.3</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: There was a nasty bug which was seen <strong>only</strong> during PDU mode and <strong>only</strong> for countries where mobile phones have an odd number of digits. Under these two specific circumstances, no messages could be sent, and all incoming messages were missing the last digit from the originator's number. This bug did not appear when working under TEXT mode in these countries, or for countries having an even number of digits in their phone addressing. There was an error in the way address fields were encoded / decoded in / from PDU format. <strong>Please note</strong> that I have made every effort to fix this bug, however I have not done a real test, since here in Greece, numbers are even. So, <strong>please test it</strong> if you leave in a country where mobile phones have an odd number of digits.</li>
                <li><strong>jSMSServer</strong>: There are some minor changes made, regarding the stability of the jSMSServer. Once connected to a GSM device, jSMSServer will always try to reconnect during each refresh cycle, even if there was a fatal error in the previous refresh cycle, which caused the serial communication to drop. This helps jSMSServer to work continously and unattended, overcoming any errors during its operation.</li>
        </ul>
        <br><br>
        <strong>Version 1.1.2</strong>
        <br>
        <ul>
                <li><strong>jSMSEngine API</strong>: Increased the timeout period for the serial driver to 30 seconds (was 15 secs).</li>
                <li><strong>jSMSServer</strong>: *BUG SOLVED* There was an error in the way the service was initialized, and if you had your GSM mobile / modem connected to a port other than COM1, the connection would never be established. This bug was due to the way jSMSEngine was coded, and did not affect the API package, or the other examples.</li>
                <li><strong>jSMSEngine API</strong>: *BUG SOLVED* There was an inconsistency in the way the SMSC number was initialized by the API library. This caused errors, unless you specifically set the SMSC number to null. This bug did not appear during jSMSServer operation. This bug affected the PDU operation. This bug was also solved in <strong>Maintenance Release #1</strong>.</li>
                <li><strong>jSMSEngine API</strong>: *BUG SOLVED* There was a bug in jSMSEngine API which caused responses from the GSM device to be ignored. Due to that, some outgoing messages were not dispatched. This bug did not appear during jSMSServer operation. This bug affected the PDU operation. This bug was also solved in <strong>Maintenance Release #1</strong>.</li>
        </ul>
        <br><br>
        <strong>Version 1.1</strong>
        <ul>
                <li><strong>jSMSServer</strong>: This version of jSMSServer requires some changes in its configuration file. It should be used only with jSMSEngine v1.1 API. Please look at the README.txt and CHANGES.txt file in jSMSServer distribution directory for latest information.</li>
                <li><strong>API</strong>: The big change is that the API now <strong>supports PDU mode</strong>, as well as the older ASCII mode. When you operate in PDU mode, you also get support for sending and receiving 7-bit (GSM Default Alphabet for now), 8-bit or UNICODE messages. The operation is transparent - all you have to do is to set the operation mode by using CService.setOperationMode(). Default is 7-bit.</li>
                <li><strong>API</strong>: You need to define a "cache" directory. This is an existing directory which will be used from jSMSEngine API for his own use. This directory is defined with CService.setCacheDir(). If you don't define a cache directory, the API will not work (will not connect). Make sure that you don't have any valuable files in the cache directory.
        </ul>
        <br><br>
        <strong>Version 1.0</strong>
        <ul>
                <li><strong>jSMSServer</strong>: Converted the old jSMSEngine GUI Application (now called jSMSServer) in order to take advantage of the new API package. Some modifications were inevitable - please see the relevant jSMSServer.txt file</li>
                <li><strong>API</strong>: The AT+CNMI command is used in order to disable indications of arrived messages. This setting is needed for some GSM modems (i.e. Wavecom) which send indications to TE by default.</li>
                <li><strong>API</strong>: Some methods of CMessage class and descendants changes place (for example, setRecipient() is now found in COutgoingMessage() and not CMessage()).</li>
                <li><strong>API</strong>: Some modifications are made in the GSM alphabet - some characters were interpreted wrong.</li>
                <li><strong>API</strong>: The constructor of COutgoingMessage class <b>does not</b> take a date as parameter.</li>
                <li><strong>API</strong>: Changes some method from private/protected to public.</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 v1.2.7</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>