SMS Server Tools 3
This site is hosted by Kekekasvi.com
 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. Please login or register. Sat May 25, 2024 10:12
SMSTools3 Community » Help and support Bottom

[solved] Could not send character A, cause: Permission denied

  This topic is locked

Page:  1

Author Post
Member
Registered:
May 2009
Location: Hinnerup, Denmark
Operating system name and version: W2k8 and Cygwin
Version of smsd: 3.1.6
Smsd installed from: sources
Name and model of a modem / phone: Siemens MC35
Interface: Serial using RS232-to-IP Server


Hello, im having the following problem with my modem AFTER I have connected my new RS232-to-IP adapter.

RS232-to-IP:  http://www.roline.dk/RolFront/varekat3.aspx?art=4288 


When I start the sms server, then I works fine for a minute or two, but then it makes this errors and hangs
This is the error with rtscts=no in conf file.:


This is the error with rtscts=yes in conf file.:


What can I do to prevent this error ?

Best regards
WolfieDK

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Your model of this device does not support hardware handshake, which causes that only rtscts = no setting can be used.

Have you checked and changed the baudrate setting? In 3.1.6 it defaults to 115200, but with this device only values 300 - 921600 are supported. Probably a value 57600 is a good choice.

I do not know why this device works only for a few minutes under Cygwin. Perhaps it has something to do with drivers which do not work properly. I think that there is not much to do for fixing this issue.

It may be interesting to test if this device can be used as a network modem, which is supported since 3.1.7. However, the "quick guide" talks about IP address and netmask, but it does not say what port is used. If you have some spare time and interest, you could try to capture network traffic using Wireshark application. It may give a hint about what causes the error, and it will show if this device can be used directly through the socket.

Member
Registered:
May 2009
Location: Hinnerup, Denmark
Topic owner
Hi Keke, and thank you soooo mutch for a awesome apllication and forum. It is so mutch appriciated :D

Quote
Have you checked and changed the baudrate setting? In 3.1.6 it defaults to 115200, but with this device only values 300 - 921600 are supported. Probably a value 57600 is a good choice.

Yes, I have all ready changed the baudrate to 9600 on both the modem and the rs232-to-ip device. But the error still occur. I will try to change it to 57600 as requested.

Quote
However, the "quick guide" talks about IP address and netmask, but it does not say what port is used.

It uses TCP port 1235 ?

Quote
... and it will show if this device can be used directly through the socket....

I have all ready wireshack installed, shall I capture a log, and paste it here, can you then help me furtere ?

Best regards
WolfieDK

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
WolfieDK wrote
Quote
... and it will show if this device can be used directly through the socket....

I have all ready wireshack installed, shall I capture a log, and paste it here, can you then help me furtere ?

I could try to check what can be examined from the dump...

Instructions in the private block:

Hidden private text.



Member
Registered:
May 2009
Location: Hinnerup, Denmark
Topic owner
Hello Keke

Thanks for you help, i have found the problem.

I have updated from 3.1.6 to 3.1.14 and it stil makes some other errors.
But then I changed from dev/com3 to @172.0.10.5:1235 and then it can connect without the windows driver/software from the manufactor.

But it stil makes an error, so I changed the rtscts=off to rtscts=on again, and now it works flawless :mrgreen:

Best regards
WolfieDK

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Thank's for the information.

I'm still wondering if rtscts really has any effect when device is a socket. At least it should not have...

Member
Registered:
May 2009
Location: Hinnerup, Denmark
Topic owner
Hi Keke

Quote
I'm still wondering if rtscts really has any effect when device is a socket. At least it should not have...

Okay, do you need any information before you can confirm if there is a problem with rtscts or not?
I will gladly post logs or configurations files if needed?

Best regards
WolfieDK :D

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
WolfieDK wrote
Quote
I'm still wondering if rtscts really has any effect when device is a socket. At least it should not have...

Okay, do you need any information before you can confirm if there is a problem with rtscts or not?
I will gladly post logs or configurations files if needed?

In the code there is DEVICE_IS_SOCKET tested. If you can show with smsd.conf and smsd.log files that rtscts still has an effect, it might be interesting to check.

Member
Registered:
May 2009
Location: Hinnerup, Denmark
Topic owner
Hi Keke!

Quote
In the code there is DEVICE_IS_SOCKET tested...

Sorry, but will you please tell me where I can find this ? :mrgreen:

Best regards
WolfieDK

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
WolfieDK wrote
Quote
In the code there is DEVICE_IS_SOCKET tested...

Sorry, but will you please tell me where I can find this ? :mrgreen:

My writing was unclear... :(

What I meant was that there is DEVICE_IS_SOCKET tested, and therefore the code does not use the setting rtscts at all, and it then should not have any effect.

You have now a working system with decice = @172.0.10.5:1235 and rtscts = yes. For testing, do not change anything else than rtscts = no, and restart the smsd. There should be no errors in the log, but in the case of errors show the piece of log here.

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Have you checked rtscts = no and found results, or should I close this topic?

Member
Registered:
May 2009
Location: Hinnerup, Denmark
Topic owner
Hi Keke

Sorry for not posting befor. I dont have the same spare time after I become daddy :-)

I will test this tomorrow :mrgreen:

  This topic is locked

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.