This message was deleted.
# helpdesks
steep-balloon-41261
07/31/2023, 2:17 AMThis message was deleted.
a
able-gigabyte-21598
07/31/2023, 9:48 PMWhat do your egress logs show?
able-gigabyte-21598
07/31/2023, 11:56 PMAnd it is connected to the same redis instance as your LiveKit server?
l
limited-easter-25430
08/01/2023, 12:01 AMHow do I do it? just use the livekit-server --dev command, do I have to add any flags?
a
able-gigabyte-21598
08/01/2023, 12:02 AMl
limited-easter-25430
08/01/2023, 12:31 AMThank you very much, I was missing the redis configuration, now I get this message in egress
d
dry-elephant-14928
08/01/2023, 1:02 AMyou are getting this because
START_RECORDINGl
limited-easter-25430
08/01/2023, 1:35 AMAre you referring to this? i used this command
livekit-cli join-room --room test-room --identity publisher --publish-demo
and I still get the same message when I make the request
livekit-cli start-room-composite-egress --request request.json --api-key devkey --api-secret secret
d
dry-elephant-14928
08/01/2023, 6:28 AMcan you paste your request.json? (please redact any storage details)
l
limited-easter-25430
08/01/2023, 1:56 PM Copy code
{
"room_name": "test-room",
"file": {
"filepath": "livekit/{room_name}-{time}",
"azure": {
"accountName": "test",
"accountKey": "",
"containerName": "livekit-tesst"
}
}
}limited-easter-25430
08/01/2023, 1:57 PMthe request is pointing to a blobstorage in azure
a
able-gigabyte-21598
08/02/2023, 12:26 AMthis might be related to the fact that it’s considered a screenshare. I’ll have to do some testing and make sure this case works. However, if you join a room in your browser with a camera, that should work