SMS Server Tools 3
This site is hosted by Kekekasvi.com
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Thu Apr 25, 2024 04:08
SMSTools3 Community » Help and support Bottom

Connecting Modem ONDA MSA110up

Login and Post Reply

Page:  1

Author Post
Member
Registered:
Sep 2013
Location: BH / MG / BR, Brazil
Operating system name and version: Debian 7.01
Version of smsd: 3.1.15.
Smsd installed from: sources
Name and model of a modem / phone: ONDA MSA110up
Interface: USB

Hello!!
I need to help with smstools.
My problem is.
I have one Modem ONDA MSA110up, and the log smstools show me:

smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 16592.
Modem handler 0 terminated. PID: 16593, was started 13-09-12 16:23:58.
smsd: Smsd mainprocess terminated. PID 16592, was started 13-09-12 16:23:58.
smsd: Smsd v3.1.14 started.
smsd: Running as smsd:dialout.
smsd: File mode creation mask: 022 (0644, rw-r--r--).
GSM1: Unexpected input: ATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATATAT

anyone have any idea what it is? :mrgreen:

My conf is:

#
# /etc/smsd.conf
#

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 = 4
receive_before_send = yes
autosplit = 3

[GSM1]
device = /dev/gsmmodem
incoming = yes
sending_disabled = no
memory_start = 0
baudrate = 115200

the file /dev/gsmodem i create one direct link to my device, in /etc/udev/rules.d/00-gsmmodem.conf

the comand is: SUBSYSTEMS=="usb", ATTRS{idVendor}=="idmysub", ATTRS{idProduct}=="idmyusb", MODE:="0666", SYMLINK+="gsmmodem"


Thank's!!

Member
Registered:
Apr 2011
Location: São Paulo, Brazil
My configuration for ONDA MSA190UP

[GSM1]
device = /dev/ttyUSB0
start = AT+CREG=1
startsleeptime = 5
check_memory_method = 2
primary_memory = ME
secondary_memory = SR
incoming = yes
detect_unexpected_input = no
phonecalls = clip
signal_quality_ber_ignore = yes

This modem creates four devices, for example: ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3.
You can only use the device 2 (ttyUSB1) or 4 (ttyUSB3) in the configuration file.
Check the symbolic link is created via udev, but I recommend that you test using /dev/ttyUSBxx directly to isolate the problem.
If /dev/ttyUSBxx work, we must review the udev rule.

Sorry my poor english :).

Rodrigo.

Member
Registered:
Sep 2013
Location: BH / MG / BR, Brazil
Topic owner
Entao Rodrigo, eu criei os links redirecionando gssmodem para o dispositivo indepentende da porta que ele estiver conectado nos tty... mandando para /etc/udev/rules.d/00-gsmmodem.conf

O que acontece é que ele fica nesse loop infinito.

Estou testando em paralelo o gammu, e obtive mais sucesso com ele..

Mas de qualquer forma, obrigado!

Thank's! =) :mrgreen:

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
If your device works with gammu, it also should work with smstools. Have you tried to use /dev/ttyUSBxx directly, as rbariviera recommended?

Member
Registered:
Apr 2011
Location: São Paulo, Brazil
conekta,

Testar diretamente utilizando o /dev/TTYUSBxx irá ajudar muito a entender o que esta acontecendo.

Porem, tenho outra dúvida, esta regra de udev que vc postou é a que está no arquivo de configuração ou é só um exemplo ??
Pergunto isso pois a regra: ATTRS{idVendor}=="idmysub" não deveria funcionar pois o idVendor deste modem é o 19d2 e o idProduct é o 0091...

Independente da pergunta acima, sugiro que vc adicione a seguinte regra no udev:
ATTRS{bInterfaceNumber}=="01"
ou
ATTRS{bInterfaceNumber}=="04"

"01" representa a segunda porta do modem e "04" a quarta porta.

OBS: os números que coloquei acima correspondem ao meu modem. o seu pode conter algumas alterações devido a data de fabricação, versão do firmware, etc

O comando abaixo pode auxiliar a coletar as informações de idProduct, idVendor e bInterfaceNumber
udevadm info -a -p $(udevadm info -q path -n ttyUSBxx) | egrep "bInterfaceNumber|idVendor|idProduct" | head -n3

Espero ter ajudado.

----------------------------------

In english to help others...

Test directly using the /dev/TTYUSBxx will greatly help to understand what is happening.

However, I have another question, this udev rule that u posted is the one in the configuration file or is it just an example?
I ask this because the rule: ATTRS{idVendor}=="idmysub" should not work because of this modem's idVendor is 19d2 and idProduct is 0091...

Regardless of the question above, I suggest that u add the following rule in udev:
ATTRS{bInterfaceNumber}=="01"
or
ATTRS{bInterfaceNumber}=="04"

"01" represents the second port of the modem and "04" the fourth port.

PS: The numbers listed here correspond to my modem. your modem may contain some changes due to manufacturing date and firmware version, etc.

The command below can help you collect informations like idProduct, idVendor and bInterfaceNumber.
udevadm info-a-p $ (udevadm info-q path-n ttyUSBxx) | egrep "bInterfaceNumber|idVendor|idProduct" | head-n3

Rodigo.

Member
Registered:
Sep 2013
Location: BH / MG / BR, Brazil
Topic owner
Rodrigo... A regra que postei está no arquivo de configuração.

O smstools inicia a chamada porem fica na msg "TATATA.."

Keke
i'm going to test with ttyusbxx, and post the results.

Thx!! =)

Login and Post Reply

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.