Hi

I have been trying to use the GTmurmur tool so that I can add my Mumble server to GameTracker, but following the included readme file step by step gives me a couple of errors.

Specifically, step 12 is where everything derails.
12. Execute "gtmurmur-static PATH_TO_MURMUR_SERVER/murmur.ini". Replacing
"PATH_TO_MURMUR_SERVER" with the path that you have just jotted down.

When I do that, this is what I get back:



Then I can do steps 13 through 15 with no issues.
But then at 16:
16. Execute "test_gtmurmur 1.2.3.4 27800". Replace 1.2.3.4 with the IP address
of your Murmur server.

I get a timeout error, which I'm assuming has to be a direct consequence of my failure to complete step 12.




Query port 27800 TCP is open in both Windows and router firewalls.

Mumble Server v. 1.2.3a
GTMurmur v. 1.2.0
Windows XP Professional x64


I have TeamViewer installed, so if somebody who knows their stuff would like to have a look, that can be arranged.
It's entirely plausible that I'm missing something really obvious here, I just can't spot it myself.

Try entering that address to the murmur ini file directly into windows explorer to determine if that is the correct location. It should attempt to open it.

I'd recommend reentering the path with the correct capitalization to determine if it has any impact.

burn wrote:
Try entering that address to the murmur ini file directly into windows explorer to determine if that is the correct location. It should attempt to open it.

I'd recommend reentering the path with the correct capitalization to determine if it has any impact.



As far as I know, Windows environments don't care about capitalization, and as you can see in the screenshot, explorer is able to find the path I to murmur.ini fine, even if I WrItE iT lIkE tHiS.
So when explorer comes up with auto-complete suggestions on that path, it must mean I'm pointing it to the correct directory, yes?


You think GTmurmur acts the same way, or is capitalization more important here?

Woops - it looks like their is a bug in the tutorial. For step 12, it should be:

"gtmurmur-static -conf PATH_TO_MURMUR_SERVER/murmur.ini"

I'll correct this in the next release.

maul wrote:
Woops - it looks like their is a bug in the tutorial. For step 12, it should be:

"gtmurmur-static -conf PATH_TO_MURMUR_SERVER/murmur.ini"


Yeah, at least now I get a different kind of fatal error.

Another day, another problem



But I'm using the default murmur.ini file, and from what I can understand, GTmurmur is pointed to that out of the box.
Now we "just" have some sort of socket issue on our hands.

How is the config looking for the following lines?

gtmurmur_ip=1.2.3.4
gtmurmur_port=27800

"gtmurmur_ip" can be any IP address on that machine. It works best if you use the same IP address as murmur.

"gtmurmur_port" cannot match a port already in use on that machine. It can be any number from 1025-65000. Using the murmur port + 1 makes it easy to remember.

maul wrote:
How is the config looking for the following lines?

gtmurmur_ip=1.2.3.4
gtmurmur_port=27800



gtmurmur_ip=95.154.23.142 (same as Murmur server)
gtmurmur_port=27800 (default value)

I have TCP and UDP traffic allowed on port 27800 in Windows firewall as well as the router.

Hmm, typically the "... The requested address is not valid in its context ..." error means that you are specifying an IP address that does not exist on that machine.

Can you verify that "95.154.23.142" is correct?

"ipconfig /all" will show you the available IP addresses on your machine. If "95.154.23.142" is an external IP, you will need to setup port forwarding. You can also use "gtmurmur_ip=0.0.0.0" to bind to all IP's on the machine hosting gtmurmur.

Best regards.

maul wrote:
Can you verify that "95.154.23.142" is correct?

"ipconfig /all" will show you the available IP addresses on your machine. If "95.154.23.142" is an external IP, you will need to setup port forwarding. You can also use "gtmurmur_ip=0.0.0.0" to bind to all IP's on the machine hosting gtmurmur.


95.154.23.142 is my external IP address.


I'm not interested in assigning a local address to Murmur or GTmurmur, I'd like both accessible from the web (which Murmur already is, so the port forwarding is set up correctly)

If you'd like to have a look for yourself I'm happy to use Teamviewer.
Do you use anything that supports instant messaging?
Skype, Messenger, Steam, Xfire?
Drop me a name and I will add you.

Hello,

For a variety of reasons, I do not offer support outside of GameTracker.

GTMurmur will not be able to bind to an IP address that is not hosted on the machine running it. In order to get it to work properly, you would have to bind it to a local address (e.g 192.168.1.xxx) then setup port forwarding accordingly. The port forwarding setup process should be identical to your Murmur setup, except that you'll have to add 27800 TCP.

I would imagine that you had already gone through a similar process to get Murmur working externally. GTMurmur is a server application which works in the same fashion.

Best regards.