Lantizia: So it's 8 years later than when I started this post :) Now working somewhere else entirely.
Currently using version '3.1.21-3' from Debian 10 (currently in testing, but seems to have the latest patches included) but installed on Debian 9 using the below config...
[GSM1]
device = @10.20.0.72:23
incoming = no
telnet_login_prompt = username:
telnet_login = voip
telnet_password_prompt = password:
telnet_password = 1234
telnet_cmd_prompt = module
telnet_cmd = module1
init = ATV1
needs_wakeup_at=yes
hangup_incoming_call = yes
rtscts=no
Few things I've learnt so far which may be helpful to others...
- Using 'telnet_cmd_prompt' this way deals both with the initial request and any subsequent requests after the module times out
- This works fine with a MV-372 with part number 2N149A (on firmware v10.160) but didn't work with a MV-370 I had with part number 2K123C (which has no newer firmware than v6.694.j) - something about it asking for the module/timeout is different (despite a 370 only having one module).
So my current setup with the config above works great with my MV-372/2N149A/v10.160 device (I have a few if people are interested)...
Except if SMSTools3 starts up *before* the GSM gateway has.
Does anyone know of some setting I can use which means SMSTools3 will regularly try to re-telnet every so often? Because if there is a network outage (between the VM running SMSTools3 and the MV-372) or a power outage of the MV-372 - it means restarting the smstools service everytime at the moment.
|
Lantizia: Hey, Thanks for writing that patch - I've only just got around to trying it. Here are my results...
2012-02-01 13:51:25,2, smsd: Smsd v3.1.14 started.
2012-02-01 13:51:25,2, smsd: Running as smsd:dialout.
2012-02-01 13:51:25,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.ixm96q /tmp/smsd_data.JL6SBG
2012-02-01 13:51:25,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2012-02-01 13:51:25,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2012-02-01 13:51:25,5, portech: Modem handler 0 has started. PID: 12271. Will only send messages.
2012-02-01 13:51:25,5, smsd: Outgoing file checker has started. PID: 12270.
2012-02-01 13:51:25,7, smsd: All PID's: 12270,12271
2012-02-01 13:51:25,6, portech: Checking if modem is ready
2012-02-01 13:51:26,7, portech: -> AT
2012-02-01 13:51:26,7, portech: Command is sent, waiting for the answer
2012-02-01 13:51:33,7, portech: put_command expected (OK)|(ERROR), timeout occurred. 1.
2012-02-01 13:51:33,7, portech: <- seaquake
2012-02-01 13:51:33,7, portech: ->
2012-02-01 13:51:33,7, portech: Command is sent, waiting for the answer
2012-02-01 13:51:39,7, portech: put_command expected (OK)|(ERROR), timeout occurred. 2.
2012-02-01 13:51:39,7, portech: <- *********
2012-02-01 13:51:39,7, portech: -> AT
2012-02-01 13:51:39,7, portech: Command is sent, waiting for the answer
2012-02-01 13:51:45,7, portech: put_command expected (OK)|(ERROR), timeout occurred. 3.
2012-02-01 13:51:45,7, portech: <- ** bad username or password!!! exit...
2012-02-01 13:51:46,7, portech: ->
2012-02-01 13:51:46,7, portech: Command is sent, waiting for the answer
Clearly there is still something off with what is send/received or the timings of the events when speaking to this device.
If anyone is interested in some paid work writing a fix for this I'm all ears - I can provide a server to work on that has access to one of these devices. It's probably something small really.
Steven
|
Lantizia: Hi,
We're a UK company that specializes in IP phone systems and I'd like to commission work to be done to support a new device with SMSTools3, this can be paid either to you or as a donation to the project.
The device is a PORTech MV-372 which is essentially two Siemens TS35i modules (two SIM cards in total) housed in a black box with ethernet ports. You can connect to it via SIP to send/receive calls and also connect to it over telnet to send/receive SMS over a mobile network.
I realise the Siemens TS35/TS35i have good support in SMSTools3 already, but after connecting with telnet SMSTools3 has issues logging in to the device before it can access the TS35i module directly.
I have one of these devices ready and a dedicated server with SMSTools3 3.1.14 installed anyone would like a try at this.
Details on how the telnet connection works can be found on page 36 of the manual for this device below. This works when using telnet manually, just not through SMSTools3.
http://www.portech.com.tw/data/MV-370%20user%20manual.pdf
Other people on the forum have had similar issues, such as the final post of this thread. This is partly why I am seeking someone to literally look at the issue directly as the forum holds no answers and the question has already been asked.
http://smstools3.kekekasvi.com/topic.php?post=3851#post3851
Any input you may have would be most appreciated, we intend to put SMSTools3 in to our phone system distribution and then convert SMS to XMPP (Jabber) allowing our customers to send/receive SMS to their customers or employees using a standard Instant Messaging client.
Naturally we prefer using Ethernet enabled GSM modems as our phone systems are mostly hosted virtually so serial or USB is out of the question.
Please reply below if your interested.
|
