SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Thu Nov 21, 2024 22:44
SMSTools3 Community » Help and support Bottom

Problem with Portech

Login and Post Reply

Page:  1

Author Post
Member
Registered:
May 2011
Location: Porto, Portugal
Operating system name and version: CentOS 5.6
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Portech MV-370 Gateway
Interface: Lan - over telnet port.

Hi,

I'm trying to get sms server tools 3 to send sms via Portech gateway.

I've try with this two configuration but just doesn't work:
[GSM1]

device = @192.168.XX.XX:23
incoming = no
telnet_login_prompt = voip
telnet_password_prompt = 1234


and

[GSM1]

device = @192.168.XX.XX:23
incoming = no
telnet_login = voip
telnet_password = 1234


Thanks in advance.

Regards,

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Those settings are correct:
telnet_login = voip
telnet_password = 1234


*_prompt settings are needed, if default values do not match.

You could connect to the device with telnet, and show what that device talks before prompts, and what are the prompts.

Member
Registered:
May 2011
Location: Porto, Portugal
Topic owner
Log messages:
2011-05-23 20:24:18,7, GSM1: Command is sent, waiting for the answer
2011-05-23 20:24:24,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-05-23 20:24:24,7, GSM1: <- username:
2011-05-23 20:24:25,7, GSM1: ->
2011-05-23 20:24:25,7, GSM1: Command is sent, waiting for the answer
2011-05-23 20:24:30,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-05-23 20:24:30,7, GSM1: <- password:
2011-05-23 20:24:31,3, GSM1: Modem is not ready to answer commands (Timeouts: 0)
2011-05-23 20:24:31,2, GSM1: Failed to initialize modem GSM1. Stopping.



Telnet with Porteck:

[root@nms checked]# telnet 192.168.12.35 23
Trying 192.168.12.35...
Connected to 192.168.12.35.
Escape character is '^]'.

username: voip
voip
password: *1234
****
user level = admin.

command: logout, module1, module2, state1, state2, info.
]

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Use the following settings:

telnet_login_prompt: username:
telnet_login_prompt = username:
telnet_login = voip
telnet_password_prompt: password:
telnet_password_prompt = password:
telnet_password = 1234


« Last edit by keke on Thu May 26, 2011 09:12, 164 months ago. »
Member
Registered:
May 2011
Location: Porto, Portugal
Topic owner
Hi,

I've need to change your code for sms3 service start to:
device = @192.168.12.35:23
incoming = no
telnet_login_prompt = username:
telnet_login = voip
telnet_password_prompt = password:
telnet_password = 1234


Message log:
2011-05-23 20:40:40,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2011-05-23 20:40:40,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2011-05-23 20:40:40,5, GSM1: Modem handler 0 has started. PID: 16783. Will only send messages.
2011-05-23 20:40:40,5, smsd: Outgoing file checker has started. PID: 16782.
2011-05-23 20:40:40,7, smsd: All PID's: 16782,16783
2011-05-23 20:40:40,3, GSM1: Couldn't connect socket @192.168.12.35:23, error: Connection refused, waiting 5 sec.
2011-05-23 20:40:45,6, GSM1: Couldn't connect socket @192.168.12.35:23, error: Connection refused, waiting 5 sec.
2011-05-23 20:40:50,6, GSM1: Couldn't connect socket @192.168.12.35:23, error: Connection refused, waiting 5 sec.

Regards

Member
Registered:
May 2011
Location: Porto, Portugal
Topic owner
Connectivity issue only happen with smst3 since I can telnet mv370 without problems.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Goofy wrote
I've need to change your code for sms3 service start to:

