fstinglmayr Posted December 26, 2010 Share Posted December 26, 2010 Hello all,Sorry if I didn't hit the right forum though, but: I have been trying to setup a rather private mumble server for days now, but whoever connects cannot talk to each other. I opened both TCP and UDP port 64738 on the server, and the client application can connect just fine. People can send messages to each other, and create temporary rooms. But when ever one tries to speak no one else hears him; even the little mouth does not go red in the user list.I'm running murmur 1.2.2 on debian 64bit, on 85.126.82.84 on the default port, password is "test" if you want to checkout the installation.I have tried with two Linux clients (Fedora 14) and one Windows client. No one can talk to one another and all get the same message: [13:21] Unable to find matching CELT codecs with other clients. You will not be able to talk to all users. Anyone got any idea? Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted December 26, 2010 Administrators Share Posted December 26, 2010 With that error, check your clients codecs.Rightclick user -> information.Celt versions are listed.When alone I can talk on that srv. Quote Link to comment Share on other sites More sharing options...
fstinglmayr Posted December 26, 2010 Author Share Posted December 26, 2010 Stupid question, but if you are alone, how can you tell that someone else would receive it?Aye, and the celt versions between the two Fedora machines is exactly the same... Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted December 26, 2010 Administrators Share Posted December 26, 2010 I didn’t say others would be able to hear it. :)Just that it’s not a mute-/speakperm-issue.The celt version mumble displays are the same and they can't talk with each other when only those 2 are in one channel?And then that error is logged? Quote Link to comment Share on other sites More sharing options...
fstinglmayr Posted December 26, 2010 Author Share Posted December 26, 2010 Ah okay :)No the error is logged to both clients when they connect initially. Both have the same versions but they can't hear each other talk. I get no error, I checked the fire wall settings twice... Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted December 27, 2010 Administrators Share Posted December 27, 2010 So you are in the same channel when they get the log msg?Make sure those 2 are by themselves in a channel, so other codecs/clients (yours) won't influence codec-decisions. Quote Link to comment Share on other sites More sharing options...
Moderators pcgod Posted December 27, 2010 Moderators Share Posted December 27, 2010 Afaik the Fedora package has Mumble 1.2.2 and CELT 0.8.1. That will not work, 1.2.2 supports 0.7.x only (the API changed between 0.7.x and 0.8.x), but that's a Fedora packaging problem... Quote Link to comment Share on other sites More sharing options...
fstinglmayr Posted December 27, 2010 Author Share Posted December 27, 2010 Afaik the Fedora package has Mumble 1.2.2 and CELT 0.8.1. That will not work, 1.2.2 supports 0.7.x only (the API changed between 0.7.x and 0.8.x), but that's a Fedora packaging problem... That is of course very interesting. Does the current unstable of mumble 1.2.3 support CELT 0.8.1? Or should I remove the celt packages and install 0.7.X by hand? Quote Link to comment Share on other sites More sharing options...
Administrators kissaki Posted December 28, 2010 Administrators Share Posted December 28, 2010 Current unstable (snapshots) include 0.7.0, 0.9.0,. 0.10.0 on windows. Not sure about centos.0.7 is always the fallback for mumble, as that was the first celt included in 1.2.x.So installing 0.7 should at least allow talking with each other, while it may be inferior to using a newer codec version. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.