Using Push-to-Talk

Use Oracle Radio to request the floor on a joined channel, transmit audio, and use available background talk controls.

Use the Radio app for interactive talk controls or the WebSocket API for a client's live audio sequence. REST can return a talk-status snapshot but doesn't replace the live transmission sequence.

Review the voice permissions for requesting or releasing the floor and transmitting audio. Priority Talk additionally requires radio.talk.priority.high. REST talk-status queries instead use channel permissions. In either case, verify access to the target channel.

Transmitting with Oracle Radio

Follow the channel steps to join and listen to the intended channel, and allow the browser to use your microphone.

You can listen to multiple channels, but push-to-talk sends voice to one transmit channel. Opening another workspace does not change that target. Verify the target again after leaving a channel or restoring the connection.
Only one user holds the floor on a channel at a time. Radio represents that temporary floor-control grant with a talk token. An Identity Domain access token and a talk token are different credentials and serve different purposes.
Priority Talk lets an authorized user request a higher-priority transmission on the current channel and interrupt a lower-priority speaker. Ask a Radio administrator to enable the required access listed above if your role needs Priority Talk.
1. In Radio, open the channel list and verify that you are listening to the intended joined channel. Use Transmit to select it, and check the displayed transmit channel.
2. Check Talk mode under Settings, in Audio. If you prefer the keyboard, also check your talk key in Hotkey, then close Settings.
  The default mode is Push to talk and the default shortcut is Shift+T. Use a talk key different from your channel keys. Shift plus a channel key only selects a joined, listening transmit channel; it doesn't start speaking. See talk settings.
3. When the channel is Connected, request the floor using your selected mode:
  In Push to talk mode, press and hold Hold to talk or Shift and your talk key.
  In Tap to talk mode, select Tap to talk or press Shift and your talk key once.
  When the channel is Busy, authorized Priority Talk users can instead use Hold to interrupt and talk or Tap to interrupt and talk, depending on the mode. The same talk shortcut applies. If no priority control is available, wait until the current transmission ends. A Priority Talk request doesn't guarantee that you receive the floor.
4. Wait for Transmitting before speaking.
  Requesting means that Radio is still requesting the floor. In Push to talk mode, keep holding the button or shortcut while speaking. In Tap to talk mode, releasing the button or key doesn't stop transmission. Radio keyboard shortcuts don't start talk or select channels while focus is inside a form or dialog; close the dialog and return focus to the Radio workspace before using them.
5. Stop transmitting when you finish.
  In Push to talk mode, release the button or talk key.
  In Tap to talk mode, select Tap to stop or press Shift and your talk key again.
6. Check the channel state before requesting the floor again.
  If Radio shows Busy, another user holds the floor. Wait until the transmission ends unless you need to use an available Priority Talk control.
Radio ends the transmission and releases your talk token. Stopping transmission doesn't leave the channel or stop listening. To stop listening and remove your saved membership, select Leave. See channel actions. If the floor request is denied, Radio doesn't transmit your audio. For an unavailable Priority Talk control, see talk guidance.
Sign in, go on duty, allow microphone access, and follow the Android channels steps. Verify that the intended active channel is connected.

The on-screen button defaults to hold-to-talk. An app upgrade switches existing installations to hold mode once, even if you previously used tap-to-toggle. This is separate from the Browser App and iPhone settings.
1. Check your screen PTT settings and the active channel before speaking.
2. In the default hold mode, press and hold Hold to talk. If Tap to toggle talking is enabled, select Tap to talk once.
3. Wait for the app to indicate that it is transmitting, then speak. In hold mode, keep the button pressed. Releasing while authorization is pending cancels the request.
4. In hold mode, release the button to stop. In tap-to-toggle mode, select Tap to stop. If the request is still pending, use Tap to cancel.
5. Verify that transmission has ended before changing channels or putting the device away.
Stopping transmission does not leave the channel. For an unavailable control or unexpected talk mode, see Android PTT help.
Sign in, go on duty, allow microphone access, and follow the iOS channel steps. Verify that the intended active channel is connected.

The on-screen button defaults to hold-to-talk. An app upgrade switches existing installations to hold mode once, even if you previously used tap-to-toggle. To change the mode, use iOS screen PTT settings.
1. Check that Enable is on under Screen PTT Button, and verify the active channel before speaking.
2. In the default hold mode, press and hold Hold to talk. If Tap to toggle talking is enabled, select Tap to talk once.
3. Wait for Transmitting, then speak. In hold mode, keep the button pressed. Releasing while the floor request is pending cancels the request.
4. In hold mode, release the button to stop. In tap-to-toggle mode, select Tap to stop. If the request is still pending, use Tap to cancel. Lifting your finger after the first tap doesn't stop transmission.
5. Verify that transmission has ended before changing channels or putting the device away.
Stopping transmission doesn't leave the channel. For an unavailable button or unexpected mode, see iOS screen PTT help. For Dynamic Island, use the separate background talk steps.
Review the audio prerequisites. Authenticate the connection and subscribe to an authorized channel.
1. Send REQUEST_TALK and wait for GRANTED.
  Don't transmit while the request is queued or denied.
