Am 19.06.2016 um 09:12 schrieb Kozlov Konstantin:
Hello!
Just trying to implement XEP-0167: Jingle RTP Sessions in my client software.
There's something, I can't understand.
According to 5. Negotiating a Jingle RTP Session, instances should start exchange media just
after session-accept sent and acknowledged and connectivity established. To play RTP media
stream, receiving party needs SDP, which could be build, using <payload-type/> element
attributes. But session-accept stanza may have <description/> element, which contains more
than one <payload-type/> element. And it says, that any of them could be used. How
receiving party can determine, which payload type uses sending party, to generate SDP to play
media stream?
typically that is done by looking at the payload type of the rtp
packets. You could have multiple 'codecs' like rtx after all
_______________________________________________
Standards mailing list
Info: http://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
