Help · Operators

olcRTC carriers

olcRTC reaches users through public video-call services: Telemost (Yandex), WB Stream, MTS Link, SaluteJazz (Sber) and VK Calls. Telemost and WB Stream rooms are created on your own accounts; SaluteJazz needs none; VK Calls runs on calls you create in the VK app, one call per exit. Which of them are open changes with the services themselves.

Open in the app All help topics
example
Telemost (Yandex)  → your Yandex 360 for Business account
WB Stream          → your own dedicated stream.wb.ru account
SaluteJazz (Sber)  → no account
VK Calls           → one call per exit, created in the VK app

olcRTC hides a user's traffic inside a video call. The call runs on a public service — a carrier — and your origin sits in a room on that service. A node can offer up to four carriers. Users see one line per carrier in their Ghostlane list (plain, then · WB, then · SJ, then · VK) and connect with whichever one their network lets through.

What is open now

The platform opens each carrier exit by exit. At the moment SaluteJazz and VK Calls are open on every exit, MTS Link runs on ProofKit's own exits, and Telemost and WB Stream are not offered: Telemost's service cuts the streams of a call to a trickle, and WB Stream has closed to outside users. A carrier that is not open is not listed in a node's Settings.

The carriers

  • Telemost (Yandex). Needs your own Yandex account, and it must be a Yandex 360 for Business domain account: Telemost's API only serves business accounts. Connect it under olcRTC carriers on your dashboard: Connect opens Yandex in a new tab, you approve access there, and paste the confirmation code it shows. Sign in to that tab with your business account first: Yandex authorizes whichever account the tab is signed in to, and a personal Yandex account connects but is refused at the first room.
  • WB Stream (Wildberries). Needs your own stream.wb.ru account. Log in at stream.wb.ru, open DevTools → Network, filter by "api", and copy the value after Authorization: Bearer from any API request into the WB Stream token field. Use a dedicated account, not your personal one: anyone who has a WB room's code can read its organiser's e-mail, and every user of your WB line has that code. Clear or replace the e-mail in that account's Stream profile. The platform opens WB Stream node by node, so its row appears under olcRTC carriers once one of your nodes has it.
  • SaluteJazz (Sber). Needs no account: each room is an anonymous call.
  • VK Calls. Needs calls you create yourself, one call per exit: in the VK app, start a call ("Create call") for each node you tick VK Calls on, and paste the join links (https://vk.ru/call/join/…) under olcRTC carriers, a link per line. VK has no API an app could create rooms with, so each link is its call's whole credential, and the dashboard shows only its last characters. Each node is given a call of its own, and its users stay on that node's own key: a call shared by several nodes slows down for everyone in it. A node with no call left waits for one, and the carriers box says how many wait; add a link for each. Saving the list replaces the saved one, so paste every link you keep. Disconnecting forgets every link; create fresh calls before connecting again.

Whose account a room uses

Every Telemost and WB Stream room of your node is created and opened with your account, never anyone else's — there is no shared account to fall back on. The code, the refresh token and the WB token are kept only on ProofKit's isolated provisioning server; the dashboard shows their status and never shows them back.

Choosing carriers per node

In a node's Settings, with olcRTC switched on, tick the carriers that node should offer. The list holds the carriers the platform has opened for that node, each carrier node by node. Telemost and WB Stream stay greyed out until you connect the matching account under olcRTC carriers; SaluteJazz needs no account; VK Calls is listed once you have added call links, and a node that ticks it is given one of them. A node you switched to olcRTC before connecting any account gets every carrier your new account opens, as soon as you connect it. A carrier the platform has not opened for a node is not listed for it.

When an account stops working

If Yandex or WB Stream refuses your account later (a revoked token, a banned account, or for Telemost a Yandex account that is not a Yandex 360 for Business domain account), the carrier shows error with the reason. Rooms that are already live keep serving, but no new room is created on that account until you reconnect it. Disconnecting an account withdraws its carrier from all your nodes at once; their rooms are kept, and reconnecting brings the carrier back on the nodes that still have it ticked.

Billing

Every carrier is billed the same: the same user key, the same per-GB price, the same earnings for you. A user who switches carrier is still one user on one bill.