Room Docs

Room provides multi-party real-time audio rooms for IoT devices on the Tange platform. Your application server requests short-lived room credentials for a device. The device then calls the TiRTC TiRtcWhipConnect API to join the target room. The Tange platform handles credential verification, room sessions, audio uplink processing, and one downlink audio stream.

What You Can Build

• Add multi-party voice rooms to walkie-talkies, companion devices, meeting terminals, inspection devices, and other hardware.
• Let devices handle one downlink audio stream, reducing playback and decoding complexity in multi-party audio scenarios.
• Use the TiRTC command channel to synchronize participant lists, joins, leaves, and room close events.

Start Here

1. Overall Flow: understand the interaction between your application server, device, and the Tange platform.
2. Server Integration: request peer_id and token for the device.
3. Device Integration: call TiRTC TiRtcWhipConnect, send audio, receive downlink audio, and handle commands.
4. Server API: review how the application server requests peer_id and token.
5. Room Signaling: implement the JSON-RPC 2.0 room signaling protocol.

Roles

Role	Responsibility
Application server	Holds application secrets, checks business permissions, requests room credentials, and securely delivers them to devices.
Device	Uses short-lived credentials to connect, exchange audio, and handle room signaling.
Tange platform	Verifies credentials, manages room sessions, and handles audio uplink, one downlink audio stream, and room event delivery.

Prerequisites

• You have created a Tange platform application and obtained the server-side application identifier and secret.
• Your device has integrated the TiRTC SDK and can call TiRTC TiRtcWhipConnect, send audio frames, and exchange command messages.
• You have defined how your business room_id and device device_id are generated.
• Your application server can check room permissions and deliver short-lived credentials to devices securely.