Using COM/IP to Access TCP/IP Endpoints

Guidelines for applications using COM/IP virtual COM ports to reach
endpoints on public/private networks and wireless data networks

Dial-based applications use modem emulator to connect over TCP/IP
The client computer
Windows 10/8/7/2012/2008/Vista/2003/XP/2000, 32 and 64-bit versions, single and multi-user, native and virtual environments
Your application runs with no software changes, using Windows modem devices or issues modem AT commands directly to virtual COM ports
The COM/IP Redirector
Kernel-level device driver, no service overhead, always available
High-performance data path entirely at kernel level
Interprets ATD dial strings as IP address and port number, such as ATDT19207413700504000 connects to port 4000
Can answer incoming TCP connections and indicate RING to application
The network connection
Firewalls must allow outbound connections to IP addresses and port numbers used by any connection through COM/IP
Proxy servers are supported by COM/IP for SOCKS v4/5 and HTTPS
The TCP/IP endpoint
Any network device that supports TCP/IP connections, including TCP/IP access points on wireless data networks
Can initiate connections to be answered by COM/IP
Can be another copy of COM/IP for back-to-back operation

Applications using the COM/IP Redirector
with wired and wireless networks

electricity/gas meters automated meter reading / alarm monitoring
substation management monitoring, control
flow/pressure meters data collection
oil/gas field equipment data collection
wind turbines monitoring, control
billing, insurance, pharmacy inbound data feeds
linear accelerators monitoring
financial services  
trading systems data collection/submission
transactions point-to-point (non-Internet) networking
GPS nav units upload map and routing data updates
traffic recorders data collection
variable message signs text upload, control
road condition sensors data collection
tank gauges, pumps fuel asset management
 Industrial Automation
 Networks / IT Services