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

Jigasi media error with latest videobridge builds #124

Closed
driesken opened this issue Jan 21, 2016 · 34 comments
Closed

Jigasi media error with latest videobridge builds #124

driesken opened this issue Jan 21, 2016 · 34 comments

Comments

@driesken
Copy link

I was struggeling the last few days with the following error in jigasi:

jigasi.sh[22134]: 2016-01-21 10:47:41.735 INFO: [109] org.jitsi.jigasi.GatewaySession.handleCallState().628 SIP call format used: rtpmap:0 PCMU/8000
jigasi.sh[22134]: 2016-01-21 10:47:41.735 INFO: [109] org.jitsi.jigasi.GatewaySession.peerStateChanged().692 15263950d86@callcontrol.myserver.xx SIP peer state: Connected
jigasi.sh[22134]: 2016-01-21 10:47:41.736 INFO: [109] service.protocol.media.CallPeerMediaHandler.start().1932 Starting
jigasi.sh[22134]: 2016-01-21 10:47:42.245 SEVERE: [148] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed

It seems that this occurs in the latest builds of videobridge (621, 620, ...). The latest compatible version is build 618. Anyone who has the same problem?

@damencho
Copy link
Member

What is the error that you face, what is not working? Last time I was using jigasi I have seen this error and the calls were successful. The thing was that for some reason DTLS is not working for jigasi. You need to make sure jvb is not dropping non-dtls packets. There is a property for that: org.jitsi.impl.neomedia.transform.dtls.DtlsPacketTransformer.dropUnencryptedPkts=false

@driesken
Copy link
Author

The error is the one in the post above, jigasi successfully makes the call but no audio is received at all. The property you suggested unfortunately doesn't fix that.

@damencho
Copy link
Member

You put the property in video bridge and restarted it?

@driesken
Copy link
Author

Yes, I tried adding it to logging.properties (since there was already a org.jitsi.impl.neomedia entry there) and restarted the videobridge but the problem remains.

I see a lot of these warnings:
jvb.sh[10863]: 2016-01-21 20:28:37.593 WARNING: [86] org.jitsi.impl.neomedia.rtp.translator.OutputDataStreamImpl.warn() Will not translate RTP packet.

@damencho
Copy link
Member

You need to add it to sip-communicator.properties for videobridge and
restart it.

On Thu, Jan 21, 2016 at 1:29 PM, Dries De Gendt notifications@github.com
wrote:

Yes, I tried adding it to logging.properties (since there was already a
org.jitsi.impl.neomedia entry there) and restarted the videobridge but the
problem remains.

I see a lot of these warnings:
jvb.sh[10863]: 2016-01-21 20:28:37.593 WARNING: [86]
org.jitsi.impl.neomedia.rtp.translator.OutputDataStreamImpl.warn() Will not
translate RTP packet.


Reply to this email directly or view it on GitHub
#124 (comment)
.

@driesken
Copy link
Author

I believe I don't have a sip-communicator.properties in the videobridge directory? I took one of the builds listed at https://download.jitsi.org/jitsi-videobridge/linux/.

I only have such a file for jigasi...

@damencho
Copy link
Member

Well if you install it from package the the file is in /etc/jitsi/videobridge/sip-communicator.properties. From the archive folder, I think it uses the home to be the folder where it is extracted. So you need to create .sip-communicator folder and place the file there. Information about that should be written in the beginning of the logs or console output.
For installed from deb package it is:
net.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi
net.java.sip.communicator.SC_HOME_DIR_NAME=videobridge
Which forms /etc/jitsi/videobridge/sip-communicator.properties.
You need to make sure jvb founds your config file.

@driesken
Copy link
Author

Thanks, found the file. I've added the parameter and did a restart, videobridge enabled it:
jvb.sh[15182]: 2016-01-21 21:04:43.832 INFO: [1] org.jitsi.impl.configuration.ConfigurationServiceImpl.info() org.jitsi.impl.neomedia.transform.dtls.DtlsPacketTransformer.dropUnencryptedPkts=false

