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!

What are exact models and types of those two Wavecom devices?

The FTDI chipset should not be a problem, and I'm just wondering why those devices did not work.

When using multiple GSM modules, it is required that each module has it's own serial interface to the host. Multiplexed interface is not supported currently.

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.

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

Please verify that in your smsd.conf there is device = /dev/ttyUSB0. By default there might be ttyS0 which does not give an error, but is silent.

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

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!!!!