INFO livekit.agents - received job request {"job_id": "AJ_QP2jikwDHwTd", "dispatch_id": "", "room_name": "", "agent_name": "", "resuming": false} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,758 - INFO livekit.agents - initializing job process {"pid": 982538} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,835 - INFO livekit.agents - job process initialized {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,835 - DEBUG asyncio - Using selector: EpollSelector {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,899 - WARNING livekit.plugins.deepgram - nova-2-general does support language en-US, using to nova-3-general {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,899 - INFO voice-agent - connecting to room {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,903 - INFO livekit - livekit_api:signal clientsignal stream96livekit apisignal client:signal_stream - connecting to wss://sajjadproject-j3rqzfu5.livekit.cloud/rtc?sdk=python&protocol=15&auto_subscribe=0&adaptive_stream=0&version=0.22.0&access_token=... {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,926 - DEBUG livekit - rustls:anchors150rustls:anchors - add_parsable_certificates processed 146 valid and 0 invalid certs {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,927 - DEBUG livekit - tokio_tungstenite:tlsencryptionrustls103tokio tungstenitetlsencryption:rustls - Added 146/146 native root certificates (ignored 0) {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,927 - DEBUG livekit - rustls:clienths73rustlsclient:hs - No cached session for DnsName("sajjadproject-j3rqzfu5.livekit.cloud") {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,927 - DEBUG livekit - rustls:clienths132rustlsclient:hs - Not resuming any session {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,949 - DEBUG livekit - rustls:clienths615rustlsclient:hs - Using ciphersuite TLS13_AES_128_GCM_SHA256 {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,949 - DEBUG livekit - rustls:clienttls13142rustlsclient:tls13 - Not resuming {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,949 - DEBUG livekit - rustls:clienttls13381rustlsclient:tls13 - TLS1.3 encrypted extensions: [] {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224004 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224004,950 - DEBUG livekit - rustls:clienths472rustlsclient:hs - ALPN protocol is None {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224005 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224005,125 - DEBUG livekit - tungstenite:🤝client95tungstenite🤝:client - Client handshake done. {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224035,530 - DEBUG livekit - tungstenite:protocol666tungstenite:protocol - Received close frame: Some(CloseFrame { code: Normal, reason: "" }) {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224035,530 - DEBUG livekit - tungstenite:protocol683tungstenite:protocol - Replying to close with Frame { header: FrameHeader { is_final: true, rsv1: false, rsv2: false, rsv3: false, opcode: Control(Close), mask: None }, payload: [3, 232] } {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224035,531 - WARNING livekit - livekit:rtc engine446livekit:rtc_engine - received session close: "signal client closed: \"stream closed\"" UnknownReason Resume {"pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224035,532 - INFO livekit.agents - process exiting {"reason": "room disconnected", "pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 224035,532 - DEBUG livekit.agents - shutting down job task {"reason": "room disconnected", "user_initiated": false, "pid": 982538, "job_id": "AJ_QP2jikwDHwTd"} Jul 27 224035 ip-172-31-10-245 python3.11[694435]: 2025-07-27 22:40

Thanks for reaching out, Shehryar. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

can this be a ip auth issue.

Hey there! That "signal client closed: stream closed" error you’re seeing can definitely pop up because of IP authentication issues, especially when you’re using LiveKit Cloud. Since LiveKit Cloud nodes have dynamic IP addresses, it can sometimes cause authentication hiccups if your SIP trunk or firewall is set to accept connections only from specific IP ranges. Here’s what you can do to smooth things out: • Use User/Password Authentication: This is usually the easiest and most reliable way to go, as it doesn’t rely on fixed IP addresses. • Adjust IP Range Configuration: If you need to stick with IP authentication, try setting ranges like

0.0.0.0/0

or

0.0.0.0/1

+

128.0.0.0/1

. Just a heads-up, this can lower security a bit, so it’s best to combine it with other methods. Also, it’s a good idea to double-check your firewall rules and SIP trunk settings to make sure they’re in sync with LiveKit’s dynamic setup. If you want, I’m here to help you walk through these steps—just let me know! Sources: livekit/src/rtc_engine/rtc_session.rs | protobufs/livekit_models.proto | SIP outbound trunk | LiveKit Docs

i have connect through genesys to livekit sip server and they ip authencation at their end then are unable to connect to our agent using their private dids.

Hey there! To help you get Genesys connected to the LiveKit SIP server using IP authentication and private DIDs, here’s a simple step-by-step guide: 1. Switch to Username/Password Authentication: Since LiveKit Cloud doesn’t support static IP ranges for authentication, the best bet is to set up Genesys to use username and password authentication for the SIP trunk. 2. Adjust IP Range Configuration: If you really need to stick with IP authentication, try setting a broad IP range like

0.0.0.0/0

or a combination such as

0.0.0.0/1

and

128.0.0.0/1

. Just make sure Genesys is set to accept traffic from these ranges. 3. Configure Private DIDs: Don’t forget to set up the SIP trunk in LiveKit with the specific private DIDs for incoming calls, and double-check that Genesys routes calls properly to those DIDs. 4. Check Network and NAT Settings: Make sure your NAT traversal settings like

use_external_ip

or

nat_1_to_1_ip

are correctly configured in LiveKit. Also, verify that RTP ports (like 10000-20000) are open and properly set up on both sides. One more thing—please confirm that Genesys supports username/password authentication. If it doesn’t, you might want to explore other authentication methods or providers. Feel free to reach out if you want a hand with any of these steps! Sources: SIP APIs | LiveKit Docs | SIP outbound trunk | LiveKit Docs | SIP outbound trunk | LiveKit Docs | SIP inbound trunk | LiveKit Docs | SIP Integration | livekit/livekit_composite | DeepWiki

this problem started when on our ec2 we delve requirement and even enable the shh authencation from specific ip only. and we are using sip cloud and livekit cloud. and enable the ip restriction on ec2 can cause this problem with gensys. but when i try to connect from twilio it works before and after both time it works but the genesys before and after this it is not working.

Just a heads-up: enabling IP restrictions on your EC2 instance might cause some hiccups with Genesys connecting to LiveKit SIP Cloud. That’s because LiveKit Cloud uses dynamic IPs, which aren’t static or easy to predict. So, if Genesys’ IPs aren’t explicitly whitelisted in your EC2 security group, it could end up getting blocked. Here are a few friendly tips to help you out: • Review EC2 Security Groups: Double-check that Genesys IPs are allowed in your EC2 security group settings. If Genesys uses dynamic IPs, this part can get a bit tricky to manage. • Use User/Password Authentication: This tends to be more reliable than relying on IP-based restrictions when connecting to LiveKit SIP Cloud. • Consider Region Pinning: Instead of locking down by IP, try restricting traffic by geographic region for smoother compliance and better reliability. • Check Genesys Configuration: Make sure Genesys is set up to handle LiveKit’s dynamic IP setup properly. Since Twilio works in both cases, it might be handling dynamic IPs differently or using a more flexible authentication method. If you want, I’m here to help you work through these settings—just let me know! Sources: SIP APIs | LiveKit Docs | SIP inbound trunk | LiveKit Docs | SIP outbound trunk | LiveKit Docs | Ports and Firewall | LiveKit Docs | SIP cloud and region pinning | LiveKit Docs

i have attempted almost ten to fifteen calls but im livekit there is no calls for 25 july.

Hey there! If you’re not seeing any calls in LiveKit for July 25th despite trying a few times, no worries—here are some things to check that might help: • Analytics API Constraints: Make sure the date range you’re looking at is within the last 7 days, since the Analytics API only supports that window. • Date Format: Double-check that the date is written as

YYYY-MM-DD

. If it’s off, the data might not show up. • Pagination: If you’re using the API, take a quick look at the pagination settings to be sure you’re on the right page of results. • Call Records: Confirm that calls were actually started and routed through LiveKit on that day. If you’re still stuck after this, just give me a shout—I’m here to help figure it out with you! Sources: Analytics API | LiveKit Docs | Analytics API | LiveKit Docs

I don't have the answer you're looking for. You could also try asking your question: • in one of the other Slack channels or • to https://deepwiki.com/livekit/livekit_composite which is trained on all LiveKit source code If you find the answer, please post it here to help others!