> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 27, 2001 4:00 AM
> To: Jonathan Rosenberg
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Sip-implementors] Clarifications on SDP usage
>
>
>
>
>
> Hello,
>
> Thanks for the reply. I have another clarification
> to ask ...
>
> In the second case that I had sent earlier.
>
> > Case 2:
> > ----------
> > Invite recd contained a SDP message of the form:
> >
> > v=0
> > o=mhandley 29739 7272939 IN IP4 126.5.4.3
> > c=IN IP4 135.180.130.88
> > a=sendonly
> > m=audio 34567 RTP/AVP 0 4 12
>
> What you have mentioned in your mail is that
> the end-point is not allowed to break the "m="
> line recd into multiple ones. In the scenario that
> the end-point is willing to accept both media
> formats 0 and 4; but on different ports (say, 5555
> for the former and 6666 for the latter) how does it
> convey this information to the other end without
> breaking the media line?
It cannot. This is a limitation in SDP. It has been raised,
and an Internet Draft written that proposes a possible solution:
http://search.ietf.org/internet-drafts/draft-ietf-mmusic-fid-00.txt
>
> Also is it not necessary/desirable to repond
> definitively as to whether we are willing to accept
> each codec that the other end-point sends in his
> session description?
You do. The response contains those codecs that are accepted.
-Jonathan R.
---
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
