A SIP URI handles inbound calls into an agent (something dials the agent). If you want to give an agent a real phone number on the public network instead, see Import a phone number from Twilio.
Anatomy of the SIP URI
Every agent’s SIP URI has the same shape:- The host
1mq55afrqof.sip.livekit.cloudis shared by all Verbeo accounts. - The user part (e.g.
a1b2c3d4e5f67890abcdef1234567890) is unique to one agent and is what selects which agent answers.
Where to find your SIP URI
1
Open the agent
In the Verbeo dashboard, go to Agents in the left sidebar and click the agent you want to connect.
2
Open the SIP Configuration section
In the agent editor, expand the SIP Configuration panel.
3
Copy the SIP URI
Click the copy icon next to the SIP URI field. It looks like:This is the value you paste into your softphone, PBX, or trunk.
Connect a system to your agent
Use the fullsip_uri as the destination. The exact steps depend on what’s placing the call.
- Softphone
- PBX / SIP trunk
- Twilio
Any SIP softphone (Zoiper, Linphone, MicroSIP, etc.) can dial the agent directly.
- Add a SIP account with Host / Domain =
1mq55afrqof.sip.livekit.cloud. A username/password is not required — registration will show as failed, which is expected and fine. - Set the transport (see Transport below).
- Dial the full URI:
Transport
Verbeo’s SIP host accepts TLS (recommended), as well as TCP and UDP.Use TLS when your client supports it — it encrypts the call setup. Some free softphone tiers gate TLS behind a paid plan; in that case use TCP, or place the call through a service that handles TLS for you (such as the Twilio bridge above).
Test your SIP URI
1
Copy the agent's SIP URI
Grab it from the agent’s SIP Configuration panel (or the API).
2
Place a call
Dial the URI from a softphone or your PBX/trunk. The agent should pick up and start the conversation.
3
Confirm in Call History
Open Call History in the dashboard. You’ll see a new Inbound call to the agent’s SIP URI with status Completed and the duration of your test.
Keep your SIP URI secure
The SIP URI is open by design (so any carrier can reach it without credentials), and the unguessable agent ID is what protects it. A few good practices:Treat the URI as a secret
Treat the URI as a secret
Don’t embed the SIP URI in client‑side code or public repositories. Anyone with the full address can call the agent and use your credits.
Prefer TLS transport
Prefer TLS transport
Where your client or PBX supports it, connect over TLS rather than plain UDP/TCP so the call signaling is encrypted in transit.
Restrict source addresses on your side
Restrict source addresses on your side
If the calls originate from your own PBX or SIP trunk, use that system’s IP allowlisting so only your trusted infrastructure can reach the agent.
Need stricter access control?
Need stricter access control?
If you require per‑agent authentication or an IP allowlist on Verbeo’s side, contact support@verbeo.ai.