Difference between revisions of "Mumble"

Revision as of 13:57, 10 March 2022

Since version 20220310-120737 BrandMeister Core has support of direct integration with Mumble.

BrandMeister uses name 'bridge-<profile ID>' and server password for authentication (non-default password has to be registered in the Registry on a standard way for applications)
Only TG bridging is supported, each TG has to be associated with a Mumble channel
Users may have user name in format '[<call-sign>]-[<DMR ID>]' (configurable), user name is used to map Mumble caller to DMR
AMBE codec is required on the DMR side, Opus codec is only supported on the Mumble side
Mumble client should use Opus and 20 ms (default) / 40 ms / 60 ms buffer
It is strongly recommended to use PTT mode and not VOX
Due to radio-specific identification, BrandMeister passes only first-come call, when multiple Mumble users are transmitting (no mix-down)
When BrandMeister cannot recognise DMR ID / call from the user name, TG ID will be used, Mumble user name will be passed as a talker alias
Bridge's transmitting party could be identified via chat message as well as bridge's contact commentary

@@ Line 7: / Line 7: @@
 * Mumble client should use Opus and 20 ms (default) / 40 ms / 60 ms buffer
 * It is strongly recommended to use PTT mode and not VOX
-* Due to radio-specific identification, BrandMeister passed only first-come call, when multiple Mumble users are transmitting (no mix-down)
+* Due to radio-specific identification, BrandMeister passes only first-come call, when multiple Mumble users are transmitting (no mix-down)
 * When BrandMeister cannot recognise DMR ID / call from the user name, TG ID will be used, Mumble user name will be passed as a talker alias
 * Bridge's transmitting party could be identified via chat message as well as bridge's contact commentary