| Keywords: Mode: All keywords (AND) |
|
Thu Apr 26, 2012 07:32
|
Arenio: Hello,
I've investigated that I have to change TP-PID and TP-DCS parameters of TPDU.
Is it possible to chnage these parameters via SMSTools3?
Thanks for yopur reply.
Arenio
|
|
Mon Apr 23, 2012 11:01
|
Arenio: Hello,
I would like to ask some of you if it's possible or not to send OTA data using SMSTools3?
Does somebody have an experience in this issue? I have proper SIM data for do this, of course.
I know that hex binary data is possible via SMSTools3 but I confused about UDH data that should be properly included in compliance with 3GPP TS 03.48 specification.
Thanks for your reply.
Arenio
|
|
Wed Feb 09, 2011 23:30
|
Arenio: Hello,
I would like to propose to implement W&B lists for incoming messages.
I know that it's possible to do it by a script (just deleting received messages) but I think it could be a good feature for the next realeses of SMS Server Tools 3 :D
Arenio
|
|
Sun Dec 05, 2010 20:22
|
Arenio: Really, I don't remember that I was changing device entry and why :?
I was sure that /dev/usb0 is ok.
I've removed rtscts and send_delay and it works.
Thanks.
|
|
Sun Dec 05, 2010 19:57
|
Arenio: Great :D
It works. I changed device as /dev/cuaU0 :mrgreen:
So there was the problem.
Thanks for help.
Arenio
|
|
Sat Dec 04, 2010 18:25
|
Arenio: I decided to completely uninstall SMSTools and install from the beginning. I deleted all SMSTools files etc.
Then I installed again. See the following terminal commands and outputs.
In smsd.conf I only changed device as /dev/usb0 .
# ll /dev/usb*
1090 crw-rw---- 1 root wheel 61, 0 Dec 2 22:54:26 2010 /dev/usb0
1091 crw-rw---- 1 root wheel 61, 1 Nov 7 00:21:13 2010 /dev/usb1
1092 crw-rw---- 1 root wheel 61, 2 Nov 7 00:21:13 2010 /dev/usb2
1093 crw-rw---- 1 root wheel 61, 3 Nov 7 00:21:13 2010 /dev/usb3
1094 crw-rw---- 1 root wheel 61, 4 Nov 7 00:21:13 2010 /dev/usb4
1095 crw-rw---- 1 root wheel 61, 5 Nov 7 00:21:13 2010 /dev/usb5
1096 crw-rw---- 1 root wheel 61, 6 Nov 7 00:21:13 2010 /dev/usb6
1097 crw-rw---- 1 root wheel 61, 7 Nov 7 00:21:13 2010 /dev/usb7
# usbdevs -dv
Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x8086), rev 1.00
uhub0
port 1 powered
port 2 addr 2: high speed, power 500 mA, config 1, Nokia Datacard(0x0612), Nokia(0x0421), rev 0.01, iSerialNumber 0.0.1
umsm0
umsm1
umsm2
umsm3
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x8086), rev 1.00
uhub1
port 1 powered
port 2 powered
# make install clean
===> smstools3-3.1.11p1 depends on: procmail-* - found
===> smstools3-3.1.11p1 depends on: mm-* - found
===> smstools3-3.1.11p1 depends on: gmake-* - found
===> Verifying specs: mm c
===> found mm.13.21 c.56.0
===> Installing smstools3-3.1.11p1 from /usr/ports/packages/i386/all/
smstools3-3.1.11p1: ok
--- +smstools3-3.1.11p1 -------------------
To have smsd start at boot time, you have to adapt
/etc/smsd.conf and insert the following into /etc/rc.local.
if [ -x /usr/local/bin/smsd ]; then
install -d -o _smsd /var/run/smsd
echo -n ' smsd'; /usr/local/bin/smsd
fi
smsd needs access to the serial port; this can be done by adding
the _smsd user to 'dialer' in /etc/group.
===> Cleaning for smstools3-3.1.11p1
# vi /etc/smsd.conf
# vi /etc/rc.local
# vi /etc/group
# sh /etc/rc.local
starting local daemons:.
smsd
# cd /var/spool/sms/outgoing/
# vi mysms
# ll /var/spool/sms/outgoing/
total 8
80 drwxrwx--- 2 _smsd _smsd 512B Dec 4 19:17:25 2010 ./
64 drwxr-xr-x 5 root wheel 512B Dec 4 19:14:13 2010 ../
# ll /var/spool/sms/checked/
total 12
79 drwxrwx--- 2 _smsd _smsd 512B Dec 4 19:17:25 2010 ./
64 drwxr-xr-x 5 root wheel 512B Dec 4 19:14:13 2010 ../
92 -rw-r--r-- 1 _smsd _smsd 33B Dec 4 19:17:25 2010 mysms
# ll /var/spool/sms/checked/
total 12
79 drwxrwx--- 2 _smsd _smsd 512B Dec 4 19:17:25 2010 ./
64 drwxr-xr-x 5 root wheel 512B Dec 4 19:14:13 2010 ../
92 -rw-r--r-- 1 _smsd _smsd 33B Dec 4 19:17:25 2010 mysms
# ll /var/spool/sms/checked/
total 12
79 drwxrwx--- 2 _smsd _smsd 512B Dec 4 19:17:25 2010 ./
64 drwxr-xr-x 5 root wheel 512B Dec 4 19:14:13 2010 ../
92 -rw-r--r-- 1 _smsd _smsd 33B Dec 4 19:17:25 2010 mysms
# cat /var/log/smsd/smsd.log
2010-12-04 19:16:53,2, smsd: Smsd v3.1.11 started.
2010-12-04 19:16:53,2, smsd: Running as _smsd:_smsd.
2010-12-04 19:16:53,7, smsd: Running startup_check (shell): /tmp/smsd_script.OcPy2x /tmp/smsd_data.RNsl0n
2010-12-04 19:16:53,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2010-12-04 19:16:53,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-12-04 19:16:53,5, smsd: Outgoing file checker has started. PID: 2395.
2010-12-04 19:16:53,5, GSM1: Modem handler 0 has started. PID: 6991. Will only send messages.
2010-12-04 19:16:53,3, GSM1: Couldn't open serial port /dev/usb0, error: Permission denied, waiting 30 sec.
2010-12-04 19:17:23,3, GSM1: Cannot open serial port /dev/usb0, error: Permission denied
2010-12-04 19:17:23,2, GSM1: Modem handler 0 terminated. PID: 6991, was started 10-12-04 19:16:53.
2010-12-04 19:17:25,5, smsd: Moved file /var/spool/sms/outgoing/mysms to /var/spool/sms/checked
|
|
Thu Dec 02, 2010 21:46
|
Arenio: I didn't change any permissions for /dev/usb0 and only at smd.conf file the device and the log file I changed.
_smd is not in the wheel group.
I'm sure that I didn't change anything except device and log file entries.
I've restarted the server, reinstalled the SMSTools and the problem still exists :?
I suppose that for some reason the device is busy or something like that and SMSTools cannot get the access to the device.
|
|
Wed Dec 01, 2010 17:54
|
Arenio: I always have rtscts = no even during the last my conf with handshake set to no.
Problem is still the same:
Cannot open serial port /dev/usb0, error: Permission denied
or
GSM1: Checking if modem is ready
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
or
GSM1: Checking if modem is ready
GSM1: -> AT
GSM1: Modem is not clear to send
Why it doesn't work?
Answer is difficult because it worked before errors occurs and I don't know why it doesn't work now :?
I run smsd deamon as _smd user with no errors before, strange.
|
|
Tue Nov 30, 2010 23:05
|
Arenio: I didn't make any OS updates. I've tried with no handshake and the result is below.
smsd: Smsd v3.1.11 started.
smsd: Running as root:wheel.
smsd: Running startup_check (shell): /tmp/smsd_script.Q2w4nz /tmp/smsd_data.39OHBu
smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
smsd: File mode creation mask: 022 (0644, rw-r--r--).
smsd: Mainspooler uses GSM1 to send administrative messages.
smsd: Outgoing file checker has started. PID: 9167.
GSM1: Modem handler 0 has started. PID: 31975. Will only send messages.
GSM1: Checking if modem is ready
GSM1: -> AT
GSM1: Modem is not clear to send
GSM1: ->
GSM1: Modem is not clear to send
GSM1: -> AT
GSM1: Modem is not clear to send
GSM1: ->
GSM1: Modem is not clear to send
GSM1: -> AT
GSM1: Modem is not clear to send
GSM1: ->
GSM1: Modem is not clear to send
GSM1: -> AT
GSM1: Modem is not clear to send
GSM1: ->
|
|
Tue Nov 30, 2010 22:27
|
Arenio: I don't think so in order it's with privileges problem. I've changed _smsd user to root in smsd.conf .
ls -l /dev/usb0:
1090 crw-rw---- 1 root wheel 61, 0 Nov 30 23:21:04 2010 /dev/usb0
smsd.log:
smsd: Smsd v3.1.11 started.
smsd: Running as root:wheel.
smsd: Running startup_check (shell): /tmp/smsd_script.SmKYHf /tmp/smsd_data.F6qGyQ
smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
smsd: File mode creation mask: 022 (0644, rw-r--r--).
smsd: Mainspooler uses GSM1 to send administrative messages.
smsd: Outgoing file checker has started. PID: 11925.
GSM1: Modem handler 0 has started. PID: 26797. Will only send messages.
GSM1: Checking if modem is ready
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: -> AT
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: ->
GSM1: write_to_modem: error 19: Operation not supported by device
GSM1: Modem is not ready to answer commands (Timeouts: 0)
GSM1: Failed to initialize modem GSM1. Stopping.
GSM1: Modem handler 0 terminated. PID: 26797, was started 10-11-30 23:20:35.
I have old log file when SMSTools worked fine.
smsd: Smsd v3.1.11 started.
smsd: Running as _smsd:_smsd.
smsd: Running startup_check (shell): /tmp/smsd_script.sG2fWh /tmp/smsd_data.8OCJjr
smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
smsd: File mode creation mask: 022 (0644, rw-r--r--).
smsd: Outgoing file checker has started. PID: 6843.
GSM1: Modem handler 0 has started. PID: 16193. Will only send messages.
GSM1: Checking if modem is ready
GSM1: -> AT
GSM1: Command is sent, waiting for the answer
GSM1: <- AT OK
GSM1: Pre-initializing modem
GSM1: -> ATE0+CMEE=1
GSM1: Command is sent, waiting for the answer
GSM1: <- ATE0+CMEE=1 OK
GSM1: Checking if modem needs PIN
GSM1: -> AT+CPIN?
GSM1: Command is sent, waiting for the answer
GSM1: <- +CPIN: READY OK
GSM1: -> AT+CSQ
GSM1: Command is sent, waiting for the answer
GSM1: <- +CSQ: 16,0 OK
GSM1: Signal Strength Indicator: (16,0) -81 dBm, Bit Error Rate: less than 0.2 %
GSM1: Checking if Modem is registered to the network
GSM1: -> AT+CREG?
GSM1: Command is sent, waiting for the answer
GSM1: <- +CREG: 0,5 OK
GSM1: Modem is registered to a roaming partner network
GSM1: Selecting PDU mode
GSM1: -> AT+CMGF=0
GSM1: Command is sent, waiting for the answer
GSM1: <- OK
GSM1: -> AT+CIMI
GSM1: Command is sent, waiting for the answer
|
|
Tue Nov 30, 2010 22:04
|
Arenio: Operating system name and version: OpenBSD 4.8
Version of smsd: 3.1.11
Smsd installed from: ports
Name and model of a modem / phone: Nokia Datacard
Interface: USB
Hello,
I have a problem with connection to a modem.
First time when I've run the SMSTools, It was working OK. But after one day, I've decided to change the path to the log file. And then errors occured.
After reinstalling SMSTools with defaults settings (log file etc.) problem is still the same.
Error from smsd.log:
smsd: Smsd v3.1.11 started.
smsd: Running as _smsd:_smsd.
smsd: Running startup_check (shell): /tmp/smsd_script.dVkYH1 /tmp/smsd_data.IV2ExN
smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
smsd: File mode creation mask: 022 (0644, rw-r--r--).
smsd: Outgoing file checker has started. PID: 29018.
GSM1: Modem handler 0 has started. PID: 7797. Will only send messages.
GSM1: Couldn't open serial port /dev/usb0, error: Permission denied, waiting 30 sec.
GSM1: Cannot open serial port /dev/usb0, error: Permission denied
GSM1: Modem handler 0 terminated. PID: 7797, was started 10-11-30 22:36:44.
smsd.conf:
# $OpenBSD: smsd.conf.openbsd,v 1.3 2010/06/30 16:45:27 sthen Exp $
# See /usr/local/share/doc/smstools/configure.html for more details
devices = GSM1
#devices = GSM1, GSM2
loglevel = 7
# After initial setup this might be a good option; notices by default,
# but debug logging is buffered and stored to another file after an error.
#loglevel = 5
#smart_logging = yes
# setuid() to this user:
user = _smsd
# it's possible to setgid too, but default is the set of
# groups from /etc/groups
pidfile = /var/run/smsd/smsd.pid
infofile = /var/run/smsd/smsd.info
#logfile = syslog
logfile = /var/log/smsd/smsd.log
[GSM1]
# A sample USB device with typical broken rtscts, so use
# a send delay to reduce the risk of overruns. Some PC cards
# also break rts/cts. On some 3G cards you might be able to
# use the control device for SMS simultaneously with using
# the data device for a PPP connection.
# For this one I have set incoming=no so it doesn't pull
# the existing messages off the phone.
device = /dev/usb0
incoming = no
rtscts = no
send_delay = 20
# smsc = +447958879879 # some devices need the smsc to be explicitly set
# memory_start = 0 # defaults to 1; some devices start their index at 0
# init = ATE0 # /usr/local/share/doc/smstools/hardwarecomp.html
# pin = 1111 # pin normally used only with data cards, not phones
[GSM2]
#device = /dev/cua00
#incoming = yes
And I don't know where is the problem because before it was workig fine.
The Nokia Datacard USB modem works at Windows.
Thanks for help.
Arenio
|
