|
|
SMS Server Tools 3 Community |
Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 09:19 |
Login and Post Reply
Page: 1
Author |
Post |
|
#1 Wed May 31, 2017 15:23, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
|
Operating system name and version: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux Version of smsd: 3.1.15 Smsd installed from: apt-get Name and model of a modem / phone: modem appears as "Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem Interface: usb
Hi guys I have problem with smstools. I can send sms, but not receiving. In logs there's nothing about incoming :/ I thought maybe rights to incoming directory, but even with full - nothing :/ 3g modem appears as "Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem". Can u help me? Thx and tc.
|
|
#2 Wed May 31, 2017 15:33, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Do you have a modem setting incoming = yes?
With Huawei you will also need memory_start = 0.
If still nothing is received, use a modem setting report_device_details = yes and show those details from the log.
|
|
#3 Wed May 31, 2017 15:43, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
keke wrote Do you have a modem setting incoming = yes?
With Huawei you will also need memory_start = 0.
If still nothing is received, use a modem setting report_device_details = yes and show those details from the log.
1. yes 2. yes 3. i've just put in config. (in config logs are /var/log/smstools/smsd.log).
|
|
#4 Thu Jun 01, 2017 07:16, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
This is my smsd.conf - i know, a little bit messy # # /etc/smsd.conf # # Description: Main configuration file for the smsd #
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 #loglevel = 7 #delaytime = 10 #errorsleeptime = 10 #blocktime = 3600 #stats = /var/log/smsd_stats #stats_interval = 3600 #stats_no_zeroes = no #checkhandler = /usr/local/bin/smscheck receive_before_send = no # autosplit 0=no 1=yes 2=with text numbers 3=concatenated autosplit = 3 # store_received_pdu 0=no, 1=unsupported, 2=unsupported and 8bit, 3=all #store_received_pdu = 1 #validity = 255 #decode_unicode_text = no #internal_combine = no # You can specify here an external program that is started whenever an alarm occurs. # alarmhandler = /path/to/an/alarmhandler/script # Specifies what levels start an alarmhandler. You can use value between 2 and 5. # alarmlevel = 4 # eventhandler = @EVENTHANDLER@ #blacklist = /etc/smstools/blacklist #whitelist = /etc/smstools/whitelist
#[queues] # Commented lines are examples for germany # D1 = /var/spool/sms/D1 # D2 = /var/spool/sms/D2 # O2 = /var/spool/sms/O2 # EPLUS = /var/spool/sms/EPLUS # QUAM = /var/sppol/sms/QUAM # MOBILCOM = /var/spool/sms/MOBILCOM #OTHER = /var/spool/sms/OTHER
#[provider] # Commented lines are examples for germany # D1 = 49160, 49170, 49171, 49175, 49151 # D2 = 491520, 49162, 49172, 49173, 49174 # O2 = 49176, 49179, 49159 # EPLUS = 49163, 49177, 49178, 49157 # QUAM = 49150 # MOBILCOM = 49156 #OTHER = 0,1,2,3,4,5,6,7,8,9
#[GSM1] # init = ATE0+CPMS="SM"+CNMI=2,0,0,2,1 # # Windows: /dev/com1, Solaris: /dev/cua/a, Linux /dev/ttyS0 # device = /dev/ttyS0 # incoming = yes # queues = OTHER # You don't need a PIN for mobile phones # pin = 1111 # mode = new # smsc = 491722270000 # baudrate = 19200 # rtscts = yes # cs_convert = yes # report = no # memory_start = 1 # primary_memory = memory name # secondary_memory = memory name # secondary_memory_max = number # pdu_from_file = /var/spool/sms/GSM1-PDU # sending_disabled = no # decode_unicode_text = no # internal_combine = no # #[GSM2] #init = ATE0 # Windows: /dev/com2, Solaris: /dev/cua/b, Linux /dev/ttyS1 #device = /dev/ttyS1 #incoming = yes #queues = OTHER #You don't need a PIN for mobile phones #pin = 2222 #mode = new #smsc = 491710760000 #baudrate = 19200 #rtscts = yes #cs_convert = yes #report = no #memory_start = 1 #primary_memory = memory name #secondary_memory = memory name #secondary_memory_max = number #pdu_from_file = /var/spool/sms/GSM2-PDU #sending_disabled = no #decode_unicode_text = no #internal_combine = no [GSM1] #init = AT+CPMS="MT","MT","MT" init=AT+CPMS="ME","ME","ME" #init=AT+CPMS="IRA","GSM","UCS2" device = /dev/ttyUSB0 #init=AT+CPMS="MT","MT","MT" #init = AT+CURC=0 incoming = yes #pin = baudrate = 19200 memory_start=0 #1 hangup_incoming_call = yes #check_memory_method = 31 report_device_details = yes 'smsdconf' Syntax Highlight powered by GeSHi and logs since last smstools restart as I understand incoming smses should be files in incoming directory?
|
|
#5 Thu Jun 01, 2017 12:17, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
We need to see what is the status of each memory in the modem. Stop the smsd if it is running. Open a terminal connection to the modem using smsd: # smsd -C GSM1 Communicating with GSM1. ( Press Ctrl-C to abort. ) ( If you need to send Ctrl-Z, use Alt-Z ) Default device is /dev/ttyUSB3 Press Enter to start or type an another device name.
Opening device /dev/ttyUSB3 Ready. ATE1 OK ATZ ( reset the modem ) OK AT+CPMS? ( check current Preferred Message Storages ) +CPMS: "SM",15,20,"SM",15,20,"SM",15,20
OK AT+CPMS="SR" ( check Status Report storage ) +CPMS: 0,10,15,20,15,20 ( = no messages, 10 slots )
OK AT+CPMS="ME" ( check Mobile Equipment storage ) +CPMS: 6,23,15,20,15,20 ( = 6 messages, 23 slots )
OK AT+CPMS="SM" ( check SIM storage ) +CPMS: 15,20,15,20,15,20 ( = 15 messages, 20 slots )
OK
What are the answers in your case? If all message counters are zeroes, keep the modem powered and send SMS to it using your handset. Then repeat those commands and show the results.
|
|
#6 Thu Jun 01, 2017 13:25, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
how long should taking anwer for "smsd -C GSM1" ?
|
|
#7 Thu Jun 01, 2017 13:32, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
It should answer immediately. Check the last lines from the log.
You could also use the last port which is provided by the modem. I think it is /dev/ttyUSB2 in your case.
Also check what ifconfig says. Is there any wwan* interfaces which you do not usually use? If there are any, shut them down with ifconfig wwan0 down and so on.
|
|
#8 Thu Jun 01, 2017 13:39, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
and i dont have wwan interfaces, i dont need them at all, 'cause it's only for sms.
|
|
#9 Thu Jun 01, 2017 13:44, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Ok, after the command smsd -C GSM1, did you get anything on the terminal? If you did not get any lines, I do not know what is the problem. In this case you should use Minicom for communication.
|
|
#10 Thu Jun 01, 2017 13:46, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
|
|
#11 Thu Jun 01, 2017 13:50, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
After the "Ready.", give a command ATE1 (probably blind). If the answer is OK, continue with blue commands.
|
|
#12 Thu Jun 01, 2017 14:04, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
done all  after sendign sms to this number: « Last edit by helianthus on Thu Jun 01, 2017 14:08, 94 months ago. »
|
|
#13 Thu Jun 01, 2017 14:11, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
It looks like "echo on" command ATE1 does not work, but it is a minor issue as smsd itself does not like "echo".
All memories are empty. You should try to send SMS to modem, and check memories again.
|
|
#14 Thu Jun 01, 2017 14:12, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Ok, you already tried. You should check again with /dev/ttyUSB2, but if result is the same, I think that your modem is broken. 
|
|
#15 Thu Jun 01, 2017 14:16, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
after sending sms to modem from another phone #edit, damn, it cant be 
|
|
#16 Thu Jun 01, 2017 14:31, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
On the other topic daniel361 was using E3131 which had the similar problem. He was talking about some "web interface of the modem", but I do not know anything about those interfaces. If the modem does not show messages through the standard AT command interface, it is not compatible with smstools. Sorry. 
|
|
#17 Thu Jun 01, 2017 14:32, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
ok, modem is responding only on USB0. So...
|
|
#18 Thu Jun 01, 2017 14:33, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
keke wrote On the other topic daniel361 was using E3131 which had the similar problem. He was talking about some "web interface of the modem", but I do not know anything about those interfaces. If the modem does not show messages through the standard AT command interface, it is not compatible with smstools. Sorry. 
thx, i will see it, but now, can u recommend me any modem working good with smstools?
|
|
#19 Thu Jun 01, 2017 14:41, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
In some systems I use these: https://www.fasttech.com/products/0/10008211/2409900-huawei-e353-21mbps-3g-umts-hspa-hsdpa-usb-surf. They all have the same MAC, but it does not matter very much. With phonecalls there are some limitations, but SMS messaging works very well and fast. And those devices are cheap...
|
|
#20 Thu Jun 01, 2017 14:49, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
thx! I need only sending/receiving sms. I've just bought that e353. We will see 
|
|
#21 Mon Jun 05, 2017 10:55, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
KEKE, u r a hero!  Huawei e353 works geat! I've only changed init command to "init=AT+CPMS="SM","SM","SM"" and i;m receiving smses, too  Thx for your help and patience 
|
|
#22 Mon Jun 05, 2017 13:08, 94 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Thank you. If you later want to get delivery reports received, change initialization to: init = AT+CPMS="SM","SM","SM";+CNMI=2,0,0,2,1If some unexpected input is shown in the log, use this setting too: init2 = AT^CURC=0When this device produces three ports, it is recommended to use the last of them. If your system has symbolic links on /dev/serial/by-id/ directory, use for example usb-HUAWEI_HUAWEI_Mobile-if0 3-port0.
|
|
#23 Wed Jun 07, 2017 13:27, 94 months ago.
|
Member
Registered: May 2017
Location: Wrocław, Poland
Topic owner
|
thx!
|
Login and Post Reply
Page: 1
Time in this board is UTC.
|
|
|
 |
|
 |
|