forked from restitux/mumble-wiki-export
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Channel_Viewer_Protocol.txt
450 lines (381 loc) · 17.6 KB
/
Channel_Viewer_Protocol.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
People often wish to have a view on their Mumble servers without needing to actually
run the client. This is mostly accomplished using a web based channel viewer which
retrieves channel and user data from a web server, which in turn queries it from
Murmur, and then using techniques like JavaScript to render that data into a nice
tree structure.
As multiple channel viewers started to arise, developers found the consensus that
using a standardized format for data retrieval yields multiple advantages, the most
important of which is interoperability: The need for using a specific server and
viewer does not arise when all servers and viewers use a shared data format, thus
allowing for both parts to be exchanged easily and independent from one another.
A good example implementation is [[Mumble reader]], written in PHP and JQuery. It uses IcePHP to query Murmur via [[Ice]] and generate the Channel Viewer Protocol JSON data, which the JQuery front-end reads and formats into the channel viewer itself. The Ice query code only works with IcePHP versions earlier than 3.4, although other query services can be read by its JQuery front-end.
== General notes ==
=== Data integrity ===
The data format should generally be aimed towards delivering information retrieved
from Murmur unaltered. That means that any field that exists in Murmur should be
exposed by the server (unless there is a really good reason not to do so, like for
passwords and the like), and it should not alter any fields that exist in Murmur
to prevent confusion.
=== Custom data fields ===
If the implementer of the protocol chooses to add extra information that does not
originate from Murmur itself, these fields should be prefixed with "x_" in order
to prevent name clashes (so for example, a custom field named "coolstuff" should
be named "x_coolstuff" instead).
If a client encounters a field which it does not understand, it must ignore that
field.
=== Empty fields ===
In general, empty fields should be treated as if they would not have been set at
all. This means that a client should not rely on that a field that exists actually
has a usable value.
=== Encoding ===
The documents, be it JSON or XML, should be encoded in UTF-8 in order to be as
easily usable as possible. Servers must set their encoding headers correctly to
prevent encoding issues.
=== The Address field ===
The address field in the user records requires special attention for multiple reasons.
* To respect users' privacy, user records should generally not contain the address if the request does not provide any means of authentication. What kind of authentication the client needs to provide is a bit hard to say; a compromise between security and ease of implementation (both client- and server side) is to accept both...
** the standard authentication means of the platform the server is implemented in; that means if your server implementation uses a web framework, its built-in authentication (e.g. through cookies) should be accepted. This way, web based clients will support authentication without any further modification.
** HTTP Basic auth if no other authentication data has been provided, to enable non-web-based clients to retrieve the address information if they need to.
* To ease client implementation, the server should set the "x_addrstr" field to a string that contains either...
** a fully qualified domain name: "somewhere.example.com".
** an IPv4 address in dotted quad notation: "192.168.0.1".
** an IPv6 address in colon notation: "2001:6f8:108f:1:21f:3cff:wx:yz".
Note however that in most cases, the users' addresses will not even be needed by the
client, so most of this shouldn't even apply to most clients.
If a server does not support delivering users' addresses at all, it should just ignore
any authentication data the client may have sent.
== Example Channel tree ==
All examples are based on the following channel structure:
* test server
** newtesting
** testing
*** htmlsubtesting - This channel has HTML elements in its description
**** subsubtesting
*** plainsubtesting - This channel has HTML elements in its description which are escaped and should NOT be evaluated
**** subsubtesting
== JSON ==
To expose the full channel tree using JSON, start with the root channel and
recursively add the users and data to it.
In order to make cross-site requests easier, the server must implement
[http://bob.pythonmac.org/archives/2005/12/05/remote-json-jsonp/ JSONP].
The name for the request parameter that holds the callback name must be
"callback". If this parameter is not specified, the server must not wrap
the JSON in parenthesis to ensure compatibility with e.g. Python's
simplejson.
=== Server format ===
The root object of the tree must always be the server itself, which has
the following properties:
'id': 1, // The ID of this server instance
'name': 'some name', // The server's name
'root': {...}, // The root channel object
And may optionally have:
'x_connecturl': 'mumble://somewhere/'
'x_uptime': 7156 // The number of seconds this server has been running
=== Channel format ===
A Channel entry must at least contain the following fields:
'description': '',
'id': 0,
'links': [], // A list of IDs that name linked channels
'name': 'Root',
'parent': -1,
'users': [], // A list of users in this channel
'position': 0,
'channels': [], // A list of subchannels
'temporary': false
And may optionally contain:
'x_connecturl': 'mumble://somewhere/somechannel'
=== User format ===
A User entry must at least contain the following fields:
'channel': 40,
'deaf': false,
'mute': false,
'name': 'Yps0',
'selfDeaf': false,
'selfMute': false,
'session': 143,
'suppress': false,
'userid': 4,
And may optionally contain:
'address': (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 192, 168, 0, 10),
'x_addrstring': '192.168.0.10', // A nicely formatted version of the IP address (hostname, dotted quad, IPv6 notation)
'recording': false,
'bytespersec': 6580,
'comment': '',
'context': '',
'identity': '',
'idlesecs': 0,
'onlinesecs': 161,
'os': 'Win',
'osversion': '5.1.2600.1',
'prioritySpeaker': false,
'release': '02071e',
'tcponly': false,
'x_texture': 'http://shotgunfun.de/mumble/1/4/texture.png', // A URL to retrieve the texture/avatar from
'version': 66051
Which fields to expose may depend on the user of the channel viewer, e.g. the IP adress
may be shown to certain logged-in users only.
=== Full Example: JSON ===
Serializing the aforementioned channel structure as JSON, we will get:
{
"x_connecturl": "mumble://kuunavang.funzt-halt.net?version=1.2.2",
"x_uptime": 53289,
"root": {
"channels": [
{
"channels": [],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/newtesting?version=1.2.2",
"temporary": false,
"description": "",
"parent": 0,
"position": 0,
"users": [],
"name": "newtesting",
"links": [],
"id": 6
},
{
"channels": [
{
"channels": [
{
"channels": [],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/testing/htmlsubtesting%20%C3%B6%C3%A4%C3%BC/subsubtesting?version=1.2.2",
"temporary": false,
"description": "",
"parent": 4,
"position": 0,
"users": [],
"name": "subsubtesting",
"links": [],
"id": 5
}
],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/testing/htmlsubtesting%20%C3%B6%C3%A4%C3%BC?version=1.2.2",
"temporary": false,
"description": "This channel has <i>HTML</i> elements in its description that are evaluated as <span style=\"color:#ff0000\">red </span><b><span style=\"color:#ff0000\">bold</span></b> Fonts!",
"parent": 1,
"position": 0,
"users": [
{
"comment": "",
"mute": false,
"suppress": false,
"selfDeaf": false,
"x_addrstring": "2001:6f8:108f:1:21f:3cff:wx:yz",
"deaf": false,
"selfMute": true,
"bytespersec": 0,
"session": 1,
"tcponly": false,
"address": [ 32, 1, 6, 248, 16, 143, 0, 1, 2, 31, 60, 255, w, x, y, z ],
"idlesecs": 33,
"identity": "",
"name": "svedrin",
"userid": 1,
"version": 66050,
"context": "",
"release": "1.2.2-2",
"osversion": "Debian GNU/Linux unstable (sid)",
"os": "X11",
"onlinesecs": 35,
"channel": 4
}
],
"name": "htmlsubtesting \u00f6\u00e4\u00fc",
"links": [
2
],
"id": 4
},
{
"channels": [
{
"channels": [],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/testing/plainsubtesting/subsubtesting?version=1.2.2",
"temporary": false,
"description": "",
"parent": 2,
"position": 0,
"users": [],
"name": "subsubtesting",
"links": [],
"id": 3
}
],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/testing/plainsubtesting?version=1.2.2",
"temporary": false,
"description": "This channel has <i>HTML</i> elements in its description that are not evaluated as <span style="color: red">red <b>bold</b></span> Fonts!",
"parent": 1,
"position": 0,
"users": [],
"name": "plainsubtesting",
"links": [
4
],
"id": 2
}
],
"x_connecturl": "mumble://kuunavang.funzt-halt.net/testing?version=1.2.2",
"temporary": false,
"description": "",
"parent": 0,
"position": 0,
"users": [],
"name": "testing",
"links": [],
"id": 1
}
],
"x_connecturl": "mumble://kuunavang.funzt-halt.net?version=1.2.2",
"temporary": false,
"description": "",
"parent": -1,
"position": 0,
"users": [],
"name": "Root",
"links": [],
"id": 0
},
"name": "test server",
"id": 1
}
== XML ==
For XML, the same principles apply as for JSON, along with the following encoding principles:
* Boolean values are represented as "true" or "false"
* Lists (e.g. for the players' IP addresses or the channel links) are space-separated numbers
The root element (<tt><server></tt>) should set the following namespace attributes:
* xmlns="http://mumble.sourceforge.net/Channel_Viewer_Protocol"
* xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
* xsi:schemaLocation="http://bitbucket.org/Svedrin/mumble-django/wiki/channel-viewer-protocol_murmur-X-Y-Z.xsd" with X.Y.Z being the version of Murmur that the data in this document originates from.
As XML Schema Definitions need to be adapted to match the fields returned by Murmur,
including the correct Murmur version in the URL is important to enable a correct
validation. Currently, the following XSD documents are available:
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Murmur Version
! XSD URL
|-
| 1.2.2
| http://bitbucket.org/Svedrin/mumble-django/wiki/channel-viewer-protocol_murmur-1-2-2.xsd
|-
| 1.2.3
| http://bitbucket.org/Svedrin/mumble-django/wiki/channel-viewer-protocol_murmur-1-2-3.xsd
|}
=== Server Format ===
A server is represented using the <tt><server /></tt> tag.
=== Channel Format ===
A channel is represented using the <tt><channel /></tt> tag.
=== User Format ===
A user is represented using the <tt><user /></tt> tag.
'''Warning''': Mumble includes NULL bytes in the ''context'' field, so the context field - if not empty - must be base64 encoded.
=== Full Example: XML ===
<?xml version="1.0" encoding="UTF-8" ?>
<server
xmlns="http://mumble.sourceforge.net/Channel_Viewer_Protocol"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation="http://bitbucket.org/Svedrin/mumble-django/wiki/channel-viewer-protocol_murmur-1-2-3.xsd"
id="1"
name="test server"
x_connecturl="mumble://kuunavang.funzt-halt.net?version=1.2.2">
<channel
description=""
id="0"
links=""
name="Root"
parent="-1"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net?version=1.2.2">
<channel
description=""
id="6"
links=""
name="newtesting"
parent="0"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/newtesting?version=1.2.2" />
<channel
description=""
id="1"
links=""
name="testing"
parent="0"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/testing?version=1.2.2">
<channel
description="This channel has <i>HTML</i> elements in its description that are evaluated as <span style=&quot;color:#ff0000&quot;>red </span><b><span style=&quot;color:#ff0000&quot;>bold</span></b> Fonts!"
id="4"
links="2"
name="htmlsubtesting"
parent="1"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/testing/htmlsubtesting?version=1.2.2">
<channel
description=""
id="5"
links=""
name="subsubtesting"
parent="4"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/testing/htmlsubtesting/subsubtesting?version=1.2.2" />
<user
address="32 1 6 248 16 143 0 1 2 31 60 255 w x y z"
bytespersec="0"
channel="4"
comment=""
context="QmF0dGxlZmllbGQgQmFkIENvbXBhbnkgMgA= "
deaf="false"
identity=""
idlesecs="1693"
mute="false"
name="svedrin"
onlinesecs="2943"
os="X11"
osversion="Debian GNU/Linux unstable (sid)"
release="1.2.2-2"
selfDeaf="false"
selfMute="false"
session="7"
suppress="false"
tcponly="false"
userid="1"
version="66050"
x_addrstring="2001:6f8:108f:1:21f:3cff:wx:yz" />
</channel>
<channel
description="This channel has &lt;i&gt;HTML&lt;/i&gt; elements in its description that are not evaluated as &lt;span style=&quot;color: red&quot;&gt;red &lt;b&gt;bold&lt;/b&gt;&lt;/span&gt; Fonts!"
id="2"
links="4"
name="plainsubtesting"
parent="1"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/testing/plainsubtesting?version=1.2.2">
<channel
description=""
id="3"
links=""
name="subsubtesting"
parent="2"
position="0"
temporary="false"
x_connecturl="mumble://kuunavang.funzt-halt.net/testing/plainsubtesting/subsubtesting?version=1.2.2" />
</channel>
</channel>
</channel>
</server>
== Existing Implementations ==
A number of implementations exist already, which one you choose depends mostly on your needs. If you only want a channel viewer and no administration capabilities, you might want to go with [http://code.google.com/p/mumblereader/ MumbleReader]. For a full-featured web administration interface that also features CVP, check out [[Mumble-Django]] or [[Mumble_PHP_Interface|MumPI]].
More information is to be found on the [[3rd Party Applications#Channel_Viewers|3rd Party Applications]] page.
== Authors and Contact ==
This standard has been written based on the consensus made on [[IRC]]: #mumble on irc.freenode.net.
Main authors:
* Michael "Svedrin" Ziegler <diese-addy@funzt-halt.net>
* Pimmetje
* S_Roach
If you wish to discuss parts of this standard or help maintaining it, you should join the [[IRC]]
channel or send a mail to Svedrin.
[[Category:Documentation English]]