I want to integrate the livekit and Genesys, pleas...
# ask-ain
narrow-advantage-65481
12/17/2025, 3:33 AMI want to integrate the livekit and Genesys, please give me some details about the integration steps
t
tall-airline-16756
12/17/2025, 3:33 AMThanks for reaching out, Yuhan. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
12/17/2025, 3:34 AMThanks — I can help outline integration options and steps. Quick clarifying questions so I give the right guidance:
1. Which Genesys product are you using (Genesys Cloud/Genesys Engage/other)?
2. Do you want LiveKit to handle real-time audio/video within a Genesys contact flow (in-call media), or do you need agent-side web apps that join LiveKit rooms alongside Genesys sessions, or both?
3. Are you targeting a browser-based integration, a native app, or telephony PSTN integration through Genesys?
4. Do you already have LiveKit server(s) and API keys set up, or should I include LiveKit deployment steps?
Answering these will let me provide a precise step-by-step integration plan and example flows.
n
narrow-advantage-65481
12/17/2025, 3:36 AMMy bot is hosted on LiveKit Cloud, and the Genesys SIP Access Control requires the addresses to be allowed, where can I find the IP addesses to be used
t
tall-airline-16756
12/17/2025, 3:36 AMThanks — you're using LiveKit Cloud and need the IPs to allow in Genesys SIP Access Control.
• If your LiveKit project is in the EU, India, or US regions, use these static IP blocks:
◦ 143.223.88.0/21
◦ 161.115.160.0/19
• If your project is in any other region, static IPs are not available. Instead allow the wildcard DNS names:
◦ *.livekit.cloud
◦ *.turn.livekit.cloud
To confirm your project region, check the LiveKit Cloud dashboard: https://cloud.livekit.io
For the firewall/static IP guidance, see: https://docs.livekit.io/home/cloud/firewall/#static-ips
Would you like me to tell you which option applies to your project if you share its region or project name?
Sources: Configuring firewalls | LiveKit docs
tall-airline-16756
12/17/2025, 3:38 AMThanks — since your agent region is US-East, use the LiveKit Cloud static IP blocks for US (these apply to Realtime and SIP signaling/media):
• 143.223.88.0/21
• 161.115.160.0/19
Add those ranges to Genesys SIP Access Control. If you want, I can:
• Confirm whether your LiveKit project is specifically in the "us-east" zone if you share the project name, or
• Provide example SIP ACL entries for Genesys with these CIDR ranges. Which would you like?
n
narrow-advantage-65481
12/17/2025, 3:41 AMprovide example SIP ACL entries for Genesys with these CIDR ranges.
t
tall-airline-16756
12/17/2025, 3:41 AMYou're right — below are ready-to-import example ACL entries for a common Genesys Engage SIP server format. I provide two variants: (A) IP/CIDR-only rules, and (B) IP+protocol+port rules (SIP/TLS and RTP). If your Genesys product requires a different syntax, tell me which one and I’ll adapt these.
A) IP/CIDR-only allow rules
• Allow 143.223.88.0/21
• Allow 161.115.160.0/19
Example (generic ACL lines)
• allow ip 143.223.88.0/21
• allow ip 161.115.160.0/19
B) IP + protocol + port rules (SIP/TLS + RTP) Typical ports: UDP/TCP 5060 (SIP), TCP/TLS 5061 (SIP-TLS), RTP 10000–20000 UDP.
Example (generic ACL lines)
• allow udp 143.223.88.0/21 5060
• allow tcp 143.223.88.0/21 5060
• allow tcp 143.223.88.0/21 5061
• allow udp 143.223.88.0/21 10000-20000
• allow udp 161.115.160.0/19 5060
• allow tcp 161.115.160.0/19 5060
• allow tcp 161.115.160.0/19 5061
• allow udp 161.115.160.0/19 10000-20000
Example JSON-style entry (if your system accepts structured ACLs) { "rules": [ {"action":"allow","proto":"udp","cidr":"143.223.88.0/21","ports":"5060"}, {"action":"allow","proto":"tcp","cidr":"143.223.88.0/21","ports":"5060"}, {"action":"allow","proto":"tcp","cidr":"143.223.88.0/21","ports":"5061"}, {"action":"allow","proto":"udp","cidr":"143.223.88.0/21","ports":"10000-20000"}, {"action":"allow","proto":"udp","cidr":"161.115.160.0/19","ports":"5060"}, {"action":"allow","proto":"tcp","cidr":"161.115.160.0/19","ports":"5060"}, {"action":"allow","proto":"tcp","cidr":"161.115.160.0/19","ports":"5061"}, {"action":"allow","proto":"udp","cidr":"161.115.160.0/19","ports":"10000-20000"} ] }
Notes:
• These ranges apply to both Realtime and SIP signaling/media from LiveKit Cloud.
• If your Genesys deployment requires explicit DNS/wildcard entries instead of IPs, use *.livekit.cloud and *.turn.livekit.cloud instead.
• Tell me which Genesys product/version you use if you want these in product-specific syntax (e.g., Genesys Engage SIP server config).
11 Views