[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] SDP offer answer model
From:       Brett Tate <brett () broadsoft ! com>
Date:       2014-04-18 9:15:40
Message-ID: 64d705bb64fa20e4cffe7877baa5a1a2 () mail ! gmail ! com
[Download RAW message or body]

Hi,

Since a prior reply was emphasizing "first audio line and the first video
line", I just wanted to mention that "first media format listed in the
answer" within the RFC 3264 snippet corresponds to first "fmt" within the
"m=" line instead of "first audio line and the first video line".

RFC 4566: m=<media> <port> <proto> <fmt> ...

> -----Original Message-----
> From: sip-implementors-bounces@lists.cs.columbia.edu [mailto:sip-
> implementors-bounces@lists.cs.columbia.edu] On Behalf Of Ozan Terzi
> Sent: Friday, April 18, 2014 4:45 AM
> To: Paul Kyzivat; sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] SDP offer answer model
>
> http://www.ietf.org/rfc/rfc3264.txt
>
> 7 Offerer Processing of the Answer When the offerer receives the
> answer, it MAY send media on the accepted stream(s) (assuming it is
> listed as sendrecv or recvonly in the answer). It MUST send using a
> media format listed in the answer, and it SHOULD use the first media
> format listed in the answer when it does send.
> Thanks,
> Ozan.

-- 


This email is intended solely for the person or entity to which it is 
addressed and may contain confidential and/or privileged information. If 
you are not the intended recipient and have received this email in error, 
please notify BroadSoft, Inc. immediately by replying to this message, and 
destroy all copies of this message, along with any attachment, prior to 
reading, distributing or copying it.

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[prev in list] [next in list] [prev in thread] [next in thread]