USB-Stick: Raspian (debian) stretch :
how can I recognize the actual version ? I have just updated / upgraded by smstools by apt-get ...:
smstools was installed from raspian package
Name and model of a modem / phone : various Huawei modems and Medion (ALDI) modems
Interface: USB adapter...
I am using all kinds of modems very successfully with smstools and wvdial (internet connection). One issue remains:
What is the rule, how ttyUSBx serial lines are connected either to wvdial or to smstools ? How can I find out automatically that in scripts or in the appropriate config files the right serial interfaces are linked to the right application.
e.g. - smstools is momentarily linked to /dev/serial/by-id/usb-MediaTek_Inc_Product-if03-port0 (which is momentarily pointing to ttyUSB1), whereas wvdial is blocking ttyUSB0
Is this always? Why not vice versa?
Can it be different for other modem types? As I am often changing modem types I am looking for a routine which does find out automatically - such as wvdialconf does ...!
Any advice, how this cumbersome manual adapting / testing the right serial interface can be automated is appreciated!
Thanks in advance!
|
USB-Stick: Raspberry Jessie:
latest:
ALDI Medion WebStick:
Hello All,
I am facing a strange problem:
After many days of proper work (followed by possible modifications, which I am not aware of today ...) SMSTOOS doesn't read any more the UMTS Stick memory areas ...:
--------------------------------------------------------------------------------
....
2016-04-25 05:59:17,6, GSM1: No SMS received
2016-04-25 05:59:27,6, GSM1: Checking device for incoming SMS
2016-04-25 05:59:27,6, GSM1: Checking if modem is ready
2016-04-25 05:59:27,7, GSM1: -> AT
2016-04-25 05:59:27,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:28,7, GSM1: <- OK
2016-04-25 05:59:28,6, GSM1: Pre-initializing modem
2016-04-25 05:59:28,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2016-04-25 05:59:28,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:28,7, GSM1: <- OK
2016-04-25 05:59:28,6, GSM1: Initializing modem
2016-04-25 05:59:28,7, GSM1: -> AT+CSCA?
2016-04-25 05:59:28,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:29,7, GSM1: <- +CSCA: "491760000443", 145 OK
2016-04-25 05:59:29,7, GSM1: -> AT+CSQ
2016-04-25 05:59:29,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:29,7, GSM1: <- +CSQ: 14, 99 OK
2016-04-25 05:59:29,6, GSM1: Signal Strength Indicator: (14,99) -85 dBm (Workable), Bit Error Rate: not known or not detectable
2016-04-25 05:59:29,6, GSM1: Checking if Modem is registered to the network
2016-04-25 05:59:29,7, GSM1: -> AT+CREG?
2016-04-25 05:59:29,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:29,7, GSM1: <- +CREG: 2,5,"9E1C","09AC68F8",6 OK
2016-04-25 05:59:29,6, GSM1: Modem is registered to a roaming partner network
2016-04-25 05:59:29,6, GSM1: Selecting PDU mode
2016-04-25 05:59:30,7, GSM1: -> AT+CMGF=0
2016-04-25 05:59:30,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:30,7, GSM1: <- OK
2016-04-25 05:59:30,6, GSM1: Checking memory size
2016-04-25 05:59:30,7, GSM1: -> AT+CPMS?
2016-04-25 05:59:30,7, GSM1: Command is sent, waiting for the answer
2016-04-25 05:59:30,7, GSM1: <- +CPMS: "ME", 0, 50, "SM", 1, 10, "SM", 1, 10 OK
2016-04-25 05:59:30,6, GSM1: Used memory is 0 of 50
2016-04-25 05:59:30,6, GSM1: No SMS received
...
-----------------------------------------------------------------------------------
As you can see, the statistic line (bolded) +CPMS: .... shows ONE of 10 possible SMS entries on the SimCard Memory, but it seems that SMSTOOS is unable to recognize that SMS and pull it into processing!
Definitely the SMS has arrived and ist readable (under windows 7).
I am not asking for your deep analysis help, but I just wanted to be advised for possibly overseen parameters in SMSTOOLS which have to be switched on for reading the UMST stick memory area(s)?
Thanks in advance!
Regards
|
USB-Stick: :D ... Solved!
I got it! By defining GSM1, GSM2, ... and corresponding paragraphs [GSM1], [GSM2], ... the settings are activated automatically - dependent on modem type (resp. SIM-card in the modem) plugged in.
Swaping the modem will ask for a restart or reload of SMStools service.
For real use a reboot will be the standard procedure after swapping modems - fully acceptable!
(Sometimes a post and one night sleep can be self-sufficient) :P :P :twisted:
Many thanks to the software developers for this marvellous "piece of software"!
An additional nice feature would be an automatic scan which /dev/ttyUSB* is usable/activated for SMS services with the corresponding stick.
I am using a cheap Medion stick (ALDI Germany) with o2 (D1 Network works as well).
Hopefully the logic link names
lrwxrwxrwx 1 root root 13 March 27 10:07 usb-MediaTek_Inc_Product-if03-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 March 27 10:07 usb-MediaTek_Inc_Product-if05-port0 -> ../../ttyUSB4
lrwxrwxrwx 1 root root 13 March 27 10:07 usb-MediaTek_Inc_Product-if02-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 March 27 10:07 usb-MediaTek_Inc_Product-if04-port0 -> ../../ttyUSB2
will remain a constant.
I am using for SMS serial connections
[GSM1]
...
#device = /dev/serial/by-id/usb-MediaTek_Inc_Product-if02-port0
device = /dev/serial/by-id/usb-MediaTek_Inc_Product-if03-port0
#device = /dev/serial/by-id/usb-MediaTek_Inc_Product-if04-port0
#device = /dev/serial/by-id/usb-MediaTek_Inc_Product-if05-port0
...
to bind to the o2 network via the Medion stick.
Using a Huawei E3131s (Web'nWalk III)
[GSM2]
...
#device = /dev/serial/by-id/usb-HUAWEI_HUAWEI_Mobile-if02-port0
#device = /dev/serial/by-id/usb-HUAWEI_HUAWEI_Mobile-if00-port0
device = /dev/serial/by-id/usb-HUAWEI_HUAWEI_Mobile-if03-port0
...
works fine for me.
Cross change of SIM cards to Modems (e.g. D1-SIM with Medion stick) works fine as well, only serial connections have to be changed. Defining [GMS3 and GSM4] allows all variations (Permutations)
of Modems with SIM cards.
--------------------------------------------------------------------------------------
The WIFI <-> UMTS Router connection are managed via pppd (PON, POFF) in parallel - works also perfect for me - for either modem!
All implemented on a Raspberry B+ Version 2.
Regards ;)
|
USB-Stick: Debian Wheezy (Raspberry):
Version of smsd:
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone:
Interface: serial / USB / some adapter...
Hi All,
I am using different UMTS modem sticks from various suppliers which are demanding different /dev/ttyUSB* for SMS-connect. Until now I am manually adjusting the configuration file smsd.conf.
I strongly assume, that the different sections [GSM1], [GSM2], ... can be assigned to different Hardware modems, but how / where is the assignment done?
Or is it possible to provide different smsd.conf - files which can be selected and assigend automatically to the specific modem (via usb_modswitch ???).
Or am I totally mistaken: Do I need to set up queues first which I need to assign to the specific IMSI of the SIM-cards ? That would mean any new SIM-card has to be manually adjusted in the configuration file before usage. I would prefer different Modemsticks (~ 5 types) which automatically after plugin will be assigned the appropriate type settings.
I appologize for this newbie question - any help ist pretty much appreciated!
Best regards, thanks in advance!
|
