Required ICE Gateway Data
The following required deployment data must be collected before attempting to run an ICE Gateway. Obtain and record this data before continuing.
Required Gateway Deployment Data for All Gateway Types
Data | Source |
<nic> | Enter the name of the Gateway Network Interface used by the radio system. |
<nic_ip> | IP address if the network interface connection used by the ICE Gateway requires an IP address. |
<gateway_type> | Enter dfsig, issig, or telephony depending on what type of ICE Gateway you are deploying. |
<api_key> | Enter the ICE API key from ICE Desktop > Settings > License > API Key. |
<server_address> | Enter the URL of the ICE Server that the Gateway will connect with. |
<coast> | Refer to External Server Coasting. |
<group> | Optionally enter the three character Server Group ID specifying the Group that this Gateway will belong to. The server group ID can be determined from the ICE Desktop Client in Settings > Radio Interoperability > DFSI or ISSI. For Telephony, or if you have no Group preference, leave this setting as default. |
<version> | Enter the current release version: 3.6.5:8825. |
Required For DFSI and ISSI Gateways Only | |
<license_dongle> | This is the license dongle address as determined in a previous step (DFSI and ISSI Gateways only). |
<radio-system-id> | For ISSI only, your Radio System ID is generated by the ICE Server and available to admins on Desktop at Settings > Radio Interoperability > P25 Interoperability > ISSI > Radio Systems tab > ICE Radio System ID. |
Required For Telephony Gateways Only | |
<tls_enabled> | Set to Y if TLS is enabled, else set to N. Note that if this value is set to N, then the next two values (cert and private key path) may be omitted as they are not used. |
<tls_cert_file_path> | Path to the location of the certificate .pem file. |
<tls_private_key_file_path> | Path to the location of the certificate key .pem file. |