search

jitsi / jibri

Jitsi BRoadcasting Infrastructure
Apache License 2.0
603 stars 314 forks source link

Jibri can't join room after jicofo changed to client_proxy and removed focus component #370

Closed billybobilly closed 3 years ago

billybobilly commented 3 years ago

This Issue tracker is only for reporting bugs and tracking code related issues.

Current behavior

Jibri fails to join room

Expected Behavior

when jibri starts, chrome launches and joins the room

Possible Solution

modify jibri to use client_proxy for focus like jicofo does now

Steps to reproduce

connect a jibri instance to a prosody configured with focus as client_proxy and without focus component. Start recording.

Environment details

Linux Ubuntu 20

Log from jibri: jibri.log

damencho commented 3 years ago

Can you open 3 tabs in the browser on the same deployment?

billybobilly commented 3 years ago

Yes. The deployment is working with 3+ users in the same room. The jibri instance I'm trying to connect is also a working instance when it is connected to a jitsi that was installed by .deb packages (uses component connection for jicofo).

What I am trying to do is change the connection details on a working jibri instance so that it points to this new build that was done from source and uses the new client_proxy connection for jicofo

billybobilly commented 3 years ago

This jibri instance is also a jibri sip gateway connecting to PolyCom video calls and it works fine on the other .deb build.

bgrozev commented 3 years ago

Can you provide logs from jicofo and jibri when the failure occurs?

billybobilly commented 3 years ago

reivsed log with jibri and jicofo during the failure jibri-jicofo.log

damencho commented 3 years ago

RemoteWebDriver.get(RemoteWebDriver.java:271) WebDriverException: unknown error: net::ERR_CONNECTION_REFUSED

This means jibri cannot open the link of your deployment ... not sure what link it tries to open though ...

billybobilly commented 3 years ago

all ports are open to the server. if it's chrome, it is just trying to open the browser to the room, right? I am able to curl to the front end web server successfully from the command line on the recorder (jibri)

billybobilly commented 3 years ago

just watched the web server logs and see that the jibri makes a successful POST with a 200 response when it tries to connect.

damencho commented 3 years ago

It is interesting to see what's in there ...

bgrozev commented 3 years ago

Prior to the Sending 'pending' response to start IQ log in jibri do you see Parsed call url? Does the URL look correct?

bbaldino commented 3 years ago

Can you include the entire Jibri log please?

billybobilly commented 3 years ago

I'm creating a clean one for jibri and jicofo and prosody. One minute

billybobilly commented 3 years ago

log.0.txt cofo.log prosody.log

bbaldino commented 3 years ago

Ok, and the https://signal.xxxxxxx.xxx, callName=siptest is correct for your environment? Are you sure the Jibri machine is able to reach that url correctly? Network connectivity, certs, etc. are all good? Can you login to the Jibri and verify it? (via curl or something)

billybobilly commented 3 years ago

signal.xxx is the prosody and jicofo server. meet.xxxx is the web front end. two separate servers. meet.xxx works fine and is connected to signal with no problems. Also, you can see from the logs that jibri is successfully connecting to the muc on signal.

curl from jibri to https://meet.xxx gets the expected result and valid config:

Githubissues.
  • Githubissues is a development platform for aggregating issues.