Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to start recording #16

Open
sanket-parte opened this issue Mar 13, 2023 · 4 comments
Open

Not able to start recording #16

sanket-parte opened this issue Mar 13, 2023 · 4 comments

Comments

@sanket-parte
Copy link

Hello,

I have followed all the given steps to build and run the edumeet-recorder image. Afterward, I opened the following URL to start a new test meeting session: https://letsmeet.no/test-edumeet-recorder.

Next, I ran the following CURL command to start recording:
curl -i -H "Accept: application/json" -H "Content-Type: application/json" --data '{"type":"uri", "data":{"bitrate":6000, "uri":"https://letsmeet.no/test-edumeet-recorder?headless=true&displayName=recorder", "stream_uri":"","mode":"record"}}' -X POST http://127.0.0.1:34568/api/start

Although I received a "Started" response, the recording did not begin since no recorder joined the room. Additionally, I encountered the following error in the edumeet-recorder container:
edumeet-recorder-error

Could anyone please tell me what the issue might be with this error?

Thank you.

@kapsa
Copy link
Contributor

kapsa commented Mar 13, 2023

I built a new image of the recorder in the docker. Recording works fine. The recording is located in /tmp. The logs you presented are irrelevant and do not affect the recording. Send me more info about your setup. Does the recorder have network access?

@sanket-parte
Copy link
Author

The machine I am using to run this recorder has restricted internet access. However, I am able to access and join the session at https://letsmeet.no/test-edumeet-recorder.

Here are the setup details: I cloned the repository and built the edumeet-recorded docker image using the following command: "docker build -t edumeet-recorder .". Then, I ran the following command to start edumeet-recorder: "docker run -v /tmp/edumeet-recorder:/records --name edumeet-recorder -it -d --network=host edumeet-recorder".

The recorded container started successfully. As I mentioned before, I ran the CURL command to start the edumeet recording on https://letsmeet.no/test-edumeet-recorder. However, the recorder is not joining the room, but the .ts file is being created in the /records directory.

I checked the file, but nothing was recorded, and it was just a video file with a black screen. When I ran this recorder on a machine with full internet access, it worked fine. However, on the machine with restricted internet access, it did not work as expected.

I want to understand what could be causing this issue so that I can resolve it.

@kapsa
Copy link
Contributor

kapsa commented Mar 14, 2023

It looks like network problems since it is running on a machine with full internet access. Perhaps some ports are blocked. For some reason the headless browser did not connect to the edumeet server. Here are the requirements: https://github.com/edumeet/edumeet#ports-and-firewall. When investigating network problems, I recommend chrome://webrtc-internals/ and wireshark.

@sanket-parte
Copy link
Author

Ok, Thanks for the information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants