Re: [SIP] draft-camarillo-sip-sdp-00.txt

[Gonzalo Camarillo <[e-mail]>]

Hi,

I already checked with the guys of the AVT WG and we reached some
conclusions on this matter. The issue was what to do when RTP has to be
sent to different ports based on the codec used at any moment.

The conclusion is that two RTP streams will be used. Right below I
attach a small review of the thread and one open issue regarding the fid
attribute.

Feedback is appreciated,

************

Hi,

Henning Schulzrinne wrote:
> 
> Gonzalo Camarillo wrote:
> >
> 
> >
> > Yes, that is one of the concerns people have - RTCP. Anyway, this 3rd
> > party developed RTP library is just one among many examples. There are
> > other scenarios where this feature might be useful. For instance, when
> > the DTMF tones have to be received in a different device than the voice.
> 
> That is solvable in a far cleaner manner by having two voice sessions,
> one for regular audio and one for DTMF. The same applies to other
> scenarios. To the end system, this is just like mixing several sources.
> Implementing this gets you mixing and conferencing for free, so this is
> a Good Thing.

I am happy with this solution. However, I would like to signal it
properly to the other end.

That is, I receive the following description (in an INVITE for
instance).

         v=0
         o=John 289085535 289085535 IN IP4 first.example.com
         t=0 0
         c=IN IP4 111.111.111.111
         m=audio 20000 RTP/AVP 0
         m=audio 20002 RTP/AVP 8

This means that I will receive two media streams. The first one on port
number 20000 will use PCM u-law. The second one will arrive on port
number 20002 and will be using PCM A-law.
Actually I might receive media from both media streams simultaneously.
One of the media streams might contain the voice of the singer and the
other the background (public, guitars, ...) of the concert.


I would like to differentiate this case from the following one.
Now I want to have a conversation with somebody. I want just to transmit
my voice. However, sometimes I will use PCM u-law and others PCM A-law.
The receiver wants to receive (due to any reason) different codecs on
different port numbers.

As we have discussed previously in this thread, we will establish two
media streams. But I want the receiver to know that I will never
transmit simultaneouly in both media streams.

I will transmit using one OR the other.

I would like my session description to look like:

         v=0
         o=John 289085535 289085535 IN IP4 first.example.com
         t=0 0
         c=IN IP4 111.111.111.111
         m=audio 20000 RTP/AVP 0
         a=fid:1
         m=audio 20002 RTP/AVP 8
         a=fid:1

If an implementation does not understand the fid attribute it will try
to mix the audio streams. Since one is "empty" all the time, doing this
is not really a big deal. Thus, backwards compatibility is not a
concern.

Do you have any concerns with this approach?

RTP and RTCP remain untouched.

Actually, this discussion began being very much RTP related, but now we
are moving to MMUSIC or SIP probably...

Best regards,

Gonzalo
************

-- 
Gonzalo Camarillo         Phone :  [phone]
Oy L M Ericsson Ab        Mobile:  [phone]
Telecom R&D               Fax   :  [phone]
FIN-02420 Jorvas          Email :  [e-mail]
Finland                   http://www.hut.fi/~gonzalo

_______________________________________________
SIP mailing list
[e-mail]
http://lists.bell-labs.com/mailman/listinfo/sip