However, the warnings still appear and jigasi doesn't produce any audio. It throws the same errors as in my first post. When I used a previous version like 618, it immediately works again.

@damencho
Copy link
Member

I don't see any change after 618 that can break it, it must use opus. But there is nothing extra to install. I remembered a problem I faced, I didn't make it working with asterisk and jigasi on one machine, if that is the case try moving asterisk on different machine. I didn't had time to investigate the problem. But this doesn't explain how it is working with 618.

@driesken
Copy link
Author

Indeed, very weird since the only thing I do is replacing the original videobridge directory (618 build) with the 621 build and restarting the videobridge.

The Asterisk runs on a different server so that shouldn't be the cause of it. For now I'll stick with build 618 and try again in a few weeks. Thanks for the effort though!

@Kidav
Copy link

Kidav commented Feb 29, 2016

Hi, any news here? I have not working jigasi too jitsi/jigasi#26 . But I am not sure if 618 version will work for me. Can you give me deb or link for your videobridge please?

@driesken
Copy link
Author

For now I'm still stuck at 618 (haven't tried anything else since). It seems that the older builds are no longer available for download using the link above. You can still grab build 618 over here: http://raspi.degendt.com/jitsi-videobridge-linux-x64-618.zip
(Please send a reply when you've got the file)

@Kidav
Copy link

Kidav commented Feb 29, 2016

Got it. thx! I will check it later

@Kidav
Copy link

Kidav commented Mar 2, 2016

Checked. Unfortunately, there is also problem with new jicofo too. For example: if I use videobridge 618 , jicofo 1.0-68-1, jigasi 1.0-99 then all work as expected; If I use videobridge 618 , jicofo 1.0-211-1, jigasi 1.0-99 then sip calls not work. Too bad that new jitsi-meet is not compatible with old jicofo. So now I have to choose between Firefox support and SIP calls

@sysreq0
Copy link

sysreq0 commented Mar 3, 2016

I'm experiencing the same issue. No audio on incoming/outgoing calls between Asterisk and Jigasi/Jitsi-Videobridge when using Jitsi-Videobridge version 659. When I revert back to 513, with no configuration changes, it starts working again immediately.

@hisham1402
Copy link

Hi driesken,

I'm facing same issue, could you please upload videobridge 618 again.
I want to try it maybe it will solve mine.

BR

@driesken
Copy link
Author

driesken commented Mar 7, 2016

@hisham1402
I've uploaded the file again.

@hisham1402
Copy link

Got it, Thanks a lot.

@hisham1402
Copy link

OK I tired it and the audio start working, unfortunately the video not working.

I got this message:

jvb,log:
2016-03-07 13:40:24.045 WARNING: [286] org.ice4j.stack.Connector.run() Connector died: x.x.x.x:10002/udp -> null
java.net.SocketException: Socket closed

and this error keep repeating
java.util.prefs.checkLockFile0ErrorCode() Could not lock User prefs. Unix error code 2.

jigasi.log:
"No ICE media stream for media: video - ignored candidates"

Thanks a lot

@driesken
Copy link
Author

driesken commented Mar 7, 2016

The error "java.util.prefs.checkLockFile0ErrorCode" appears to be caused by the home dir not being writable. Have you tried running the videobridge as root?

@hisham1402
Copy link

Hi

Thanks for your kind support, I changed the owner of /usr/share/jitsi-videobridge to jvb:jitsi
Same error, then I started jitsi-videobridge, jicofo and jigasi using root and I got same behavior: Audio OK but no video:
My installation done using quick method on ubuntu 14.04 with openJDK8
Thanks in advance

jigasi.log:
2016-03-07 15:22:48.872 INFO: [375] service.protocol.media.CallPeerMediaHandler.start().1932 Starting
(Stopped here no other log)

jvb.log:
2016-03-07 15:23:50.618 INFO: [14] org.ice4j.ice.Agent.setState() ICE state changed from Waiting to Terminated
2016-03-07 15:23:50.618 INFO: [184] org.jitsi.videobridge.IceUdpTransportManager.info() Cannot start DTLS, no sockets from ICE.

jicofo.log
Jicofo 2016-03-07 15:24:01.724 SEVERE: [93] org.jitsi.jicofo.JvbDoctor.error() Unexpected error returned by the bridge: jitsi-videobridge.myjitsi, err:

@driesken
Copy link
Author

driesken commented Mar 7, 2016

I haven't tried it on ubuntu 14.04 using the quick install (did a manual install on Centos 7), so I don't have a lot of experience with that.

You could try to do some more verbose logging?
https://github.com/jitsi/jitsi-videobridge/blob/master/lib/logging.properties

Also, you could use Wireshark to analyze the streams for the presence of video.

@hisham1402
Copy link

Thanks for your help.

I'll do fresh installation and try to start all services using root. also I'll do manual installation.

Thanks again for your valuable info.

@ogmkp
Copy link

ogmkp commented Apr 4, 2016

Hi,

I have the same issue with jvb 704.

2016-04-04 16:33:53.163 GRAVE: [902] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2016-04-04 16:33:53.164 GRAVE: [902] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@136b5a9
2016-04-04 16:33:53.164 GRAVE: [901] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@136b5a9

I can't retrieve the last working version in deb format, can you help me ?

Good luck to find a fix :)

