Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-01-01 21:48:37 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Fix type of other version fields, fix anchor.

Browse source
This commit is contained in:
David Baker 2023-05-04 12:20:53 +01:00
parent e741e3a7af
commit a7f5b8f8f4
7 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/client-server-api/modules/voip_events.md
View file

@ -39,7 +39,7 @@ or it may choose, for example, to use a different one for each call to avoid lea
devices were used in a call (in an unencrypted room) or if a single device (ie. access token) were used to
send signalling for more than one call party.
A grammar for `party_id` is defined [below](#specify-exact-grammar-for-voip-ids).
A grammar for `party_id` is defined [below](#grammar-for-voip-ids).
#### Politeness
In line with WebRTC perfect negotiation (https://w3c.github.io/webrtc-pc/#perfect-negotiation-example)

2
data/event-schemas/schema/m.call.answer.yaml
View file

@ -30,7 +30,7 @@
"required": ["type", "sdp"]
},
"version": {
"type": "number",
"type": "string",
"description": "The version of the VoIP specification this message adheres to. This specification is version 1. This field is a string such that experimental implementations can use non-integer versions. This field was an integer in the previous spec version and implementations must accept an integer 0"
},
"party_id": {

2
data/event-schemas/schema/m.call.candidates.yaml
View file

@ -40,7 +40,7 @@
"description": "This identifies the party that sent this event. A client may choose to re-use the device ID from end-to-end cryptography for the value of this field. "
},
"version": {
"type": "integer",
"type": "string",
"description": "The version of the VoIP specification this message adheres to. This specification is version 1. This field is a string such that experimental implementations can use non-integer versions. This field was an integer in the previous spec version and implementations must accept an integer 0."
}
},

2
data/event-schemas/schema/m.call.hangup.yaml
View file

@ -30,7 +30,7 @@ properties:
type: string
description: The ID of the call this event relates to.
version:
type: integer
type: string
description: The version of the VoIP specification this message adheres to.
This specification is version 1. This field is a string such that experimental
implementations can use non-integer versions. This field was an integer

2
data/event-schemas/schema/m.call.negotiate.yaml
View file

@ -44,7 +44,7 @@ properties:
type: string
description: The ID of the call this event relates to.
version:
type: integer
type: string
description: The version of the VoIP specification this message adheres to.
This specification is version 1. This field is a string such that experimental
implementations can use non-integer versions. This field was an integer

2
data/event-schemas/schema/m.call.reject.yaml
View file

@ -22,7 +22,7 @@ properties:
type: string
description: The ID of the call this event relates to.
version:
type: integer
type: string
description: The version of the VoIP specification this message adheres to.
This specification is version 1. This field is a string such that experimental
implementations can use non-integer versions. This field was an integer

2
data/event-schemas/schema/m.call.select_answer.yaml
View file

@ -13,7 +13,7 @@
"description": "The ID of the call this event relates to."
},
"version": {
"type": "integer",
"type": "string",
"description": "The version of the VoIP specification this message adheres to. This specification is version 1. This field is a string such that experimental implementations can use non-integer versions. This field was an integer in the previous spec version and implementations must accept an integer 0."
},
"party_id": {