Which ports should I use to connect to Total Response?

This one-page article summarizes ports needed for Total Response.

💻 Total Response Software Ports and Firewall Configuration

🚀 Introduction

The Total Response Software requires configuration to communicate with the SQL Server and its various services across several specific network ports.

For the software to function correctly, the following ports and services must have exceptions configured through your firewall and any endpoint security solutions that may be blocking access.

🌐 Total Response Version 5.x Required Ports and Services

Total Response Version 5.x requires use of several TCP ports. For the software to work properly, the following information and ports need to have exceptions through the firewall and any endpoint security that may be blocking their access: 

• LoginManager service configured to TCP port 9000
• Login Service TCP port 9090
• Launcher service configured to TCP port 8000
• CAD to API configured over TCP port 5000
• Traffic between the Supervisor and Call Handler requires TCP ports 1000 and 11000
• The default port for SQL Server communication is TCP port 1433 (see below for more information). This port is used for the MSSQLSERVER instance by default. 
• UDP port 1434 is utilized for specific connections. (See below for more information).
   

🌐 Total Response Version 6.x Required Ports and Services

Total Response Version 6.x or higher requires use of several TCP ports. For the software to work properly, the following information and ports need to have exceptions through the firewall and any endpoint security that may be blocking their access: 

• LoginManager service configured to TCP port 9100
• Launcher service configured to TCP port 8100
• CAD to API configured over TCP port 5000
• Traffic between the Supervisor and Call Handler requires TCP ports 1000 and 11000
• The default port for SQL Server communication is TCP port 1433 (see below for more information). This port is used for the MSSQLSERVER instance by default. 
• UDP port 1434 is utilized for specific connections. (See below for more information).

🔑 Key Points Regarding SQL Server Ports

Total Response requires access to the SQL Server via the following default ports:

TCP Port 1433

• Purpose: The default port for primary SQL Server communication (specifically for the MSSQLSERVER instance).

• Default Behavior: SQL Server listens on this port by default.

• Security: TCP ensures data integrity by creating a secure, authenticated connection before exchanging data streams.

• Configuration: You can configure SQL Server to listen on a different port, but port 1433 is used in most standard installations.

UDP Port 1434

• Purpose: Utilized by the SQL Server Browser Service.

• Function: This service helps client applications discover available SQL Server instances on the network.

• Dynamic Nature: Unlike TCP port 1433, UDP port 1434 is dynamically assigned.

⚠️ Important Configuration Note

To allow SQL Server access through your Windows Firewall or other security measures, you must create rules to open these ports.

Please leave all listed Ports OPEN.

If any changes are required, including moving or changing a port for any of the listed services, you must contact us before making the modification:

Email Support: support@totalresponse.com

This ensures that our software is configured correctly and will continue to work properly after any infrastructure changes.

Addendum

PowerShell Administrator cmdlet to open up the ports:

Command to verify the ports are open on a TR Server: