CentOS 6.5:
3.1.15:
CentOS repository:
Portech MV 370 GSM Gateway:
over Ethernet:

Hi all,

i tried to connect my Portech MV 370 to my LAN over Ethernet. But I'm quiet new to Linux and smstools.
so i'm not sure how i have to configure smstools. with my config the program starts, then the files are moved from outgoing to checked but they won't be send...

after spending hours with google search and everybody even used gateways as usb device i posted in here.

maybe anyone could tell me where's my fault and maybe explain a bit if i don't get it,

thanks in advance

my log file
2014-02-05 15:55:30,7, smsd: All PID's: 12965,12967 2014-02-05 15:55:30,5, GSM1: Modem handler 0 has started. PID: 12967. Will only send messages. 2014-02-05 15:55:30,6, GSM1: Checking if modem is ready 2014-02-05 15:55:30,7, GSM1: -> AT 2014-02-05 15:55:30,7, GSM1: Command is sent, waiting for the answer 2014-02-05 15:55:40,5, smsd: Moved file /var/spool/sms/outgoing/send_iuOVaC to /var/spool/sms/checked 2014-02-05 15:55:49,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1. 2014-02-05 15:55:49,7, GSM1: <- username: root root root root root root root root root root root root root root root rpassword: ****************************************************************************bad username or password!!! exit... 2014-02-05 15:55:49,7, GSM1: -> 2014-02-05 15:55:49,7, GSM1: Command is sent, waiting for the answer 2014-02-05 15:55:51,5, smsd: Moved file /var/spool/sms/outgoing/send_diT347 to /var/spool/sms/checked 2014-02-05 15:55:54,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.

smsd.conf

devices = GSM1 logfile = /var/log/smsd/smsd.log outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed report = /var/spool/sms/report sent = /var/spool/sms/sent loglevel = 7 user = root infofile = /var/run/smsd/smsd.working pidfile = /var/run/smsd/smsd.pid # 3.1.5 introduced smart logging # once your configuration is OK, set log level lower (5 is good in most cases) smart_logging = yes [GSM1] device = @192.168.X.X:23 telnet_login_prompt = username: telnet_login = root telnet_password_prompt = password: telnet_password = X

I'm have such a problem. You managed to solve this problem? please help me if you can

Me too. Any suggestion?

FYI, I will release a new beta version within a few days. This version will have some changes for the network modems.

Ok thanks, be waiting for it.

Garraty wrote

Me too. Any suggestion?

I found solution for this problem in this post - http://smstools3.kekekasvi.com/topic.php?id=763

Hi guys,
thanks for all.

I installed 3.1.16 Version, for use Portech and telnet socket. It's work fine for me with this config:

+++++++++++++++++++++++++++++++++++++++++
[GSM1]
device = @10.XXX.XXX.XXX:23
telnet_crlf = yes
telnet_login_prompt = username:
telnet_password_prompt = password:
telnet_login = voip
telnet_password = 1234
telnet_cmd_prompt = logout, module, module1, module2, state1, state2.
telnet_cmd = module1
incoming = no
device_open_alarm_after = 5
socket_connection_alarm_after = 5
init = ATV1
#
needs_wakeup_at=yes
hangup_incoming_call = yes
rtscts=no
regular_run_logfile = /var/log/smstools/smsd_run_GSM1.log
pin = ignore
status_signal_quality = no
mode = new
queues = GSM1,ALL
decode_unicode_text = yes
internal_combine = yes
++++++++++++++++++++++++++++++++++++++++

Now, i need to use ALL modem into the portech (my device is MV37 with 8 modules. But if i add a context GSM2-module2, GSM3-module3, etc.. demon says:

GSM2: Couldn't connect socket @10.139.233.100:23, error: Connection refused, waiting 5 sec.

Obviously, because the socket connection is busy for GSM1-module1. So, the solution could be to keep the socket open and change module for each SMS, and rotate them until the end of the task, but how do that?

Garraty wrote

Obviously, because the socket connection is busy for GSM1-module1.

Each module should use it's own port. I do not have this kind of device, but I believe that there are settings for each module.

I confirm, each module has its own identification number, module1, module2 etc. But all modules can be contacted through the same telnet connection. Certainly I can not use them all at once, it would be enough to cycle them without disconnect the socket connection every time.

I can do this with a script in PHP, so

open the connection
call the module1
send SMS
release module1 (without close connection)

call module2
send SMS
release module2
....
etc ..
release module8
close socket connection.

In this way i can use all the modems, 1 every 4 seconds.


But this is not replicable with smstool because if i create two contexts with 2 different modules, as mentioned, the second module is not used because the connection is busy with the first module and the first connection.

I seem to understand that this version is fine to use with GSM Gateway with a single modem.


Am i wrong?

Smstools does not and will not support cycling, because each modem handlers are different processes. If only one port is provided, it cannot be shared and therefore only one module can be used.

Can you check if different port can be defined for each modem? It looks like "Server URL" or "Forward Setting" might be the key.

Thanks Keke,

Forward Setting is used to forward voice calls.

Instead, i don't understand fully what means "Server Mode" and "Bank Mode", i believe that this modes are used for manage received SMS and forward to a "BANK" or a "SERVER". But i'm don't realy sure.

I'm study..!