Thanks — you're asking whether you can integrate Krisp without using LiveKit Cloud. Yes — you can. Krisp noise cancellation can be enabled when you self-host LiveKit. Use the SIP inbound trunk configuration and set

krisp_enabled: true

on

SIPInboundTrunkInfo

so incoming caller audio is processed with Krisp before being forwarded into rooms. The same server SDK and SIP service used in LiveKit Cloud are available in a self‑hosted deployment; the main difference is the

LIVEKIT_URL

you point clients to. Do you want: • the exact config snippet for

SIPInboundTrunkInfo

to enable

krisp_enabled

, or • step‑by‑step instructions to set up the self‑hosted SIP service? Sources: sip | livekit/livekit_composite | DeepWiki | server-sdk-js | livekit/livekit_composite | DeepWiki

Thanks — you’ve shared your inbound trunk JSON and want to confirm Krisp is enabled for your self‑hosted LiveKit server. Your JSON shows

krispEnabled: true

, but LiveKit expects the field name

krisp_enabled

(snake_case) in

SIPInboundTrunkInfo

. Update the payload to use

krisp_enabled: true

. Example:

{
  "trunk": {
    "name": "My trunk",
    "numbers": [
      "+8502906634"
    ],
    "krisp_enabled": true
  }
}

Would you like: • the exact API endpoint and headers to send this payload to your self‑hosted server, or • help verifying the SIP service logs after you apply the change?