Listening Socket by AT | Thales IoT Developer Community
January 28, 2018 - 10:39am, 2324 views
I want to setup a listening socket with AT Commands.
Unfortunately the examples in the AT pdf are confusing and don't work.
AT^SISS=0,srvType,"Socket"
AT^SISS=0,conId,0
AT^SISS=0,address,"socktcp://listener:80"
AT^SISO=0
^SIS: 0,5
AT^SISO?
^SISO: 0,"Socket",3,3,0,0,"1.2.3.4:80","0.0.0.0:0"
I can't connect to 1.2.3.4:80 , tried different hosts and programms
telnet 1.2.3.4 80
***** - TCP4-CONNECT:1.2.3.4:80
Connect Timeout and No Unc / ^SIS Message
In Knowledge Base there is no Server / Listening Example and the Client Example uses
AT^SISS=0,"srvType","Transparent"
while AT pdf uses "Socket"
Hello,
from the reply to AT^SISO? command I can see that the connection is still in the "connecting" state, so the listener is not yet up.
Are you sure that you have configured the internet connection properly? Please also make sure that your subscription includes the public IP address that is accessible form the internet. If not you will not connect to your server.
If your listener is configured properly (as in AT commands specification) and the connection is up and the address is accessible from outside you should get the same URC as it is shown for transparent ****.
Transparent or non-transparent connection type makes a difference after connection establishment - in non-transparent **** you need AT commands to send and receive data while in transparent **** the data is just being exchanged transparently.
Please also see here for internet services: https://iot-developer.thalesgroup.com/tutorial/concept-board-internet-se...
Please paste the complete log and the ATI1 reply to identify the module type.
Best regards,
Bartłomiej
The responses are exactly as described in the AT pdf, what other do you expect?
This is a listening socket so it does not connect but wait for a connection from outside.
I have an IP adress and can ping 8.8.8.8 (google) so connection is up.
What else as the public adress is shown by AT^SISO?
There is no listening example at the page you linked as I told.
ATI1
Cinterion
EHS6
REVISION 03.001
A-REVISION 00.000.31
OK
The log is complete what else is needed to get a listening tcp socket up?
There is no Internet connection setup log. But if you can ping 8.8.8.8 address using the same Internet connection profile identifier it seems that the connection is working.
It looks like you have done everything correctly on the module.
But still you should make sure (check with your service provider or test with some other device) that your subscription allows incoming connections. It is possible that even if you get the IP address from the public pool, your provider may still block the incoming traffic until you buy a special service.
Regards,
Bartłomiej
Ok it works the other way round, I can connect from the EHS6 to my computer.
And I can't connect from my Computer to an SSH Server on my Smartphone either.
So probably the ports are blocked from outside by my network.
May be there are not enough IP-Adresses for every phone to have a real one.
I've just got the info all smartphones work via proxy here and don't have a public ip on their own.
Thanks for the information.