wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarifications that room invites are m.call.invites not actual invites

Browse source
This commit is contained in:
Kegan Dougal 2015-10-01 11:11:08 +01:00
parent e82661413e
commit 3b73b07bab
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
specification/modules/voip_events.rst
View file

@ -60,14 +60,14 @@ As calls are "placed" to rooms rather than users, the glare resolution algorithm
outlined below is only considered for calls which are to the same room. The outlined below is only considered for calls which are to the same room. The
algorithm is as follows: algorithm is as follows:
- If an invite to a room is received whilst the client is **preparing to send** - If an ``m.call.invite`` to a room is received whilst the client is
an invite to the same room: **preparing to send** an ``m.call.invite`` to the same room:
* the client should cancel its outgoing call and instead * the client should cancel its outgoing call and instead
automatically accept the incoming call on behalf of the user. automatically accept the incoming call on behalf of the user.
- If an invite to a room is received **after the client has sent** an invite to - If an ``m.call.invite`` to a room is received **after the client has sent**
the same room and is waiting for a response: an ``m.call.invite`` to the same room and is waiting for a response:
* the client should perform a lexicographical comparison of the call IDs of * the client should perform a lexicographical comparison of the call IDs of
the two calls and use the *lesser* of the two calls, aborting the the two calls and use the *lesser* of the two calls, aborting the
@ -83,9 +83,9 @@ replaces it.
Server behaviour Server behaviour
---------------- ----------------
The server MAY provide a TURN server which clients can use to contact the The homeserver MAY provide a TURN server which clients can use to contact the
remote party. This server should be accessible via the HTTP endpoint listed remote party. The following HTTP API endpoints will be used by clients in order
below. to get information about the TURN server.
{{voip_http_api}} {{voip_http_api}}