Difference between revisions of "Mumble"

Line 1: Line 1:
 
Since version 20220310-120737 BrandMeister Core has support of direct integration with Mumble.
 
Since version 20220310-120737 BrandMeister Core has support of direct integration with Mumble.
 +
 +
== Features and limitations ==
  
 
* 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: ''setPassword(LINK_TYPE_APPLICATION, <profile ID>, '<password>')''')
 
* 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: ''setPassword(LINK_TYPE_APPLICATION, <profile ID>, '<password>')''')
Line 10: Line 12:
 
* 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
 
* 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
 
* Bridge's transmitting party could be identified via chat message as well as bridge's contact commentary
 +
 +
== Compatibility ==
 +
 +
* Works well with native Mumble client on macOS, iOS, Linux
 +
* Doesn't work on Android with Mumla and Plumbl

Revision as of 21:26, 10 March 2022

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

Features and limitations

  • 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: setPassword(LINK_TYPE_APPLICATION, <profile ID>, '<password>')')
  • 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 ID
  • 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

Compatibility

  • Works well with native Mumble client on macOS, iOS, Linux
  • Doesn't work on Android with Mumla and Plumbl
Retrieved from "https://wiki.brandmeister.network/index.php?title=Mumble&oldid=18085"

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

Features and limitations[edit]

Compatibility[edit]