IPSC3 can queue selected Motorola short data commands to a radio that is currently known through the roaming table. These commands are handled by the IPSC3 radio daemon outside the live voice path.
On the IPSC3 roaming dashboard, operator and admin users can click a radio ID to open radio actions.
| Action | Availability | Behaviour |
|---|---|---|
| Send SMS | Operator/admin, current roaming route | Queues a TMS message from the IPSC3 data radio ID to the selected radio. |
| Call Alert | Operator/admin, Motorola ARS active radio on an IPSC repeater route | Queues a Motorola call-alert short command. |
| Radio Disable | Operator/admin, Motorola ARS active radio on an IPSC repeater route | Queues a Motorola radio-disable short command. |
| Radio Re-enable | Operator/admin, Motorola ARS active radio on an IPSC repeater route | Queues a Motorola radio-enable short command. |
The dashboard re-validates the roaming route and user role at submit time. The row being visible in a browser is not sufficient authority to send a command.
Field captures show these commands travelling as short Motorola private data bursts over IPSC. The command body is carried in Motorola data frames rather than as normal DMR voice. IPSC3 currently emits the captured command family as three synthetic Motorola private-data frames:
The outbound frame must be internally consistent. During generation IPSC3 rewrites the source radio ID, destination radio ID, target timeslot, sequence values and RTP-style timing fields. It also recomputes the embedded Motorola CSBK CRC after address rewrite. In field testing, Motorola repeaters required the IPSC packet origin to be the configured Motorola master ID rather than the target repeater ID.
| Command | Status | Notes |
|---|---|---|
| Call Alert | Implemented / tested | Exposed to operator/admin users for Motorola ARS radios and useful as a non-destructive test command. |
| Message Alert | Implemented / diagnostic | Available in the daemon command sender but not exposed on the roaming dashboard. |
| Radio Disable | Implemented / restricted | Dashboard access is restricted to operator/admin users and active Motorola ARS radios. |
| Radio Enable | Implemented / restricted | Used to re-enable a radio after a successful disable command. |
The exact protocol pieces required to generate radio-disable and radio-enable commands are intentionally not published here. They are safety-sensitive and may be available to trusted network operators on request. This page documents the operational behaviour, guardrails and high-level transport shape only.
signal_requests and sent by the daemon worker.