|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. Please login or register. |
Thu Apr 25, 2024 10:54 |
Login and Post Reply
Page: 1
| Author |
Post |
|
|
#1 Wed Jun 01, 2016 22:22, 96 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
|
Operating system name and version: Raspbian 8.0 Version of smsd: 3.1.15 Smsd installed from: package repository Name and model of a modem / phone: Huweii E3131 Revision: 22.157.39.00.105 Interface: USB I am attempting to setup an SMS gateway. I can send messages no problem, but I cannot receive messages. Here's my smsd.conf... Global configuration
# devices = modem1, modem2
devices = modem1
loglevel = 7
# logfiles
stats = /var/log/smstools/stats
logfile = /var/log/smstools/smsd.log
delaytime = 2
errorsleeptime = 10
blocktime = 180
autosplit = 3
#receive_before_send = yes
[queues]
modem1 = /var/spool/sms/modem1
# Modem name: modem1
# Modem type: Huweii E3131 USB
[modem1]
#init=AT+CPMS="SM","SM","SM"
#init=AT+CPMS="ME","ME","ME"
device = /dev/gsm1-1
baudrate = 115200
incoming = yes
report = yes
queues = modem1
decode_unicode_text = yes
cs_convert = yes
memory_start = 0
'smsdconf' Syntax Highlight powered by GeSHi gsm1-1 is a symlink to ttyUSB2 Quote # ls -l /dev/gsm1-1
lrwxrwxrwx 1 root root 7 Jun 1 19:51 /dev/gsm1-1 -> ttyUSB2
I've also tried ttyUSB0.... Tried AT+CPMS with "SM", "ME", and "MT"... The smsd.log I had some initial trouble with it until I setup usb_modeswitch. Here is my usb_modeswitch.conf... DisableSwitching=0
DisableMBIMGlobal=0
EnableLogging=1
'smsdconf' Syntax Highlight powered by GeSHi And the modeswitch settings that work.... cat /etc/usb_modeswitch.d/12d1\:1f01
# Huawei E353 (3.se) and others
TargetVendor=0x12d1
TargetProductList=0x1001
MessageContent="55534243123456780000000000000011063000000100010000000000000000"
NoDriverLoading=0 'smsdconf' Syntax Highlight powered by GeSHi Hoping I've just got something misconfigured here and someone can point me in the right direction. Thanks
|
|
|
#2 Fri Aug 12, 2016 16:12, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
I have been able to take the E3131 and plug it into my laptop. From there I can see there are incoming SMS messages sitting on the modem. I just can't see them from the Pi.
|
|
|
#3 Sat Aug 13, 2016 16:56, 93 months ago.
|
|
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
|
Huawei provides three devices. Try to use the first one, likely /dev/ttyUSB0 in your case.
|
|
|
#4 Mon Aug 15, 2016 22:09, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
I tried ttyUSB0 with the same results. No incoming messages. I've tried these inits... init=AT+CPMS="ME","ME","ME" init=AT+CPMS="SM","SM","SM" Both result in 0 incoming messages found..... Quote 2016-08-15 22:05:13,6, modem1: Modem is registered to the network
2016-08-15 22:05:13,6, modem1: Selecting PDU mode
2016-08-15 22:05:13,7, modem1: -> AT+CMGF=0
2016-08-15 22:05:13,7, modem1: Command is sent, waiting for the answer
2016-08-15 22:05:13,7, modem1: <- OK
2016-08-15 22:05:13,6, modem1: Checking memory size
2016-08-15 22:05:14,7, modem1: -> AT+CPMS?
2016-08-15 22:05:14,7, modem1: Command is sent, waiting for the answer
2016-08-15 22:05:14,7, modem1: <- +CPMS: "ME",0,20,"ME",0,20,"ME",0,20 OK
2016-08-15 22:05:14,6, modem1: Used memory is 0 of 20
2016-08-15 22:05:14,6, modem1: No SMS received
Quote 2016-08-15 22:05:39,6, modem1: Checking if Modem is registered to the network
2016-08-15 22:05:39,7, modem1: -> AT+CREG?
2016-08-15 22:05:39,7, modem1: Command is sent, waiting for the answer
2016-08-15 22:05:40,7, modem1: <- +CREG: 2,1,"520E","D6C3" OK
2016-08-15 22:05:40,6, modem1: Modem is registered to the network
2016-08-15 22:05:40,6, modem1: Selecting PDU mode
2016-08-15 22:05:40,7, modem1: -> AT+CMGF=0
2016-08-15 22:05:40,7, modem1: Command is sent, waiting for the answer
2016-08-15 22:05:40,7, modem1: <- OK
2016-08-15 22:05:40,6, modem1: Checking memory size
2016-08-15 22:05:40,7, modem1: -> AT+CPMS?
2016-08-15 22:05:40,7, modem1: Command is sent, waiting for the answer
2016-08-15 22:05:41,7, modem1: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2016-08-15 22:05:41,6, modem1: Used memory is 0 of 30
2016-08-15 22:05:41,6, modem1: No SMS received
Using MT in the init instead of SM or ME just gives me a 302 error. |
|
|
#5 Tue Aug 16, 2016 20:26, 93 months ago.
|
|
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
|
I was remembering that there has been some issues between the ports, but now when I tried this with Huawei E1820, I was able to read message using ttyUSB0 and also with ttyUSB2.
When your test says that ME and SM memories are both empty, they likely are empty. How did you come to the conclusion that the modem has a message, even when memories are shown as empty?
It may help if you use a modem setting report_device_details = yes and restart the daemon. Some details are listed in the log and you could show those lines here.
|
|
|
#6 Tue Aug 16, 2016 20:33, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
I plugged the modem into my laptop and configured it there. Using an app on my Mac I was able to see all the incoming messages I have sent to the modem. I can't see them on the Pi though. Here is the device details.... |
|
|
#7 Tue Aug 16, 2016 21:17, 93 months ago.
|
|
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
|
Weird...  So, your device has two memories and both are shown as empty. However, your "app" on Mac shows some messages. Could it be possible that this app has those messages in it's own storage, meaning that messages were deleted from the SIM after they were read? You could do the following: - Start smsd and notice that the memory is empty. No matter which one is selected, but SM is preferred. - Using your handset, send an SMS to the Pi. - tail -f the log. There should be incoming message shown. - If there is no incoming message after waiting for awhile, create an outgoing message on Pi and sent it to your handset. - After sending, E3131 might get the incoming message, but this means that the stick is bad. |
|
|
#8 Tue Aug 16, 2016 21:27, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
I've sent new messages to that modem since I tested it on my laptop, so there should be some there. Sending messages works fine. I can see them going out in the smsd.log and I get them on my phone. When I reply I get nothing, unless I plug the modem back into my laptop and then I can see them there. Is my init in smsd.conf ok? |
|
|
#9 Tue Aug 16, 2016 21:44, 93 months ago.
|
|
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
|
Conf is ok.
Probably the firmware in the stick is bad. With a quick googling it seems that this E3131 does not receive messages unless some message is sent. Also switching on the internet might do the same. Your app on Mac probably does this, but I cannot be sure about that.
The test I listed might give more information, but it's not sure. It may detect if receiving works after sending.
But currently it seems that this stick is just bad and should be replaced with another (different) model.
|
|
|
#10 Tue Aug 16, 2016 21:50, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
Any particular USB modem recommendations?
|
|
|
#11 Wed Aug 17, 2016 21:47, 93 months ago.
|
|
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
|
There are large numbers of USB devices and usually I do not particularly recommend anything. However, just today I received a stick for evaluating, as I need to build couple of USB hubs with 8 sticks in each. The device is Huawei E353 from FastTech, and the price was reasonable $23.59. Details here. It produced, as usual, ttyUSB0, 1 and 2. Configuration was the following: [GSM1]
device = /dev/ttyUSB0
incoming = yes
memory_start = 0
'smsdconf' Syntax Highlight powered by GeSHi Sending worked, receiving worked without any issues, and delivery report also worked. This sounds good for me, and I'm going to order more of these devices for the hub construction. |
|
|
#12 Wed Aug 17, 2016 21:50, 93 months ago.
|
|
Member
Registered:
Jun 2016
Location: United States of America
Topic owner
|
Excellent, the E353 was one I was looking at today too, but that's a better price then I've seen. Thanks!
|
Login and Post Reply
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
