You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
The problem is that mixer's URIs are indistinguishable from call's URIs, and they may both send identical events (eg output complete). We need some way to identify if the entity is a call or a mixer.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: