Oracle Cloud Infrastructure Documentation

Oracle Radio WebSocket Session Operations

Authenticate a bearer-token connection, check an established Radio WebSocket connection, and get its current identity and state.

Use AUTH to establish or renew a bearer-token session after the connection opens. PING is also available before authentication. Other session and Radio operations require an authenticated connection.

Report Mobile Audio Readiness

For a supported mobile client, audio readiness means the registered installation can receive and play audio without another native push-to-talk activation. An open WebSocket, PONG, or device heartbeat does not establish audio readiness. Readiness does not grant a talk token or replace channel permissions.

  1. Open the connection with the registered installation's X-Oracle-Radio-Device-Id, send AUTH, and wait for AUTH_SUCCESS. A connection without a registered device binding cannot report audio readiness.
  2. Read the optional audioReadiness object in AUTH_SUCCESS. When present, renewalIntervalSeconds gives the reporting interval and expirySeconds gives the readiness lifetime after a report. Use the returned values rather than hard-coding an interval.
  3. Only when the audio path is ready, send this JSON text message: 
    {
  "type": "AUDIO_READINESS",
  "ready": true
}

    The response is AUDIO_READINESS_ACK. A current ready report receives a server-calculated expiresAt timestamp. For example, the following illustrates the response shape, not a fixed expiry:

    {
  "type": "AUDIO_READINESS_ACK",
  "expiresAt": "2026-09-21T14:01:00Z"
}
  4. Repeat ready: true at the advertised renewal interval while audio remains ready. Process each acknowledgment; readiness expires if it is not renewed.
  5. When audio can no longer be received, send {"type":"AUDIO_READINESS","ready":false} if the connection and application can still send. Its acknowledgment omits expiresAt.

Readiness is connection-owned. A new or replacement connection starts not ready; disconnection clears its readiness. After reconnecting, authenticate, restore required live subscriptions, and report readiness again only when the audio path is ready. Readiness does not promise notification delivery or replay of audio missed during a disconnection.

For a rejected report or missing audio, see readiness help.