We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
extmap
While doing a RTP call, Movim being the initiator, if the other peer send XEP-0294 <rtp-hdrext> elements like those:
<rtp-hdrext>
<rtp-hdrext xmlns="urn:xmpp:jingle:apps:rtp:rtp-hdrext:0" id="1" uri="urn:ietf:params:rtp-hdrext:ssrc-audio-level" senders="both"/> <rtp-hdrext xmlns="urn:xmpp:jingle:apps:rtp:rtp-hdrext:0" id="3" uri="urn:ietf:params:rtp-hdrext:sdes:mid" senders="both"/>
Movim convert it to following SDP:
a=extmap:1 both urn:ietf:params:rtp-hdrext:ssrc-audio-level a=extmap:3 both urn:ietf:params:rtp-hdrext:sdes:mid
This is invalid and result in failed call:
senders
direction
/
Reference: https://datatracker.ietf.org/doc/html/rfc8285#section-8
Tested with Movim v0.21rc7
The text was updated successfully, but these errors were encountered:
Fixed in b5b7aa0
Sorry, something went wrong.
edhelas
No branches or pull requests
While doing a RTP call, Movim being the initiator, if the other peer send XEP-0294
<rtp-hdrext>
elements like those:Movim convert it to following SDP:
This is invalid and result in failed call:
senders
value is used directly while it should be mapped to adirection
value ("sendonly", "recvonly", "sendrecv", or "inactive"). This is most probably related to Movim is sending incorrect value in 'senders' attribute of XEP-0294 #1212/
Reference: https://datatracker.ietf.org/doc/html/rfc8285#section-8
Tested with Movim v0.21rc7
The text was updated successfully, but these errors were encountered: