Hello!
20 июня 2016 г. 0:02 пользователь Philipp Hancke
написал:
>
> Am 19.06.2016 um 09:12 schrieb Kozlov Konstantin:
> > Hello!
> >
>
> typically that is done by looking at the payload type of the rtp
> packets. You could have multiple 'codecs' like rtx after all
And how can I tell FFMpeg
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 a
Hello, Florian!
19.06.2016, 11:33, "Florian Schmaus" :
> Thanks for your feedback. I've created a patch for this and issued a PR
> on github: https://github.com/xsf/xeps/pull/200
>
> Feel free to use this way in the future too. :)
Thanx, I will.
With my best regards,
On 19.06.2016 08:23, Kozlov Konstantin wrote:
> Hello!
>
> I found a minor typo in XEP-0167: Jingle RTP Sessions, section 5, example 2
> comments. Last paragraph says:
>
> In the following example, we imagine that the responder supports Speex at a
> clockrate of 8000 but not 16000, G729, and PC
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 pl
