Request access
Sign inRequest access

Docs Start here

Getting started

From access request to your first call: connect LiveKit, add an endpoint and test both directions. Once your team is approved this takes about fifteen minutes.

1. Request access

RelayDock is in a limited pilot for LiveKit customers in the EU and the UK. Fill in the access request form with your work email, company and monthly call volume. We reply within one business day.

When your request is approved you get an invitation email. Open the link, choose a password and you land on the setup screen. New teams start with a 30-day trial with Pro limits; no card is needed.

2. Connect your LiveKit project

  1. In LiveKit Cloud, open Settings → SIP and copy the SIP address, for example abc123.eu.sip.livekit.cloud.
  2. Create an API key with SIP admin rights and copy the key and the secret.
  3. In RelayDock, open LiveKit project, fill in SIP address, API URL (it starts with wss:// or https://), API key and API secret, then choose Connect and verify.
  4. RelayDock checks the key right away, then places a test call with its own credentials to confirm that the SIP address belongs to this project. The state changes to Verified.

3. Add your first endpoint

An endpoint is one connection to your carrier or PBX. Open Endpoints → Add endpoint and choose the type:

Type When to use it
Registration A carrier number or PBX extension. RelayDock registers with a user name and password.
Trunk The carrier sends calls to your static IP, checked by IP or digest. Outbound calls work too.

Fill in the connection details; for a registration, a Provider template fills in the registrar, the transport and the carrier's addresses. Under LiveKit agent, enter the agent_name of the agent that should answer. When you create the endpoint, RelayDock sets up the inbound trunk and the dispatch rule in LiveKit for you.

Step-by-step instructions for your carrier: Telnyx or any SIP trunk or PBX.

4. Test both directions

Outbound: test call

Choose Test call on the endpoint. LiveKit dials out through RelayDock and your carrier, and the panel shows each step: LiveKit started the call, RelayDock verified the credentials, the other side answered, the call ended.

Inbound: listen for a call

In the same card choose Inbound, then Listen for a call and call your number from your phone within five minutes. The panel shows whether the call reached RelayDock and your agent. If it didn't, it tells you why: the carrier's IP isn't allowed, the digest user name doesn't match, or the carrier dialed a number the endpoint doesn't have.

5. Choose how audio flows

Under Advanced settings, each endpoint has an audio mode:

Mode What it does
Automatic Tries direct first; routes audio through RelayDock when it sees NAT. The default.
Always Relay Audio flows from the static IP; for carriers that restrict media IPs.
Direct only Audio never passes through RelayDock; calls behind NAT are rejected.

Minutes beyond your plan cost $0.0015 on Direct and $0.003 on Relay. See pricing.

Next steps

  • Automate setup with the RelayDock API.
  • Add notification emails under Settings → Notifications so registration and LiveKit alerts reach the right people.