Installing and Configuring a RadioPro IP Gateway with the ICU Utility
Step-by-step outline for configuring a RadioPro IP Gateway with ICU, assigning a static IP, setting time sync, client accounts and aliases, and port forwarding.
This article outlines how a RadioPro IP Gateway is installed. The radio-specific steps are in the per-radio articles (radiopro-ip-gateway-with-motorola-mototrbo, radiopro-ip-gateway-with-motorola-apx-4500, radiopro-ip-gateway-with-kenwood-nexedge).
What a minimum system needs
A working RadioPro system needs at least one of each of these:
- one IP Gateway kit (S2-61815), which is the server, with one gateway for each control-station radio used for voice;
- one control-station radio for each voice channel or talk group used at the same time, with its interface cable;
- one client: Dispatch, Solo or Talk;
- Ethernet/IP connectivity (LAN, WAN or VPN) between them;
- a connection license for each Dispatch or Solo client (Solo and Talk seats are licensed on the gateway).
The kit contains the gateway with its power supply, a USB flash drive (S2-61971) carrying the RadioPro software, installation guides and licenses, and a 10 ft Cat 5 cable (89-10712). An optional 2RU x 15" rack shelf (S2-61548) holds the gateway and its radio side by side. Part numbers for cables, licenses and Dispatch modules are in radiopro-part-numbers-and-ordering. Because each gateway is its own server, there is no single point of failure across the fleet.
System limits
- 80 clients per gateway (Dispatch, Solo and Talk connections combined). This is the tested figure and the published specification. It is guidance rather than a hard cap: more than 80 clients can attach, but because the gateway passes all audio to every connected client, noticeable performance degradation typically begins somewhere around 100 to 120 clients.
- 70 gateways per Dispatch client, the multilink limit.
- The Solo and Talk seat license on the gateway sets how many simultaneous users are kept; connections beyond that number are dropped after 5 minutes.
- Because all clients on a gateway follow its one control-station radio, they all hear the radio's currently selected channel. Several independent channels at once need several gateways (radiopro-ip-gateway-overview).
Planning
- Each gateway needs a static IP address, subnet mask and default gateway from the IT administrator. The gateway must be given its network parameters with the ICU (IP Configuration Utility) before it is attached to an active network. See ip-networking-in-two-way-radio-systems.
- MOTOTRBO control-station radios connect to the gateway over their own independent IP network, so the gateway and radio use different subnets. See radiopro-system-planning-for-mototrbo.
- If clients will reach the gateway from a different network or across the Internet, the firewall or router must forward a port to it (below).
- Plan time synchronization (below).
- Record names, addresses and serial numbers in the system planner template.
Steps
- Program the control-station radio following the guide for its type.
- Connect the gateway to the radio with the interface cable. Do not connect the gateway to an IP network yet.
- Configure the gateway with ICU. Disable Wi-Fi on the configuring PC. Connect the gateway's RJ45 port directly to the PC, power up the gateway and the radio, run ICU and use Read Device, Auto Find (or Manual if the PC and gateway are separated by routers or switches, or if the address is known). - By default a gateway uses DHCP and, with no DHCP server, assigns itself a link-local 169.254.x.x address. A static address is required in production, and the guide says DHCP should not be selected without consulting CTI engineering.
- Fill in the ICU tabs, then use Gateway, Write Settings with the gateway administrator password. Remove the configuration cable.
- Connect the gateway to the LAN with a straight-through Cat 5 cable to a switch or router.
- Configure port forwarding if needed.
- Install and configure the clients: radiopro-dispatch-layout-gateways-and-licensing, radiopro-solo-virtual-radio, radiopro-talk-mobile-app.
ICU tabs
| Tab | What it holds |
|---|---|
| General | Gateway version, radio type, serial number, Gateway Name (change the factory default to something recognizable; it labels the radio controller in Dispatch and Talk), NTP server address or custom local time, firmware upgrade button |
| License Key | Export the license file to send to CTI Products when more user connections are bought, and import the upgraded file. The value is 1 to 80. |
| Client Accounts | User names and passwords for Solo and Talk clients, and the Dispatch password a Dispatch client needs to connect. The built-in administrator account cannot be renamed or deleted and its default password should be changed. |
| Network | IP address, subnet mask, default gateway, DNS server and TCP port. Do not use leading zeros in address fields. A default gateway is needed only if clients are on another network or the Internet. A DNS server is needed only if the NTP server was given as a host name. |
| Radio Aliases | Alias names for radio IDs, which appear in the contact lists of Solo and Talk clients |
| Radio-system-specific | GPS, polling and other settings that depend on the radio type, covered in the per-radio guides |
| Voice Recorder | RTP streaming (radiopro-ip-gateway-rtp-streaming-and-logging-recorders) |
ICU has no audio level, gain or volume setting, and the installation guide gives none: audio levels belong to the radio's own programming software and to the client. See audio-clipping for where they are set and how to find a stage that is overloading.
File, Export saves all ICU settings for a gateway to an .icu file, which is a backup in case the gateway has to be replaced; Import restores all or a subset.
Time synchronization
Accurate time prevents logging errors and operational glitches, especially with audio logging and GPS tracking. All gateways should carry the same time as the PC running the client. The best option is a time server: one on a LAN PC, one managed by the domain service, or a public NTP server. Enter it in the NTP Server field on the General tab. If no time server is available, a custom local time can be entered. See ntp-network-time-protocol.
Port forwarding
The default TCP port for both gateways and clients is 48222 (changeable on the ICU Network tab). If a client is on another subnet, such as a client using the Internet to reach a gateway behind a firewall, the IT administrator must forward a port in the firewall or router. The client's address entry is then the firewall's external address. If a different external port is used, the client entry includes it after a colon (address:port).
If several gateways are behind one firewall, each needs its own forwarding rule with a unique external port. See port-forwarding-and-remote-access and networking-tcp.
Firmware and licenses
- The General tab has an Upgrade Firmware button, and gateway installers are available from the RadioPro upgrade downloads page. See radiopro-system-upgrades.
- A gateway's packing list shows part number S2-61612 while its 120-day timed license is active.
- To convert a 120-day timed license to a non-expiring one, use ICU to export the license key from the gateway, name the file with the gateway serial number and the CTI sales order or customer name, and e-mail it to CTI support with the serial number in the subject line. Then import the updated file with the Import License Key button.
Compatibility
Version 9 gateways work with Dispatch 9.x (9.3.11 and later on Windows 10 or 11 Professional; 9.3.0 to 9.3.10 on Windows 10 Professional), and version 8 gateways work with Dispatch 8.x. The Solo client (versions 8 and 9) and the Talk mobile app work with either gateway version. Talk for Android needs Android 8.0 (API level 26) or later with Google Play, and Talk for iOS needs iOS 9.0 or later. Upgrade the gateways before the clients.
Source documents
This article summarizes the following published CTI Products manuals. They are the authoritative reference.
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.