StartMonitor
| Frame
|
{{{frame}}}, field {{{field}}}
|
| Member
|
{{{member}}}
|
| Direction
|
Client → server
|
| Session
|
Control
|
| Roles
|
|
| Permission
|
Authenticated; own transmitters only (moderators: monitor.any)
|
| Answered by
|
MonitorBlock stream, ended by MonitorEnd
|
| Answers
|
|
| Defined in
|
|
StartMonitor asks the server to stream the signal of one of the account's own transmitters back to the client, so that an operator can hear what they are sending. The stream is the transmitter's complex baseband after the modulator and amplifier model, before the antenna and propagation.
Layout
| Field |
Type |
Description
|
packetId |
u8 |
Always 6.
|
stationUuid |
UTF |
UUID of the transmitter, as listed in StationList.
|
Rules
- On a control session, the transmitter must belong to the same account as the control session, on any connection. An anonymous control session cannot monitor anything.
- Authenticated control sessions require a
control ticket, which the account service issues only to credentials with catalog.publish.
- On a moderation session, any transmitter may be monitored with
monitor.any.
- If monitoring is not possible, the server answers with MonitorEnd and a reason.
- Not a heavy request. The stream starts with the newest samples; there is no backlog.
