Statistics
| Branch: | Revision:

janus-gateway / conf / janus.transport.rabbitmq.cfg.sample @ 88b5da7b

History | View | Annotate | Download (2.25 KB)

1
; Configuration of the RabbitMQ additional transport for the Janus API.
2
; This is only useful when you're wrapping Janus requests in your server
3
; application, and handling the communication with clients your own way.
4
; At the moment, only a single "application" can be handled at the same
5
; time, meaning that Janus won't implement multiple queues to handle
6
; multiple concurrent "application servers" taking advantage of its
7
; features. Support for this is planned, though (e.g., through some kind
8
; of negotiation to create queues on the fly). Right now, you can only
9
; configure the address of the RabbitMQ server to use, and the queues to
10
; make use of to receive (to-janus) and send (from-janus) messages
11
; from/to an external application. If you're using the same RabbitMQ
12
; server instance for multiple Janus instances, make sure you configure
13
; different queues for each of them (e.g., from-janus-1/to-janus-1 and
14
; from-janus-2/to-janus-2), or otherwise both the instances will make
15
; use of the same queues and messages will get lost. The integration
16
; is disabled by default, so set enable=yes if you want to use it.
17
[general]
18
enable = no					; Whether the support must be enabled
19
json = indented				; Whether the JSON messages should be indented (default),
20
							; plain (no indentation) or compact (no indentation and no spaces)
21
host = localhost			; The address of the RabbitMQ server
22
;port = 5672				; The port of the RabbitMQ server (5672 by default)
23
;username = guest			; Username to use to authenticate, if needed
24
;password = guest			; Password to use to authenticate, if needed
25
;vhost = /					; Virtual host to specify when logging in, if needed
26
to_janus = to-janus			; Name of the queue for incoming messages
27
from_janus = from-janus		; Name of the queue for outgoing messages
28

    
29
; If you want to expose the Admin API via RabbitMQ as well, you need to
30
; specify a different set of queues, as you cannot mix Janus API and
31
; Admin API messaging. The same RabbitMQ server is supposed to be used.
32
; Notice that by default the Admin API support via RabbitMQ is disabled.
33
[admin]
34
;admin_enable = no						; Whether the support must be enabled
35
;to_janus_admin = to-janus-admin		; Name of the queue for incoming messages
36
;from_janus_admin = from-janus-admin	; Name of the queue for outgoing messages