|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Fri Mar 14, 2025 10:57 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Sun Apr 23, 2017 21:55
|
FOCOhalsoft: Thank you kindly, that seemed to do the trick!!! The memory start = 0...
Another donation on the way!!! You have saved me....
|
|
Sat Apr 22, 2017 18:54
|
FOCOhalsoft: I have been trying init strings all day for my 4G Wavecom device :( I can send and receive SMS's but this constant traffic back and forth from the modem is bogging down my daemon...
I am encountering the old:
2017-04-22 12:52:38,7, GSM1: Command is sent, waiting for the answer
2017-04-22 12:52:38,7, GSM1: <- +CPMS: "SM",1,30,"SM",1,30,"SM",1,30 OK
2017-04-22 12:52:38,6, GSM1: Used memory is 1 of 30
2017-04-22 12:52:38,6, GSM1: Trying to get stored message 1
2017-04-22 12:52:39,7, GSM1: -> AT+CMGR=1
2017-04-22 12:52:39,7, GSM1: Command is sent, waiting for the answer
2017-04-22 12:52:39,7, GSM1: <- +CMS ERROR: 321 (Invalid memory index)
2017-04-22 12:52:39,6, GSM1: Trying to get stored message 2
2017-04-22 12:52:39,7, GSM1: -> AT+CMGR=2
2017-04-22 12:52:39,7, GSM1: Command is sent, waiting for the answer
2017-04-22 12:52:39,7, GSM1: <- +CMS ERROR: 321 (Invalid memory index)
2017-04-22 12:52:39,6, GSM1: Trying to get stored message 3
2017-04-22 12:52:40,7, GSM1: -> AT+CMGR=3
2017-04-22 12:52:40,7, GSM1: Command is sent, waiting for the answer
2017-04-22 12:52:40,7, GSM1: <- +CMS ERROR: 321 (Invalid memory index)
2017-04-22 12:52:40,6, GSM1: Trying to get stored message 4
2017-04-22 12:52:40,7, GSM1: -> AT+CMGR=4
2017-04-22 12:52:40,7, GSM1: Command is sent, waiting for the answer
2017-04-22 12:52:40,7, GSM1: <- +CMS ERROR: 321 (Invalid memory index)
2017-04-22 12:52:40,6, GSM1: Trying to get stored message 5
2017-04-22 12:52:41,7, GSM1: -> AT+CMGR=5
Any help would be appreciated...
|
|
Wed Apr 19, 2017 20:42
|
FOCOhalsoft: Good Day SMS Server Tools 3 Community,
Does anyone have any code and/or examples of sending an MMS / WAP Push message using SMS Server Tools and Wavecom devices?
If anyone has any experience and knowledge regarding this I would be happy to paypal / fund for time spent and/or materials...
Thank you all!!!
|
|
Wed Apr 19, 2017 17:40
|
FOCOhalsoft: Holy cow, solved it...
It was the BAUD rate, set it to 115200 and now it all works... on all modems...
Thanks for the assistance Forum!!!! :)
|
|
Wed Apr 19, 2017 17:27
|
FOCOhalsoft: Here is my modem portion of smsd.conf
[GSM1]
#init = AT^SSMSS=1+CPMS="MT"
device = /dev/ttyUSB0
incoming = yes
queues = other
mode = new
baudrate = 19200
rtscts = yes
cs_convert = yes
report = no
memory_start = 1
#eventhandler = /usr/local/bin/smsevent
|
|
Wed Apr 19, 2017 17:16
|
FOCOhalsoft: :( Uggg, again same result with different DISTRO
2017-04-19 11:15:09,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2017-04-19 11:15:09,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2017-04-19 11:15:09,5, smsd: Outgoing file checker has started. PID: 2556.
2017-04-19 11:15:09,7, smsd: All PID's: 2556,2558
2017-04-19 11:15:09,5, GSM1: Modem handler 0 has started. PID: 2558.
2017-04-19 11:15:09,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-04-19 11:15:09,6, GSM1: Checking device for incoming SMS
2017-04-19 11:15:09,6, GSM1: Checking if modem is ready
2017-04-19 11:15:09,7, GSM1: -> AT
2017-04-19 11:15:09,7, GSM1: Command is sent, waiting for the answer
2017-04-19 11:15:14,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2017-04-19 11:15:14,7, GSM1: <-
2017-04-19 11:15:15,7, GSM1: ->
2017-04-19 11:15:15,7, GSM1: Command is sent, waiting for the answer
2017-04-19 11:15:20,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2017-04-19 11:15:20,7, GSM1: <-
2017-04-19 11:15:20,7, GSM1: -> AT
2017-04-19 11:15:20,7, GSM1: Command is sent, waiting for the answer
2017-04-19 11:15:25,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 3.
2017-04-19 11:15:25,7, GSM1: <-
2017-04-19 11:15:25,7, GSM1: ->
2017-04-19 11:15:25,7, GSM1: Command is sent, waiting for the answer
|
|
Wed Apr 19, 2017 17:13
|
FOCOhalsoft: Detected FT4232H
[ 7.504736] usb 1-4.1: Number of endpoints 2
[ 7.504739] usb 1-4.1: Endpoint 1 MaxPacketSize 512
[ 7.504741] usb 1-4.1: Endpoint 2 MaxPacketSize 512
[ 7.504743] usb 1-4.1: Setting MaxPacketSize 512
[ 7.509764] usb 1-4.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 7.509792] ftdi_sio 1-4.1:1.1: FTDI USB Serial Device converter detected
[ 7.509818] usb 1-4.1: Detected FT4232H
The OS was seeing the modems, but the daemon was operating sluggish and displaying this error:
put_command expected (OK)|(ERROR), but minicom -s set to /dev/ttyUSB0 was echoing the key strokes, ie: reporting back OK with almost all commands.
I am trying another Ubuntu Distribution now with smstools3-3.1.15 to see if this was the 64bit Ubuntu issue.
|
|
Wed Apr 19, 2017 02:34
|
FOCOhalsoft: What new devices are best to work with SMS Server Tools, 3G and Higher? in USA and Europe?
I have 2 Wavecom Devices 3G "32 Port" and 4G "8 Port" and neither of them work so far with Server Tools :(
They have the FTDI chipset, and I am using Centos and Ubuntu to attempt operation!
|
|
Wed Apr 19, 2017 02:33
|
FOCOhalsoft: Based on your research are there any modems that are sold now that are compatible?
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
