IETF Logo Mail Archive

Re: [Megaco] Local/Remote descriptors and Permanent terminations

"Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com> Wed, 03 April 2002 00:48 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 TAA09912 for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 19:48:17 -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 TAA27840; Tue, 2 Apr 2002 19:18:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA27734 for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 19:17:58 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09328 for <megaco@ietf.org>; Tue, 2 Apr 2002 19:17:57 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1]) by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g330GQV06078 for <megaco@ietf.org>; Tue, 2 Apr 2002 18:16:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53]) by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g330FYO21737 for <megaco@ietf.org>; Tue, 2 Apr 2002 18:15:34 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1]) by sun3144.ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g330FY727498 for <megaco@ietf.org>; Tue, 2 Apr 2002 18:15:34 -0600 (CST)
Message-ID: <3CAA49A5.ABEBF2C1@alcatel.com>
Date: Tue, 02 Apr 2002 18:15:34 -0600
From: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <4D79C746863DD51197690002A52CDA0001E8A23A@zcard0kc.ca.nortel.com>
Content-Type: multipart/alternative; boundary="------------5968615F4FC9ABE4064587AD"
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

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 ****

v2.23.0 | Report a Bug | By Email