Hi,
at the moment I am using a LifeSize-bridge and some other LifeSize-hardware videostations for a conference
Now I created a Jitsi-Meet server, but I can’t connect with this LifeSize-hardware-videostations to this Jitsi-server. Is there a software necessary (if yes, which) or what should I do to make this work?
thx
Andi
We had done that, but setting it up is not like running jus apt-get install command, it is complicated process.
# SIP Gateway
Currently the XMPP API is the only officially supported API, so this doc will discuss how to configure Jibri to allow SIP gateway calls via the XMPP API.
To use the SIP gateway functionality of Jibri, you'll need to set the `sip_control_muc` field in `config.json`, it can be found within the `XmppEnvironment` field. Jibri will join this MUC to announce itself of being capable of providing SIP gateway services to Jicofo.
# Configuring sipgw jibri with jitsi-meet
This document describes how you can configure jitsi-meet to use sipgw jibri and enable rooms in 'Add people dialog'
You will need a working deployment of jibri configured to use a regular sip video device, for more info check out the [jibri documentation](https://github.com/jitsi/jibri/blob/master/README.md).
This feature is available for non-guests of the system, so this relies on setting in config.js ``enableUserRolesBasedOnToken: true`` and providing a jwt token when accessing the conference.
* Jicofo configuration:
edit /etc/jitsi/jicofo/sip-communicator.properties (or similar), set the appropriate MUC to look for the Jibri Controllers. This should be the same MUC as is referenced in jibri's config.json file. Restart Jicofo after setting this property.
```
org.jitsi.jicofo.jibri.SIP_BREWERY=TheSipBrewery@conference.yourdomain.com
```
* Jitsi Meet configuration:
- config.js: add
```
enableUserRolesBasedOnToken: true,
peopleSearchQueryTypes: ['conferenceRooms'],
peopleSearchUrl: 'https://api.yourdomain.com/testpath/searchpeople',
This file has been truncated. show original
1 Like
thx first
and how does/should this finally work? I mean if I open with jitsi meet the room “hostname/test123”… how can I connect with my lifesize (lifesize room 200) this conference? What IP/URL should i call?
So there is an invite option in the UI (the plus in bottom right corner), if you start typing there the name of the room you will get the room and when choosing it, its id, which will be the sip address will come to jibri and jibri will use the pjsua client to call it using sip.
for jibri… is there a dns entry necessary (for jitsi meet or jibri)?
Bcs always when I try to start a recording I get an error "Recordingunvailable - Oops! The Recording service is currently unvailable. We’re working on resolve the issue. Please try again later.
Or what could be the problem?
ty
Maybe jicofo does not see any reocrders. Check jibri and jicofo logs.
Is there something false?
ty
No, I don’t see anything for the moment
But logs describe the situation, more than looking at the config …
jicofo.log (27.2 KB)
my jibri logfolder is empty
Is your jibri running? You uploaded a log snippet, which doesn’t say much. You need to check the log file from starting jicofo, do you see that it detects a jibri. But as you say jibri has no logs, I suppose it is not running for some reason, and neither jicofo and neither you can use it. Check why jibri is not running.
root@jibri:/var/log/jitsi/jibri# service jibri status
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2019-02-11 11:57:11 UTC; 12min ago
Process: 5013 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=0/SUCCESS)
Main PID: 5065 (java)
Tasks: 35 (limit: 4915)
CGroup: /system.slice/jibri.service
└─5065 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/ji
Feb 11 12:02:41 jibri launch.sh[5065]: org.jitsi.jibri.service.impl.FileRecordingJibriService.(FileReco
Feb 11 12:02:41 jibri launch.sh[5065]: org.jitsi.jibri.JibriManager.startFileRecording(JibriManager.kt:134)
Feb 11 12:02:41 jibri launch.sh[5065]: org.jitsi.jibri.api.xmpp.XmppApi.handleStartService(XmppApi.kt:290)
Feb 11 12:02:41 jibri launch.sh[5065]: org.jitsi.jibri.api.xmpp.XmppApi.access$handleStartService(XmppApi.kt:
Feb 11 12:02:41 jibri launch.sh[5065]: org.jitsi.jibri.api.xmpp.XmppApi$handleStartJibriIq$1.run(XmppApi.kt:2
Feb 11 12:02:41 jibri launch.sh[5065]: java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executor
Feb 11 12:02:41 jibri launch.sh[5065]: java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
Feb 11 12:02:41 jibri launch.sh[5065]: java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Feb 11 12:02:41 jibri launch.sh[5065]: java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
Feb 11 12:02:41 jibri launch.sh[5065]: java.base/java.lang.Thread.run(Thread.java:844)
but jicofo doesn’t detect a jibri…
I also installed jibri again… but without successs…
jibri-logs are still empty
What is the java version you use to run it? Make sure it is java8.
root@jibri:/var/log/jitsi/jibri# java -version
java version “1.8.0_201”
Java™ SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot™ 64-Bit Server VM (build 25.201-b09, mixed mode)
root@jibri:/var/log/jitsi/jibri#
on jibri
root@Jitsi:/home/jitsi# java -version
openjdk version “1.8.0_181”
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-2~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
on jitsi/jicofo/xmpp
btw
jicofo_1.0-440-1_amd64.deb
jicofo_1.0-451-1_amd64.deb
jitsi-meet_1.0.3383-1_all.deb
jitsi-meet_1.0.3508-1_all.deb
jitsi-meet-prosody_1.0.3081-1_all.deb
jitsi-meet-prosody_1.0.3186-1_all.deb
jitsi-meet-web_1.0.3081-1_all.deb
jitsi-meet-web_1.0.3186-1_all.deb
jitsi-meet-web-config_1.0.3081-1_all.deb
jitsi-meet-web-config_1.0.3186-1_all.deb
jitsi-videobridge_1093-1_amd64.deb
jitsi-videobridge_1104-1_amd64.deb
jibri_7.2.71-1_all.deb
google-chrome-stable_72.0.3626.96-1_amd64.deb
I just tried guessing from the part of the logs that you had shown. Find and paste the whole jibri log file, so we can see the error from the beginning.
my logging properties:
handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
java.util.logging.FileHandler.level = FINE
java.util.logging.FileHandler.pattern = /var/log/jitsi/jibri/log.%g.txt
java.util.logging.FileHandler.formatter = net.java.sip.communicator.util.ScLogFormatter
java.util.logging.FileHandler.count = 10
java.util.logging.FileHandler.limit = 10000000
org.jitsi.jibri.capture.ffmpeg.util.FfmpegFileHandler.level = FINE
org.jitsi.jibri.capture.ffmpeg.util.FfmpegFileHandler.pattern = /var/log/jitsi/jibri/ffmpeg.%g.txt
org.jitsi.jibri.capture.ffmpeg.util.FfmpegFileHandler.formatter = net.java.sip.communicator.util.ScLogFor$
org.jitsi.jibri.capture.ffmpeg.util.FfmpegFileHandler.count = 10
org.jitsi.jibri.capture.ffmpeg.util.FfmpegFileHandler.limit = 10000000
org.jitsi.jibri.sipgateway.pjsua.util.PjsuaFileHandler.level = FINE
org.jitsi.jibri.sipgateway.pjsua.util.PjsuaFileHandler.pattern = /var/log/jitsi/jibri/pjsua.%g.txt
org.jitsi.jibri.sipgateway.pjsua.util.PjsuaFileHandler.formatter = net.java.sip.communicator.util.ScLogFo$
org.jitsi.jibri.sipgateway.pjsua.util.PjsuaFileHandler.count = 10
org.jitsi.jibri.sipgateway.pjsua.util.PjsuaFileHandler.limit = 10000000
org.jitsi.jibri.selenium.util.BrowserFileHandler.level = FINE
org.jitsi.jibri.selenium.util.BrowserFileHandler.pattern = /var/log/jitsi/jibri/browser.%g.txt
org.jitsi.jibri.selenium.util.BrowserFileHandler.formatter = net.java.sip.communicator.util.ScLogFormatter
org.jitsi.jibri.selenium.util.BrowserFileHandler.count = 10
org.jitsi.jibri.selenium.util.BrowserFileHandler.limit = 10000000
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = net.java.sip.communicator.util.ScLogFormatter
org.jitsi.level = FINE
org.glassfish.level = INFO
org.osgi.level = INFO
but my /var/log/jitsi/jibri folder is empty…
where should the log file be?
Try using journalctl -u jibri
to extract it.