LCP Prerequisites

SmartPTT§

Newest available version is highly recommended.

Voice Dispatch in Enterprise§

For voice dispatch in SmartPTT Enterprise (using hybrid voice interface), read the dedicated article.

MOTOTRBO§

Repeaters must have NAI Voice and NAI Data licenses.
Newest MOTOTRBO release is highly recommended.

Cybersecurity§

All interfaces between solution components are open (not encrypted). If required, protect them using third-party VPN tools.
Main repeaters may send encrypted traffic to SmartPTT server over the open IP channel.
Main repeaters may send encrypted traffic to MNIS over the open IP channel.

Bandwidth§

Explained in the “Server to MOTOTRBO” section of Networking Requirements.

Radio ID (ISSI)§

Ensure that you have the following Radio ID (ISSI) unique:

Every subscriber radio,
SmartPTT Server.

If you are using SmartPTT PLUS, you must also assign unique ISSI to dispatchers.

If you wish to have voice dispatch in SmartPTT Enterprise, assign unique and/or repeated ISSI according to one of strategies explained in “TX Radios for Individual Calls”.

Group ID§

Basically, SmartPTT does not have limitations to group ID setup. However, if you wish to have voice dispatch solution based on SmartPTT, you will have limitations due to hybrid voice interface.

Repeater Radio ID§

The parameter (also know as “peer ID”) must be unique for the following entities:

LCP repeaters (including main repeater),
MNIS,
SmartPTT main, additional, and backup servers.

Secure Keys§

For voice encryption/decryption, SmartPTT must have secure key values added to its configuration.

TX Radios§

SMARTPTT ENTERPRISE ONLY

This section is applicable to SmartPTT Enterprise only. If you are using SmartPTT PLUS, please skip it.

Number of TX radios you need is determined by number of sites and number of concurrent voice calls you need per every site.