Sorry, I was not sensitive enough... :(

Goofy wrote
Connectivity issue only happen with smst3 since I can telnet mv370 without problems.

In the post #3 smsd was able to connect to that device. And now it's not. I'm not sure what causes that. As the error message is "Connection refused", you could try to reset the mv370 and try with smsd without using telnet before it.

Member
Registered:
May 2011
Location: Porto, Portugal
Topic owner
Keke,

I've to change following lines:
telnet_login_prompt : username:
telnet_login = voip
telnet_password_prompt : password:
telnet_password = 1234

to

telnet_login_prompt = username:
telnet_login = voip
telnet_password_prompt = password:
telnet_password = 1234

After reboot I can attempt to login but no success on send sms, can anyone help please?

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Goofy wrote
I've to change following lines:
telnet_login_prompt : username:
telnet_login = voip
telnet_password_prompt : password:
telnet_password = 1234

to

telnet_login_prompt = username:
telnet_login = voip
telnet_password_prompt = password:
telnet_password = 1234

Yes, I was not sensitive enough... :( The original post is now fixed.

Goofy wrote
After reboot I can attempt to login but no success on send sms, can anyone help please?

Without seeing the log I cannot guess what is the problem.

Member
Registered:
Aug 2011
Location: Australia
Running into the same issue with Portech mv-370 using smstools latest version.

Did you ever resolve it?

I can telnet to the MV370 and issue the commands manually and it works fine.


Configs

# /etc/smsd.conf
# Description: Main configuration file for the smsd
devices = GSM1
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
incoming = /var/spool/sms/incoming
logfile = /var/log/smstools/smsd.log
infofile = /var/run/smstools/smsd.working
pidfile = /var/run/smstools/smsd.pid
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
stats = /var/log/smstools/smsd_stats
loglevel = 7

[GSM1]
device = @172.1.1.253:23
telnet_login_prompt = username:
telnet_password_prompt = password:
telnet_login = voip
telnet_password = 1234
incoming = no
device_open_alarm_after = 5
socket_connection_alarm_after = 5
init = module1



Startup log
2011-08-22 12:50:52,2, smsd: Smsd v3.1.14 started.
2011-08-22 12:50:52,2, smsd: Running as root:root.
2011-08-22 12:50:52,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.89Jux2 /tmp/smsd_data.kwnqDt
2011-08-22 12:50:52,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2011-08-22 12:50:52,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2011-08-22 12:50:52,5, smsd: Outgoing file checker has started. PID: 27339.
2011-08-22 12:50:52,7, smsd: All PID's: 27339,27341
2011-08-22 12:50:52,5, GSM1: Modem handler 0 has started. PID: 27341. Will only send messages.
2011-08-22 12:50:52,6, GSM1: Checking if modem is ready
2011-08-22 12:50:52,7, GSM1: -> AT
2011-08-22 12:50:52,7, GSM1: Command is sent, waiting for the answer
2011-08-22 12:50:58,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-08-22 12:50:58,7, GSM1: <- username:
2011-08-22 12:50:59,7, GSM1: ->
2011-08-22 12:50:59,7, GSM1: Command is sent, waiting for the answer
2011-08-22 12:51:04,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-08-22 12:51:04,7, GSM1: <- password:
2011-08-22 12:51:04,7, GSM1: -> AT
2011-08-22 12:51:04,7, GSM1: Command is sent, waiting for the answer
2011-08-22 12:51:09,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 3.
2011-08-22 12:51:09,7, GSM1: <- ** bad username or password!!!
2011-08-22 12:51:10,7, GSM1: ->
2011-08-22 12:51:10,7, GSM1: Command is sent, waiting for the answer
2011-08-22 12:51:15,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 4.
2011-08-22 12:51:15,7, GSM1: <-
2011-08-22 12:51:15,7, GSM1: -> AT
2011-08-22 12:51:15,7, GSM1: Command is sent, waiting for the answer
2011-08-22 12:51:20,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 5.

Member
Registered:
Aug 2011
Location: Australia
A bit more messing around with the configuration and trying to modify I can see that the Portech doesn't handle the username/input part correctly through smstools.

This configuration seems to repeat the username and even in the password box until it can't accept any more characters, causing error.
telnet_login_prompt = username:^M
telnet_login = voip^M
#telnet_password_prompt = password:
#telnet_password = 1234

^M is ctrl+v ctrl+m which I got from another bugreport thread on the Portech not accepting end of line correctly.

Anyone got any suggestions on how to get it to correctly accept the username and password?


2011-08-22 16:43:23,6, GSM1: Checking if modem is ready
2011-08-22 16:43:24,7, GSM1: -> AT
2011-08-22 16:43:24,7, GSM1: Command is sent, waiting for the answer
2011-08-22 16:43:39,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2011-08-22 16:43:39,7, GSM1: <- username: voip voip voip voip voip voip voip voip voip voip voip voip voip voip voip vpassword: ****************************************************************************bad username or password!!!
2011-08-22 16:43:39,7, GSM1: ->
2011-08-22 16:43:39,7, GSM1: Command is sent, waiting for the answer
2011-08-22 16:43:44,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2011-08-22 16:43:44,7, GSM1: <-

Member
Registered:
Jan 2012
Location: Lisbon, Portugal
Hi,



Are there any news about the problem?

I have the same issue.


Thanks

Member
Registered:
Apr 2011
Location: Kupchino, Russian Federation
Take a look at the patch from another similar topic http://smstools3.kekekasvi.com/topic.php?post=4011#post4011.

Login and Post Reply

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.