|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Wed Jun 25, 2025 06:57 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Thu Sep 09, 2010 18:32
|
kessi: 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
|
|
Thu Sep 09, 2010 18:03
|
kessi: 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 !
|
|
Wed Sep 08, 2010 15:27
|
kessi: 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
|
|
Wed Sep 08, 2010 15:23
|
kessi: 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"
|
|
Tue Sep 07, 2010 20:37
|
kessi: 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?
|
|
Tue Oct 06, 2009 20:30
|
kessi: ok. thanks for script, pointing to look for alarmhandler and ideas around it.
Didn't need to change the code at all - so big thanks for easy "portability".
|
|
Sun Oct 04, 2009 20:35
|
kessi: Operating system name and version: OperatLinux OpenWrt 2.6.25.17 #16 Sun Feb 15 00:19:46 CET 2009 mips unknown - ASUS WL-500G Premium - Kamikaze 8.09, r14511
Version of smsd: 3.1.5
Smsd installed from: sources
Name and model of a modem / phone: Nokia 6210
Interface: serial
What are the typical causes for Modem handler to terminate abnormally? Below a log for a case where such a thing happened [last line in log]
How does people here recover from this i.e. any comments on how to detect abnormal termination and restart smsd?
2009-10-02 15:30:50,2, smsd: Smsd v3.1.5 started.
2009-10-02 15:30:50,2, smsd: Running as root:root.
2009-10-02 15:30:50,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2009-10-02 15:30:50,5, paarsim: Modem handler 0 has started. PID: 1222.
2009-10-02 15:30:50,5, paarsim: Using check_memory_method 1: CPMS is used.
2009-10-02 15:30:50,5, smsd: Outgoing file checker has started. PID: 1221.
2009-10-02 15:31:05,5, paarsim: IMSI: 350xxxxxxxxxx
2009-10-03 10:39:22,5, paarsim: SMS received, From: 358xxxxxxxxx
2009-10-03 10:40:25,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/sms.park to /mnt/usbdrive/sms/spool/checked
2009-10-03 10:40:26,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/sms.park.NOTIFY to /mnt/usbdrive/sms/spool/checked
2009-10-03 10:40:31,5, paarsim: SMS sent, Message_id: 79, To: 358xxxxxxxxx, sending time 5 sec.
2009-10-03 10:40:37,5, paarsim: SMS sent, Message_id: 80, To: 358xxxxxxxxx, sending time 5 sec.
2009-10-03 15:00:07,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/SMS.temperature to /mnt/usbdrive/sms/spool/checked
2009-10-03 15:00:15,5, paarsim: SMS sent, Message_id: 81, To: 358xxxxxxxxx, sending time 7 sec.
2009-10-03 20:05:17,3, paarsim: Modem did not accept the pre-init string
2009-10-03 21:40:17,3, paarsim: Modem did not accept the pre-init string
2009-10-04 08:10:17,3, paarsim: Modem did not accept the pre-init string
2009-10-04 12:55:17,3, paarsim: Modem did not accept the pre-init string
2009-10-04 15:00:11,5, smsd: Moved file /mnt/usbdrive/sms/spool/outgoing/SMS.temperature to /mnt/usbdrive/sms/spool/checked
2009-10-04 15:11:06,3, paarsim: The modem did not answer (expected OK).
2009-10-04 15:11:06,5, paarsim: Waiting 10 sec. before retrying
2009-10-04 15:15:10,5, paarsim: SMS sent, Message_id: 83, To: 358xxxxxxxxx, sending time 603 sec.
2009-10-04 16:35:16,3, paarsim: Modem did not accept the pre-init string
2009-10-04 18:05:17,2, paarsim: PIN handling: expected READY, modem answered
2009-10-04 18:05:18,2, paarsim: Modem handler 0 terminated abnormally. PID: 1222.
smsd.conf
#
devices = paarsim
user = root
loglevel = 5
logfile = /mnt/usbdrive/sms/spool/smsd.log
outgoing = /mnt/usbdrive/sms/spool/outgoing
sent = /mnt/usbdrive/sms/spool/sent
phonecalls = /mnt/usbdrive/sms/spool/phonecalls
saved = /mnt/usbdrive/sms/spool/saved
spool = /mnt/usbdrive/sms/spool/outgoing
incoming = /mnt/usbdrive/sms/spool/incoming
checked = /mnt/usbdrive/sms/spool/checked
internal_combine = yes
eventhandler = /mnt/usbdrive/sms/perl/event.sh
[paarsim]
device = /dev/ttyUSB1
incoming = yes
baudrate = 19200
phonecalls = yes
pin = xxxx
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
