Hi Ling,
See inline.
Ling, Fan wrote:
Magnus,
You are dead on on the issues we are concerned about. Initially, our
understanding is the same as yours. However, when we proceed from
one-to-one video telephony application to multiparty video conference
application, the same understanding brings i
; sip-implementors@cs.columbia.edu; [EMAIL PROTECTED];
IETF AVT WG
Subject: Re: [AVT] RE: [Sip] RE: [Sip-implementors] media description in
SDP is for sender or receiver?
Hi Ling,
See inline.
Ling, Fan wrote:
> Magnus,
> You are dead on on the issues we are concerned about. Initially, our
> un
[EMAIL PROTECTED]; sip-implementors@cs.columbia.edu; sip@ietf.org;
IETF AVT WG
Subject: Re: [Sip] RE: [Sip-implementors] media description in SDP is
for sender or receiver?
Hi,
(cc also AVT as this is an AVT WG matter)
It took AVT a long time until actually offer/answer sections started
appearin
Hi,
(cc also AVT as this is an AVT WG matter)
It took AVT a long time until actually offer/answer sections started
appearing in the RTP payload formats. It is basically only the last year
or two that they have been included.
In general parameters applies for the stream the offerer/answer wan
essage-
From: Somesh S Shanbhag [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 03, 2005 9:33 PM
To: Ling, Fan; sip-implementors@cs.columbia.edu
Subject: Re: [Sip-implementors] media description in SDP is for sender
or receiver?
Hi,
RFC 3264 specifies sendonly, recvonly, sendrecv and
Hi,
RFC 3264 specifies sendonly, recvonly, sendrecv and
inactive attributes. UA can specify any of these
attributes according to it's preference. When no such
attribute is present, it is assumed that the stream is
"sendrecv" stream and whatever the encodings specified
applies to both sender and
Hi,
The following SDP message describes a MPEG4 video bitstream:
m=video 2 RTP/AVP 98 34
a=rtpmap:98 MP4V-ES/9
a=fmtp:98
profile-level-id=8;config=01B00801B50901000120008440FA28
2C2090A21F
Does this SDP message describes the sender encoder generated media
settings
