Hi whenever I add auto egress to my dispatch rule ``` egress LiveKit Community #ask-ai

Hi, whenever I add auto_egress to my dispatch rule...

glamorous-oil-12326

09/12/2025, 8:51 PM

Hi, whenever I add auto_egress to my dispatch rule:

Copy code

"egress": {
    "tracks": {
        "filepath": "dev/{room_id}-{track_id}.ogg",
        "azure": {
            "account_name": "",
            "account_key": "",
            "container_name": ""
        }
    }
}

I am not able to call into my trunk. When I remove the egress configuration everything works fine (Note: I use the correct azure env variables when actually applying my dispatch rule). When I use the SIP API to upload this, it works fine and goes through. Had a few followups: 1. Are there any issues with using auto_egress in a SRTP setting? 2. Is there anything wrong with the auto_egress config for my dispatch rule?

tall-airline-16756

09/12/2025, 8:51 PM

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

tall-airline-16756

09/12/2025, 8:52 PM

Thank you for reaching out! Here are some thoughts on your queries: 1. At the moment, there’s no specific information suggesting issues with using auto-egress in an SRTP setting. To better support you, could you please clarify if you’re referring to SRTP for media transport in WebRTC connections, or if you’re trying to egress media to an SRTP endpoint? Also, if you’ve encountered any particular errors when using auto-egress with SRTP-enabled participants or rooms, sharing those would be really helpful. 2. Your auto-egress configuration looks good from what I can see, but its success can depend on a few important factors: • Make sure the egress service is properly deployed and running, with the right API credentials, WebSocket URL, and Redis configuration in place. • Double-check that your Azure storage credentials are valid and that the service has permission to write to the container you’ve specified. • Take a look at the egress service logs to spot any errors or misconfigurations that might be occurring. • Confirm that the egress service isn’t running into session duration limits or other constraints. If you run into any specific errors or if something isn’t working as expected, please don’t hesitate to share those details. I’m here to help and can guide you through the next steps! Sources: livekit-protocol/src/livekit.rs | README.md | lib/livekit/proto/livekit_egress_pb.rb | Auto egress | LiveKit Docs | SIP Integration | livekit/livekit_composite | DeepWiki

glamorous-oil-12326

09/12/2025, 8:59 PM

When I take the egress param out of my dispatch rule, I am able to call in fine; however when I put it in, it always fails

tall-airline-16756

09/12/2025, 8:59 PM

I'd love to help you get to the bottom of the issue with the egress parameter in your dispatch rule. Could you share a bit more about what happens when the call fails? For example: • Do you see any error messages or logs when the call doesn't go through? • Is the problem happening during call setup, media transmission, or at another point? • Have you had a chance to check if the egress service is up and running, and properly configured? With these details, we'll be in a much better position to figure out what's going on and find the right solution together.

glamorous-oil-12326

09/12/2025, 9:00 PM

I get the message: "The person you are trying to reach is not accepting calls at this time"

tall-airline-16756

09/12/2025, 9:01 PM

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!

Open in Slack

Previous Next