|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. Please login or register. |
Mon May 20, 2024 02:01 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Tue Sep 29, 2009 10:19
|
brutalpanda: Yes they are also running SMS Tools 3 with similar setups. The only difference is they use different simcards. Is this a possible simcard error?
|
|
Tue Sep 29, 2009 02:10
|
brutalpanda: The sending has failed. Probably three retries did not help, this is not shown in the log?
Actually, we just cut the log as it was repeating itself. On our count, it did retry three times - all with the same put_command() error.
As for 2009-09-25 12:20:10, no CMGS was being returned for the message_id because we always thought that the message failed to send and as such no message_id was being returned. is this assumption correct?
I think it starts to feel that your modem is somehow broken. Probably it has a bad firmware.
Can you move to some another device, or if it does not help, to some another network provider?
As for broken firmware, I have to confirm from our supplier if they have any updates to our modem's firmware. But currently, we already have three iTegno 3800s on hand and all of them are experiencing put_command() errors on this server alone. From the other servers we have not experienced this problem yet.
Can you provide a list of compatible hardware with SMS Tools 3 that are USB based?
Thanks!
|
|
Mon Sep 28, 2009 01:42
|
brutalpanda:
9-09-25 12:19:24,5, GSM1: SMS sent, Message_id: 210, To: 63917xxxxxxx
2009-09-25 12:19:24,6, GSM1: Sending SMS from to 63917xxxxxxx
2009-09-25 12:19:24,7, GSM1: -> AT+CMGS=32^M
2009-09-25 12:19:24,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:19:25,7, GSM1: <- AT+CMGS=32
>
2009-09-25 12:19:25,7, GSM1: -> PDU 1
2009-09-25 12:19:25,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:19:27,7, GSM1: <- PDU 1 echoed, correct
+CMGS: 211
OK
2009-09-25 12:19:27,5, GSM1: SMS sent, Message_id: 211, To: 63917xxxxxxx
2009-09-25 12:19:27,6, GSM1: Moved file /var/spool/sms/checked/send_x15478 to /var/spool/sms/sent
2009-09-25 12:19:28,6, GSM1: Splitting this message into 2 parts of max 153 characters.
2009-09-25 12:19:28,6, GSM1: I have to send 2 short message for /var/spool/sms/checked/send_z15486
2009-09-25 12:19:28,6, GSM1: Sending SMS from to 63917xxxxxxx
2009-09-25 12:19:28,7, GSM1: -> AT+CMGS=154^M
2009-09-25 12:19:28,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:19:28,7, GSM1: <- AT+CMGS=154
>
2009-09-25 12:19:28,7, GSM1: -> PDU 2
2009-09-25 12:19:29,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:19:59,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred.
2009-09-25 12:19:59,7, GSM1: <- PDU 2 echoed, correct
2009-09-25 12:19:59,3, GSM1: The modem said ERROR or did not answer.
2009-09-25 12:19:59,5, GSM1: Waiting 10 sec. before retrying
2009-09-25 12:20:09,6, GSM1: Checking if modem is ready
2009-09-25 12:20:09,7, GSM1: -> AT^M
2009-09-25 12:20:09,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:20:10,7, GSM1: <- OK
T
OK
2009-09-25 12:20:10,6, GSM1: Pre-initializing modem
2009-09-25 12:20:10,7, GSM1: -> ATE0+CMEE=1^M
2009-09-25 12:20:10,7, GSM1: Command is sent, waiting for the answer
2009-09-25 12:20:10,7, GSM1: <- ATE0+CMEE=1
OK
PDU's:
( PRIVATE BLOCK )
2009-09-25 12:19:27,5 -> SMS was sent
2009-09-25 12:19:59,7 -> SMS failed
Another observation is that Modem fails on multipart messages but this does not happen all the time.
|
|
Tue Sep 22, 2009 10:28
|
brutalpanda: Operating system name and version: CentOS 5.2
Version of smsd: 3.0.10
Smsd installed from: N/A
Name and model of a modem / phone: iTegno GSM Modem 3800
Interface: USB
Hi! We have been having constant problems with our GSM Modem for the past few weeks. The GSM Modem suddenly stops running properly and have shown a put_command error. Please see the log below for details:
2009-09-11 10:49:10,6, GSM1: Modem is registered to the network
2009-09-11 10:49:10,6, GSM1: Selecting PDU mode
2009-09-11 10:49:10,7, GSM1: -> AT+CMGF=0
2009-09-11 10:49:10,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:11,7, GSM1: <- OK
2009-09-11 10:49:11,7, GSM1: -> AT+CMGS=154
2009-09-11 10:49:11,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:11,7, GSM1: <- >
2009-09-11 10:49:11,7, GSM1: -> PDU 1 (moved to private)
2009-09-11 10:49:12,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:16,7, GSM1: <- +CMGS: 0
OK
2009-09-11 10:49:16,5, GSM1: SMS sent, Message_id: 0, To: 6391788998xx
2009-09-11 10:49:16,6, GSM1: Sending SMS from to 6391788998xx
2009-09-11 10:49:16,7, GSM1: -> AT+CMGS=136
2009-09-11 10:49:16,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:16,7, GSM1: <- >
2009-09-11 10:49:16,7, GSM1: -> PDU 2
2009-09-11 10:49:16,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:21,7, GSM1: <- +CMGS: 1
OK
2009-09-11 10:49:21,5, GSM1: SMS sent, Message_id: 1, To: 6391788998xx
2009-09-11 10:49:21,6, GSM1: Moved file /var/spool/sms/checked/send_ok4702 to /var/spool/sms/sent
2009-09-11 10:49:22,6, GSM1: Splitting this message into 4 parts of max 153 characters.
2009-09-11 10:49:22,6, GSM1: I have to send 4 short message for /var/spool/sms/checked/send_Yi4710
2009-09-11 10:49:22,6, GSM1: Sending SMS from to 091788992xx
2009-09-11 10:49:22,7, GSM1: -> AT+CMGS=154
2009-09-11 10:49:22,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:22,7, GSM1: <- >
2009-09-11 10:49:22,7, GSM1: -> PDU 3
2009-09-11 10:49:23,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:49:53,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred.
2009-09-11 10:49:53,7, GSM1: <-
2009-09-11 10:49:53,3, GSM1: The modem said ERROR or did not answer.
2009-09-11 10:49:53,5, GSM1: Waiting 10 sec. before retrying
2009-09-11 10:50:03,6, GSM1: Checking if modem is ready
2009-09-11 10:50:03,7, GSM1: -> AT
2009-09-11 10:50:03,7, GSM1: Command is sent, waiting for the answer
2009-09-11 10:50:03,7, GSM1: <- OK
PDU's:
( PRIVATE BLOCK )
On "2009-11-2009-09-11 10:49:21,5,", an SMS was sent successfully but the next transaction on "2009-09-11 10:49:53" a put_command error popped up.
After this put_command error, GSM Modem fails to send or receive messages. We have to resort to unplug the GSM Modem and restart the SMS service for it to work again. We tried replicating the error in our development server but we cannot pinpoint what's the main cause of this.
For extra reference, this is the contents of our config file:
devices = GSM1
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
logfile = /var/log/smsd.log
mypath = /usr/local/bin
loglevel = 9
#alarmhandler = /opt/smstools/alarmevent
alarmlevel = 4
delaytime = 3
errorsleeptime = 10
#blocktime = 300
blocktime = 60
eventhandler = /opt/smstools/smsevent
#stats = /var/log/smsd_stats
#stats_interval = 3600
#stats_no_zeroes = no
#blacklist = /etc/smsd.black
#whitelist = /etc/smsd.white
checkhandler = /opt/smstools/smscheck
receive_before_send = no
# autosplit 0=no 1=yes 2=with text numbers 3=concatenated
autosplit = 3
internal_combine = yes
validity = 167
# regular_run = /opt/smstools/sql2sms
#regular_run_interval = 7
[GSM1]
init = AT+CPMS="SM","SM"
#device = /dev/ttyUSB0
device = /dev/ttyUSB1
#device = /dev/ttyS0
#device = /dev/usb/ttyUSB0
incoming = yes
mode = new
baudrate = 115200
#baudrate = 9600
# hardware handshake
#rtscts = yes
rtscts = no
cs_convert = yes
report = no
memory_start = 1
We think rtscts being disabled is causing error but have no proof that it is.
Anyone have any ideas what is causing this problem and why the modem is not recovering from this error message?
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
