2009/2/26 Klaus Darilion :
> I will try to summarize:
>
> If Alice offers codecs X and Y, and Bob answers with X and Y, both are
> allowed to send with any of these codecs and must be prepared to receive any
> of these codecs. Thus, asymmetric codecs may happen.
And if Alice offers codecs X and Y
I will try to summarize:
If Alice offers codecs X and Y, and Bob answers with X and Y, both are
allowed to send with any of these codecs and must be prepared to receive
any of these codecs. Thus, asymmetric codecs may happen.
regards
klaus
Maxim Sobolev wrote:
> Sorry, you guys were right, I w
Maxim Sobolev schreef:
> stephane wrote:
>> I am a bit confused now. Didn't you mean example 2.4? In 2.2 it says
>> explicitly
>> ... uses either PCMU or PCMA codecs (payload type in RTP
>> packet tells which
>> is being used) , where in 2.4 two seperate audio streams
>> are established.
>
stephane wrote:
> I am a bit confused now. Didn't you mean example 2.4? In 2.2 it says
> explicitly
> ... uses either PCMU or PCMA codecs (payload type in RTP packet
> tells which
> is being used) , where in 2.4 two seperate audio streams are
> established.
No, I did not. So, what's unclea
Maxim Sobolev schreef:
> Maxim Sobolev wrote:
>
>> Sorry, you guys were right, I was not. It seems that if Bob accepts only
>> one format then the Alice can rely on not receiving any other payload type.
>>
>> http://www.rfc-archive.org/getrfc.php?rfc=4317
>>
>> Example 2.1.
>>
>> In order to al
El Miércoles, 25 de Febrero de 2009, Maxim Sobolev escribió:
> Sorry, you guys were right, I was not. It seems that if Bob accepts only
> one format then the Alice can rely on not receiving any other payload type.
>
> http://www.rfc-archive.org/getrfc.php?rfc=4317
>
> Example 2.1.
>
> In order to a
Maxim Sobolev wrote:
> Sorry, you guys were right, I was not. It seems that if Bob accepts only
> one format then the Alice can rely on not receiving any other payload type.
>
> http://www.rfc-archive.org/getrfc.php?rfc=4317
>
> Example 2.1.
>
> In order to allow asymmetric session, Bob should
Sorry, you guys were right, I was not. It seems that if Bob accepts only
one format then the Alice can rely on not receiving any other payload type.
http://www.rfc-archive.org/getrfc.php?rfc=4317
Example 2.1.
In order to allow asymmetric session, Bob should accept more than one
format, as in e
El Miércoles, 25 de Febrero de 2009, Maxim Sobolev escribió:
> For some reason you think that the SDP delivered by the Bob to Alice
> should somehow affect selection of codecs available for Bob to use when
> sending to Alice, but I cannot find any place in the standard where it's
> required.
>
> O
Iñaki Baz Castillo wrote:
> El Miércoles, 25 de Febrero de 2009, Maxim Sobolev escribió:
>>> Yes, this is the point. Are you sure that devices check that payload
>>> type? or do they assume they will receive the codec negociated in the
>>> SDP?
>> Yes they do. Mixing several payload types within on
El Miércoles, 25 de Febrero de 2009, Maxim Sobolev escribió:
> > Yes, this is the point. Are you sure that devices check that payload
> > type? or do they assume they will receive the codec negociated in the
> > SDP?
>
> Yes they do. Mixing several payload types within one RTP sessions is
> common
Klaus Darilion wrote:
> But AFAIK there are embedded devices which load the codec code into the
> DSP once the codec is negotiated, or after reINVITE if the codec
> changes. Thus, with such devices tis would not work. Or if Alice sends a
The practice disagrees with you. All hardware and softwar
Iñaki Baz Castillo wrote:
> 2009/2/25 Klaus Darilion :
>
>>> But if Bob sends G711, how will detect Alice that the incoming RTP is not
>>> G729?
>> There is the payloadtype field in the RTP header. So it is easy to differ
>> them.
>
> Yes, this is the point. Are you sure that devices check that p
Iñaki Baz Castillo wrote:
> 2009/2/25 Klaus Darilion :
>> I think if Alice announces G711 and G729, and Bob answers with G.729,
>> Alice must send with G729 and Bob can send with G711 too. Is this correct?
>
> If Bob answers G729 then Alice expects that Bob will send G729.
> But if Bob sends G711,
entors-boun...@lists.cs.columbia.edu
> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On
> Behalf Of Iñaki Baz Castillo
> Sent: Mittwoch, 25. Februar 2009 14:21
> Cc: sip-implementors
> Subject: Re: [Sip-implementors] asymmetric audio codecs
>
> 2009/2/25 Klaus Darilion :
>
> >
2009/2/25 Klaus Darilion :
>> But if Bob sends G711, how will detect Alice that the incoming RTP is not
>> G729?
>
> There is the payloadtype field in the RTP header. So it is easy to differ
> them.
Yes, this is the point. Are you sure that devices check that payload
type? or do they assume they
implementors
> Subject: Re: [Sip-implementors] asymmetric audio codecs
>
>
>
> Iñaki Baz Castillo schrieb:
> > 2009/2/25 Klaus Darilion :
> >> I think if Alice announces G711 and G729, and Bob answers
> with G.729,
> >> Alice must send with G729 and Bob
Iñaki Baz Castillo schrieb:
> 2009/2/25 Klaus Darilion :
>> I think if Alice announces G711 and G729, and Bob answers with G.729,
>> Alice must send with G729 and Bob can send with G711 too. Is this correct?
>
> If Bob answers G729 then Alice expects that Bob will send G729.
I wonder why? If I
: Wednesday, February 25, 2009 5:04 PM
To: Iñaki Baz Castillo; Klaus Darilion
Cc: sip-implementors
Subject: Re: [Sip-implementors] asymmetric audio codecs
- Original Message -
From: "Iñaki Baz Castillo"
To: "Klaus Darilion"
Cc: "sip-implementors"
Sent: Wednesd
- Original Message -
From: "Iñaki Baz Castillo"
To: "Klaus Darilion"
Cc: "sip-implementors"
Sent: Wednesday, February 25, 2009 12:20 PM
Subject: Re: [Sip-implementors] asymmetric audio codecs
> 2009/2/25 Klaus Darilion :
>> I think if Alice a
2009/2/25 Klaus Darilion :
> I think if Alice announces G711 and G729, and Bob answers with G.729,
> Alice must send with G729 and Bob can send with G711 too. Is this correct?
If Bob answers G729 then Alice expects that Bob will send G729.
But if Bob sends G711, how will detect Alice that the inco
>
> Stephane van Hardeveld schrieb:
>>
>> - Original Message - From: "Klaus Darilion"
>>
>> To: "sip-implementors"
>> Sent: Wednesday, February 25, 2009 9:29 AM
>> Subject: [Sip-implementors] asymmetric audio codecs
>&
Stephane van Hardeveld schrieb:
>
> - Original Message - From: "Klaus Darilion"
>
> To: "sip-implementors"
> Sent: Wednesday, February 25, 2009 9:29 AM
> Subject: [Sip-implementors] asymmetric audio codecs
>
>
>> Hi!
>>
>&g
Maxim Sobolev schrieb:
> Klaus Darilion wrote:
>> Hi!
>>
>> For a certain application where uplink is low bandwidth and downlink
>> is high bandwidth I want to use the best available codec - ie. up
>> G729, down G.711.
>>
>> How can I setup such an asymmetric session?
>>
>> eg.
>> high
Klaus Darilion wrote:
> Hi!
>
> For a certain application where uplink is low bandwidth and downlink is
> high bandwidth I want to use the best available codec - ie. up G729,
> down G.711.
>
> How can I setup such an asymmetric session?
>
> eg.
> high down
> Alice Bob
>
- Original Message -
From: "Klaus Darilion"
To: "sip-implementors"
Sent: Wednesday, February 25, 2009 9:29 AM
Subject: [Sip-implementors] asymmetric audio codecs
> Hi!
>
> For a certain application where uplink is low bandwidth and downlink is
> high
Hi!
For a certain application where uplink is low bandwidth and downlink is
high bandwidth I want to use the best available codec - ie. up G729,
down G.711.
How can I setup such an asymmetric session?
eg.
high down
Alice Bob
up low
I think if Alice announces G711
27 matches
Mail list logo
