|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 10:55 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Tue Feb 22, 2011 10:30
|
cyanshade: Operating system name and version: Debian 5.0.8
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: WAVECOM Fastrack Xtend GPRS
Interface: serial
This WAVECOM unit had all kinds of trouble when used with a USB link, so a serial cable has now been in use for a few weeks. However, the unit still hangs seemingly at random after prolonged use.
The log file always reports the same thing:
-> AT
Command is sent, waiting for the answer
put_command expected (OK)|(ERROR), timeout occurred
<-
At this point, restarting sms3 to reset the modem doesn't work. The unit remains completely mute until power cycled. The problem will repeat itself every 2 or 3 days.
Here's the config. send_handshake_select used to be "no" because it made the USB link a bit more stable. It doesn't seem to affect how often the device hangs when connected via serial.
devices = GSM1
logfile = /var/log/smsd.log
loglevel = 4
smart_logging = yes
stats = /var/spool/sms/stats
store_received_pdu = 3
hangup_incoming_call = yes
voicecall_hangup_ath = yes
datetime_format = %Y-%m-%d %H:%M:%S
alarmhandler = /usr/local/bin/alarmhandler
eventhandler = /usr/local/bin/eventhandler
regular_run = /usr/local/bin/regular_run
regular_run_interval = 60
[GSM1]
device = /dev/ttyS0
baudrate = 115200
rtscts = yes
init = AT+CNMI=1,0,0,2,0
#send_handshake_select = no # this tweak was for ttyACM0, testing without
primary_memory = SM
secondary_memory = SR
report_device_details = yes
incoming = yes
mode = new
smsc = 358451100100
pin = **** # removed
cs_convert = yes
report = yes
Elsewhere on the site it was suggested that an unstable power supply can cause unexplained behaviour. However, this unit is powered through a heavy duty Fiskars UPS and the supplied power brick.
|
|
Tue Nov 23, 2010 14:38
|
cyanshade: That did the trick, thanks! :)
I now have send/receive/report working and can replace the ludicrously expensive content gateway. Hurray.
|
|
Tue Nov 23, 2010 12:42
|
cyanshade: Here's the latest test:
( PRIVATE BLOCK )
|
|
Tue Nov 23, 2010 12:26
|
cyanshade: Changing the memory setting had no effect. :(
|
|
Tue Nov 23, 2010 11:58
|
cyanshade: 2010-11-23 13:55:55,2, smsd: Smsd v3.1.14 started.
2010-11-23 13:55:55,2, smsd: Running as root:root.
2010-11-23 13:55:55,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.GMRaPR /tmp/smsd_data.4C8tTT
2010-11-23 13:55:55,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2010-11-23 13:55:55,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-11-23 13:55:55,6, smsd: Using datetime format "%Y-%m-%d %H:%M:%S". It produces "2010-11-23 13:55:55".
2010-11-23 13:55:55,5, smsd: Outgoing file checker has started. PID: 6438.
2010-11-23 13:55:55,7, smsd: All PID's: 6438,6440
2010-11-23 13:55:55,6, smsd: Running a regular_run.
2010-11-23 13:55:55,7, smsd: Running regular_run (mainprocess): /var/www/html/pigeon/regular_run
2010-11-23 13:55:55,5, GSM1: Modem handler 0 has started. PID: 6440.
2010-11-23 13:55:55,5, GSM1: Using check_memory_method 1: CPMS is used.
2010-11-23 13:55:55,6, GSM1: Checking device for incoming SMS
2010-11-23 13:55:55,6, GSM1: Checking if modem is ready
2010-11-23 13:55:56,7, GSM1: -> AT
2010-11-23 13:55:56,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:56,7, smsd: Done: regular_run (mainprocess), execution time 1 sec., status: 0 (0)
2010-11-23 13:55:56,7, GSM1: <- AT OK
2010-11-23 13:55:56,6, GSM1: Pre-initializing modem
2010-11-23 13:55:56,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2010-11-23 13:55:56,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:56,7, GSM1: <- ATE0+CMEE=1;+CREG=2 OK +CREG: 5,"4ACE","F62B"
2010-11-23 13:55:56,6, GSM1: Checking if modem needs PIN
2010-11-23 13:55:57,7, GSM1: -> AT+CPIN?
2010-11-23 13:55:57,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:57,7, GSM1: <- +CPIN: READY
2010-11-23 13:55:57,7, GSM1: -> AT+CSQ
2010-11-23 13:55:57,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:57,7, GSM1: <- +CSQ: 20,0 OK
2010-11-23 13:55:57,6, GSM1: Signal Strength Indicator: (20,0) -73 dBm (Excellent), Bit Error Rate: less than 0.2 %
2010-11-23 13:55:57,6, GSM1: Checking if Modem is registered to the network
2010-11-23 13:55:58,7, GSM1: -> AT+CREG?
2010-11-23 13:55:58,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:58,7, GSM1: <- +CREG: 2,5,"4ACE","F62B" OK
2010-11-23 13:55:58,6, GSM1: Modem is registered to a roaming partner network
2010-11-23 13:55:58,6, GSM1: Location area code: 4ACE, Cell ID: F62B
2010-11-23 13:55:58,7, GSM1: -> AT+CSQ
2010-11-23 13:55:58,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:58,7, GSM1: <- +CSQ: 22,0 OK
2010-11-23 13:55:58,6, GSM1: Signal Strength Indicator: (22,0) -69 dBm (Excellent), Bit Error Rate: less than 0.2 %
2010-11-23 13:55:58,6, GSM1: Selecting PDU mode
2010-11-23 13:55:59,7, GSM1: -> AT+CMGF=0
2010-11-23 13:55:59,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:59,7, GSM1: <- OK
2010-11-23 13:55:59,6, GSM1: Changing SMSC
2010-11-23 13:55:59,7, GSM1: -> AT+CSCA="+358451100100"
2010-11-23 13:55:59,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:55:59,7, GSM1: <- OK
2010-11-23 13:56:00,7, GSM1: -> AT+CIMI
2010-11-23 13:56:00,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:56:00,7, GSM1: <- 244212000005057 OK
2010-11-23 13:56:00,7, GSM1: -> AT+CGSN
2010-11-23 13:56:00,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:56:00,7, GSM1: <- 354662030032873 OK
2010-11-23 13:56:00,5, GSM1: CGSN: 354662030032873
2010-11-23 13:56:00,5, GSM1: IMSI: 244212000005057
2010-11-23 13:56:00,6, GSM1: Checking if reading of messages is supported
2010-11-23 13:56:01,7, GSM1: -> AT+CPMS?
2010-11-23 13:56:01,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:56:01,7, GSM1: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2010-11-23 13:56:01,7, GSM1: ## Start of device details
2010-11-23 13:56:01,7, GSM1: # Manufacturer identification:
2010-11-23 13:56:01,7, GSM1: -> AT+CGMI
2010-11-23 13:56:01,7, GSM1: <- WAVECOM WIRELESS CPU
OK
2010-11-23 13:56:01,7, GSM1: # Model identification:
2010-11-23 13:56:02,7, GSM1: -> AT+CGMM
2010-11-23 13:56:02,7, GSM1: <- MULTIBAND 900E 1800
OK
2010-11-23 13:56:02,7, GSM1: # Revision identification:
2010-11-23 13:56:02,7, GSM1: -> AT+CGMR
2010-11-23 13:56:02,7, GSM1: <- R7.43.0.201003261552.FXT001 2139952 032610 15:52
OK
2010-11-23 13:56:02,7, GSM1: # New message indications, list of supported modes:
2010-11-23 13:56:03,7, GSM1: -> AT+CNMI=?
2010-11-23 13:56:03,7, GSM1: <- +CNMI: (0-3),(0-3),(0-3),(0-2),(0,1)
OK
2010-11-23 13:56:03,7, GSM1: # New message indications, current settings:
2010-11-23 13:56:03,7, GSM1: -> AT+CNMI?
2010-11-23 13:56:03,7, GSM1: <- +CNMI: 0,1,0,0,0
OK
2010-11-23 13:56:03,7, GSM1: # Preferred message storage, list of supported mem's:
2010-11-23 13:56:04,7, GSM1: -> AT+CPMS=?
2010-11-23 13:56:04,7, GSM1: <- +CPMS: (("SM","ME","BM","SR"),("SM","ME"),("SM","ME"))
OK
2010-11-23 13:56:04,7, GSM1: # Phonebook storage, available mem's:
2010-11-23 13:56:04,7, GSM1: -> AT+CPBS=?
2010-11-23 13:56:04,7, GSM1: <- +CPBS: ("SM","FD","LD","MC","ME","RC","MT","EN","SN")
OK
2010-11-23 13:56:04,7, GSM1: # List messages, list of supported stat's:
2010-11-23 13:56:05,7, GSM1: -> AT+CMGL=?
2010-11-23 13:56:05,7, GSM1: <- +CMGL: (0-4)
OK
2010-11-23 13:56:05,7, GSM1: # Delete message, list of supported values:
2010-11-23 13:56:05,7, GSM1: -> AT+CMGD=?
2010-11-23 13:56:05,7, GSM1: <- OK
2010-11-23 13:56:05,7, GSM1: # Phone activity status, list of supported stat's:
2010-11-23 13:56:06,7, GSM1: -> AT+CPAS=?
2010-11-23 13:56:06,7, GSM1: <- +CPAS: (0-5)
OK
2010-11-23 13:56:06,7, GSM1: # TE character set, list of supported charset's:
2010-11-23 13:56:06,7, GSM1: -> AT+CSCS=?
2010-11-23 13:56:06,7, GSM1: <- +CSCS: ("GSM","PCCP437","CUSTOM","HEX")
OK
2010-11-23 13:56:06,7, GSM1: # TE character set, current setting:
2010-11-23 13:56:07,7, GSM1: -> AT+CSCS?
2010-11-23 13:56:07,7, GSM1: <- +CSCS: "PCCP437"
OK
2010-11-23 13:56:07,7, GSM1: ## End of device details
2010-11-23 13:56:07,6, GSM1: Checking memory size
2010-11-23 13:56:07,7, GSM1: -> AT+CPMS?
2010-11-23 13:56:07,7, GSM1: Command is sent, waiting for the answer
2010-11-23 13:56:07,7, GSM1: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK
2010-11-23 13:56:07,6, GSM1: Used memory is 0 of 30
2010-11-23 13:56:07,6, GSM1: No SMS received
Another head scratcher is why the device reports being registered in a roaming partner network. Makes no sense.
|
|
Tue Nov 23, 2010 11:47
|
cyanshade: Operating system name and version: Debian Linux 5.0.6
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: WAVECOM Fastrack Xtend GPRS
Interface: USB
Having written my own eventhandler and regular_run scripts, I can now send and receive messages stored in a MySQL database. However, delivery reports are never seen, and looking at the configuration options I haven't found anything wrong.
My eventhandler has been set up to report the [filename] and <message_id> it gets as parameters $2 and $3 when SENT fires. These are present:
Nov 23 13:34:41 marissa eventhandler: SENT event fired.
Nov 23 13:34:41 marissa eventhandler: [119102] <33> Sent.
However, no REPORT events ever occur. Does this modem need special treatment with AT commands to have the delivery reports work? Looking through other threads the relevant commands seem to be:
at+cnmi?
+CNMI: 0,1,0,0,0
at+cpms?
+CPMS: "SM",0,30,"SM",0,30,"SM",0,30
Do these require tweaking?
|
|
Wed Nov 17, 2010 14:37
|
cyanshade: I never tried long strings in minicom, so this detail is unclear. Typical AT commands worked instantly though.
Before setting send_handshake_select = no, I noticed that smsd always hung after sending its first AT, but it did continue when something else was requested of it, like sending a message would make it notice the AT OK and it would then send the init line and again stop there until nudged...
Does it matter that it's running on AMD64?
$ uname -a
Linux marissa 2.6.26-2-amd64 #1 SMP Mon Jun 21 07:30:07 UTC 2010 x86_64 GNU/Linux
|
|
Wed Nov 17, 2010 14:19
|
cyanshade: send_handshake_select worked perfectly, thanks for the quick reply!
|
|
Wed Nov 17, 2010 13:39
|
cyanshade: Operating system name and version: Debian Linux 5.0.6
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: WAVECOM Fastrack Xtend GPRS
Interface: USB
This Wavecom seemed to work correctly over a serial link (115200 with hardware flow control), until a longer message (>100 chars) was sent. Any long string would hang the device completely.
I suspected the serial cable could be faulty and switched to USB. Minicom works happily with the device that sits at /dev/ttyACM0 configured to 115200 baud. However, smsd refuses to talk to this device completely.
Here's my smsd.conf with non-relevant lines commented out for testing:
devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7
smart_logging = yes
stats = /var/spool/sms/stats
#store_received_pdu = 3
#hangup_incoming_call = yes
#voicecall_hangup_ath = yes
#datetime_format = %Y-%m-%d %H:%M:%S
[GSM1]
device = /dev/ttyACM0
baudrate = 115200
rtscts = yes
#report_device_details = yes
#incoming = yes
#mode = new
#smsc = 358451100100
#cs_convert = yes
#report = yes
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
