| Keywords: Mode: All keywords (AND) |
|
Tue Jun 30, 2015 00:21
|
|
|
|
Fri Feb 27, 2015 16:27
|
adrianTNT: What is the best way to separately send messages trough different modem/providers ?
I have one SIM from T-mobile, one from Verizon, and when sending a message I want to tell it what modem/provider to use based on the receiver number format, so it will send SMS in it's own network.
From what I read, it is not possible to specify modem in the sendsms command, is it ?! Or specify modem in the file I can manually write inside "outgoing" folder ?
Is the "queue" and "providers" the only way to do this? Seems more complicated than it could be.
|
|
Tue Jan 13, 2015 21:42
|
adrianTNT: To identify the correct port you can also try a command like this:
socat - /dev/ttyUSB0
or
socat - /dev/ttyUSB1
socat - /dev/ttyUSB2
and after entering that mode, you can type commands, directly type "ATI" and see what you get, if it is the correct GSM interface then you should see the IMEI number and maybe a bit more text. If it is the wrong interface (like the storage of that dongle) then you might see more random text that updates around once a second and you might notice text "storage" on screen.
To exit that mde (that socat command) try CTRL+C;
Maybe others can correct me if I am wrong, I am not an expert :)
|
|
Thu Dec 18, 2014 00:20
|
adrianTNT: On my system(s) I identify the ports by running this command:
ls -alh /dev/ttyUSB*
If your USB dongle is connected you should see something like:
crw-rw---T 1 root dialout 188, 0 Dec 17 23:09 /dev/ttyUSB0
crw-rw---T 1 root dialout 188, 1 Dec 17 23:09 /dev/ttyUSB1
crw-rw---T 1 root dialout 188, 2 Dec 17 23:09 /dev/ttyUSB2
If so, try using /dev/ttyUSB0 as device in smsd.conf
With my Huawei dongles I get these 3 interfaces when I connect one dongle.
|
|
Thu Dec 18, 2014 00:15
|
adrianTNT: I still need some help, anyone ?
An update ...
Each dongle I connect adds 3 usb interfaces, first one would add: ttyUSB0, ttyUSB1, tyyUSB2, then when I connect all 4 dongles I get up to ttyUSB11.
If I wait a few seconds after connecting each device, then first device is always the valid one to send SMS, for example with 4 dongles connected my SMS interfaces would be:
ttyUSB0, ttyUSB3, ttyUSB6, ttyUSB9
Now the problem is that when system reboots or if I connect all dongles at once, the ports/interfaces mix and I cannot know which one to use in order to send messages.
Is there a way to disable the other 2 interfaces of each dongle by default ? I am not sure what the other 2 are.
|
|
Tue Nov 11, 2014 14:16
|
adrianTNT: Hello.
I am trying to use SmsTools with Raspberry pi B+ and 4 GSM dongles.
In lsusb I see 4 devices, look ok to me
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 006: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 007: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 008: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
But ls -alh /deb/ttyUSB* shows 12 USB devices, it ads 3 for every dongle I connect:
crw-rw---T 1 root dialout 188, 0 Jan 1 1970 /dev/ttyUSB0
crw-rw---T 1 root dialout 188, 1 Jan 1 1970 /dev/ttyUSB1
crw-rw---T 1 root dialout 188, 10 Jan 1 1970 /dev/ttyUSB10
crw-rw---T 1 root dialout 188, 11 Jan 1 1970 /dev/ttyUSB11
crw-rw---T 1 root dialout 188, 2 Jan 1 1970 /dev/ttyUSB2
crw-rw---T 1 root dialout 188, 3 Jan 1 1970 /dev/ttyUSB3
crw-rw---T 1 root dialout 188, 4 Jan 1 1970 /dev/ttyUSB4
crw-rw---T 1 root dialout 188, 5 Jan 1 1970 /dev/ttyUSB5
crw-rw---T 1 root dialout 188, 6 Jan 1 1970 /dev/ttyUSB6
crw-rw---T 1 root dialout 188, 7 Jan 1 1970 /dev/ttyUSB7
crw-rw---T 1 root dialout 188, 8 Jan 1 1970 /dev/ttyUSB8
crw-rw---T 1 root dialout 188, 9 Jan 1 1970 /dev/ttyUSB9
So what ports should I setup in smsd.conf ? Because I am not sure why I have more ports for one dongle.
Are the extra ports there because of the sd card adapter on each dongle ? I tried checking/disable with usb_modeswitch without much success. I did disable the CD emulator feature and in Windows it doesn't load a CD anymore.
Operating system name and version: Raspbian on Raspberry pi
Version of smsd: smstools3-3.1.15.tar.gz
Smsd installed from: sources
Name and model of a modem / phone: Huawei 3G dongle K3765
Interface: USB
|
|
Mon Nov 10, 2014 00:01
|
adrianTNT: If anyone else has this problem, I fixed it by editing Makefile and adding one tab character before the "override" word, so it looks something like this:
ifneq (,$(findstring SOLARIS,$(CFLAGS)))
ifeq (,$(findstring DISABLE_INET_SOCKET,$(CFLAGS)))
override LFLAGS += -lsocket -lnsl
endif
endif
|
|
Sun Nov 09, 2014 20:32
|
adrianTNT: Hello.
I am trying to compile smstools3-3.1.15.tar.gz from source but I get these errors:
make[1]: Entering directory '/adrian/smstools3/src'
Makefile:51: *** recipe commences before first target. Stop.
make[1]: Leaving directory '/adrian/smstools3/src'
Makefile:10: recipe for target 'compile' failed
make: *** [compile] Error 2
I thougth this topic is similar, so I tried adjusting the two lines as explained there, but I am now getting this other error:
Makefile:51: *** recipe commences before first target. Stop.
This was my code after editing:
ifneq (,$(findstring NOSTATS,$(CFLAGS)))
$(CC) $(CFLAGS) -o $@ $^ -lsocket -lnsl
else
$(CC) `mm-config --cflags` $(CFLAGS) -o $@ $^ `mm-config --ldflags --libs` -lsocket -lnsl
endif
clean:
rm -f *.o smsd *.exe *~
Operating system name and version: Raspbian on raspberry Pi board
Version of smsd: smstools3-3.1.15.tar.gz
Smsd installed from: sources / package repository / from elsewhere: downloaded latest source archive from site
Name and model of a modem / phone: none yet, I will test with Huawei K3765 dongle
Interface: serial / USB / some adapter: USB
|
|
Tue Sep 03, 2013 22:15
|
adrianTNT: I also thought about checking for existent files before creating more, I will check in both "outgoing" and "checked" folder, both can get filled with many messages and slow down the system, I noticed that if I have under 200 in outgoing folder then it loads a file in 1-2 seconds, otherwise it can take even 20-30 seconds in case there are over 1000 files.
Thanks for the great support Keke.
|
|
Tue Sep 03, 2013 06:29
|
adrianTNT: Processes are named smsd.exe, yes, sorry :)
So I understand that this can be caused by a slow system and I should better create the SMS files myself ? The system indeed has an extremly slow processor, I cannot use it for anything else.
I do not see "os_cygwin = yes", should I add it in smsd.conf ?
( PRIVATE BLOCK )
Thank you.
|
|
Sun Sep 01, 2013 22:10
|
adrianTNT: Thanks for your reply.
It is a python script that loads data from an url and then triggers the local sendsms command in order to send a message.
Data is loaded as plain text and contains 10 lines per page load, each line contains phone number and message to send, separated by "|":
+1555224565|Hello Jack, blah, blah
+1222343433|Hi Mark, blah, blah
.. 8 more ...
This is repeated every 34 seconds, seems enough for the modems to send data.
I noticed each time I restart smsd that there are 7 instances of sendsms.exe in windows, is that correct for 6 modems ?
( PRIVATE BLOCK )
|
|
Sun Sep 01, 2013 13:05
|
adrianTNT: Hello.
I am running a script to send the messages from Cygwin command line, it sends around 10 per minute, and there are 6 modems configured, sometimes my script stops because I am getting this back from the SmsTools:
mv: try to overwrite `/var/spool/sms/outgoing/send_tRZacZ', overriding mode 0600 (rw-------)? n
The folders only contain a low amount of files, changing from 0 to ~5.
I am not sure what caused it, maybe the unique filename is not so unique? Or maybe the 6 instances of the modem all try to move the file at once and causes the conflict ? It happen twice in last hour.
Does this indicate a problem and is there a way to tell it to automatically overwrite it or skip it ?
Thank you.
|
|
Thu Aug 22, 2013 22:48
|
|
|
|
Thu Aug 22, 2013 22:01
|
adrianTNT: Thanks. Do you think it is useful enough to be added on a future update?
|
|
Thu Aug 22, 2013 15:18
|
adrianTNT: Hello.
Is there a way to customize the "Limit reached" warning SMS to include the date that limit was reached?
I am asking because I have an hourly limit but today I received many "warning" SMS messages one after another, I am not sure if it was a bug or they were just previous messages that could not reach me while my phone was off.
It was useful to include date: "Message limit 100 was reached at 14:30 21 Aug".
Let me know.
Thank you.
|
|
Sun Aug 18, 2013 23:51
|
adrianTNT: Yes. Thanks. Great tool.
I just used it with Cygwin on Windows, I was wondering... in CentOS does it need drivers for each GSM stick or does it work directly with the mentioned devices ? I have no experience with these devices on linux.
|
|
Thu Jul 25, 2013 16:42
|
adrianTNT: First of all, thank you to coder(s) for a nice tool.
I am trying to understand how the variables message_limit and message_count_clear work.
The message_count_clear starts counting when message_limit was reached and then it resets after X minutes ?
Or does it simply resets every X minutes regardless if message_limit was reached or not ?
First one would mean that there will be a blank period when nothing is sent, doesn't sound effective.
Second one would make more sense and would mean that you could effectivly set an 100 messages per hour or so by these settings
message_limit=100
message_count_clear=60
Which one is it ?
Thank you.
|
