Simulator configuration: wolfvoice.ini
Exact file location, DLL modules, shared keys, security and verification on every region.
Official repositories and downloads
Three distinct components: voice server, simulator modules, and optional ad hoc conferences. Use versions compatible with your installation.
Personal file bin/config/wolfvoice.ini
The documented module setup uses bin/config/wolfvoice.ini, read as an override after OpenSim.ini. If one simulator process hosts several regions, the WebRTC enable flag may affect every region in that process.
Install all three matching DLL/PDB pairs
For a fresh installation, copy WebRtcVoice.dll/.pdb, WebRtcVoiceRegionModule.dll/.pdb and WebRtcVoiceServiceModule.dll/.pdb from the v0.9.3.1-webrtc.3 ZIP. Keep versions matched; never replace its included AdHoc module with an older standalone DLL.
Transfer the same keys, do not generate new ones
Privately distribute the server's two key files to authorized simulator hosts. When key paths are relative, start OpenSimulator from its bin directory. Restrict file permissions to the service account and never publish keys.
Fresh-install INI example
Use your own TLS DNS hostname rather than a raw IP. Two-key mode requires both RpcKeyFile and CredKeyFile. example.org URLs are placeholders. Configure the AdHoc API URL only after deploying your own conference service.
Example for your own installation: adapt all domains, paths and names.
[WebRtcVoice] Enabled = true SpatialVoiceService = WebRtcVoice.dll:WebRtcVoiceServiceConnector NonSpatialVoiceService = WebRtcVoice.dll:WebRtcVoiceServiceConnector WebRtcVoiceServerURI = https://voice.example.org:9443 RpcKeyFile = voice_rpc_key CredKeyFile = voice_cred_key MessageDetails = false StunServers = stun:stun.l.google.com:19302,stun:stun1.l.google.com:19302 ; ConferenceApiUrl = https://conference.example.org/adhocconf/wolf_api.php [VivoxVoice] enabled = false
Why disable Vivox
Both voice modules may register the same capability. In the documented setup, [VivoxVoice] enabled=false avoids this conflict. Voice must also be allowed on the estate and parcel for the viewer to request a connection.
BloodMoon legacy mode: one key and IP allowlist
A previously validated BloodMoon deployment uses a credential key and an IP allowlist. Do not convert it to two-key mode without coordinating every simulator: a server enforcing rpc_key rejects older region modules that cannot send it.
No Janus gateway required
The WebRtcVoice service connector talks to the BloodMoon voice backend. No separate Janus server is needed for this system.