RE: [Megaco] Local/Remote descriptors and Permanent terminations
Pauls Markus <Markus.Pauls@icn.siemens.de> Wed, 03 April 2002 12:38 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 HAA00974 for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 07:38:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17887; Wed, 3 Apr 2002 07:22:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01304 for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 02:50:32 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26661 for <megaco@ietf.org>; Wed, 3 Apr 2002 02:49:08 -0500 (EST)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226]) by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA01570; Wed, 3 Apr 2002 09:49:03 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56]) by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA01070; Wed, 3 Apr 2002 09:48:45 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19) id <H22NL17P>; Wed, 3 Apr 2002 09:49:04 +0200
Message-ID: <E01FD2A7A400D511A97C0008C791E2DF5FCBF0@MCHH262E>
From: Pauls Markus <Markus.Pauls@icn.siemens.de>
To: megaco@ietf.org
Cc: 'Carl Rutter' <crutter@telica.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 03 Apr 2002 09:48:51 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA01305
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Content-Transfer-Encoding: 8bit
Suppose you have the following SDP: m=audio 4444 RTP/AVP 0 18 a=fmtp:18 annexb=no // G.729, Silence Suppression off (see draft-ietf-avt-rtp-mime-05) a=silenceSupp: on - - - - (that means the GW may either use G.711 µ-law or G.729) The silenceSupp attribute is not specific for a payload type, the fmtp attribute is. So which one has precedence in this case? In my opinion you should have the ability to switch on silence suppression depending on the payload type. If you want to use it with G.711, it does not mean that you want it with G.729. Beyond that I believe generally it is more suited to an ephemeral termination. Therefore it should be expressed by means of SDP. However, if you want to transport the comfort noise payload (according to draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP media line as well (IMO). From my point of view the SDP should therefore look something like this: m=audio 4444 RTP/AVP 0 18 13 a=fmtp:18 annexb=no a=fmtp:0 silSup=yes where this PCMU specific parameter silSup must still be defined (for PCMA as well). Any comment is appreciated. Kind regards Markus Pauls ________________________________________________________ Markus Pauls SIEMENS Information and Communication Networks ICN WN CC NA B13 Tel.: +49 89 722 62937 Hofmannstr. 51 Fax: +49 89 722 44176 81359 Munich Email: markus.pauls@icn.siemens.de Germany -----Original Message----- From: Carl Rutter [mailto:crutter@telica.com] Sent: Wednesday, April 03, 2002 3:36 AM To: Chuong N. Nguyen Cc: megaco@ietf.org Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations You bring up a good point, Is/Should Silient Suppression be tied to the TDM package or SDP TDM, if in fact its really more applicable to the Ephemral side. If no can think of a good reason then your right it would make more sense to be in the SDP. For now we could use 0 13 for G711 and long-term use the ATM approach for SDP. Trying to drive towards closure as we have a need to implement this. Yea, the hairpinning would be in the MG Switch. Comments? Carl -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen Sent: Tuesday, April 02, 2002 8:05 PM Cc: megaco@ietf.org Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations That is what I initially thought silence suppression was about. But then I was told differently. It could be applied to TDM. If not, then why are we discussing adding silence suppresion to the TDM package? By the way, I thought TDM-TDM calls are being made at the Gwy too. Aren't you guys doing that now? Carl Rutter wrote: I can't think of an application where you'd want to do that. Silence suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at the CO. The DS0 is dedicated. The advantage of Silent suppression it to limit the RTP traffic on the IP side, which you wouldn't have in that case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice in the TDM-TDM call??Carl -----Original Message----- From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen Sent: Tuesday, April 02, 2002 7:16 PM To: megaco@ietf.org Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations Tom-PT Taylor wrote: I've had a message pointing out the existence of draft-ietf-avt-rtp-cn-05.txt. Specifying this payload type as well as G.711 would indicate the use of silence suppression implicitly. That covers RTP transport. For ATM we have the a=silenceSupp attribute defined in RFC 3108. Do we need anything for TDM? What if someone wanted to make a TDM-TDM, hairpin call? Would silenceSupp be used for such a call? If yes, then what? -- Alcatel USA, Inc Internet: Chuong.Nguyen@usa.alcatel.com 1000 Coit Road Plano, Texas 75075 Phone: (972) 519-4613 **** The opinions expressed are not those of Alcatel USA, Inc **** -- Alcatel USA, Inc Internet: Chuong.Nguyen@usa.alcatel.com 1000 Coit Road Plano, Texas 75075 Phone: (972) 519-4613 **** The opinions expressed are not those of Alcatel USA, Inc **** _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] Local/Remote descriptors and Permanent t… Rajesh N
- RE: [Megaco] Local/Remote descriptors and Permane… Tom-PT Taylor
- RE: [Megaco] Local/Remote descriptors and Permane… Madhu Babu Brahmanapally
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Tom-PT Taylor
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Tom-PT Taylor
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- Re: [Megaco] Local/Remote descriptors and Permane… Chuong N. Nguyen
- RE: [Megaco] Local/Remote descriptors and Permane… Pauls Markus
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- RE: [Megaco] Local/Remote descriptors and Permane… Carl Rutter
- RE: [Megaco] Local/Remote descriptors and Permane… Tom-PT Taylor
- RE: [Megaco] Local/Remote descriptors and Permane… David Barr
- Re: [Megaco] Local/Remote descriptors and Permane… Terry L Anderson