-
Notifications
You must be signed in to change notification settings - Fork 301
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
No audio after upgrade from jigasi_1.1-231-gd792d0f-1 to jigasi_1.1-259-g25c51d6-1 #433
Comments
Please attach logs. Maybe clear the logs, restart jigasi and make a call where you reproduce the problem. What is the java that you use? And the jitsi-meet version? |
Thank you for the fast reply. VersionsJitsi-Meet Version: 1.0.6260 Log output
|
Are you using g722? Can you try disabling it and try with g711, is it working? |
Changing to G711 did not work. |
Do you reproduce the issue if you run it with java11? |
I will try to install java 11 instead of 14 and test if I can reproduce it. |
i have exactly the same problem but using 11:
Log:
|
@obi12341 Can you clean the log file, restart jigasi and upload the log. |
@damencho So if everything works for you, how does your config look like? Would be nice to have something to compare with since we now are in the same situation after upgrading to Ubuntu 22.04 and latest Jitsi + Jigasi + everything else. |
@enoch85 I wrote my entire sip-communication.properties new because there are variables inside that would break jigasi after the upgrade. |
@holzi1005 So you mean, use this and just change the values needed to talk to an external PBX? |
@enoch85 Correct.
acc1 is the long acc1xxxxx number you have in your configuration. Do you use asterisk between jigasi and PBX? Then it could be that the Codecs must be added there as well. |
So ubuntu 22.04 latest jitsi and jigasi using openjdk 11 gives no sound in a conference. This is a new clean setup with a new clean asterisk as a trunk in to jigasi. Everything registers. A user can join a conference but no sound. I have tried changing the different settings for codecs without any luck. It still behaves the same. And the only thing that stands out are these lines in jigasi a bit after the user joined. 2023-11-20 08:45:34.641 SEVERE: [161] net.sf.fmj.media.Log.error: Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed |
So for me a solution (this took some time to find) was to send the conference room with domain. If the header is set with only "conferenceroom" you get no sound. If you send the header with |
There is a similar problem with no audio from a SIP participant in Debian 12. |
Description
After upgrading from 1.1-231 to 1.1-259 the phone is joining the conference but with no audio in both directions.
Current behavior
In the Version 1.1-231, the user can speak and hear other participants in the conference. Jigasi is installed on a seperate server without any other service. Prosody is installed in a shard. Both servers can communicate in a private network and over the internet (public)
As java version, I have installed OpenJDK Runtime Environment and OpenJDK 64-Bit Server VM 14.0.2
When I downgrade jigasi, it immediately works with the same configuration, so I marked jigasi as hold that I can still upgrade the system without any issues with jigasi.
The same configuration was used until version 1.1.231 without any issues.
Steps to reproduce
apt update && apt upgrade -y
Environment details
The text was updated successfully, but these errors were encountered: