Latest News

Hi all,

A database problem has been identified which has forced me to temporarily disable the forum.
For the time being, please use the old SMSLib User Group until I sort things out.

Thanks.

This is an initial review of my latest USB modem.

I needed to see how these $20 devices work, as they are a pretty cheap alternative to a real gsm modem. So I bought one. I shopped from Deal Extreme. First time, everything went ok. Order arrived in Greece after a couple of weeks - I was prepared for this delay, as they use standard post. Package was stamped as "sample".

I purchased this device.

Don't expect much from the packaging or the modem. I've managed to insert the SIM correctly after trying a couple of times. There is no manual or anything, no brand and the label just reads "EDGE MODEM"... LOL!

Installation on my Win XP machine:

1) Plug the USB.
2) Wait for the driver to install.
3) Don't run the setup! If it runs by itself, cancel it!
4) Reboot as instructed.
5) The USB appears as a normal USB storage device.
6) Run the setup in order to install the modem drivers.

Mine appeared as COM5. It identified itself like this:

Modem Information:
Manufacturer: HOJY
Model: WYLESS_600
Serial No: 353036025712340
SIM IMSI: ** MASKED **
Signal Level: -71 dBm
Battery Level: 100%

I used the default HUAWEI handler, i.e.:

new SerialModemGateway("modem.com1", "COM6", 115200, "Huawei", "");

The good thing is that this cheap device plays OK! I've managed to send and receive messages without problems. The inbound notifications don't work, but I will examine it further.

Of course, I cannot give any feedback about the stability of the device in long running applications. I just played for a couple of hours and, for what's worth, it seems good enough.

Hi all,

Here is the fix for the previously reported bug - a really important bug that leads to message loss with mathematical accuracy. You are advised to fix this manually ASAP. The same fix can be applied to v3.4.6 as well.

• Edit ModemGateway.java file.
• Locate the checkMpMsgList(msgList) call inside the readMessagesPDU() method.
• Add the following lines:

List tmpList;
for (int k = 0; k < this.mpMsgList.size(); k++)
{
    tmpList = this.mpMsgList.get(k);
    tmpList.clear();
}
mpMsgList.clear();

For more information, check this revision.
If you follow the SMSLib repository, just update to revision r2303.

An official new release will of course, follow shortly.

While checking a user bug report, I've discovered something really worrying that may lead to data (i.e. message) loss. The actual cause of this problem has not (yet) been identified, but since data loss was observed, a formal warning is in order:


I've observed this a couple of times without being able to trace down the reason.

In case you have implemented the orphaned part notification method, you are advised to remove the callback handler ASAP.

You can follow the progress on this issue on the relevant Issue Tracker Ticket. More information will also be posted on the blog.