Operating system name and version: linux fedora 9 (2.6.27.25-78.2.56.fc9.x86_64)
Version of smsd: 3.1.12
Smsd installed from: sources
Name and model of a modem / phone: Huawei e160e
Interface: USB

Does missed call work with Huawei E160E ? Would anyone here know?

I do not know about E160E, but with E1552 missed calls are not supported because there is no "MC" memory available.

I assume that you do not yet have E160E, but if you have (or someone else has and is willing to check this and share the information), use the modem setting report_device_details = yes and restart the smsd. In my case the result in the log is:

2010-09-08 11:53:35,7, GSM1: # Manufacturer identification:
2010-09-08 11:53:35,7, GSM1: -> AT+CGMI
2010-09-08 11:53:36,7, GSM1: <- huawei
OK
2010-09-08 11:53:36,7, GSM1: # Model identification:
2010-09-08 11:53:36,7, GSM1: -> AT+CGMM
2010-09-08 11:53:36,7, GSM1: <- E1552

...

2010-09-08 11:53:38,7, GSM1: # Phonebook storage, available mem's:
2010-09-08 11:53:38,7, GSM1: -> AT+CPBS=?
2010-09-08 11:53:39,7, GSM1: <- +CPBS: ("SM","EN","ON")

I actually have one for loan. It says following, which obviously means that not phonecalls are not supported.

There is an interesting link related to voicemail hacking, though.

http://www.ruchirablog.com/activating-voice-calling-on-huawei-hspa-modems/

2010-09-08 18:16:46,7, huawei: ## Start of device details
2010-09-08 18:16:46,7, huawei: # Manufacturer identification:
2010-09-08 18:16:46,7, huawei: -> AT+CGMI
2010-09-08 18:16:47,7, huawei: <- huawei
OK
2010-09-08 18:16:47,7, huawei: # Model identification:
2010-09-08 18:16:47,7, huawei: -> AT+CGMM
2010-09-08 18:16:47,7, huawei: <- E160X
OK
2010-09-08 18:16:47,7, huawei: # Revision identification:
2010-09-08 18:16:47,7, huawei: -> AT+CGMR
2010-09-08 18:16:48,7, huawei: <- 11.609.10.00.00
OK
2010-09-08 18:16:48,7, huawei: # New message indications, list of supported modes:
2010-09-08 18:16:48,7, huawei: -> AT+CNMI=?
2010-09-08 18:16:48,7, huawei: <- +CNMI: (0,1,2),(0,1,2,3),(0,2),(0,1,2),(0,1)
OK
2010-09-08 18:16:48,7, huawei: # New message indications, current settings:
2010-09-08 18:16:48,7, huawei: -> AT+CNMI?
2010-09-08 18:16:49,7, huawei: <- +CNMI: 0,0,0,0,0
OK
2010-09-08 18:16:49,7, huawei: # Preferred message storage, list of supported mem's:
2010-09-08 18:16:49,7, huawei: -> AT+CPMS=?
2010-09-08 18:16:49,7, huawei: <- +CPMS: ("ME","MT","SM","SR"),("ME","MT","SM","SR"),("ME","MT","SM","SR")
OK
2010-09-08 18:16:49,7, huawei: # Phonebook storage, available mem's:
2010-09-08 18:16:49,7, huawei: -> AT+CPBS=?
2010-09-08 18:16:50,7, huawei: <- +CME ERROR: 14
(SIM busy)
2010-09-08 18:16:50,7, huawei: # List messages, list of supported stat's:
2010-09-08 18:16:50,7, huawei: -> AT+CMGL=?
2010-09-08 18:16:50,7, huawei: <- +CMGL: (0-4)
OK
2010-09-08 18:16:50,7, huawei: # Delete message, list of supported values:
2010-09-08 18:16:50,7, huawei: -> AT+CMGD=?
2010-09-08 18:16:51,7, huawei: <- +CMGD: (0,1,2,3),(0-4)
OK
2010-09-08 18:16:51,7, huawei: # Phone activity status, list of supported stat's:
2010-09-08 18:16:51,7, huawei: -> AT+CPAS=?
2010-09-08 18:16:51,7, huawei: <- +CPAS: (0,3,4)
OK
2010-09-08 18:16:51,7, huawei: # TE character set, list of supported charset's:
2010-09-08 18:16:51,7, huawei: -> AT+CSCS=?
2010-09-08 18:16:52,7, huawei: <- +CSCS: ("IRA","GSM","UCS2")
OK
2010-09-08 18:16:52,7, huawei: # TE character set, current setting:
2010-09-08 18:16:52,7, huawei: -> AT+CSCS?
2010-09-08 18:16:52,7, huawei: <- +CSCS: "IRA"

Sorry a correction to SIM BUSY status to my previous posting.
...
2010-09-08 18:26:17,7, huawei: # Phonebook storage, available mem's:
2010-09-08 18:26:17,7, huawei: -> AT+CPBS=?
2010-09-08 18:26:18,7, huawei: <- +CPBS: ("SM","EN","ON")
OK

Thanks, the link was interesting...

My stick (E1552) already had Voice feature enabled.

There still is no "MC" memory shown, and smsd therefore cannot handle missed calls.

When using "PC UI Interface" port (on Linux it was the highest number of three devices), incoming RING is shown and hangup_incoming_call works. This device can also make an outgoing call, and with voicecall_clcc hangup and answering is detected. But this device does not send tones. Perhaps there is some "unlocking" for DTMF feature too, I do not know about it.

If you start to use huawei stick with smsd, you will need this:

init = AT^CURC=0

Great, this is enough for my purposes. I can get what I want with that setup.

smsd.conf
[huawei] device = /dev/ttyUSB3 init = AT^CURC=0 incoming = yes pin = 2222 phonecalls = clip hangup_incoming_call = yes memory_start = 0

smsd.log
2010-09-09 20:45:10,5, huawei: Ending incoming call: RING +CLIP: "xxxxxxxxx",129,,,,0

... and message in the phonecalls directory:
From: xxxxxxxxx From_TOA: 81 unknown, ISDN/telephone Subject: huawei Modem: huawei IMSI: xxxxxxxxxxxxxxxxx Call_type: missed Received: 10-09-09 20:45:10 CALL MISSED

Thanks for the good tip !

Infact, for my purposes seemed to be enough just to use /dev/ttyUSB3 instead of /dev/ttyUSB1.
[huawei] device = /dev/ttyUSB3 #init = AT^CURC=0 incoming = yes #pin = 2222 phonecalls = clip hangup_incoming_call = no memory_start = 0 # voicecall_vts_list = yes # report_device_details = yes

kessi wrote

Infact, for my purposes seemed to be enough just to use /dev/ttyUSB3 instead of /dev/ttyUSB1.

You mean that vice versa? ... to use /dev/ttyUSB1.

As you do not need to hangup incoming calls, the first port is ok. Probably outgoing calls work with this port too, I have not tested it.

And it was good idea to disable the PIN, in modem usage the PIN is useless and just causes more traffic...