I'm currently using version 1.0-beta1-nightly.build.3820. When a SIP call is setup with a dynamically assigned payload type (>96), Jitsi sends its RTP packets with its local payload type, instead of using the remote payload type, as should be.
Is that a bug which has already been fixed, or should I file it?
I'm currently using version 1.0-beta1-nightly.build.3820. When a SIP
call is setup with a dynamically assigned payload type (>96), Jitsi
sends its RTP packets with its local payload type, instead of using
the remote payload type, as should be.
Is that a bug which has already been fixed, or should I file it?
It's a known issue and we currently have it under #1006 :
Just a quick followup question: does that mean that if I send the SDP offer to Jitsi, it will reply with the same payload type mapping?
-Raphael.
···
On 02.03.2012, at 15:47, Emil Ivov wrote:
Hey Raphael,
On 02.03.12 16:22, Raphael Coeffic wrote:
Hi!
I'm currently using version 1.0-beta1-nightly.build.3820. When a SIP
call is setup with a dynamically assigned payload type (>96), Jitsi
sends its RTP packets with its local payload type, instead of using
the remote payload type, as should be.
Is that a bug which has already been fixed, or should I file it?
It's a known issue and we currently have it under #1006 :
Just a quick followup question: does that mean that if I send the SDP
offer to Jitsi, it will reply with the same payload type mapping?
Yes, we always respect/use PT mappings provided by the remote party.
Cheers,
Emil
···
On 02.03.12 17:22, Raphael Coeffic wrote:
-Raphael.
On 02.03.2012, at 15:47, Emil Ivov wrote:
Hey Raphael,
On 02.03.12 16:22, Raphael Coeffic wrote:
Hi!
I'm currently using version 1.0-beta1-nightly.build.3820. When a
SIP call is setup with a dynamically assigned payload type (>96),
Jitsi sends its RTP packets with its local payload type, instead
of using the remote payload type, as should be.
Is that a bug which has already been fixed, or should I file it?
It's a known issue and we currently have it under #1006 :