Re: [MMUSIC] (no subject)

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Wed, 13 August 2003 20:41 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05166 for <mmusic-archive@odin.ietf.org>; Wed, 13 Aug 2003 16:41:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19n2Qa-0007AZ-Ck for mmusic-archive@odin.ietf.org; Wed, 13 Aug 2003 16:41:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7DKf4aO027553 for mmusic-archive@odin.ietf.org; Wed, 13 Aug 2003 16:41:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19n2Qa-0007AK-9E for mmusic-web-archive@optimus.ietf.org; Wed, 13 Aug 2003 16:41:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05134 for <mmusic-web-archive@ietf.org>; Wed, 13 Aug 2003 16:40:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19n2QY-0004sT-00 for mmusic-web-archive@ietf.org; Wed, 13 Aug 2003 16:41:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19n2QX-0004sQ-00 for mmusic-web-archive@ietf.org; Wed, 13 Aug 2003 16:41:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19n2QY-00078Q-6G; Wed, 13 Aug 2003 16:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19n2Pf-00077b-W2 for mmusic@optimus.ietf.org; Wed, 13 Aug 2003 16:40:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05100 for <mmusic@ietf.org>; Wed, 13 Aug 2003 16:40:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19n2Pd-0004rx-00 for mmusic@ietf.org; Wed, 13 Aug 2003 16:40:05 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19n2Pd-0004ru-00 for mmusic@ietf.org; Wed, 13 Aug 2003 16:40:05 -0400
Received: from dynamicsoft.com ([63.113.46.76]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h7DKdU3m003854; Wed, 13 Aug 2003 16:39:33 -0400 (EDT)
Message-ID: <3F3AA1FE.8050800@dynamicsoft.com>
Date: Wed, 13 Aug 2003 16:39:26 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Raman, Sundereshwaran (Sundereshwaran)" <ramsun@avaya.com>
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] (no subject)
References: <E51B810754014D4FB52FAB2F188C265201118909@cof110avexu2.global.avaya.com>
In-Reply-To: <E51B810754014D4FB52FAB2F188C265201118909@cof110avexu2.global.avaya.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I believe Section 8.3.2 of RFC 3264 directly answers your question:

The list of media formats used in the session MAY be changed.  To do
    this, the offerer creates a new media description, with the list of
    media formats in the "m=" line different from the corresponding media
    stream in the previous SDP.  This list MAY include new formats, and
    MAY remove formats present from the previous SDP.  However, in the
    case of RTP, the mapping from a particular dynamic payload type
    number to a particular codec within that media stream MUST NOT change
    for the duration of a session.  For example, if A generates an offer
    with G.711 assigned to dynamic payload type number 46, payload type
    number 46 MUST refer to G.711 from that point forward in any offers
    or answers for that media stream within the session.  However, it is
    acceptable for multiple payload type numbers to be mapped to the same
    codec, so that an updated offer could also use payload type number 72
    for G.711.


This is true for the answerer as well. Thus, in each direction, once 
PT number is bound to a codec, that PT number can not be used for a 
different codec.

-Jonathan R.

Raman, Sundereshwaran (Sundereshwaran) wrote:

> I have question related to dynamic payloads. If a session is estblished 
> with a dynamic payload type number mapped to a particular codec, can the 
> number change for the same codec in subsequent offers/answers in the 
> same session? e.g. Lets say a session was established with a dynamic 
> payload type number 96 mapped to telephone-event. Now if a new Re-Invite 
> is sent out, can the response have a different payload type number for 
> the telephone event?
> 
> Thanks
> Sundi
> 
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic