Operating system name and version: Debian Jessie 8.7
Version of smsd: 3.1.20
Smsd installed from: source, make & make install
Name and model of a modem / phone: 2N Voiceblue
Interface: ttyUSB0

I've installed SMSTools on a Debian Linux box and attempted to configure to work. I'm looking at purchasing this unit:

https://www.aliexpress.com/item/Wavecom-16-ports-wavecom-q2303-modem-pool-with-cheapest-gsm-module/32337026196.html?spm=2114.13010208.99999999.264.feDWYf

Question: Will this work with SMS Server Tools 3 ?


Before I spend any money however - I'm testing with an old (10 year) 2N Voiceblue modem I have. I'm starting to suspect that it doesn't support the protocols that newer devices use (and hence SMS Tools will work with).

Any advice appreciated.

thanks
Kent.


When I connect to the modem through the terminal, this is what I've done to send a message.
-----------------------------------------------
T!G=55

OK
AT!G=A6

OK
AT&G00=AT+CMGF=1
<++g00 AT+CMGF=1
-->g00 OK

OK
AT&G00=AT+CMGS="+6421123456"
<++g00 AT+CMGS="+6421123456"
-->g00 >
-->g00 +CMGS: 5
-->g00 OK

OK

*smsout: 0,1,
---------------------------------------------

Attempting to send using SMS Tools, it always errors. I've played with the pre-init and init settings, which has got me a bit further.

---------------------------------------------------------------

2017-04-12 22:47:12,2, smsd: Smsd v3.1.20 started.
2017-04-12 22:47:12,2, smsd: Running as root:root (0:0).
2017-04-12 22:47:12,7, smsd: Running startup_check (shell): /sms/incoming//smsd_script.s8AqRE /tmp/smsd_data.P6AvOX
2017-04-12 22:47:12,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2017-04-12 22:47:12,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2017-04-12 22:47:12,5, smsd: Notifier has started. PID: 7552.
2017-04-12 22:47:12,5, smsd: Outgoing file checker has started. PID: 7550.
2017-04-12 22:47:12,7, smsd: All PID's: 7550,7553,7552
2017-04-12 22:47:12,5, GSM1: Modem handler 0 has started. PID: 7553.
2017-04-12 22:47:12,5, GSM1: Using check_memory_method 1: CPMS is used.
2017-04-12 22:47:12,6, GSM1: Checking device for incoming SMS
2017-04-12 22:47:12,6, GSM1: Checking if modem is ready
2017-04-12 22:47:12,7, GSM1: -> AT
2017-04-12 22:47:12,7, GSM1: Command is sent, waiting for the answer. (5)
2017-04-12 22:47:12,7, GSM1: <- AT OK
2017-04-12 22:47:12,6, GSM1: Initializing modem
2017-04-12 22:47:13,7, GSM1: -> AT!G=55
2017-04-12 22:47:13,7, GSM1: Command is sent, waiting for the answer. (10)
2017-04-12 22:47:13,7, GSM1: <- AT!G=55 OK
2017-04-12 22:47:13,7, GSM1: -> AT!G=A6
2017-04-12 22:47:13,7, GSM1: Command is sent, waiting for the answer. (10)
2017-04-12 22:47:13,7, GSM1: <- AT!G=A6 OK
2017-04-12 22:47:13,6, GSM1: Checking if Modem is registered to the network
2017-04-12 22:47:13,7, GSM1: -> AT+CREG?
2017-04-12 22:47:13,7, GSM1: Command is sent, waiting for the answer. (10)
2017-04-12 22:47:13,7, GSM1: <- AT+CREG? ERROR
2017-04-12 22:47:13,6, GSM1: Ignoring that modem does not support +CREG command.
2017-04-12 22:47:13,6, GSM1: Selecting PDU mode
2017-04-12 22:47:13,7, GSM1: -> AT+CMGF=0
2017-04-12 22:47:13,7, GSM1: Command is sent, waiting for the answer. (5)
2017-04-12 22:47:13,7, GSM1: <- AT+CMGF=0 ERROR

If the device provides independent serial interface for each module, like /dev/ttyUSB0, /dev/ttyUSB1 and so on, it can be used with SMSTools3.

If the device is using single serial interface and multiplexer with prefixes, like 2N Voiceblue does, it cannot be used. In the past (2010) I created a test version of smsd with MUX capabilities, but at that time there was a problem with the firmware of 2N Gateway. Also the gateway was able to handle only single module concurrently, which causes lots of problems when smsd is trying to handle tens of modules simultaneously. Because of that I did not publish a version containing MUX.

Hi Keke,

Thanks for that - that makes sense and fits with what I'm seeing.

How do I know if this device will work this way then ?

https://www.aliexpress.com/item/M35-16-Channels-GSM-Modem-Pool-For-Bulk-SMS-Sending-support-Imei-change-Quad-band/32735203721.html

It says: AT command control standards: GSM07.07, GSM07.05 and other extension

thanks

Kent.

Standards are OK and PDU mode is required, it seems to be OK too.

Screenshots of the program SMSCaster E-Marketer looks very similar, which may mean that both devices provides individual serial ports, or both are providing multiplexed interface only. To get the final and reliable answer, I think that you should contact the seller or manufacturer.

Hi Keke,

I've already checked with the supplier and they have confirmed the unit has independent serial interfaces for each modem.

Thanks for getting back to me. I'll see how it goes and report back here.

cheers

Kent.

Based on your research are there any modems that are sold now that are compatible?