LiveKit Agents on a Jamaican Number: Open-Source AI Receptionist with a WOCOM SIP Trunk
LiveKit is an open-source platform for real-time audio and video. Its Agents framework is used to build voice AI, and its SIP service connects those agents to ordinary phone calls. Because it is open source, you choose every component: speech recognition, a language model such as GPT, Claude or Gemini, and the voice. You can run it on LiveKit Cloud or on your own servers.
This guide connects a LiveKit agent to your Jamaican number, with WOCOM carrying the calls.
What You Need
- A WOCOM number on Cloud PBX or a SIP trunk.
- A LiveKit Cloud project (or a self-hosted LiveKit server with SIP) and the
lkcommand-line tool. - An agent built with LiveKit Agents, registered with an
agent_nameso calls can be sent to it.
Step 1: Find Your SIP Address
Every LiveKit Cloud project has a SIP address, shown on the project settings page (or with lk project list --json). It looks like sip:abc123xyz.sip.livekit.cloud. For encrypted signalling, add ;transport=tls or use port 5061.
Step 2: Create the Inbound Trunk
Write a small JSON file describing which calls LiveKit should accept, and create it with lk sip inbound create inbound-trunk.json. The important fields are:
numbers: your Jamaican number(s), in E.164 form with the plus:["+1876XXXXXXX"].auth_usernameandauth_password, orallowed_addresseswith WOCOM's signalling addresses. If you leavenumbersempty, you must set one of these, or anyone could send calls to your project. On LiveKit Cloud, address filtering only takes effect once LiveKit support has enabled it for your project, so credentials are the safer default.media_encryption: set it toSIP_MEDIA_ENCRYPT_ALLOWorSIP_MEDIA_ENCRYPT_REQUIREif you want SRTP. It is off by default.
Step 3: Create a Dispatch Rule
A dispatch rule decides which room each call joins and which agent is sent in. For a receptionist, use dispatch_rule_individual, which gives every caller their own room, with a room_prefix such as call-. Add your agent under room_config.agents using its agent_name, then create the rule with lk sip dispatch create dispatch-rule.json. Use a callee rule instead if several numbers should reach different agents.
Step 4: Ask WOCOM to Route the Number
Send WOCOM support the following:
- The Jamaican number(s) you want answered by the AI, written in E.164 form (for example +1876XXXXXXX or +1658XXXXXXX).
- The platform's SIP address for inbound calls (shown below for this platform).
- Whether the AI also needs to place outbound calls, and from which number.
- Where calls should go if the AI hands a caller to a person: an extension, a ring group, or a mobile number.
Give WOCOM your project's SIP address from step 1 and, if you set them, the inbound username and password. LiveKit accepts PCMU, PCMA and G.722 by default. Ask for G.722, which WOCOM supports, for the clearest audio: it helps the speech recogniser with Jamaican names and accents.
Step 5: Outbound Calls
To let the agent place calls, create an outbound trunk with lk sip outbound create outbound-trunk.json, using the WOCOM gateway as address, your number in numbers, and the SIP username and password WOCOM issued (--auth-user and --auth-pass). Each call is then started with lk sip participant create, or the CreateSIPParticipant API, with the trunk ID, your caller ID and the destination number.
Transfers and the Keypad
LiveKit transfers a caller with TransferSIPParticipant, which sends a SIP REFER with the target you give in transfer_to. That can be an extension on your Cloud PBX or a staff mobile. LiveKit also documents warm transfers, where the agent briefs a person first. Keypad tones are supported. Ask WOCOM to allow REFER on your route.
What It Costs (November 2026)
When you bring your own trunk, LiveKit Cloud counted SIP minutes against your plan: 1,000 free minutes on Build, 5,000 on Ship (US$50 per month) and then about US$0.004 per minute, and 50,000 on Scale (US$500 per month) and then about US$0.003. Your speech, model and voice providers bill separately, and WOCOM bills the call.
Why This Route Is Worth Knowing
LiveKit is the most flexible option in this series, and the WOCOM AI receptionist itself runs on this kind of stack. If you have engineers and want complete control, it is an excellent foundation. If you want the result without the build, WOCOM AI is included with Cloud PBX. Read about choosing the model behind your agent, or contact WOCOM to route your number to LiveKit.
Continue exploring
Ready to upgrade your communications?
Talk to our team about the right solution for your business.
Book a Demo Contact SalesEverett Kildare is WOCOM's voice and infrastructure specialist, with more than 25 years of experience designing and running carrier-grade voice, SIP and virtualization infrastructure. Holding a BSc in Information Technology, he has built, secured and migrated phone systems for businesses of every size. Everett writes WOCOM's technical coverage of SIP trunking, cloud PBX, contact centres, business continuity and migration.