Hi all,

in case you follow the changelog, you will already have seen this coming: OsmoNITB now has a SMPP interface for submitting MT-SMS.

This is by no means some kind of competition to a more complete SMSC developed by other people on this list, but it was a quick solution to a requirement of a commercial user.

You can use it to submit SMS identifying the recipient subscriber either by his extension or his IMSI. OsmoNITB will also send SMPP ALERT NOTIFICATION in case a previously detached subscriber comes online again. Contrary to the spec, you don't have to subscribe ot ALERT NOTIFICATIONS, but they will be sent to all ESME's registered.

The SMPP interface supports both store-and-forward (via database) as well as forward/transactoin mdoe, where the SMS is attempted for immediate delivery, not buffered and will only send a positive SUBMIT-SM result in case it was acknowledged by the MS.

You can submit both GSM charset as well as binary messages. UCS2 is not tested. multi-part SMS (or anything else using UDH) only works with binary SMS at this point, i.e. GSM alphabet encoded multi-part messages are broken.

The interface will soon be extended to also cover MO-SMS, where you would configure a given destination address by VTY and then messages to that address would be forwarded to the ESME.

Only SMPP 3.4 is currently supported. You will need libsmpp34 from git://git.osmocom.org/libsmpp34.git and need to build openbsc with '--enable-smpp'

Regards, Harald