I succeeded in configuring a Huawei E180 (which is reported by lsusb as ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E230/E270/E870 HSDPA/HSUPA Modem) for receiving SMS's on Debian 6, and since there was so little documentation of that exact device I decided to share it with you here, even though it really requires nothing too special.

Smstools config:
devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked incoming = /var/spool/sms/incoming logfile = /var/log/smstools/smsd.log infofile = /var/run/smstools/smsd.working pidfile = /var/run/smstools/smsd.pid outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent stats = /var/log/smstools/smsd_stats [GSM1] init = AT device = /dev/ttyUSB0 incoming = yes pin = 0000 report = yes

In addition, it seems that the device presents itself as a mass storage device and only secondarily as a modem. This is why you also need to install the package usb-modeswitch, and after that (re-)connect your device and (re-)start the sms service with the command

# /etc/init.d/smstools restart

That was actually it, it seems to be working for me. Hope it's useful for you.

For the Huawei E1552, I found it necessary to add

memory_start = 0

to the config to receive SMS. The symptoms are in the log a servies of mesaages like

GSM1: Command is sent, waiting for the answer GSM1: <- +CPMS: "SM",1,30,"SM",1,30,"SM",1,30 OK GSM1: Used memory is 1 of 30 GSM1: Trying to get stored message 1 GSM1: -> AT+CMGR=1 GSM1: Command is sent, waiting for the answer GSM1: <- OK GSM1: Trying to get stored message 2 GSM1: -> AT+CMGR=2 (repeats for AT+CMGR=3 to AT+CMGR=29 then) GSM1: Trying to get stored message 30 GSM1: -> AT+CMGR=30 GSM1: Command is sent, waiting for the answer GSM1: <- +CMS ERROR: 321 (Invalid memory index) GSM1: No SMS received (reading interrupted)

which then repeats forever. SMSTools is looking inb slots 1 - 30, but the message is in slot zero. The configuration noted above sets the search to beging at slot zero, and then it works.

Aslo,

signal_quality_ber_ignore = yes

will reduce log clutter.