SmartConnect
Configuration Guide
This guide explains how to configure SmartConnect on supported Motorola MXP600, MXP660 and MXM600 radios for use with TetraPack
The instructions assume the user has already purchased the "SmartConnect" feature license and has compatible firmware installed on the radio.
Requirements
Before configuring SmartConnect, ensure the following prerequisites are met.
Radio Requirements
The radio must have:
-
SmartConnect feature licensed
-
Firmware MR2025.2b or newer
-
Working Wi-Fi capability
- MS Authentication DISABLED
Software Requirements
Configuration requires:
-
Motorola Tetra CPS Plus 8.4 or newer
Network Requirements
The radio must have access to the internet via Wi-Fi and be able to reach TetraPack Core.
Endpoint
The TetraPack endpoint is:
REMEMBER - If your Hotspot Password contains Special Characters, these need to be entered into CPS URL Encoded.
For Example.
P@ssw0rd! = P%40ssw0rd%21
Radio Configuration (CPS)
Open the radio configuration in Tetra CPS Plus 8.4.
Step 1 – Configure Wi-Fi
Create a new Wi-Fi profile and configure:
-
SSID
-
Security mode
-
Password
Write the configuration to the radio.
Step 2 – Configure SmartConnect
Within CPS, configure the SmartConnect connection parameters.
Enter the TetraPack endpoint:
REMEMBER - If your Hotspot Password contains Special Characters, these need to be entered into CPS URL Encoded.
For Example.
P@ssw0rd! = P%40ssw0rd%21
Write the configuration to the radio.
Troubleshooting
If the radio fails to connect to the gateway, the most common cause is a cached certificate or invalid SmartConnect Certificate.
Reset the SmartConnect certificates using the radio Test Mode.
Enter Test Mode
On the radio keypad enter:
This opens the Test Mode menu.
Delete SmartConnect Enrollment Certificates
Delete the stored certificate.
After deleting the certificate:
-
Restart the radio
-
Reconnect to Wi-Fi
-
Attempt the SmartConnect connection again
Additional Notes
-
Radios must have a valid SmartConnect feature license installed.
-
Firmware older than MR2025.2b may not support the required connection methods.
-
Ensure outbound TCP connectivity to the gateway port is allowed.
No comments to display
No comments to display