Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSC3635: Early Media for VoIP #3635

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

MSC3635: Early Media for VoIP #3635

wants to merge 6 commits into from

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Jan 10, 2022

Rendered

Early media is essentially any media that is exchanged between the moment you start a call, to the moment the other side picks up (a connection is established). For instance, the ringing you hear while waiting for someone to pick up (called "ringback tones"), or the "busy" tone you hear when the line is busy. Those audio bits are known as "early media". Video can also fall into this category (though that's less common).

-- https://matrix.org/blog/2022/01/21/this-week-in-matrix-2022-01-21#random-msc-of-the-week

Preview: https://pr3635--matrix-org-previews.netlify.app

@dbkr dbkr added proposal-in-review proposal A matrix spec change proposal labels Jan 10, 2022
@turt2live turt2live added kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. voip labels Jan 10, 2022
This MSC proposes to allow early media in a manner similar to the gateway model above. We do this
by allowing an `m.call.negotiate` event to be sent by the callee before `m.call.answer`. The `type`
field MUST be set to `pranswer`. The caller should ignore `m.call.negotiate` events before
of any other type before the `m.call.answer`. Clients using WebRTC compatible APIs should imply

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The caller should ignore m.call.negotiate events before
of any other type before the m.call.answer."

I dont understand the meaning of this this sentence. Should it be callee? Does it refer to clients not having implemented this spec?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there was just an extra word in there - the caller should be throwing away any negotiate events that come before an answer if they're not of type pranswer.

Co-authored-by: opusforlife2 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal voip
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants