WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.
This repository was archived by the owner on May 6, 2020. It is now read-only.

Entity capabilities and mixer/call presence #65

@crienzo

Description

@crienzo

Issue #48 added entity capabilities to rayo presence events so that mixers and calls can be identified as such.

The rayo spec says to use the node to identify the entity as either a mixer or call, however XEP-0115 says the node is supposed to identify the software application, preferably a URI. Furthermore, a disco is to be performed to actually determine the capabilities of the entity.

I'm not sure why this is needed for calls. The fact that only calls send offer and the offer is in the rayo namespace should be enough to figure out the presence is from a call. Maybe the dial case was more problematic?

Similarly, with mixers, you see a mixer-name in the joined event which tells you that the presence is from a mixer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions