Advertisement
ouissla

Alternate Jibri config

Apr 15th, 2020
272
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
JSON 2.94 KB | None | 0 0
  1. {
  2.     // Where recording files should be temporarily stored
  3.     "recording_directory":"/srv/recordings",
  4.     // The path to the script which will be run on completed recordings
  5.     "finalize_recording_script_path": "/home/ubuntu/finalize_recording.sh",
  6.     "xmpp_environments": [
  7.         {
  8.             // A friendly name for this environment which can be used
  9.             //  for logging, stats, etc.
  10.             "name": "docker environment",
  11.             // The hosts of the XMPP servers to connect to as part of
  12.             //  this environment
  13.             "xmpp_server_hosts": [
  14.                 "meet.mydomain.com"
  15.             ],
  16.             // The xmpp domain we'll connect to on the XMPP server
  17.             "xmpp_domain": "meet.mydomain.com",
  18.             // Jibri will login to the xmpp server as a privileged user
  19.             "control_login": {
  20.                 // The domain to use for logging in
  21.                 "domain": "auth.meet.mydomain.com",
  22.                 // The credentials for logging in
  23.                 "username": "jibri",
  24.                 "password": "jibriauthpass"
  25.             },
  26.             // Using the control_login information above, Jibri will join
  27.             //  a control muc as a means of announcing its availability
  28.             //  to provide services for a given environment
  29.             "control_muc": {
  30.                 "domain": "internal.auth.meet.mydomain.com",
  31.                 "room_name": "JibriBrewery",
  32.                 "nickname": "jibri-docker-1"
  33.             },
  34.             // All participants in a call join a muc so they can exchange
  35.             //  information.  Jibri can be instructed to join a special muc
  36.             //  with credentials to give it special abilities (e.g. not being
  37.             //  displayed to other users like a normal participant)
  38.             "call_login": {
  39.                 "domain": "recorder.meet.mydomain.com",
  40.                 "username": "recorder",
  41.                 "password": "jibrirecorderpass"
  42.             },
  43.         // When jibri gets a request to start a service for a room, the room
  44.             //  jid will look like:
  45.             //  roomName@optional.prefixes.subdomain.xmpp_domain
  46.             // We'll build the url for the call by transforming that into:
  47.             //  https://xmpp_domain/subdomain/roomName
  48.             // So if there are any prefixes in the jid (like jitsi meet, which
  49.             //  has its participants join a muc at conference.xmpp_domain) then
  50.             //  list that prefix here so it can be stripped out to generate
  51.             //  the call url correctly
  52.             "room_jid_domain_string_to_strip_from_start": "conference.",
  53.             // The amount of time, in minutes, a service is allowed to continue.
  54.             //  Once a service has been running for this long, it will be
  55.             //  stopped (cleanly).  A value of 0 means an indefinite amount
  56.             //  of time is allowed
  57.             "usage_timeout": "0"
  58.         }
  59.     ]
  60. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement