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

List:       sip-implementors
Subject:    RE: [Sip-implementors] Different ptime for offered codecs
From:       "Jean-Francois Mule" <jf.mule () cablelabs ! com>
Date:       2003-02-20 4:53:31
Message-ID: E63E74E1F5391449BDFCAE1F352EC7DC95F04E () srvxchg ! cablelabs ! com
[Download RAW message or body]

John,
The answer is mptime, multiple packetization period. PacketCable has
defined this as part of the current NCS spec available on
http://www.packetcable.com/specifications/ .

Kevin Boyle & Graeme Currie of Nortel took it up to mmusic on behalf of
the PacketCable participating vendors, see
http://www1.ietf.org/mail-archive/working-groups/mmusic/current/msg01030
.html . May be Kevin could add on to my note.

Jean-Francois.

> -----Original Message-----
> From: Yadavalli, Satya [mailto:syadavalli@telogy.com] 
> Sent: Wednesday, February 19, 2003 8:00 PM
> To: 'Hearty, John'; sip-implementors@cs.columbia.edu
> Subject: RE: [Sip-implementors] Different ptime for offered codecs
> 
> 
> (not sure if there were any responses on this..)
> I guess we are supposed to use multiple "m" lines (one codec 
> per line) to be able to specify different attribute (like 
> ptime) values per each codec.
> 
> -satya
> 
> -----Original Message-----
> From: Hearty, John [mailto:John.Hearty@Level3.com] 
> Sent: Thursday, February 13, 2003 5:53 PM
> To: sip-implementors@cs.columbia.edu
> Subject: [Sip-implementors] Different ptime for offered codecs
> 
> Not sure if there is a more appropriate list for this 
> question, if so please forward.  When it is desired to offer 
> more than one codec for a particular stream, but different 
> packetization intervals are desired for each codec, how is 
> this accomplished?  It appears the ptime attribute is 
> relevant for everything on the m= line.  For example, if we 
> wish to send the below in an offer and would like to receive 
> g711 at 20 ms and g729 at 30 ms, can this be done?  If 
> a=ptime:30 is included and the answerer selects g711, will 
> they send 30 ms packets?  This does not seem to be clearly 
> covered in RFC3264 or other docs I've looked at.
> 
> m=audio 62986 RTP/AVP 0 18
> a=rtpmap:0 PCMU/8000
> a=rtpmap:18 G729/8000
> 
> 
> John Hearty
> Level 3
> 
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@cs.columbia.edu 
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


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