matrix-org / matrix-org/matrix-spec
m.call.* events need a way to handle call errors (SPEC-167)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
We don't currently have any way of relaying call errors - e.g. mapping SIP or PRI error codes into Matrix events. We need an m.call.reject or similar. We also need to specify how to detail failure modes of other bits of the call lifetime.
(Imported from https://matrix.org/jira/browse/SPEC-167)
(Reported by @ara4n)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue; start by reviewing the existing m.call.* event definitions and the Matrix call-lifetime specification. Done means the specification defines an m.call.reject or equivalent, maps SIP/PRI errors into Matrix events, and describes failure modes for other call-lifetime stages.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100