OpenSimulator · EN

Private calls, group voice and AdHoc conferences

Understand features, dependencies and the central PHP/MySQL service.

This documents one specific WebRTC stack. Respect compatible versions and consult linked sources before modifying a production deployment.

Official repositories and downloads

Three distinct components: voice server, simulator modules, and optional ad hoc conferences. Use versions compatible with your installation.

BloodMoon Voice — voice serverRelease v1.0.0 and installer
OpenSimulator WebRTC modulesRelease v0.9.3.1-webrtc.3, DLL/PDB ZIP
OpenSimulator AdHoc ConferencesPHP/MySQL source and installation guide

Spatial voice

Two avatars on a voice-enabled parcel can use spatial 3D audio. If voice is disabled by estate or parcel settings, the viewer may not request voice even when the WebRTC server is healthy.

Private IM calls

A private voice call started from IM uses the voice server and compatible region modules. Test both directions and verify returning to local voice after hanging up.

Existing OpenSimulator group voice

Standard group calls can use voice with the appropriate release modules. This differs from AdHoc conferences, which do not require creating a persistent group.

Why AdHoc requires a third component

Cross-simulator multi-avatar text conferences need membership and invitation/message routing. The central PHP/MySQL registry in OpenSimulator-AdHocConferences provides this; the WebRTC server alone is insufficient.

Independent API setup

The AdHoc repository provides database/wolf_schema.sql, web/wolf_api.php and web/wolf_config.php.example. Independent installs should choose authorization_source=local and trusted egress IPs. bloodmoon_db relies on a BloodMoon-specific table and is not a general requirement.

Configure every participating simulator

Once YOUR own HTTPS API is installed, set ConferenceApiUrl on every simulator participating in conferences. Do not reuse the BloodMoon production endpoint or publish keys. The API rejects unauthorized simulators.

Example for your own installation: adapt all domains, paths and names.

[WebRtcVoice]
ConferenceApiUrl = https://conference.example.org/adhocconf/wolf_api.php

Full validation scenario

Test a three-avatar conference with at least one avatar on a different simulator: invitations, text, late joining, optional voice, participant volumes, hanging up without closing IM, and rejoining.

Further reading and sources