Bulk Solutions / Livekit - IP Based Authentication

How the integration works

LiveKit Cloud does not SIP-register to Bulk Solutions. Both sides use IP-based peering and hostname routing.

Shared SIP settings

Values to collect before you start

Have these ready from both portals. Replace the examples with your own project and numbers.

Inbound setup

Route calls that arrive on your Bulk DID into LiveKit rooms or voice agents.

1. Create a LiveKit inbound trunk

   In LiveKit Cloud go to Telephony → SIP trunks → Create new trunk, choose Inbound, then paste:

   Copy{
     "name": "Bulk inbound",
     "numbers": [
       "+13109060901",
       "13109060901"
     ],
     "allowedAddresses": [
       "x.x.x.x - find IPs in our portal -> interconnection guide -> IP Based Authentication",
       "",
       ""
     ]
   }

   Include both number formats. Bulk sends the request URI as 1NXXNXXXXXX (example 13109060901). LiveKit often matches E.164 with a plus. Listing both avoids a trunk miss.

   Do not set a SIP username or password on this trunk. Bulk inbound IP authentication does not send digest credentials.

   allowedAddresses: this field may need to be enabled on your LiveKit project by LiveKit support. If the dashboard rejects it, create the trunk with numbers only and ask LiveKit to turn on IP allowlisting.

2. Create a LiveKit dispatch rule

   A trunk alone is not enough. A dispatch rule tells LiveKit which room to create. In Telephony → Dispatch rules:

   Copy{
     "name": "Bulk inbound dispatch",
     "rule": {
       "dispatchRuleIndividual": {
         "roomPrefix": "call-"
       }
     }
   }

   To send every inbound call to a LiveKit agent, add roomConfig.agents and set agentName to your worker name.

3. Point the Bulk DID at LiveKit

   In the Bulk Solutions portal:

   1. Interconnection → Host → Add your LiveKit SIP host: YOURSUBDOMAIN.sip.livekit.cloud, port 5060. Prefer the hostname over a frozen A-record IP. LiveKit Cloud addresses can change.
   2. If your portal screen only accepts IPv4, add the current resolved addresses and contact Bulk support so we can attach the FQDN for you.
   3. Interconnection → Trunk Group → Add and assign that host to the trunk group.
   4. Inbound → DIDs → Manage and set your telephone number to that trunk group.
   5. Wait 2–3 minutes for the host and trunk group to propagate to all Bulk SBC nodes.

   Inbound calls are sent from one of our signaling IPs to your LiveKit host with request URI 1NXXNXXXXXX.

4. Optional: pin inbound to the US LiveKit region

   If you want signaling to stay in the United States, use:

   CopyYOURSUBDOMAIN.us.sip.livekit.cloud

Outbound setup

Allow LiveKit Cloud to originate calls through Bulk Solutions.

1. Allow LiveKit source IPs in Bulk

   LiveKit Cloud publishes static ranges for SIP signaling and media in US and several other regions. Add these as hosts in Interconnection → Host → Add, then wait 2–3 minutes:

   Copy143.223.88.0/21
   161.115.160.0/19
   153.57.128.0/18

   If the portal does not accept CIDR notation, contact support@bulkvs.com and we will add the ranges on your account.

2. Create a LiveKit outbound trunk

   In LiveKit Cloud go to Telephony → SIP trunks → Create new trunk, choose Outbound:

   Copy{
     "name": "Bulk outbound",
     "address": "sip.bulkvs.com",
     "numbers": [
       "+13109060901"
     ]
   }

   Use the hostname sip.bulkvs.com, not a single Bulk IP. Leave username and password empty for IP authentication. Save the trunk ID (ST_…) for API calls.

3. Place a call from LiveKit

   Create a SIP participant. Example CLI payload:

   Copy{
     "sip_trunk_id": "ST_xxxxxxxxxxxx",
     "sip_call_to": "+13105551212",
     "room_name": "outbound-test",
     "participant_identity": "bulk-test",
     "wait_until_answered": true
   }

   Bulk accepts destinations as 1NXXNXXXXXX@sip.bulkvs.com or NXXNXXXXXX@sip.bulkvs.com.

Caller ID rules

Set LiveKit numbers / sip_number to a number on your Bulk account in one of these formats. Any other caller ID format is rejected:

E911

Emergency calling uses the same outbound trunk. Caller ID must be a provisioned 10-digit, 11-digit, or +E.164 number.

Test plan

Troubleshooting

Need help?

If you get stuck on either side of the trunk, send us the DID, LiveKit SIP URI, approximate call time, and a Call-ID. We can pull the SIP ladder from our network.

LiveKit Cloud documentation for trunks and dispatch rules is at docs.livekit.io/telephony.