|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. Please login or register. |
Sat May 11, 2024 03:34 |
Page: 1 2 3 Next Last
| Keywords: Mode: All keywords (AND) |
|
Mon Feb 07, 2011 12:04
|
Janeks: It worked for about 2-4 weeks, then hanged around once per week, than later - every couple of days.
I can solve it temporary, by unpluging the USB stick, then back.
|
|
Mon Feb 07, 2011 09:05
|
Janeks: Problems again, but I am not sure that it is smstools problem, because I had some problems with usb_modeswitch.
But last time when I stopped sms3, than I could still access the modem, by Minicom.
Here is the last lines of logs:
smsd_trouble.log
2011-02-07 07:52:57,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:02,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 11.
2011-02-07 07:53:02,7, GSM1: <-
2011-02-07 07:53:04,3, GSM1: Unexpected input: +CMGS: 67 OK OK OK OK OK OK
2011-02-07 07:53:04,7, GSM1: -> AT
2011-02-07 07:53:04,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:04,7, GSM1: <- OK
2011-02-07 07:53:04,6, GSM1: Pre-initializing modem
2011-02-07 07:53:04,7, GSM1: -> ATE0+CMEE=1
2011-02-07 07:53:04,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:05,7, GSM1: <- OK
2011-02-07 07:53:05,6, GSM1: Checking if modem needs PIN
2011-02-07 07:53:05,7, GSM1: -> AT+CPIN?
2011-02-07 07:53:05,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:05,7, GSM1: <- +CPIN: READY OK
2011-02-07 07:53:05,6, GSM1: Initializing modem
2011-02-07 07:53:05,7, GSM1: -> AT^CURC=0
2011-02-07 07:53:05,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:06,7, GSM1: <- OK
2011-02-07 07:53:06,7, GSM1: -> AT+CSQ
2011-02-07 07:53:06,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:53:06,7, GSM1: <- +CSQ: 21,99 OK
2011-02-07 07:53:06,6, GSM1: Signal Strength Indicator: (21,99) -71 dBm (Excellent), Bit Error Rate: not known or not detectable
2011-02-07 07:53:06,6, GSM1: Checking if Modem is registered to the network
2011-02-07 07:53:15,5, GSM1: Everything ok now.
2011-02-07 07:57:01,7, GSM1: -> AT
2011-02-07 07:57:01,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:06,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-02-07 07:57:06,7, GSM1: <-
2011-02-07 07:57:06,7, GSM1: -> .
2011-02-07 07:57:06,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:11,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-02-07 07:57:11,7, GSM1: <-
2011-02-07 07:57:11,7, GSM1: -> AT
2011-02-07 07:57:11,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:16,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 3.
2011-02-07 07:57:16,7, GSM1: <-
2011-02-07 07:57:16,7, GSM1: -> .
2011-02-07 07:57:16,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:21,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 4.
2011-02-07 07:57:21,7, GSM1: <-
2011-02-07 07:57:22,7, GSM1: -> AT
2011-02-07 07:57:22,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:27,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 5.
2011-02-07 07:57:27,7, GSM1: <-
2011-02-07 07:57:27,7, GSM1: -> .
2011-02-07 07:57:27,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:32,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 6.
2011-02-07 07:57:32,7, GSM1: <-
2011-02-07 07:57:32,7, GSM1: -> AT
2011-02-07 07:57:32,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:37,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 7.
2011-02-07 07:57:37,7, GSM1: <-
2011-02-07 07:57:37,7, GSM1: -> .
2011-02-07 07:57:37,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:42,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 8.
2011-02-07 07:57:42,7, GSM1: <-
2011-02-07 07:57:43,7, GSM1: -> AT
2011-02-07 07:57:43,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:48,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 9.
2011-02-07 07:57:48,7, GSM1: <-
2011-02-07 07:57:48,7, GSM1: -> .
2011-02-07 07:57:48,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:53,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 10.
2011-02-07 07:57:53,7, GSM1: <-
2011-02-07 07:57:54,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-07 07:57:54,7, GSM1: -> AT
2011-02-07 07:57:54,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:54,7, GSM1: <- OK
2011-02-07 07:57:54,6, GSM1: Pre-initializing modem
2011-02-07 07:57:55,7, GSM1: -> ATE0+CMEE=1
2011-02-07 07:57:55,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:57:55,7, GSM1: <- OK
2011-02-07 07:57:55,6, GSM1: Checking if modem needs PIN
2011-02-07 07:57:55,7, GSM1: -> AT+CPIN?
2011-02-07 07:57:55,7, GSM1: Command is sent, waiting for the answer
2011-02-07 07:58:05,7, GSM1: put_command expected (READY)|( PIN)|( PUK)|(ERROR), timeout occurred. 1.
2011-02-07 07:58:05,7, GSM1: <-
2011-02-07 07:58:05,2, GSM1: PIN handling: expected READY, modem answered
2011-02-07 07:58:05,2, GSM1: Modem handler 0 terminated abnormally. PID: 3634.
smsd.log
2011-02-06 10:20:24,3, GSM1: Unexpected input: +CMGS: 48 OK OK OK OK OK OK
2011-02-06 10:21:28,3, GSM1: The modem answer was not OK:
2011-02-06 10:21:28,5, GSM1: Waiting 10 sec. before retrying
2011-02-06 10:22:32,3, GSM1: Unexpected input: +CMGS: 49 OK OK OK OK OK OK
2011-02-06 10:23:36,3, GSM1: The modem answer was not OK:
2011-02-06 10:23:36,4, GSM1: Sending SMS to 37128681088 failed, trying time 322 sec. Retries: 2.
2011-02-06 10:24:31,3, GSM1: Unexpected input: +CMGS: 50 OK OK OK OK OK OK
2011-02-06 10:24:35,5, GSM1: SMS received, From: 37126374846
2011-02-06 10:24:37,5, GSM1: SMS received, From: 37126374846
2011-02-06 10:24:45,5, smsd: Moved file /var/spool/sms/outgoing/GSM1q9k7.smsg to /var/spool/sms/checked
2011-02-06 10:24:46,5, smsd: Moved file /var/spool/sms/outgoing/GSM12d51.smsg to /var/spool/sms/checked
2011-02-06 10:25:48,3, GSM1: The modem answer was not OK:
2011-02-06 10:25:48,5, GSM1: Waiting 10 sec. before retrying
2011-02-06 10:26:51,3, GSM1: Unexpected input: +CMGS: 51 OK OK OK OK OK OK
2011-02-06 10:27:56,3, GSM1: The modem answer was not OK:
2011-02-06 10:27:56,5, GSM1: Waiting 10 sec. before retrying
2011-02-06 10:28:59,3, GSM1: Unexpected input: +CMGS: 52 OK OK OK OK OK OK
2011-02-06 10:30:04,3, GSM1: The modem answer was not OK:
2011-02-06 10:30:04,4, GSM1: Sending SMS to 37128617395 failed, trying time 318 sec. Retries: 2.
2011-02-06 10:30:59,3, GSM1: Unexpected input: +CMGS: 53 OK OK OK OK OK OK
2011-02-06 10:31:17,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 3223.
2011-02-06 10:31:17,2, GSM1: Modem handler 0 terminated. PID: 3225, was started 11-02-06 10:18:14.
2011-02-06 10:31:17,2, smsd: Smsd mainprocess terminated. PID 3223, was started 11-02-06 10:18:14.
2011-02-06 10:42:13,2, smsd: Smsd v3.1.14 started.
2011-02-06 10:42:13,2, smsd: Running as root:root.
2011-02-06 10:42:14,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2011-02-06 10:42:14,4, smsd: Note that at least GSM1 will send administrative messages, but mainspooler will not because shared memory is not available.
2011-02-06 10:42:14,5, smsd: Outgoing file checker has started. PID: 3632.
2011-02-06 10:42:14,5, GSM1: Modem handler 0 has started. PID: 3634.
2011-02-06 10:42:14,5, GSM1: Using check_memory_method 1: CPMS is used.
2011-02-06 10:42:15,5, GSM1: Modem needs PIN, entering PIN...
2011-02-06 10:42:18,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME
2011-02-06 10:42:19,5, GSM1: Signal Strength Indicator: (4,99) -105 dBm (Marginal), Bit Error Rate: not known or not detectable
2011-02-06 10:42:21,5, GSM1: CGSN: 354639040061290
2011-02-06 10:42:21,5, GSM1: IMSI: 247010200742648
2011-02-06 10:42:24,5, GSM1: SMS sent, Message_id: 54, To: 37126547910, sending time 10 sec.
2011-02-06 10:42:27,5, GSM1: SMS sent, Message_id: 55, To: 37128695292, sending time 2 sec.
2011-02-06 10:42:30,5, GSM1: SMS sent, Message_id: 56, To: 37128325388, sending time 2 sec.
2011-02-06 10:42:32,5, GSM1: SMS sent, Message_id: 57, To: 37126307837, sending time 2 sec.
2011-02-06 10:42:34,5, GSM1: SMS sent, Message_id: 58, To: 37126374846, sending time 1 sec.
2011-02-06 10:42:37,5, GSM1: SMS sent, Message_id: 59, To: 37126374846, sending time 2 sec.
2011-02-06 10:42:39,5, GSM1: SMS received, From: 37126374846
2011-02-06 10:42:44,5, smsd: Moved file /var/spool/sms/outgoing/GSM1tk8c.smsg to /var/spool/sms/checked
2011-02-06 10:42:50,5, GSM1: SMS sent (part 1/2), Message_id: 60, To: 37126374846, sending time 3 sec.
2011-02-06 10:42:51,5, GSM1: SMS sent (part 2/2), Message_id: 61, To: 37126374846, sending time 1 sec.
2011-02-06 19:32:07,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:34:28,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:38:17,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:40:39,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:43:01,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:47:33,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:51:21,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 19:58:48,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:01:53,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:04:15,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:13:08,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:20:56,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:25:28,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:28:12,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:30:11,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:32:33,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:34:54,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:38:01,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:42:33,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:44:33,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:46:55,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:49:16,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:52:01,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:54:45,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:57:07,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 20:59:49,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 21:02:33,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 21:04:56,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-06 21:08:23,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-07 00:09:39,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-07 00:09:44,5, GSM1: SMS received, From: 37128695292
2011-02-07 00:09:56,5, smsd: Moved file /var/spool/sms/outgoing/GSM1r85q.smsg to /var/spool/sms/checked
2011-02-07 00:11:05,3, GSM1: The modem answer was not OK:
2011-02-07 00:11:05,5, GSM1: Waiting 10 sec. before retrying
2011-02-07 00:12:09,3, GSM1: Unexpected input: +CMGS: 62 OK OK OK OK OK OK
2011-02-07 00:13:13,3, GSM1: The modem answer was not OK:
2011-02-07 00:13:13,5, GSM1: Waiting 10 sec. before retrying
2011-02-07 00:14:17,3, GSM1: Unexpected input: +CMGS: 63 OK OK OK OK OK OK
2011-02-07 00:15:21,3, GSM1: The modem answer was not OK:
2011-02-07 00:15:21,4, GSM1: Sending SMS to 37128695292 failed, trying time 320 sec. Retries: 2.
2011-02-07 00:16:16,3, GSM1: Unexpected input: +CMGS: 64 OK OK OK OK OK OK
2011-02-07 07:46:39,3, GSM1: Unexpected input: OK OK OK OK OK OK
2011-02-07 07:46:44,5, GSM1: SMS received, From: 37126670280
2011-02-07 07:46:47,5, smsd: Moved file /var/spool/sms/outgoing/GSM1csvn.smsg to /var/spool/sms/checked
2011-02-07 07:47:54,3, GSM1: The modem answer was not OK:
2011-02-07 07:47:54,5, GSM1: Waiting 10 sec. before retrying
2011-02-07 07:48:57,3, GSM1: Unexpected input: +CMGS: 65 OK OK OK OK OK OK
2011-02-07 07:50:02,3, GSM1: The modem answer was not OK:
2011-02-07 07:50:02,5, GSM1: Waiting 10 sec. before retrying
2011-02-07 07:51:05,3, GSM1: Unexpected input: +CMGS: 66 OK OK OK OK OK OK
2011-02-07 07:52:10,3, GSM1: The modem answer was not OK:
2011-02-07 07:52:10,4, GSM1: Sending SMS to 37126670280 failed, trying time 318 sec. Retries: 2.
2011-02-07 07:53:04,3, GSM1: Unexpected input: +CMGS: 67 OK OK OK OK OK OK
2011-02-07 07:57:54,3, GSM1: Unexpected input: OK OK OK OK OK
2011-02-07 07:58:05,2, GSM1: PIN handling: expected READY, modem answered
2011-02-07 07:58:05,2, GSM1: Modem handler 0 terminated abnormally. PID: 3634.
2011-02-07 10:50:37,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 3632.
2011-02-07 10:50:37,2, smsd: Smsd mainprocess terminated. PID 3632, was started 11-02-06 10:42:14.
|
|
Thu Dec 16, 2010 12:02
|
Janeks: Thanks for your links!
I shortly tested my current configuration and as I see there is only one serial port in system for my Huawei E1752.
But I as I have time and the second modem I'll test that multiplexer & report.
|
|
Tue Dec 14, 2010 07:36
|
Janeks: Is the subject possible/real?
brgds
Janeks
|
|
Sun Dec 12, 2010 20:05
|
Janeks: It looks like I successfully moved from old (damaged) Nokia N30 to Huawei E1752.
For that I needed to install usb_modeswitch tool and also I used custom init string (see previous post).
Let's see what will happen in next week when it will have more SMSes to process.
|
|
Sun Dec 12, 2010 19:56
|
Janeks: I think that this topic could be closed - it seems, that there had some problem with Nokia N30 modem. I changed serial to USB converter and nothing changes: I got the same sporadic problems, when modem connection hangs.
As I got second linux device I successfuly tested the another modem: Huawei E1752
The details in the topic: Huawei E1752
|
|
Sun Dec 12, 2010 17:19
|
Janeks: The accentuated character conversion is working also now.
The problem in sendsms or how my ssh client is translating accentuated characters:
linbox:~# sendsms
Destination(s): 3712637xxxx
Text: ļāūņš
--
Text: ļāūņš
To: 3712637xxxx
iconv: illegal input sequence at position 0
and the result file in outgoing folder is with empty text body.
|
|
Sun Dec 12, 2010 14:14
|
Janeks: It seems from my tests that the last problem (smsd: The file /var/spool/sms/outgoing/send_xJ3059 has no text or data) caused by using accentuated characters in message body, by using sendsms?
I did such tests from command line and when the first character was accentuated, than I got this message.
|
|
Sun Dec 12, 2010 09:28
|
Janeks: Operating system name and version: Debian on PPC
Version of smsd: 3.1.14.
Smsd installed from: sources
Name and model of a modem / phone: Huawei E1752
Interface: USB
It looks like modem runs well, but I tested it just by sending few SMSes.
There are some minor errors are they significant?
conf:
# Example smsd.conf. Read the manual for a description
devices = GSM1
logfile = /var/log/smsd.log
failed = /var/spool/sms/failed
report = /var/spool/sms/report
loglevel = 5
smart_logging = yes
incoming_utf8 = yes
eventhandler = /usr/local/bin/smsd_eventhandler.sh
checkhandler = /usr/local/bin/smsd_checkhandler.sh
incoming_utf8 = yes
date_filename = 2
#END GLOBAL DIRECTIVES
[GSM1]
device = /dev/ttyUSB0
incoming = yes
pin = XXXX
init = AT^CURC=0
#END GSM1 DIRECTIVES
smd.log
2010-12-11 23:43:09,2, smsd: Smsd v3.1.14 started.
2010-12-11 23:43:09,2, smsd: Running as root:root.
2010-12-11 23:43:09,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-12-11 23:43:09,4, smsd: Note that at least GSM1 will send administrative messages, but mainspooler will not because shared memory is not available.
2010-12-11 23:43:09,5, smsd: Outgoing file checker has started. PID: 12363.
2010-12-11 23:43:09,5, GSM1: Modem handler 0 has started. PID: 12365.
2010-12-11 23:43:09,5, GSM1: Using check_memory_method 1: CPMS is used.
2010-12-11 23:43:10,3, GSM1: Unexpected input: OK
2010-12-11 23:43:14,5, GSM1: CGSN: 354639040061290
2010-12-11 23:43:14,5, GSM1: IMSI: 247010301694450
2010-12-11 23:45:25,5, GSM1: SMS received, From: 3712637xxxx
2010-12-12 10:30:31,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 12363.
2010-12-12 10:30:31,2, GSM1: Modem handler 0 terminated. PID: 12365, was started 10-12-11 23:43:09.
2010-12-12 10:30:31,2, smsd: Smsd mainprocess terminated. PID 12363, was started 10-12-11 23:43:09.
2010-12-12 10:46:07,2, smsd: Smsd v3.1.14 started.
2010-12-12 10:46:07,2, smsd: Running as root:root.
2010-12-12 10:46:07,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-12-12 10:46:07,4, smsd: Note that at least GSM1 will send administrative messages, but mainspooler will not because shared memory is not available.
2010-12-12 10:46:07,5, smsd: Outgoing file checker has started. PID: 3026.
2010-12-12 10:46:07,5, GSM1: Modem handler 0 has started. PID: 3028.
2010-12-12 10:46:07,5, GSM1: Using check_memory_method 1: CPMS is used.
2010-12-12 10:46:12,5, GSM1: CGSN: 354639040061290
2010-12-12 10:46:12,5, GSM1: IMSI: 247010301694450
2010-12-12 10:46:58,5, smsd: Moved file /var/spool/sms/outgoing/send_tv3040 to /var/spool/sms/checked
2010-12-12 10:47:10,5, GSM1: SMS sent, Message_id: 8, To: 37126374846, sending time 7 sec.
2010-12-12 10:48:08,5, smsd: The file /var/spool/sms/outgoing/send_xJ3059 has no text or data
2010-12-12 10:48:45,5, GSM1: SMS received, From: 37126374846
trouble.log
2010-12-11 23:43:09,5, smsd: Outgoing file checker has started. PID: 12363.
2010-12-11 23:43:09,5, smsd: Everything ok now.
2010-12-11 23:43:10,3, GSM1: Unexpected input: OK
2010-12-11 23:43:10,7, GSM1: -> AT
2010-12-11 23:43:10,7, GSM1: Command is sent, waiting for the answer
2010-12-11 23:43:10,7, GSM1: <- OK
2010-12-11 23:43:10,6, GSM1: Pre-initializing modem
2010-12-11 23:43:10,7, GSM1: -> ATE0+CMEE=1
2010-12-11 23:43:10,7, GSM1: Command is sent, waiting for the answer
2010-12-11 23:43:11,7, GSM1: <- OK
2010-12-11 23:43:11,6, GSM1: Checking if modem needs PIN
2010-12-11 23:43:11,7, GSM1: -> AT+CPIN?
2010-12-11 23:43:11,7, GSM1: Command is sent, waiting for the answer
2010-12-11 23:43:11,7, GSM1: <- +CPIN: READY OK
2010-12-11 23:43:11,6, GSM1: Initializing modem
2010-12-11 23:43:11,7, GSM1: -> AT^CURC=0
2010-12-11 23:43:11,7, GSM1: Command is sent, waiting for the answer
2010-12-11 23:43:12,7, GSM1: <- OK
2010-12-11 23:43:12,7, GSM1: -> AT+CSQ
2010-12-11 23:43:12,7, GSM1: Command is sent, waiting for the answer
2010-12-11 23:43:12,7, GSM1: <- +CSQ: 9,99 OK
2010-12-11 23:43:12,6, GSM1: Signal Strength Indicator: (9,99) -95 dBm (Marginal), Bit Error Rate: not known or not detectable
2010-12-11 23:43:12,6, GSM1: Checking if Modem is registered to the network
2010-12-11 23:43:23,5, GSM1: Everything ok now.
2010-12-12 10:46:07,5, smsd: Outgoing file checker has started. PID: 3026.
2010-12-12 10:46:07,5, smsd: Everything ok now.
|
|
Thu Nov 11, 2010 08:03
|
Janeks: There is also another problem - I got sudden restart/shutdown of my linux box.
Later I found from syslog and internet resources that it is connected with this message:
kernel: option: option_instat_callback: error -71
F.ex. here is similar problem discussion:
http://www.murga-linux.com/puppy/viewtopic.php?p=357695
Are you faced with this - do you know how to fix it?
|
|
Wed Nov 10, 2010 22:48
|
Janeks: It looks like I need some correct configuration for Huawei E1752... :?
I could something receive and send, but there is errors in comunication between smsd and modem:
smsd.log:
2010-11-11 00:40:46,2, smsd: Smsd v3.1.14 started.
2010-11-11 00:40:46,2, smsd: Running as root:root.
2010-11-11 00:40:46,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-11-11 00:40:46,4, smsd: Note that at least GSM1 will send administrative messages, but mainspooler will not because shared memory is not available.
2010-11-11 00:40:46,5, smsd: Outgoing file checker has started. PID: 3209.
2010-11-11 00:40:46,5, GSM1: Modem handler 0 has started. PID: 3211.
2010-11-11 00:40:46,5, GSM1: Using check_memory_method 1: CPMS is used.
2010-11-11 00:40:50,5, GSM1: CGSN: 353444042232051
2010-11-11 00:40:50,5, GSM1: IMSI: 247010200742648
2010-11-11 00:40:51,5, GSM1: SMS received, From: 37126374846
2010-11-11 00:40:53,5, GSM1: SMS received, From: 37126374846
2010-11-11 00:40:55,5, GSM1: SMS received, From: 37126374846
2010-11-11 00:40:57,5, smsd: Moved file /var/spool/sms/outgoing/GSM19qt7.smsg to /var/spool/sms/checked
2010-11-11 00:40:57,5, smsd: Moved file /var/spool/sms/outgoing/GSM1e6ua.smsg to /var/spool/sms/checked
2010-11-11 00:40:58,5, smsd: Moved file /var/spool/sms/outgoing/GSM1gvhu.smsg to /var/spool/sms/checked
2010-11-11 00:41:40,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 3209.
2010-11-11 00:41:40,3, GSM1: The modem answer was not OK:
2010-11-11 00:41:40,5, GSM1: Waiting 10 sec. before retrying
2010-11-11 00:41:40,4, GSM1: Sending SMS (part 1/2) to 37126374846 failed, trying time 38 sec. Retries: 0.
2010-11-11 00:41:40,2, GSM1: Modem handler 0 terminated. PID: 3211, was started 10-11-11 00:40:46.
2010-11-11 00:41:40,2, smsd: Smsd mainprocess terminated. PID 3209, was started 10-11-11 00:40:46.
smsd_trouble.log:
2010-11-11 00:40:46,5, smsd: Outgoing file checker has started. PID: 3209.
2010-11-11 00:40:46,5, smsd: Everything ok now.
2010-11-11 00:41:02,7, GSM1: -> AT+CREG?
2010-11-11 00:41:02,7, GSM1: Command is sent, waiting for the answer
2010-11-11 00:41:02,7, GSM1: <- +CREG: 0,1 OK
2010-11-11 00:41:02,6, GSM1: Modem is registered to the network
2010-11-11 00:41:02,7, GSM1: -> AT+CMGS=154
2010-11-11 00:41:02,7, GSM1: Command is sent, waiting for the answer
2010-11-11 00:41:03,7, GSM1: <- >
2010-11-11 00:41:03,7, GSM1: -> 0051000B917321364748F60008FF8C0500035E0201012A0073007A006901460061007300200066006F0072006D010100740073002000620065007A0020007001130064006901460101006D003A000A00220063006900720073006D00610073006B006F0064007300200053006F00720074004E006F00730020006D003300200053006F00720074004E006F00730020006D00330020002E002E002E.
2010-11-11 00:41:03,7, GSM1: Command is sent, waiting for the answer
2010-11-11 00:41:40,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2010-11-11 00:41:40,7, GSM1: <-
2010-11-11 00:41:40,3, GSM1: The modem answer was not OK:
2010-11-11 00:41:40,5, GSM1: Waiting 10 sec. before retrying
2010-11-11 00:41:40,4, GSM1: Sending SMS (part 1/2) to 37126374846 failed, trying time 38 sec. Retries: 0.
2010-11-11 00:41:40,5, GSM1: Everything ok now.
Before these logs was created I was able to send out simple (latin only) SMS which file was created by using sendsms script. But the message was sent three times out!?
|
|
Fri Nov 05, 2010 13:41
|
Janeks: It seems, that I should try either another modem and/or serial-usb connector.
Could smsd work with Huawei E1752?
|
|
Tue Nov 02, 2010 16:40
|
Janeks: Ah, sorry, made the same mistake. For sent SMS file I need first argument $1 only. :roll:
BTW: I would recomend add arguments list description into "How to configure" page near each handler description.
That is the first place I looked to. In page http://smstools3.kekekasvi.com/index.php?p=eventhandler there was not exact desription about checkhandler arguments.
|
|
Tue Nov 02, 2010 15:09
|
Janeks: checkhandler:
#!/bin/bash
if [ "$1" == "RECEIVED" ]; then
if sed -e '/^$/ q' < "$2" | grep "^Alphabet: UCS2" > /dev/null; then
TMPFILE=`mktemp /tmp/smsd_XXXXXX`
sed -e '/^$/ q' < "$2" | sed -e 's/Alphabet: UCS2/Alphabet: UTF-8/g' > $TMPFILE
sed -e '1,/^$/ d' < "$2" | iconv -f UNICODEBIG -t UTF-8 >> $TMPFILE
mv $TMPFILE "$2"
fi
fi
if [ "$1" == "SENT" ]; then
if sed -e '/^$/ q' < "$2" | grep "^Alphabet: UTF-8" > /dev/null; then
TMPFILE=`mktemp /tmp/smsd_XXXXXX`
sed -e '/^$/ q' < "$2" | sed -e 's/Alphabet: UTF-8/Alphabet: UCS2/g' > $TMPFILE
sed -e '1,/^$/ d' < $2 | iconv -f UTF-8 -t UNICODEBIG >> $TMPFILE
mv $TMPFILE $2
fi
fi
orginal message:
From: 3712642XXXX
To: 3712783XXXX
Alphabet: UTF-8
ID: 20
MngrID: 4
Īsziņa pieņemta
failed message:
From: 3712642XXXX
To: 3712783XXXX
Alphabet: UTF-8
ID: 20
MngrID: 4
Fail_reason: Invalid alphabet
Failed: 10-11-02 13:33:06
Īsziņa pieņemta
|
|
Tue Nov 02, 2010 10:47
|
Janeks: Operating system name and version: Linux Debian 2.6.32.13 PPC
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Nokia N30
Interface: serial with USB adapter...
I used the same approach like for older version:
[answered] Accentuated character conversion
It works well with incomming messages
But I got "Invalid alphabet" error.
I tried to not use conversion at all by setting format to ISO, but then I got message sent, but with wrong characters.
Does smsd checks for alphabet before checkhandler?
:?
Otherwise I can hardly explain why I am getting "Alphabet: UTF-8" after this line of my checkhandler:
sed -e '/^$/ q' < "$1" | sed -e 's/Alphabet: UTF-8/Alphabet: UCS2/g' > $TMPFILE
Or I am doing something that I am missing...
|
|
Wed Oct 27, 2010 12:31
|
Janeks: The unit's HD died couple of weeks ago. So I gues , that probably the problem somehow was connected with HD failures.
And I did not yet restored the system, but I am planning it to do within a week.
|
|
Mon Oct 04, 2010 15:51
|
Janeks: Yes, but not exactly the same, modem and USB-serial adapter are the same, but computer parameters are the same and model is the same, but it is not the same box.
|
|
Mon Oct 04, 2010 15:35
|
Janeks: It could happen around once per week, but not on regular basis.
The longest run without it was around two weeks, but last was around two days.
|
|
Mon Oct 04, 2010 10:23
|
Janeks: Is this a HW problem I am not shure, but I have the same HW.
And yet working with the same old version of sms3: 3.1.6
smsd.conf:
# Example smsd.conf. Read the manual for a description
#GLOBAL DIRECTIVES
devices = GSM1
failed = /var/spool/sms/failed
report = /var/spool/sms/report
sent = /var/spool/sms/sent
logfile = /var/spool/sms/logs/sms3.log
loglevel = 5
#errorsleeptime = number
#Default value: 10.
#A modem sleeps so many seconds when it answers a command with ERROR.
#blockafter = number
#Default value: 3.
#A modem is blocked after n number of errors while sending messages.
#A successfull sending will reset this counter.
eventhandler = /usr/local/bin/smsd_eventhandler.sh
#Default value: not in use.
#Specifies an external program or script that will execute whenever a message
#was sent, received or failed.
#stats = directory
#Default value: not in use.
#Specifies the directory where smsd stores statistic files. The directoy must
#exist before you start smsd. If not given, then the program does not write
#statistic files. After version >= 3.1.1 message counter files are stored to
#this directory even if smsd is compiled without statistics enabled.
#stats_interval = number
#Default value: 3600.
#Smsd writes statistics files every n seconds. Value 0 disables statistics but
#counters are still updated if stats directory is defined.
#stats_no_zeroes = yes/no
#Default value: no.
#Smsd does not write statistic files when no message was sent or received
#(Zero-Counters) if this is set to yes.
#blacklist = filename
#Default value: not in use.
#Name of the blacklist file.
#whitelist = filename
#Default value: not in use.
#Name of the whitelist file.
#The black list takes precedence before the white list
checkhandler = /usr/local/bin/smsd_checkhandler.sh
#Default value: not in use.
#External program that checks if a message file is valid.
#If the checkhandler return a non-zero (other than 2) exitcode the message
#will not be sent. With the smsd version >= 3.1 the checkhandler can also
#modify a message file. Exitcode 2 means that the checkhandler has moved a
#message to the spooler by itself.
#autosplit = number
#Default value: 3.
#Controls if and how the program splits large text messages.
#The program does not split text messages with UDH.
#If splitting is disabled, binary messages requiring more than one part are
#not sent.
# 0 disabled
# 1 enabled, no part-number
# 2 enabled, text numbers
# 3 enabled, concatenated format (not supported by some phones)
#receive_before_send = yes/no
#Default value: no.
#Forces smsd to empty the first SIM card memory before sending SM.
#This is a workaround for modems that cannot send SM with a full SIM card.
#store_received_pdu = 3
#Default value: 1.
#Controls when the incoming PDU string(s) is stored to message file.
# 0 no PDU's are stored
# 1 unsupported PDU's are stored
# 2 unsupported and PDU's with 8bit binary data or Unicode text are stored
# 3 all PDU's are stored
# Header is "PDU: " and PDU's of a multipart message are stored from 1 to n order.
#ic_purge_hours = 0
#validity = number
#Default value: 255.
#0 ... 143 (value + 1) * 5 minutes (i.e. 5 minutes intervals up to 12 hours)
#144 ... 167 12 hours + ((value - 143) * 30 minutes) (i.e. 30 min intervals up to 24 hours)
#168 ... 196 (value - 166) * 1 day (i.e. 1 day intervals up to 30 days)
#197 ... 255 (value - 192) * 1 week (i.e. 1 week intervals up to 63 weeks)
#decode_unicode_text = yes
#Default value: no.
#Controls when the incoming Unicode text is decoded internally.
incoming_utf8 = yes
#Default value: no.
#With this setting messages using ISO or GSM alphabet are stored using UTF-8
#character set.
#log_charconv = yes
#Default value: no.
#With this setting a details of character set conversions (outgoing UTF-8 to
#ISO conversion and incoming GSM/ISO to UTF-8 conversion) is printed to the log.
#If smsd is compiled using DEBUGMSG definition, details are also printed to the
#console. Logging feature can be useful if you have some troubles with
#characters and like to know what exactly happens inside the smsd.#internal_combine = yes/no
#Default value: yes.
#Controls when the incoming multipart message is combined internally.
#internal_combine_binary = no
#Default value: internal_combine.
#Controls when the incoming multipart binary message is not combined internally.
date_filename = 2
#Default value: 0. Defines if date is included to the filename of incoming
#message. With value 1 like 2007-09-02.GSM1.xxxxxx and with value 2 like
#GSM1.2007-09-02.xxxxxx.
#user = username
#Default value: not in use.
#group = groupname
#Default value: not in use.
#If the smsd is started by the root, these two settings can be used to switch
#smsd to run as an unpriviledged user.
#If user is set but group is unset, that user's normal groups
#(e.g. from /etc/groups) are used.
#This means you can allow other users on the system access to write messages
#to the outgoing spool without giving them direct access to the serial port.
#infofile = filename
#Default value: /var/run/smsd.working.
#pidfile = filename
#Default value: /var/run/smsd.pid.
#Location of infofile and pidfile can be changed with these settings. This is
#usually necessary if the smsd is running as an unpriviledged user. If a sms3
#script is used to start and stop the smsd, these settings should be defined
#in the script.
#regular_run = filename
#Default value: not in use.
#regular_run_interval = number
#Default value: 300.
#A regular_run is an external script or program which is run regularly while
#the smsd is running. A value regular_run_interval describes number of seconds
#between each run.
admin_to = 3712637XXXX
#Default value: not in use.
#Specifies a destination number for administrative messages created by smsd.
#Messages are sent without using the filesystem.
#executable_check = yes/no
#Default value: yes.
#This setting defines if all executables are checked during the startup check.
#Usually eventhanler, alarmhandler etc. are shell scripts or some other single
#files which can be executed and therefore checked simply. If using a settings
#like eventhandler = /usr/local/bin/php -f /usr/local/bin/smsd_eventhandler.php,
# the check will fail and smsd will not start unless executable_check = no is
#defined.
#international_prefixes = list of numbers
#national_prefixes = list of numbers
#Default value: not in use.
#See SMS file (Using Type Of Address selection) for details.
#adminmessage_device = name
#Default value: first available modem.
#Defines which modem is used to send administrative messages from the mainspooler.
#This feature uses shared memory and works only if libmm is installed and statistics
#functionality is enabled.
smart_logging = yes
#Default value: no.
#This feature is available when file based logging is used.
#If loglevel is less than 7 (for example "notice" is a good choise with
#smart_logging), trouble log (with loglevel 7) about whole communication is
#written to different file if there has been any errors.
#END GLOBAL DIRECTIVES
#DEVICE DIRECTIVES
[GSM1]
device = /dev/ttyUSB0
incoming = yes
#pin = 3375
#init = modem command
#Default value: not in use.
#Specifies a modem initialisation command.
#Most modems do not need any init string. See the manual of your modem for more
#details of modem commands.
#init2 = modem command
#Default value: not in use.
#Specifies a second modem initialisation command. Most users do not need this.
#smsc = number
#Default value: not in use.
#Specifies the SMSC number that this modem should use to send SM.
#You need this setting only if the default of the SIM card is bad.
#Write the phone number of the SMSC in international format without the
#starting "+".
#baudrate = number
#Default value: 115200.
#Specifies the speed of the serial communication in bits per second.
#Most modems including old devices work well with 115200. If this speed is
#not supported by the system, 19200 is used. Some very old devices may need
#lower speed like 9600 baud.
#rtscts = yes/no
#Default value: yes.
#You can disable usage of hardware handshake wires by setting this option to
#"no". Please don't use this feature in commercial applications because the
#hardware handshake wires ensure proper communications timing between the
#computer and the modem.
#send_delay = number
#Default value: 1 (milsec)
#If your modem does not support hardware handshake you should use the lowest
#possible baudrate to ensure that the program does not run faster than the
#modem can do. However, if the lowest possible baudrate is still too fast,
#then you can use this parameter to make it even slower.
#cs_convert = yes/no
#Default value: yes.
#The program converts normal text messages into GSM character set.
#You need this to display german umlauts and control characters correctly.
#report = yes/no
#Default value: no.
#If you enable this, the program requests a status report SM from the SMSC for
#each sent message. This does not work on many mobile phones and on some modems.
#check_network = value
#Default value: 1.
#Defines how network registration is checked:
# 0 no Network registration is not checked.
# 1 yes Network registration is always checked
# 2 Network registration is checked only when preparing to send messages.
#If a modem does not support network checking, checking is automatically ignored.
#With value 2 incoming messages are processed faster.
#messageids = number
#Default value: 2.
#Available from version >= 3.1.1. Defines how message id's are stored:
#1 = first, 2 = last, 3 = all. When all id's are stored, numbers are delimited
#whith space and there is one space and dot in the end of string.
number = 3712642XXXX
#Default value: empty.
#SIM card's telephone number. If not empty, it is stored to the message files
#using header "Number:".
#END GSM1 device directives
#END DEVICE DIRECTIVES
|
|
Mon Oct 04, 2010 07:12
|
Janeks: I am getting any way sporadic problems.
The last looks in a sms file:
Error: Cannot decode PDU, see text part for details.
From:
Received: 10-10-02 13:29:06
Subject: GSM1
Modem: GSM1
Number: 37126421304
IMSI: 350775910323487
Report: no
Alphabet: UTF-8
Length: 341
PDU: 07917321292020F0640B917321660782F0000801012070`129021280500033F0202002000320020007300340031003500200039002000`73003900350032002000320036
Pos: ....-....*....-....*....-....*....-....*....^^^^^^~here(45)
First tried with PDU mode new (with CSA):
PDU ERROR: Position 45,6: Invalid character(s) in time of Service Centre Time Stamp: "07:1`:92"
Next tried with PDU mode old (without CSA):
The PDU data (07) says that the message format is 3 which is not supported. Cannot decode.
No success. This PDU cannot be decoded. There is something wrong.
|
|
Thu Sep 09, 2010 09:26
|
Janeks: No it not happened on other HW.
I has the same HW that worked well, but it has other problems, so I changed it to the same but new one, that has the same paramaters, but new version of software.
|
|
Thu Sep 09, 2010 07:16
|
Janeks: No it hangs again this morning.
Strange - it means that it worked with almoust the same configuration like it was before.
But the strange too was that logfiles in /var/log was empty.
WIth version 3.1.11 despite I has logfile to another directory it wrote logfiles into /var/log
Now I has the logfile specified in configuration file, but it was damaged or something like that - I could not it open and if copied then system reports IO error and I could not get whole file.
So I have no logging info. :(
Could it be a HW problem on my side? Because I have another box, but with the same parameters - should be identical, may be some other version of linux kernel.
I now did uninstall and compile the 3.1.6, let's see ... :?
|
|
Wed Sep 08, 2010 09:09
|
Janeks: The version 3.1.6 works. At least I have all the messages that I got this morning. And smsd still running and modem shows no unread messages.
|
|
Tue Sep 07, 2010 12:21
|
Janeks: O'k I did it. Let's see...
I had to disable send_handshake_select in my config file. As it was unknown for old version.
|
|
Tue Sep 07, 2010 10:48
|
Janeks: How to correclty remove last installed version.
I got:
boxy:/home/auser/dls/smstools3# /etc/init.d/sms3 stop
boxy:/home/auser/dls/smstools3# make uninstall
./uninstall.sh /usr/local/bin
You are going to delete all files from the SMS Server Tools.
This script deletes also the config file and stored messages.
Are you sure to proceed? [yes/no]
y
make: *** [uninstall] Error 1
|
Page: 1 2 3 Next Last
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
