> -----Original Message-----
> From: Ovidiu Sas [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 27, 2001 11:46 AM
> To: Manoj Bhatia
> Cc: Manish S. Jalan; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: [Sip-implementors] Re: [SIP] Clarification on sdp
> usage sought
>
> > > I am back to seek some more clarifications.
> > >
> > > Is the following sdp description ok: (the order of
> attribute definitions especially)
> > >
> > > m=audio 1234 RTP/AVP 4 0
> > > a=rtpmap:4 G723/8000
> > > a=rtpmap:0 PCMU/8000
> > > a=ptime:20
> > > a=fmtp:4 bitrate=6300
> > >
> >
> > This may not be illegal (given how loose the RFC is )
> > but I would think that it is not the preferred way.
> >
> > >
> > > or it should be,
> > >
> > > m=audio 1234 RTP/AVP 4 0
> > > a=rtpmap:4 G723/8000
> > > a=fmtp:4 bitrate=6300
> > > a=rtpmap:0 PCMU/8000
> > > a=ptime:20
> > >
> >
> > This is the right definition.
> > The ptime parameter would correspond to G.711ulaw (payload 0) .
>
> I could't find any statement about the order of the media attributes
> inside a media announcement in the RFC. In this context, how about
> this definition:
>
> m=audio 1234 RTP/AVP 4
> a=rtpmap:4 G723/8000
> a=fmtp:4 bitrate=6300
> m=audio 1234 RTP/AVP 0
> a=rtpmap:0 PCMU/8000
> a=ptime:20
>
> => no information about the G723's packetization and 20ms
> packetization for PCMU.
This is fine, but its TWO PARALLEL media streams, which may not be what you
mean.
-Jonathan R.
---
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
