|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Thu Mar 13, 2025 05:26 |
Page: 1 2 Next
| Keywords: Mode: All keywords (AND) |
|
Thu May 16, 2024 06:59
|
electronico_nc: Hi all,
We have to use the driver from manufactor that creates a virtualport in /dev/ttyr00
|
|
Mon Nov 27, 2023 22:54
|
electronico_nc: Operating system name and version: Ubuntu 18.04.06
Version of smsd: 3.1.21
Smsd installed from: sources
Name and model of a modem / phone: FALCOM Tango-55
Interface: serial / USB
Hello,
I'll be in need to move this serial modem to IP.
The RS-232 / IP converter is not avalaible right now, so tests can't be run right now.
Seeking the forum for smsd config, I found that I would have the replace
devices = GSM1
...
[GSM1]
device = /dev/ttyUSB1
... with :
devices = GSMLAN1
...
[GSMLAN1]
device = @192.168.15.2:5000
...
Could someone confirm it will run with this kind of smsd.conf ?
Thanks in advance for your time !
Nicolas
|
|
Fri May 04, 2018 20:45
|
electronico_nc: Operating system name and version: ubuntu 12.04
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: not important
Interface: not important
Looking at src/pdu.c
case 0: p = "Ok,short message received by the SME"; break;
case 1: p = "Ok,short message forwarded by the SC to the SME but the SC is unable to confirm delivery"; break;
case 2: p = "Ok,short message replaced by the SC"; break;
// Temporary error, SC still trying to transfer SM
case 32: p = "Still trying,congestion"; break;
case 33: p = "Still trying,SME busy"; break;
case 34: p = "Still trying,no response sendr SME"; break;
case 35: p = "Still trying,service rejected"; break;
case 36: p = "Still trying,quality of service not available"; break;
case 37: p = "Still trying,error in SME"; break;
// 38...47: Reserved
// 48...63: Values specific to each SC
// Permanent error, SC is not making any more transfer attempts
case 64: p = "Error,remote procedure error"; break;
case 65: p = "Error,incompatible destination"; break;
case 66: p = "Error,connection rejected by SME"; break;
case 67: p = "Error,not obtainable"; break;
case 68: p = "Error,quality of service not available"; break;
case 69: p = "Error,no interworking available"; break;
case 70: p = "Error,SM validity period expired"; break;
case 71: p = "Error,SM deleted by originating SME"; break;
case 72: p = "Error,SM deleted by SC administration"; break;
case 73: p = "Error,SM does not exist"; break;
// 74...79: Reserved
// 80...95: Values specific to each SC
// Permanent error, SC is not making any more transfer attempts
case 96: p = "Error,congestion"; break;
case 97: p = "Error,SME busy"; break;
case 98: p = "Error,no response sendr SME"; break;
case 99: p = "Error,service rejected"; break;
case 100: p = "Error,quality of service not available"; break;
case 101: p = "Error,error in SME"; break;
// 102...105: Reserved
// 106...111: Reserved
// 112...127: Values specific to each SC
// 128...255: Reserved
default:
if (status >= 48 && status <= 63)
p = "Temporary error, SC specific, unknown";
else if ((status >= 80 && status <= 95) || (status >= 112 && status <= 127))
p = "Permanent error, SC specific, unknown";
I have troubles to understand under which circumstance can status 2 be returned.
-> Ok,short message replaced by the SC
Thanks in advance for your lights.
|
|
Tue Jul 12, 2016 01:18
|
|
|
|
Tue Jul 12, 2016 00:40
|
electronico_nc: Operating system name and version: Ubuntu 12.04.5 x64 3.2.0-105-generic
Version of smsd: Smsd v3.1.14
Smsd installed from: sources
Name and model of a modem / phone: FALCOM TANGO 55
Interface: serial to USB
Well, after nearly 8 years of good services, sms3 has failed once today.
Despite to have setup a lot of automatic failure detection that restarts sms3 when needed, it wasn't enough today.
Here is the log when sms3 wasn't running correctly (better tell the modem wasn't answreing correctly):
2016-07-12 09:43:06,7, GSM1: -> AT
2016-07-12 09:43:06,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:06,7, GSM1: <- OK
2016-07-12 09:43:06,6, GSM1: Pre-initializing modem
2016-07-12 09:43:06,7, GSM1: -> ATE0+CMEE=1
2016-07-12 09:43:06,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:07,7, GSM1: <- OK
2016-07-12 09:43:07,6, GSM1: Checking if modem needs PIN
2016-07-12 09:43:07,7, GSM1: -> AT+CPIN?
2016-07-12 09:43:07,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:07,7, GSM1: <- +CPIN: READY OK
2016-07-12 09:43:07,7, GSM1: -> AT+CSQ
2016-07-12 09:43:07,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:17,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2016-07-12 09:43:17,7, GSM1: <-
2016-07-12 09:43:17,7, GSM1: -> AT+CSQ
2016-07-12 09:43:17,7, GSM1: Command is sent, waiting for the answer
2016-07-12 09:43:27,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2016-07-12 09:43:27,7, GSM1: <-
Then after a sms3 stop and start, everything is back OK:
2016-07-12 10:03:17,5, smsd: Outgoing file checker has started. PID: 30027.
2016-07-12 10:03:17,5, smsd: Everything ok now.
2016-07-12 10:03:18,3, GSM1: Unexpected input: +CSQ: 16,99 OK +CSQ: 16,99 OK +CREG: 0,1 OK
2016-07-12 10:03:18,7, GSM1: -> AT
2016-07-12 10:03:18,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:18,7, GSM1: <- OK
2016-07-12 10:03:18,6, GSM1: Pre-initializing modem
2016-07-12 10:03:18,7, GSM1: -> ATE0+CMEE=1
2016-07-12 10:03:18,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:18,7, GSM1: <- OK
2016-07-12 10:03:18,6, GSM1: Checking if modem needs PIN
2016-07-12 10:03:19,7, GSM1: -> AT+CPIN?
2016-07-12 10:03:19,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:19,7, GSM1: <- +CPIN: READY OK
2016-07-12 10:03:19,7, GSM1: -> AT+CSQ
2016-07-12 10:03:19,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:19,7, GSM1: <- +CSQ: 16,99 OK
2016-07-12 10:03:19,6, GSM1: Signal Strength Indicator: (16,99) -81 dBm (Good)
2016-07-12 10:03:19,6, GSM1: Checking if Modem is registered to the network
2016-07-12 10:03:20,7, GSM1: -> AT+CREG?
2016-07-12 10:03:20,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:20,7, GSM1: <- +CREG: 0,1 OK
2016-07-12 10:03:20,6, GSM1: Modem is registered to the network
2016-07-12 10:03:20,6, GSM1: Selecting PDU mode
2016-07-12 10:03:20,7, GSM1: -> AT+CMGF=0
2016-07-12 10:03:20,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:20,7, GSM1: <- OK
2016-07-12 10:03:20,6, GSM1: Changing SMSC
2016-07-12 10:03:21,7, GSM1: -> AT+CSCA="+687770009"
2016-07-12 10:03:21,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:21,7, GSM1: <- OK
2016-07-12 10:03:21,7, GSM1: -> AT+CIMI
2016-07-12 10:03:21,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:21,7, GSM1: <- 546010100209020 OK
2016-07-12 10:03:22,7, GSM1: -> AT+CGSN
2016-07-12 10:03:22,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:22,7, GSM1: <- 357248015960598 OK
2016-07-12 10:03:22,5, GSM1: CGSN: 357248015960598
2016-07-12 10:03:22,5, GSM1: IMSI: 546010100209020
2016-07-12 10:03:22,6, GSM1: Checking if reading of messages is supported
2016-07-12 10:03:22,7, GSM1: -> AT+CPMS?
2016-07-12 10:03:22,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:22,7, GSM1: <- +CPMS: "MT",1,49,"MT",1,49,"MT",1,49 OK
2016-07-12 10:03:22,6, GSM1: Checking memory size
2016-07-12 10:03:23,7, GSM1: -> AT+CPMS?
2016-07-12 10:03:23,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:23,7, GSM1: <- +CPMS: "MT",1,49,"MT",1,49,"MT",1,49 OK
2016-07-12 10:03:23,6, GSM1: Used memory is 1 of 49
2016-07-12 10:03:23,6, GSM1: Trying to get stored message 1
2016-07-12 10:03:23,7, GSM1: -> AT+CMGR=1
2016-07-12 10:03:23,7, GSM1: Command is sent, waiting for the answer
2016-07-12 10:03:24,7, GSM1: <- +CMGR: 0,,22 069186770700F924099186772869F400006170219065904404D4F29C0E OK
When modem wasn't answering to AT+CSQ , tests about sms3 state where running without problem:
/bin/ps ax | grep -v grep | grep 'smsd -n MAINPROCESS'
28447 ? Ss 0:34 /usr/local/bin/smsd -n MAINPROCESS -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.log
/bin/ps ax | grep -v grep | grep 'GSM1_'
28448 ? S 65:32 /usr/local/bin/smsd -n GSM1_______ -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.log
/bin/ps ax | grep -v grep | grep '[smsd] <defunct>'
What would be an option to detect this failure ?
Thanks in advance for your time.
(I think it is a sporadic failure, but I'd like to try to fix it)
|
|
Mon Aug 05, 2013 21:12
|
|
|
|
Mon Aug 05, 2013 17:53
|
electronico_nc: Just would like to tell that I would have expected that the date fields from received SMS would be :
Sent: 2013-08-05 13:41:20
Received: 2013-08-05 13:41:30
and not :
Sent: 13-08-05 13:41:20
Received: 13-08-05 13:41:30
|
|
Mon Aug 05, 2013 17:43
|
electronico_nc: Please disreagard (delete) this post.
There were a mixup with the server that send SMS to mine.
The 'Sent:' date is well the SMS creation date.
|
|
Mon Aug 05, 2013 05:27
|
electronico_nc: Operating system name and version: Ubuntu 12.04.2 server 3.2.0-51 X64
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: FALCOM TANGO 55
Interface: USB to serial
Hello,
I'm an happy smstools user for years (thanks again for this software).
Now I'm in need to know the date created for a received SMS.
I haven't been able to find this in the parameters.
Thanks in advance for your lights!
|
|
Tue Nov 06, 2012 19:12
|
electronico_nc: Found a newer 3G USB stick, configured it for 3G (ttyUSB5) and I can send SMS via ttyUSB4.
This was due to this old ZTE K3565-Z.
|
|
Sat Nov 03, 2012 07:17
|
electronico_nc: Hello,
I'm not an expert but I would first suggest to upgrade smstools to the latest version (3.1.15) or at least the one available in ubuntu 10.04 repositories (3.1.14).
Then I would check the file permissions for your /smsgateway/smstools3/scripts/evento_accion2 file (executable ?)
Hope this helps.
|
|
Thu Nov 01, 2012 23:32
|
electronico_nc: 1) please fill the form embedded in new posts (to win time) :
Operating system name and version:
Version of smsd:
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone:
Interface: serial / USB / some adapter...
2) if node /dev/ttyUSB2 is not found, I don't see how your smsd could run (from what you said).
|
|
Thu Nov 01, 2012 04:17
|
electronico_nc: Hi,
No it is not possible via standard SMS protocol.
Some (I don't know which) paid SMS Gateways can "offer" this kind of options.
|
|
Thu Nov 01, 2012 03:53
|
electronico_nc: Operating system name and version: Ubuntu 12.04.1 LTS server
Version of smsd: 3.1.15
Smsd installed from: sources
Name and model of a modem / phone: USB 3G ZTE 3565-Z
Interface: USB
Well,
This is not especially smstools relative, but I know there are lot of experienced people here...
After a lot of work, tries, searches, I've succeed to connect this ZTE 3565-Z 3G USB stick to Internet on this server.
The main problem I face is that once this device has dialed the required *99# to connect to Internet, device is busy so I can't send it AT commands to send a SMS.
I don't have any other 3G USB stick at hand right now, so I wonder :
- Is it just this device that can't send a SMS once connected via 3G ? (my phone can do it)
Thanks in advance for your time.
|
|
Tue Oct 30, 2012 21:06
|
electronico_nc: Hello,
No, the GSM protocol doesn't allow any field to be 'pre-filled' (except DA) by replying to a SMS.
|
|
Tue Oct 30, 2012 21:03
|
electronico_nc: Hello,
Supposing you're using a Debian-like distro ( ??? )
What's the output of :sudo udevadm info --query=all --name=ttyUSB2
|
|
Mon Jun 25, 2012 20:46
|
|
|
|
Thu Jun 21, 2012 22:48
|
electronico_nc: Hi all,
For a specific case, I would like to simulate a received SMS that will be created then treated by eventhandler.
The easiest way is to use the sendsms command but it will cost me 1 SMS to phone provider.
So I'd like to know if I can create a file containing the SMS so it can be treated by eventhandler.
As my eventhandler only use the From field and SMS content, I've tried to create a file in /var/spool/sms/incoming named GSM1.000001 with this content:From: localhost
My SMS text herebut eventhandler doesn't look at it...
(for sure if I tell eventhandler to test the file, it works : /usr/local/bin/smsd_eventhandler.sh RECEIVED /var/spool/sms/incoming/GSM1.000001 )
Is there a way to do this or must I send a SMS ?
Thanks in advance for your time.
|
|
Thu Jun 21, 2012 22:17
|
electronico_nc: Hi,
First check if your ttyUSB0 doesn't change at reboot, if so read : http://smstools3.kekekasvi.com/topic.php?id=482
I use a really basic script (run by cron) to check smsd state.
Adjust your modem name if it's not called GSM1:cat smsd_check.sh
#!/bin/sh
SMSTOOLS_STOP="/etc/init.d/sms3 stop"
SMSTOOLS_START="/etc/init.d/sms3 start"
if ps ax | grep -v grep | grep 'smsd -n MAINPROCESS' > /dev/null
then
echo "smsd OK" > /dev/null
else
$SMSTOOLS_STOP
$SMSTOOLS_START
fi
if ps ax | grep -v grep | grep 'GSM1_' > /dev/null
then
echo "smsd OK" > /dev/null
else
$SMSTOOLS_STOP
$SMSTOOLS_START
fi
if ps ax | grep -v grep | grep 'GSM1_' | grep '<defunct>' > /dev/null
then
$SMSTOOLS_STOP
$SMSTOOLS_START
fi
Hope this helps
|
|
Mon Oct 03, 2011 02:49
|
electronico_nc: [1500387.870117] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[1500387.873060] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[1500387.876165] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
-> This should fix your problem about USB change
|
|
Mon Oct 03, 2011 02:02
|
electronico_nc: Operating system name and version: 2.6.32-34-server #77-Ubuntu SMP Tue Sep 13 20:54:38 UTC 2011 x86_64 GNU/Linux
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: FALCOM TANGO-55 RS-232
Interface: mos7720 Moschip 2 port adapter converter USB-RS232
Well this is regarding this message (can't answer as it has been locked).
My USB ports sometimes disconnect (happened only twice this year).
I wanted to try the keke's script, but I haven't been able to make it run :?
So here is the one I've used : smsd_check.sh (run by a cron every minute)#!/bin/sh
SMSTOOLS_STOP="/etc/init.d/sms3 stop"
SMSTOOLS_START="/etc/init.d/sms3 start"
if ps ax | grep -v grep | grep 'smsd -n MAINPROCESS' > /dev/null
then
echo "smsd OK" > /dev/null
else
$SMSTOOLS_STOP > /dev/null
$SMSTOOLS_START > /dev/null
fi
if ps ax | grep -v grep | grep 'GSM1_' > /dev/null
then
echo "smsd OK" > /dev/null
else
$SMSTOOLS_STOP > /dev/null
$SMSTOOLS_START > /dev/null
fi
Then I tried to disconnect the USB port from server, wait a few seconds, plug it again.
The bad thing is that GSM1 was still running (so the script can't restart sms3) and I had in the smsd.log2011-10-03 12:34:52,3, GSM1: write_to_modem: error 5: Input/output error
2011-10-03 12:35:02,3, GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
Could someone give some tracks on how I might detect this error then restart smsd ?
|
|
Fri Mar 18, 2011 23:44
|
electronico_nc: This is probably not the only answer to your problem if there are really hardware defaults, but about ttyUSBx changes, see this post
|
|
Mon Mar 14, 2011 22:18
|
electronico_nc: Okay, but why are USB ports gone away when UPS goes on battery? Isn't it the main problem, as UPS should still deliver the power? Or is the UPS too small, and cannot feed the adapter and modem? ;)UPS is a 800VA model and it well feeds the server and the modem, thanks for asking ;)
Its online power consumption is 9VA, so no trouble with this.
I have tried a dozen times to unplug it's main cord (to simulate a power failure) and this has NEVER disconnected the modem USB port ... So I think it is a problem that only occurs sometimes ...
I'll post if I find further infos about this.
Thanks again.
|
|
Mon Mar 14, 2011 19:18
|
electronico_nc: cat /var/log/smsd.log.12011-03-11 18:31:41,2, GSM1: PIN handling: expected READY, modem answered
2011-03-11 18:31:41,2, GSM1: Modem handler 0 terminated abnormally. PID: 2106.cat /var/log/messages.1 | grep usbMar 11 18:31:31 server1 kernel: [521982.541503] usb 2-1: USB disconnect, address 2
Mar 11 18:31:32 server1 kernel: [521982.820011] usb 2-1: new full speed USB device using uhci_hcd and address 3
Mar 11 18:31:32 server1 kernel: [521982.981924] usb 2-1: configuration #1 chosen from 1 choice
Mar 11 18:31:32 server1 kernel: [521982.988903] usb 2-1: Moschip 2 port adapter converter now attached to ttyUSB3
Mar 11 18:31:32 server1 kernel: [521982.988944] usb 2-1: Moschip 2 port adapter converter now attached to ttyUSB4
Mar 11 18:31:38 server1 kernel: [521989.041497] usb 3-1: USB disconnect, address 4
Mar 11 18:31:38 server1 kernel: [521989.320083] usb 3-1: new low speed USB device using uhci_hcd and address 5
Mar 11 18:31:38 server1 kernel: [521989.503163] usb 3-1: configuration #1 chosen from 1 choiceFrom your answer, I understand that smsd has quit because USB port has been lost.
It turns out that this is caused by main a main power lost.
cat /var/log/ups.log2011-03-11 18:31:35 - server1 : Main power failure. UPS on battery.
2011-03-11 18:32:30 - server1 : Main power back.I'll update my UPS script to restart smsd when power is back.
Thanks so much keke to have pointed out the different ways for smsd to stop !
|
|
Mon Mar 14, 2011 01:43
|
electronico_nc: Operating system name and version: Linux 2.6.32-29-server #58-Ubuntu SMP Fri Feb 11 21:06:51 UTC 2011 x86_64 GNU/Linux
Version of smsd: 3.1.14
Smsd installed from: source
Name and model of a modem / phone: FALCOM TANGO-55 RS-232
Interface: mos7720 Moschip 2 port adapter converter USB-RS232
Well, I had the bad surprise to see that smsd was not running anymore.
sms3 is well installed with rc-inits :sudo sysv-rc-conf --list | grep sms
sms3 0:off 1:off 2:on 3:on 4:on 5:on 6:offGSM1 service was not runningps -All | grep sms
1 S 0 2105 1 0 80 0 - 4003 hrtime ? 00:00:34 smsd
1 Z 0 2106 2105 0 80 0 - 0 exit ? 00:56:06 smsd <defunct>I had to restart it to make it run:sudo /etc/init.d/sms3 restart
Starting SMS Daemon: smsd.Now all is OKps ax | grep sms
26107 ? Ss 0:00 /usr/local/bin/smsd -n MAINPROCESS -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.log
26108 ? S 0:33 /usr/local/bin/smsd -n GSM1_______ -p/var/run/smsd.pid -i/var/run/smsd.working -uroot -gdialout -l/var/log/smsd.logBut I would like to know if some of you have experienced this kind of problem ...
I plan to check if there is no defunct flag on smsd lines and restart service is needed but I would prefer to understand how it can have been in default.
Thanks in advance for your time.
|
Page: 1 2 Next
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
