How to Troubleshoot MOTOTRBO Radio Delivery Failures

Symptoms of Radio Delivery Failure

Alarms fire in SeQent but radios stay silent. Text messages arrive but text-to-speech does not trigger. Some radio users receive alarms while others on the same talk group do not. Delivery is intermittent without a clear pattern.

Common Root Causes

Radio Link Configuration Error. The FPLNKTDIRECT (FirstPAGE Link for TRBODirect) is misconfigured. The link does not connect to a “repeater IP.” It talks to a Donor Radio (IP, TMS UDP Port, ID, CAI Group Network) and to DDMS (Host, Port Watcher). Config errors typically mean a mismatch between the Link’s TRBODirect tab and the Motorola side: donor radio IP, TMS UDP Port matching MNIS, CAI Group Network matching MNIS, or DDMS host reachability.

Talk Group Mismatch. The escalation rule routes to talk group 1, but the radio user is subscribed to talk group 2.

Network Path Blocked. Firewall rules between the SeQent server and the MOTOTRBO repeater block the connection port.

Diagnostic Steps

Step 1: Verify Radio Link Status. On the FPLNKTDIRECT Admin, right-click the DDMS/Donor connection in the status bar to view DDMS/Donor Status. Both must show Connected. Per-SUID Presence, queue size, and last text message timestamp are visible in the Radio Status and Talk Group Status folders in the tree view (sections 4.1 and 4.2, pp.26-28). There is no “Gateway Status” page.

Step 2: Send a Test Message. There is no “Send Test Alert” function on the Link. The Link is the recipient of SNPP messages from FirstPAGE Server, not an originator. Real test path: open FirstPAGE Administrator, send a test message to a Destination routed through the FPLNKTDIRECT Provider, then verify it lands by checking Radio Status (queue grows then drains) and the Server Log on the Link side.

Step 3: Check Radio Link Configuration. Verify the Donor Radio settings. The default ports are: SNPP listener 444 (FPS to Link), Server 8160 (Admin to Server), TMS UDP 4007 (Link to Donor Radio, must match MNIS), DDMS Port Watcher 3000., and authentication key match the MOTOTRBO repeater admin panel exactly.

Step 4: Verify Radio Configuration. In the MOTOTRBO repeater admin console, check that the user is assigned to the intended talk group, the talk group is configured as “data capable,” and text messaging is enabled.

Step 5: Review Delivery Logs. Open View > View Logs > Server Log on the FPLNKTDIRECT Admin. Real error patterns to look for: 554 Failed: PN Absent for SUID ##### (radio not present per DDMS), 554 Failed: Text message greater than 138 characters (message too long), Invalid SUID: <#####> (TGID sent but not configured as Talk Group), 780 Failed: Stale Message TTL Expired (DDMS/MNIS unreachable too long). There is no “Notification Delivery logs” page in the product. Look for “sent to radio gateway” status. If “sent but no ACK from repeater,” the repeater is not acknowledging. If “failed to send,” the gateway could not reach the repeater.

Step 6: Test on Known-Good Radio. Send a test alert to a different radio user on the same talk group. If that radio receives it, the issue is specific to the original user’s radio configuration.

When to Engage Motorola vs. SeQent Support

SeQent issues: gateway offline, test message fails, repeater rejects connection. Motorola issues: radio firmware incompatibility, repeater configuration, talk group settings. Send a test message from the MOTOTRBO repeater admin console directly to determine the boundary.