Open stefanor opened 3 years ago
Use java8 for the time beeing. We will work at some point to make sure it works with java11, but we are still not there.
Any help is welcome, we are happy to review any PRs. Thank you.
We have sound only in one direction (phone mic to Jitsi) but we do not hear anything on the phone speaker.
2022-01-23 09:38:30.995 SEVERE: [10] org.jitsi.impl.neomedia.device.DeviceConfiguration.log() Failed to register custom Renderer org.jitsi.impl.neomedia.jmfext.media.renderer.audio.PulseAudioRenderer with JMF.
...
2022-01-23 09:31:51.427 SEVERE: [187] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2022-01-23 09:31:51.432 SEVERE: [187] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@25a88eb3
2022-01-23 09:31:51.433 SEVERE: [186] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@25a88eb3
...
2022-01-23 09:32:59.626 SEVERE: [141] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to send a packet to target /2a41:4f4:201:6241:0:0:0:2:10000:java.io.IOException: No active socket.
So it seems we have not an issue with the Java version, but probably that IPv6 may not supported by the active video bridge. However, firewall udp port 10000 is open for both IPv4 and IPv6 on this jvb server. Can we force Jigasi to talk with a jvb on IPv4?
For jicofo and jigasi we are still on openjdk version "1.8.0_312" (= Java 8), which is recommended here.
Don't hijack threads/issues reporting other problems.
Please, when you have questions or problems use the community forum before opening new issues, thank you.
-Djava.net.preferIPv4Stack=true
Ok, sorry, I thought it was related as I had some of the same SEVERE log entries and partially the same effect. Thanks for the hint with the IPv4 option, will give a try.
在arm架构操作系统上跑jigasi的时候也遇到了这个问题
Failed to build a graph for the given custom options. Failed to realize: net.sf.fmj.media.ProcessEngine@48c22159 Cannot build a flow graph with the customized options: Unable to transcode format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed to: opus/rtp, 48000.0 Hz, Stereo outputting to: raw.rtp Unable to add customed codecs: org.jitsi.impl.neomedia.audiolevel.AudioLevelEffect2@59562a94 Error: Unable to realize net.sf.fmj.media.ProcessEngine@48c22159
请问我应该怎样去解决这个问题呢
Any news on this?
We deploy Jigasi with Java 11 so no news from our end.
Debian 12 now uses Java 17 by default, so Jigasi won't work until you downgrade (not always possible or easy), and it could potentially come back with updates, breaking the calls :/
It works fine here on Java 17, built from source, along with libjnopus from libjitsi, libfvad, and jitsi-webrtc-vad-wrapper also built from source, so I suspect it might be to do with the native libraries being built against Java 11 and then being run against Java 17?
Debian 12 now uses Java 17 by default, so Jigasi won't work until you downgrade (not always possible or easy), and it could potentially come back with updates, breaking the calls :/
You can use the adoptopenjdk repos to get Java 11, which is LTS and still supported AFAIK.
It works fine here on Java 17, built from source, along with libjnopus from libjitsi, libfvad, and jitsi-webrtc-vad-wrapper also built from source, so I suspect it might be to do with the native libraries being built against Java 11 and then being run against Java 17?
So if I understand right, if Jitsi/Jigasi had a flavour/version built with Java 17 (and published to dockerhub), we could use that ? Understood 😉
Description
No audio is carried when Jigasi runs under OpenJDK 17 on Debian bullseye.
We have an Asterisk in front of a jitsi+jigasi. When deployed on Debian 11 bullseye, with the default OpenJDK 17, no audio is carried after the conference room selection in Asterisk. Asterisk is configured to only use opus with jigasi.
Relevant issue seems to be:
Downgrading to OpenJDK 11 makes it work again.
Current behaviour
Here are the relevant log lines from jigasi:
Expected Behaviour
We expect sound to be carried. After downgrading to OpenJDK 11, the log entries are:
Possible Workaround
Downgrade to OpenJDK 11.
Steps to reproduce
Environment details
Debian 11 bullseye, amd64, OpenJDK 17
Ansible Config: https://salsa.debian.org/debconf-video-team/ansible/-/tree/master/roles/jitsi