Technical Documentation
IN THIS ARTICLE

Incorrect email!

The article was successfully sent to the email

Summary

This article helps determine the number of ports that must be opened on Network equipment for remote Consoles, Devices and Services.

Example deployment scenarios are provided at the end of this article to help you select the appropriate port allocation.
All ports and protocols referenced in this article are based on the default TRBOnet configuration.

Clients connecting to the server - open ports on the server side

Dispatch Console

VoIP ports: 4022–4032 UDP
Command port: 4021 TCP

Mobile Client

VoIP ports: 20000–20404 UDP
Command port: 5070 TCP & UDP

Watch Console

Port range: 4020–4040 UDP
Command port: 4019 TCP

Web Console

Connection port: 80 TCP

Services or devices - open ports for incoming Server connections

TRBOnet Agent

VoIP port: 4022 UDP
Command port: 4020 TCP
One VoIP port is required for each Server connected to the TRBOnet Agent.

Swift IP Gateway

A200 Connection & Programming port: 8002 UDP
A002 Connection ; Programming port: 8002 ; 3836 UDP

Map Server

Connection port: 58775 TCP
Capacity MAX: One VoIP port is required for each talkpath added in TRBOnet Agent or Server.

Use Case: Saving Multiple Audio Recordings

One of the most common issues in deployments with Remote Consoles and a TRBOnet Server is an insufficient number of allocated ports.

This issue often occurs when dispatchers save multiple voice recordings simultaneously from the Recent Calls window. For example, a dispatcher may select 20 to 30 recordings and save all files at the same time. Each file transfer requires a separate TCP or UDP port.

If only 10 ports are allocated for a Console and a dispatcher starts downloading 30 recordings simultaneously, the Console may consume ports outside its assigned range. The additional connections may overlap with ports allocated to other Consoles.

As a result, other Consoles may fail to connect or may be unable to download recordings.

To prevent this issue, use one of the following approaches:

• Instruct dispatchers to save recordings one file at a time.
• If simultaneous download of multiple recordings is required, allocate enough ports for each Console to support the maximum number of recordings that can be downloaded at the same time.

The values provided by the calculator are average recommendations suitable for most TRBOnet deployments.


Summary

This article helps determine the number of ports that must be opened on Network equipment for remote Consoles, Devices and Services.

Example deployment scenarios are provided at the end of this article to help you select the appropriate port allocation.
All ports and protocols referenced in this article are based on the default TRBOnet configuration.

Clients connecting to the server - open ports on the server side

Dispatch Console

VoIP ports: 4022–4032 UDP
Command port: 4021 TCP

Mobile Client

VoIP ports: 20000–20404 UDP
Command port: 5070 TCP & UDP

Watch Console

Port range: 4020–4040 UDP
Command port: 4019 TCP

Web Console

Connection port: 80 TCP

Services or devices - open ports for incoming Server connections

TRBOnet Agent

VoIP port: 4022 UDP
Command port: 4020 TCP
One VoIP port is required for each Server connected to the TRBOnet Agent.

Swift IP Gateway

A200 Connection & Programming port: 8002 UDP
A002 Connection ; Programming port: 8002 ; 3836 UDP

Map Server

Connection port: 58775 TCP
Capacity MAX: One VoIP port is required for each talkpath added in TRBOnet Agent or Server.

Use Case: Saving Multiple Audio Recordings

One of the most common issues in deployments with Remote Consoles and a TRBOnet Server is an insufficient number of allocated ports.

This issue often occurs when dispatchers save multiple voice recordings simultaneously from the Recent Calls window. For example, a dispatcher may select 20 to 30 recordings and save all files at the same time. Each file transfer requires a separate TCP or UDP port.

If only 10 ports are allocated for a Console and a dispatcher starts downloading 30 recordings simultaneously, the Console may consume ports outside its assigned range. The additional connections may overlap with ports allocated to other Consoles.

As a result, other Consoles may fail to connect or may be unable to download recordings.

To prevent this issue, use one of the following approaches:

• Instruct dispatchers to save recordings one file at a time.
• If simultaneous download of multiple recordings is required, allocate enough ports for each Console to support the maximum number of recordings that can be downloaded at the same time.

The values provided by the calculator are average recommendations suitable for most TRBOnet deployments.


Helpful?
We're glad this article helped.

Thanks for letting us know. What went wrong?