I created a VM and installed Mumble's Murmur server. Pretty simple install. Works fine on the LAN and with other mumble servers such as my commercial instance at mumble.com. I want a backup server in the event that MUMBLE.COM has an outage.
The Azure Control Panel shows
.. the mumble port is 64738
I have the firewall open for murmur.exe on inbound and outbound public and private.
Is there a step I am missing to get the outside world to be allowed to see this Azure VM and the MURMUR.EXE process running on it.
Here is what I get on the client side when I point the client to 191.238.51.219:64738
[12:20:04 AM] Server connection failed: Connection timed out.
[12:20:14 AM] Reconnecting.
[12:20:44 AM] Server connection failed: Connection timed out.
[12:20:54 AM] Reconnecting.
Thanks!
One More Thing: Here is the server side mumble log:
<W>2014-02-19 06:27:07.062 Initializing settings from C:/Program Files (x86)/Mumble/murmur.ini (basepath C:/Program Files (x86)/Mumble)<W>2014-02-19 06:27:07.062 OpenSSL: OpenSSL 1.0.0l 6 Jan 2014
<W>2014-02-19 06:27:07.078 ServerDB: Opened SQLite database C:/Program Files (x86)/Mumble/murmur.sqlite
<W>2014-02-19 06:27:07.078 Meta: Failed to load qWave.dll, no QoS available
<W>2014-02-19 06:27:07.078 Murmur 1.2.5 (1.2.5) running on Win: 6.2.9200.0: Booting servers
<W>2014-02-19 06:27:07.169 1 => Server listening on [::]:64738
<W>2014-02-19 06:27:07.263 1 => Server listening on 0.0.0.0:6473
<W>2014-02-19 06:27:07.263 Bonjour: Failed to load dnssd.dll
<W>2014-02-19 06:27:07.359 1 => Not registering server as public
[note don't let that last line fool you.. that is a registration to a list of public mumble servers and nothing related to this instance or VM]