# Channels & Calls

A Channel stores the connection and routing configuration for an Assistant. Reuse it for successive calls. An individual call is a live conversation, recorded as an [Exchange](/docs/exchanges-and-conversation-lifecycle).

## Choose a Channel type

| Channel | Connects | Setup |
| --- | --- | --- |
| SIP | Callers using your phone system or SIP provider | Configure permitted destination numbers or source addresses, and route SIP traffic to Reecall |
| WebRTC | Callers in a browser or application | Create a Channel, request a connection token on your backend, and connect with a LiveKit client |

Each Channel points to one Assistant through `assistantId`. An Assistant can have one SIP Channel and one WebRTC Channel. A second Channel of the same type for that Assistant is rejected.

## Phone calls through SIP

Creating a SIP Channel provisions its inbound trunk and routing configuration. Configure at least one non-empty whitelist of destination phone numbers or permitted source IP addresses. Your phone system or SIP provider must then send calls to the provisioned endpoint.

The Channel connects an existing telephony setup to the Assistant. Creating it does not purchase a phone number or configure your provider for you.

See the [SIP Channel guide](/docs/sip-channel) for routing and whitelist configuration.

## Browser and app calls through WebRTC

For each new conversation, your backend sends `POST /calls/{channelId}` using a Reecall API key. The response contains a LiveKit WebSocket URL, `wsUrl`, and a room-scoped connection `token` with a one-hour lifetime.

The browser connects to LiveKit with these values, publishes microphone audio, and plays the Assistant's audio. Requesting a token prepares the connection; the browser still needs to join and enable its microphone.

:::warning{title="Keep the Reecall API key on your backend"}

Pass only `wsUrl` and the connection `token` to the browser. A LiveKit token grants access to the call's room; it does not replace your Reecall API key for managing resources.

:::

Use the [Quickstart](/docs/quickstart) for a working browser example, or the [WebRTC Channel guide](/docs/webrtc-channel) for integration details.

## Keep resource IDs distinct

| ID | Identifies | Used for |
| --- | --- | --- |
| `assistantId` | The Assistant configuration | Assigning an Assistant to a Channel |
| `channelId` | The reusable connection configuration | Requesting a WebRTC connection token |
| `exchangeId` | A conversation record | Reading the transcript and results for one call |

The Calls API returns connection credentials. It does not return an Exchange ID. Read conversation records through the Data API after the Assistant starts handling the call.

## Next steps

- [Quickstart](/docs/quickstart) creates an Assistant and a WebRTC Channel.
- [Connecting to an Assistant](/docs/connecting-to-an-assistant) covers Channel configuration requirements.
- [Exchanges & Conversation Lifecycle](/docs/exchanges-and-conversation-lifecycle) explains what a call records.
