RE: [Megaco] Residential Gateway

"Tom-PT Taylor"<taylor@nortelnetworks.com> Thu, 09 May 2002 17:12 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 NAA00959 for <megaco-archive@odin.ietf.org>; Thu, 9 May 2002 13:12:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA08097; Thu, 9 May 2002 12:42:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA08038 for <megaco@optimus.ietf.org>; Thu, 9 May 2002 12:42:36 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28897 for <megaco@ietf.org>; Thu, 9 May 2002 12:42:27 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g49GfsR14279 for <megaco@ietf.org>; Thu, 9 May 2002 12:41:54 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <KH1XH423>; Thu, 9 May 2002 12:41:59 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A456@zcard0kc.ca.nortel.com>
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: 'Pellegrino Jose Luis' <pellegrj@telefonica.com.ar>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Residential Gateway
Date: Thu, 09 May 2002 12:42:21 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
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

These will be published as independent RFCs.  The IESG is looking at the
first one now.  The tonepkgs document got bounced on a formatting
technicality and awaits recycling.

-----Original Message-----
From: Pellegrino Jose Luis [mailto:pellegrj@TELEFONICA.COM.AR]
Sent: Thursday, May 09, 2002 11:27 AM
To: 'Flemming Andreasen'; Miao, Kai
Cc: megaco@ietf.org
Subject: RE: [Megaco] Residential Gateway


You are right, the answer for MGCP is in the basic packages of the RFC 2705,
but I'm not sure how does MEGACO handle Caller ID servcies in residencial
gateway.

I remeber that some mouths ago two drafts were published in the IETF about
alerting packages and tone packages for MEGACO:

draft-boyle-megaco-alerting-02.txt ("Enhanced Alerting Packages for
Megaco/H.248")

draft-boyle-megaco-tonepkgs-06.txt("Supplemental Tones Packages for
Megaco/H.248")
   
Can anyone answer me::
Have these documents became obsolet?.
Will FRC 3015 (or perhaps a new annex) take into account the packages
mencionated in these two document?




> -----Mensaje original-----
> De:	Flemming Andreasen [SMTP:fandreas@cisco.com]
> Enviado el:	Jueves 9 de Mayo de 2002 11:25
> Para:	Miao, Kai
> CC:	megaco@ietf.org
> Asunto:	Re: [Megaco] Residential Gateway
> 
> For MGCP, you will find the relevant packages in the "Basic MGCP Packages"
> document
> (http://search.ietf.org/internet-drafts/draft-foster-mgcp-basic-packages-0
> 4.txt).
> In particular, you probably want to take a look at the "Generic Media",
> "DTMF" and "Line" packages.
> 
> -- Flemming
> 
> 
> "Miao, Kai" wrote:
> 
> > Hello, Everyone,
> >
> > Does anyone have any information regarding the specific requirements for
> > tone handling and callerID for a Residential Gateway in the context of
> > Megaco or MGCP?
> >
> > Appreciate your help.
> >
> > Kai Miao
> > Intel
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

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

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