Skip to content
Documentation

RTC limits and troubleshooting

RTC must be enabled on the active subscription. The console’s plan control and Usage page expose the allowances applicable to the workspace. Do not assume that all subscriptions with the same marketing name have identical limits. Plans and billing lists the trial, tiers and packs, and GET /v1/subscription (signed-in console session) returns every allowance.

Feature codeControls
max-projectsProject creation allowance
max-participantsAllowed participant capacity per room
participant-minutesParticipant-time allowance
recording-jobsRecording-job allowance

A server key uses its owning workspace’s access and allowances, not a separate subscription for the person holding the key. Increasing a room’s requested capacity cannot override the plan or available media capacity.

The activity totals show completed connection history. They are not live occupancy or a billing-period invoice. Usage and billing updates are asynchronous. Check central Billing for subscription details and invoices.

  • Room capacity is a whole number of at least two, within the host workspace’s participant allowance. Available media capacity is checked separately from the plan. A temporary capacity refusal does not mean a plan upgrade is needed.
  • Lists are paged with ?limit and ?cursor (see the API conventions) and have no server-side search. Console search only searches the loaded list.
  • Requests are rate limited per IP address, API key and organization.
  • Room rename, reopen, and deletion are not currently supported customer methods.
  • General mutation idempotency keys and bulk export APIs are not available.
  • Use the supported Web SDK distribution. Python/Node.js server SDKs and stack-specific guides are coming soon, not installable releases.
  • Recordings contain individual tracks, not a composed video. See recording constraints.
  • There is no general guarantee of seamless reconnect, unlimited rooms, infinite retention, or specific service uptime in these guides.

Check the active CHAMPREP profile, then confirm that RTC is included and enabled for that profile’s subscription. A newly created CHAMPREP account does not automatically have access. Try signing in again if the session expired. If the plan appears correct, contact support with the time and displayed error.

Check the error code (X-Error-Code), key expiry/revocation, required scope, project selection, resource state, and plan allowance. Copy UUIDs from the console or API rather than using names. Unknown JSON properties are rejected. Do not retry an authorization error repeatedly or add unrelated scopes.

A room connects but I cannot hear or see anyone

Section titled “A room connects but I cannot hear or see anyone”
  • Confirm that at least one participant is publishing and not muted.
  • Check browser and operating-system microphone/camera permissions and the selected physical devices.
  • A receive-only token cannot publish. Your application should not offer that user a publish control.
  • In a custom client, attach both audio and video tracks and handle browser autoplay restrictions with a user gesture.
  • A connected signaling state alone does not prove media is flowing. Test with two authorized participants on different devices or networks.

Try Low bandwidth receive mode and consider audio-only publishing. Check whether the network allows the signaling and relay services returned in the credential response. Use a different network to distinguish a local firewall issue from a service problem; do not disable security controls indiscriminately.

Your join endpoint must mint fresh credentials on reconnect. Reusing an expired or consumed token fails. The SDK’s retries are bounded; show the failure and offer a deliberate rejoin after checking room state and access.

Refresh the list and check the job status. Only ready tracks are downloadable. Start recording after the desired participants publish; late-starting tracks are not automatically included. A stop response means finalization was requested, not completed. Request a new download URL if the previous one expired.

For failed jobs, preserve the recording ID and timestamp for support. Do not repeatedly create new jobs without checking whether an earlier one is active.

Verify that your receiver accepts HTTPS POST on port 443 without redirecting and that the endpoint is enabled and subscribed to the event type. Send a test event and read the delivery log, then check the secret, the key for the signature scheme, exact raw-body verification and clock skew. Allow duplicate events without repeating their side effects. See webhook troubleshooting.

Use the CHAMPREP contact page. Include the timestamp and timezone, affected operation, browser/device, resource identifier where appropriate, the X-Request-Id of the failing request, and a redacted error code or HTTP status. Never include passwords, API keys, participant tokens, download URLs, signing secrets, or private media.