Java SMPP API News

The smppapi is now included in the Maven2 central repository. You can add it as a dependency in your POM with

<dependency>
<groupId>com.adenki</groupId>
<artifactId>smppapi</artifactId>
<version>0.3.7</version>
</dependency>

Note that the groupId is "com.adenki" and not "ie.omk", though the package names are still "ie.omk.smpp" for the 0.3.7 release, as they will be for any further releases in the 0.3.x branch.... read more

I have made a bug-fix release of the smppapi to close off some bugs that have been outstanding for a while. List of closed bugs is in the release notes for the release.

oran

I have removed 0.3.5 from the file releases section as some code errant code I had been testing with was released with it causing some bad problems.

My apologies to all. I will try to get the 0.3.6 release up as soon as is possible.

I've released a minor revision of the API. It contains a number of fixes for some bugs that have been open a while (check the release notes for which ones).

A quick update on latest changes in CVS.

1. Implemented a new bind timout feature in asynchronous comms. [see RFE #821700]

2. Fixed a number of bugs - search for open bugs in the fixed state to see which ones.

3. Moved to the Jakarta commons logging API. Internally, the project now uses commons logging calls. So you're no longer tied to configuring log4j for the API if your application uses something else. Course, you can continue to use log4j same as before if you like.... read more

Bug fix release of some long-fixed (and some recent) bugs.

I have done a small release of the API. It fixes the bug many of you have reported where space characters were turning up as @ signs (bug id 635415). I've also added an alphabet encoding class which supports the HPRoman8 character set.

oran

The problem many of you have been having with space characters turning up as '@' on your mobile devices has been fixed and checked into CVS. It was a problem with the DefaultAlphabetEncoding class.

I have also added a new character encoding class: HPRoman8Encoding. Hope this helps with those of you connecting to SMSCs running on HP-UX which are using this encoding format by default.

Bug reports and the like to the usual locations...... read more

Version 0.3.1 has been released. Fixes a couple of important bugs that were logged against 0.3.0. Also adds a new event dispatcher framework.

Only about a year late, but version 0.3.0 has finally been posted. Should be appearing in the download area real soon.

This version now supports SMPPv3.4, though v3.3 remains the default version in use.

Please, post any bug reports you have to this site using the bug tracker. Use the support tracker to ask for help using the API and post all your flames for breaking applications to the discussion forums. :-)... read more

I'm looking to get some feedback from users of the API about the implementation of optional parameters which I need to get done Real Soon. Most other SMPP3.4 features have been done but optional parameters remain. I have opened a
discussion thread in the 'smpp-v3.4' discussion forum titled 'Optional parameters support'. Head on over, read the web page (link is posted in
the article) and submit your opinions! The forum is over at
http://sourceforge.net/forum/forum.php?thread_id=661302&forum_id=107330

I will shortly begin checking in a slew of changes I've been working on which add the initial stages of SMPP v3.4 support. As well as adding functionality, some internals of the API have been shifted around and there's some externally visible changes. As a result, these changes will lead to a version 0.3.0 release of the API.

A quick summary of what will be checked in:

• Support for Optional parameters (TLVs)
• Support for the bind_transceiver connection type.
• Support for the data_sm message.
  I'll be looking for people to test the new functionality soon as I'm done with my unit testing. If you're interested, please drop me an email!... read more

Well, it's been a long break and all's been silent here at the smppapi project. However, the holidays are over and work shall recommence. Expect lots of updates over the month of January as some fairly aggressive coding is happening on my part. Fancy helping me out...? :-)

I have uploaded a .tar.gz file of my working tree which contains a new event framework for the API. The tar file can be downloaded from http://smppapi.sf.net/smpp-09122001.tar.gz

Please download the new version and review and comment on it. There is a discussion thread started for it in the Open Discussion forum or post any comments to orank@users.sf.net.

oran

This release fixes the performance problems in 0.2.4. If you're using version 0.2.4 I suggest you upgrade to this version asap. There's a few internal interface changes too but nothing that applications would be using.

Some externally visible interfaces have been deprecated in SmppTransmitter (ones that use the MsgFlags class). See the home page for more information on deprecated methods.

oran

Version 0.2.4 of the API has been released. It is identical to 0.2.4-rc2 so if you've already downloaded that version, there's no need to re-download!

oran

I'm currently in 'getting feedback' mode for the 0.2.4 release...there are tar files available for download from the homepage which I'm calling 'release candidates' (for want of a better term!) of version 0.2.4 of the API. Problems fixed:
o The message encoding problem.
o SmppConnection sending/receiving multi-
threading issues cleaned up.
o SmppConnection run method re-written.

Give the new version a try and send any feedback you have to orank@users.sf.net (or post it to the discussion forums!)

New file release has been posted...version 0.2.3. See http://smppapi.sf.net for details.

Bug 450439 was not fixed in 0.2.1 like it should have been. Release 0.2.2 is just 0.2.1 with a fix for that bug.

New exceptions that derive from SMPPException.
Identify what went wrong!

Bugs fixed! We now convert from bytes to integers
and back properly (Doh!). And no more
NumberFormatExceptions on messageId's.

Tests. There is now a tests/ sub-directory with
some very simple test classes for
verification. Please...if anyone has any other
test classes/cases they've written, send 'em in to
me!

Sequence numbering is now logical. You, the
developer, can send SMPP packets without worrying
about calling currentPacket or nextPacket. You
still have to construct a packet with a sequence
number but it doesn't have to be valid. The
SmppConnection.sendRequest method will kindly fill
in the next sequence number for you. The SMPP
packet classes will soon have no-argument
constructors for your programming pleasure!... read more