 |  |  |  |  | Site map / Terms of use |  |
 |  |  |  |  |  |
- What are the possible sources of problem when using the TCP socket application?
- please read carefully the documentation on the AT#EscapeCodingMode parameter
- When the eDevice module is server:
- The principal cause of trouble is when the eDevice module does not have a public IP. Indeed, to reach the web server from any location, the eDevice must be attributed a public IP from the provider. Please check with your provider to determine if you can have public IPs with your subscritpion. More generally, IP addresses like 10.x.x.x, or 192.168.x.x are private. If the edevice module has a private IP, the web server can be reached only by devides that are on the same private networks. This is the case for example with Ethernet devices that can be reached only by other devices on the same LAN.
- As a first step it is recommended to remove an IP filtering with the AT#TCPClient=0.0.0.0 setting.
- Only one client can be connected at a time. Hence the TCP socket application may seem unavailable if several clients try to access it at the same time.
Back
FAQ
