I'm happy to guide you through setting up auto egress on a dispatch rule for Azure in LiveKit. Here’s a simple step-by-step approach: 1. Enable Auto-Egress in Dispatch Rule: When you create or update a SIP dispatch rule, be sure to include the

egress

field inside

room_config

. This will turn on the auto-egress feature for any rooms created through this rule. 2. Configure AutoTrackEgress for Azure Output: Next, use the

AutoTrackEgress

configuration to capture individual audio and video tracks published in the room. You’ll need to provide your Azure details here:Also, feel free to use placeholders like

{room_name}

,

{track_id}

, and

{time}

in the

filepath

to keep things dynamic and organized. ◦ account_name: Your Azure storage account name ◦ account_key: Your Azure storage account key ◦ container_name: The Blob container where you want the recordings to be saved 1. Example Configuration:

{
  "room_config": {
    "egress": {
      "tracks": {
        "filepath": "recordings/{room_name}/{track_id}-{time}",
        "azure": {
          "account_name": "your-azure-account-name",
          "account_key": "your-azure-account-key",
          "container_name": "your-container-name"
        }
      }
    }
  }
}

You can apply this configuration using the LiveKit Admin API or CLI when setting up your SIP dispatch rule. Just a quick reminder: make sure your Azure credentials have the right permissions to write to the container you specify. If you have any questions or need further help, I’m here for you! Sources: livekit-protocol/src/livekit.rs | livekit/livekit_egress.pb.go | Docs::Home | SIP Integration | livekit/livekit_composite | DeepWiki | How to enable auto-egress with SIP