Real-time Control/Payload Control/Speaker

Open Aircraft Two-Way Voice Channel

Open bidirectional voice channel for specified gateway SN (typical scenario: aircraft-mounted microphone capture + aircraft-mounted speaker playback; frontend connects via RTC). After server selects and initializes RTC provider (Agora / Volcano Engine / Twilio, etc.), dispatches channel access parameters (room number, Token, UID, etc.); frontend selects corresponding RTC SDK to connect by provider field.

post/openapi/v2.0/drc/api/v2/projects/{uuid}/voice-channels/{sn}

Request

  • Base URL
    https://41b04hdzmc.apifox.cn (the document declares no server; this is the origin it was published from)
  • URL
    https://41b04hdzmc.apifox.cn/openapi/v2.0/drc/api/v2/projects/{uuid}/voice-channels/{sn}
  • Auth
    none required

Path parameters

uuidstring required

Project UUID

snstring required

Gateway Device SN (Aircraft / Dock with Speaker)

Query parameters

providerstring

Specify RTC Provider (e.g. agora_rtc / volc_rtc). If omitted, server auto-selects per deployment configuration. Actual available values for on-premises deployment depend on site DRC configuration; client usually does not need to specify; server selects per device/deployment-side strategy

Headers

x-user-tokenstring required

User Login Session Token (client invocation credential for on-premises deployment)

X-Request-Idstring uuid

Client-Generated Request Trace ID (UUID v4 recommended), used for cross-service log correlation and troubleshooting

X-Project-Uuidstring required

Project UUID

Request body

object required

This API does not require request body content; recommended to pass empty object {}

Response

Operation Successful

codeinteger required

Business Status Code: 0=Success; non-zero=Error Code (see message for meaning)

messagestring

Error Description Message (Omitted on Success)

Changes

No recorded changes to this operation across all 1 revision of this API.