x27;t have a satisfactory solution
to our problem. We are now looking for proprietary methods.
Thanks for your wonderful comments and advices.
Fan
-Original Message-
From: Magnus Westerlund [mailto:[EMAIL PROTECTED]
Sent: Monday, November 07, 2005 5:45 AM
To: Ling, Fan
Cc: sip@ietf.org
to be the same,
the video bitstream parameters (VOL) also needs to be the same for both
encoder and decoder.
Your suggestion/advice is greatly appreciated.
Fan
-Original Message-
From: Magnus Westerlund [mailto:[EMAIL PROTECTED]
Sent: Friday, November 04, 2005 5:04 AM
To: Ling, Fan
Cc:
o specific media RFCs, in my case, RFC3016. But I can't find
comments regarding this in RFC3016.
Thanks for your advice.
Fan
-Original Message-
From: Christer Holmberg (JO/LMF) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 04, 2005 1:16 AM
To: Somesh S Shanbhag ; [EMAIL PROTECTED];
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,
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