@haocse
Copy link

haocse commented Apr 5, 2016

Same here jvb704, Ubuntu 14.04, quick install, as @maxdrash wrote.

@haocse
Copy link

haocse commented Apr 5, 2016

@hisham1402 : have you passed this issue? any suggestions, thanks.

@peererror
Copy link

I am also facing the same issue with no audio and video from sip client (linphone) .I am using opensips as sip server and also tried freeswitch but having the same problem. I have installed jitsi-meet and jigasi on same ubuntu 14.04 machine with quick installation guide.

@ibauersachs
Copy link
Member

Video with jigasi isn't supported and never was (or did I miss something there @damencho?).

@damencho
Copy link
Member

damencho commented Apr 6, 2016

Yes, that is correct. Only audio is available from jigasi deployments.

@peererror
Copy link

Oh so only audio is supported sorry for misunderstanding on my end.So then I am not hearing any audio from sip client but sip client is able to join the "siptest" room on the server .

@shock143
Copy link

shock143 commented Apr 7, 2016

Hi
I have same problem No Audio :(

@damencho
Copy link
Member

damencho commented Apr 7, 2016

I've created an issue to track update and fixing latest jigasi.
jitsi/jigasi#29
If there are comments or suggestions please feel free to step in and write in that issue.

@damencho damencho closed this as completed Apr 7, 2016
@Dzaito
Copy link

Dzaito commented Apr 11, 2016

Why this module can't support video? Can anybody help me ? Thanks.

@TheReal1604
Copy link

@damencho this is also actual for the current releases. I open another issue with logs tomorrow.

bbaldino pushed a commit to bbaldino/jitsi-videobridge that referenced this issue Jan 22, 2020
* Typo fix.

* Import libjitsi remotebitrateestimator to jmt's jitsi_modified tree.

* Adjust remotebitrateestimator to be in jmt's jitsi_modified tree.

* Use logger2 API in bandwidth estimation code.
bbaldino pushed a commit to bbaldino/jitsi-videobridge that referenced this issue Sep 24, 2020
* Typo fix.

* Import libjitsi remotebitrateestimator to jmt's jitsi_modified tree.

* Adjust remotebitrateestimator to be in jmt's jitsi_modified tree.

* Use logger2 API in bandwidth estimation code.
JonathanLennox added a commit to JonathanLennox/jitsi-videobridge that referenced this issue Jun 1, 2022
* Typo fix.

* Import libjitsi remotebitrateestimator to jmt's jitsi_modified tree.

* Adjust remotebitrateestimator to be in jmt's jitsi_modified tree.

* Use logger2 API in bandwidth estimation code.
This was referenced Jul 15, 2022
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