Diagnostics and Logs
When troubleshooting Room integration, check the flow in this order: credential issuance, TiRTC TiRtcWhipConnect, connection result, audio uplink/downlink, and room signaling.
Common Issues
| Symptom | Diagnostic direction | Recommendation |
|---|---|---|
| Token request fails | Token service returns 401 or 403. | Check X-Tg-App-Id, Authorization, and device room permission. |
| TiRTC connect reports authentication failure | token is invalid, expired, or not used with the returned peer_id. | Request a new credential and confirm the device passes the delivered peer_id and token unchanged. |
| TiRTC connect is temporarily unavailable | The service is temporarily unavailable or the network has a transient issue. | Request a new credential and retry. If the issue continues, contact technical support with time, room_id, device_id, and request details. |
| Connection cannot complete | Network, NAT, or UDP connectivity issue. | Check device network and TiRTC SDK logs. |
| Joined but no audio | No uplink audio, codec mismatch, or playback does not handle downlink audio. | Verify sample rate, channel count, codec, and downlink playback buffer. |
| Participant list does not update | room_snapshot was not received, or command-channel handling failed. | Check whether command channel 0x2200 receives valid JSON-RPC notifications. Send get_room_snapshot if active state realignment is needed. |
| Microphone state does not update | set_mic_state was not sent, or participant_mic_state_changed was not handled. | Confirm the local microphone switch and speaking detection map to on, speaking, and off, and check whether other participants receive the state change notification. |
| State remains after leaving | Local resources were not fully released, or room state was not cleared. | Route active leave, disconnect, and timeout to one cleanup flow. |
Information to Collect
- Application ID, business
room_id, devicedevice_id, and incident time. - Redacted
peer_id. Do not provide the fulltoken. - Token service HTTP status and error response.
- Call time, return code, and error information from TiRTC
TiRtcWhipConnect. - TiRTC SDK logs for connection, audio, and command channel.
Log Redaction
Logs may keep diagnostic fields such as room_id, device_id, session_id, and error code. Do not log the full token, full application secret, or full URLs containing sensitive query values.