2. Use the granted talk token to start transmission, then send audio.
3. When finished, end transmission and release the talk floor.
The transmission ends without removing the channel subscription. Follow the full audio sequence for interruption, expiration, error, and disconnect handling.
Use getChannelStatus to inspect the current talk-floor state. The result is a snapshot, not a talk grant. To request the floor and transmit live audio, use the Radio app or WebSocket API tab.

Talking from iPhone Dynamic Island

On an iPhone with Dynamic Island, Oracle Radio can display a blue system Push-to-Talk indicator after you enable Background Reception. The lock-screen control shows the active channel and provides Leave and Talk.

In the Oracle Radio app, verify that you are signed in, on duty, and connected to the intended channel.
Lock the iPhone, then select the blue Radio indicator in Dynamic Island to open the lock-screen control.
Verify the displayed channel. Press and hold Talk while speaking, as you would hold the talk control in the app, then release it when you finish.

The Dynamic Island control uses press-and-hold behavior. It doesn't change the Browser App's Talk mode preference. If the indicator or lock-screen control isn't available, follow the background PTT guidance.

Starting a Mobile Critical Alert

Use Critical Alert for urgent voice communication on the selected channel. The app also attempts one location update when available. This isn't the critical-text option in the message composer, and it doesn't broadcast to every channel.

Recipients must be signed in, on duty, and have notifications enabled for mobile receipt in the foreground, background, or while the device is locked. Review the receiving prerequisites; this isn't a delivery guarantee.

After transmission starts, Critical Alert captures at least 10 seconds of audio on Android and iOS. If you try to finish sooner, the app keeps the alert active and shows the remaining capture time.

Review the voice permissions and channel access for transmission. Location reporting requires location permission and device location access. A Critical Alert doesn't bypass either API's authorization checks.

1. Open Radio, verify the active channel and connection, and allow microphone access when needed.
2. Press and hold Hold for Critical Alert until the action starts.
3. Wait for the app to indicate that it is transmitting before speaking. To finish, use the displayed transmission controls. If the app shows remaining capture time, wait for the 10-second minimum to complete, then follow the controls to finish.
The app attempts a location update only if location access was already allowed. It doesn't interrupt the alert to request location permission. Missing location doesn't establish that the voice request failed.
1. Open Radio and verify the active channel and connection. The app must be able to transmit, not in receive-only mode or already transmitting.
2. Select Critical Alert, then select Start critical alert in the confirmation.
3. Wait for the app to indicate that it is transmitting before speaking. To finish, use the displayed transmission controls. If the app shows remaining capture time, wait for the 10-second minimum to complete, then follow the controls to finish.
The app attempts one eligible location update. Location availability and a successful talk-floor request are separate; don't assume either succeeded solely because you selected the control.

How Critical Alert Uses Oracle Radio APIs

The app combines a priority voice request with a separate location update. There isn't one combined Critical Alert operation or an atomic guarantee that both actions succeed. For unavailable controls or missing location, see alert help.

The voice path uses REQUEST_TALK with a priority, waits for a grant, then follows the audio sequence. A higher priority can preempt a lower-priority speaker, but doesn't guarantee a grant. TEXT_MESSAGE with critical: true sends critical text, not voice or location.
The separate updateLocation request reports the authenticated user's position when available and authorized. It doesn't transmit audio, grant the talk floor, or prove that every recipient received an alert.

Talking from Other Oracle Radio Pages

In the browser app, use the floating Radio control to talk while viewing Locations or an available administration page, such as Channels, Users, Groups, Devices, or Application settings. It isn't a control for unrelated browser tabs or other desktop applications.

You need the same voice permissions and channel access as in the Radio workspace. Your administrator must allow the control, and you must be listening to a channel.

In Radio, join and listen to the intended channel. Follow the channel steps.
Open Settings, select Appearance, and enable Show Radio control in other applications. Select Done.
Open a supported page. On compact or touch-enabled browsers, the control initially appears as a launcher. Select Show Radio control to open it. If the control is collapsed, select Expand Radio control.
In the control's Transmit list, select the intended listening channel and verify the displayed target.
Use the talk control for your selected talk mode. In Push to talk mode, hold Hold to talk and release it to stop. In Tap to talk mode, select Tap to talk, then Tap to stop when finished. Wait for Transmitting before speaking. Priority Talk remains subject to the same authorization and floor availability as in the Radio workspace.
To reposition the control, drag its move handle or focus that handle and use the arrow keys. Use Reset Radio control position to restore its position.

Stop transmitting before collapsing or hiding the control. In Tap to talk mode, use Tap to stop; releasing the button isn't sufficient. Hiding the control isn't a substitute for ending a call or signing out. If it doesn't appear, follow control guidance.