Why doesn't my RadioPro IP Gateway respond to ping even though RadioPro works?

Last updated:

A missing ping reply does not necessarily mean the Gateway is offline. RadioPro Gateway security settings can intentionally discard ICMP echo requests while normal client connections continue to work.

Test the service you actually need. Connect using a compatible RadioPro client or ICU. On a Windows PC, a direct-path test of the default client port can be made in PowerShell:

Test-NetConnection -ComputerName 192.168.1.50 -Port 48222

Replace the example address and port with your Gateway's configured values. A successful TCP test confirms port reachability, not user authentication or radio operation. For RadioPro Link, test using the service's assigned connection settings instead of assuming the direct-Gateway test applies.

CTI can enable additional diagnostics when needed; changing the normal ping policy is not required for client operation.

Documentation

Back to RadioPro IP Gateway