From mailman-owner@ietf.org  Tue Jan  1 05:11:51 2002
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 FAA10133
	for <megaco-archive@odin.ietf.org>; Tue, 1 Jan 2002 05:11:51 -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 FAA07393
	for <megaco-archive@lists.ietf.org>; Tue, 1 Jan 2002 05:11:54 -0500 (EST)
Date: Tue, 1 Jan 2002 05:11:54 -0500 (EST)
Message-Id: <200201011011.FAA07393@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: megaco-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, megaco-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for megaco-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
megaco@ietf.org                          rFKd      
https://www1.ietf.org/mailman/options/megaco/megaco-archive@lists.ietf.org


From megaco-admin@ietf.org  Wed Jan  2 08:32:59 2002
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 IAA03595
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:32:59 -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 IAA05868;
	Wed, 2 Jan 2002 08:18:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA05840
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:18:38 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03412
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:18:35 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA23856;
	Wed, 2 Jan 2002 08:18:04 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA29054;
	Wed, 2 Jan 2002 08:18:04 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNKNPA>; Wed, 2 Jan 2002 08:18:02 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C735@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 08:18:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You audit the Media descriptor of all of the terminations
to determine which terminations are employing the
codec of interest.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, December 28, 2001 9:25 PM
> To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian,  All
> I agree with you on the concept of Audit capability and Audit 
> Value . But in present protocol , How can we get the 500 busy 
> through Audit value present defined, I can't find the 
> parameter or package defined the case. 
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 29, 2001 12:54 AM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Audit capabilities tells you what the capabilities of the system
> > are.  Audit Value tells you what is currently "in use".
> > In theory, the "1000 G.711 channel resource" comes from Audit
> > Capability, "500 busy" comes from Audit Value.
> > 
> > In general, the RFC is compliant with the requirements with one
> > notable exception: many gateways are implemented with DSPs or other
> > programmable resources. There is no good way to express capability
> > with such resources.
> > 
> > If you have 1000 fixed G.711 channels, Audit Capability will reveal
> > that.  If 500 channels are used, Audit Value will reveal that.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > Sent: Friday, December 28, 2001 9:44 AM
> > > To: 'Shashi Kumar'; 'zhangzhong'
> > > Cc: megaco@ietf.org
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > HI Shashi,All,
> > > Its true that Audit will help MGC to reconcile the 
> > > inconsistency. But for
> > > the specific scenario Zhang has pointed, How this resource 
> > > information is
> > > exchanged between the MG and the MGC. According to my 
> > > knowledge there is no
> > > parameter or anything as such to "quantitatively" identify 
> > > G711 or any such
> > > channel resource.
> > > Regards
> > > Madhubabu
> > > 
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > > Shashi Kumar
> > > Sent: Thursday, December 27, 2001 11:55 PM
> > > To: zhangzhong
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > we have provision to audit the MG resource, which 
> clearlty defined by
> > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > "reconcile inconsistencies between the MGC and the MG"
> > > 
> > > thanks,
> > > shashi
> > > 
> > > 
> > > > zhangzhong wrote:
> > > >
> > > > Hi :
> > > > In the rfc 2805, there have a request to H.248:
> > > >         Provide a mechanism to discover the current available
> > > > resources
> > > >         in the MG, where resources are dynamically consumed by
> > > >         connections and the MGC cannot reasonably or 
> reliably track
> > > > the
> > > >         consumption of such resources. It should also 
> be possible to
> > > >         discover resources currently in use, in order 
> to reconcile
> > > >         inconsistencies between the MGC and the MG.
> > > >
> > > > This means MGC can know the resource consume in the MGW , 
> > > for example
> > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > busy , How can
> > > > MGC know this through RFC3015?
> > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > >
> > > > Thanks for the reply.
> > > > Regards
> > > > Zhangzhong
> > > 
> > > 
> > > _______________________________________________
> > > 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


From daemon@optimus.ietf.org  Wed Jan  2 08:33:00 2002
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 IAA03604
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:33:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07021
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 08:33:02 -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 IAA05868;
	Wed, 2 Jan 2002 08:18:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA05840
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:18:38 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03412
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:18:35 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA23856;
	Wed, 2 Jan 2002 08:18:04 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA29054;
	Wed, 2 Jan 2002 08:18:04 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNKNPA>; Wed, 2 Jan 2002 08:18:02 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C735@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 08:18:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You audit the Media descriptor of all of the terminations
to determine which terminations are employing the
codec of interest.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, December 28, 2001 9:25 PM
> To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian,  All
> I agree with you on the concept of Audit capability and Audit 
> Value . But in present protocol , How can we get the 500 busy 
> through Audit value present defined, I can't find the 
> parameter or package defined the case. 
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Saturday, December 29, 2001 12:54 AM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Audit capabilities tells you what the capabilities of the system
> > are.  Audit Value tells you what is currently "in use".
> > In theory, the "1000 G.711 channel resource" comes from Audit
> > Capability, "500 busy" comes from Audit Value.
> > 
> > In general, the RFC is compliant with the requirements with one
> > notable exception: many gateways are implemented with DSPs or other
> > programmable resources. There is no good way to express capability
> > with such resources.
> > 
> > If you have 1000 fixed G.711 channels, Audit Capability will reveal
> > that.  If 500 channels are used, Audit Value will reveal that.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > Sent: Friday, December 28, 2001 9:44 AM
> > > To: 'Shashi Kumar'; 'zhangzhong'
> > > Cc: megaco@ietf.org
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > HI Shashi,All,
> > > Its true that Audit will help MGC to reconcile the 
> > > inconsistency. But for
> > > the specific scenario Zhang has pointed, How this resource 
> > > information is
> > > exchanged between the MG and the MGC. According to my 
> > > knowledge there is no
> > > parameter or anything as such to "quantitatively" identify 
> > > G711 or any such
> > > channel resource.
> > > Regards
> > > Madhubabu
> > > 
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > > Shashi Kumar
> > > Sent: Thursday, December 27, 2001 11:55 PM
> > > To: zhangzhong
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > we have provision to audit the MG resource, which 
> clearlty defined by
> > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > "reconcile inconsistencies between the MGC and the MG"
> > > 
> > > thanks,
> > > shashi
> > > 
> > > 
> > > > zhangzhong wrote:
> > > >
> > > > Hi :
> > > > In the rfc 2805, there have a request to H.248:
> > > >         Provide a mechanism to discover the current available
> > > > resources
> > > >         in the MG, where resources are dynamically consumed by
> > > >         connections and the MGC cannot reasonably or 
> reliably track
> > > > the
> > > >         consumption of such resources. It should also 
> be possible to
> > > >         discover resources currently in use, in order 
> to reconcile
> > > >         inconsistencies between the MGC and the MG.
> > > >
> > > > This means MGC can know the resource consume in the MGW , 
> > > for example
> > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > busy , How can
> > > > MGC know this through RFC3015?
> > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > >
> > > > Thanks for the reply.
> > > > Regards
> > > > Zhangzhong
> > > 
> > > 
> > > _______________________________________________
> > > 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



From megaco-admin@ietf.org  Wed Jan  2 08:33:24 2002
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 IAA03654
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:33:24 -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 IAA06239;
	Wed, 2 Jan 2002 08:24:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06213
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:24:09 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03465
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:24:02 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA24140;
	Wed, 2 Jan 2002 08:23:28 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA29728;
	Wed, 2 Jan 2002 08:23:29 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNKN4Z>; Wed, 2 Jan 2002 08:23:28 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C736@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'mmraju@lucent.com'" <mmraju@lucent.com>,
        zhangzhong
	 <zhangzhong@huawei.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 08:23:26 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I agree that when the expression of available and consumed
resources is not a simple count, then the audit mechanisms
in 3015 are inadequate.  This is actually a limitation of
SDP and the Annex C equivalent of it.  There is work to extend
SDP, which may have more facilities to assist this problem.

Please note that the problem is quite complex, and it isn't
clear to me that there exists any straightforward way for
the MG to express capability and consumed resources in a
manner that the MGC can always predict whether a new
Add or Modify will work.

Brian

> -----Original Message-----
> From: Raju [mailto:mmraju@lucent.com]
> Sent: Monday, December 31, 2001 9:56 AM
> To: zhangzhong; Madhu Babu Brahmanapally
> Cc: megaco@ietf.org
> Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> I do agree with Zhangzhong.
> 
> Infact calculation of available resources by MGC becomes more 
> tough and
> ambigous if the GW supports more than one codec
> (e.g. G.723 and G.711), which is generally be the case.
> The number of available G.711 codecs depends on the number of 
> G.723 codecs
> in use, as G.723 uses more MIPS.
> MGC can't understand these dependencies and calculate the 
> exact number of
> free resources available, only MG
> knows how eactly to calculate the free or available resources.
> 
> Pls read my previous mail below.
> 
> Thanks
> Raju
> 
> > -----Original Message-----
> > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > zhangzhong
> > Sent: Friday, December 28, 2001 9:17 PM
> > To: Madhu Babu Brahmanapally; 'Shashi Kumar'
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > Hi all,
> > 1  I think the method below can  reach the aim in theory , It is
> > a idea in the present protocol, but not very good. And Because it
> > is very ambiguous . It will introduct the difficulity of
> > interwork between MGC and MGW with more difficulity. If the MGW
> > has a big capability , the management of these termination 
> has problems .
> > The method is not the idea of MEGACO, because  operations of
> > sending tone or playing announcemnt  are all done on  the same
> > termination which receive/send media from/to outside not specified.
> >
> >
> > Thans for your reply and help.
> > Regards
> > Zhangzhong
> >
> >
> > ----- Original Message -----
> > Hi Zhangzhong,
> >
> > as of current understanding we should admit that there is 
> no direct was
> > of doing, but we have the information with in the Megaco scope to do
> > this.
> >
> > we shall take your specific example of G.711 resource issue...
> > 1. Each G.711 resource is identified as a Termination 
> (using Termination
> > ID), which is a provisioned info( or otherwise)
> > 2. At any Given point of time, you know how many 
> termination's are in
> > (a) context(s) ( in both MG and MGC instance of protocol), 
> which shall
> > be take as G.711 resource which is busy....
> >
> > with the above info it is very easy to identify how many of G.711
> > resource are free...
> >
> > hope this helps...
> >
> > shashi
> >
> >
> >
> >
> > ----- Original Message -----
> > From: Madhu Babu Brahmanapally <madhubabu@kenetec.com>
> > To: 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> > <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 28, 2001 10:44 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the requirement
> > on RFC2805
> >
> >
> > > HI Shashi,All,
> > > Its true that Audit will help MGC to reconcile the
> > inconsistency. But for
> > > the specific scenario Zhang has pointed, How this resource
> > information is
> > > exchanged between the MG and the MGC. According to my knowledge
> > there is no
> > > parameter or anything as such to "quantitatively" identify G711
> > or any such
> > > channel resource.
> > > Regards
> > > Madhubabu
> > >
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > > Shashi Kumar
> > > Sent: Thursday, December 27, 2001 11:55 PM
> > > To: zhangzhong
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > >
> > >
> > > we have provision to audit the MG resource, which 
> clearlty defined by
> > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > "reconcile inconsistencies between the MGC and the MG"
> > >
> > > thanks,
> > > shashi
> > >
> > >
> > > > zhangzhong wrote:
> > > >
> > > > Hi :
> > > > In the rfc 2805, there have a request to H.248:
> > > >         Provide a mechanism to discover the current available
> > > > resources
> > > >         in the MG, where resources are dynamically consumed by
> > > >         connections and the MGC cannot reasonably or 
> reliably track
> > > > the
> > > >         consumption of such resources. It should also 
> be possible to
> > > >         discover resources currently in use, in order 
> to reconcile
> > > >         inconsistencies between the MGC and the MG.
> > > >
> > > > This means MGC can know the resource consume in the MGW 
> , for example
> > > > , if There have 1000 G.711 channel resource , if 500 is 
> busy , How can
> > > > MGC know this through RFC3015?
> > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > >
> > > > Thanks for the reply.
> > > > Regards
> > > > Zhangzhong
> > >
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Wed Jan  2 08:33:25 2002
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 IAA03664
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:33:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07077
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 08:33:26 -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 IAA06239;
	Wed, 2 Jan 2002 08:24:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06213
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:24:09 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03465
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:24:02 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA24140;
	Wed, 2 Jan 2002 08:23:28 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA29728;
	Wed, 2 Jan 2002 08:23:29 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNKN4Z>; Wed, 2 Jan 2002 08:23:28 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C736@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'mmraju@lucent.com'" <mmraju@lucent.com>,
        zhangzhong
	 <zhangzhong@huawei.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 08:23:26 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I agree that when the expression of available and consumed
resources is not a simple count, then the audit mechanisms
in 3015 are inadequate.  This is actually a limitation of
SDP and the Annex C equivalent of it.  There is work to extend
SDP, which may have more facilities to assist this problem.

Please note that the problem is quite complex, and it isn't
clear to me that there exists any straightforward way for
the MG to express capability and consumed resources in a
manner that the MGC can always predict whether a new
Add or Modify will work.

Brian

> -----Original Message-----
> From: Raju [mailto:mmraju@lucent.com]
> Sent: Monday, December 31, 2001 9:56 AM
> To: zhangzhong; Madhu Babu Brahmanapally
> Cc: megaco@ietf.org
> Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> I do agree with Zhangzhong.
> 
> Infact calculation of available resources by MGC becomes more 
> tough and
> ambigous if the GW supports more than one codec
> (e.g. G.723 and G.711), which is generally be the case.
> The number of available G.711 codecs depends on the number of 
> G.723 codecs
> in use, as G.723 uses more MIPS.
> MGC can't understand these dependencies and calculate the 
> exact number of
> free resources available, only MG
> knows how eactly to calculate the free or available resources.
> 
> Pls read my previous mail below.
> 
> Thanks
> Raju
> 
> > -----Original Message-----
> > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > zhangzhong
> > Sent: Friday, December 28, 2001 9:17 PM
> > To: Madhu Babu Brahmanapally; 'Shashi Kumar'
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > Hi all,
> > 1  I think the method below can  reach the aim in theory , It is
> > a idea in the present protocol, but not very good. And Because it
> > is very ambiguous . It will introduct the difficulity of
> > interwork between MGC and MGW with more difficulity. If the MGW
> > has a big capability , the management of these termination 
> has problems .
> > The method is not the idea of MEGACO, because  operations of
> > sending tone or playing announcemnt  are all done on  the same
> > termination which receive/send media from/to outside not specified.
> >
> >
> > Thans for your reply and help.
> > Regards
> > Zhangzhong
> >
> >
> > ----- Original Message -----
> > Hi Zhangzhong,
> >
> > as of current understanding we should admit that there is 
> no direct was
> > of doing, but we have the information with in the Megaco scope to do
> > this.
> >
> > we shall take your specific example of G.711 resource issue...
> > 1. Each G.711 resource is identified as a Termination 
> (using Termination
> > ID), which is a provisioned info( or otherwise)
> > 2. At any Given point of time, you know how many 
> termination's are in
> > (a) context(s) ( in both MG and MGC instance of protocol), 
> which shall
> > be take as G.711 resource which is busy....
> >
> > with the above info it is very easy to identify how many of G.711
> > resource are free...
> >
> > hope this helps...
> >
> > shashi
> >
> >
> >
> >
> > ----- Original Message -----
> > From: Madhu Babu Brahmanapally <madhubabu@kenetec.com>
> > To: 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> > <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, December 28, 2001 10:44 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the requirement
> > on RFC2805
> >
> >
> > > HI Shashi,All,
> > > Its true that Audit will help MGC to reconcile the
> > inconsistency. But for
> > > the specific scenario Zhang has pointed, How this resource
> > information is
> > > exchanged between the MG and the MGC. According to my knowledge
> > there is no
> > > parameter or anything as such to "quantitatively" identify G711
> > or any such
> > > channel resource.
> > > Regards
> > > Madhubabu
> > >
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org 
> [mailto:megaco-admin@ietf.org]On Behalf Of
> > > Shashi Kumar
> > > Sent: Thursday, December 27, 2001 11:55 PM
> > > To: zhangzhong
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > >
> > >
> > > we have provision to audit the MG resource, which 
> clearlty defined by
> > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > "reconcile inconsistencies between the MGC and the MG"
> > >
> > > thanks,
> > > shashi
> > >
> > >
> > > > zhangzhong wrote:
> > > >
> > > > Hi :
> > > > In the rfc 2805, there have a request to H.248:
> > > >         Provide a mechanism to discover the current available
> > > > resources
> > > >         in the MG, where resources are dynamically consumed by
> > > >         connections and the MGC cannot reasonably or 
> reliably track
> > > > the
> > > >         consumption of such resources. It should also 
> be possible to
> > > >         discover resources currently in use, in order 
> to reconcile
> > > >         inconsistencies between the MGC and the MG.
> > > >
> > > > This means MGC can know the resource consume in the MGW 
> , for example
> > > > , if There have 1000 G.711 channel resource , if 500 is 
> busy , How can
> > > > MGC know this through RFC3015?
> > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > >
> > > > Thanks for the reply.
> > > > Regards
> > > > Zhangzhong
> > >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Wed Jan  2 08:33:46 2002
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 IAA03698
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:33:46 -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 IAA06402;
	Wed, 2 Jan 2002 08:25:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06359
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:25:36 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03515
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:25:33 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g02740J12276
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:04:00 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Wed Jan 02 08:03:59 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKHHX6>; Wed, 2 Jan 2002 08:03:43 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB11@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Madhu Babu Brahmanapally'" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Annex L in Version 2
Date: Wed, 2 Jan 2002 08:03:39 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Madhu,

annexes like L are published as separate docs in ITU.
Draft for v2 reflects changes according to the 
ITU draft for v2.

Regards,
Marcello 

-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 29, 2001 4:53 PM
To: megaco@ietf.org
Subject: [Megaco] Annex L in Version 2


Hi All,
The Draft for version 2 at
http://www.ietf.org/internet-drafts/draft-ietf-megaco-h248v2-00.txt doesn't
includes other annexes like annex L. Shouldn't it be the part of protocol
draft.
Regards
Madhubabu


_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan  2 08:33:46 2002
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 IAA03707
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 08:33:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07106
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 08:33:48 -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 IAA06402;
	Wed, 2 Jan 2002 08:25:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06359
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 08:25:36 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03515
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:25:33 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g02740J12276
	for <megaco@ietf.org>; Wed, 2 Jan 2002 08:04:00 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Wed Jan 02 08:03:59 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKHHX6>; Wed, 2 Jan 2002 08:03:43 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB11@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Madhu Babu Brahmanapally'" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Annex L in Version 2
Date: Wed, 2 Jan 2002 08:03:39 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Madhu,

annexes like L are published as separate docs in ITU.
Draft for v2 reflects changes according to the 
ITU draft for v2.

Regards,
Marcello 

-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 29, 2001 4:53 PM
To: megaco@ietf.org
Subject: [Megaco] Annex L in Version 2


Hi All,
The Draft for version 2 at
http://www.ietf.org/internet-drafts/draft-ietf-megaco-h248v2-00.txt doesn't
includes other annexes like annex L. Shouldn't it be the part of protocol
draft.
Regards
Madhubabu


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 12:18:27 2002
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 MAA07405
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 12:18:27 -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 MAA13702;
	Wed, 2 Jan 2002 12:07:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13671
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 12:07:18 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07205
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:07:15 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02H6lu12787
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:06:47 -0500 (EST)
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 g02H6jx20383
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:06:45 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Z844RNR4>; Wed, 2 Jan 2002 12:05:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C87@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 2 Jan 2002 12:05:11 -0500 
Importance: high
X-Priority: 1
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: Study Group 16 Deadlines
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

ITU-T Study Group 16 is meeting in Geneva from 5-15 February.  Details are
given in Collective Letter 3/16 at 
http://www.itu.int/itudoc/itu-t/com16/coll/01-04/003.html

You should be aware of two deadlines:

  1) If you plan to go, you should register with the ITU-T by this Friday.

  2) Delayed Contributions are due by January 24.

The significance of this second deadline is that we should complete our Last
Call process on draft-ietf-megaco-h248v2-00.txt before that date so I can
submit a document representing the changes proposed by the Megaco WG.  I
will open up an issues list today as a focus for discussion.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@optimus.ietf.org  Wed Jan  2 12:18:28 2002
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 MAA07415
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 12:18:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA13816
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 12:18:30 -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 MAA13702;
	Wed, 2 Jan 2002 12:07:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13671
	for <megaco@optimus.ietf.org>; Wed, 2 Jan 2002 12:07:18 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07205
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:07:15 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02H6lu12787
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:06:47 -0500 (EST)
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 g02H6jx20383
	for <megaco@ietf.org>; Wed, 2 Jan 2002 12:06:45 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Z844RNR4>; Wed, 2 Jan 2002 12:05:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C87@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 2 Jan 2002 12:05:11 -0500 
Importance: high
X-Priority: 1
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: Study Group 16 Deadlines
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

ITU-T Study Group 16 is meeting in Geneva from 5-15 February.  Details are
given in Collective Letter 3/16 at 
http://www.itu.int/itudoc/itu-t/com16/coll/01-04/003.html

You should be aware of two deadlines:

  1) If you plan to go, you should register with the ITU-T by this Friday.

  2) Delayed Contributions are due by January 24.

The significance of this second deadline is that we should complete our Last
Call process on draft-ietf-megaco-h248v2-00.txt before that date so I can
submit a document representing the changes proposed by the Megaco WG.  I
will open up an issues list today as a focus for discussion.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Wed Jan  2 14:17:10 2002
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 OAA08834
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:17:10 -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 OAA17158;
	Wed, 2 Jan 2002 14:06:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17127
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:06:27 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08730
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:06:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02J5pi10195
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:05:51 -0500 (EST)
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 g02J5oK26426
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:05:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR15N>; Wed, 2 Jan 2002 14:04:11 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Registration Procedure
Date: Wed, 2 Jan 2002 14:04:16 -0500 
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

My previous attempt at reply got away when I hit the wrong button.

The MGC could simply send back a transaction reply containing an error
response such as 503 Service Unavailable.



-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, December 28, 2001 4:43 AM
To: megaco@ietf.org
Subject: [Megaco] Registration Procedure


Hi All,

During the registration process,  the MG sends a Service Change Request
(with Restart, Root) to the MGC. How can the MGC  refuse the registration
attempt without sending ServiceChangeMgcId.

Basically I would like to know, how a registration attempt is refused by an
MGC and what are the contents of the Service Change Reply message.

Thanks in Advance

- Nayantara

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


From daemon@ns.ietf.org  Wed Jan  2 14:17:11 2002
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 OAA08847
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:17:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17378
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:17:12 -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 OAA17158;
	Wed, 2 Jan 2002 14:06:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17127
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:06:27 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08730
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:06:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02J5pi10195
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:05:51 -0500 (EST)
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 g02J5oK26426
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:05:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR15N>; Wed, 2 Jan 2002 14:04:11 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Registration Procedure
Date: Wed, 2 Jan 2002 14:04:16 -0500 
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

My previous attempt at reply got away when I hit the wrong button.

The MGC could simply send back a transaction reply containing an error
response such as 503 Service Unavailable.



-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, December 28, 2001 4:43 AM
To: megaco@ietf.org
Subject: [Megaco] Registration Procedure


Hi All,

During the registration process,  the MG sends a Service Change Request
(with Restart, Root) to the MGC. How can the MGC  refuse the registration
attempt without sending ServiceChangeMgcId.

Basically I would like to know, how a registration attempt is refused by an
MGC and what are the contents of the Service Change Reply message.

Thanks in Advance

- Nayantara

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



From megaco-admin@ietf.org  Wed Jan  2 14:18:48 2002
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 OAA08877
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:18:48 -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 OAA17062;
	Wed, 2 Jan 2002 14:03:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17031
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:03:26 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08694
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:03:24 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02J2si09776;
	Wed, 2 Jan 2002 14:02:54 -0500 (EST)
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 g02J2qK26196;
	Wed, 2 Jan 2002 14:02:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR1XC>; Wed, 2 Jan 2002 14:01:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Registration Procedure
Date: Wed, 2 Jan 2002 14:00:06 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C193BF.B16AAF00"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C193BF.B16AAF00
Content-Type: text/plain;
	charset="iso-8859-1"


-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, December 28, 2001 4:43 AM
To: megaco@ietf.org
Subject: [Megaco] Registration Procedure


Hi All,

During the registration process,  the MG sends a Service Change Request
(with Restart, Root) to the MGC. How can the MGC  refuse the registration
attempt without sending ServiceChangeMgcId.

Basically I would like to know, how a registration attempt is refused by an
MGC and what are the contents of the Service Change Reply message.

Thanks in Advance

- Nayantara

------_=_NextPart_001_01C193BF.B16AAF00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Registration Procedure</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sundareswaram P V [<A =
HREF=3D"mailto:sundareswarampv@netbrahma.com">mailto:sundareswarampv@net=
brahma.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, December 28, 2001 4:43 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Registration Procedure</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi All,</FONT>
</P>

<P><FONT SIZE=3D2>During the registration process,&nbsp; the MG sends a =
Service Change Request (with Restart, Root) to the MGC. How can the =
MGC&nbsp; refuse the registration attempt without sending =
ServiceChangeMgcId.</FONT></P>

<P><FONT SIZE=3D2>Basically I would like to know, how a registration =
attempt is refused by an MGC and what are the contents of the Service =
Change Reply message.</FONT></P>

<P><FONT SIZE=3D2>Thanks in Advance</FONT>
</P>

<P><FONT SIZE=3D2>- Nayantara</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C193BF.B16AAF00--

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


From daemon@ns.ietf.org  Wed Jan  2 14:18:49 2002
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 OAA08888
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:18:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17428
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:18:50 -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 OAA17062;
	Wed, 2 Jan 2002 14:03:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17031
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:03:26 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08694
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:03:24 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02J2si09776;
	Wed, 2 Jan 2002 14:02:54 -0500 (EST)
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 g02J2qK26196;
	Wed, 2 Jan 2002 14:02:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR1XC>; Wed, 2 Jan 2002 14:01:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Registration Procedure
Date: Wed, 2 Jan 2002 14:00:06 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C193BF.B16AAF00"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C193BF.B16AAF00
Content-Type: text/plain;
	charset="iso-8859-1"


-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, December 28, 2001 4:43 AM
To: megaco@ietf.org
Subject: [Megaco] Registration Procedure


Hi All,

During the registration process,  the MG sends a Service Change Request
(with Restart, Root) to the MGC. How can the MGC  refuse the registration
attempt without sending ServiceChangeMgcId.

Basically I would like to know, how a registration attempt is refused by an
MGC and what are the contents of the Service Change Reply message.

Thanks in Advance

- Nayantara

------_=_NextPart_001_01C193BF.B16AAF00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Registration Procedure</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sundareswaram P V [<A =
HREF=3D"mailto:sundareswarampv@netbrahma.com">mailto:sundareswarampv@net=
brahma.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, December 28, 2001 4:43 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Registration Procedure</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi All,</FONT>
</P>

<P><FONT SIZE=3D2>During the registration process,&nbsp; the MG sends a =
Service Change Request (with Restart, Root) to the MGC. How can the =
MGC&nbsp; refuse the registration attempt without sending =
ServiceChangeMgcId.</FONT></P>

<P><FONT SIZE=3D2>Basically I would like to know, how a registration =
attempt is refused by an MGC and what are the contents of the Service =
Change Reply message.</FONT></P>

<P><FONT SIZE=3D2>Thanks in Advance</FONT>
</P>

<P><FONT SIZE=3D2>- Nayantara</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C193BF.B16AAF00--

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



From megaco-admin@ietf.org  Wed Jan  2 14:19:53 2002
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 OAA08909
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:19:53 -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 OAA17241;
	Wed, 2 Jan 2002 14:11:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17211
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:11:22 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08781
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:11:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JApi10777;
	Wed, 2 Jan 2002 14:10:51 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JAn104330;
	Wed, 2 Jan 2002 14:10:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR19G>; Wed, 2 Jan 2002 14:09:11 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'subramaniyan saravanan'" <saravin76@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Wed, 2 Jan 2002 14:09:13 -0500 
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

Not allowed.  Megaco considers the MGC to be the master in all cases except
Notify (always from the MG) and ServiceChange (may come from either the MG
or MGC).  Our charter restricted us from considering the case where MGs
could signal SDP directly to the remote peer.

-----Original Message-----
From: subramaniyan saravanan [mailto:saravin76@yahoo.com]
Sent: Friday, December 28, 2001 5:09 AM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


Hi,

  Is it possible to send Modify command from Gateway
to MGC ?

  This will be helpful if MG wants to change the
RTP/SDP parameters of any existing call.

regards
saravanan



__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 14:19:53 2002
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 OAA08920
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:19:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17465
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:19:55 -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 OAA17241;
	Wed, 2 Jan 2002 14:11:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17211
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:11:22 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08781
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:11:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JApi10777;
	Wed, 2 Jan 2002 14:10:51 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JAn104330;
	Wed, 2 Jan 2002 14:10:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR19G>; Wed, 2 Jan 2002 14:09:11 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'subramaniyan saravanan'" <saravin76@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Wed, 2 Jan 2002 14:09:13 -0500 
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

Not allowed.  Megaco considers the MGC to be the master in all cases except
Notify (always from the MG) and ServiceChange (may come from either the MG
or MGC).  Our charter restricted us from considering the case where MGs
could signal SDP directly to the remote peer.

-----Original Message-----
From: subramaniyan saravanan [mailto:saravin76@yahoo.com]
Sent: Friday, December 28, 2001 5:09 AM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


Hi,

  Is it possible to send Modify command from Gateway
to MGC ?

  This will be helpful if MG wants to change the
RTP/SDP parameters of any existing call.

regards
saravanan



__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 14:24:32 2002
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 OAA08985
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:24:32 -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 OAA17326;
	Wed, 2 Jan 2002 14:13:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17294
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:13:55 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08819
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:13:52 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JDNi11040;
	Wed, 2 Jan 2002 14:13:23 -0500 (EST)
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 g02JDLK26804;
	Wed, 2 Jan 2002 14:13:22 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFAA>; Wed, 2 Jan 2002 14:11:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Wed, 2 Jan 2002 14:11:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C193C1.4D659A40"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C193C1.4D659A40
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Saturday, December 29, 2001 1:27 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Reserve Value and Reserve Group


Hi,
In the RFC 3015, following is given in section 7.1.8 (Local and Remote
Descriptors):
"If ReserveGroup is true, the MG reserves the resources required to
support any of the requested property group alternatives that it can
currently support.  If ReserveValue is true, the MG reserves the
resources required to support any of the requested property value
alternatives that it can currently support."

In the above statement, I want to know "what is property group and what is
property value". Where can I get more information on this. I referred
SDP RFC 2327, in that Session level Description and Media level Description
are differentiated. But I could not conclude from this.

In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
Session level descriptions. Can anybody mail me how can I interpret this,
as property groups or as property values. I will be happy, if somebody
explains this with some example packets.

One more doubt regarding SDP Paramters:
In SDP RFC 2327, it is given that following fields are mandatory:
For 'Session description':
v=  (protocol version)
o=  (owner/creator and session identifier).
s=  (session name)
For 'Time description':
t=  (time the session is active)

For 'Media description':
m=  (media name and transport address)

But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields are
not required.


Thanks,
Sudhir


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

------_=_NextPart_001_01C193C1.4D659A40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Reserve Value and Reserve Group</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sudhir Kumar Appana [<A =
HREF=3D"mailto:sudhirk@future.futsoft.com">mailto:sudhirk@future.futsoft=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Saturday, December 29, 2001 1:27 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: Sudhir (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Reserve Value and Reserve =
Group</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR><FONT SIZE=3D2>In the RFC 3015, following is given in section 7.1.8 =
(Local and Remote</FONT>
<BR><FONT SIZE=3D2>Descriptors):</FONT>
<BR><FONT SIZE=3D2>&quot;If ReserveGroup is true, the MG reserves the =
resources required to</FONT>
<BR><FONT SIZE=3D2>support any of the requested property group =
alternatives that it can</FONT>
<BR><FONT SIZE=3D2>currently support.&nbsp; If ReserveValue is true, =
the MG reserves the</FONT>
<BR><FONT SIZE=3D2>resources required to support any of the requested =
property value</FONT>
<BR><FONT SIZE=3D2>alternatives that it can currently =
support.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>In the above statement, I want to know &quot;what is =
property group and what is</FONT>
<BR><FONT SIZE=3D2>property value&quot;. Where can I get more =
information on this. I referred</FONT>
<BR><FONT SIZE=3D2>SDP RFC 2327, in that Session level Description and =
Media level Description</FONT>
<BR><FONT SIZE=3D2>are differentiated. But I could not conclude from =
this.</FONT>
</P>

<P><FONT SIZE=3D2>In RFC 3015 Appendix-A section-A.1.2 Step-12, Local =
Descriptor defines two</FONT>
<BR><FONT SIZE=3D2>Session level descriptions. Can anybody mail me how =
can I interpret this,</FONT>
<BR><FONT SIZE=3D2>as property groups or as property values. I will be =
happy, if somebody</FONT>
<BR><FONT SIZE=3D2>explains this with some example packets.</FONT>
</P>

<P><FONT SIZE=3D2>One more doubt regarding SDP Paramters:</FONT>
<BR><FONT SIZE=3D2>In SDP RFC 2327, it is given that following fields =
are mandatory:</FONT>
<BR><FONT SIZE=3D2>For 'Session description':</FONT>
<BR><FONT SIZE=3D2>v=3D&nbsp; (protocol version)</FONT>
<BR><FONT SIZE=3D2>o=3D&nbsp; (owner/creator and session =
identifier).</FONT>
<BR><FONT SIZE=3D2>s=3D&nbsp; (session name)</FONT>
<BR><FONT SIZE=3D2>For 'Time description':</FONT>
<BR><FONT SIZE=3D2>t=3D&nbsp; (time the session is active)</FONT>
</P>

<P><FONT SIZE=3D2>For 'Media description':</FONT>
<BR><FONT SIZE=3D2>m=3D&nbsp; (media name and transport address)</FONT>
</P>

<P><FONT SIZE=3D2>But in call flows given in RFC 3015 Appendix A and in =
'draft-madhu-megaco-</FONT>
<BR><FONT SIZE=3D2>callflows-00.txt', I haven't found fields 'o=3D' and =
's=3D'. Are this fields are</FONT>
<BR><FONT SIZE=3D2>not required.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Sudhir</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C193C1.4D659A40--

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


From daemon@ns.ietf.org  Wed Jan  2 14:24:32 2002
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 OAA08995
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:24:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17560
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:24:34 -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 OAA17326;
	Wed, 2 Jan 2002 14:13:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17294
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:13:55 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08819
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:13:52 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JDNi11040;
	Wed, 2 Jan 2002 14:13:23 -0500 (EST)
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 g02JDLK26804;
	Wed, 2 Jan 2002 14:13:22 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFAA>; Wed, 2 Jan 2002 14:11:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Wed, 2 Jan 2002 14:11:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C193C1.4D659A40"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C193C1.4D659A40
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Saturday, December 29, 2001 1:27 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Reserve Value and Reserve Group


Hi,
In the RFC 3015, following is given in section 7.1.8 (Local and Remote
Descriptors):
"If ReserveGroup is true, the MG reserves the resources required to
support any of the requested property group alternatives that it can
currently support.  If ReserveValue is true, the MG reserves the
resources required to support any of the requested property value
alternatives that it can currently support."

In the above statement, I want to know "what is property group and what is
property value". Where can I get more information on this. I referred
SDP RFC 2327, in that Session level Description and Media level Description
are differentiated. But I could not conclude from this.

In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
Session level descriptions. Can anybody mail me how can I interpret this,
as property groups or as property values. I will be happy, if somebody
explains this with some example packets.

One more doubt regarding SDP Paramters:
In SDP RFC 2327, it is given that following fields are mandatory:
For 'Session description':
v=  (protocol version)
o=  (owner/creator and session identifier).
s=  (session name)
For 'Time description':
t=  (time the session is active)

For 'Media description':
m=  (media name and transport address)

But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields are
not required.


Thanks,
Sudhir


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

------_=_NextPart_001_01C193C1.4D659A40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Reserve Value and Reserve Group</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sudhir Kumar Appana [<A =
HREF=3D"mailto:sudhirk@future.futsoft.com">mailto:sudhirk@future.futsoft=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Saturday, December 29, 2001 1:27 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: Sudhir (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Reserve Value and Reserve =
Group</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR><FONT SIZE=3D2>In the RFC 3015, following is given in section 7.1.8 =
(Local and Remote</FONT>
<BR><FONT SIZE=3D2>Descriptors):</FONT>
<BR><FONT SIZE=3D2>&quot;If ReserveGroup is true, the MG reserves the =
resources required to</FONT>
<BR><FONT SIZE=3D2>support any of the requested property group =
alternatives that it can</FONT>
<BR><FONT SIZE=3D2>currently support.&nbsp; If ReserveValue is true, =
the MG reserves the</FONT>
<BR><FONT SIZE=3D2>resources required to support any of the requested =
property value</FONT>
<BR><FONT SIZE=3D2>alternatives that it can currently =
support.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>In the above statement, I want to know &quot;what is =
property group and what is</FONT>
<BR><FONT SIZE=3D2>property value&quot;. Where can I get more =
information on this. I referred</FONT>
<BR><FONT SIZE=3D2>SDP RFC 2327, in that Session level Description and =
Media level Description</FONT>
<BR><FONT SIZE=3D2>are differentiated. But I could not conclude from =
this.</FONT>
</P>

<P><FONT SIZE=3D2>In RFC 3015 Appendix-A section-A.1.2 Step-12, Local =
Descriptor defines two</FONT>
<BR><FONT SIZE=3D2>Session level descriptions. Can anybody mail me how =
can I interpret this,</FONT>
<BR><FONT SIZE=3D2>as property groups or as property values. I will be =
happy, if somebody</FONT>
<BR><FONT SIZE=3D2>explains this with some example packets.</FONT>
</P>

<P><FONT SIZE=3D2>One more doubt regarding SDP Paramters:</FONT>
<BR><FONT SIZE=3D2>In SDP RFC 2327, it is given that following fields =
are mandatory:</FONT>
<BR><FONT SIZE=3D2>For 'Session description':</FONT>
<BR><FONT SIZE=3D2>v=3D&nbsp; (protocol version)</FONT>
<BR><FONT SIZE=3D2>o=3D&nbsp; (owner/creator and session =
identifier).</FONT>
<BR><FONT SIZE=3D2>s=3D&nbsp; (session name)</FONT>
<BR><FONT SIZE=3D2>For 'Time description':</FONT>
<BR><FONT SIZE=3D2>t=3D&nbsp; (time the session is active)</FONT>
</P>

<P><FONT SIZE=3D2>For 'Media description':</FONT>
<BR><FONT SIZE=3D2>m=3D&nbsp; (media name and transport address)</FONT>
</P>

<P><FONT SIZE=3D2>But in call flows given in RFC 3015 Appendix A and in =
'draft-madhu-megaco-</FONT>
<BR><FONT SIZE=3D2>callflows-00.txt', I haven't found fields 'o=3D' and =
's=3D'. Are this fields are</FONT>
<BR><FONT SIZE=3D2>not required.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Sudhir</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C193C1.4D659A40--

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



From megaco-admin@ietf.org  Wed Jan  2 14:36:22 2002
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 OAA09176
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:36:22 -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 OAA17721;
	Wed, 2 Jan 2002 14:27:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17685
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:27:37 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09082
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:35 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JR6i12789
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:06 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JR4105315
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:04 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFNA>; Wed, 2 Jan 2002 14:25:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc'" <gokulc@future.futsoft.com>, megaco <megaco@ietf.org>
Subject: RE: [Megaco] Re: maxTerminationsPerContext
Date: Wed, 2 Jan 2002 14:25:31 -0500 
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

Error code 434 is defined for this purpose.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 2:01 AM
To: megaco
Subject: [Megaco] Re: maxTerminationsPerContext


Hi,

If the maxTerminationsPerContext is set to 2, and an attempt is made to
include
third termination into the context, what would be the error code returned.

It seems that

400 - Bad Request

is the relevant one.

gokul


_______________________________________________
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


From megaco-admin@ietf.org  Wed Jan  2 14:36:48 2002
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 OAA09204
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:36:48 -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 OAA17863;
	Wed, 2 Jan 2002 14:30:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17816
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:30:07 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09104
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:30:05 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JTai13047
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:29:36 -0500 (EST)
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 g02JTYK27808
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:29:35 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFPA>; Wed, 2 Jan 2002 14:27:56 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C90@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor
Date: Wed, 2 Jan 2002 14:28:01 -0500 
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

It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 14:36:48 2002
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 OAA09212
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:36:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA18327
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:36:50 -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 OAA17863;
	Wed, 2 Jan 2002 14:30:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17816
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:30:07 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09104
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:30:05 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JTai13047
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:29:36 -0500 (EST)
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 g02JTYK27808
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:29:35 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFPA>; Wed, 2 Jan 2002 14:27:56 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C90@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor
Date: Wed, 2 Jan 2002 14:28:01 -0500 
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

It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 14:37:15 2002
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 OAA09259
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:37:15 -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 OAA17667;
	Wed, 2 Jan 2002 14:26:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17620
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:26:19 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09035
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:26:17 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JPmi12676
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:25:48 -0500 (EST)
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 g02JPkK27632
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:25:47 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFM1>; Wed, 2 Jan 2002 14:24:08 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Wed, 2 Jan 2002 14:24:11 -0500 
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

A "property group" is the same as a session description.  ReserveGroup=true
says to reserve resources to support all of the session descriptions
presented.

ReserveValue=true definitely says that if multiple payload types are
presented on the same m= line, resources should be reserved for all of them.
The grey area is if there are multiple m= lines within the same session
description.  I propose the interpretation that ReserveValue=true reserves
all resources within the same session description.

I believe a further interpretation is needed as follows:

  ReserveValue=true, ReserveGroup=false, multiple session descriptions
presented:
  --------------
 means that the MG chooses its preferred session description, then reserves
all resources specified therein.

  ReserveValue=false, ReserveGroup=true, multiple session descriptions
presented:
  --------------
 means that the MG reserves resources for every session description, but
within each session description, where any m= line presents alternative
payload types, the MG chooses just one of the alternatives. 

I suspect it may be simpler to use the FID mechanism
(draft-ietf-mmusic-fid-05.txt) when it is finished.

As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in the
MGC-to-MG direction.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Saturday, December 29, 2001 1:27 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Reserve Value and Reserve Group


Hi,
In the RFC 3015, following is given in section 7.1.8 (Local and Remote
Descriptors):
"If ReserveGroup is true, the MG reserves the resources required to
support any of the requested property group alternatives that it can
currently support.  If ReserveValue is true, the MG reserves the
resources required to support any of the requested property value
alternatives that it can currently support."

In the above statement, I want to know "what is property group and what is
property value". Where can I get more information on this. I referred
SDP RFC 2327, in that Session level Description and Media level Description
are differentiated. But I could not conclude from this.

In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
Session level descriptions. Can anybody mail me how can I interpret this,
as property groups or as property values. I will be happy, if somebody
explains this with some example packets.

One more doubt regarding SDP Paramters:
In SDP RFC 2327, it is given that following fields are mandatory:
For 'Session description':
v=  (protocol version)
o=  (owner/creator and session identifier).
s=  (session name)
For 'Time description':
t=  (time the session is active)

For 'Media description':
m=  (media name and transport address)

But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields are
not required.


Thanks,
Sudhir


_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 14:37:16 2002
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 OAA09268
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:37:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA18347
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:37: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 OAA17667;
	Wed, 2 Jan 2002 14:26:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17620
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:26:19 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09035
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:26:17 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JPmi12676
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:25:48 -0500 (EST)
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 g02JPkK27632
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:25:47 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFM1>; Wed, 2 Jan 2002 14:24:08 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Wed, 2 Jan 2002 14:24:11 -0500 
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

A "property group" is the same as a session description.  ReserveGroup=true
says to reserve resources to support all of the session descriptions
presented.

ReserveValue=true definitely says that if multiple payload types are
presented on the same m= line, resources should be reserved for all of them.
The grey area is if there are multiple m= lines within the same session
description.  I propose the interpretation that ReserveValue=true reserves
all resources within the same session description.

I believe a further interpretation is needed as follows:

  ReserveValue=true, ReserveGroup=false, multiple session descriptions
presented:
  --------------
 means that the MG chooses its preferred session description, then reserves
all resources specified therein.

  ReserveValue=false, ReserveGroup=true, multiple session descriptions
presented:
  --------------
 means that the MG reserves resources for every session description, but
within each session description, where any m= line presents alternative
payload types, the MG chooses just one of the alternatives. 

I suspect it may be simpler to use the FID mechanism
(draft-ietf-mmusic-fid-05.txt) when it is finished.

As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in the
MGC-to-MG direction.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Saturday, December 29, 2001 1:27 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Reserve Value and Reserve Group


Hi,
In the RFC 3015, following is given in section 7.1.8 (Local and Remote
Descriptors):
"If ReserveGroup is true, the MG reserves the resources required to
support any of the requested property group alternatives that it can
currently support.  If ReserveValue is true, the MG reserves the
resources required to support any of the requested property value
alternatives that it can currently support."

In the above statement, I want to know "what is property group and what is
property value". Where can I get more information on this. I referred
SDP RFC 2327, in that Session level Description and Media level Description
are differentiated. But I could not conclude from this.

In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
Session level descriptions. Can anybody mail me how can I interpret this,
as property groups or as property values. I will be happy, if somebody
explains this with some example packets.

One more doubt regarding SDP Paramters:
In SDP RFC 2327, it is given that following fields are mandatory:
For 'Session description':
v=  (protocol version)
o=  (owner/creator and session identifier).
s=  (session name)
For 'Time description':
t=  (time the session is active)

For 'Media description':
m=  (media name and transport address)

But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields are
not required.


Thanks,
Sudhir


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 14:40:18 2002
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 OAA09368
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:40:18 -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 OAA18263;
	Wed, 2 Jan 2002 14:33:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18235
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:33:26 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09152
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:33:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JWsi13363;
	Wed, 2 Jan 2002 14:32:54 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JWq105572;
	Wed, 2 Jan 2002 14:32:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFRM>; Wed, 2 Jan 2002 14:31:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C91@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'deepak nagrath'" <deepaknagrath@yahoo.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>, megaco@ietf.org
Subject: RE: [Megaco] Script Handling in Megaco
Date: Wed, 2 Jan 2002 14:31:16 -0500 
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

The question has come up a couple of times, and the response has been that
the requirement isn't really there.  Hence v2 introduces no new scripting
capability.

I'll note that signals provide a very powerful way of invoking operations
which have nbeen predefined on the MG.

-----Original Message-----
From: deepak nagrath [mailto:deepaknagrath@yahoo.com]
Sent: Saturday, December 29, 2001 2:40 PM
To: Madhu Babu Brahmanapally; megaco@ietf.org
Cc: deepaknagrath@yahoo.com
Subject: [Megaco] Script Handling in Megaco



Hi LIST,
   Is there any decision/disscussion made regarding
handling of "scripts invocation by MGC" issue.

 Regards,
- Deepak

--- Madhu Babu Brahmanapally <madhubabu@kenetec.com>
wrote:
> Hi Deepak,
> I think you are addressing some thing related to
> invoking of scripts(files
> storage).. which the MGC is aware of. If yes, IMO
> version 1 of Megaco is not
> addressing this. The scripts invocation by the MGC
> will be addressed in
> Version 2 of Megaco.
> 
> Regards
> Madhubabu
> 
> -----Original Message-----
> From: owner-megaco@pit.comms.marconi.com
> [mailto:owner-megaco@pit.comms.marconi.com]On Behalf
> Of deepak nagrath
> Sent: Friday, April 13, 2001 10:05 AM
> To: megaco@fore.com
> Subject: ivr
> 
> 
> 
>  Hi,
>    I have some basic questions regarding ivr
> implementation using megaco:
>    1) Can we take IVR resource as termination at MG.
> For comparison, we don't take tone generation h/w as
> termination.
>    2)Voice files storage.
> Are these files stored at media gateway ( can be
> simple or complex announcements). How they are
> handled.
> 
>  Regards,
> - Deepak
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
> 


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 14:40:19 2002
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 OAA09377
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:40:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA18459
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:40:20 -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 OAA18263;
	Wed, 2 Jan 2002 14:33:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18235
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:33:26 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09152
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:33:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JWsi13363;
	Wed, 2 Jan 2002 14:32:54 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JWq105572;
	Wed, 2 Jan 2002 14:32:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFRM>; Wed, 2 Jan 2002 14:31:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C91@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'deepak nagrath'" <deepaknagrath@yahoo.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>, megaco@ietf.org
Subject: RE: [Megaco] Script Handling in Megaco
Date: Wed, 2 Jan 2002 14:31:16 -0500 
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

The question has come up a couple of times, and the response has been that
the requirement isn't really there.  Hence v2 introduces no new scripting
capability.

I'll note that signals provide a very powerful way of invoking operations
which have nbeen predefined on the MG.

-----Original Message-----
From: deepak nagrath [mailto:deepaknagrath@yahoo.com]
Sent: Saturday, December 29, 2001 2:40 PM
To: Madhu Babu Brahmanapally; megaco@ietf.org
Cc: deepaknagrath@yahoo.com
Subject: [Megaco] Script Handling in Megaco



Hi LIST,
   Is there any decision/disscussion made regarding
handling of "scripts invocation by MGC" issue.

 Regards,
- Deepak

--- Madhu Babu Brahmanapally <madhubabu@kenetec.com>
wrote:
> Hi Deepak,
> I think you are addressing some thing related to
> invoking of scripts(files
> storage).. which the MGC is aware of. If yes, IMO
> version 1 of Megaco is not
> addressing this. The scripts invocation by the MGC
> will be addressed in
> Version 2 of Megaco.
> 
> Regards
> Madhubabu
> 
> -----Original Message-----
> From: owner-megaco@pit.comms.marconi.com
> [mailto:owner-megaco@pit.comms.marconi.com]On Behalf
> Of deepak nagrath
> Sent: Friday, April 13, 2001 10:05 AM
> To: megaco@fore.com
> Subject: ivr
> 
> 
> 
>  Hi,
>    I have some basic questions regarding ivr
> implementation using megaco:
>    1) Can we take IVR resource as termination at MG.
> For comparison, we don't take tone generation h/w as
> termination.
>    2)Voice files storage.
> Are these files stored at media gateway ( can be
> simple or complex announcements). How they are
> handled.
> 
>  Regards,
> - Deepak
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
> 


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 15:02:49 2002
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 PAA09747
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:02:49 -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 OAA18424;
	Wed, 2 Jan 2002 14:39:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18388
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:38:13 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09322
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:38:11 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jbgi13878;
	Wed, 2 Jan 2002 14:37:42 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jbe105827;
	Wed, 2 Jan 2002 14:37:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRF49>; Wed, 2 Jan 2002 14:36:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C92@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'vibansal@hss.hns.com'" <vibansal@hss.hns.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Wed, 2 Jan 2002 14:36:02 -0500 
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

The immAckRequired flag was introduced because without it a protocol glitch
was possible, so what you postulate is not a nice situation.  Anyway, to
answer your question, I would say that retransmission of the final response
(with exponential backoff) is necessary until an acknowledgement is
received.

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Sunday, December 30, 2001 8:23 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding immAckRequired field.





Hi

I have a doubt regarding immAckRequired field.

Section D.1.4 says

"An entity that sends a provisional response, SHALL include the
immAckRequired
field in the ensuing final response, indicating that an immediate
confirmation
is expected."


Now what would happen, if the entity receiving the final response with
immAckRequired field, does not send the immediate confirmation? In this case
do
we need to retransmit the response till we get the confirmation?

Please clarify.

Regards
Vivek



_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 15:02:50 2002
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 PAA09757
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:02:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA19780
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 15:02:52 -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 OAA18424;
	Wed, 2 Jan 2002 14:39:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18388
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:38:13 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09322
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:38:11 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jbgi13878;
	Wed, 2 Jan 2002 14:37:42 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jbe105827;
	Wed, 2 Jan 2002 14:37:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRF49>; Wed, 2 Jan 2002 14:36:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C92@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'vibansal@hss.hns.com'" <vibansal@hss.hns.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Wed, 2 Jan 2002 14:36:02 -0500 
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

The immAckRequired flag was introduced because without it a protocol glitch
was possible, so what you postulate is not a nice situation.  Anyway, to
answer your question, I would say that retransmission of the final response
(with exponential backoff) is necessary until an acknowledgement is
received.

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Sunday, December 30, 2001 8:23 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding immAckRequired field.





Hi

I have a doubt regarding immAckRequired field.

Section D.1.4 says

"An entity that sends a provisional response, SHALL include the
immAckRequired
field in the ensuing final response, indicating that an immediate
confirmation
is expected."


Now what would happen, if the entity receiving the final response with
immAckRequired field, does not send the immediate confirmation? In this case
do
we need to retransmit the response till we get the confirmation?

Please clarify.

Regards
Vivek



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 15:09:20 2002
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 PAA09857
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:09:20 -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 OAA18658;
	Wed, 2 Jan 2002 14:43:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18629
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:43:39 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09453
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:43:36 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jh3i14419;
	Wed, 2 Jan 2002 14:43:03 -0500 (EST)
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 g02Jh2K28460;
	Wed, 2 Jan 2002 14:43:02 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFZN>; Wed, 2 Jan 2002 14:41:23 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADAE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'mmraju@lucent.com'" <mmraju@lucent.com>,
        zhangzhong
	 <zhangzhong@huawei.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 14:41:19 -0500 
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

If I summarize your argument, it is that the MGC should not try to manage
the raw resources (e.g. DSP MIPS) on the MG, but should have available
normalized estimates of gross capacity.  The most straightforward way of
achieving this is to define a package with the appropriate properties on
ROOT.  The technicalities of how you would define the properties (in terms
of simultaneous and alternative capabilities) are rather complex, but the
package mechanism would let us hive off the work.



-----Original Message-----
From: Raju [mailto:mmraju@lucent.com]
Sent: Monday, December 31, 2001 9:56 AM
To: zhangzhong; Madhu Babu Brahmanapally
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on
RFC2805


I do agree with Zhangzhong.

Infact calculation of available resources by MGC becomes more tough and
ambigous if the GW supports more than one codec
(e.g. G.723 and G.711), which is generally be the case.
The number of available G.711 codecs depends on the number of G.723 codecs
in use, as G.723 uses more MIPS.
MGC can't understand these dependencies and calculate the exact number of
free resources available, only MG
knows how eactly to calculate the free or available resources.

Pls read my previous mail below.

Thanks
Raju

> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> zhangzhong
> Sent: Friday, December 28, 2001 9:17 PM
> To: Madhu Babu Brahmanapally; 'Shashi Kumar'
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
>
>
> Hi all,
> 1  I think the method below can  reach the aim in theory , It is
> a idea in the present protocol, but not very good. And Because it
> is very ambiguous . It will introduct the difficulity of
> interwork between MGC and MGW with more difficulity. If the MGW
> has a big capability , the management of these termination has problems .
> The method is not the idea of MEGACO, because  operations of
> sending tone or playing announcemnt  are all done on  the same
> termination which receive/send media from/to outside not specified.
>
>
> Thans for your reply and help.
> Regards
> Zhangzhong
>
>
> ----- Original Message -----
> Hi Zhangzhong,
>
> as of current understanding we should admit that there is no direct was
> of doing, but we have the information with in the Megaco scope to do
> this.
>
> we shall take your specific example of G.711 resource issue...
> 1. Each G.711 resource is identified as a Termination (using Termination
> ID), which is a provisioned info( or otherwise)
> 2. At any Given point of time, you know how many termination's are in
> (a) context(s) ( in both MG and MGC instance of protocol), which shall
> be take as G.711 resource which is busy....
>
> with the above info it is very easy to identify how many of G.711
> resource are free...
>
> hope this helps...
>
> shashi
>
>
>
>
> ----- Original Message -----
> From: Madhu Babu Brahmanapally <madhubabu@kenetec.com>
> To: 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 28, 2001 10:44 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the requirement
> on RFC2805
>
>
> > HI Shashi,All,
> > Its true that Audit will help MGC to reconcile the
> inconsistency. But for
> > the specific scenario Zhang has pointed, How this resource
> information is
> > exchanged between the MG and the MGC. According to my knowledge
> there is no
> > parameter or anything as such to "quantitatively" identify G711
> or any such
> > channel resource.
> > Regards
> > Madhubabu
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> > Shashi Kumar
> > Sent: Thursday, December 27, 2001 11:55 PM
> > To: zhangzhong
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > we have provision to audit the MG resource, which clearlty defined by
> > Megaco/H.248. By means of Auduting the MG resources we can always
> > "reconcile inconsistencies between the MGC and the MG"
> >
> > thanks,
> > shashi
> >
> >
> > > zhangzhong wrote:
> > >
> > > Hi :
> > > In the rfc 2805, there have a request to H.248:
> > >         Provide a mechanism to discover the current available
> > > resources
> > >         in the MG, where resources are dynamically consumed by
> > >         connections and the MGC cannot reasonably or reliably track
> > > the
> > >         consumption of such resources. It should also be possible to
> > >         discover resources currently in use, in order to reconcile
> > >         inconsistencies between the MGC and the MG.
> > >
> > > This means MGC can know the resource consume in the MGW , for example
> > > , if There have 1000 G.711 channel resource , if 500 is busy , How can
> > > MGC know this through RFC3015?
> > > If can't , The RFC3015 is inconsist with the RFC2805
> > >
> > > Thanks for the reply.
> > > Regards
> > > Zhangzhong
> >
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 15:09:21 2002
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 PAA09867
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:09:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA20011
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 15:09:23 -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 OAA18658;
	Wed, 2 Jan 2002 14:43:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA18629
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:43:39 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09453
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:43:36 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Jh3i14419;
	Wed, 2 Jan 2002 14:43:03 -0500 (EST)
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 g02Jh2K28460;
	Wed, 2 Jan 2002 14:43:02 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFZN>; Wed, 2 Jan 2002 14:41:23 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADAE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'mmraju@lucent.com'" <mmraju@lucent.com>,
        zhangzhong
	 <zhangzhong@huawei.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Wed, 2 Jan 2002 14:41:19 -0500 
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

If I summarize your argument, it is that the MGC should not try to manage
the raw resources (e.g. DSP MIPS) on the MG, but should have available
normalized estimates of gross capacity.  The most straightforward way of
achieving this is to define a package with the appropriate properties on
ROOT.  The technicalities of how you would define the properties (in terms
of simultaneous and alternative capabilities) are rather complex, but the
package mechanism would let us hive off the work.



-----Original Message-----
From: Raju [mailto:mmraju@lucent.com]
Sent: Monday, December 31, 2001 9:56 AM
To: zhangzhong; Madhu Babu Brahmanapally
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on
RFC2805


I do agree with Zhangzhong.

Infact calculation of available resources by MGC becomes more tough and
ambigous if the GW supports more than one codec
(e.g. G.723 and G.711), which is generally be the case.
The number of available G.711 codecs depends on the number of G.723 codecs
in use, as G.723 uses more MIPS.
MGC can't understand these dependencies and calculate the exact number of
free resources available, only MG
knows how eactly to calculate the free or available resources.

Pls read my previous mail below.

Thanks
Raju

> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> zhangzhong
> Sent: Friday, December 28, 2001 9:17 PM
> To: Madhu Babu Brahmanapally; 'Shashi Kumar'
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
>
>
> Hi all,
> 1  I think the method below can  reach the aim in theory , It is
> a idea in the present protocol, but not very good. And Because it
> is very ambiguous . It will introduct the difficulity of
> interwork between MGC and MGW with more difficulity. If the MGW
> has a big capability , the management of these termination has problems .
> The method is not the idea of MEGACO, because  operations of
> sending tone or playing announcemnt  are all done on  the same
> termination which receive/send media from/to outside not specified.
>
>
> Thans for your reply and help.
> Regards
> Zhangzhong
>
>
> ----- Original Message -----
> Hi Zhangzhong,
>
> as of current understanding we should admit that there is no direct was
> of doing, but we have the information with in the Megaco scope to do
> this.
>
> we shall take your specific example of G.711 resource issue...
> 1. Each G.711 resource is identified as a Termination (using Termination
> ID), which is a provisioned info( or otherwise)
> 2. At any Given point of time, you know how many termination's are in
> (a) context(s) ( in both MG and MGC instance of protocol), which shall
> be take as G.711 resource which is busy....
>
> with the above info it is very easy to identify how many of G.711
> resource are free...
>
> hope this helps...
>
> shashi
>
>
>
>
> ----- Original Message -----
> From: Madhu Babu Brahmanapally <madhubabu@kenetec.com>
> To: 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, December 28, 2001 10:44 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the requirement
> on RFC2805
>
>
> > HI Shashi,All,
> > Its true that Audit will help MGC to reconcile the
> inconsistency. But for
> > the specific scenario Zhang has pointed, How this resource
> information is
> > exchanged between the MG and the MGC. According to my knowledge
> there is no
> > parameter or anything as such to "quantitatively" identify G711
> or any such
> > channel resource.
> > Regards
> > Madhubabu
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> > Shashi Kumar
> > Sent: Thursday, December 27, 2001 11:55 PM
> > To: zhangzhong
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > we have provision to audit the MG resource, which clearlty defined by
> > Megaco/H.248. By means of Auduting the MG resources we can always
> > "reconcile inconsistencies between the MGC and the MG"
> >
> > thanks,
> > shashi
> >
> >
> > > zhangzhong wrote:
> > >
> > > Hi :
> > > In the rfc 2805, there have a request to H.248:
> > >         Provide a mechanism to discover the current available
> > > resources
> > >         in the MG, where resources are dynamically consumed by
> > >         connections and the MGC cannot reasonably or reliably track
> > > the
> > >         consumption of such resources. It should also be possible to
> > >         discover resources currently in use, in order to reconcile
> > >         inconsistencies between the MGC and the MG.
> > >
> > > This means MGC can know the resource consume in the MGW , for example
> > > , if There have 1000 G.711 channel resource , if 500 is busy , How can
> > > MGC know this through RFC3015?
> > > If can't , The RFC3015 is inconsist with the RFC2805
> > >
> > > Thanks for the reply.
> > > Regards
> > > Zhangzhong
> >
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 15:15:01 2002
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 PAA09939
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:15:00 -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 PAA19879;
	Wed, 2 Jan 2002 15:05:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19848
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 15:05:41 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09814
	for <megaco@ietf.org>; Wed, 2 Jan 2002 15:05:38 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBUGN00.I4E; Wed,
          2 Jan 2002 12:05:11 -0800 
Message-ID: <3C336769.B56720BC@encc.com>
Date: Wed, 02 Jan 2002 12:02:49 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org, mgcp@vovida.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] How does H.323 work with MGCP or Megaco?
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: 7bit

Hi:

This might be a stupid question for most of you here, but I couldn't
figured that out yet .....

When I have an H.323 terminal calling to another, say Netmeeting, the
H.245 procedures (OLC) set up the RTP channels between the 2 terminals.

However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
how can I make the MGC know whether it needs to setup the RTP channel
for the MG or the terminal?

What is the difference, in terms of H.225 and H.245 procedures, when
MGCP (or Megaco) is used and when it's not used?

Thanks very much in advance,

Patrick.


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


From daemon@ns.ietf.org  Wed Jan  2 15:15:01 2002
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 PAA09948
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:15:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA20136
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 15:15:03 -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 PAA19879;
	Wed, 2 Jan 2002 15:05:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19848
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 15:05:41 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09814
	for <megaco@ietf.org>; Wed, 2 Jan 2002 15:05:38 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBUGN00.I4E; Wed,
          2 Jan 2002 12:05:11 -0800 
Message-ID: <3C336769.B56720BC@encc.com>
Date: Wed, 02 Jan 2002 12:02:49 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org, mgcp@vovida.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] How does H.323 work with MGCP or Megaco?
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: 7bit

Hi:

This might be a stupid question for most of you here, but I couldn't
figured that out yet .....

When I have an H.323 terminal calling to another, say Netmeeting, the
H.245 procedures (OLC) set up the RTP channels between the 2 terminals.

However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
how can I make the MGC know whether it needs to setup the RTP channel
for the MG or the terminal?

What is the difference, in terms of H.225 and H.245 procedures, when
MGCP (or Megaco) is used and when it's not used?

Thanks very much in advance,

Patrick.


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



From daemon@ns.ietf.org  Wed Jan  2 15:24:31 2002
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 OAA09186
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:36:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA18311
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 14:36:24 -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 OAA17721;
	Wed, 2 Jan 2002 14:27:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17685
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 14:27:37 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09082
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:35 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JR6i12789
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:06 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02JR4105315
	for <megaco@ietf.org>; Wed, 2 Jan 2002 14:27:04 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRFNA>; Wed, 2 Jan 2002 14:25:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA00274C8F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc'" <gokulc@future.futsoft.com>, megaco <megaco@ietf.org>
Subject: RE: [Megaco] Re: maxTerminationsPerContext
Date: Wed, 2 Jan 2002 14:25:31 -0500 
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

Error code 434 is defined for this purpose.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 2:01 AM
To: megaco
Subject: [Megaco] Re: maxTerminationsPerContext


Hi,

If the maxTerminationsPerContext is set to 2, and an attempt is made to
include
third termination into the context, what would be the error code returned.

It seems that

400 - Bad Request

is the relevant one.

gokul


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 15:56:54 2002
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 PAA10682
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:56:53 -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 PAA21259;
	Wed, 2 Jan 2002 15:50:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21230
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 15:50:11 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10593
	for <megaco@ietf.org>; Wed, 2 Jan 2002 15:50:07 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBWIS00.R3Y; Wed,
          2 Jan 2002 12:49:40 -0800 
Message-ID: <3C3371D6.E2E886DC@encc.com>
Date: Wed, 02 Jan 2002 12:47:18 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <3C336769.B56720BC@encc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Actually, to simplify my question a bit, does MGC do H.245?  Or does it
only do H.225 to setup the call, and then use MGCP or Megaco to setup the
RTP channel with the MG?

If it's the former case, how does the MGCP (or Megaco) interact with
H.245?  If it's the later case, how does the MGCs exchange capabilities?

Thanks very much in advance,

Patrick.

Patrick Lam wrote:

> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 15:56:54 2002
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 PAA10695
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 15:56:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA21410
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 15:56:57 -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 PAA21259;
	Wed, 2 Jan 2002 15:50:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21230
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 15:50:11 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10593
	for <megaco@ietf.org>; Wed, 2 Jan 2002 15:50:07 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBWIS00.R3Y; Wed,
          2 Jan 2002 12:49:40 -0800 
Message-ID: <3C3371D6.E2E886DC@encc.com>
Date: Wed, 02 Jan 2002 12:47:18 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <3C336769.B56720BC@encc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Actually, to simplify my question a bit, does MGC do H.245?  Or does it
only do H.225 to setup the call, and then use MGCP or Megaco to setup the
RTP channel with the MG?

If it's the former case, how does the MGCP (or Megaco) interact with
H.245?  If it's the later case, how does the MGCs exchange capabilities?

Thanks very much in advance,

Patrick.

Patrick Lam wrote:

> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 16:20:31 2002
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 QAA10982
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:20:31 -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 QAA22135;
	Wed, 2 Jan 2002 16:13:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22042
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:13:06 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10887
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:13:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LCXi06421;
	Wed, 2 Jan 2002 16:12:33 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LCV116431;
	Wed, 2 Jan 2002 16:12:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRHZM>; Wed, 2 Jan 2002 16:10:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADAF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Patrick Lam'" <plam@encc.com>, megaco@ietf.org, mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:10:57 -0500 
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

Assuming the MG supports either MGCP or Megaco with text encoding, you end
up having to do a translation between H.245 and SDP.  In the capability
exchange phase, the MGC may use capabilities gleaned via an AuditCapability
request.  OpenLogicalChannel has to be mapped into the appropriate Local
and/or Remote descriptor content.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 3:03 PM
To: megaco@ietf.org; mgcp@vovida.org
Subject: [Megaco] How does H.323 work with MGCP or Megaco?


Hi:

This might be a stupid question for most of you here, but I couldn't
figured that out yet .....

When I have an H.323 terminal calling to another, say Netmeeting, the
H.245 procedures (OLC) set up the RTP channels between the 2 terminals.

However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
how can I make the MGC know whether it needs to setup the RTP channel
for the MG or the terminal?

What is the difference, in terms of H.225 and H.245 procedures, when
MGCP (or Megaco) is used and when it's not used?

Thanks very much in advance,

Patrick.


_______________________________________________
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


From daemon@ns.ietf.org  Wed Jan  2 16:20:32 2002
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 QAA10991
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:20:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA22192
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 16:20:34 -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 QAA22135;
	Wed, 2 Jan 2002 16:13:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22042
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:13:06 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10887
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:13:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LCXi06421;
	Wed, 2 Jan 2002 16:12:33 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LCV116431;
	Wed, 2 Jan 2002 16:12:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRHZM>; Wed, 2 Jan 2002 16:10:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADAF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Patrick Lam'" <plam@encc.com>, megaco@ietf.org, mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:10:57 -0500 
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

Assuming the MG supports either MGCP or Megaco with text encoding, you end
up having to do a translation between H.245 and SDP.  In the capability
exchange phase, the MGC may use capabilities gleaned via an AuditCapability
request.  OpenLogicalChannel has to be mapped into the appropriate Local
and/or Remote descriptor content.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 3:03 PM
To: megaco@ietf.org; mgcp@vovida.org
Subject: [Megaco] How does H.323 work with MGCP or Megaco?


Hi:

This might be a stupid question for most of you here, but I couldn't
figured that out yet .....

When I have an H.323 terminal calling to another, say Netmeeting, the
H.245 procedures (OLC) set up the RTP channels between the 2 terminals.

However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
how can I make the MGC know whether it needs to setup the RTP channel
for the MG or the terminal?

What is the difference, in terms of H.225 and H.245 procedures, when
MGCP (or Megaco) is used and when it's not used?

Thanks very much in advance,

Patrick.


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  2 16:35:20 2002
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 QAA11224
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:35:20 -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 QAA22363;
	Wed, 2 Jan 2002 16:26:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22336
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:26:03 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11061
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:26:00 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFO61487;
	Wed, 2 Jan 2002 16:25:20 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Patrick Lam'" <plam@encc.com>, <megaco@ietf.org>, <mgcp@vovida.org>
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:24:00 -0500
Message-ID: <038b01c193d3$cc66db80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <3C3371D6.E2E886DC@encc.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Pat,
Yes, the MGC should do all the H.323 signaling with the H.323 Endpoint. I
mean both H.225 and H.245. The MGC will map the H.245 OLC information to the
local and remote descriptors. The MGC will talk to the 323 terminal in H.225
and H.245 and in MEGACO or MGCP towards the MG.

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Patrick Lam
Sent: Wednesday, January 02, 2002 3:47 PM
To: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Actually, to simplify my question a bit, does MGC do H.245?  Or does it
only do H.225 to setup the call, and then use MGCP or Megaco to setup the
RTP channel with the MG?

If it's the former case, how does the MGCP (or Megaco) interact with
H.245?  If it's the later case, how does the MGCs exchange capabilities?

Thanks very much in advance,

Patrick.

Patrick Lam wrote:

> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 16:35:20 2002
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 QAA11233
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:35:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23065
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 16:35:23 -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 QAA22363;
	Wed, 2 Jan 2002 16:26:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22336
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:26:03 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11061
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:26:00 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFO61487;
	Wed, 2 Jan 2002 16:25:20 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Patrick Lam'" <plam@encc.com>, <megaco@ietf.org>, <mgcp@vovida.org>
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:24:00 -0500
Message-ID: <038b01c193d3$cc66db80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <3C3371D6.E2E886DC@encc.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Pat,
Yes, the MGC should do all the H.323 signaling with the H.323 Endpoint. I
mean both H.225 and H.245. The MGC will map the H.245 OLC information to the
local and remote descriptors. The MGC will talk to the 323 terminal in H.225
and H.245 and in MEGACO or MGCP towards the MG.

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Patrick Lam
Sent: Wednesday, January 02, 2002 3:47 PM
To: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Actually, to simplify my question a bit, does MGC do H.245?  Or does it
only do H.225 to setup the call, and then use MGCP or Megaco to setup the
RTP channel with the MG?

If it's the former case, how does the MGCP (or Megaco) interact with
H.245?  If it's the later case, how does the MGCs exchange capabilities?

Thanks very much in advance,

Patrick.

Patrick Lam wrote:

> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 16:35:23 2002
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 QAA11250
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:35:23 -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 QAA22302;
	Wed, 2 Jan 2002 16:24:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22273
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:24:17 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11048
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:24:13 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBY3M00.E48; Wed,
          2 Jan 2002 13:23:46 -0800 
Message-ID: <3C3379D4.76B7F5B3@encc.com>
Date: Wed, 02 Jan 2002 13:21:24 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <4D79C746863DD51197690002A52CDA000102ADAF@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 16:35:24 2002
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 QAA11262
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:35:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23079
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 16:35:26 -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 QAA22302;
	Wed, 2 Jan 2002 16:24:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22273
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:24:17 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11048
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:24:13 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBY3M00.E48; Wed,
          2 Jan 2002 13:23:46 -0800 
Message-ID: <3C3379D4.76B7F5B3@encc.com>
Date: Wed, 02 Jan 2002 13:21:24 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <4D79C746863DD51197690002A52CDA000102ADAF@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 16:42:18 2002
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 QAA11401
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:42:18 -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 QAA22909;
	Wed, 2 Jan 2002 16:32:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22881
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:32:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11193
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:32:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LWDi08273;
	Wed, 2 Jan 2002 16:32:13 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LWB117398;
	Wed, 2 Jan 2002 16:32:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR2M2>; Wed, 2 Jan 2002 16:30:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Patrick Lam'" <plam@encc.com>
Cc: megaco@ietf.org, mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:30:35 -0500 
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

I should have waited to read your second message before reply.

To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
between itself and a remote H.323 entity (which might be another MGC).  It
maps between that and Megaco's Local and Remote descriptors.

I have some sample call flows showing this sort of operation.  If I get a
moment, I'll purge them of proprietary content and post them to the Megaco
supplementary web site.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 4:21 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco
to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an
AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 16:42:19 2002
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 QAA11411
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:42:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23321
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 16:42:22 -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 QAA22909;
	Wed, 2 Jan 2002 16:32:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22881
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:32:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11193
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:32:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LWDi08273;
	Wed, 2 Jan 2002 16:32:13 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02LWB117398;
	Wed, 2 Jan 2002 16:32:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPR2M2>; Wed, 2 Jan 2002 16:30:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Patrick Lam'" <plam@encc.com>
Cc: megaco@ietf.org, mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:30:35 -0500 
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

I should have waited to read your second message before reply.

To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
between itself and a remote H.323 entity (which might be another MGC).  It
maps between that and Megaco's Local and Remote descriptors.

I have some sample call flows showing this sort of operation.  If I get a
moment, I'll purge them of proprietary content and post them to the Megaco
supplementary web site.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 4:21 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco
to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an
AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 16:58:37 2002
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 QAA11762
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:58:37 -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 QAA23477;
	Wed, 2 Jan 2002 16:48:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23448
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:48:32 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11603
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:48:28 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBZ8100.V4G; Wed,
          2 Jan 2002 13:48:01 -0800 
Message-ID: <3C337F83.FF1C196B@encc.com>
Date: Wed, 02 Jan 2002 13:45:39 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

I see ....

Thanks to all who answered this question in such a quick manner.

I really appreciate it.

Patrick.

Tom-PT Taylor wrote:

> I should have waited to read your second message before reply.
>
> To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
> between itself and a remote H.323 entity (which might be another MGC).  It
> maps between that and Megaco's Local and Remote descriptors.
>
> I have some sample call flows showing this sort of operation.  If I get a
> moment, I'll purge them of proprietary content and post them to the Megaco
> supplementary web site.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 4:21 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: megaco@ietf.org; mgcp@vovida.org
> Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Thanks a lot.
>
> Can the MGC not use H.245 though?
>
> What I am thinking is to setup the call using H.225, and use MGCP or Megaco
> to
> setup the RTP channel with the MG?  Does this make sense at all?  Is this
> possible?
>
> Thanks very much again,
>
> Patrick.
>
> Tom-PT Taylor wrote:
>
> > Assuming the MG supports either MGCP or Megaco with text encoding, you end
> > up having to do a translation between H.245 and SDP.  In the capability
> > exchange phase, the MGC may use capabilities gleaned via an
> AuditCapability
> > request.  OpenLogicalChannel has to be mapped into the appropriate Local
> > and/or Remote descriptor content.
> >
> > -----Original Message-----
> > From: Patrick Lam [mailto:plam@encc.com]
> > Sent: Wednesday, January 02, 2002 3:03 PM
> > To: megaco@ietf.org; mgcp@vovida.org
> > Subject: [Megaco] How does H.323 work with MGCP or Megaco?
> >
> > Hi:
> >
> > This might be a stupid question for most of you here, but I couldn't
> > figured that out yet .....
> >
> > When I have an H.323 terminal calling to another, say Netmeeting, the
> > H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
> >
> > However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> > setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> > how can I make the MGC know whether it needs to setup the RTP channel
> > for the MG or the terminal?
> >
> > What is the difference, in terms of H.225 and H.245 procedures, when
> > MGCP (or Megaco) is used and when it's not used?
> >
> > Thanks very much in advance,
> >
> > Patrick.
> >
> > _______________________________________________
> > 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


From daemon@ns.ietf.org  Wed Jan  2 16:58:38 2002
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 QAA11771
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 16:58:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23685
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 16:58:40 -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 QAA23477;
	Wed, 2 Jan 2002 16:48:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23448
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:48:32 -0500 (EST)
Received: from mail.encc.com (corp1.encc.com [207.20.253.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11603
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:48:28 -0500 (EST)
Received: from encc.com ([207.20.253.69]) by mail.encc.com
          (Netscape Messaging Server 4.1) with ESMTP id GPBZ8100.V4G; Wed,
          2 Jan 2002 13:48:01 -0800 
Message-ID: <3C337F83.FF1C196B@encc.com>
Date: Wed, 02 Jan 2002 13:45:39 -0800
From: "Patrick Lam" <plam@encc.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org, mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
References: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

I see ....

Thanks to all who answered this question in such a quick manner.

I really appreciate it.

Patrick.

Tom-PT Taylor wrote:

> I should have waited to read your second message before reply.
>
> To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
> between itself and a remote H.323 entity (which might be another MGC).  It
> maps between that and Megaco's Local and Remote descriptors.
>
> I have some sample call flows showing this sort of operation.  If I get a
> moment, I'll purge them of proprietary content and post them to the Megaco
> supplementary web site.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 4:21 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: megaco@ietf.org; mgcp@vovida.org
> Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Thanks a lot.
>
> Can the MGC not use H.245 though?
>
> What I am thinking is to setup the call using H.225, and use MGCP or Megaco
> to
> setup the RTP channel with the MG?  Does this make sense at all?  Is this
> possible?
>
> Thanks very much again,
>
> Patrick.
>
> Tom-PT Taylor wrote:
>
> > Assuming the MG supports either MGCP or Megaco with text encoding, you end
> > up having to do a translation between H.245 and SDP.  In the capability
> > exchange phase, the MGC may use capabilities gleaned via an
> AuditCapability
> > request.  OpenLogicalChannel has to be mapped into the appropriate Local
> > and/or Remote descriptor content.
> >
> > -----Original Message-----
> > From: Patrick Lam [mailto:plam@encc.com]
> > Sent: Wednesday, January 02, 2002 3:03 PM
> > To: megaco@ietf.org; mgcp@vovida.org
> > Subject: [Megaco] How does H.323 work with MGCP or Megaco?
> >
> > Hi:
> >
> > This might be a stupid question for most of you here, but I couldn't
> > figured that out yet .....
> >
> > When I have an H.323 terminal calling to another, say Netmeeting, the
> > H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
> >
> > However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> > setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> > how can I make the MGC know whether it needs to setup the RTP channel
> > for the MG or the terminal?
> >
> > What is the difference, in terms of H.225 and H.245 procedures, when
> > MGCP (or Megaco) is used and when it's not used?
> >
> > Thanks very much in advance,
> >
> > Patrick.
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Wed Jan  2 17:03:38 2002
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 RAA11892
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 17:03:38 -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 QAA23524;
	Wed, 2 Jan 2002 16:49:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23495
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:49:10 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11611
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:49:07 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFO62416;
	Wed, 2 Jan 2002 16:46:54 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Patrick Lam'" <plam@encc.com>
Cc: <megaco@ietf.org>, <mgcp@vovida.org>
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:45:34 -0500
Message-ID: <039101c193d6$cf294f80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Pat,
You can also refer to the Megaco call flow draft which has a scenario
explaining the MGC communication with H.323 endpoint.
http://www.ietf.org/internet-drafts/draft-madhu-megaco-callflows-00.txt
Hope this helps.

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom-PT Taylor
Sent: Wednesday, January 02, 2002 4:31 PM
To: 'Patrick Lam'
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?


I should have waited to read your second message before reply.

To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
between itself and a remote H.323 entity (which might be another MGC).  It
maps between that and Megaco's Local and Remote descriptors.

I have some sample call flows showing this sort of operation.  If I get a
moment, I'll purge them of proprietary content and post them to the Megaco
supplementary web site.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 4:21 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco
to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an
AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Wed Jan  2 17:03:39 2002
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 RAA11902
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 17:03:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA24395
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 17:03:42 -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 QAA23524;
	Wed, 2 Jan 2002 16:49:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23495
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:49:10 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11611
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:49:07 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFO62416;
	Wed, 2 Jan 2002 16:46:54 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Patrick Lam'" <plam@encc.com>
Cc: <megaco@ietf.org>, <mgcp@vovida.org>
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?
Date: Wed, 2 Jan 2002 16:45:34 -0500
Message-ID: <039101c193d6$cf294f80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <4D79C746863DD51197690002A52CDA000102ADB2@zcard0kc.ca.nortel.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Pat,
You can also refer to the Megaco call flow draft which has a scenario
explaining the MGC communication with H.323 endpoint.
http://www.ietf.org/internet-drafts/draft-madhu-megaco-callflows-00.txt
Hope this helps.

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom-PT Taylor
Sent: Wednesday, January 02, 2002 4:31 PM
To: 'Patrick Lam'
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: RE: [Megaco] How does H.323 work with MGCP or Megaco?


I should have waited to read your second message before reply.

To be absolutely clear: the MGC can use H.225.0 call signalling and H.245
between itself and a remote H.323 entity (which might be another MGC).  It
maps between that and Megaco's Local and Remote descriptors.

I have some sample call flows showing this sort of operation.  If I get a
moment, I'll purge them of proprietary content and post them to the Megaco
supplementary web site.

-----Original Message-----
From: Patrick Lam [mailto:plam@encc.com]
Sent: Wednesday, January 02, 2002 4:21 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org; mgcp@vovida.org
Subject: Re: [Megaco] How does H.323 work with MGCP or Megaco?


Thanks a lot.

Can the MGC not use H.245 though?

What I am thinking is to setup the call using H.225, and use MGCP or Megaco
to
setup the RTP channel with the MG?  Does this make sense at all?  Is this
possible?

Thanks very much again,

Patrick.

Tom-PT Taylor wrote:

> Assuming the MG supports either MGCP or Megaco with text encoding, you end
> up having to do a translation between H.245 and SDP.  In the capability
> exchange phase, the MGC may use capabilities gleaned via an
AuditCapability
> request.  OpenLogicalChannel has to be mapped into the appropriate Local
> and/or Remote descriptor content.
>
> -----Original Message-----
> From: Patrick Lam [mailto:plam@encc.com]
> Sent: Wednesday, January 02, 2002 3:03 PM
> To: megaco@ietf.org; mgcp@vovida.org
> Subject: [Megaco] How does H.323 work with MGCP or Megaco?
>
> Hi:
>
> This might be a stupid question for most of you here, but I couldn't
> figured that out yet .....
>
> When I have an H.323 terminal calling to another, say Netmeeting, the
> H.245 procedures (OLC) set up the RTP channels between the 2 terminals.
>
> However, when H.323 is used in a MGC, the MGC employs MGCP or Megaco to
> setup the RTP channels in the MGs.  Is H.245 used in this case?  If so,
> how can I make the MGC know whether it needs to setup the RTP channel
> for the MG or the terminal?
>
> What is the difference, in terms of H.225 and H.245 procedures, when
> MGCP (or Megaco) is used and when it's not used?
>
> Thanks very much in advance,
>
> Patrick.
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  2 17:08:57 2002
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 RAA11997
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 17:08:57 -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 QAA23728;
	Wed, 2 Jan 2002 16:59:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23697
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:59:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11788
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:59:21 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Lwri10347
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:58:53 -0500 (EST)
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 g02LwpK05262
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:58:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRJC5>; Wed, 2 Jan 2002 16:57:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADB4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Shashi Kumar'" <shashi.kumar@wipro.com>, megaco@ietf.org
Subject: RE: [Megaco] draft-ietf-megaco-3015corr-00.txt  Vs  Latest ITU H.
	248
Date: Wed, 2 Jan 2002 16:57:18 -0500 
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

That second description is for H.248v2 -- it includes a new feature which
allows the MGC to specify which particular properties it wants to audit.
RFC3015corr pertains to H.248v1 with all the accumulated corrections.



-----Original Message-----
From: Shashi Kumar [mailto:shashi.kumar@wipro.com]
Sent: Monday, December 31, 2001 12:13 AM
To: megaco@ietf.org
Subject: [Megaco] draft-ietf-megaco-3015corr-00.txt Vs Latest ITU H.248


Hi,

  latest ID (draft-ietf-megaco-3015corr-00.txt) defines Auditdescriptor
as 

AuditDescriptor ::= SEQUENCE 
{ 
      auditToken  BIT STRING 
      { 
        muxToken(0), modemToken(1), mediaToken(2), 
        eventsToken(3), signalsToken(4), 
        digitMapToken(5), statsToken(6), 
        observedEventsToken(7), 
        packagesToken(8), eventBufferToken(9) 
      } OPTIONAL, 
      ... 
}


but latest ITU specification of H.248(Dublin, 29 October-2 November
2001) and also ITU H.248v2 defines AuditDescriptor with addition of
"auditPropertyToken" token....

AuditDescriptor ::= SEQUENCE
{	
   auditToken	BIT STRING
   { 
      muxToken(0), modemToken(1), mediaToken(2),
      eventsToken(3), signalsToken(4),
      digitMapToken(5), statsToken(6),
      observedEventsToken(7),
      packagesToken(8), eventBufferToken(9)
   } OPTIONAL,
   ...,
   >>>>auditPropertyToken SEQUENCE OF IndAuditParameter OPTIONAL, >>>>>
}



please clarify which is the correct representaion of AuditDescriptor....


thanks,
shashi

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


From daemon@ns.ietf.org  Wed Jan  2 17:08:58 2002
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 RAA12005
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 17:08:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA24511
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 17:09:01 -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 QAA23728;
	Wed, 2 Jan 2002 16:59:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23697
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 16:59:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11788
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:59:21 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g02Lwri10347
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:58:53 -0500 (EST)
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 g02LwpK05262
	for <megaco@ietf.org>; Wed, 2 Jan 2002 16:58:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRJC5>; Wed, 2 Jan 2002 16:57:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADB4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Shashi Kumar'" <shashi.kumar@wipro.com>, megaco@ietf.org
Subject: RE: [Megaco] draft-ietf-megaco-3015corr-00.txt  Vs  Latest ITU H.
	248
Date: Wed, 2 Jan 2002 16:57:18 -0500 
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

That second description is for H.248v2 -- it includes a new feature which
allows the MGC to specify which particular properties it wants to audit.
RFC3015corr pertains to H.248v1 with all the accumulated corrections.



-----Original Message-----
From: Shashi Kumar [mailto:shashi.kumar@wipro.com]
Sent: Monday, December 31, 2001 12:13 AM
To: megaco@ietf.org
Subject: [Megaco] draft-ietf-megaco-3015corr-00.txt Vs Latest ITU H.248


Hi,

  latest ID (draft-ietf-megaco-3015corr-00.txt) defines Auditdescriptor
as 

AuditDescriptor ::= SEQUENCE 
{ 
      auditToken  BIT STRING 
      { 
        muxToken(0), modemToken(1), mediaToken(2), 
        eventsToken(3), signalsToken(4), 
        digitMapToken(5), statsToken(6), 
        observedEventsToken(7), 
        packagesToken(8), eventBufferToken(9) 
      } OPTIONAL, 
      ... 
}


but latest ITU specification of H.248(Dublin, 29 October-2 November
2001) and also ITU H.248v2 defines AuditDescriptor with addition of
"auditPropertyToken" token....

AuditDescriptor ::= SEQUENCE
{	
   auditToken	BIT STRING
   { 
      muxToken(0), modemToken(1), mediaToken(2),
      eventsToken(3), signalsToken(4),
      digitMapToken(5), statsToken(6),
      observedEventsToken(7),
      packagesToken(8), eventBufferToken(9)
   } OPTIONAL,
   ...,
   >>>>auditPropertyToken SEQUENCE OF IndAuditParameter OPTIONAL, >>>>>
}



please clarify which is the correct representaion of AuditDescriptor....


thanks,
shashi

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



From megaco-admin@ietf.org  Wed Jan  2 21:31:10 2002
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 VAA14245
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 21:31:05 -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 UAA00071;
	Wed, 2 Jan 2002 20:54:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00037
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 20:54:49 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13974
	for <megaco@ietf.org>; Wed, 2 Jan 2002 20:54:46 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id TAA22330
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:19 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g031sIm29498
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -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 g031sIG16859
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -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 g031sIT06699
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -0600 (CST)
Message-ID: <3C33B9C9.A80FD550@alcatel.com>
Date: Wed, 02 Jan 2002 19:54:17 -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" <megaco@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------913B54DBDDAA6728F697E68B"
Subject: [Megaco] onhook/offhook strict and init
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


--------------913B54DBDDAA6728F697E68B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Tom

From Analog Line Supervision Package:

        "exact" means that only an actual hook state transition to on-
        hook is to be recognized;

        "state" means that the event is to be recognized either if the
        hook state transition is detected or if the hook state is
        already on-hook;

        "failWrong" means that if the hook state is already on-hook,
        the command fails and an error is reported.

   ObservedEventsDescriptor parameters

        Initial State
        -------------
        ParameterID: init (0x0002)

        Type: Boolean

        Possible values:

        True means that the event was reported because the line was
        already on-hook when the events descriptor containing this
        event was activated;

        False means that the event represents an actual state
        transition to on-hook.


Was  "Initial State" only intended to be used if "state" was used in the
Event Descriptor Request?
If yes, can we add some clarification to IG?

It is clear that "failWrong" would not cause Gwy to return "Initial
State" since an Error Descriptor is
returned w/error code 540.

Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy.



Thanks
Chuong




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



--------------913B54DBDDAA6728F697E68B
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Tom
<p>From Analog Line Supervision Package:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "exact" means that only an
actual hook state transition to on-
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hook is to be recognized;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "state" means that the event
is to be recognized either if the
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hook state transition is
detected or if the hook state is
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; already on-hook;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "failWrong" means that if
the hook state is already on-hook,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the command fails and an
error is reported.
<p>&nbsp;&nbsp; ObservedEventsDescriptor parameters
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Initial State
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------------
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: init (0x0002)
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: Boolean
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible values:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; True means that the event
was reported because the line was
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; already on-hook when the
events descriptor containing this
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; event was activated;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; False means that the event
represents an actual state
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; transition to on-hook.
<br>&nbsp;
<p>Was&nbsp; "Initial State" only intended to be used if "state" was used
in the Event Descriptor Request?
<br>If yes, can we add some clarification to IG?
<p>It is clear that "failWrong" would not cause Gwy to return "Initial
State" since an Error Descriptor is
<br>returned w/error code 540.
<p>Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy.
<br>&nbsp;
<br>&nbsp;
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------913B54DBDDAA6728F697E68B--


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


From daemon@ns.ietf.org  Wed Jan  2 21:31:10 2002
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 VAA14256
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 21:31:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA01425
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 21:31:12 -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 UAA00071;
	Wed, 2 Jan 2002 20:54:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00037
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 20:54:49 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13974
	for <megaco@ietf.org>; Wed, 2 Jan 2002 20:54:46 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id TAA22330
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:19 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g031sIm29498
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -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 g031sIG16859
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -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 g031sIT06699
	for <megaco@ietf.org>; Wed, 2 Jan 2002 19:54:18 -0600 (CST)
Message-ID: <3C33B9C9.A80FD550@alcatel.com>
Date: Wed, 02 Jan 2002 19:54:17 -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" <megaco@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------913B54DBDDAA6728F697E68B"
Subject: [Megaco] onhook/offhook strict and init
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


--------------913B54DBDDAA6728F697E68B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Tom

From Analog Line Supervision Package:

        "exact" means that only an actual hook state transition to on-
        hook is to be recognized;

        "state" means that the event is to be recognized either if the
        hook state transition is detected or if the hook state is
        already on-hook;

        "failWrong" means that if the hook state is already on-hook,
        the command fails and an error is reported.

   ObservedEventsDescriptor parameters

        Initial State
        -------------
        ParameterID: init (0x0002)

        Type: Boolean

        Possible values:

        True means that the event was reported because the line was
        already on-hook when the events descriptor containing this
        event was activated;

        False means that the event represents an actual state
        transition to on-hook.


Was  "Initial State" only intended to be used if "state" was used in the
Event Descriptor Request?
If yes, can we add some clarification to IG?

It is clear that "failWrong" would not cause Gwy to return "Initial
State" since an Error Descriptor is
returned w/error code 540.

Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy.



Thanks
Chuong




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



--------------913B54DBDDAA6728F697E68B
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Tom
<p>From Analog Line Supervision Package:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "exact" means that only an
actual hook state transition to on-
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hook is to be recognized;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "state" means that the event
is to be recognized either if the
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hook state transition is
detected or if the hook state is
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; already on-hook;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "failWrong" means that if
the hook state is already on-hook,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the command fails and an
error is reported.
<p>&nbsp;&nbsp; ObservedEventsDescriptor parameters
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Initial State
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------------
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: init (0x0002)
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: Boolean
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible values:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; True means that the event
was reported because the line was
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; already on-hook when the
events descriptor containing this
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; event was activated;
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; False means that the event
represents an actual state
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; transition to on-hook.
<br>&nbsp;
<p>Was&nbsp; "Initial State" only intended to be used if "state" was used
in the Event Descriptor Request?
<br>If yes, can we add some clarification to IG?
<p>It is clear that "failWrong" would not cause Gwy to return "Initial
State" since an Error Descriptor is
<br>returned w/error code 540.
<p>Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy.
<br>&nbsp;
<br>&nbsp;
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------913B54DBDDAA6728F697E68B--


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



From megaco-admin@ietf.org  Wed Jan  2 23:41:36 2002
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 XAA17437
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 23:41:36 -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 XAA04177;
	Wed, 2 Jan 2002 23:28:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04148
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 23:28:36 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16958
	for <megaco@ietf.org>; Wed, 2 Jan 2002 23:28:28 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g034RU123213
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:57:30 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GPCHQ901.I2W; Thu, 3 Jan 2002 09:57:45 +0530 
Message-ID: <030601c1940f$7ac67010$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>, <sudhirk@future.futsoft.com>,
        <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA00274C8E@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Reserve Value and Reserve Group
Date: Thu, 3 Jan 2002 10:01:14 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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


------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8--

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


From daemon@ns.ietf.org  Wed Jan  2 23:41:38 2002
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 XAA17450
	for <megaco-archive@odin.ietf.org>; Wed, 2 Jan 2002 23:41:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA04661
	for megaco-archive@odin.ietf.org; Wed, 2 Jan 2002 23:41:41 -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 XAA04177;
	Wed, 2 Jan 2002 23:28:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04148
	for <megaco@ns.ietf.org>; Wed, 2 Jan 2002 23:28:36 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16958
	for <megaco@ietf.org>; Wed, 2 Jan 2002 23:28:28 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g034RU123213
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:57:30 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GPCHQ901.I2W; Thu, 3 Jan 2002 09:57:45 +0530 
Message-ID: <030601c1940f$7ac67010$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>, <sudhirk@future.futsoft.com>,
        <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA00274C8E@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Reserve Value and Reserve Group
Date: Thu, 3 Jan 2002 10:01:14 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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


------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-f8b2a0e4-fffb-11d5-a940-00b0d0d06be8--

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



From megaco-admin@ietf.org  Thu Jan  3 02:21:17 2002
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 CAA26861
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 02:21: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 CAA17278;
	Thu, 3 Jan 2002 02:11:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA17249
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 02:11:19 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26797
	for <megaco@ietf.org>; Thu, 3 Jan 2002 02:11:16 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW37K8>; Thu, 3 Jan 2002 12:18:28 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822D5000@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Date: Thu, 3 Jan 2002 12:18:25 +0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Inter-MGC Communication
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

Can Any one confirm that 
Only SIP or SIP-T is used for Inter-MGC Communication.
 What about other options.
Can any one guide If There are any callFlows available for Inte-MGC
communication ...

  regards
 Asrar Ashraf
 AvazNetworks
 Islamabad, Pakistan

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


From daemon@optimus.ietf.org  Thu Jan  3 02:21:18 2002
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 CAA26873
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 02:21:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA17432
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 02:21:19 -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 CAA17278;
	Thu, 3 Jan 2002 02:11:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA17249
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 02:11:19 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26797
	for <megaco@ietf.org>; Thu, 3 Jan 2002 02:11:16 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW37K8>; Thu, 3 Jan 2002 12:18:28 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822D5000@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Date: Thu, 3 Jan 2002 12:18:25 +0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Inter-MGC Communication
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

Can Any one confirm that 
Only SIP or SIP-T is used for Inter-MGC Communication.
 What about other options.
Can any one guide If There are any callFlows available for Inte-MGC
communication ...

  regards
 Asrar Ashraf
 AvazNetworks
 Islamabad, Pakistan

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



From daemon@optimus.ietf.org  Thu Jan  3 04:51:53 2002
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 EAA28496
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 04:51:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22395
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 04:51:55 -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 EAA22310;
	Thu, 3 Jan 2002 04:44:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA22281
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 04:44:29 -0500 (EST)
Received: from localhost ([211.212.15.206])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28369
	for <megaco@ietf.org>; Thu, 3 Jan 2002 04:44:24 -0500 (EST)
Message-Id: <200201030944.EAA28369@ietf.org>
Reply-To: test@test.com
From: test<test@test.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Thu, 3 Jan 2002 18:45:28 +0900
Subject: [Megaco] (no subject)
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

<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
<DIV></DIV>
</BODY>
</HTML>

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



From megaco-admin@ietf.org  Thu Jan  3 05:38:27 2002
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 EAA28488
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 04:51:52 -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 EAA22310;
	Thu, 3 Jan 2002 04:44:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA22281
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 04:44:29 -0500 (EST)
Received: from localhost ([211.212.15.206])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28369
	for <megaco@ietf.org>; Thu, 3 Jan 2002 04:44:24 -0500 (EST)
Message-Id: <200201030944.EAA28369@ietf.org>
Reply-To: test@test.com
From: test<test@test.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Thu, 3 Jan 2002 18:45:28 +0900
Subject: [Megaco] (no subject)
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

<HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
<DIV></DIV>
</BODY>
</HTML>

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


From megaco-admin@ietf.org  Thu Jan  3 07:15:42 2002
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 HAA29656
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 07:15:42 -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 GAA25822;
	Thu, 3 Jan 2002 06:50:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA25793
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 06:50:54 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29410
	for <megaco@ietf.org>; Thu, 3 Jan 2002 06:50:50 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001624593@fsnt.future.futsoft.com>;
 Thu, 03 Jan 2002 17:35:05 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g03BnHo26623;
	Thu, 3 Jan 2002 17:19:18 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Topology Descriptor
Date: Thu, 3 Jan 2002 17:27:24 +0530
Message-Id: <001501c1944d$cfce9720$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA00274C90@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

will the same results be observed even if the topology descriptor is fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 07:15:43 2002
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 HAA29666
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 07:15:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA26667
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 07:15:45 -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 GAA25822;
	Thu, 3 Jan 2002 06:50:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA25793
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 06:50:54 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29410
	for <megaco@ietf.org>; Thu, 3 Jan 2002 06:50:50 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001624593@fsnt.future.futsoft.com>;
 Thu, 03 Jan 2002 17:35:05 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g03BnHo26623;
	Thu, 3 Jan 2002 17:19:18 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Topology Descriptor
Date: Thu, 3 Jan 2002 17:27:24 +0530
Message-Id: <001501c1944d$cfce9720$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA00274C90@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

will the same results be observed even if the topology descriptor is fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 07:37:36 2002
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 HAA00069
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 07:37:36 -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 HAA26945;
	Thu, 3 Jan 2002 07:23:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA26852
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 07:22:55 -0500 (EST)
Received: from huaweidns.in.huawei.com ([203.197.168.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29830
	for <megaco@ietf.org>; Thu, 3 Jan 2002 07:22:51 -0500 (EST)
Received: from HUAWEIMAIL [203.197.168.162] by huaweidns.in.huawei.com - SuperScout Email Filter ; Thursday, 03 January 2002, 10:37:02
Message-ID: <751B6DD7A243D511AB9F0002557C5687022B7D99@huaweimail>
From: "Rajeev K. R." <Rajeev@in.huawei.com>
To: "Megaco (E-mail)" <megaco@ietf.org>
Date: Thu, 3 Jan 2002 10:34:44 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038"
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Reply ordering
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Does Megaco guarantee that the actions in a transaction reply are in the
same
order as that in the transaction request ?

I could not find any explicit statement that actions in the reply has the
same order as in the request. 

Regards,
Rajeev
--------------------------------------------------------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please notify the
originator of the message. 

Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Huawei Technologies India Pvt. Ltd.
----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Reply ordering</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>Does Megaco guarantee that the actions in a transaction reply are in the same</FONT>
<BR><FONT SIZE=2>order as that in the transaction request ?</FONT>
</P>

<P><FONT SIZE=2>I could not find any explicit statement that actions in the reply has the</FONT>
<BR><FONT SIZE=2>same order as in the request. </FONT>
</P>

<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Rajeev</FONT>
</P>

--------------------------------------------------------------------------------------------------------------------<br>This email and any files transmitted with it are confidential and<br>intended solely for the use of the individual or entity to whom<br>they are addressed. If you have received this email in error please notify the<br>originator of the message. <br><br>Any views expressed in this message are those of the individual<br>sender, except where the sender specifies and with authority,<br>states them to be the views of Huawei Technologies India Pvt. Ltd.</BODY>
</HTML>
----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038--


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


From daemon@optimus.ietf.org  Thu Jan  3 07:37:37 2002
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 HAA00081
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 07:37:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA27484
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 07:37:39 -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 HAA26945;
	Thu, 3 Jan 2002 07:23:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA26852
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 07:22:55 -0500 (EST)
Received: from huaweidns.in.huawei.com ([203.197.168.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29830
	for <megaco@ietf.org>; Thu, 3 Jan 2002 07:22:51 -0500 (EST)
Received: from HUAWEIMAIL [203.197.168.162] by huaweidns.in.huawei.com - SuperScout Email Filter ; Thursday, 03 January 2002, 10:37:02
Message-ID: <751B6DD7A243D511AB9F0002557C5687022B7D99@huaweimail>
From: "Rajeev K. R." <Rajeev@in.huawei.com>
To: "Megaco (E-mail)" <megaco@ietf.org>
Date: Thu, 3 Jan 2002 10:34:44 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="--=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038"
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Reply ordering
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Does Megaco guarantee that the actions in a transaction reply are in the
same
order as that in the transaction request ?

I could not find any explicit statement that actions in the reply has the
same order as in the request. 

Regards,
Rajeev
--------------------------------------------------------------------------------------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please notify the
originator of the message. 

Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Huawei Technologies India Pvt. Ltd.
----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Reply ordering</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>Does Megaco guarantee that the actions in a transaction reply are in the same</FONT>
<BR><FONT SIZE=2>order as that in the transaction request ?</FONT>
</P>

<P><FONT SIZE=2>I could not find any explicit statement that actions in the reply has the</FONT>
<BR><FONT SIZE=2>same order as in the request. </FONT>
</P>

<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Rajeev</FONT>
</P>

--------------------------------------------------------------------------------------------------------------------<br>This email and any files transmitted with it are confidential and<br>intended solely for the use of the individual or entity to whom<br>they are addressed. If you have received this email in error please notify the<br>originator of the message. <br><br>Any views expressed in this message are those of the individual<br>sender, except where the sender specifies and with authority,<br>states them to be the views of Huawei Technologies India Pvt. Ltd.</BODY>
</HTML>
----=_NextPart_ST_17_55_15_Thursday_January_03_2002_16038--


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



From megaco-admin@ietf.org  Thu Jan  3 09:35:00 2002
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 JAA02179
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:35:00 -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 JAA00012;
	Thu, 3 Jan 2002 09:19:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29982
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:19:20 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01799
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:19:15 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03EIka01278;
	Thu, 3 Jan 2002 09:18:47 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03EIij26331;
	Thu, 3 Jan 2002 09:18:44 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRS38>; Thu, 3 Jan 2002 09:17:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor
Date: Thu, 3 Jan 2002 09:17:14 -0500 
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

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There is
no half-way measure possible within the syntax such as just returning the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive actions
affecting the same context, another question that comes to mind is whether
the MG returns the topology descriptor supplied by the MGC with wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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


From megaco-admin@ietf.org  Thu Jan  3 09:36:08 2002
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 JAA02210
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:36:08 -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 JAA00145;
	Thu, 3 Jan 2002 09:25:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00118
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:25:09 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01889
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:25:05 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA29748;
	Thu, 3 Jan 2002 09:24:36 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25812;
	Thu, 3 Jan 2002 09:24:35 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNMCBW>; Thu, 3 Jan 2002 09:24:35 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C752@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 09:24:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan  3 09:36:08 2002
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 JAA02219
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:36:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00861
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 09:36:12 -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 JAA00145;
	Thu, 3 Jan 2002 09:25:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00118
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:25:09 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01889
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:25:05 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA29748;
	Thu, 3 Jan 2002 09:24:36 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25812;
	Thu, 3 Jan 2002 09:24:35 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNMCBW>; Thu, 3 Jan 2002 09:24:35 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C752@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 09:24:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan  3 09:49:37 2002
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 JAA02574
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:49:37 -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 JAA00726;
	Thu, 3 Jan 2002 09:32:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00698
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:32:35 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02073
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:32:29 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g03EWpE14651;
	Thu, 3 Jan 2002 20:02:51 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B36.004FC8AD ; Thu, 3 Jan 2002 20:01:27 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: megaco@ietf.org
Message-ID: <65256B36.004FC73E.00@sandesh.hss.hns.com>
Date: Thu, 3 Jan 2002 20:04:49 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




If this is the case, then we need update the same in the v2 draft.

Regards
Vivek






"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM

To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
cc:

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




The immAckRequired flag was introduced because without it a protocol glitch
was possible, so what you postulate is not a nice situation.  Anyway, to
answer your question, I would say that retransmission of the final response
(with exponential backoff) is necessary until an acknowledgement is
received.

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Sunday, December 30, 2001 8:23 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding immAckRequired field.





Hi

I have a doubt regarding immAckRequired field.

Section D.1.4 says

"An entity that sends a provisional response, SHALL include the
immAckRequired
field in the ensuing final response, indicating that an immediate
confirmation
is expected."


Now what would happen, if the entity receiving the final response with
immAckRequired field, does not send the immediate confirmation? In this case
do
we need to retransmit the response till we get the confirmation?

Please clarify.

Regards
Vivek



_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 09:49:38 2002
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 JAA02583
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:49:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA01128
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 09:49:42 -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 JAA00726;
	Thu, 3 Jan 2002 09:32:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00698
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:32:35 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02073
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:32:29 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g03EWpE14651;
	Thu, 3 Jan 2002 20:02:51 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B36.004FC8AD ; Thu, 3 Jan 2002 20:01:27 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: megaco@ietf.org
Message-ID: <65256B36.004FC73E.00@sandesh.hss.hns.com>
Date: Thu, 3 Jan 2002 20:04:49 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




If this is the case, then we need update the same in the v2 draft.

Regards
Vivek






"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM

To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
cc:

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




The immAckRequired flag was introduced because without it a protocol glitch
was possible, so what you postulate is not a nice situation.  Anyway, to
answer your question, I would say that retransmission of the final response
(with exponential backoff) is necessary until an acknowledgement is
received.

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Sunday, December 30, 2001 8:23 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding immAckRequired field.





Hi

I have a doubt regarding immAckRequired field.

Section D.1.4 says

"An entity that sends a provisional response, SHALL include the
immAckRequired
field in the ensuing final response, indicating that an immediate
confirmation
is expected."


Now what would happen, if the entity receiving the final response with
immAckRequired field, does not send the immediate confirmation? In this case
do
we need to retransmit the response till we get the confirmation?

Please clarify.

Regards
Vivek



_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 10:09:41 2002
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 KAA03361
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:09:41 -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 KAA01583;
	Thu, 3 Jan 2002 10:00:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01504
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:00:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03165
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:00:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03Exba18495;
	Thu, 3 Jan 2002 09:59:37 -0500 (EST)
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 g03ExSv01183;
	Thu, 3 Jan 2002 09:59:36 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTS3>; Thu, 3 Jan 2002 09:57:51 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Rajeev K. R.'" <Rajeev@in.huawei.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Reply ordering
Date: Thu, 3 Jan 2002 09:57:57 -0500 
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

I think I could build the case that this order is implied by the fact that
the actions must be processed in the order they occur in the request.


-----Original Message-----
From: Rajeev K. R. [mailto:Rajeev@in.huawei.com]
Sent: Thursday, January 03, 2002 12:05 AM
To: Megaco (E-mail)
Subject: [Megaco] Reply ordering


Hi, 
Does Megaco guarantee that the actions in a transaction reply are in the
same 
order as that in the transaction request ? 
I could not find any explicit statement that actions in the reply has the 
same order as in the request. 
Regards, 
Rajeev 
----------------------------------------------------------------------------
----------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please notify
the
originator of the message. 

Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Huawei Technologies India Pvt. Ltd. 

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


From daemon@optimus.ietf.org  Thu Jan  3 10:09:42 2002
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 KAA03380
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:09:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02231
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:09:44 -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 JAA01355;
	Thu, 3 Jan 2002 09:56: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 JAA01325
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:56:56 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03123
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:56:51 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03Etqa17165;
	Thu, 3 Jan 2002 09:55:53 -0500 (EST)
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 g03Etpv00955;
	Thu, 3 Jan 2002 09:55:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTPJ>; Thu, 3 Jan 2002 09:54:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Cc: "'Terry L Anderson'" <tla@lucent.com>
Subject: RE: [Megaco] onhook/offhook strict and init
Date: Thu, 3 Jan 2002 09:54:21 -0500 
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

You are right.  The init parameter is required if strict has been set to
"state", but otherwise must not be reported.  


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Wednesday, January 02, 2002 8:54 PM
To: megaco@ietf.org
Subject: [Megaco] onhook/offhook strict and init


Hi Tom 
From Analog Line Supervision Package: 
        "exact" means that only an actual hook state transition to on- 
        hook is to be recognized; 
        "state" means that the event is to be recognized either if the 
        hook state transition is detected or if the hook state is 
        already on-hook; 
        "failWrong" means that if the hook state is already on-hook, 
        the command fails and an error is reported. 
   ObservedEventsDescriptor parameters 
        Initial State 
        ------------- 
        ParameterID: init (0x0002) 
        Type: Boolean 
        Possible values: 
        True means that the event was reported because the line was 
        already on-hook when the events descriptor containing this 
        event was activated; 
        False means that the event represents an actual state 
        transition to on-hook. 
  
Was  "Initial State" only intended to be used if "state" was used in the
Event Descriptor Request? 
If yes, can we add some clarification to IG? 
It is clear that "failWrong" would not cause Gwy to return "Initial State"
since an Error Descriptor is 
returned w/error code 540. 
Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy. 
  
  
Thanks 
Chuong 
  
  
  
-- 
  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



From daemon@optimus.ietf.org  Thu Jan  3 10:09:42 2002
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 KAA03384
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:09:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02226
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:09:44 -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 KAA01583;
	Thu, 3 Jan 2002 10:00:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01504
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:00:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03165
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:00:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03Exba18495;
	Thu, 3 Jan 2002 09:59:37 -0500 (EST)
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 g03ExSv01183;
	Thu, 3 Jan 2002 09:59:36 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTS3>; Thu, 3 Jan 2002 09:57:51 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Rajeev K. R.'" <Rajeev@in.huawei.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Reply ordering
Date: Thu, 3 Jan 2002 09:57:57 -0500 
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

I think I could build the case that this order is implied by the fact that
the actions must be processed in the order they occur in the request.


-----Original Message-----
From: Rajeev K. R. [mailto:Rajeev@in.huawei.com]
Sent: Thursday, January 03, 2002 12:05 AM
To: Megaco (E-mail)
Subject: [Megaco] Reply ordering


Hi, 
Does Megaco guarantee that the actions in a transaction reply are in the
same 
order as that in the transaction request ? 
I could not find any explicit statement that actions in the reply has the 
same order as in the request. 
Regards, 
Rajeev 
----------------------------------------------------------------------------
----------------------------------------
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please notify
the
originator of the message. 

Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Huawei Technologies India Pvt. Ltd. 

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



From megaco-admin@ietf.org  Thu Jan  3 10:11:39 2002
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 KAA03437
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:11:39 -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 KAA02022;
	Thu, 3 Jan 2002 10:05:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01995
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:05:00 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03304
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:04:53 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839b93b0bc0722b33420@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 3 Jan 2002 17:06:02 +0200
content-class: urn:content-classes:message
Subject: RE: [Megaco] Topology Descriptor
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 3 Jan 2002 17:04:16 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C03D@lodmsg01.corp.audiocodes.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [Megaco] Topology Descriptor
Thread-Index: AcGUZYItrzyWfp0uRUOzsuKxPVK4KQAAcxpw
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: "'Megaco_IETF (E-mail)" <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA01996
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

Hi

If we want to know what the topology is, we can audit it. Example:

MEGACO/1 [10.2.1.228]:2944
Transaction = 1237 {
       Context = 1 {
          Topology{*, gws0c2, oneway},ca{tp}
}}

Even so, I don't think that the ALL wildcard should be resolved, as it
may cause a huge reply. Only the CHOOSE wildcard should be resolved in
the answer.

Nurit

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, January 03, 2002 4:17 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There
is
no half-way measure possible within the syntax such as just returning
the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive
actions
affecting the same context, another question that comes to mind is
whether
the MG returns the topology descriptor supplied by the MGC with
wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that
in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is
fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and
the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology
descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 10:11:40 2002
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 KAA03446
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:11:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02325
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:11:42 -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 KAA02022;
	Thu, 3 Jan 2002 10:05:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01995
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:05:00 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03304
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:04:53 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839b93b0bc0722b33420@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 3 Jan 2002 17:06:02 +0200
content-class: urn:content-classes:message
Subject: RE: [Megaco] Topology Descriptor
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 3 Jan 2002 17:04:16 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C03D@lodmsg01.corp.audiocodes.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [Megaco] Topology Descriptor
Thread-Index: AcGUZYItrzyWfp0uRUOzsuKxPVK4KQAAcxpw
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: "'Megaco_IETF (E-mail)" <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA01996
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

Hi

If we want to know what the topology is, we can audit it. Example:

MEGACO/1 [10.2.1.228]:2944
Transaction = 1237 {
       Context = 1 {
          Topology{*, gws0c2, oneway},ca{tp}
}}

Even so, I don't think that the ALL wildcard should be resolved, as it
may cause a huge reply. Only the CHOOSE wildcard should be resolved in
the answer.

Nurit

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, January 03, 2002 4:17 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There
is
no half-way measure possible within the syntax such as just returning
the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive
actions
affecting the same context, another question that comes to mind is
whether
the MG returns the topology descriptor supplied by the MGC with
wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that
in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is
fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and
the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology
descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 10:12:36 2002
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 KAA03479
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:12:36 -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 KAA02100;
	Thu, 3 Jan 2002 10:05:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02071
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:05:52 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03310
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:44 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F5Fx20177
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:15 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F5Dj01802
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:13 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTWS>; Thu, 3 Jan 2002 10:03:36 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC1@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Thu, 3 Jan 2002 10:03:43 -0500 
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

Darn.  That Korean spam that has been hitting the other WG lists has found
a way to get onto ours.  I'll have to see if I can tinker with my spam
filters ...


-----Original Message-----
From: test [mailto:test@test.com]
Sent: Thursday, January 03, 2002 4:45 AM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


_______________________________________________ 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


From daemon@optimus.ietf.org  Thu Jan  3 10:12:37 2002
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 KAA03490
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:12:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02381
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:12:39 -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 KAA02100;
	Thu, 3 Jan 2002 10:05:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02071
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:05:52 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03310
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:44 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F5Fx20177
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:15 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F5Dj01802
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:05:13 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTWS>; Thu, 3 Jan 2002 10:03:36 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC1@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Thu, 3 Jan 2002 10:03:43 -0500 
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

Darn.  That Korean spam that has been hitting the other WG lists has found
a way to get onto ours.  I'll have to see if I can tinker with my spam
filters ...


-----Original Message-----
From: test [mailto:test@test.com]
Sent: Thursday, January 03, 2002 4:45 AM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


_______________________________________________ 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



From megaco-admin@ietf.org  Thu Jan  3 10:20:16 2002
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 KAA03768
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:20:16 -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 KAA01906;
	Thu, 3 Jan 2002 10:02:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01876
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:02:40 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03220
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:02:34 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F25x19325;
	Thu, 3 Jan 2002 10:02:06 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F23j01678;
	Thu, 3 Jan 2002 10:02:03 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRT4L>; Thu, 3 Jan 2002 10:00:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC0@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:00:34 -0500 
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

You can use any call signalling protocol you want for inter-MGC
communication.  Standardized protocols include BICC CS2 and H.323 as well as
SIP/SIP-T.

-----Original Message-----
From: asrar ashraf [mailto:asrar@enabtech.com]
Sent: Thursday, January 03, 2002 2:18 AM
To: megaco@ietf.org
Subject: [Megaco] Inter-MGC Communication


Can Any one confirm that 
Only SIP or SIP-T is used for Inter-MGC Communication.
 What about other options.
Can any one guide If There are any callFlows available for Inte-MGC
communication ...

  regards
 Asrar Ashraf
 AvazNetworks
 Islamabad, Pakistan

_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 10:20:17 2002
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 KAA03778
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:20:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02723
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:20:19 -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 KAA01906;
	Thu, 3 Jan 2002 10:02:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01876
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:02:40 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03220
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:02:34 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F25x19325;
	Thu, 3 Jan 2002 10:02:06 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03F23j01678;
	Thu, 3 Jan 2002 10:02:03 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRT4L>; Thu, 3 Jan 2002 10:00:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC0@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:00:34 -0500 
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

You can use any call signalling protocol you want for inter-MGC
communication.  Standardized protocols include BICC CS2 and H.323 as well as
SIP/SIP-T.

-----Original Message-----
From: asrar ashraf [mailto:asrar@enabtech.com]
Sent: Thursday, January 03, 2002 2:18 AM
To: megaco@ietf.org
Subject: [Megaco] Inter-MGC Communication


Can Any one confirm that 
Only SIP or SIP-T is used for Inter-MGC Communication.
 What about other options.
Can any one guide If There are any callFlows available for Inte-MGC
communication ...

  regards
 Asrar Ashraf
 AvazNetworks
 Islamabad, Pakistan

_______________________________________________
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



From daemon@optimus.ietf.org  Thu Jan  3 10:24:37 2002
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 JAA02189
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 09:35:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00823
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 09:35:04 -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 JAA00012;
	Thu, 3 Jan 2002 09:19:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29982
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:19:20 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01799
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:19:15 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03EIka01278;
	Thu, 3 Jan 2002 09:18:47 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03EIij26331;
	Thu, 3 Jan 2002 09:18:44 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRS38>; Thu, 3 Jan 2002 09:17:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor
Date: Thu, 3 Jan 2002 09:17:14 -0500 
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

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There is
no half-way measure possible within the syntax such as just returning the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive actions
affecting the same context, another question that comes to mind is whether
the MG returns the topology descriptor supplied by the MGC with wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 10:48:18 2002
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 KAA04372
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:48:18 -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 KAA03023;
	Thu, 3 Jan 2002 10:28:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02996
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:28:17 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03857
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:28:12 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839ce2956c0722b33420@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 3 Jan 2002 17:28:54 +0200
content-class: urn:content-classes:message
Subject: RE: [Megaco] Topology Descriptor
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 3 Jan 2002 17:26:09 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01BAC5@lodmsg01.corp.audiocodes.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [Megaco] Topology Descriptor
Thread-Index: AcGUZYItrzyWfp0uRUOzsuKxPVK4KQAAcxpwAADl4PA=
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA02997
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

Hi

If we want to know what the topology is, we can audit it. Example:

MEGACO/1 [10.2.1.228]:2944
Transaction = 1237 {
       Context = 1 {
          Topology{*, gws0c2, oneway},ca{tp}
}}

Even so, I don't think that the ALL wildcard should be resolved, as it
may cause a huge reply. Only the CHOOSE wildcard should be resolved in
the answer.

Nurit

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, January 03, 2002 4:17 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There
is
no half-way measure possible within the syntax such as just returning
the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive
actions
affecting the same context, another question that comes to mind is
whether
the MG returns the topology descriptor supplied by the MGC with
wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that
in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is
fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and
the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology
descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 10:48:19 2002
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 KAA04381
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:48:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA04644
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:48:21 -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 KAA03023;
	Thu, 3 Jan 2002 10:28:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02996
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:28:17 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03857
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:28:12 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839ce2956c0722b33420@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 3 Jan 2002 17:28:54 +0200
content-class: urn:content-classes:message
Subject: RE: [Megaco] Topology Descriptor
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 3 Jan 2002 17:26:09 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01BAC5@lodmsg01.corp.audiocodes.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [Megaco] Topology Descriptor
Thread-Index: AcGUZYItrzyWfp0uRUOzsuKxPVK4KQAAcxpwAADl4PA=
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA02997
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

Hi

If we want to know what the topology is, we can audit it. Example:

MEGACO/1 [10.2.1.228]:2944
Transaction = 1237 {
       Context = 1 {
          Topology{*, gws0c2, oneway},ca{tp}
}}

Even so, I don't think that the ALL wildcard should be resolved, as it
may cause a huge reply. Only the CHOOSE wildcard should be resolved in
the answer.

Nurit

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, January 03, 2002 4:17 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor

I see your point: either the topology descriptor is returned, even if no
wildcards were present, or the topology doesn't get acknowledged.  There
is
no half-way measure possible within the syntax such as just returning
the
topology token.  So the answer is that if the MGC specifies a topology
descriptor, the MG returns a topology descriptor in the response.

Remembering that topology descriptors are cumulative over successive
actions
affecting the same context, another question that comes to mind is
whether
the MG returns the topology descriptor supplied by the MGC with
wildcarded
terminationIDs resolved, or whether instead it should return a complete
description of the current topology of the context.  Bear in mind that
in
H.248v2 we will be able to specify topology per stream, unless someone
strongly objects at the last moment.

Opinions?

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 03, 2002 6:57 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


Hi,

will the same results be observed even if the topology descriptor is
fully
specified.

gokul

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 3 January 2002 12:58 AM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Topology Descriptor


It should be returned, because the original descriptor had wildcards and
the
returned value should show how they were resolved.

-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Saturday, December 29, 2001 6:43 AM
To: megaco@ietf.org
Subject: [Megaco] Topology Descriptor


Hi,

When a context is created using two add comands and a topology
descriptor,
will
the topology descriptor be returned in the reply.

regards
gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 10:50:25 2002
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 KAA04451
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:50:25 -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 KAA03100;
	Thu, 3 Jan 2002 10:28:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03045
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:28:34 -0500 (EST)
Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03860
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:28:27 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03FRbZ01280
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:27:40 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A500178D99; Thu, 3 Jan 2002 10:27:19 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:27:20 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF50F4@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUZMraiuwsJgBUEdajbgCQJ60IGQABGejA
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA03046
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

Hi, Brian:

You are right.

What could have been better if we could have a document, like Madhubabu's call flows, how the mapping is done as Tom Taylor has indicated. For example, the scenarios can be as follows:

	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
	 ^						   ^
	 |						   |
     MEGACO/MGCP  				MEGACO/MGCP
	 |						   |
	 v						   v
	MG  <---------- RTP ---------------->  MG

Now the appropriate mapping needs to be done between H.323 (H.225.0, H.245) and MEGACO (or MGCP). This part is missing and no documentation is available. If this is done, people could have interoperable implementations.

Similarly, the scenarios can be created for SIP and BICC and, mappings need to be done as follows:

SIP/SDP <-> MEGACO (or MGCP)
BICC  <-> MEGACO (or MGCP)

Best regards,

Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 9:25 AM
To: 'asrar ashraf'; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 

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


From daemon@optimus.ietf.org  Thu Jan  3 10:50:26 2002
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 KAA04463
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:50:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA04825
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:50:28 -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 KAA03100;
	Thu, 3 Jan 2002 10:28:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03045
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:28:34 -0500 (EST)
Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03860
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:28:27 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03FRbZ01280
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:27:40 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A500178D99; Thu, 3 Jan 2002 10:27:19 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:27:20 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF50F4@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUZMraiuwsJgBUEdajbgCQJ60IGQABGejA
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA03046
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

Hi, Brian:

You are right.

What could have been better if we could have a document, like Madhubabu's call flows, how the mapping is done as Tom Taylor has indicated. For example, the scenarios can be as follows:

	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
	 ^						   ^
	 |						   |
     MEGACO/MGCP  				MEGACO/MGCP
	 |						   |
	 v						   v
	MG  <---------- RTP ---------------->  MG

Now the appropriate mapping needs to be done between H.323 (H.225.0, H.245) and MEGACO (or MGCP). This part is missing and no documentation is available. If this is done, people could have interoperable implementations.

Similarly, the scenarios can be created for SIP and BICC and, mappings need to be done as follows:

SIP/SDP <-> MEGACO (or MGCP)
BICC  <-> MEGACO (or MGCP)

Best regards,

Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 9:25 AM
To: 'asrar ashraf'; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 

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



From megaco-admin@ietf.org  Thu Jan  3 10:55:16 2002
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 KAA04573
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:55:16 -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 KAA04155;
	Thu, 3 Jan 2002 10:40:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04128
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:40:56 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04056
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:40:53 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA08885;
	Thu, 3 Jan 2002 10:40:24 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA15529;
	Thu, 3 Jan 2002 10:40:24 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNMHFP>; Thu, 3 Jan 2002 10:40:23 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C757@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        asrar ashraf
	 <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:40:15 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

As the method used to map H.232 into the appropriate Megaco
commands is solely within the domain of a single MGC, it is
not appropriate to standardize it, at least in the IETF.

ITU sometimes does this sort of thing, and it's always possible
to have an informational RFC that describes ONE WAY to do it,
but I think it's a very bad idea to specify that any particular
mapping is the RIGHT way.

The only important thing is that the MGC implementation
work on a wide variety of MGs, using standard Megaco/H248,
and that it interwork with a wide variety of H.323 devices
using standard H.323.  I suspect there is not a single exact
mapping.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan  3 10:55:17 2002
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 KAA04583
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:55:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA05317
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:55:19 -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 KAA04155;
	Thu, 3 Jan 2002 10:40:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04128
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:40:56 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04056
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:40:53 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA08885;
	Thu, 3 Jan 2002 10:40:24 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA15529;
	Thu, 3 Jan 2002 10:40:24 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNMHFP>; Thu, 3 Jan 2002 10:40:23 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C757@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        asrar ashraf
	 <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 10:40:15 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

As the method used to map H.232 into the appropriate Megaco
commands is solely within the domain of a single MGC, it is
not appropriate to standardize it, at least in the IETF.

ITU sometimes does this sort of thing, and it's always possible
to have an informational RFC that describes ONE WAY to do it,
but I think it's a very bad idea to specify that any particular
mapping is the RIGHT way.

The only important thing is that the MGC implementation
work on a wide variety of MGs, using standard Megaco/H248,
and that it interwork with a wide variety of H.323 devices
using standard H.323.  I suspect there is not a single exact
mapping.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan  3 10:56:30 2002
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 KAA04657
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:56:29 -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 KAA04494;
	Thu, 3 Jan 2002 10:46:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04465
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:46:21 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04284
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:46:17 -0500 (EST)
From: Ext-Venkata.Ghadiyaram@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g03FkCC22562
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:46:12 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839de1cbdac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 3 Jan 2002 17:46:19 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <C1088QYD>; Thu, 3 Jan 2002 17:46:19 +0200
Message-ID: <9E3407CE45911B4097632389B77B2023AC7333@esebe014.NOE.Nokia.com>
To: rrroy@att.com, Brian.Rosen@marconi.com, asrar@enabtech.com,
        megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:46:10 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi,

I think we are getting further out of scope. If some document as Radhika
suggested, it would be appropriate in other forums rather than megaco.

Regards,
Kishore

-----Original Message-----
From: ext Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
Sent: 03. January 2002 17:27
To: Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Hi, Brian:

You are right.

What could have been better if we could have a document, like Madhubabu's
call flows, how the mapping is done as Tom Taylor has indicated. For
example, the scenarios can be as follows:

	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
	 ^						   ^
	 |						   |
     MEGACO/MGCP  				MEGACO/MGCP
	 |						   |
	 v						   v
	MG  <---------- RTP ---------------->  MG

Now the appropriate mapping needs to be done between H.323 (H.225.0, H.245)
and MEGACO (or MGCP). This part is missing and no documentation is
available. If this is done, people could have interoperable implementations.

Similarly, the scenarios can be created for SIP and BICC and, mappings need
to be done as follows:

SIP/SDP <-> MEGACO (or MGCP)
BICC  <-> MEGACO (or MGCP)

Best regards,

Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 9:25 AM
To: 'asrar ashraf'; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 

_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan  3 10:56:31 2002
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 KAA04670
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:56:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA05495
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 10:56:33 -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 KAA04494;
	Thu, 3 Jan 2002 10:46:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04465
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 10:46:21 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04284
	for <megaco@ietf.org>; Thu, 3 Jan 2002 10:46:17 -0500 (EST)
From: Ext-Venkata.Ghadiyaram@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g03FkCC22562
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:46:12 +0200 (EET)
Received: from esebh24nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5839de1cbdac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 3 Jan 2002 17:46:19 +0200
Received: by esebh24nok with Internet Mail Service (5.5.2652.78)
	id <C1088QYD>; Thu, 3 Jan 2002 17:46:19 +0200
Message-ID: <9E3407CE45911B4097632389B77B2023AC7333@esebe014.NOE.Nokia.com>
To: rrroy@att.com, Brian.Rosen@marconi.com, asrar@enabtech.com,
        megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:46:10 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi,

I think we are getting further out of scope. If some document as Radhika
suggested, it would be appropriate in other forums rather than megaco.

Regards,
Kishore

-----Original Message-----
From: ext Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
Sent: 03. January 2002 17:27
To: Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Hi, Brian:

You are right.

What could have been better if we could have a document, like Madhubabu's
call flows, how the mapping is done as Tom Taylor has indicated. For
example, the scenarios can be as follows:

	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
	 ^						   ^
	 |						   |
     MEGACO/MGCP  				MEGACO/MGCP
	 |						   |
	 v						   v
	MG  <---------- RTP ---------------->  MG

Now the appropriate mapping needs to be done between H.323 (H.225.0, H.245)
and MEGACO (or MGCP). This part is missing and no documentation is
available. If this is done, people could have interoperable implementations.

Similarly, the scenarios can be created for SIP and BICC and, mappings need
to be done as follows:

SIP/SDP <-> MEGACO (or MGCP)
BICC  <-> MEGACO (or MGCP)

Best regards,

Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 9:25 AM
To: 'asrar ashraf'; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Neither RFC3015 nor Recommendation H.248 say anything about
interMGC communication.  It is out of scope of the protocol.
You can use anything you would like.  SIP/SIP-T works, but so
does BICC or even H.323.

Brian

> -----Original Message-----
> From: asrar ashraf [mailto:asrar@enabtech.com]
> Sent: Thursday, January 03, 2002 2:18 AM
> To: megaco@ietf.org
> Subject: [Megaco] Inter-MGC Communication
> 
> 
> Can Any one confirm that 
> Only SIP or SIP-T is used for Inter-MGC Communication.
>  What about other options.
> Can any one guide If There are any callFlows available for Inte-MGC
> communication ...
> 
>   regards
>  Asrar Ashraf
>  AvazNetworks
>  Islamabad, Pakistan
> 

_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan  3 11:09:37 2002
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 KAA03362
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 10:09:41 -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 JAA01355;
	Thu, 3 Jan 2002 09:56: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 JAA01325
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 09:56:56 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03123
	for <megaco@ietf.org>; Thu, 3 Jan 2002 09:56:51 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03Etqa17165;
	Thu, 3 Jan 2002 09:55:53 -0500 (EST)
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 g03Etpv00955;
	Thu, 3 Jan 2002 09:55:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPRTPJ>; Thu, 3 Jan 2002 09:54:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADBE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Cc: "'Terry L Anderson'" <tla@lucent.com>
Subject: RE: [Megaco] onhook/offhook strict and init
Date: Thu, 3 Jan 2002 09:54:21 -0500 
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

You are right.  The init parameter is required if strict has been set to
"state", but otherwise must not be reported.  


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Wednesday, January 02, 2002 8:54 PM
To: megaco@ietf.org
Subject: [Megaco] onhook/offhook strict and init


Hi Tom 
From Analog Line Supervision Package: 
        "exact" means that only an actual hook state transition to on- 
        hook is to be recognized; 
        "state" means that the event is to be recognized either if the 
        hook state transition is detected or if the hook state is 
        already on-hook; 
        "failWrong" means that if the hook state is already on-hook, 
        the command fails and an error is reported. 
   ObservedEventsDescriptor parameters 
        Initial State 
        ------------- 
        ParameterID: init (0x0002) 
        Type: Boolean 
        Possible values: 
        True means that the event was reported because the line was 
        already on-hook when the events descriptor containing this 
        event was activated; 
        False means that the event represents an actual state 
        transition to on-hook. 
  
Was  "Initial State" only intended to be used if "state" was used in the
Event Descriptor Request? 
If yes, can we add some clarification to IG? 
It is clear that "failWrong" would not cause Gwy to return "Initial State"
since an Error Descriptor is 
returned w/error code 540. 
Also it does not make sense for "exact" to result in an "Initial State"
parameter in the Notify from Gwy. 
  
  
Thanks 
Chuong 
  
  
  
-- 
  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


From megaco-admin@ietf.org  Thu Jan  3 11:52:28 2002
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 LAA05845
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 11:52:28 -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 LAA08238;
	Thu, 3 Jan 2002 11:40:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08209
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 11:40:39 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05665
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:40:35 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03Ge5n22714
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:40:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017A6AB; Thu, 3 Jan 2002 11:39:52 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 11:39:51 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF51C4@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUbRcxjEsLsQBdEdaSygAAwCUaDwAB/OIQ
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA08210
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

...

I suspect there is not a single exact
mapping.

[RRR] This is the problem. Should people like to live with this?

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan  3 11:52:29 2002
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 LAA05856
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 11:52:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08744
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 11:52:32 -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 LAA08238;
	Thu, 3 Jan 2002 11:40:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08209
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 11:40:39 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05665
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:40:35 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03Ge5n22714
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:40:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017A6AB; Thu, 3 Jan 2002 11:39:52 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 11:39:51 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF51C4@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUbRcxjEsLsQBdEdaSygAAwCUaDwAB/OIQ
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA08210
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

...

I suspect there is not a single exact
mapping.

[RRR] This is the problem. Should people like to live with this?

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan  3 11:52:43 2002
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 LAA05874
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 11:52:43 -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 LAA08407;
	Thu, 3 Jan 2002 11:45:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08377
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 11:45:31 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05748
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:45:26 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03Givn25943
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:44:58 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017A832; Thu, 3 Jan 2002 11:44:35 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 11:44:34 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF51D2@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUcB/sltmLXgBgEdaKOACQJ7Zb0gABVyQQ
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: <Ext-Venkata.Ghadiyaram@nokia.com>, <Brian.Rosen@marconi.com>,
        <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA08378
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



-----Original Message-----
From: Ext-Venkata.Ghadiyaram@nokia.com
[mailto:Ext-Venkata.Ghadiyaram@nokia.com]
Sent: Thursday, January 03, 2002 10:46 AM
To: Roy, Radhika R, ALCTA; Brian.Rosen@marconi.com; asrar@enabtech.com;
megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Hi,

I think we are getting further out of scope. If some document as Radhika
suggested, it would be appropriate in other forums rather than megaco.

[RRR] Yes, I agree. (Other forums will be a better place. Sometimes, people also do informational RFCs.)

Regards,
Kishore

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


From daemon@optimus.ietf.org  Thu Jan  3 11:52:44 2002
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 LAA05884
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 11:52:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08771
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 11:52:47 -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 LAA08407;
	Thu, 3 Jan 2002 11:45:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08377
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 11:45:31 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05748
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:45:26 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03Givn25943
	for <megaco@ietf.org>; Thu, 3 Jan 2002 11:44:58 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017A832; Thu, 3 Jan 2002 11:44:35 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 11:44:34 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF51D2@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUcB/sltmLXgBgEdaKOACQJ7Zb0gABVyQQ
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: <Ext-Venkata.Ghadiyaram@nokia.com>, <Brian.Rosen@marconi.com>,
        <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA08378
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



-----Original Message-----
From: Ext-Venkata.Ghadiyaram@nokia.com
[mailto:Ext-Venkata.Ghadiyaram@nokia.com]
Sent: Thursday, January 03, 2002 10:46 AM
To: Roy, Radhika R, ALCTA; Brian.Rosen@marconi.com; asrar@enabtech.com;
megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


Hi,

I think we are getting further out of scope. If some document as Radhika
suggested, it would be appropriate in other forums rather than megaco.

[RRR] Yes, I agree. (Other forums will be a better place. Sometimes, people also do informational RFCs.)

Regards,
Kishore

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



From megaco-admin@ietf.org  Thu Jan  3 13:33:17 2002
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 NAA07700
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 13:33: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 NAA12602;
	Thu, 3 Jan 2002 13:14:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12571
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 13:14:08 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (h56s192a140n47.user.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07479
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:14:05 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03IDHN03469;
	Thu, 3 Jan 2002 13:13:17 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y79WXR8Y>; Thu, 3 Jan 2002 13:11:38 -0500
Message-ID: <6DEE1D8911D5D411953E00508BE3DDF602D356A7@zrtpd0jn.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Roy, Radhika R, ALCTA" <rrroy@att.com>,
        "Rosen, Brian"
	 <Brian.Rosen@marconi.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 13:12:09 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19482.28B20820"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19482.28B20820
Content-Type: text/plain;
	charset="iso-8859-1"

As Brian stated, the translation is internal to a single entity (in this
case, the MGC).  I don't see a problem here, just as I don't see a problem
with different MGCs having different internal hardware.  Think "black box".
If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or
SIP or whatever on the other), then why worry about the translation?  If the
translation is not correct, for whatever reason, then the vendor will surely
figure that out and correct it, or their product will not sell!

Kevin

-----Original Message-----
From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
Sent: Thursday, January 03, 2002 11:40 AM
To: Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


...

I suspect there is not a single exact
mapping.

[RRR] This is the problem. Should people like to live with this?

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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

------_=_NextPart_001_01C19482.28B20820
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Inter-MGC Communication</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>As Brian stated, the translation is internal to a =
single entity (in this case, the MGC).&nbsp; I don't see a problem =
here, just as I don't see a problem with different MGCs having =
different internal hardware.&nbsp; Think &quot;black box&quot;.&nbsp; =
If the external interfaces are OK (H.248/Megaco on the one hand, and =
BICC or SIP or whatever on the other), then why worry about the =
translation?&nbsp; If the translation is not correct, for whatever =
reason, then the vendor will surely figure that out and correct it, or =
their product will not sell!</FONT></P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Roy, Radhika R, ALCTA [<A =
HREF=3D"mailto:rrroy@att.com">mailto:rrroy@att.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 03, 2002 11:40 AM</FONT>
<BR><FONT SIZE=3D2>To: Rosen, Brian; asrar ashraf; =
megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Inter-MGC Communication</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>...</FONT>
</P>

<P><FONT SIZE=3D2>I suspect there is not a single exact</FONT>
<BR><FONT SIZE=3D2>mapping.</FONT>
</P>

<P><FONT SIZE=3D2>[RRR] This is the problem. Should people like to live =
with this?</FONT>
</P>

<P><FONT SIZE=3D2>Brian</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Roy, Radhika R, ALCTA [<A =
HREF=3D"mailto:rrroy@att.com">mailto:rrroy@att.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 03, 2002 10:27 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Rosen, Brian; asrar ashraf; =
megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi, Brian:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; You are right.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; What could have been better if we could have a =
document, like </FONT>
<BR><FONT SIZE=3D2>&gt; Madhubabu's call flows, how the mapping is done =
as Tom Taylor </FONT>
<BR><FONT SIZE=3D2>&gt; has indicated. For example, the scenarios can =
be as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MGC&nbsp; =
&lt;--- H.323 (H.225.0, H.245) ---&gt; MGC</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
^&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ^</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MEGACO/MGCP&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MEGACO/MGCP</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
v&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; v</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MG&nbsp; =
&lt;---------- RTP ----------------&gt;&nbsp; MG</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Now the appropriate mapping needs to be done =
between H.323 </FONT>
<BR><FONT SIZE=3D2>&gt; (H.225.0, H.245) and MEGACO (or MGCP). This =
part is missing </FONT>
<BR><FONT SIZE=3D2>&gt; and no documentation is available. If this is =
done, people </FONT>
<BR><FONT SIZE=3D2>&gt; could have interoperable =
implementations.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Similarly, the scenarios can be created for SIP =
and BICC and, </FONT>
<BR><FONT SIZE=3D2>&gt; mappings need to be done as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; SIP/SDP &lt;-&gt; MEGACO (or MGCP)</FONT>
<BR><FONT SIZE=3D2>&gt; BICC&nbsp; &lt;-&gt; MEGACO (or MGCP)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Best regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Radhika R. Roy</FONT>
<BR><FONT SIZE=3D2>&gt; rrroy@att.com</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Rosen, Brian [<A =
HREF=3D"mailto:Brian.Rosen@marconi.com">mailto:Brian.Rosen@marconi.com</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 03, 2002 9:25 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'asrar ashraf'; megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Neither RFC3015 nor Recommendation H.248 say =
anything about</FONT>
<BR><FONT SIZE=3D2>&gt; interMGC communication.&nbsp; It is out of =
scope of the protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; You can use anything you would like.&nbsp; =
SIP/SIP-T works, but so</FONT>
<BR><FONT SIZE=3D2>&gt; does BICC or even H.323.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Brian</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: asrar ashraf [<A =
HREF=3D"mailto:asrar@enabtech.com">mailto:asrar@enabtech.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, January 03, 2002 2:18 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Can Any one confirm that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Only SIP or SIP-T is used for Inter-MGC =
Communication.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; What about other options.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Can any one guide If There are any =
callFlows available for Inte-MGC</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; communication ...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; regards</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; Asrar Ashraf</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; AvazNetworks</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; Islamabad, Pakistan</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" TARGET=3D"_blank"=
>https://www1.ietf.org/mailman/listinfo/megaco</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19482.28B20820--

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


From daemon@optimus.ietf.org  Thu Jan  3 13:33:19 2002
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 NAA07709
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 13:33:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA13320
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 13:33:20 -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 NAA12602;
	Thu, 3 Jan 2002 13:14:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA12571
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 13:14:08 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (h56s192a140n47.user.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07479
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:14:05 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g03IDHN03469;
	Thu, 3 Jan 2002 13:13:17 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y79WXR8Y>; Thu, 3 Jan 2002 13:11:38 -0500
Message-ID: <6DEE1D8911D5D411953E00508BE3DDF602D356A7@zrtpd0jn.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Roy, Radhika R, ALCTA" <rrroy@att.com>,
        "Rosen, Brian"
	 <Brian.Rosen@marconi.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 13:12:09 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19482.28B20820"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19482.28B20820
Content-Type: text/plain;
	charset="iso-8859-1"

As Brian stated, the translation is internal to a single entity (in this
case, the MGC).  I don't see a problem here, just as I don't see a problem
with different MGCs having different internal hardware.  Think "black box".
If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or
SIP or whatever on the other), then why worry about the translation?  If the
translation is not correct, for whatever reason, then the vendor will surely
figure that out and correct it, or their product will not sell!

Kevin

-----Original Message-----
From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
Sent: Thursday, January 03, 2002 11:40 AM
To: Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


...

I suspect there is not a single exact
mapping.

[RRR] This is the problem. Should people like to live with this?

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 10:27 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Brian:
> 
> You are right.
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows:
> 
> 	MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> 	 ^						   ^
> 	 |						   |
>      MEGACO/MGCP  				MEGACO/MGCP
> 	 |						   |
> 	 v						   v
> 	MG  <---------- RTP ---------------->  MG
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations.
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows:
> 
> SIP/SDP <-> MEGACO (or MGCP)
> BICC  <-> MEGACO (or MGCP)
> 
> Best regards,
> 
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 9:25 AM
> To: 'asrar ashraf'; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about
> interMGC communication.  It is out of scope of the protocol.
> You can use anything you would like.  SIP/SIP-T works, but so
> does BICC or even H.323.
> 
> Brian
> 
> > -----Original Message-----
> > From: asrar ashraf [mailto:asrar@enabtech.com]
> > Sent: Thursday, January 03, 2002 2:18 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Inter-MGC Communication
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication.
> >  What about other options.
> > Can any one guide If There are any callFlows available for Inte-MGC
> > communication ...
> > 
> >   regards
> >  Asrar Ashraf
> >  AvazNetworks
> >  Islamabad, Pakistan
> > 
> 
> _______________________________________________
> 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

------_=_NextPart_001_01C19482.28B20820
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Inter-MGC Communication</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>As Brian stated, the translation is internal to a =
single entity (in this case, the MGC).&nbsp; I don't see a problem =
here, just as I don't see a problem with different MGCs having =
different internal hardware.&nbsp; Think &quot;black box&quot;.&nbsp; =
If the external interfaces are OK (H.248/Megaco on the one hand, and =
BICC or SIP or whatever on the other), then why worry about the =
translation?&nbsp; If the translation is not correct, for whatever =
reason, then the vendor will surely figure that out and correct it, or =
their product will not sell!</FONT></P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Roy, Radhika R, ALCTA [<A =
HREF=3D"mailto:rrroy@att.com">mailto:rrroy@att.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 03, 2002 11:40 AM</FONT>
<BR><FONT SIZE=3D2>To: Rosen, Brian; asrar ashraf; =
megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Inter-MGC Communication</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>...</FONT>
</P>

<P><FONT SIZE=3D2>I suspect there is not a single exact</FONT>
<BR><FONT SIZE=3D2>mapping.</FONT>
</P>

<P><FONT SIZE=3D2>[RRR] This is the problem. Should people like to live =
with this?</FONT>
</P>

<P><FONT SIZE=3D2>Brian</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Roy, Radhika R, ALCTA [<A =
HREF=3D"mailto:rrroy@att.com">mailto:rrroy@att.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 03, 2002 10:27 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Rosen, Brian; asrar ashraf; =
megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi, Brian:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; You are right.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; What could have been better if we could have a =
document, like </FONT>
<BR><FONT SIZE=3D2>&gt; Madhubabu's call flows, how the mapping is done =
as Tom Taylor </FONT>
<BR><FONT SIZE=3D2>&gt; has indicated. For example, the scenarios can =
be as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MGC&nbsp; =
&lt;--- H.323 (H.225.0, H.245) ---&gt; MGC</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
^&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ^</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MEGACO/MGCP&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MEGACO/MGCP</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
v&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; v</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MG&nbsp; =
&lt;---------- RTP ----------------&gt;&nbsp; MG</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Now the appropriate mapping needs to be done =
between H.323 </FONT>
<BR><FONT SIZE=3D2>&gt; (H.225.0, H.245) and MEGACO (or MGCP). This =
part is missing </FONT>
<BR><FONT SIZE=3D2>&gt; and no documentation is available. If this is =
done, people </FONT>
<BR><FONT SIZE=3D2>&gt; could have interoperable =
implementations.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Similarly, the scenarios can be created for SIP =
and BICC and, </FONT>
<BR><FONT SIZE=3D2>&gt; mappings need to be done as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; SIP/SDP &lt;-&gt; MEGACO (or MGCP)</FONT>
<BR><FONT SIZE=3D2>&gt; BICC&nbsp; &lt;-&gt; MEGACO (or MGCP)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Best regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Radhika R. Roy</FONT>
<BR><FONT SIZE=3D2>&gt; rrroy@att.com</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Rosen, Brian [<A =
HREF=3D"mailto:Brian.Rosen@marconi.com">mailto:Brian.Rosen@marconi.com</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, January 03, 2002 9:25 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'asrar ashraf'; megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Neither RFC3015 nor Recommendation H.248 say =
anything about</FONT>
<BR><FONT SIZE=3D2>&gt; interMGC communication.&nbsp; It is out of =
scope of the protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; You can use anything you would like.&nbsp; =
SIP/SIP-T works, but so</FONT>
<BR><FONT SIZE=3D2>&gt; does BICC or even H.323.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Brian</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: asrar ashraf [<A =
HREF=3D"mailto:asrar@enabtech.com">mailto:asrar@enabtech.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, January 03, 2002 2:18 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Megaco] Inter-MGC =
Communication</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Can Any one confirm that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Only SIP or SIP-T is used for Inter-MGC =
Communication.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; What about other options.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Can any one guide If There are any =
callFlows available for Inte-MGC</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; communication ...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; regards</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; Asrar Ashraf</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; AvazNetworks</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; Islamabad, Pakistan</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" TARGET=3D"_blank"=
>https://www1.ietf.org/mailman/listinfo/megaco</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19482.28B20820--

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



From megaco-admin@ietf.org  Thu Jan  3 14:15:42 2002
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 OAA08621
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 14:15:42 -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 NAA13985;
	Thu, 3 Jan 2002 13:59:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13954
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 13:59:13 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08259
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:59:10 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03IvVn29963
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:57:31 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh3i.attrh.att.com (5.5.029)
        id 3C0695050074FDEA; Thu, 3 Jan 2002 13:55:57 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 13:56:31 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF52E5@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUglQAVcQbgQBxEdaSygAAwCUaDwAAlYWw
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA13955
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

Hi, Kevin:
 
I beg to disagree with you here.
 
The decomposition of the GWs has been done to have other benefits as well. For example, MGCs from one vendor, while MGs from other vendors.
 
What do we expect in those situations? Do the service providers be forced to lock into proprietary solutions/implementations?
 
I understand the problems that MEGACO WG may not be chartered to address those issues. That does not mean we should NOT be worried about those issues. MEGACO WG has done its primary job and it is a very proud achievement (in standardizing the MEGACO protocol). As we move forward, we have to see how the industry can reap the benefits in implementing the large-scale networks in multi-vendor and multi-protocol environment using the MEGACO protocol.
 
Since the MEGACO protocol is standardized, now, we have the luxury to go for the next step: Interoperability in multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor environment using the MEGACO protocol. Not only that, it is also applicable for all transport networks (PSTN, IP, ATM, FR). I feel that MEGACO is providing a wonderful GLUE to solve these complex problems what could not even be imagined couples of years ago.
 
Best regards,
Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Sent: Thursday, January 03, 2002 1:12 PM
To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication



As Brian stated, the translation is internal to a single entity (in this case, the MGC).  I don't see a problem here, just as I don't see a problem with different MGCs having different internal hardware.  Think "black box".  If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or SIP or whatever on the other), then why worry about the translation?  If the translation is not correct, for whatever reason, then the vendor will surely figure that out and correct it, or their product will not sell!

Kevin 

-----Original Message----- 
From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
Sent: Thursday, January 03, 2002 11:40 AM 
To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
Subject: RE: [Megaco] Inter-MGC Communication 


... 

I suspect there is not a single exact 
mapping. 

[RRR] This is the problem. Should people like to live with this? 

Brian 

> -----Original Message----- 
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> Sent: Thursday, January 03, 2002 10:27 AM 
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> Hi, Brian: 
> 
> You are right. 
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows: 
> 
>       MGC  <--- H.323 (H.225.0, H.245) ---> MGC 
>        ^                                                 ^ 
>        |                                                 | 
>      MEGACO/MGCP                              MEGACO/MGCP 
>        |                                                 | 
>        v                                                 v 
>       MG  <---------- RTP ---------------->  MG 
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations. 
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows: 
> 
> SIP/SDP <-> MEGACO (or MGCP) 
> BICC  <-> MEGACO (or MGCP) 
> 
> Best regards, 
> 
> Radhika R. Roy 
> rrroy@att.com 
> 
> -----Original Message----- 
> From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com] 
> Sent: Thursday, January 03, 2002 9:25 AM 
> To: 'asrar ashraf'; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about 
> interMGC communication.  It is out of scope of the protocol. 
> You can use anything you would like.  SIP/SIP-T works, but so 
> does BICC or even H.323. 
> 
> Brian 
> 
> > -----Original Message----- 
> > From: asrar ashraf [ mailto:asrar@enabtech.com] 
> > Sent: Thursday, January 03, 2002 2:18 AM 
> > To: megaco@ietf.org 
> > Subject: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication. 
> >  What about other options. 
> > Can any one guide If There are any callFlows available for Inte-MGC 
> > communication ... 
> > 
> >   regards 
> >  Asrar Ashraf 
> >  AvazNetworks 
> >  Islamabad, Pakistan 
> > 
> 
> _______________________________________________ 
> 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


From daemon@optimus.ietf.org  Thu Jan  3 15:09:39 2002
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 OAA08630
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 14:15:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14871
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 14:15:45 -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 NAA13985;
	Thu, 3 Jan 2002 13:59:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13954
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 13:59:13 -0500 (EST)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08259
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:59:10 -0500 (EST)
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03IvVn29963
	for <megaco@ietf.org>; Thu, 3 Jan 2002 13:57:31 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh3i.attrh.att.com (5.5.029)
        id 3C0695050074FDEA; Thu, 3 Jan 2002 13:55:57 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 13:56:31 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF52E5@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUglQAVcQbgQBxEdaSygAAwCUaDwAAlYWw
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA13955
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

Hi, Kevin:
 
I beg to disagree with you here.
 
The decomposition of the GWs has been done to have other benefits as well. For example, MGCs from one vendor, while MGs from other vendors.
 
What do we expect in those situations? Do the service providers be forced to lock into proprietary solutions/implementations?
 
I understand the problems that MEGACO WG may not be chartered to address those issues. That does not mean we should NOT be worried about those issues. MEGACO WG has done its primary job and it is a very proud achievement (in standardizing the MEGACO protocol). As we move forward, we have to see how the industry can reap the benefits in implementing the large-scale networks in multi-vendor and multi-protocol environment using the MEGACO protocol.
 
Since the MEGACO protocol is standardized, now, we have the luxury to go for the next step: Interoperability in multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor environment using the MEGACO protocol. Not only that, it is also applicable for all transport networks (PSTN, IP, ATM, FR). I feel that MEGACO is providing a wonderful GLUE to solve these complex problems what could not even be imagined couples of years ago.
 
Best regards,
Radhika R. Roy
rrroy@att.com

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
Sent: Thursday, January 03, 2002 1:12 PM
To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication



As Brian stated, the translation is internal to a single entity (in this case, the MGC).  I don't see a problem here, just as I don't see a problem with different MGCs having different internal hardware.  Think "black box".  If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or SIP or whatever on the other), then why worry about the translation?  If the translation is not correct, for whatever reason, then the vendor will surely figure that out and correct it, or their product will not sell!

Kevin 

-----Original Message----- 
From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
Sent: Thursday, January 03, 2002 11:40 AM 
To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
Subject: RE: [Megaco] Inter-MGC Communication 


... 

I suspect there is not a single exact 
mapping. 

[RRR] This is the problem. Should people like to live with this? 

Brian 

> -----Original Message----- 
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> Sent: Thursday, January 03, 2002 10:27 AM 
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> Hi, Brian: 
> 
> You are right. 
> 
> What could have been better if we could have a document, like 
> Madhubabu's call flows, how the mapping is done as Tom Taylor 
> has indicated. For example, the scenarios can be as follows: 
> 
>       MGC  <--- H.323 (H.225.0, H.245) ---> MGC 
>        ^                                                 ^ 
>        |                                                 | 
>      MEGACO/MGCP                              MEGACO/MGCP 
>        |                                                 | 
>        v                                                 v 
>       MG  <---------- RTP ---------------->  MG 
> 
> Now the appropriate mapping needs to be done between H.323 
> (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> and no documentation is available. If this is done, people 
> could have interoperable implementations. 
> 
> Similarly, the scenarios can be created for SIP and BICC and, 
> mappings need to be done as follows: 
> 
> SIP/SDP <-> MEGACO (or MGCP) 
> BICC  <-> MEGACO (or MGCP) 
> 
> Best regards, 
> 
> Radhika R. Roy 
> rrroy@att.com 
> 
> -----Original Message----- 
> From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com] 
> Sent: Thursday, January 03, 2002 9:25 AM 
> To: 'asrar ashraf'; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> Neither RFC3015 nor Recommendation H.248 say anything about 
> interMGC communication.  It is out of scope of the protocol. 
> You can use anything you would like.  SIP/SIP-T works, but so 
> does BICC or even H.323. 
> 
> Brian 
> 
> > -----Original Message----- 
> > From: asrar ashraf [ mailto:asrar@enabtech.com] 
> > Sent: Thursday, January 03, 2002 2:18 AM 
> > To: megaco@ietf.org 
> > Subject: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Can Any one confirm that 
> > Only SIP or SIP-T is used for Inter-MGC Communication. 
> >  What about other options. 
> > Can any one guide If There are any callFlows available for Inte-MGC 
> > communication ... 
> > 
> >   regards 
> >  Asrar Ashraf 
> >  AvazNetworks 
> >  Islamabad, Pakistan 
> > 
> 
> _______________________________________________ 
> 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



From megaco-admin@ietf.org  Thu Jan  3 15:12:26 2002
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 PAA10120
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 15:12:22 -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 OAA17148;
	Thu, 3 Jan 2002 14:53:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17118
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 14:53:16 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09734
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:53:11 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03JqeW04346
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:52:41 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017DFB1; Thu, 3 Jan 2002 14:52:10 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 14:52:11 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF5385@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUjeyMFi2PFwCAEdanAgCQJ3s5nwAACu2w
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA17119
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



-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 2:36 PM
To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


You are missing the point.  An MGC that interworks H.323 to Megaco
should work with any MG from any vendor that supports the appropriate
packages for the type of termination supported.  No standardization is
required for that.  Such an MGC should be able to interwork with
any H.323 terminal or gateway.  

It's all local to the MGC.

[RRR] If everything is local to MGC and there is no dependency in sending the particular messages among the MGCs, there is no need for any additional work.

[RRR] However, there may be a dependency directly or indirectly in communications between the MGC and MG and vice versa based on what MGCs do among themselves using other protocols (e.g., H.323, SIP). For example, the implications of QOS and other attributes.

[RRR] The whole idea has been to go through all those scenarios for a given protocol, we can then find out what the end result is (may be to prove what you have said).

No standardization is required for that.

[RRR] It is not about standardization per se. The concern is more about interoperability.

Brian


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


From daemon@optimus.ietf.org  Thu Jan  3 15:12:27 2002
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 PAA10130
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 15:12:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA18016
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 15:12:30 -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 OAA17148;
	Thu, 3 Jan 2002 14:53:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17118
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 14:53:16 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09734
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:53:11 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03JqeW04346
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:52:41 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A50017DFB1; Thu, 3 Jan 2002 14:52:10 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 14:52:11 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF5385@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUjeyMFi2PFwCAEdanAgCQJ3s5nwAACu2w
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA17119
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



-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 2:36 PM
To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


You are missing the point.  An MGC that interworks H.323 to Megaco
should work with any MG from any vendor that supports the appropriate
packages for the type of termination supported.  No standardization is
required for that.  Such an MGC should be able to interwork with
any H.323 terminal or gateway.  

It's all local to the MGC.

[RRR] If everything is local to MGC and there is no dependency in sending the particular messages among the MGCs, there is no need for any additional work.

[RRR] However, there may be a dependency directly or indirectly in communications between the MGC and MG and vice versa based on what MGCs do among themselves using other protocols (e.g., H.323, SIP). For example, the implications of QOS and other attributes.

[RRR] The whole idea has been to go through all those scenarios for a given protocol, we can then find out what the end result is (may be to prove what you have said).

No standardization is required for that.

[RRR] It is not about standardization per se. The concern is more about interoperability.

Brian


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



From megaco-admin@ietf.org  Thu Jan  3 15:17:37 2002
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 PAA10270
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 15:17:37 -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 OAA16021;
	Thu, 3 Jan 2002 14:36:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15992
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 14:36:12 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09171
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:36:08 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA02534;
	Thu, 3 Jan 2002 14:35:38 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA08076;
	Thu, 3 Jan 2002 14:35:38 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNM4X0>; Thu, 3 Jan 2002 14:35:38 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C76B@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        Kevin Boyle
	 <kboyle@nortelnetworks.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 14:35:36 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You are missing the point.  An MGC that interworks H.323 to Megaco
should work with any MG from any vendor that supports the appropriate
packages for the type of termination supported.  No standardization is
required for that.  Such an MGC should be able to interwork with
any H.323 terminal or gateway.  No standardization is required for
that.

It's all local to the MGC.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 1:57 PM
> To: Kevin Boyle; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Kevin:
>  
> I beg to disagree with you here.
>  
> The decomposition of the GWs has been done to have other 
> benefits as well. For example, MGCs from one vendor, while 
> MGs from other vendors.
>  
> What do we expect in those situations? Do the service 
> providers be forced to lock into proprietary 
> solutions/implementations?
>  
> I understand the problems that MEGACO WG may not be chartered 
> to address those issues. That does not mean we should NOT be 
> worried about those issues. MEGACO WG has done its primary 
> job and it is a very proud achievement (in standardizing the 
> MEGACO protocol). As we move forward, we have to see how the 
> industry can reap the benefits in implementing the 
> large-scale networks in multi-vendor and multi-protocol 
> environment using the MEGACO protocol.
>  
> Since the MEGACO protocol is standardized, now, we have the 
> luxury to go for the next step: Interoperability in 
> multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor 
> environment using the MEGACO protocol. Not only that, it is 
> also applicable for all transport networks (PSTN, IP, ATM, 
> FR). I feel that MEGACO is providing a wonderful GLUE to 
> solve these complex problems what could not even be imagined 
> couples of years ago.
>  
> Best regards,
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
> Sent: Thursday, January 03, 2002 1:12 PM
> To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> 
> As Brian stated, the translation is internal to a single 
> entity (in this case, the MGC).  I don't see a problem here, 
> just as I don't see a problem with different MGCs having 
> different internal hardware.  Think "black box".  If the 
> external interfaces are OK (H.248/Megaco on the one hand, and 
> BICC or SIP or whatever on the other), then why worry about 
> the translation?  If the translation is not correct, for 
> whatever reason, then the vendor will surely figure that out 
> and correct it, or their product will not sell!
> 
> Kevin 
> 
> -----Original Message----- 
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> Sent: Thursday, January 03, 2002 11:40 AM 
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> ... 
> 
> I suspect there is not a single exact 
> mapping. 
> 
> [RRR] This is the problem. Should people like to live with this? 
> 
> Brian 
> 
> > -----Original Message----- 
> > From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> > Sent: Thursday, January 03, 2002 10:27 AM 
> > To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> > Subject: RE: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Hi, Brian: 
> > 
> > You are right. 
> > 
> > What could have been better if we could have a document, like 
> > Madhubabu's call flows, how the mapping is done as Tom Taylor 
> > has indicated. For example, the scenarios can be as follows: 
> > 
> >       MGC  <--- H.323 (H.225.0, H.245) ---> MGC 
> >        ^                                                 ^ 
> >        |                                                 | 
> >      MEGACO/MGCP                              MEGACO/MGCP 
> >        |                                                 | 
> >        v                                                 v 
> >       MG  <---------- RTP ---------------->  MG 
> > 
> > Now the appropriate mapping needs to be done between H.323 
> > (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> > and no documentation is available. If this is done, people 
> > could have interoperable implementations. 
> > 
> > Similarly, the scenarios can be created for SIP and BICC and, 
> > mappings need to be done as follows: 
> > 
> > SIP/SDP <-> MEGACO (or MGCP) 
> > BICC  <-> MEGACO (or MGCP) 
> > 
> > Best regards, 
> > 
> > Radhika R. Roy 
> > rrroy@att.com 
> > 
> > -----Original Message----- 
> > From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com] 
> > Sent: Thursday, January 03, 2002 9:25 AM 
> > To: 'asrar ashraf'; megaco@ietf.org 
> > Subject: RE: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Neither RFC3015 nor Recommendation H.248 say anything about 
> > interMGC communication.  It is out of scope of the protocol. 
> > You can use anything you would like.  SIP/SIP-T works, but so 
> > does BICC or even H.323. 
> > 
> > Brian 
> > 
> > > -----Original Message----- 
> > > From: asrar ashraf [ mailto:asrar@enabtech.com] 
> > > Sent: Thursday, January 03, 2002 2:18 AM 
> > > To: megaco@ietf.org 
> > > Subject: [Megaco] Inter-MGC Communication 
> > > 
> > > 
> > > Can Any one confirm that 
> > > Only SIP or SIP-T is used for Inter-MGC Communication. 
> > >  What about other options. 
> > > Can any one guide If There are any callFlows available 
> for Inte-MGC 
> > > communication ... 
> > > 
> > >   regards 
> > >  Asrar Ashraf 
> > >  AvazNetworks 
> > >  Islamabad, Pakistan 
> > > 
> > 
> > _______________________________________________ 
> > 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


From daemon@optimus.ietf.org  Thu Jan  3 15:17:37 2002
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 PAA10280
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 15:17:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA18171
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 15:17:40 -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 OAA16021;
	Thu, 3 Jan 2002 14:36:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15992
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 14:36:12 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09171
	for <megaco@ietf.org>; Thu, 3 Jan 2002 14:36:08 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA02534;
	Thu, 3 Jan 2002 14:35:38 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA08076;
	Thu, 3 Jan 2002 14:35:38 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNM4X0>; Thu, 3 Jan 2002 14:35:38 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C76B@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        Kevin Boyle
	 <kboyle@nortelnetworks.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 14:35:36 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You are missing the point.  An MGC that interworks H.323 to Megaco
should work with any MG from any vendor that supports the appropriate
packages for the type of termination supported.  No standardization is
required for that.  Such an MGC should be able to interwork with
any H.323 terminal or gateway.  No standardization is required for
that.

It's all local to the MGC.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 1:57 PM
> To: Kevin Boyle; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> Hi, Kevin:
>  
> I beg to disagree with you here.
>  
> The decomposition of the GWs has been done to have other 
> benefits as well. For example, MGCs from one vendor, while 
> MGs from other vendors.
>  
> What do we expect in those situations? Do the service 
> providers be forced to lock into proprietary 
> solutions/implementations?
>  
> I understand the problems that MEGACO WG may not be chartered 
> to address those issues. That does not mean we should NOT be 
> worried about those issues. MEGACO WG has done its primary 
> job and it is a very proud achievement (in standardizing the 
> MEGACO protocol). As we move forward, we have to see how the 
> industry can reap the benefits in implementing the 
> large-scale networks in multi-vendor and multi-protocol 
> environment using the MEGACO protocol.
>  
> Since the MEGACO protocol is standardized, now, we have the 
> luxury to go for the next step: Interoperability in 
> multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor 
> environment using the MEGACO protocol. Not only that, it is 
> also applicable for all transport networks (PSTN, IP, ATM, 
> FR). I feel that MEGACO is providing a wonderful GLUE to 
> solve these complex problems what could not even be imagined 
> couples of years ago.
>  
> Best regards,
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
> Sent: Thursday, January 03, 2002 1:12 PM
> To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> 
> As Brian stated, the translation is internal to a single 
> entity (in this case, the MGC).  I don't see a problem here, 
> just as I don't see a problem with different MGCs having 
> different internal hardware.  Think "black box".  If the 
> external interfaces are OK (H.248/Megaco on the one hand, and 
> BICC or SIP or whatever on the other), then why worry about 
> the translation?  If the translation is not correct, for 
> whatever reason, then the vendor will surely figure that out 
> and correct it, or their product will not sell!
> 
> Kevin 
> 
> -----Original Message----- 
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> Sent: Thursday, January 03, 2002 11:40 AM 
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> Subject: RE: [Megaco] Inter-MGC Communication 
> 
> 
> ... 
> 
> I suspect there is not a single exact 
> mapping. 
> 
> [RRR] This is the problem. Should people like to live with this? 
> 
> Brian 
> 
> > -----Original Message----- 
> > From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com] 
> > Sent: Thursday, January 03, 2002 10:27 AM 
> > To: Rosen, Brian; asrar ashraf; megaco@ietf.org 
> > Subject: RE: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Hi, Brian: 
> > 
> > You are right. 
> > 
> > What could have been better if we could have a document, like 
> > Madhubabu's call flows, how the mapping is done as Tom Taylor 
> > has indicated. For example, the scenarios can be as follows: 
> > 
> >       MGC  <--- H.323 (H.225.0, H.245) ---> MGC 
> >        ^                                                 ^ 
> >        |                                                 | 
> >      MEGACO/MGCP                              MEGACO/MGCP 
> >        |                                                 | 
> >        v                                                 v 
> >       MG  <---------- RTP ---------------->  MG 
> > 
> > Now the appropriate mapping needs to be done between H.323 
> > (H.225.0, H.245) and MEGACO (or MGCP). This part is missing 
> > and no documentation is available. If this is done, people 
> > could have interoperable implementations. 
> > 
> > Similarly, the scenarios can be created for SIP and BICC and, 
> > mappings need to be done as follows: 
> > 
> > SIP/SDP <-> MEGACO (or MGCP) 
> > BICC  <-> MEGACO (or MGCP) 
> > 
> > Best regards, 
> > 
> > Radhika R. Roy 
> > rrroy@att.com 
> > 
> > -----Original Message----- 
> > From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com] 
> > Sent: Thursday, January 03, 2002 9:25 AM 
> > To: 'asrar ashraf'; megaco@ietf.org 
> > Subject: RE: [Megaco] Inter-MGC Communication 
> > 
> > 
> > Neither RFC3015 nor Recommendation H.248 say anything about 
> > interMGC communication.  It is out of scope of the protocol. 
> > You can use anything you would like.  SIP/SIP-T works, but so 
> > does BICC or even H.323. 
> > 
> > Brian 
> > 
> > > -----Original Message----- 
> > > From: asrar ashraf [ mailto:asrar@enabtech.com] 
> > > Sent: Thursday, January 03, 2002 2:18 AM 
> > > To: megaco@ietf.org 
> > > Subject: [Megaco] Inter-MGC Communication 
> > > 
> > > 
> > > Can Any one confirm that 
> > > Only SIP or SIP-T is used for Inter-MGC Communication. 
> > >  What about other options. 
> > > Can any one guide If There are any callFlows available 
> for Inte-MGC 
> > > communication ... 
> > > 
> > >   regards 
> > >  Asrar Ashraf 
> > >  AvazNetworks 
> > >  Islamabad, Pakistan 
> > > 
> > 
> > _______________________________________________ 
> > 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



From megaco-admin@ietf.org  Thu Jan  3 17:14:51 2002
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 RAA12522
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:14:51 -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 RAA22416;
	Thu, 3 Jan 2002 17:03:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22385
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 17:02:59 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12309
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:02:54 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA15714;
	Thu, 3 Jan 2002 17:02:25 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA07693;
	Thu, 3 Jan 2002 17:02:26 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNM7G0>; Thu, 3 Jan 2002 17:02:26 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C775@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        Kevin Boyle
	 <kboyle@nortelnetworks.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:01:59 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.

I don't think there is anything like it.  I believe there was a
concern raised about H.450 video events; they would be hard
to field at the MGC.  Because Megaco is master/slave, the MGC
tells the MG how to handle the QoS stuff.  I don't think there is
any problem with SIP or BICC.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 2:52 PM
> To: Rosen, Brian; Kevin Boyle; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> 
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 2:36 PM
> To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> You are missing the point.  An MGC that interworks H.323 to Megaco
> should work with any MG from any vendor that supports the appropriate
> packages for the type of termination supported.  No standardization is
> required for that.  Such an MGC should be able to interwork with
> any H.323 terminal or gateway.  
> 
> It's all local to the MGC.
> 
> [RRR] If everything is local to MGC and there is no 
> dependency in sending the particular messages among the MGCs, 
> there is no need for any additional work.
> 
> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.
> 
> [RRR] The whole idea has been to go through all those 
> scenarios for a given protocol, we can then find out what the 
> end result is (may be to prove what you have said).
> 
> No standardization is required for that.
> 
> [RRR] It is not about standardization per se. The concern is 
> more about interoperability.
> 
> Brian
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan  3 17:14:51 2002
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 RAA12531
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:14:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA22565
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 17:14:56 -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 RAA22416;
	Thu, 3 Jan 2002 17:03:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22385
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 17:02:59 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12309
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:02:54 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA15714;
	Thu, 3 Jan 2002 17:02:25 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA07693;
	Thu, 3 Jan 2002 17:02:26 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZNKNM7G0>; Thu, 3 Jan 2002 17:02:26 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C775@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Roy, Radhika R, ALCTA'" <rrroy@att.com>,
        Kevin Boyle
	 <kboyle@nortelnetworks.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:01:59 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.

I don't think there is anything like it.  I believe there was a
concern raised about H.450 video events; they would be hard
to field at the MGC.  Because Megaco is master/slave, the MGC
tells the MG how to handle the QoS stuff.  I don't think there is
any problem with SIP or BICC.

Brian

> -----Original Message-----
> From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 2:52 PM
> To: Rosen, Brian; Kevin Boyle; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> 
> 
> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, January 03, 2002 2:36 PM
> To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> 
> You are missing the point.  An MGC that interworks H.323 to Megaco
> should work with any MG from any vendor that supports the appropriate
> packages for the type of termination supported.  No standardization is
> required for that.  Such an MGC should be able to interwork with
> any H.323 terminal or gateway.  
> 
> It's all local to the MGC.
> 
> [RRR] If everything is local to MGC and there is no 
> dependency in sending the particular messages among the MGCs, 
> there is no need for any additional work.
> 
> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.
> 
> [RRR] The whole idea has been to go through all those 
> scenarios for a given protocol, we can then find out what the 
> end result is (may be to prove what you have said).
> 
> No standardization is required for that.
> 
> [RRR] It is not about standardization per se. The concern is 
> more about interoperability.
> 
> Brian
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan  3 17:45:41 2002
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 RAA12852
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:45:41 -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 RAA22803;
	Thu, 3 Jan 2002 17:26:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22710
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 17:26:44 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12653
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:26:40 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03MQAW02638
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:26:10 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A500180EDF; Thu, 3 Jan 2002 17:25:13 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:25:12 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF5509@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUopzn/8dcYQCSEdajbgCQJ60IGQAAGhNw
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA22711
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



-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 5:02 PM
To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.

I don't think there is anything like it.  I believe there was a
concern raised about H.450 video events; they would be hard
to field at the MGC.  

[RRR] It is nice to know someone did some analysis or testing. This is what is needed to come out for interoperable implementations. As long as we all agree that it works and interoperates, we are done. (Still it appears that there may be some issues.)

Because Megaco is master/slave, the MGC
tells the MG how to handle the QoS stuff. 

[RRR] I would suggest to look into some QOS contributions provided in MEGACO. It shows that there are some basic issues (e.g., policy) that need to be resolved for the base MEGACO protocol itself. Then the question comes whether we need to do anything extra when other protocols are used among the MGCs.

I don't think there is
any problem with SIP or BICC.

[RRR] May be you are right. So, as I explained earlier, if we all agree that things are interoperable in multi-protocol and multi-vendor environment, then we are done. (Are we all sure about this?)

[RRR} Last of all, let me provide a pointer. For example, Madhubabu has provided a "MEGACO Call Flows" I-D. There is no new standardization works. However, it shows how things can be implemented and if we all agree with these procedures and it provides a baseline for interoperable implementations (should any questions arise). The same is true for the SIP Call Flows or SIP services example. (Why can we not do the same MEGACO for inter-MGC communications where SIP, H.323, etc. are used?)

Brian


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


From daemon@optimus.ietf.org  Thu Jan  3 17:45:41 2002
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 RAA12861
	for <megaco-archive@odin.ietf.org>; Thu, 3 Jan 2002 17:45:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA23403
	for megaco-archive@odin.ietf.org; Thu, 3 Jan 2002 17:45:44 -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 RAA22803;
	Thu, 3 Jan 2002 17:26:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22710
	for <megaco@optimus.ietf.org>; Thu, 3 Jan 2002 17:26:44 -0500 (EST)
Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12653
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:26:40 -0500 (EST)
Received: from attrh1i.attrh.att.com ([135.71.62.10])
	by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g03MQAW02638
	for <megaco@ietf.org>; Thu, 3 Jan 2002 17:26:10 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh1i.attrh.att.com (5.5.029)
        id 3C0BA3A500180EDF; Thu, 3 Jan 2002 17:25:13 -0500
content-class: urn:content-classes:message
Subject: RE: [Megaco] Inter-MGC Communication
Date: Thu, 3 Jan 2002 17:25:12 -0500
Message-ID: <62DA45D4963FA747BA1B253E266760F9FF5509@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [Megaco] Inter-MGC Communication
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Index: AcGUopzn/8dcYQCSEdajbgCQJ60IGQAAGhNw
From: "Roy, Radhika R, ALCTA" <rrroy@att.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>,
        "asrar ashraf" <asrar@enabtech.com>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA22711
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



-----Original Message-----
From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: Thursday, January 03, 2002 5:02 PM
To: Roy, Radhika R, ALCTA; Kevin Boyle; asrar ashraf; megaco@ietf.org
Subject: RE: [Megaco] Inter-MGC Communication


> [RRR] However, there may be a dependency directly or 
> indirectly in communications between the MGC and MG and vice 
> versa based on what MGCs do among themselves using other 
> protocols (e.g., H.323, SIP). For example, the implications 
> of QOS and other attributes.

I don't think there is anything like it.  I believe there was a
concern raised about H.450 video events; they would be hard
to field at the MGC.  

[RRR] It is nice to know someone did some analysis or testing. This is what is needed to come out for interoperable implementations. As long as we all agree that it works and interoperates, we are done. (Still it appears that there may be some issues.)

Because Megaco is master/slave, the MGC
tells the MG how to handle the QoS stuff. 

[RRR] I would suggest to look into some QOS contributions provided in MEGACO. It shows that there are some basic issues (e.g., policy) that need to be resolved for the base MEGACO protocol itself. Then the question comes whether we need to do anything extra when other protocols are used among the MGCs.

I don't think there is
any problem with SIP or BICC.

[RRR] May be you are right. So, as I explained earlier, if we all agree that things are interoperable in multi-protocol and multi-vendor environment, then we are done. (Are we all sure about this?)

[RRR} Last of all, let me provide a pointer. For example, Madhubabu has provided a "MEGACO Call Flows" I-D. There is no new standardization works. However, it shows how things can be implemented and if we all agree with these procedures and it provides a baseline for interoperable implementations (should any questions arise). The same is true for the SIP Call Flows or SIP services example. (Why can we not do the same MEGACO for inter-MGC communications where SIP, H.323, etc. are used?)

Brian


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



From megaco-admin@ietf.org  Fri Jan  4 00:31:41 2002
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 AAA19891
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 00:31:41 -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 AAA01341;
	Fri, 4 Jan 2002 00:24:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA01313
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 00:24:00 -0500 (EST)
Received: from blaze.hcltech.com (IDENT:root@[203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19704
	for <megaco@ietf.org>; Fri, 4 Jan 2002 00:23:57 -0500 (EST)
Received: from suryapc (narendran [192.168.201.25])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id KAA18638
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:55:23 +0530
Message-ID: <001b01c194df$bf3a4750$19c9a8c0@suryapc>
From: "Surya Kumar IVG" <surya@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Fri, 4 Jan 2002 10:52:04 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0018_01C1950D.D8B9E720"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [Megaco] Fw: Handoff-query-reg
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

This is a multi-part message in MIME format.

------=_NextPart_000_0018_01C1950D.D8B9E720
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


----- Original Message -----=20
From: Madhu Babu Brahmanapally=20
To: 'Surya Kumar IVG'=20
Sent: Thursday, January 03, 2002 7:51 PM
Subject: RE: Handoff-query-reg


HI Surya,
I wrote the reply yesterday and thought I sent it to you, Sorry for =
that. Normally when a MG is controlled by a MGC pool, IMO all the MGCs =
inside that control pool will have similar transport mechanism. I mean =
if the Primary is using TCP, the new MGC contacted due to failover or =
handoff will also be using the same transport protocol. As you =
mentioned, the RFC doesn't throw any light on this. Whydont you send a =
mail to the mailing list for expected outcome in this situation. But IMO =
don't hardcode any transport protocol for this purpose(or assume any =
default). Hope that the mailing list replies may help us.

Regards
Madhubabu
  -----Original Message-----
  From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
  Sent: Thursday, January 03, 2002 2:02 AM
  To: Madhu Babu Brahmanapally
  Subject: Fw: Handoff-query-reg


  REPEAT
  ----- Original Message -----=20
  From: Surya Kumar IVG=20
  To: Madhu Babu Brahmanapally=20
  Sent: Wednesday, January 02, 2002 12:30 PM
  Subject: Handoff-query-reg


  Dear Madhubabu

  I have a query with regards to handoff mechanism.

  Considering that MGC P is going down for a while for maintenance and =
sends a handoff to MG and provides the ID of MGC to be contacted , while =
it goes down.

  The MG tries with a failover to that particular MGC and treats that as =
Primary for all practical purposes, if contacts successfully. Else it =
goes for list of designated secondary mGCs one after another , till it =
is successful.

  But , once handoff comes, MGC does not specify any transport  media on =
which MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not =
throw any details on that.

  Can we make it as default for MG to try on UDP and not successful, it =
can still try on TCP to the same MGC. ? If not successful , then MG =
moves to secondary MGC.

  regards
  surya

------=_NextPart_000_0018_01C1950D.D8B9E720
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dmadhubabu@kenetec.com =
href=3D"mailto:madhubabu@kenetec.com">Madhu Babu=20
Brahmanapally</A> </DIV>
<DIV><B>To:</B> <A title=3Dsurya@netlab.hcltech.com=20
href=3D"mailto:surya@netlab.hcltech.com">'Surya Kumar IVG'</A> </DIV>
<DIV><B>Sent:</B> Thursday, January 03, 2002 7:51 PM</DIV>
<DIV><B>Subject:</B> RE: Handoff-query-reg</DIV></DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>HI=20
Surya,</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
wrote the reply yesterday and thought I sent it to you, Sorry for=20
that.&nbsp;Normally when a MG is controlled by a MGC pool, IMO all the =
MGCs=20
inside that control pool will have similar transport mechanism. I mean =
if the=20
Primary is using TCP, the new MGC contacted due to failover or handoff =
will also=20
be using the same transport protocol. As you mentioned, the RFC doesn't =
throw=20
any light on this. Whydont you send a mail to the mailing list for =
expected=20
outcome in this situation. But IMO don't hardcode any transport protocol =
for=20
this purpose(or assume any default). Hope that the mailing list replies =
may help=20
us.</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2>Madhubabu</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Surya Kumar IVG=20
  [mailto:surya@netlab.hcltech.com]<BR><B>Sent:</B> Thursday, January =
03, 2002=20
  2:02 AM<BR><B>To:</B> Madhu Babu Brahmanapally<BR><B>Subject:</B> Fw:=20
  Handoff-query-reg<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>REPEAT</FONT></DIV>
  <DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
  <DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
  title=3Dsurya@netlab.hcltech.com =
href=3D"mailto:surya@netlab.hcltech.com">Surya=20
  Kumar IVG</A> </DIV>
  <DIV><B>To:</B> <A title=3Dmadhubabu@kenetec.com=20
  href=3D"mailto:madhubabu@kenetec.com">Madhu Babu Brahmanapally</A> =
</DIV>
  <DIV><B>Sent:</B> Wednesday, January 02, 2002 12:30 PM</DIV>
  <DIV><B>Subject:</B> Handoff-query-reg</DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Dear Madhubabu</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I have a query with regards to =
handoff=20
  mechanism.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Considering that MGC P is going down =
for a while=20
  for maintenance and sends a handoff to MG and provides the ID of MGC =
to be=20
  contacted , while it goes down.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>The MG tries with a failover to that =
particular=20
  MGC and treats that as Primary for all practical purposes, if contacts =

  successfully. Else it goes for list of designated secondary mGCs one =
after=20
  another , till it is successful.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>But , once handoff comes, MGC does =
not specify=20
  any transport&nbsp; media on which MG has to try to talk to MGC i.e =
UDp or=20
  TCP. The RFC also does not throw any details on that.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can we make it as default for MG to =
try on UDP=20
  and not successful, it can still try on TCP to the same MGC. ? If not=20
  successful , then MG moves to secondary MGC.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>regards</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2>surya</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0018_01C1950D.D8B9E720--


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


From daemon@optimus.ietf.org  Fri Jan  4 00:31:41 2002
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 AAA19903
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 00:31:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA01779
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 00:31:43 -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 AAA01341;
	Fri, 4 Jan 2002 00:24:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA01313
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 00:24:00 -0500 (EST)
Received: from blaze.hcltech.com (IDENT:root@[203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19704
	for <megaco@ietf.org>; Fri, 4 Jan 2002 00:23:57 -0500 (EST)
Received: from suryapc (narendran [192.168.201.25])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id KAA18638
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:55:23 +0530
Message-ID: <001b01c194df$bf3a4750$19c9a8c0@suryapc>
From: "Surya Kumar IVG" <surya@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Fri, 4 Jan 2002 10:52:04 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0018_01C1950D.D8B9E720"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [Megaco] Fw: Handoff-query-reg
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

This is a multi-part message in MIME format.

------=_NextPart_000_0018_01C1950D.D8B9E720
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


----- Original Message -----=20
From: Madhu Babu Brahmanapally=20
To: 'Surya Kumar IVG'=20
Sent: Thursday, January 03, 2002 7:51 PM
Subject: RE: Handoff-query-reg


HI Surya,
I wrote the reply yesterday and thought I sent it to you, Sorry for =
that. Normally when a MG is controlled by a MGC pool, IMO all the MGCs =
inside that control pool will have similar transport mechanism. I mean =
if the Primary is using TCP, the new MGC contacted due to failover or =
handoff will also be using the same transport protocol. As you =
mentioned, the RFC doesn't throw any light on this. Whydont you send a =
mail to the mailing list for expected outcome in this situation. But IMO =
don't hardcode any transport protocol for this purpose(or assume any =
default). Hope that the mailing list replies may help us.

Regards
Madhubabu
  -----Original Message-----
  From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
  Sent: Thursday, January 03, 2002 2:02 AM
  To: Madhu Babu Brahmanapally
  Subject: Fw: Handoff-query-reg


  REPEAT
  ----- Original Message -----=20
  From: Surya Kumar IVG=20
  To: Madhu Babu Brahmanapally=20
  Sent: Wednesday, January 02, 2002 12:30 PM
  Subject: Handoff-query-reg


  Dear Madhubabu

  I have a query with regards to handoff mechanism.

  Considering that MGC P is going down for a while for maintenance and =
sends a handoff to MG and provides the ID of MGC to be contacted , while =
it goes down.

  The MG tries with a failover to that particular MGC and treats that as =
Primary for all practical purposes, if contacts successfully. Else it =
goes for list of designated secondary mGCs one after another , till it =
is successful.

  But , once handoff comes, MGC does not specify any transport  media on =
which MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not =
throw any details on that.

  Can we make it as default for MG to try on UDP and not successful, it =
can still try on TCP to the same MGC. ? If not successful , then MG =
moves to secondary MGC.

  regards
  surya

------=_NextPart_000_0018_01C1950D.D8B9E720
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dmadhubabu@kenetec.com =
href=3D"mailto:madhubabu@kenetec.com">Madhu Babu=20
Brahmanapally</A> </DIV>
<DIV><B>To:</B> <A title=3Dsurya@netlab.hcltech.com=20
href=3D"mailto:surya@netlab.hcltech.com">'Surya Kumar IVG'</A> </DIV>
<DIV><B>Sent:</B> Thursday, January 03, 2002 7:51 PM</DIV>
<DIV><B>Subject:</B> RE: Handoff-query-reg</DIV></DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>HI=20
Surya,</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
wrote the reply yesterday and thought I sent it to you, Sorry for=20
that.&nbsp;Normally when a MG is controlled by a MGC pool, IMO all the =
MGCs=20
inside that control pool will have similar transport mechanism. I mean =
if the=20
Primary is using TCP, the new MGC contacted due to failover or handoff =
will also=20
be using the same transport protocol. As you mentioned, the RFC doesn't =
throw=20
any light on this. Whydont you send a mail to the mailing list for =
expected=20
outcome in this situation. But IMO don't hardcode any transport protocol =
for=20
this purpose(or assume any default). Hope that the mailing list replies =
may help=20
us.</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D066221614-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2>Madhubabu</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Surya Kumar IVG=20
  [mailto:surya@netlab.hcltech.com]<BR><B>Sent:</B> Thursday, January =
03, 2002=20
  2:02 AM<BR><B>To:</B> Madhu Babu Brahmanapally<BR><B>Subject:</B> Fw:=20
  Handoff-query-reg<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>REPEAT</FONT></DIV>
  <DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
  <DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
  title=3Dsurya@netlab.hcltech.com =
href=3D"mailto:surya@netlab.hcltech.com">Surya=20
  Kumar IVG</A> </DIV>
  <DIV><B>To:</B> <A title=3Dmadhubabu@kenetec.com=20
  href=3D"mailto:madhubabu@kenetec.com">Madhu Babu Brahmanapally</A> =
</DIV>
  <DIV><B>Sent:</B> Wednesday, January 02, 2002 12:30 PM</DIV>
  <DIV><B>Subject:</B> Handoff-query-reg</DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Dear Madhubabu</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I have a query with regards to =
handoff=20
  mechanism.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Considering that MGC P is going down =
for a while=20
  for maintenance and sends a handoff to MG and provides the ID of MGC =
to be=20
  contacted , while it goes down.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>The MG tries with a failover to that =
particular=20
  MGC and treats that as Primary for all practical purposes, if contacts =

  successfully. Else it goes for list of designated secondary mGCs one =
after=20
  another , till it is successful.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>But , once handoff comes, MGC does =
not specify=20
  any transport&nbsp; media on which MG has to try to talk to MGC i.e =
UDp or=20
  TCP. The RFC also does not throw any details on that.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can we make it as default for MG to =
try on UDP=20
  and not successful, it can still try on TCP to the same MGC. ? If not=20
  successful , then MG moves to secondary MGC.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>regards</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2>surya</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0018_01C1950D.D8B9E720--


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



From megaco-admin@ietf.org  Fri Jan  4 04:28:06 2002
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 EAA29719
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 04:28:06 -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 EAA15464;
	Fri, 4 Jan 2002 04:07:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA15434
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 04:06:59 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29554
	for <megaco@ietf.org>; Fri, 4 Jan 2002 04:06:53 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPEP7C00.AGX; Fri,
          4 Jan 2002 17:04:24 +0800 
Message-ID: <006601c194ff$4f117500$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C735@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Fri, 4 Jan 2002 17:08:00 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id EAA15435
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

Hi Brian,
Yes , It can know the resource using, But if you can't binding all channel with Termination, How can you know the 
status of left? idle or failed? 
We can configure the Max number of channel and we can know the exact number of them is busy, but we can't know the status of spares . We can bind a termination with one channel, and put into NULL context, Only in this case, when one channel failed, MGW report the status to MGC .
But this method , I think , is not a standard way .
Why not define a explicit way to reach the aim?

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, January 02, 2002 9:18 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> You audit the Media descriptor of all of the terminations
> to determine which terminations are employing the
> codec of interest.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, December 28, 2001 9:25 PM
> > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,  All
> > I agree with you on the concept of Audit capability and Audit 
> > Value . But in present protocol , How can we get the 500 busy 
> > through Audit value present defined, I can't find the 
> > parameter or package defined the case. 
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Saturday, December 29, 2001 12:54 AM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > Audit capabilities tells you what the capabilities of the system
> > > are.  Audit Value tells you what is currently "in use".
> > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > Capability, "500 busy" comes from Audit Value.
> > > 
> > > In general, the RFC is compliant with the requirements with one
> > > notable exception: many gateways are implemented with DSPs or other
> > > programmable resources. There is no good way to express capability
> > > with such resources.
> > > 
> > > If you have 1000 fixed G.711 channels, Audit Capability will reveal
> > > that.  If 500 channels are used, Audit Value will reveal that.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > Cc: megaco@ietf.org
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > HI Shashi,All,
> > > > Its true that Audit will help MGC to reconcile the 
> > > > inconsistency. But for
> > > > the specific scenario Zhang has pointed, How this resource 
> > > > information is
> > > > exchanged between the MG and the MGC. According to my 
> > > > knowledge there is no
> > > > parameter or anything as such to "quantitatively" identify 
> > > > G711 or any such
> > > > channel resource.
> > > > Regards
> > > > Madhubabu
> > > > 
> > > > -----Original Message-----
> > > > From: megaco-admin@ietf.org 
> > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > Shashi Kumar
> > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > To: zhangzhong
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > we have provision to audit the MG resource, which 
> > clearlty defined by
> > > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > > "reconcile inconsistencies between the MGC and the MG"
> > > > 
> > > > thanks,
> > > > shashi
> > > > 
> > > > 
> > > > > zhangzhong wrote:
> > > > >
> > > > > Hi :
> > > > > In the rfc 2805, there have a request to H.248:
> > > > >         Provide a mechanism to discover the current available
> > > > > resources
> > > > >         in the MG, where resources are dynamically consumed by
> > > > >         connections and the MGC cannot reasonably or 
> > reliably track
> > > > > the
> > > > >         consumption of such resources. It should also 
> > be possible to
> > > > >         discover resources currently in use, in order 
> > to reconcile
> > > > >         inconsistencies between the MGC and the MG.
> > > > >
> > > > > This means MGC can know the resource consume in the MGW , 
> > > > for example
> > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > busy , How can
> > > > > MGC know this through RFC3015?
> > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > >
> > > > > Thanks for the reply.
> > > > > Regards
> > > > > Zhangzhong
> > > > 
> > > > 
> > > > _______________________________________________
> > > > 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


From daemon@optimus.ietf.org  Fri Jan  4 04:28:06 2002
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 EAA29729
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 04:28:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA15818
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 04:28:08 -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 EAA15464;
	Fri, 4 Jan 2002 04:07:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA15434
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 04:06:59 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29554
	for <megaco@ietf.org>; Fri, 4 Jan 2002 04:06:53 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPEP7C00.AGX; Fri,
          4 Jan 2002 17:04:24 +0800 
Message-ID: <006601c194ff$4f117500$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C735@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Fri, 4 Jan 2002 17:08:00 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id EAA15435
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

Hi Brian,
Yes , It can know the resource using, But if you can't binding all channel with Termination, How can you know the 
status of left? idle or failed? 
We can configure the Max number of channel and we can know the exact number of them is busy, but we can't know the status of spares . We can bind a termination with one channel, and put into NULL context, Only in this case, when one channel failed, MGW report the status to MGC .
But this method , I think , is not a standard way .
Why not define a explicit way to reach the aim?

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, January 02, 2002 9:18 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> You audit the Media descriptor of all of the terminations
> to determine which terminations are employing the
> codec of interest.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, December 28, 2001 9:25 PM
> > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,  All
> > I agree with you on the concept of Audit capability and Audit 
> > Value . But in present protocol , How can we get the 500 busy 
> > through Audit value present defined, I can't find the 
> > parameter or package defined the case. 
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Saturday, December 29, 2001 12:54 AM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > Audit capabilities tells you what the capabilities of the system
> > > are.  Audit Value tells you what is currently "in use".
> > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > Capability, "500 busy" comes from Audit Value.
> > > 
> > > In general, the RFC is compliant with the requirements with one
> > > notable exception: many gateways are implemented with DSPs or other
> > > programmable resources. There is no good way to express capability
> > > with such resources.
> > > 
> > > If you have 1000 fixed G.711 channels, Audit Capability will reveal
> > > that.  If 500 channels are used, Audit Value will reveal that.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > Cc: megaco@ietf.org
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > HI Shashi,All,
> > > > Its true that Audit will help MGC to reconcile the 
> > > > inconsistency. But for
> > > > the specific scenario Zhang has pointed, How this resource 
> > > > information is
> > > > exchanged between the MG and the MGC. According to my 
> > > > knowledge there is no
> > > > parameter or anything as such to "quantitatively" identify 
> > > > G711 or any such
> > > > channel resource.
> > > > Regards
> > > > Madhubabu
> > > > 
> > > > -----Original Message-----
> > > > From: megaco-admin@ietf.org 
> > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > Shashi Kumar
> > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > To: zhangzhong
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > we have provision to audit the MG resource, which 
> > clearlty defined by
> > > > Megaco/H.248. By means of Auduting the MG resources we can always
> > > > "reconcile inconsistencies between the MGC and the MG"
> > > > 
> > > > thanks,
> > > > shashi
> > > > 
> > > > 
> > > > > zhangzhong wrote:
> > > > >
> > > > > Hi :
> > > > > In the rfc 2805, there have a request to H.248:
> > > > >         Provide a mechanism to discover the current available
> > > > > resources
> > > > >         in the MG, where resources are dynamically consumed by
> > > > >         connections and the MGC cannot reasonably or 
> > reliably track
> > > > > the
> > > > >         consumption of such resources. It should also 
> > be possible to
> > > > >         discover resources currently in use, in order 
> > to reconcile
> > > > >         inconsistencies between the MGC and the MG.
> > > > >
> > > > > This means MGC can know the resource consume in the MGW , 
> > > > for example
> > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > busy , How can
> > > > > MGC know this through RFC3015?
> > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > >
> > > > > Thanks for the reply.
> > > > > Regards
> > > > > Zhangzhong
> > > > 
> > > > 
> > > > _______________________________________________
> > > > 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



From megaco-admin@ietf.org  Fri Jan  4 08:26:38 2002
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 IAA01629
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 08:26:38 -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 IAA21203;
	Fri, 4 Jan 2002 08:14:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21174
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 08:14:32 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01435
	for <megaco@ietf.org>; Fri, 4 Jan 2002 08:14:31 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA26746;
	Fri, 4 Jan 2002 08:13:59 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA26419;
	Fri, 4 Jan 2002 08:14:00 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FRQHN>; Fri, 4 Jan 2002 08:13:59 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Fri, 4 Jan 2002 08:13:59 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Because the general problem is very complex, and no one has
proposed a general solution that seems likely to cover most
cases.

As an example, many systems are implemented with DSPs.  These
systems have very complex interaction between how many codecs
of different types can be in use simultaneously.  A system might,
for example, support 16 channels of G.729, 32 channels of G.711
and 32 channels of G.165 echo cancel with 64 ms tails, but
not simultaneously.  It may be that if you have one channel of
G.729, then you can support another 27 channels of G.711, and
if you have any G.729, then the longest tail is reduced.
This is because there are actually several variables at work -
DSP MIPs, and memory capacity, and the interaction between those
variables is complex.  I once discussed having a language which
allowed you to express this kind of thing, but it was too complex
for most people to deal with.  Then you add spares issues and
things get even more complex.

The other side of this issue is that the MGC can ask for resources
on the MG, and the MG can fail if there are no more resources.
This can be done in a way that lets the MGC either try to reroute
the call, or supply the appropriate error message to the caller.
That is why we didn't worry more about this known limitation.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 4:08 AM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian,
> Yes , It can know the resource using, But if you can't 
> binding all channel with Termination, How can you know the 
> status of left? idle or failed? 
> We can configure the Max number of channel and we can know 
> the exact number of them is busy, but we can't know the 
> status of spares . We can bind a termination with one 
> channel, and put into NULL context, Only in this case, when 
> one channel failed, MGW report the status to MGC .
> But this method , I think , is not a standard way .
> Why not define a explicit way to reach the aim?
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, January 02, 2002 9:18 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > You audit the Media descriptor of all of the terminations
> > to determine which terminations are employing the
> > codec of interest.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, December 28, 2001 9:25 PM
> > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,  All
> > > I agree with you on the concept of Audit capability and Audit 
> > > Value . But in present protocol , How can we get the 500 busy 
> > > through Audit value present defined, I can't find the 
> > > parameter or package defined the case. 
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Saturday, December 29, 2001 12:54 AM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > Audit capabilities tells you what the capabilities of the system
> > > > are.  Audit Value tells you what is currently "in use".
> > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > Capability, "500 busy" comes from Audit Value.
> > > > 
> > > > In general, the RFC is compliant with the requirements with one
> > > > notable exception: many gateways are implemented with 
> DSPs or other
> > > > programmable resources. There is no good way to express 
> capability
> > > > with such resources.
> > > > 
> > > > If you have 1000 fixed G.711 channels, Audit Capability 
> will reveal
> > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > HI Shashi,All,
> > > > > Its true that Audit will help MGC to reconcile the 
> > > > > inconsistency. But for
> > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > information is
> > > > > exchanged between the MG and the MGC. According to my 
> > > > > knowledge there is no
> > > > > parameter or anything as such to "quantitatively" identify 
> > > > > G711 or any such
> > > > > channel resource.
> > > > > Regards
> > > > > Madhubabu
> > > > > 
> > > > > -----Original Message-----
> > > > > From: megaco-admin@ietf.org 
> > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > Shashi Kumar
> > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > To: zhangzhong
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > we have provision to audit the MG resource, which 
> > > clearlty defined by
> > > > > Megaco/H.248. By means of Auduting the MG resources 
> we can always
> > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > 
> > > > > thanks,
> > > > > shashi
> > > > > 
> > > > > 
> > > > > > zhangzhong wrote:
> > > > > >
> > > > > > Hi :
> > > > > > In the rfc 2805, there have a request to H.248:
> > > > > >         Provide a mechanism to discover the current 
> available
> > > > > > resources
> > > > > >         in the MG, where resources are dynamically 
> consumed by
> > > > > >         connections and the MGC cannot reasonably or 
> > > reliably track
> > > > > > the
> > > > > >         consumption of such resources. It should also 
> > > be possible to
> > > > > >         discover resources currently in use, in order 
> > > to reconcile
> > > > > >         inconsistencies between the MGC and the MG.
> > > > > >
> > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > for example
> > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > busy , How can
> > > > > > MGC know this through RFC3015?
> > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > >
> > > > > > Thanks for the reply.
> > > > > > Regards
> > > > > > Zhangzhong
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > 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


From daemon@optimus.ietf.org  Fri Jan  4 08:26:38 2002
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 IAA01638
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 08:26:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA21413
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 08:26:39 -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 IAA21203;
	Fri, 4 Jan 2002 08:14:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21174
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 08:14:32 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01435
	for <megaco@ietf.org>; Fri, 4 Jan 2002 08:14:31 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA26746;
	Fri, 4 Jan 2002 08:13:59 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA26419;
	Fri, 4 Jan 2002 08:14:00 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FRQHN>; Fri, 4 Jan 2002 08:13:59 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Fri, 4 Jan 2002 08:13:59 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Because the general problem is very complex, and no one has
proposed a general solution that seems likely to cover most
cases.

As an example, many systems are implemented with DSPs.  These
systems have very complex interaction between how many codecs
of different types can be in use simultaneously.  A system might,
for example, support 16 channels of G.729, 32 channels of G.711
and 32 channels of G.165 echo cancel with 64 ms tails, but
not simultaneously.  It may be that if you have one channel of
G.729, then you can support another 27 channels of G.711, and
if you have any G.729, then the longest tail is reduced.
This is because there are actually several variables at work -
DSP MIPs, and memory capacity, and the interaction between those
variables is complex.  I once discussed having a language which
allowed you to express this kind of thing, but it was too complex
for most people to deal with.  Then you add spares issues and
things get even more complex.

The other side of this issue is that the MGC can ask for resources
on the MG, and the MG can fail if there are no more resources.
This can be done in a way that lets the MGC either try to reroute
the call, or supply the appropriate error message to the caller.
That is why we didn't worry more about this known limitation.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 4:08 AM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian,
> Yes , It can know the resource using, But if you can't 
> binding all channel with Termination, How can you know the 
> status of left? idle or failed? 
> We can configure the Max number of channel and we can know 
> the exact number of them is busy, but we can't know the 
> status of spares . We can bind a termination with one 
> channel, and put into NULL context, Only in this case, when 
> one channel failed, MGW report the status to MGC .
> But this method , I think , is not a standard way .
> Why not define a explicit way to reach the aim?
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, January 02, 2002 9:18 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > You audit the Media descriptor of all of the terminations
> > to determine which terminations are employing the
> > codec of interest.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, December 28, 2001 9:25 PM
> > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,  All
> > > I agree with you on the concept of Audit capability and Audit 
> > > Value . But in present protocol , How can we get the 500 busy 
> > > through Audit value present defined, I can't find the 
> > > parameter or package defined the case. 
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Saturday, December 29, 2001 12:54 AM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > Audit capabilities tells you what the capabilities of the system
> > > > are.  Audit Value tells you what is currently "in use".
> > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > Capability, "500 busy" comes from Audit Value.
> > > > 
> > > > In general, the RFC is compliant with the requirements with one
> > > > notable exception: many gateways are implemented with 
> DSPs or other
> > > > programmable resources. There is no good way to express 
> capability
> > > > with such resources.
> > > > 
> > > > If you have 1000 fixed G.711 channels, Audit Capability 
> will reveal
> > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > HI Shashi,All,
> > > > > Its true that Audit will help MGC to reconcile the 
> > > > > inconsistency. But for
> > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > information is
> > > > > exchanged between the MG and the MGC. According to my 
> > > > > knowledge there is no
> > > > > parameter or anything as such to "quantitatively" identify 
> > > > > G711 or any such
> > > > > channel resource.
> > > > > Regards
> > > > > Madhubabu
> > > > > 
> > > > > -----Original Message-----
> > > > > From: megaco-admin@ietf.org 
> > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > Shashi Kumar
> > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > To: zhangzhong
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > we have provision to audit the MG resource, which 
> > > clearlty defined by
> > > > > Megaco/H.248. By means of Auduting the MG resources 
> we can always
> > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > 
> > > > > thanks,
> > > > > shashi
> > > > > 
> > > > > 
> > > > > > zhangzhong wrote:
> > > > > >
> > > > > > Hi :
> > > > > > In the rfc 2805, there have a request to H.248:
> > > > > >         Provide a mechanism to discover the current 
> available
> > > > > > resources
> > > > > >         in the MG, where resources are dynamically 
> consumed by
> > > > > >         connections and the MGC cannot reasonably or 
> > > reliably track
> > > > > > the
> > > > > >         consumption of such resources. It should also 
> > > be possible to
> > > > > >         discover resources currently in use, in order 
> > > to reconcile
> > > > > >         inconsistencies between the MGC and the MG.
> > > > > >
> > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > for example
> > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > busy , How can
> > > > > > MGC know this through RFC3015?
> > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > >
> > > > > > Thanks for the reply.
> > > > > > Regards
> > > > > > Zhangzhong
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > 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



From megaco-admin@ietf.org  Fri Jan  4 10:28:29 2002
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 KAA05399
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 10:28:25 -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 KAA24315;
	Fri, 4 Jan 2002 10:04:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24284
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:04:55 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04718
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:04:52 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001632783@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Fri, 04 Jan 2002 20:06:45 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g04EKu705918;
	Fri, 4 Jan 2002 19:50:56 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Subject:  [Megaco] Use of COMMANDS without a event notification
Date: Fri, 4 Jan 2002 19:51:46 +0530
Message-Id: <001601c1952b$24bbbbe0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

There will be no problem in adding Physical terminations.

Can I add Ephermeral terminations in the same way, that is, can I
use "Add $" (without any event from Trunking Gateway) from the
MGC to Trunking Gateway.

Thanks,
Sudhir


-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 22, 2001 12:14 AM
To: ranabk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Use of COMMANDS without a event notification


Hi Rana,
Even without the event occurrence, the MGC can use ADD, SUBTRACT and MOVE
commands. This is not protocol error. In case of Trunking gateways, there
may not be any user events at all. The trunks are just added and subtracted.
Hope this helps.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
ranabk
Sent: Friday, December 21, 2001 11:02 AM
To: megaco@ietf.org
Subject: [Megaco] Use of COMMANDS without a event notification


Assume that I am testing MG. Assume that there is no call  generator which
generates call
to MG and hence events . If I use ADD , SUBTRACT , MOVE commands from my
tester to MG
without any event from MG will it return a protocl error from MG .

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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


From daemon@optimus.ietf.org  Fri Jan  4 10:28:30 2002
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 KAA05410
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 10:28:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA25001
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 10:28:32 -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 KAA24315;
	Fri, 4 Jan 2002 10:04:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24284
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:04:55 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04718
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:04:52 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001632783@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Fri, 04 Jan 2002 20:06:45 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g04EKu705918;
	Fri, 4 Jan 2002 19:50:56 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Subject:  [Megaco] Use of COMMANDS without a event notification
Date: Fri, 4 Jan 2002 19:51:46 +0530
Message-Id: <001601c1952b$24bbbbe0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

There will be no problem in adding Physical terminations.

Can I add Ephermeral terminations in the same way, that is, can I
use "Add $" (without any event from Trunking Gateway) from the
MGC to Trunking Gateway.

Thanks,
Sudhir


-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 22, 2001 12:14 AM
To: ranabk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Use of COMMANDS without a event notification


Hi Rana,
Even without the event occurrence, the MGC can use ADD, SUBTRACT and MOVE
commands. This is not protocol error. In case of Trunking gateways, there
may not be any user events at all. The trunks are just added and subtracted.
Hope this helps.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
ranabk
Sent: Friday, December 21, 2001 11:02 AM
To: megaco@ietf.org
Subject: [Megaco] Use of COMMANDS without a event notification


Assume that I am testing MG. Assume that there is no call  generator which
generates call
to MG and hence events . If I use ADD , SUBTRACT , MOVE commands from my
tester to MG
without any event from MG will it return a protocl error from MG .

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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



From megaco-admin@ietf.org  Fri Jan  4 10:35:57 2002
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 KAA05774
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 10:35:57 -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 KAA24969;
	Fri, 4 Jan 2002 10:27:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24940
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:27:40 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05380
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:27:38 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFP09218;
	Fri, 4 Jan 2002 10:27:07 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <sudhirk@future.futsoft.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of COMMANDS without a event notification
Date: Fri, 4 Jan 2002 10:25:39 -0500
Message-ID: <03dc01c19534$11182e80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <001601c1952b$24bbbbe0$3a07020a@future.futsoft.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Sudhir,
Yes, But in case of Ephemeral termination "creation", the MGC needs to
specify those descriptors which enables the MG to identify it as ephemeral
termination. (probably using the local/remote descriptors).
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Sudhir Kumar Appana
Sent: Friday, January 04, 2002 9:22 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Use of COMMANDS without a event notification


Hi,

There will be no problem in adding Physical terminations.

Can I add Ephermeral terminations in the same way, that is, can I
use "Add $" (without any event from Trunking Gateway) from the
MGC to Trunking Gateway.

Thanks,
Sudhir


-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 22, 2001 12:14 AM
To: ranabk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Use of COMMANDS without a event notification


Hi Rana,
Even without the event occurrence, the MGC can use ADD, SUBTRACT and MOVE
commands. This is not protocol error. In case of Trunking gateways, there
may not be any user events at all. The trunks are just added and subtracted.
Hope this helps.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
ranabk
Sent: Friday, December 21, 2001 11:02 AM
To: megaco@ietf.org
Subject: [Megaco] Use of COMMANDS without a event notification


Assume that I am testing MG. Assume that there is no call  generator which
generates call
to MG and hence events . If I use ADD , SUBTRACT , MOVE commands from my
tester to MG
without any event from MG will it return a protocl error from MG .

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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


From daemon@optimus.ietf.org  Fri Jan  4 10:35:57 2002
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 KAA05784
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 10:35:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA25640
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 10:35:59 -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 KAA24969;
	Fri, 4 Jan 2002 10:27:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24940
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:27:40 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05380
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:27:38 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFP09218;
	Fri, 4 Jan 2002 10:27:07 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <sudhirk@future.futsoft.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of COMMANDS without a event notification
Date: Fri, 4 Jan 2002 10:25:39 -0500
Message-ID: <03dc01c19534$11182e80$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <001601c1952b$24bbbbe0$3a07020a@future.futsoft.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Sudhir,
Yes, But in case of Ephemeral termination "creation", the MGC needs to
specify those descriptors which enables the MG to identify it as ephemeral
termination. (probably using the local/remote descriptors).
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Sudhir Kumar Appana
Sent: Friday, January 04, 2002 9:22 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Use of COMMANDS without a event notification


Hi,

There will be no problem in adding Physical terminations.

Can I add Ephermeral terminations in the same way, that is, can I
use "Add $" (without any event from Trunking Gateway) from the
MGC to Trunking Gateway.

Thanks,
Sudhir


-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Saturday, December 22, 2001 12:14 AM
To: ranabk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Use of COMMANDS without a event notification


Hi Rana,
Even without the event occurrence, the MGC can use ADD, SUBTRACT and MOVE
commands. This is not protocol error. In case of Trunking gateways, there
may not be any user events at all. The trunks are just added and subtracted.
Hope this helps.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
ranabk
Sent: Friday, December 21, 2001 11:02 AM
To: megaco@ietf.org
Subject: [Megaco] Use of COMMANDS without a event notification


Assume that I am testing MG. Assume that there is no call  generator which
generates call
to MG and hence events . If I use ADD , SUBTRACT , MOVE commands from my
tester to MG
without any event from MG will it return a protocl error from MG .

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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



From megaco-admin@ietf.org  Fri Jan  4 11:07:00 2002
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 LAA07079
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 11:07:00 -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 KAA26159;
	Fri, 4 Jan 2002 10:58:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26068
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:58:31 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06744
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:58:28 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04FvxA08399;
	Fri, 4 Jan 2002 10:57:59 -0500 (EST)
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 g04Fvwj23054;
	Fri, 4 Jan 2002 10:57:58 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPS2W5>; Fri, 4 Jan 2002 10:56:21 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Usha Iyer'" <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 10:56:32 -0500 
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

I think we made a mistake when we added this IG item.  It will block us from
using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
below.  If other people feel the same way, we may want to modify the wording
to handle that case.

The same draft also provides a capability to indicate synchronization
dependencies between media streams.  Megaco will be unable to use this.
Back when we put the protocol together, I thought we would need something to
show which streams were related, but we chose to add a general requirement
for synchronization of streams emanating from the same context.  I think the
current work on MCU decomposition in SG 16 may come up with package-based
solutions for greater selectivity.

If ReserveGroup and ReserveValue are both true, the MG is expected to
reserve resources to cover every session description and, within each one,
every codec alternative offered.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 02, 2002 11:31 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
megaco@ietf.org
Subject: Re: [Megaco] Reserve Value and Reserve Group


Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Fri Jan  4 11:07:05 2002
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 LAA07089
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 11:07:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA26638
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 11:07:03 -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 KAA26159;
	Fri, 4 Jan 2002 10:58:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26068
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 10:58:31 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06744
	for <megaco@ietf.org>; Fri, 4 Jan 2002 10:58:28 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04FvxA08399;
	Fri, 4 Jan 2002 10:57:59 -0500 (EST)
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 g04Fvwj23054;
	Fri, 4 Jan 2002 10:57:58 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPS2W5>; Fri, 4 Jan 2002 10:56:21 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Usha Iyer'" <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 10:56:32 -0500 
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

I think we made a mistake when we added this IG item.  It will block us from
using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
below.  If other people feel the same way, we may want to modify the wording
to handle that case.

The same draft also provides a capability to indicate synchronization
dependencies between media streams.  Megaco will be unable to use this.
Back when we put the protocol together, I thought we would need something to
show which streams were related, but we chose to add a general requirement
for synchronization of streams emanating from the same context.  I think the
current work on MCU decomposition in SG 16 may come up with package-based
solutions for greater selectivity.

If ReserveGroup and ReserveValue are both true, the MG is expected to
reserve resources to cover every session description and, within each one,
every codec alternative offered.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 02, 2002 11:31 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
megaco@ietf.org
Subject: Re: [Megaco] Reserve Value and Reserve Group


Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Fri Jan  4 11:44:44 2002
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 LAA08172
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 11:44:44 -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 LAA27626;
	Fri, 4 Jan 2002 11:32:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27597
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 11:32:28 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07837
	for <megaco@ietf.org>; Fri, 4 Jan 2002 11:32:20 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA17310;
	Fri, 4 Jan 2002 11:31:47 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA14123;
	Fri, 4 Jan 2002 11:31:47 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FR9L1>; Fri, 4 Jan 2002 11:31:46 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C78F@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Usha Iyer'"
	 <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 11:31:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

FID is a good thing, we should be able to use it.

Brian

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Friday, January 04, 2002 10:57 AM
> To: 'Usha Iyer'; sudhirk@future.futsoft.com; megaco@ietf.org
> Subject: RE: [Megaco] Reserve Value and Reserve Group
> 
> 
> I think we made a mistake when we added this IG item.  It 
> will block us from
> using the FID capability (draft-ietf-mmusic-fid-05.txt) that 
> I refer to
> below.  If other people feel the same way, we may want to 
> modify the wording
> to handle that case.
> 
> The same draft also provides a capability to indicate synchronization
> dependencies between media streams.  Megaco will be unable to 
> use this.
> Back when we put the protocol together, I thought we would 
> need something to
> show which streams were related, but we chose to add a 
> general requirement
> for synchronization of streams emanating from the same 
> context.  I think the
> current work on MCU decomposition in SG 16 may come up with 
> package-based
> solutions for greater selectivity.
> 
> If ReserveGroup and ReserveValue are both true, the MG is expected to
> reserve resources to cover every session description and, 
> within each one,
> every codec alternative offered.
> 
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 02, 2002 11:31 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
> megaco@ietf.org
> Subject: Re: [Megaco] Reserve Value and Reserve Group
> 
> 
> Hi Tom, All
> 
>     Section  6.98 of  AVD-2128 doc ( H248IG) states that
> --------------------
> A Stream Descriptor specifies a single bi-directional media 
> stream and so a
> single session description MUST NOT include more than one 
> media description
> ("m=" line).  Any additional media streams for a termination 
> must appear in
> distinct Stream Descriptors.
> -----------------------
>       Due to the above restriction ,you can't have multiple 
> "m=" lines in
> one session desc.
>        One ques:  How do u resolve ReserveValue = True and 
> also ReserveGroup
> = True
> 
> Regards
> Usha
> 
> ----- Original Message -----
> From: Tom-PT Taylor <taylor@nortelnetworks.com>
> To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
> Sent: Thursday, January 03, 2002 12:54 AM
> Subject: RE: [Megaco] Reserve Value and Reserve Group
> 
> 
> > A "property group" is the same as a session description.
> ReserveGroup=true
> > says to reserve resources to support all of the session descriptions
> > presented.
> >
> > ReserveValue=true definitely says that if multiple payload types are
> > presented on the same m= line, resources should be reserved 
> for all of
> them.
> > The grey area is if there are multiple m= lines within the 
> same session
> > description.  I propose the interpretation that 
> ReserveValue=true reserves
> > all resources within the same session description.
> >
> > I believe a further interpretation is needed as follows:
> >
> >   ReserveValue=true, ReserveGroup=false, multiple session 
> descriptions
> > presented:
> >   --------------
> >  means that the MG chooses its preferred session description, then
> reserves
> > all resources specified therein.
> >
> >   ReserveValue=false, ReserveGroup=true, multiple session 
> descriptions
> > presented:
> >   --------------
> >  means that the MG reserves resources for every session 
> description, but
> > within each session description, where any m= line presents 
> alternative
> > payload types, the MG chooses just one of the alternatives.
> >
> > I suspect it may be simpler to use the FID mechanism
> > (draft-ietf-mmusic-fid-05.txt) when it is finished.
> >
> > As for the missing s=, o=, and t= lines, RFC 3015 makes 
> them optional in
> the
> > MGC-to-MG direction.
> >
> > -----Original Message-----
> > From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> > Sent: Saturday, December 29, 2001 1:27 AM
> > To: megaco@ietf.org
> > Cc: Sudhir (E-mail)
> > Subject: [Megaco] Reserve Value and Reserve Group
> >
> >
> > Hi,
> > In the RFC 3015, following is given in section 7.1.8 (Local 
> and Remote
> > Descriptors):
> > "If ReserveGroup is true, the MG reserves the resources required to
> > support any of the requested property group alternatives that it can
> > currently support.  If ReserveValue is true, the MG reserves the
> > resources required to support any of the requested property value
> > alternatives that it can currently support."
> >
> > In the above statement, I want to know "what is property 
> group and what is
> > property value". Where can I get more information on this. 
> I referred
> > SDP RFC 2327, in that Session level Description and Media level
> Description
> > are differentiated. But I could not conclude from this.
> >
> > In RFC 3015 Appendix-A section-A.1.2 Step-12, Local 
> Descriptor defines two
> > Session level descriptions. Can anybody mail me how can I 
> interpret this,
> > as property groups or as property values. I will be happy, 
> if somebody
> > explains this with some example packets.
> >
> > One more doubt regarding SDP Paramters:
> > In SDP RFC 2327, it is given that following fields are mandatory:
> > For 'Session description':
> > v=  (protocol version)
> > o=  (owner/creator and session identifier).
> > s=  (session name)
> > For 'Time description':
> > t=  (time the session is active)
> >
> > For 'Media description':
> > m=  (media name and transport address)
> >
> > But in call flows given in RFC 3015 Appendix A and in 
> 'draft-madhu-megaco-
> > callflows-00.txt', I haven't found fields 'o=' and 's='. 
> Are this fields
> are
> > not required.
> >
> >
> > Thanks,
> > Sudhir
> >
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Fri Jan  4 11:44:45 2002
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 LAA08181
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 11:44:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA28240
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 11:44:47 -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 LAA27626;
	Fri, 4 Jan 2002 11:32:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27597
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 11:32:28 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07837
	for <megaco@ietf.org>; Fri, 4 Jan 2002 11:32:20 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA17310;
	Fri, 4 Jan 2002 11:31:47 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA14123;
	Fri, 4 Jan 2002 11:31:47 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FR9L1>; Fri, 4 Jan 2002 11:31:46 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C78F@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Usha Iyer'"
	 <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 11:31:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

FID is a good thing, we should be able to use it.

Brian

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Friday, January 04, 2002 10:57 AM
> To: 'Usha Iyer'; sudhirk@future.futsoft.com; megaco@ietf.org
> Subject: RE: [Megaco] Reserve Value and Reserve Group
> 
> 
> I think we made a mistake when we added this IG item.  It 
> will block us from
> using the FID capability (draft-ietf-mmusic-fid-05.txt) that 
> I refer to
> below.  If other people feel the same way, we may want to 
> modify the wording
> to handle that case.
> 
> The same draft also provides a capability to indicate synchronization
> dependencies between media streams.  Megaco will be unable to 
> use this.
> Back when we put the protocol together, I thought we would 
> need something to
> show which streams were related, but we chose to add a 
> general requirement
> for synchronization of streams emanating from the same 
> context.  I think the
> current work on MCU decomposition in SG 16 may come up with 
> package-based
> solutions for greater selectivity.
> 
> If ReserveGroup and ReserveValue are both true, the MG is expected to
> reserve resources to cover every session description and, 
> within each one,
> every codec alternative offered.
> 
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 02, 2002 11:31 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
> megaco@ietf.org
> Subject: Re: [Megaco] Reserve Value and Reserve Group
> 
> 
> Hi Tom, All
> 
>     Section  6.98 of  AVD-2128 doc ( H248IG) states that
> --------------------
> A Stream Descriptor specifies a single bi-directional media 
> stream and so a
> single session description MUST NOT include more than one 
> media description
> ("m=" line).  Any additional media streams for a termination 
> must appear in
> distinct Stream Descriptors.
> -----------------------
>       Due to the above restriction ,you can't have multiple 
> "m=" lines in
> one session desc.
>        One ques:  How do u resolve ReserveValue = True and 
> also ReserveGroup
> = True
> 
> Regards
> Usha
> 
> ----- Original Message -----
> From: Tom-PT Taylor <taylor@nortelnetworks.com>
> To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
> Sent: Thursday, January 03, 2002 12:54 AM
> Subject: RE: [Megaco] Reserve Value and Reserve Group
> 
> 
> > A "property group" is the same as a session description.
> ReserveGroup=true
> > says to reserve resources to support all of the session descriptions
> > presented.
> >
> > ReserveValue=true definitely says that if multiple payload types are
> > presented on the same m= line, resources should be reserved 
> for all of
> them.
> > The grey area is if there are multiple m= lines within the 
> same session
> > description.  I propose the interpretation that 
> ReserveValue=true reserves
> > all resources within the same session description.
> >
> > I believe a further interpretation is needed as follows:
> >
> >   ReserveValue=true, ReserveGroup=false, multiple session 
> descriptions
> > presented:
> >   --------------
> >  means that the MG chooses its preferred session description, then
> reserves
> > all resources specified therein.
> >
> >   ReserveValue=false, ReserveGroup=true, multiple session 
> descriptions
> > presented:
> >   --------------
> >  means that the MG reserves resources for every session 
> description, but
> > within each session description, where any m= line presents 
> alternative
> > payload types, the MG chooses just one of the alternatives.
> >
> > I suspect it may be simpler to use the FID mechanism
> > (draft-ietf-mmusic-fid-05.txt) when it is finished.
> >
> > As for the missing s=, o=, and t= lines, RFC 3015 makes 
> them optional in
> the
> > MGC-to-MG direction.
> >
> > -----Original Message-----
> > From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> > Sent: Saturday, December 29, 2001 1:27 AM
> > To: megaco@ietf.org
> > Cc: Sudhir (E-mail)
> > Subject: [Megaco] Reserve Value and Reserve Group
> >
> >
> > Hi,
> > In the RFC 3015, following is given in section 7.1.8 (Local 
> and Remote
> > Descriptors):
> > "If ReserveGroup is true, the MG reserves the resources required to
> > support any of the requested property group alternatives that it can
> > currently support.  If ReserveValue is true, the MG reserves the
> > resources required to support any of the requested property value
> > alternatives that it can currently support."
> >
> > In the above statement, I want to know "what is property 
> group and what is
> > property value". Where can I get more information on this. 
> I referred
> > SDP RFC 2327, in that Session level Description and Media level
> Description
> > are differentiated. But I could not conclude from this.
> >
> > In RFC 3015 Appendix-A section-A.1.2 Step-12, Local 
> Descriptor defines two
> > Session level descriptions. Can anybody mail me how can I 
> interpret this,
> > as property groups or as property values. I will be happy, 
> if somebody
> > explains this with some example packets.
> >
> > One more doubt regarding SDP Paramters:
> > In SDP RFC 2327, it is given that following fields are mandatory:
> > For 'Session description':
> > v=  (protocol version)
> > o=  (owner/creator and session identifier).
> > s=  (session name)
> > For 'Time description':
> > t=  (time the session is active)
> >
> > For 'Media description':
> > m=  (media name and transport address)
> >
> > But in call flows given in RFC 3015 Appendix A and in 
> 'draft-madhu-megaco-
> > callflows-00.txt', I haven't found fields 'o=' and 's='. 
> Are this fields
> are
> > not required.
> >
> >
> > Thanks,
> > Sudhir
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Fri Jan  4 12:40:03 2002
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 MAA09322
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 12:40:03 -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 MAA29581;
	Fri, 4 Jan 2002 12:23:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29550
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 12:23:53 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09010
	for <megaco@ietf.org>; Fri, 4 Jan 2002 12:23:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04HNJw29053;
	Fri, 4 Jan 2002 12:23:19 -0500 (EST)
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 g04HNIK27448;
	Fri, 4 Jan 2002 12:23:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPSKN6>; Fri, 4 Jan 2002 12:21:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Surya Kumar IVG'" <surya@netlab.hcltech.com>, megaco@ietf.org
Subject: RE: [Megaco] Fw: Handoff-query-reg
Date: Fri, 4 Jan 2002 12:21:52 -0500 
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

As I see it, this is a configuration issue -- don't look to the RFC for
guidance.


-----Original Message-----
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
Sent: Friday, January 04, 2002 12:22 AM
To: megaco@ietf.org
Subject: [Megaco] Fw: Handoff-query-reg



----- Original Message ----- 
From: Madhu Babu Brahmanapally 
To: 'Surya Kumar IVG' 
Sent: Thursday, January 03, 2002 7:51 PM
Subject: RE: Handoff-query-reg


HI Surya,
I wrote the reply yesterday and thought I sent it to you, Sorry for that.
Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that
control pool will have similar transport mechanism. I mean if the Primary is
using TCP, the new MGC contacted due to failover or handoff will also be
using the same transport protocol. As you mentioned, the RFC doesn't throw
any light on this. Whydont you send a mail to the mailing list for expected
outcome in this situation. But IMO don't hardcode any transport protocol for
this purpose(or assume any default). Hope that the mailing list replies may
help us.
 
Regards
Madhubabu
-----Original Message-----
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
Sent: Thursday, January 03, 2002 2:02 AM
To: Madhu Babu Brahmanapally
Subject: Fw: Handoff-query-reg


REPEAT
----- Original Message ----- 
From: Surya Kumar IVG 
To: Madhu Babu Brahmanapally 
Sent: Wednesday, January 02, 2002 12:30 PM
Subject: Handoff-query-reg


Dear Madhubabu
 
I have a query with regards to handoff mechanism.
 
Considering that MGC P is going down for a while for maintenance and sends a
handoff to MG and provides the ID of MGC to be contacted , while it goes
down.
 
The MG tries with a failover to that particular MGC and treats that as
Primary for all practical purposes, if contacts successfully. Else it goes
for list of designated secondary mGCs one after another , till it is
successful.
 
But , once handoff comes, MGC does not specify any transport  media on which
MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any
details on that.
 
Can we make it as default for MG to try on UDP and not successful, it can
still try on TCP to the same MGC. ? If not successful , then MG moves to
secondary MGC.
 
regards
surya

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


From daemon@optimus.ietf.org  Fri Jan  4 12:40:04 2002
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 MAA09334
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 12:40:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00773
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 12:40:05 -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 MAA29581;
	Fri, 4 Jan 2002 12:23:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29550
	for <megaco@optimus.ietf.org>; Fri, 4 Jan 2002 12:23:53 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09010
	for <megaco@ietf.org>; Fri, 4 Jan 2002 12:23:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04HNJw29053;
	Fri, 4 Jan 2002 12:23:19 -0500 (EST)
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 g04HNIK27448;
	Fri, 4 Jan 2002 12:23:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CFTPSKN6>; Fri, 4 Jan 2002 12:21:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADC9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Surya Kumar IVG'" <surya@netlab.hcltech.com>, megaco@ietf.org
Subject: RE: [Megaco] Fw: Handoff-query-reg
Date: Fri, 4 Jan 2002 12:21:52 -0500 
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

As I see it, this is a configuration issue -- don't look to the RFC for
guidance.


-----Original Message-----
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
Sent: Friday, January 04, 2002 12:22 AM
To: megaco@ietf.org
Subject: [Megaco] Fw: Handoff-query-reg



----- Original Message ----- 
From: Madhu Babu Brahmanapally 
To: 'Surya Kumar IVG' 
Sent: Thursday, January 03, 2002 7:51 PM
Subject: RE: Handoff-query-reg


HI Surya,
I wrote the reply yesterday and thought I sent it to you, Sorry for that.
Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that
control pool will have similar transport mechanism. I mean if the Primary is
using TCP, the new MGC contacted due to failover or handoff will also be
using the same transport protocol. As you mentioned, the RFC doesn't throw
any light on this. Whydont you send a mail to the mailing list for expected
outcome in this situation. But IMO don't hardcode any transport protocol for
this purpose(or assume any default). Hope that the mailing list replies may
help us.
 
Regards
Madhubabu
-----Original Message-----
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
Sent: Thursday, January 03, 2002 2:02 AM
To: Madhu Babu Brahmanapally
Subject: Fw: Handoff-query-reg


REPEAT
----- Original Message ----- 
From: Surya Kumar IVG 
To: Madhu Babu Brahmanapally 
Sent: Wednesday, January 02, 2002 12:30 PM
Subject: Handoff-query-reg


Dear Madhubabu
 
I have a query with regards to handoff mechanism.
 
Considering that MGC P is going down for a while for maintenance and sends a
handoff to MG and provides the ID of MGC to be contacted , while it goes
down.
 
The MG tries with a failover to that particular MGC and treats that as
Primary for all practical purposes, if contacts successfully. Else it goes
for list of designated secondary mGCs one after another , till it is
successful.
 
But , once handoff comes, MGC does not specify any transport  media on which
MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any
details on that.
 
Can we make it as default for MG to try on UDP and not successful, it can
still try on TCP to the same MGC. ? If not successful , then MG moves to
secondary MGC.
 
regards
surya

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



From megaco-admin@ietf.org  Fri Jan  4 15:00:57 2002
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 PAA12639
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 15:00:56 -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 OAA04513;
	Fri, 4 Jan 2002 14:39:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04483
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 14:39:45 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12212
	for <megaco@ietf.org>; Fri, 4 Jan 2002 14:39:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04JdCE14612;
	Fri, 4 Jan 2002 14:39:12 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04JdAc11186;
	Fri, 4 Jan 2002 14:39:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJYPPM2Y>; Fri, 4 Jan 2002 14:37:34 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADCB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: usha.iyer@wipro.com, sudhirk@future.futsoft.com, megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 14:37:38 -0500 
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

I've just remembered the other reason I wondered if it was a mistake to
restrict the number of m= lines in a stream.  However, this one may be more
debatable.  Suppose you want the ability to alternate between voice and T.38
FAX.  You can't put them both into the same m= line because they use
different transport (RTP vs. T.38).  Now, do we consider these to be
separate streams?  I think this is quite feasible, which makes my original
concern moot, but someone else may want to think it through.



-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Friday, January 04, 2002 10:57 AM
To: usha.iyer@wipro.com; sudhirk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group


I think we made a mistake when we added this IG item.  It will block us from
using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
below.  If other people feel the same way, we may want to modify the wording
to handle that case.

The same draft also provides a capability to indicate synchronization
dependencies between media streams.  Megaco will be unable to use this.
Back when we put the protocol together, I thought we would need something to
show which streams were related, but we chose to add a general requirement
for synchronization of streams emanating from the same context.  I think the
current work on MCU decomposition in SG 16 may come up with package-based
solutions for greater selectivity.

If ReserveGroup and ReserveValue are both true, the MG is expected to
reserve resources to cover every session description and, within each one,
every codec alternative offered.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 02, 2002 11:31 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
megaco@ietf.org
Subject: Re: [Megaco] Reserve Value and Reserve Group


Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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


From daemon@ns.ietf.org  Fri Jan  4 15:00:57 2002
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 PAA12649
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 15:00:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA05152
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 15:00: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 OAA04513;
	Fri, 4 Jan 2002 14:39:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04483
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 14:39:45 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12212
	for <megaco@ietf.org>; Fri, 4 Jan 2002 14:39:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04JdCE14612;
	Fri, 4 Jan 2002 14:39:12 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g04JdAc11186;
	Fri, 4 Jan 2002 14:39:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJYPPM2Y>; Fri, 4 Jan 2002 14:37:34 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADCB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: usha.iyer@wipro.com, sudhirk@future.futsoft.com, megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group
Date: Fri, 4 Jan 2002 14:37:38 -0500 
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

I've just remembered the other reason I wondered if it was a mistake to
restrict the number of m= lines in a stream.  However, this one may be more
debatable.  Suppose you want the ability to alternate between voice and T.38
FAX.  You can't put them both into the same m= line because they use
different transport (RTP vs. T.38).  Now, do we consider these to be
separate streams?  I think this is quite feasible, which makes my original
concern moot, but someone else may want to think it through.



-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Friday, January 04, 2002 10:57 AM
To: usha.iyer@wipro.com; sudhirk@future.futsoft.com; megaco@ietf.org
Subject: RE: [Megaco] Reserve Value and Reserve Group


I think we made a mistake when we added this IG item.  It will block us from
using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
below.  If other people feel the same way, we may want to modify the wording
to handle that case.

The same draft also provides a capability to indicate synchronization
dependencies between media streams.  Megaco will be unable to use this.
Back when we put the protocol together, I thought we would need something to
show which streams were related, but we chose to add a general requirement
for synchronization of streams emanating from the same context.  I think the
current work on MCU decomposition in SG 16 may come up with package-based
solutions for greater selectivity.

If ReserveGroup and ReserveValue are both true, the MG is expected to
reserve resources to cover every session description and, within each one,
every codec alternative offered.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 02, 2002 11:31 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
megaco@ietf.org
Subject: Re: [Megaco] Reserve Value and Reserve Group


Hi Tom, All

    Section  6.98 of  AVD-2128 doc ( H248IG) states that
--------------------
A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.
-----------------------
      Due to the above restriction ,you can't have multiple "m=" lines in
one session desc.
       One ques:  How do u resolve ReserveValue = True and also ReserveGroup
= True

Regards
Usha

----- Original Message -----
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
Sent: Thursday, January 03, 2002 12:54 AM
Subject: RE: [Megaco] Reserve Value and Reserve Group


> A "property group" is the same as a session description.
ReserveGroup=true
> says to reserve resources to support all of the session descriptions
> presented.
>
> ReserveValue=true definitely says that if multiple payload types are
> presented on the same m= line, resources should be reserved for all of
them.
> The grey area is if there are multiple m= lines within the same session
> description.  I propose the interpretation that ReserveValue=true reserves
> all resources within the same session description.
>
> I believe a further interpretation is needed as follows:
>
>   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> presented:
>   --------------
>  means that the MG chooses its preferred session description, then
reserves
> all resources specified therein.
>
>   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> presented:
>   --------------
>  means that the MG reserves resources for every session description, but
> within each session description, where any m= line presents alternative
> payload types, the MG chooses just one of the alternatives.
>
> I suspect it may be simpler to use the FID mechanism
> (draft-ietf-mmusic-fid-05.txt) when it is finished.
>
> As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
the
> MGC-to-MG direction.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Saturday, December 29, 2001 1:27 AM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] Reserve Value and Reserve Group
>
>
> Hi,
> In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> Descriptors):
> "If ReserveGroup is true, the MG reserves the resources required to
> support any of the requested property group alternatives that it can
> currently support.  If ReserveValue is true, the MG reserves the
> resources required to support any of the requested property value
> alternatives that it can currently support."
>
> In the above statement, I want to know "what is property group and what is
> property value". Where can I get more information on this. I referred
> SDP RFC 2327, in that Session level Description and Media level
Description
> are differentiated. But I could not conclude from this.
>
> In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> Session level descriptions. Can anybody mail me how can I interpret this,
> as property groups or as property values. I will be happy, if somebody
> explains this with some example packets.
>
> One more doubt regarding SDP Paramters:
> In SDP RFC 2327, it is given that following fields are mandatory:
> For 'Session description':
> v=  (protocol version)
> o=  (owner/creator and session identifier).
> s=  (session name)
> For 'Time description':
> t=  (time the session is active)
>
> For 'Media description':
> m=  (media name and transport address)
>
> But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
are
> not required.
>
>
> Thanks,
> Sudhir
>
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Fri Jan  4 22:49:49 2002
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 WAA20161
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 22:49:49 -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 WAA17078;
	Fri, 4 Jan 2002 22:38:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17049
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 22:38:56 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19937
	for <megaco@ietf.org>; Fri, 4 Jan 2002 22:38:50 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPG4OO00.151; Sat,
          5 Jan 2002 11:36:24 +0800 
Message-ID: <007801c1959a$a4e29720$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Sat, 5 Jan 2002 11:39:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id WAA17050
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

Hi Brian, all
Yes , It has problems about this. I think there should have some methods resolving them. 
And If we can't resolve these problems, There will introduce more difficulity of interworking between different company's product  and low the efficiency of network.
Problems:
MGW can reject the resource command from MGC, OK, It is no problems. But how MGC know the resource in this MGW is available again?  We can  setup a flag , and apply the request periodicly, when success, reset the flag, or start a timer , after the timer time out , reset the flag. etc.
All these methods will introcude much traffic between MGC and MGW. It is not good for the network resource management in the MGC. 

Regards
Zhangzhong



----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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


From daemon@ns.ietf.org  Fri Jan  4 22:49:50 2002
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 WAA20170
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 22:49:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA17335
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 22:49:51 -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 WAA17078;
	Fri, 4 Jan 2002 22:38:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17049
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 22:38:56 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19937
	for <megaco@ietf.org>; Fri, 4 Jan 2002 22:38:50 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPG4OO00.151; Sat,
          5 Jan 2002 11:36:24 +0800 
Message-ID: <007801c1959a$a4e29720$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Sat, 5 Jan 2002 11:39:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id WAA17050
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

Hi Brian, all
Yes , It has problems about this. I think there should have some methods resolving them. 
And If we can't resolve these problems, There will introduce more difficulity of interworking between different company's product  and low the efficiency of network.
Problems:
MGW can reject the resource command from MGC, OK, It is no problems. But how MGC know the resource in this MGW is available again?  We can  setup a flag , and apply the request periodicly, when success, reset the flag, or start a timer , after the timer time out , reset the flag. etc.
All these methods will introcude much traffic between MGC and MGW. It is not good for the network resource management in the MGC. 

Regards
Zhangzhong



----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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



From megaco-admin@ietf.org  Fri Jan  4 22:53:23 2002
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 WAA20223
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 22:53:23 -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 WAA17187;
	Fri, 4 Jan 2002 22:43:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17155
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 22:43:41 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20111
	for <megaco@ietf.org>; Fri, 4 Jan 2002 22:43:35 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPG4WL00.P5I; Sat,
          5 Jan 2002 11:41:09 +0800 
Message-ID: <008e01c1959b$4f161000$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Sat, 5 Jan 2002 11:44:42 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id WAA17156
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

Hi Brian, all
Ok, This problem will discuss later after having a way.
Another problems, could you answer to me , thanks .
Why not define a explicit way to apply the conference resource ?
How can MGW know when to activate conference resource ?
How can MGC know whether a MGW have the conference resource or not? If through configuration, How does MGC maintain the dynamic status of conference resource when it is bad or restrore?
If through the max number in one context , it is no problem in fixed network , but in mobiles cases, HandOver will introduce more than two termination into one context.

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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


From daemon@ns.ietf.org  Fri Jan  4 22:53:28 2002
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 WAA20232
	for <megaco-archive@odin.ietf.org>; Fri, 4 Jan 2002 22:53:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA17425
	for megaco-archive@odin.ietf.org; Fri, 4 Jan 2002 22:53:25 -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 WAA17187;
	Fri, 4 Jan 2002 22:43:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17155
	for <megaco@ns.ietf.org>; Fri, 4 Jan 2002 22:43:41 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20111
	for <megaco@ietf.org>; Fri, 4 Jan 2002 22:43:35 -0500 (EST)
Received: from z10528 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GPG4WL00.P5I; Sat,
          5 Jan 2002 11:41:09 +0800 
Message-ID: <008e01c1959b$4f161000$a9190b0a@huawei.com>
From: "zhangzhong" <zhangzhong@huawei.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: <megaco@ietf.org>
References: <313680C9A886D511A06000204840E1CF57C78B@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
Date: Sat, 5 Jan 2002 11:44:42 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id WAA17156
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

Hi Brian, all
Ok, This problem will discuss later after having a way.
Another problems, could you answer to me , thanks .
Why not define a explicit way to apply the conference resource ?
How can MGW know when to activate conference resource ?
How can MGC know whether a MGW have the conference resource or not? If through configuration, How does MGC maintain the dynamic status of conference resource when it is bad or restrore?
If through the max number in one context , it is no problem in fixed network , but in mobiles cases, HandOver will introduce more than two termination into one context.

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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



From megaco-admin@ietf.org  Sat Jan  5 01:36:18 2002
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 BAA23484
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 01:36:18 -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 BAA29563;
	Sat, 5 Jan 2002 01:23:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29536
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 01:23:34 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23375
	for <megaco@ietf.org>; Sat, 5 Jan 2002 01:23:32 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001635683@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Sat, 05 Jan 2002 12:07:37 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g056Mke05182
	for <megaco@ietf.org>; Sat, 5 Jan 2002 11:52:46 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Date: Sat, 5 Jan 2002 12:00:07 +0530
Message-Id: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Routing
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: 7bit

Hi,

I believe that routing is the responsibility of MGC, and MG plays no role in
routing.
In view of this I also believe that the wildcards(partial) used in the
selection of the terminations
is only to identify the terminations, and not for routing in the MG. That is
MG may not take routing
decisions on receipt of command like Add = $. MGC has figured out the
destination MG based on the
dialed digits and also the termination(or possible set of terminations in
the case of trunk group).

Is that valid?

gokul


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


From daemon@optimus.ietf.org  Sat Jan  5 01:36:19 2002
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 BAA23496
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 01:36:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA00076
	for megaco-archive@odin.ietf.org; Sat, 5 Jan 2002 01:36:20 -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 BAA29563;
	Sat, 5 Jan 2002 01:23:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29536
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 01:23:34 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23375
	for <megaco@ietf.org>; Sat, 5 Jan 2002 01:23:32 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001635683@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Sat, 05 Jan 2002 12:07:37 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g056Mke05182
	for <megaco@ietf.org>; Sat, 5 Jan 2002 11:52:46 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Date: Sat, 5 Jan 2002 12:00:07 +0530
Message-Id: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Routing
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: 7bit

Hi,

I believe that routing is the responsibility of MGC, and MG plays no role in
routing.
In view of this I also believe that the wildcards(partial) used in the
selection of the terminations
is only to identify the terminations, and not for routing in the MG. That is
MG may not take routing
decisions on receipt of command like Add = $. MGC has figured out the
destination MG based on the
dialed digits and also the termination(or possible set of terminations in
the case of trunk group).

Is that valid?

gokul


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



From megaco-admin@ietf.org  Sat Jan  5 03:28:02 2002
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 DAA02506
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 03:28:02 -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 DAA03014;
	Sat, 5 Jan 2002 03:20:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02987
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 03:20:09 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02334
	for <megaco@ietf.org>; Sat, 5 Jan 2002 03:20:06 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id AAA14575;
	Sat, 5 Jan 2002 00:20:07 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 5 Jan 2002 08:20:08 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id AAA19179;
	Sat, 5 Jan 2002 00:20:07 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id AAA06996;
	Sat, 5 Jan 2002 00:20:05 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id NAA24197;
	Sat, 5 Jan 2002 13:48:32 +0530 (IST)
Message-ID: <3C36B66D.3AA0A63D@lucent.com>
Date: Sat, 05 Jan 2002 13:46:45 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: gokulc@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Routing
References: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi gokul,

You are right, MGC takes the decision on which terminations to use on the MG based on the dial number and the routing information in
its database or other means. 

After the session is up, ofcourse routing of the data packets to the destination IP Address is done by MG, based on MG's routing
table. 

-Shambhu

gokulc wrote:
> 
> Hi,
> 
> I believe that routing is the responsibility of MGC, and MG plays no role in
> routing.
> In view of this I also believe that the wildcards(partial) used in the
> selection of the terminations
> is only to identify the terminations, and not for routing in the MG. That is
> MG may not take routing
> decisions on receipt of command like Add = $. MGC has figured out the
> destination MG based on the
> dialed digits and also the termination(or possible set of terminations in
> the case of trunk group).
> 
> Is that valid?
> 
> gokul
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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


From daemon@optimus.ietf.org  Sat Jan  5 03:28:03 2002
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 DAA02514
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 03:28:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA03146
	for megaco-archive@odin.ietf.org; Sat, 5 Jan 2002 03:28:05 -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 DAA03014;
	Sat, 5 Jan 2002 03:20:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02987
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 03:20:09 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02334
	for <megaco@ietf.org>; Sat, 5 Jan 2002 03:20:06 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id AAA14575;
	Sat, 5 Jan 2002 00:20:07 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 5 Jan 2002 08:20:08 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id AAA19179;
	Sat, 5 Jan 2002 00:20:07 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id AAA06996;
	Sat, 5 Jan 2002 00:20:05 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id NAA24197;
	Sat, 5 Jan 2002 13:48:32 +0530 (IST)
Message-ID: <3C36B66D.3AA0A63D@lucent.com>
Date: Sat, 05 Jan 2002 13:46:45 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: gokulc@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Routing
References: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi gokul,

You are right, MGC takes the decision on which terminations to use on the MG based on the dial number and the routing information in
its database or other means. 

After the session is up, ofcourse routing of the data packets to the destination IP Address is done by MG, based on MG's routing
table. 

-Shambhu

gokulc wrote:
> 
> Hi,
> 
> I believe that routing is the responsibility of MGC, and MG plays no role in
> routing.
> In view of this I also believe that the wildcards(partial) used in the
> selection of the terminations
> is only to identify the terminations, and not for routing in the MG. That is
> MG may not take routing
> decisions on receipt of command like Add = $. MGC has figured out the
> destination MG based on the
> dialed digits and also the termination(or possible set of terminations in
> the case of trunk group).
> 
> Is that valid?
> 
> gokul
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Sat Jan  5 04:04:34 2002
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 EAA02884
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 04:04:33 -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 DAA04011;
	Sat, 5 Jan 2002 03:50:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03923
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 03:50:25 -0500 (EST)
Received: from blaze.hcltech.com (IDENT:root@[203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02766
	for <megaco@ietf.org>; Sat, 5 Jan 2002 03:50:21 -0500 (EST)
Received: from netlab.hcltech.com (giri [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id OAA26972;
	Sat, 5 Jan 2002 14:21:44 +0530
Message-ID: <3C3567CD.C0456ADF@netlab.hcltech.com>
Date: Fri, 04 Jan 2002 13:59:01 +0530
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
Reply-To: girirs@netlab.hcltech.com
Organization: HCL Technologies Ltd, Chennai
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gokulc@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Routing
References: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Gokul,
	Here I assume, Routing you mean by is Call Routing.

gokulc wrote:
> 
> Hi,
> 
> I believe that routing is the responsibility of MGC, and MG plays no role in
> routing.
> In view of this I also believe that the wildcards(partial) used in the
> selection of the terminations
> is only to identify the terminations, and not for routing in the MG. That is
> MG may not take routing
> decisions on receipt of command like Add = $. MGC has figured out the
> destination MG based on the
> dialed digits and also the termination(or possible set of terminations in
> the case of trunk group).
> 
> Is that valid?

To my knowledge what you believe is true.
You can visualise MG as a dedicated device for Media Transfer between
terminations that are grouped under the term 'context'. And does this
grouping and ungrouping of terminations with instructions received from
an intelligent guy called MGC using the protocol MEGACO. It's upto the
MGC to decide which terminations to interconnect(group) to accomplish
the call.

> 
> gokul

Thanks,
Giri


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

-- 

Giri Rajasekhar Saladi
HCL Technologies Ltd.,
51, Jawaharlal Nehru Road 
Guindy Industrial Estate,
Ekkatuthangal,
Chennai - 600 097.


Phone Off : +91 44 233 4174 or +91 44 233 4181
Fax : +91 44 234 4256
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

-- 

Giri Rajasekhar Saladi
HCL Technologies Ltd.,
51, Jawaharlal Nehru Road 
Guindy Industrial Estate,
Ekkatuthangal,
Chennai - 600 097.


Phone Off : +91 44 233 4174 or +91 44 233 4181
Fax : +91 44 234 4256
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

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


From daemon@optimus.ietf.org  Sat Jan  5 04:04:34 2002
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 EAA02893
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 04:04:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA04640
	for megaco-archive@odin.ietf.org; Sat, 5 Jan 2002 04:04:36 -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 DAA04011;
	Sat, 5 Jan 2002 03:50:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03923
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 03:50:25 -0500 (EST)
Received: from blaze.hcltech.com (IDENT:root@[203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02766
	for <megaco@ietf.org>; Sat, 5 Jan 2002 03:50:21 -0500 (EST)
Received: from netlab.hcltech.com (giri [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id OAA26972;
	Sat, 5 Jan 2002 14:21:44 +0530
Message-ID: <3C3567CD.C0456ADF@netlab.hcltech.com>
Date: Fri, 04 Jan 2002 13:59:01 +0530
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
Reply-To: girirs@netlab.hcltech.com
Organization: HCL Technologies Ltd, Chennai
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gokulc@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Routing
References: <000801c195b2$6bbc3ba0$0803080a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Gokul,
	Here I assume, Routing you mean by is Call Routing.

gokulc wrote:
> 
> Hi,
> 
> I believe that routing is the responsibility of MGC, and MG plays no role in
> routing.
> In view of this I also believe that the wildcards(partial) used in the
> selection of the terminations
> is only to identify the terminations, and not for routing in the MG. That is
> MG may not take routing
> decisions on receipt of command like Add = $. MGC has figured out the
> destination MG based on the
> dialed digits and also the termination(or possible set of terminations in
> the case of trunk group).
> 
> Is that valid?

To my knowledge what you believe is true.
You can visualise MG as a dedicated device for Media Transfer between
terminations that are grouped under the term 'context'. And does this
grouping and ungrouping of terminations with instructions received from
an intelligent guy called MGC using the protocol MEGACO. It's upto the
MGC to decide which terminations to interconnect(group) to accomplish
the call.

> 
> gokul

Thanks,
Giri


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

-- 

Giri Rajasekhar Saladi
HCL Technologies Ltd.,
51, Jawaharlal Nehru Road 
Guindy Industrial Estate,
Ekkatuthangal,
Chennai - 600 097.


Phone Off : +91 44 233 4174 or +91 44 233 4181
Fax : +91 44 234 4256
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

-- 

Giri Rajasekhar Saladi
HCL Technologies Ltd.,
51, Jawaharlal Nehru Road 
Guindy Industrial Estate,
Ekkatuthangal,
Chennai - 600 097.


Phone Off : +91 44 233 4174 or +91 44 233 4181
Fax : +91 44 234 4256
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

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



From megaco-admin@ietf.org  Sat Jan  5 14:07:14 2002
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 OAA06595
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 14:07:14 -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 NAA17730;
	Sat, 5 Jan 2002 13:58:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17701
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 13:58:03 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06536
	for <megaco@ietf.org>; Sat, 5 Jan 2002 13:57:59 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id MAA24363
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:57:31 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g05IvVr18278
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:57:31 -0600 (CST)
Received: from cls11ws1.ssd.usa.alcatel.com (cls11ws1.ssd.usa.alcatel.com [143.209.200.151])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g05IulG27085
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:56:47 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls11ws1.ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g05IulS07517
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:56:47 -0600 (CST)
Message-ID: <3C374C6F.7837AFA6@alcatel.com>
Date: Sat, 05 Jan 2002 12:56:47 -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] Fw: Handoff-query-reg
References: <4D79C746863DD51197690002A52CDA000102ADC9@zcard0kc.ca.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------A1B445CE4A47464A709F6B00"
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


--------------A1B445CE4A47464A709F6B00
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom

Way back, I thought the Standard said that MGC has to support both - UDP/TCP
and MG
can support either.
Earlier attempt also tried to define 2 well know Megaco port for UDP and TCP
which turns out
to be unnecessary for the following reason.

Since MGC is the server, it listens on port 2944 (text encoding) or 2945
(binary encoding) for UDP or TCP.

If MG attempts a registration on UDP, then MGC uses UDP for that MG and same
goes for TCP.

Has this been changed in v1?

Thanks
Chuong


Tom-PT Taylor wrote:

> As I see it, this is a configuration issue -- don't look to the RFC for
> guidance.
>
> -----Original Message-----
> From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
> Sent: Friday, January 04, 2002 12:22 AM
> To: megaco@ietf.org
> Subject: [Megaco] Fw: Handoff-query-reg
>
> ----- Original Message -----
> From: Madhu Babu Brahmanapally
> To: 'Surya Kumar IVG'
> Sent: Thursday, January 03, 2002 7:51 PM
> Subject: RE: Handoff-query-reg
>
> HI Surya,
> I wrote the reply yesterday and thought I sent it to you, Sorry for that.
> Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that
> control pool will have similar transport mechanism. I mean if the Primary is
> using TCP, the new MGC contacted due to failover or handoff will also be
> using the same transport protocol. As you mentioned, the RFC doesn't throw
> any light on this. Whydont you send a mail to the mailing list for expected
> outcome in this situation. But IMO don't hardcode any transport protocol for
> this purpose(or assume any default). Hope that the mailing list replies may
> help us.
>
> Regards
> Madhubabu
> -----Original Message-----
> From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
> Sent: Thursday, January 03, 2002 2:02 AM
> To: Madhu Babu Brahmanapally
> Subject: Fw: Handoff-query-reg
>
> REPEAT
> ----- Original Message -----
> From: Surya Kumar IVG
> To: Madhu Babu Brahmanapally
> Sent: Wednesday, January 02, 2002 12:30 PM
> Subject: Handoff-query-reg
>
> Dear Madhubabu
>
> I have a query with regards to handoff mechanism.
>
> Considering that MGC P is going down for a while for maintenance and sends a
> handoff to MG and provides the ID of MGC to be contacted , while it goes
> down.
>
> The MG tries with a failover to that particular MGC and treats that as
> Primary for all practical purposes, if contacts successfully. Else it goes
> for list of designated secondary mGCs one after another , till it is
> successful.
>
> But , once handoff comes, MGC does not specify any transport  media on which
> MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any
> details on that.
>
> Can we make it as default for MG to try on UDP and not successful, it can
> still try on TCP to the same MGC. ? If not successful , then MG moves to
> secondary MGC.
>
> regards
> surya
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

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



--------------A1B445CE4A47464A709F6B00
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Tom
<p>Way back, I&nbsp;thought the Standard said that MGC&nbsp;has to support
both - UDP/TCP and MG
<br>can support either.
<br>Earlier attempt also tried to define 2 well know Megaco port for UDP&nbsp;and
TCP which turns out
<br>to be unnecessary for the following reason.
<p>Since MGC&nbsp;is the server, it listens on port 2944 (text encoding)
or 2945 (binary encoding) for UDP&nbsp;or TCP.
<p>If MG attempts a registration on UDP, then MGC&nbsp;uses UDP for that
MG and same goes for TCP.
<p>Has this been changed in v1?
<p>Thanks
<br>Chuong
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE=CITE>As I see it, this is a configuration issue -- don't
look to the RFC for
<br>guidance.
<p>-----Original Message-----
<br>From: Surya Kumar IVG [<a href="mailto:surya@netlab.hcltech.com">mailto:surya@netlab.hcltech.com</a>]
<br>Sent: Friday, January 04, 2002 12:22 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Fw: Handoff-query-reg
<p>----- Original Message -----
<br>From: Madhu Babu Brahmanapally
<br>To: 'Surya Kumar IVG'
<br>Sent: Thursday, January 03, 2002 7:51 PM
<br>Subject: RE: Handoff-query-reg
<p>HI Surya,
<br>I wrote the reply yesterday and thought I sent it to you, Sorry for
that.
<br>Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside
that
<br>control pool will have similar transport mechanism. I mean if the Primary
is
<br>using TCP, the new MGC contacted due to failover or handoff will also
be
<br>using the same transport protocol. As you mentioned, the RFC doesn't
throw
<br>any light on this. Whydont you send a mail to the mailing list for
expected
<br>outcome in this situation. But IMO don't hardcode any transport protocol
for
<br>this purpose(or assume any default). Hope that the mailing list replies
may
<br>help us.
<p>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: Surya Kumar IVG [<a href="mailto:surya@netlab.hcltech.com">mailto:surya@netlab.hcltech.com</a>]
<br>Sent: Thursday, January 03, 2002 2:02 AM
<br>To: Madhu Babu Brahmanapally
<br>Subject: Fw: Handoff-query-reg
<p>REPEAT
<br>----- Original Message -----
<br>From: Surya Kumar IVG
<br>To: Madhu Babu Brahmanapally
<br>Sent: Wednesday, January 02, 2002 12:30 PM
<br>Subject: Handoff-query-reg
<p>Dear Madhubabu
<p>I have a query with regards to handoff mechanism.
<p>Considering that MGC P is going down for a while for maintenance and
sends a
<br>handoff to MG and provides the ID of MGC to be contacted , while it
goes
<br>down.
<p>The MG tries with a failover to that particular MGC and treats that
as
<br>Primary for all practical purposes, if contacts successfully. Else
it goes
<br>for list of designated secondary mGCs one after another , till it is
<br>successful.
<p>But , once handoff comes, MGC does not specify any transport&nbsp; media
on which
<br>MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not
throw any
<br>details on that.
<p>Can we make it as default for MG to try on UDP and not successful, it
can
<br>still try on TCP to the same MGC. ? If not successful , then MG moves
to
<br>secondary MGC.
<p>regards
<br>surya
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------A1B445CE4A47464A709F6B00--


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


From daemon@optimus.ietf.org  Sat Jan  5 14:07:15 2002
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 OAA06604
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 14:07:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA18367
	for megaco-archive@odin.ietf.org; Sat, 5 Jan 2002 14:07: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 NAA17730;
	Sat, 5 Jan 2002 13:58:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17701
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 13:58:03 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06536
	for <megaco@ietf.org>; Sat, 5 Jan 2002 13:57:59 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id MAA24363
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:57:31 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g05IvVr18278
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:57:31 -0600 (CST)
Received: from cls11ws1.ssd.usa.alcatel.com (cls11ws1.ssd.usa.alcatel.com [143.209.200.151])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g05IulG27085
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:56:47 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls11ws1.ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g05IulS07517
	for <megaco@ietf.org>; Sat, 5 Jan 2002 12:56:47 -0600 (CST)
Message-ID: <3C374C6F.7837AFA6@alcatel.com>
Date: Sat, 05 Jan 2002 12:56:47 -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] Fw: Handoff-query-reg
References: <4D79C746863DD51197690002A52CDA000102ADC9@zcard0kc.ca.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------A1B445CE4A47464A709F6B00"
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


--------------A1B445CE4A47464A709F6B00
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom

Way back, I thought the Standard said that MGC has to support both - UDP/TCP
and MG
can support either.
Earlier attempt also tried to define 2 well know Megaco port for UDP and TCP
which turns out
to be unnecessary for the following reason.

Since MGC is the server, it listens on port 2944 (text encoding) or 2945
(binary encoding) for UDP or TCP.

If MG attempts a registration on UDP, then MGC uses UDP for that MG and same
goes for TCP.

Has this been changed in v1?

Thanks
Chuong


Tom-PT Taylor wrote:

> As I see it, this is a configuration issue -- don't look to the RFC for
> guidance.
>
> -----Original Message-----
> From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
> Sent: Friday, January 04, 2002 12:22 AM
> To: megaco@ietf.org
> Subject: [Megaco] Fw: Handoff-query-reg
>
> ----- Original Message -----
> From: Madhu Babu Brahmanapally
> To: 'Surya Kumar IVG'
> Sent: Thursday, January 03, 2002 7:51 PM
> Subject: RE: Handoff-query-reg
>
> HI Surya,
> I wrote the reply yesterday and thought I sent it to you, Sorry for that.
> Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that
> control pool will have similar transport mechanism. I mean if the Primary is
> using TCP, the new MGC contacted due to failover or handoff will also be
> using the same transport protocol. As you mentioned, the RFC doesn't throw
> any light on this. Whydont you send a mail to the mailing list for expected
> outcome in this situation. But IMO don't hardcode any transport protocol for
> this purpose(or assume any default). Hope that the mailing list replies may
> help us.
>
> Regards
> Madhubabu
> -----Original Message-----
> From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com]
> Sent: Thursday, January 03, 2002 2:02 AM
> To: Madhu Babu Brahmanapally
> Subject: Fw: Handoff-query-reg
>
> REPEAT
> ----- Original Message -----
> From: Surya Kumar IVG
> To: Madhu Babu Brahmanapally
> Sent: Wednesday, January 02, 2002 12:30 PM
> Subject: Handoff-query-reg
>
> Dear Madhubabu
>
> I have a query with regards to handoff mechanism.
>
> Considering that MGC P is going down for a while for maintenance and sends a
> handoff to MG and provides the ID of MGC to be contacted , while it goes
> down.
>
> The MG tries with a failover to that particular MGC and treats that as
> Primary for all practical purposes, if contacts successfully. Else it goes
> for list of designated secondary mGCs one after another , till it is
> successful.
>
> But , once handoff comes, MGC does not specify any transport  media on which
> MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any
> details on that.
>
> Can we make it as default for MG to try on UDP and not successful, it can
> still try on TCP to the same MGC. ? If not successful , then MG moves to
> secondary MGC.
>
> regards
> surya
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

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



--------------A1B445CE4A47464A709F6B00
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Tom
<p>Way back, I&nbsp;thought the Standard said that MGC&nbsp;has to support
both - UDP/TCP and MG
<br>can support either.
<br>Earlier attempt also tried to define 2 well know Megaco port for UDP&nbsp;and
TCP which turns out
<br>to be unnecessary for the following reason.
<p>Since MGC&nbsp;is the server, it listens on port 2944 (text encoding)
or 2945 (binary encoding) for UDP&nbsp;or TCP.
<p>If MG attempts a registration on UDP, then MGC&nbsp;uses UDP for that
MG and same goes for TCP.
<p>Has this been changed in v1?
<p>Thanks
<br>Chuong
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE=CITE>As I see it, this is a configuration issue -- don't
look to the RFC for
<br>guidance.
<p>-----Original Message-----
<br>From: Surya Kumar IVG [<a href="mailto:surya@netlab.hcltech.com">mailto:surya@netlab.hcltech.com</a>]
<br>Sent: Friday, January 04, 2002 12:22 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Fw: Handoff-query-reg
<p>----- Original Message -----
<br>From: Madhu Babu Brahmanapally
<br>To: 'Surya Kumar IVG'
<br>Sent: Thursday, January 03, 2002 7:51 PM
<br>Subject: RE: Handoff-query-reg
<p>HI Surya,
<br>I wrote the reply yesterday and thought I sent it to you, Sorry for
that.
<br>Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside
that
<br>control pool will have similar transport mechanism. I mean if the Primary
is
<br>using TCP, the new MGC contacted due to failover or handoff will also
be
<br>using the same transport protocol. As you mentioned, the RFC doesn't
throw
<br>any light on this. Whydont you send a mail to the mailing list for
expected
<br>outcome in this situation. But IMO don't hardcode any transport protocol
for
<br>this purpose(or assume any default). Hope that the mailing list replies
may
<br>help us.
<p>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: Surya Kumar IVG [<a href="mailto:surya@netlab.hcltech.com">mailto:surya@netlab.hcltech.com</a>]
<br>Sent: Thursday, January 03, 2002 2:02 AM
<br>To: Madhu Babu Brahmanapally
<br>Subject: Fw: Handoff-query-reg
<p>REPEAT
<br>----- Original Message -----
<br>From: Surya Kumar IVG
<br>To: Madhu Babu Brahmanapally
<br>Sent: Wednesday, January 02, 2002 12:30 PM
<br>Subject: Handoff-query-reg
<p>Dear Madhubabu
<p>I have a query with regards to handoff mechanism.
<p>Considering that MGC P is going down for a while for maintenance and
sends a
<br>handoff to MG and provides the ID of MGC to be contacted , while it
goes
<br>down.
<p>The MG tries with a failover to that particular MGC and treats that
as
<br>Primary for all practical purposes, if contacts successfully. Else
it goes
<br>for list of designated secondary mGCs one after another , till it is
<br>successful.
<p>But , once handoff comes, MGC does not specify any transport&nbsp; media
on which
<br>MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not
throw any
<br>details on that.
<p>Can we make it as default for MG to try on UDP and not successful, it
can
<br>still try on TCP to the same MGC. ? If not successful , then MG moves
to
<br>secondary MGC.
<p>regards
<br>surya
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------A1B445CE4A47464A709F6B00--


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



From megaco-admin@ietf.org  Sat Jan  5 19:28:09 2002
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 TAA08462
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 19:28:09 -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 TAA24801;
	Sat, 5 Jan 2002 19:01:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24770
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 19:01:06 -0500 (EST)
Received: from mail.nexverse.com ([65.195.29.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08356
	for <megaco@ietf.org>; Sat, 5 Jan 2002 19:01:03 -0500 (EST)
Received: by mail.nexverse.com with Internet Mail Service (5.5.2653.19)
	id <Y7VYQ0WL>; Sat, 5 Jan 2002 15:57:47 -0800
Message-ID: <9E388C880C1ED411AFE1009027E78725035654F9@mail.nexverse.com>
From: Seshagiri Rao <rsesh@nexverse.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Sat, 5 Jan 2002 15:57:46 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19644.C6257290"
Subject: [Megaco] Megaco Interoperability
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19644.C6257290
Content-Type: text/plain

All:

I would like to know if there is any reference design/test sequence for
Megaco stack implementation.
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh


------_=_NextPart_001_01C19644.C6257290
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Megaco Interoperability</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All:</FONT>
</P>

<P><FONT SIZE=3D2>I would like to know if there is any reference =
design/test sequence for Megaco stack implementation.</FONT>
<BR><FONT SIZE=3D2>I would also like to know if there is any =
forthcoming interop/bake-off event.&nbsp; </FONT>
<BR><FONT SIZE=3D2>How many of the current Megaco stack implementations =
support ABNF/Text encoding and how many support ASN.1/binary =
encoding?</FONT></P>

<P><FONT SIZE=3D2>Sesh</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19644.C6257290--

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


From daemon@optimus.ietf.org  Sat Jan  5 19:28:10 2002
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 TAA08477
	for <megaco-archive@odin.ietf.org>; Sat, 5 Jan 2002 19:28:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA25042
	for megaco-archive@odin.ietf.org; Sat, 5 Jan 2002 19:28:12 -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 TAA24801;
	Sat, 5 Jan 2002 19:01:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24770
	for <megaco@optimus.ietf.org>; Sat, 5 Jan 2002 19:01:06 -0500 (EST)
Received: from mail.nexverse.com ([65.195.29.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08356
	for <megaco@ietf.org>; Sat, 5 Jan 2002 19:01:03 -0500 (EST)
Received: by mail.nexverse.com with Internet Mail Service (5.5.2653.19)
	id <Y7VYQ0WL>; Sat, 5 Jan 2002 15:57:47 -0800
Message-ID: <9E388C880C1ED411AFE1009027E78725035654F9@mail.nexverse.com>
From: Seshagiri Rao <rsesh@nexverse.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Sat, 5 Jan 2002 15:57:46 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19644.C6257290"
Subject: [Megaco] Megaco Interoperability
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19644.C6257290
Content-Type: text/plain

All:

I would like to know if there is any reference design/test sequence for
Megaco stack implementation.
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh


------_=_NextPart_001_01C19644.C6257290
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Megaco Interoperability</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All:</FONT>
</P>

<P><FONT SIZE=3D2>I would like to know if there is any reference =
design/test sequence for Megaco stack implementation.</FONT>
<BR><FONT SIZE=3D2>I would also like to know if there is any =
forthcoming interop/bake-off event.&nbsp; </FONT>
<BR><FONT SIZE=3D2>How many of the current Megaco stack implementations =
support ABNF/Text encoding and how many support ASN.1/binary =
encoding?</FONT></P>

<P><FONT SIZE=3D2>Sesh</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19644.C6257290--

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



From megaco-admin@ietf.org  Mon Jan  7 07:27:36 2002
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 HAA13342
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 07:27:36 -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 HAA03338;
	Mon, 7 Jan 2002 07:12:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03307
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 07:12:29 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA13285
	for <megaco@ietf.org>; Mon, 7 Jan 2002 07:12:26 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Mon Jan 07 14:28:26 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FJ24>; Mon, 7 Jan 2002 14:03:00 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF017F8351@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Date: Mon, 7 Jan 2002 14:02:59 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19773.3FDD3760"
Subject: [Megaco] precise identification of an incoming call
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19773.3FDD3760
Content-Type: text/plain

In the example call flow given in RFC 3015 Appendix A, the incoming call to
the second subscriber begins with an ADD command from MGC to MG2 in step 14.
Is this the only way an incoming call can begin?  In other words, can the MG
assume the MGC will not send it any other commands related to an incoming
call before the ADD?


Raphael Tryster

------_=_NextPart_001_01C19773.3FDD3760
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>precise identification of an incoming call</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the example call flow given in RFC 30=
15 Appendix A, the incoming call to the second subscriber begins with an =
ADD command from MGC to MG2 in step 14.&nbsp; Is this the only way an inc=
oming call can begin?&nbsp; In other words, can the MG assume the MGC wil=
l not send it any other commands related to an incoming call before the A=
DD?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19773.3FDD3760--

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


From daemon@optimus.ietf.org  Mon Jan  7 07:27:36 2002
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 HAA13351
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 07:27:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA03518
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 07:27:38 -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 HAA03338;
	Mon, 7 Jan 2002 07:12:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03307
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 07:12:29 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA13285
	for <megaco@ietf.org>; Mon, 7 Jan 2002 07:12:26 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Mon Jan 07 14:28:26 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FJ24>; Mon, 7 Jan 2002 14:03:00 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF017F8351@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Date: Mon, 7 Jan 2002 14:02:59 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19773.3FDD3760"
Subject: [Megaco] precise identification of an incoming call
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19773.3FDD3760
Content-Type: text/plain

In the example call flow given in RFC 3015 Appendix A, the incoming call to
the second subscriber begins with an ADD command from MGC to MG2 in step 14.
Is this the only way an incoming call can begin?  In other words, can the MG
assume the MGC will not send it any other commands related to an incoming
call before the ADD?


Raphael Tryster

------_=_NextPart_001_01C19773.3FDD3760
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>precise identification of an incoming call</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the example call flow given in RFC 30=
15 Appendix A, the incoming call to the second subscriber begins with an =
ADD command from MGC to MG2 in step 14.&nbsp; Is this the only way an inc=
oming call can begin?&nbsp; In other words, can the MG assume the MGC wil=
l not send it any other commands related to an incoming call before the A=
DD?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19773.3FDD3760--

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



From megaco-admin@ietf.org  Mon Jan  7 08:21:47 2002
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 IAA14000
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 08:21:47 -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 IAA04697;
	Mon, 7 Jan 2002 08:13:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04666
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 08:13:16 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13856
	for <megaco@ietf.org>; Mon, 7 Jan 2002 08:13:13 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001644688@fsnt.future.futsoft.com>;
 Mon, 07 Jan 2002 18:57:18 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g07DCNe16104;
	Mon, 7 Jan 2002 18:42:23 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Cc: <madhubabu@kenetec.com>
Date: Mon, 7 Jan 2002 18:49:57 +0530
Message-Id: <001a01c1977e$01a74f20$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Use of Modem descriptor
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: 7bit

Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


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


From daemon@optimus.ietf.org  Mon Jan  7 08:21:48 2002
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 IAA14009
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 08:21:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA04767
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 08:21:49 -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 IAA04697;
	Mon, 7 Jan 2002 08:13:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04666
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 08:13:16 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13856
	for <megaco@ietf.org>; Mon, 7 Jan 2002 08:13:13 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001644688@fsnt.future.futsoft.com>;
 Mon, 07 Jan 2002 18:57:18 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g07DCNe16104;
	Mon, 7 Jan 2002 18:42:23 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Cc: <madhubabu@kenetec.com>
Date: Mon, 7 Jan 2002 18:49:57 +0530
Message-Id: <001a01c1977e$01a74f20$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Use of Modem descriptor
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: 7bit

Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


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



From megaco-admin@ietf.org  Mon Jan  7 08:44:13 2002
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 IAA14188
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 08:44:13 -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 IAA04861;
	Mon, 7 Jan 2002 08:28:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04832
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 08:28:00 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14044
	for <megaco@ietf.org>; Mon, 7 Jan 2002 08:27:57 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g07DRvJ25228;
	Mon, 7 Jan 2002 14:27:57 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g07DRthO013617;
	Mon, 7 Jan 2002 15:27:55 +0200 (EET)
Message-ID: <3C39A256.A7721E51@lmf.ericsson.se>
Date: Mon, 07 Jan 2002 15:27:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Raphael Tryster <raphael@tdsoft.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] precise identification of an incoming call
References: <B1584457374ED211B7A90008C7242DEF017F8351@Exchange>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I guess the "call" can begin by the MG collecting events, eg digits or
NAS events, which will be sent to the MGC using Notify. To do that, the
MGC would first ask for the digits by sending a Modify to the
termination(s) where digits may be received.

Regards,

Christer Holmberg
Ericsson Finland



However,

Raphael Tryster wrote:
> 
> In the example call flow given in RFC 3015 Appendix A, the incoming
> call to the second subscriber begins with an ADD command from MGC to
> MG2 in step 14.  Is this the only way an incoming call can begin?  In
> other words, can the MG assume the MGC will not send it any other
> commands related to an incoming call before the ADD?
> 
> Raphael Tryster

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


From daemon@optimus.ietf.org  Mon Jan  7 08:44:14 2002
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 IAA14197
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 08:44:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA05494
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 08:44:16 -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 IAA04861;
	Mon, 7 Jan 2002 08:28:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04832
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 08:28:00 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14044
	for <megaco@ietf.org>; Mon, 7 Jan 2002 08:27:57 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g07DRvJ25228;
	Mon, 7 Jan 2002 14:27:57 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g07DRthO013617;
	Mon, 7 Jan 2002 15:27:55 +0200 (EET)
Message-ID: <3C39A256.A7721E51@lmf.ericsson.se>
Date: Mon, 07 Jan 2002 15:27:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Raphael Tryster <raphael@tdsoft.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] precise identification of an incoming call
References: <B1584457374ED211B7A90008C7242DEF017F8351@Exchange>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I guess the "call" can begin by the MG collecting events, eg digits or
NAS events, which will be sent to the MGC using Notify. To do that, the
MGC would first ask for the digits by sending a Modify to the
termination(s) where digits may be received.

Regards,

Christer Holmberg
Ericsson Finland



However,

Raphael Tryster wrote:
> 
> In the example call flow given in RFC 3015 Appendix A, the incoming
> call to the second subscriber begins with an ADD command from MGC to
> MG2 in step 14.  Is this the only way an incoming call can begin?  In
> other words, can the MG assume the MGC will not send it any other
> commands related to an incoming call before the ADD?
> 
> Raphael Tryster

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



From megaco-admin@ietf.org  Mon Jan  7 09:26:17 2002
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 JAA15149
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:26: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 JAA06225;
	Mon, 7 Jan 2002 09:06:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06193
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:06:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14402
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:06:33 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07E62A02215;
	Mon, 7 Jan 2002 09:06:02 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07E60C17353;
	Mon, 7 Jan 2002 09:06:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQNVLF>; Mon, 7 Jan 2002 09:04:24 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Mon, 7 Jan 2002 09:04:44 -0500 
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

Your proposal is a bit against the Megaco philosophy.  Megaco tells the MG
what results are required and leaves it up to the MG to manage its internal
resources to get those results.  In older technology conferencing required a
dedicated resource, in the way you suggest, but these days my understanding
is that everything is done by DSPs.  Conferencing just requires the loading
of a little more software and the allocation of more memory and CPU time.

Your remarks on handoff make me suspect there are some requirements to be
looked at before we consider a detailed solution.  I assume you are saying
that in both the handoff and conferencing cases you may have three
terminations in the context, but in the handoff case two of the terminations
represent the same user.  What sort of behaviour are you then expecting from
the MG?  Why do you need two terminations to represent the user being handed
off?

-----Original Message-----
From: zhangzhong [mailto:zhangzhong@huawei.com]
Sent: Friday, January 04, 2002 10:45 PM
To: Rosen, Brian
Cc: megaco@ietf.org
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
RFC2805


Hi Brian, all
Ok, This problem will discuss later after having a way.
Another problems, could you answer to me , thanks .
Why not define a explicit way to apply the conference resource ?
How can MGW know when to activate conference resource ?
How can MGC know whether a MGW have the conference resource or not? If
through configuration, How does MGC maintain the dynamic status of
conference resource when it is bad or restrore?
If through the max number in one context , it is no problem in fixed network
, but in mobiles cases, HandOver will introduce more than two termination
into one context.

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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


From daemon@optimus.ietf.org  Mon Jan  7 09:26:18 2002
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 JAA15159
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:26:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06740
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:26:18 -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 JAA06225;
	Mon, 7 Jan 2002 09:06:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06193
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:06:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14402
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:06:33 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07E62A02215;
	Mon, 7 Jan 2002 09:06:02 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07E60C17353;
	Mon, 7 Jan 2002 09:06:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQNVLF>; Mon, 7 Jan 2002 09:04:24 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Mon, 7 Jan 2002 09:04:44 -0500 
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

Your proposal is a bit against the Megaco philosophy.  Megaco tells the MG
what results are required and leaves it up to the MG to manage its internal
resources to get those results.  In older technology conferencing required a
dedicated resource, in the way you suggest, but these days my understanding
is that everything is done by DSPs.  Conferencing just requires the loading
of a little more software and the allocation of more memory and CPU time.

Your remarks on handoff make me suspect there are some requirements to be
looked at before we consider a detailed solution.  I assume you are saying
that in both the handoff and conferencing cases you may have three
terminations in the context, but in the handoff case two of the terminations
represent the same user.  What sort of behaviour are you then expecting from
the MG?  Why do you need two terminations to represent the user being handed
off?

-----Original Message-----
From: zhangzhong [mailto:zhangzhong@huawei.com]
Sent: Friday, January 04, 2002 10:45 PM
To: Rosen, Brian
Cc: megaco@ietf.org
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
RFC2805


Hi Brian, all
Ok, This problem will discuss later after having a way.
Another problems, could you answer to me , thanks .
Why not define a explicit way to apply the conference resource ?
How can MGW know when to activate conference resource ?
How can MGC know whether a MGW have the conference resource or not? If
through configuration, How does MGC maintain the dynamic status of
conference resource when it is bad or restrore?
If through the max number in one context , it is no problem in fixed network
, but in mobiles cases, HandOver will introduce more than two termination
into one context.

Regards
Zhangzhong

----- Original Message ----- 
From: Rosen, Brian <Brian.Rosen@marconi.com>
To: 'zhangzhong' <zhangzhong@huawei.com>
Cc: <megaco@ietf.org>
Sent: Friday, January 04, 2002 9:13 PM
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC2805


> Because the general problem is very complex, and no one has
> proposed a general solution that seems likely to cover most
> cases.
> 
> As an example, many systems are implemented with DSPs.  These
> systems have very complex interaction between how many codecs
> of different types can be in use simultaneously.  A system might,
> for example, support 16 channels of G.729, 32 channels of G.711
> and 32 channels of G.165 echo cancel with 64 ms tails, but
> not simultaneously.  It may be that if you have one channel of
> G.729, then you can support another 27 channels of G.711, and
> if you have any G.729, then the longest tail is reduced.
> This is because there are actually several variables at work -
> DSP MIPs, and memory capacity, and the interaction between those
> variables is complex.  I once discussed having a language which
> allowed you to express this kind of thing, but it was too complex
> for most people to deal with.  Then you add spares issues and
> things get even more complex.
> 
> The other side of this issue is that the MGC can ask for resources
> on the MG, and the MG can fail if there are no more resources.
> This can be done in a way that lets the MGC either try to reroute
> the call, or supply the appropriate error message to the caller.
> That is why we didn't worry more about this known limitation.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 4:08 AM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> > 
> > 
> > Hi Brian,
> > Yes , It can know the resource using, But if you can't 
> > binding all channel with Termination, How can you know the 
> > status of left? idle or failed? 
> > We can configure the Max number of channel and we can know 
> > the exact number of them is busy, but we can't know the 
> > status of spares . We can bind a termination with one 
> > channel, and put into NULL context, Only in this case, when 
> > one channel failed, MGW report the status to MGC .
> > But this method , I think , is not a standard way .
> > Why not define a explicit way to reach the aim?
> > 
> > Regards
> > Zhangzhong
> > 
> > ----- Original Message ----- 
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Wednesday, January 02, 2002 9:18 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > requirement on RFC2805
> > 
> > 
> > > You audit the Media descriptor of all of the terminations
> > > to determine which terminations are employing the
> > > codec of interest.
> > > 
> > > Brian
> > > 
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > requirement on
> > > > RFC2805
> > > > 
> > > > 
> > > > Hi Brian,  All
> > > > I agree with you on the concept of Audit capability and Audit 
> > > > Value . But in present protocol , How can we get the 500 busy 
> > > > through Audit value present defined, I can't find the 
> > > > parameter or package defined the case. 
> > > > 
> > > > Regards
> > > > Zhangzhong
> > > > 
> > > > ----- Original Message ----- 
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on RFC2805
> > > > 
> > > > 
> > > > > Audit capabilities tells you what the capabilities of the system
> > > > > are.  Audit Value tells you what is currently "in use".
> > > > > In theory, the "1000 G.711 channel resource" comes from Audit
> > > > > Capability, "500 busy" comes from Audit Value.
> > > > > 
> > > > > In general, the RFC is compliant with the requirements with one
> > > > > notable exception: many gateways are implemented with 
> > DSPs or other
> > > > > programmable resources. There is no good way to express 
> > capability
> > > > > with such resources.
> > > > > 
> > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > will reveal
> > > > > that.  If 500 channels are used, Audit Value will reveal that.
> > > > > 
> > > > > Brian
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
> > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > HI Shashi,All,
> > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > inconsistency. But for
> > > > > > the specific scenario Zhang has pointed, How this resource 
> > > > > > information is
> > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > knowledge there is no
> > > > > > parameter or anything as such to "quantitatively" identify 
> > > > > > G711 or any such
> > > > > > channel resource.
> > > > > > Regards
> > > > > > Madhubabu
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From: megaco-admin@ietf.org 
> > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > Shashi Kumar
> > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > To: zhangzhong
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > requirement on
> > > > > > RFC2805
> > > > > > 
> > > > > > 
> > > > > > we have provision to audit the MG resource, which 
> > > > clearlty defined by
> > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > we can always
> > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > 
> > > > > > thanks,
> > > > > > shashi
> > > > > > 
> > > > > > 
> > > > > > > zhangzhong wrote:
> > > > > > >
> > > > > > > Hi :
> > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > >         Provide a mechanism to discover the current 
> > available
> > > > > > > resources
> > > > > > >         in the MG, where resources are dynamically 
> > consumed by
> > > > > > >         connections and the MGC cannot reasonably or 
> > > > reliably track
> > > > > > > the
> > > > > > >         consumption of such resources. It should also 
> > > > be possible to
> > > > > > >         discover resources currently in use, in order 
> > > > to reconcile
> > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > >
> > > > > > > This means MGC can know the resource consume in the MGW , 
> > > > > > for example
> > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > busy , How can
> > > > > > > MGC know this through RFC3015?
> > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > >
> > > > > > > Thanks for the reply.
> > > > > > > Regards
> > > > > > > Zhangzhong
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > 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



From megaco-admin@ietf.org  Mon Jan  7 09:37:02 2002
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 JAA15480
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:37:02 -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 JAA06579;
	Mon, 7 Jan 2002 09:18:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06550
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:18:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14997
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:18:22 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EHqA07359;
	Mon, 7 Jan 2002 09:17:52 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EHoC18291;
	Mon, 7 Jan 2002 09:17:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQNYCV>; Mon, 7 Jan 2002 09:16:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Fw: Handoff-query-reg
Date: Mon, 7 Jan 2002 09:15:51 -0500 
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

The exact requirement is stated in the first paragraph of section 9 of the
standard, and is unchanged in v2:

  "For transport of the protocol over IP, MGCs shall implement both TCP and
UDP/ALF, an MG shall implement TCP or UDP/ALF or both."

The original question, though, was whether the standard should dictate
exactly which protocol an MG should use for alternative MGCs given that it
used a specific protocol with one of them.  In fact, the standard says that
it can use whichever protocol it wants and the MGC will support it. 


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Saturday, January 05, 2002 1:57 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Fw: Handoff-query-reg


Tom 
Way back, I thought the Standard said that MGC has to support both - UDP/TCP
and MG 
can support either. 
Earlier attempt also tried to define 2 well know Megaco port for UDP and TCP
which turns out 
to be unnecessary for the following reason. 
Since MGC is the server, it listens on port 2944 (text encoding) or 2945
(binary encoding) for UDP or TCP. 
If MG attempts a registration on UDP, then MGC uses UDP for that MG and same
goes for TCP. 
Has this been changed in v1? 
Thanks 
Chuong 
  
Tom-PT Taylor wrote: 
As I see it, this is a configuration issue -- don't look to the RFC for 
guidance. 
-----Original Message----- 
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com] 
Sent: Friday, January 04, 2002 12:22 AM 
To: megaco@ietf.org 
Subject: [Megaco] Fw: Handoff-query-reg 
----- Original Message ----- 
From: Madhu Babu Brahmanapally 
To: 'Surya Kumar IVG' 
Sent: Thursday, January 03, 2002 7:51 PM 
Subject: RE: Handoff-query-reg 
HI Surya, 
I wrote the reply yesterday and thought I sent it to you, Sorry for that. 
Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that

control pool will have similar transport mechanism. I mean if the Primary is

using TCP, the new MGC contacted due to failover or handoff will also be 
using the same transport protocol. As you mentioned, the RFC doesn't throw 
any light on this. Whydont you send a mail to the mailing list for expected 
outcome in this situation. But IMO don't hardcode any transport protocol for

this purpose(or assume any default). Hope that the mailing list replies may 
help us. 
Regards 
Madhubabu 
-----Original Message----- 
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com] 
Sent: Thursday, January 03, 2002 2:02 AM 
To: Madhu Babu Brahmanapally 
Subject: Fw: Handoff-query-reg 
REPEAT 
----- Original Message ----- 
From: Surya Kumar IVG 
To: Madhu Babu Brahmanapally 
Sent: Wednesday, January 02, 2002 12:30 PM 
Subject: Handoff-query-reg 
Dear Madhubabu 
I have a query with regards to handoff mechanism. 
Considering that MGC P is going down for a while for maintenance and sends a

handoff to MG and provides the ID of MGC to be contacted , while it goes 
down. 
The MG tries with a failover to that particular MGC and treats that as 
Primary for all practical purposes, if contacts successfully. Else it goes 
for list of designated secondary mGCs one after another , till it is 
successful. 
But , once handoff comes, MGC does not specify any transport  media on which

MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any

details on that. 
Can we make it as default for MG to try on UDP and not successful, it can 
still try on TCP to the same MGC. ? If not successful , then MG moves to 
secondary MGC. 
regards 
surya 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
-- 
  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


From daemon@optimus.ietf.org  Mon Jan  7 09:37:03 2002
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 JAA15492
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:37:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA07677
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:37:03 -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 JAA06579;
	Mon, 7 Jan 2002 09:18:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06550
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:18:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14997
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:18:22 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EHqA07359;
	Mon, 7 Jan 2002 09:17:52 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EHoC18291;
	Mon, 7 Jan 2002 09:17:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQNYCV>; Mon, 7 Jan 2002 09:16:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Fw: Handoff-query-reg
Date: Mon, 7 Jan 2002 09:15:51 -0500 
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

The exact requirement is stated in the first paragraph of section 9 of the
standard, and is unchanged in v2:

  "For transport of the protocol over IP, MGCs shall implement both TCP and
UDP/ALF, an MG shall implement TCP or UDP/ALF or both."

The original question, though, was whether the standard should dictate
exactly which protocol an MG should use for alternative MGCs given that it
used a specific protocol with one of them.  In fact, the standard says that
it can use whichever protocol it wants and the MGC will support it. 


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Saturday, January 05, 2002 1:57 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Fw: Handoff-query-reg


Tom 
Way back, I thought the Standard said that MGC has to support both - UDP/TCP
and MG 
can support either. 
Earlier attempt also tried to define 2 well know Megaco port for UDP and TCP
which turns out 
to be unnecessary for the following reason. 
Since MGC is the server, it listens on port 2944 (text encoding) or 2945
(binary encoding) for UDP or TCP. 
If MG attempts a registration on UDP, then MGC uses UDP for that MG and same
goes for TCP. 
Has this been changed in v1? 
Thanks 
Chuong 
  
Tom-PT Taylor wrote: 
As I see it, this is a configuration issue -- don't look to the RFC for 
guidance. 
-----Original Message----- 
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com] 
Sent: Friday, January 04, 2002 12:22 AM 
To: megaco@ietf.org 
Subject: [Megaco] Fw: Handoff-query-reg 
----- Original Message ----- 
From: Madhu Babu Brahmanapally 
To: 'Surya Kumar IVG' 
Sent: Thursday, January 03, 2002 7:51 PM 
Subject: RE: Handoff-query-reg 
HI Surya, 
I wrote the reply yesterday and thought I sent it to you, Sorry for that. 
Normally when a MG is controlled by a MGC pool, IMO all the MGCs inside that

control pool will have similar transport mechanism. I mean if the Primary is

using TCP, the new MGC contacted due to failover or handoff will also be 
using the same transport protocol. As you mentioned, the RFC doesn't throw 
any light on this. Whydont you send a mail to the mailing list for expected 
outcome in this situation. But IMO don't hardcode any transport protocol for

this purpose(or assume any default). Hope that the mailing list replies may 
help us. 
Regards 
Madhubabu 
-----Original Message----- 
From: Surya Kumar IVG [mailto:surya@netlab.hcltech.com] 
Sent: Thursday, January 03, 2002 2:02 AM 
To: Madhu Babu Brahmanapally 
Subject: Fw: Handoff-query-reg 
REPEAT 
----- Original Message ----- 
From: Surya Kumar IVG 
To: Madhu Babu Brahmanapally 
Sent: Wednesday, January 02, 2002 12:30 PM 
Subject: Handoff-query-reg 
Dear Madhubabu 
I have a query with regards to handoff mechanism. 
Considering that MGC P is going down for a while for maintenance and sends a

handoff to MG and provides the ID of MGC to be contacted , while it goes 
down. 
The MG tries with a failover to that particular MGC and treats that as 
Primary for all practical purposes, if contacts successfully. Else it goes 
for list of designated secondary mGCs one after another , till it is 
successful. 
But , once handoff comes, MGC does not specify any transport  media on which

MG has to try to talk to MGC i.e UDp or TCP. The RFC also does not throw any

details on that. 
Can we make it as default for MG to try on UDP and not successful, it can 
still try on TCP to the same MGC. ? If not successful , then MG moves to 
secondary MGC. 
regards 
surya 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
-- 
  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



From megaco-admin@ietf.org  Mon Jan  7 09:44:44 2002
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 JAA15697
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:44:44 -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 JAA06723;
	Mon, 7 Jan 2002 09:25:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06692
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:25:45 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15125
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:25:42 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EPCA10167;
	Mon, 7 Jan 2002 09:25:12 -0500 (EST)
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 g07EPAM29748;
	Mon, 7 Jan 2002 09:25:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQN5XZ>; Mon, 7 Jan 2002 09:23:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] precise identification of an incoming call
Date: Mon, 7 Jan 2002 09:21:27 -0500 
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

You may be correct, but my agreement is because no counter-examples come
immediately to mind.  I wouldn't design equipment on this assumption.  There
may be some call flow where it makes sense to modify the second subscriber's
termination while it is still in the null context.


-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Monday, January 07, 2002 7:03 AM
To: megaco@ietf.org
Subject: [Megaco] precise identification of an incoming call


In the example call flow given in RFC 3015 Appendix A, the incoming call to
the second subscriber begins with an ADD command from MGC to MG2 in step 14.
Is this the only way an incoming call can begin?  In other words, can the MG
assume the MGC will not send it any other commands related to an incoming
call before the ADD?


Raphael Tryster 

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


From daemon@optimus.ietf.org  Mon Jan  7 09:44:44 2002
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 JAA15706
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:44:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA07964
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:44:45 -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 JAA06723;
	Mon, 7 Jan 2002 09:25:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06692
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:25:45 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15125
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:25:42 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EPCA10167;
	Mon, 7 Jan 2002 09:25:12 -0500 (EST)
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 g07EPAM29748;
	Mon, 7 Jan 2002 09:25:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQN5XZ>; Mon, 7 Jan 2002 09:23:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADD9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] precise identification of an incoming call
Date: Mon, 7 Jan 2002 09:21:27 -0500 
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

You may be correct, but my agreement is because no counter-examples come
immediately to mind.  I wouldn't design equipment on this assumption.  There
may be some call flow where it makes sense to modify the second subscriber's
termination while it is still in the null context.


-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Monday, January 07, 2002 7:03 AM
To: megaco@ietf.org
Subject: [Megaco] precise identification of an incoming call


In the example call flow given in RFC 3015 Appendix A, the incoming call to
the second subscriber begins with an ADD command from MGC to MG2 in step 14.
Is this the only way an incoming call can begin?  In other words, can the MG
assume the MGC will not send it any other commands related to an incoming
call before the ADD?


Raphael Tryster 

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



From megaco-admin@ietf.org  Mon Jan  7 09:44:58 2002
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 JAA15725
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:44:57 -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 JAA06814;
	Mon, 7 Jan 2002 09:27:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06783
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:27:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15206
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:27:14 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EQfA10726;
	Mon, 7 Jan 2002 09:26:41 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EQcC18875;
	Mon, 7 Jan 2002 09:26:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQN6JZ>; Mon, 7 Jan 2002 09:25:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADDA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor
Date: Mon, 7 Jan 2002 09:22:25 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19786.BAD15F60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19786.BAD15F60
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


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

------_=_NextPart_001_01C19786.BAD15F60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Use of Modem descriptor</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: gokulc [<A =
HREF=3D"mailto:gokulc@future.futsoft.com">mailto:gokulc@future.futsoft.c=
om</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 07, 2002 8:20 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: madhubabu@kenetec.com</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Use of Modem descriptor</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>When a add/move/modify command with the modem =
descriptor is issued,</FONT>
<BR><FONT SIZE=3D2>the MG connects the appropriate modem from the free =
resource pool to the</FONT>
<BR><FONT SIZE=3D2>addressed termination in the command.</FONT>
</P>

<P><FONT SIZE=3D2>Add =3D Term1{</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Modem =3D =
V90</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>....</FONT>
<BR><FONT SIZE=3D2>}</FONT>
</P>

<P><FONT SIZE=3D2>It is my understanding that the Term1 is not the =
identification of the</FONT>
<BR><FONT SIZE=3D2>modem, but</FONT>
<BR><FONT SIZE=3D2>that of the line/trunk termination.</FONT>
</P>

<P><FONT SIZE=3D2>On the same lines how is a mux resource =
handled...</FONT>
</P>

<P><FONT SIZE=3D2>gokul</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19786.BAD15F60--

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


From daemon@optimus.ietf.org  Mon Jan  7 09:44:59 2002
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 JAA15738
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:44:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA07989
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:44:59 -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 JAA06814;
	Mon, 7 Jan 2002 09:27:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06783
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:27:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15206
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:27:14 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EQfA10726;
	Mon, 7 Jan 2002 09:26:41 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07EQcC18875;
	Mon, 7 Jan 2002 09:26:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPGQN6JZ>; Mon, 7 Jan 2002 09:25:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADDA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor
Date: Mon, 7 Jan 2002 09:22:25 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19786.BAD15F60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19786.BAD15F60
Content-Type: text/plain;
	charset="iso-8859-1"



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


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

------_=_NextPart_001_01C19786.BAD15F60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Use of Modem descriptor</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: gokulc [<A =
HREF=3D"mailto:gokulc@future.futsoft.com">mailto:gokulc@future.futsoft.c=
om</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 07, 2002 8:20 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: madhubabu@kenetec.com</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Use of Modem descriptor</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>When a add/move/modify command with the modem =
descriptor is issued,</FONT>
<BR><FONT SIZE=3D2>the MG connects the appropriate modem from the free =
resource pool to the</FONT>
<BR><FONT SIZE=3D2>addressed termination in the command.</FONT>
</P>

<P><FONT SIZE=3D2>Add =3D Term1{</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Modem =3D =
V90</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>....</FONT>
<BR><FONT SIZE=3D2>}</FONT>
</P>

<P><FONT SIZE=3D2>It is my understanding that the Term1 is not the =
identification of the</FONT>
<BR><FONT SIZE=3D2>modem, but</FONT>
<BR><FONT SIZE=3D2>that of the line/trunk termination.</FONT>
</P>

<P><FONT SIZE=3D2>On the same lines how is a mux resource =
handled...</FONT>
</P>

<P><FONT SIZE=3D2>gokul</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19786.BAD15F60--

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



From megaco-admin@ietf.org  Mon Jan  7 09:50:14 2002
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 JAA15959
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:50:14 -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 JAA07478;
	Mon, 7 Jan 2002 09:31:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07381
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:31:33 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15366
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:31:31 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA24862;
	Mon, 7 Jan 2002 09:30:56 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA29702;
	Mon, 7 Jan 2002 09:30:55 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTWKQ>; Mon, 7 Jan 2002 09:30:54 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A0@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Mon, 7 Jan 2002 09:30:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Well, the door is, at least in theory, open to add features in
V2.  I actually oppose doing this, but there are some who feel
that tinkering with the protocol before there is any substantial
deployment experience is a good idea.

You could propose a solution.  If you do, I think you would want
to see if it works for a wide variety of resource models that MGs
might implement, and yet be simple enough that a really small
phone or gateway could implement it without a lot of code.

The answer to your question is that if the MGC knows the MG has
a capability for something, but gets an error when it tries to
use it, then it could, when a future requirement arises for that
capability, ask for it again.  It will either work, or fail
again.  No need to poll.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 10:40 PM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian, all
> Yes , It has problems about this. I think there should have 
> some methods resolving them. 
> And If we can't resolve these problems, There will introduce 
> more difficulity of interworking between different company's 
> product  and low the efficiency of network.
> Problems:
> MGW can reject the resource command from MGC, OK, It is no 
> problems. But how MGC know the resource in this MGW is 
> available again?  We can  setup a flag , and apply the 
> request periodicly, when success, reset the flag, or start a 
> timer , after the timer time out , reset the flag. etc.
> All these methods will introcude much traffic between MGC and 
> MGW. It is not good for the network resource management in the MGC. 
> 
> Regards
> Zhangzhong
> 
> 
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, January 04, 2002 9:13 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Because the general problem is very complex, and no one has
> > proposed a general solution that seems likely to cover most
> > cases.
> > 
> > As an example, many systems are implemented with DSPs.  These
> > systems have very complex interaction between how many codecs
> > of different types can be in use simultaneously.  A system might,
> > for example, support 16 channels of G.729, 32 channels of G.711
> > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > not simultaneously.  It may be that if you have one channel of
> > G.729, then you can support another 27 channels of G.711, and
> > if you have any G.729, then the longest tail is reduced.
> > This is because there are actually several variables at work -
> > DSP MIPs, and memory capacity, and the interaction between those
> > variables is complex.  I once discussed having a language which
> > allowed you to express this kind of thing, but it was too complex
> > for most people to deal with.  Then you add spares issues and
> > things get even more complex.
> > 
> > The other side of this issue is that the MGC can ask for resources
> > on the MG, and the MG can fail if there are no more resources.
> > This can be done in a way that lets the MGC either try to reroute
> > the call, or supply the appropriate error message to the caller.
> > That is why we didn't worry more about this known limitation.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, January 04, 2002 4:08 AM
> > > To: Rosen, Brian
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,
> > > Yes , It can know the resource using, But if you can't 
> > > binding all channel with Termination, How can you know the 
> > > status of left? idle or failed? 
> > > We can configure the Max number of channel and we can know 
> > > the exact number of them is busy, but we can't know the 
> > > status of spares . We can bind a termination with one 
> > > channel, and put into NULL context, Only in this case, when 
> > > one channel failed, MGW report the status to MGC .
> > > But this method , I think , is not a standard way .
> > > Why not define a explicit way to reach the aim?
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > You audit the Media descriptor of all of the terminations
> > > > to determine which terminations are employing the
> > > > codec of interest.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > Hi Brian,  All
> > > > > I agree with you on the concept of Audit capability and Audit 
> > > > > Value . But in present protocol , How can we get the 500 busy 
> > > > > through Audit value present defined, I can't find the 
> > > > > parameter or package defined the case. 
> > > > > 
> > > > > Regards
> > > > > Zhangzhong
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > > <zhangzhong@huawei.com>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on RFC2805
> > > > > 
> > > > > 
> > > > > > Audit capabilities tells you what the capabilities 
> of the system
> > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > In theory, the "1000 G.711 channel resource" comes 
> from Audit
> > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > 
> > > > > > In general, the RFC is compliant with the 
> requirements with one
> > > > > > notable exception: many gateways are implemented with 
> > > DSPs or other
> > > > > > programmable resources. There is no good way to express 
> > > capability
> > > > > > with such resources.
> > > > > > 
> > > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > > will reveal
> > > > > > that.  If 500 channels are used, Audit Value will 
> reveal that.
> > > > > > 
> > > > > > Brian
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Madhu Babu Brahmanapally 
> [mailto:madhubabu@kenetec.com]
> > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > HI Shashi,All,
> > > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > > inconsistency. But for
> > > > > > > the specific scenario Zhang has pointed, How this 
> resource 
> > > > > > > information is
> > > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > > knowledge there is no
> > > > > > > parameter or anything as such to "quantitatively" 
> identify 
> > > > > > > G711 or any such
> > > > > > > channel resource.
> > > > > > > Regards
> > > > > > > Madhubabu
> > > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: megaco-admin@ietf.org 
> > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > Shashi Kumar
> > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > To: zhangzhong
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > we have provision to audit the MG resource, which 
> > > > > clearlty defined by
> > > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > > we can always
> > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > 
> > > > > > > thanks,
> > > > > > > shashi
> > > > > > > 
> > > > > > > 
> > > > > > > > zhangzhong wrote:
> > > > > > > >
> > > > > > > > Hi :
> > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > >         Provide a mechanism to discover the current 
> > > available
> > > > > > > > resources
> > > > > > > >         in the MG, where resources are dynamically 
> > > consumed by
> > > > > > > >         connections and the MGC cannot reasonably or 
> > > > > reliably track
> > > > > > > > the
> > > > > > > >         consumption of such resources. It should also 
> > > > > be possible to
> > > > > > > >         discover resources currently in use, in order 
> > > > > to reconcile
> > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > >
> > > > > > > > This means MGC can know the resource consume in 
> the MGW , 
> > > > > > > for example
> > > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > > busy , How can
> > > > > > > > MGC know this through RFC3015?
> > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > >
> > > > > > > > Thanks for the reply.
> > > > > > > > Regards
> > > > > > > > Zhangzhong
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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


From daemon@optimus.ietf.org  Mon Jan  7 09:50:14 2002
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 JAA15969
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:50:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08117
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:50:15 -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 JAA07478;
	Mon, 7 Jan 2002 09:31:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07381
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:31:33 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15366
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:31:31 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA24862;
	Mon, 7 Jan 2002 09:30:56 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA29702;
	Mon, 7 Jan 2002 09:30:55 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTWKQ>; Mon, 7 Jan 2002 09:30:54 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A0@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] one dount on RFC3015 as to the requirement on RFC280
	5
Date: Mon, 7 Jan 2002 09:30:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Well, the door is, at least in theory, open to add features in
V2.  I actually oppose doing this, but there are some who feel
that tinkering with the protocol before there is any substantial
deployment experience is a good idea.

You could propose a solution.  If you do, I think you would want
to see if it works for a wide variety of resource models that MGs
might implement, and yet be simple enough that a really small
phone or gateway could implement it without a lot of code.

The answer to your question is that if the MGC knows the MG has
a capability for something, but gets an error when it tries to
use it, then it could, when a future requirement arises for that
capability, ask for it again.  It will either work, or fail
again.  No need to poll.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 10:40 PM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian, all
> Yes , It has problems about this. I think there should have 
> some methods resolving them. 
> And If we can't resolve these problems, There will introduce 
> more difficulity of interworking between different company's 
> product  and low the efficiency of network.
> Problems:
> MGW can reject the resource command from MGC, OK, It is no 
> problems. But how MGC know the resource in this MGW is 
> available again?  We can  setup a flag , and apply the 
> request periodicly, when success, reset the flag, or start a 
> timer , after the timer time out , reset the flag. etc.
> All these methods will introcude much traffic between MGC and 
> MGW. It is not good for the network resource management in the MGC. 
> 
> Regards
> Zhangzhong
> 
> 
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, January 04, 2002 9:13 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Because the general problem is very complex, and no one has
> > proposed a general solution that seems likely to cover most
> > cases.
> > 
> > As an example, many systems are implemented with DSPs.  These
> > systems have very complex interaction between how many codecs
> > of different types can be in use simultaneously.  A system might,
> > for example, support 16 channels of G.729, 32 channels of G.711
> > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > not simultaneously.  It may be that if you have one channel of
> > G.729, then you can support another 27 channels of G.711, and
> > if you have any G.729, then the longest tail is reduced.
> > This is because there are actually several variables at work -
> > DSP MIPs, and memory capacity, and the interaction between those
> > variables is complex.  I once discussed having a language which
> > allowed you to express this kind of thing, but it was too complex
> > for most people to deal with.  Then you add spares issues and
> > things get even more complex.
> > 
> > The other side of this issue is that the MGC can ask for resources
> > on the MG, and the MG can fail if there are no more resources.
> > This can be done in a way that lets the MGC either try to reroute
> > the call, or supply the appropriate error message to the caller.
> > That is why we didn't worry more about this known limitation.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, January 04, 2002 4:08 AM
> > > To: Rosen, Brian
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,
> > > Yes , It can know the resource using, But if you can't 
> > > binding all channel with Termination, How can you know the 
> > > status of left? idle or failed? 
> > > We can configure the Max number of channel and we can know 
> > > the exact number of them is busy, but we can't know the 
> > > status of spares . We can bind a termination with one 
> > > channel, and put into NULL context, Only in this case, when 
> > > one channel failed, MGW report the status to MGC .
> > > But this method , I think , is not a standard way .
> > > Why not define a explicit way to reach the aim?
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > You audit the Media descriptor of all of the terminations
> > > > to determine which terminations are employing the
> > > > codec of interest.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > Hi Brian,  All
> > > > > I agree with you on the concept of Audit capability and Audit 
> > > > > Value . But in present protocol , How can we get the 500 busy 
> > > > > through Audit value present defined, I can't find the 
> > > > > parameter or package defined the case. 
> > > > > 
> > > > > Regards
> > > > > Zhangzhong
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > > <zhangzhong@huawei.com>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on RFC2805
> > > > > 
> > > > > 
> > > > > > Audit capabilities tells you what the capabilities 
> of the system
> > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > In theory, the "1000 G.711 channel resource" comes 
> from Audit
> > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > 
> > > > > > In general, the RFC is compliant with the 
> requirements with one
> > > > > > notable exception: many gateways are implemented with 
> > > DSPs or other
> > > > > > programmable resources. There is no good way to express 
> > > capability
> > > > > > with such resources.
> > > > > > 
> > > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > > will reveal
> > > > > > that.  If 500 channels are used, Audit Value will 
> reveal that.
> > > > > > 
> > > > > > Brian
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Madhu Babu Brahmanapally 
> [mailto:madhubabu@kenetec.com]
> > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > HI Shashi,All,
> > > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > > inconsistency. But for
> > > > > > > the specific scenario Zhang has pointed, How this 
> resource 
> > > > > > > information is
> > > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > > knowledge there is no
> > > > > > > parameter or anything as such to "quantitatively" 
> identify 
> > > > > > > G711 or any such
> > > > > > > channel resource.
> > > > > > > Regards
> > > > > > > Madhubabu
> > > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: megaco-admin@ietf.org 
> > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > Shashi Kumar
> > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > To: zhangzhong
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > we have provision to audit the MG resource, which 
> > > > > clearlty defined by
> > > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > > we can always
> > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > 
> > > > > > > thanks,
> > > > > > > shashi
> > > > > > > 
> > > > > > > 
> > > > > > > > zhangzhong wrote:
> > > > > > > >
> > > > > > > > Hi :
> > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > >         Provide a mechanism to discover the current 
> > > available
> > > > > > > > resources
> > > > > > > >         in the MG, where resources are dynamically 
> > > consumed by
> > > > > > > >         connections and the MGC cannot reasonably or 
> > > > > reliably track
> > > > > > > > the
> > > > > > > >         consumption of such resources. It should also 
> > > > > be possible to
> > > > > > > >         discover resources currently in use, in order 
> > > > > to reconcile
> > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > >
> > > > > > > > This means MGC can know the resource consume in 
> the MGW , 
> > > > > > > for example
> > > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > > busy , How can
> > > > > > > > MGC know this through RFC3015?
> > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > >
> > > > > > > > Thanks for the reply.
> > > > > > > > Regards
> > > > > > > > Zhangzhong
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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



From megaco-admin@ietf.org  Mon Jan  7 09:50:54 2002
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 JAA15990
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:50:54 -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 JAA07577;
	Mon, 7 Jan 2002 09:34:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07551
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:34:14 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15434
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:34:12 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25182;
	Mon, 7 Jan 2002 09:33:42 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA01005;
	Mon, 7 Jan 2002 09:33:27 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTWZ3>; Mon, 7 Jan 2002 09:33:26 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A1@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Conference Resources, was: one dount on RFC3015 as t
	o the requirement on RFC2805
Date: Mon, 7 Jan 2002 09:33:18 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

If the maximum number of terminations per context is 2, then
there is no conference resource.  If the max number of terminations
is 3, then a 3-way is possible.  If the max number is greater
than 3, then a more expansive conference is possible.

There is a conference package under discussion.  This would allow
an MGC to control a bridge.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 10:45 PM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian, all
> Ok, This problem will discuss later after having a way.
> Another problems, could you answer to me , thanks .
> Why not define a explicit way to apply the conference resource ?
> How can MGW know when to activate conference resource ?
> How can MGC know whether a MGW have the conference resource 
> or not? If through configuration, How does MGC maintain the 
> dynamic status of conference resource when it is bad or restrore?
> If through the max number in one context , it is no problem 
> in fixed network , but in mobiles cases, HandOver will 
> introduce more than two termination into one context.
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, January 04, 2002 9:13 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Because the general problem is very complex, and no one has
> > proposed a general solution that seems likely to cover most
> > cases.
> > 
> > As an example, many systems are implemented with DSPs.  These
> > systems have very complex interaction between how many codecs
> > of different types can be in use simultaneously.  A system might,
> > for example, support 16 channels of G.729, 32 channels of G.711
> > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > not simultaneously.  It may be that if you have one channel of
> > G.729, then you can support another 27 channels of G.711, and
> > if you have any G.729, then the longest tail is reduced.
> > This is because there are actually several variables at work -
> > DSP MIPs, and memory capacity, and the interaction between those
> > variables is complex.  I once discussed having a language which
> > allowed you to express this kind of thing, but it was too complex
> > for most people to deal with.  Then you add spares issues and
> > things get even more complex.
> > 
> > The other side of this issue is that the MGC can ask for resources
> > on the MG, and the MG can fail if there are no more resources.
> > This can be done in a way that lets the MGC either try to reroute
> > the call, or supply the appropriate error message to the caller.
> > That is why we didn't worry more about this known limitation.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, January 04, 2002 4:08 AM
> > > To: Rosen, Brian
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,
> > > Yes , It can know the resource using, But if you can't 
> > > binding all channel with Termination, How can you know the 
> > > status of left? idle or failed? 
> > > We can configure the Max number of channel and we can know 
> > > the exact number of them is busy, but we can't know the 
> > > status of spares . We can bind a termination with one 
> > > channel, and put into NULL context, Only in this case, when 
> > > one channel failed, MGW report the status to MGC .
> > > But this method , I think , is not a standard way .
> > > Why not define a explicit way to reach the aim?
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > You audit the Media descriptor of all of the terminations
> > > > to determine which terminations are employing the
> > > > codec of interest.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > Hi Brian,  All
> > > > > I agree with you on the concept of Audit capability and Audit 
> > > > > Value . But in present protocol , How can we get the 500 busy 
> > > > > through Audit value present defined, I can't find the 
> > > > > parameter or package defined the case. 
> > > > > 
> > > > > Regards
> > > > > Zhangzhong
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > > <zhangzhong@huawei.com>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on RFC2805
> > > > > 
> > > > > 
> > > > > > Audit capabilities tells you what the capabilities 
> of the system
> > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > In theory, the "1000 G.711 channel resource" comes 
> from Audit
> > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > 
> > > > > > In general, the RFC is compliant with the 
> requirements with one
> > > > > > notable exception: many gateways are implemented with 
> > > DSPs or other
> > > > > > programmable resources. There is no good way to express 
> > > capability
> > > > > > with such resources.
> > > > > > 
> > > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > > will reveal
> > > > > > that.  If 500 channels are used, Audit Value will 
> reveal that.
> > > > > > 
> > > > > > Brian
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Madhu Babu Brahmanapally 
> [mailto:madhubabu@kenetec.com]
> > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > HI Shashi,All,
> > > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > > inconsistency. But for
> > > > > > > the specific scenario Zhang has pointed, How this 
> resource 
> > > > > > > information is
> > > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > > knowledge there is no
> > > > > > > parameter or anything as such to "quantitatively" 
> identify 
> > > > > > > G711 or any such
> > > > > > > channel resource.
> > > > > > > Regards
> > > > > > > Madhubabu
> > > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: megaco-admin@ietf.org 
> > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > Shashi Kumar
> > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > To: zhangzhong
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > we have provision to audit the MG resource, which 
> > > > > clearlty defined by
> > > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > > we can always
> > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > 
> > > > > > > thanks,
> > > > > > > shashi
> > > > > > > 
> > > > > > > 
> > > > > > > > zhangzhong wrote:
> > > > > > > >
> > > > > > > > Hi :
> > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > >         Provide a mechanism to discover the current 
> > > available
> > > > > > > > resources
> > > > > > > >         in the MG, where resources are dynamically 
> > > consumed by
> > > > > > > >         connections and the MGC cannot reasonably or 
> > > > > reliably track
> > > > > > > > the
> > > > > > > >         consumption of such resources. It should also 
> > > > > be possible to
> > > > > > > >         discover resources currently in use, in order 
> > > > > to reconcile
> > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > >
> > > > > > > > This means MGC can know the resource consume in 
> the MGW , 
> > > > > > > for example
> > > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > > busy , How can
> > > > > > > > MGC know this through RFC3015?
> > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > >
> > > > > > > > Thanks for the reply.
> > > > > > > > Regards
> > > > > > > > Zhangzhong
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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


From daemon@optimus.ietf.org  Mon Jan  7 09:50:55 2002
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 JAA15999
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:50:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08140
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:50:55 -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 JAA07577;
	Mon, 7 Jan 2002 09:34:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07551
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:34:14 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15434
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:34:12 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25182;
	Mon, 7 Jan 2002 09:33:42 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA01005;
	Mon, 7 Jan 2002 09:33:27 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTWZ3>; Mon, 7 Jan 2002 09:33:26 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A1@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'zhangzhong'" <zhangzhong@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Conference Resources, was: one dount on RFC3015 as t
	o the requirement on RFC2805
Date: Mon, 7 Jan 2002 09:33:18 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

If the maximum number of terminations per context is 2, then
there is no conference resource.  If the max number of terminations
is 3, then a 3-way is possible.  If the max number is greater
than 3, then a more expansive conference is possible.

There is a conference package under discussion.  This would allow
an MGC to control a bridge.

Brian

> -----Original Message-----
> From: zhangzhong [mailto:zhangzhong@huawei.com]
> Sent: Friday, January 04, 2002 10:45 PM
> To: Rosen, Brian
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> RFC2805
> 
> 
> Hi Brian, all
> Ok, This problem will discuss later after having a way.
> Another problems, could you answer to me , thanks .
> Why not define a explicit way to apply the conference resource ?
> How can MGW know when to activate conference resource ?
> How can MGC know whether a MGW have the conference resource 
> or not? If through configuration, How does MGC maintain the 
> dynamic status of conference resource when it is bad or restrore?
> If through the max number in one context , it is no problem 
> in fixed network , but in mobiles cases, HandOver will 
> introduce more than two termination into one context.
> 
> Regards
> Zhangzhong
> 
> ----- Original Message ----- 
> From: Rosen, Brian <Brian.Rosen@marconi.com>
> To: 'zhangzhong' <zhangzhong@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Friday, January 04, 2002 9:13 PM
> Subject: RE: [Megaco] one dount on RFC3015 as to the 
> requirement on RFC2805
> 
> 
> > Because the general problem is very complex, and no one has
> > proposed a general solution that seems likely to cover most
> > cases.
> > 
> > As an example, many systems are implemented with DSPs.  These
> > systems have very complex interaction between how many codecs
> > of different types can be in use simultaneously.  A system might,
> > for example, support 16 channels of G.729, 32 channels of G.711
> > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > not simultaneously.  It may be that if you have one channel of
> > G.729, then you can support another 27 channels of G.711, and
> > if you have any G.729, then the longest tail is reduced.
> > This is because there are actually several variables at work -
> > DSP MIPs, and memory capacity, and the interaction between those
> > variables is complex.  I once discussed having a language which
> > allowed you to express this kind of thing, but it was too complex
> > for most people to deal with.  Then you add spares issues and
> > things get even more complex.
> > 
> > The other side of this issue is that the MGC can ask for resources
> > on the MG, and the MG can fail if there are no more resources.
> > This can be done in a way that lets the MGC either try to reroute
> > the call, or supply the appropriate error message to the caller.
> > That is why we didn't worry more about this known limitation.
> > 
> > Brian
> > 
> > > -----Original Message-----
> > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > Sent: Friday, January 04, 2002 4:08 AM
> > > To: Rosen, Brian
> > > Cc: megaco@ietf.org
> > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> requirement on
> > > RFC2805
> > > 
> > > 
> > > Hi Brian,
> > > Yes , It can know the resource using, But if you can't 
> > > binding all channel with Termination, How can you know the 
> > > status of left? idle or failed? 
> > > We can configure the Max number of channel and we can know 
> > > the exact number of them is busy, but we can't know the 
> > > status of spares . We can bind a termination with one 
> > > channel, and put into NULL context, Only in this case, when 
> > > one channel failed, MGW report the status to MGC .
> > > But this method , I think , is not a standard way .
> > > Why not define a explicit way to reach the aim?
> > > 
> > > Regards
> > > Zhangzhong
> > > 
> > > ----- Original Message ----- 
> > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > Cc: <megaco@ietf.org>
> > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > requirement on RFC2805
> > > 
> > > 
> > > > You audit the Media descriptor of all of the terminations
> > > > to determine which terminations are employing the
> > > > codec of interest.
> > > > 
> > > > Brian
> > > > 
> > > > > -----Original Message-----
> > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > Cc: megaco@ietf.org
> > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > requirement on
> > > > > RFC2805
> > > > > 
> > > > > 
> > > > > Hi Brian,  All
> > > > > I agree with you on the concept of Audit capability and Audit 
> > > > > Value . But in present protocol , How can we get the 500 busy 
> > > > > through Audit value present defined, I can't find the 
> > > > > parameter or package defined the case. 
> > > > > 
> > > > > Regards
> > > > > Zhangzhong
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>; 
> > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong' 
> > > > > <zhangzhong@huawei.com>
> > > > > Cc: <megaco@ietf.org>
> > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on RFC2805
> > > > > 
> > > > > 
> > > > > > Audit capabilities tells you what the capabilities 
> of the system
> > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > In theory, the "1000 G.711 channel resource" comes 
> from Audit
> > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > 
> > > > > > In general, the RFC is compliant with the 
> requirements with one
> > > > > > notable exception: many gateways are implemented with 
> > > DSPs or other
> > > > > > programmable resources. There is no good way to express 
> > > capability
> > > > > > with such resources.
> > > > > > 
> > > > > > If you have 1000 fixed G.711 channels, Audit Capability 
> > > will reveal
> > > > > > that.  If 500 channels are used, Audit Value will 
> reveal that.
> > > > > > 
> > > > > > Brian
> > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: Madhu Babu Brahmanapally 
> [mailto:madhubabu@kenetec.com]
> > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > HI Shashi,All,
> > > > > > > Its true that Audit will help MGC to reconcile the 
> > > > > > > inconsistency. But for
> > > > > > > the specific scenario Zhang has pointed, How this 
> resource 
> > > > > > > information is
> > > > > > > exchanged between the MG and the MGC. According to my 
> > > > > > > knowledge there is no
> > > > > > > parameter or anything as such to "quantitatively" 
> identify 
> > > > > > > G711 or any such
> > > > > > > channel resource.
> > > > > > > Regards
> > > > > > > Madhubabu
> > > > > > > 
> > > > > > > -----Original Message-----
> > > > > > > From: megaco-admin@ietf.org 
> > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > Shashi Kumar
> > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > To: zhangzhong
> > > > > > > Cc: megaco@ietf.org
> > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the 
> > > > > requirement on
> > > > > > > RFC2805
> > > > > > > 
> > > > > > > 
> > > > > > > we have provision to audit the MG resource, which 
> > > > > clearlty defined by
> > > > > > > Megaco/H.248. By means of Auduting the MG resources 
> > > we can always
> > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > 
> > > > > > > thanks,
> > > > > > > shashi
> > > > > > > 
> > > > > > > 
> > > > > > > > zhangzhong wrote:
> > > > > > > >
> > > > > > > > Hi :
> > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > >         Provide a mechanism to discover the current 
> > > available
> > > > > > > > resources
> > > > > > > >         in the MG, where resources are dynamically 
> > > consumed by
> > > > > > > >         connections and the MGC cannot reasonably or 
> > > > > reliably track
> > > > > > > > the
> > > > > > > >         consumption of such resources. It should also 
> > > > > be possible to
> > > > > > > >         discover resources currently in use, in order 
> > > > > to reconcile
> > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > >
> > > > > > > > This means MGC can know the resource consume in 
> the MGW , 
> > > > > > > for example
> > > > > > > > , if There have 1000 G.711 channel resource , if 500 is 
> > > > > > > busy , How can
> > > > > > > > MGC know this through RFC3015?
> > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > >
> > > > > > > > Thanks for the reply.
> > > > > > > > Regards
> > > > > > > > Zhangzhong
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > 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



From megaco-admin@ietf.org  Mon Jan  7 09:54:18 2002
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 JAA16103
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:54:18 -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 JAA07719;
	Mon, 7 Jan 2002 09:37:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07691
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:37:20 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15506
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:37:18 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25564;
	Mon, 7 Jan 2002 09:36:48 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA01659;
	Mon, 7 Jan 2002 09:36:48 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTW0H>; Mon, 7 Jan 2002 09:36:47 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A2@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Seshagiri Rao'" <rsesh@nexverse.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Megaco Interoperability
Date: Mon, 7 Jan 2002 09:36:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19788.B9D5AF60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19788.B9D5AF60
Content-Type: text/plain;
	charset="iso-8859-1"

There is not a reference design available.
There are test scenarios developed for the bakeoffs.  These explicitly DO
NOT
include message sequences.
I have been stalling on scheduling another bakeoff until we had better
participation.
  I plan to "call the question" again soon
Virtually all implementations are text only.  A few are both (a very few).
I don't
know of any that are binary only.
 
Brian

-----Original Message-----
From: Seshagiri Rao [mailto:rsesh@nexverse.com]
Sent: Saturday, January 05, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Megaco Interoperability



All: 

I would like to know if there is any reference design/test sequence for
Megaco stack implementation. 
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh 


------_=_NextPart_001_01C19788.B9D5AF60
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Megaco Interoperability</TITLE>

<META content="MSHTML 6.00.2712.300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>There is not 
a reference design available.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>There are 
test scenarios developed for the bakeoffs.&nbsp; These explicitly DO 
NOT</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>include 
message sequences.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>I have been 
stalling on scheduling another bakeoff until we had better 
participation.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>&nbsp; I plan 
to "call the question" again soon</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>Virtually all 
implementations are text only.&nbsp; A few are both (a very few).&nbsp; I 
don't</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>know of any 
that are binary only.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial 
color=#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial 
color=#0000ff>Brian</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Seshagiri Rao 
  [mailto:rsesh@nexverse.com]<BR><B>Sent:</B> Saturday, January 05, 2002 6:58 
  PM<BR><B>To:</B> 'megaco@ietf.org'<BR><B>Subject:</B> [Megaco] Megaco 
  Interoperability<BR><BR></FONT></DIV>
  <P><FONT size=2>All:</FONT> </P>
  <P><FONT size=2>I would like to know if there is any reference design/test 
  sequence for Megaco stack implementation.</FONT> <BR><FONT size=2>I would also 
  like to know if there is any forthcoming interop/bake-off event.&nbsp; 
  </FONT><BR><FONT size=2>How many of the current Megaco stack implementations 
  support ABNF/Text encoding and how many support ASN.1/binary 
  encoding?</FONT></P>
  <P><FONT size=2>Sesh</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C19788.B9D5AF60--

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


From daemon@optimus.ietf.org  Mon Jan  7 09:54:20 2002
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 JAA16117
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:54:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08179
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:54:20 -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 JAA07719;
	Mon, 7 Jan 2002 09:37:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07691
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:37:20 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15506
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:37:18 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA25564;
	Mon, 7 Jan 2002 09:36:48 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA01659;
	Mon, 7 Jan 2002 09:36:48 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTW0H>; Mon, 7 Jan 2002 09:36:47 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A2@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Seshagiri Rao'" <rsesh@nexverse.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Megaco Interoperability
Date: Mon, 7 Jan 2002 09:36:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19788.B9D5AF60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19788.B9D5AF60
Content-Type: text/plain;
	charset="iso-8859-1"

There is not a reference design available.
There are test scenarios developed for the bakeoffs.  These explicitly DO
NOT
include message sequences.
I have been stalling on scheduling another bakeoff until we had better
participation.
  I plan to "call the question" again soon
Virtually all implementations are text only.  A few are both (a very few).
I don't
know of any that are binary only.
 
Brian

-----Original Message-----
From: Seshagiri Rao [mailto:rsesh@nexverse.com]
Sent: Saturday, January 05, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Megaco Interoperability



All: 

I would like to know if there is any reference design/test sequence for
Megaco stack implementation. 
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh 


------_=_NextPart_001_01C19788.B9D5AF60
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Megaco Interoperability</TITLE>

<META content="MSHTML 6.00.2712.300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>There is not 
a reference design available.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>There are 
test scenarios developed for the bakeoffs.&nbsp; These explicitly DO 
NOT</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>include 
message sequences.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>I have been 
stalling on scheduling another bakeoff until we had better 
participation.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>&nbsp; I plan 
to "call the question" again soon</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>Virtually all 
implementations are text only.&nbsp; A few are both (a very few).&nbsp; I 
don't</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial color=#0000ff>know of any 
that are binary only.</FONT></SPAN></DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial 
color=#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=247423214-07012002><FONT face=Arial 
color=#0000ff>Brian</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Seshagiri Rao 
  [mailto:rsesh@nexverse.com]<BR><B>Sent:</B> Saturday, January 05, 2002 6:58 
  PM<BR><B>To:</B> 'megaco@ietf.org'<BR><B>Subject:</B> [Megaco] Megaco 
  Interoperability<BR><BR></FONT></DIV>
  <P><FONT size=2>All:</FONT> </P>
  <P><FONT size=2>I would like to know if there is any reference design/test 
  sequence for Megaco stack implementation.</FONT> <BR><FONT size=2>I would also 
  like to know if there is any forthcoming interop/bake-off event.&nbsp; 
  </FONT><BR><FONT size=2>How many of the current Megaco stack implementations 
  support ABNF/Text encoding and how many support ASN.1/binary 
  encoding?</FONT></P>
  <P><FONT size=2>Sesh</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C19788.B9D5AF60--

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



From megaco-admin@ietf.org  Mon Jan  7 09:56:17 2002
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 JAA16166
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:56: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 JAA07877;
	Mon, 7 Jan 2002 09:40:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07849
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:40:34 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15645
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:40:33 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA26014;
	Mon, 7 Jan 2002 09:40:03 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA02679;
	Mon, 7 Jan 2002 09:40:03 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTX2R>; Mon, 7 Jan 2002 09:39:59 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A3@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Raphael Tryster'"
	 <raphael@tdsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] precise identification of an incoming call
Date: Mon, 7 Jan 2002 09:39:57 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I second this.  DO NOT assume anything.

The question itself makes me nervous.  In general, the MG is a slave,
and slaves never make assumptions about anything.  The MG should
not even have any notion of a "call".  It only deals with
events, signals, properties, and streams of media.

Brian

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Monday, January 07, 2002 9:21 AM
> To: 'Raphael Tryster'; megaco@ietf.org
> Subject: RE: [Megaco] precise identification of an incoming call
> 
> 
> You may be correct, but my agreement is because no 
> counter-examples come
> immediately to mind.  I wouldn't design equipment on this 
> assumption.  There
> may be some call flow where it makes sense to modify the 
> second subscriber's
> termination while it is still in the null context.
> 
> 
> -----Original Message-----
> From: Raphael Tryster [mailto:raphael@tdsoft.com]
> Sent: Monday, January 07, 2002 7:03 AM
> To: megaco@ietf.org
> Subject: [Megaco] precise identification of an incoming call
> 
> 
> In the example call flow given in RFC 3015 Appendix A, the 
> incoming call to
> the second subscriber begins with an ADD command from MGC to 
> MG2 in step 14.
> Is this the only way an incoming call can begin?  In other 
> words, can the MG
> assume the MGC will not send it any other commands related to 
> an incoming
> call before the ADD?
> 
> 
> Raphael Tryster 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Mon Jan  7 09:56:18 2002
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 JAA16179
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 09:56:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08223
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 09:56:18 -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 JAA07877;
	Mon, 7 Jan 2002 09:40:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07849
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 09:40:34 -0500 (EST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15645
	for <megaco@ietf.org>; Mon, 7 Jan 2002 09:40:33 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA26014;
	Mon, 7 Jan 2002 09:40:03 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA02679;
	Mon, 7 Jan 2002 09:40:03 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <C24FTX2R>; Mon, 7 Jan 2002 09:39:59 -0500
Message-ID: <313680C9A886D511A06000204840E1CF57C7A3@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'Raphael Tryster'"
	 <raphael@tdsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] precise identification of an incoming call
Date: Mon, 7 Jan 2002 09:39:57 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I second this.  DO NOT assume anything.

The question itself makes me nervous.  In general, the MG is a slave,
and slaves never make assumptions about anything.  The MG should
not even have any notion of a "call".  It only deals with
events, signals, properties, and streams of media.

Brian

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Monday, January 07, 2002 9:21 AM
> To: 'Raphael Tryster'; megaco@ietf.org
> Subject: RE: [Megaco] precise identification of an incoming call
> 
> 
> You may be correct, but my agreement is because no 
> counter-examples come
> immediately to mind.  I wouldn't design equipment on this 
> assumption.  There
> may be some call flow where it makes sense to modify the 
> second subscriber's
> termination while it is still in the null context.
> 
> 
> -----Original Message-----
> From: Raphael Tryster [mailto:raphael@tdsoft.com]
> Sent: Monday, January 07, 2002 7:03 AM
> To: megaco@ietf.org
> Subject: [Megaco] precise identification of an incoming call
> 
> 
> In the example call flow given in RFC 3015 Appendix A, the 
> incoming call to
> the second subscriber begins with an ADD command from MGC to 
> MG2 in step 14.
> Is this the only way an incoming call can begin?  In other 
> words, can the MG
> assume the MGC will not send it any other commands related to 
> an incoming
> call before the ADD?
> 
> 
> Raphael Tryster 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Mon Jan  7 10:32:52 2002
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 KAA17337
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 10:32:52 -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 KAA08851;
	Mon, 7 Jan 2002 10:12:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08820
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 10:12:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16592
	for <megaco@ietf.org>; Mon, 7 Jan 2002 10:12:31 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07FBwA29467;
	Mon, 7 Jan 2002 10:11:58 -0500 (EST)
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 g07FBtM03517;
	Mon, 7 Jan 2002 10:11:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPRK9WGP>; Mon, 7 Jan 2002 10:10:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor
Date: Mon, 7 Jan 2002 09:58:31 -0500 
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

Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan  7 10:32:53 2002
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 KAA17347
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 10:32:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09655
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 10:32:54 -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 KAA08851;
	Mon, 7 Jan 2002 10:12:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08820
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 10:12:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16592
	for <megaco@ietf.org>; Mon, 7 Jan 2002 10:12:31 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g07FBwA29467;
	Mon, 7 Jan 2002 10:11:58 -0500 (EST)
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 g07FBtM03517;
	Mon, 7 Jan 2002 10:11:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPRK9WGP>; Mon, 7 Jan 2002 10:10:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor
Date: Mon, 7 Jan 2002 09:58:31 -0500 
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

Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan  7 10:55:13 2002
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 KAA18163
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 10:55:13 -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 KAA09874;
	Mon, 7 Jan 2002 10:38:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09837
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 10:38:25 -0500 (EST)
Received: from mtiwmhc25.worldnet.att.net (mtiwmhc25.worldnet.att.net [204.127.131.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17510
	for <megaco@ietf.org>; Mon, 7 Jan 2002 10:38:23 -0500 (EST)
Received: from varneyhome.ieee.org ([12.84.122.105])
          by mtiwmhc25.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020107153755.YGFB15547.mtiwmhc25.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Mon, 7 Jan 2002 15:37:55 +0000
Message-Id: <4.3.2.7.2.20020107090529.00b46c80@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 Jan 2002 09:37:05 -0600
To: megaco@ietf.org
From: Al Varney <varney@ieee.org>
Subject: RE: [Megaco] precise identification of an incoming call
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADD9@zcard0kc.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 09:21 AM 1/7/02 -0500, Tom-PT Taylor wrote:
>You may be correct, but my agreement is because no counter-examples come
>immediately to mind.  I wouldn't design equipment on this assumption.  There
>may be some call flow where it makes sense to modify the second subscriber's
>termination while it is still in the null context.
>
>From: Raphael Tryster [mailto:raphael@tdsoft.com]
>
>>In the example call flow given in RFC 3015 Appendix A, the incoming call to
>>the second subscriber begins with an ADD command from MGC to MG2 in step 14.
>>Is this the only way an incoming call can begin?  In other words, can the MG
>>assume the MGC will not send it any other commands related to an incoming
>>call before the ADD?

    Given the low-level, device-control nature of MEGACO/H.248, I've found 
it easier to understand MG functionality by assuming the MG knows nothing 
about "calls".  An MG is a device for making connections -- a higher layer 
(the MGC) is where the concept of calls beginning/ending or 
incoming/outgoing takes place.  You could even imagine applications where 
MEGACO is used to control non-call-related connections (Public Address 
announcements, for example).

    Rephrased in connection terms, you could ask if any commands related to 
a new connection (in or out) occurs prior to an ADD.  The answer to that 
requires defining when a "connection" begins to exist; that is, can a 
connection exist prior to ADD?  If it can, then presumably some non-ADD 
command created it.  (Move from another context would not be a "new" 
connection.)

    Back to your call-level question (commands before ADD):  Well, the 
whole notify/event mechanism could occur multiple times in the null context 
before a "connection" is created.  An incoming call might have only an 
outgoing connection (MG-based dial tone on an ISDN B-channel connection) at 
the beginning of an incoming ISDN voice call.  An IP Phone might have some 
local signal (dial tone) turned on via MEGACO prior to a connection being 
ADDed (although ADDing early would be a way to reserve resources for the 
call).  I think it likely other pre-ADD scenarios exist.

    This is just my own opinion and my attempt at trying to keep 
"device-control" protocols separated from "call-control" protocols.  It 
could be all wrong.  I do know it's been difficult trying to avoid thinking 
in terms of "calls".

Al Varney


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


From daemon@optimus.ietf.org  Mon Jan  7 10:55:14 2002
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 KAA18173
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 10:55:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10525
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 10:55:15 -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 KAA09874;
	Mon, 7 Jan 2002 10:38:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09837
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 10:38:25 -0500 (EST)
Received: from mtiwmhc25.worldnet.att.net (mtiwmhc25.worldnet.att.net [204.127.131.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17510
	for <megaco@ietf.org>; Mon, 7 Jan 2002 10:38:23 -0500 (EST)
Received: from varneyhome.ieee.org ([12.84.122.105])
          by mtiwmhc25.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020107153755.YGFB15547.mtiwmhc25.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Mon, 7 Jan 2002 15:37:55 +0000
Message-Id: <4.3.2.7.2.20020107090529.00b46c80@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 Jan 2002 09:37:05 -0600
To: megaco@ietf.org
From: Al Varney <varney@ieee.org>
Subject: RE: [Megaco] precise identification of an incoming call
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADD9@zcard0kc.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 09:21 AM 1/7/02 -0500, Tom-PT Taylor wrote:
>You may be correct, but my agreement is because no counter-examples come
>immediately to mind.  I wouldn't design equipment on this assumption.  There
>may be some call flow where it makes sense to modify the second subscriber's
>termination while it is still in the null context.
>
>From: Raphael Tryster [mailto:raphael@tdsoft.com]
>
>>In the example call flow given in RFC 3015 Appendix A, the incoming call to
>>the second subscriber begins with an ADD command from MGC to MG2 in step 14.
>>Is this the only way an incoming call can begin?  In other words, can the MG
>>assume the MGC will not send it any other commands related to an incoming
>>call before the ADD?

    Given the low-level, device-control nature of MEGACO/H.248, I've found 
it easier to understand MG functionality by assuming the MG knows nothing 
about "calls".  An MG is a device for making connections -- a higher layer 
(the MGC) is where the concept of calls beginning/ending or 
incoming/outgoing takes place.  You could even imagine applications where 
MEGACO is used to control non-call-related connections (Public Address 
announcements, for example).

    Rephrased in connection terms, you could ask if any commands related to 
a new connection (in or out) occurs prior to an ADD.  The answer to that 
requires defining when a "connection" begins to exist; that is, can a 
connection exist prior to ADD?  If it can, then presumably some non-ADD 
command created it.  (Move from another context would not be a "new" 
connection.)

    Back to your call-level question (commands before ADD):  Well, the 
whole notify/event mechanism could occur multiple times in the null context 
before a "connection" is created.  An incoming call might have only an 
outgoing connection (MG-based dial tone on an ISDN B-channel connection) at 
the beginning of an incoming ISDN voice call.  An IP Phone might have some 
local signal (dial tone) turned on via MEGACO prior to a connection being 
ADDed (although ADDing early would be a way to reserve resources for the 
call).  I think it likely other pre-ADD scenarios exist.

    This is just my own opinion and my attempt at trying to keep 
"device-control" protocols separated from "call-control" protocols.  It 
could be all wrong.  I do know it's been difficult trying to avoid thinking 
in terms of "calls".

Al Varney


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



From megaco-admin@ietf.org  Mon Jan  7 16:56:27 2002
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 QAA29158
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 16:56:27 -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 QAA22559;
	Mon, 7 Jan 2002 16:42:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22525
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 16:42:01 -0500 (EST)
Received: from webmail.pi.se (webmail.pi.se [195.7.65.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28772
	for <megaco@ietf.org>; Mon, 7 Jan 2002 16:41:57 -0500 (EST)
Received: (from www-data@localhost)
	by webmail.pi.se (8.11.6/8.11.1) id g07LYe451258;
	Mon, 7 Jan 2002 22:34:40 +0100 (CET)
	(envelope-from gunnar.hellstrom@omnitor.se)
X-Authentication-Warning: webmail.pi.se: www-data set sender to gunnar.hellstrom@omnitor.se using -f
To: Tom-PT Taylor <taylor@nortelnetworks.com>
Subject: RE: [Megaco] Use of Modem descriptor
Message-ID: <1010439280.3c3a1470d5c32@webmail.pi.se>
Date: Mon, 07 Jan 2002 22:34:40 +0100 (CET)
From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
Cc: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org,
        madhubabu@kenetec.com
References: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Cable & Wireless - pi.se webmail http://www.pi.se (IMP 2.2.3)
Content-Transfer-Encoding: 8bit
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

Hi,
For H.324, I would expect that you use the V.8 bis negotiation in the ctyp 
package of  H.324 Annex F so that you can respond properly to all the V.8 bis 
parameters required by H.324.

( same if the H.324 make use of the non-preferred V.8 negotiation )

After that, you signal to the MGC that you have discriminated an H.324 calling 
in and the MGC takes action and sets up corresponding call and stream and 
activates multiplexing.

Regards
Gunnar Hellström.



Quoting Tom-PT Taylor <taylor@nortelnetworks.com>:

> Sorry about the previous non-reply.  When trying for
> "File/Properties/Send
> Options" to make sure the message goes out as text, I sometimes get
> distracted by the "Send" button immediately below the File menu item.
> 
> Anyway, I assume you are talking about a situation where someone is
> running
> an H.324 session over a modem connection -- this is the only example I
> can
> think of that would require both descriptors.  There are a few other
> assumptions one must make about how the MGC knows it's an H.324 call,
> but I
> can visualize one or two scenarios where this might be so.  In any
> event,
> the specification is straightforward:
> 
> Add=MuxedTerm{
>   Modem=V.34,
>   Mux=H.223 {LineTerm},
>   etc.
> 
> Here MuxedTerm is the ephemeral termination being created to represent
> the
> H.324 session, and LineTerm is the physical analogue line termination
> supporting it.  The original H.324 specification is based on use of a
> V.34
> modem.  I can't recall if that has been extended to V.90.  H.223 is
> the
> H.324 multiplex.
> 
> 
> 
> -----Original Message-----
> From: gokulc [mailto:gokulc@future.futsoft.com]
> Sent: Monday, January 07, 2002 8:20 AM
> To: megaco@ietf.org
> Cc: madhubabu@kenetec.com
> Subject: [Megaco] Use of Modem descriptor
> 
> 
> Hi,
> 
> When a add/move/modify command with the modem descriptor is issued,
> the MG connects the appropriate modem from the free resource pool to
> the
> addressed termination in the command.
> 
> Add = Term1{
> 	Modem = V90
> 	....
> }
> 
> It is my understanding that the Term1 is not the identification of the
> modem, but
> that of the line/trunk termination.
> 
> On the same lines how is a mux resource handled...
> 
> gokul
> 
> 
> _______________________________________________
> 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
> 
> 



************************
Gunnar Hellström
Omnitor AB
+46 708 204 288
gunnar.hellstrom@omnitor.se
www.omnitor.se
*********************************

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


From daemon@optimus.ietf.org  Mon Jan  7 16:56:28 2002
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 QAA29166
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jan 2002 16:56:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA22898
	for megaco-archive@odin.ietf.org; Mon, 7 Jan 2002 16:56:29 -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 QAA22559;
	Mon, 7 Jan 2002 16:42:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22525
	for <megaco@optimus.ietf.org>; Mon, 7 Jan 2002 16:42:01 -0500 (EST)
Received: from webmail.pi.se (webmail.pi.se [195.7.65.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28772
	for <megaco@ietf.org>; Mon, 7 Jan 2002 16:41:57 -0500 (EST)
Received: (from www-data@localhost)
	by webmail.pi.se (8.11.6/8.11.1) id g07LYe451258;
	Mon, 7 Jan 2002 22:34:40 +0100 (CET)
	(envelope-from gunnar.hellstrom@omnitor.se)
X-Authentication-Warning: webmail.pi.se: www-data set sender to gunnar.hellstrom@omnitor.se using -f
To: Tom-PT Taylor <taylor@nortelnetworks.com>
Subject: RE: [Megaco] Use of Modem descriptor
Message-ID: <1010439280.3c3a1470d5c32@webmail.pi.se>
Date: Mon, 07 Jan 2002 22:34:40 +0100 (CET)
From: =?ISO-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
Cc: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org,
        madhubabu@kenetec.com
References: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Cable & Wireless - pi.se webmail http://www.pi.se (IMP 2.2.3)
Content-Transfer-Encoding: 8bit
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

Hi,
For H.324, I would expect that you use the V.8 bis negotiation in the ctyp 
package of  H.324 Annex F so that you can respond properly to all the V.8 bis 
parameters required by H.324.

( same if the H.324 make use of the non-preferred V.8 negotiation )

After that, you signal to the MGC that you have discriminated an H.324 calling 
in and the MGC takes action and sets up corresponding call and stream and 
activates multiplexing.

Regards
Gunnar Hellström.



Quoting Tom-PT Taylor <taylor@nortelnetworks.com>:

> Sorry about the previous non-reply.  When trying for
> "File/Properties/Send
> Options" to make sure the message goes out as text, I sometimes get
> distracted by the "Send" button immediately below the File menu item.
> 
> Anyway, I assume you are talking about a situation where someone is
> running
> an H.324 session over a modem connection -- this is the only example I
> can
> think of that would require both descriptors.  There are a few other
> assumptions one must make about how the MGC knows it's an H.324 call,
> but I
> can visualize one or two scenarios where this might be so.  In any
> event,
> the specification is straightforward:
> 
> Add=MuxedTerm{
>   Modem=V.34,
>   Mux=H.223 {LineTerm},
>   etc.
> 
> Here MuxedTerm is the ephemeral termination being created to represent
> the
> H.324 session, and LineTerm is the physical analogue line termination
> supporting it.  The original H.324 specification is based on use of a
> V.34
> modem.  I can't recall if that has been extended to V.90.  H.223 is
> the
> H.324 multiplex.
> 
> 
> 
> -----Original Message-----
> From: gokulc [mailto:gokulc@future.futsoft.com]
> Sent: Monday, January 07, 2002 8:20 AM
> To: megaco@ietf.org
> Cc: madhubabu@kenetec.com
> Subject: [Megaco] Use of Modem descriptor
> 
> 
> Hi,
> 
> When a add/move/modify command with the modem descriptor is issued,
> the MG connects the appropriate modem from the free resource pool to
> the
> addressed termination in the command.
> 
> Add = Term1{
> 	Modem = V90
> 	....
> }
> 
> It is my understanding that the Term1 is not the identification of the
> modem, but
> that of the line/trunk termination.
> 
> On the same lines how is a mux resource handled...
> 
> gokul
> 
> 
> _______________________________________________
> 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
> 
> 



************************
Gunnar Hellström
Omnitor AB
+46 708 204 288
gunnar.hellstrom@omnitor.se
www.omnitor.se
*********************************

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



From megaco-admin@ietf.org  Tue Jan  8 00:07:18 2002
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 AAA07205
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 00:07:18 -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 XAA04998;
	Mon, 7 Jan 2002 23:50:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04932
	for <megaco@ns.ietf.org>; Mon, 7 Jan 2002 23:50:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07076
	for <megaco@ietf.org>; Mon, 7 Jan 2002 23:50:33 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA07883;
	Tue, 8 Jan 2002 15:49:11 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA01238;
	Tue, 8 Jan 2002 15:50:27 +1100 (EST)
Message-ID: <3C3A5CFF.D95BC178@ericsson.com.au>
Date: Tue, 08 Jan 2002 13:44:15 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Roy, Radhika R, ALCTA" <rrroy@att.com>
CC: Kevin Boyle <kboyle@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: Re: [Megaco] Inter-MGC Communication
References: <62DA45D4963FA747BA1B253E266760F9FF52E5@OCCLUST04EVS1.ugd.att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Roy,

There is some work ongoing in ITU SG11 to define mapping between BICC
1902.x and Q.1950 which is based on H.248.

Regards, Christian

"Roy, Radhika R, ALCTA" wrote:
> 
> Hi, Kevin:
> 
> I beg to disagree with you here.
> 
> The decomposition of the GWs has been done to have other benefits as well. For example, MGCs from one vendor, while MGs from other vendors.
> 
> What do we expect in those situations? Do the service providers be forced to lock into proprietary solutions/implementations?
> 
> I understand the problems that MEGACO WG may not be chartered to address those issues. That does not mean we should NOT be worried about those issues. MEGACO WG has done its primary job and it is a very proud achievement (in standardizing the MEGACO protocol). As we move forward, we have to see how the industry can reap the benefits in implementing the large-scale networks in multi-vendor and multi-protocol environment using the MEGACO protocol.
> 
> Since the MEGACO protocol is standardized, now, we have the luxury to go for the next step: Interoperability in multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor environment using the MEGACO protocol. Not only that, it is also applicable for all transport networks (PSTN, IP, ATM, FR). I feel that MEGACO is providing a wonderful GLUE to solve these complex problems what could not even be imagined couples of years ago.
> 
> Best regards,
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
> Sent: Thursday, January 03, 2002 1:12 PM
> To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> As Brian stated, the translation is internal to a single entity (in this case, the MGC).  I don't see a problem here, just as I don't see a problem with different MGCs having different internal hardware.  Think "black box".  If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or SIP or whatever on the other), then why worry about the translation?  If the translation is not correct, for whatever reason, then the vendor will surely figure that out and correct it, or their product will not sell!
> 
> Kevin
> 
> -----Original Message-----
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 11:40 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> ...
> 
> I suspect there is not a single exact
> mapping.
> 
> [RRR] This is the problem. Should people like to live with this?
> 
> Brian
> 
> > -----Original Message-----
> > From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com]
> > Sent: Thursday, January 03, 2002 10:27 AM
> > To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> > Subject: RE: [Megaco] Inter-MGC Communication
> >
> >
> > Hi, Brian:
> >
> > You are right.
> >
> > What could have been better if we could have a document, like
> > Madhubabu's call flows, how the mapping is done as Tom Taylor
> > has indicated. For example, the scenarios can be as follows:
> >
> >       MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> >        ^                                                 ^
> >        |                                                 |
> >      MEGACO/MGCP                              MEGACO/MGCP
> >        |                                                 |
> >        v                                                 v
> >       MG  <---------- RTP ---------------->  MG
> >
> > Now the appropriate mapping needs to be done between H.323
> > (H.225.0, H.245) and MEGACO (or MGCP). This part is missing
> > and no documentation is available. If this is done, people
> > could have interoperable implementations.
> >
> > Similarly, the scenarios can be created for SIP and BICC and,
> > mappings need to be done as follows:
> >
> > SIP/SDP <-> MEGACO (or MGCP)
> > BICC  <-> MEGACO (or MGCP)
> >
> > Best regards,
> >
> > Radhika R. Roy
> > rrroy@att.com
> >
> > -----Original Message-----
> > From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com]
> > Sent: Thursday, January 03, 2002 9:25 AM
> > To: 'asrar ashraf'; megaco@ietf.org
> > Subject: RE: [Megaco] Inter-MGC Communication
> >
> >
> > Neither RFC3015 nor Recommendation H.248 say anything about
> > interMGC communication.  It is out of scope of the protocol.
> > You can use anything you would like.  SIP/SIP-T works, but so
> > does BICC or even H.323.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: asrar ashraf [ mailto:asrar@enabtech.com]
> > > Sent: Thursday, January 03, 2002 2:18 AM
> > > To: megaco@ietf.org
> > > Subject: [Megaco] Inter-MGC Communication
> > >
> > >
> > > Can Any one confirm that
> > > Only SIP or SIP-T is used for Inter-MGC Communication.
> > >  What about other options.
> > > Can any one guide If There are any callFlows available for Inte-MGC
> > > communication ...
> > >
> > >   regards
> > >  Asrar Ashraf
> > >  AvazNetworks
> > >  Islamabad, Pakistan
> > >
> >
> > _______________________________________________
> > 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


From daemon@ns.ietf.org  Tue Jan  8 00:07:18 2002
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 AAA07214
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 00:07:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA05890
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 00:07: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 XAA04998;
	Mon, 7 Jan 2002 23:50:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04932
	for <megaco@ns.ietf.org>; Mon, 7 Jan 2002 23:50:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07076
	for <megaco@ietf.org>; Mon, 7 Jan 2002 23:50:33 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA07883;
	Tue, 8 Jan 2002 15:49:11 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA01238;
	Tue, 8 Jan 2002 15:50:27 +1100 (EST)
Message-ID: <3C3A5CFF.D95BC178@ericsson.com.au>
Date: Tue, 08 Jan 2002 13:44:15 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Roy, Radhika R, ALCTA" <rrroy@att.com>
CC: Kevin Boyle <kboyle@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        asrar ashraf <asrar@enabtech.com>, megaco@ietf.org
Subject: Re: [Megaco] Inter-MGC Communication
References: <62DA45D4963FA747BA1B253E266760F9FF52E5@OCCLUST04EVS1.ugd.att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Roy,

There is some work ongoing in ITU SG11 to define mapping between BICC
1902.x and Q.1950 which is based on H.248.

Regards, Christian

"Roy, Radhika R, ALCTA" wrote:
> 
> Hi, Kevin:
> 
> I beg to disagree with you here.
> 
> The decomposition of the GWs has been done to have other benefits as well. For example, MGCs from one vendor, while MGs from other vendors.
> 
> What do we expect in those situations? Do the service providers be forced to lock into proprietary solutions/implementations?
> 
> I understand the problems that MEGACO WG may not be chartered to address those issues. That does not mean we should NOT be worried about those issues. MEGACO WG has done its primary job and it is a very proud achievement (in standardizing the MEGACO protocol). As we move forward, we have to see how the industry can reap the benefits in implementing the large-scale networks in multi-vendor and multi-protocol environment using the MEGACO protocol.
> 
> Since the MEGACO protocol is standardized, now, we have the luxury to go for the next step: Interoperability in multiprotocol (SIP, H.323, BICC, ISUP) and multi-vendor environment using the MEGACO protocol. Not only that, it is also applicable for all transport networks (PSTN, IP, ATM, FR). I feel that MEGACO is providing a wonderful GLUE to solve these complex problems what could not even be imagined couples of years ago.
> 
> Best regards,
> Radhika R. Roy
> rrroy@att.com
> 
> -----Original Message-----
> From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
> Sent: Thursday, January 03, 2002 1:12 PM
> To: Roy, Radhika R, ALCTA; Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> As Brian stated, the translation is internal to a single entity (in this case, the MGC).  I don't see a problem here, just as I don't see a problem with different MGCs having different internal hardware.  Think "black box".  If the external interfaces are OK (H.248/Megaco on the one hand, and BICC or SIP or whatever on the other), then why worry about the translation?  If the translation is not correct, for whatever reason, then the vendor will surely figure that out and correct it, or their product will not sell!
> 
> Kevin
> 
> -----Original Message-----
> From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com]
> Sent: Thursday, January 03, 2002 11:40 AM
> To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> Subject: RE: [Megaco] Inter-MGC Communication
> 
> ...
> 
> I suspect there is not a single exact
> mapping.
> 
> [RRR] This is the problem. Should people like to live with this?
> 
> Brian
> 
> > -----Original Message-----
> > From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com]
> > Sent: Thursday, January 03, 2002 10:27 AM
> > To: Rosen, Brian; asrar ashraf; megaco@ietf.org
> > Subject: RE: [Megaco] Inter-MGC Communication
> >
> >
> > Hi, Brian:
> >
> > You are right.
> >
> > What could have been better if we could have a document, like
> > Madhubabu's call flows, how the mapping is done as Tom Taylor
> > has indicated. For example, the scenarios can be as follows:
> >
> >       MGC  <--- H.323 (H.225.0, H.245) ---> MGC
> >        ^                                                 ^
> >        |                                                 |
> >      MEGACO/MGCP                              MEGACO/MGCP
> >        |                                                 |
> >        v                                                 v
> >       MG  <---------- RTP ---------------->  MG
> >
> > Now the appropriate mapping needs to be done between H.323
> > (H.225.0, H.245) and MEGACO (or MGCP). This part is missing
> > and no documentation is available. If this is done, people
> > could have interoperable implementations.
> >
> > Similarly, the scenarios can be created for SIP and BICC and,
> > mappings need to be done as follows:
> >
> > SIP/SDP <-> MEGACO (or MGCP)
> > BICC  <-> MEGACO (or MGCP)
> >
> > Best regards,
> >
> > Radhika R. Roy
> > rrroy@att.com
> >
> > -----Original Message-----
> > From: Rosen, Brian [ mailto:Brian.Rosen@marconi.com]
> > Sent: Thursday, January 03, 2002 9:25 AM
> > To: 'asrar ashraf'; megaco@ietf.org
> > Subject: RE: [Megaco] Inter-MGC Communication
> >
> >
> > Neither RFC3015 nor Recommendation H.248 say anything about
> > interMGC communication.  It is out of scope of the protocol.
> > You can use anything you would like.  SIP/SIP-T works, but so
> > does BICC or even H.323.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: asrar ashraf [ mailto:asrar@enabtech.com]
> > > Sent: Thursday, January 03, 2002 2:18 AM
> > > To: megaco@ietf.org
> > > Subject: [Megaco] Inter-MGC Communication
> > >
> > >
> > > Can Any one confirm that
> > > Only SIP or SIP-T is used for Inter-MGC Communication.
> > >  What about other options.
> > > Can any one guide If There are any callFlows available for Inte-MGC
> > > communication ...
> > >
> > >   regards
> > >  Asrar Ashraf
> > >  AvazNetworks
> > >  Islamabad, Pakistan
> > >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Tue Jan  8 00:08:46 2002
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 AAA07236
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 00:08:46 -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 XAA05000;
	Mon, 7 Jan 2002 23:50:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04934
	for <megaco@ns.ietf.org>; Mon, 7 Jan 2002 23:50:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07077
	for <megaco@ietf.org>; Mon, 7 Jan 2002 23:50:33 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA07893;
	Tue, 8 Jan 2002 15:49:14 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA01252;
	Tue, 8 Jan 2002 15:50:31 +1100 (EST)
Message-ID: <3C3A5E35.7F66E746@ericsson.com.au>
Date: Tue, 08 Jan 2002 13:49:25 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'zhangzhong'" <zhangzhong@huawei.com>, megaco@ietf.org
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
References: <313680C9A886D511A06000204840E1CF57C7A0@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

In terms of congestion of resources there is already a package that can
be used to indicate when a MG is congested. There is also some work
ongoing in SG16 to further refine the resource congestion handling
perhaps this work can also address individual resources.

Christian

"Rosen, Brian" wrote:
> 
> Well, the door is, at least in theory, open to add features in
> V2.  I actually oppose doing this, but there are some who feel
> that tinkering with the protocol before there is any substantial
> deployment experience is a good idea.
> 
> You could propose a solution.  If you do, I think you would want
> to see if it works for a wide variety of resource models that MGs
> might implement, and yet be simple enough that a really small
> phone or gateway could implement it without a lot of code.
> 
> The answer to your question is that if the MGC knows the MG has
> a capability for something, but gets an error when it tries to
> use it, then it could, when a future requirement arises for that
> capability, ask for it again.  It will either work, or fail
> again.  No need to poll.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 10:40 PM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > Hi Brian, all
> > Yes , It has problems about this. I think there should have
> > some methods resolving them.
> > And If we can't resolve these problems, There will introduce
> > more difficulity of interworking between different company's
> > product  and low the efficiency of network.
> > Problems:
> > MGW can reject the resource command from MGC, OK, It is no
> > problems. But how MGC know the resource in this MGW is
> > available again?  We can  setup a flag , and apply the
> > request periodicly, when success, reset the flag, or start a
> > timer , after the timer time out , reset the flag. etc.
> > All these methods will introcude much traffic between MGC and
> > MGW. It is not good for the network resource management in the MGC.
> >
> > Regards
> > Zhangzhong
> >
> >
> >
> > ----- Original Message -----
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, January 04, 2002 9:13 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > requirement on RFC2805
> >
> >
> > > Because the general problem is very complex, and no one has
> > > proposed a general solution that seems likely to cover most
> > > cases.
> > >
> > > As an example, many systems are implemented with DSPs.  These
> > > systems have very complex interaction between how many codecs
> > > of different types can be in use simultaneously.  A system might,
> > > for example, support 16 channels of G.729, 32 channels of G.711
> > > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > > not simultaneously.  It may be that if you have one channel of
> > > G.729, then you can support another 27 channels of G.711, and
> > > if you have any G.729, then the longest tail is reduced.
> > > This is because there are actually several variables at work -
> > > DSP MIPs, and memory capacity, and the interaction between those
> > > variables is complex.  I once discussed having a language which
> > > allowed you to express this kind of thing, but it was too complex
> > > for most people to deal with.  Then you add spares issues and
> > > things get even more complex.
> > >
> > > The other side of this issue is that the MGC can ask for resources
> > > on the MG, and the MG can fail if there are no more resources.
> > > This can be done in a way that lets the MGC either try to reroute
> > > the call, or supply the appropriate error message to the caller.
> > > That is why we didn't worry more about this known limitation.
> > >
> > > Brian
> > >
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, January 04, 2002 4:08 AM
> > > > To: Rosen, Brian
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > requirement on
> > > > RFC2805
> > > >
> > > >
> > > > Hi Brian,
> > > > Yes , It can know the resource using, But if you can't
> > > > binding all channel with Termination, How can you know the
> > > > status of left? idle or failed?
> > > > We can configure the Max number of channel and we can know
> > > > the exact number of them is busy, but we can't know the
> > > > status of spares . We can bind a termination with one
> > > > channel, and put into NULL context, Only in this case, when
> > > > one channel failed, MGW report the status to MGC .
> > > > But this method , I think , is not a standard way .
> > > > Why not define a explicit way to reach the aim?
> > > >
> > > > Regards
> > > > Zhangzhong
> > > >
> > > > ----- Original Message -----
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > requirement on RFC2805
> > > >
> > > >
> > > > > You audit the Media descriptor of all of the terminations
> > > > > to determine which terminations are employing the
> > > > > codec of interest.
> > > > >
> > > > > Brian
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > > > requirement on
> > > > > > RFC2805
> > > > > >
> > > > > >
> > > > > > Hi Brian,  All
> > > > > > I agree with you on the concept of Audit capability and Audit
> > > > > > Value . But in present protocol , How can we get the 500 busy
> > > > > > through Audit value present defined, I can't find the
> > > > > > parameter or package defined the case.
> > > > > >
> > > > > > Regards
> > > > > > Zhangzhong
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>;
> > > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> > > > > > <zhangzhong@huawei.com>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on RFC2805
> > > > > >
> > > > > >
> > > > > > > Audit capabilities tells you what the capabilities
> > of the system
> > > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > > In theory, the "1000 G.711 channel resource" comes
> > from Audit
> > > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > >
> > > > > > > In general, the RFC is compliant with the
> > requirements with one
> > > > > > > notable exception: many gateways are implemented with
> > > > DSPs or other
> > > > > > > programmable resources. There is no good way to express
> > > > capability
> > > > > > > with such resources.
> > > > > > >
> > > > > > > If you have 1000 fixed G.711 channels, Audit Capability
> > > > will reveal
> > > > > > > that.  If 500 channels are used, Audit Value will
> > reveal that.
> > > > > > >
> > > > > > > Brian
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Madhu Babu Brahmanapally
> > [mailto:madhubabu@kenetec.com]
> > > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > > Cc: megaco@ietf.org
> > > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on
> > > > > > > > RFC2805
> > > > > > > >
> > > > > > > >
> > > > > > > > HI Shashi,All,
> > > > > > > > Its true that Audit will help MGC to reconcile the
> > > > > > > > inconsistency. But for
> > > > > > > > the specific scenario Zhang has pointed, How this
> > resource
> > > > > > > > information is
> > > > > > > > exchanged between the MG and the MGC. According to my
> > > > > > > > knowledge there is no
> > > > > > > > parameter or anything as such to "quantitatively"
> > identify
> > > > > > > > G711 or any such
> > > > > > > > channel resource.
> > > > > > > > Regards
> > > > > > > > Madhubabu
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: megaco-admin@ietf.org
> > > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > > Shashi Kumar
> > > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > > To: zhangzhong
> > > > > > > > Cc: megaco@ietf.org
> > > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on
> > > > > > > > RFC2805
> > > > > > > >
> > > > > > > >
> > > > > > > > we have provision to audit the MG resource, which
> > > > > > clearlty defined by
> > > > > > > > Megaco/H.248. By means of Auduting the MG resources
> > > > we can always
> > > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > >
> > > > > > > > thanks,
> > > > > > > > shashi
> > > > > > > >
> > > > > > > >
> > > > > > > > > zhangzhong wrote:
> > > > > > > > >
> > > > > > > > > Hi :
> > > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > > >         Provide a mechanism to discover the current
> > > > available
> > > > > > > > > resources
> > > > > > > > >         in the MG, where resources are dynamically
> > > > consumed by
> > > > > > > > >         connections and the MGC cannot reasonably or
> > > > > > reliably track
> > > > > > > > > the
> > > > > > > > >         consumption of such resources. It should also
> > > > > > be possible to
> > > > > > > > >         discover resources currently in use, in order
> > > > > > to reconcile
> > > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > > >
> > > > > > > > > This means MGC can know the resource consume in
> > the MGW ,
> > > > > > > > for example
> > > > > > > > > , if There have 1000 G.711 channel resource , if 500 is
> > > > > > > > busy , How can
> > > > > > > > > MGC know this through RFC3015?
> > > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > > >
> > > > > > > > > Thanks for the reply.
> > > > > > > > > Regards
> > > > > > > > > Zhangzhong
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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


From daemon@ns.ietf.org  Tue Jan  8 00:08:51 2002
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 AAA07245
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 00:08:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA05910
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 00:08:46 -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 XAA05000;
	Mon, 7 Jan 2002 23:50:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04934
	for <megaco@ns.ietf.org>; Mon, 7 Jan 2002 23:50:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07077
	for <megaco@ietf.org>; Mon, 7 Jan 2002 23:50:33 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA07893;
	Tue, 8 Jan 2002 15:49:14 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA01252;
	Tue, 8 Jan 2002 15:50:31 +1100 (EST)
Message-ID: <3C3A5E35.7F66E746@ericsson.com.au>
Date: Tue, 08 Jan 2002 13:49:25 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'zhangzhong'" <zhangzhong@huawei.com>, megaco@ietf.org
Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on RFC2805
References: <313680C9A886D511A06000204840E1CF57C7A0@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

In terms of congestion of resources there is already a package that can
be used to indicate when a MG is congested. There is also some work
ongoing in SG16 to further refine the resource congestion handling
perhaps this work can also address individual resources.

Christian

"Rosen, Brian" wrote:
> 
> Well, the door is, at least in theory, open to add features in
> V2.  I actually oppose doing this, but there are some who feel
> that tinkering with the protocol before there is any substantial
> deployment experience is a good idea.
> 
> You could propose a solution.  If you do, I think you would want
> to see if it works for a wide variety of resource models that MGs
> might implement, and yet be simple enough that a really small
> phone or gateway could implement it without a lot of code.
> 
> The answer to your question is that if the MGC knows the MG has
> a capability for something, but gets an error when it tries to
> use it, then it could, when a future requirement arises for that
> capability, ask for it again.  It will either work, or fail
> again.  No need to poll.
> 
> Brian
> 
> > -----Original Message-----
> > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > Sent: Friday, January 04, 2002 10:40 PM
> > To: Rosen, Brian
> > Cc: megaco@ietf.org
> > Subject: Re: [Megaco] one dount on RFC3015 as to the requirement on
> > RFC2805
> >
> >
> > Hi Brian, all
> > Yes , It has problems about this. I think there should have
> > some methods resolving them.
> > And If we can't resolve these problems, There will introduce
> > more difficulity of interworking between different company's
> > product  and low the efficiency of network.
> > Problems:
> > MGW can reject the resource command from MGC, OK, It is no
> > problems. But how MGC know the resource in this MGW is
> > available again?  We can  setup a flag , and apply the
> > request periodicly, when success, reset the flag, or start a
> > timer , after the timer time out , reset the flag. etc.
> > All these methods will introcude much traffic between MGC and
> > MGW. It is not good for the network resource management in the MGC.
> >
> > Regards
> > Zhangzhong
> >
> >
> >
> > ----- Original Message -----
> > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > To: 'zhangzhong' <zhangzhong@huawei.com>
> > Cc: <megaco@ietf.org>
> > Sent: Friday, January 04, 2002 9:13 PM
> > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > requirement on RFC2805
> >
> >
> > > Because the general problem is very complex, and no one has
> > > proposed a general solution that seems likely to cover most
> > > cases.
> > >
> > > As an example, many systems are implemented with DSPs.  These
> > > systems have very complex interaction between how many codecs
> > > of different types can be in use simultaneously.  A system might,
> > > for example, support 16 channels of G.729, 32 channels of G.711
> > > and 32 channels of G.165 echo cancel with 64 ms tails, but
> > > not simultaneously.  It may be that if you have one channel of
> > > G.729, then you can support another 27 channels of G.711, and
> > > if you have any G.729, then the longest tail is reduced.
> > > This is because there are actually several variables at work -
> > > DSP MIPs, and memory capacity, and the interaction between those
> > > variables is complex.  I once discussed having a language which
> > > allowed you to express this kind of thing, but it was too complex
> > > for most people to deal with.  Then you add spares issues and
> > > things get even more complex.
> > >
> > > The other side of this issue is that the MGC can ask for resources
> > > on the MG, and the MG can fail if there are no more resources.
> > > This can be done in a way that lets the MGC either try to reroute
> > > the call, or supply the appropriate error message to the caller.
> > > That is why we didn't worry more about this known limitation.
> > >
> > > Brian
> > >
> > > > -----Original Message-----
> > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > Sent: Friday, January 04, 2002 4:08 AM
> > > > To: Rosen, Brian
> > > > Cc: megaco@ietf.org
> > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > requirement on
> > > > RFC2805
> > > >
> > > >
> > > > Hi Brian,
> > > > Yes , It can know the resource using, But if you can't
> > > > binding all channel with Termination, How can you know the
> > > > status of left? idle or failed?
> > > > We can configure the Max number of channel and we can know
> > > > the exact number of them is busy, but we can't know the
> > > > status of spares . We can bind a termination with one
> > > > channel, and put into NULL context, Only in this case, when
> > > > one channel failed, MGW report the status to MGC .
> > > > But this method , I think , is not a standard way .
> > > > Why not define a explicit way to reach the aim?
> > > >
> > > > Regards
> > > > Zhangzhong
> > > >
> > > > ----- Original Message -----
> > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > To: 'zhangzhong' <zhangzhong@huawei.com>
> > > > Cc: <megaco@ietf.org>
> > > > Sent: Wednesday, January 02, 2002 9:18 PM
> > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > requirement on RFC2805
> > > >
> > > >
> > > > > You audit the Media descriptor of all of the terminations
> > > > > to determine which terminations are employing the
> > > > > codec of interest.
> > > > >
> > > > > Brian
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: zhangzhong [mailto:zhangzhong@huawei.com]
> > > > > > Sent: Friday, December 28, 2001 9:25 PM
> > > > > > To: Rosen, Brian; 'Madhu Babu Brahmanapally'; 'Shashi Kumar'
> > > > > > Cc: megaco@ietf.org
> > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > > > requirement on
> > > > > > RFC2805
> > > > > >
> > > > > >
> > > > > > Hi Brian,  All
> > > > > > I agree with you on the concept of Audit capability and Audit
> > > > > > Value . But in present protocol , How can we get the 500 busy
> > > > > > through Audit value present defined, I can't find the
> > > > > > parameter or package defined the case.
> > > > > >
> > > > > > Regards
> > > > > > Zhangzhong
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: Rosen, Brian <Brian.Rosen@marconi.com>
> > > > > > To: 'Madhu Babu Brahmanapally' <madhubabu@kenetec.com>;
> > > > > > 'Shashi Kumar' <shashi.kumar@wipro.com>; 'zhangzhong'
> > > > > > <zhangzhong@huawei.com>
> > > > > > Cc: <megaco@ietf.org>
> > > > > > Sent: Saturday, December 29, 2001 12:54 AM
> > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on RFC2805
> > > > > >
> > > > > >
> > > > > > > Audit capabilities tells you what the capabilities
> > of the system
> > > > > > > are.  Audit Value tells you what is currently "in use".
> > > > > > > In theory, the "1000 G.711 channel resource" comes
> > from Audit
> > > > > > > Capability, "500 busy" comes from Audit Value.
> > > > > > >
> > > > > > > In general, the RFC is compliant with the
> > requirements with one
> > > > > > > notable exception: many gateways are implemented with
> > > > DSPs or other
> > > > > > > programmable resources. There is no good way to express
> > > > capability
> > > > > > > with such resources.
> > > > > > >
> > > > > > > If you have 1000 fixed G.711 channels, Audit Capability
> > > > will reveal
> > > > > > > that.  If 500 channels are used, Audit Value will
> > reveal that.
> > > > > > >
> > > > > > > Brian
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Madhu Babu Brahmanapally
> > [mailto:madhubabu@kenetec.com]
> > > > > > > > Sent: Friday, December 28, 2001 9:44 AM
> > > > > > > > To: 'Shashi Kumar'; 'zhangzhong'
> > > > > > > > Cc: megaco@ietf.org
> > > > > > > > Subject: RE: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on
> > > > > > > > RFC2805
> > > > > > > >
> > > > > > > >
> > > > > > > > HI Shashi,All,
> > > > > > > > Its true that Audit will help MGC to reconcile the
> > > > > > > > inconsistency. But for
> > > > > > > > the specific scenario Zhang has pointed, How this
> > resource
> > > > > > > > information is
> > > > > > > > exchanged between the MG and the MGC. According to my
> > > > > > > > knowledge there is no
> > > > > > > > parameter or anything as such to "quantitatively"
> > identify
> > > > > > > > G711 or any such
> > > > > > > > channel resource.
> > > > > > > > Regards
> > > > > > > > Madhubabu
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: megaco-admin@ietf.org
> > > > > > [mailto:megaco-admin@ietf.org]On Behalf Of
> > > > > > > > Shashi Kumar
> > > > > > > > Sent: Thursday, December 27, 2001 11:55 PM
> > > > > > > > To: zhangzhong
> > > > > > > > Cc: megaco@ietf.org
> > > > > > > > Subject: Re: [Megaco] one dount on RFC3015 as to the
> > > > > > requirement on
> > > > > > > > RFC2805
> > > > > > > >
> > > > > > > >
> > > > > > > > we have provision to audit the MG resource, which
> > > > > > clearlty defined by
> > > > > > > > Megaco/H.248. By means of Auduting the MG resources
> > > > we can always
> > > > > > > > "reconcile inconsistencies between the MGC and the MG"
> > > > > > > >
> > > > > > > > thanks,
> > > > > > > > shashi
> > > > > > > >
> > > > > > > >
> > > > > > > > > zhangzhong wrote:
> > > > > > > > >
> > > > > > > > > Hi :
> > > > > > > > > In the rfc 2805, there have a request to H.248:
> > > > > > > > >         Provide a mechanism to discover the current
> > > > available
> > > > > > > > > resources
> > > > > > > > >         in the MG, where resources are dynamically
> > > > consumed by
> > > > > > > > >         connections and the MGC cannot reasonably or
> > > > > > reliably track
> > > > > > > > > the
> > > > > > > > >         consumption of such resources. It should also
> > > > > > be possible to
> > > > > > > > >         discover resources currently in use, in order
> > > > > > to reconcile
> > > > > > > > >         inconsistencies between the MGC and the MG.
> > > > > > > > >
> > > > > > > > > This means MGC can know the resource consume in
> > the MGW ,
> > > > > > > > for example
> > > > > > > > > , if There have 1000 G.711 channel resource , if 500 is
> > > > > > > > busy , How can
> > > > > > > > > MGC know this through RFC3015?
> > > > > > > > > If can't , The RFC3015 is inconsist with the RFC2805
> > > > > > > > >
> > > > > > > > > Thanks for the reply.
> > > > > > > > > Regards
> > > > > > > > > Zhangzhong
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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



From megaco-admin@ietf.org  Tue Jan  8 05:58:45 2002
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 FAA18926
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 05:58:44 -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 FAA23627;
	Tue, 8 Jan 2002 05:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23600
	for <megaco@ns.ietf.org>; Tue, 8 Jan 2002 05:46:35 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18760
	for <megaco@ietf.org>; Tue, 8 Jan 2002 05:46:32 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id CAA22932
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:34 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Jan 2002 10:46:34 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id CAA25266
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:33 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id CAA16437
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:32 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id QAA19641
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:15:08 +0530 (IST)
Message-ID: <3C3ACD3B.9DD9A6B6@lucent.com>
Date: Tue, 08 Jan 2002 16:13:07 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Query on LBRKT, RBRKT, COMMA.
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: 7bit

Hi All,

can someone let me know for what following terms stand for in the h248 ABNF ?

LBRKT,
RBRKT, 
COMMA.

thanks,
Shambhu

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


From daemon@ns.ietf.org  Tue Jan  8 05:58:45 2002
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 FAA18938
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 05:58:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA23898
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 05:58:47 -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 FAA23627;
	Tue, 8 Jan 2002 05:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23600
	for <megaco@ns.ietf.org>; Tue, 8 Jan 2002 05:46:35 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18760
	for <megaco@ietf.org>; Tue, 8 Jan 2002 05:46:32 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id CAA22932
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:34 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Jan 2002 10:46:34 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id CAA25266
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:33 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id CAA16437
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:46:32 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id QAA19641
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:15:08 +0530 (IST)
Message-ID: <3C3ACD3B.9DD9A6B6@lucent.com>
Date: Tue, 08 Jan 2002 16:13:07 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Query on LBRKT, RBRKT, COMMA.
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: 7bit

Hi All,

can someone let me know for what following terms stand for in the h248 ABNF ?

LBRKT,
RBRKT, 
COMMA.

thanks,
Shambhu

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



From megaco-admin@ietf.org  Tue Jan  8 06:06:39 2002
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 GAA19006
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 06:06:39 -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 FAA23856;
	Tue, 8 Jan 2002 05:57:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23828
	for <megaco@ns.ietf.org>; Tue, 8 Jan 2002 05:57:05 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18913
	for <megaco@ietf.org>; Tue, 8 Jan 2002 05:57:02 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id CAA23017
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:03 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Jan 2002 10:57:04 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id CAA25926
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:03 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id CAA17009
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:01 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id QAA20199
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:25:38 +0530 (IST)
Message-ID: <3C3ACFB1.AF055CF5@lucent.com>
Date: Tue, 08 Jan 2002 16:23:37 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Query on LBRKT, RBRKT, COMMA.
References: <3C3ACD3B.9DD9A6B6@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

sorry for confusion, got it..
-shambhu

Shambhu Dayal Rai wrote:
> 
> Hi All,
> 
> can someone let me know for what following terms stand for in the h248 ABNF ?
> 
> LBRKT,
> RBRKT,
> COMMA.
> 
> thanks,
> Shambhu
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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


From daemon@ns.ietf.org  Tue Jan  8 06:06:40 2002
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 GAA19015
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 06:06:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA24461
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 06:06:42 -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 FAA23856;
	Tue, 8 Jan 2002 05:57:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23828
	for <megaco@ns.ietf.org>; Tue, 8 Jan 2002 05:57:05 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18913
	for <megaco@ietf.org>; Tue, 8 Jan 2002 05:57:02 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id CAA23017
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:03 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Jan 2002 10:57:04 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id CAA25926
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:03 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id CAA17009
	for <megaco@ietf.org>; Tue, 8 Jan 2002 02:57:01 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id QAA20199
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:25:38 +0530 (IST)
Message-ID: <3C3ACFB1.AF055CF5@lucent.com>
Date: Tue, 08 Jan 2002 16:23:37 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Query on LBRKT, RBRKT, COMMA.
References: <3C3ACD3B.9DD9A6B6@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

sorry for confusion, got it..
-shambhu

Shambhu Dayal Rai wrote:
> 
> Hi All,
> 
> can someone let me know for what following terms stand for in the h248 ABNF ?
> 
> LBRKT,
> RBRKT,
> COMMA.
> 
> thanks,
> Shambhu
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Tue Jan  8 07:08:05 2002
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 HAA19500
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 07:08:05 -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 GAA25564;
	Tue, 8 Jan 2002 06:50:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA25532
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 06:50:46 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19351
	for <megaco@ietf.org>; Tue, 8 Jan 2002 06:50:44 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g08BoXC12714
	for <megaco@ietf.org>; Tue, 8 Jan 2002 13:50:33 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5852c636f8ac158f21082@esvir01nok.ntc.nokia.com>;
 Tue, 8 Jan 2002 13:50:43 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <CHNT3P41>; Tue, 8 Jan 2002 13:50:40 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D257@esebe004.NOE.Nokia.com>
To: Brian.Rosen@marconi.com, rsesh@nexverse.com, megaco@ietf.org
Cc: Maher.M.Awad@nokia.com, heikki.stahl@nokia.com, marita.pistemaa@nokia.com,
        toni.p.karppinen@nokia.com
Subject: RE: [Megaco] Megaco Interoperability
Date: Tue, 8 Jan 2002 13:50:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="ISO-8859-1"
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

we have a business unit who has a Megaco stack (MG side) with only
binary implementation. We are developing a stack for MGC, which
currently supports only text, but would have to include binary support
if the MGs we have to control only understand binary. I would try to
convince our team developing MG to support Text if not moving totally to
text. 
 
-sunesh

-----Original Message-----
From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: 07. January 2002 16:37
To: Seshagiri Rao; megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability


There is not a reference design available.
There are test scenarios developed for the bakeoffs.  These explicitly
DO NOT
include message sequences.
I have been stalling on scheduling another bakeoff until we had better
participation.
  I plan to "call the question" again soon
Virtually all implementations are text only.  A few are both (a very
few).  I don't
know of any that are binary only.
 
Brian

-----Original Message-----
From: Seshagiri Rao [mailto:rsesh@nexverse.com]
Sent: Saturday, January 05, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Megaco Interoperability



All: 

I would like to know if there is any reference design/test sequence for
Megaco stack implementation. 
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh 


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


From daemon@optimus.ietf.org  Tue Jan  8 07:08:06 2002
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 HAA19512
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 07:08:05 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA26194
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 07:08:06 -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 GAA25564;
	Tue, 8 Jan 2002 06:50:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA25532
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 06:50:46 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19351
	for <megaco@ietf.org>; Tue, 8 Jan 2002 06:50:44 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g08BoXC12714
	for <megaco@ietf.org>; Tue, 8 Jan 2002 13:50:33 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5852c636f8ac158f21082@esvir01nok.ntc.nokia.com>;
 Tue, 8 Jan 2002 13:50:43 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <CHNT3P41>; Tue, 8 Jan 2002 13:50:40 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D257@esebe004.NOE.Nokia.com>
To: Brian.Rosen@marconi.com, rsesh@nexverse.com, megaco@ietf.org
Cc: Maher.M.Awad@nokia.com, heikki.stahl@nokia.com, marita.pistemaa@nokia.com,
        toni.p.karppinen@nokia.com
Subject: RE: [Megaco] Megaco Interoperability
Date: Tue, 8 Jan 2002 13:50:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="ISO-8859-1"
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

we have a business unit who has a Megaco stack (MG side) with only
binary implementation. We are developing a stack for MGC, which
currently supports only text, but would have to include binary support
if the MGs we have to control only understand binary. I would try to
convince our team developing MG to support Text if not moving totally to
text. 
 
-sunesh

-----Original Message-----
From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
Sent: 07. January 2002 16:37
To: Seshagiri Rao; megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability


There is not a reference design available.
There are test scenarios developed for the bakeoffs.  These explicitly
DO NOT
include message sequences.
I have been stalling on scheduling another bakeoff until we had better
participation.
  I plan to "call the question" again soon
Virtually all implementations are text only.  A few are both (a very
few).  I don't
know of any that are binary only.
 
Brian

-----Original Message-----
From: Seshagiri Rao [mailto:rsesh@nexverse.com]
Sent: Saturday, January 05, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Megaco Interoperability



All: 

I would like to know if there is any reference design/test sequence for
Megaco stack implementation. 
I would also like to know if there is any forthcoming interop/bake-off
event.  
How many of the current Megaco stack implementations support ABNF/Text
encoding and how many support ASN.1/binary encoding?

Sesh 


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



From megaco-admin@ietf.org  Tue Jan  8 09:16:31 2002
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 JAA22434
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:16:31 -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 JAA29750;
	Tue, 8 Jan 2002 09:00: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 JAA29697
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:00:01 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21473
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:00:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08DxUt28247;
	Tue, 8 Jan 2002 08:59:30 -0500 (EST)
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 g08DxTN28298;
	Tue, 8 Jan 2002 08:59:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPQCQ>; Tue, 8 Jan 2002 08:57:55 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shambhu Dayal Rai'" <sdrai@lucent.com>, megaco@ietf.org
Subject: RE: [Megaco] Query on LBRKT, RBRKT, COMMA.
Date: Tue, 8 Jan 2002 08:58:20 -0500 
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

LBRKT                = LWSP %x7B LWSP ; "{"
RBRKT                = LWSP %x7D LWSP ; "}"
COMMA                = LWSP %x2C LWSP ; ","

These are defined down in the primitives section, just ahead of such basics
as SLASH, ALPHA, and DIGIT.

-----Original Message-----
From: Shambhu Dayal Rai [mailto:sdrai@lucent.com]
Sent: Tuesday, January 08, 2002 5:43 AM
To: megaco@ietf.org
Subject: [Megaco] Query on LBRKT, RBRKT, COMMA.


Hi All,

can someone let me know for what following terms stand for in the h248 ABNF
?

LBRKT,
RBRKT, 
COMMA.

thanks,
Shambhu

_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan  8 09:16:32 2002
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 JAA22443
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:16:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00722
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 09:16:32 -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 JAA29750;
	Tue, 8 Jan 2002 09:00: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 JAA29697
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:00:01 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21473
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:00:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08DxUt28247;
	Tue, 8 Jan 2002 08:59:30 -0500 (EST)
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 g08DxTN28298;
	Tue, 8 Jan 2002 08:59:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPQCQ>; Tue, 8 Jan 2002 08:57:55 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shambhu Dayal Rai'" <sdrai@lucent.com>, megaco@ietf.org
Subject: RE: [Megaco] Query on LBRKT, RBRKT, COMMA.
Date: Tue, 8 Jan 2002 08:58:20 -0500 
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

LBRKT                = LWSP %x7B LWSP ; "{"
RBRKT                = LWSP %x7D LWSP ; "}"
COMMA                = LWSP %x2C LWSP ; ","

These are defined down in the primitives section, just ahead of such basics
as SLASH, ALPHA, and DIGIT.

-----Original Message-----
From: Shambhu Dayal Rai [mailto:sdrai@lucent.com]
Sent: Tuesday, January 08, 2002 5:43 AM
To: megaco@ietf.org
Subject: [Megaco] Query on LBRKT, RBRKT, COMMA.


Hi All,

can someone let me know for what following terms stand for in the h248 ABNF
?

LBRKT,
RBRKT, 
COMMA.

thanks,
Shambhu

_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan  8 09:16:36 2002
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 JAA22433
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:16:31 -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 JAA00314;
	Tue, 8 Jan 2002 09:03:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00285
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:03:54 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21891
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:03:53 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g08E3hC19000
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:03:43 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5853402122ac158f270d4@esvir07nok.ntc.nokia.com> for <megaco@ietf.org>;
 Tue, 8 Jan 2002 16:03:53 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <C13GZB4D>; Tue, 8 Jan 2002 16:03:53 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D25A@esebe004.NOE.Nokia.com>
To: megaco@ietf.org
Date: Tue, 8 Jan 2002 16:03:49 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] indAudmuxDescriptor
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

Hi,

In v2 of the protocol indAudmuxDescriptor has not been defined. It has
been mentioned (declared) as one of the possible value for
indAudauditReturnParameter but not defined anywhere in the draft (pg
112). 
On page 105 of the same draft, I think a SLASH (/) is missing in the
contextAuditProperties. 

Regards,
sunesh

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


From daemon@optimus.ietf.org  Tue Jan  8 09:16:36 2002
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 JAA22472
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:16:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00760
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 09:16:36 -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 JAA00314;
	Tue, 8 Jan 2002 09:03:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00285
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:03:54 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21891
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:03:53 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g08E3hC19000
	for <megaco@ietf.org>; Tue, 8 Jan 2002 16:03:43 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5853402122ac158f270d4@esvir07nok.ntc.nokia.com> for <megaco@ietf.org>;
 Tue, 8 Jan 2002 16:03:53 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <C13GZB4D>; Tue, 8 Jan 2002 16:03:53 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D25A@esebe004.NOE.Nokia.com>
To: megaco@ietf.org
Date: Tue, 8 Jan 2002 16:03:49 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] indAudmuxDescriptor
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

Hi,

In v2 of the protocol indAudmuxDescriptor has not been defined. It has
been mentioned (declared) as one of the possible value for
indAudauditReturnParameter but not defined anywhere in the draft (pg
112). 
On page 105 of the same draft, I think a SLASH (/) is missing in the
contextAuditProperties. 

Regards,
sunesh

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



From megaco-admin@ietf.org  Tue Jan  8 09:28:42 2002
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 JAA23069
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:28:37 -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 JAA00633;
	Tue, 8 Jan 2002 09:12:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00604
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:12:52 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22341
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:51 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08ECLt03678
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:21 -0500 (EST)
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 g08ECJN29415
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:19 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPQ4F>; Tue, 8 Jan 2002 09:10:42 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 8 Jan 2002 09:11:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1984E.50C91130"
Subject: [Megaco] Implications Of New SDP Features
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1984E.50C91130
Content-Type: text/plain;
	charset="iso-8859-1"

SDP is in the process of picking up some new features, including FID,
SIMCAP, connection-oriented media, and the new negotiation model.  I'm just
testing the waters here, but is there any sentiment in favour of altering
the text to encourage the use of these features in place of existing Megaco
protocol provisions?  For instance, should we discourage the use of
wildcarding, sub-lists, and ranges when text encoding Local and Remote,
saying that applications SHOULD use the alternatives provided by MMUSIC?

Alternatively, should we hold our fire until we introduce SDPnG?

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

------_=_NextPart_001_01C1984E.50C91130
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Implications Of New SDP Features</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>SDP is in the process of picking up some new =
features, including FID, SIMCAP, connection-oriented media, and the new =
negotiation model.&nbsp; I'm just testing the waters here, but is there =
any sentiment in favour of altering the text to encourage the use of =
these features in place of existing Megaco protocol provisions?&nbsp; =
For instance, should we discourage the use of wildcarding, sub-lists, =
and ranges when text encoding Local and Remote, saying that =
applications SHOULD use the alternatives provided by MMUSIC?</FONT></P>

<P><FONT SIZE=3D2>Alternatively, should we hold our fire until we =
introduce SDPnG?</FONT>
</P>

<P><FONT SIZE=3D2>Tom Taylor</FONT>
<BR><FONT SIZE=3D2>taylor@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>Ph. +1 613 736 0961 (ESN 396 1490)</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1984E.50C91130--

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


From daemon@optimus.ietf.org  Tue Jan  8 09:28:43 2002
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 JAA23079
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:28:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA01473
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 09:28:43 -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 JAA00633;
	Tue, 8 Jan 2002 09:12:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00604
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:12:52 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22341
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:51 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08ECLt03678
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:21 -0500 (EST)
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 g08ECJN29415
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:12:19 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPQ4F>; Tue, 8 Jan 2002 09:10:42 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 8 Jan 2002 09:11:07 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1984E.50C91130"
Subject: [Megaco] Implications Of New SDP Features
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1984E.50C91130
Content-Type: text/plain;
	charset="iso-8859-1"

SDP is in the process of picking up some new features, including FID,
SIMCAP, connection-oriented media, and the new negotiation model.  I'm just
testing the waters here, but is there any sentiment in favour of altering
the text to encourage the use of these features in place of existing Megaco
protocol provisions?  For instance, should we discourage the use of
wildcarding, sub-lists, and ranges when text encoding Local and Remote,
saying that applications SHOULD use the alternatives provided by MMUSIC?

Alternatively, should we hold our fire until we introduce SDPnG?

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

------_=_NextPart_001_01C1984E.50C91130
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Implications Of New SDP Features</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>SDP is in the process of picking up some new =
features, including FID, SIMCAP, connection-oriented media, and the new =
negotiation model.&nbsp; I'm just testing the waters here, but is there =
any sentiment in favour of altering the text to encourage the use of =
these features in place of existing Megaco protocol provisions?&nbsp; =
For instance, should we discourage the use of wildcarding, sub-lists, =
and ranges when text encoding Local and Remote, saying that =
applications SHOULD use the alternatives provided by MMUSIC?</FONT></P>

<P><FONT SIZE=3D2>Alternatively, should we hold our fire until we =
introduce SDPnG?</FONT>
</P>

<P><FONT SIZE=3D2>Tom Taylor</FONT>
<BR><FONT SIZE=3D2>taylor@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>Ph. +1 613 736 0961 (ESN 396 1490)</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1984E.50C91130--

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



From megaco-admin@ietf.org  Tue Jan  8 09:37:20 2002
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 JAA23451
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:37:16 -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 JAA00858;
	Tue, 8 Jan 2002 09:18:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00827
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:18:42 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22518
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:18:35 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g08EIVJ24007;
	Tue, 8 Jan 2002 15:18:31 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g08EIVhO001058;
	Tue, 8 Jan 2002 16:18:31 +0200 (EET)
Message-ID: <3C3AFF89.34F64710@lmf.ericsson.se>
Date: Tue, 08 Jan 2002 16:17:45 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Implications Of New SDP Features
References: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

Don't the ReserveGroup- and ReserveValue properties already handle lots
of the issues FID, SIMCAP etc are trying to solve?

Also, I don't think those extensions can replace all the cases we use
wildcarding for.

Regards,

Christer Holmberg
Ericsson Finland


Tom-PT Taylor wrote:
> 
> SDP is in the process of picking up some new features, including FID,
> SIMCAP, connection-oriented media, and the new negotiation model.  I'm
> just testing the waters here, but is there any sentiment in favour of
> altering the text to encourage the use of these features in place of
> existing Megaco protocol provisions?  For instance, should we
> discourage the use of wildcarding, sub-lists, and ranges when text
> encoding Local and Remote, saying that applications SHOULD use the
> alternatives provided by MMUSIC?
> 

>Alternatively, should we hold our fire until we introduce SDPnG?





 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
>

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


From daemon@optimus.ietf.org  Tue Jan  8 09:37:24 2002
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 JAA23464
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:37:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA02157
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 09:37:21 -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 JAA00858;
	Tue, 8 Jan 2002 09:18:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00827
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:18:42 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22518
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:18:35 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g08EIVJ24007;
	Tue, 8 Jan 2002 15:18:31 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g08EIVhO001058;
	Tue, 8 Jan 2002 16:18:31 +0200 (EET)
Message-ID: <3C3AFF89.34F64710@lmf.ericsson.se>
Date: Tue, 08 Jan 2002 16:17:45 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Implications Of New SDP Features
References: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

Don't the ReserveGroup- and ReserveValue properties already handle lots
of the issues FID, SIMCAP etc are trying to solve?

Also, I don't think those extensions can replace all the cases we use
wildcarding for.

Regards,

Christer Holmberg
Ericsson Finland


Tom-PT Taylor wrote:
> 
> SDP is in the process of picking up some new features, including FID,
> SIMCAP, connection-oriented media, and the new negotiation model.  I'm
> just testing the waters here, but is there any sentiment in favour of
> altering the text to encourage the use of these features in place of
> existing Megaco protocol provisions?  For instance, should we
> discourage the use of wildcarding, sub-lists, and ranges when text
> encoding Local and Remote, saying that applications SHOULD use the
> alternatives provided by MMUSIC?
> 

>Alternatively, should we hold our fire until we introduce SDPnG?





 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
>

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



From megaco-admin@ietf.org  Tue Jan  8 09:40:54 2002
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 JAA23583
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:40:54 -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 JAA01237;
	Tue, 8 Jan 2002 09:26:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01150
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:26:25 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22936
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:26:24 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id IAA19117
	for <megaco@ietf.org>; Tue, 8 Jan 2002 08:25:53 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g08EPkm21693
	for <megaco@ietf.org>; Tue, 8 Jan 2002 08:25:47 -0600 (CST)
Message-ID: <001101c19851$03ca0a30$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
Date: Tue, 8 Jan 2002 20:00:16 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1987F.17A5B990"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Subject: [Megaco] Megaco CAS
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

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C1987F.17A5B990
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Implications Of New SDP FeaturesHi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5=20
    Signal Name: Address=20
    SignalID: addr (0x0005)=20
    Description: Applies the address signals in the form of either=20
          DTMF, dial-pulse or MF-tones on the trunk. The actual=20
          frequency, cadence, duration and amplitude values for the=20
          multi-frequency tones that convey the address information are=20
          provisioned in the MG.=20
    Signal Type: (BR) Brief=20
    Duration: Provisioned=20
    Additional Parameters: =20
        Parameter Name: Digit String=20
        ParameterID: ds (0x0001)=20
        Description: The digit string that needs to be sent as address=20
          signals.=20
        Type: string of digits.=20
        Possible Values: a sequence of the characters "0" through "9"=20
          as well as "A" through "H" ("A" through "H" used for MF=20
          signalling - refer to the symbols defined for the digit map=20
          in the MF Tone Detection package).=20
        Parameter Name: Address Delay=20
        ParameterID: ad (0x0002)=20
        Description: Specifies a timed delay that is applied prior to=20
          signalling the address. The address delay is optional. If the=20
          address delay parameter is not provided, the MG uses the=20
          provisioned value by default. =20
        Type: integer=20
        Possible Values: 0 and up in milliseconds=20

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or =
dial pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or =
Dial Pulse?

Thanks in advance.

Chak

------=_NextPart_000_000E_01C1987F.17A5B990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Implications Of New SDP Features</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi List,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As per =
draft-manyfolks-megaco-caspackage-01.txt=20
Section</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>6.4.5 <BR>&nbsp;&nbsp;&nbsp; Signal =
Name: Address=20
<BR>&nbsp;&nbsp;&nbsp; SignalID: addr (0x0005) <BR>&nbsp;&nbsp;&nbsp;=20
Description: Applies the address signals in the form of either=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DTMF, =
dial-pulse or=20
MF-tones on the trunk. The actual=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; frequency, =
cadence,=20
duration and amplitude values for the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multi-frequency tones=20
that convey the address information are=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provisioned =
in the=20
MG. <BR>&nbsp;&nbsp;&nbsp; Signal Type: (BR) Brief =
<BR>&nbsp;&nbsp;&nbsp;=20
Duration: Provisioned <BR>&nbsp;&nbsp;&nbsp; Additional =
Parameters:&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: Digit =
String=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ds (0x0001)=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: The digit =
string=20
that needs to be sent as address=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signals.=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: string of digits.=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: a =
sequence of=20
the characters "0" through "9"=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as well as =
"A"=20
through "H" ("A" through "H" used for MF=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signalling - =
refer to=20
the symbols defined for the digit map=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the MF =
Tone=20
Detection package). <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Parameter=20
Name: Address Delay <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
ParameterID:=20
ad (0x0002) <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description:=20
Specifies a timed delay that is applied prior to=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signalling =
the=20
address. The address delay is optional. If the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; address delay =

parameter is not provided, the MG uses the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provisioned =
value by=20
default.&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
integer=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: 0 and up =
in=20
milliseconds </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Question:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>MGC can instruct gateway to out pulse =
digits either=20
in DTMF or MF or dial pulse.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>How MGC can tell gateway about the mode =
of the=20
digits is MF or DTMF or Dial Pulse?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chak</FONT></DIV></BODY></HTML>

------=_NextPart_000_000E_01C1987F.17A5B990--


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


From daemon@optimus.ietf.org  Tue Jan  8 09:40:55 2002
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 JAA23596
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 09:40:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA02237
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 09:40:55 -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 JAA01237;
	Tue, 8 Jan 2002 09:26:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01150
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 09:26:25 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22936
	for <megaco@ietf.org>; Tue, 8 Jan 2002 09:26:24 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id IAA19117
	for <megaco@ietf.org>; Tue, 8 Jan 2002 08:25:53 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g08EPkm21693
	for <megaco@ietf.org>; Tue, 8 Jan 2002 08:25:47 -0600 (CST)
Message-ID: <001101c19851$03ca0a30$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEB@zcard0kc.ca.nortel.com>
Date: Tue, 8 Jan 2002 20:00:16 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1987F.17A5B990"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Subject: [Megaco] Megaco CAS
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

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C1987F.17A5B990
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Implications Of New SDP FeaturesHi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5=20
    Signal Name: Address=20
    SignalID: addr (0x0005)=20
    Description: Applies the address signals in the form of either=20
          DTMF, dial-pulse or MF-tones on the trunk. The actual=20
          frequency, cadence, duration and amplitude values for the=20
          multi-frequency tones that convey the address information are=20
          provisioned in the MG.=20
    Signal Type: (BR) Brief=20
    Duration: Provisioned=20
    Additional Parameters: =20
        Parameter Name: Digit String=20
        ParameterID: ds (0x0001)=20
        Description: The digit string that needs to be sent as address=20
          signals.=20
        Type: string of digits.=20
        Possible Values: a sequence of the characters "0" through "9"=20
          as well as "A" through "H" ("A" through "H" used for MF=20
          signalling - refer to the symbols defined for the digit map=20
          in the MF Tone Detection package).=20
        Parameter Name: Address Delay=20
        ParameterID: ad (0x0002)=20
        Description: Specifies a timed delay that is applied prior to=20
          signalling the address. The address delay is optional. If the=20
          address delay parameter is not provided, the MG uses the=20
          provisioned value by default. =20
        Type: integer=20
        Possible Values: 0 and up in milliseconds=20

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or =
dial pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or =
Dial Pulse?

Thanks in advance.

Chak

------=_NextPart_000_000E_01C1987F.17A5B990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Implications Of New SDP Features</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi List,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>As per =
draft-manyfolks-megaco-caspackage-01.txt=20
Section</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>6.4.5 <BR>&nbsp;&nbsp;&nbsp; Signal =
Name: Address=20
<BR>&nbsp;&nbsp;&nbsp; SignalID: addr (0x0005) <BR>&nbsp;&nbsp;&nbsp;=20
Description: Applies the address signals in the form of either=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DTMF, =
dial-pulse or=20
MF-tones on the trunk. The actual=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; frequency, =
cadence,=20
duration and amplitude values for the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multi-frequency tones=20
that convey the address information are=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provisioned =
in the=20
MG. <BR>&nbsp;&nbsp;&nbsp; Signal Type: (BR) Brief =
<BR>&nbsp;&nbsp;&nbsp;=20
Duration: Provisioned <BR>&nbsp;&nbsp;&nbsp; Additional =
Parameters:&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: Digit =
String=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ds (0x0001)=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: The digit =
string=20
that needs to be sent as address=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signals.=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: string of digits.=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: a =
sequence of=20
the characters "0" through "9"=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as well as =
"A"=20
through "H" ("A" through "H" used for MF=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signalling - =
refer to=20
the symbols defined for the digit map=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the MF =
Tone=20
Detection package). <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Parameter=20
Name: Address Delay <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
ParameterID:=20
ad (0x0002) <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description:=20
Specifies a timed delay that is applied prior to=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signalling =
the=20
address. The address delay is optional. If the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; address delay =

parameter is not provided, the MG uses the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provisioned =
value by=20
default.&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
integer=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: 0 and up =
in=20
milliseconds </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Question:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>MGC can instruct gateway to out pulse =
digits either=20
in DTMF or MF or dial pulse.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>How MGC can tell gateway about the mode =
of the=20
digits is MF or DTMF or Dial Pulse?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chak</FONT></DIV></BODY></HTML>

------=_NextPart_000_000E_01C1987F.17A5B990--


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



From megaco-admin@ietf.org  Tue Jan  8 10:34:56 2002
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 KAA25802
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 10:34:55 -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 KAA03227;
	Tue, 8 Jan 2002 10:10:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03197
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 10:10:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24730
	for <megaco@ietf.org>; Tue, 8 Jan 2002 10:08:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08F7ot01836;
	Tue, 8 Jan 2002 10:07:50 -0500 (EST)
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 g08F7nN04911;
	Tue, 8 Jan 2002 10:07:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPTKD>; Tue, 8 Jan 2002 10:06:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco CAS
Date: Tue, 8 Jan 2002 10:06:40 -0500 
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

Good point.  What did the authors have in mind?  If the type of outpulsing
is provsioned, the text should say so.

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Tuesday, January 08, 2002 9:30 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco CAS


Hi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5 
    Signal Name: Address 
    SignalID: addr (0x0005) 
    Description: Applies the address signals in the form of either 
          DTMF, dial-pulse or MF-tones on the trunk. The actual 
          frequency, cadence, duration and amplitude values for the 
          multi-frequency tones that convey the address information are 
          provisioned in the MG. 
    Signal Type: (BR) Brief 
    Duration: Provisioned 
    Additional Parameters:  
        Parameter Name: Digit String 
        ParameterID: ds (0x0001) 
        Description: The digit string that needs to be sent as address 
          signals. 
        Type: string of digits. 
        Possible Values: a sequence of the characters "0" through "9" 
          as well as "A" through "H" ("A" through "H" used for MF 
          signalling - refer to the symbols defined for the digit map 
          in the MF Tone Detection package). 
        Parameter Name: Address Delay 
        ParameterID: ad (0x0002) 
        Description: Specifies a timed delay that is applied prior to 
          signalling the address. The address delay is optional. If the 
          address delay parameter is not provided, the MG uses the 
          provisioned value by default.  
        Type: integer 
        Possible Values: 0 and up in milliseconds 

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
Pulse?

Thanks in advance.

Chak

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


From daemon@optimus.ietf.org  Tue Jan  8 10:34:56 2002
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 KAA25813
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 10:34:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA04192
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 10:34:57 -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 KAA03227;
	Tue, 8 Jan 2002 10:10:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03197
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 10:10:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24730
	for <megaco@ietf.org>; Tue, 8 Jan 2002 10:08:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g08F7ot01836;
	Tue, 8 Jan 2002 10:07:50 -0500 (EST)
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 g08F7nN04911;
	Tue, 8 Jan 2002 10:07:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CPSXPTKD>; Tue, 8 Jan 2002 10:06:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco CAS
Date: Tue, 8 Jan 2002 10:06:40 -0500 
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

Good point.  What did the authors have in mind?  If the type of outpulsing
is provsioned, the text should say so.

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Tuesday, January 08, 2002 9:30 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco CAS


Hi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5 
    Signal Name: Address 
    SignalID: addr (0x0005) 
    Description: Applies the address signals in the form of either 
          DTMF, dial-pulse or MF-tones on the trunk. The actual 
          frequency, cadence, duration and amplitude values for the 
          multi-frequency tones that convey the address information are 
          provisioned in the MG. 
    Signal Type: (BR) Brief 
    Duration: Provisioned 
    Additional Parameters:  
        Parameter Name: Digit String 
        ParameterID: ds (0x0001) 
        Description: The digit string that needs to be sent as address 
          signals. 
        Type: string of digits. 
        Possible Values: a sequence of the characters "0" through "9" 
          as well as "A" through "H" ("A" through "H" used for MF 
          signalling - refer to the symbols defined for the digit map 
          in the MF Tone Detection package). 
        Parameter Name: Address Delay 
        ParameterID: ad (0x0002) 
        Description: Specifies a timed delay that is applied prior to 
          signalling the address. The address delay is optional. If the 
          address delay parameter is not provided, the MG uses the 
          provisioned value by default.  
        Type: integer 
        Possible Values: 0 and up in milliseconds 

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
Pulse?

Thanks in advance.

Chak

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



From megaco-admin@ietf.org  Tue Jan  8 11:22:56 2002
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 LAA28187
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 11:22:56 -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 LAA06111;
	Tue, 8 Jan 2002 11:11:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06080
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 11:11:47 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27487
	for <megaco@ietf.org>; Tue, 8 Jan 2002 11:11:45 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFP86942;
	Tue, 8 Jan 2002 11:04:41 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Megaco CAS
Date: Tue, 8 Jan 2002 11:02:49 -0500
Message-ID: <051b01c1985d$ec3bff60$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Tom,Chak,all,
The description of the "addr" it indicates that the "The actual frequency,
cadence, duration and amplitude values for the           multi-frequency
tones" is "provisioned" at the MG. Wont that be sufficient to say that the
type of outpulsing is "provisioned".

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom-PT Taylor
Sent: Tuesday, January 08, 2002 10:07 AM
To: 'PSK Chakravarthi'; megaco@ietf.org
Subject: RE: [Megaco] Megaco CAS


Good point.  What did the authors have in mind?  If the type of outpulsing
is provsioned, the text should say so.

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Tuesday, January 08, 2002 9:30 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco CAS


Hi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5
    Signal Name: Address
    SignalID: addr (0x0005)
    Description: Applies the address signals in the form of either
          DTMF, dial-pulse or MF-tones on the trunk. The actual
          frequency, cadence, duration and amplitude values for the
          multi-frequency tones that convey the address information are
          provisioned in the MG.
    Signal Type: (BR) Brief
    Duration: Provisioned
    Additional Parameters:
        Parameter Name: Digit String
        ParameterID: ds (0x0001)
        Description: The digit string that needs to be sent as address
          signals.
        Type: string of digits.
        Possible Values: a sequence of the characters "0" through "9"
          as well as "A" through "H" ("A" through "H" used for MF
          signalling - refer to the symbols defined for the digit map
          in the MF Tone Detection package).
        Parameter Name: Address Delay
        ParameterID: ad (0x0002)
        Description: Specifies a timed delay that is applied prior to
          signalling the address. The address delay is optional. If the
          address delay parameter is not provided, the MG uses the
          provisioned value by default.
        Type: integer
        Possible Values: 0 and up in milliseconds

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
Pulse?

Thanks in advance.

Chak

_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan  8 12:10:18 2002
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 LAA28194
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jan 2002 11:22:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06428
	for megaco-archive@odin.ietf.org; Tue, 8 Jan 2002 11:22: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 LAA06111;
	Tue, 8 Jan 2002 11:11:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06080
	for <megaco@optimus.ietf.org>; Tue, 8 Jan 2002 11:11:47 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27487
	for <megaco@ietf.org>; Tue, 8 Jan 2002 11:11:45 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFP86942;
	Tue, 8 Jan 2002 11:04:41 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Megaco CAS
Date: Tue, 8 Jan 2002 11:02:49 -0500
Message-ID: <051b01c1985d$ec3bff60$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Content-Transfer-Encoding: 7bit
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: 7bit

HI Tom,Chak,all,
The description of the "addr" it indicates that the "The actual frequency,
cadence, duration and amplitude values for the           multi-frequency
tones" is "provisioned" at the MG. Wont that be sufficient to say that the
type of outpulsing is "provisioned".

Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom-PT Taylor
Sent: Tuesday, January 08, 2002 10:07 AM
To: 'PSK Chakravarthi'; megaco@ietf.org
Subject: RE: [Megaco] Megaco CAS


Good point.  What did the authors have in mind?  If the type of outpulsing
is provsioned, the text should say so.

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Tuesday, January 08, 2002 9:30 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco CAS


Hi List,
As per draft-manyfolks-megaco-caspackage-01.txt Section
6.4.5
    Signal Name: Address
    SignalID: addr (0x0005)
    Description: Applies the address signals in the form of either
          DTMF, dial-pulse or MF-tones on the trunk. The actual
          frequency, cadence, duration and amplitude values for the
          multi-frequency tones that convey the address information are
          provisioned in the MG.
    Signal Type: (BR) Brief
    Duration: Provisioned
    Additional Parameters:
        Parameter Name: Digit String
        ParameterID: ds (0x0001)
        Description: The digit string that needs to be sent as address
          signals.
        Type: string of digits.
        Possible Values: a sequence of the characters "0" through "9"
          as well as "A" through "H" ("A" through "H" used for MF
          signalling - refer to the symbols defined for the digit map
          in the MF Tone Detection package).
        Parameter Name: Address Delay
        ParameterID: ad (0x0002)
        Description: Specifies a timed delay that is applied prior to
          signalling the address. The address delay is optional. If the
          address delay parameter is not provided, the MG uses the
          provisioned value by default.
        Type: integer
        Possible Values: 0 and up in milliseconds

Question:
MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
pulse.
How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
Pulse?

Thanks in advance.

Chak

_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan  9 00:44:13 2002
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 AAA20998
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:44:13 -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 AAA08659;
	Wed, 9 Jan 2002 00:35:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08605
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:08 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20899
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:06 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09908;
	Wed, 9 Jan 2002 16:33:45 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00410;
	Wed, 9 Jan 2002 16:35:03 +1100 (EST)
Message-ID: <3C3B89F4.52671994@ericsson.com.au>
Date: Wed, 09 Jan 2002 11:08:20 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sunesh.Kumra@nokia.com
CC: Brian.Rosen@marconi.com, megaco@ietf.org
Subject: Re: [Megaco] Megaco Interoperability
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D257@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

We also have MGs that are binary only. We have others that are text,
others that are text/binary.

Christian

Sunesh.Kumra@nokia.com wrote:
> 
> we have a business unit who has a Megaco stack (MG side) with only
> binary implementation. We are developing a stack for MGC, which
> currently supports only text, but would have to include binary support
> if the MGs we have to control only understand binary. I would try to
> convince our team developing MG to support Text if not moving totally to
> text.
> 
> -sunesh
> 
> -----Original Message-----
> From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: 07. January 2002 16:37
> To: Seshagiri Rao; megaco@ietf.org
> Subject: RE: [Megaco] Megaco Interoperability
> 
> There is not a reference design available.
> There are test scenarios developed for the bakeoffs.  These explicitly
> DO NOT
> include message sequences.
> I have been stalling on scheduling another bakeoff until we had better
> participation.
>   I plan to "call the question" again soon
> Virtually all implementations are text only.  A few are both (a very
> few).  I don't
> know of any that are binary only.
> 
> Brian
> 
> -----Original Message-----
> From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> Sent: Saturday, January 05, 2002 6:58 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Megaco Interoperability
> 
> All:
> 
> I would like to know if there is any reference design/test sequence for
> Megaco stack implementation.
> I would also like to know if there is any forthcoming interop/bake-off
> event.
> How many of the current Megaco stack implementations support ABNF/Text
> encoding and how many support ASN.1/binary encoding?
> 
> Sesh
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 00:44:13 2002
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 AAA21007
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:44:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA08851
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 00:44:13 -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 AAA08659;
	Wed, 9 Jan 2002 00:35:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08605
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:08 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20899
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:06 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09908;
	Wed, 9 Jan 2002 16:33:45 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00410;
	Wed, 9 Jan 2002 16:35:03 +1100 (EST)
Message-ID: <3C3B89F4.52671994@ericsson.com.au>
Date: Wed, 09 Jan 2002 11:08:20 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sunesh.Kumra@nokia.com
CC: Brian.Rosen@marconi.com, megaco@ietf.org
Subject: Re: [Megaco] Megaco Interoperability
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D257@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

We also have MGs that are binary only. We have others that are text,
others that are text/binary.

Christian

Sunesh.Kumra@nokia.com wrote:
> 
> we have a business unit who has a Megaco stack (MG side) with only
> binary implementation. We are developing a stack for MGC, which
> currently supports only text, but would have to include binary support
> if the MGs we have to control only understand binary. I would try to
> convince our team developing MG to support Text if not moving totally to
> text.
> 
> -sunesh
> 
> -----Original Message-----
> From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: 07. January 2002 16:37
> To: Seshagiri Rao; megaco@ietf.org
> Subject: RE: [Megaco] Megaco Interoperability
> 
> There is not a reference design available.
> There are test scenarios developed for the bakeoffs.  These explicitly
> DO NOT
> include message sequences.
> I have been stalling on scheduling another bakeoff until we had better
> participation.
>   I plan to "call the question" again soon
> Virtually all implementations are text only.  A few are both (a very
> few).  I don't
> know of any that are binary only.
> 
> Brian
> 
> -----Original Message-----
> From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> Sent: Saturday, January 05, 2002 6:58 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Megaco Interoperability
> 
> All:
> 
> I would like to know if there is any reference design/test sequence for
> Megaco stack implementation.
> I would also like to know if there is any forthcoming interop/bake-off
> event.
> How many of the current Megaco stack implementations support ABNF/Text
> encoding and how many support ASN.1/binary encoding?
> 
> Sesh
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 00:44:59 2002
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 AAA21025
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:44:59 -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 AAA08673;
	Wed, 9 Jan 2002 00:35:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08607
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:09 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20900
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:07 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09922;
	Wed, 9 Jan 2002 16:33:48 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00438;
	Wed, 9 Jan 2002 16:35:07 +1100 (EST)
Message-ID: <3C3BAD10.5EF75E8D@ericsson.com.au>
Date: Wed, 09 Jan 2002 13:38:08 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sunesh.Kumra@nokia.com
CC: megaco@ietf.org, Marcello Pantaleo <Marcello.Pantaleo@eed.ericsson.se>
Subject: Re: [Megaco] indAudmuxDescriptor
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D25A@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Sunesh,

It looks like you've found a couple of bugs.
indAudmuxDescriptor should be removed from the ABNF. It wasn't meant to
be included for individual audit as there's only one instance in the
descriptor. I agree that a slash is missing.

Marcello could you capture these bugs in any v2 update?

Regards, Christian



Sunesh.Kumra@nokia.com wrote:
> 
> Hi,
> 
> In v2 of the protocol indAudmuxDescriptor has not been defined. It has
> been mentioned (declared) as one of the possible value for
> indAudauditReturnParameter but not defined anywhere in the draft (pg
> 112).
> On page 105 of the same draft, I think a SLASH (/) is missing in the
> contextAuditProperties.
> 
> Regards,
> sunesh
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 00:45:00 2002
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 AAA21033
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:44:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA08880
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 00:45:00 -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 AAA08673;
	Wed, 9 Jan 2002 00:35:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08607
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:09 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20900
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:07 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09922;
	Wed, 9 Jan 2002 16:33:48 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00438;
	Wed, 9 Jan 2002 16:35:07 +1100 (EST)
Message-ID: <3C3BAD10.5EF75E8D@ericsson.com.au>
Date: Wed, 09 Jan 2002 13:38:08 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sunesh.Kumra@nokia.com
CC: megaco@ietf.org, Marcello Pantaleo <Marcello.Pantaleo@eed.ericsson.se>
Subject: Re: [Megaco] indAudmuxDescriptor
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D25A@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Sunesh,

It looks like you've found a couple of bugs.
indAudmuxDescriptor should be removed from the ABNF. It wasn't meant to
be included for individual audit as there's only one instance in the
descriptor. I agree that a slash is missing.

Marcello could you capture these bugs in any v2 update?

Regards, Christian



Sunesh.Kumra@nokia.com wrote:
> 
> Hi,
> 
> In v2 of the protocol indAudmuxDescriptor has not been defined. It has
> been mentioned (declared) as one of the possible value for
> indAudauditReturnParameter but not defined anywhere in the draft (pg
> 112).
> On page 105 of the same draft, I think a SLASH (/) is missing in the
> contextAuditProperties.
> 
> Regards,
> sunesh
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 00:47:29 2002
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 AAA21075
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:47:29 -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 AAA08710;
	Wed, 9 Jan 2002 00:35:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08661
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:12 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20904
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09928;
	Wed, 9 Jan 2002 16:33:50 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00460;
	Wed, 9 Jan 2002 16:35:09 +1100 (EST)
Message-ID: <3C3BB1A7.6D206AF@ericsson.com.au>
Date: Wed, 09 Jan 2002 13:57:43 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <65256B36.004FC73E.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Vivek,

What exactly do you propose to update in v2?

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> If this is the case, then we need update the same in the v2 draft.
> 
> Regards
> Vivek
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> 
> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> cc:
> 
> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> 
> The immAckRequired flag was introduced because without it a protocol glitch
> was possible, so what you postulate is not a nice situation.  Anyway, to
> answer your question, I would say that retransmission of the final response
> (with exponential backoff) is necessary until an acknowledgement is
> received.
> 
> -----Original Message-----
> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> Sent: Sunday, December 30, 2001 8:23 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt regarding immAckRequired field.
> 
> Hi
> 
> I have a doubt regarding immAckRequired field.
> 
> Section D.1.4 says
> 
> "An entity that sends a provisional response, SHALL include the
> immAckRequired
> field in the ensuing final response, indicating that an immediate
> confirmation
> is expected."
> 
> Now what would happen, if the entity receiving the final response with
> immAckRequired field, does not send the immediate confirmation? In this case
> do
> we need to retransmit the response till we get the confirmation?
> 
> Please clarify.
> 
> Regards
> Vivek
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 00:47:34 2002
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 AAA21085
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 00:47:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA08925
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 00:47:30 -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 AAA08710;
	Wed, 9 Jan 2002 00:35:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA08661
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 00:35:12 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20904
	for <megaco@ietf.org>; Wed, 9 Jan 2002 00:35:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09928;
	Wed, 9 Jan 2002 16:33:50 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA00460;
	Wed, 9 Jan 2002 16:35:09 +1100 (EST)
Message-ID: <3C3BB1A7.6D206AF@ericsson.com.au>
Date: Wed, 09 Jan 2002 13:57:43 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <65256B36.004FC73E.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Vivek,

What exactly do you propose to update in v2?

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> If this is the case, then we need update the same in the v2 draft.
> 
> Regards
> Vivek
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> 
> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> cc:
> 
> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> 
> The immAckRequired flag was introduced because without it a protocol glitch
> was possible, so what you postulate is not a nice situation.  Anyway, to
> answer your question, I would say that retransmission of the final response
> (with exponential backoff) is necessary until an acknowledgement is
> received.
> 
> -----Original Message-----
> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> Sent: Sunday, December 30, 2001 8:23 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt regarding immAckRequired field.
> 
> Hi
> 
> I have a doubt regarding immAckRequired field.
> 
> Section D.1.4 says
> 
> "An entity that sends a provisional response, SHALL include the
> immAckRequired
> field in the ensuing final response, indicating that an immediate
> confirmation
> is expected."
> 
> Now what would happen, if the entity receiving the final response with
> immAckRequired field, does not send the immediate confirmation? In this case
> do
> we need to retransmit the response till we get the confirmation?
> 
> Please clarify.
> 
> Regards
> Vivek
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 02:07:38 2002
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 CAA00145
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:07:38 -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 BAA19478;
	Wed, 9 Jan 2002 01:52:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA19446
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 01:52:34 -0500 (EST)
Received: from mail.lge.co.kr (mail.lge.co.kr [156.147.1.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21850
	for <megaco@ietf.org>; Wed, 9 Jan 2002 01:52:32 -0500 (EST)
Received: from lgekrhqmh01.lge.com (lgekrhqmh01.lge.com [156.147.51.51])
	by mail.lge.co.kr (8.11.3/8.11.3) with ESMTP id g096iCZ07435
	for <megaco@ietf.org>; Wed, 9 Jan 2002 15:44:13 +0900 (KST)
Received: from aeb099w ([150.150.40.209])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002010915470995:1443938 ;
          Wed, 9 Jan 2002 15:47:09 +0900 
Message-ID: <009201c198d8$b73ada90$d1289696@aeb099w>
From: =?ks_c_5601-1987?B?sejFwr/r?= <jeaimetu@lge.com>
To: <megaco@ietf.org>
Date: Wed, 9 Jan 2002 15:41:49 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 03:47:09 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 03:54:51 PM,
	Serialize complete at 01/09/2002 03:54:51 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_008F_01C19924.26DF3800"
Subject: [Megaco] Question about alarm.
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

This is a multi-part message in MIME format.

------=_NextPart_000_008F_01C19924.26DF3800
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGVsbG8uDQoNCkkgaGF2ZSBhIHF1ZXN0aW9uIGZhdWx0IG1hbmFnZW1lbnQgb24gUjQgc3dpdGNo
aW5nIHN5c3RlbS4NCg0KSWYgaGFyZHdhcmUgb3Igc29mdHdhcmUgZmF1bHQgaXMgb2NjdXJlZCBv
biBNZWRpYSBHYXRld2F5LCB0aGVuIE1HDQpyZXBvcnQgdGhhdCBmYXVsdCB0byBNU0Mgc2VydmVy
Pw0KDQpJZiBzbywgaXMgdGhlcmUgYW55IG1ldGhvZCB0byByZXBvcnQgYnkgTUVHQUNPPw0KDQpI
YXZlIGEgbmljZSBkYXkuDQo=

------=_NextPart_000_008F_01C19924.26DF3800
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQ4MDcuMjMwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhlbGxvLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPkkgaGF2ZSZuYnNwO2EgcXVlc3Rpb24gZmF1bHQgbWFuYWdlbWVudCBvbiBS
NCBzd2l0Y2hpbmcgDQpzeXN0ZW0uPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+SWYgaGFyZHdhcmUgb3Igc29mdHdh
cmUgZmF1bHQgaXMgb2NjdXJlZCBvbiBNZWRpYSBHYXRld2F5LCANCnRoZW4gTUc8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxGT05UIHNpemU9Mj5yZXBvcnQgdGhhdCBmYXVsdCB0byBNU0Mgc2VydmVyPzwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPklmIHNvLCBpcyB0aGVyZSBhbnkgbWV0aG9kIHRvIHJlcG9ydCBieSBNRUdB
Q08/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+SGF2ZSBhIG5pY2UgZGF5LjwvRk9OVD48L0RJVj48L0JPRFk+PC9I
VE1MPg0K

------=_NextPart_000_008F_01C19924.26DF3800--


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


From daemon@optimus.ietf.org  Wed Jan  9 02:07:40 2002
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 CAA00155
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:07:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA20031
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 02:07:39 -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 BAA19478;
	Wed, 9 Jan 2002 01:52:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA19446
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 01:52:34 -0500 (EST)
Received: from mail.lge.co.kr (mail.lge.co.kr [156.147.1.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21850
	for <megaco@ietf.org>; Wed, 9 Jan 2002 01:52:32 -0500 (EST)
Received: from lgekrhqmh01.lge.com (lgekrhqmh01.lge.com [156.147.51.51])
	by mail.lge.co.kr (8.11.3/8.11.3) with ESMTP id g096iCZ07435
	for <megaco@ietf.org>; Wed, 9 Jan 2002 15:44:13 +0900 (KST)
Received: from aeb099w ([150.150.40.209])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002010915470995:1443938 ;
          Wed, 9 Jan 2002 15:47:09 +0900 
Message-ID: <009201c198d8$b73ada90$d1289696@aeb099w>
From: =?ks_c_5601-1987?B?sejFwr/r?= <jeaimetu@lge.com>
To: <megaco@ietf.org>
Date: Wed, 9 Jan 2002 15:41:49 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 03:47:09 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 03:54:51 PM,
	Serialize complete at 01/09/2002 03:54:51 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_008F_01C19924.26DF3800"
Subject: [Megaco] Question about alarm.
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

This is a multi-part message in MIME format.

------=_NextPart_000_008F_01C19924.26DF3800
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGVsbG8uDQoNCkkgaGF2ZSBhIHF1ZXN0aW9uIGZhdWx0IG1hbmFnZW1lbnQgb24gUjQgc3dpdGNo
aW5nIHN5c3RlbS4NCg0KSWYgaGFyZHdhcmUgb3Igc29mdHdhcmUgZmF1bHQgaXMgb2NjdXJlZCBv
biBNZWRpYSBHYXRld2F5LCB0aGVuIE1HDQpyZXBvcnQgdGhhdCBmYXVsdCB0byBNU0Mgc2VydmVy
Pw0KDQpJZiBzbywgaXMgdGhlcmUgYW55IG1ldGhvZCB0byByZXBvcnQgYnkgTUVHQUNPPw0KDQpI
YXZlIGEgbmljZSBkYXkuDQo=

------=_NextPart_000_008F_01C19924.26DF3800
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQ4MDcuMjMwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhlbGxvLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPkkgaGF2ZSZuYnNwO2EgcXVlc3Rpb24gZmF1bHQgbWFuYWdlbWVudCBvbiBS
NCBzd2l0Y2hpbmcgDQpzeXN0ZW0uPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+SWYgaGFyZHdhcmUgb3Igc29mdHdh
cmUgZmF1bHQgaXMgb2NjdXJlZCBvbiBNZWRpYSBHYXRld2F5LCANCnRoZW4gTUc8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxGT05UIHNpemU9Mj5yZXBvcnQgdGhhdCBmYXVsdCB0byBNU0Mgc2VydmVyPzwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPklmIHNvLCBpcyB0aGVyZSBhbnkgbWV0aG9kIHRvIHJlcG9ydCBieSBNRUdB
Q08/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+SGF2ZSBhIG5pY2UgZGF5LjwvRk9OVD48L0RJVj48L0JPRFk+PC9I
VE1MPg0K

------=_NextPart_000_008F_01C19924.26DF3800--


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



From megaco-admin@ietf.org  Wed Jan  9 02:22:25 2002
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 CAA00404
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:22:25 -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 CAA20075;
	Wed, 9 Jan 2002 02:07:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20043
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:07:45 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00169
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:07:43 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id BAA28448;
	Wed, 9 Jan 2002 01:07:14 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g09775m00643;
	Wed, 9 Jan 2002 01:07:07 -0600 (CST)
Message-ID: <005601c198dc$e40897c0$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>,
        "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
References: <051b01c1985d$ec3bff60$c500a8c0@MBRAHMANAPALLY>
Subject: Re: [Megaco] Megaco CAS
Date: Wed, 9 Jan 2002 12:41:30 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Madhubabu,

I think it will not be sufficient.  If MG wishes to support outpulsing in more
than one mode (DTMF/MF), then how to instruct MG.  This is required for the MGs
which support both FGD MF and FGD DTMF.

regards,
Chak


----- Original Message -----
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>; "'PSK Chakravarthi'"
<pchakrav@ssd.usa.alcatel.com>; <megaco@ietf.org>
Sent: Tuesday, January 08, 2002 9:32 PM
Subject: RE: [Megaco] Megaco CAS


> HI Tom,Chak,all,
> The description of the "addr" it indicates that the "The actual frequency,
> cadence, duration and amplitude values for the           multi-frequency
> tones" is "provisioned" at the MG. Wont that be sufficient to say that the
> type of outpulsing is "provisioned".
>
> Regards
> Madhubabu
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Tom-PT Taylor
> Sent: Tuesday, January 08, 2002 10:07 AM
> To: 'PSK Chakravarthi'; megaco@ietf.org
> Subject: RE: [Megaco] Megaco CAS
>
>
> Good point.  What did the authors have in mind?  If the type of outpulsing
> is provsioned, the text should say so.
>
> -----Original Message-----
> From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> Sent: Tuesday, January 08, 2002 9:30 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco CAS
>
>
> Hi List,
> As per draft-manyfolks-megaco-caspackage-01.txt Section
> 6.4.5
>     Signal Name: Address
>     SignalID: addr (0x0005)
>     Description: Applies the address signals in the form of either
>           DTMF, dial-pulse or MF-tones on the trunk. The actual
>           frequency, cadence, duration and amplitude values for the
>           multi-frequency tones that convey the address information are
>           provisioned in the MG.
>     Signal Type: (BR) Brief
>     Duration: Provisioned
>     Additional Parameters:
>         Parameter Name: Digit String
>         ParameterID: ds (0x0001)
>         Description: The digit string that needs to be sent as address
>           signals.
>         Type: string of digits.
>         Possible Values: a sequence of the characters "0" through "9"
>           as well as "A" through "H" ("A" through "H" used for MF
>           signalling - refer to the symbols defined for the digit map
>           in the MF Tone Detection package).
>         Parameter Name: Address Delay
>         ParameterID: ad (0x0002)
>         Description: Specifies a timed delay that is applied prior to
>           signalling the address. The address delay is optional. If the
>           address delay parameter is not provided, the MG uses the
>           provisioned value by default.
>         Type: integer
>         Possible Values: 0 and up in milliseconds
>
> Question:
> MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> pulse.
> How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> Pulse?
>
> Thanks in advance.
>
> Chak
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 02:22:25 2002
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 CAA00413
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:22:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA20502
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 02:22:26 -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 CAA20075;
	Wed, 9 Jan 2002 02:07:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20043
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:07:45 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00169
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:07:43 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id BAA28448;
	Wed, 9 Jan 2002 01:07:14 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g09775m00643;
	Wed, 9 Jan 2002 01:07:07 -0600 (CST)
Message-ID: <005601c198dc$e40897c0$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>,
        "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
References: <051b01c1985d$ec3bff60$c500a8c0@MBRAHMANAPALLY>
Subject: Re: [Megaco] Megaco CAS
Date: Wed, 9 Jan 2002 12:41:30 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Madhubabu,

I think it will not be sufficient.  If MG wishes to support outpulsing in more
than one mode (DTMF/MF), then how to instruct MG.  This is required for the MGs
which support both FGD MF and FGD DTMF.

regards,
Chak


----- Original Message -----
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>; "'PSK Chakravarthi'"
<pchakrav@ssd.usa.alcatel.com>; <megaco@ietf.org>
Sent: Tuesday, January 08, 2002 9:32 PM
Subject: RE: [Megaco] Megaco CAS


> HI Tom,Chak,all,
> The description of the "addr" it indicates that the "The actual frequency,
> cadence, duration and amplitude values for the           multi-frequency
> tones" is "provisioned" at the MG. Wont that be sufficient to say that the
> type of outpulsing is "provisioned".
>
> Regards
> Madhubabu
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Tom-PT Taylor
> Sent: Tuesday, January 08, 2002 10:07 AM
> To: 'PSK Chakravarthi'; megaco@ietf.org
> Subject: RE: [Megaco] Megaco CAS
>
>
> Good point.  What did the authors have in mind?  If the type of outpulsing
> is provsioned, the text should say so.
>
> -----Original Message-----
> From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> Sent: Tuesday, January 08, 2002 9:30 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco CAS
>
>
> Hi List,
> As per draft-manyfolks-megaco-caspackage-01.txt Section
> 6.4.5
>     Signal Name: Address
>     SignalID: addr (0x0005)
>     Description: Applies the address signals in the form of either
>           DTMF, dial-pulse or MF-tones on the trunk. The actual
>           frequency, cadence, duration and amplitude values for the
>           multi-frequency tones that convey the address information are
>           provisioned in the MG.
>     Signal Type: (BR) Brief
>     Duration: Provisioned
>     Additional Parameters:
>         Parameter Name: Digit String
>         ParameterID: ds (0x0001)
>         Description: The digit string that needs to be sent as address
>           signals.
>         Type: string of digits.
>         Possible Values: a sequence of the characters "0" through "9"
>           as well as "A" through "H" ("A" through "H" used for MF
>           signalling - refer to the symbols defined for the digit map
>           in the MF Tone Detection package).
>         Parameter Name: Address Delay
>         ParameterID: ad (0x0002)
>         Description: Specifies a timed delay that is applied prior to
>           signalling the address. The address delay is optional. If the
>           address delay parameter is not provided, the MG uses the
>           provisioned value by default.
>         Type: integer
>         Possible Values: 0 and up in milliseconds
>
> Question:
> MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> pulse.
> How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> Pulse?
>
> Thanks in advance.
>
> Chak
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 02:29:10 2002
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 CAA00535
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:29:10 -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 CAA20245;
	Wed, 9 Jan 2002 02:12:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20217
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:12:21 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00211
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:12:19 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g097CFJ04499;
	Wed, 9 Jan 2002 08:12:15 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g097CEhO027547;
	Wed, 9 Jan 2002 09:12:14 +0200 (EET)
Message-ID: <3C3BED4C.85315C4D@lmf.ericsson.se>
Date: Wed, 09 Jan 2002 09:12:12 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: =?iso-8859-1?Q?=B1=E8=C5=C2=BF=EB?= <jeaimetu@lge.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Question about alarm.
References: <009201c198d8$b73ada90$d1289696@aeb099w>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>Hello.
> 
>I have a question fault management on R4 switching system.
> 
>If hardware or software fault is occured on Media Gateway, then MG
>report that fault to MSC server?
> 
>If so, is there any method to report by MEGACO?
> 
>Have a nice day.

The MG uses EVENTS, defined in PACKAGES, to inform the controller (MGC)
about events (faults etc) that occur in the MG. These event detections
are sent using the NOTIFY command.

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Wed Jan  9 02:29:11 2002
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 CAA00544
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:29:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA20639
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 02:29:12 -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 CAA20245;
	Wed, 9 Jan 2002 02:12:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20217
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:12:21 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00211
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:12:19 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g097CFJ04499;
	Wed, 9 Jan 2002 08:12:15 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g097CEhO027547;
	Wed, 9 Jan 2002 09:12:14 +0200 (EET)
Message-ID: <3C3BED4C.85315C4D@lmf.ericsson.se>
Date: Wed, 09 Jan 2002 09:12:12 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: =?iso-8859-1?Q?=B1=E8=C5=C2=BF=EB?= <jeaimetu@lge.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Question about alarm.
References: <009201c198d8$b73ada90$d1289696@aeb099w>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>Hello.
> 
>I have a question fault management on R4 switching system.
> 
>If hardware or software fault is occured on Media Gateway, then MG
>report that fault to MSC server?
> 
>If so, is there any method to report by MEGACO?
> 
>Have a nice day.

The MG uses EVENTS, defined in PACKAGES, to inform the controller (MGC)
about events (faults etc) that occur in the MG. These event detections
are sent using the NOTIFY command.

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Wed Jan  9 02:33:04 2002
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 CAA00623
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:32:59 -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 CAA20489;
	Wed, 9 Jan 2002 02:22:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20460
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:22:18 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00401
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:22:16 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id BAA19645;
	Wed, 9 Jan 2002 01:21:47 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g097Lfm02551;
	Wed, 9 Jan 2002 01:21:42 -0600 (CST)
Message-ID: <006601c198de$ec738580$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>, <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Megaco CAS
Date: Wed, 9 Jan 2002 12:56:05 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Tom,

I think we can have another parameter as given below:

        Parameter Name: Address Type 
        ParameterID: at (0x0003) 
        Description: Specifies Type of address digits.  
        Type: enumeration 
        Possible Values: 
        "DTMF"  (0x0000)  DTMF Digits
        "MF"       (0x0001)  MF Digits
        "DP"        (0x0002)  Dial Pulse Digits

Thanks
Chak

----- Original Message ----- 
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>; <megaco@ietf.org>
Sent: Tuesday, January 08, 2002 8:36 PM
Subject: RE: [Megaco] Megaco CAS


> Good point.  What did the authors have in mind?  If the type of outpulsing
> is provsioned, the text should say so.
> 
> -----Original Message-----
> From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> Sent: Tuesday, January 08, 2002 9:30 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco CAS
> 
> 
> Hi List,
> As per draft-manyfolks-megaco-caspackage-01.txt Section
> 6.4.5 
>     Signal Name: Address 
>     SignalID: addr (0x0005) 
>     Description: Applies the address signals in the form of either 
>           DTMF, dial-pulse or MF-tones on the trunk. The actual 
>           frequency, cadence, duration and amplitude values for the 
>           multi-frequency tones that convey the address information are 
>           provisioned in the MG. 
>     Signal Type: (BR) Brief 
>     Duration: Provisioned 
>     Additional Parameters:  
>         Parameter Name: Digit String 
>         ParameterID: ds (0x0001) 
>         Description: The digit string that needs to be sent as address 
>           signals. 
>         Type: string of digits. 
>         Possible Values: a sequence of the characters "0" through "9" 
>           as well as "A" through "H" ("A" through "H" used for MF 
>           signalling - refer to the symbols defined for the digit map 
>           in the MF Tone Detection package). 
>         Parameter Name: Address Delay 
>         ParameterID: ad (0x0002) 
>         Description: Specifies a timed delay that is applied prior to 
>           signalling the address. The address delay is optional. If the 
>           address delay parameter is not provided, the MG uses the 
>           provisioned value by default.  
>         Type: integer 
>         Possible Values: 0 and up in milliseconds 
> 
> Question:
> MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> pulse.
> How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> Pulse?
> 
> Thanks in advance.
> 
> Chak
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 02:33:04 2002
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 CAA00631
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:33:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA21054
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 02:33:05 -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 CAA20489;
	Wed, 9 Jan 2002 02:22:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20460
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:22:18 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00401
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:22:16 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id BAA19645;
	Wed, 9 Jan 2002 01:21:47 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g097Lfm02551;
	Wed, 9 Jan 2002 01:21:42 -0600 (CST)
Message-ID: <006601c198de$ec738580$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>, <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Megaco CAS
Date: Wed, 9 Jan 2002 12:56:05 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Tom,

I think we can have another parameter as given below:

        Parameter Name: Address Type 
        ParameterID: at (0x0003) 
        Description: Specifies Type of address digits.  
        Type: enumeration 
        Possible Values: 
        "DTMF"  (0x0000)  DTMF Digits
        "MF"       (0x0001)  MF Digits
        "DP"        (0x0002)  Dial Pulse Digits

Thanks
Chak

----- Original Message ----- 
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'PSK Chakravarthi'" <pchakrav@ssd.usa.alcatel.com>; <megaco@ietf.org>
Sent: Tuesday, January 08, 2002 8:36 PM
Subject: RE: [Megaco] Megaco CAS


> Good point.  What did the authors have in mind?  If the type of outpulsing
> is provsioned, the text should say so.
> 
> -----Original Message-----
> From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> Sent: Tuesday, January 08, 2002 9:30 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco CAS
> 
> 
> Hi List,
> As per draft-manyfolks-megaco-caspackage-01.txt Section
> 6.4.5 
>     Signal Name: Address 
>     SignalID: addr (0x0005) 
>     Description: Applies the address signals in the form of either 
>           DTMF, dial-pulse or MF-tones on the trunk. The actual 
>           frequency, cadence, duration and amplitude values for the 
>           multi-frequency tones that convey the address information are 
>           provisioned in the MG. 
>     Signal Type: (BR) Brief 
>     Duration: Provisioned 
>     Additional Parameters:  
>         Parameter Name: Digit String 
>         ParameterID: ds (0x0001) 
>         Description: The digit string that needs to be sent as address 
>           signals. 
>         Type: string of digits. 
>         Possible Values: a sequence of the characters "0" through "9" 
>           as well as "A" through "H" ("A" through "H" used for MF 
>           signalling - refer to the symbols defined for the digit map 
>           in the MF Tone Detection package). 
>         Parameter Name: Address Delay 
>         ParameterID: ad (0x0002) 
>         Description: Specifies a timed delay that is applied prior to 
>           signalling the address. The address delay is optional. If the 
>           address delay parameter is not provided, the MG uses the 
>           provisioned value by default.  
>         Type: integer 
>         Possible Values: 0 and up in milliseconds 
> 
> Question:
> MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> pulse.
> How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> Pulse?
> 
> Thanks in advance.
> 
> Chak
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 02:46:10 2002
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 CAA00795
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:46:10 -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 CAA21135;
	Wed, 9 Jan 2002 02:35:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA21106
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:35:20 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00675
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:35:18 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g097ZJJ24178
	for <megaco@ietf.org>; Wed, 9 Jan 2002 08:35:19 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Wed Jan 09 08:35:17 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKLV0K>; Wed, 9 Jan 2002 08:35:02 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB2E@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Sunesh.Kumra@nokia.com
Cc: megaco@ietf.org
Subject: RE: [Megaco] indAudmuxDescriptor
Date: Wed, 9 Jan 2002 08:35:00 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hello,

I agee too. I'll fix it.
Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Wednesday, January 09, 2002 3:38 AM
To: Sunesh.Kumra@nokia.com
Cc: megaco@ietf.org; Marcello Pantaleo
Subject: Re: [Megaco] indAudmuxDescriptor


G'Day Sunesh,

It looks like you've found a couple of bugs.
indAudmuxDescriptor should be removed from the ABNF. It wasn't meant to
be included for individual audit as there's only one instance in the
descriptor. I agree that a slash is missing.

Marcello could you capture these bugs in any v2 update?

Regards, Christian



Sunesh.Kumra@nokia.com wrote:
> 
> Hi,
> 
> In v2 of the protocol indAudmuxDescriptor has not been defined. It has
> been mentioned (declared) as one of the possible value for
> indAudauditReturnParameter but not defined anywhere in the draft (pg
> 112).
> On page 105 of the same draft, I think a SLASH (/) is missing in the
> contextAuditProperties.
> 
> Regards,
> sunesh
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan  9 02:46:11 2002
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 CAA00805
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 02:46:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA21243
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 02:46:12 -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 CAA21135;
	Wed, 9 Jan 2002 02:35:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA21106
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 02:35:20 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00675
	for <megaco@ietf.org>; Wed, 9 Jan 2002 02:35:18 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g097ZJJ24178
	for <megaco@ietf.org>; Wed, 9 Jan 2002 08:35:19 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Wed Jan 09 08:35:17 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKLV0K>; Wed, 9 Jan 2002 08:35:02 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB2E@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Sunesh.Kumra@nokia.com
Cc: megaco@ietf.org
Subject: RE: [Megaco] indAudmuxDescriptor
Date: Wed, 9 Jan 2002 08:35:00 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hello,

I agee too. I'll fix it.
Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Wednesday, January 09, 2002 3:38 AM
To: Sunesh.Kumra@nokia.com
Cc: megaco@ietf.org; Marcello Pantaleo
Subject: Re: [Megaco] indAudmuxDescriptor


G'Day Sunesh,

It looks like you've found a couple of bugs.
indAudmuxDescriptor should be removed from the ABNF. It wasn't meant to
be included for individual audit as there's only one instance in the
descriptor. I agree that a slash is missing.

Marcello could you capture these bugs in any v2 update?

Regards, Christian



Sunesh.Kumra@nokia.com wrote:
> 
> Hi,
> 
> In v2 of the protocol indAudmuxDescriptor has not been defined. It has
> been mentioned (declared) as one of the possible value for
> indAudauditReturnParameter but not defined anywhere in the draft (pg
> 112).
> On page 105 of the same draft, I think a SLASH (/) is missing in the
> contextAuditProperties.
> 
> Regards,
> sunesh
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan  9 03:47:07 2002
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 DAA01267
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 03:47:07 -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 DAA22840;
	Wed, 9 Jan 2002 03:36:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22807
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 03:36:16 -0500 (EST)
Received: from mail.lge.co.kr (mail.lge.co.kr [156.147.1.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01186
	for <megaco@ietf.org>; Wed, 9 Jan 2002 03:36:12 -0500 (EST)
Received: from lgekrhqmh01.lge.com (lgekrhqmh01.lge.com [156.147.51.51])
	by mail.lge.co.kr (8.11.3/8.11.3) with ESMTP id g097rKZ17573
	for <megaco@ietf.org>; Wed, 9 Jan 2002 16:53:21 +0900 (KST)
Received: from aeb099w ([150.150.40.209])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002010916593980:1452655 ;
          Wed, 9 Jan 2002 16:59:39 +0900 
Message-ID: <00ba01c198e2$d893f2d0$d1289696@aeb099w>
From: "Kim Taeyong" <jeaimetu@lge.com>
To: <megaco@ietf.org>
Date: Wed, 9 Jan 2002 16:54:20 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 04:59:39 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 05:03:58 PM,
	Serialize complete at 01/09/2002 05:03:58 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00B7_01C1992E.485E9CF0"
Subject: [Megaco] Do MG must report critical fault to MSC server?
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

This is a multi-part message in MIME format.

------=_NextPart_000_00B7_01C1992E.485E9CF0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGVsbG8uDQoNCkkgY2FuJ3QgZGV0ZXJtaW5lIHdoZXRoZXIgTUcgcmVwb3J0IEhhcmR3YXJlIG9y
IHNvZnR3YXJlIGZhdWx0IHRvIE1TQyBzZXJ2ZXIgb3Igbm90Lg0KSXMgdGhlcmUgYW55IGltcGxl
bWVudGF0aW9uIGFib3V0IGl0IG9yIGFueSBkb2N1bWVudHMgPw0KDQphbmQgDQpJZiBNRyBtdXN0
IHJlcG9ydCBpdCwgV2hhdCBraW5kIG9mIGZhdWx0IHJlcG9ydGVkIHRvIE1TQyBzZXJ2ZXI/DQoN
CkkgdGhpbmsgaXQgaXMgbm90IGNvcnJlY3QgdGhhdCBhbGwgZmF1bHRzIGFyZSByZXBvcnRlZCB0
byBNU0Mgc2VydmVyLg0KQW0gSSByaWdodD8NCg0KDQoNCg0K

------=_NextPart_000_00B7_01C1992E.485E9CF0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQ4MDcuMjMwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhlbGxvLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPkkgY2FuJ3QgZGV0ZXJtaW5lIHdoZXRoZXIgTUcgcmVwb3J0IEhhcmR3YXJl
IG9yIHNvZnR3YXJlIGZhdWx0IA0KdG8gTVNDIHNlcnZlciBvciBub3QuPC9GT05UPjwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+SXMgdGhlcmUgYW55IGltcGxlbWVudGF0aW9uIGFib3V0IGl0IG9y
IGFueSBkb2N1bWVudHMgDQo/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05U
PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+YW5kIDwvRk9OVD48L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPklmIE1HIG11c3QgcmVwb3J0IGl0LCBXaGF0IGtpbmQgb2YgZmF1bHQgcmVw
b3J0ZWQgdG8gTVNDIA0Kc2VydmVyPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwv
Rk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgdGhpbmsgaXQgaXMgbm90IGNv
cnJlY3QgdGhhdCBhbGwgZmF1bHRzIGFyZSByZXBvcnRlZCB0byBNU0MgDQpzZXJ2ZXIuPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+QW0gSSByaWdodD88L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_00B7_01C1992E.485E9CF0--


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


From daemon@optimus.ietf.org  Wed Jan  9 03:47:08 2002
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 DAA01280
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 03:47:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA23019
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 03:47:10 -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 DAA22840;
	Wed, 9 Jan 2002 03:36:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22807
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 03:36:16 -0500 (EST)
Received: from mail.lge.co.kr (mail.lge.co.kr [156.147.1.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01186
	for <megaco@ietf.org>; Wed, 9 Jan 2002 03:36:12 -0500 (EST)
Received: from lgekrhqmh01.lge.com (lgekrhqmh01.lge.com [156.147.51.51])
	by mail.lge.co.kr (8.11.3/8.11.3) with ESMTP id g097rKZ17573
	for <megaco@ietf.org>; Wed, 9 Jan 2002 16:53:21 +0900 (KST)
Received: from aeb099w ([150.150.40.209])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002010916593980:1452655 ;
          Wed, 9 Jan 2002 16:59:39 +0900 
Message-ID: <00ba01c198e2$d893f2d0$d1289696@aeb099w>
From: "Kim Taeyong" <jeaimetu@lge.com>
To: <megaco@ietf.org>
Date: Wed, 9 Jan 2002 16:54:20 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 04:59:39 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 01/09/2002 05:03:58 PM,
	Serialize complete at 01/09/2002 05:03:58 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00B7_01C1992E.485E9CF0"
Subject: [Megaco] Do MG must report critical fault to MSC server?
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

This is a multi-part message in MIME format.

------=_NextPart_000_00B7_01C1992E.485E9CF0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGVsbG8uDQoNCkkgY2FuJ3QgZGV0ZXJtaW5lIHdoZXRoZXIgTUcgcmVwb3J0IEhhcmR3YXJlIG9y
IHNvZnR3YXJlIGZhdWx0IHRvIE1TQyBzZXJ2ZXIgb3Igbm90Lg0KSXMgdGhlcmUgYW55IGltcGxl
bWVudGF0aW9uIGFib3V0IGl0IG9yIGFueSBkb2N1bWVudHMgPw0KDQphbmQgDQpJZiBNRyBtdXN0
IHJlcG9ydCBpdCwgV2hhdCBraW5kIG9mIGZhdWx0IHJlcG9ydGVkIHRvIE1TQyBzZXJ2ZXI/DQoN
CkkgdGhpbmsgaXQgaXMgbm90IGNvcnJlY3QgdGhhdCBhbGwgZmF1bHRzIGFyZSByZXBvcnRlZCB0
byBNU0Mgc2VydmVyLg0KQW0gSSByaWdodD8NCg0KDQoNCg0K

------=_NextPart_000_00B7_01C1992E.485E9CF0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQ4MDcuMjMwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhlbGxvLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPkkgY2FuJ3QgZGV0ZXJtaW5lIHdoZXRoZXIgTUcgcmVwb3J0IEhhcmR3YXJl
IG9yIHNvZnR3YXJlIGZhdWx0IA0KdG8gTVNDIHNlcnZlciBvciBub3QuPC9GT05UPjwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+SXMgdGhlcmUgYW55IGltcGxlbWVudGF0aW9uIGFib3V0IGl0IG9y
IGFueSBkb2N1bWVudHMgDQo/PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05U
PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+YW5kIDwvRk9OVD48L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPklmIE1HIG11c3QgcmVwb3J0IGl0LCBXaGF0IGtpbmQgb2YgZmF1bHQgcmVw
b3J0ZWQgdG8gTVNDIA0Kc2VydmVyPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwv
Rk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgdGhpbmsgaXQgaXMgbm90IGNv
cnJlY3QgdGhhdCBhbGwgZmF1bHRzIGFyZSByZXBvcnRlZCB0byBNU0MgDQpzZXJ2ZXIuPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+QW0gSSByaWdodD88L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_00B7_01C1992E.485E9CF0--


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



From megaco-admin@ietf.org  Wed Jan  9 04:02:04 2002
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 EAA01439
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:02:04 -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 DAA22983;
	Wed, 9 Jan 2002 03:44:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22952
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 03:44:49 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01252
	for <megaco@ietf.org>; Wed, 9 Jan 2002 03:44:45 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g098jCE07509;
	Wed, 9 Jan 2002 14:15:13 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B3C.002FF32A ; Wed, 9 Jan 2002 14:13:44 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B3C.002FF26A.00@sandesh.hss.hns.com>
Date: Wed, 9 Jan 2002 14:16:48 +0530
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Christian

Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
asked if the entity sending response sends the response with immAckRequired
field, and the entity receiving the response does not send back ACK, then what
should entity sending the response do. To handle this Tom had suggested that the
entity sending rerponse will retransmit the response till it gets the ACK of it.
And this solutions seems fine, otherwise the presence of immAckRequired field in
the message will not make any difference.

This is all that I wanted to be updated in V2.

Regards
Vivek






Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM

To:   Vivek Bansal/HSS@HSS
cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  Re: [Megaco] Doubt regarding immAckRequired field.




G'Day Vivek,

What exactly do you propose to update in v2?

Regards, Christian

vibansal@hss.hns.com wrote:
>
> If this is the case, then we need update the same in the v2 draft.
>
> Regards
> Vivek
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
>
> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> cc:
>
> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
>
> The immAckRequired flag was introduced because without it a protocol glitch
> was possible, so what you postulate is not a nice situation.  Anyway, to
> answer your question, I would say that retransmission of the final response
> (with exponential backoff) is necessary until an acknowledgement is
> received.
>
> -----Original Message-----
> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> Sent: Sunday, December 30, 2001 8:23 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt regarding immAckRequired field.
>
> Hi
>
> I have a doubt regarding immAckRequired field.
>
> Section D.1.4 says
>
> "An entity that sends a provisional response, SHALL include the
> immAckRequired
> field in the ensuing final response, indicating that an immediate
> confirmation
> is expected."
>
> Now what would happen, if the entity receiving the final response with
> immAckRequired field, does not send the immediate confirmation? In this case
> do
> we need to retransmit the response till we get the confirmation?
>
> Please clarify.
>
> Regards
> Vivek
>
> _______________________________________________
> 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





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


From daemon@optimus.ietf.org  Wed Jan  9 04:02:04 2002
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 EAA01448
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:02:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA23695
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 04:02:06 -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 DAA22983;
	Wed, 9 Jan 2002 03:44:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22952
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 03:44:49 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01252
	for <megaco@ietf.org>; Wed, 9 Jan 2002 03:44:45 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g098jCE07509;
	Wed, 9 Jan 2002 14:15:13 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B3C.002FF32A ; Wed, 9 Jan 2002 14:13:44 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B3C.002FF26A.00@sandesh.hss.hns.com>
Date: Wed, 9 Jan 2002 14:16:48 +0530
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Christian

Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
asked if the entity sending response sends the response with immAckRequired
field, and the entity receiving the response does not send back ACK, then what
should entity sending the response do. To handle this Tom had suggested that the
entity sending rerponse will retransmit the response till it gets the ACK of it.
And this solutions seems fine, otherwise the presence of immAckRequired field in
the message will not make any difference.

This is all that I wanted to be updated in V2.

Regards
Vivek






Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM

To:   Vivek Bansal/HSS@HSS
cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  Re: [Megaco] Doubt regarding immAckRequired field.




G'Day Vivek,

What exactly do you propose to update in v2?

Regards, Christian

vibansal@hss.hns.com wrote:
>
> If this is the case, then we need update the same in the v2 draft.
>
> Regards
> Vivek
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
>
> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> cc:
>
> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
>
> The immAckRequired flag was introduced because without it a protocol glitch
> was possible, so what you postulate is not a nice situation.  Anyway, to
> answer your question, I would say that retransmission of the final response
> (with exponential backoff) is necessary until an acknowledgement is
> received.
>
> -----Original Message-----
> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> Sent: Sunday, December 30, 2001 8:23 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt regarding immAckRequired field.
>
> Hi
>
> I have a doubt regarding immAckRequired field.
>
> Section D.1.4 says
>
> "An entity that sends a provisional response, SHALL include the
> immAckRequired
> field in the ensuing final response, indicating that an immediate
> confirmation
> is expected."
>
> Now what would happen, if the entity receiving the final response with
> immAckRequired field, does not send the immediate confirmation? In this case
> do
> we need to retransmit the response till we get the confirmation?
>
> Please clarify.
>
> Regards
> Vivek
>
> _______________________________________________
> 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





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



From megaco-admin@ietf.org  Wed Jan  9 04:34:19 2002
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 EAA01671
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:34:18 -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 EAA24005;
	Wed, 9 Jan 2002 04:24:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA23975
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 04:24:37 -0500 (EST)
Received: from tama5.ecl.ntt.co.jp (tama5.ecl.ntt.co.jp [129.60.39.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01616
	for <megaco@ietf.org>; Wed, 9 Jan 2002 04:24:31 -0500 (EST)
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/09/13/01) with ESMTP id SAA18674
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:27 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from nttmail3.ecl.ntt.co.jp
	by vcs3.rdh.ecl.ntt.co.jp (8.9.3/3.7W/20011217) with ESMTP id SAA07806
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:27 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from eclscan3.m.ecl.ntt.co.jp
	by nttmail3.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/01/09/02) with ESMTP id SAA17147
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:26 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from imb.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id SAA06674
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:26 +0900 (JST)
Received: from ide
	by imb.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id SAA14043
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:25 +0900 (JST)
Message-Id: <4.2.0.58.J.20020109172021.0283fdb0@imb.m.ecl.ntt.co.jp>
X-Sender: sy001@imb.m.ecl.ntt.co.jp
Reply-To: yamamoto.susumu@lab.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 09 Jan 2002 18:24:35 +0900
To: megaco@ietf.org
From: Susumu YAMAMOTO <yamamoto.susumu@lab.ntt.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] failover operation conflicted with handoff operation
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

Hi all,

I have a question on failover operation conflicted with handoff
operation.

If an MG invokes failover to a duplicated MG, in the cause of
failure of the MG or else,  just after receiving handoff message
from an MGC, MG would precede failover operation to handoff
operation.

I think that an MGC should receive failover message from the new
MG taking over the service, and that the MG should not make
response for the handoff message after failover operation.

This is because the MG which sends handoff message to a
MGC MUST be the same as the MG which received corresponding
handoff message from the MGC.

So in this case, the MGC should abort handoff operation by
receiving failover message from an MG which has taken over the
service from the MG the handoff message sent to.

Is my idea true?
Please give me comments.

Thanks,

Susumu

-*-*-*
SUSUMU YAMAMOTO, NTT Corporation


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


From daemon@optimus.ietf.org  Wed Jan  9 04:34:19 2002
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 EAA01681
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:34:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA24583
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 04:34:21 -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 EAA24005;
	Wed, 9 Jan 2002 04:24:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA23975
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 04:24:37 -0500 (EST)
Received: from tama5.ecl.ntt.co.jp (tama5.ecl.ntt.co.jp [129.60.39.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01616
	for <megaco@ietf.org>; Wed, 9 Jan 2002 04:24:31 -0500 (EST)
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/09/13/01) with ESMTP id SAA18674
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:27 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from nttmail3.ecl.ntt.co.jp
	by vcs3.rdh.ecl.ntt.co.jp (8.9.3/3.7W/20011217) with ESMTP id SAA07806
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:27 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from eclscan3.m.ecl.ntt.co.jp
	by nttmail3.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/01/09/02) with ESMTP id SAA17147
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:26 +0900 (JST)
	(envelope-from yamamoto.susumu@lab.ntt.co.jp)
Received: from imb.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id SAA06674
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:26 +0900 (JST)
Received: from ide
	by imb.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id SAA14043
	for <megaco@ietf.org>; Wed, 9 Jan 2002 18:24:25 +0900 (JST)
Message-Id: <4.2.0.58.J.20020109172021.0283fdb0@imb.m.ecl.ntt.co.jp>
X-Sender: sy001@imb.m.ecl.ntt.co.jp
Reply-To: yamamoto.susumu@lab.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 09 Jan 2002 18:24:35 +0900
To: megaco@ietf.org
From: Susumu YAMAMOTO <yamamoto.susumu@lab.ntt.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] failover operation conflicted with handoff operation
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

Hi all,

I have a question on failover operation conflicted with handoff
operation.

If an MG invokes failover to a duplicated MG, in the cause of
failure of the MG or else,  just after receiving handoff message
from an MGC, MG would precede failover operation to handoff
operation.

I think that an MGC should receive failover message from the new
MG taking over the service, and that the MG should not make
response for the handoff message after failover operation.

This is because the MG which sends handoff message to a
MGC MUST be the same as the MG which received corresponding
handoff message from the MGC.

So in this case, the MGC should abort handoff operation by
receiving failover message from an MG which has taken over the
service from the MG the handoff message sent to.

Is my idea true?
Please give me comments.

Thanks,

Susumu

-*-*-*
SUSUMU YAMAMOTO, NTT Corporation


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



From megaco-admin@ietf.org  Wed Jan  9 04:56:35 2002
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 EAA01813
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:56:35 -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 EAA24901;
	Wed, 9 Jan 2002 04:43:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24805
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 04:43:04 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA01733
	for <megaco@ietf.org>; Wed, 9 Jan 2002 04:42:55 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Wed Jan 09 11:58:51 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FLTC>; Wed, 9 Jan 2002 11:33:34 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF017F85C9@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Wed, 9 Jan 2002 11:33:32 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C198F0.B44CCE70"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C198F0.B44CCE70
Content-Type: text/plain;
	charset="iso-8859-1"

I have some questions related to this discussion.

1.	What should an entity receiving a response do if the immAckRequired
field is absent?  Is sending ACK at other times optional?
2.	When an entity sends ACK because it received a response with
immAckRequired, should it ACK only that transaction, or also other
transactions for which it recently received responses, but where no
immAckRequired was specified?
3.	In the previous question, is there a precise definition of
"recently"?
4.	When an entity sends ACK with a transaction id range, may the
recipient of the ACK assume that every number in the range represents a
transaction that was actually sent?  Or is the sender of the ACK permitted
to send a range even though it only used some of the transaction numbers in
that range, and the meaning is "whatever transactions in this range I sent,
I got your answers"?


Raphael Tryster


	-----Original Message-----
	From:	vibansal@hss.hns.com [SMTP:vibansal@hss.hns.com]
	Sent:	Wednesday, 09 January, 2002 10:47 AM
	To:	Christian Groves
	Cc:	Tom-PT Taylor; megaco@ietf.org
	Subject:	Re: [Megaco] Doubt regarding immAckRequired field.




	Hi Christian

	Regarding the Immediate ACK nothing has been mentioned in the
protocol. I had
	asked if the entity sending response sends the response with
immAckRequired
	field, and the entity receiving the response does not send back ACK,
then what
	should entity sending the response do. To handle this Tom had
suggested that the
	entity sending rerponse will retransmit the response till it gets
the ACK of it.
	And this solutions seems fine, otherwise the presence of
immAckRequired field in
	the message will not make any difference.

	This is all that I wanted to be updated in V2.

	Regards
	Vivek






	Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002
08:27:43 AM

	To:   Vivek Bansal/HSS@HSS
	cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org

	Subject:  Re: [Megaco] Doubt regarding immAckRequired field.




	G'Day Vivek,

	What exactly do you propose to update in v2?

	Regards, Christian

	vibansal@hss.hns.com wrote:
	>
	> If this is the case, then we need update the same in the v2 draft.
	>
	> Regards
	> Vivek
	>
	> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02
AM
	>
	> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
	> cc:
	>
	> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
	>
	> The immAckRequired flag was introduced because without it a
protocol glitch
	> was possible, so what you postulate is not a nice situation.
Anyway, to
	> answer your question, I would say that retransmission of the final
response
	> (with exponential backoff) is necessary until an acknowledgement
is
	> received.
	>
	> -----Original Message-----
	> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
	> Sent: Sunday, December 30, 2001 8:23 AM
	> To: megaco@ietf.org
	> Subject: [Megaco] Doubt regarding immAckRequired field.
	>
	> Hi
	>
	> I have a doubt regarding immAckRequired field.
	>
	> Section D.1.4 says
	>
	> "An entity that sends a provisional response, SHALL include the
	> immAckRequired
	> field in the ensuing final response, indicating that an immediate
	> confirmation
	> is expected."
	>
	> Now what would happen, if the entity receiving the final response
with
	> immAckRequired field, does not send the immediate confirmation? In
this case
	> do
	> we need to retransmit the response till we get the confirmation?
	>
	> Please clarify.
	>
	> Regards
	> Vivek
	>
	> _______________________________________________
	> 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





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

------_=_NextPart_001_01C198F0.B44CCE70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] Doubt regarding immAckRequired field.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have some questions related to this di=
scussion.</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">What should an entity rece=
iving a response do if the</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckReq=
uired</FONT><FONT SIZE=3D2 FACE=3D"Arial"> field is absent?&nbsp; Is send=
ing ACK at other times optional?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When an entity sends ACK because it rec=
eived a response with</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckRequired=
</FONT><FONT SIZE=3D2 FACE=3D"Arial">, should it ACK only that transactio=
n, or also other transactions for which it recently received responses, b=
ut where no</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckRequired</FONT><FO=
NT SIZE=3D2 FACE=3D"Arial"> was specified?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In the previous question, is there a pr=
ecise definition of "recently"?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When an entity sends ACK with a transac=
tion id range, may the recipient of the ACK assume that every number in t=
he range represents a transaction that was actually sent?&nbsp; Or is the=
 sender of the ACK permitted to send a range even though it only used som=
e of the transaction numbers in that range, and the meaning is "whatever =
transactions in this range I sent, I got your answers"?</FONT></LI>
<BR>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; vibansal@hss.hns.c=
om [SMTP:vibansal@hss.hns.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Wednesday, 09 January, 2002 10:47 AM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Tom-PT Taylor; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Megaco] Doub=
t regarding immAckRequired field.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Hi Christian</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regarding the Immediate ACK nothin=
g has been mentioned in the protocol. I had</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">asked if the entity sending respo=
nse sends the response with immAckRequired</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">field, and the entity receiving t=
he response does not send back ACK, then what</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">should entity sending the respons=
e do. To handle this Tom had suggested that the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">entity sending rerponse will retr=
ansmit the response till it gets the ACK of it.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">And this solutions seems fine, ot=
herwise the presence of immAckRequired field in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">the message will not make any dif=
ference.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">This is all that I wanted to be up=
dated in V2.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Vivek</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves &lt;Christian.Gro=
ves@ericsson.com.au&gt; on 01/09/2002 08:27:43 AM</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">To:&nbsp;&nbsp; Vivek Bansal/HSS@H=
SS</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">cc:&nbsp;&nbsp; Tom-PT Taylor &lt=
;taylor@nortelnetworks.com&gt;, megaco@ietf.org</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Subject:&nbsp; Re: [Megaco] Doubt =
regarding immAckRequired field.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">G'Day Vivek,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">What exactly do you propose to upd=
ate in v2?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regards, Christian</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">vibansal@hss.hns.com wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; If this is the case, then we=
 need update the same in the v2 draft.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Vivek</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &quot;Tom-PT Taylor&quot; &l=
t;taylor@nortelnetworks.com&gt; on 01/03/2002 01:06:02 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; To:&nbsp;&nbsp; Vivek Bansal=
/HSS@HSS, megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; cc:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Subject:&nbsp; RE: [Megaco] =
Doubt regarding immAckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The immAckRequired flag was =
introduced because without it a protocol glitch</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; was possible, so what you po=
stulate is not a nice situation.&nbsp; Anyway, to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; answer your question, I woul=
d say that retransmission of the final response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; (with exponential backoff) i=
s necessary until an acknowledgement is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; received.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; -----Original Message-----</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; From: vibansal@hss.hns.com [=
<A HREF=3D"mailto:vibansal@hss.hns.com">mailto:vibansal@hss.hns.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Sent: Sunday, December 30, 2=
001 8:23 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Subject: [Megaco] Doubt rega=
rding immAckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Hi</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; I have a doubt regarding imm=
AckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Section D.1.4 says</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &quot;An entity that sends a=
 provisional response, SHALL include the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; immAckRequired</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; field in the ensuing final r=
esponse, indicating that an immediate</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; confirmation</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; is expected.&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Now what would happen, if th=
e entity receiving the final response with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; immAckRequired field, does n=
ot send the immediate confirmation? In this case</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; do</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; we need to retransmit the re=
sponse till we get the confirmation?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Please clarify.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Vivek</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">__________________________________=
_____________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"https://www1.ietf.org/=
mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ietf.org/mailman/=
listinfo/megaco</A></FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">__________________________________=
_____________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"https://www1.ietf.org/=
mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ietf.org/mailman/=
listinfo/megaco</A></FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C198F0.B44CCE70--

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


From daemon@optimus.ietf.org  Wed Jan  9 04:56:36 2002
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 EAA01823
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 04:56:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA25207
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 04:56:39 -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 EAA24901;
	Wed, 9 Jan 2002 04:43:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24805
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 04:43:04 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA01733
	for <megaco@ietf.org>; Wed, 9 Jan 2002 04:42:55 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Wed Jan 09 11:58:51 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FLTC>; Wed, 9 Jan 2002 11:33:34 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF017F85C9@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Wed, 9 Jan 2002 11:33:32 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C198F0.B44CCE70"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C198F0.B44CCE70
Content-Type: text/plain;
	charset="iso-8859-1"

I have some questions related to this discussion.

1.	What should an entity receiving a response do if the immAckRequired
field is absent?  Is sending ACK at other times optional?
2.	When an entity sends ACK because it received a response with
immAckRequired, should it ACK only that transaction, or also other
transactions for which it recently received responses, but where no
immAckRequired was specified?
3.	In the previous question, is there a precise definition of
"recently"?
4.	When an entity sends ACK with a transaction id range, may the
recipient of the ACK assume that every number in the range represents a
transaction that was actually sent?  Or is the sender of the ACK permitted
to send a range even though it only used some of the transaction numbers in
that range, and the meaning is "whatever transactions in this range I sent,
I got your answers"?


Raphael Tryster


	-----Original Message-----
	From:	vibansal@hss.hns.com [SMTP:vibansal@hss.hns.com]
	Sent:	Wednesday, 09 January, 2002 10:47 AM
	To:	Christian Groves
	Cc:	Tom-PT Taylor; megaco@ietf.org
	Subject:	Re: [Megaco] Doubt regarding immAckRequired field.




	Hi Christian

	Regarding the Immediate ACK nothing has been mentioned in the
protocol. I had
	asked if the entity sending response sends the response with
immAckRequired
	field, and the entity receiving the response does not send back ACK,
then what
	should entity sending the response do. To handle this Tom had
suggested that the
	entity sending rerponse will retransmit the response till it gets
the ACK of it.
	And this solutions seems fine, otherwise the presence of
immAckRequired field in
	the message will not make any difference.

	This is all that I wanted to be updated in V2.

	Regards
	Vivek






	Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002
08:27:43 AM

	To:   Vivek Bansal/HSS@HSS
	cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org

	Subject:  Re: [Megaco] Doubt regarding immAckRequired field.




	G'Day Vivek,

	What exactly do you propose to update in v2?

	Regards, Christian

	vibansal@hss.hns.com wrote:
	>
	> If this is the case, then we need update the same in the v2 draft.
	>
	> Regards
	> Vivek
	>
	> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02
AM
	>
	> To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
	> cc:
	>
	> Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
	>
	> The immAckRequired flag was introduced because without it a
protocol glitch
	> was possible, so what you postulate is not a nice situation.
Anyway, to
	> answer your question, I would say that retransmission of the final
response
	> (with exponential backoff) is necessary until an acknowledgement
is
	> received.
	>
	> -----Original Message-----
	> From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
	> Sent: Sunday, December 30, 2001 8:23 AM
	> To: megaco@ietf.org
	> Subject: [Megaco] Doubt regarding immAckRequired field.
	>
	> Hi
	>
	> I have a doubt regarding immAckRequired field.
	>
	> Section D.1.4 says
	>
	> "An entity that sends a provisional response, SHALL include the
	> immAckRequired
	> field in the ensuing final response, indicating that an immediate
	> confirmation
	> is expected."
	>
	> Now what would happen, if the entity receiving the final response
with
	> immAckRequired field, does not send the immediate confirmation? In
this case
	> do
	> we need to retransmit the response till we get the confirmation?
	>
	> Please clarify.
	>
	> Regards
	> Vivek
	>
	> _______________________________________________
	> 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





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

------_=_NextPart_001_01C198F0.B44CCE70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] Doubt regarding immAckRequired field.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have some questions related to this di=
scussion.</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">What should an entity rece=
iving a response do if the</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckReq=
uired</FONT><FONT SIZE=3D2 FACE=3D"Arial"> field is absent?&nbsp; Is send=
ing ACK at other times optional?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When an entity sends ACK because it rec=
eived a response with</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckRequired=
</FONT><FONT SIZE=3D2 FACE=3D"Arial">, should it ACK only that transactio=
n, or also other transactions for which it recently received responses, b=
ut where no</FONT> <FONT SIZE=3D2 FACE=3D"Arial">immAckRequired</FONT><FO=
NT SIZE=3D2 FACE=3D"Arial"> was specified?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In the previous question, is there a pr=
ecise definition of "recently"?</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When an entity sends ACK with a transac=
tion id range, may the recipient of the ACK assume that every number in t=
he range represents a transaction that was actually sent?&nbsp; Or is the=
 sender of the ACK permitted to send a range even though it only used som=
e of the transaction numbers in that range, and the meaning is "whatever =
transactions in this range I sent, I got your answers"?</FONT></LI>
<BR>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; vibansal@hss.hns.c=
om [SMTP:vibansal@hss.hns.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Wednesday, 09 January, 2002 10:47 AM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Tom-PT Taylor; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Megaco] Doub=
t regarding immAckRequired field.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Hi Christian</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regarding the Immediate ACK nothin=
g has been mentioned in the protocol. I had</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">asked if the entity sending respo=
nse sends the response with immAckRequired</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">field, and the entity receiving t=
he response does not send back ACK, then what</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">should entity sending the respons=
e do. To handle this Tom had suggested that the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">entity sending rerponse will retr=
ansmit the response till it gets the ACK of it.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">And this solutions seems fine, ot=
herwise the presence of immAckRequired field in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">the message will not make any dif=
ference.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">This is all that I wanted to be up=
dated in V2.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Vivek</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves &lt;Christian.Gro=
ves@ericsson.com.au&gt; on 01/09/2002 08:27:43 AM</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">To:&nbsp;&nbsp; Vivek Bansal/HSS@H=
SS</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">cc:&nbsp;&nbsp; Tom-PT Taylor &lt=
;taylor@nortelnetworks.com&gt;, megaco@ietf.org</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Subject:&nbsp; Re: [Megaco] Doubt =
regarding immAckRequired field.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">G'Day Vivek,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">What exactly do you propose to upd=
ate in v2?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regards, Christian</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">vibansal@hss.hns.com wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; If this is the case, then we=
 need update the same in the v2 draft.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Vivek</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &quot;Tom-PT Taylor&quot; &l=
t;taylor@nortelnetworks.com&gt; on 01/03/2002 01:06:02 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; To:&nbsp;&nbsp; Vivek Bansal=
/HSS@HSS, megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; cc:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Subject:&nbsp; RE: [Megaco] =
Doubt regarding immAckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The immAckRequired flag was =
introduced because without it a protocol glitch</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; was possible, so what you po=
stulate is not a nice situation.&nbsp; Anyway, to</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; answer your question, I woul=
d say that retransmission of the final response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; (with exponential backoff) i=
s necessary until an acknowledgement is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; received.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; -----Original Message-----</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; From: vibansal@hss.hns.com [=
<A HREF=3D"mailto:vibansal@hss.hns.com">mailto:vibansal@hss.hns.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Sent: Sunday, December 30, 2=
001 8:23 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Subject: [Megaco] Doubt rega=
rding immAckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Hi</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; I have a doubt regarding imm=
AckRequired field.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Section D.1.4 says</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &quot;An entity that sends a=
 provisional response, SHALL include the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; immAckRequired</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; field in the ensuing final r=
esponse, indicating that an immediate</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; confirmation</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; is expected.&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Now what would happen, if th=
e entity receiving the final response with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; immAckRequired field, does n=
ot send the immediate confirmation? In this case</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; do</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; we need to retransmit the re=
sponse till we get the confirmation?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Please clarify.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Vivek</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; ____________________________=
___________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; <A HREF=3D"https://www1.ietf=

lman/listinfo/megaco</A></FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">__________________________________=
_____________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"https://www1.ietf.org/=
mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ietf.org/mailman/=
listinfo/megaco</A></FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">__________________________________=
_____________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"https://www1.ietf.org/=
mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ietf.org/mailman/=
listinfo/megaco</A></FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C198F0.B44CCE70--

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



From megaco-admin@ietf.org  Wed Jan  9 07:07:00 2002
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 HAA02877
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 07:07:00 -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 GAA28299;
	Wed, 9 Jan 2002 06:57:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28272
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 06:57:00 -0500 (EST)
Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02759
	for <megaco@ietf.org>; Wed, 9 Jan 2002 06:56:57 -0500 (EST)
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g09BuvW11313
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:56:57 +0100 (MET)
Received: from poseidon.siemens.gr (poseidon.siemens.gr [141.29.40.250])
	by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g09Buug16764
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:56:56 +0100 (MET)
Received: by poseidon.siemens.gr with Internet Mail Service (5.5.2653.19)
	id <CH1CAW8F>; Wed, 9 Jan 2002 13:56:56 +0200
Message-ID: <2ECFB18E44E2D511A0C80002B32B056B28E878@PROMETHEUS>
From: Stefanioros Nikolaos <Nikolaos.Stefanioros@siemens.gr>
To: megaco@ietf.org
Date: Wed, 9 Jan 2002 13:56:49 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Question regarding ISDN terminations.
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

Hi,

could anyone inform me if there is any call flow for a call between 2 MGs
with ISDN terminations, using Megaco and Sigtran protocols?

Thanx.

Nikos.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 974803815
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



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


From daemon@optimus.ietf.org  Wed Jan  9 07:07:01 2002
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 HAA02887
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 07:07:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA28835
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 07:07:03 -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 GAA28299;
	Wed, 9 Jan 2002 06:57:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28272
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 06:57:00 -0500 (EST)
Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02759
	for <megaco@ietf.org>; Wed, 9 Jan 2002 06:56:57 -0500 (EST)
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g09BuvW11313
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:56:57 +0100 (MET)
Received: from poseidon.siemens.gr (poseidon.siemens.gr [141.29.40.250])
	by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id g09Buug16764
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:56:56 +0100 (MET)
Received: by poseidon.siemens.gr with Internet Mail Service (5.5.2653.19)
	id <CH1CAW8F>; Wed, 9 Jan 2002 13:56:56 +0200
Message-ID: <2ECFB18E44E2D511A0C80002B32B056B28E878@PROMETHEUS>
From: Stefanioros Nikolaos <Nikolaos.Stefanioros@siemens.gr>
To: megaco@ietf.org
Date: Wed, 9 Jan 2002 13:56:49 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Question regarding ISDN terminations.
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

Hi,

could anyone inform me if there is any call flow for a call between 2 MGs
with ISDN terminations, using Megaco and Sigtran protocols?

Thanx.

Nikos.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 974803815
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



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



From megaco-admin@ietf.org  Wed Jan  9 07:32:33 2002
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 HAA03070
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 07:32:33 -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 HAA29065;
	Wed, 9 Jan 2002 07:17:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA29035
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:17:20 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02973
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:17:16 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001659116@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 09 Jan 2002 17:35:41 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g09BoiR16986;
	Wed, 9 Jan 2002 17:20:44 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Wed, 9 Jan 2002 17:20:51 +0530
Message-Id: <001a01c19903$e3854c40$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] UnSpecified Local or Remote Descriptor
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: 7bit

Hi,

It was given in RFC 3015 as "An unspecified Local or Remote descriptor
requires the MG to use
whatever was last specified for that descriptor".

I want to know whether the above statement is valid for a specified Ephermal
Termination or
for a specified Context or for a whole MG.

One more thing, in the above statement, what "last specified" indicates.
Suppose MGC
sends Under Specified SDP parameters (using CHOOSE) in Local descriptor and
MG replies with Specified values, then "last specified" indicates the "Under
Specified
SDP parameters sent by the MGC"or "Specified SDP parameters sent by the MG"

Thanks,
Sudhir



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


From daemon@optimus.ietf.org  Wed Jan  9 07:32:34 2002
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 HAA03079
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 07:32:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA29659
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 07:32:36 -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 HAA29065;
	Wed, 9 Jan 2002 07:17:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA29035
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:17:20 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02973
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:17:16 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001659116@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 09 Jan 2002 17:35:41 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g09BoiR16986;
	Wed, 9 Jan 2002 17:20:44 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Wed, 9 Jan 2002 17:20:51 +0530
Message-Id: <001a01c19903$e3854c40$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] UnSpecified Local or Remote Descriptor
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: 7bit

Hi,

It was given in RFC 3015 as "An unspecified Local or Remote descriptor
requires the MG to use
whatever was last specified for that descriptor".

I want to know whether the above statement is valid for a specified Ephermal
Termination or
for a specified Context or for a whole MG.

One more thing, in the above statement, what "last specified" indicates.
Suppose MGC
sends Under Specified SDP parameters (using CHOOSE) in Local descriptor and
MG replies with Specified values, then "last specified" indicates the "Under
Specified
SDP parameters sent by the MGC"or "Specified SDP parameters sent by the MG"

Thanks,
Sudhir



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



From megaco-admin@ietf.org  Wed Jan  9 08:04:24 2002
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 IAA03304
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 08:04:23 -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 HAA00015;
	Wed, 9 Jan 2002 07:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA29981
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:53:44 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03210
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:53:40 -0500 (EST)
Received: (qmail 2746 invoked by uid 510); 9 Jan 2002 12:53:41 -0000
Date: 9 Jan 2002 12:53:41 -0000
Message-ID: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 09 Jan 2002 12:53:41 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA29982
Subject: [Megaco] new to megaco
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


hi all

    I am new to megaco and now I am into an MG development. can any one send me a kind of tutorial kind of material which covers the issues in the development. I have experience of developing H248 protocol stack ( encoding and decoding ).

regs
sree 


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


From daemon@optimus.ietf.org  Wed Jan  9 08:04:24 2002
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 IAA03316
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 08:04:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA00570
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 08:04:27 -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 HAA00015;
	Wed, 9 Jan 2002 07:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA29981
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:53:44 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03210
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:53:40 -0500 (EST)
Received: (qmail 2746 invoked by uid 510); 9 Jan 2002 12:53:41 -0000
Date: 9 Jan 2002 12:53:41 -0000
Message-ID: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 09 Jan 2002 12:53:41 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA29982
Subject: [Megaco] new to megaco
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


hi all

    I am new to megaco and now I am into an MG development. can any one send me a kind of tutorial kind of material which covers the issues in the development. I have experience of developing H248 protocol stack ( encoding and decoding ).

regs
sree 


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



From megaco-admin@ietf.org  Wed Jan  9 08:05:53 2002
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 IAA03339
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 08:05:53 -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 HAA00060;
	Wed, 9 Jan 2002 07:54:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00029
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:54:03 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03217
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:53:58 -0500 (EST)
Received: (qmail 3085 invoked by uid 510); 9 Jan 2002 12:54:02 -0000
Date: 9 Jan 2002 12:54:02 -0000
Message-ID: <20020109125402.3084.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 09 Jan 2002 12:54:02 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA00030
Subject: [Megaco] new to megaco
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


hi all

    I am new to megaco and now I am into an MG development. can any one send me a kind of tutorial kind of material which covers the issues in the development. I have experience of developing H248 protocol stack ( encoding and decoding ).

regs
sree 


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


From daemon@optimus.ietf.org  Wed Jan  9 08:05:54 2002
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 IAA03348
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 08:05:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA00648
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 08:05:56 -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 HAA00060;
	Wed, 9 Jan 2002 07:54:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00029
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 07:54:03 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03217
	for <megaco@ietf.org>; Wed, 9 Jan 2002 07:53:58 -0500 (EST)
Received: (qmail 3085 invoked by uid 510); 9 Jan 2002 12:54:02 -0000
Date: 9 Jan 2002 12:54:02 -0000
Message-ID: <20020109125402.3084.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 09 Jan 2002 12:54:02 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA00030
Subject: [Megaco] new to megaco
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


hi all

    I am new to megaco and now I am into an MG development. can any one send me a kind of tutorial kind of material which covers the issues in the development. I have experience of developing H248 protocol stack ( encoding and decoding ).

regs
sree 


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



From megaco-admin@ietf.org  Wed Jan  9 12:00:39 2002
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 MAA07263
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 12:00:39 -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 LAA09931;
	Wed, 9 Jan 2002 11:49:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09902
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 11:49:40 -0500 (EST)
Received: from mtiwmhc22.worldnet.att.net (mtiwmhc22.worldnet.att.net [204.127.131.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07121
	for <megaco@ietf.org>; Wed, 9 Jan 2002 11:49:36 -0500 (EST)
Received: from varneyhome.ieee.org ([12.84.123.134])
          by mtiwmhc22.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020109164908.XWDM941.mtiwmhc22.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Wed, 9 Jan 2002 16:49:08 +0000
Message-Id: <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Jan 2002 10:48:09 -0600
To: <megaco@ietf.org>
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] Megaco CAS
In-Reply-To: <006601c198de$ec738580$3401ff0a@axsppc02>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Chak,
    At first, I thought the Description of "provisioned" frequency, 
cadence, etc. could be clarified as a per-trunk attribute (not per MG, as 
some might read it).  That is, MF trunks always used MF signaling, etc.  On 
further reflection, this is insufficient to emulate some forms of older 
signaling used in the USA.  For example, some circuits signal using Dial 
Pulse in a first stage, followed by MF in the second.  Also, it might be 
useful to force DTMF signaling over an MF trunk which is already connected 
on a call (although that goes beyond the function typically associated with 
the acronym "CAS").

    So I'm agreeing with you, with a small suggestion below:

At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
>I think we can have another parameter as given below:
>
>         Parameter Name: Address Type
>         ParameterID: at (0x0003)
>         Description: Specifies Type of address digits.
>         Type: enumeration
>         Possible Values:
>         "DTMF"  (0x0000)  DTMF Digits
>         "MF"       (0x0001)  MF Digits
>         "DP"        (0x0002)  Dial Pulse Digits

    It might be less confusing if the word "Type" was not used in the Name 
or Description, since it is part of the meta-language of MEGACO 
packages.  I used "Coding" below, but another word might be better.  Also, 
you offered no default text in the Description -- did you really want 
"Address Type" to be included in every use of "addr"?

      Alternative Name/ID/Description for consideration:
  Parameter Name: Address Coding
  ParameterID: ac (0x0003)
  Description: Specifies the coding of Digit String parameter
           in tones or DC pulses.  Address Coding is optional;
           if not provided, the MG uses the value provisioned
           as an attribute of the circuit associated with the
           signal.

    Would it be useful to mention an error case if Address Coding is not 
present and the "circuit" has no 'ac' value provisioned?  (For example, 
could CAS package be used to signal over an ephemeral?)

    On second thought, having 'ac' optional might be a mistake.  It forces 
the MGC to "know" the coding for every circuit.  (The 
provisioned-per-MG-circuit option allows the MGC to be ignorant of the 
coding.)  I think it unlikely that the MGC could be ignorant of MF vs. DTMF 
vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is 
just asking for an error.

Al Varney - varney@ieee.org

> > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > Hi List,
> > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > 6.4.5
> >     Signal Name: Address
> >     SignalID: addr (0x0005)
> >     Description: Applies the address signals in the form of either
> >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> >           frequency, cadence, duration and amplitude values for the
> >           multi-frequency tones that convey the address information are
> >           provisioned in the MG.
> >     Signal Type: (BR) Brief
> >     Duration: Provisioned
> >     Additional Parameters:
> >         Parameter Name: Digit String
> >         ParameterID: ds (0x0001)
> >         Description: The digit string that needs to be sent as address
> >           signals.
> >         Type: string of digits.
> >         Possible Values: a sequence of the characters "0" through "9"
> >           as well as "A" through "H" ("A" through "H" used for MF
> >           signalling - refer to the symbols defined for the digit map
> >           in the MF Tone Detection package).
> >         Parameter Name: Address Delay
> >         ParameterID: ad (0x0002)
> >         Description: Specifies a timed delay that is applied prior to
> >           signalling the address. The address delay is optional. If the
> >           address delay parameter is not provided, the MG uses the
> >           provisioned value by default.
> >         Type: integer
> >         Possible Values: 0 and up in milliseconds
> >
> > Question:
> > MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> > pulse.
> > How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> > Pulse?


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


From daemon@optimus.ietf.org  Wed Jan  9 12:00:40 2002
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 MAA07273
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 12:00:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA11057
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 12:00:43 -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 LAA09931;
	Wed, 9 Jan 2002 11:49:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09902
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 11:49:40 -0500 (EST)
Received: from mtiwmhc22.worldnet.att.net (mtiwmhc22.worldnet.att.net [204.127.131.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07121
	for <megaco@ietf.org>; Wed, 9 Jan 2002 11:49:36 -0500 (EST)
Received: from varneyhome.ieee.org ([12.84.123.134])
          by mtiwmhc22.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020109164908.XWDM941.mtiwmhc22.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Wed, 9 Jan 2002 16:49:08 +0000
Message-Id: <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Jan 2002 10:48:09 -0600
To: <megaco@ietf.org>
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] Megaco CAS
In-Reply-To: <006601c198de$ec738580$3401ff0a@axsppc02>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Chak,
    At first, I thought the Description of "provisioned" frequency, 
cadence, etc. could be clarified as a per-trunk attribute (not per MG, as 
some might read it).  That is, MF trunks always used MF signaling, etc.  On 
further reflection, this is insufficient to emulate some forms of older 
signaling used in the USA.  For example, some circuits signal using Dial 
Pulse in a first stage, followed by MF in the second.  Also, it might be 
useful to force DTMF signaling over an MF trunk which is already connected 
on a call (although that goes beyond the function typically associated with 
the acronym "CAS").

    So I'm agreeing with you, with a small suggestion below:

At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
>I think we can have another parameter as given below:
>
>         Parameter Name: Address Type
>         ParameterID: at (0x0003)
>         Description: Specifies Type of address digits.
>         Type: enumeration
>         Possible Values:
>         "DTMF"  (0x0000)  DTMF Digits
>         "MF"       (0x0001)  MF Digits
>         "DP"        (0x0002)  Dial Pulse Digits

    It might be less confusing if the word "Type" was not used in the Name 
or Description, since it is part of the meta-language of MEGACO 
packages.  I used "Coding" below, but another word might be better.  Also, 
you offered no default text in the Description -- did you really want 
"Address Type" to be included in every use of "addr"?

      Alternative Name/ID/Description for consideration:
  Parameter Name: Address Coding
  ParameterID: ac (0x0003)
  Description: Specifies the coding of Digit String parameter
           in tones or DC pulses.  Address Coding is optional;
           if not provided, the MG uses the value provisioned
           as an attribute of the circuit associated with the
           signal.

    Would it be useful to mention an error case if Address Coding is not 
present and the "circuit" has no 'ac' value provisioned?  (For example, 
could CAS package be used to signal over an ephemeral?)

    On second thought, having 'ac' optional might be a mistake.  It forces 
the MGC to "know" the coding for every circuit.  (The 
provisioned-per-MG-circuit option allows the MGC to be ignorant of the 
coding.)  I think it unlikely that the MGC could be ignorant of MF vs. DTMF 
vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is 
just asking for an error.

Al Varney - varney@ieee.org

> > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > Hi List,
> > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > 6.4.5
> >     Signal Name: Address
> >     SignalID: addr (0x0005)
> >     Description: Applies the address signals in the form of either
> >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> >           frequency, cadence, duration and amplitude values for the
> >           multi-frequency tones that convey the address information are
> >           provisioned in the MG.
> >     Signal Type: (BR) Brief
> >     Duration: Provisioned
> >     Additional Parameters:
> >         Parameter Name: Digit String
> >         ParameterID: ds (0x0001)
> >         Description: The digit string that needs to be sent as address
> >           signals.
> >         Type: string of digits.
> >         Possible Values: a sequence of the characters "0" through "9"
> >           as well as "A" through "H" ("A" through "H" used for MF
> >           signalling - refer to the symbols defined for the digit map
> >           in the MF Tone Detection package).
> >         Parameter Name: Address Delay
> >         ParameterID: ad (0x0002)
> >         Description: Specifies a timed delay that is applied prior to
> >           signalling the address. The address delay is optional. If the
> >           address delay parameter is not provided, the MG uses the
> >           provisioned value by default.
> >         Type: integer
> >         Possible Values: 0 and up in milliseconds
> >
> > Question:
> > MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> > pulse.
> > How MGC can tell gateway about the mode of the digits is MF or DTMF or Dial
> > Pulse?


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



From megaco-admin@ietf.org  Wed Jan  9 13:24:13 2002
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 NAA09021
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:24:13 -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 NAA14028;
	Wed, 9 Jan 2002 13:09:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13998
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:09:55 -0500 (EST)
Received: from sm13.texas.rr.com (sm13.texas.rr.com [24.93.35.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08601
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:09:53 -0500 (EST)
Received: from plong1 (bu24242141-164.austin.rr.com [24.242.141.164])
	by sm13.texas.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id g09ICPma025594
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:12:25 -0600
From: "Paul Long" <plong@ipdialog.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] new to megaco
Date: Wed, 9 Jan 2002 12:05:39 -0600
Message-ID: <NEBBIELHMLDIACLLJHCNEEPEDIAA.plong@ipdialog.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Content-Transfer-Encoding: 7bit
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: 7bit

sree,

Then I guess you know that Megaco and H.248 are the same thing so you should
feel right at home here. :-)

Paul Long
ipDialog, Inc.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
sree gk
Sent: Wednesday, January 09, 2002 6:54 AM
To: megaco@ietf.org
Subject: [Megaco] new to megaco



hi all

    I am new to megaco and now I am into an MG development. can any one send
me a kind of tutorial kind of material which covers the issues in the
development. I have experience of developing H248 protocol stack ( encoding
and decoding ).

regs
sree


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


From daemon@optimus.ietf.org  Wed Jan  9 13:24:14 2002
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 NAA09030
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:24:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14348
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 13:24:16 -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 NAA14028;
	Wed, 9 Jan 2002 13:09:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13998
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:09:55 -0500 (EST)
Received: from sm13.texas.rr.com (sm13.texas.rr.com [24.93.35.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08601
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:09:53 -0500 (EST)
Received: from plong1 (bu24242141-164.austin.rr.com [24.242.141.164])
	by sm13.texas.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id g09ICPma025594
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:12:25 -0600
From: "Paul Long" <plong@ipdialog.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] new to megaco
Date: Wed, 9 Jan 2002 12:05:39 -0600
Message-ID: <NEBBIELHMLDIACLLJHCNEEPEDIAA.plong@ipdialog.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Content-Transfer-Encoding: 7bit
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: 7bit

sree,

Then I guess you know that Megaco and H.248 are the same thing so you should
feel right at home here. :-)

Paul Long
ipDialog, Inc.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
sree gk
Sent: Wednesday, January 09, 2002 6:54 AM
To: megaco@ietf.org
Subject: [Megaco] new to megaco



hi all

    I am new to megaco and now I am into an MG development. can any one send
me a kind of tutorial kind of material which covers the issues in the
development. I have experience of developing H248 protocol stack ( encoding
and decoding ).

regs
sree


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



From megaco-admin@ietf.org  Wed Jan  9 13:28:08 2002
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 NAA09274
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:28:08 -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 NAA14109;
	Wed, 9 Jan 2002 13:13:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14086
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:13:56 -0500 (EST)
Received: from sm13.texas.rr.com (sm13.texas.rr.com [24.93.35.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08702
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:13:53 -0500 (EST)
Received: from plong1 (bu24242141-164.austin.rr.com [24.242.141.164])
	by sm13.texas.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id g09IGWma027689
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:16:32 -0600
From: "Paul Long" <plong@ipdialog.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] new to megaco
Date: Wed, 9 Jan 2002 12:09:46 -0600
Message-ID: <NEBBIELHMLDIACLLJHCNKEPEDIAA.plong@ipdialog.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Content-Transfer-Encoding: 7bit
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: 7bit

sree,

Well, I suppose I could be a little more helpful. Here is some info,
although it doesn't contain a tutorial:
http://packetizer.com/iptel/h248/
http://packetizer.com/h248link.html

Paul Long
ipDialog, Inc.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
sree gk
Sent: Wednesday, January 09, 2002 6:54 AM
To: megaco@ietf.org
Subject: [Megaco] new to megaco



hi all

    I am new to megaco and now I am into an MG development. can any one send
me a kind of tutorial kind of material which covers the issues in the
development. I have experience of developing H248 protocol stack ( encoding
and decoding ).

regs
sree


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


From daemon@optimus.ietf.org  Wed Jan  9 13:28:09 2002
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 NAA09287
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:28:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14487
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 13:28:11 -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 NAA14109;
	Wed, 9 Jan 2002 13:13:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14086
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:13:56 -0500 (EST)
Received: from sm13.texas.rr.com (sm13.texas.rr.com [24.93.35.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08702
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:13:53 -0500 (EST)
Received: from plong1 (bu24242141-164.austin.rr.com [24.242.141.164])
	by sm13.texas.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id g09IGWma027689
	for <megaco@ietf.org>; Wed, 9 Jan 2002 12:16:32 -0600
From: "Paul Long" <plong@ipdialog.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] new to megaco
Date: Wed, 9 Jan 2002 12:09:46 -0600
Message-ID: <NEBBIELHMLDIACLLJHCNKEPEDIAA.plong@ipdialog.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <20020109125341.2745.qmail@mailweb31.rediffmail.com>
Content-Transfer-Encoding: 7bit
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: 7bit

sree,

Well, I suppose I could be a little more helpful. Here is some info,
although it doesn't contain a tutorial:
http://packetizer.com/iptel/h248/
http://packetizer.com/h248link.html

Paul Long
ipDialog, Inc.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
sree gk
Sent: Wednesday, January 09, 2002 6:54 AM
To: megaco@ietf.org
Subject: [Megaco] new to megaco



hi all

    I am new to megaco and now I am into an MG development. can any one send
me a kind of tutorial kind of material which covers the issues in the
development. I have experience of developing H248 protocol stack ( encoding
and decoding ).

regs
sree


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



From megaco-admin@ietf.org  Wed Jan  9 13:36:38 2002
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 NAA09864
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:36:38 -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 NAA14311;
	Wed, 9 Jan 2002 13:21:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14282
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:21:06 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08881
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:21:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09IKY627011;
	Wed, 9 Jan 2002 13:20:34 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09IKVl08799;
	Wed, 9 Jan 2002 13:20:32 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGG54X>; Wed, 9 Jan 2002 13:18:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE02@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <jeaimetu@lge.com>, megaco@ietf.org
Subject: RE: [Megaco] Question about alarm.
Date: Wed, 9 Jan 2002 13:19:27 -0500 
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

I'm not clear on the architecture involved, but assuming the MSC server is
the equivalent of the MGC, faults can be reported through the ServiceChange
mechanism.

-----Original Message-----
From: jeaimetu@lge.com [mailto:jeaimetu@lge.com]
Sent: Wednesday, January 09, 2002 1:42 AM
To: megaco@ietf.org
Subject: [Megaco] Question about alarm.


Hello.
 
I have a question fault management on R4 switching system.
 
If hardware or software fault is occured on Media Gateway, then MG
report that fault to MSC server?
 
If so, is there any method to report by MEGACO?
 
Have a nice day.

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


From daemon@optimus.ietf.org  Wed Jan  9 13:36:38 2002
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 NAA09873
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:36:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA15124
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 13:36:40 -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 NAA14311;
	Wed, 9 Jan 2002 13:21:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14282
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:21:06 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08881
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:21:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09IKY627011;
	Wed, 9 Jan 2002 13:20:34 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09IKVl08799;
	Wed, 9 Jan 2002 13:20:32 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGG54X>; Wed, 9 Jan 2002 13:18:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE02@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <jeaimetu@lge.com>, megaco@ietf.org
Subject: RE: [Megaco] Question about alarm.
Date: Wed, 9 Jan 2002 13:19:27 -0500 
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

I'm not clear on the architecture involved, but assuming the MSC server is
the equivalent of the MGC, faults can be reported through the ServiceChange
mechanism.

-----Original Message-----
From: jeaimetu@lge.com [mailto:jeaimetu@lge.com]
Sent: Wednesday, January 09, 2002 1:42 AM
To: megaco@ietf.org
Subject: [Megaco] Question about alarm.


Hello.
 
I have a question fault management on R4 switching system.
 
If hardware or software fault is occured on Media Gateway, then MG
report that fault to MSC server?
 
If so, is there any method to report by MEGACO?
 
Have a nice day.

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



From megaco-admin@ietf.org  Wed Jan  9 13:42:01 2002
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 NAA10322
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:42:00 -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 NAA14594;
	Wed, 9 Jan 2002 13:30:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14556
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:29:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09392
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:29:56 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09ITR628643;
	Wed, 9 Jan 2002 13:29:27 -0500 (EST)
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 g09ITPG13882;
	Wed, 9 Jan 2002 13:29:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGG59A>; Wed, 9 Jan 2002 13:27:52 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE03@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] UnSpecified Local or Remote Descriptor
Date: Wed, 9 Jan 2002 13:28:20 -0500 
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

The basic intent is that if no Local and/or Remote descriptor is specified
in a command, there is no change to the properties concerned on the specific
termination, from whatever values they had before that command was
processed.  So the answers to your questions are:
 -- we're talking specific terminations
 -- we're talking whatever values were last set on those terminations,
whether specifically by the MGC or by MG choice within a range set by the
MGC.



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, January 09, 2002 6:51 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] UnSpecified Local or Remote Descriptor


Hi,

It was given in RFC 3015 as "An unspecified Local or Remote descriptor
requires the MG to use
whatever was last specified for that descriptor".

I want to know whether the above statement is valid for a specified Ephermal
Termination or
for a specified Context or for a whole MG.

One more thing, in the above statement, what "last specified" indicates.
Suppose MGC
sends Under Specified SDP parameters (using CHOOSE) in Local descriptor and
MG replies with Specified values, then "last specified" indicates the "Under
Specified
SDP parameters sent by the MGC"or "Specified SDP parameters sent by the MG"

Thanks,
Sudhir



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan  9 13:42:01 2002
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 NAA10334
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jan 2002 13:42:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA15336
	for megaco-archive@odin.ietf.org; Wed, 9 Jan 2002 13:42:03 -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 NAA14594;
	Wed, 9 Jan 2002 13:30:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14556
	for <megaco@optimus.ietf.org>; Wed, 9 Jan 2002 13:29:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09392
	for <megaco@ietf.org>; Wed, 9 Jan 2002 13:29:56 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g09ITR628643;
	Wed, 9 Jan 2002 13:29:27 -0500 (EST)
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 g09ITPG13882;
	Wed, 9 Jan 2002 13:29:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGG59A>; Wed, 9 Jan 2002 13:27:52 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE03@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] UnSpecified Local or Remote Descriptor
Date: Wed, 9 Jan 2002 13:28:20 -0500 
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

The basic intent is that if no Local and/or Remote descriptor is specified
in a command, there is no change to the properties concerned on the specific
termination, from whatever values they had before that command was
processed.  So the answers to your questions are:
 -- we're talking specific terminations
 -- we're talking whatever values were last set on those terminations,
whether specifically by the MGC or by MG choice within a range set by the
MGC.



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, January 09, 2002 6:51 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] UnSpecified Local or Remote Descriptor


Hi,

It was given in RFC 3015 as "An unspecified Local or Remote descriptor
requires the MG to use
whatever was last specified for that descriptor".

I want to know whether the above statement is valid for a specified Ephermal
Termination or
for a specified Context or for a whole MG.

One more thing, in the above statement, what "last specified" indicates.
Suppose MGC
sends Under Specified SDP parameters (using CHOOSE) in Local descriptor and
MG replies with Specified values, then "last specified" indicates the "Under
Specified
SDP parameters sent by the MGC"or "Specified SDP parameters sent by the MG"

Thanks,
Sudhir



_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 10 00:33:01 2002
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 AAA01252
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 00:33:01 -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 AAA03626;
	Thu, 10 Jan 2002 00:21:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03597
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 00:20:57 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00692
	for <megaco@ietf.org>; Thu, 10 Jan 2002 00:20:56 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA07105;
	Thu, 10 Jan 2002 16:19:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA11507;
	Thu, 10 Jan 2002 16:20:51 +1100 (EST)
Message-ID: <3C3CDA5E.2953AACD@ericsson.com.au>
Date: Thu, 10 Jan 2002 11:03:42 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <65256B3C.002FF26A.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> Hi Christian
> 
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that the
> entity sending rerponse will retransmit the response till it gets the ACK of it.
> And this solutions seems fine, otherwise the presence of immAckRequired field in
> the message will not make any difference.
> 
> This is all that I wanted to be updated in V2.
> 
> Regards
> Vivek
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
> 
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> 
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> 
> G'Day Vivek,
> 
> What exactly do you propose to update in v2?
> 
> Regards, Christian
> 
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



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


From daemon@optimus.ietf.org  Thu Jan 10 00:33:02 2002
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 AAA01261
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 00:33:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA04124
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 00:33:01 -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 AAA03626;
	Thu, 10 Jan 2002 00:21:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03597
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 00:20:57 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00692
	for <megaco@ietf.org>; Thu, 10 Jan 2002 00:20:56 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA07105;
	Thu, 10 Jan 2002 16:19:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA11507;
	Thu, 10 Jan 2002 16:20:51 +1100 (EST)
Message-ID: <3C3CDA5E.2953AACD@ericsson.com.au>
Date: Thu, 10 Jan 2002 11:03:42 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <65256B3C.002FF26A.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> Hi Christian
> 
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that the
> entity sending rerponse will retransmit the response till it gets the ACK of it.
> And this solutions seems fine, otherwise the presence of immAckRequired field in
> the message will not make any difference.
> 
> This is all that I wanted to be updated in V2.
> 
> Regards
> Vivek
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
> 
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> 
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> 
> G'Day Vivek,
> 
> What exactly do you propose to update in v2?
> 
> Regards, Christian
> 
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



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



From megaco-admin@ietf.org  Thu Jan 10 01:03:36 2002
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 BAA01834
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 01:03:35 -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 AAA04305;
	Thu, 10 Jan 2002 00:51:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04278
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 00:51:11 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01597
	for <megaco@ietf.org>; Thu, 10 Jan 2002 00:51:09 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001664571@fsnt.future.futsoft.com>;
 Thu, 10 Jan 2002 11:35:04 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0A5o6R29318;
	Thu, 10 Jan 2002 11:20:06 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 10 Jan 2002 11:27:56 +0530
Message-Id: <000601c1999b$c0ba4ce0$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 10 01:03:36 2002
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 BAA01844
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 01:03:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA04824
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 01:03:36 -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 AAA04305;
	Thu, 10 Jan 2002 00:51:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04278
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 00:51:11 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01597
	for <megaco@ietf.org>; Thu, 10 Jan 2002 00:51:09 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001664571@fsnt.future.futsoft.com>;
 Thu, 10 Jan 2002 11:35:04 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0A5o6R29318;
	Thu, 10 Jan 2002 11:20:06 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 10 Jan 2002 11:27:56 +0530
Message-Id: <000601c1999b$c0ba4ce0$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA000102ADDB@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 10 03:35:52 2002
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 DAA11671
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 03:35:52 -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 DAA16528;
	Thu, 10 Jan 2002 03:12:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA16499
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 03:12:51 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11483
	for <megaco@ietf.org>; Thu, 10 Jan 2002 03:12:49 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id CAA24014;
	Thu, 10 Jan 2002 02:12:18 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g0A8CCs19845;
	Thu, 10 Jan 2002 02:12:12 -0600 (CST)
Message-ID: <002a01c199af$433dba90$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: <megaco@ietf.org>, "Al Varney" <varney@ieee.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
Subject: Re: [Megaco] Megaco CAS
Date: Thu, 10 Jan 2002 13:47:25 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Al Varney,

I think optional is OK.  Default coding type for a termination should be
provisioned in MG.  If MGC want to override, it can use optional parameter "ac".

Thanks
Chak
----- Original Message -----
From: "Al Varney" <varney@ieee.org>
To: <megaco@ietf.org>
Sent: Wednesday, January 09, 2002 10:18 PM
Subject: Re: [Megaco] Megaco CAS


> Chak,
>     At first, I thought the Description of "provisioned" frequency,
> cadence, etc. could be clarified as a per-trunk attribute (not per MG, as
> some might read it).  That is, MF trunks always used MF signaling, etc.  On
> further reflection, this is insufficient to emulate some forms of older
> signaling used in the USA.  For example, some circuits signal using Dial
> Pulse in a first stage, followed by MF in the second.  Also, it might be
> useful to force DTMF signaling over an MF trunk which is already connected
> on a call (although that goes beyond the function typically associated with
> the acronym "CAS").
>
>     So I'm agreeing with you, with a small suggestion below:
>
> At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
> >I think we can have another parameter as given below:
> >
> >         Parameter Name: Address Type
> >         ParameterID: at (0x0003)
> >         Description: Specifies Type of address digits.
> >         Type: enumeration
> >         Possible Values:
> >         "DTMF"  (0x0000)  DTMF Digits
> >         "MF"       (0x0001)  MF Digits
> >         "DP"        (0x0002)  Dial Pulse Digits
>
>     It might be less confusing if the word "Type" was not used in the Name
> or Description, since it is part of the meta-language of MEGACO
> packages.  I used "Coding" below, but another word might be better.  Also,
> you offered no default text in the Description -- did you really want
> "Address Type" to be included in every use of "addr"?
>
>       Alternative Name/ID/Description for consideration:
>   Parameter Name: Address Coding
>   ParameterID: ac (0x0003)
>   Description: Specifies the coding of Digit String parameter
>            in tones or DC pulses.  Address Coding is optional;
>            if not provided, the MG uses the value provisioned
>            as an attribute of the circuit associated with the
>            signal.
>
>     Would it be useful to mention an error case if Address Coding is not
> present and the "circuit" has no 'ac' value provisioned?  (For example,
> could CAS package be used to signal over an ephemeral?)
>
>     On second thought, having 'ac' optional might be a mistake.  It forces
> the MGC to "know" the coding for every circuit.  (The
> provisioned-per-MG-circuit option allows the MGC to be ignorant of the
> coding.)  I think it unlikely that the MGC could be ignorant of MF vs. DTMF
> vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is
> just asking for an error.
>
> Al Varney - varney@ieee.org
>
> > > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > > Hi List,
> > > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > > 6.4.5
> > >     Signal Name: Address
> > >     SignalID: addr (0x0005)
> > >     Description: Applies the address signals in the form of either
> > >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> > >           frequency, cadence, duration and amplitude values for the
> > >           multi-frequency tones that convey the address information are
> > >           provisioned in the MG.
> > >     Signal Type: (BR) Brief
> > >     Duration: Provisioned
> > >     Additional Parameters:
> > >         Parameter Name: Digit String
> > >         ParameterID: ds (0x0001)
> > >         Description: The digit string that needs to be sent as address
> > >           signals.
> > >         Type: string of digits.
> > >         Possible Values: a sequence of the characters "0" through "9"
> > >           as well as "A" through "H" ("A" through "H" used for MF
> > >           signalling - refer to the symbols defined for the digit map
> > >           in the MF Tone Detection package).
> > >         Parameter Name: Address Delay
> > >         ParameterID: ad (0x0002)
> > >         Description: Specifies a timed delay that is applied prior to
> > >           signalling the address. The address delay is optional. If the
> > >           address delay parameter is not provided, the MG uses the
> > >           provisioned value by default.
> > >         Type: integer
> > >         Possible Values: 0 and up in milliseconds
> > >
> > > Question:
> > > MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> > > pulse.
> > > How MGC can tell gateway about the mode of the digits is MF or DTMF or
Dial
> > > Pulse?
>
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan 10 03:35:53 2002
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 DAA11680
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 03:35:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA17449
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 03:35:54 -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 DAA16528;
	Thu, 10 Jan 2002 03:12:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA16499
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 03:12:51 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11483
	for <megaco@ietf.org>; Thu, 10 Jan 2002 03:12:49 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id CAA24014;
	Thu, 10 Jan 2002 02:12:18 -0600 (CST)
Received: from axsppc02 (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g0A8CCs19845;
	Thu, 10 Jan 2002 02:12:12 -0600 (CST)
Message-ID: <002a01c199af$433dba90$3401ff0a@axsppc02>
From: "PSK Chakravarthi" <pchakrav@ssd.usa.alcatel.com>
To: <megaco@ietf.org>, "Al Varney" <varney@ieee.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
Subject: Re: [Megaco] Megaco CAS
Date: Thu, 10 Jan 2002 13:47:25 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
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: 7bit

Al Varney,

I think optional is OK.  Default coding type for a termination should be
provisioned in MG.  If MGC want to override, it can use optional parameter "ac".

Thanks
Chak
----- Original Message -----
From: "Al Varney" <varney@ieee.org>
To: <megaco@ietf.org>
Sent: Wednesday, January 09, 2002 10:18 PM
Subject: Re: [Megaco] Megaco CAS


> Chak,
>     At first, I thought the Description of "provisioned" frequency,
> cadence, etc. could be clarified as a per-trunk attribute (not per MG, as
> some might read it).  That is, MF trunks always used MF signaling, etc.  On
> further reflection, this is insufficient to emulate some forms of older
> signaling used in the USA.  For example, some circuits signal using Dial
> Pulse in a first stage, followed by MF in the second.  Also, it might be
> useful to force DTMF signaling over an MF trunk which is already connected
> on a call (although that goes beyond the function typically associated with
> the acronym "CAS").
>
>     So I'm agreeing with you, with a small suggestion below:
>
> At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
> >I think we can have another parameter as given below:
> >
> >         Parameter Name: Address Type
> >         ParameterID: at (0x0003)
> >         Description: Specifies Type of address digits.
> >         Type: enumeration
> >         Possible Values:
> >         "DTMF"  (0x0000)  DTMF Digits
> >         "MF"       (0x0001)  MF Digits
> >         "DP"        (0x0002)  Dial Pulse Digits
>
>     It might be less confusing if the word "Type" was not used in the Name
> or Description, since it is part of the meta-language of MEGACO
> packages.  I used "Coding" below, but another word might be better.  Also,
> you offered no default text in the Description -- did you really want
> "Address Type" to be included in every use of "addr"?
>
>       Alternative Name/ID/Description for consideration:
>   Parameter Name: Address Coding
>   ParameterID: ac (0x0003)
>   Description: Specifies the coding of Digit String parameter
>            in tones or DC pulses.  Address Coding is optional;
>            if not provided, the MG uses the value provisioned
>            as an attribute of the circuit associated with the
>            signal.
>
>     Would it be useful to mention an error case if Address Coding is not
> present and the "circuit" has no 'ac' value provisioned?  (For example,
> could CAS package be used to signal over an ephemeral?)
>
>     On second thought, having 'ac' optional might be a mistake.  It forces
> the MGC to "know" the coding for every circuit.  (The
> provisioned-per-MG-circuit option allows the MGC to be ignorant of the
> coding.)  I think it unlikely that the MGC could be ignorant of MF vs. DTMF
> vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is
> just asking for an error.
>
> Al Varney - varney@ieee.org
>
> > > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > > Hi List,
> > > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > > 6.4.5
> > >     Signal Name: Address
> > >     SignalID: addr (0x0005)
> > >     Description: Applies the address signals in the form of either
> > >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> > >           frequency, cadence, duration and amplitude values for the
> > >           multi-frequency tones that convey the address information are
> > >           provisioned in the MG.
> > >     Signal Type: (BR) Brief
> > >     Duration: Provisioned
> > >     Additional Parameters:
> > >         Parameter Name: Digit String
> > >         ParameterID: ds (0x0001)
> > >         Description: The digit string that needs to be sent as address
> > >           signals.
> > >         Type: string of digits.
> > >         Possible Values: a sequence of the characters "0" through "9"
> > >           as well as "A" through "H" ("A" through "H" used for MF
> > >           signalling - refer to the symbols defined for the digit map
> > >           in the MF Tone Detection package).
> > >         Parameter Name: Address Delay
> > >         ParameterID: ad (0x0002)
> > >         Description: Specifies a timed delay that is applied prior to
> > >           signalling the address. The address delay is optional. If the
> > >           address delay parameter is not provided, the MG uses the
> > >           provisioned value by default.
> > >         Type: integer
> > >         Possible Values: 0 and up in milliseconds
> > >
> > > Question:
> > > MGC can instruct gateway to out pulse digits either in DTMF or MF or dial
> > > pulse.
> > > How MGC can tell gateway about the mode of the digits is MF or DTMF or
Dial
> > > Pulse?
>
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan 10 04:56:18 2002
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 EAA12388
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 04:56:18 -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 EAA19379;
	Thu, 10 Jan 2002 04:46:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19350
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 04:46:05 -0500 (EST)
Received: from banyannetworks.com ([203.199.199.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12223
	for <megaco@ietf.org>; Thu, 10 Jan 2002 04:46:01 -0500 (EST)
Received: from anand (ctmedia [192.168.9.200])
	by banyannetworks.com (8.12.1/8.12.1) with SMTP id g0A9mKmG003259
	for <megaco@ietf.org>; Thu, 10 Jan 2002 15:18:20 +0530
Message-ID: <006e01c199ba$f677d5e0$c809a8c0@banyannetworks.com>
From: "Anand N.S." <anand@banyannetworks.com>
To: <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net> <002a01c199af$433dba90$3401ff0a@axsppc02>
Date: Thu, 10 Jan 2002 15:11:21 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGCP-RFC 2075
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: 7bit

Hi All ,
     How to implement
           a) Embedded Request
           b) Piggy Backing
           c) Softswitch failure
  in MGCP. RFC 2075

  Any one who has implemented these can share their ideas.
  Thanks.



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


From daemon@optimus.ietf.org  Thu Jan 10 04:56:18 2002
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 EAA12397
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 04:56:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA19594
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 04:56:20 -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 EAA19379;
	Thu, 10 Jan 2002 04:46:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19350
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 04:46:05 -0500 (EST)
Received: from banyannetworks.com ([203.199.199.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12223
	for <megaco@ietf.org>; Thu, 10 Jan 2002 04:46:01 -0500 (EST)
Received: from anand (ctmedia [192.168.9.200])
	by banyannetworks.com (8.12.1/8.12.1) with SMTP id g0A9mKmG003259
	for <megaco@ietf.org>; Thu, 10 Jan 2002 15:18:20 +0530
Message-ID: <006e01c199ba$f677d5e0$c809a8c0@banyannetworks.com>
From: "Anand N.S." <anand@banyannetworks.com>
To: <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net> <002a01c199af$433dba90$3401ff0a@axsppc02>
Date: Thu, 10 Jan 2002 15:11:21 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGCP-RFC 2075
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: 7bit

Hi All ,
     How to implement
           a) Embedded Request
           b) Piggy Backing
           c) Softswitch failure
  in MGCP. RFC 2075

  Any one who has implemented these can share their ideas.
  Thanks.



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



From megaco-admin@ietf.org  Thu Jan 10 07:25:29 2002
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 HAA13570
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 07:25:29 -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 HAA23820;
	Thu, 10 Jan 2002 07:05: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 HAA23793
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 07:05:04 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13343
	for <megaco@ietf.org>; Thu, 10 Jan 2002 07:05:01 -0500 (EST)
Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0AC51K10732
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:01 +0100 (MET)
Received: from boddington.du.uab.ericsson.se (hakan@boddington [134.138.176.81])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id g0AC50X21331
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:00 +0100 (MET)
Received: from localhost (hakan@localhost)
	by boddington.du.uab.ericsson.se (8.9.3+Sun/8.9.1/client-1.0) with ESMTP id NAA01826
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:00 +0100 (MET)
X-Authentication-Warning: boddington.du.uab.ericsson.se: hakan owned process doing -bs
Date: Thu, 10 Jan 2002 13:05:00 +0100 (MET)
From: Hakan Mattsson <hakan@erix.ericsson.se>
To: Megaconians <megaco@ietf.org>
Message-ID: <Pine.GSO.4.10.10201100946570.596-100000@boddington>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Subject: [Megaco] Announcement: Megaco goes Open Source
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


The Megaco/H.248 protocol stack implemented by Ericsson Computer
Science Laboratory, is now available as an Open Source product.

The source code and the complete documentation of Erlang/OTP
including the Megaco protocol stack, can be found at:

    http://www.erlang.org

License info is found at the end of the top page. It is also possible
to buy commercial licences in order to obtain full support.

Megaco related info, such as comparisons between the different
encodings, can be found at:

    http://www.erlang.org/project/megaco

In order to better understand what Erlang is about, you could read
Ulf Wiger's paper "Four-fold Increase in Productivity and Quality".
It was presented at the "Workshop on Formal Design of Safety
Critical Embedded Systems" in Munich, March 21-23, 2001. This paper
describes how the large ATM switch AXD 301 was developed and how
they used Erlang/OTP:

    http://www.erlang.se/publications/Ulf_Wiger.pdf

/Håkan

---
Håkan Mattsson
Ericsson
Computer Science Laboratory
http://www.ericsson.com/cslab/~hakan/





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


From daemon@optimus.ietf.org  Thu Jan 10 07:25:30 2002
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 HAA13579
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 07:25:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA24288
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 07:25:31 -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 HAA23820;
	Thu, 10 Jan 2002 07:05: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 HAA23793
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 07:05:04 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13343
	for <megaco@ietf.org>; Thu, 10 Jan 2002 07:05:01 -0500 (EST)
Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0AC51K10732
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:01 +0100 (MET)
Received: from boddington.du.uab.ericsson.se (hakan@boddington [134.138.176.81])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id g0AC50X21331
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:00 +0100 (MET)
Received: from localhost (hakan@localhost)
	by boddington.du.uab.ericsson.se (8.9.3+Sun/8.9.1/client-1.0) with ESMTP id NAA01826
	for <megaco@ietf.org>; Thu, 10 Jan 2002 13:05:00 +0100 (MET)
X-Authentication-Warning: boddington.du.uab.ericsson.se: hakan owned process doing -bs
Date: Thu, 10 Jan 2002 13:05:00 +0100 (MET)
From: Hakan Mattsson <hakan@erix.ericsson.se>
To: Megaconians <megaco@ietf.org>
Message-ID: <Pine.GSO.4.10.10201100946570.596-100000@boddington>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT
Subject: [Megaco] Announcement: Megaco goes Open Source
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


The Megaco/H.248 protocol stack implemented by Ericsson Computer
Science Laboratory, is now available as an Open Source product.

The source code and the complete documentation of Erlang/OTP
including the Megaco protocol stack, can be found at:

    http://www.erlang.org

License info is found at the end of the top page. It is also possible
to buy commercial licences in order to obtain full support.

Megaco related info, such as comparisons between the different
encodings, can be found at:

    http://www.erlang.org/project/megaco

In order to better understand what Erlang is about, you could read
Ulf Wiger's paper "Four-fold Increase in Productivity and Quality".
It was presented at the "Workshop on Formal Design of Safety
Critical Embedded Systems" in Munich, March 21-23, 2001. This paper
describes how the large ATM switch AXD 301 was developed and how
they used Erlang/OTP:

    http://www.erlang.se/publications/Ulf_Wiger.pdf

/Håkan

---
Håkan Mattsson
Ericsson
Computer Science Laboratory
http://www.ericsson.com/cslab/~hakan/





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



From megaco-admin@ietf.org  Thu Jan 10 10:08:37 2002
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 KAA15902
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:08:37 -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 JAA29327;
	Thu, 10 Jan 2002 09:54:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29298
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 09:54:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15746
	for <megaco@ietf.org>; Thu, 10 Jan 2002 09:54:32 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AEs2405146;
	Thu, 10 Jan 2002 09:54:02 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AErxO21510;
	Thu, 10 Jan 2002 09:54:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGHNRM>; Thu, 10 Jan 2002 09:52:28 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE12@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 10 Jan 2002 09:53:59 -0500
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

There is a potential application where the MuxedTerm represents a
higher-order facility (e.g. T1 or E1) and the multiplexing relationship
describes the channels that make it up.  The MuxedTerm would be defined only
for maintenance purposes, to monitor the status of the facility as a whole.
We haven't actually specified MUX types which would cover this.

The current specification views the MuxedTerm as an ephemeral typically
supporting multiple media streams.  Each stream gets its own SDP in Local
and Remote.  The MuxedTerm as a whole represents, for example, a complete
H.320 session.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 10, 2002 12:58 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 10 10:08:38 2002
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 KAA15912
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:08:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA29978
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 10:08:39 -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 JAA29327;
	Thu, 10 Jan 2002 09:54:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29298
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 09:54:34 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15746
	for <megaco@ietf.org>; Thu, 10 Jan 2002 09:54:32 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AEs2405146;
	Thu, 10 Jan 2002 09:54:02 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AErxO21510;
	Thu, 10 Jan 2002 09:54:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGHNRM>; Thu, 10 Jan 2002 09:52:28 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE12@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'gokulc@future.futsoft.com'" <gokulc@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 10 Jan 2002 09:53:59 -0500
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

There is a potential application where the MuxedTerm represents a
higher-order facility (e.g. T1 or E1) and the multiplexing relationship
describes the channels that make it up.  The MuxedTerm would be defined only
for maintenance purposes, to monitor the status of the facility as a whole.
We haven't actually specified MUX types which would cover this.

The current specification views the MuxedTerm as an ephemeral typically
supporting multiple media streams.  Each stream gets its own SDP in Local
and Remote.  The MuxedTerm as a whole represents, for example, a complete
H.320 session.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 10, 2002 12:58 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 10 10:52:20 2002
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 KAA16890
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:52:20 -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 KAA01105;
	Thu, 10 Jan 2002 10:40:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01075
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:40:17 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16556
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:40:15 -0500 (EST)
Received: from openetsrv.ho.lucent.com (h135-17-127-229.lucent.com [135.17.127.229])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0AFdiZ29650;
	Thu, 10 Jan 2002 10:39:44 -0500 (EST)
Received: from openetpc011 by openetsrv.ho.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA08969; Thu, 10 Jan 2002 10:39:42 -0500 (EST)
Reply-To: <mmraju@lucent.com>
From: "Raju" <mmraju@lucent.com>
To: "Christian Groves" <Christian.Groves@ericsson.com.au>,
        <Sunesh.Kumra@nokia.com>
Cc: <Brian.Rosen@marconi.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Megaco Interoperability
Date: Thu, 10 Jan 2002 10:39:25 -0500
Message-ID: <OAEGLOLAHPHJDAOCBECNKEOFCOAA.mmraju@lucent.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <3C3B89F4.52671994@ericsson.com.au>
Content-Transfer-Encoding: 7bit
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: 7bit


We have a stack which supports both binary and text.
Our MGC supports both. Some of out MGs support text whereas others support
binary
but not both.


> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Christian Groves
> Sent: Tuesday, January 08, 2002 7:08 PM
> To: Sunesh.Kumra@nokia.com
> Cc: Brian.Rosen@marconi.com; megaco@ietf.org
> Subject: Re: [Megaco] Megaco Interoperability
>
>
> We also have MGs that are binary only. We have others that are text,
> others that are text/binary.
>
> Christian
>
> Sunesh.Kumra@nokia.com wrote:
> >
> > we have a business unit who has a Megaco stack (MG side) with only
> > binary implementation. We are developing a stack for MGC, which
> > currently supports only text, but would have to include binary support
> > if the MGs we have to control only understand binary. I would try to
> > convince our team developing MG to support Text if not moving totally to
> > text.
> >
> > -sunesh
> >
> > -----Original Message-----
> > From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Sent: 07. January 2002 16:37
> > To: Seshagiri Rao; megaco@ietf.org
> > Subject: RE: [Megaco] Megaco Interoperability
> >
> > There is not a reference design available.
> > There are test scenarios developed for the bakeoffs.  These explicitly
> > DO NOT
> > include message sequences.
> > I have been stalling on scheduling another bakeoff until we had better
> > participation.
> >   I plan to "call the question" again soon
> > Virtually all implementations are text only.  A few are both (a very
> > few).  I don't
> > know of any that are binary only.
> >
> > Brian
> >
> > -----Original Message-----
> > From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> > Sent: Saturday, January 05, 2002 6:58 PM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Megaco Interoperability
> >
> > All:
> >
> > I would like to know if there is any reference design/test sequence for
> > Megaco stack implementation.
> > I would also like to know if there is any forthcoming interop/bake-off
> > event.
> > How many of the current Megaco stack implementations support ABNF/Text
> > encoding and how many support ASN.1/binary encoding?
> >
> > Sesh
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Thu Jan 10 10:52:20 2002
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 KAA16899
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:52:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01482
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 10:52:22 -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 KAA01105;
	Thu, 10 Jan 2002 10:40:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01075
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:40:17 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16556
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:40:15 -0500 (EST)
Received: from openetsrv.ho.lucent.com (h135-17-127-229.lucent.com [135.17.127.229])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0AFdiZ29650;
	Thu, 10 Jan 2002 10:39:44 -0500 (EST)
Received: from openetpc011 by openetsrv.ho.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA08969; Thu, 10 Jan 2002 10:39:42 -0500 (EST)
Reply-To: <mmraju@lucent.com>
From: "Raju" <mmraju@lucent.com>
To: "Christian Groves" <Christian.Groves@ericsson.com.au>,
        <Sunesh.Kumra@nokia.com>
Cc: <Brian.Rosen@marconi.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Megaco Interoperability
Date: Thu, 10 Jan 2002 10:39:25 -0500
Message-ID: <OAEGLOLAHPHJDAOCBECNKEOFCOAA.mmraju@lucent.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-reply-to: <3C3B89F4.52671994@ericsson.com.au>
Content-Transfer-Encoding: 7bit
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: 7bit


We have a stack which supports both binary and text.
Our MGC supports both. Some of out MGs support text whereas others support
binary
but not both.


> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Christian Groves
> Sent: Tuesday, January 08, 2002 7:08 PM
> To: Sunesh.Kumra@nokia.com
> Cc: Brian.Rosen@marconi.com; megaco@ietf.org
> Subject: Re: [Megaco] Megaco Interoperability
>
>
> We also have MGs that are binary only. We have others that are text,
> others that are text/binary.
>
> Christian
>
> Sunesh.Kumra@nokia.com wrote:
> >
> > we have a business unit who has a Megaco stack (MG side) with only
> > binary implementation. We are developing a stack for MGC, which
> > currently supports only text, but would have to include binary support
> > if the MGs we have to control only understand binary. I would try to
> > convince our team developing MG to support Text if not moving totally to
> > text.
> >
> > -sunesh
> >
> > -----Original Message-----
> > From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Sent: 07. January 2002 16:37
> > To: Seshagiri Rao; megaco@ietf.org
> > Subject: RE: [Megaco] Megaco Interoperability
> >
> > There is not a reference design available.
> > There are test scenarios developed for the bakeoffs.  These explicitly
> > DO NOT
> > include message sequences.
> > I have been stalling on scheduling another bakeoff until we had better
> > participation.
> >   I plan to "call the question" again soon
> > Virtually all implementations are text only.  A few are both (a very
> > few).  I don't
> > know of any that are binary only.
> >
> > Brian
> >
> > -----Original Message-----
> > From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> > Sent: Saturday, January 05, 2002 6:58 PM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Megaco Interoperability
> >
> > All:
> >
> > I would like to know if there is any reference design/test sequence for
> > Megaco stack implementation.
> > I would also like to know if there is any forthcoming interop/bake-off
> > event.
> > How many of the current Megaco stack implementations support ABNF/Text
> > encoding and how many support ASN.1/binary encoding?
> >
> > Sesh
> >
> > _______________________________________________
> > 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



From daemon@optimus.ietf.org  Thu Jan 10 10:52:21 2002
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 KAA16923
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:52:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01496
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 10:52:23 -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 KAA00990;
	Thu, 10 Jan 2002 10:37:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00961
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:37:14 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16522
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:37:11 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0AFbBK23727
	for <megaco@ietf.org>; Thu, 10 Jan 2002 16:37:12 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Thu Jan 10 16:37:10 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKNYD2>; Thu, 10 Jan 2002 16:37:10 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB31@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: vibansal@hss.hns.com
Cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Thu, 10 Jan 2002 16:36:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an immediate confirmation shall be sent, and normal repetition timers shall be used thereafter.  An entity that sends a provisional response, SHALL include the immAckRequired field in the ensuing final response, indicating that an immediate confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final response will retransmit the final response including the immAckRequired field (with exponential backoff) until a confirmation is received.<EA> Receipt of a Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> Hi Christian
> 
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that the
> entity sending rerponse will retransmit the response till it gets the ACK of it.
> And this solutions seems fine, otherwise the presence of immAckRequired field in
> the message will not make any difference.
> 
> This is all that I wanted to be updated in V2.
> 
> Regards
> Vivek
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
> 
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> 
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> 
> G'Day Vivek,
> 
> What exactly do you propose to update in v2?
> 
> Regards, Christian
> 
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 10 10:59:42 2002
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 KAA17174
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:59:42 -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 KAA01442;
	Thu, 10 Jan 2002 10:49:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01353
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:49:46 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16821
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:49:39 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AFn9426303;
	Thu, 10 Jan 2002 10:49:09 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AFn6O25430;
	Thu, 10 Jan 2002 10:49:07 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGHPKZ>; Thu, 10 Jan 2002 10:47:35 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE15@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Hakan Mattsson'" <hakan@erix.ericsson.se>,
        Megaconians
	 <megaco@ietf.org>,
        "'brian.rosen@marconi.com'" <brian.rosen@marconi.com>
Subject: RE: [Megaco] Announcement: Megaco goes Open Source
Date: Thu, 10 Jan 2002 10:49:04 -0500
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

On the one hand, it is good to have this information.  On the other, it is
inappropriate to use the IETF Megaco list for such announcements.  It would
be nice to have some list where we could pass this sort of information
along.  As another example, I had a call a while back from someone with a
Megaco-related job to fill, and had no idea how to get the message out.

Would the Implementor's list set up by Marconi be the right place?

-----Original Message-----
From: Hakan Mattsson [mailto:hakan@erix.ericsson.se]
Sent: Thursday, January 10, 2002 7:05 AM
To: Megaconians
Subject: [Megaco] Announcement: Megaco goes Open Source



The Megaco/H.248 protocol stack implemented by Ericsson Computer
Science Laboratory, is now available as an Open Source product.

The source code and the complete documentation of Erlang/OTP
including the Megaco protocol stack, can be found at:

    http://www.erlang.org

License info is found at the end of the top page. It is also possible
to buy commercial licences in order to obtain full support.

Megaco related info, such as comparisons between the different
encodings, can be found at:

    http://www.erlang.org/project/megaco

In order to better understand what Erlang is about, you could read
Ulf Wiger's paper "Four-fold Increase in Productivity and Quality".
It was presented at the "Workshop on Formal Design of Safety
Critical Embedded Systems" in Munich, March 21-23, 2001. This paper
describes how the large ATM switch AXD 301 was developed and how
they used Erlang/OTP:

    http://www.erlang.se/publications/Ulf_Wiger.pdf

/Håkan

---
Håkan Mattsson
Ericsson
Computer Science Laboratory
http://www.ericsson.com/cslab/~hakan/





_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 10 10:59:42 2002
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 KAA17184
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:59:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01694
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 10:59:44 -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 KAA01442;
	Thu, 10 Jan 2002 10:49:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01353
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:49:46 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16821
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:49:39 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AFn9426303;
	Thu, 10 Jan 2002 10:49:09 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0AFn6O25430;
	Thu, 10 Jan 2002 10:49:07 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRGHPKZ>; Thu, 10 Jan 2002 10:47:35 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE15@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Hakan Mattsson'" <hakan@erix.ericsson.se>,
        Megaconians
	 <megaco@ietf.org>,
        "'brian.rosen@marconi.com'" <brian.rosen@marconi.com>
Subject: RE: [Megaco] Announcement: Megaco goes Open Source
Date: Thu, 10 Jan 2002 10:49:04 -0500
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

On the one hand, it is good to have this information.  On the other, it is
inappropriate to use the IETF Megaco list for such announcements.  It would
be nice to have some list where we could pass this sort of information
along.  As another example, I had a call a while back from someone with a
Megaco-related job to fill, and had no idea how to get the message out.

Would the Implementor's list set up by Marconi be the right place?

-----Original Message-----
From: Hakan Mattsson [mailto:hakan@erix.ericsson.se]
Sent: Thursday, January 10, 2002 7:05 AM
To: Megaconians
Subject: [Megaco] Announcement: Megaco goes Open Source



The Megaco/H.248 protocol stack implemented by Ericsson Computer
Science Laboratory, is now available as an Open Source product.

The source code and the complete documentation of Erlang/OTP
including the Megaco protocol stack, can be found at:

    http://www.erlang.org

License info is found at the end of the top page. It is also possible
to buy commercial licences in order to obtain full support.

Megaco related info, such as comparisons between the different
encodings, can be found at:

    http://www.erlang.org/project/megaco

In order to better understand what Erlang is about, you could read
Ulf Wiger's paper "Four-fold Increase in Productivity and Quality".
It was presented at the "Workshop on Formal Design of Safety
Critical Embedded Systems" in Munich, March 21-23, 2001. This paper
describes how the large ATM switch AXD 301 was developed and how
they used Erlang/OTP:

    http://www.erlang.se/publications/Ulf_Wiger.pdf

/Håkan

---
Håkan Mattsson
Ericsson
Computer Science Laboratory
http://www.ericsson.com/cslab/~hakan/





_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 10 11:43:58 2002
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 KAA16909
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 10:52:21 -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 KAA00990;
	Thu, 10 Jan 2002 10:37:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00961
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 10:37:14 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16522
	for <megaco@ietf.org>; Thu, 10 Jan 2002 10:37:11 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0AFbBK23727
	for <megaco@ietf.org>; Thu, 10 Jan 2002 16:37:12 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Thu Jan 10 16:37:10 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKNYD2>; Thu, 10 Jan 2002 16:37:10 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB31@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: vibansal@hss.hns.com
Cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Thu, 10 Jan 2002 16:36:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an immediate confirmation shall be sent, and normal repetition timers shall be used thereafter.  An entity that sends a provisional response, SHALL include the immAckRequired field in the ensuing final response, indicating that an immediate confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final response will retransmit the final response including the immAckRequired field (with exponential backoff) until a confirmation is received.<EA> Receipt of a Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
> 
> Hi Christian
> 
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that the
> entity sending rerponse will retransmit the response till it gets the ACK of it.
> And this solutions seems fine, otherwise the presence of immAckRequired field in
> the message will not make any difference.
> 
> This is all that I wanted to be updated in V2.
> 
> Regards
> Vivek
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
> 
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> 
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> 
> G'Day Vivek,
> 
> What exactly do you propose to update in v2?
> 
> Regards, Christian
> 
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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


From megaco-admin@ietf.org  Thu Jan 10 21:40:24 2002
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 VAA28976
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 21:40:24 -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 VAA23814;
	Thu, 10 Jan 2002 21:16:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA23786
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 21:16:05 -0500 (EST)
Received: from sparky.fibre.com (216-174-194-169.atgi.net [216.174.194.169])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27866
	for <megaco@ietf.org>; Thu, 10 Jan 2002 21:16:02 -0500 (EST)
Received: from zzzconn03.fibre.com (zzzconn03.afc.com [10.1.4.53]) by sparky.fibre.com with SMTP id SAA26545 for <megaco@ietf.org>; Thu, 10 Jan 2002 18:15:55 -0800
X-Authentication-Warning: sparky.fibre.com: Host zzzconn03.afc.com [10.1.4.53] claimed to be zzzconn03.fibre.com
Received: FROM xconn01.fibre.com BY zzzconn03.fibre.com ; Thu Jan 10 18:10:18 2002 -0800
Received: by xconn01.fibre.com with Internet Mail Service (5.5.2653.19)
	id <TGCG5Q62>; Thu, 10 Jan 2002 18:19:28 -0800
Message-ID: <2525B519863CD311907600A0C9AB1B8308D85FB3@zzzmail01.fibre.com>
From: John Stock <John.Stock@fibre.com>
To: megaco@ietf.org
Date: Thu, 10 Jan 2002 18:10:27 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Searchable mail archives?
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

Hi all,

Anyone know how to import the Megaco email archives into a program to make
them easily searchable (e.g. Outlook or something like that)?  I've see the
HTML version of the archives, but there's no search mechanism, and using an
editor to search on the raw files is a pain due to the lack of formatting
when reading.

Thanks!

John Stock
Systems Engineer
Advanced Fibre Communications
1465 N. McDowell Blvd.
Petaluma, CA 94954
Tel. 707-792-6249


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


From daemon@optimus.ietf.org  Thu Jan 10 21:40:25 2002
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 VAA28985
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jan 2002 21:40:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA24566
	for megaco-archive@odin.ietf.org; Thu, 10 Jan 2002 21:40:27 -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 VAA23814;
	Thu, 10 Jan 2002 21:16:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA23786
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 21:16:05 -0500 (EST)
Received: from sparky.fibre.com (216-174-194-169.atgi.net [216.174.194.169])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27866
	for <megaco@ietf.org>; Thu, 10 Jan 2002 21:16:02 -0500 (EST)
Received: from zzzconn03.fibre.com (zzzconn03.afc.com [10.1.4.53]) by sparky.fibre.com with SMTP id SAA26545 for <megaco@ietf.org>; Thu, 10 Jan 2002 18:15:55 -0800
X-Authentication-Warning: sparky.fibre.com: Host zzzconn03.afc.com [10.1.4.53] claimed to be zzzconn03.fibre.com
Received: FROM xconn01.fibre.com BY zzzconn03.fibre.com ; Thu Jan 10 18:10:18 2002 -0800
Received: by xconn01.fibre.com with Internet Mail Service (5.5.2653.19)
	id <TGCG5Q62>; Thu, 10 Jan 2002 18:19:28 -0800
Message-ID: <2525B519863CD311907600A0C9AB1B8308D85FB3@zzzmail01.fibre.com>
From: John Stock <John.Stock@fibre.com>
To: megaco@ietf.org
Date: Thu, 10 Jan 2002 18:10:27 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Searchable mail archives?
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

Hi all,

Anyone know how to import the Megaco email archives into a program to make
them easily searchable (e.g. Outlook or something like that)?  I've see the
HTML version of the archives, but there's no search mechanism, and using an
editor to search on the raw files is a pain due to the lack of formatting
when reading.

Thanks!

John Stock
Systems Engineer
Advanced Fibre Communications
1465 N. McDowell Blvd.
Petaluma, CA 94954
Tel. 707-792-6249


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



From megaco-admin@ietf.org  Fri Jan 11 00:14:53 2002
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 AAA01951
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 00:14:53 -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 XAA06656;
	Thu, 10 Jan 2002 23:57:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06623
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 23:57:14 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01762
	for <megaco@ietf.org>; Thu, 10 Jan 2002 23:57:11 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW38B2>; Fri, 11 Jan 2002 10:04:24 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822EC1A5@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability
Date: Fri, 11 Jan 2002 10:04:14 +0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
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


We too have Level3 compliant Megaco Residential and Trunking Gateway and MGC
Supporting Both Binary and Text version
along with complete Media gateway solution.
and will make available demos freely available with in two weeks.


Asrar Ashraf
Team Lead Megaco/H.248
AvazNetworks
Islamabad,Pakistan



-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Raju
Sent: Thursday, January 10, 2002 8:39 PM
To: Christian Groves; Sunesh.Kumra@nokia.com
Cc: Brian.Rosen@marconi.com; megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability



We have a stack which supports both binary and text.
Our MGC supports both. Some of out MGs support text whereas others support
binary
but not both.


> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Christian Groves
> Sent: Tuesday, January 08, 2002 7:08 PM
> To: Sunesh.Kumra@nokia.com
> Cc: Brian.Rosen@marconi.com; megaco@ietf.org
> Subject: Re: [Megaco] Megaco Interoperability
>
>
> We also have MGs that are binary only. We have others that are text,
> others that are text/binary.
>
> Christian
>
> Sunesh.Kumra@nokia.com wrote:
> >
> > we have a business unit who has a Megaco stack (MG side) with only
> > binary implementation. We are developing a stack for MGC, which
> > currently supports only text, but would have to include binary support
> > if the MGs we have to control only understand binary. I would try to
> > convince our team developing MG to support Text if not moving totally to
> > text.
> >
> > -sunesh
> >
> > -----Original Message-----
> > From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Sent: 07. January 2002 16:37
> > To: Seshagiri Rao; megaco@ietf.org
> > Subject: RE: [Megaco] Megaco Interoperability
> >
> > There is not a reference design available.
> > There are test scenarios developed for the bakeoffs.  These explicitly
> > DO NOT
> > include message sequences.
> > I have been stalling on scheduling another bakeoff until we had better
> > participation.
> >   I plan to "call the question" again soon
> > Virtually all implementations are text only.  A few are both (a very
> > few).  I don't
> > know of any that are binary only.
> >
> > Brian
> >
> > -----Original Message-----
> > From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> > Sent: Saturday, January 05, 2002 6:58 PM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Megaco Interoperability
> >
> > All:
> >
> > I would like to know if there is any reference design/test sequence for
> > Megaco stack implementation.
> > I would also like to know if there is any forthcoming interop/bake-off
> > event.
> > How many of the current Megaco stack implementations support ABNF/Text
> > encoding and how many support ASN.1/binary encoding?
> >
> > Sesh
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Fri Jan 11 00:14:54 2002
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 AAA01960
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 00:14:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA07453
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 00:14:54 -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 XAA06656;
	Thu, 10 Jan 2002 23:57:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06623
	for <megaco@optimus.ietf.org>; Thu, 10 Jan 2002 23:57:14 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01762
	for <megaco@ietf.org>; Thu, 10 Jan 2002 23:57:11 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW38B2>; Fri, 11 Jan 2002 10:04:24 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822EC1A5@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability
Date: Fri, 11 Jan 2002 10:04:14 +0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
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


We too have Level3 compliant Megaco Residential and Trunking Gateway and MGC
Supporting Both Binary and Text version
along with complete Media gateway solution.
and will make available demos freely available with in two weeks.


Asrar Ashraf
Team Lead Megaco/H.248
AvazNetworks
Islamabad,Pakistan



-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Raju
Sent: Thursday, January 10, 2002 8:39 PM
To: Christian Groves; Sunesh.Kumra@nokia.com
Cc: Brian.Rosen@marconi.com; megaco@ietf.org
Subject: RE: [Megaco] Megaco Interoperability



We have a stack which supports both binary and text.
Our MGC supports both. Some of out MGs support text whereas others support
binary
but not both.


> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Christian Groves
> Sent: Tuesday, January 08, 2002 7:08 PM
> To: Sunesh.Kumra@nokia.com
> Cc: Brian.Rosen@marconi.com; megaco@ietf.org
> Subject: Re: [Megaco] Megaco Interoperability
>
>
> We also have MGs that are binary only. We have others that are text,
> others that are text/binary.
>
> Christian
>
> Sunesh.Kumra@nokia.com wrote:
> >
> > we have a business unit who has a Megaco stack (MG side) with only
> > binary implementation. We are developing a stack for MGC, which
> > currently supports only text, but would have to include binary support
> > if the MGs we have to control only understand binary. I would try to
> > convince our team developing MG to support Text if not moving totally to
> > text.
> >
> > -sunesh
> >
> > -----Original Message-----
> > From: ext Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Sent: 07. January 2002 16:37
> > To: Seshagiri Rao; megaco@ietf.org
> > Subject: RE: [Megaco] Megaco Interoperability
> >
> > There is not a reference design available.
> > There are test scenarios developed for the bakeoffs.  These explicitly
> > DO NOT
> > include message sequences.
> > I have been stalling on scheduling another bakeoff until we had better
> > participation.
> >   I plan to "call the question" again soon
> > Virtually all implementations are text only.  A few are both (a very
> > few).  I don't
> > know of any that are binary only.
> >
> > Brian
> >
> > -----Original Message-----
> > From: Seshagiri Rao [mailto:rsesh@nexverse.com]
> > Sent: Saturday, January 05, 2002 6:58 PM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Megaco Interoperability
> >
> > All:
> >
> > I would like to know if there is any reference design/test sequence for
> > Megaco stack implementation.
> > I would also like to know if there is any forthcoming interop/bake-off
> > event.
> > How many of the current Megaco stack implementations support ABNF/Text
> > encoding and how many support ASN.1/binary encoding?
> >
> > Sesh
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Fri Jan 11 00:36:27 2002
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 AAA02292
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 00:36:26 -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 AAA07583;
	Fri, 11 Jan 2002 00:26:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA07552
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 00:26:20 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02172
	for <megaco@ietf.org>; Fri, 11 Jan 2002 00:26:18 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW38BK>; Fri, 11 Jan 2002 10:33:36 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822EC1B8@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Date: Fri, 11 Jan 2002 10:33:32 +0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Megaco Implementors List
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


can any one tell email or Website address for Implementor's list set up by
Marconi.

regards
Asrar Ashraf

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


From daemon@optimus.ietf.org  Fri Jan 11 00:36:27 2002
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 AAA02302
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 00:36:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA08090
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 00:36:27 -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 AAA07583;
	Fri, 11 Jan 2002 00:26:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA07552
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 00:26:20 -0500 (EST)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02172
	for <megaco@ietf.org>; Fri, 11 Jan 2002 00:26:18 -0500 (EST)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <Z9QW38BK>; Fri, 11 Jan 2002 10:33:36 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3822EC1B8@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Date: Fri, 11 Jan 2002 10:33:32 +0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Megaco Implementors List
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


can any one tell email or Website address for Implementor's list set up by
Marconi.

regards
Asrar Ashraf

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



From megaco-admin@ietf.org  Fri Jan 11 02:18:16 2002
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 CAA11325
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 02:18:16 -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 BAA18414;
	Fri, 11 Jan 2002 01:56:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA18387
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 01:56:09 -0500 (EST)
Received: from web20901.mail.yahoo.com (web20901.mail.yahoo.com [216.136.226.223])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02975
	for <megaco@ietf.org>; Fri, 11 Jan 2002 01:56:07 -0500 (EST)
Message-ID: <20020111065608.7475.qmail@web20901.mail.yahoo.com>
Received: from [203.241.146.3] by web20901.mail.yahoo.com via HTTP; Thu, 10 Jan 2002 22:56:08 PST
Date: Thu, 10 Jan 2002 22:56:08 -0800 (PST)
From: Niraj Kedar <nirajk_blr@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] doubt regarding SecondEventsDescriptor
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

Hi,

Does the SecondEventsDescriptor found in the Requested
Actions structure and the embedded events descriptor
as described by the RFC 3015, mean the same?

thanx,
niraj

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

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


From daemon@optimus.ietf.org  Fri Jan 11 02:18:17 2002
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 CAA11335
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 02:18:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA19064
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 02:18:18 -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 BAA18414;
	Fri, 11 Jan 2002 01:56:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA18387
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 01:56:09 -0500 (EST)
Received: from web20901.mail.yahoo.com (web20901.mail.yahoo.com [216.136.226.223])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02975
	for <megaco@ietf.org>; Fri, 11 Jan 2002 01:56:07 -0500 (EST)
Message-ID: <20020111065608.7475.qmail@web20901.mail.yahoo.com>
Received: from [203.241.146.3] by web20901.mail.yahoo.com via HTTP; Thu, 10 Jan 2002 22:56:08 PST
Date: Thu, 10 Jan 2002 22:56:08 -0800 (PST)
From: Niraj Kedar <nirajk_blr@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] doubt regarding SecondEventsDescriptor
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

Hi,

Does the SecondEventsDescriptor found in the Requested
Actions structure and the embedded events descriptor
as described by the RFC 3015, mean the same?

thanx,
niraj

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

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



From megaco-admin@ietf.org  Fri Jan 11 04:13:30 2002
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 EAA12242
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 04:13:26 -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 DAA21746;
	Fri, 11 Jan 2002 03:56:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21715
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 03:56:33 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12107
	for <megaco@ietf.org>; Fri, 11 Jan 2002 03:56:30 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0B8uW908569
	for <megaco@ietf.org>; Fri, 11 Jan 2002 10:56:32 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T586199cda9ac158f22141@esvir02nok.ntc.nokia.com>;
 Fri, 11 Jan 2002 10:56:31 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <C13HJT31>; Fri, 11 Jan 2002 10:56:31 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D267@esebe004.NOE.Nokia.com>
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Date: Fri, 11 Jan 2002 10:53:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] comment in v2
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

Hi Marcello,

On page 112 of Megaco v2 draft, auditItem has been extended to include
indAudterminationAudit which is defined as 

indAudterminationAudit   = indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)

now AuditDescriptor has been defined as containing multiple AuditItem
separated by COMMA, so when there are multiple AuditItem all separated
by COMMA , which further contain multiple indAudauditReturnParameter
each again separated by COMMA , then how can one tell which AuditItem
did the indAudauditReturnParameter belong to ? I think that from
functionality point of view it would NOT matter because at the end all
the AuditItems would be applied to one TerminationId regardless of which
AuditItem they were a part of.

But for clarity why not define indAudterminationAudit as
indAudterminationAudit   = LBRKT indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)
RBRKT

regards,
sunesh

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


From daemon@optimus.ietf.org  Fri Jan 11 04:13:31 2002
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 EAA12251
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 04:13:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22406
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 04:13:33 -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 DAA21746;
	Fri, 11 Jan 2002 03:56:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21715
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 03:56:33 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12107
	for <megaco@ietf.org>; Fri, 11 Jan 2002 03:56:30 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0B8uW908569
	for <megaco@ietf.org>; Fri, 11 Jan 2002 10:56:32 +0200 (EET)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T586199cda9ac158f22141@esvir02nok.ntc.nokia.com>;
 Fri, 11 Jan 2002 10:56:31 +0200
Received: by esebh03nok with Internet Mail Service (5.5.2652.78)
	id <C13HJT31>; Fri, 11 Jan 2002 10:56:31 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D267@esebe004.NOE.Nokia.com>
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Date: Fri, 11 Jan 2002 10:53:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] comment in v2
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

Hi Marcello,

On page 112 of Megaco v2 draft, auditItem has been extended to include
indAudterminationAudit which is defined as 

indAudterminationAudit   = indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)

now AuditDescriptor has been defined as containing multiple AuditItem
separated by COMMA, so when there are multiple AuditItem all separated
by COMMA , which further contain multiple indAudauditReturnParameter
each again separated by COMMA , then how can one tell which AuditItem
did the indAudauditReturnParameter belong to ? I think that from
functionality point of view it would NOT matter because at the end all
the AuditItems would be applied to one TerminationId regardless of which
AuditItem they were a part of.

But for clarity why not define indAudterminationAudit as
indAudterminationAudit   = LBRKT indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)
RBRKT

regards,
sunesh

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



From megaco-admin@ietf.org  Fri Jan 11 12:22:18 2002
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 MAA22210
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 12:22:04 -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 MAA07597;
	Fri, 11 Jan 2002 12:05:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07569
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 12:05:46 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21771
	for <megaco@ietf.org>; Fri, 11 Jan 2002 12:05:42 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0BH5iJ00488
	for <megaco@ietf.org>; Fri, 11 Jan 2002 18:05:44 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Fri Jan 11 18:05:43 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKK388C>; Fri, 11 Jan 2002 18:05:27 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB3D@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Sunesh.Kumra@nokia.com'" <Sunesh.Kumra@nokia.com>
Cc: megaco@ietf.org
Date: Fri, 11 Jan 2002 18:05:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Sunesh,

I think that the current definition works fine. In my opinion it doesn't really matter which AuditItem the indAudauditReturnParameter belongs to.

For instance if you want to audit:
1)current value of events associated with the termination
2)Item2= signal Sig1,signal Sig2
 
you will have something like:

AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

Any other opinions?

Regards,
Marcello

-----Original Message-----
From: Sunesh.Kumra@nokia.com [mailto:Sunesh.Kumra@nokia.com]
Sent: Friday, January 11, 2002 9:54 AM
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Subject: comment in v2


Hi Marcello,

On page 112 of Megaco v2 draft, auditItem has been extended to include
indAudterminationAudit which is defined as 

indAudterminationAudit   = indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)

now AuditDescriptor has been defined as containing multiple AuditItem
separated by COMMA, so when there are multiple AuditItem all separated
by COMMA , which further contain multiple indAudauditReturnParameter
each again separated by COMMA , then how can one tell which AuditItem
did the indAudauditReturnParameter belong to ? I think that from
functionality point of view it would NOT matter because at the end all
the AuditItems would be applied to one TerminationId regardless of which
AuditItem they were a part of.

But for clarity why not define indAudterminationAudit as
indAudterminationAudit   = LBRKT indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)
RBRKT

regards,
sunesh

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


From daemon@optimus.ietf.org  Fri Jan 11 12:22:20 2002
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 MAA22236
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 12:22:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA07968
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 12:22:21 -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 MAA07597;
	Fri, 11 Jan 2002 12:05:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07569
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 12:05:46 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21771
	for <megaco@ietf.org>; Fri, 11 Jan 2002 12:05:42 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0BH5iJ00488
	for <megaco@ietf.org>; Fri, 11 Jan 2002 18:05:44 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Fri Jan 11 18:05:43 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKK388C>; Fri, 11 Jan 2002 18:05:27 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB3D@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Sunesh.Kumra@nokia.com'" <Sunesh.Kumra@nokia.com>
Cc: megaco@ietf.org
Date: Fri, 11 Jan 2002 18:05:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Sunesh,

I think that the current definition works fine. In my opinion it doesn't really matter which AuditItem the indAudauditReturnParameter belongs to.

For instance if you want to audit:
1)current value of events associated with the termination
2)Item2= signal Sig1,signal Sig2
 
you will have something like:

AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

Any other opinions?

Regards,
Marcello

-----Original Message-----
From: Sunesh.Kumra@nokia.com [mailto:Sunesh.Kumra@nokia.com]
Sent: Friday, January 11, 2002 9:54 AM
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Subject: comment in v2


Hi Marcello,

On page 112 of Megaco v2 draft, auditItem has been extended to include
indAudterminationAudit which is defined as 

indAudterminationAudit   = indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)

now AuditDescriptor has been defined as containing multiple AuditItem
separated by COMMA, so when there are multiple AuditItem all separated
by COMMA , which further contain multiple indAudauditReturnParameter
each again separated by COMMA , then how can one tell which AuditItem
did the indAudauditReturnParameter belong to ? I think that from
functionality point of view it would NOT matter because at the end all
the AuditItems would be applied to one TerminationId regardless of which
AuditItem they were a part of.

But for clarity why not define indAudterminationAudit as
indAudterminationAudit   = LBRKT indAudauditReturnParameter  
                                *(COMMA indAudauditReturnParameter)
RBRKT

regards,
sunesh

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



From megaco-admin@ietf.org  Fri Jan 11 16:46:03 2002
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 QAA00609
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 16:46:03 -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 QAA17306;
	Fri, 11 Jan 2002 16:33:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17186
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 16:31:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00269
	for <megaco@ietf.org>; Fri, 11 Jan 2002 16:31:49 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVJD09197;
	Fri, 11 Jan 2002 16:31:19 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVHG00953;
	Fri, 11 Jan 2002 16:31:17 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRG2NK7>; Fri, 11 Jan 2002 16:29:47 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE2A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Implementors List
Date: Fri, 11 Jan 2002 16:31:16 -0500
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

Send a message to majordomo@marconi.com containing the line
subscribe megaco-interop

List mail goes to megaco-interop@marconi.com.

-----Original Message-----
From: asrar ashraf [mailto:asrar@enabtech.com]
Sent: Friday, January 11, 2002 12:34 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco Implementors List



can any one tell email or Website address for Implementor's list set up by
Marconi.

regards
Asrar Ashraf

_______________________________________________
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


From daemon@optimus.ietf.org  Fri Jan 11 16:46:04 2002
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 QAA00617
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 16:46:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17519
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 16:46:05 -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 QAA17306;
	Fri, 11 Jan 2002 16:33:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17186
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 16:31:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00269
	for <megaco@ietf.org>; Fri, 11 Jan 2002 16:31:49 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVJD09197;
	Fri, 11 Jan 2002 16:31:19 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVHG00953;
	Fri, 11 Jan 2002 16:31:17 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRG2NK7>; Fri, 11 Jan 2002 16:29:47 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE2A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Implementors List
Date: Fri, 11 Jan 2002 16:31:16 -0500
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

Send a message to majordomo@marconi.com containing the line
subscribe megaco-interop

List mail goes to megaco-interop@marconi.com.

-----Original Message-----
From: asrar ashraf [mailto:asrar@enabtech.com]
Sent: Friday, January 11, 2002 12:34 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco Implementors List



can any one tell email or Website address for Implementor's list set up by
Marconi.

regards
Asrar Ashraf

_______________________________________________
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



From megaco-admin@ietf.org  Fri Jan 11 16:49:51 2002
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 QAA00756
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 16:49:51 -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 QAA17255;
	Fri, 11 Jan 2002 16:32:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17227
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 16:32:29 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00287
	for <megaco@ietf.org>; Fri, 11 Jan 2002 16:32:27 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVwD09327;
	Fri, 11 Jan 2002 16:31:58 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVuG01003;
	Fri, 11 Jan 2002 16:31:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRG2NLW>; Fri, 11 Jan 2002 16:30:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE2B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Niraj Kedar'" <nirajk_blr@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] doubt regarding SecondEventsDescriptor
Date: Fri, 11 Jan 2002 16:31:51 -0500
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

Yes.

-----Original Message-----
From: Niraj Kedar [mailto:nirajk_blr@yahoo.com]
Sent: Friday, January 11, 2002 1:56 AM
To: megaco@ietf.org
Subject: [Megaco] doubt regarding SecondEventsDescriptor


Hi,

Does the SecondEventsDescriptor found in the Requested
Actions structure and the embedded events descriptor
as described by the RFC 3015, mean the same?

thanx,
niraj

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

_______________________________________________
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


From daemon@optimus.ietf.org  Fri Jan 11 16:49:52 2002
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 QAA00767
	for <megaco-archive@odin.ietf.org>; Fri, 11 Jan 2002 16:49:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17579
	for megaco-archive@odin.ietf.org; Fri, 11 Jan 2002 16:49:54 -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 QAA17255;
	Fri, 11 Jan 2002 16:32:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17227
	for <megaco@optimus.ietf.org>; Fri, 11 Jan 2002 16:32:29 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00287
	for <megaco@ietf.org>; Fri, 11 Jan 2002 16:32:27 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVwD09327;
	Fri, 11 Jan 2002 16:31:58 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0BLVuG01003;
	Fri, 11 Jan 2002 16:31:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CTRG2NLW>; Fri, 11 Jan 2002 16:30:26 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE2B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Niraj Kedar'" <nirajk_blr@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] doubt regarding SecondEventsDescriptor
Date: Fri, 11 Jan 2002 16:31:51 -0500
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

Yes.

-----Original Message-----
From: Niraj Kedar [mailto:nirajk_blr@yahoo.com]
Sent: Friday, January 11, 2002 1:56 AM
To: megaco@ietf.org
Subject: [Megaco] doubt regarding SecondEventsDescriptor


Hi,

Does the SecondEventsDescriptor found in the Requested
Actions structure and the embedded events descriptor
as described by the RFC 3015, mean the same?

thanx,
niraj

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

_______________________________________________
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



From megaco-admin@ietf.org  Sat Jan 12 01:46:00 2002
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 BAA09324
	for <megaco-archive@odin.ietf.org>; Sat, 12 Jan 2002 01:46:00 -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 BAA08688;
	Sat, 12 Jan 2002 01:29:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA08659
	for <megaco@optimus.ietf.org>; Sat, 12 Jan 2002 01:29:32 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09125
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 01:29:28 -0500 (EST)
From: raverma@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0C6TOE19781
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 11:59:24 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B3F.002384DC ; Sat, 12 Jan 2002 11:57:57 +0530
X-Lotus-FromDomain: HSS
To: MEGACO@ietf.org
Message-ID: <65256B3F.0023845B.00@sandesh.hss.hns.com>
Date: Sat, 12 Jan 2002 11:59:45 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Error on receiving Transaction Pending for non-existent
 Transaction
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



Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




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


From daemon@optimus.ietf.org  Sat Jan 12 01:46:01 2002
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 BAA09336
	for <megaco-archive@odin.ietf.org>; Sat, 12 Jan 2002 01:46:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA09277
	for megaco-archive@odin.ietf.org; Sat, 12 Jan 2002 01:46:02 -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 BAA08688;
	Sat, 12 Jan 2002 01:29:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA08659
	for <megaco@optimus.ietf.org>; Sat, 12 Jan 2002 01:29:32 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09125
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 01:29:28 -0500 (EST)
From: raverma@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0C6TOE19781
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 11:59:24 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B3F.002384DC ; Sat, 12 Jan 2002 11:57:57 +0530
X-Lotus-FromDomain: HSS
To: MEGACO@ietf.org
Message-ID: <65256B3F.0023845B.00@sandesh.hss.hns.com>
Date: Sat, 12 Jan 2002 11:59:45 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Error on receiving Transaction Pending for non-existent
 Transaction
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



Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




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



From megaco-admin@ietf.org  Sat Jan 12 11:30:31 2002
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 LAA21845
	for <megaco-archive@odin.ietf.org>; Sat, 12 Jan 2002 11:30:30 -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 LAA20574;
	Sat, 12 Jan 2002 11:09:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20546
	for <megaco@optimus.ietf.org>; Sat, 12 Jan 2002 11:09:53 -0500 (EST)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21620
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 11:09:49 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.122])
	by muninn.ctccom.net (Mirapoint)
	with SMTP id AFY51033;
	Sat, 12 Jan 2002 11:09:12 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <raverma@hss.hns.com>, <MEGACO@ietf.org>
Subject: RE: [Megaco] Error on receiving Transaction Pending for non-existent Transaction
Date: Sat, 12 Jan 2002 11:05:31 -0500
Message-ID: <012001c19b82$f633acc0$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <65256B3F.0023845B.00@sandesh.hss.hns.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Rakhi,All,
The transaction pending message is an indication to the command generator
that the command responder needs some more time to handle the request. If
due to what ever reasons the transaction pending is received, say after the
transaction response is received, then it should be silently discarded. NO
need to generate any error code as such. Since there is no acknowledgement
for transaction pending, discarding any such message doesn't pose a problem.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
raverma@hss.hns.com
Sent: Saturday, January 12, 2002 1:30 AM
To: MEGACO@ietf.org
Subject: [Megaco] Error on receiving Transaction Pending for
non-existent Transaction




Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




_______________________________________________
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


From daemon@optimus.ietf.org  Sat Jan 12 11:30:31 2002
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 LAA21854
	for <megaco-archive@odin.ietf.org>; Sat, 12 Jan 2002 11:30:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA21081
	for megaco-archive@odin.ietf.org; Sat, 12 Jan 2002 11:30:34 -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 LAA20574;
	Sat, 12 Jan 2002 11:09:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20546
	for <megaco@optimus.ietf.org>; Sat, 12 Jan 2002 11:09:53 -0500 (EST)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21620
	for <MEGACO@ietf.org>; Sat, 12 Jan 2002 11:09:49 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.122])
	by muninn.ctccom.net (Mirapoint)
	with SMTP id AFY51033;
	Sat, 12 Jan 2002 11:09:12 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <raverma@hss.hns.com>, <MEGACO@ietf.org>
Subject: RE: [Megaco] Error on receiving Transaction Pending for non-existent Transaction
Date: Sat, 12 Jan 2002 11:05:31 -0500
Message-ID: <012001c19b82$f633acc0$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <65256B3F.0023845B.00@sandesh.hss.hns.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Rakhi,All,
The transaction pending message is an indication to the command generator
that the command responder needs some more time to handle the request. If
due to what ever reasons the transaction pending is received, say after the
transaction response is received, then it should be silently discarded. NO
need to generate any error code as such. Since there is no acknowledgement
for transaction pending, discarding any such message doesn't pose a problem.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
raverma@hss.hns.com
Sent: Saturday, January 12, 2002 1:30 AM
To: MEGACO@ietf.org
Subject: [Megaco] Error on receiving Transaction Pending for
non-existent Transaction




Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 14 03:28:25 2002
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 DAA29827
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 03:28:25 -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 DAA27814;
	Mon, 14 Jan 2002 03:10:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27784
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 03:10:37 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29740
	for <megaco@ietf.org>; Mon, 14 Jan 2002 03:10:34 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0E8AKu06175
	for <megaco@ietf.org>; Mon, 14 Jan 2002 10:10:20 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5870e2c57fac158f270dc@esvir07nok.ntc.nokia.com>;
 Mon, 14 Jan 2002 10:10:31 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <CHN4KLXX>; Mon, 14 Jan 2002 10:10:28 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D26C@esebe004.NOE.Nokia.com>
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Date: Mon, 14 Jan 2002 10:10:26 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Marcello,

I agree that from functionality point of view this would absolutely
work, but from design point of view it looked a little odd. But I can
live with it. 
Also on page 113 :
indAudsignalList = SignalListToken EQUAL signalListId LBRKT  
                      indAudsignalListParm RBRKT

but indAudsignalListParm is not defined in the draft.

Regards,
sunesh

		-----Original Message-----
		From:	ext Marcello Pantaleo (EED)
[mailto:Marcello.Pantaleo@eed.ericsson.se]
		Sent:	11. January 2002 19:06
		To:	Kumra Sunesh (NET/Helsinki)
		Cc:	megaco@ietf.org
		Subject:	RE: comment in v2

		Hi Sunesh,

		I think that the current definition works fine. In my
opinion it doesn't really matter which AuditItem the
indAudauditReturnParameter belongs to.

		For instance if you want to audit:
		1)current value of events associated with the
termination
		2)Item2= signal Sig1,signal Sig2
		 
		you will have something like:

	
AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

		Any other opinions?

		Regards,
		Marcello

		-----Original Message-----
		From: Sunesh.Kumra@nokia.com
[mailto:Sunesh.Kumra@nokia.com]
		Sent: Friday, January 11, 2002 9:54 AM
		To: Marcello.Pantaleo@eed.ericsson.se
		Cc: megaco@ietf.org
		Subject: comment in v2


		Hi Marcello,

		On page 112 of Megaco v2 draft, auditItem has been
extended to include
		indAudterminationAudit which is defined as 

		indAudterminationAudit   = indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)

		now AuditDescriptor has been defined as containing
multiple AuditItem
		separated by COMMA, so when there are multiple AuditItem
all separated
		by COMMA , which further contain multiple
indAudauditReturnParameter
		each again separated by COMMA , then how can one tell
which AuditItem
		did the indAudauditReturnParameter belong to ? I think
that from
		functionality point of view it would NOT matter because
at the end all
		the AuditItems would be applied to one TerminationId
regardless of which
		AuditItem they were a part of.

		But for clarity why not define indAudterminationAudit as
		indAudterminationAudit   = LBRKT
indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)
		RBRKT

		regards,
		sunesh

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


From daemon@optimus.ietf.org  Mon Jan 14 03:28:26 2002
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 DAA29838
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 03:28:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA27988
	for megaco-archive@odin.ietf.org; Mon, 14 Jan 2002 03:28:28 -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 DAA27814;
	Mon, 14 Jan 2002 03:10:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27784
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 03:10:37 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29740
	for <megaco@ietf.org>; Mon, 14 Jan 2002 03:10:34 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir07nok.ntc.nokia.com (esvir07nokt.ntc.nokia.com [172.21.143.39])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0E8AKu06175
	for <megaco@ietf.org>; Mon, 14 Jan 2002 10:10:20 +0200 (EET)
Received: from esebh01nok.ntc.nokia.com (unverified) by esvir07nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5870e2c57fac158f270dc@esvir07nok.ntc.nokia.com>;
 Mon, 14 Jan 2002 10:10:31 +0200
Received: by esebh01nok with Internet Mail Service (5.5.2652.78)
	id <CHN4KLXX>; Mon, 14 Jan 2002 10:10:28 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D26C@esebe004.NOE.Nokia.com>
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Date: Mon, 14 Jan 2002 10:10:26 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Marcello,

I agree that from functionality point of view this would absolutely
work, but from design point of view it looked a little odd. But I can
live with it. 
Also on page 113 :
indAudsignalList = SignalListToken EQUAL signalListId LBRKT  
                      indAudsignalListParm RBRKT

but indAudsignalListParm is not defined in the draft.

Regards,
sunesh

		-----Original Message-----
		From:	ext Marcello Pantaleo (EED)
[mailto:Marcello.Pantaleo@eed.ericsson.se]
		Sent:	11. January 2002 19:06
		To:	Kumra Sunesh (NET/Helsinki)
		Cc:	megaco@ietf.org
		Subject:	RE: comment in v2

		Hi Sunesh,

		I think that the current definition works fine. In my
opinion it doesn't really matter which AuditItem the
indAudauditReturnParameter belongs to.

		For instance if you want to audit:
		1)current value of events associated with the
termination
		2)Item2= signal Sig1,signal Sig2
		 
		you will have something like:

	
AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

		Any other opinions?

		Regards,
		Marcello

		-----Original Message-----
		From: Sunesh.Kumra@nokia.com
[mailto:Sunesh.Kumra@nokia.com]
		Sent: Friday, January 11, 2002 9:54 AM
		To: Marcello.Pantaleo@eed.ericsson.se
		Cc: megaco@ietf.org
		Subject: comment in v2


		Hi Marcello,

		On page 112 of Megaco v2 draft, auditItem has been
extended to include
		indAudterminationAudit which is defined as 

		indAudterminationAudit   = indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)

		now AuditDescriptor has been defined as containing
multiple AuditItem
		separated by COMMA, so when there are multiple AuditItem
all separated
		by COMMA , which further contain multiple
indAudauditReturnParameter
		each again separated by COMMA , then how can one tell
which AuditItem
		did the indAudauditReturnParameter belong to ? I think
that from
		functionality point of view it would NOT matter because
at the end all
		the AuditItems would be applied to one TerminationId
regardless of which
		AuditItem they were a part of.

		But for clarity why not define indAudterminationAudit as
		indAudterminationAudit   = LBRKT
indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)
		RBRKT

		regards,
		sunesh

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



From megaco-admin@ietf.org  Mon Jan 14 07:06:14 2002
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 HAA01523
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 07:06:09 -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 GAA03605;
	Mon, 14 Jan 2002 06:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03574
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 06:53:44 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01455
	for <megaco@ietf.org>; Mon, 14 Jan 2002 06:53:37 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0EBrbJ28043
	for <megaco@ietf.org>; Mon, 14 Jan 2002 12:53:37 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Jan 14 12:53:16 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKP778>; Mon, 14 Jan 2002 12:53:32 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB3E@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Sunesh.Kumra@nokia.com'" <Sunesh.Kumra@nokia.com>
Cc: megaco@ietf.org
Date: Mon, 14 Jan 2002 12:53:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Sunesh,

yes, you're right. indAudsignalListParm is not defined.

I think it should be:

indAudsignalListParm       = indAudsignalRequest

I'll fix it.

Regards,
Marcello
-----Original Message-----
From: Sunesh.Kumra@nokia.com [mailto:Sunesh.Kumra@nokia.com]
Sent: Monday, January 14, 2002 9:10 AM
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Subject: RE: comment in v2


Hi Marcello,

I agree that from functionality point of view this would absolutely
work, but from design point of view it looked a little odd. But I can
live with it. 
Also on page 113 :
indAudsignalList = SignalListToken EQUAL signalListId LBRKT  
                      indAudsignalListParm RBRKT

but indAudsignalListParm is not defined in the draft.

Regards,
sunesh

		-----Original Message-----
		From:	ext Marcello Pantaleo (EED)
[mailto:Marcello.Pantaleo@eed.ericsson.se]
		Sent:	11. January 2002 19:06
		To:	Kumra Sunesh (NET/Helsinki)
		Cc:	megaco@ietf.org
		Subject:	RE: comment in v2

		Hi Sunesh,

		I think that the current definition works fine. In my
opinion it doesn't really matter which AuditItem the
indAudauditReturnParameter belongs to.

		For instance if you want to audit:
		1)current value of events associated with the
termination
		2)Item2= signal Sig1,signal Sig2
		 
		you will have something like:

	
AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

		Any other opinions?

		Regards,
		Marcello

		-----Original Message-----
		From: Sunesh.Kumra@nokia.com
[mailto:Sunesh.Kumra@nokia.com]
		Sent: Friday, January 11, 2002 9:54 AM
		To: Marcello.Pantaleo@eed.ericsson.se
		Cc: megaco@ietf.org
		Subject: comment in v2


		Hi Marcello,

		On page 112 of Megaco v2 draft, auditItem has been
extended to include
		indAudterminationAudit which is defined as 

		indAudterminationAudit   = indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)

		now AuditDescriptor has been defined as containing
multiple AuditItem
		separated by COMMA, so when there are multiple AuditItem
all separated
		by COMMA , which further contain multiple
indAudauditReturnParameter
		each again separated by COMMA , then how can one tell
which AuditItem
		did the indAudauditReturnParameter belong to ? I think
that from
		functionality point of view it would NOT matter because
at the end all
		the AuditItems would be applied to one TerminationId
regardless of which
		AuditItem they were a part of.

		But for clarity why not define indAudterminationAudit as
		indAudterminationAudit   = LBRKT
indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)
		RBRKT

		regards,
		sunesh

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


From daemon@optimus.ietf.org  Mon Jan 14 07:06:14 2002
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 HAA01530
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 07:06:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA04110
	for megaco-archive@odin.ietf.org; Mon, 14 Jan 2002 07:06:16 -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 GAA03605;
	Mon, 14 Jan 2002 06:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03574
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 06:53:44 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01455
	for <megaco@ietf.org>; Mon, 14 Jan 2002 06:53:37 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0EBrbJ28043
	for <megaco@ietf.org>; Mon, 14 Jan 2002 12:53:37 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Jan 14 12:53:16 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKP778>; Mon, 14 Jan 2002 12:53:32 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB3E@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Sunesh.Kumra@nokia.com'" <Sunesh.Kumra@nokia.com>
Cc: megaco@ietf.org
Date: Mon, 14 Jan 2002 12:53:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] RE: comment in v2
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

Hi Sunesh,

yes, you're right. indAudsignalListParm is not defined.

I think it should be:

indAudsignalListParm       = indAudsignalRequest

I'll fix it.

Regards,
Marcello
-----Original Message-----
From: Sunesh.Kumra@nokia.com [mailto:Sunesh.Kumra@nokia.com]
Sent: Monday, January 14, 2002 9:10 AM
To: Marcello.Pantaleo@eed.ericsson.se
Cc: megaco@ietf.org
Subject: RE: comment in v2


Hi Marcello,

I agree that from functionality point of view this would absolutely
work, but from design point of view it looked a little odd. But I can
live with it. 
Also on page 113 :
indAudsignalList = SignalListToken EQUAL signalListId LBRKT  
                      indAudsignalListParm RBRKT

but indAudsignalListParm is not defined in the draft.

Regards,
sunesh

		-----Original Message-----
		From:	ext Marcello Pantaleo (EED)
[mailto:Marcello.Pantaleo@eed.ericsson.se]
		Sent:	11. January 2002 19:06
		To:	Kumra Sunesh (NET/Helsinki)
		Cc:	megaco@ietf.org
		Subject:	RE: comment in v2

		Hi Sunesh,

		I think that the current definition works fine. In my
opinion it doesn't really matter which AuditItem the
indAudauditReturnParameter belongs to.

		For instance if you want to audit:
		1)current value of events associated with the
termination
		2)Item2= signal Sig1,signal Sig2
		 
		you will have something like:

	
AV=TerminationId{AT{E,SG{PackageName/Sig1},SG{PackageName/Sig2}}}

		Any other opinions?

		Regards,
		Marcello

		-----Original Message-----
		From: Sunesh.Kumra@nokia.com
[mailto:Sunesh.Kumra@nokia.com]
		Sent: Friday, January 11, 2002 9:54 AM
		To: Marcello.Pantaleo@eed.ericsson.se
		Cc: megaco@ietf.org
		Subject: comment in v2


		Hi Marcello,

		On page 112 of Megaco v2 draft, auditItem has been
extended to include
		indAudterminationAudit which is defined as 

		indAudterminationAudit   = indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)

		now AuditDescriptor has been defined as containing
multiple AuditItem
		separated by COMMA, so when there are multiple AuditItem
all separated
		by COMMA , which further contain multiple
indAudauditReturnParameter
		each again separated by COMMA , then how can one tell
which AuditItem
		did the indAudauditReturnParameter belong to ? I think
that from
		functionality point of view it would NOT matter because
at the end all
		the AuditItems would be applied to one TerminationId
regardless of which
		AuditItem they were a part of.

		But for clarity why not define indAudterminationAudit as
		indAudterminationAudit   = LBRKT
indAudauditReturnParameter  
		                                *(COMMA
indAudauditReturnParameter)
		RBRKT

		regards,
		sunesh

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



From megaco-admin@ietf.org  Mon Jan 14 07:36:18 2002
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 HAA01772
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 07:36:18 -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 HAA04312;
	Mon, 14 Jan 2002 07:19:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA04281
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 07:19:14 -0500 (EST)
Received: from ws1-9.us4.outblaze.com (205-158-62-55.outblaze.com [205.158.62.55])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01640
	for <megaco@ietf.org>; Mon, 14 Jan 2002 07:19:11 -0500 (EST)
Received: (qmail 89196 invoked by uid 1001); 14 Jan 2002 12:18:42 -0000
Message-ID: <20020114121842.89194.qmail@mail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from ws1-3.us4.outblaze.com for [203.215.160.34] via web-mailer
    on Mon, 14 Jan 2002 20:18:42 +0800
From: "Zahid Anwar" <zahidanwar@mail.com>
To: megaco@ietf.org
Date: Mon, 14 Jan 2002 20:18:42 +0800
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Information regarding MEGACO Torture Tests
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: 7bit

Hello All.

Does anyone have information to share regarding any tests that can be used to verify whether one's MEGACO stack is Level 3 compliant or not. Any kind of information regarding

-torture tests
-basic test cases
-tests carried out at the last Interop

would be very welcome. Also is there any formal Megaco Interop Report other than draft-rosen-interop-1-report-00.txt available?

Regards
Zahid Anwar
-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup


1 cent a minute calls anywhere in the U.S.!

http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com



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


From daemon@optimus.ietf.org  Mon Jan 14 07:36:19 2002
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 HAA01783
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 07:36:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA04908
	for megaco-archive@odin.ietf.org; Mon, 14 Jan 2002 07:36:21 -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 HAA04312;
	Mon, 14 Jan 2002 07:19:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA04281
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 07:19:14 -0500 (EST)
Received: from ws1-9.us4.outblaze.com (205-158-62-55.outblaze.com [205.158.62.55])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01640
	for <megaco@ietf.org>; Mon, 14 Jan 2002 07:19:11 -0500 (EST)
Received: (qmail 89196 invoked by uid 1001); 14 Jan 2002 12:18:42 -0000
Message-ID: <20020114121842.89194.qmail@mail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from ws1-3.us4.outblaze.com for [203.215.160.34] via web-mailer
    on Mon, 14 Jan 2002 20:18:42 +0800
From: "Zahid Anwar" <zahidanwar@mail.com>
To: megaco@ietf.org
Date: Mon, 14 Jan 2002 20:18:42 +0800
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Information regarding MEGACO Torture Tests
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: 7bit

Hello All.

Does anyone have information to share regarding any tests that can be used to verify whether one's MEGACO stack is Level 3 compliant or not. Any kind of information regarding

-torture tests
-basic test cases
-tests carried out at the last Interop

would be very welcome. Also is there any formal Megaco Interop Report other than draft-rosen-interop-1-report-00.txt available?

Regards
Zahid Anwar
-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup


1 cent a minute calls anywhere in the U.S.!

http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com



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



From megaco-admin@ietf.org  Mon Jan 14 09:40:36 2002
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 JAA03200
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 09:40:36 -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 JAA08028;
	Mon, 14 Jan 2002 09:17:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07999
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 09:17:14 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02890
	for <MEGACO@ietf.org>; Mon, 14 Jan 2002 09:17:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0EEGgK09270;
	Mon, 14 Jan 2002 09:16:43 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0EEGe109843;
	Mon, 14 Jan 2002 09:16:41 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZTG1Q>; Mon, 14 Jan 2002 09:16:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE33@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'raverma@hss.hns.com'" <raverma@hss.hns.com>, MEGACO@ietf.org
Subject: RE: [Megaco] Error on receiving Transaction Pending for non-exist
	ent Transaction
Date: Mon, 14 Jan 2002 09:16:46 -0500
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

No error is to be sent in this case.  A general principle is that errors are
sent only in transaction replies -- otherwise you have the potential for an
infinite loop of error responses or at the very least a denial-of-service
attack.

-----Original Message-----
From: raverma@hss.hns.com [mailto:raverma@hss.hns.com]
Sent: Saturday, January 12, 2002 1:30 AM
To: MEGACO@ietf.org
Subject: [Megaco] Error on receiving Transaction Pending for
non-existent Transaction




Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan 14 09:40:37 2002
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 JAA03209
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 09:40:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA09032
	for megaco-archive@odin.ietf.org; Mon, 14 Jan 2002 09:40:38 -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 JAA08028;
	Mon, 14 Jan 2002 09:17:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07999
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 09:17:14 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02890
	for <MEGACO@ietf.org>; Mon, 14 Jan 2002 09:17:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0EEGgK09270;
	Mon, 14 Jan 2002 09:16:43 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0EEGe109843;
	Mon, 14 Jan 2002 09:16:41 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZTG1Q>; Mon, 14 Jan 2002 09:16:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE33@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'raverma@hss.hns.com'" <raverma@hss.hns.com>, MEGACO@ietf.org
Subject: RE: [Megaco] Error on receiving Transaction Pending for non-exist
	ent Transaction
Date: Mon, 14 Jan 2002 09:16:46 -0500
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

No error is to be sent in this case.  A general principle is that errors are
sent only in transaction replies -- otherwise you have the potential for an
infinite loop of error responses or at the very least a denial-of-service
attack.

-----Original Message-----
From: raverma@hss.hns.com [mailto:raverma@hss.hns.com]
Sent: Saturday, January 12, 2002 1:30 AM
To: MEGACO@ietf.org
Subject: [Megaco] Error on receiving Transaction Pending for
non-existent Transaction




Hi all,
       I have a doubt regarding error to be sent when Transaction Pending is
received for a non-existent transaction .
Which error code should be sent  in this case?


Thanks & regards
Rakhi

Hughes Software Systems




_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 14 23:58:08 2002
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 XAA04557
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 23:58:08 -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 XAA10643;
	Mon, 14 Jan 2002 23:50:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10615
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 23:50:39 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04483
	for <megaco@ietf.org>; Mon, 14 Jan 2002 23:50:35 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001689715@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 10:35:25 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0F4o2o30794;
	Tue, 15 Jan 2002 10:20:02 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 10:19:43 +0530
Message-Id: <000501c19d80$0d6ff3e0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Service Change command with "ServiceChangeVersion" parameter
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: 7bit

Hi,

In between if MGC changes the protocol version through Service Change
command,
then "Is MG will send Service Change with method = warmboot or not".

Assume that changed protocol version is supported by MG.

Thanks,
Sudhir



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


From daemon@optimus.ietf.org  Mon Jan 14 23:58:08 2002
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 XAA04565
	for <megaco-archive@odin.ietf.org>; Mon, 14 Jan 2002 23:58:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA10704
	for megaco-archive@odin.ietf.org; Mon, 14 Jan 2002 23:58:10 -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 XAA10643;
	Mon, 14 Jan 2002 23:50:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10615
	for <megaco@optimus.ietf.org>; Mon, 14 Jan 2002 23:50:39 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04483
	for <megaco@ietf.org>; Mon, 14 Jan 2002 23:50:35 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001689715@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 10:35:25 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0F4o2o30794;
	Tue, 15 Jan 2002 10:20:02 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 10:19:43 +0530
Message-Id: <000501c19d80$0d6ff3e0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Service Change command with "ServiceChangeVersion" parameter
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: 7bit

Hi,

In between if MGC changes the protocol version through Service Change
command,
then "Is MG will send Service Change with method = warmboot or not".

Assume that changed protocol version is supported by MG.

Thanks,
Sudhir



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



From megaco-admin@ietf.org  Tue Jan 15 02:23:32 2002
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 CAA14373
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 02:23:32 -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 CAA23315;
	Tue, 15 Jan 2002 02:01:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23289
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 02:01:34 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07181
	for <megaco@ietf.org>; Tue, 15 Jan 2002 02:01:31 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001690713@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 12:46:21 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0F70xo11641;
	Tue, 15 Jan 2002 12:30:59 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 12:30:40 +0530
Message-Id: <000801c19d92$58885400$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] different versions of Packages
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: 7bit

Hi,

Can anybody mail me "where can I get different versions of Packages".

Is there any version 2 for Network, RTP, TDM Circuit and R2 packages.
If there was any version 2 for the above specified packages, please mail me
information about "where can I get those packages from Internet".

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Tue Jan 15 02:23:32 2002
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 CAA14382
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 02:23:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA23556
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 02:23:33 -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 CAA23315;
	Tue, 15 Jan 2002 02:01:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23289
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 02:01:34 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07181
	for <megaco@ietf.org>; Tue, 15 Jan 2002 02:01:31 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001690713@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 12:46:21 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0F70xo11641;
	Tue, 15 Jan 2002 12:30:59 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 12:30:40 +0530
Message-Id: <000801c19d92$58885400$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] different versions of Packages
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: 7bit

Hi,

Can anybody mail me "where can I get different versions of Packages".

Is there any version 2 for Network, RTP, TDM Circuit and R2 packages.
If there was any version 2 for the above specified packages, please mail me
information about "where can I get those packages from Internet".

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Tue Jan 15 02:44:19 2002
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 CAA14630
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 02:44:19 -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 CAA23650;
	Tue, 15 Jan 2002 02:27:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23621
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 02:27:54 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14409
	for <megaco@ietf.org>; Tue, 15 Jan 2002 02:27:51 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0F7RpK20905
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:27:51 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0F7Rpds011532
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:27:51 +0200 (EET)
Message-ID: <3C43D9F6.3DBB2A01@lmf.ericsson.se>
Date: Tue, 15 Jan 2002 09:27:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] LCN mapping
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: 7bit


Hi,

I have a question related to H.223 multiplexing.

Assume that I have one E1/T1 termination (T1) and one RTP termination
(T2). The RTP termination has two streams, one for audio and one for
video (I could also have separate terminations for each RTP stream).

Then I also add a multiplexing termination (T3), and in the
MuxDescriptor I define that T1 and T2 shall be multiplexed.

My question is: how do I define that a specific H.223 LCN is multiplexed
into a specific H.248 stream? Can I assume that this will be done if I
use the same value for the StreamId and the specific LCN that stream
shall be mapped into?

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Tue Jan 15 02:44:20 2002
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 CAA14639
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 02:44:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA24188
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 02:44:21 -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 CAA23650;
	Tue, 15 Jan 2002 02:27:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23621
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 02:27:54 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14409
	for <megaco@ietf.org>; Tue, 15 Jan 2002 02:27:51 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0F7RpK20905
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:27:51 +0100 (MET)
Received: from lmf.ericsson.se (lmf00215pc.lmf.ericsson.se [131.160.30.14])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0F7Rpds011532
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:27:51 +0200 (EET)
Message-ID: <3C43D9F6.3DBB2A01@lmf.ericsson.se>
Date: Tue, 15 Jan 2002 09:27:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] LCN mapping
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: 7bit


Hi,

I have a question related to H.223 multiplexing.

Assume that I have one E1/T1 termination (T1) and one RTP termination
(T2). The RTP termination has two streams, one for audio and one for
video (I could also have separate terminations for each RTP stream).

Then I also add a multiplexing termination (T3), and in the
MuxDescriptor I define that T1 and T2 shall be multiplexed.

My question is: how do I define that a specific H.223 LCN is multiplexed
into a specific H.248 stream? Can I assume that this will be done if I
use the same value for the StreamId and the specific LCN that stream
shall be mapped into?

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Tue Jan 15 06:30:57 2002
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 GAA18188
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 06:30:57 -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 GAA00647;
	Tue, 15 Jan 2002 06:12:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00619
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 06:12:06 -0500 (EST)
Received: from pop007pub.verizon.net ([206.46.170.234])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17412
	for <megaco@ietf.org>; Tue, 15 Jan 2002 06:12:03 -0500 (EST)
Received: from matt.verizon.net ([212.234.161.3])
	by pop007pub.verizon.net  with ESMTP
	for <megaco@ietf.org>; id g0FBC3Hm022316
	Tue, 15 Jan 2002 05:12:04 -0600 (CST)
Message-Id: <5.1.0.14.2.20020115030929.00a32b30@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 15 Jan 2002 03:11:50 -0800
To: megaco@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] error handling
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

I was thinking about error handling and looked at RFC 3015 for some text to 
see if there are any MUST's or SHOULD's for how to handle invalid messages 
or parameters. I see Section 7.3, but I don't see any text which mandates 
the use.

Is this an oversight? Is this being considered for V2?


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


From daemon@optimus.ietf.org  Tue Jan 15 06:30:58 2002
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 GAA18199
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 06:30:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA01451
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 06:30:59 -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 GAA00647;
	Tue, 15 Jan 2002 06:12:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00619
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 06:12:06 -0500 (EST)
Received: from pop007pub.verizon.net ([206.46.170.234])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17412
	for <megaco@ietf.org>; Tue, 15 Jan 2002 06:12:03 -0500 (EST)
Received: from matt.verizon.net ([212.234.161.3])
	by pop007pub.verizon.net  with ESMTP
	for <megaco@ietf.org>; id g0FBC3Hm022316
	Tue, 15 Jan 2002 05:12:04 -0600 (CST)
Message-Id: <5.1.0.14.2.20020115030929.00a32b30@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 15 Jan 2002 03:11:50 -0800
To: megaco@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] error handling
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

I was thinking about error handling and looked at RFC 3015 for some text to 
see if there are any MUST's or SHOULD's for how to handle invalid messages 
or parameters. I see Section 7.3, but I don't see any text which mandates 
the use.

Is this an oversight? Is this being considered for V2?


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



From megaco-admin@ietf.org  Tue Jan 15 07:05:37 2002
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 HAA19178
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 07:05:36 -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 GAA01891;
	Tue, 15 Jan 2002 06:49:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA01861
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 06:49:40 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18902
	for <megaco@ietf.org>; Tue, 15 Jan 2002 06:49:36 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0FBnuE02892;
	Tue, 15 Jan 2002 17:19:56 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B42.0040D9D8 ; Tue, 15 Jan 2002 17:18:20 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B42.003FB27C.00@sandesh.hss.hns.com>
Date: Tue, 15 Jan 2002 17:09:22 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, Christian

I need some more clarification to this. Now when we are retransmitting the
response, then we should have some kind of threshold value for the
retransmission also. And if the number of retries exceeds the threshold, then
should it assume that the peer entity has gone down and start the recovery
mechanism as suggested for transaction request.

Regards
Vivek






"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmatio is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan 15 07:05:37 2002
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 HAA19184
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 07:05:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA02506
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 07:05:38 -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 GAA01891;
	Tue, 15 Jan 2002 06:49:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA01861
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 06:49:40 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18902
	for <megaco@ietf.org>; Tue, 15 Jan 2002 06:49:36 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0FBnuE02892;
	Tue, 15 Jan 2002 17:19:56 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B42.0040D9D8 ; Tue, 15 Jan 2002 17:18:20 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B42.003FB27C.00@sandesh.hss.hns.com>
Date: Tue, 15 Jan 2002 17:09:22 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, Christian

I need some more clarification to this. Now when we are retransmitting the
response, then we should have some kind of threshold value for the
retransmission also. And if the number of retries exceeds the threshold, then
should it assume that the peer entity has gone down and start the recovery
mechanism as suggested for transaction request.

Regards
Vivek






"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmatio is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 15 07:53:50 2002
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 HAA20695
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 07:53:49 -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 HAA03725;
	Tue, 15 Jan 2002 07:45:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03698
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 07:45:24 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20443
	for <megaco@ietf.org>; Tue, 15 Jan 2002 07:45:20 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0FCjLJ14587
	for <megaco@ietf.org>; Tue, 15 Jan 2002 13:45:21 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Jan 15 13:45:12 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKRFJY>; Tue, 15 Jan 2002 13:45:11 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB43@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling
Date: Tue, 15 Jan 2002 13:44:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You shold have a look at H.248 Annex L. You find a copy at:

ftp://standards.nortelnetworks.com/megaco/docs/Approved/

/MP
-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Tuesday, January 15, 2002 12:12 PM
To: megaco@ietf.org
Subject: [Megaco] error handling


I was thinking about error handling and looked at RFC 3015 for some text to 
see if there are any MUST's or SHOULD's for how to handle invalid messages 
or parameters. I see Section 7.3, but I don't see any text which mandates 
the use.

Is this an oversight? Is this being considered for V2?


_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan 15 07:53:50 2002
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 HAA20707
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 07:53:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA03809
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 07:53:52 -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 HAA03725;
	Tue, 15 Jan 2002 07:45:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03698
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 07:45:24 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20443
	for <megaco@ietf.org>; Tue, 15 Jan 2002 07:45:20 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0FCjLJ14587
	for <megaco@ietf.org>; Tue, 15 Jan 2002 13:45:21 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Jan 15 13:45:12 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKRFJY>; Tue, 15 Jan 2002 13:45:11 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB43@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling
Date: Tue, 15 Jan 2002 13:44:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

You shold have a look at H.248 Annex L. You find a copy at:

ftp://standards.nortelnetworks.com/megaco/docs/Approved/

/MP
-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Tuesday, January 15, 2002 12:12 PM
To: megaco@ietf.org
Subject: [Megaco] error handling


I was thinking about error handling and looked at RFC 3015 for some text to 
see if there are any MUST's or SHOULD's for how to handle invalid messages 
or parameters. I see Section 7.3, but I don't see any text which mandates 
the use.

Is this an oversight? Is this being considered for V2?


_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 15 08:25:02 2002
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 IAA21690
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 08:25:02 -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 IAA04544;
	Tue, 15 Jan 2002 08:17:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04514
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 08:17:28 -0500 (EST)
Received: from smtp005pub.verizon.net (smtp005pub.verizon.net [206.46.170.184])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21374
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:17:22 -0500 (EST)
Received: from matt.verizon.net ([212.234.161.3])
	by smtp005pub.verizon.net  with ESMTP
	; id g0FDHJR00297
	Tue, 15 Jan 2002 07:17:19 -0600 (CST)
Message-Id: <5.1.0.14.2.20020115051220.02883ec0@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 15 Jan 2002 05:17:07 -0800
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: [Megaco] error handling
Cc: megaco@ietf.org
In-Reply-To: <5E5172B4DE05D311B3AB0008C75DA9410938AB43@edeacnt100.eed.er
 icsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Annex L doesn't have any text which describes what MUST be sent if a MEGACO 
endpoint detects an error. I'm thinking about text which says something 
like "if you receive an unknown command or parameter you MUST respond with 
such and such"

At 04:44 AM 1/15/2002, Marcello Pantaleo (EED) wrote:
>You shold have a look at H.248 Annex L. You find a copy at:
>
>ftp://standards.nortelnetworks.com/megaco/docs/Approved/
>
>/MP
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Tuesday, January 15, 2002 12:12 PM
>To: megaco@ietf.org
>Subject: [Megaco] error handling
>
>
>I was thinking about error handling and looked at RFC 3015 for some text to
>see if there are any MUST's or SHOULD's for how to handle invalid messages
>or parameters. I see Section 7.3, but I don't see any text which mandates
>the use.
>
>Is this an oversight? Is this being considered for V2?
>
>
>_______________________________________________
>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


From daemon@optimus.ietf.org  Tue Jan 15 08:25:03 2002
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 IAA21699
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 08:25:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA04702
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 08:25:05 -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 IAA04544;
	Tue, 15 Jan 2002 08:17:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04514
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 08:17:28 -0500 (EST)
Received: from smtp005pub.verizon.net (smtp005pub.verizon.net [206.46.170.184])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21374
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:17:22 -0500 (EST)
Received: from matt.verizon.net ([212.234.161.3])
	by smtp005pub.verizon.net  with ESMTP
	; id g0FDHJR00297
	Tue, 15 Jan 2002 07:17:19 -0600 (CST)
Message-Id: <5.1.0.14.2.20020115051220.02883ec0@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 15 Jan 2002 05:17:07 -0800
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: [Megaco] error handling
Cc: megaco@ietf.org
In-Reply-To: <5E5172B4DE05D311B3AB0008C75DA9410938AB43@edeacnt100.eed.er
 icsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Annex L doesn't have any text which describes what MUST be sent if a MEGACO 
endpoint detects an error. I'm thinking about text which says something 
like "if you receive an unknown command or parameter you MUST respond with 
such and such"

At 04:44 AM 1/15/2002, Marcello Pantaleo (EED) wrote:
>You shold have a look at H.248 Annex L. You find a copy at:
>
>ftp://standards.nortelnetworks.com/megaco/docs/Approved/
>
>/MP
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Tuesday, January 15, 2002 12:12 PM
>To: megaco@ietf.org
>Subject: [Megaco] error handling
>
>
>I was thinking about error handling and looked at RFC 3015 for some text to
>see if there are any MUST's or SHOULD's for how to handle invalid messages
>or parameters. I see Section 7.3, but I don't see any text which mandates
>the use.
>
>Is this an oversight? Is this being considered for V2?
>
>
>_______________________________________________
>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



From megaco-admin@ietf.org  Tue Jan 15 08:46:46 2002
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 IAA23046
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 08:46:46 -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 IAA05212;
	Tue, 15 Jan 2002 08:33:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA05179
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 08:33:22 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22233
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:33:17 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0FDXIK17474
	for <megaco@ietf.org>; Tue, 15 Jan 2002 14:33:18 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Tue Jan 15 14:33:17 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKRHRT>; Tue, 15 Jan 2002 14:33:17 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB44@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling
Date: Tue, 15 Jan 2002 14:32:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I don't think you will find such a thing and I don't think
this is an oversight.
Annex L defines all the possible error that it's possible to
have. Looking at the description you may infer what error is needed
in a specific situation.
Nontheless in the H.248 core specification in many cases (not 
all the possible cases)it is explicitely stated which error code 
it should be used in a particular situation. I imagine that also
in the procedure section of a package it is possible to specify
which error code to use but at the moment I can't remember any 
examples.

/MP

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Tuesday, January 15, 2002 2:17 PM
To: Marcello Pantaleo (EED)
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling


Annex L doesn't have any text which describes what MUST be sent if a MEGACO 
endpoint detects an error. I'm thinking about text which says something 
like "if you receive an unknown command or parameter you MUST respond with 
such and such"

At 04:44 AM 1/15/2002, Marcello Pantaleo (EED) wrote:
>You shold have a look at H.248 Annex L. You find a copy at:
>
>ftp://standards.nortelnetworks.com/megaco/docs/Approved/
>
>/MP
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Tuesday, January 15, 2002 12:12 PM
>To: megaco@ietf.org
>Subject: [Megaco] error handling
>
>
>I was thinking about error handling and looked at RFC 3015 for some text to
>see if there are any MUST's or SHOULD's for how to handle invalid messages
>or parameters. I see Section 7.3, but I don't see any text which mandates
>the use.
>
>Is this an oversight? Is this being considered for V2?
>
>
>_______________________________________________
>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


From daemon@optimus.ietf.org  Tue Jan 15 08:46:47 2002
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 IAA23057
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 08:46:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA05583
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 08:46:49 -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 IAA05212;
	Tue, 15 Jan 2002 08:33:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA05179
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 08:33:22 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22233
	for <megaco@ietf.org>; Tue, 15 Jan 2002 08:33:17 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0FDXIK17474
	for <megaco@ietf.org>; Tue, 15 Jan 2002 14:33:18 +0100 (MET)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt461 ; Tue Jan 15 14:33:17 2002 +0100
Received: by ESEALNT743.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKKRHRT>; Tue, 15 Jan 2002 14:33:17 +0100
Message-ID: <5E5172B4DE05D311B3AB0008C75DA9410938AB44@edeacnt100.eed.ericsson.se>
From: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling
Date: Tue, 15 Jan 2002 14:32:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I don't think you will find such a thing and I don't think
this is an oversight.
Annex L defines all the possible error that it's possible to
have. Looking at the description you may infer what error is needed
in a specific situation.
Nontheless in the H.248 core specification in many cases (not 
all the possible cases)it is explicitely stated which error code 
it should be used in a particular situation. I imagine that also
in the procedure section of a package it is possible to specify
which error code to use but at the moment I can't remember any 
examples.

/MP

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Tuesday, January 15, 2002 2:17 PM
To: Marcello Pantaleo (EED)
Cc: megaco@ietf.org
Subject: RE: [Megaco] error handling


Annex L doesn't have any text which describes what MUST be sent if a MEGACO 
endpoint detects an error. I'm thinking about text which says something 
like "if you receive an unknown command or parameter you MUST respond with 
such and such"

At 04:44 AM 1/15/2002, Marcello Pantaleo (EED) wrote:
>You shold have a look at H.248 Annex L. You find a copy at:
>
>ftp://standards.nortelnetworks.com/megaco/docs/Approved/
>
>/MP
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Tuesday, January 15, 2002 12:12 PM
>To: megaco@ietf.org
>Subject: [Megaco] error handling
>
>
>I was thinking about error handling and looked at RFC 3015 for some text to
>see if there are any MUST's or SHOULD's for how to handle invalid messages
>or parameters. I see Section 7.3, but I don't see any text which mandates
>the use.
>
>Is this an oversight? Is this being considered for V2?
>
>
>_______________________________________________
>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



From megaco-admin@ietf.org  Tue Jan 15 09:17:26 2002
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 JAA24121
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 09:17:26 -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 JAA06590;
	Tue, 15 Jan 2002 09:03:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06561
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 09:03:33 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23742
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:03:29 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001693593@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 19:48:15 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0FE2ro15952;
	Tue, 15 Jan 2002 19:32:53 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 19:32:33 +0530
Message-Id: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error descriptor when timed out
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: 7bit

Hi,

What Error will be reported by MG when MGC hasn't responded (for the request
sent
by MG itself) within the Execution Timer interval i.e., on a transaction
time-out.
Please mail me the supported Error Number for the above scenario.

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Tue Jan 15 09:17:27 2002
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 JAA24130
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 09:17:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06881
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 09:17:30 -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 JAA06590;
	Tue, 15 Jan 2002 09:03:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06561
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 09:03:33 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23742
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:03:29 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001693593@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 15 Jan 2002 19:48:15 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0FE2ro15952;
	Tue, 15 Jan 2002 19:32:53 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Tue, 15 Jan 2002 19:32:33 +0530
Message-Id: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error descriptor when timed out
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: 7bit

Hi,

What Error will be reported by MG when MGC hasn't responded (for the request
sent
by MG itself) within the Execution Timer interval i.e., on a transaction
time-out.
Please mail me the supported Error Number for the above scenario.

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Tue Jan 15 10:01:30 2002
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 KAA25983
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 10:01:30 -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 JAA08659;
	Tue, 15 Jan 2002 09:48:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08596
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 09:48:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25327
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:48:02 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FEhKl19935;
	Tue, 15 Jan 2002 09:43:21 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FEhId06227;
	Tue, 15 Jan 2002 09:43:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZT04Q>; Tue, 15 Jan 2002 09:43:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE45@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] different versions of Packages
Date: Tue, 15 Jan 2002 09:43:34 -0500
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

To see if a second version exists for any of these packages, go to the IANA
registry at
http://www.iana.org/assignments/megaco-h248
This will also tell you where to find any associated documentation.



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Tuesday, January 15, 2002 2:01 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] different versions of Packages


Hi,

Can anybody mail me "where can I get different versions of Packages".

Is there any version 2 for Network, RTP, TDM Circuit and R2 packages.
If there was any version 2 for the above specified packages, please mail me
information about "where can I get those packages from Internet".

Thanks,
Sudhir


_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan 15 10:01:30 2002
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 KAA25990
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 10:01:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09636
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 10:01:31 -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 JAA08659;
	Tue, 15 Jan 2002 09:48:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08596
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 09:48:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25327
	for <megaco@ietf.org>; Tue, 15 Jan 2002 09:48:02 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FEhKl19935;
	Tue, 15 Jan 2002 09:43:21 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FEhId06227;
	Tue, 15 Jan 2002 09:43:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZT04Q>; Tue, 15 Jan 2002 09:43:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE45@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] different versions of Packages
Date: Tue, 15 Jan 2002 09:43:34 -0500
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

To see if a second version exists for any of these packages, go to the IANA
registry at
http://www.iana.org/assignments/megaco-h248
This will also tell you where to find any associated documentation.



-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Tuesday, January 15, 2002 2:01 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] different versions of Packages


Hi,

Can anybody mail me "where can I get different versions of Packages".

Is there any version 2 for Network, RTP, TDM Circuit and R2 packages.
If there was any version 2 for the above specified packages, please mail me
information about "where can I get those packages from Internet".

Thanks,
Sudhir


_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 15 10:25:45 2002
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 KAA28886
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 10:25:41 -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 KAA09870;
	Tue, 15 Jan 2002 10:10:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09839
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 10:10:44 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28279
	for <megaco@ietf.org>; Tue, 15 Jan 2002 10:10:38 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0FF9Vn28631
	for <megaco@ietf.org>; Tue, 15 Jan 2002 20:39:32 +0530 (IST)
Received: from wipro.com ([192.168.178.139]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GPZJGP01.QCY; Tue, 15 Jan 2002 20:40:01 +0530 
Message-ID: <3C444623.197DF19B@wipro.com>
Date: Tue, 15 Jan 2002 20:39:23 +0530
From: "Shashi Kumar" <shashi.kumar@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sudhirk@future.futsoft.com
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Error descriptor when timed out
References: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8"
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sudhir,

if all the retransmission attempts(typically 7 to 11) have failed to get
a response from MGC, *one* of the recovery action from MG might be, to
contact the secondary MGC( out of the scope of protocol ) with Service
Change command, with appropriate Service Change Reason ( probably '907
Transmission Failure' )...

Thanks,
Shashi



Sudhir Kumar Appana wrote:
> 
> Hi,
> 
> What Error will be reported by MG when MGC hasn't responded (for the request
> sent
> by MG itself) within the Execution Timer interval i.e., on a transaction
> time-out.
> Please mail me the supported Error Number for the above scenario.
> 
> Thanks,
> Sudhir
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8--

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


From daemon@optimus.ietf.org  Tue Jan 15 10:25:46 2002
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 KAA28895
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 10:25:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10217
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 10:25:47 -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 KAA09870;
	Tue, 15 Jan 2002 10:10:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09839
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 10:10:44 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28279
	for <megaco@ietf.org>; Tue, 15 Jan 2002 10:10:38 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0FF9Vn28631
	for <megaco@ietf.org>; Tue, 15 Jan 2002 20:39:32 +0530 (IST)
Received: from wipro.com ([192.168.178.139]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GPZJGP01.QCY; Tue, 15 Jan 2002 20:40:01 +0530 
Message-ID: <3C444623.197DF19B@wipro.com>
Date: Tue, 15 Jan 2002 20:39:23 +0530
From: "Shashi Kumar" <shashi.kumar@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sudhirk@future.futsoft.com
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Error descriptor when timed out
References: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8"
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sudhir,

if all the retransmission attempts(typically 7 to 11) have failed to get
a response from MGC, *one* of the recovery action from MG might be, to
contact the secondary MGC( out of the scope of protocol ) with Service
Change command, with appropriate Service Change Reason ( probably '907
Transmission Failure' )...

Thanks,
Shashi



Sudhir Kumar Appana wrote:
> 
> Hi,
> 
> What Error will be reported by MG when MGC hasn't responded (for the request
> sent
> by MG itself) within the Execution Timer interval i.e., on a transaction
> time-out.
> Please mail me the supported Error Number for the above scenario.
> 
> Thanks,
> Sudhir
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-f11df154-09c3-11d6-a941-00b0d0d06be8--

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



From megaco-admin@ietf.org  Tue Jan 15 13:00:27 2002
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 NAA07294
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 13:00:23 -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 MAA15229;
	Tue, 15 Jan 2002 12:38:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15199
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 12:38:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06530
	for <megaco@ietf.org>; Tue, 15 Jan 2002 12:38:29 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FHc1l23600;
	Tue, 15 Jan 2002 12:38:01 -0500 (EST)
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 g0FHbxD00322;
	Tue, 15 Jan 2002 12:38:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ4FFM>; Tue, 15 Jan 2002 12:37:58 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE47@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>, megaco@ietf.org
Subject: RE: [Megaco] LCN mapping
Date: Tue, 15 Jan 2002 12:37:55 -0500
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

The short answer is that the relationship between LCN (Logical Channel
Number) and streamID is set by the application control, which probably
resides in the MGC.  Assuming your H.223 mux is operating as part of the
H.324 system it was designed for, the control information is carried in
H.245 signalling, gets routed to the MGC, and results in H.248 requests back
to the MG.

However, let me first address your proposed multiplexing structure.  I
should mention that several of us (Christian Groves, Roni Even, Marcello
Pantaleo and myself) are nearing the end of a discussion initiated by
Christian, on additional words to add around the multiplex concept,
clarifying it and at the same time allowing it to be used to represent Nx64K
wideband service.  I will report the results and reasoning to the list
shortly.  In any event, the basic multiplex concept I have been defending
(based on what we already have in RFC 3015/H.248)is something that
specifically has one or more circuits on one side and appears as an ordinary
termination to the rest of the context on the other.  Along the way, it
hides the circuits (which are represented by terminationIDs of their own)
from the rest of the context.

In your present example, you have the multiplexing termination (T3), 30 or
24 circuits which support it (the circuits in the E1/T1), and the RTP
termination T2.  If you are running H.324, the recommended way to tie the
circuits together is to use H.226 channel aggregation (set up with V.140
signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
(Annex F) but not in H.223, I suspect we have to model the two layers of
multiplexing explicitly.  This blows holes in my idea that all multiplexes
are supported directly by circuits.  In diagramatic terms, we have the
following situation:

                        Context interior ---->
                    _________                 _________
       Data stream  | H.226 |                 | H.223 |   Audio stream
Ckt 1 ..............| "MUX" |                 |  MUX  | .................
       . . .        | term  |   Data stream   | term  |
       Data stream  |       | ................|       |   Video stream
Ckt n ..............|       |                 |       | .................
                    |       |                 |       |
                    ---------                 ---------

Here the H.226 MUX termination contains/is supported by the individual
circuits, which appear as terminations in their own right.  The H.223 MUX
termination contains/is supported by the H.226 MUX termination.

The model I have been arguing for is that a multiplexing termination hides
all of the terminations it contains from the rest of the context.  One
implication of this is that the streamIDs of the streams flowing between the
contained terminations and the multiplexing termination are local rather
than global in scope.

Looking at the above diagram, people may ask how we know that the stream
between the H.226 and H.223 multiplexing terminations is a data stream,
while the streams passing from the H.223 termination to the rest of the
context are audio and video.  I will maintain that this is a result of the
definition of the respective multiplexes.  If this is not clear, we need an
explicit description of the exterior-side and context-side streams supported
by each multiplex somewhere within our Megaco/H.248 documentation.

I come to my final point.  Your example included the RTP termination T2
within the multiplex.  In my view this is a mistake: T2 is just another
termination in the context.  All it sees is T3, the H.223 multiplexing
termination, and it exchanges audio and video with that termination.

I hope this makes things clearer.  The question has raised some points which
I will now have to reflect back into my conversation with Christian and all.
Even better if they bring that conversation to this list.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Tuesday, January 15, 2002 2:28 AM
To: megaco@ietf.org
Subject: [Megaco] LCN mapping



Hi,

I have a question related to H.223 multiplexing.

Assume that I have one E1/T1 termination (T1) and one RTP termination
(T2). The RTP termination has two streams, one for audio and one for
video (I could also have separate terminations for each RTP stream).

Then I also add a multiplexing termination (T3), and in the
MuxDescriptor I define that T1 and T2 shall be multiplexed.

My question is: how do I define that a specific H.223 LCN is multiplexed
into a specific H.248 stream? Can I assume that this will be done if I
use the same value for the StreamId and the specific LCN that stream
shall be mapped into?

Regards,

Christer Holmberg
Ericsson Finland

_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan 15 13:00:28 2002
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 NAA07304
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 13:00:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA15935
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 13:00:29 -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 MAA15229;
	Tue, 15 Jan 2002 12:38:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15199
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 12:38:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06530
	for <megaco@ietf.org>; Tue, 15 Jan 2002 12:38:29 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0FHc1l23600;
	Tue, 15 Jan 2002 12:38:01 -0500 (EST)
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 g0FHbxD00322;
	Tue, 15 Jan 2002 12:38:00 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ4FFM>; Tue, 15 Jan 2002 12:37:58 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE47@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>, megaco@ietf.org
Subject: RE: [Megaco] LCN mapping
Date: Tue, 15 Jan 2002 12:37:55 -0500
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

The short answer is that the relationship between LCN (Logical Channel
Number) and streamID is set by the application control, which probably
resides in the MGC.  Assuming your H.223 mux is operating as part of the
H.324 system it was designed for, the control information is carried in
H.245 signalling, gets routed to the MGC, and results in H.248 requests back
to the MG.

However, let me first address your proposed multiplexing structure.  I
should mention that several of us (Christian Groves, Roni Even, Marcello
Pantaleo and myself) are nearing the end of a discussion initiated by
Christian, on additional words to add around the multiplex concept,
clarifying it and at the same time allowing it to be used to represent Nx64K
wideband service.  I will report the results and reasoning to the list
shortly.  In any event, the basic multiplex concept I have been defending
(based on what we already have in RFC 3015/H.248)is something that
specifically has one or more circuits on one side and appears as an ordinary
termination to the rest of the context on the other.  Along the way, it
hides the circuits (which are represented by terminationIDs of their own)
from the rest of the context.

In your present example, you have the multiplexing termination (T3), 30 or
24 circuits which support it (the circuits in the E1/T1), and the RTP
termination T2.  If you are running H.324, the recommended way to tie the
circuits together is to use H.226 channel aggregation (set up with V.140
signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
(Annex F) but not in H.223, I suspect we have to model the two layers of
multiplexing explicitly.  This blows holes in my idea that all multiplexes
are supported directly by circuits.  In diagramatic terms, we have the
following situation:

                        Context interior ---->
                    _________                 _________
       Data stream  | H.226 |                 | H.223 |   Audio stream
Ckt 1 ..............| "MUX" |                 |  MUX  | .................
       . . .        | term  |   Data stream   | term  |
       Data stream  |       | ................|       |   Video stream
Ckt n ..............|       |                 |       | .................
                    |       |                 |       |
                    ---------                 ---------

Here the H.226 MUX termination contains/is supported by the individual
circuits, which appear as terminations in their own right.  The H.223 MUX
termination contains/is supported by the H.226 MUX termination.

The model I have been arguing for is that a multiplexing termination hides
all of the terminations it contains from the rest of the context.  One
implication of this is that the streamIDs of the streams flowing between the
contained terminations and the multiplexing termination are local rather
than global in scope.

Looking at the above diagram, people may ask how we know that the stream
between the H.226 and H.223 multiplexing terminations is a data stream,
while the streams passing from the H.223 termination to the rest of the
context are audio and video.  I will maintain that this is a result of the
definition of the respective multiplexes.  If this is not clear, we need an
explicit description of the exterior-side and context-side streams supported
by each multiplex somewhere within our Megaco/H.248 documentation.

I come to my final point.  Your example included the RTP termination T2
within the multiplex.  In my view this is a mistake: T2 is just another
termination in the context.  All it sees is T3, the H.223 multiplexing
termination, and it exchanges audio and video with that termination.

I hope this makes things clearer.  The question has raised some points which
I will now have to reflect back into my conversation with Christian and all.
Even better if they bring that conversation to this list.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Tuesday, January 15, 2002 2:28 AM
To: megaco@ietf.org
Subject: [Megaco] LCN mapping



Hi,

I have a question related to H.223 multiplexing.

Assume that I have one E1/T1 termination (T1) and one RTP termination
(T2). The RTP termination has two streams, one for audio and one for
video (I could also have separate terminations for each RTP stream).

Then I also add a multiplexing termination (T3), and in the
MuxDescriptor I define that T1 and T2 shall be multiplexed.

My question is: how do I define that a specific H.223 LCN is multiplexed
into a specific H.248 stream? Can I assume that this will be done if I
use the same value for the StreamId and the specific LCN that stream
shall be mapped into?

Regards,

Christer Holmberg
Ericsson Finland

_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 15 22:52:57 2002
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 WAA21128
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 22:52:57 -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 WAA05497;
	Tue, 15 Jan 2002 22:41:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA05464
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 22:41:27 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21053
	for <megaco@ietf.org>; Tue, 15 Jan 2002 22:41:23 -0500 (EST)
Received: (qmail 23491 invoked by uid 510); 16 Jan 2002 03:42:09 -0000
Date: 16 Jan 2002 03:42:09 -0000
Message-ID: <20020116034209.23490.qmail@mailFA9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 03:42:09 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id WAA05466
Subject: [Megaco] need help
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


Hi all

   Is there any reaymade algorithm available for matching dialed digits with the dial plan. Since such activities are common in all telecom applications, I don't think we need to reinvent the wheel again ..

sree 


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


From daemon@optimus.ietf.org  Tue Jan 15 22:52:58 2002
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 WAA21138
	for <megaco-archive@odin.ietf.org>; Tue, 15 Jan 2002 22:52:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA05747
	for megaco-archive@odin.ietf.org; Tue, 15 Jan 2002 22:53:01 -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 WAA05497;
	Tue, 15 Jan 2002 22:41:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA05464
	for <megaco@optimus.ietf.org>; Tue, 15 Jan 2002 22:41:27 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21053
	for <megaco@ietf.org>; Tue, 15 Jan 2002 22:41:23 -0500 (EST)
Received: (qmail 23491 invoked by uid 510); 16 Jan 2002 03:42:09 -0000
Date: 16 Jan 2002 03:42:09 -0000
Message-ID: <20020116034209.23490.qmail@mailFA9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 03:42:09 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id WAA05466
Subject: [Megaco] need help
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


Hi all

   Is there any reaymade algorithm available for matching dialed digits with the dial plan. Since such activities are common in all telecom applications, I don't think we need to reinvent the wheel again ..

sree 


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



From megaco-admin@ietf.org  Wed Jan 16 08:45:00 2002
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 IAA06843
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:45:00 -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 IAA00328;
	Wed, 16 Jan 2002 08:27:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22358
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 03:54:48 -0500 (EST)
Received: from mailweb18.rediffmail.com ([203.199.83.142])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02906
	for <megaco@ietf.org>; Wed, 16 Jan 2002 03:54:44 -0500 (EST)
Received: (qmail 2363 invoked by uid 510); 16 Jan 2002 08:55:22 -0000
Date: 16 Jan 2002 08:55:22 -0000
Message-ID: <20020116085522.2362.qmail@mailweb18.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 08:55:22 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA22359
Subject: [Megaco] help
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


hi

    I like to get some sequence diagram kind of document which depicts some of the possible transaction between MGC - MG / MG - MGC. In RFC the example given doesn't tell all the details of the transaction for establishing a call I feel. Can any one help me out for this.

sree. 



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


From daemon@optimus.ietf.org  Wed Jan 16 08:45:01 2002
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 IAA06857
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:45:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA01088
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 08:45:04 -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 IAA00328;
	Wed, 16 Jan 2002 08:27:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22358
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 03:54:48 -0500 (EST)
Received: from mailweb18.rediffmail.com ([203.199.83.142])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02906
	for <megaco@ietf.org>; Wed, 16 Jan 2002 03:54:44 -0500 (EST)
Received: (qmail 2363 invoked by uid 510); 16 Jan 2002 08:55:22 -0000
Date: 16 Jan 2002 08:55:22 -0000
Message-ID: <20020116085522.2362.qmail@mailweb18.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 08:55:22 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA22359
Subject: [Megaco] help
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


hi

    I like to get some sequence diagram kind of document which depicts some of the possible transaction between MGC - MG / MG - MGC. In RFC the example given doesn't tell all the details of the transaction for establishing a call I feel. Can any one help me out for this.

sree. 



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



From megaco-admin@ietf.org  Wed Jan 16 08:45:03 2002
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 IAA06870
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:45:02 -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 IAA00293;
	Wed, 16 Jan 2002 08:27:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22168
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 03:48:15 -0500 (EST)
Received: from mailweb33.rediffmail.com ([203.199.83.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02841
	for <megaco@ietf.org>; Wed, 16 Jan 2002 03:48:12 -0500 (EST)
Received: (qmail 908 invoked by uid 510); 16 Jan 2002 08:47:51 -0000
Date: 16 Jan 2002 08:47:51 -0000
Message-ID: <20020116084751.907.qmail@mailweb33.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 08:47:51 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA22169
Subject: [Megaco] help
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


hi

  If MGC sends service change message with handsoff, the default behaviour in MG is to register with new MGC of which ID is given by the former MGC. Now while registering with new MGC, which all information should MG give to new MGC. Whether MGC will be updating the new MGC with all activities with MG or he is totally new to the MG scenario.. ?

sree. 



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


From daemon@optimus.ietf.org  Wed Jan 16 08:45:03 2002
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 IAA06880
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:45:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA01102
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 08:45:06 -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 IAA00293;
	Wed, 16 Jan 2002 08:27:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22168
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 03:48:15 -0500 (EST)
Received: from mailweb33.rediffmail.com ([203.199.83.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02841
	for <megaco@ietf.org>; Wed, 16 Jan 2002 03:48:12 -0500 (EST)
Received: (qmail 908 invoked by uid 510); 16 Jan 2002 08:47:51 -0000
Date: 16 Jan 2002 08:47:51 -0000
Message-ID: <20020116084751.907.qmail@mailweb33.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 16 Jan 2002 08:47:51 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA22169
Subject: [Megaco] help
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


hi

  If MGC sends service change message with handsoff, the default behaviour in MG is to register with new MGC of which ID is given by the former MGC. Now while registering with new MGC, which all information should MG give to new MGC. Whether MGC will be updating the new MGC with all activities with MG or he is totally new to the MG scenario.. ?

sree. 



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



From megaco-admin@ietf.org  Wed Jan 16 08:54:05 2002
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 IAA07118
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:54:04 -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 IAA01016;
	Wed, 16 Jan 2002 08:41:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA00987
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 08:41:09 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06745
	for <megaco@ietf.org>; Wed, 16 Jan 2002 08:41:05 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0GDepu03613
	for <megaco@ietf.org>; Wed, 16 Jan 2002 15:40:51 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T587c5e21b9ac158f25077@esvir05nok.ntc.nokia.com>;
 Wed, 16 Jan 2002 15:41:05 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Wed, 16 Jan 2002 15:41:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Megaco] help
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 16 Jan 2002 15:41:04 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF3D0EA3@esebe004.NOE.Nokia.com>
Thread-Topic: [Megaco] help
Thread-Index: AcGekn+Or5VUKwqEEdar0gAIx6S5QwAANEkA
From: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, <megaco@ietf.org>
X-OriginalArrivalTime: 16 Jan 2002 13:41:05.0450 (UTC) FILETIME=[7215D8A0:01C19E93]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA00988
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

Try reading the doc Megaco/H.248 Call flow examples at 
http://search.ietf.org/internet-drafts/draft-madhu-megaco-callflows-00.t
xt

sunesh

		-----Original Message-----
		From:	ext sree  gk [mailto:sgk73@rediffmail.com]
		Sent:	16. January 2002 10:55
		To:	megaco@ietf.org
		Subject:	[Megaco] help


		hi

		    I like to get some sequence diagram kind of document
which depicts some of the possible transaction between MGC - MG / MG -
MGC. In RFC the example given doesn't tell all the details of the
transaction for establishing a call I feel. Can any one help me out for
this.

		sree. 



		_______________________________________________
		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


From daemon@optimus.ietf.org  Wed Jan 16 08:54:05 2002
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 IAA07129
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 08:54:05 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA01334
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 08:54:09 -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 IAA01016;
	Wed, 16 Jan 2002 08:41:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA00987
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 08:41:09 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06745
	for <megaco@ietf.org>; Wed, 16 Jan 2002 08:41:05 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0GDepu03613
	for <megaco@ietf.org>; Wed, 16 Jan 2002 15:40:51 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T587c5e21b9ac158f25077@esvir05nok.ntc.nokia.com>;
 Wed, 16 Jan 2002 15:41:05 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Wed, 16 Jan 2002 15:41:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Megaco] help
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 16 Jan 2002 15:41:04 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF3D0EA3@esebe004.NOE.Nokia.com>
Thread-Topic: [Megaco] help
Thread-Index: AcGekn+Or5VUKwqEEdar0gAIx6S5QwAANEkA
From: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, <megaco@ietf.org>
X-OriginalArrivalTime: 16 Jan 2002 13:41:05.0450 (UTC) FILETIME=[7215D8A0:01C19E93]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA00988
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

Try reading the doc Megaco/H.248 Call flow examples at 
http://search.ietf.org/internet-drafts/draft-madhu-megaco-callflows-00.t
xt

sunesh

		-----Original Message-----
		From:	ext sree  gk [mailto:sgk73@rediffmail.com]
		Sent:	16. January 2002 10:55
		To:	megaco@ietf.org
		Subject:	[Megaco] help


		hi

		    I like to get some sequence diagram kind of document
which depicts some of the possible transaction between MGC - MG / MG -
MGC. In RFC the example given doesn't tell all the details of the
transaction for establishing a call I feel. Can any one help me out for
this.

		sree. 



		_______________________________________________
		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



From megaco-admin@ietf.org  Wed Jan 16 09:07:36 2002
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 JAA07653
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 09:07:35 -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 IAA01408;
	Wed, 16 Jan 2002 08:56:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01377
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 08:56:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07193
	for <megaco@ietf.org>; Wed, 16 Jan 2002 08:56:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GDuHp24399;
	Wed, 16 Jan 2002 08:56:17 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GDuFT18332;
	Wed, 16 Jan 2002 08:56:15 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ4TJC>; Wed, 16 Jan 2002 08:56:16 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE58@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] help
Date: Wed, 16 Jan 2002 08:56:16 -0500
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

Have a look at draft-madhu-megaco-callflows-00.txt.



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Wednesday, January 16, 2002 3:55 AM
To: megaco@ietf.org
Subject: [Megaco] help



hi

    I like to get some sequence diagram kind of document which depicts some
of the possible transaction between MGC - MG / MG - MGC. In RFC the example
given doesn't tell all the details of the transaction for establishing a
call I feel. Can any one help me out for this.

sree. 



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 16 09:07:36 2002
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 JAA07662
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 09:07:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA01997
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 09:07:40 -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 IAA01408;
	Wed, 16 Jan 2002 08:56:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01377
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 08:56:51 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07193
	for <megaco@ietf.org>; Wed, 16 Jan 2002 08:56:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GDuHp24399;
	Wed, 16 Jan 2002 08:56:17 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GDuFT18332;
	Wed, 16 Jan 2002 08:56:15 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ4TJC>; Wed, 16 Jan 2002 08:56:16 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE58@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] help
Date: Wed, 16 Jan 2002 08:56:16 -0500
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

Have a look at draft-madhu-megaco-callflows-00.txt.



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Wednesday, January 16, 2002 3:55 AM
To: megaco@ietf.org
Subject: [Megaco] help



hi

    I like to get some sequence diagram kind of document which depicts some
of the possible transaction between MGC - MG / MG - MGC. In RFC the example
given doesn't tell all the details of the transaction for establishing a
call I feel. Can any one help me out for this.

sree. 



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 16 11:31:13 2002
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 LAA13207
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 11:31:13 -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 LAA07504;
	Wed, 16 Jan 2002 11:21:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07474
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 11:21:23 -0500 (EST)
Received: from genius.empirix.com (genius.empirix.com [12.38.211.104])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12910
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:21:19 -0500 (EST)
Received: from kappa.midnight.com (fw-att [12.38.211.98])
	by genius.empirix.com (Postfix) with ESMTP id 41CB8110908
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:11:24 -0500 (EST)
Received: by kappa.empirix.com with Internet Mail Service (5.5.2653.19)
	id <YHBK11XC>; Wed, 16 Jan 2002 11:19:32 -0500
Message-ID: <5CB426A04E141C499676B19B6CF3DE5726354C@kappa.empirix.com>
From: "Rabindranath, Das" <drabindranath@empirix.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 16 Jan 2002 11:19:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Latest Documents
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

Hi 
 I would like to know the internet links of the latest documents(RFCs &
Drafts) on MGCP.

--Rabin.

Rabindranath  Das
p| 978-661-1292
email | drabindranath@empirix.com 
205 Lowell Street | Wilmington, MA | 01887
E M P I R I X
www.empirix.com


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


From megaco-admin@ietf.org  Wed Jan 16 11:49:44 2002
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 LAA13763
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 11:49:44 -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 LAA08302;
	Wed, 16 Jan 2002 11:30:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08276
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 11:30:53 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13189
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:30:49 -0500 (EST)
Received: from Bala (icepak3 [172.16.137.54] (may be forged))
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g0GGV3T20382
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:31:03 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Wed, 16 Jan 2002 11:30:51 -0500
Message-ID: <000b01c19eab$2c9234a0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <5CB426A04E141C499676B19B6CF3DE5726354C@kappa.empirix.com>
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Megaco Questions
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: 7bit

Hi All,

I am a newbie to the group.

I have a few questions about implementation of Megaco on the MG side.

1. Is it a mandatory requirement of Megaco for the MG to support "IP
Multicasting"?
2. Can the MGs by-pass the MGC to make a direct call to another
endpoint?
3. Can the MGCs impose restrictions on MGs to support all the packages
that are supported by themselves?
4. What is the latest status of the Megaco MIB? I saw the latest draft
(draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
official word on when would it be RFC-ed?

Thanks in advance for your replies.

Regards
Bala
________________________
Bala Pitchandi
UTStarcom Inc.



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


From daemon@optimus.ietf.org  Wed Jan 16 11:49:45 2002
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 LAA13772
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 11:49:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08906
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 11:49:48 -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 LAA08302;
	Wed, 16 Jan 2002 11:30:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08276
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 11:30:53 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13189
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:30:49 -0500 (EST)
Received: from Bala (icepak3 [172.16.137.54] (may be forged))
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g0GGV3T20382
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:31:03 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Wed, 16 Jan 2002 11:30:51 -0500
Message-ID: <000b01c19eab$2c9234a0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <5CB426A04E141C499676B19B6CF3DE5726354C@kappa.empirix.com>
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Megaco Questions
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: 7bit

Hi All,

I am a newbie to the group.

I have a few questions about implementation of Megaco on the MG side.

1. Is it a mandatory requirement of Megaco for the MG to support "IP
Multicasting"?
2. Can the MGs by-pass the MGC to make a direct call to another
endpoint?
3. Can the MGCs impose restrictions on MGs to support all the packages
that are supported by themselves?
4. What is the latest status of the Megaco MIB? I saw the latest draft
(draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
official word on when would it be RFC-ed?

Thanks in advance for your replies.

Regards
Bala
________________________
Bala Pitchandi
UTStarcom Inc.



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



From daemon@optimus.ietf.org  Wed Jan 16 12:29:49 2002
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 LAA13214
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 11:31:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08386
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 11:31:16 -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 LAA07504;
	Wed, 16 Jan 2002 11:21:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07474
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 11:21:23 -0500 (EST)
Received: from genius.empirix.com (genius.empirix.com [12.38.211.104])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12910
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:21:19 -0500 (EST)
Received: from kappa.midnight.com (fw-att [12.38.211.98])
	by genius.empirix.com (Postfix) with ESMTP id 41CB8110908
	for <megaco@ietf.org>; Wed, 16 Jan 2002 11:11:24 -0500 (EST)
Received: by kappa.empirix.com with Internet Mail Service (5.5.2653.19)
	id <YHBK11XC>; Wed, 16 Jan 2002 11:19:32 -0500
Message-ID: <5CB426A04E141C499676B19B6CF3DE5726354C@kappa.empirix.com>
From: "Rabindranath, Das" <drabindranath@empirix.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 16 Jan 2002 11:19:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Latest Documents
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

Hi 
 I would like to know the internet links of the latest documents(RFCs &
Drafts) on MGCP.

--Rabin.

Rabindranath  Das
p| 978-661-1292
email | drabindranath@empirix.com 
205 Lowell Street | Wilmington, MA | 01887
E M P I R I X
www.empirix.com


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



From megaco-admin@ietf.org  Wed Jan 16 13:25:03 2002
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 NAA16693
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:25:02 -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 NAA13177;
	Wed, 16 Jan 2002 13:15:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13147
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 13:15:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16370
	for <megaco@ietf.org>; Wed, 16 Jan 2002 13:15:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIEor27727;
	Wed, 16 Jan 2002 13:14:50 -0500 (EST)
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 g0GIEmm16407;
	Wed, 16 Jan 2002 13:14:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVFRF>; Wed, 16 Jan 2002 13:14:48 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE59@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rabindranath, Das'" <drabindranath@empirix.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Latest Documents
Date: Wed, 16 Jan 2002 13:14:48 -0500
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

Please send MGCP queries to MGCP@pulver.com.

-----Original Message-----
From: Rabindranath, Das [mailto:drabindranath@empirix.com]
Sent: Wednesday, January 16, 2002 11:20 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Latest Documents


Hi 
 I would like to know the internet links of the latest documents(RFCs &
Drafts) on MGCP.

--Rabin.

Rabindranath  Das
p| 978-661-1292
email | drabindranath@empirix.com 
205 Lowell Street | Wilmington, MA | 01887
E M P I R I X
www.empirix.com


_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 16 13:25:03 2002
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 NAA16701
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:25:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA13605
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 13:25:05 -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 NAA13177;
	Wed, 16 Jan 2002 13:15:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13147
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 13:15:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16370
	for <megaco@ietf.org>; Wed, 16 Jan 2002 13:15:20 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIEor27727;
	Wed, 16 Jan 2002 13:14:50 -0500 (EST)
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 g0GIEmm16407;
	Wed, 16 Jan 2002 13:14:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVFRF>; Wed, 16 Jan 2002 13:14:48 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE59@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rabindranath, Das'" <drabindranath@empirix.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Latest Documents
Date: Wed, 16 Jan 2002 13:14:48 -0500
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

Please send MGCP queries to MGCP@pulver.com.

-----Original Message-----
From: Rabindranath, Das [mailto:drabindranath@empirix.com]
Sent: Wednesday, January 16, 2002 11:20 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Latest Documents


Hi 
 I would like to know the internet links of the latest documents(RFCs &
Drafts) on MGCP.

--Rabin.

Rabindranath  Das
p| 978-661-1292
email | drabindranath@empirix.com 
205 Lowell Street | Wilmington, MA | 01887
E M P I R I X
www.empirix.com


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 16 13:32:02 2002
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 NAA16961
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:31: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 NAA13441;
	Wed, 16 Jan 2002 13:20:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13412
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 13:20:09 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16551
	for <megaco@ietf.org>; Wed, 16 Jan 2002 13:20:06 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIJZr28491;
	Wed, 16 Jan 2002 13:19:35 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIJXT20203;
	Wed, 16 Jan 2002 13:19:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVFWF>; Wed, 16 Jan 2002 13:19:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE5A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Questions
Date: Wed, 16 Jan 2002 13:19:13 -0500
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

Hi and welcome.  Answers below.



-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Wednesday, January 16, 2002 11:31 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco Questions


Hi All,

I am a newbie to the group.

I have a few questions about implementation of Megaco on the MG side.

1. Is it a mandatory requirement of Megaco for the MG to support "IP
Multicasting"?
[PTT] Megaco doesn't say anything about required media transports.

2. Can the MGs by-pass the MGC to make a direct call to another
endpoint?
[PTT] Not within the Megaco architecture.  Of course, that is a functional
architecture for the purpose of defining a protocol: how you choose to build
a product could be different.

3. Can the MGCs impose restrictions on MGs to support all the packages
that are supported by themselves?
[PTT] Yes.  The MGC can refuse the control association if it sees inadequate
package support from the MG.

4. What is the latest status of the Megaco MIB? I saw the latest draft
(draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
official word on when would it be RFC-ed?
[PTT]  I want to push ahead with it and have the WG finish it within a month
or so -- as soon as we get H.248v2 out the door.

Thanks in advance for your replies.

Regards
Bala
________________________
Bala Pitchandi
UTStarcom Inc.



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 16 13:32:04 2002
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 NAA16979
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:32:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14225
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 13:32:05 -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 NAA13441;
	Wed, 16 Jan 2002 13:20:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13412
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 13:20:09 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16551
	for <megaco@ietf.org>; Wed, 16 Jan 2002 13:20:06 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIJZr28491;
	Wed, 16 Jan 2002 13:19:35 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0GIJXT20203;
	Wed, 16 Jan 2002 13:19:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVFWF>; Wed, 16 Jan 2002 13:19:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE5A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Questions
Date: Wed, 16 Jan 2002 13:19:13 -0500
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

Hi and welcome.  Answers below.



-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Wednesday, January 16, 2002 11:31 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco Questions


Hi All,

I am a newbie to the group.

I have a few questions about implementation of Megaco on the MG side.

1. Is it a mandatory requirement of Megaco for the MG to support "IP
Multicasting"?
[PTT] Megaco doesn't say anything about required media transports.

2. Can the MGs by-pass the MGC to make a direct call to another
endpoint?
[PTT] Not within the Megaco architecture.  Of course, that is a functional
architecture for the purpose of defining a protocol: how you choose to build
a product could be different.

3. Can the MGCs impose restrictions on MGs to support all the packages
that are supported by themselves?
[PTT] Yes.  The MGC can refuse the control association if it sees inadequate
package support from the MG.

4. What is the latest status of the Megaco MIB? I saw the latest draft
(draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
official word on when would it be RFC-ed?
[PTT]  I want to push ahead with it and have the WG finish it within a month
or so -- as soon as we get H.248v2 out the door.

Thanks in advance for your replies.

Regards
Bala
________________________
Bala Pitchandi
UTStarcom Inc.



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 16 16:34:05 2002
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 QAA21398
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 16:34:05 -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 QAA19938;
	Wed, 16 Jan 2002 16:20:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19912
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 16:20:31 -0500 (EST)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21173
	for <megaco@ietf.org>; Wed, 16 Jan 2002 16:20:23 -0500 (EST)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GQ100401V93VU@firewall.wcom.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:51 +0000 (GMT)
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GQ10040LV92V2@firewall.wcom.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:51 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (PMDF V5.2-33 #42259) with SMTP id <0GQ100A01V8Q8W@pmismtp02.wcomnet.com> for
 megaco@ietf.org; Wed, 16 Jan 2002 21:19:50 +0000 (GMT)
Received: from ws678v1154 ([166.34.97.169])
 by pmismtp02.wcomnet.com (PMDF V5.2-33 #42259)
 with SMTP id <0GQ1004N1V8MIK@pmismtp02.wcomnet.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:35 +0000 (GMT)
Date: Wed, 16 Jan 2002 15:26:14 -0600
From: Mike Huang <Mike.Huang@wcom.com>
To: megaco@ietf.org
Reply-to: Mike.Huang@wcom.com
Message-id: <NEBBLDAODEBDIGMKKOCGOEJIDAAA.Mike.Huang@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: multipart/mixed; boundary="Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-MS-TNEF-Correlator: <NEBBLDAODEBDIGMKKOCGOEJIDAAA.Mike.Huang@wcom.com>
Subject: [Megaco] Service Change Question
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

This is a multi-part message in MIME format.

--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike 


--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)
Content-type: application/ms-tnef; name=winmail.dat
Content-disposition: attachment; filename=winmail.dat
Content-Transfer-Encoding: base64

eJ8+Ig4VAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANIHAQAQAA8AGgAAAAMAFgEB
A5AGAIAFAAAiAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAGAAAAFNlcnZpY2UgQ2hhbmdlIFF1ZXN0aW9uAAIBcQABAAAAFgAAAAHBntRqjGgBbMZ1mEun
updHq+2VpaUAAAIBHQwBAAAAGQAAAFNNVFA6TUlLRS5IVUFOR0BXQ09NLkNPTQAAAAALAAEOAAAA
AEAABg4AZIhk1J7BAQIBCg4BAAAAGAAAAAAAAAA0cwoB8CTUEbMOAGCMy14CwoAAAAsAHw4BAAAA
AgEJEAEAAACaAQAAlgEAAEUCAABMWkZ1kYGUUQMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQE
ZAIAY2gKwHPwZXQwIAhVB7ICgwBQVwPVBxMCgH0KgXYIkHfSawuAZDQMYGMAUAsDoQu1IEhlbAkA
LAqiQwqECoBJIHdhBCB35wIgBIELgGcgAhAFwAZhMRPAY2VDEQAPIGUsiCBkbweRdGhlBdDoR0Mg
EQB2GTAZEgGgUQMQaXR5GQBvGhBzdmsZBReDYRfMFqAaYGh5G7FzcAWQBpAN4BfMUoZlFsACIC4g
IEYFsXBleGFtC1AYkQaQIN8WkB+AG7EZUgBwZBahAjDnGpILgBpgYXQaARvfHOHDCXAesiA5MDEa
khsV3QlwZwsRH7AEEW8gABnj+GN0dQdAHSAhwyVlGVDpGKBzaAhgbCDwGxUHQL8JAAfgGRAEABqS
EQBwHUC9A6BlGbADoBkQCGBnHPDfGmAf4AQgBaACMHIKwBqDEyWfJWVzeSZAZW0/ZRXaVBhRa3MV
ySDwTfxpaxkwEmIumAKyFeMTgQIAMUAAAAsAAYAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAA
AwACgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAALAAWACCAGAAAAAADAAAAAAAAARgAAAAAD
hQAAAAAAAAMACYAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAMgAggBgAAAAAAwAAAAAAA
AEYAAAAAAYUAAAAAAAADAB2ACCAGAAAAAADAAAAAAAAARgAAAABShQAAtnQBAB4AHoAIIAYAAAAA
AMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAALAB+ACCAGAAAAAADAAAAAAAAARgAAAAAGhQAA
AAAAAAMAJIAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwA9gAggBgAAAAAAwAAAAAAAAEYA
AAAAgoUAAAEAAAACAfgPAQAAABAAAAA0cwoB8CTUEbMOAGCMy14CAgH6DwEAAAAQAAAANHMKAfAk
1BGzDgBgjMteAgIB+w8BAAAAjAAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAA
AAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcbWlrZWh1YW5n
XEFwcGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcb3V0bG9vay5wc3QAAwD+DwUAAAAD
AA00/TcAAAIBfwABAAAAMwAAADxORUJCTERBT0RFQkRJR01LS09DR09FSklEQUFBLk1pa2UuSHVh
bmdAd2NvbS5jb20+AAADAAYQ0XIE0wMABxA4AQAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAA
AEhFTExPLElXQVNXT05ERVJJTkdGT1JTRVJWSUNFQ0hBTkdFLERPRVNUSEVNR0NIQVZFVEhFQUJJ
TElUWVRPQVNLVEhFTUdGT1JBU0VSVklDRUNIQU5HRVdJVEhBU1BFQ0lGSUMAAAAAbi8=

--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)--

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


From daemon@optimus.ietf.org  Wed Jan 16 16:34:10 2002
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 QAA21407
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 16:34:05 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA20559
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 16:34:10 -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 QAA19938;
	Wed, 16 Jan 2002 16:20:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19912
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 16:20:31 -0500 (EST)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21173
	for <megaco@ietf.org>; Wed, 16 Jan 2002 16:20:23 -0500 (EST)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GQ100401V93VU@firewall.wcom.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:51 +0000 (GMT)
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GQ10040LV92V2@firewall.wcom.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:51 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (PMDF V5.2-33 #42259) with SMTP id <0GQ100A01V8Q8W@pmismtp02.wcomnet.com> for
 megaco@ietf.org; Wed, 16 Jan 2002 21:19:50 +0000 (GMT)
Received: from ws678v1154 ([166.34.97.169])
 by pmismtp02.wcomnet.com (PMDF V5.2-33 #42259)
 with SMTP id <0GQ1004N1V8MIK@pmismtp02.wcomnet.com> for megaco@ietf.org; Wed,
 16 Jan 2002 21:19:35 +0000 (GMT)
Date: Wed, 16 Jan 2002 15:26:14 -0600
From: Mike Huang <Mike.Huang@wcom.com>
To: megaco@ietf.org
Reply-to: Mike.Huang@wcom.com
Message-id: <NEBBLDAODEBDIGMKKOCGOEJIDAAA.Mike.Huang@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: multipart/mixed; boundary="Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-MS-TNEF-Correlator: <NEBBLDAODEBDIGMKKOCGOEJIDAAA.Mike.Huang@wcom.com>
Subject: [Megaco] Service Change Question
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

This is a multi-part message in MIME format.

--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike 


--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)
Content-type: application/ms-tnef; name=winmail.dat
Content-disposition: attachment; filename=winmail.dat
Content-Transfer-Encoding: base64

eJ8+Ig4VAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANIHAQAQAA8AGgAAAAMAFgEB
A5AGAIAFAAAiAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAGAAAAFNlcnZpY2UgQ2hhbmdlIFF1ZXN0aW9uAAIBcQABAAAAFgAAAAHBntRqjGgBbMZ1mEun
updHq+2VpaUAAAIBHQwBAAAAGQAAAFNNVFA6TUlLRS5IVUFOR0BXQ09NLkNPTQAAAAALAAEOAAAA
AEAABg4AZIhk1J7BAQIBCg4BAAAAGAAAAAAAAAA0cwoB8CTUEbMOAGCMy14CwoAAAAsAHw4BAAAA
AgEJEAEAAACaAQAAlgEAAEUCAABMWkZ1kYGUUQMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQE
ZAIAY2gKwHPwZXQwIAhVB7ICgwBQVwPVBxMCgH0KgXYIkHfSawuAZDQMYGMAUAsDoQu1IEhlbAkA
LAqiQwqECoBJIHdhBCB35wIgBIELgGcgAhAFwAZhMRPAY2VDEQAPIGUsiCBkbweRdGhlBdDoR0Mg
EQB2GTAZEgGgUQMQaXR5GQBvGhBzdmsZBReDYRfMFqAaYGh5G7FzcAWQBpAN4BfMUoZlFsACIC4g
IEYFsXBleGFtC1AYkQaQIN8WkB+AG7EZUgBwZBahAjDnGpILgBpgYXQaARvfHOHDCXAesiA5MDEa
khsV3QlwZwsRH7AEEW8gABnj+GN0dQdAHSAhwyVlGVDpGKBzaAhgbCDwGxUHQL8JAAfgGRAEABqS
EQBwHUC9A6BlGbADoBkQCGBnHPDfGmAf4AQgBaACMHIKwBqDEyWfJWVzeSZAZW0/ZRXaVBhRa3MV
ySDwTfxpaxkwEmIumAKyFeMTgQIAMUAAAAsAAYAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAA
AwACgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAALAAWACCAGAAAAAADAAAAAAAAARgAAAAAD
hQAAAAAAAAMACYAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAMgAggBgAAAAAAwAAAAAAA
AEYAAAAAAYUAAAAAAAADAB2ACCAGAAAAAADAAAAAAAAARgAAAABShQAAtnQBAB4AHoAIIAYAAAAA
AMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAALAB+ACCAGAAAAAADAAAAAAAAARgAAAAAGhQAA
AAAAAAMAJIAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwA9gAggBgAAAAAAwAAAAAAAAEYA
AAAAgoUAAAEAAAACAfgPAQAAABAAAAA0cwoB8CTUEbMOAGCMy14CAgH6DwEAAAAQAAAANHMKAfAk
1BGzDgBgjMteAgIB+w8BAAAAjAAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAA
AAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcbWlrZWh1YW5n
XEFwcGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcb3V0bG9vay5wc3QAAwD+DwUAAAAD
AA00/TcAAAIBfwABAAAAMwAAADxORUJCTERBT0RFQkRJR01LS09DR09FSklEQUFBLk1pa2UuSHVh
bmdAd2NvbS5jb20+AAADAAYQ0XIE0wMABxA4AQAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAA
AEhFTExPLElXQVNXT05ERVJJTkdGT1JTRVJWSUNFQ0hBTkdFLERPRVNUSEVNR0NIQVZFVEhFQUJJ
TElUWVRPQVNLVEhFTUdGT1JBU0VSVklDRUNIQU5HRVdJVEhBU1BFQ0lGSUMAAAAAbi8=

--Boundary_(ID_24CLdv28/Qatq+5YUpjVRw)--

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



From megaco-admin@ietf.org  Wed Jan 16 21:58:57 2002
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 VAA27048
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 21:58:57 -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 VAA29784;
	Wed, 16 Jan 2002 21:38:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29753
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 21:38:10 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26855
	for <megaco@ietf.org>; Wed, 16 Jan 2002 21:38:04 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA20128;
	Thu, 17 Jan 2002 13:36:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA17174;
	Thu, 17 Jan 2002 13:37:51 +1100 (EST)
Message-ID: <3C4639D2.9703DAA6@ericsson.com.au>
Date: Thu, 17 Jan 2002 13:41:22 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
CC: Terry Anderson <tla@lucent.com>, Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] IG Resolution on : g/sc SigID list
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

G'Day all,

Back in September there was some discussion on the encoding of g/sc
SigID. We sorted out the correct definition of sub-list but
unfortunately I believe that we didn't finish of the discussion on the
encoding of g/sc.

Below is a proposed resolution to start off the discussions. Flame away.

x.xx Signal List Completion Encoding

Description:	In the Signal completion event it is unclear how the signal
identity is encoded. Firstly the type: list is not a standard type
defined in the packages template. Secondly it is unclear how to encode
the value of the parameter. A simple solution is proposed to carry only
the signal identity of the completed signal in pkgdname format. If a
signal is part of a signal list it is indicated by the signal list
identity parameter.

Reference:	<to be filled in by editor>
 [Begin Correction]
E.1.2 Events
…
Signal Identity
ParameterID:  SigID (0x0001)
This parameter identifies the signals which have terminated.
Type: octet string
Possible values: a signal which has terminated.  A signal shall be
identified using the pkgdName syntax without wildcarding. For a signal
that is contained in a signal list the signal list identity parameter
should also be returned indicating the appropriate list. 

[End Correction]

Regards, Christian

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


From daemon@optimus.ietf.org  Wed Jan 16 21:58:58 2002
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 VAA27056
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 21:58:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA00249
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 21:59:01 -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 VAA29784;
	Wed, 16 Jan 2002 21:38:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29753
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 21:38:10 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26855
	for <megaco@ietf.org>; Wed, 16 Jan 2002 21:38:04 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA20128;
	Thu, 17 Jan 2002 13:36:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA17174;
	Thu, 17 Jan 2002 13:37:51 +1100 (EST)
Message-ID: <3C4639D2.9703DAA6@ericsson.com.au>
Date: Thu, 17 Jan 2002 13:41:22 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
CC: Terry Anderson <tla@lucent.com>, Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] IG Resolution on : g/sc SigID list
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

G'Day all,

Back in September there was some discussion on the encoding of g/sc
SigID. We sorted out the correct definition of sub-list but
unfortunately I believe that we didn't finish of the discussion on the
encoding of g/sc.

Below is a proposed resolution to start off the discussions. Flame away.

x.xx Signal List Completion Encoding

Description:	In the Signal completion event it is unclear how the signal
identity is encoded. Firstly the type: list is not a standard type
defined in the packages template. Secondly it is unclear how to encode
the value of the parameter. A simple solution is proposed to carry only
the signal identity of the completed signal in pkgdname format. If a
signal is part of a signal list it is indicated by the signal list
identity parameter.

Reference:	<to be filled in by editor>
 [Begin Correction]
E.1.2 Events
…
Signal Identity
ParameterID:  SigID (0x0001)
This parameter identifies the signals which have terminated.
Type: octet string
Possible values: a signal which has terminated.  A signal shall be
identified using the pkgdName syntax without wildcarding. For a signal
that is contained in a signal list the signal list identity parameter
should also be returned indicating the appropriate list. 

[End Correction]

Regards, Christian

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



From megaco-admin@ietf.org  Wed Jan 16 22:34:57 2002
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 WAA28480
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 22:34:52 -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 WAA01137;
	Wed, 16 Jan 2002 22:23:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01109
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:23:05 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27352
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:22:58 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3NBE01380;
	Thu, 17 Jan 2002 08:53:11 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0012774F ; Thu, 17 Jan 2002 08:51:41 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.0012638E.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 08:54:32 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 16 22:34:58 2002
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 WAA28490
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 22:34:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA01889
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 22:35:01 -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 WAA01137;
	Wed, 16 Jan 2002 22:23:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01109
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:23:05 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27352
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:22:58 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3NBE01380;
	Thu, 17 Jan 2002 08:53:11 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0012774F ; Thu, 17 Jan 2002 08:51:41 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.0012638E.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 08:54:32 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 16 22:36:54 2002
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 WAA28519
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 22:36:49 -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 WAA01289;
	Wed, 16 Jan 2002 22:29:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01258
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:29:17 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27446
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:29:10 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3TrE02026;
	Thu, 17 Jan 2002 08:59:53 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.001312B2 ; Thu, 17 Jan 2002 08:58:19 +0530
X-Lotus-FromDomain: HSS
To: "sree gk" <sgk73@rediffmail.com>
cc: megaco@ietf.org
Message-ID: <65256B44.00130CBC.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 09:01:44 +0530
Subject: Re: [Megaco] help
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Sree

While registering with the new MGC, the MG will send service change request with
Handoff method and service change reason as "MGC Directed Change".
The new MGC can find out more about the MG by two methods
1. It can audit the MG
2. The old MGC can update the new MGC. How it does this is outside the scope of
the protocol.

Regards
Vivek
Hughes software Systems






"sree gk" <sgk73@rediffmail.com> on 01/16/2002 02:17:51 PM

Please respond to "sree  gk" <sgk73@rediffmail.com>

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] help





hi

  If MGC sends service change message with handsoff, the default behaviour in MG
is to register with new MGC of which ID is given by the former MGC. Now while
registering with new MGC, which all information should MG give to new MGC.
Whether MGC will be updating the new MGC with all activities with MG or he is
totally new to the MG scenario.. ?

sree.



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 16 22:36:55 2002
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 WAA28529
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 22:36:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA01951
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 22:36: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 WAA01289;
	Wed, 16 Jan 2002 22:29:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01258
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:29:17 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27446
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:29:10 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3TrE02026;
	Thu, 17 Jan 2002 08:59:53 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.001312B2 ; Thu, 17 Jan 2002 08:58:19 +0530
X-Lotus-FromDomain: HSS
To: "sree gk" <sgk73@rediffmail.com>
cc: megaco@ietf.org
Message-ID: <65256B44.00130CBC.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 09:01:44 +0530
Subject: Re: [Megaco] help
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Sree

While registering with the new MGC, the MG will send service change request with
Handoff method and service change reason as "MGC Directed Change".
The new MGC can find out more about the MG by two methods
1. It can audit the MG
2. The old MGC can update the new MGC. How it does this is outside the scope of
the protocol.

Regards
Vivek
Hughes software Systems






"sree gk" <sgk73@rediffmail.com> on 01/16/2002 02:17:51 PM

Please respond to "sree  gk" <sgk73@rediffmail.com>

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] help





hi

  If MGC sends service change message with handsoff, the default behaviour in MG
is to register with new MGC of which ID is given by the former MGC. Now while
registering with new MGC, which all information should MG give to new MGC.
Whether MGC will be updating the new MGC with all activities with MG or he is
totally new to the MG scenario.. ?

sree.



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 16 23:13:56 2002
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 XAA29015
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 23:13:51 -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 WAA02256;
	Wed, 16 Jan 2002 22:48:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02225
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:48:21 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28816
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:48:15 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3mpE03869;
	Thu, 17 Jan 2002 09:18:52 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0014CF69 ; Thu, 17 Jan 2002 09:17:18 +0530
X-Lotus-FromDomain: HSS
To: Mike.Huang@wcom.com
cc: megaco@ietf.org
Message-ID: <65256B44.00148668.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 09:16:47 +0530
Subject: Re: [Megaco] Service Change Question
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF"
Content-Disposition: inline
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

--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




Hi

The MG should look into the service change reason sent in Service change request
from MGC to gauge the severity of change in the states of the calls currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike



--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF
Content-type: application/octet-stream; 
	name="winmail.dat"
Content-Disposition: attachment; filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+Ig4VAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANIHAQAQAA8AGgAAAAMAFgEB
A5AGAIAFAAAiAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAGAAAAFNlcnZpY2UgQ2hhbmdlIFF1ZXN0aW9uAAIBcQABAAAAFgAAAAHBntRqjGgBbMZ1mEun
updHq+2VpaUAAAIBHQwBAAAAGQAAAFNNVFA6TUlLRS5IVUFOR0BXQ09NLkNPTQAAAAALAAEOAAAA
AEAABg4AZIhk1J7BAQIBCg4BAAAAGAAAAAAAAAA0cwoB8CTUEbMOAGCMy14CwoAAAAsAHw4BAAAA
AgEJEAEAAACaAQAAlgEAAEUCAABMWkZ1kYGUUQMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQE
ZAIAY2gKwHPwZXQwIAhVB7ICgwBQVwPVBxMCgH0KgXYIkHfSawuAZDQMYGMAUAsDoQu1IEhlbAkA
LAqiQwqECoBJIHdhBCB35wIgBIELgGcgAhAFwAZhMRPAY2VDEQAPIGUsiCBkbweRdGhlBdDoR0Mg
EQB2GTAZEgGgUQMQaXR5GQBvGhBzdmsZBReDYRfMFqAaYGh5G7FzcAWQBpAN4BfMUoZlFsACIC4g
IEYFsXBleGFtC1AYkQaQIN8WkB+AG7EZUgBwZBahAjDnGpILgBpgYXQaARvfHOHDCXAesiA5MDEa
khsV3QlwZwsRH7AEEW8gABnj+GN0dQdAHSAhwyVlGVDpGKBzaAhgbCDwGxUHQL8JAAfgGRAEABqS
EQBwHUC9A6BlGbADoBkQCGBnHPDfGmAf4AQgBaACMHIKwBqDEyWfJWVzeSZAZW0/ZRXaVBhRa3MV
ySDwTfxpaxkwEmIumAKyFeMTgQIAMUAAAAsAAYAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAA
AwACgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAALAAWACCAGAAAAAADAAAAAAAAARgAAAAAD
hQAAAAAAAAMACYAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAMgAggBgAAAAAAwAAAAAAA
AEYAAAAAAYUAAAAAAAADAB2ACCAGAAAAAADAAAAAAAAARgAAAABShQAAtnQBAB4AHoAIIAYAAAAA
AMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAALAB+ACCAGAAAAAADAAAAAAAAARgAAAAAGhQAA
AAAAAAMAJIAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwA9gAggBgAAAAAAwAAAAAAAAEYA
AAAAgoUAAAEAAAACAfgPAQAAABAAAAA0cwoB8CTUEbMOAGCMy14CAgH6DwEAAAAQAAAANHMKAfAk
1BGzDgBgjMteAgIB+w8BAAAAjAAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAA
AAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcbWlrZWh1YW5n
XEFwcGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcb3V0bG9vay5wc3QAAwD+DwUAAAAD
AA00/TcAAAIBfwABAAAAMwAAADxORUJCTERBT0RFQkRJR01LS09DR09FSklEQUFBLk1pa2UuSHVh
bmdAd2NvbS5jb20+AAADAAYQ0XIE0wMABxA4AQAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAA
AEhFTExPLElXQVNXT05ERVJJTkdGT1JTRVJWSUNFQ0hBTkdFLERPRVNUSEVNR0NIQVZFVEhFQUJJ
TElUWVRPQVNLVEhFTUdGT1JBU0VSVklDRUNIQU5HRVdJVEhBU1BFQ0lGSUMAAAAAbi8=

--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF--


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


From daemon@optimus.ietf.org  Wed Jan 16 23:14:01 2002
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 XAA29025
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jan 2002 23:13:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA03197
	for megaco-archive@odin.ietf.org; Wed, 16 Jan 2002 23:14:01 -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 WAA02256;
	Wed, 16 Jan 2002 22:48:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02225
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 22:48:21 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28816
	for <megaco@ietf.org>; Wed, 16 Jan 2002 22:48:15 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H3mpE03869;
	Thu, 17 Jan 2002 09:18:52 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0014CF69 ; Thu, 17 Jan 2002 09:17:18 +0530
X-Lotus-FromDomain: HSS
To: Mike.Huang@wcom.com
cc: megaco@ietf.org
Message-ID: <65256B44.00148668.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 09:16:47 +0530
Subject: Re: [Megaco] Service Change Question
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF"
Content-Disposition: inline
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

--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




Hi

The MG should look into the service change reason sent in Service change request
from MGC to gauge the severity of change in the states of the calls currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike



--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF
Content-type: application/octet-stream; 
	name="winmail.dat"
Content-Disposition: attachment; filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+Ig4VAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANIHAQAQAA8AGgAAAAMAFgEB
A5AGAIAFAAAiAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAGAAAAFNlcnZpY2UgQ2hhbmdlIFF1ZXN0aW9uAAIBcQABAAAAFgAAAAHBntRqjGgBbMZ1mEun
updHq+2VpaUAAAIBHQwBAAAAGQAAAFNNVFA6TUlLRS5IVUFOR0BXQ09NLkNPTQAAAAALAAEOAAAA
AEAABg4AZIhk1J7BAQIBCg4BAAAAGAAAAAAAAAA0cwoB8CTUEbMOAGCMy14CwoAAAAsAHw4BAAAA
AgEJEAEAAACaAQAAlgEAAEUCAABMWkZ1kYGUUQMACgByY3BnMTI1FjIA+Atgbg4QMDMzTwH3AqQE
ZAIAY2gKwHPwZXQwIAhVB7ICgwBQVwPVBxMCgH0KgXYIkHfSawuAZDQMYGMAUAsDoQu1IEhlbAkA
LAqiQwqECoBJIHdhBCB35wIgBIELgGcgAhAFwAZhMRPAY2VDEQAPIGUsiCBkbweRdGhlBdDoR0Mg
EQB2GTAZEgGgUQMQaXR5GQBvGhBzdmsZBReDYRfMFqAaYGh5G7FzcAWQBpAN4BfMUoZlFsACIC4g
IEYFsXBleGFtC1AYkQaQIN8WkB+AG7EZUgBwZBahAjDnGpILgBpgYXQaARvfHOHDCXAesiA5MDEa
khsV3QlwZwsRH7AEEW8gABnj+GN0dQdAHSAhwyVlGVDpGKBzaAhgbCDwGxUHQL8JAAfgGRAEABqS
EQBwHUC9A6BlGbADoBkQCGBnHPDfGmAf4AQgBaACMHIKwBqDEyWfJWVzeSZAZW0/ZRXaVBhRa3MV
ySDwTfxpaxkwEmIumAKyFeMTgQIAMUAAAAsAAYAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAA
AwACgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAALAAWACCAGAAAAAADAAAAAAAAARgAAAAAD
hQAAAAAAAAMACYAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAMgAggBgAAAAAAwAAAAAAA
AEYAAAAAAYUAAAAAAAADAB2ACCAGAAAAAADAAAAAAAAARgAAAABShQAAtnQBAB4AHoAIIAYAAAAA
AMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAALAB+ACCAGAAAAAADAAAAAAAAARgAAAAAGhQAA
AAAAAAMAJIAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwA9gAggBgAAAAAAwAAAAAAAAEYA
AAAAgoUAAAEAAAACAfgPAQAAABAAAAA0cwoB8CTUEbMOAGCMy14CAgH6DwEAAAAQAAAANHMKAfAk
1BGzDgBgjMteAgIB+w8BAAAAjAAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAA
AAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XERvY3VtZW50cyBhbmQgU2V0dGluZ3NcbWlrZWh1YW5n
XEFwcGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcb3V0bG9vay5wc3QAAwD+DwUAAAAD
AA00/TcAAAIBfwABAAAAMwAAADxORUJCTERBT0RFQkRJR01LS09DR09FSklEQUFBLk1pa2UuSHVh
bmdAd2NvbS5jb20+AAADAAYQ0XIE0wMABxA4AQAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAA
AEhFTExPLElXQVNXT05ERVJJTkdGT1JTRVJWSUNFQ0hBTkdFLERPRVNUSEVNR0NIQVZFVEhFQUJJ
TElUWVRPQVNLVEhFTUdGT1JBU0VSVklDRUNIQU5HRVdJVEhBU1BFQ0lGSUMAAAAAbi8=

--0__=r0SA0u5hKt1JfJbkuJz4JKAgI85INUn4P9pTdER47ae7EEJbwuQ6a1oF--


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



From megaco-admin@ietf.org  Thu Jan 17 00:11:15 2002
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 AAA00064
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 00:11:10 -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 XAA04312;
	Wed, 16 Jan 2002 23:51:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04283
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 23:51:27 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29892
	for <megaco@ietf.org>; Wed, 16 Jan 2002 23:51:21 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id UAA02901;
	Wed, 16 Jan 2002 20:51:24 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 17 Jan 2002 04:51:24 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id UAA18634;
	Wed, 16 Jan 2002 20:51:23 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id UAA12752;
	Wed, 16 Jan 2002 20:51:20 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id KAA29374;
	Thu, 17 Jan 2002 10:20:23 +0530 (IST)
Message-ID: <3C46576D.4417B9EE@lucent.com>
Date: Thu, 17 Jan 2002 10:17:41 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: Re: [Megaco] Megaco Questions
References: <4D79C746863DD51197690002A52CDA000102AE5A@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Tom,

I am not clear on your comment to the third point.

3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees inadequate
> package support from the MG

I had a impression MGC should support all the packages but MG needs to support only the packages which are of its use. for example a
gateway not dealing with ATM need not support ATM packages. May be, Packages supported for a MG can be provisioned on the MGC, then
MGC may check  the packages supported on the MG.

If its mandatery to support all the packages, Do we make mandatery to send all the packages supported  from MG in the initial
Service Change message, If not How can MGC refuse the control associan at this stage ?

Please clarify.
-Shambhu

Tom-PT Taylor wrote:
> 
> Hi and welcome.  Answers below.
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
> Sent: Wednesday, January 16, 2002 11:31 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco Questions
> 
> Hi All,
> 
> I am a newbie to the group.
> 
> I have a few questions about implementation of Megaco on the MG side.
> 
> 1. Is it a mandatory requirement of Megaco for the MG to support "IP
> Multicasting"?
> [PTT] Megaco doesn't say anything about required media transports.
> 
> 2. Can the MGs by-pass the MGC to make a direct call to another
> endpoint?
> [PTT] Not within the Megaco architecture.  Of course, that is a functional
> architecture for the purpose of defining a protocol: how you choose to build
> a product could be different.
> 
> 3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees inadequate
> package support from the MG.
> 
> 4. What is the latest status of the Megaco MIB? I saw the latest draft
> (draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
> official word on when would it be RFC-ed?
> [PTT]  I want to push ahead with it and have the WG finish it within a month
> or so -- as soon as we get H.248v2 out the door.
> 
> Thanks in advance for your replies.
> 
> Regards
> Bala
> ________________________


-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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


From daemon@optimus.ietf.org  Thu Jan 17 00:11:15 2002
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 AAA00074
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 00:11:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA05123
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 00:11: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 XAA04312;
	Wed, 16 Jan 2002 23:51:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04283
	for <megaco@optimus.ietf.org>; Wed, 16 Jan 2002 23:51:27 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29892
	for <megaco@ietf.org>; Wed, 16 Jan 2002 23:51:21 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id UAA02901;
	Wed, 16 Jan 2002 20:51:24 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 17 Jan 2002 04:51:24 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id UAA18634;
	Wed, 16 Jan 2002 20:51:23 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id UAA12752;
	Wed, 16 Jan 2002 20:51:20 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id KAA29374;
	Thu, 17 Jan 2002 10:20:23 +0530 (IST)
Message-ID: <3C46576D.4417B9EE@lucent.com>
Date: Thu, 17 Jan 2002 10:17:41 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: Re: [Megaco] Megaco Questions
References: <4D79C746863DD51197690002A52CDA000102AE5A@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi Tom,

I am not clear on your comment to the third point.

3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees inadequate
> package support from the MG

I had a impression MGC should support all the packages but MG needs to support only the packages which are of its use. for example a
gateway not dealing with ATM need not support ATM packages. May be, Packages supported for a MG can be provisioned on the MGC, then
MGC may check  the packages supported on the MG.

If its mandatery to support all the packages, Do we make mandatery to send all the packages supported  from MG in the initial
Service Change message, If not How can MGC refuse the control associan at this stage ?

Please clarify.
-Shambhu

Tom-PT Taylor wrote:
> 
> Hi and welcome.  Answers below.
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
> Sent: Wednesday, January 16, 2002 11:31 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco Questions
> 
> Hi All,
> 
> I am a newbie to the group.
> 
> I have a few questions about implementation of Megaco on the MG side.
> 
> 1. Is it a mandatory requirement of Megaco for the MG to support "IP
> Multicasting"?
> [PTT] Megaco doesn't say anything about required media transports.
> 
> 2. Can the MGs by-pass the MGC to make a direct call to another
> endpoint?
> [PTT] Not within the Megaco architecture.  Of course, that is a functional
> architecture for the purpose of defining a protocol: how you choose to build
> a product could be different.
> 
> 3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees inadequate
> package support from the MG.
> 
> 4. What is the latest status of the Megaco MIB? I saw the latest draft
> (draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
> official word on when would it be RFC-ed?
> [PTT]  I want to push ahead with it and have the WG finish it within a month
> or so -- as soon as we get H.248v2 out the door.
> 
> Thanks in advance for your replies.
> 
> Regards
> Bala
> ________________________


-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Thu Jan 17 00:45:21 2002
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 AAA00380
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 00:45:21 -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 AAA06280;
	Thu, 17 Jan 2002 00:37:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA06253
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 00:37:56 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00328
	for <megaco@ietf.org>; Thu, 17 Jan 2002 00:37:53 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001705519@fsnt.future.futsoft.com>;
 Thu, 17 Jan 2002 11:22:33 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0H5bFo14447;
	Thu, 17 Jan 2002 11:07:16 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 17 Jan 2002 11:14:59 +0530
Message-Id: <001701c19f1a$1ac3f320$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA000102AE12@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

If the bandwidth required is equal to 2Mbps then the muxed term could
represent the whole span like Trnk1 where the Trnk1/c1...Trnk1/c32.

Add = Trnk1 {
	...
	Mux = H223 { Line1, Line2,...}
}

How to represent the case where the bandwidth required is n * 64Kbps, say
3 * 64Kbps.
How to represnt the egress terminals after muxing.
The input channels for the muxing relation could be specified in the mux
descriptor,
what about the output channels.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 10 January 2002 8:24 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


There is a potential application where the MuxedTerm represents a
higher-order facility (e.g. T1 or E1) and the multiplexing relationship
describes the channels that make it up.  The MuxedTerm would be defined only
for maintenance purposes, to monitor the status of the facility as a whole.
We haven't actually specified MUX types which would cover this.

The current specification views the MuxedTerm as an ephemeral typically
supporting multiple media streams.  Each stream gets its own SDP in Local
and Remote.  The MuxedTerm as a whole represents, for example, a complete
H.320 session.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 10, 2002 12:58 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 17 00:45:26 2002
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 AAA00389
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 00:45:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA06372
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 00:45:22 -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 AAA06280;
	Thu, 17 Jan 2002 00:37:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA06253
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 00:37:56 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00328
	for <megaco@ietf.org>; Thu, 17 Jan 2002 00:37:53 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001705519@fsnt.future.futsoft.com>;
 Thu, 17 Jan 2002 11:22:33 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0H5bFo14447;
	Thu, 17 Jan 2002 11:07:16 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Use of Modem descriptor
Date: Thu, 17 Jan 2002 11:14:59 +0530
Message-Id: <001701c19f1a$1ac3f320$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <4D79C746863DD51197690002A52CDA000102AE12@zcard0kc.ca.nortel.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,

If the bandwidth required is equal to 2Mbps then the muxed term could
represent the whole span like Trnk1 where the Trnk1/c1...Trnk1/c32.

Add = Trnk1 {
	...
	Mux = H223 { Line1, Line2,...}
}

How to represent the case where the bandwidth required is n * 64Kbps, say
3 * 64Kbps.
How to represnt the egress terminals after muxing.
The input channels for the muxing relation could be specified in the mux
descriptor,
what about the output channels.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, 10 January 2002 8:24 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


There is a potential application where the MuxedTerm represents a
higher-order facility (e.g. T1 or E1) and the multiplexing relationship
describes the channels that make it up.  The MuxedTerm would be defined only
for maintenance purposes, to monitor the status of the facility as a whole.
We haven't actually specified MUX types which would cover this.

The current specification views the MuxedTerm as an ephemeral typically
supporting multiple media streams.  Each stream gets its own SDP in Local
and Remote.  The MuxedTerm as a whole represents, for example, a complete
H.320 session.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Thursday, January 10, 2002 12:58 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] Use of Modem descriptor


Hi,

Can the MuxedTerm be a physical termination or should it always be
a ephemeral termination. If ephemeral then what kind of SDP parameters
would be required.

gokul


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Monday, 7 January 2002 8:29 PM
To: 'gokulc@future.futsoft.com'; megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: RE: [Megaco] Use of Modem descriptor


Sorry about the previous non-reply.  When trying for "File/Properties/Send
Options" to make sure the message goes out as text, I sometimes get
distracted by the "Send" button immediately below the File menu item.

Anyway, I assume you are talking about a situation where someone is running
an H.324 session over a modem connection -- this is the only example I can
think of that would require both descriptors.  There are a few other
assumptions one must make about how the MGC knows it's an H.324 call, but I
can visualize one or two scenarios where this might be so.  In any event,
the specification is straightforward:

Add=MuxedTerm{
  Modem=V.34,
  Mux=H.223 {LineTerm},
  etc.

Here MuxedTerm is the ephemeral termination being created to represent the
H.324 session, and LineTerm is the physical analogue line termination
supporting it.  The original H.324 specification is based on use of a V.34
modem.  I can't recall if that has been extended to V.90.  H.223 is the
H.324 multiplex.



-----Original Message-----
From: gokulc [mailto:gokulc@future.futsoft.com]
Sent: Monday, January 07, 2002 8:20 AM
To: megaco@ietf.org
Cc: madhubabu@kenetec.com
Subject: [Megaco] Use of Modem descriptor


Hi,

When a add/move/modify command with the modem descriptor is issued,
the MG connects the appropriate modem from the free resource pool to the
addressed termination in the command.

Add = Term1{
	Modem = V90
	....
}

It is my understanding that the Term1 is not the identification of the
modem, but
that of the line/trunk termination.

On the same lines how is a mux resource handled...

gokul


_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 17 03:27:22 2002
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 DAA10068
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:27:22 -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 CAA19254;
	Thu, 17 Jan 2002 02:55:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19163
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 02:55:29 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09819
	for <megaco@ietf.org>; Thu, 17 Jan 2002 02:55:25 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H7sHE01389;
	Thu, 17 Jan 2002 13:24:17 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.002B4498 ; Thu, 17 Jan 2002 13:22:36 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.001B2E39.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 10:30:29 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 17 03:27:27 2002
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 DAA10078
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:27:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA20594
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 03:27:24 -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 CAA19254;
	Thu, 17 Jan 2002 02:55:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19163
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 02:55:29 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09819
	for <megaco@ietf.org>; Thu, 17 Jan 2002 02:55:25 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0H7sHE01389;
	Thu, 17 Jan 2002 13:24:17 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.002B4498 ; Thu, 17 Jan 2002 13:22:36 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.001B2E39.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 10:30:29 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 17 03:30:46 2002
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 DAA10127
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:30:46 -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 CAA19321;
	Thu, 17 Jan 2002 02:56:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19287
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 02:56:42 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09833
	for <megaco@ietf.org>; Thu, 17 Jan 2002 02:56:38 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58804a4c9ac0722b3314c@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 17 Jan 2002 09:57:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Subject: [MEGACO] CNAME
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19F2C.59216622"
Date: Thu, 17 Jan 2002 09:55:36 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C051@lodmsg01.corp.audiocodes.com>
Thread-Topic: [MEGACO] CNAME
Thread-Index: AcGfLFkRzPz95ZMIQky2aCwlVzxSAQ==
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: "'Megaco_IETF (E-mail)" <megaco@ietf.org>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19F2C.59216622
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi

Do we have in the MEGACO a way to supply a CNAME from the MGC, or should th=
e MG define it itself? (e.g TerminationName)

Thanks, Nurit



***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the individual or entity to whom th=
ey are addressed.
If you have received this email in error please notify postmaster@audiocode=
s.com
and permanently delete the e-mail and files.
***************************************************************************=
********************************


------_=_NextPart_001_01C19F2C.59216622
Content-Type: text/html; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dwindows-1=
255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.0.5762.3">
<TITLE>[MEGACO] CNAME</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"ar-sa"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=
=3D"#000000" SIZE=3D2 FACE=3D"Arial">Hi</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"=
Arial">Do we have in the MEGACO a way to supply a CNAME from the MGC, or sh=
ould the MG define it itself?</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLO=
R=3D"#000000" SIZE=3D2 FACE=3D"Arial">(e.g TerminationName</FONT></SPAN><SP=
AN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">)</FONT><=
/SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"=
Arial">Thanks, Nurit</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<CODE><FONT SIZE=3D3><BR>
<BR>
***************************************************************************=
*********************************<BR>
This email and any files transmitted with it are confidential material.<BR>
They are intended solely for the use of the individual or entity to whom th=
ey are addressed.<BR>
If you have received this email in error please notify postmaster@audiocode=
s.com<BR>
and permanently delete the e-mail and files.<BR>
***************************************************************************=
********************************<BR>
</FONT></CODE>
</BODY>
</HTML>
------_=_NextPart_001_01C19F2C.59216622--

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


From daemon@optimus.ietf.org  Thu Jan 17 03:30:47 2002
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 DAA10135
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:30:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA20995
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 03:30:49 -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 CAA19321;
	Thu, 17 Jan 2002 02:56:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19287
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 02:56:42 -0500 (EST)
Received: from mail-sweeper.msw (mail.audiocodes.com [192.114.43.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09833
	for <megaco@ietf.org>; Thu, 17 Jan 2002 02:56:38 -0500 (EST)
Received: from lodmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58804a4c9ac0722b3314c@mail-sweeper.msw> for <megaco@ietf.org>;
 Thu, 17 Jan 2002 09:57:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Subject: [MEGACO] CNAME
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19F2C.59216622"
Date: Thu, 17 Jan 2002 09:55:36 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C051@lodmsg01.corp.audiocodes.com>
Thread-Topic: [MEGACO] CNAME
Thread-Index: AcGfLFkRzPz95ZMIQky2aCwlVzxSAQ==
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: "'Megaco_IETF (E-mail)" <megaco@ietf.org>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19F2C.59216622
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi

Do we have in the MEGACO a way to supply a CNAME from the MGC, or should th=
e MG define it itself? (e.g TerminationName)

Thanks, Nurit



***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the individual or entity to whom th=
ey are addressed.
If you have received this email in error please notify postmaster@audiocode=
s.com
and permanently delete the e-mail and files.
***************************************************************************=
********************************


------_=_NextPart_001_01C19F2C.59216622
Content-Type: text/html; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dwindows-1=
255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.0.5762.3">
<TITLE>[MEGACO] CNAME</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"ar-sa"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=
=3D"#000000" SIZE=3D2 FACE=3D"Arial">Hi</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"=
Arial">Do we have in the MEGACO a way to supply a CNAME from the MGC, or sh=
ould the MG define it itself?</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT COLO=
R=3D"#000000" SIZE=3D2 FACE=3D"Arial">(e.g TerminationName</FONT></SPAN><SP=
AN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">)</FONT><=
/SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"=
Arial">Thanks, Nurit</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<CODE><FONT SIZE=3D3><BR>
<BR>
***************************************************************************=
*********************************<BR>
This email and any files transmitted with it are confidential material.<BR>
They are intended solely for the use of the individual or entity to whom th=
ey are addressed.<BR>
If you have received this email in error please notify postmaster@audiocode=
s.com<BR>
and permanently delete the e-mail and files.<BR>
***************************************************************************=
********************************<BR>
</FONT></CODE>
</BODY>
</HTML>
------_=_NextPart_001_01C19F2C.59216622--

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



From megaco-admin@ietf.org  Thu Jan 17 03:40:56 2002
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 DAA10224
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:40:55 -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 DAA20537;
	Thu, 17 Jan 2002 03:24:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA20509
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 03:24:02 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10056
	for <megaco@ietf.org>; Thu, 17 Jan 2002 03:23:58 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001706725@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 17 Jan 2002 13:53:33 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0H88Go26136;
	Thu, 17 Jan 2002 13:38:16 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Thu, 17 Jan 2002 13:37:55 +0530
Message-Id: <002801c19f2e$127739c0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error Descriptor in a packet
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: 7bit

Hi,

I hope Error Descripor can come in the reply packet either
- after MID or
- after Transaction ID or
- after Context ID or
- in Notify reply if the request if Notify request or
- in Service Change reply if the request is Service Change request


I want to know one scenario when each of the above can occur so that I will
understand the
behaviour of MG in difference scenarios.

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Thu Jan 17 03:40:56 2002
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 DAA10234
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 03:40:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA21229
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 03:40: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 DAA20537;
	Thu, 17 Jan 2002 03:24:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA20509
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 03:24:02 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10056
	for <megaco@ietf.org>; Thu, 17 Jan 2002 03:23:58 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001706725@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 17 Jan 2002 13:53:33 +0530
Received: from sudhirk (sudhirk.future.futsoft.com [10.2.7.58])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0H88Go26136;
	Thu, 17 Jan 2002 13:38:16 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Date: Thu, 17 Jan 2002 13:37:55 +0530
Message-Id: <002801c19f2e$127739c0$3a07020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error Descriptor in a packet
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: 7bit

Hi,

I hope Error Descripor can come in the reply packet either
- after MID or
- after Transaction ID or
- after Context ID or
- in Notify reply if the request if Notify request or
- in Service Change reply if the request is Service Change request


I want to know one scenario when each of the above can occur so that I will
understand the
behaviour of MG in difference scenarios.

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Thu Jan 17 08:51:48 2002
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 IAA15193
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 08:51:44 -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 IAA02104;
	Thu, 17 Jan 2002 08:37:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02077
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 08:37:18 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14846
	for <megaco@ietf.org>; Thu, 17 Jan 2002 08:37:13 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0HDbGE04606;
	Thu, 17 Jan 2002 19:07:16 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.004AAA4E ; Thu, 17 Jan 2002 19:05:32 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.004A446D.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 19:04:52 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 17 08:51:49 2002
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 IAA15205
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 08:51:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA02331
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 08:51:52 -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 IAA02104;
	Thu, 17 Jan 2002 08:37:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02077
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 08:37:18 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14846
	for <megaco@ietf.org>; Thu, 17 Jan 2002 08:37:13 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0HDbGE04606;
	Thu, 17 Jan 2002 19:07:16 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.004AAA4E ; Thu, 17 Jan 2002 19:05:32 +0530
X-Lotus-FromDomain: HSS
To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
Message-ID: <65256B44.004A446D.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 19:04:52 +0530
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Marcello, All

Before actually phrasing the paragragh can we discuss this issue some more to
make it even clearer. We should remember that we need to handle the LONG timer
also. Here is the suggested behavior for the entity sending the Transaction
response containing immAckRequired field

1. The entity sending response with immAckRequired field will start
retransmission timers as per section D.1.5. It shall not start the long timer.

2.If the acknowledgement comes, the entity sending response will stop
retransmitting the response and start the long timer for the remaining duration.

3.If the acknowledgement does not come within N retries (or  time elapsed since
the sending of the initial datagram is no greater than T-MAX), then entity
sending response shall assume that the peer entity has gone down and would start
the recovery action as suggested in section 11.4/11.5 of rfc 3015. It shall stop
retransmitting the response and it start the long timer for that transaction
response for the remaining duration.

With this we have tried to avoid running two timers for the same transaction.

Regards
Vivek
Hughes Software Systems







"Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on 01/10/2002
09:06:48 PM

To:   Vivek Bansal/HSS@HSS
cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT Taylor
      <taylor@nortelnetworks.com>, megaco@ietf.org

Subject:  RE: [Megaco] Doubt regarding immAckRequired field.




Hi Vivek,

how does it sound this (addition between <SA> and <EA>?

H.248, Section D.1.4 Provisional response:
...
Upon receipt of a final response following receipt of provisional responses, an
immediate confirmation shall be sent, and normal repetition timers shall be used
thereafter.  An entity that sends a provisional response, SHALL include the
immAckRequired field in the ensuing final response, indicating that an immediate
confirmation is expected.
<SA>If an immediate confirmation is not received, the entity that sent the final
response will retransmit the final response including the immAckRequired field
(with exponential backoff) until a confirmation is received.<EA> Receipt of a
Transaction Pending after receipt of a reply shall be ignored.

If it sounds ok I guess this should be also added to the IG.

Regards,
Marcello

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Thursday, January 10, 2002 1:04 AM
To: vibansal@hss.hns.com
Cc: Tom-PT Taylor; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


G'Day Vivek,

I understood that its not mentioned what I was asking for was a wording
proposal to D.1.4 or whereever it is relevant to assist the IG and v2
editors.

Regards, Christian

vibansal@hss.hns.com wrote:
>
> Hi Christian
>
> Regarding the Immediate ACK nothing has been mentioned in the protocol. I had
> asked if the entity sending response sends the response with immAckRequired
> field, and the entity receiving the response does not send back ACK, then what
> should entity sending the response do. To handle this Tom had suggested that
the
> entity sending rerponse will retransmit the response till it gets the ACK of
it.
> And this solutions seems fine, otherwise the presence of immAckRequired field
in
> the message will not make any difference.
>
> This is all that I wanted to be updated in V2.
>
> Regards
> Vivek
>
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002 08:27:43 AM
>
> To:   Vivek Bansal/HSS@HSS
> cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
>
> Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
>
> G'Day Vivek,
>
> What exactly do you propose to update in v2?
>
> Regards, Christian
>
> vibansal@hss.hns.com wrote:
> >
> > If this is the case, then we need update the same in the v2 draft.
> >
> > Regards
> > Vivek
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> >
> > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > cc:
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> > The immAckRequired flag was introduced because without it a protocol glitch
> > was possible, so what you postulate is not a nice situation.  Anyway, to
> > answer your question, I would say that retransmission of the final response
> > (with exponential backoff) is necessary until an acknowledgement is
> > received.
> >
> > -----Original Message-----
> > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > Sent: Sunday, December 30, 2001 8:23 AM
> > To: megaco@ietf.org
> > Subject: [Megaco] Doubt regarding immAckRequired field.
> >
> > Hi
> >
> > I have a doubt regarding immAckRequired field.
> >
> > Section D.1.4 says
> >
> > "An entity that sends a provisional response, SHALL include the
> > immAckRequired
> > field in the ensuing final response, indicating that an immediate
> > confirmation
> > is expected."
> >
> > Now what would happen, if the entity receiving the final response with
> > immAckRequired field, does not send the immediate confirmation? In this case
> > do
> > we need to retransmit the response till we get the confirmation?
> >
> > Please clarify.
> >
> > Regards
> > Vivek
> >
> > _______________________________________________
> > 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



_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 17 09:28:41 2002
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 JAA16438
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 09:28:37 -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 JAA03402;
	Thu, 17 Jan 2002 09:17:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03371
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 09:17:35 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16113
	for <megaco@ietf.org>; Thu, 17 Jan 2002 09:17:31 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEH0b04247;
	Thu, 17 Jan 2002 09:17:01 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEGwG06703;
	Thu, 17 Jan 2002 09:16:58 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVSZD>; Thu, 17 Jan 2002 09:16:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE69@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shambhu Dayal Rai'" <sdrai@lucent.com>
Cc: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Questions
Date: Thu, 17 Jan 2002 09:17:03 -0500
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

You are right on the mechanism.  ServiceChange only indicates profile.  Thus
the MGC would have to audit before discontinuing the association.

As to the issue of what packages have to be supported, this is really an
issue of network configuration.  The MGC will have an idea of the services
it has been configured to provide, and the packages that enable those
services.  If the MG does not support those packages, there is a defect in
network configuration.  What the MGC does about that is a matter of local
policy.  I said it would discontinue the association, but I suppose other
responses are possible.  The first and most obvious action is to notify
network management that there is a problem.



-----Original Message-----
From: Shambhu Dayal Rai [mailto:sdrai@lucent.com]
Sent: Wednesday, January 16, 2002 11:48 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: Re: [Megaco] Megaco Questions


Hi Tom,

I am not clear on your comment to the third point.

3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees
inadequate
> package support from the MG

I had a impression MGC should support all the packages but MG needs to
support only the packages which are of its use. for example a
gateway not dealing with ATM need not support ATM packages. May be, Packages
supported for a MG can be provisioned on the MGC, then
MGC may check  the packages supported on the MG.

If its mandatery to support all the packages, Do we make mandatery to send
all the packages supported  from MG in the initial
Service Change message, If not How can MGC refuse the control associan at
this stage ?

Please clarify.
-Shambhu

Tom-PT Taylor wrote:
> 
> Hi and welcome.  Answers below.
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
> Sent: Wednesday, January 16, 2002 11:31 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco Questions
> 
> Hi All,
> 
> I am a newbie to the group.
> 
> I have a few questions about implementation of Megaco on the MG side.
> 
> 1. Is it a mandatory requirement of Megaco for the MG to support "IP
> Multicasting"?
> [PTT] Megaco doesn't say anything about required media transports.
> 
> 2. Can the MGs by-pass the MGC to make a direct call to another
> endpoint?
> [PTT] Not within the Megaco architecture.  Of course, that is a functional
> architecture for the purpose of defining a protocol: how you choose to
build
> a product could be different.
> 
> 3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees
inadequate
> package support from the MG.
> 
> 4. What is the latest status of the Megaco MIB? I saw the latest draft
> (draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
> official word on when would it be RFC-ed?
> [PTT]  I want to push ahead with it and have the WG finish it within a
month
> or so -- as soon as we get H.248v2 out the door.
> 
> Thanks in advance for your replies.
> 
> Regards
> Bala
> ________________________


-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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


From daemon@optimus.ietf.org  Thu Jan 17 09:28:42 2002
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 JAA16446
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 09:28:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA03703
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 09:28:45 -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 JAA03402;
	Thu, 17 Jan 2002 09:17:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03371
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 09:17:35 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16113
	for <megaco@ietf.org>; Thu, 17 Jan 2002 09:17:31 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEH0b04247;
	Thu, 17 Jan 2002 09:17:01 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEGwG06703;
	Thu, 17 Jan 2002 09:16:58 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVSZD>; Thu, 17 Jan 2002 09:16:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE69@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shambhu Dayal Rai'" <sdrai@lucent.com>
Cc: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco Questions
Date: Thu, 17 Jan 2002 09:17:03 -0500
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

You are right on the mechanism.  ServiceChange only indicates profile.  Thus
the MGC would have to audit before discontinuing the association.

As to the issue of what packages have to be supported, this is really an
issue of network configuration.  The MGC will have an idea of the services
it has been configured to provide, and the packages that enable those
services.  If the MG does not support those packages, there is a defect in
network configuration.  What the MGC does about that is a matter of local
policy.  I said it would discontinue the association, but I suppose other
responses are possible.  The first and most obvious action is to notify
network management that there is a problem.



-----Original Message-----
From: Shambhu Dayal Rai [mailto:sdrai@lucent.com]
Sent: Wednesday, January 16, 2002 11:48 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: Re: [Megaco] Megaco Questions


Hi Tom,

I am not clear on your comment to the third point.

3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees
inadequate
> package support from the MG

I had a impression MGC should support all the packages but MG needs to
support only the packages which are of its use. for example a
gateway not dealing with ATM need not support ATM packages. May be, Packages
supported for a MG can be provisioned on the MGC, then
MGC may check  the packages supported on the MG.

If its mandatery to support all the packages, Do we make mandatery to send
all the packages supported  from MG in the initial
Service Change message, If not How can MGC refuse the control associan at
this stage ?

Please clarify.
-Shambhu

Tom-PT Taylor wrote:
> 
> Hi and welcome.  Answers below.
> 
> -----Original Message-----
> From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
> Sent: Wednesday, January 16, 2002 11:31 AM
> To: megaco@ietf.org
> Subject: [Megaco] Megaco Questions
> 
> Hi All,
> 
> I am a newbie to the group.
> 
> I have a few questions about implementation of Megaco on the MG side.
> 
> 1. Is it a mandatory requirement of Megaco for the MG to support "IP
> Multicasting"?
> [PTT] Megaco doesn't say anything about required media transports.
> 
> 2. Can the MGs by-pass the MGC to make a direct call to another
> endpoint?
> [PTT] Not within the Megaco architecture.  Of course, that is a functional
> architecture for the purpose of defining a protocol: how you choose to
build
> a product could be different.
> 
> 3. Can the MGCs impose restrictions on MGs to support all the packages
> that are supported by themselves?
> [PTT] Yes.  The MGC can refuse the control association if it sees
inadequate
> package support from the MG.
> 
> 4. What is the latest status of the Megaco MIB? I saw the latest draft
> (draft-ietf-megaco-mib-02.txt) that was done in May 2001. Is there any
> official word on when would it be RFC-ed?
> [PTT]  I want to push ahead with it and have the WG finish it within a
month
> or so -- as soon as we get H.248v2 out the door.
> 
> Thanks in advance for your replies.
> 
> Regards
> Bala
> ________________________


-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Thu Jan 17 09:47:17 2002
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 JAA17349
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 09:47: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 JAA04421;
	Thu, 17 Jan 2002 09:39:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04395
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 09:39:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16790
	for <megaco@ietf.org>; Thu, 17 Jan 2002 09:39:21 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEcob16822;
	Thu, 17 Jan 2002 09:38:50 -0500 (EST)
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 g0HEcnG15455;
	Thu, 17 Jan 2002 09:38:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVTN5>; Thu, 17 Jan 2002 09:38:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE6A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Nurit Shenhar'" <NuritS@audiocodes.com>,
        "'Megaco_IETF (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [MEGACO] CNAME
Date: Thu, 17 Jan 2002 09:38:53 -0500
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

There is nothing in Megaco for this purpose.  If someone can make a good
case for it, they could add it in an extension of the RTP package.

-----Original Message-----
From: Nurit Shenhar [mailto:NuritS@audiocodes.com]
Sent: Thursday, January 17, 2002 2:56 AM
To: 'Megaco_IETF (E-mail)
Subject: [MEGACO] CNAME


Hi
Do we have in the MEGACO a way to supply a CNAME from the MGC, or should the
MG define it itself? (e.g TerminationName)
Thanks, Nurit


****************************************************************************
********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the individual or entity to whom
they are addressed.
If you have received this email in error please notify
postmaster@audiocodes.com
and permanently delete the e-mail and files.
****************************************************************************
*******************************

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


From megaco-admin@ietf.org  Thu Jan 17 10:16:13 2002
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 KAA18361
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:16:13 -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 KAA05469;
	Thu, 17 Jan 2002 10:04:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05433
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:04:54 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18005
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 10:04:52 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <Y6085ZKT>; Thu, 17 Jan 2002 10:04:22 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A4484048A2@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Megaco@ietf.org'" <Megaco@ietf.org>
Date: Thu, 17 Jan 2002 10:04:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] NotifyCompletion Question
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

For V1 the possible values of NotifyCompletion reason are:

notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
          notificationReason *(COMMA notificationReason) RBRKT) 
    
   notificationReason   = ( TimeOutToken / InterruptByEventToken 
               / InterruptByNewSignalsDescrToken 
               / OtherReasonToken ) 


So when an MGC wants the MG to notify a completion of a Signal
the MGC would specify:

NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
for)

Is this correct???

The reason I ask is later in the RFC there is this:
Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to "ON".  For further 
      procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 

Which seems to indicate that the NC really should be an ON or OFF value and
the 4 notificationReasons are really just return values.

Thanks,
Carl

Carl Rutter
Telica, Inc.
Building G, Suite 100
734 Forest Street
Marlboro, MA 01752
Email crutter@telica.com
Voice 508-480-0909 x8178
Fax 508-480-0922 
www.telica.com




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


From daemon@ns.ietf.org  Thu Jan 17 10:16:14 2002
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 KAA18371
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:16:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA05757
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 10:16:15 -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 KAA05469;
	Thu, 17 Jan 2002 10:04:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05433
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:04:54 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18005
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 10:04:52 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <Y6085ZKT>; Thu, 17 Jan 2002 10:04:22 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A4484048A2@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Megaco@ietf.org'" <Megaco@ietf.org>
Date: Thu, 17 Jan 2002 10:04:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] NotifyCompletion Question
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

For V1 the possible values of NotifyCompletion reason are:

notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
          notificationReason *(COMMA notificationReason) RBRKT) 
    
   notificationReason   = ( TimeOutToken / InterruptByEventToken 
               / InterruptByNewSignalsDescrToken 
               / OtherReasonToken ) 


So when an MGC wants the MG to notify a completion of a Signal
the MGC would specify:

NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
for)

Is this correct???

The reason I ask is later in the RFC there is this:
Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to "ON".  For further 
      procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 

Which seems to indicate that the NC really should be an ON or OFF value and
the 4 notificationReasons are really just return values.

Thanks,
Carl

Carl Rutter
Telica, Inc.
Building G, Suite 100
734 Forest Street
Marlboro, MA 01752
Email crutter@telica.com
Voice 508-480-0909 x8178
Fax 508-480-0922 
www.telica.com




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



From megaco-admin@ietf.org  Thu Jan 17 10:31:26 2002
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 KAA18877
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:31:26 -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 KAA05853;
	Thu, 17 Jan 2002 10:18:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05821
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:18:30 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18435
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 10:18:28 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFHsb23705;
	Thu, 17 Jan 2002 10:17:55 -0500 (EST)
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 g0HFHrG18215;
	Thu, 17 Jan 2002 10:17:53 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZV463>; Thu, 17 Jan 2002 10:17:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'"
	 <Megaco@ietf.org>
Subject: RE: [Megaco] NotifyCompletion Question
Date: Thu, 17 Jan 2002 10:17:57 -0500
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

The error is in the Annex E text.  This material was a fairly late addition
(part of the enormous amount of work we did in the Feb'00 meeting in
Geneva), and an inconsistency crept in.  You are the first to spot it.  The
text should read:

Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to enable reporting of a
      completion event.  For further procedural description, see 
      sections 7.1.11, 7.1.17, and 7.2.7. 



-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Thursday, January 17, 2002 10:04 AM
To: 'Megaco@ietf.org'
Subject: [Megaco] NotifyCompletion Question


For V1 the possible values of NotifyCompletion reason are:

notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
          notificationReason *(COMMA notificationReason) RBRKT) 
    
   notificationReason   = ( TimeOutToken / InterruptByEventToken 
               / InterruptByNewSignalsDescrToken 
               / OtherReasonToken ) 


So when an MGC wants the MG to notify a completion of a Signal
the MGC would specify:

NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
for)

Is this correct???

The reason I ask is later in the RFC there is this:
Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to "ON".  For further 
      procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 

Which seems to indicate that the NC really should be an ON or OFF value and
the 4 notificationReasons are really just return values.

Thanks,
Carl

Carl Rutter
Telica, Inc.
Building G, Suite 100
734 Forest Street
Marlboro, MA 01752
Email crutter@telica.com
Voice 508-480-0909 x8178
Fax 508-480-0922 
www.telica.com




_______________________________________________
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


From daemon@ns.ietf.org  Thu Jan 17 10:31:28 2002
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 KAA18886
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:31:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA06721
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 10:31:28 -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 KAA05853;
	Thu, 17 Jan 2002 10:18:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05821
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:18:30 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18435
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 10:18:28 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFHsb23705;
	Thu, 17 Jan 2002 10:17:55 -0500 (EST)
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 g0HFHrG18215;
	Thu, 17 Jan 2002 10:17:53 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZV463>; Thu, 17 Jan 2002 10:17:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'"
	 <Megaco@ietf.org>
Subject: RE: [Megaco] NotifyCompletion Question
Date: Thu, 17 Jan 2002 10:17:57 -0500
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

The error is in the Annex E text.  This material was a fairly late addition
(part of the enormous amount of work we did in the Feb'00 meeting in
Geneva), and an inconsistency crept in.  You are the first to spot it.  The
text should read:

Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to enable reporting of a
      completion event.  For further procedural description, see 
      sections 7.1.11, 7.1.17, and 7.2.7. 



-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Thursday, January 17, 2002 10:04 AM
To: 'Megaco@ietf.org'
Subject: [Megaco] NotifyCompletion Question


For V1 the possible values of NotifyCompletion reason are:

notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
          notificationReason *(COMMA notificationReason) RBRKT) 
    
   notificationReason   = ( TimeOutToken / InterruptByEventToken 
               / InterruptByNewSignalsDescrToken 
               / OtherReasonToken ) 


So when an MGC wants the MG to notify a completion of a Signal
the MGC would specify:

NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
for)

Is this correct???

The reason I ask is later in the RFC there is this:
Signal Completion 
      EventID: sc (0x0002) 
      Indicates termination of one or more signals for which the 
      notifyCompletion parameter was set to "ON".  For further 
      procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 

Which seems to indicate that the NC really should be an ON or OFF value and
the 4 notificationReasons are really just return values.

Thanks,
Carl

Carl Rutter
Telica, Inc.
Building G, Suite 100
734 Forest Street
Marlboro, MA 01752
Email crutter@telica.com
Voice 508-480-0909 x8178
Fax 508-480-0922 
www.telica.com




_______________________________________________
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



From daemon@ns.ietf.org  Thu Jan 17 10:34:41 2002
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 JAA17358
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 09:47:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA04663
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 09:47:20 -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 JAA04421;
	Thu, 17 Jan 2002 09:39:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04395
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 09:39:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16790
	for <megaco@ietf.org>; Thu, 17 Jan 2002 09:39:21 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HEcob16822;
	Thu, 17 Jan 2002 09:38:50 -0500 (EST)
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 g0HEcnG15455;
	Thu, 17 Jan 2002 09:38:49 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVTN5>; Thu, 17 Jan 2002 09:38:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE6A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Nurit Shenhar'" <NuritS@audiocodes.com>,
        "'Megaco_IETF (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [MEGACO] CNAME
Date: Thu, 17 Jan 2002 09:38:53 -0500
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

There is nothing in Megaco for this purpose.  If someone can make a good
case for it, they could add it in an extension of the RTP package.

-----Original Message-----
From: Nurit Shenhar [mailto:NuritS@audiocodes.com]
Sent: Thursday, January 17, 2002 2:56 AM
To: 'Megaco_IETF (E-mail)
Subject: [MEGACO] CNAME


Hi
Do we have in the MEGACO a way to supply a CNAME from the MGC, or should the
MG define it itself? (e.g TerminationName)
Thanks, Nurit


****************************************************************************
********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the individual or entity to whom
they are addressed.
If you have received this email in error please notify
postmaster@audiocodes.com
and permanently delete the e-mail and files.
****************************************************************************
*******************************

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



From megaco-admin@ietf.org  Thu Jan 17 10:36:11 2002
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 KAA19033
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:36:06 -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 KAA06123;
	Thu, 17 Jan 2002 10:25:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA06096
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:25:52 -0500 (EST)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18665
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:25:49 -0500 (EST)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GQ300E019G0EF@firewall.wcom.com> for megaco@ietf.org; Thu,
 17 Jan 2002 15:24:00 +0000 (GMT)
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GQ300DBO9FZFV@firewall.wcom.com>; Thu,
 17 Jan 2002 15:24:00 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com
 (PMDF V5.2-33 #42262) with SMTP id <0GQ3009019FWZM@dgismtp01.wcomnet.com>;
 Thu, 17 Jan 2002 15:23:59 +0000 (GMT)
Received: from ws678v1154 ([166.35.147.150])
 by dgismtp01.wcomnet.com (PMDF V5.2-33 #42262)
 with SMTP id <0GQ30096Y9FK42@dgismtp01.wcomnet.com>; Thu,
 17 Jan 2002 15:23:44 +0000 (GMT)
Date: Thu, 17 Jan 2002 09:30:28 -0600
From: Mike Huang <Mike.Huang@wcom.com>
Subject: RE: [Megaco] Service Change Question
In-reply-to: <65256B44.00148668.00@sandesh.hss.hns.com>
To: vibansal@hss.hns.com
Cc: megaco@ietf.org
Reply-to: Mike.Huang@wcom.com
Message-id: <NEBBLDAODEBDIGMKKOCGCEJPDAAA.Mike.Huang@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
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: 7bit

Vivek,

I agree with you statement below, but what if a MGC decides to ask for
ServiceChange request of 901 repeatedly?  Is the MG is obligated to respond
back everytime?  Let's say that the MGC asks for a 901 from the MG, the MG
has responded once already and it is being asked for another 901.  Should
the MG decide whether or not this is valid or should the MG honor the
request?

Thanks,
Mike

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Wednesday, January 16, 2002 9:47 PM
To: Mike.Huang@wcom.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Service Change Question





Hi

The MG should look into the service change reason sent in Service change
request
from MGC to gauge the severity of change in the states of the calls
currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete
the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike




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


From daemon@ns.ietf.org  Thu Jan 17 10:36:12 2002
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 KAA19042
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 10:36:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA06924
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 10:36:13 -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 KAA06123;
	Thu, 17 Jan 2002 10:25:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA06096
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:25:52 -0500 (EST)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18665
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:25:49 -0500 (EST)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GQ300E019G0EF@firewall.wcom.com> for megaco@ietf.org; Thu,
 17 Jan 2002 15:24:00 +0000 (GMT)
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GQ300DBO9FZFV@firewall.wcom.com>; Thu,
 17 Jan 2002 15:24:00 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com
 (PMDF V5.2-33 #42262) with SMTP id <0GQ3009019FWZM@dgismtp01.wcomnet.com>;
 Thu, 17 Jan 2002 15:23:59 +0000 (GMT)
Received: from ws678v1154 ([166.35.147.150])
 by dgismtp01.wcomnet.com (PMDF V5.2-33 #42262)
 with SMTP id <0GQ30096Y9FK42@dgismtp01.wcomnet.com>; Thu,
 17 Jan 2002 15:23:44 +0000 (GMT)
Date: Thu, 17 Jan 2002 09:30:28 -0600
From: Mike Huang <Mike.Huang@wcom.com>
Subject: RE: [Megaco] Service Change Question
In-reply-to: <65256B44.00148668.00@sandesh.hss.hns.com>
To: vibansal@hss.hns.com
Cc: megaco@ietf.org
Reply-to: Mike.Huang@wcom.com
Message-id: <NEBBLDAODEBDIGMKKOCGCEJPDAAA.Mike.Huang@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
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: 7bit

Vivek,

I agree with you statement below, but what if a MGC decides to ask for
ServiceChange request of 901 repeatedly?  Is the MG is obligated to respond
back everytime?  Let's say that the MGC asks for a 901 from the MG, the MG
has responded once already and it is being asked for another 901.  Should
the MG decide whether or not this is valid or should the MG honor the
request?

Thanks,
Mike

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Wednesday, January 16, 2002 9:47 PM
To: Mike.Huang@wcom.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Service Change Question





Hi

The MG should look into the service change reason sent in Service change
request
from MGC to gauge the severity of change in the states of the calls
currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete
the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike




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



From megaco-admin@ietf.org  Thu Jan 17 11:01:53 2002
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 LAA19906
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:01:52 -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 KAA07156;
	Thu, 17 Jan 2002 10:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07127
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:46:35 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19399
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:32 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFk3b04389
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:03 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFk1G15945
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVV61>; Thu, 17 Jan 2002 10:46:00 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 17 Jan 2002 10:46:03 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Clarification Of Multiplex Descriptor Text
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

I mentioned that several of us have been discussing additional text for
Multiplex Descriptors.  I have placed the proposed text as marked up changes
in the Megaco FTP site.  According to your taste, you can download
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
x64K.doc
or
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
x64K.pdf

Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
proposed text needs a further update.  The supporting bearers contained by a
multiplexing termination can be ephemeral as well as physical.  However, I
believe it would be essential that any ephemrals mentioned in a MUX
descriptor already exist in the context, since their properties are probably
not directly inferrable from those of the multiplexing termination.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@ns.ietf.org  Thu Jan 17 11:01:53 2002
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 LAA19918
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:01:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08097
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 11:01:55 -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 KAA07156;
	Thu, 17 Jan 2002 10:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07127
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:46:35 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19399
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:32 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFk3b04389
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:03 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0HFk1G15945
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:46:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZVV61>; Thu, 17 Jan 2002 10:46:00 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 17 Jan 2002 10:46:03 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Clarification Of Multiplex Descriptor Text
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

I mentioned that several of us have been discussing additional text for
Multiplex Descriptors.  I have placed the proposed text as marked up changes
in the Megaco FTP site.  According to your taste, you can download
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
x64K.doc
or
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
x64K.pdf

Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
proposed text needs a further update.  The supporting bearers contained by a
multiplexing termination can be ephemeral as well as physical.  However, I
believe it would be essential that any ephemrals mentioned in a MUX
descriptor already exist in the context, since their properties are probably
not directly inferrable from those of the multiplexing termination.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Thu Jan 17 11:03:47 2002
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 LAA19986
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:03:42 -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 KAA07256;
	Thu, 17 Jan 2002 10:49:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07228
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:49:35 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19469
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:49:31 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0HFo3E18188;
	Thu, 17 Jan 2002 21:20:03 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0056D3CB ; Thu, 17 Jan 2002 21:18:23 +0530
X-Lotus-FromDomain: HSS
To: Mike.Huang@wcom.com
cc: megaco@ietf.org
Message-ID: <65256B44.0056D248.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 21:22:00 +0530
Subject: RE: [Megaco] Service Change Question
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Mike

If you talk in terms of protocol then the MG is obliged to honour the request
every time. But at the same time it can implementation level decision to not the
talk to such an MGC and rather try different MGC.

Regards
Vivek
Hughes Software Systems







Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 09:00:28 PM

Please respond to Mike.Huang@wcom.com

To:   Vivek Bansal/HSS@HSS
cc:   megaco@ietf.org

Subject:  RE: [Megaco] Service Change Question




Vivek,

I agree with you statement below, but what if a MGC decides to ask for
ServiceChange request of 901 repeatedly?  Is the MG is obligated to respond
back everytime?  Let's say that the MGC asks for a 901 from the MG, the MG
has responded once already and it is being asked for another 901.  Should
the MG decide whether or not this is valid or should the MG honor the
request?

Thanks,
Mike

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Wednesday, January 16, 2002 9:47 PM
To: Mike.Huang@wcom.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Service Change Question





Hi

The MG should look into the service change reason sent in Service change
request
from MGC to gauge the severity of change in the states of the calls
currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete
the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike




_______________________________________________
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


From daemon@ns.ietf.org  Thu Jan 17 11:03:48 2002
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 LAA19997
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:03:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08146
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 11:03:49 -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 KAA07256;
	Thu, 17 Jan 2002 10:49:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07228
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 10:49:35 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19469
	for <megaco@ietf.org>; Thu, 17 Jan 2002 10:49:31 -0500 (EST)
From: vibansal@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0HFo3E18188;
	Thu, 17 Jan 2002 21:20:03 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B44.0056D3CB ; Thu, 17 Jan 2002 21:18:23 +0530
X-Lotus-FromDomain: HSS
To: Mike.Huang@wcom.com
cc: megaco@ietf.org
Message-ID: <65256B44.0056D248.00@sandesh.hss.hns.com>
Date: Thu, 17 Jan 2002 21:22:00 +0530
Subject: RE: [Megaco] Service Change Question
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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




Hi Mike

If you talk in terms of protocol then the MG is obliged to honour the request
every time. But at the same time it can implementation level decision to not the
talk to such an MGC and rather try different MGC.

Regards
Vivek
Hughes Software Systems







Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 09:00:28 PM

Please respond to Mike.Huang@wcom.com

To:   Vivek Bansal/HSS@HSS
cc:   megaco@ietf.org

Subject:  RE: [Megaco] Service Change Question




Vivek,

I agree with you statement below, but what if a MGC decides to ask for
ServiceChange request of 901 repeatedly?  Is the MG is obligated to respond
back everytime?  Let's say that the MGC asks for a 901 from the MG, the MG
has responded once already and it is being asked for another 901.  Should
the MG decide whether or not this is valid or should the MG honor the
request?

Thanks,
Mike

-----Original Message-----
From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
Sent: Wednesday, January 16, 2002 9:47 PM
To: Mike.Huang@wcom.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Service Change Question





Hi

The MG should look into the service change reason sent in Service change
request
from MGC to gauge the severity of change in the states of the calls
currently
active. If for eg., MGC sends reason 901, which indicates that the MGC has
deleted all the calls at its end. The MG in this case is obliged to delete
the
calls at its end also.

Regards
Vivek
Hughes Software Systems






Mike Huang <Mike.Huang@wcom.com> on 01/17/2002 02:56:14 AM

Please respond to Mike.Huang@wcom.com

To:   megaco@ietf.org
cc:    (bcc: Vivek Bansal/HSS)

Subject:  [Megaco] Service Change Question




Hello,

I was wondering for ServiceChange, does the MGC have the ability to ask the
MG for a ServiceChange with a specific ServiceChangeReason.  For example, if
I am a MGC and want to initate a ServiceChange with reason 901 to the MG
regardless of the actual state of the MG, should the MG allow this to happen
even though it is contrary to the actual state of the system?

Thanks,
Mike




_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 17 11:18:57 2002
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 LAA20528
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:18:56 -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 LAA08279;
	Thu, 17 Jan 2002 11:07:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08252
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 11:07:01 -0500 (EST)
Received: from gconsrv04.g-connect.co.il (g-connect.co.il [194.90.46.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20082
	for <megaco@ietf.org>; Thu, 17 Jan 2002 11:06:57 -0500 (EST)
Received: by GCONSRV04 with Internet Mail Service (5.5.2653.19)
	id <4WDBR3F9>; Thu, 17 Jan 2002 18:03:36 +0200
Message-ID: <F6FE1FFFD945D411A56A00D0B70C2912707644@GCONSRV04>
From: Yair Arian <yair.arian@G-CONNECT.co.il>
To: megaco@ietf.org
Date: Thu, 17 Jan 2002 18:03:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19F70.83030010"
Subject: [Megaco] (no subject)
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19F70.83030010
Content-Type: text/plain;
	charset="windows-1255"

unsubscribe megaco

------_=_NextPart_001_01C19F70.83030010
Content-Type: text/html;
	charset="windows-1255"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">unsubscribe megaco</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19F70.83030010--

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


From daemon@ns.ietf.org  Thu Jan 17 11:18:57 2002
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 LAA20536
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:18:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08662
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 11:18:59 -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 LAA08279;
	Thu, 17 Jan 2002 11:07:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08252
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 11:07:01 -0500 (EST)
Received: from gconsrv04.g-connect.co.il (g-connect.co.il [194.90.46.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20082
	for <megaco@ietf.org>; Thu, 17 Jan 2002 11:06:57 -0500 (EST)
Received: by GCONSRV04 with Internet Mail Service (5.5.2653.19)
	id <4WDBR3F9>; Thu, 17 Jan 2002 18:03:36 +0200
Message-ID: <F6FE1FFFD945D411A56A00D0B70C2912707644@GCONSRV04>
From: Yair Arian <yair.arian@G-CONNECT.co.il>
To: megaco@ietf.org
Date: Thu, 17 Jan 2002 18:03:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C19F70.83030010"
Subject: [Megaco] (no subject)
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19F70.83030010
Content-Type: text/plain;
	charset="windows-1255"

unsubscribe megaco

------_=_NextPart_001_01C19F70.83030010
Content-Type: text/html;
	charset="windows-1255"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">unsubscribe megaco</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19F70.83030010--

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



From megaco-admin@ietf.org  Thu Jan 17 11:31:10 2002
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 LAA21505
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:31:10 -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 LAA08639;
	Thu, 17 Jan 2002 11:18:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08609
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 11:17:59 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20479
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 11:17:56 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0HGHNM00932;
	Thu, 17 Jan 2002 11:17:23 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA02564;
	Thu, 17 Jan 2002 10:39:00 -0500 (EST)
Message-ID: <3C46EF5D.BF00B7E1@lucent.com>
Date: Thu, 17 Jan 2002 10:35:57 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: Re: [Megaco] NotifyCompletion Question
References: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------8FA2C41B0EED52BCD9220AAF"
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

This is a multi-part message in MIME format.
--------------8FA2C41B0EED52BCD9220AAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I agree.  I will add to IG.

Tom-PT Taylor wrote:

> The error is in the Annex E text.  This material was a fairly late addition
> (part of the enormous amount of work we did in the Feb'00 meeting in
> Geneva), and an inconsistency crept in.  You are the first to spot it.  The
> text should read:
>
> Signal Completion
>       EventID: sc (0x0002)
>       Indicates termination of one or more signals for which the
>       notifyCompletion parameter was set to enable reporting of a
>       completion event.  For further procedural description, see
>       sections 7.1.11, 7.1.17, and 7.2.7.
>
> -----Original Message-----
> From: Carl Rutter [mailto:crutter@telica.com]
> Sent: Thursday, January 17, 2002 10:04 AM
> To: 'Megaco@ietf.org'
> Subject: [Megaco] NotifyCompletion Question
>
> For V1 the possible values of NotifyCompletion reason are:
>
> notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
>           notificationReason *(COMMA notificationReason) RBRKT)
>
>    notificationReason   = ( TimeOutToken / InterruptByEventToken
>                / InterruptByNewSignalsDescrToken
>                / OtherReasonToken )
>
> So when an MGC wants the MG to notify a completion of a Signal
> the MGC would specify:
>
> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
> for)
>
> Is this correct???
>
> The reason I ask is later in the RFC there is this:
> Signal Completion
>       EventID: sc (0x0002)
>       Indicates termination of one or more signals for which the
>       notifyCompletion parameter was set to "ON".  For further
>       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7.
>
> Which seems to indicate that the NC really should be an ON or OFF value and
> the 4 notificationReasons are really just return values.
>
> Thanks,
> Carl
>
> Carl Rutter
> Telica, Inc.
> Building G, Suite 100
> 734 Forest Street
> Marlboro, MA 01752
> Email crutter@telica.com
> Voice 508-480-0909 x8178
> Fax 508-480-0922
> www.telica.com
>
> _______________________________________________
> 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------8FA2C41B0EED52BCD9220AAF
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------8FA2C41B0EED52BCD9220AAF--


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


From daemon@ns.ietf.org  Thu Jan 17 11:31:15 2002
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 LAA21515
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 11:31:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA09511
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 11:31:13 -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 LAA08639;
	Thu, 17 Jan 2002 11:18:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08609
	for <megaco@ns.ietf.org>; Thu, 17 Jan 2002 11:17:59 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20479
	for <Megaco@ietf.org>; Thu, 17 Jan 2002 11:17:56 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0HGHNM00932;
	Thu, 17 Jan 2002 11:17:23 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA02564;
	Thu, 17 Jan 2002 10:39:00 -0500 (EST)
Message-ID: <3C46EF5D.BF00B7E1@lucent.com>
Date: Thu, 17 Jan 2002 10:35:57 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: Re: [Megaco] NotifyCompletion Question
References: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------8FA2C41B0EED52BCD9220AAF"
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

This is a multi-part message in MIME format.
--------------8FA2C41B0EED52BCD9220AAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I agree.  I will add to IG.

Tom-PT Taylor wrote:

> The error is in the Annex E text.  This material was a fairly late addition
> (part of the enormous amount of work we did in the Feb'00 meeting in
> Geneva), and an inconsistency crept in.  You are the first to spot it.  The
> text should read:
>
> Signal Completion
>       EventID: sc (0x0002)
>       Indicates termination of one or more signals for which the
>       notifyCompletion parameter was set to enable reporting of a
>       completion event.  For further procedural description, see
>       sections 7.1.11, 7.1.17, and 7.2.7.
>
> -----Original Message-----
> From: Carl Rutter [mailto:crutter@telica.com]
> Sent: Thursday, January 17, 2002 10:04 AM
> To: 'Megaco@ietf.org'
> Subject: [Megaco] NotifyCompletion Question
>
> For V1 the possible values of NotifyCompletion reason are:
>
> notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
>           notificationReason *(COMMA notificationReason) RBRKT)
>
>    notificationReason   = ( TimeOutToken / InterruptByEventToken
>                / InterruptByNewSignalsDescrToken
>                / OtherReasonToken )
>
> So when an MGC wants the MG to notify a completion of a Signal
> the MGC would specify:
>
> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
> for)
>
> Is this correct???
>
> The reason I ask is later in the RFC there is this:
> Signal Completion
>       EventID: sc (0x0002)
>       Indicates termination of one or more signals for which the
>       notifyCompletion parameter was set to "ON".  For further
>       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7.
>
> Which seems to indicate that the NC really should be an ON or OFF value and
> the 4 notificationReasons are really just return values.
>
> Thanks,
> Carl
>
> Carl Rutter
> Telica, Inc.
> Building G, Suite 100
> 734 Forest Street
> Marlboro, MA 01752
> Email crutter@telica.com
> Voice 508-480-0909 x8178
> Fax 508-480-0922
> www.telica.com
>
> _______________________________________________
> 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------8FA2C41B0EED52BCD9220AAF
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------8FA2C41B0EED52BCD9220AAF--


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



From megaco-admin@ietf.org  Thu Jan 17 18:45:15 2002
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 SAA15677
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 18:45:14 -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 SAA29714;
	Thu, 17 Jan 2002 18:33:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA29685
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 18:33:52 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15563
	for <megaco@ietf.org>; Thu, 17 Jan 2002 18:33:48 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0HNXnK02166;
	Fri, 18 Jan 2002 00:33:49 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id AAA09520; Fri, 18 Jan 2002 00:33:37 +0100
Message-ID: <3C475F66.DC9A8601@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 01:33:58 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] LCN mapping
References: <4D79C746863DD51197690002A52CDA000102AE47@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>The short answer is that the relationship between LCN (Logical Channel
>Number) and streamID is set by the application control, which probably
>resides in the MGC.

I agree. But, how do I indicate that relationship to the MG, where the
actual LCN and streamID "connection" is?

>Assuming your H.223 mux is operating as part of the H.324 system it was designed for, the control information >is carried in H.245 signalling, gets routed to the MGC, and results in H.248 requests back
>to the MG.

I agree. But, again, in that request the MGC have to tell the MG how to
do the mapping.
 
>However, let me first address your proposed multiplexing structure.  I
>should mention that several of us (Christian Groves, Roni Even, Marcello
>Pantaleo and myself) are nearing the end of a discussion initiated by
>Christian, on additional words to add around the multiplex concept,
>clarifying it and at the same time allowing it to be used to represent Nx64K
>wideband service.  I will report the results and reasoning to the list
>shortly.  In any event, the basic multiplex concept I have been defending
>(based on what we already have in RFC 3015/H.248)is something that
>specifically has one or more circuits on one side and appears as an ordinary
>termination to the rest of the context on the other.  Along the way, it
>hides the circuits (which are represented by terminationIDs of their own)
>from the rest of the context.
> 
>In your present example, you have the multiplexing termination (T3), 30 or
>24 circuits which support it (the circuits in the E1/T1), and the RTP
>termination T2.  If you are running H.324, the recommended way to tie the
>circuits together is to use H.226 channel aggregation (set up with V.140
>signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
>(Annex F) but not in H.223, I suspect we have to model the two layers of
>multiplexing explicitly.  This blows holes in my idea that all multiplexes
>are supported directly by circuits.  In diagramatic terms, we have the
>following situation:
> 
>                        Context interior ---->
>                    _________                 _________
>       Data stream  | H.226 |                 | H.223 |   Audio stream
>Ckt 1 ..............| "MUX" |                 |  MUX  | .................
>       . . .        | term  |   Data stream   | term  |
>       Data stream  |       | ................|       |   Video stream
>Ckt n ..............|       |                 |       | .................
>                    |       |                 |       |
>                    ---------                 ---------
> 
>Here the H.226 MUX termination contains/is supported by the individual
>circuits, which appear as terminations in their own right.  The H.223 MUX
>termination contains/is supported by the H.226 MUX termination.
> 
>The model I have been arguing for is that a multiplexing termination hides
>all of the terminations it contains from the rest of the context.  One
>implication of this is that the streamIDs of the streams flowing between the
>contained terminations and the multiplexing termination are local rather
>than global in scope.
> 
>Looking at the above diagram, people may ask how we know that the stream
>between the H.226 and H.223 multiplexing terminations is a data stream,
>while the streams passing from the H.223 termination to the rest of the
>context are audio and video.  I will maintain that this is a result of the
>definition of the respective multiplexes.  If this is not clear, we need an
>explicit description of the exterior-side and context-side streams supported
>by each multiplex somewhere within our Megaco/H.248 documentation.

I look at the above diagram, and my question is still the same: how do I
map the Audio- and Video straems coming out from the H.223 MUX term to
specific RTP terminations (and possibly specific streams within them)?

>I come to my final point.  Your example included the RTP termination T2
>within the multiplex.  In my view this is a mistake: T2 is just another
>termination in the context.  All it sees is T3, the H.223 multiplexing
>termination, and it exchanges audio and video with that termination.

Ok, but my question STILL remains :) T3 does see the mux termination,
but I need to be able to tell my context that stream 1 (eg audio) from
the mux shall be mapped to stream X in T3, and stream 2 (eg video) shall
be mapped to stream Y in T3.

...or, if I want to use separate RTP terminations for audio and video, I
need to be able to tell that mux stream 1 shall be mapped to RTP
termination T3, and stream 2 into RTP termination T4.

>I hope this makes things clearer.  The question has raised some points which
>I will now have to reflect back into my conversation with Christian and all.
>Even better if they bring that conversation to this list.

Maybe I've missed some point, but I am still as confused :)

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Thu Jan 17 18:45:15 2002
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 SAA15686
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 18:45:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA29954
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 18:45:18 -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 SAA29714;
	Thu, 17 Jan 2002 18:33:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA29685
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 18:33:52 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15563
	for <megaco@ietf.org>; Thu, 17 Jan 2002 18:33:48 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0HNXnK02166;
	Fri, 18 Jan 2002 00:33:49 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id AAA09520; Fri, 18 Jan 2002 00:33:37 +0100
Message-ID: <3C475F66.DC9A8601@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 01:33:58 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] LCN mapping
References: <4D79C746863DD51197690002A52CDA000102AE47@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>The short answer is that the relationship between LCN (Logical Channel
>Number) and streamID is set by the application control, which probably
>resides in the MGC.

I agree. But, how do I indicate that relationship to the MG, where the
actual LCN and streamID "connection" is?

>Assuming your H.223 mux is operating as part of the H.324 system it was designed for, the control information >is carried in H.245 signalling, gets routed to the MGC, and results in H.248 requests back
>to the MG.

I agree. But, again, in that request the MGC have to tell the MG how to
do the mapping.
 
>However, let me first address your proposed multiplexing structure.  I
>should mention that several of us (Christian Groves, Roni Even, Marcello
>Pantaleo and myself) are nearing the end of a discussion initiated by
>Christian, on additional words to add around the multiplex concept,
>clarifying it and at the same time allowing it to be used to represent Nx64K
>wideband service.  I will report the results and reasoning to the list
>shortly.  In any event, the basic multiplex concept I have been defending
>(based on what we already have in RFC 3015/H.248)is something that
>specifically has one or more circuits on one side and appears as an ordinary
>termination to the rest of the context on the other.  Along the way, it
>hides the circuits (which are represented by terminationIDs of their own)
>from the rest of the context.
> 
>In your present example, you have the multiplexing termination (T3), 30 or
>24 circuits which support it (the circuits in the E1/T1), and the RTP
>termination T2.  If you are running H.324, the recommended way to tie the
>circuits together is to use H.226 channel aggregation (set up with V.140
>signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
>(Annex F) but not in H.223, I suspect we have to model the two layers of
>multiplexing explicitly.  This blows holes in my idea that all multiplexes
>are supported directly by circuits.  In diagramatic terms, we have the
>following situation:
> 
>                        Context interior ---->
>                    _________                 _________
>       Data stream  | H.226 |                 | H.223 |   Audio stream
>Ckt 1 ..............| "MUX" |                 |  MUX  | .................
>       . . .        | term  |   Data stream   | term  |
>       Data stream  |       | ................|       |   Video stream
>Ckt n ..............|       |                 |       | .................
>                    |       |                 |       |
>                    ---------                 ---------
> 
>Here the H.226 MUX termination contains/is supported by the individual
>circuits, which appear as terminations in their own right.  The H.223 MUX
>termination contains/is supported by the H.226 MUX termination.
> 
>The model I have been arguing for is that a multiplexing termination hides
>all of the terminations it contains from the rest of the context.  One
>implication of this is that the streamIDs of the streams flowing between the
>contained terminations and the multiplexing termination are local rather
>than global in scope.
> 
>Looking at the above diagram, people may ask how we know that the stream
>between the H.226 and H.223 multiplexing terminations is a data stream,
>while the streams passing from the H.223 termination to the rest of the
>context are audio and video.  I will maintain that this is a result of the
>definition of the respective multiplexes.  If this is not clear, we need an
>explicit description of the exterior-side and context-side streams supported
>by each multiplex somewhere within our Megaco/H.248 documentation.

I look at the above diagram, and my question is still the same: how do I
map the Audio- and Video straems coming out from the H.223 MUX term to
specific RTP terminations (and possibly specific streams within them)?

>I come to my final point.  Your example included the RTP termination T2
>within the multiplex.  In my view this is a mistake: T2 is just another
>termination in the context.  All it sees is T3, the H.223 multiplexing
>termination, and it exchanges audio and video with that termination.

Ok, but my question STILL remains :) T3 does see the mux termination,
but I need to be able to tell my context that stream 1 (eg audio) from
the mux shall be mapped to stream X in T3, and stream 2 (eg video) shall
be mapped to stream Y in T3.

...or, if I want to use separate RTP terminations for audio and video, I
need to be able to tell that mux stream 1 shall be mapped to RTP
termination T3, and stream 2 into RTP termination T4.

>I hope this makes things clearer.  The question has raised some points which
>I will now have to reflect back into my conversation with Christian and all.
>Even better if they bring that conversation to this list.

Maybe I've missed some point, but I am still as confused :)

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Thu Jan 17 20:15:52 2002
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 UAA16775
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 20:15:51 -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 UAA02674;
	Thu, 17 Jan 2002 20:03:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02640
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 20:03:05 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16638
	for <megaco@ietf.org>; Thu, 17 Jan 2002 20:03:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0I0wjb04798;
	Thu, 17 Jan 2002 19:58:45 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0I0wgG07175;
	Thu, 17 Jan 2002 19:58:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZW1FN>; Thu, 17 Jan 2002 19:58:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE83@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: megaco@ietf.org, "'sg16@jf.intel.com'" <sg16@jf.intel.com>
Subject: RE: [Megaco] LCN mapping
Date: Thu, 17 Jan 2002 19:58:43 -0500
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

H.248 Annex M.4 (packages for H.324 operation) says this right at the end of
section M.4.6:

"When logical channels are opened for audio, video and data, the termination
shall be connected to the appropriate terminations respectively."

In other words, it happens by magic.  You make a valid point: there is
something missing in the specification.  One possibility is to say that the
MG associates streams with logical channels in the sequence in which the two
are respectively defined.  Because of the possibility of misordering it
would be safer to have an explicit means for the purpose.

I wonder if it is too soon to amend Annex M.4?  I'm copying this message to
the SG 16 list so they can think about the issue.



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, January 17, 2002 6:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: Re: [Megaco] LCN mapping



Hi,

>The short answer is that the relationship between LCN (Logical Channel
>Number) and streamID is set by the application control, which probably
>resides in the MGC.

I agree. But, how do I indicate that relationship to the MG, where the
actual LCN and streamID "connection" is?

>Assuming your H.223 mux is operating as part of the H.324 system it was
designed for, the control information >is carried in H.245 signalling, gets
routed to the MGC, and results in H.248 requests back
>to the MG.

I agree. But, again, in that request the MGC have to tell the MG how to
do the mapping.
 
>However, let me first address your proposed multiplexing structure.  I
>should mention that several of us (Christian Groves, Roni Even, Marcello
>Pantaleo and myself) are nearing the end of a discussion initiated by
>Christian, on additional words to add around the multiplex concept,
>clarifying it and at the same time allowing it to be used to represent
Nx64K
>wideband service.  I will report the results and reasoning to the list
>shortly.  In any event, the basic multiplex concept I have been defending
>(based on what we already have in RFC 3015/H.248)is something that
>specifically has one or more circuits on one side and appears as an
ordinary
>termination to the rest of the context on the other.  Along the way, it
>hides the circuits (which are represented by terminationIDs of their own)
>from the rest of the context.
> 
>In your present example, you have the multiplexing termination (T3), 30 or
>24 circuits which support it (the circuits in the E1/T1), and the RTP
>termination T2.  If you are running H.324, the recommended way to tie the
>circuits together is to use H.226 channel aggregation (set up with V.140
>signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
>(Annex F) but not in H.223, I suspect we have to model the two layers of
>multiplexing explicitly.  This blows holes in my idea that all multiplexes
>are supported directly by circuits.  In diagramatic terms, we have the
>following situation:
> 
>                        Context interior ---->
>                    _________                 _________
>       Data stream  | H.226 |                 | H.223 |   Audio stream
>Ckt 1 ..............| "MUX" |                 |  MUX  | .................
>       . . .        | term  |   Data stream   | term  |
>       Data stream  |       | ................|       |   Video stream
>Ckt n ..............|       |                 |       | .................
>                    |       |                 |       |
>                    ---------                 ---------
> 
>Here the H.226 MUX termination contains/is supported by the individual
>circuits, which appear as terminations in their own right.  The H.223 MUX
>termination contains/is supported by the H.226 MUX termination.
> 
>The model I have been arguing for is that a multiplexing termination hides
>all of the terminations it contains from the rest of the context.  One
>implication of this is that the streamIDs of the streams flowing between
the
>contained terminations and the multiplexing termination are local rather
>than global in scope.
> 
>Looking at the above diagram, people may ask how we know that the stream
>between the H.226 and H.223 multiplexing terminations is a data stream,
>while the streams passing from the H.223 termination to the rest of the
>context are audio and video.  I will maintain that this is a result of the
>definition of the respective multiplexes.  If this is not clear, we need an
>explicit description of the exterior-side and context-side streams
supported
>by each multiplex somewhere within our Megaco/H.248 documentation.

I look at the above diagram, and my question is still the same: how do I
map the Audio- and Video straems coming out from the H.223 MUX term to
specific RTP terminations (and possibly specific streams within them)?

>I come to my final point.  Your example included the RTP termination T2
>within the multiplex.  In my view this is a mistake: T2 is just another
>termination in the context.  All it sees is T3, the H.223 multiplexing
>termination, and it exchanges audio and video with that termination.

Ok, but my question STILL remains :) T3 does see the mux termination,
but I need to be able to tell my context that stream 1 (eg audio) from
the mux shall be mapped to stream X in T3, and stream 2 (eg video) shall
be mapped to stream Y in T3.

...or, if I want to use separate RTP terminations for audio and video, I
need to be able to tell that mux stream 1 shall be mapped to RTP
termination T3, and stream 2 into RTP termination T4.

>I hope this makes things clearer.  The question has raised some points
which
>I will now have to reflect back into my conversation with Christian and
all.
>Even better if they bring that conversation to this list.

Maybe I've missed some point, but I am still as confused :)

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Thu Jan 17 20:15:52 2002
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 UAA16785
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 20:15:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA02937
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 20:15:54 -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 UAA02674;
	Thu, 17 Jan 2002 20:03:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02640
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 20:03:05 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16638
	for <megaco@ietf.org>; Thu, 17 Jan 2002 20:03:03 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0I0wjb04798;
	Thu, 17 Jan 2002 19:58:45 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0I0wgG07175;
	Thu, 17 Jan 2002 19:58:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZW1FN>; Thu, 17 Jan 2002 19:58:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE83@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: megaco@ietf.org, "'sg16@jf.intel.com'" <sg16@jf.intel.com>
Subject: RE: [Megaco] LCN mapping
Date: Thu, 17 Jan 2002 19:58:43 -0500
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

H.248 Annex M.4 (packages for H.324 operation) says this right at the end of
section M.4.6:

"When logical channels are opened for audio, video and data, the termination
shall be connected to the appropriate terminations respectively."

In other words, it happens by magic.  You make a valid point: there is
something missing in the specification.  One possibility is to say that the
MG associates streams with logical channels in the sequence in which the two
are respectively defined.  Because of the possibility of misordering it
would be safer to have an explicit means for the purpose.

I wonder if it is too soon to amend Annex M.4?  I'm copying this message to
the SG 16 list so they can think about the issue.



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, January 17, 2002 6:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: Re: [Megaco] LCN mapping



Hi,

>The short answer is that the relationship between LCN (Logical Channel
>Number) and streamID is set by the application control, which probably
>resides in the MGC.

I agree. But, how do I indicate that relationship to the MG, where the
actual LCN and streamID "connection" is?

>Assuming your H.223 mux is operating as part of the H.324 system it was
designed for, the control information >is carried in H.245 signalling, gets
routed to the MGC, and results in H.248 requests back
>to the MG.

I agree. But, again, in that request the MGC have to tell the MG how to
do the mapping.
 
>However, let me first address your proposed multiplexing structure.  I
>should mention that several of us (Christian Groves, Roni Even, Marcello
>Pantaleo and myself) are nearing the end of a discussion initiated by
>Christian, on additional words to add around the multiplex concept,
>clarifying it and at the same time allowing it to be used to represent
Nx64K
>wideband service.  I will report the results and reasoning to the list
>shortly.  In any event, the basic multiplex concept I have been defending
>(based on what we already have in RFC 3015/H.248)is something that
>specifically has one or more circuits on one side and appears as an
ordinary
>termination to the rest of the context on the other.  Along the way, it
>hides the circuits (which are represented by terminationIDs of their own)
>from the rest of the context.
> 
>In your present example, you have the multiplexing termination (T3), 30 or
>24 circuits which support it (the circuits in the E1/T1), and the RTP
>termination T2.  If you are running H.324, the recommended way to tie the
>circuits together is to use H.226 channel aggregation (set up with V.140
>signalling) under the H.223 multiplex.  Because H.226 is mentioned in H.324
>(Annex F) but not in H.223, I suspect we have to model the two layers of
>multiplexing explicitly.  This blows holes in my idea that all multiplexes
>are supported directly by circuits.  In diagramatic terms, we have the
>following situation:
> 
>                        Context interior ---->
>                    _________                 _________
>       Data stream  | H.226 |                 | H.223 |   Audio stream
>Ckt 1 ..............| "MUX" |                 |  MUX  | .................
>       . . .        | term  |   Data stream   | term  |
>       Data stream  |       | ................|       |   Video stream
>Ckt n ..............|       |                 |       | .................
>                    |       |                 |       |
>                    ---------                 ---------
> 
>Here the H.226 MUX termination contains/is supported by the individual
>circuits, which appear as terminations in their own right.  The H.223 MUX
>termination contains/is supported by the H.226 MUX termination.
> 
>The model I have been arguing for is that a multiplexing termination hides
>all of the terminations it contains from the rest of the context.  One
>implication of this is that the streamIDs of the streams flowing between
the
>contained terminations and the multiplexing termination are local rather
>than global in scope.
> 
>Looking at the above diagram, people may ask how we know that the stream
>between the H.226 and H.223 multiplexing terminations is a data stream,
>while the streams passing from the H.223 termination to the rest of the
>context are audio and video.  I will maintain that this is a result of the
>definition of the respective multiplexes.  If this is not clear, we need an
>explicit description of the exterior-side and context-side streams
supported
>by each multiplex somewhere within our Megaco/H.248 documentation.

I look at the above diagram, and my question is still the same: how do I
map the Audio- and Video straems coming out from the H.223 MUX term to
specific RTP terminations (and possibly specific streams within them)?

>I come to my final point.  Your example included the RTP termination T2
>within the multiplex.  In my view this is a mistake: T2 is just another
>termination in the context.  All it sees is T3, the H.223 multiplexing
>termination, and it exchanges audio and video with that termination.

Ok, but my question STILL remains :) T3 does see the mux termination,
but I need to be able to tell my context that stream 1 (eg audio) from
the mux shall be mapped to stream X in T3, and stream 2 (eg video) shall
be mapped to stream Y in T3.

...or, if I want to use separate RTP terminations for audio and video, I
need to be able to tell that mux stream 1 shall be mapped to RTP
termination T3, and stream 2 into RTP termination T4.

>I hope this makes things clearer.  The question has raised some points
which
>I will now have to reflect back into my conversation with Christian and
all.
>Even better if they bring that conversation to this list.

Maybe I've missed some point, but I am still as confused :)

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Thu Jan 17 23:26:06 2002
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 XAA21789
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 23:26:06 -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 XAA09739;
	Thu, 17 Jan 2002 23:08:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA09708
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 23:08:26 -0500 (EST)
Received: from mailweb13.rediffmail.com ([203.199.83.25])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA21328
	for <megaco@ietf.org>; Thu, 17 Jan 2002 23:08:21 -0500 (EST)
Received: (qmail 13296 invoked by uid 510); 18 Jan 2002 04:07:43 -0000
Date: 18 Jan 2002 04:07:43 -0000
Message-ID: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 04:07:43 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA09709
Subject: [Megaco] **SERVICE CHANGE REASON
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


hi

   Where do I get the list of service change reasons .. ? RFC doesn't talk about that.

sree 


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


From daemon@optimus.ietf.org  Thu Jan 17 23:26:08 2002
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 XAA21803
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jan 2002 23:26:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12010
	for megaco-archive@odin.ietf.org; Thu, 17 Jan 2002 23:26:12 -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 XAA09739;
	Thu, 17 Jan 2002 23:08:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA09708
	for <megaco@optimus.ietf.org>; Thu, 17 Jan 2002 23:08:26 -0500 (EST)
Received: from mailweb13.rediffmail.com ([203.199.83.25])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA21328
	for <megaco@ietf.org>; Thu, 17 Jan 2002 23:08:21 -0500 (EST)
Received: (qmail 13296 invoked by uid 510); 18 Jan 2002 04:07:43 -0000
Date: 18 Jan 2002 04:07:43 -0000
Message-ID: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 04:07:43 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA09709
Subject: [Megaco] **SERVICE CHANGE REASON
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


hi

   Where do I get the list of service change reasons .. ? RFC doesn't talk about that.

sree 


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



From megaco-admin@ietf.org  Fri Jan 18 00:31:35 2002
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 AAA23154
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 00:31:35 -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 AAA14073;
	Fri, 18 Jan 2002 00:15:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14045
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 00:15:00 -0500 (EST)
Received: from brahma01.netbrahma.com ([164.164.70.67])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22845
	for <megaco@ietf.org>; Fri, 18 Jan 2002 00:14:53 -0500 (EST)
Received: from sundarpv (sundarpv.netbrahma.com [172.16.72.85]) by brahma01.netbrahma.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id CPSXB9HS; Fri, 18 Jan 2002 10:43:38 +0530
Message-ID: <032f01c19fde$d7e5eb10$554810ac@netbrahma.com>
Reply-To: "Sundareswaram P V" <sundareswarampv@netbrahma.com>
From: "Sundareswaram P V" <sundareswarampv@netbrahma.com>
To: <megaco@ietf.org>
Date: Fri, 18 Jan 2002 10:43:19 +0530
Organization: Netbrahma Tech. Pvt. Ltd.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_032C_01C1A00C.F194FF50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [Megaco] Doubt regarding sending Error in Transaction Reply.
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

This is a multi-part message in MIME format.

------=_NextPart_000_032C_01C1A00C.F194FF50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
     consider the example message below.

MEGACO/1 [125.125.125.111]:55555
Transaction =3D 50009 {
   Context =3D 5000 {
      Subtract =3D A5555 {
         Statistics {
            ........
         }
       },
       abc =3D A5556 {=20
                    // --- request type is corrupted=20
                    // instead of subtract it become 'abc'
               Statistics {
                  ......
                    nt/os=3D62345, ; octets sent
                     rtp/pr=3D780, ; packets received
                     nt/or=3D45123, ; octets received
               }
            }
         }
      }

The problem is as follows :
In the same context we have two commands. the first command get parsed =
well and will be inserted in to the Action Request while in the second =
command, the command type it self is corrupted. so how, do i form the =
ActionReply :

as the RFC 3015 states :

action reply =3D CtxToken EQUAL ContextID LBRKT
            (ErrorDescriptor / Command Reply) RBRKT

but as such for an action request i can send only one action reply. but =
the syntax above doesn't allow me to set both an error descriptor and an =
command reply with in an action reply.

cud any one help me resolve the issue  ??

thanx in advance.

rgds,
Sundar.



------=_NextPart_000_032C_01C1A00C.F194FF50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; consider the =
example=20
message below.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>MEGACO/1 =
[125.125.125.111]:55555<BR>Transaction =3D=20
50009 {<BR>&nbsp;&nbsp;&nbsp;Context =3D 5000=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Subtract =3D A5555=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
........<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
}<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},<BR>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;abc=20
=3D A5556 {&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//=20
--- request type&nbsp;is corrupted</STRONG>&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
// instead of subtract it become=20
'abc'</STRONG><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Statistics=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;......<BR>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;nt/os=3D62345,=20
; octets sent<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
&nbsp; rtp/pr=3D780, ; packets received<BR> &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; nt/or=3D45123, ; octets=20
received<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
}<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}<BR> &nbsp; &nbsp; =
&nbsp; &nbsp;=20
}<BR> &nbsp; &nbsp; &nbsp;}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The problem is as follows =
:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In the same context we have two =
commands. the first=20
command get parsed well and will be inserted in to the Action=20
Request&nbsp;while&nbsp;in the second command, the command type it self =
is=20
corrupted. so how, do i form the ActionReply :</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>as the RFC 3015 states :</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>action reply =3D CtxToken EQUAL =
ContextID=20
LBRKT</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; (ErrorDescriptor / Command Reply) RBRKT</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>but as such for an action request i can =
send only=20
one action reply. but the syntax above doesn't allow me to set both an =
error=20
descriptor and an command reply with in an action reply.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>cud any one help me resolve the =
issue&nbsp;=20
??</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanx in advance.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>rgds,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sundar.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_032C_01C1A00C.F194FF50--


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


From daemon@optimus.ietf.org  Fri Jan 18 00:31:36 2002
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 AAA23164
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 00:31:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA14746
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 00:31:38 -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 AAA14073;
	Fri, 18 Jan 2002 00:15:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14045
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 00:15:00 -0500 (EST)
Received: from brahma01.netbrahma.com ([164.164.70.67])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22845
	for <megaco@ietf.org>; Fri, 18 Jan 2002 00:14:53 -0500 (EST)
Received: from sundarpv (sundarpv.netbrahma.com [172.16.72.85]) by brahma01.netbrahma.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id CPSXB9HS; Fri, 18 Jan 2002 10:43:38 +0530
Message-ID: <032f01c19fde$d7e5eb10$554810ac@netbrahma.com>
Reply-To: "Sundareswaram P V" <sundareswarampv@netbrahma.com>
From: "Sundareswaram P V" <sundareswarampv@netbrahma.com>
To: <megaco@ietf.org>
Date: Fri, 18 Jan 2002 10:43:19 +0530
Organization: Netbrahma Tech. Pvt. Ltd.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_032C_01C1A00C.F194FF50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [Megaco] Doubt regarding sending Error in Transaction Reply.
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

This is a multi-part message in MIME format.

------=_NextPart_000_032C_01C1A00C.F194FF50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
     consider the example message below.

MEGACO/1 [125.125.125.111]:55555
Transaction =3D 50009 {
   Context =3D 5000 {
      Subtract =3D A5555 {
         Statistics {
            ........
         }
       },
       abc =3D A5556 {=20
                    // --- request type is corrupted=20
                    // instead of subtract it become 'abc'
               Statistics {
                  ......
                    nt/os=3D62345, ; octets sent
                     rtp/pr=3D780, ; packets received
                     nt/or=3D45123, ; octets received
               }
            }
         }
      }

The problem is as follows :
In the same context we have two commands. the first command get parsed =
well and will be inserted in to the Action Request while in the second =
command, the command type it self is corrupted. so how, do i form the =
ActionReply :

as the RFC 3015 states :

action reply =3D CtxToken EQUAL ContextID LBRKT
            (ErrorDescriptor / Command Reply) RBRKT

but as such for an action request i can send only one action reply. but =
the syntax above doesn't allow me to set both an error descriptor and an =
command reply with in an action reply.

cud any one help me resolve the issue  ??

thanx in advance.

rgds,
Sundar.



------=_NextPart_000_032C_01C1A00C.F194FF50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; consider the =
example=20
message below.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>MEGACO/1 =
[125.125.125.111]:55555<BR>Transaction =3D=20
50009 {<BR>&nbsp;&nbsp;&nbsp;Context =3D 5000=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Subtract =3D A5555=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
........<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
}<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},<BR>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;abc=20
=3D A5556 {&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//=20
--- request type&nbsp;is corrupted</STRONG>&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
// instead of subtract it become=20
'abc'</STRONG><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Statistics=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;......<BR>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;nt/os=3D62345,=20
; octets sent<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;=20
&nbsp; rtp/pr=3D780, ; packets received<BR> &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; nt/or=3D45123, ; octets=20
received<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
}<BR> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}<BR> &nbsp; &nbsp; =
&nbsp; &nbsp;=20
}<BR> &nbsp; &nbsp; &nbsp;}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The problem is as follows =
:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In the same context we have two =
commands. the first=20
command get parsed well and will be inserted in to the Action=20
Request&nbsp;while&nbsp;in the second command, the command type it self =
is=20
corrupted. so how, do i form the ActionReply :</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>as the RFC 3015 states :</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>action reply =3D CtxToken EQUAL =
ContextID=20
LBRKT</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; (ErrorDescriptor / Command Reply) RBRKT</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>but as such for an action request i can =
send only=20
one action reply. but the syntax above doesn't allow me to set both an =
error=20
descriptor and an command reply with in an action reply.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>cud any one help me resolve the =
issue&nbsp;=20
??</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanx in advance.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>rgds,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sundar.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_032C_01C1A00C.F194FF50--


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



From megaco-admin@ietf.org  Fri Jan 18 01:39:40 2002
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 BAA23819
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 01:39:39 -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 BAA25318;
	Fri, 18 Jan 2002 01:29:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25286
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:29:24 -0500 (EST)
Received: from mail.deldsl.com ([202.131.154.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23712
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:29:20 -0500 (EST)
Received: from dexceldesigns.com ([202.131.154.196])
	by mail.deldsl.com (8.11.0/8.8.7) with ESMTP id g0IBs9X23639
	for <megaco@ietf.org>; Fri, 18 Jan 2002 11:54:11 GMT
Message-ID: <000801c19fea$7cfd4020$12010a64@domain.dexceldesigns.com>
From: Narendra Babu <narendra@dexceldesigns.com>
To: <megaco@ietf.org>
Date: Fri, 18 Jan 2002 12:06:41 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;	boundary="----=_NextPart_000_0005_01C1A018.96A639E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailserver: Sent using PostMaster (v4.1.10)
Subject: [Megaco] Regarding IPsec and interim AH
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

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C1A018.96A639E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

        I am a newbie to this mail list as well as megaco.

We are developing a megaco stack.My doubt is whether
we have to implement full IPsec(RFC 2401-RFC 2411) or
only interim AH as a secrity support? Please clarify  this as early as =
possible.


Thankig you in advance

Narendra



------=_NextPart_000_0005_01C1A018.96A639E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; I =
am a newbie=20
to this mail list as well as megaco.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We are developing a megaco stack.My =
doubt is=20
whether</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we have to implement full IPsec(RFC =
2401-RFC 2411)=20
or</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>only interim AH as a secrity support? =
Please=20
clarify&nbsp; this as early as possible.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thankig you in advance</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Narendra</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

<br>--------------------------------------------------------------<br>Dexcel Electronics Designs (P) Ltd., Bangalore, India<br>
------=_NextPart_000_0005_01C1A018.96A639E0--


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


From daemon@optimus.ietf.org  Fri Jan 18 01:39:45 2002
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 BAA23833
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 01:39:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA26013
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 01:39:41 -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 BAA25318;
	Fri, 18 Jan 2002 01:29:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25286
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:29:24 -0500 (EST)
Received: from mail.deldsl.com ([202.131.154.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23712
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:29:20 -0500 (EST)
Received: from dexceldesigns.com ([202.131.154.196])
	by mail.deldsl.com (8.11.0/8.8.7) with ESMTP id g0IBs9X23639
	for <megaco@ietf.org>; Fri, 18 Jan 2002 11:54:11 GMT
Message-ID: <000801c19fea$7cfd4020$12010a64@domain.dexceldesigns.com>
From: Narendra Babu <narendra@dexceldesigns.com>
To: <megaco@ietf.org>
Date: Fri, 18 Jan 2002 12:06:41 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;	boundary="----=_NextPart_000_0005_01C1A018.96A639E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailserver: Sent using PostMaster (v4.1.10)
Subject: [Megaco] Regarding IPsec and interim AH
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

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C1A018.96A639E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

        I am a newbie to this mail list as well as megaco.

We are developing a megaco stack.My doubt is whether
we have to implement full IPsec(RFC 2401-RFC 2411) or
only interim AH as a secrity support? Please clarify  this as early as =
possible.


Thankig you in advance

Narendra



------=_NextPart_000_0005_01C1A018.96A639E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; I =
am a newbie=20
to this mail list as well as megaco.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We are developing a megaco stack.My =
doubt is=20
whether</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we have to implement full IPsec(RFC =
2401-RFC 2411)=20
or</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>only interim AH as a secrity support? =
Please=20
clarify&nbsp; this as early as possible.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thankig you in advance</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Narendra</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

<br>--------------------------------------------------------------<br>Dexcel Electronics Designs (P) Ltd., Bangalore, India<br>
------=_NextPart_000_0005_01C1A018.96A639E0--


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



From megaco-admin@ietf.org  Fri Jan 18 01:46:50 2002
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 BAA23945
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 01:46:49 -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 BAA25890;
	Fri, 18 Jan 2002 01:35:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25864
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:35:33 -0500 (EST)
Received: from mailFA8.rediffmail.com ([202.54.124.153])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA23780
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:35:30 -0500 (EST)
Received: (qmail 28617 invoked by uid 510); 18 Jan 2002 06:36:29 -0000
Date: 18 Jan 2002 06:36:29 -0000
Message-ID: <20020118063629.28616.qmail@mailFA8.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 06:36:29 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA25865
Subject: [Megaco] DOUBT ABUOT ACK
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


hi

   Every transaction request should be responded with ACK/REP/PEND. But in the example given in RFC, 
places where ACK is expected also reply is sent. Why is it happened here so -  or is that the correct sequence .. ?

sree 


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


From daemon@optimus.ietf.org  Fri Jan 18 01:46:50 2002
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 BAA23955
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 01:46:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA26177
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 01:46:51 -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 BAA25890;
	Fri, 18 Jan 2002 01:35:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25864
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:35:33 -0500 (EST)
Received: from mailFA8.rediffmail.com ([202.54.124.153])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA23780
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:35:30 -0500 (EST)
Received: (qmail 28617 invoked by uid 510); 18 Jan 2002 06:36:29 -0000
Date: 18 Jan 2002 06:36:29 -0000
Message-ID: <20020118063629.28616.qmail@mailFA8.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 06:36:29 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA25865
Subject: [Megaco] DOUBT ABUOT ACK
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


hi

   Every transaction request should be responded with ACK/REP/PEND. But in the example given in RFC, 
places where ACK is expected also reply is sent. Why is it happened here so -  or is that the correct sequence .. ?

sree 


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



From megaco-admin@ietf.org  Fri Jan 18 02:06:12 2002
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 CAA02231
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:06:12 -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 BAA26348;
	Fri, 18 Jan 2002 01:57: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 BAA26315
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:57:57 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24125
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:57:54 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0I6vsK17444;
	Fri, 18 Jan 2002 07:57:54 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id HAA27121; Fri, 18 Jan 2002 07:57:48 +0100
Message-ID: <3C47C76E.45E057D1@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 08:57:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sree gk <sgk73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] **SERVICE CHANGE REASON
References: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Annex L.

Regards,

Christer Holmberg
Ericsson Finland

sree gk wrote:
> 
> hi
> 
>    Where do I get the list of service change reasons .. ? RFC doesn't talk about that.
> 
> sree
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Fri Jan 18 02:06:13 2002
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 CAA02239
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:06:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA27204
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 02:06:14 -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 BAA26348;
	Fri, 18 Jan 2002 01:57: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 BAA26315
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 01:57:57 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24125
	for <megaco@ietf.org>; Fri, 18 Jan 2002 01:57:54 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0I6vsK17444;
	Fri, 18 Jan 2002 07:57:54 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id HAA27121; Fri, 18 Jan 2002 07:57:48 +0100
Message-ID: <3C47C76E.45E057D1@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 08:57:50 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sree gk <sgk73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] **SERVICE CHANGE REASON
References: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Annex L.

Regards,

Christer Holmberg
Ericsson Finland

sree gk wrote:
> 
> hi
> 
>    Where do I get the list of service change reasons .. ? RFC doesn't talk about that.
> 
> sree
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Fri Jan 18 02:08:45 2002
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 CAA02576
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:08:44 -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 CAA26833;
	Fri, 18 Jan 2002 02:01:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26791
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:00:58 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25385
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:00:56 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id XAA25749;
	Thu, 17 Jan 2002 23:00:57 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 18 Jan 2002 07:00:57 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id XAA23014;
	Thu, 17 Jan 2002 23:00:55 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id XAA01466;
	Thu, 17 Jan 2002 23:00:54 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id MAA29636;
	Fri, 18 Jan 2002 12:30:01 +0530 (IST)
Message-ID: <3C47C74B.BA4AF005@lucent.com>
Date: Fri, 18 Jan 2002 12:27:15 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: sree gk <sgk73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] **SERVICE CHANGE REASON
References: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Annex L has the listing of all  reasons and cause codes.
-Shambhu

sree gk wrote:
> 
> hi
> 
>    Where do I get the list of service change reasons .. ? RFC doesn't talk about that.
> 
> sree
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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


From daemon@optimus.ietf.org  Fri Jan 18 02:08:45 2002
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 CAA02587
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:08:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA27324
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 02:08:46 -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 CAA26833;
	Fri, 18 Jan 2002 02:01:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26791
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:00:58 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25385
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:00:56 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id XAA25749;
	Thu, 17 Jan 2002 23:00:57 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 18 Jan 2002 07:00:57 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id XAA23014;
	Thu, 17 Jan 2002 23:00:55 -0800 (PST)
Received: from india.ascend.com (h135-254-196-198.outland.lucent.com [135.254.196.198])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id XAA01466;
	Thu, 17 Jan 2002 23:00:54 -0800 (PST)
Received: from lucent.com (aztec.india.ascend.com [135.254.196.32])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id MAA29636;
	Fri, 18 Jan 2002 12:30:01 +0530 (IST)
Message-ID: <3C47C74B.BA4AF005@lucent.com>
Date: Fri, 18 Jan 2002 12:27:15 +0530
From: Shambhu Dayal Rai <sdrai@lucent.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 i86pc)
X-Accept-Language: en
MIME-Version: 1.0
To: sree gk <sgk73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] **SERVICE CHANGE REASON
References: <20020118040743.13295.qmail@mailweb13.rediffmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Annex L has the listing of all  reasons and cause codes.
-Shambhu

sree gk wrote:
> 
> hi
> 
>    Where do I get the list of service change reasons .. ? RFC doesn't talk about that.
> 
> sree
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

-- 
-------------------------------------------------------------------
Shambhu Dayal Rai                              sdrai@lucent.com 
Infosys - India SQA Team              91-80-8520362 Ext. : 6561
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Fri Jan 18 02:20:49 2002
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 CAA02795
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:20:44 -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 CAA27024;
	Fri, 18 Jan 2002 02:04:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26995
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:04:06 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29275
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:04:03 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0I743J28846;
	Fri, 18 Jan 2002 08:04:03 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id IAA27498; Fri, 18 Jan 2002 08:03:58 +0100
Message-ID: <3C47C8E0.81FD02DE@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 09:04:00 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I mentioned that several of us have been discussing additional text for
>Multiplex Descriptors.  I have placed the proposed text as marked up changes
>in the Megaco FTP site.  According to your taste, you can download
>ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
>x64K.doc or ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
>x64K.pdf
> 
>Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
>proposed text needs a further update.  The supporting bearers contained by a
>multiplexing termination can be ephemeral as well as physical.  However, I
>believe it would be essential that any ephemrals mentioned in a MUX
>descriptor already exist in the context, since their properties are probably
>not directly inferrable from those of the multiplexing termination.

Well, it depends on how it will be done. If something (a RTP
termination, for example) is added LATER, that part of the MUX
properties could be unspecified first, and then maybe changed using
MODIFY when the RTP termination is added... But, before going into that,
I think we should decided how to do the mapping in the first place.

Thanks for your comments!

Regards,

Christer Holmberg
Ericsson Finland

> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Fri Jan 18 02:20:50 2002
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 CAA02808
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:20:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA27810
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 02:20:51 -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 CAA27024;
	Fri, 18 Jan 2002 02:04:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26995
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:04:06 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29275
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:04:03 -0500 (EST)
Received: from madrid.ericsson.se (madrid.es.eu.ericsson.se [159.107.53.220])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0I743J28846;
	Fri, 18 Jan 2002 08:04:03 +0100 (MET)
Received: from lmf.ericsson.se by madrid.ericsson.se (SMI-8.6/SMI-SVR4)
	id IAA27498; Fri, 18 Jan 2002 08:03:58 +0100
Message-ID: <3C47C8E0.81FD02DE@lmf.ericsson.se>
Date: Fri, 18 Jan 2002 09:04:00 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I mentioned that several of us have been discussing additional text for
>Multiplex Descriptors.  I have placed the proposed text as marked up changes
>in the Megaco FTP site.  According to your taste, you can download
>ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
>x64K.doc or ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
>x64K.pdf
> 
>Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
>proposed text needs a further update.  The supporting bearers contained by a
>multiplexing termination can be ephemeral as well as physical.  However, I
>believe it would be essential that any ephemrals mentioned in a MUX
>descriptor already exist in the context, since their properties are probably
>not directly inferrable from those of the multiplexing termination.

Well, it depends on how it will be done. If something (a RTP
termination, for example) is added LATER, that part of the MUX
properties could be unspecified first, and then maybe changed using
MODIFY when the RTP termination is added... But, before going into that,
I think we should decided how to do the mapping in the first place.

Thanks for your comments!

Regards,

Christer Holmberg
Ericsson Finland

> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Fri Jan 18 03:04:28 2002
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 DAA03473
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 03:04:28 -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 CAA28919;
	Fri, 18 Jan 2002 02:56:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA28891
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:56:14 -0500 (EST)
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03307
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:56:11 -0500 (EST)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by david.siemens.de (8.11.6/8.11.6) with ESMTP id g0I7uBO08062
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:56:12 +0100 (MET)
Received: from poseidon.siemens.gr (poseidon.siemens.gr [141.29.40.250])
	by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id g0I7uAk29796
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:56:11 +0100 (MET)
Received: by poseidon.siemens.gr with Internet Mail Service (5.5.2653.19)
	id <CVYT0JZ5>; Fri, 18 Jan 2002 09:56:10 +0200
Message-ID: <2ECFB18E44E2D511A0C80002B32B056B2D3EBC@PROMETHEUS>
From: Stefanioros Nikolaos <Nikolaos.Stefanioros@siemens.gr>
To: megaco@ietf.org
Date: Fri, 18 Jan 2002 09:56:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] Question regarding ServiceChange command.
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

Hi everybody,

could someone give me an answer to the following question?

In case of "cold start", the MG sends a ServiceChange command towards its
primary MGC. This ServiceChange command should be sent to the default port
of MGC (2944 for Text encoded or 2945 for Binary encoded messages) or to any
other port of MGC?

Regards.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 942 980181
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



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


From daemon@optimus.ietf.org  Fri Jan 18 03:04:29 2002
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 DAA03484
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 03:04:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA29456
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 03:04:30 -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 CAA28919;
	Fri, 18 Jan 2002 02:56:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA28891
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 02:56:14 -0500 (EST)
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03307
	for <megaco@ietf.org>; Fri, 18 Jan 2002 02:56:11 -0500 (EST)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by david.siemens.de (8.11.6/8.11.6) with ESMTP id g0I7uBO08062
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:56:12 +0100 (MET)
Received: from poseidon.siemens.gr (poseidon.siemens.gr [141.29.40.250])
	by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id g0I7uAk29796
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:56:11 +0100 (MET)
Received: by poseidon.siemens.gr with Internet Mail Service (5.5.2653.19)
	id <CVYT0JZ5>; Fri, 18 Jan 2002 09:56:10 +0200
Message-ID: <2ECFB18E44E2D511A0C80002B32B056B2D3EBC@PROMETHEUS>
From: Stefanioros Nikolaos <Nikolaos.Stefanioros@siemens.gr>
To: megaco@ietf.org
Date: Fri, 18 Jan 2002 09:56:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] Question regarding ServiceChange command.
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

Hi everybody,

could someone give me an answer to the following question?

In case of "cold start", the MG sends a ServiceChange command towards its
primary MGC. This ServiceChange command should be sent to the default port
of MGC (2944 for Text encoded or 2945 for Binary encoded messages) or to any
other port of MGC?

Regards.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 942 980181
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



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



From megaco-admin@ietf.org  Fri Jan 18 06:16:00 2002
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 GAA06450
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 06:16:00 -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 GAA05558;
	Fri, 18 Jan 2002 06:08:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA05467
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 06:08:30 -0500 (EST)
Received: from ipgen-india.com (lan-202-144-91-188.maa.sify.net [202.144.91.188] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06273
	for <megaco@ietf.org>; Fri, 18 Jan 2002 06:08:22 -0500 (EST)
Received: from ipgen-india.com [192.168.1.253] by ipgen-india.com [192.168.1.15]
	with SMTP (MDaemon.v3.5.2.R)
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:35:16 -0600
Message-ID: <3C48A642.DE6B961B@ipgen-india.com>
Date: Fri, 18 Jan 2002 16:48:34 -0600
From: J K Ramchandra <jkr@ipgen-india.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com, Christian.Groves@ericsson.com.au,
        taylor@nortelnetworks.com, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <026f01c19fff$5e28bed0$d401a8c0@keshav1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.1.253
X-Return-Path: jkr@ipgen-india.com
X-MDaemon-Deliver-To: megaco@ietf.org
Content-Transfer-Encoding: 7bit
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: 7bit

Hi all,

I think we are heading somewhere here. If I remember correctly, the sole purpose
of responseAck is to reduce the overall memory consumption. The entity sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till long
timer to clean up these buffer. Normally, the response ack is appended with the
next message sent towards that destination (MG/MGC). By setting immAckRequired
flag in the response, it is requesting to send it immediately (not waiting till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after one
or more transaction Pending was sent), I believe, is due to the fact that this
specific transaction has already  active for quite some time and better to be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will retransmit
the response only when the repeated request is received. This is the case with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN

> ----- Original Message -----
> From: <vibansal@hss.hns.com>
> To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
> Cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>; "Tom-PT
> Taylor" <taylor@nortelnetworks.com>; <megaco@ietf.org>
> Sent: Thursday, January 17, 2002 10:30 AM
> Subject: RE: [Megaco] Doubt regarding immAckRequired field.
>
> >
> >
> >
> > Hi Marcello, All
> >
> > Before actually phrasing the paragragh can we discuss this issue some more
> to
> > make it even clearer. We should remember that we need to handle the LONG
> timer
> > also. Here is the suggested behavior for the entity sending the
> Transaction
> > response containing immAckRequired field
> >
> > 1. The entity sending response with immAckRequired field will start
> > retransmission timers as per section D.1.5. It shall not start the long
> timer.
> >
> > 2.If the acknowledgement comes, the entity sending response will stop
> > retransmitting the response and start the long timer for the remaining
> duration.
> >
> > 3.If the acknowledgement does not come within N retries (or  time elapsed
> since
> > the sending of the initial datagram is no greater than T-MAX), then entity
> > sending response shall assume that the peer entity has gone down and would
> start
> > the recovery action as suggested in section 11.4/11.5 of rfc 3015. It
> shall stop
> > retransmitting the response and it start the long timer for that
> transaction
> > response for the remaining duration.
> >
> > With this we have tried to avoid running two timers for the same
> transaction.
> >
> > Regards
> > Vivek
> > Hughes Software Systems
> >
> >
> >
> >
> >
> >
> >
> > "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on
> 01/10/2002
> > 09:06:48 PM
> >
> > To:   Vivek Bansal/HSS@HSS
> > cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT
> Taylor
> >       <taylor@nortelnetworks.com>, megaco@ietf.org
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> >
> >
> >
> > Hi Vivek,
> >
> > how does it sound this (addition between <SA> and <EA>?
> >
> > H.248, Section D.1.4 Provisional response:
> > ...
> > Upon receipt of a final response following receipt of provisional
> responses, an
> > immediate confirmation shall be sent, and normal repetition timers shall
> be used
> > thereafter.  An entity that sends a provisional response, SHALL include
> the
> > immAckRequired field in the ensuing final response, indicating that an
> immediate
> > confirmation is expected.
> > <SA>If an immediate confirmation is not received, the entity that sent the
> final
> > response will retransmit the final response including the immAckRequired
> field
> > (with exponential backoff) until a confirmation is received.<EA> Receipt
> of a
> > Transaction Pending after receipt of a reply shall be ignored.
> >
> > If it sounds ok I guess this should be also added to the IG.
> >
> > Regards,
> > Marcello
> >
> > -----Original Message-----
> > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > Sent: Thursday, January 10, 2002 1:04 AM
> > To: vibansal@hss.hns.com
> > Cc: Tom-PT Taylor; megaco@ietf.org
> > Subject: Re: [Megaco] Doubt regarding immAckRequired field.
> >
> >
> > G'Day Vivek,
> >
> > I understood that its not mentioned what I was asking for was a wording
> > proposal to D.1.4 or whereever it is relevant to assist the IG and v2
> > editors.
> >
> > Regards, Christian
> >
> > vibansal@hss.hns.com wrote:
> > >
> > > Hi Christian
> > >
> > > Regarding the Immediate ACK nothing has been mentioned in the protocol.
> I had
> > > asked if the entity sending response sends the response with
> immAckRequired
> > > field, and the entity receiving the response does not send back ACK,
> then what
> > > should entity sending the response do. To handle this Tom had suggested
> that
> > the
> > > entity sending rerponse will retransmit the response till it gets the
> ACK of
> > it.
> > > And this solutions seems fine, otherwise the presence of immAckRequired
> field
> > in
> > > the message will not make any difference.
> > >
> > > This is all that I wanted to be updated in V2.
> > >
> > > Regards
> > > Vivek
> > >
> > > Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002
> 08:27:43 AM
> > >
> > > To:   Vivek Bansal/HSS@HSS
> > > cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> > >
> > > Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> > >
> > > G'Day Vivek,
> > >
> > > What exactly do you propose to update in v2?
> > >
> > > Regards, Christian
> > >
> > > vibansal@hss.hns.com wrote:
> > > >
> > > > If this is the case, then we need update the same in the v2 draft.
> > > >
> > > > Regards
> > > > Vivek
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> > > >
> > > > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > > > cc:
> > > >
> > > > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> > > >
> > > > The immAckRequired flag was introduced because without it a protocol
> glitch
> > > > was possible, so what you postulate is not a nice situation.  Anyway,
> to
> > > > answer your question, I would say that retransmission of the final
> response
> > > > (with exponential backoff) is necessary until an acknowledgement is
> > > > received.
> > > >
> > > > -----Original Message-----
> > > > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > > > Sent: Sunday, December 30, 2001 8:23 AM
> > > > To: megaco@ietf.org
> > > > Subject: [Megaco] Doubt regarding immAckRequired field.
> > > >
> > > > Hi
> > > >
> > > > I have a doubt regarding immAckRequired field.
> > > >
> > > > Section D.1.4 says
> > > >
> > > > "An entity that sends a provisional response, SHALL include the
> > > > immAckRequired
> > > > field in the ensuing final response, indicating that an immediate
> > > > confirmation
> > > > is expected."
> > > >
> > > > Now what would happen, if the entity receiving the final response with
> > > > immAckRequired field, does not send the immediate confirmation? In
> this case
> > > > do
> > > > we need to retransmit the response till we get the confirmation?
> > > >
> > > > Please clarify.
> > > >
> > > > Regards
> > > > Vivek
> > > >
> > > > _______________________________________________
> > > > 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
> >
> >
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Fri Jan 18 06:16:00 2002
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 GAA06460
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 06:16:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA05752
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 06:16:04 -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 GAA05558;
	Fri, 18 Jan 2002 06:08:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA05467
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 06:08:30 -0500 (EST)
Received: from ipgen-india.com (lan-202-144-91-188.maa.sify.net [202.144.91.188] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06273
	for <megaco@ietf.org>; Fri, 18 Jan 2002 06:08:22 -0500 (EST)
Received: from ipgen-india.com [192.168.1.253] by ipgen-india.com [192.168.1.15]
	with SMTP (MDaemon.v3.5.2.R)
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:35:16 -0600
Message-ID: <3C48A642.DE6B961B@ipgen-india.com>
Date: Fri, 18 Jan 2002 16:48:34 -0600
From: J K Ramchandra <jkr@ipgen-india.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vibansal@hss.hns.com, Christian.Groves@ericsson.com.au,
        taylor@nortelnetworks.com, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <026f01c19fff$5e28bed0$d401a8c0@keshav1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.1.253
X-Return-Path: jkr@ipgen-india.com
X-MDaemon-Deliver-To: megaco@ietf.org
Content-Transfer-Encoding: 7bit
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: 7bit

Hi all,

I think we are heading somewhere here. If I remember correctly, the sole purpose
of responseAck is to reduce the overall memory consumption. The entity sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till long
timer to clean up these buffer. Normally, the response ack is appended with the
next message sent towards that destination (MG/MGC). By setting immAckRequired
flag in the response, it is requesting to send it immediately (not waiting till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after one
or more transaction Pending was sent), I believe, is due to the fact that this
specific transaction has already  active for quite some time and better to be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will retransmit
the response only when the repeated request is received. This is the case with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN

> ----- Original Message -----
> From: <vibansal@hss.hns.com>
> To: "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se>
> Cc: "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>; "Tom-PT
> Taylor" <taylor@nortelnetworks.com>; <megaco@ietf.org>
> Sent: Thursday, January 17, 2002 10:30 AM
> Subject: RE: [Megaco] Doubt regarding immAckRequired field.
>
> >
> >
> >
> > Hi Marcello, All
> >
> > Before actually phrasing the paragragh can we discuss this issue some more
> to
> > make it even clearer. We should remember that we need to handle the LONG
> timer
> > also. Here is the suggested behavior for the entity sending the
> Transaction
> > response containing immAckRequired field
> >
> > 1. The entity sending response with immAckRequired field will start
> > retransmission timers as per section D.1.5. It shall not start the long
> timer.
> >
> > 2.If the acknowledgement comes, the entity sending response will stop
> > retransmitting the response and start the long timer for the remaining
> duration.
> >
> > 3.If the acknowledgement does not come within N retries (or  time elapsed
> since
> > the sending of the initial datagram is no greater than T-MAX), then entity
> > sending response shall assume that the peer entity has gone down and would
> start
> > the recovery action as suggested in section 11.4/11.5 of rfc 3015. It
> shall stop
> > retransmitting the response and it start the long timer for that
> transaction
> > response for the remaining duration.
> >
> > With this we have tried to avoid running two timers for the same
> transaction.
> >
> > Regards
> > Vivek
> > Hughes Software Systems
> >
> >
> >
> >
> >
> >
> >
> > "Marcello Pantaleo (EED)" <Marcello.Pantaleo@eed.ericsson.se> on
> 01/10/2002
> > 09:06:48 PM
> >
> > To:   Vivek Bansal/HSS@HSS
> > cc:   "Christian Groves (EAA)" <Christian.Groves@ericsson.com.au>, Tom-PT
> Taylor
> >       <taylor@nortelnetworks.com>, megaco@ietf.org
> >
> > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> >
> >
> >
> >
> > Hi Vivek,
> >
> > how does it sound this (addition between <SA> and <EA>?
> >
> > H.248, Section D.1.4 Provisional response:
> > ...
> > Upon receipt of a final response following receipt of provisional
> responses, an
> > immediate confirmation shall be sent, and normal repetition timers shall
> be used
> > thereafter.  An entity that sends a provisional response, SHALL include
> the
> > immAckRequired field in the ensuing final response, indicating that an
> immediate
> > confirmation is expected.
> > <SA>If an immediate confirmation is not received, the entity that sent the
> final
> > response will retransmit the final response including the immAckRequired
> field
> > (with exponential backoff) until a confirmation is received.<EA> Receipt
> of a
> > Transaction Pending after receipt of a reply shall be ignored.
> >
> > If it sounds ok I guess this should be also added to the IG.
> >
> > Regards,
> > Marcello
> >
> > -----Original Message-----
> > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > Sent: Thursday, January 10, 2002 1:04 AM
> > To: vibansal@hss.hns.com
> > Cc: Tom-PT Taylor; megaco@ietf.org
> > Subject: Re: [Megaco] Doubt regarding immAckRequired field.
> >
> >
> > G'Day Vivek,
> >
> > I understood that its not mentioned what I was asking for was a wording
> > proposal to D.1.4 or whereever it is relevant to assist the IG and v2
> > editors.
> >
> > Regards, Christian
> >
> > vibansal@hss.hns.com wrote:
> > >
> > > Hi Christian
> > >
> > > Regarding the Immediate ACK nothing has been mentioned in the protocol.
> I had
> > > asked if the entity sending response sends the response with
> immAckRequired
> > > field, and the entity receiving the response does not send back ACK,
> then what
> > > should entity sending the response do. To handle this Tom had suggested
> that
> > the
> > > entity sending rerponse will retransmit the response till it gets the
> ACK of
> > it.
> > > And this solutions seems fine, otherwise the presence of immAckRequired
> field
> > in
> > > the message will not make any difference.
> > >
> > > This is all that I wanted to be updated in V2.
> > >
> > > Regards
> > > Vivek
> > >
> > > Christian Groves <Christian.Groves@ericsson.com.au> on 01/09/2002
> 08:27:43 AM
> > >
> > > To:   Vivek Bansal/HSS@HSS
> > > cc:   Tom-PT Taylor <taylor@nortelnetworks.com>, megaco@ietf.org
> > >
> > > Subject:  Re: [Megaco] Doubt regarding immAckRequired field.
> > >
> > > G'Day Vivek,
> > >
> > > What exactly do you propose to update in v2?
> > >
> > > Regards, Christian
> > >
> > > vibansal@hss.hns.com wrote:
> > > >
> > > > If this is the case, then we need update the same in the v2 draft.
> > > >
> > > > Regards
> > > > Vivek
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/03/2002 01:06:02 AM
> > > >
> > > > To:   Vivek Bansal/HSS@HSS, megaco@ietf.org
> > > > cc:
> > > >
> > > > Subject:  RE: [Megaco] Doubt regarding immAckRequired field.
> > > >
> > > > The immAckRequired flag was introduced because without it a protocol
> glitch
> > > > was possible, so what you postulate is not a nice situation.  Anyway,
> to
> > > > answer your question, I would say that retransmission of the final
> response
> > > > (with exponential backoff) is necessary until an acknowledgement is
> > > > received.
> > > >
> > > > -----Original Message-----
> > > > From: vibansal@hss.hns.com [mailto:vibansal@hss.hns.com]
> > > > Sent: Sunday, December 30, 2001 8:23 AM
> > > > To: megaco@ietf.org
> > > > Subject: [Megaco] Doubt regarding immAckRequired field.
> > > >
> > > > Hi
> > > >
> > > > I have a doubt regarding immAckRequired field.
> > > >
> > > > Section D.1.4 says
> > > >
> > > > "An entity that sends a provisional response, SHALL include the
> > > > immAckRequired
> > > > field in the ensuing final response, indicating that an immediate
> > > > confirmation
> > > > is expected."
> > > >
> > > > Now what would happen, if the entity receiving the final response with
> > > > immAckRequired field, does not send the immediate confirmation? In
> this case
> > > > do
> > > > we need to retransmit the response till we get the confirmation?
> > > >
> > > > Please clarify.
> > > >
> > > > Regards
> > > > Vivek
> > > >
> > > > _______________________________________________
> > > > 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
> >
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Fri Jan 18 08:01:36 2002
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 IAA09115
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:01:36 -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 HAA10190;
	Fri, 18 Jan 2002 07:48:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10159
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 07:48:29 -0500 (EST)
Received: from mailFA3.rediffmail.com ([202.54.124.148])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA08735
	for <megaco@ietf.org>; Fri, 18 Jan 2002 07:48:25 -0500 (EST)
Received: (qmail 25673 invoked by uid 510); 18 Jan 2002 12:49:35 -0000
Date: 18 Jan 2002 12:49:35 -0000
Message-ID: <20020118124935.25671.qmail@mailFA3.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 12:49:35 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA10160
Subject: [Megaco] ***In CASE of faulti address .. ?
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


Hi all

 I have a doubt about a sequence in MG side. In case MG detects a faulty number which 1user has dialed ( no match in dial plan ). Then how should MG react to such a case. ? Should he intimate MGc about the faulti number detection .. ?

regs
sree 


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


From daemon@optimus.ietf.org  Fri Jan 18 08:01:37 2002
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 IAA09126
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:01:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA10832
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 08:01:39 -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 HAA10190;
	Fri, 18 Jan 2002 07:48:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10159
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 07:48:29 -0500 (EST)
Received: from mailFA3.rediffmail.com ([202.54.124.148])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA08735
	for <megaco@ietf.org>; Fri, 18 Jan 2002 07:48:25 -0500 (EST)
Received: (qmail 25673 invoked by uid 510); 18 Jan 2002 12:49:35 -0000
Date: 18 Jan 2002 12:49:35 -0000
Message-ID: <20020118124935.25671.qmail@mailFA3.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 18 Jan 2002 12:49:35 -0000
MIME-Version: 1.0
From: "sree  gk" <sgk73@rediffmail.com>
Reply-To: "sree  gk" <sgk73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA10160
Subject: [Megaco] ***In CASE of faulti address .. ?
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


Hi all

 I have a doubt about a sequence in MG side. In case MG detects a faulty number which 1user has dialed ( no match in dial plan ). Then how should MG react to such a case. ? Should he intimate MGc about the faulti number detection .. ?

regs
sree 


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



From megaco-admin@ietf.org  Fri Jan 18 08:39:14 2002
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 IAA10150
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:39:13 -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 IAA11471;
	Fri, 18 Jan 2002 08:26:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11442
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 08:26:12 -0500 (EST)
Received: from mta020.verizon.net (mta020pub.verizon.net [206.46.170.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09805
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:26:11 -0500 (EST)
Received: from matt.verizon.net ([213.228.29.225]) by mta020.verizon.net
          (InterMail vM.5.01.04.02 201-253-122-122-102-20011128) with ESMTP
          id <20020118132609.IOA9070.mta020.verizon.net@matt.verizon.net>;
          Fri, 18 Jan 2002 07:26:09 -0600
Message-Id: <5.1.0.14.2.20020118052320.0213c570@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 18 Jan 2002 05:25:30 -0800
To: Narendra Babu <narendra@dexceldesigns.com>, <megaco@ietf.org>
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: Re: [Megaco] Regarding IPsec and interim AH
In-Reply-To: <000801c19fea$7cfd4020$12010a64@domain.dexceldesigns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


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


From daemon@optimus.ietf.org  Fri Jan 18 08:39:14 2002
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 IAA10159
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:39:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12309
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 08:39:15 -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 IAA11471;
	Fri, 18 Jan 2002 08:26:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11442
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 08:26:12 -0500 (EST)
Received: from mta020.verizon.net (mta020pub.verizon.net [206.46.170.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09805
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:26:11 -0500 (EST)
Received: from matt.verizon.net ([213.228.29.225]) by mta020.verizon.net
          (InterMail vM.5.01.04.02 201-253-122-122-102-20011128) with ESMTP
          id <20020118132609.IOA9070.mta020.verizon.net@matt.verizon.net>;
          Fri, 18 Jan 2002 07:26:09 -0600
Message-Id: <5.1.0.14.2.20020118052320.0213c570@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 18 Jan 2002 05:25:30 -0800
To: Narendra Babu <narendra@dexceldesigns.com>, <megaco@ietf.org>
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: Re: [Megaco] Regarding IPsec and interim AH
In-Reply-To: <000801c19fea$7cfd4020$12010a64@domain.dexceldesigns.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


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



From megaco-admin@ietf.org  Fri Jan 18 08:58:42 2002
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 IAA11022
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:58:41 -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 IAA12539;
	Fri, 18 Jan 2002 08:46:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12507
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 08:46:15 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10506
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:46:11 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0IDjvu23462
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:45:57 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5886af822aac158f2515f@esvir05nok.ntc.nokia.com> for <megaco@ietf.org>;
 Fri, 18 Jan 2002 15:46:11 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Fri, 18 Jan 2002 15:46:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 18 Jan 2002 15:46:10 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D280@esebe004.NOE.Nokia.com>
Thread-Topic: [Megaco] Regarding IPsec and interim AH
Thread-Index: AcGgJCfSBmiRPhgST/G0et0LH4ogaQAAcoLg
From: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 18 Jan 2002 13:46:11.0153 (UTC) FILETIME=[7D1FEC10:01C1A026]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA12508
Subject: [Megaco] question about AuditDescriptor in v2
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

Hi,

Can AuditDescriptor have multiple occurrence of any particular
indAudauditReturnParameter ? for e.g. can there be multiple
indAudMediaDescriptor within an AuditDescriptor ?

Thanks in advance,
sunesh

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


From daemon@optimus.ietf.org  Fri Jan 18 08:58:42 2002
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 IAA11032
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 08:58:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12950
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 08:58:43 -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 IAA12539;
	Fri, 18 Jan 2002 08:46:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12507
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 08:46:15 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10506
	for <megaco@ietf.org>; Fri, 18 Jan 2002 08:46:11 -0500 (EST)
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0IDjvu23462
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:45:57 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5886af822aac158f2515f@esvir05nok.ntc.nokia.com> for <megaco@ietf.org>;
 Fri, 18 Jan 2002 15:46:11 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Fri, 18 Jan 2002 15:46:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 18 Jan 2002 15:46:10 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09D280@esebe004.NOE.Nokia.com>
Thread-Topic: [Megaco] Regarding IPsec and interim AH
Thread-Index: AcGgJCfSBmiRPhgST/G0et0LH4ogaQAAcoLg
From: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 18 Jan 2002 13:46:11.0153 (UTC) FILETIME=[7D1FEC10:01C1A026]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA12508
Subject: [Megaco] question about AuditDescriptor in v2
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

Hi,

Can AuditDescriptor have multiple occurrence of any particular
indAudauditReturnParameter ? for e.g. can there be multiple
indAudMediaDescriptor within an AuditDescriptor ?

Thanks in advance,
sunesh

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



From megaco-admin@ietf.org  Fri Jan 18 11:10:14 2002
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 LAA16608
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 11:10:14 -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 KAA19282;
	Fri, 18 Jan 2002 10:58:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19254
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 10:57:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15798
	for <megaco@ietf.org>; Fri, 18 Jan 2002 10:57:56 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IFvMf25086;
	Fri, 18 Jan 2002 10:57:22 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IFvKO06170;
	Fri, 18 Jan 2002 10:57:20 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZWMS7>; Fri, 18 Jan 2002 10:57:20 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE8C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] **SERVICE CHANGE REASON
Date: Fri, 18 Jan 2002 10:57:20 -0500
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

Look near the end of the IANA registry at
http://www.iana.org/assignments/megaco-h248



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Thursday, January 17, 2002 11:08 PM
To: megaco@ietf.org
Subject: [Megaco] **SERVICE CHANGE REASON



hi

   Where do I get the list of service change reasons .. ? RFC doesn't talk
about that.

sree 


_______________________________________________
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


From daemon@optimus.ietf.org  Fri Jan 18 11:10:15 2002
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 LAA16615
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 11:10:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20331
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 11:10: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 KAA19282;
	Fri, 18 Jan 2002 10:58:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19254
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 10:57:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15798
	for <megaco@ietf.org>; Fri, 18 Jan 2002 10:57:56 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IFvMf25086;
	Fri, 18 Jan 2002 10:57:22 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IFvKO06170;
	Fri, 18 Jan 2002 10:57:20 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZWMS7>; Fri, 18 Jan 2002 10:57:20 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE8C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] **SERVICE CHANGE REASON
Date: Fri, 18 Jan 2002 10:57:20 -0500
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

Look near the end of the IANA registry at
http://www.iana.org/assignments/megaco-h248



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Thursday, January 17, 2002 11:08 PM
To: megaco@ietf.org
Subject: [Megaco] **SERVICE CHANGE REASON



hi

   Where do I get the list of service change reasons .. ? RFC doesn't talk
about that.

sree 


_______________________________________________
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



From megaco-admin@ietf.org  Fri Jan 18 14:13:07 2002
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 OAA23899
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 14:13:05 -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 NAA28961;
	Fri, 18 Jan 2002 13:55:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28903
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 13:55:09 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23250
	for <megaco@ietf.org>; Fri, 18 Jan 2002 13:55:06 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IIsHc28718;
	Fri, 18 Jan 2002 13:54:17 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id NAA15329;
	Fri, 18 Jan 2002 13:54:05 -0500 (EST)
Message-ID: <3C486E95.AED0052@lucent.com>
Date: Fri, 18 Jan 2002 13:51:01 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco ietf <megaco@ietf.org>, Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
References: <3C4639D2.9703DAA6@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------2114547AD9EF17BD72B9EE79"
Subject: [Megaco] Re: Open Issue #1: IG Resolution on : g/sc SigID list
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

This is a multi-part message in MIME format.
--------------2114547AD9EF17BD72B9EE79
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

There are several issues that have arisen on the mailing list that I would like
to see resolved for the next IG and before any H.248v2 is issued.  The one
Christian raises is one of these.  I would like to assign numbers to help us
track these.  Please include the open issue number in the subject line of any
responses to these issues.  We'll call this one Open Issue 1.

Christian Groves wrote:

> G'Day all,
>
> Back in September there was some discussion on the encoding of g/sc
> SigID. We sorted out the correct definition of sub-list but
> unfortunately I believe that we didn't finish of the discussion on the
> encoding of g/sc.
>
> Below is a proposed resolution to start off the discussions. Flame away.
>
> x.xx Signal List Completion Encoding
>
> Description:    In the Signal completion event it is unclear how the signal
> identity is encoded. Firstly the type: list is not a standard type
> defined in the packages template. Secondly it is unclear how to encode
> the value of the parameter. A simple solution is proposed to carry only
> the signal identity of the completed signal in pkgdname format. If a
> signal is part of a signal list it is indicated by the signal list
> identity parameter.
>
> Reference:      <to be filled in by editor>
>  [Begin Correction]
> E.1.2 Events
> …
> Signal Identity
> ParameterID:  SigID (0x0001)
> This parameter identifies the signals which have terminated.
> Type: octet string
> Possible values: a signal which has terminated.  A signal shall be
> identified using the pkgdName syntax without wildcarding. For a signal
> that is contained in a signal list the signal list identity parameter
> should also be returned indicating the appropriate list.
>
> [End Correction]
>
> Regards, Christian

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------2114547AD9EF17BD72B9EE79
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------2114547AD9EF17BD72B9EE79--


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


From daemon@optimus.ietf.org  Fri Jan 18 14:13:13 2002
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 OAA23909
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 14:13:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA00023
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 14:13:10 -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 NAA28961;
	Fri, 18 Jan 2002 13:55:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28903
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 13:55:09 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23250
	for <megaco@ietf.org>; Fri, 18 Jan 2002 13:55:06 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IIsHc28718;
	Fri, 18 Jan 2002 13:54:17 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id NAA15329;
	Fri, 18 Jan 2002 13:54:05 -0500 (EST)
Message-ID: <3C486E95.AED0052@lucent.com>
Date: Fri, 18 Jan 2002 13:51:01 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco ietf <megaco@ietf.org>, Tom-PT Taylor <taylor@NORTELNETWORKS.COM>
References: <3C4639D2.9703DAA6@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------2114547AD9EF17BD72B9EE79"
Subject: [Megaco] Re: Open Issue #1: IG Resolution on : g/sc SigID list
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

This is a multi-part message in MIME format.
--------------2114547AD9EF17BD72B9EE79
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

There are several issues that have arisen on the mailing list that I would like
to see resolved for the next IG and before any H.248v2 is issued.  The one
Christian raises is one of these.  I would like to assign numbers to help us
track these.  Please include the open issue number in the subject line of any
responses to these issues.  We'll call this one Open Issue 1.

Christian Groves wrote:

> G'Day all,
>
> Back in September there was some discussion on the encoding of g/sc
> SigID. We sorted out the correct definition of sub-list but
> unfortunately I believe that we didn't finish of the discussion on the
> encoding of g/sc.
>
> Below is a proposed resolution to start off the discussions. Flame away.
>
> x.xx Signal List Completion Encoding
>
> Description:    In the Signal completion event it is unclear how the signal
> identity is encoded. Firstly the type: list is not a standard type
> defined in the packages template. Secondly it is unclear how to encode
> the value of the parameter. A simple solution is proposed to carry only
> the signal identity of the completed signal in pkgdname format. If a
> signal is part of a signal list it is indicated by the signal list
> identity parameter.
>
> Reference:      <to be filled in by editor>
>  [Begin Correction]
> E.1.2 Events
> …
> Signal Identity
> ParameterID:  SigID (0x0001)
> This parameter identifies the signals which have terminated.
> Type: octet string
> Possible values: a signal which has terminated.  A signal shall be
> identified using the pkgdName syntax without wildcarding. For a signal
> that is contained in a signal list the signal list identity parameter
> should also be returned indicating the appropriate list.
>
> [End Correction]
>
> Regards, Christian

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------2114547AD9EF17BD72B9EE79
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------2114547AD9EF17BD72B9EE79--


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



From megaco-admin@ietf.org  Fri Jan 18 14:46:55 2002
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 OAA24743
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 14:46:47 -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 OAA01017;
	Fri, 18 Jan 2002 14:31:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00987
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 14:31:47 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24317
	for <megaco@ietf.org>; Fri, 18 Jan 2002 14:31:43 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IJVEc12592;
	Fri, 18 Jan 2002 14:31:14 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA16725;
	Fri, 18 Jan 2002 14:31:14 -0500 (EST)
Message-ID: <3C487749.33ED2EE7@lucent.com>
Date: Fri, 18 Jan 2002 14:28:09 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Open Issue 2: Replies to requests from failed MGC
References: <3B799EBD.F54C2B88@lucent.com> <3B80A153.4419D58E@ericsson.com> <3B812262.C78022C2@lucent.com> <3B821552.139ECF29@ericsson.com>
Content-Type: multipart/mixed;
 boundary="------------12B7A7ADAF3173B412781B6F"
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

This is a multi-part message in MIME format.
--------------12B7A7ADAF3173B412781B6F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Here's a second open issue.  There were only 5 messages in this thread back in
August but then it died without a resolution.  Yet it seems IMHO an important issue
on which the current H.248 is inconsistent.

The issue is whether replies to requests from a failed MGC are sent to a secondary
MGC or are sent to the failed MGC (in spite of likely failure) and whether replies
go to the original MGC after a handoff or be sent to the new MGC.  See the original
analysis of the current statements in H.248 near the bottom.  The conflict is
between 9.1 and statements in D.1 and D.1.5 (that apply only to IP) with that
statement in 11.5.

As explained below, the email archives show a previous discussion of the issue in
Jan 2000 with the final statements suggesting 11.5 be changed and Tom seems to come
to that conclusion in his reply below.

Admitted the rule that the reply should be sent to the MGC that is believed to have
failed makes little sense, but I think that that real issues are:

1. should the protocol use a simple rule that replies ALWAYS go the the addr/port
from which the request came, or have exceptions?

2. should the protocol assume that a Secondary MGC shares state with the Primary? or
should that only be one possible design.

I argued for the simple rule to apply even to this case, since if Secondary and
Primary do NOT share state, sending the reply to the secondary will do no good (it
knows nothing about the request).

If we want to make the operation of pair (Primary and Secondary) that share state
more efficient, perhaps we need to negotiate between the two cases at Registration.

To summarize:
Option #1:
    Change 11.5 to agree with 9.1 and D.1 and the "simple rule" (I actually proposed
text in my original message near the bottom).

Option #2:
    Introduce a way for MGC to specify in Registration response, which of two
options to follow, (1) send all responses to sender, (2) send all responses to
active MGC (after handoff or failover).  MGC would chose based on whether it shared
state with its Secondary.  Change 11.5 (and 9.1, D.1) to use this information to
choose between two behaviors on where to send responses.  This seems like a
significant change to try to introduce into V1 through the IG.  If option #2 is
preferred, perhaps we need to do Option #1 in V1 and introduce Option #2 in H.248v2.




Tom Taylor wrote:

> When we did that section 11.5 stuff, it was certainly in my mind that (assuming shared MGC state), the new MGC would take over from
> the old at a certain point, including closing out old transactions.  I can see the catch: this makes message validation at the MG really
> messy.  If there was no shared state, the old transactions would be cleared by resending them to the new MGC.  Maybe this is the
> appropriate procedure in all cases and 11.5 should be changed.
>

Christian Groves wrote:

> G'Day Terry,
>
> Please see comments below [CHG].
>
> Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > A few points on this.
> > >
> > > o I think D.1.5 needs to be updated ie.
> > >
> > > "In order to account for the possibility of an undetected or in-progress
> > > "failover", we modify the classic algorithm so that if the Media Gateway
> > > receives a valid ServiceChange message announcing a failover".
> > >
> > > Shouldn't this state "handoff" instead of "failover" as handoff is sent
> > > from the MGC to the MG?
> >
> > You are right.  Hadn't noticed this, but MG should never receive ServiceChange
> > message announcing a failover".
> >
> > > o Given that the MGCs are maintaining state in a "handoff" situation I
> > > find it strange that replies from the MG are sent to the "old MGC"
> > > whilst the "new MGC" must send replies to the MG. If the "old MGC" has
> > > died and can't actually receive the command reply how will the "new MGC"
> > > know that a command has been executed?
> >
> > I thought we had agreed that replies would always be sent to source address of
> > request (which would be "old MGC" in this case):
> > - to keep simple consistent rule
> > - because entity at another addr may not know about request
> > - match rule for handoff
>
> [CHG] I'd like to keep things simple also but if simple means broken
> then I'd rather something a little more complicated. I'm confused about
> your comment on handoff because the text was talking about the handoff
> case. Also the comment about the entity at another addr not knowing
> about the request this is also true for the new entity sending a reply.
> So we have an inconsistent rule, the new MGC can't know to receive a
> reply but can know to send one.
>
> >
> > This means of course that the in the event of an MGC failure, these
> > transactions will fail (replies sent to old MGC will not be processed), but
> > unless the new MGC shares transaction state with old the replies will be
> > ignored anyway if sent to new MGC.  If these transactions fail, the new MGC
> > should (through shared state or audit) should issue new transactions to
> > accomplish the still needed task and these will succeed.
>
> [CHG] I think the real question we need to ask is do the MGCs share
> state? If so then the new MGC shall be able to operate as the old one.
> If not then the new MGC can't know anything. ie. it can't send or
> receive replys from previous commands.
>
> >
> > For handoff the rule works since the old MGC can send/accept replies for
> > outstanding transactions before going out of service.
>
> [CHG] Yes but what happen if the MG sends a reply to a command received
> before the service change after the acceptance of the service change?
> The MGC may have already gone out of service.
>
> >
> > Basically there are two stategies:
> > 1) tie transactions to a specific MGC: all pending transactions between MG and
> > old MGC (either direction) will complete with old MGC during a handoff and
> > will fail during a failover.  MG may reissue new transactions with same
> > actions for those that fail after registration with new MGC.  MGC may reissue
> > new transactions with same actions for those that fail after determining they
> > are still needed by shared state or audit.
> >
> > 2) tie transactions to collections of MGCs (primary and all secondaries): all
> > pending transactions between MG and old MGC will be continued (if possible)
> > with new MGC.  MG should send replies to new MGC and expect replies to its
> > transactions from new MGC.
> >
> > Some current statements in H.248 seem to assume the first and others the
> > second.  I dislike #2 because:
> > a) it will only work if MGCs share transaction state.  Elsewhere H.248 allows
> > but does not require MGCs to share state with its secondaries.  Although, I
> > admit that all that will happen if they do not share state is that all pending
> > transactions will fail, which is the same that will happen in #1 for
> > failover.  #1, though allows pending transactions during handoff to succeed.
> >
> > b) it breaks our "all replies to source address" rule.  It requires that in
> > this case we send replies to an address in the ServiceChange message or in
> > provisioned secondary MGC list.  I believe that this breaks one of the hacks
> > for working through NAT devices.
> >
> > #1 seemed to be the conclusion of all mail threads I found (3 or 4 since Jan
> > 2000).
>
> [CHG] Perhaps what we need is option of both and describe the behaviour.
> As I mentioned above it comes down to whether you support state sharing
> or not.
> I'm not particularly concerned about a general rule for NATs because its
> a transport specific behaviour see my comment below.
>
> >
> > > o Annex D is purely about IP transports, so I don't think we should take
> > > it as a general guide to how the protocol works. We put transports in
> > > Annexes so that we could have a common core protocol and use the Annexes
> > > to tailor some procedures.
> >
> > I agree.  Perhaps, details describing this issue should be removed, allowing
> > such to be stated in 7.2.8 and 11.5.  This also helps ensure that we treat TCP
> > equally with UDP.  D.1.5 only applies to UDP but issues of where replies go
> > should be same for both.
> >
> > > o Perhaps an exception to the rule is necessary. If you receive a
> > > command from a valid, secure MGC telling you to you a new address then
> > > what is the problem in using it?
> >
> > Of course you will use it for new transactions, the question is whether that
> > new MGC can handle pending transactions (send or receive replies).
> >
> > > Cheers, Christian
> > >
> > > Terry L Anderson wrote:
> > > >
> > > > I hate to open this again.  I believe we have settled this but the IG
> > > > does not seem to have a change.
> > > >
> > > > The issue is whether replies to requests from a failed MGC are sent to a
> > > > secondary MGC or are sent to the failed MGC (in spite of likely
> > > > failure).
> > > >
> > > > We have a number of statements (section 9.1, D.1, D.1.5) all of which
> > > > say that replies must be sent to the address and port from which the
> > > > request was sent.  I believe we are in agreement that this is a rule
> > > > without exception.  But 11.5 pretty clearly contradicts this.
> > > >     "Accordingly, commands in progress continue, TRANSACTION REPLIES ARE
> > > > SENT TO THE NEW MGC (after a new control association is established),
> > > > and the ..."
> > > >
> > > > The context does NOT sound like these replies are only replies to new
> > > > requests (which would hardly need to be stated.  And so this seems to
> > > > contradict the general principle or suggest an exception to the
> > > > otherwise simple rule.  However, D.1.5 seems to be talking about exactly
> > > > this same case and follows the general rule.
> > > >
> > > > This discrepancy appears to have been noticed as early as Jan 20, 2000
> > > > by Shalini Philip and Brian Rosen's reply of Jan 21, 2000 suggested 11.5
> > > > needed to be changed.  I see the same point raised a few more times in
> > > > the archives.  And replies always seem to support the general rule.  I
> > > > find no support for the 11.5 wording.  But I can find no correction to
> > > > this in the IG (if its there could someone point out the item number).
> > > >
> > > > Are we in agreement that this wording is in error and should be changed
> > > > to something like:
> > > >
> > > > "Accordingly, commands in progress continue and replies to all commands
> > > > from the original MGC must be sent to source address and port from which
> > > > they were sent (even if they are likely to fail). The MG should expect
> > > > outstanding transaction replies from the new MGC."
> > > >
> > > > Do we still agree with the last sentence (from the last clause of the
> > > > original)?  Should the new MGC (if it can) reply to transactions sent to
> > > > the failed MGC (this, of course, will  happen only if the MGCs had
> > > > shared state)?  These replies can still be sent to the addr/port from
> > > > which they came (the MG) and so do not violate the general rule, but
> > > > this does seem to fit with the general philosophy (which we would be
> > > > changing) that the new MGC is taking over role of original even for
> > > > pending transactions.
> > > >
> > > > --
> > > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > > ------------------------------------------------------------
> > > > Terry L Anderson             mailto:tla@lucent.com
> > > > Tel:908.582.7013   Fax:908.582.6729
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> > Waiting for the other shoe to drop but hoping its a one legged man.
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------12B7A7ADAF3173B412781B6F
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------12B7A7ADAF3173B412781B6F--


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


From daemon@ns.ietf.org  Fri Jan 18 14:46:57 2002
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 OAA24767
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 14:46:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA01322
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 14:46:59 -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 OAA01017;
	Fri, 18 Jan 2002 14:31:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00987
	for <megaco@optimus.ietf.org>; Fri, 18 Jan 2002 14:31:47 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24317
	for <megaco@ietf.org>; Fri, 18 Jan 2002 14:31:43 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IJVEc12592;
	Fri, 18 Jan 2002 14:31:14 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA16725;
	Fri, 18 Jan 2002 14:31:14 -0500 (EST)
Message-ID: <3C487749.33ED2EE7@lucent.com>
Date: Fri, 18 Jan 2002 14:28:09 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Open Issue 2: Replies to requests from failed MGC
References: <3B799EBD.F54C2B88@lucent.com> <3B80A153.4419D58E@ericsson.com> <3B812262.C78022C2@lucent.com> <3B821552.139ECF29@ericsson.com>
Content-Type: multipart/mixed;
 boundary="------------12B7A7ADAF3173B412781B6F"
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

This is a multi-part message in MIME format.
--------------12B7A7ADAF3173B412781B6F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Here's a second open issue.  There were only 5 messages in this thread back in
August but then it died without a resolution.  Yet it seems IMHO an important issue
on which the current H.248 is inconsistent.

The issue is whether replies to requests from a failed MGC are sent to a secondary
MGC or are sent to the failed MGC (in spite of likely failure) and whether replies
go to the original MGC after a handoff or be sent to the new MGC.  See the original
analysis of the current statements in H.248 near the bottom.  The conflict is
between 9.1 and statements in D.1 and D.1.5 (that apply only to IP) with that
statement in 11.5.

As explained below, the email archives show a previous discussion of the issue in
Jan 2000 with the final statements suggesting 11.5 be changed and Tom seems to come
to that conclusion in his reply below.

Admitted the rule that the reply should be sent to the MGC that is believed to have
failed makes little sense, but I think that that real issues are:

1. should the protocol use a simple rule that replies ALWAYS go the the addr/port
from which the request came, or have exceptions?

2. should the protocol assume that a Secondary MGC shares state with the Primary? or
should that only be one possible design.

I argued for the simple rule to apply even to this case, since if Secondary and
Primary do NOT share state, sending the reply to the secondary will do no good (it
knows nothing about the request).

If we want to make the operation of pair (Primary and Secondary) that share state
more efficient, perhaps we need to negotiate between the two cases at Registration.

To summarize:
Option #1:
    Change 11.5 to agree with 9.1 and D.1 and the "simple rule" (I actually proposed
text in my original message near the bottom).

Option #2:
    Introduce a way for MGC to specify in Registration response, which of two
options to follow, (1) send all responses to sender, (2) send all responses to
active MGC (after handoff or failover).  MGC would chose based on whether it shared
state with its Secondary.  Change 11.5 (and 9.1, D.1) to use this information to
choose between two behaviors on where to send responses.  This seems like a
significant change to try to introduce into V1 through the IG.  If option #2 is
preferred, perhaps we need to do Option #1 in V1 and introduce Option #2 in H.248v2.




Tom Taylor wrote:

> When we did that section 11.5 stuff, it was certainly in my mind that (assuming shared MGC state), the new MGC would take over from
> the old at a certain point, including closing out old transactions.  I can see the catch: this makes message validation at the MG really
> messy.  If there was no shared state, the old transactions would be cleared by resending them to the new MGC.  Maybe this is the
> appropriate procedure in all cases and 11.5 should be changed.
>

Christian Groves wrote:

> G'Day Terry,
>
> Please see comments below [CHG].
>
> Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > A few points on this.
> > >
> > > o I think D.1.5 needs to be updated ie.
> > >
> > > "In order to account for the possibility of an undetected or in-progress
> > > "failover", we modify the classic algorithm so that if the Media Gateway
> > > receives a valid ServiceChange message announcing a failover".
> > >
> > > Shouldn't this state "handoff" instead of "failover" as handoff is sent
> > > from the MGC to the MG?
> >
> > You are right.  Hadn't noticed this, but MG should never receive ServiceChange
> > message announcing a failover".
> >
> > > o Given that the MGCs are maintaining state in a "handoff" situation I
> > > find it strange that replies from the MG are sent to the "old MGC"
> > > whilst the "new MGC" must send replies to the MG. If the "old MGC" has
> > > died and can't actually receive the command reply how will the "new MGC"
> > > know that a command has been executed?
> >
> > I thought we had agreed that replies would always be sent to source address of
> > request (which would be "old MGC" in this case):
> > - to keep simple consistent rule
> > - because entity at another addr may not know about request
> > - match rule for handoff
>
> [CHG] I'd like to keep things simple also but if simple means broken
> then I'd rather something a little more complicated. I'm confused about
> your comment on handoff because the text was talking about the handoff
> case. Also the comment about the entity at another addr not knowing
> about the request this is also true for the new entity sending a reply.
> So we have an inconsistent rule, the new MGC can't know to receive a
> reply but can know to send one.
>
> >
> > This means of course that the in the event of an MGC failure, these
> > transactions will fail (replies sent to old MGC will not be processed), but
> > unless the new MGC shares transaction state with old the replies will be
> > ignored anyway if sent to new MGC.  If these transactions fail, the new MGC
> > should (through shared state or audit) should issue new transactions to
> > accomplish the still needed task and these will succeed.
>
> [CHG] I think the real question we need to ask is do the MGCs share
> state? If so then the new MGC shall be able to operate as the old one.
> If not then the new MGC can't know anything. ie. it can't send or
> receive replys from previous commands.
>
> >
> > For handoff the rule works since the old MGC can send/accept replies for
> > outstanding transactions before going out of service.
>
> [CHG] Yes but what happen if the MG sends a reply to a command received
> before the service change after the acceptance of the service change?
> The MGC may have already gone out of service.
>
> >
> > Basically there are two stategies:
> > 1) tie transactions to a specific MGC: all pending transactions between MG and
> > old MGC (either direction) will complete with old MGC during a handoff and
> > will fail during a failover.  MG may reissue new transactions with same
> > actions for those that fail after registration with new MGC.  MGC may reissue
> > new transactions with same actions for those that fail after determining they
> > are still needed by shared state or audit.
> >
> > 2) tie transactions to collections of MGCs (primary and all secondaries): all
> > pending transactions between MG and old MGC will be continued (if possible)
> > with new MGC.  MG should send replies to new MGC and expect replies to its
> > transactions from new MGC.
> >
> > Some current statements in H.248 seem to assume the first and others the
> > second.  I dislike #2 because:
> > a) it will only work if MGCs share transaction state.  Elsewhere H.248 allows
> > but does not require MGCs to share state with its secondaries.  Although, I
> > admit that all that will happen if they do not share state is that all pending
> > transactions will fail, which is the same that will happen in #1 for
> > failover.  #1, though allows pending transactions during handoff to succeed.
> >
> > b) it breaks our "all replies to source address" rule.  It requires that in
> > this case we send replies to an address in the ServiceChange message or in
> > provisioned secondary MGC list.  I believe that this breaks one of the hacks
> > for working through NAT devices.
> >
> > #1 seemed to be the conclusion of all mail threads I found (3 or 4 since Jan
> > 2000).
>
> [CHG] Perhaps what we need is option of both and describe the behaviour.
> As I mentioned above it comes down to whether you support state sharing
> or not.
> I'm not particularly concerned about a general rule for NATs because its
> a transport specific behaviour see my comment below.
>
> >
> > > o Annex D is purely about IP transports, so I don't think we should take
> > > it as a general guide to how the protocol works. We put transports in
> > > Annexes so that we could have a common core protocol and use the Annexes
> > > to tailor some procedures.
> >
> > I agree.  Perhaps, details describing this issue should be removed, allowing
> > such to be stated in 7.2.8 and 11.5.  This also helps ensure that we treat TCP
> > equally with UDP.  D.1.5 only applies to UDP but issues of where replies go
> > should be same for both.
> >
> > > o Perhaps an exception to the rule is necessary. If you receive a
> > > command from a valid, secure MGC telling you to you a new address then
> > > what is the problem in using it?
> >
> > Of course you will use it for new transactions, the question is whether that
> > new MGC can handle pending transactions (send or receive replies).
> >
> > > Cheers, Christian
> > >
> > > Terry L Anderson wrote:
> > > >
> > > > I hate to open this again.  I believe we have settled this but the IG
> > > > does not seem to have a change.
> > > >
> > > > The issue is whether replies to requests from a failed MGC are sent to a
> > > > secondary MGC or are sent to the failed MGC (in spite of likely
> > > > failure).
> > > >
> > > > We have a number of statements (section 9.1, D.1, D.1.5) all of which
> > > > say that replies must be sent to the address and port from which the
> > > > request was sent.  I believe we are in agreement that this is a rule
> > > > without exception.  But 11.5 pretty clearly contradicts this.
> > > >     "Accordingly, commands in progress continue, TRANSACTION REPLIES ARE
> > > > SENT TO THE NEW MGC (after a new control association is established),
> > > > and the ..."
> > > >
> > > > The context does NOT sound like these replies are only replies to new
> > > > requests (which would hardly need to be stated.  And so this seems to
> > > > contradict the general principle or suggest an exception to the
> > > > otherwise simple rule.  However, D.1.5 seems to be talking about exactly
> > > > this same case and follows the general rule.
> > > >
> > > > This discrepancy appears to have been noticed as early as Jan 20, 2000
> > > > by Shalini Philip and Brian Rosen's reply of Jan 21, 2000 suggested 11.5
> > > > needed to be changed.  I see the same point raised a few more times in
> > > > the archives.  And replies always seem to support the general rule.  I
> > > > find no support for the 11.5 wording.  But I can find no correction to
> > > > this in the IG (if its there could someone point out the item number).
> > > >
> > > > Are we in agreement that this wording is in error and should be changed
> > > > to something like:
> > > >
> > > > "Accordingly, commands in progress continue and replies to all commands
> > > > from the original MGC must be sent to source address and port from which
> > > > they were sent (even if they are likely to fail). The MG should expect
> > > > outstanding transaction replies from the new MGC."
> > > >
> > > > Do we still agree with the last sentence (from the last clause of the
> > > > original)?  Should the new MGC (if it can) reply to transactions sent to
> > > > the failed MGC (this, of course, will  happen only if the MGCs had
> > > > shared state)?  These replies can still be sent to the addr/port from
> > > > which they came (the MG) and so do not violate the general rule, but
> > > > this does seem to fit with the general philosophy (which we would be
> > > > changing) that the new MGC is taking over role of original even for
> > > > pending transactions.
> > > >
> > > > --
> > > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > > ------------------------------------------------------------
> > > > Terry L Anderson             mailto:tla@lucent.com
> > > > Tel:908.582.7013   Fax:908.582.6729
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> > Waiting for the other shoe to drop but hoping its a one legged man.
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------12B7A7ADAF3173B412781B6F
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------12B7A7ADAF3173B412781B6F--


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



From megaco-admin@ietf.org  Fri Jan 18 15:43:08 2002
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 PAA26240
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:43:08 -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 PAA02747;
	Fri, 18 Jan 2002 15:17:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02719
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 15:17:24 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25651
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:17:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IKGof20902;
	Fri, 18 Jan 2002 15:16:50 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IKGlO07776;
	Fri, 18 Jan 2002 15:16:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZW4L4>; Fri, 18 Jan 2002 15:16:48 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE96@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding sending Error in Transaction Reply.
Date: Fri, 18 Jan 2002 15:16:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A05D.0D3F75F0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A05D.0D3F75F0
Content-Type: text/plain;
	charset="ISO-8859-1"

 

-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, January 18, 2002 12:13 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding sending Error in Transaction Reply.


Hi All,
     consider the example message below.
 
MEGACO/1 [125.125.125.111]:55555
Transaction = 50009 {
   Context = 5000 {
      Subtract = A5555 {
         Statistics {
            ........
         }
       },
       abc = A5556 { 
                    // --- request type is corrupted 
                    // instead of subtract it become 'abc'
               Statistics {
                  ......
                    nt/os=62345, ; octets sent
                    rtp/pr=780, ; packets received
                    nt/or=45123, ; octets received
               }
           }
        }
     }
 
The problem is as follows :
In the same context we have two commands. the first command get parsed well
and will be inserted in to the Action Request while in the second command,
the command type it self is corrupted. so how, do i form the ActionReply :
 
as the RFC 3015 states :
 
action reply = CtxToken EQUAL ContextID LBRKT
            (ErrorDescriptor / Command Reply) RBRKT
 
but as such for an action request i can send only one action reply. but the
syntax above doesn't allow me to set both an error descriptor and an command
reply with in an action reply.
 
cud any one help me resolve the issue  ??
 
thanx in advance.
 
rgds,
Sundar.
 
 


------_=_NextPart_001_01C1A05D.0D3F75F0
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">


<META content=3D"MSHTML 5.00.3315.2869" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Sundareswaram P V =

  [mailto:sundareswarampv@netbrahma.com]<BR><B>Sent:</B> Friday, =
January 18,=20
  2002 12:13 AM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> =
[Megaco] Doubt=20
  regarding sending Error in Transaction Reply.<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; consider =
the example=20
  message below.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
[125.125.125.111]:55555<BR>Transaction =3D=20
  50009 {<BR>&nbsp;&nbsp;&nbsp;Context =3D 5000=20
  {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Subtract =3D A5555=20
  {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics=20
  =
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  ........<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
}<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},<BR>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;abc=20
  =3D A5556 {&nbsp;</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//=20
  --- request type&nbsp;is corrupted</STRONG>&nbsp;</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  // instead of subtract it become=20
  =
'abc'</STRONG><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Statistics=20
  =
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;......<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;nt/os=3D62345,=20
  ; octets sent<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; rtp/pr=3D780, ; packets received<BR>&nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; nt/or=3D45123, ; octets=20
  =
received<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
  }<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}<BR>&nbsp; &nbsp; =
&nbsp; &nbsp;=20
  }<BR>&nbsp; &nbsp; &nbsp;}</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>The problem is as follows =
:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>In the same context we have two =
commands. the=20
  first command get parsed well and will be inserted in to the Action=20
  Request&nbsp;while&nbsp;in the second command, the command type it =
self is=20
  corrupted. so how, do i form the ActionReply :</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>as the RFC 3015 states =
:</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>action reply =3D CtxToken EQUAL =
ContextID=20
  LBRKT</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; (ErrorDescriptor / Command Reply) =
RBRKT</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>but as such for an action request i =
can send only=20
  one action reply. but the syntax above doesn't allow me to set both =
an error=20
  descriptor and an command reply with in an action reply.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>cud any one help me resolve the =
issue&nbsp;=20
  ??</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>thanx in advance.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>rgds,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Sundar.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1A05D.0D3F75F0--

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


From daemon@ns.ietf.org  Fri Jan 18 15:43:09 2002
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 PAA26253
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:43:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA03751
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 15:43:10 -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 PAA02747;
	Fri, 18 Jan 2002 15:17:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02719
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 15:17:24 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25651
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:17:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IKGof20902;
	Fri, 18 Jan 2002 15:16:50 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0IKGlO07776;
	Fri, 18 Jan 2002 15:16:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZW4L4>; Fri, 18 Jan 2002 15:16:48 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AE96@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Sundareswaram P V'" <sundareswarampv@netbrahma.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding sending Error in Transaction Reply.
Date: Fri, 18 Jan 2002 15:16:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A05D.0D3F75F0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A05D.0D3F75F0
Content-Type: text/plain;
	charset="ISO-8859-1"

 

-----Original Message-----
From: Sundareswaram P V [mailto:sundareswarampv@netbrahma.com]
Sent: Friday, January 18, 2002 12:13 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt regarding sending Error in Transaction Reply.


Hi All,
     consider the example message below.
 
MEGACO/1 [125.125.125.111]:55555
Transaction = 50009 {
   Context = 5000 {
      Subtract = A5555 {
         Statistics {
            ........
         }
       },
       abc = A5556 { 
                    // --- request type is corrupted 
                    // instead of subtract it become 'abc'
               Statistics {
                  ......
                    nt/os=62345, ; octets sent
                    rtp/pr=780, ; packets received
                    nt/or=45123, ; octets received
               }
           }
        }
     }
 
The problem is as follows :
In the same context we have two commands. the first command get parsed well
and will be inserted in to the Action Request while in the second command,
the command type it self is corrupted. so how, do i form the ActionReply :
 
as the RFC 3015 states :
 
action reply = CtxToken EQUAL ContextID LBRKT
            (ErrorDescriptor / Command Reply) RBRKT
 
but as such for an action request i can send only one action reply. but the
syntax above doesn't allow me to set both an error descriptor and an command
reply with in an action reply.
 
cud any one help me resolve the issue  ??
 
thanx in advance.
 
rgds,
Sundar.
 
 


------_=_NextPart_001_01C1A05D.0D3F75F0
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">


<META content=3D"MSHTML 5.00.3315.2869" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Sundareswaram P V =

  [mailto:sundareswarampv@netbrahma.com]<BR><B>Sent:</B> Friday, =
January 18,=20
  2002 12:13 AM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> =
[Megaco] Doubt=20
  regarding sending Error in Transaction Reply.<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; consider =
the example=20
  message below.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
[125.125.125.111]:55555<BR>Transaction =3D=20
  50009 {<BR>&nbsp;&nbsp;&nbsp;Context =3D 5000=20
  {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Subtract =3D A5555=20
  {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics=20
  =
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  ........<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
}<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},<BR>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;abc=20
  =3D A5556 {&nbsp;</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//=20
  --- request type&nbsp;is corrupted</STRONG>&nbsp;</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  // instead of subtract it become=20
  =
'abc'</STRONG><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Statistics=20
  =
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;......<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;nt/os=3D62345,=20
  ; octets sent<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;=20
  &nbsp; &nbsp; rtp/pr=3D780, ; packets received<BR>&nbsp; &nbsp; =
&nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; nt/or=3D45123, ; octets=20
  =
received<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
  }<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}<BR>&nbsp; &nbsp; =
&nbsp; &nbsp;=20
  }<BR>&nbsp; &nbsp; &nbsp;}</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>The problem is as follows =
:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>In the same context we have two =
commands. the=20
  first command get parsed well and will be inserted in to the Action=20
  Request&nbsp;while&nbsp;in the second command, the command type it =
self is=20
  corrupted. so how, do i form the ActionReply :</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>as the RFC 3015 states =
:</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>action reply =3D CtxToken EQUAL =
ContextID=20
  LBRKT</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp;&nbsp; (ErrorDescriptor / Command Reply) =
RBRKT</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>but as such for an action request i =
can send only=20
  one action reply. but the syntax above doesn't allow me to set both =
an error=20
  descriptor and an command reply with in an action reply.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>cud any one help me resolve the =
issue&nbsp;=20
  ??</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>thanx in advance.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>rgds,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Sundar.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1A05D.0D3F75F0--

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



From megaco-admin@ietf.org  Fri Jan 18 15:58:08 2002
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 PAA26658
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:58:08 -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 PAA03867;
	Fri, 18 Jan 2002 15:44:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03778
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 15:44:21 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26292
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:44:18 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IKiE401784;
	Fri, 18 Jan 2002 15:44:14 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA19726;
	Fri, 18 Jan 2002 15:44:11 -0500 (EST)
Message-ID: <3C488864.C76505EB@lucent.com>
Date: Fri, 18 Jan 2002 15:41:08 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Usha Iyer'" <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------D43D2B647C2D2CF89073590A"
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

This is a multi-part message in MIME format.
--------------D43D2B647C2D2CF89073590A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am designating this issue as open issue #3.  Tom suggests that we change a
statement that is proposed for the IG 6.98 (not yet approved).  The intent of
the statement was that multiple media streams in SDP should not occur in a
single H.248 StreamDescriptor, but defining this in terms of a single m line is
too restrictive.
(1) FID allows grouping multiple media lines (m lines) into a single media
stream and this should be allowed in a single H.248 StreamDescriptor.
(2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
distinct payload.  It also supports sending this payload to a different
ipaddr/port than that used for voice.  This in essence "forks" the media stream
coming from one termination (eg. PSTN) into two output streams, one containing
voice RTP and the other containing DTMF (or other telephone event RTP, sent to
(possibly) two different ipaddr/ports.  This is similar in concept to FID and
again requires multiple media (m) lines in the SDP.

The current IG draft adds the following to 7.1.8 (right under the first set of
bullets):

A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.

Perhaps we could change this to read:

A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT specify multiple streams.  This often means
that the session description will contain only a single media description ("m="
line).  However, where media descriptions are grouped and refer to a single,
logical media stream but where payload packets may be sent to different
transport addresses, multiple media description lines may be required (e.g., RFC
2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
Descriptors.
--------
If we refer to RFC 2833, a reference will have to be added to section 2.2
Informative References, but I think this helps clarify the intent with an
example.  We cannot refer to FID as it is not yet an RFC.

Tom, does this meet your intent or do you have an alternate re-wording?

Tom-PT Taylor wrote:

> I think we made a mistake when we added this IG item.  It will block us from
> using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
> below.  If other people feel the same way, we may want to modify the wording
> to handle that case.
>
> The same draft also provides a capability to indicate synchronization
> dependencies between media streams.  Megaco will be unable to use this.
> Back when we put the protocol together, I thought we would need something to
> show which streams were related, but we chose to add a general requirement
> for synchronization of streams emanating from the same context.  I think the
> current work on MCU decomposition in SG 16 may come up with package-based
> solutions for greater selectivity.
>
> If ReserveGroup and ReserveValue are both true, the MG is expected to
> reserve resources to cover every session description and, within each one,
> every codec alternative offered.
>
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 02, 2002 11:31 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
> megaco@ietf.org
> Subject: Re: [Megaco] Reserve Value and Reserve Group
>
> Hi Tom, All
>
>     Section  6.98 of  AVD-2128 doc ( H248IG) states that
> --------------------
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT include more than one media description
> ("m=" line).  Any additional media streams for a termination must appear in
> distinct Stream Descriptors.
> -----------------------
>       Due to the above restriction ,you can't have multiple "m=" lines in
> one session desc.
>        One ques:  How do u resolve ReserveValue = True and also ReserveGroup
> = True
>
> Regards
> Usha
>
> ----- Original Message -----
> From: Tom-PT Taylor <taylor@nortelnetworks.com>
> To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
> Sent: Thursday, January 03, 2002 12:54 AM
> Subject: RE: [Megaco] Reserve Value and Reserve Group
>
> > A "property group" is the same as a session description.
> ReserveGroup=true
> > says to reserve resources to support all of the session descriptions
> > presented.
> >
> > ReserveValue=true definitely says that if multiple payload types are
> > presented on the same m= line, resources should be reserved for all of
> them.
> > The grey area is if there are multiple m= lines within the same session
> > description.  I propose the interpretation that ReserveValue=true reserves
> > all resources within the same session description.
> >
> > I believe a further interpretation is needed as follows:
> >
> >   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> > presented:
> >   --------------
> >  means that the MG chooses its preferred session description, then
> reserves
> > all resources specified therein.
> >
> >   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> > presented:
> >   --------------
> >  means that the MG reserves resources for every session description, but
> > within each session description, where any m= line presents alternative
> > payload types, the MG chooses just one of the alternatives.
> >
> > I suspect it may be simpler to use the FID mechanism
> > (draft-ietf-mmusic-fid-05.txt) when it is finished.
> >
> > As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
> the
> > MGC-to-MG direction.
> >
> > -----Original Message-----
> > From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> > Sent: Saturday, December 29, 2001 1:27 AM
> > To: megaco@ietf.org
> > Cc: Sudhir (E-mail)
> > Subject: [Megaco] Reserve Value and Reserve Group
> >
> >
> > Hi,
> > In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> > Descriptors):
> > "If ReserveGroup is true, the MG reserves the resources required to
> > support any of the requested property group alternatives that it can
> > currently support.  If ReserveValue is true, the MG reserves the
> > resources required to support any of the requested property value
> > alternatives that it can currently support."
> >
> > In the above statement, I want to know "what is property group and what is
> > property value". Where can I get more information on this. I referred
> > SDP RFC 2327, in that Session level Description and Media level
> Description
> > are differentiated. But I could not conclude from this.
> >
> > In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> > Session level descriptions. Can anybody mail me how can I interpret this,
> > as property groups or as property values. I will be happy, if somebody
> > explains this with some example packets.
> >
> > One more doubt regarding SDP Paramters:
> > In SDP RFC 2327, it is given that following fields are mandatory:
> > For 'Session description':
> > v=  (protocol version)
> > o=  (owner/creator and session identifier).
> > s=  (session name)
> > For 'Time description':
> > t=  (time the session is active)
> >
> > For 'Media description':
> > m=  (media name and transport address)
> >
> > But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> > callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
> are
> > not required.
> >
> >
> > Thanks,
> > Sudhir
> >
> >
> > _______________________________________________
> > 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------D43D2B647C2D2CF89073590A
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------D43D2B647C2D2CF89073590A--


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


From daemon@ns.ietf.org  Fri Jan 18 15:58:09 2002
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 PAA26666
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 15:58:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04301
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 15:58:10 -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 PAA03867;
	Fri, 18 Jan 2002 15:44:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03778
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 15:44:21 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26292
	for <megaco@ietf.org>; Fri, 18 Jan 2002 15:44:18 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0IKiE401784;
	Fri, 18 Jan 2002 15:44:14 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA19726;
	Fri, 18 Jan 2002 15:44:11 -0500 (EST)
Message-ID: <3C488864.C76505EB@lucent.com>
Date: Fri, 18 Jan 2002 15:41:08 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Usha Iyer'" <usha.iyer@wipro.com>, sudhirk@future.futsoft.com,
        megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------D43D2B647C2D2CF89073590A"
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

This is a multi-part message in MIME format.
--------------D43D2B647C2D2CF89073590A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am designating this issue as open issue #3.  Tom suggests that we change a
statement that is proposed for the IG 6.98 (not yet approved).  The intent of
the statement was that multiple media streams in SDP should not occur in a
single H.248 StreamDescriptor, but defining this in terms of a single m line is
too restrictive.
(1) FID allows grouping multiple media lines (m lines) into a single media
stream and this should be allowed in a single H.248 StreamDescriptor.
(2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
distinct payload.  It also supports sending this payload to a different
ipaddr/port than that used for voice.  This in essence "forks" the media stream
coming from one termination (eg. PSTN) into two output streams, one containing
voice RTP and the other containing DTMF (or other telephone event RTP, sent to
(possibly) two different ipaddr/ports.  This is similar in concept to FID and
again requires multiple media (m) lines in the SDP.

The current IG draft adds the following to 7.1.8 (right under the first set of
bullets):

A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT include more than one media description
("m=" line).  Any additional media streams for a termination must appear in
distinct Stream Descriptors.

Perhaps we could change this to read:

A Stream Descriptor specifies a single bi-directional media stream and so a
single session description MUST NOT specify multiple streams.  This often means
that the session description will contain only a single media description ("m="
line).  However, where media descriptions are grouped and refer to a single,
logical media stream but where payload packets may be sent to different
transport addresses, multiple media description lines may be required (e.g., RFC
2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
Descriptors.
--------
If we refer to RFC 2833, a reference will have to be added to section 2.2
Informative References, but I think this helps clarify the intent with an
example.  We cannot refer to FID as it is not yet an RFC.

Tom, does this meet your intent or do you have an alternate re-wording?

Tom-PT Taylor wrote:

> I think we made a mistake when we added this IG item.  It will block us from
> using the FID capability (draft-ietf-mmusic-fid-05.txt) that I refer to
> below.  If other people feel the same way, we may want to modify the wording
> to handle that case.
>
> The same draft also provides a capability to indicate synchronization
> dependencies between media streams.  Megaco will be unable to use this.
> Back when we put the protocol together, I thought we would need something to
> show which streams were related, but we chose to add a general requirement
> for synchronization of streams emanating from the same context.  I think the
> current work on MCU decomposition in SG 16 may come up with package-based
> solutions for greater selectivity.
>
> If ReserveGroup and ReserveValue are both true, the MG is expected to
> reserve resources to cover every session description and, within each one,
> every codec alternative offered.
>
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 02, 2002 11:31 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; sudhirk@future.futsoft.com;
> megaco@ietf.org
> Subject: Re: [Megaco] Reserve Value and Reserve Group
>
> Hi Tom, All
>
>     Section  6.98 of  AVD-2128 doc ( H248IG) states that
> --------------------
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT include more than one media description
> ("m=" line).  Any additional media streams for a termination must appear in
> distinct Stream Descriptors.
> -----------------------
>       Due to the above restriction ,you can't have multiple "m=" lines in
> one session desc.
>        One ques:  How do u resolve ReserveValue = True and also ReserveGroup
> = True
>
> Regards
> Usha
>
> ----- Original Message -----
> From: Tom-PT Taylor <taylor@nortelnetworks.com>
> To: <sudhirk@future.futsoft.com>; <megaco@ietf.org>
> Sent: Thursday, January 03, 2002 12:54 AM
> Subject: RE: [Megaco] Reserve Value and Reserve Group
>
> > A "property group" is the same as a session description.
> ReserveGroup=true
> > says to reserve resources to support all of the session descriptions
> > presented.
> >
> > ReserveValue=true definitely says that if multiple payload types are
> > presented on the same m= line, resources should be reserved for all of
> them.
> > The grey area is if there are multiple m= lines within the same session
> > description.  I propose the interpretation that ReserveValue=true reserves
> > all resources within the same session description.
> >
> > I believe a further interpretation is needed as follows:
> >
> >   ReserveValue=true, ReserveGroup=false, multiple session descriptions
> > presented:
> >   --------------
> >  means that the MG chooses its preferred session description, then
> reserves
> > all resources specified therein.
> >
> >   ReserveValue=false, ReserveGroup=true, multiple session descriptions
> > presented:
> >   --------------
> >  means that the MG reserves resources for every session description, but
> > within each session description, where any m= line presents alternative
> > payload types, the MG chooses just one of the alternatives.
> >
> > I suspect it may be simpler to use the FID mechanism
> > (draft-ietf-mmusic-fid-05.txt) when it is finished.
> >
> > As for the missing s=, o=, and t= lines, RFC 3015 makes them optional in
> the
> > MGC-to-MG direction.
> >
> > -----Original Message-----
> > From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> > Sent: Saturday, December 29, 2001 1:27 AM
> > To: megaco@ietf.org
> > Cc: Sudhir (E-mail)
> > Subject: [Megaco] Reserve Value and Reserve Group
> >
> >
> > Hi,
> > In the RFC 3015, following is given in section 7.1.8 (Local and Remote
> > Descriptors):
> > "If ReserveGroup is true, the MG reserves the resources required to
> > support any of the requested property group alternatives that it can
> > currently support.  If ReserveValue is true, the MG reserves the
> > resources required to support any of the requested property value
> > alternatives that it can currently support."
> >
> > In the above statement, I want to know "what is property group and what is
> > property value". Where can I get more information on this. I referred
> > SDP RFC 2327, in that Session level Description and Media level
> Description
> > are differentiated. But I could not conclude from this.
> >
> > In RFC 3015 Appendix-A section-A.1.2 Step-12, Local Descriptor defines two
> > Session level descriptions. Can anybody mail me how can I interpret this,
> > as property groups or as property values. I will be happy, if somebody
> > explains this with some example packets.
> >
> > One more doubt regarding SDP Paramters:
> > In SDP RFC 2327, it is given that following fields are mandatory:
> > For 'Session description':
> > v=  (protocol version)
> > o=  (owner/creator and session identifier).
> > s=  (session name)
> > For 'Time description':
> > t=  (time the session is active)
> >
> > For 'Media description':
> > m=  (media name and transport address)
> >
> > But in call flows given in RFC 3015 Appendix A and in 'draft-madhu-megaco-
> > callflows-00.txt', I haven't found fields 'o=' and 's='. Are this fields
> are
> > not required.
> >
> >
> > Thanks,
> > Sudhir
> >
> >
> > _______________________________________________
> > 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------D43D2B647C2D2CF89073590A
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------D43D2B647C2D2CF89073590A--


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



From megaco-admin@ietf.org  Fri Jan 18 16:48:13 2002
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 QAA28386
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 16:48:13 -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 QAA05810;
	Fri, 18 Jan 2002 16:33:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA05781
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 16:33:27 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27981
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:33:24 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0ILWur24028
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:32:56 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA14034; Fri, 18 Jan 2002 16:32:52 -0500 (EST)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA14015; Fri, 18 Jan 2002 16:32:49 -0500 (EST)
Message-ID: <3C4893DB.BE8C2888@bell-labs.com>
Date: Fri, 18 Jan 2002 16:30:03 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
Original-CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Terry L Anderson wrote:
> 
> I am designating this issue as open issue #3.  Tom suggests that we change a
> statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> the statement was that multiple media streams in SDP should not occur in a
> single H.248 StreamDescriptor, but defining this in terms of a single m line is
> too restrictive.
> (1) FID allows grouping multiple media lines (m lines) into a single media
> stream and this should be allowed in a single H.248 StreamDescriptor.
> (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> distinct payload.  It also supports sending this payload to a different
> ipaddr/port than that used for voice.  This in essence "forks" the media stream
> coming from one termination (eg. PSTN) into two output streams, one containing
> voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> again requires multiple media (m) lines in the SDP.
> 
> The current IG draft adds the following to 7.1.8 (right under the first set of
> bullets):
> 
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT include more than one media description
> ("m=" line).  Any additional media streams for a termination must appear in
> distinct Stream Descriptors.
> 
> Perhaps we could change this to read:
> 
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT specify multiple streams.  This often means
> that the session description will contain only a single media description ("m="
> line).  However, where media descriptions are grouped and refer to a single,
> logical media stream but where payload packets may be sent to different
> transport addresses, multiple media description lines may be required (e.g., RFC
> 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> Descriptors.
> --------
> If we refer to RFC 2833, a reference will have to be added to section 2.2
> Informative References, but I think this helps clarify the intent with an
> example.  We cannot refer to FID as it is not yet an RFC.


I have no problem with the intent of this change.  You have to 
change the language to allow certain cases.  But the language 
is getting very fuzzy.

How do I tell a "single, logical media stream" from "multiple streams"?

Why is voice & RFC2833 DTMF a "single, logical stream", when 
audio + video is "multiple streams"?

When would an MG be handling multiple streams on a termination
that are not "logically" related in some way?

Doesn't this really mean I can put as many "streams" as I want
in my SDP and have just one StreamDescriptor?


-troy

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


From daemon@ns.ietf.org  Fri Jan 18 16:48:14 2002
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 QAA28395
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 16:48:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA06173
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 16:48:16 -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 QAA05810;
	Fri, 18 Jan 2002 16:33:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA05781
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 16:33:27 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27981
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:33:24 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0ILWur24028
	for <megaco@ietf.org>; Fri, 18 Jan 2002 16:32:56 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA14034; Fri, 18 Jan 2002 16:32:52 -0500 (EST)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA14015; Fri, 18 Jan 2002 16:32:49 -0500 (EST)
Message-ID: <3C4893DB.BE8C2888@bell-labs.com>
Date: Fri, 18 Jan 2002 16:30:03 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
Original-CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Terry L Anderson wrote:
> 
> I am designating this issue as open issue #3.  Tom suggests that we change a
> statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> the statement was that multiple media streams in SDP should not occur in a
> single H.248 StreamDescriptor, but defining this in terms of a single m line is
> too restrictive.
> (1) FID allows grouping multiple media lines (m lines) into a single media
> stream and this should be allowed in a single H.248 StreamDescriptor.
> (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> distinct payload.  It also supports sending this payload to a different
> ipaddr/port than that used for voice.  This in essence "forks" the media stream
> coming from one termination (eg. PSTN) into two output streams, one containing
> voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> again requires multiple media (m) lines in the SDP.
> 
> The current IG draft adds the following to 7.1.8 (right under the first set of
> bullets):
> 
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT include more than one media description
> ("m=" line).  Any additional media streams for a termination must appear in
> distinct Stream Descriptors.
> 
> Perhaps we could change this to read:
> 
> A Stream Descriptor specifies a single bi-directional media stream and so a
> single session description MUST NOT specify multiple streams.  This often means
> that the session description will contain only a single media description ("m="
> line).  However, where media descriptions are grouped and refer to a single,
> logical media stream but where payload packets may be sent to different
> transport addresses, multiple media description lines may be required (e.g., RFC
> 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> Descriptors.
> --------
> If we refer to RFC 2833, a reference will have to be added to section 2.2
> Informative References, but I think this helps clarify the intent with an
> example.  We cannot refer to FID as it is not yet an RFC.


I have no problem with the intent of this change.  You have to 
change the language to allow certain cases.  But the language 
is getting very fuzzy.

How do I tell a "single, logical media stream" from "multiple streams"?

Why is voice & RFC2833 DTMF a "single, logical stream", when 
audio + video is "multiple streams"?

When would an MG be handling multiple streams on a termination
that are not "logically" related in some way?

Doesn't this really mean I can put as many "streams" as I want
in my SDP and have just one StreamDescriptor?


-troy

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



From megaco-admin@ietf.org  Fri Jan 18 18:24:48 2002
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 SAA00614
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 18:24:43 -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 SAA09166;
	Fri, 18 Jan 2002 18:14:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09138
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 18:14:02 -0500 (EST)
Received: from calliope1.fm.intel.com (fmfdns01.fm.intel.com [132.233.247.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00304
	for <megaco@ietf.org>; Fri, 18 Jan 2002 18:13:58 -0500 (EST)
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110])
	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.48 2001/12/13 16:27:50 root Exp $) with SMTP id XAA27198
	for <megaco@ietf.org>; Fri, 18 Jan 2002 23:13:31 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002011815153604902
 ; Fri, 18 Jan 2002 15:15:36 -0800
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <D1007N04>; Fri, 18 Jan 2002 15:13:28 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500CE34AD2@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>,
        Narendra Babu<narendra@dexceldesigns.com>, megaco@ietf.org
Subject: RE: [Megaco] Regarding IPsec and interim AH
Date: Fri, 18 Jan 2002 15:11:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
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

I remember long time back on this list it was being discussed that AH scheme
will be deprecated. However, I still see its mention in v2.

- Bharat

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Friday, January 18, 2002 5:26 AM
To: Narendra Babu; megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH


At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


_______________________________________________
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


From daemon@ns.ietf.org  Fri Jan 18 18:24:53 2002
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 SAA00626
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 18:24:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA09383
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 18:24:52 -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 SAA09166;
	Fri, 18 Jan 2002 18:14:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09138
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 18:14:02 -0500 (EST)
Received: from calliope1.fm.intel.com (fmfdns01.fm.intel.com [132.233.247.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00304
	for <megaco@ietf.org>; Fri, 18 Jan 2002 18:13:58 -0500 (EST)
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110])
	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.48 2001/12/13 16:27:50 root Exp $) with SMTP id XAA27198
	for <megaco@ietf.org>; Fri, 18 Jan 2002 23:13:31 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002011815153604902
 ; Fri, 18 Jan 2002 15:15:36 -0800
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <D1007N04>; Fri, 18 Jan 2002 15:13:28 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500CE34AD2@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'Matt Holdrege'" <matt.holdrege@verizon.net>,
        Narendra Babu<narendra@dexceldesigns.com>, megaco@ietf.org
Subject: RE: [Megaco] Regarding IPsec and interim AH
Date: Fri, 18 Jan 2002 15:11:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
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

I remember long time back on this list it was being discussed that AH scheme
will be deprecated. However, I still see its mention in v2.

- Bharat

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Friday, January 18, 2002 5:26 AM
To: Narendra Babu; megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH


At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


_______________________________________________
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



From megaco-admin@ietf.org  Fri Jan 18 18:25:54 2002
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 SAA00654
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 18:25:54 -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 SAA09215;
	Fri, 18 Jan 2002 18:15:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09186
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 18:15:17 -0500 (EST)
Received: from hebe.or.intel.com (jffdns02.or.intel.com [134.134.248.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00316
	for <megaco@ietf.org>; Fri, 18 Jan 2002 18:15:13 -0500 (EST)
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by hebe.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.48 2001/12/13 16:27:50 root Exp $) with SMTP id XAA16524
	for <megaco@ietf.org>; Fri, 18 Jan 2002 23:14:46 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.1.16) with SMTP id M2002011815190222008
 for <megaco@ietf.org>; Fri, 18 Jan 2002 15:19:02 -0800
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <D17BKJ8J>; Fri, 18 Jan 2002 15:14:46 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500CE34AD3@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Fri, 18 Jan 2002 15:14:43 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Agreed...I don't see any reason to develop retransmission mechanisms for the
responses just because immAck was sent and we are not receiving replies.
immAck is just a request which may or may not get fulfilled and doesn't
affect any protocol operation.

- Bharat

-----Original Message-----
From: J K Ramchandra [mailto:jkr@ipgen-india.com]
Sent: Friday, January 18, 2002 2:49 PM
To: vibansal@hss.hns.com; Christian.Groves@ericsson.com.au;
taylor@nortelnetworks.com; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


Hi all,

I think we are heading somewhere here. If I remember correctly, the sole
purpose
of responseAck is to reduce the overall memory consumption. The entity
sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till
long
timer to clean up these buffer. Normally, the response ack is appended with
the
next message sent towards that destination (MG/MGC). By setting
immAckRequired
flag in the response, it is requesting to send it immediately (not waiting
till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could
be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but
simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after
one
or more transaction Pending was sent), I believe, is due to the fact that
this
specific transaction has already  active for quite some time and better to
be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will
retransmit
the response only when the repeated request is received. This is the case
with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't
see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving
side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN


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


From daemon@ns.ietf.org  Fri Jan 18 18:25:55 2002
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 SAA00664
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jan 2002 18:25:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA09422
	for megaco-archive@odin.ietf.org; Fri, 18 Jan 2002 18:25: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 SAA09215;
	Fri, 18 Jan 2002 18:15:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09186
	for <megaco@ns.ietf.org>; Fri, 18 Jan 2002 18:15:17 -0500 (EST)
Received: from hebe.or.intel.com (jffdns02.or.intel.com [134.134.248.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00316
	for <megaco@ietf.org>; Fri, 18 Jan 2002 18:15:13 -0500 (EST)
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by hebe.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.48 2001/12/13 16:27:50 root Exp $) with SMTP id XAA16524
	for <megaco@ietf.org>; Fri, 18 Jan 2002 23:14:46 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.1.16) with SMTP id M2002011815190222008
 for <megaco@ietf.org>; Fri, 18 Jan 2002 15:19:02 -0800
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <D17BKJ8J>; Fri, 18 Jan 2002 15:14:46 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500CE34AD3@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Fri, 18 Jan 2002 15:14:43 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Agreed...I don't see any reason to develop retransmission mechanisms for the
responses just because immAck was sent and we are not receiving replies.
immAck is just a request which may or may not get fulfilled and doesn't
affect any protocol operation.

- Bharat

-----Original Message-----
From: J K Ramchandra [mailto:jkr@ipgen-india.com]
Sent: Friday, January 18, 2002 2:49 PM
To: vibansal@hss.hns.com; Christian.Groves@ericsson.com.au;
taylor@nortelnetworks.com; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


Hi all,

I think we are heading somewhere here. If I remember correctly, the sole
purpose
of responseAck is to reduce the overall memory consumption. The entity
sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till
long
timer to clean up these buffer. Normally, the response ack is appended with
the
next message sent towards that destination (MG/MGC). By setting
immAckRequired
flag in the response, it is requesting to send it immediately (not waiting
till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could
be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but
simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after
one
or more transaction Pending was sent), I believe, is due to the fact that
this
specific transaction has already  active for quite some time and better to
be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will
retransmit
the response only when the repeated request is received. This is the case
with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't
see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving
side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN


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



From megaco-admin@ietf.org  Sun Jan 20 03:14:54 2002
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 DAA07847
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 03:14:54 -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 CAA09856;
	Sun, 20 Jan 2002 02:52:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09829
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 02:51:59 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA07664
	for <megaco@ietf.org>; Sun, 20 Jan 2002 02:51:54 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Sun Jan 20 10:07:34 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FW1J>; Sun, 20 Jan 2002 09:42:28 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189C88D@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Tom-PT Taylor <taylor@nortelnetworks.com>, jsegers@LUCENT.COM,
        "Rosen, Brian" <Brian.Rosen@marconi.com>, megaco@ietf.org
Date: Sun, 20 Jan 2002 09:42:20 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A185.FDD34BD0"
Subject: [Megaco] wildcard response
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A185.FDD34BD0
Content-Type: text/plain

This is a part of a thread that stopped in September 2000, but it is not
clear to me how it was resolved.  What Brian wrote agrees with the ABNF, and
what Tom and John wrote is consistent with section 6.2.2, but they
contradict each other.  The thread ended with this, seeming to imply
agreement with Tom and John, but I do not see that the ABNF was amended to
allow lists at the parameter value level.

Raphael Tryster

Message-ID:  <39B609EF.32950A75@lucent.com>
Date:         Wed, 6 Sep 2000 11:10:07 +0200
Reply-To: John Segers <jsegers@LUCENT.COM>
Sender: "Media Gateway Control (megaco)"
<MEGACO@STANDARDS.NORTELNETWORKS.COM>
From: John Segers <jsegers@LUCENT.COM>
Organization: Lucent Technologies
Subject:      Re: Transaction Reply Context=ALL, wilcard response
To: MEGACO@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Tom,

This is my understanding as well.  Relevant text appears in section
6.2.2:
        If individual responses are not required, a wildcard response
        may be requested.  In such a case, a single response is
        generated, which contains the UNION of all of the individual
        responses which otherwise would have been generated, with
        duplicate values suppressed.  For instance, given a Termination
        Ta with properties p1=a, p2=b and Termination Tb with
        properties p2=c, p3=d, a UNION response would consist of a
        wildcarded TerminationId and the sequence of properties p1=a,
        p2=b,c and p3=d.

Cheers,

John

Tom-PT Taylor wrote:
>
> I always understood the intent of "W-" to mean that the response would
show
> unions at the most atomic level (i.e. per-parameter).  In other words, it
> was meant to show the range of values supported, not something
intelligible
> on a per-session basis.  I have to admit that it isn't necessarily clear
> what a "parameter" is in SDP (i.e.) would all "a=fmtp:" be collapsed into
> one list?
>
> > -----Original Message-----
> > From: Shalini Philip [mailto:sphilip@GLOBESPAN.NET]
> > Sent: Tuesday, September 05, 2000 4:21 AM
> > To: MEGACO@STANDARDS.NORTELNETWORKS.COM
> > Subject: Re: Transaction Reply Context=ALL, wilcard response
> >
> >
> > Hello Brian, Christian & list.
> >
> >         The example given below shows multiple Statistics
> > descriptors in
> > the descriptor list for a command reply. I believe,
> > the common understanding is that only the digit map descriptor and the
> > error descriptors are the only two descriptors
> > which can be repeated. If other descriptors can also be repeated, then
> > we can have multiple Mux descriptors, if the
> > MG supports multiple MUX types.
> > Also since it is not feasible to take the union of SDP definitions in
> > local and remote descriptors, I guess we can even have
> > multiple local and remote descriptors , or do we put them as multiple
> > SDP definitions in the same local/remote descriptor.
> >
> > Thanks & Regards,
> >   Shalini Philip.
> >
> >
> > "Rosen, Brian" wrote:
> >
> > >  I don't think you can do a subtract with CHOOSE.
> > > You could use ALL, but not choose.
> > >
> > > If you ask for a wildcard response, I think you get one response per
> > > value found, if they are different.  Since you get statistics on
> > > results, any identical statistics reports would only be
> > > repeated once.  So. assuming you used ALL, I'd expect:
> > > C=1{Subtract=*{Statistics{...}, Statistics{...}....}.
> > > C=2{...
> > > ....
> > >


------_=_NextPart_001_01C1A185.FDD34BD0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>wildcard response</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is a part of a thread that stopped =
in September 2000, but it is not clear to me how it was resolved.&nbsp; W=
hat Brian wrote agrees with the ABNF, and what Tom and John wrote is cons=
istent with section 6.2.2, but they contradict each other.&nbsp; The thre=
ad ended with this, seeming to imply agreement with Tom and John, but I d=
o not see that the ABNF was amended to allow lists at the parameter value=
 level.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Message-ID:&nbsp; &lt;39B609EF.32950A75@=
lucent.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Wed, 6 Sep 2000 11:10:07 +0200</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Reply-To: John Segers &lt;jsegers@LUCEN=
T.COM&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sender: &quot;Media Gateway Control (me=
gaco)&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; &lt;MEGACO@STANDARDS.NORTELNETWORKS.COM&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: John Segers &lt;jsegers@LUCENT.CO=
M&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Organization: Lucent Technologies</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Re: Transaction Reply Context=3DALL, wilcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: MEGACO@STANDARDS.NORTELNETWORKS.COM=
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Transfer-Encoding: 7bit</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tom,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is my understanding as well.&nbsp; =
Relevant text appears in section</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">6.2.2:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; If individual responses are not required, a wildcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; may be requested.&nbsp; In such a case, a single response is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; generated, which contains the UNION of all of the individual</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; responses which otherwise would have been generated, with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; duplicate values suppressed.&nbsp; For instance, given a Termination<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Ta with properties p1=3Da, p2=3Db and Termination Tb with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; properties p2=3Dc, p3=3Dd, a UNION response would consist of a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; wildcarded TerminationId and the sequence of properties p1=3Da,</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; p2=3Db,c and p3=3Dd.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">John</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tom-PT Taylor wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I always understood the intent of =
&quot;W-&quot; to mean that the response would show</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; unions at the most atomic level (i=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; was meant to show the range of val=
ues supported, not something intelligible</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; on a per-session basis.&nbsp; I ha=
ve to admit that it isn't necessarily clear</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; what a &quot;parameter&quot; is in=
 SDP (i.e.) would all &quot;a=3Dfmtp:&quot; be collapsed into</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; one list?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; -----Original Message-----</F=
ONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; From: Shalini Philip [<A HREF=
=3D"mailto:sphilip@GLOBESPAN.NET">mailto:sphilip@GLOBESPAN.NET</A>]</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Sent: Tuesday, September 05, =
2000 4:21 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; To: MEGACO@STANDARDS.NORTELNE=
TWORKS.COM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Subject: Re: Transaction Repl=
y Context=3DALL, wilcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Hello Brian, Christian &amp; =
list.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; The example given below shows multiple Statistics</FON=
T>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; descriptors in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; the descriptor list for a com=
mand reply. I believe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; the common understanding is t=
hat only the digit map descriptor and the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; error descriptors are the onl=
y two descriptors</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; which can be repeated. If oth=
er descriptors can also be repeated, then</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; we can have multiple Mux desc=
riptors, if the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; MG supports multiple MUX type=
s.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Also since it is not feasible=
 to take the union of SDP definitions in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; local and remote descriptors,=
 I guess we can even have</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; multiple local and remote des=
criptors , or do we put them as multiple</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; SDP definitions in the same l=
ocal/remote descriptor.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Thanks &amp; Regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp; Shalini Philip.</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &quot;Rosen, Brian&quot; wrot=
e:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;&nbsp; I don't think you =
can do a subtract with CHOOSE.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; You could use ALL, but n=
ot choose.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; If you ask for a wildcar=
d response, I think you get one response per</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; value found, if they are=
 different.&nbsp; Since you get statistics on</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; results, any identical s=
tatistics reports would only be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; repeated once.&nbsp; So.=
 assuming you used ALL, I'd expect:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; C=3D1{Subtract=3D*{Stati=
stics{...}, Statistics{...}....}.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; C=3D2{...</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; ....</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A185.FDD34BD0--

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


From daemon@optimus.ietf.org  Sun Jan 20 03:14:55 2002
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 DAA07859
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 03:14:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA10637
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 03:14:57 -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 CAA09856;
	Sun, 20 Jan 2002 02:52:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09829
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 02:51:59 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA07664
	for <megaco@ietf.org>; Sun, 20 Jan 2002 02:51:54 -0500 (EST)
Received: through eSafe SMTP Relay 1010332213; Sun Jan 20 10:07:34 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FW1J>; Sun, 20 Jan 2002 09:42:28 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189C88D@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Tom-PT Taylor <taylor@nortelnetworks.com>, jsegers@LUCENT.COM,
        "Rosen, Brian" <Brian.Rosen@marconi.com>, megaco@ietf.org
Date: Sun, 20 Jan 2002 09:42:20 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A185.FDD34BD0"
Subject: [Megaco] wildcard response
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A185.FDD34BD0
Content-Type: text/plain

This is a part of a thread that stopped in September 2000, but it is not
clear to me how it was resolved.  What Brian wrote agrees with the ABNF, and
what Tom and John wrote is consistent with section 6.2.2, but they
contradict each other.  The thread ended with this, seeming to imply
agreement with Tom and John, but I do not see that the ABNF was amended to
allow lists at the parameter value level.

Raphael Tryster

Message-ID:  <39B609EF.32950A75@lucent.com>
Date:         Wed, 6 Sep 2000 11:10:07 +0200
Reply-To: John Segers <jsegers@LUCENT.COM>
Sender: "Media Gateway Control (megaco)"
<MEGACO@STANDARDS.NORTELNETWORKS.COM>
From: John Segers <jsegers@LUCENT.COM>
Organization: Lucent Technologies
Subject:      Re: Transaction Reply Context=ALL, wilcard response
To: MEGACO@STANDARDS.NORTELNETWORKS.COM
Content-Transfer-Encoding: 7bit

Tom,

This is my understanding as well.  Relevant text appears in section
6.2.2:
        If individual responses are not required, a wildcard response
        may be requested.  In such a case, a single response is
        generated, which contains the UNION of all of the individual
        responses which otherwise would have been generated, with
        duplicate values suppressed.  For instance, given a Termination
        Ta with properties p1=a, p2=b and Termination Tb with
        properties p2=c, p3=d, a UNION response would consist of a
        wildcarded TerminationId and the sequence of properties p1=a,
        p2=b,c and p3=d.

Cheers,

John

Tom-PT Taylor wrote:
>
> I always understood the intent of "W-" to mean that the response would
show
> unions at the most atomic level (i.e. per-parameter).  In other words, it
> was meant to show the range of values supported, not something
intelligible
> on a per-session basis.  I have to admit that it isn't necessarily clear
> what a "parameter" is in SDP (i.e.) would all "a=fmtp:" be collapsed into
> one list?
>
> > -----Original Message-----
> > From: Shalini Philip [mailto:sphilip@GLOBESPAN.NET]
> > Sent: Tuesday, September 05, 2000 4:21 AM
> > To: MEGACO@STANDARDS.NORTELNETWORKS.COM
> > Subject: Re: Transaction Reply Context=ALL, wilcard response
> >
> >
> > Hello Brian, Christian & list.
> >
> >         The example given below shows multiple Statistics
> > descriptors in
> > the descriptor list for a command reply. I believe,
> > the common understanding is that only the digit map descriptor and the
> > error descriptors are the only two descriptors
> > which can be repeated. If other descriptors can also be repeated, then
> > we can have multiple Mux descriptors, if the
> > MG supports multiple MUX types.
> > Also since it is not feasible to take the union of SDP definitions in
> > local and remote descriptors, I guess we can even have
> > multiple local and remote descriptors , or do we put them as multiple
> > SDP definitions in the same local/remote descriptor.
> >
> > Thanks & Regards,
> >   Shalini Philip.
> >
> >
> > "Rosen, Brian" wrote:
> >
> > >  I don't think you can do a subtract with CHOOSE.
> > > You could use ALL, but not choose.
> > >
> > > If you ask for a wildcard response, I think you get one response per
> > > value found, if they are different.  Since you get statistics on
> > > results, any identical statistics reports would only be
> > > repeated once.  So. assuming you used ALL, I'd expect:
> > > C=1{Subtract=*{Statistics{...}, Statistics{...}....}.
> > > C=2{...
> > > ....
> > >


------_=_NextPart_001_01C1A185.FDD34BD0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>wildcard response</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is a part of a thread that stopped =
in September 2000, but it is not clear to me how it was resolved.&nbsp; W=
hat Brian wrote agrees with the ABNF, and what Tom and John wrote is cons=
istent with section 6.2.2, but they contradict each other.&nbsp; The thre=
ad ended with this, seeming to imply agreement with Tom and John, but I d=
o not see that the ABNF was amended to allow lists at the parameter value=
 level.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Message-ID:&nbsp; &lt;39B609EF.32950A75@=
lucent.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Wed, 6 Sep 2000 11:10:07 +0200</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Reply-To: John Segers &lt;jsegers@LUCEN=
T.COM&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sender: &quot;Media Gateway Control (me=
gaco)&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; &lt;MEGACO@STANDARDS.NORTELNETWORKS.COM&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: John Segers &lt;jsegers@LUCENT.CO=
M&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Organization: Lucent Technologies</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Re: Transaction Reply Context=3DALL, wilcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: MEGACO@STANDARDS.NORTELNETWORKS.COM=
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Transfer-Encoding: 7bit</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tom,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is my understanding as well.&nbsp; =
Relevant text appears in section</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">6.2.2:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; If individual responses are not required, a wildcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; may be requested.&nbsp; In such a case, a single response is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; generated, which contains the UNION of all of the individual</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; responses which otherwise would have been generated, with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; duplicate values suppressed.&nbsp; For instance, given a Termination<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Ta with properties p1=3Da, p2=3Db and Termination Tb with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; properties p2=3Dc, p3=3Dd, a UNION response would consist of a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; wildcarded TerminationId and the sequence of properties p1=3Da,</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; p2=3Db,c and p3=3Dd.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">John</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tom-PT Taylor wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; I always understood the intent of =
&quot;W-&quot; to mean that the response would show</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; unions at the most atomic level (i=

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; was meant to show the range of val=
ues supported, not something intelligible</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; on a per-session basis.&nbsp; I ha=
ve to admit that it isn't necessarily clear</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; what a &quot;parameter&quot; is in=
 SDP (i.e.) would all &quot;a=3Dfmtp:&quot; be collapsed into</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; one list?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; -----Original Message-----</F=
ONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; From: Shalini Philip [<A HREF=
=3D"mailto:sphilip@GLOBESPAN.NET">mailto:sphilip@GLOBESPAN.NET</A>]</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Sent: Tuesday, September 05, =
2000 4:21 AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; To: MEGACO@STANDARDS.NORTELNE=
TWORKS.COM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Subject: Re: Transaction Repl=
y Context=3DALL, wilcard response</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Hello Brian, Christian &amp; =
list.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; The example given below shows multiple Statistics</FON=
T>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; descriptors in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; the descriptor list for a com=
mand reply. I believe,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; the common understanding is t=
hat only the digit map descriptor and the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; error descriptors are the onl=
y two descriptors</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; which can be repeated. If oth=
er descriptors can also be repeated, then</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; we can have multiple Mux desc=
riptors, if the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; MG supports multiple MUX type=
s.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Also since it is not feasible=
 to take the union of SDP definitions in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; local and remote descriptors,=
 I guess we can even have</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; multiple local and remote des=
criptors , or do we put them as multiple</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; SDP definitions in the same l=
ocal/remote descriptor.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; Thanks &amp; Regards,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;&nbsp;&nbsp; Shalini Philip.</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &quot;Rosen, Brian&quot; wrot=
e:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;&nbsp; I don't think you =
can do a subtract with CHOOSE.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; You could use ALL, but n=
ot choose.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; If you ask for a wildcar=
d response, I think you get one response per</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; value found, if they are=
 different.&nbsp; Since you get statistics on</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; results, any identical s=
tatistics reports would only be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; repeated once.&nbsp; So.=
 assuming you used ALL, I'd expect:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; C=3D1{Subtract=3D*{Stati=
stics{...}, Statistics{...}....}.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; C=3D2{...</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt; ....</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; &gt; &gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A185.FDD34BD0--

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



From megaco-admin@ietf.org  Sun Jan 20 15:26:25 2002
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 PAA15634
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 15:26:25 -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 PAA26080;
	Sun, 20 Jan 2002 15:12:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26049
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 15:12:41 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15493
	for <Megaco@ietf.org>; Sun, 20 Jan 2002 15:12:36 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA25344;
	Sun, 20 Jan 2002 14:12:08 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0KKC8r13383;
	Sun, 20 Jan 2002 14:12:08 -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 g0KKBRG00099;
	Sun, 20 Jan 2002 14:11:27 -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 g0KKBRT16230;
	Sun, 20 Jan 2002 14:11:27 -0600 (CST)
Message-ID: <3C4B246F.97219223@alcatel.com>
Date: Sun, 20 Jan 2002 14:11:27 -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: Terry L Anderson <tla@lucent.com>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: Re: [Megaco] NotifyCompletion Question
References: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com> <3C46EF5D.BF00B7E1@lucent.com>
Content-Type: multipart/alternative;
 boundary="------------F514414BF798B827F59CE2B4"
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


--------------F514414BF798B827F59CE2B4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



I am not sure we have addressed Carl's concern here.

What he is saying makes everything clear to me now and it makes better sense
than what is already
defined in the ABNF.
I didn't really understood how this NotifyCompletion really worked and I think
I had raised some questions on it before.


   signalRequest        = signalName [ LBRKT sigParameter
                          *(COMMA sigParameter) RBRKT ]

   sigParameter    = sigStream / sigSignalType / sigDuration / sigOther
                   / notifyCompletion / KeepActiveToken

   notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
                   notificationReason *(COMMA notificationReason) RBRKT

   notificationReason   = ( TimeOutToken / InterruptByEventToken
                                / InterruptByNewSignalsDescrToken
                                / OtherReasonToken )

Because of the above ABNF, my intepretation is that MGC specifies to MG that it
needs to report
signal completion based on the reason(s) that MGC has specified.
If the signal completion was not due to one of the reasons specified by the MGC
then
don't report the signal completion.
When the signal completed and the reason matches one specified by MGC, MG
reports
the signal completion w/the reason.

Tom, I am not sure if your change to Event sc makes any difference here to the
actual implementation.

I think Carl is suggesting the following (correct me if I am wrong)

   notifyCompletion    = "ON/OFF"

This is a change in syntax which will break current implementation.

I am using notifyCompletionRequest because we still have to keep
notifyCompletion for
the reporting of the signal completion in the EventDescriptor.

Since this is a BIG syntax change, it can't be done in V1 or an update to IG.
For V2, it will still be a big problem due to backward compatibilty requirement.

Chuong



Terry L Anderson wrote:

> I agree.  I will add to IG.
>
> Tom-PT Taylor wrote:
>
> > The error is in the Annex E text.  This material was a fairly late addition
> > (part of the enormous amount of work we did in the Feb'00 meeting in
> > Geneva), and an inconsistency crept in.  You are the first to spot it.  The
> > text should read:
> >
> > Signal Completion
> >       EventID: sc (0x0002)
> >       Indicates termination of one or more signals for which the
> >       notifyCompletion parameter was set to enable reporting of a
> >       completion event.  For further procedural description, see
> >       sections 7.1.11, 7.1.17, and 7.2.7.
> >
> > -----Original Message-----
> > From: Carl Rutter [mailto:crutter@telica.com]
> > Sent: Thursday, January 17, 2002 10:04 AM
> > To: 'Megaco@ietf.org'
> > Subject: [Megaco] NotifyCompletion Question
> >
> > For V1 the possible values of NotifyCompletion reason are:
> >
> > notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
> >           notificationReason *(COMMA notificationReason) RBRKT)
> >
> >    notificationReason   = ( TimeOutToken / InterruptByEventToken
> >                / InterruptByNewSignalsDescrToken
> >                / OtherReasonToken )
> >
> > So when an MGC wants the MG to notify a completion of a Signal
> > the MGC would specify:
> >
> > NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
> > for)
> >
> > Is this correct???
> >
> > The reason I ask is later in the RFC there is this:
> > Signal Completion
> >       EventID: sc (0x0002)
> >       Indicates termination of one or more signals for which the
> >       notifyCompletion parameter was set to "ON".  For further
> >       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7.
> >
> > Which seems to indicate that the NC really should be an ON or OFF value and
> > the 4 notificationReasons are really just return values.
> >
> > Thanks,
> > Carl
> >
> > Carl Rutter
> > Telica, Inc.
> > Building G, Suite 100
> > 734 Forest Street
> > Marlboro, MA 01752
> > Email crutter@telica.com
> > Voice 508-480-0909 x8178
> > Fax 508-480-0922
> > www.telica.com
> >
> > _______________________________________________
> > 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson             mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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



--------------F514414BF798B827F59CE2B4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>I am not sure we have addressed Carl's concern here.
<p>What he is saying makes everything clear to me now and it makes better
sense than what is already
<br>defined in the ABNF.
<br>I didn't really understood how this NotifyCompletion really worked
and I think
<br>I had raised some questions on it before.
<br>&nbsp;
<p>&nbsp;&nbsp; signalRequest&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= signalName [ LBRKT sigParameter
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*(COMMA sigParameter) RBRKT ]
<p>&nbsp;&nbsp; sigParameter&nbsp;&nbsp;&nbsp; = sigStream / sigSignalType
/ sigDuration / sigOther
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ notifyCompletion / KeepActiveToken
<p>&nbsp;&nbsp; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; = NotifyCompletionToken
EQUAL (LBRKT
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notificationReason *(COMMA notificationReason) RBRKT
<p>&nbsp;&nbsp; notificationReason&nbsp;&nbsp; = ( TimeOutToken / InterruptByEventToken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ InterruptByNewSignalsDescrToken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ OtherReasonToken )
<p>Because of the above ABNF, my intepretation is that MGC specifies to
MG that it needs to report
<br>signal completion based on the reason(s) that MGC has specified.
<br>If the signal completion was not due to one of the reasons specified
by the MGC then
<br>don't report the signal completion.
<br>When the signal completed and the reason matches one specified by MGC,
MG reports
<br>the signal completion w/the reason.
<p>Tom, I am not sure if your change to Event sc makes any difference here
to the actual implementation.
<p>I think Carl is suggesting the following (correct me if I am wrong)
<p>&nbsp;&nbsp; <b>notifyCompletion&nbsp;&nbsp;&nbsp; = "ON/OFF"</b>
<p>This is a change in syntax which will break current implementation.
<p>I am using notifyCompletionRequest because we still have to keep notifyCompletion
for
<br>the reporting of the signal completion in the EventDescriptor.
<p>Since this is a BIG syntax change, it can't be done in V1 or an update
to IG.
<br>For V2, it will still be a big problem due to backward compatibilty
requirement.
<p>Chuong
<br>&nbsp;
<br>&nbsp;
<p>Terry L Anderson wrote:
<blockquote TYPE=CITE>I agree.&nbsp; I will add to IG.
<p>Tom-PT Taylor wrote:
<p>> The error is in the Annex E text.&nbsp; This material was a fairly
late addition
<br>> (part of the enormous amount of work we did in the Feb'00 meeting
in
<br>> Geneva), and an inconsistency crept in.&nbsp; You are the first to
spot it.&nbsp; The
<br>> text should read:
<br>>
<br>> Signal Completion
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination of one
or more signals for which the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion parameter was
set to enable reporting of a
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; completion event.&nbsp; For further
procedural description, see
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sections 7.1.11, 7.1.17, and
7.2.7.
<br>>
<br>> -----Original Message-----
<br>> From: Carl Rutter [<a href="mailto:crutter@telica.com">mailto:crutter@telica.com</a>]
<br>> Sent: Thursday, January 17, 2002 10:04 AM
<br>> To: 'Megaco@ietf.org'
<br>> Subject: [Megaco] NotifyCompletion Question
<br>>
<br>> For V1 the possible values of NotifyCompletion reason are:
<br>>
<br>> notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; = NotifyCompletionToken
EQUAL (LBRKT
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notificationReason
*(COMMA notificationReason) RBRKT)
<br>>
<br>>&nbsp;&nbsp;&nbsp; notificationReason&nbsp;&nbsp; = ( TimeOutToken
/ InterruptByEventToken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ InterruptByNewSignalsDescrToken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ OtherReasonToken )
<br>>
<br>> So when an MGC wants the MG to notify a completion of a Signal
<br>> the MGC would specify:
<br>>
<br>> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be
notified
<br>> for)
<br>>
<br>> Is this correct???
<br>>
<br>> The reason I ask is later in the RFC there is this:
<br>> Signal Completion
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination of one
or more signals for which the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion parameter was
set to "ON".&nbsp; For further
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; procedural description, see sections
7.1.11, 7.1.17, and 7.2.7.
<br>>
<br>> Which seems to indicate that the NC really should be an ON or OFF
value and
<br>> the 4 notificationReasons are really just return values.
<br>>
<br>> Thanks,
<br>> Carl
<br>>
<br>> Carl Rutter
<br>> Telica, Inc.
<br>> Building G, Suite 100
<br>> 734 Forest Street
<br>> Marlboro, MA 01752
<br>> Email crutter@telica.com
<br>> Voice 508-480-0909 x8178
<br>> Fax 508-480-0922
<br>> www.telica.com
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<p>--
<p>------------------------------------------------------------
<br>Terry L Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<a href="mailto:tla@lucent.com">mailto:tla@lucent.com</a>
<br>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729
<br>Lucent Technologies/INS/Voice Over IP Access Networks
<br>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
<br><a href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</a>
(Lucent internal) <a href="http://www.gti.net/tla">http://www.gti.net/tla</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------F514414BF798B827F59CE2B4--


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


From daemon@optimus.ietf.org  Sun Jan 20 15:26:26 2002
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 PAA15645
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 15:26:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA26241
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 15:26:30 -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 PAA26080;
	Sun, 20 Jan 2002 15:12:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26049
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 15:12:41 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15493
	for <Megaco@ietf.org>; Sun, 20 Jan 2002 15:12:36 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA25344;
	Sun, 20 Jan 2002 14:12:08 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0KKC8r13383;
	Sun, 20 Jan 2002 14:12:08 -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 g0KKBRG00099;
	Sun, 20 Jan 2002 14:11:27 -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 g0KKBRT16230;
	Sun, 20 Jan 2002 14:11:27 -0600 (CST)
Message-ID: <3C4B246F.97219223@alcatel.com>
Date: Sun, 20 Jan 2002 14:11:27 -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: Terry L Anderson <tla@lucent.com>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'Carl Rutter'" <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: Re: [Megaco] NotifyCompletion Question
References: <4D79C746863DD51197690002A52CDA000102AE6F@zcard0kc.ca.nortel.com> <3C46EF5D.BF00B7E1@lucent.com>
Content-Type: multipart/alternative;
 boundary="------------F514414BF798B827F59CE2B4"
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


--------------F514414BF798B827F59CE2B4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



I am not sure we have addressed Carl's concern here.

What he is saying makes everything clear to me now and it makes better sense
than what is already
defined in the ABNF.
I didn't really understood how this NotifyCompletion really worked and I think
I had raised some questions on it before.


   signalRequest        = signalName [ LBRKT sigParameter
                          *(COMMA sigParameter) RBRKT ]

   sigParameter    = sigStream / sigSignalType / sigDuration / sigOther
                   / notifyCompletion / KeepActiveToken

   notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
                   notificationReason *(COMMA notificationReason) RBRKT

   notificationReason   = ( TimeOutToken / InterruptByEventToken
                                / InterruptByNewSignalsDescrToken
                                / OtherReasonToken )

Because of the above ABNF, my intepretation is that MGC specifies to MG that it
needs to report
signal completion based on the reason(s) that MGC has specified.
If the signal completion was not due to one of the reasons specified by the MGC
then
don't report the signal completion.
When the signal completed and the reason matches one specified by MGC, MG
reports
the signal completion w/the reason.

Tom, I am not sure if your change to Event sc makes any difference here to the
actual implementation.

I think Carl is suggesting the following (correct me if I am wrong)

   notifyCompletion    = "ON/OFF"

This is a change in syntax which will break current implementation.

I am using notifyCompletionRequest because we still have to keep
notifyCompletion for
the reporting of the signal completion in the EventDescriptor.

Since this is a BIG syntax change, it can't be done in V1 or an update to IG.
For V2, it will still be a big problem due to backward compatibilty requirement.

Chuong



Terry L Anderson wrote:

> I agree.  I will add to IG.
>
> Tom-PT Taylor wrote:
>
> > The error is in the Annex E text.  This material was a fairly late addition
> > (part of the enormous amount of work we did in the Feb'00 meeting in
> > Geneva), and an inconsistency crept in.  You are the first to spot it.  The
> > text should read:
> >
> > Signal Completion
> >       EventID: sc (0x0002)
> >       Indicates termination of one or more signals for which the
> >       notifyCompletion parameter was set to enable reporting of a
> >       completion event.  For further procedural description, see
> >       sections 7.1.11, 7.1.17, and 7.2.7.
> >
> > -----Original Message-----
> > From: Carl Rutter [mailto:crutter@telica.com]
> > Sent: Thursday, January 17, 2002 10:04 AM
> > To: 'Megaco@ietf.org'
> > Subject: [Megaco] NotifyCompletion Question
> >
> > For V1 the possible values of NotifyCompletion reason are:
> >
> > notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT
> >           notificationReason *(COMMA notificationReason) RBRKT)
> >
> >    notificationReason   = ( TimeOutToken / InterruptByEventToken
> >                / InterruptByNewSignalsDescrToken
> >                / OtherReasonToken )
> >
> > So when an MGC wants the MG to notify a completion of a Signal
> > the MGC would specify:
> >
> > NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified
> > for)
> >
> > Is this correct???
> >
> > The reason I ask is later in the RFC there is this:
> > Signal Completion
> >       EventID: sc (0x0002)
> >       Indicates termination of one or more signals for which the
> >       notifyCompletion parameter was set to "ON".  For further
> >       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7.
> >
> > Which seems to indicate that the NC really should be an ON or OFF value and
> > the 4 notificationReasons are really just return values.
> >
> > Thanks,
> > Carl
> >
> > Carl Rutter
> > Telica, Inc.
> > Building G, Suite 100
> > 734 Forest Street
> > Marlboro, MA 01752
> > Email crutter@telica.com
> > Voice 508-480-0909 x8178
> > Fax 508-480-0922
> > www.telica.com
> >
> > _______________________________________________
> > 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson             mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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



--------------F514414BF798B827F59CE2B4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>I am not sure we have addressed Carl's concern here.
<p>What he is saying makes everything clear to me now and it makes better
sense than what is already
<br>defined in the ABNF.
<br>I didn't really understood how this NotifyCompletion really worked
and I think
<br>I had raised some questions on it before.
<br>&nbsp;
<p>&nbsp;&nbsp; signalRequest&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= signalName [ LBRKT sigParameter
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*(COMMA sigParameter) RBRKT ]
<p>&nbsp;&nbsp; sigParameter&nbsp;&nbsp;&nbsp; = sigStream / sigSignalType
/ sigDuration / sigOther
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ notifyCompletion / KeepActiveToken
<p>&nbsp;&nbsp; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; = NotifyCompletionToken
EQUAL (LBRKT
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
notificationReason *(COMMA notificationReason) RBRKT
<p>&nbsp;&nbsp; notificationReason&nbsp;&nbsp; = ( TimeOutToken / InterruptByEventToken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ InterruptByNewSignalsDescrToken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ OtherReasonToken )
<p>Because of the above ABNF, my intepretation is that MGC specifies to
MG that it needs to report
<br>signal completion based on the reason(s) that MGC has specified.
<br>If the signal completion was not due to one of the reasons specified
by the MGC then
<br>don't report the signal completion.
<br>When the signal completed and the reason matches one specified by MGC,
MG reports
<br>the signal completion w/the reason.
<p>Tom, I am not sure if your change to Event sc makes any difference here
to the actual implementation.
<p>I think Carl is suggesting the following (correct me if I am wrong)
<p>&nbsp;&nbsp; <b>notifyCompletion&nbsp;&nbsp;&nbsp; = "ON/OFF"</b>
<p>This is a change in syntax which will break current implementation.
<p>I am using notifyCompletionRequest because we still have to keep notifyCompletion
for
<br>the reporting of the signal completion in the EventDescriptor.
<p>Since this is a BIG syntax change, it can't be done in V1 or an update
to IG.
<br>For V2, it will still be a big problem due to backward compatibilty
requirement.
<p>Chuong
<br>&nbsp;
<br>&nbsp;
<p>Terry L Anderson wrote:
<blockquote TYPE=CITE>I agree.&nbsp; I will add to IG.
<p>Tom-PT Taylor wrote:
<p>> The error is in the Annex E text.&nbsp; This material was a fairly
late addition
<br>> (part of the enormous amount of work we did in the Feb'00 meeting
in
<br>> Geneva), and an inconsistency crept in.&nbsp; You are the first to
spot it.&nbsp; The
<br>> text should read:
<br>>
<br>> Signal Completion
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination of one
or more signals for which the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion parameter was
set to enable reporting of a
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; completion event.&nbsp; For further
procedural description, see
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sections 7.1.11, 7.1.17, and
7.2.7.
<br>>
<br>> -----Original Message-----
<br>> From: Carl Rutter [<a href="mailto:crutter@telica.com">mailto:crutter@telica.com</a>]
<br>> Sent: Thursday, January 17, 2002 10:04 AM
<br>> To: 'Megaco@ietf.org'
<br>> Subject: [Megaco] NotifyCompletion Question
<br>>
<br>> For V1 the possible values of NotifyCompletion reason are:
<br>>
<br>> notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; = NotifyCompletionToken
EQUAL (LBRKT
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notificationReason
*(COMMA notificationReason) RBRKT)
<br>>
<br>>&nbsp;&nbsp;&nbsp; notificationReason&nbsp;&nbsp; = ( TimeOutToken
/ InterruptByEventToken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ InterruptByNewSignalsDescrToken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ OtherReasonToken )
<br>>
<br>> So when an MGC wants the MG to notify a completion of a Signal
<br>> the MGC would specify:
<br>>
<br>> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be
notified
<br>> for)
<br>>
<br>> Is this correct???
<br>>
<br>> The reason I ask is later in the RFC there is this:
<br>> Signal Completion
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination of one
or more signals for which the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion parameter was
set to "ON".&nbsp; For further
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; procedural description, see sections
7.1.11, 7.1.17, and 7.2.7.
<br>>
<br>> Which seems to indicate that the NC really should be an ON or OFF
value and
<br>> the 4 notificationReasons are really just return values.
<br>>
<br>> Thanks,
<br>> Carl
<br>>
<br>> Carl Rutter
<br>> Telica, Inc.
<br>> Building G, Suite 100
<br>> 734 Forest Street
<br>> Marlboro, MA 01752
<br>> Email crutter@telica.com
<br>> Voice 508-480-0909 x8178
<br>> Fax 508-480-0922
<br>> www.telica.com
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<p>--
<p>------------------------------------------------------------
<br>Terry L Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<a href="mailto:tla@lucent.com">mailto:tla@lucent.com</a>
<br>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729
<br>Lucent Technologies/INS/Voice Over IP Access Networks
<br>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
<br><a href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</a>
(Lucent internal) <a href="http://www.gti.net/tla">http://www.gti.net/tla</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------F514414BF798B827F59CE2B4--


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



From megaco-admin@ietf.org  Sun Jan 20 15:38:33 2002
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 PAA15810
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 15:38:33 -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 PAA26568;
	Sun, 20 Jan 2002 15:30:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26525
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 15:30:41 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15736
	for <megaco@ietf.org>; Sun, 20 Jan 2002 15:30:36 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0KKUSIB005443;
	Sun, 20 Jan 2002 21:30:28 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0KKURr6021662;
	Sun, 20 Jan 2002 22:30:27 +0200 (EET)
Message-ID: <3C4B2907.317149C6@lmf.ericsson.se>
Date: Sun, 20 Jan 2002 22:31:03 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I have read the document a few times, but even by having stream
descriptors in the mux termination, I still don't understand how each of
those stream descriptors are mapped to specific LNCs. Is the StreamID
supposed to be the same as the LCN number, or how is the mapping done?

A very simple solution would be to add a "LCN property" (to the H.324
package, I assume) which would be used in the each stream descriptor to
specify to which LCN it is mapped. 

Comments?

Regards,

Christer Holmberg
Ericsson Finland



Tom-PT Taylor wrote:
> 
> I mentioned that several of us have been discussing additional text for
> Multiplex Descriptors.  I have placed the proposed text as marked up changes
> in the Megaco FTP site.  According to your taste, you can download
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> x64K.doc
> or
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> x64K.pdf
> 
> Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> proposed text needs a further update.  The supporting bearers contained by a
> multiplexing termination can be ephemeral as well as physical.  However, I
> believe it would be essential that any ephemrals mentioned in a MUX
> descriptor already exist in the context, since their properties are probably
> not directly inferrable from those of the multiplexing termination.
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Sun Jan 20 15:38:33 2002
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 PAA15819
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 15:38:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA26783
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 15:38:38 -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 PAA26568;
	Sun, 20 Jan 2002 15:30:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26525
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 15:30:41 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15736
	for <megaco@ietf.org>; Sun, 20 Jan 2002 15:30:36 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0KKUSIB005443;
	Sun, 20 Jan 2002 21:30:28 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0KKURr6021662;
	Sun, 20 Jan 2002 22:30:27 +0200 (EET)
Message-ID: <3C4B2907.317149C6@lmf.ericsson.se>
Date: Sun, 20 Jan 2002 22:31:03 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I have read the document a few times, but even by having stream
descriptors in the mux termination, I still don't understand how each of
those stream descriptors are mapped to specific LNCs. Is the StreamID
supposed to be the same as the LCN number, or how is the mapping done?

A very simple solution would be to add a "LCN property" (to the H.324
package, I assume) which would be used in the each stream descriptor to
specify to which LCN it is mapped. 

Comments?

Regards,

Christer Holmberg
Ericsson Finland



Tom-PT Taylor wrote:
> 
> I mentioned that several of us have been discussing additional text for
> Multiplex Descriptors.  I have placed the proposed text as marked up changes
> in the Megaco FTP site.  According to your taste, you can download
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> x64K.doc
> or
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> x64K.pdf
> 
> Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> proposed text needs a further update.  The supporting bearers contained by a
> multiplexing termination can be ephemeral as well as physical.  However, I
> believe it would be essential that any ephemrals mentioned in a MUX
> descriptor already exist in the context, since their properties are probably
> not directly inferrable from those of the multiplexing termination.
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Sun Jan 20 17:27:20 2002
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 RAA16871
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 17:27:16 -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 RAA28942;
	Sun, 20 Jan 2002 17:14:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28917
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 17:14:21 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16757
	for <megaco@ietf.org>; Sun, 20 Jan 2002 17:14:15 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id QAA19292
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:13:49 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0KMDmr17238
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:13:48 -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 g0KMCtG19857
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:12:55 -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 g0KMCtT16435
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:12:55 -0600 (CST)
Message-ID: <3C4B40E7.F79408DC@alcatel.com>
Date: Sun, 20 Jan 2002 16:12:55 -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" <megaco@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------3FF3187EB6E8D9E491DA2D7E"
Subject: [Megaco] Cancel ServiceChange Graceful
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


--------------3FF3187EB6E8D9E491DA2D7E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Tom

What are the possibilites of defining a mechanism of cancelling
ServiceChange Graceful?
That is MG send SC Graceful w/Delay=time.
Before time expired, MG wants to cancel this ServiceChange.

1) Can this be done in V1 by adding a new SC Reason like "916 SC
Graceful cancelled"?
2) Done in V2 - new SC Method or Reason?
3) Should be covered in draft-hss-megaco-control-association?


Thanks
Chuong



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



--------------3FF3187EB6E8D9E491DA2D7E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Tom
<p>What are the possibilites of defining a mechanism of cancelling ServiceChange
Graceful?
<br>That is MG send SC Graceful w/Delay=time.
<br>Before time expired, MG wants to cancel this ServiceChange.
<p>1) Can this be done in V1 by adding a new SC Reason like "916 SC Graceful
cancelled"?
<br>2) Done in V2 - new SC Method or Reason?
<br>3) Should be covered in draft-hss-megaco-control-association?
<br>&nbsp;
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------3FF3187EB6E8D9E491DA2D7E--


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


From daemon@optimus.ietf.org  Sun Jan 20 17:27:21 2002
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 RAA16881
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 17:27:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA29069
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 17:27:26 -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 RAA28942;
	Sun, 20 Jan 2002 17:14:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28917
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 17:14:21 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16757
	for <megaco@ietf.org>; Sun, 20 Jan 2002 17:14:15 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id QAA19292
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:13:49 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0KMDmr17238
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:13:48 -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 g0KMCtG19857
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:12:55 -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 g0KMCtT16435
	for <megaco@ietf.org>; Sun, 20 Jan 2002 16:12:55 -0600 (CST)
Message-ID: <3C4B40E7.F79408DC@alcatel.com>
Date: Sun, 20 Jan 2002 16:12:55 -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" <megaco@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------3FF3187EB6E8D9E491DA2D7E"
Subject: [Megaco] Cancel ServiceChange Graceful
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


--------------3FF3187EB6E8D9E491DA2D7E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Tom

What are the possibilites of defining a mechanism of cancelling
ServiceChange Graceful?
That is MG send SC Graceful w/Delay=time.
Before time expired, MG wants to cancel this ServiceChange.

1) Can this be done in V1 by adding a new SC Reason like "916 SC
Graceful cancelled"?
2) Done in V2 - new SC Method or Reason?
3) Should be covered in draft-hss-megaco-control-association?


Thanks
Chuong



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



--------------3FF3187EB6E8D9E491DA2D7E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Tom
<p>What are the possibilites of defining a mechanism of cancelling ServiceChange
Graceful?
<br>That is MG send SC Graceful w/Delay=time.
<br>Before time expired, MG wants to cancel this ServiceChange.
<p>1) Can this be done in V1 by adding a new SC Reason like "916 SC Graceful
cancelled"?
<br>2) Done in V2 - new SC Method or Reason?
<br>3) Should be covered in draft-hss-megaco-control-association?
<br>&nbsp;
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------3FF3187EB6E8D9E491DA2D7E--


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



From megaco-admin@ietf.org  Sun Jan 20 22:24:54 2002
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 WAA20346
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:24:54 -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 WAA07052;
	Sun, 20 Jan 2002 22:11:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07023
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:23 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20215
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:16 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27780;
	Mon, 21 Jan 2002 14:09:58 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29034;
	Mon, 21 Jan 2002 14:11:19 +1100 (EST)
Message-ID: <3C4B87B2.B3F81BA2@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:14:58 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

I don't see that we need to add anything. Why can't the MG just issue a
SC with Restart, Service Restored? The specification already allows the
MG to do this.

Regards, Christian 

"Chuong N. Nguyen" wrote:
> 
> Hi Tom
> 
> What are the possibilites of defining a mechanism of cancelling
> ServiceChange Graceful?
> That is MG send SC Graceful w/Delay=time.
> Before time expired, MG wants to cancel this ServiceChange.
> 
> 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> Graceful cancelled"?
> 2) Done in V2 - new SC Method or Reason?
> 3) Should be covered in draft-hss-megaco-control-association?
> 
> 
> Thanks
> Chuong
> 
> 
> 
> --
>   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


From daemon@optimus.ietf.org  Sun Jan 20 22:24:55 2002
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 WAA20372
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:24:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07658
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 22:24:59 -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 WAA07052;
	Sun, 20 Jan 2002 22:11:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07023
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:23 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20215
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:16 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27780;
	Mon, 21 Jan 2002 14:09:58 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29034;
	Mon, 21 Jan 2002 14:11:19 +1100 (EST)
Message-ID: <3C4B87B2.B3F81BA2@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:14:58 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

I don't see that we need to add anything. Why can't the MG just issue a
SC with Restart, Service Restored? The specification already allows the
MG to do this.

Regards, Christian 

"Chuong N. Nguyen" wrote:
> 
> Hi Tom
> 
> What are the possibilites of defining a mechanism of cancelling
> ServiceChange Graceful?
> That is MG send SC Graceful w/Delay=time.
> Before time expired, MG wants to cancel this ServiceChange.
> 
> 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> Graceful cancelled"?
> 2) Done in V2 - new SC Method or Reason?
> 3) Should be covered in draft-hss-megaco-control-association?
> 
> 
> Thanks
> Chuong
> 
> 
> 
> --
>   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



From daemon@optimus.ietf.org  Sun Jan 20 22:24:56 2002
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 WAA20374
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:24:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07662
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 22:24:59 -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 WAA07096;
	Sun, 20 Jan 2002 22:11:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07061
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:26 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20219
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:20 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27833;
	Mon, 21 Jan 2002 14:10:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29046;
	Mon, 21 Jan 2002 14:11:22 +1100 (EST)
Message-ID: <3C4B87B5.C023A133@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:15:01 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] question about AuditDescriptor in v2
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D280@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Sunesh,

Yes you can have multiple indAudMEdiaDescriptor in the Audit Descriptor.
ie.
auditPropertyToken SEQUENCE OF IndAuditParameter OPTIONAL,

Regards, Christian

"Kumra Sunesh (NET/Helsinki)" wrote:
> 
> Hi,
> 
> Can AuditDescriptor have multiple occurrence of any particular
> indAudauditReturnParameter ? for e.g. can there be multiple
> indAudMediaDescriptor within an AuditDescriptor ?
> 
> Thanks in advance,
> sunesh
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Sun Jan 20 22:25:42 2002
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 WAA20408
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:25:42 -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 WAA07017;
	Sun, 20 Jan 2002 22:11:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06987
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:16 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20212
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27759;
	Mon, 21 Jan 2002 14:09:47 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29005;
	Mon, 21 Jan 2002 14:11:07 +1100 (EST)
Message-ID: <3C4B87A6.8F82385A@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:14:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

We already have this functionality in H.248 "Reserve Group" and "Reserve
Value". It allows the FID concept (group ID). With regards to sending
DTMF I thought that we used the signal mechanism for that. So I don't
think we need a change.

Regards, Christian

Troy Cauble wrote:
> 
> Terry L Anderson wrote:
> >
> > I am designating this issue as open issue #3.  Tom suggests that we change a
> > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > the statement was that multiple media streams in SDP should not occur in a
> > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > too restrictive.
> > (1) FID allows grouping multiple media lines (m lines) into a single media
> > stream and this should be allowed in a single H.248 StreamDescriptor.
> > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > distinct payload.  It also supports sending this payload to a different
> > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > coming from one termination (eg. PSTN) into two output streams, one containing
> > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > again requires multiple media (m) lines in the SDP.
> >
> > The current IG draft adds the following to 7.1.8 (right under the first set of
> > bullets):
> >
> > A Stream Descriptor specifies a single bi-directional media stream and so a
> > single session description MUST NOT include more than one media description
> > ("m=" line).  Any additional media streams for a termination must appear in
> > distinct Stream Descriptors.
> >
> > Perhaps we could change this to read:
> >
> > A Stream Descriptor specifies a single bi-directional media stream and so a
> > single session description MUST NOT specify multiple streams.  This often means
> > that the session description will contain only a single media description ("m="
> > line).  However, where media descriptions are grouped and refer to a single,
> > logical media stream but where payload packets may be sent to different
> > transport addresses, multiple media description lines may be required (e.g., RFC
> > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > Descriptors.
> > --------
> > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > Informative References, but I think this helps clarify the intent with an
> > example.  We cannot refer to FID as it is not yet an RFC.
> 
> I have no problem with the intent of this change.  You have to
> change the language to allow certain cases.  But the language
> is getting very fuzzy.
> 
> How do I tell a "single, logical media stream" from "multiple streams"?
> 
> Why is voice & RFC2833 DTMF a "single, logical stream", when
> audio + video is "multiple streams"?
> 
> When would an MG be handling multiple streams on a termination
> that are not "logically" related in some way?
> 
> Doesn't this really mean I can put as many "streams" as I want
> in my SDP and have just one StreamDescriptor?
> 
> -troy
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Sun Jan 20 22:25:43 2002
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 WAA20418
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:25:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07703
	for megaco-archive@odin.ietf.org; Sun, 20 Jan 2002 22:25:47 -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 WAA07017;
	Sun, 20 Jan 2002 22:11:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06987
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:16 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20212
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27759;
	Mon, 21 Jan 2002 14:09:47 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29005;
	Mon, 21 Jan 2002 14:11:07 +1100 (EST)
Message-ID: <3C4B87A6.8F82385A@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:14:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

We already have this functionality in H.248 "Reserve Group" and "Reserve
Value". It allows the FID concept (group ID). With regards to sending
DTMF I thought that we used the signal mechanism for that. So I don't
think we need a change.

Regards, Christian

Troy Cauble wrote:
> 
> Terry L Anderson wrote:
> >
> > I am designating this issue as open issue #3.  Tom suggests that we change a
> > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > the statement was that multiple media streams in SDP should not occur in a
> > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > too restrictive.
> > (1) FID allows grouping multiple media lines (m lines) into a single media
> > stream and this should be allowed in a single H.248 StreamDescriptor.
> > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > distinct payload.  It also supports sending this payload to a different
> > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > coming from one termination (eg. PSTN) into two output streams, one containing
> > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > again requires multiple media (m) lines in the SDP.
> >
> > The current IG draft adds the following to 7.1.8 (right under the first set of
> > bullets):
> >
> > A Stream Descriptor specifies a single bi-directional media stream and so a
> > single session description MUST NOT include more than one media description
> > ("m=" line).  Any additional media streams for a termination must appear in
> > distinct Stream Descriptors.
> >
> > Perhaps we could change this to read:
> >
> > A Stream Descriptor specifies a single bi-directional media stream and so a
> > single session description MUST NOT specify multiple streams.  This often means
> > that the session description will contain only a single media description ("m="
> > line).  However, where media descriptions are grouped and refer to a single,
> > logical media stream but where payload packets may be sent to different
> > transport addresses, multiple media description lines may be required (e.g., RFC
> > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > Descriptors.
> > --------
> > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > Informative References, but I think this helps clarify the intent with an
> > example.  We cannot refer to FID as it is not yet an RFC.
> 
> I have no problem with the intent of this change.  You have to
> change the language to allow certain cases.  But the language
> is getting very fuzzy.
> 
> How do I tell a "single, logical media stream" from "multiple streams"?
> 
> Why is voice & RFC2833 DTMF a "single, logical stream", when
> audio + video is "multiple streams"?
> 
> When would an MG be handling multiple streams on a termination
> that are not "logically" related in some way?
> 
> Doesn't this really mean I can put as many "streams" as I want
> in my SDP and have just one StreamDescriptor?
> 
> -troy
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Sun Jan 20 23:15:27 2002
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 WAA20347
	for <megaco-archive@odin.ietf.org>; Sun, 20 Jan 2002 22:24:54 -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 WAA07096;
	Sun, 20 Jan 2002 22:11:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07061
	for <megaco@optimus.ietf.org>; Sun, 20 Jan 2002 22:11:26 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20219
	for <megaco@ietf.org>; Sun, 20 Jan 2002 22:11:20 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA27833;
	Mon, 21 Jan 2002 14:10:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA29046;
	Mon, 21 Jan 2002 14:11:22 +1100 (EST)
Message-ID: <3C4B87B5.C023A133@ericsson.com.au>
Date: Mon, 21 Jan 2002 14:15:01 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kumra Sunesh (NET/Helsinki)" <Sunesh.Kumra@nokia.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] question about AuditDescriptor in v2
References: <0C1353ABB1DEB74DB067ADFF749C4EEF09D280@esebe004.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Sunesh,

Yes you can have multiple indAudMEdiaDescriptor in the Audit Descriptor.
ie.
auditPropertyToken SEQUENCE OF IndAuditParameter OPTIONAL,

Regards, Christian

"Kumra Sunesh (NET/Helsinki)" wrote:
> 
> Hi,
> 
> Can AuditDescriptor have multiple occurrence of any particular
> indAudauditReturnParameter ? for e.g. can there be multiple
> indAudMediaDescriptor within an AuditDescriptor ?
> 
> Thanks in advance,
> sunesh
> 
> _______________________________________________
> 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


From megaco-admin@ietf.org  Mon Jan 21 00:21:55 2002
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 AAA22599
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 00:21:55 -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 AAA10749;
	Mon, 21 Jan 2002 00:06:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA10720
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:05:59 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22483
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:05:54 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA15921;
	Mon, 21 Jan 2002 16:04:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA29183;
	Mon, 21 Jan 2002 16:05:49 +1100 (EST)
Message-ID: <3C4BA279.157FED8@ericsson.com.au>
Date: Mon, 21 Jan 2002 16:09:13 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com> <3C4B2907.317149C6@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Christer,

I think that the H.324 package probably needs to be updated to say how
this is done. I don't think its a core H.248 issue. Perhaps an IG note
could be added for the H324 package? I'd like to see a reply from the
H324 package authors on how they thought this was to be done.

Are there any updates you'd like to see to proposed text on
MultiplexDescriptors that Tom posted?

Regards, Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> I have read the document a few times, but even by having stream
> descriptors in the mux termination, I still don't understand how each of
> those stream descriptors are mapped to specific LNCs. Is the StreamID
> supposed to be the same as the LCN number, or how is the mapping done?
> 
> A very simple solution would be to add a "LCN property" (to the H.324
> package, I assume) which would be used in the each stream descriptor to
> specify to which LCN it is mapped.
> 
> Comments?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> Tom-PT Taylor wrote:
> >
> > I mentioned that several of us have been discussing additional text for
> > Multiplex Descriptors.  I have placed the proposed text as marked up changes
> > in the Megaco FTP site.  According to your taste, you can download
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > x64K.doc
> > or
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > x64K.pdf
> >
> > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > proposed text needs a further update.  The supporting bearers contained by a
> > multiplexing termination can be ephemeral as well as physical.  However, I
> > believe it would be essential that any ephemrals mentioned in a MUX
> > descriptor already exist in the context, since their properties are probably
> > not directly inferrable from those of the multiplexing termination.
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Mon Jan 21 00:21:55 2002
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 AAA22608
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 00:21:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA11004
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 00:21: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 AAA10749;
	Mon, 21 Jan 2002 00:06:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA10720
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:05:59 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22483
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:05:54 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA15921;
	Mon, 21 Jan 2002 16:04:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA29183;
	Mon, 21 Jan 2002 16:05:49 +1100 (EST)
Message-ID: <3C4BA279.157FED8@ericsson.com.au>
Date: Mon, 21 Jan 2002 16:09:13 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com> <3C4B2907.317149C6@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Christer,

I think that the H.324 package probably needs to be updated to say how
this is done. I don't think its a core H.248 issue. Perhaps an IG note
could be added for the H324 package? I'd like to see a reply from the
H324 package authors on how they thought this was to be done.

Are there any updates you'd like to see to proposed text on
MultiplexDescriptors that Tom posted?

Regards, Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> I have read the document a few times, but even by having stream
> descriptors in the mux termination, I still don't understand how each of
> those stream descriptors are mapped to specific LNCs. Is the StreamID
> supposed to be the same as the LCN number, or how is the mapping done?
> 
> A very simple solution would be to add a "LCN property" (to the H.324
> package, I assume) which would be used in the each stream descriptor to
> specify to which LCN it is mapped.
> 
> Comments?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> Tom-PT Taylor wrote:
> >
> > I mentioned that several of us have been discussing additional text for
> > Multiplex Descriptors.  I have placed the proposed text as marked up changes
> > in the Megaco FTP site.  According to your taste, you can download
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > x64K.doc
> > or
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > x64K.pdf
> >
> > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > proposed text needs a further update.  The supporting bearers contained by a
> > multiplexing termination can be ephemeral as well as physical.  However, I
> > believe it would be essential that any ephemrals mentioned in a MUX
> > descriptor already exist in the context, since their properties are probably
> > not directly inferrable from those of the multiplexing termination.
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Mon Jan 21 01:02:20 2002
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 BAA23085
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:02:20 -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 AAA11786;
	Mon, 21 Jan 2002 00:51:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11758
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:51:02 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22946
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:50:57 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0L5orw12621;
	Mon, 21 Jan 2002 06:50:53 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L5oqr6012794;
	Mon, 21 Jan 2002 07:50:52 +0200 (EET)
Message-ID: <3C4BAC68.FB47AA0B@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 07:51:36 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com> <3C4B2907.317149C6@lmf.ericsson.se> <3C4BA279.157FED8@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I think that the H.324 package probably needs to be updated to say how
>this is done. I don't think its a core H.248 issue.

I agree. The idea was that this property would be defined in the H.324
package, and then used within each stream descriptor in the Mux
Termination.

>Perhaps an IG note could be added for the H324 package? I'd like to see a reply from the
> H324 package authors on how they thought this was to be done.

>Are there any updates you'd like to see to proposed text on MultiplexDescriptors that Tom posted?

First, as Tom already mentioned, it should be updated so that it also
includes emphemeral bearer terminations (RTP terminations, for example).

Second, it should in detail, on a message level, describe how the
multiplexed connection is set up. Now it only says "use a stream
descriptor" - which means everyone is going to understand it their own
way, and we are going to have lots of interop problems when people start
implementing this :)

Third, it should also describe in detail how the H.223 (or whatever
multiplex method is used) descriptor is used, ie which terminations are
included etc, depending on on which "side" of the multiplexer the
terminations are.

Fourth, I think the whole Annex M.4 misses some things, but that's
another discussion...

I understand if you want to get this document ready before february, but
please let us do this correct from the beginning :)


Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I have read the document a few times, but even by having stream
> > descriptors in the mux termination, I still don't understand how each of
> > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > supposed to be the same as the LCN number, or how is the mapping done?
> >
> > A very simple solution would be to add a "LCN property" (to the H.324
> > package, I assume) which would be used in the each stream descriptor to
> > specify to which LCN it is mapped.
> >
> > Comments?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > I mentioned that several of us have been discussing additional text for
> > > Multiplex Descriptors.  I have placed the proposed text as marked up changes
> > > in the Megaco FTP site.  According to your taste, you can download
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.doc
> > > or
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.pdf
> > >
> > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > proposed text needs a further update.  The supporting bearers contained by a
> > > multiplexing termination can be ephemeral as well as physical.  However, I
> > > believe it would be essential that any ephemrals mentioned in a MUX
> > > descriptor already exist in the context, since their properties are probably
> > > not directly inferrable from those of the multiplexing termination.
> > >
> > > Tom Taylor
> > > taylor@nortelnetworks.com
> > > Ph. +1 613 736 0961 (ESN 396 1490)
> > >
> > >
> > > _______________________________________________
> > > 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


From daemon@optimus.ietf.org  Mon Jan 21 01:02:21 2002
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 BAA23095
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:02:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA12510
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 01:02:24 -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 AAA11786;
	Mon, 21 Jan 2002 00:51:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11758
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:51:02 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22946
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:50:57 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0L5orw12621;
	Mon, 21 Jan 2002 06:50:53 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L5oqr6012794;
	Mon, 21 Jan 2002 07:50:52 +0200 (EET)
Message-ID: <3C4BAC68.FB47AA0B@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 07:51:36 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AE71@zcard0kc.ca.nortel.com> <3C4B2907.317149C6@lmf.ericsson.se> <3C4BA279.157FED8@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I think that the H.324 package probably needs to be updated to say how
>this is done. I don't think its a core H.248 issue.

I agree. The idea was that this property would be defined in the H.324
package, and then used within each stream descriptor in the Mux
Termination.

>Perhaps an IG note could be added for the H324 package? I'd like to see a reply from the
> H324 package authors on how they thought this was to be done.

>Are there any updates you'd like to see to proposed text on MultiplexDescriptors that Tom posted?

First, as Tom already mentioned, it should be updated so that it also
includes emphemeral bearer terminations (RTP terminations, for example).

Second, it should in detail, on a message level, describe how the
multiplexed connection is set up. Now it only says "use a stream
descriptor" - which means everyone is going to understand it their own
way, and we are going to have lots of interop problems when people start
implementing this :)

Third, it should also describe in detail how the H.223 (or whatever
multiplex method is used) descriptor is used, ie which terminations are
included etc, depending on on which "side" of the multiplexer the
terminations are.

Fourth, I think the whole Annex M.4 misses some things, but that's
another discussion...

I understand if you want to get this document ready before february, but
please let us do this correct from the beginning :)


Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I have read the document a few times, but even by having stream
> > descriptors in the mux termination, I still don't understand how each of
> > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > supposed to be the same as the LCN number, or how is the mapping done?
> >
> > A very simple solution would be to add a "LCN property" (to the H.324
> > package, I assume) which would be used in the each stream descriptor to
> > specify to which LCN it is mapped.
> >
> > Comments?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > I mentioned that several of us have been discussing additional text for
> > > Multiplex Descriptors.  I have placed the proposed text as marked up changes
> > > in the Megaco FTP site.  According to your taste, you can download
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.doc
> > > or
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.pdf
> > >
> > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > proposed text needs a further update.  The supporting bearers contained by a
> > > multiplexing termination can be ephemeral as well as physical.  However, I
> > > believe it would be essential that any ephemrals mentioned in a MUX
> > > descriptor already exist in the context, since their properties are probably
> > > not directly inferrable from those of the multiplexing termination.
> > >
> > > Tom Taylor
> > > taylor@nortelnetworks.com
> > > Ph. +1 613 736 0961 (ESN 396 1490)
> > >
> > >
> > > _______________________________________________
> > > 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



From megaco-admin@ietf.org  Mon Jan 21 01:06:13 2002
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 BAA23138
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:06:13 -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 AAA12053;
	Mon, 21 Jan 2002 00:58:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11963
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:58:47 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23039
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:58:42 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0L5wUIB029300;
	Mon, 21 Jan 2002 06:58:30 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L5wTr6013182;
	Mon, 21 Jan 2002 07:58:29 +0200 (EET)
Message-ID: <3C4BAE32.FF83B281@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 07:59:14 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>,
        "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I agree with Christian. H.248 does not specify a way to "cancel"
commands - and if it does it shall be a generic way to do it, not only
for a specific case, and I think most agree that's not needed.

Regards,

Christer Holmberg
Ericsson Finland



Christian Groves wrote:
> 
> I don't see that we need to add anything. Why can't the MG just issue a
> SC with Restart, Service Restored? The specification already allows the
> MG to do this.
> 
> Regards, Christian
> 
> "Chuong N. Nguyen" wrote:
> >
> > Hi Tom
> >
> > What are the possibilites of defining a mechanism of cancelling
> > ServiceChange Graceful?
> > That is MG send SC Graceful w/Delay=time.
> > Before time expired, MG wants to cancel this ServiceChange.
> >
> > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > Graceful cancelled"?
> > 2) Done in V2 - new SC Method or Reason?
> > 3) Should be covered in draft-hss-megaco-control-association?
> >
> >
> > Thanks
> > Chuong
> >
> >
> >
> > --
> >   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 mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From daemon@optimus.ietf.org  Mon Jan 21 01:06:13 2002
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 BAA23150
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:06:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA14229
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 01:06: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 AAA12053;
	Mon, 21 Jan 2002 00:58:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11963
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 00:58:47 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23039
	for <megaco@ietf.org>; Mon, 21 Jan 2002 00:58:42 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0L5wUIB029300;
	Mon, 21 Jan 2002 06:58:30 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L5wTr6013182;
	Mon, 21 Jan 2002 07:58:29 +0200 (EET)
Message-ID: <3C4BAE32.FF83B281@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 07:59:14 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>,
        "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I agree with Christian. H.248 does not specify a way to "cancel"
commands - and if it does it shall be a generic way to do it, not only
for a specific case, and I think most agree that's not needed.

Regards,

Christer Holmberg
Ericsson Finland



Christian Groves wrote:
> 
> I don't see that we need to add anything. Why can't the MG just issue a
> SC with Restart, Service Restored? The specification already allows the
> MG to do this.
> 
> Regards, Christian
> 
> "Chuong N. Nguyen" wrote:
> >
> > Hi Tom
> >
> > What are the possibilites of defining a mechanism of cancelling
> > ServiceChange Graceful?
> > That is MG send SC Graceful w/Delay=time.
> > Before time expired, MG wants to cancel this ServiceChange.
> >
> > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > Graceful cancelled"?
> > 2) Done in V2 - new SC Method or Reason?
> > 3) Should be covered in draft-hss-megaco-control-association?
> >
> >
> > Thanks
> > Chuong
> >
> >
> >
> > --
> >   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 mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



From megaco-admin@ietf.org  Mon Jan 21 01:10:58 2002
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 BAA23221
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:10: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 BAA12579;
	Mon, 21 Jan 2002 01:03:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA12550
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 01:03:14 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23118
	for <megaco@ietf.org>; Mon, 21 Jan 2002 01:03:09 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0L63Aw18188;
	Mon, 21 Jan 2002 07:03:10 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L639r6013403;
	Mon, 21 Jan 2002 08:03:09 +0200 (EET)
Message-ID: <3C4BAF49.120DC511@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 08:03:53 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sudhirk@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Error descriptor when timed out
References: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>What Error will be reported by MG when MGC hasn't responded (for the request
>sent by MG itself) within the Execution Timer interval i.e., on a transaction
>time-out.
>Please mail me the supported Error Number for the above scenario.

To whom would this error be reported? If to the MG itself I don't think
you need any H.248 level error codes, because you will receive "host
unreachable" on the IP level...

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Mon Jan 21 01:10:59 2002
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 BAA23234
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 01:10:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA19004
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 01:11:02 -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 BAA12579;
	Mon, 21 Jan 2002 01:03:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA12550
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 01:03:14 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23118
	for <megaco@ietf.org>; Mon, 21 Jan 2002 01:03:09 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0L63Aw18188;
	Mon, 21 Jan 2002 07:03:10 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.30.3])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0L639r6013403;
	Mon, 21 Jan 2002 08:03:09 +0200 (EET)
Message-ID: <3C4BAF49.120DC511@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 08:03:53 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sudhirk@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Error descriptor when timed out
References: <000001c19dcd$485d11c0$3a07020a@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>What Error will be reported by MG when MGC hasn't responded (for the request
>sent by MG itself) within the Execution Timer interval i.e., on a transaction
>time-out.
>Please mail me the supported Error Number for the above scenario.

To whom would this error be reported? If to the MG itself I don't think
you need any H.248 level error codes, because you will receive "host
unreachable" on the IP level...

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Mon Jan 21 03:32:20 2002
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 DAA02717
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 03:32:20 -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 DAA25325;
	Mon, 21 Jan 2002 03:20:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25298
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 03:20:22 -0500 (EST)
Received: from bosvwl01 ([216.52.49.35])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02609
	for <megaco@ietf.org>; Mon, 21 Jan 2002 03:20:18 -0500 (EST)
Received: from 192.168.200.82 by bosvwl01 (InterScan E-Mail VirusWall NT); Mon, 21 Jan 2002 03:19:01 -0500
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 21 Jan 2002 13:48:36 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 21 Jan 2002 13:48:36 +0530
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Date: Mon, 21 Jan 2002 13:48:35 +0530
Message-ID: <56E2573C375A414191118970BDE06A1505604E16@kecmsg06.ad.infosys.com>
Thread-Topic: IPDC in VoATM Networks?
Thread-Index: AcGiVDopO83V6g4mEda8jAAA4hnv4A==
From: "Ramakrishnan" <ramki@infy.com>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 21 Jan 2002 08:18:36.0600 (UTC) FILETIME=[39566380:01C1A254]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA25299
Subject: [Megaco] IPDC in VoATM Networks?
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

Can IPDC be used as a Gateway Control Protocol in VoATM Networks?
Are there any limitations to it?

regards
Ramki
( mailto:ramki@infy.com )

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


From daemon@optimus.ietf.org  Mon Jan 21 03:32:21 2002
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 DAA02728
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 03:32:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA25960
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 03:32:24 -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 DAA25325;
	Mon, 21 Jan 2002 03:20:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25298
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 03:20:22 -0500 (EST)
Received: from bosvwl01 ([216.52.49.35])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02609
	for <megaco@ietf.org>; Mon, 21 Jan 2002 03:20:18 -0500 (EST)
Received: from 192.168.200.82 by bosvwl01 (InterScan E-Mail VirusWall NT); Mon, 21 Jan 2002 03:19:01 -0500
Received: from BLRKECIMR01.ad.infosys.com ([192.168.200.58]) by INDHUBBHS02.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 21 Jan 2002 13:48:36 +0530
Received: from kecmsg06.ad.infosys.com ([192.168.200.75]) by BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 21 Jan 2002 13:48:36 +0530
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Date: Mon, 21 Jan 2002 13:48:35 +0530
Message-ID: <56E2573C375A414191118970BDE06A1505604E16@kecmsg06.ad.infosys.com>
Thread-Topic: IPDC in VoATM Networks?
Thread-Index: AcGiVDopO83V6g4mEda8jAAA4hnv4A==
From: "Ramakrishnan" <ramki@infy.com>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 21 Jan 2002 08:18:36.0600 (UTC) FILETIME=[39566380:01C1A254]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA25299
Subject: [Megaco] IPDC in VoATM Networks?
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

Can IPDC be used as a Gateway Control Protocol in VoATM Networks?
Are there any limitations to it?

regards
Ramki
( mailto:ramki@infy.com )

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



From megaco-admin@ietf.org  Mon Jan 21 08:41:56 2002
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 IAA09471
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 08:41:56 -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 IAA06404;
	Mon, 21 Jan 2002 08:24:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06377
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 08:24:42 -0500 (EST)
Received: from sess01.rdp.asi.alcatel.es ([159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08706
	for <megaco@ietf.org>; Mon, 21 Jan 2002 08:24:37 -0500 (EST)
Received: from sers002.rpi.ses.alcatel.es (sers002 [159.23.193.30])
	by sess01.rdp.asi.alcatel.es (8.11.2/8.11.2) with ESMTP id g0LDO1722660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 14:24:01 +0100 (MET)
Received: from alcatel.es (sevsf075 [159.23.195.75])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id OAA20756
	for <megaco@ietf.org>; Mon, 21 Jan 2002 14:23:58 +0100 (MET)
Message-ID: <3C4C14AF.C1CD6A33@alcatel.es>
Date: Mon, 21 Jan 2002 14:16:31 +0100
From: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
Organization: ALCATEL
X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: [Megaco] Statistics on Move command
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
Content-Type: multipart/alternative;
 boundary="------------95FC62D484B87245C131F25F"
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


--------------95FC62D484B87245C131F25F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

When a MOVE command is received on a termination.
Do we have to accumulate the statistics or we can reset them
for the new context?

Thanks in advance
Regards
Fernando



--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------95FC62D484B87245C131F25F
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi all,
<p>When a MOVE command is received on a termination.
<br>Do we have to accumulate the statistics or we can reset them
<br>for the new context?
<p>Thanks in advance
<br>Regards
<br>Fernando
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
Fernando Vallejo Lazaro
Phone:&nbsp; +34 91 330 8279
SW&nbsp; Wireline ASD-Madrid
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALCATEL</pre>
&nbsp;</html>

--------------95FC62D484B87245C131F25F--


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


From megaco-admin@ietf.org  Mon Jan 21 08:56:12 2002
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 IAA09789
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 08:56:12 -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 IAA07346;
	Mon, 21 Jan 2002 08:39:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07315
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 08:39:22 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09387
	for <Megaco@ietf.org>; Mon, 21 Jan 2002 08:39:20 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126BQZ>; Mon, 21 Jan 2002 08:38:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A4484048C4@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        Terry L Anderson
	 <tla@lucent.com>
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Carl Rutter
	 <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: RE: [Megaco] NotifyCompletion Question
Date: Mon, 21 Jan 2002 08:38:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A280.F4016410"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A280.F4016410
Content-Type: text/plain;
	charset="iso-8859-1"

I was looking for clarification which Tom provided.
Annex E being the confusing statement which Tom rephrased.
I wasn't suggesting a change to V1 for notify Completion = "ON/OFF" 
although like yourself I see the merits of it as well.
 
Carl

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Sunday, January 20, 2002 3:11 PM
To: Terry L Anderson
Cc: Tom-PT Taylor; 'Carl Rutter'; 'Megaco@ietf.org'
Subject: Re: [Megaco] NotifyCompletion Question


  

I am not sure we have addressed Carl's concern here. 


What he is saying makes everything clear to me now and it makes better sense
than what is already 
defined in the ABNF. 
I didn't really understood how this NotifyCompletion really worked and I
think 
I had raised some questions on it before. 
  


   signalRequest        = signalName [ LBRKT sigParameter 
                          *(COMMA sigParameter) RBRKT ] 


   sigParameter    = sigStream / sigSignalType / sigDuration / sigOther 
                   / notifyCompletion / KeepActiveToken 


   notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
                   notificationReason *(COMMA notificationReason) RBRKT 


   notificationReason   = ( TimeOutToken / InterruptByEventToken 
                                / InterruptByNewSignalsDescrToken 
                                / OtherReasonToken ) 


Because of the above ABNF, my intepretation is that MGC specifies to MG that
it needs to report 
signal completion based on the reason(s) that MGC has specified. 
If the signal completion was not due to one of the reasons specified by the
MGC then 
don't report the signal completion. 
When the signal completed and the reason matches one specified by MGC, MG
reports 
the signal completion w/the reason. 


Tom, I am not sure if your change to Event sc makes any difference here to
the actual implementation. 


I think Carl is suggesting the following (correct me if I am wrong) 


   notifyCompletion    = "ON/OFF" 


This is a change in syntax which will break current implementation. 


I am using notifyCompletionRequest because we still have to keep
notifyCompletion for 
the reporting of the signal completion in the EventDescriptor. 


Since this is a BIG syntax change, it can't be done in V1 or an update to
IG. 
For V2, it will still be a big problem due to backward compatibilty
requirement. 


Chuong 
  
  


Terry L Anderson wrote: 


I agree.  I will add to IG. 

Tom-PT Taylor wrote: 


> The error is in the Annex E text.  This material was a fairly late
addition 
> (part of the enormous amount of work we did in the Feb'00 meeting in 
> Geneva), and an inconsistency crept in.  You are the first to spot it.
The 
> text should read: 
> 
> Signal Completion 
>       EventID: sc (0x0002) 
>       Indicates termination of one or more signals for which the 
>       notifyCompletion parameter was set to enable reporting of a 
>       completion event.  For further procedural description, see 
>       sections 7.1.11, 7.1.17, and 7.2.7. 
> 
> -----Original Message----- 
> From: Carl Rutter [ mailto:crutter@telica.com <mailto:crutter@telica.com>
] 
> Sent: Thursday, January 17, 2002 10:04 AM 
> To: 'Megaco@ietf.org' 
> Subject: [Megaco] NotifyCompletion Question 
> 
> For V1 the possible values of NotifyCompletion reason are: 
> 
> notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
>           notificationReason *(COMMA notificationReason) RBRKT) 
> 
>    notificationReason   = ( TimeOutToken / InterruptByEventToken 
>                / InterruptByNewSignalsDescrToken 
>                / OtherReasonToken ) 
> 
> So when an MGC wants the MG to notify a completion of a Signal 
> the MGC would specify: 
> 
> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified

> for) 
> 
> Is this correct??? 
> 
> The reason I ask is later in the RFC there is this: 
> Signal Completion 
>       EventID: sc (0x0002) 
>       Indicates termination of one or more signals for which the 
>       notifyCompletion parameter was set to "ON".  For further 
>       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 
> 
> Which seems to indicate that the NC really should be an ON or OFF value
and 
> the 4 notificationReasons are really just return values. 
> 
> Thanks, 
> Carl 
> 
> Carl Rutter 
> Telica, Inc. 
> Building G, Suite 100 
> 734 Forest Street 
> Marlboro, MA 01752 
> Email crutter@telica.com 
> Voice 508-480-0909 x8178 
> Fax 508-480-0922 
> www.telica.com 
> 
> _______________________________________________ 
> Megaco mailing list 
> Megaco@ietf.org 
> https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
> 
> _______________________________________________ 
> Megaco mailing list 
> Megaco@ietf.org 
> https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  


-- 


------------------------------------------------------------ 
Terry L Anderson             mailto:tla@lucent.com <mailto:tla@lucent.com>  
Tel:908.582.7013   Fax:908.582.6729 
Lucent Technologies/INS/Voice Over IP Access Networks 
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
http://its.lucent.com/~tla <http://its.lucent.com/~tla>  (Lucent internal)
http://www.gti.net/tla <http://www.gti.net/tla> 

-- 

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


------_=_NextPart_001_01C1A280.F4016410
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D148343013-21012002>I was looking for clarification =
which Tom=20
provided.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>Annex E being the confusing =
statement which=20
Tom rephrased.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>I wasn't suggesting a change to =
V1 for=20
notify Completion&nbsp;=3D "ON/OFF" </SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>although like yourself I see the =
merits of=20
it as well.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D148343013-21012002>Carl</SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen=20
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Sunday, January =
20, 2002=20
  3:11 PM<BR><B>To:</B> Terry L Anderson<BR><B>Cc:</B> Tom-PT Taylor; =
'Carl=20
  Rutter'; 'Megaco@ietf.org'<BR><B>Subject:</B> Re: [Megaco] =
NotifyCompletion=20
  Question<BR><BR></FONT></DIV>&nbsp;=20
  <P>I am not sure we have addressed Carl's concern here.=20
  <P>What he is saying makes everything clear to me now and it makes =
better=20
  sense than what is already <BR>defined in the ABNF. <BR>I didn't =
really=20
  understood how this NotifyCompletion really worked and I think <BR>I =
had=20
  raised some questions on it before. <BR>&nbsp;=20
  <P>&nbsp;&nbsp; =
signalRequest&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
  signalName [ LBRKT sigParameter=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
  *(COMMA sigParameter) RBRKT ]=20
  <P>&nbsp;&nbsp; sigParameter&nbsp;&nbsp;&nbsp; =3D sigStream / =
sigSignalType /=20
  sigDuration / sigOther=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / notifyCompletion / KeepActiveToken=20
  <P>&nbsp;&nbsp; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
  NotifyCompletionToken EQUAL (LBRKT=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  notificationReason *(COMMA notificationReason) RBRKT=20
  <P>&nbsp;&nbsp; notificationReason&nbsp;&nbsp; =3D ( TimeOutToken /=20
  InterruptByEventToken=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / InterruptByNewSignalsDescrToken=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / OtherReasonToken )=20
  <P>Because of the above ABNF, my intepretation is that MGC specifies =
to MG=20
  that it needs to report <BR>signal completion based on the reason(s) =
that MGC=20
  has specified. <BR>If the signal completion was not due to one of the =
reasons=20
  specified by the MGC then <BR>don't report the signal completion. =
<BR>When the=20
  signal completed and the reason matches one specified by MGC, MG =
reports=20
  <BR>the signal completion w/the reason.=20
  <P>Tom, I am not sure if your change to Event sc makes any difference =
here to=20
  the actual implementation.=20
  <P>I think Carl is suggesting the following (correct me if I am =
wrong)=20
  <P>&nbsp;&nbsp; <B>notifyCompletion&nbsp;&nbsp;&nbsp; =3D =
"ON/OFF"</B>=20
  <P>This is a change in syntax which will break current =
implementation.=20
  <P>I am using notifyCompletionRequest because we still have to keep=20
  notifyCompletion for <BR>the reporting of the signal completion in =
the=20
  EventDescriptor.=20
  <P>Since this is a BIG syntax change, it can't be done in V1 or an =
update to=20
  IG. <BR>For V2, it will still be a big problem due to backward =
compatibilty=20
  requirement.=20
  <P>Chuong <BR>&nbsp; <BR>&nbsp;=20
  <P>Terry L Anderson wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">I agree.&nbsp; I will add to IG.=20
    <P>Tom-PT Taylor wrote:=20
    <P>&gt; The error is in the Annex E text.&nbsp; This material was a =
fairly=20
    late addition <BR>&gt; (part of the enormous amount of work we did =
in the=20
    Feb'00 meeting in <BR>&gt; Geneva), and an inconsistency crept =
in.&nbsp; You=20
    are the first to spot it.&nbsp; The <BR>&gt; text should read: =
<BR>&gt;=20
    <BR>&gt; Signal Completion =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    EventID: sc (0x0002) <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Indicates=20
    termination of one or more signals for which the=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion =
parameter was=20
    set to enable reporting of a =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    completion event.&nbsp; For further procedural description, see=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sections 7.1.11, =
7.1.17, and=20
    7.2.7. <BR>&gt; <BR>&gt; -----Original Message----- <BR>&gt; From: =
Carl=20
    Rutter [<A =
href=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]=20
    <BR>&gt; Sent: Thursday, January 17, 2002 10:04 AM <BR>&gt; To:=20
    'Megaco@ietf.org' <BR>&gt; Subject: [Megaco] NotifyCompletion =
Question=20
    <BR>&gt; <BR>&gt; For V1 the possible values of NotifyCompletion =
reason are:=20
    <BR>&gt; <BR>&gt; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
    NotifyCompletionToken EQUAL (LBRKT=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    notificationReason *(COMMA notificationReason) RBRKT) <BR>&gt;=20
    <BR>&gt;&nbsp;&nbsp;&nbsp; notificationReason&nbsp;&nbsp; =3D ( =
TimeOutToken /=20
    InterruptByEventToken=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    / InterruptByNewSignalsDescrToken=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    / OtherReasonToken ) <BR>&gt; <BR>&gt; So when an MGC wants the MG =
to notify=20
    a completion of a Signal <BR>&gt; the MGC would specify: <BR>&gt; =
<BR>&gt;=20
    NC =3D TimeOut,IntByEvent etc (or whatever of the 4 they want to be =
notified=20
    <BR>&gt; for) <BR>&gt; <BR>&gt; Is this correct??? <BR>&gt; =
<BR>&gt; The=20
    reason I ask is later in the RFC there is this: <BR>&gt; Signal =
Completion=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination =
of one or=20
    more signals for which the =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    notifyCompletion parameter was set to "ON".&nbsp; For further=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; procedural =
description, see=20
    sections 7.1.11, 7.1.17, and 7.2.7. <BR>&gt; <BR>&gt; Which seems =
to=20
    indicate that the NC really should be an ON or OFF value and =
<BR>&gt; the 4=20
    notificationReasons are really just return values. <BR>&gt; =
<BR>&gt; Thanks,=20
    <BR>&gt; Carl <BR>&gt; <BR>&gt; Carl Rutter <BR>&gt; Telica, Inc. =
<BR>&gt;=20
    Building G, Suite 100 <BR>&gt; 734 Forest Street <BR>&gt; Marlboro, =
MA 01752=20
    <BR>&gt; Email crutter@telica.com <BR>&gt; Voice 508-480-0909 x8178 =
<BR>&gt;=20
    Fax 508-480-0922 <BR>&gt; www.telica.com <BR>&gt; <BR>&gt;=20
    _______________________________________________ <BR>&gt; Megaco =
mailing list=20
    <BR>&gt; Megaco@ietf.org <BR>&gt; <A=20
    =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A>=20
    <BR>&gt; <BR>&gt; _______________________________________________ =
<BR>&gt;=20
    Megaco mailing list <BR>&gt; Megaco@ietf.org <BR>&gt; <A=20
    =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A>=20

    <P>--=20
    <P>------------------------------------------------------------ =
<BR>Terry L=20
    =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
    <A href=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>=20
    <BR>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729 <BR>Lucent=20
    Technologies/INS/Voice Over IP Access Networks <BR>Rm 2B-121, 600 =
Mountain=20
    Av, Murray Hill, NJ 07974 <BR><A=20
    href=3D"http://its.lucent.com/~tla">http://its.lucent.com/~tla</A> =
(Lucent=20
    internal) <A=20
  =
href=3D"http://www.gti.net/tla">http://www.gti.net/tla</A></P></BLOCKQUO=
TE><PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc =
****</PRE>&nbsp;=20
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1A280.F4016410--

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


From daemon@optimus.ietf.org  Mon Jan 21 08:56:13 2002
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 IAA09798
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 08:56:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07845
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 08:56:14 -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 IAA07346;
	Mon, 21 Jan 2002 08:39:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07315
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 08:39:22 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09387
	for <Megaco@ietf.org>; Mon, 21 Jan 2002 08:39:20 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126BQZ>; Mon, 21 Jan 2002 08:38:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A4484048C4@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        Terry L Anderson
	 <tla@lucent.com>
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Carl Rutter
	 <crutter@telica.com>,
        "'Megaco@ietf.org'" <Megaco@ietf.org>
Subject: RE: [Megaco] NotifyCompletion Question
Date: Mon, 21 Jan 2002 08:38:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A280.F4016410"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A280.F4016410
Content-Type: text/plain;
	charset="iso-8859-1"

I was looking for clarification which Tom provided.
Annex E being the confusing statement which Tom rephrased.
I wasn't suggesting a change to V1 for notify Completion = "ON/OFF" 
although like yourself I see the merits of it as well.
 
Carl

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Sunday, January 20, 2002 3:11 PM
To: Terry L Anderson
Cc: Tom-PT Taylor; 'Carl Rutter'; 'Megaco@ietf.org'
Subject: Re: [Megaco] NotifyCompletion Question


  

I am not sure we have addressed Carl's concern here. 


What he is saying makes everything clear to me now and it makes better sense
than what is already 
defined in the ABNF. 
I didn't really understood how this NotifyCompletion really worked and I
think 
I had raised some questions on it before. 
  


   signalRequest        = signalName [ LBRKT sigParameter 
                          *(COMMA sigParameter) RBRKT ] 


   sigParameter    = sigStream / sigSignalType / sigDuration / sigOther 
                   / notifyCompletion / KeepActiveToken 


   notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
                   notificationReason *(COMMA notificationReason) RBRKT 


   notificationReason   = ( TimeOutToken / InterruptByEventToken 
                                / InterruptByNewSignalsDescrToken 
                                / OtherReasonToken ) 


Because of the above ABNF, my intepretation is that MGC specifies to MG that
it needs to report 
signal completion based on the reason(s) that MGC has specified. 
If the signal completion was not due to one of the reasons specified by the
MGC then 
don't report the signal completion. 
When the signal completed and the reason matches one specified by MGC, MG
reports 
the signal completion w/the reason. 


Tom, I am not sure if your change to Event sc makes any difference here to
the actual implementation. 


I think Carl is suggesting the following (correct me if I am wrong) 


   notifyCompletion    = "ON/OFF" 


This is a change in syntax which will break current implementation. 


I am using notifyCompletionRequest because we still have to keep
notifyCompletion for 
the reporting of the signal completion in the EventDescriptor. 


Since this is a BIG syntax change, it can't be done in V1 or an update to
IG. 
For V2, it will still be a big problem due to backward compatibilty
requirement. 


Chuong 
  
  


Terry L Anderson wrote: 


I agree.  I will add to IG. 

Tom-PT Taylor wrote: 


> The error is in the Annex E text.  This material was a fairly late
addition 
> (part of the enormous amount of work we did in the Feb'00 meeting in 
> Geneva), and an inconsistency crept in.  You are the first to spot it.
The 
> text should read: 
> 
> Signal Completion 
>       EventID: sc (0x0002) 
>       Indicates termination of one or more signals for which the 
>       notifyCompletion parameter was set to enable reporting of a 
>       completion event.  For further procedural description, see 
>       sections 7.1.11, 7.1.17, and 7.2.7. 
> 
> -----Original Message----- 
> From: Carl Rutter [ mailto:crutter@telica.com <mailto:crutter@telica.com>
] 
> Sent: Thursday, January 17, 2002 10:04 AM 
> To: 'Megaco@ietf.org' 
> Subject: [Megaco] NotifyCompletion Question 
> 
> For V1 the possible values of NotifyCompletion reason are: 
> 
> notifyCompletion     = NotifyCompletionToken EQUAL (LBRKT 
>           notificationReason *(COMMA notificationReason) RBRKT) 
> 
>    notificationReason   = ( TimeOutToken / InterruptByEventToken 
>                / InterruptByNewSignalsDescrToken 
>                / OtherReasonToken ) 
> 
> So when an MGC wants the MG to notify a completion of a Signal 
> the MGC would specify: 
> 
> NC = TimeOut,IntByEvent etc (or whatever of the 4 they want to be notified

> for) 
> 
> Is this correct??? 
> 
> The reason I ask is later in the RFC there is this: 
> Signal Completion 
>       EventID: sc (0x0002) 
>       Indicates termination of one or more signals for which the 
>       notifyCompletion parameter was set to "ON".  For further 
>       procedural description, see sections 7.1.11, 7.1.17, and 7.2.7. 
> 
> Which seems to indicate that the NC really should be an ON or OFF value
and 
> the 4 notificationReasons are really just return values. 
> 
> Thanks, 
> Carl 
> 
> Carl Rutter 
> Telica, Inc. 
> Building G, Suite 100 
> 734 Forest Street 
> Marlboro, MA 01752 
> Email crutter@telica.com 
> Voice 508-480-0909 x8178 
> Fax 508-480-0922 
> www.telica.com 
> 
> _______________________________________________ 
> Megaco mailing list 
> Megaco@ietf.org 
> https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
> 
> _______________________________________________ 
> Megaco mailing list 
> Megaco@ietf.org 
> https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  


-- 


------------------------------------------------------------ 
Terry L Anderson             mailto:tla@lucent.com <mailto:tla@lucent.com>  
Tel:908.582.7013   Fax:908.582.6729 
Lucent Technologies/INS/Voice Over IP Access Networks 
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
http://its.lucent.com/~tla <http://its.lucent.com/~tla>  (Lucent internal)
http://www.gti.net/tla <http://www.gti.net/tla> 

-- 

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


------_=_NextPart_001_01C1A280.F4016410
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D148343013-21012002>I was looking for clarification =
which Tom=20
provided.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>Annex E being the confusing =
statement which=20
Tom rephrased.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>I wasn't suggesting a change to =
V1 for=20
notify Completion&nbsp;=3D "ON/OFF" </SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002>although like yourself I see the =
merits of=20
it as well.</SPAN></DIV>
<DIV><SPAN class=3D148343013-21012002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D148343013-21012002>Carl</SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen=20
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Sunday, January =
20, 2002=20
  3:11 PM<BR><B>To:</B> Terry L Anderson<BR><B>Cc:</B> Tom-PT Taylor; =
'Carl=20
  Rutter'; 'Megaco@ietf.org'<BR><B>Subject:</B> Re: [Megaco] =
NotifyCompletion=20
  Question<BR><BR></FONT></DIV>&nbsp;=20
  <P>I am not sure we have addressed Carl's concern here.=20
  <P>What he is saying makes everything clear to me now and it makes =
better=20
  sense than what is already <BR>defined in the ABNF. <BR>I didn't =
really=20
  understood how this NotifyCompletion really worked and I think <BR>I =
had=20
  raised some questions on it before. <BR>&nbsp;=20
  <P>&nbsp;&nbsp; =
signalRequest&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
  signalName [ LBRKT sigParameter=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
  *(COMMA sigParameter) RBRKT ]=20
  <P>&nbsp;&nbsp; sigParameter&nbsp;&nbsp;&nbsp; =3D sigStream / =
sigSignalType /=20
  sigDuration / sigOther=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / notifyCompletion / KeepActiveToken=20
  <P>&nbsp;&nbsp; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
  NotifyCompletionToken EQUAL (LBRKT=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  notificationReason *(COMMA notificationReason) RBRKT=20
  <P>&nbsp;&nbsp; notificationReason&nbsp;&nbsp; =3D ( TimeOutToken /=20
  InterruptByEventToken=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / InterruptByNewSignalsDescrToken=20
  =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  / OtherReasonToken )=20
  <P>Because of the above ABNF, my intepretation is that MGC specifies =
to MG=20
  that it needs to report <BR>signal completion based on the reason(s) =
that MGC=20
  has specified. <BR>If the signal completion was not due to one of the =
reasons=20
  specified by the MGC then <BR>don't report the signal completion. =
<BR>When the=20
  signal completed and the reason matches one specified by MGC, MG =
reports=20
  <BR>the signal completion w/the reason.=20
  <P>Tom, I am not sure if your change to Event sc makes any difference =
here to=20
  the actual implementation.=20
  <P>I think Carl is suggesting the following (correct me if I am =
wrong)=20
  <P>&nbsp;&nbsp; <B>notifyCompletion&nbsp;&nbsp;&nbsp; =3D =
"ON/OFF"</B>=20
  <P>This is a change in syntax which will break current =
implementation.=20
  <P>I am using notifyCompletionRequest because we still have to keep=20
  notifyCompletion for <BR>the reporting of the signal completion in =
the=20
  EventDescriptor.=20
  <P>Since this is a BIG syntax change, it can't be done in V1 or an =
update to=20
  IG. <BR>For V2, it will still be a big problem due to backward =
compatibilty=20
  requirement.=20
  <P>Chuong <BR>&nbsp; <BR>&nbsp;=20
  <P>Terry L Anderson wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">I agree.&nbsp; I will add to IG.=20
    <P>Tom-PT Taylor wrote:=20
    <P>&gt; The error is in the Annex E text.&nbsp; This material was a =
fairly=20
    late addition <BR>&gt; (part of the enormous amount of work we did =
in the=20
    Feb'00 meeting in <BR>&gt; Geneva), and an inconsistency crept =
in.&nbsp; You=20
    are the first to spot it.&nbsp; The <BR>&gt; text should read: =
<BR>&gt;=20
    <BR>&gt; Signal Completion =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    EventID: sc (0x0002) <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Indicates=20
    termination of one or more signals for which the=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; notifyCompletion =
parameter was=20
    set to enable reporting of a =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    completion event.&nbsp; For further procedural description, see=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sections 7.1.11, =
7.1.17, and=20
    7.2.7. <BR>&gt; <BR>&gt; -----Original Message----- <BR>&gt; From: =
Carl=20
    Rutter [<A =
href=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]=20
    <BR>&gt; Sent: Thursday, January 17, 2002 10:04 AM <BR>&gt; To:=20
    'Megaco@ietf.org' <BR>&gt; Subject: [Megaco] NotifyCompletion =
Question=20
    <BR>&gt; <BR>&gt; For V1 the possible values of NotifyCompletion =
reason are:=20
    <BR>&gt; <BR>&gt; notifyCompletion&nbsp;&nbsp;&nbsp;&nbsp; =3D=20
    NotifyCompletionToken EQUAL (LBRKT=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    notificationReason *(COMMA notificationReason) RBRKT) <BR>&gt;=20
    <BR>&gt;&nbsp;&nbsp;&nbsp; notificationReason&nbsp;&nbsp; =3D ( =
TimeOutToken /=20
    InterruptByEventToken=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    / InterruptByNewSignalsDescrToken=20
    =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    / OtherReasonToken ) <BR>&gt; <BR>&gt; So when an MGC wants the MG =
to notify=20
    a completion of a Signal <BR>&gt; the MGC would specify: <BR>&gt; =
<BR>&gt;=20
    NC =3D TimeOut,IntByEvent etc (or whatever of the 4 they want to be =
notified=20
    <BR>&gt; for) <BR>&gt; <BR>&gt; Is this correct??? <BR>&gt; =
<BR>&gt; The=20
    reason I ask is later in the RFC there is this: <BR>&gt; Signal =
Completion=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EventID: sc (0x0002)=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicates termination =
of one or=20
    more signals for which the =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    notifyCompletion parameter was set to "ON".&nbsp; For further=20
    <BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; procedural =
description, see=20
    sections 7.1.11, 7.1.17, and 7.2.7. <BR>&gt; <BR>&gt; Which seems =
to=20
    indicate that the NC really should be an ON or OFF value and =
<BR>&gt; the 4=20
    notificationReasons are really just return values. <BR>&gt; =
<BR>&gt; Thanks,=20
    <BR>&gt; Carl <BR>&gt; <BR>&gt; Carl Rutter <BR>&gt; Telica, Inc. =
<BR>&gt;=20
    Building G, Suite 100 <BR>&gt; 734 Forest Street <BR>&gt; Marlboro, =
MA 01752=20
    <BR>&gt; Email crutter@telica.com <BR>&gt; Voice 508-480-0909 x8178 =
<BR>&gt;=20
    Fax 508-480-0922 <BR>&gt; www.telica.com <BR>&gt; <BR>&gt;=20
    _______________________________________________ <BR>&gt; Megaco =
mailing list=20
    <BR>&gt; Megaco@ietf.org <BR>&gt; <A=20
    =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A>=20
    <BR>&gt; <BR>&gt; _______________________________________________ =
<BR>&gt;=20
    Megaco mailing list <BR>&gt; Megaco@ietf.org <BR>&gt; <A=20
    =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf=
.org/mailman/listinfo/megaco</A>=20

    <P>--=20
    <P>------------------------------------------------------------ =
<BR>Terry L=20
    =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
    <A href=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>=20
    <BR>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729 <BR>Lucent=20
    Technologies/INS/Voice Over IP Access Networks <BR>Rm 2B-121, 600 =
Mountain=20
    Av, Murray Hill, NJ 07974 <BR><A=20
    href=3D"http://its.lucent.com/~tla">http://its.lucent.com/~tla</A> =
(Lucent=20
    internal) <A=20
  =
href=3D"http://www.gti.net/tla">http://www.gti.net/tla</A></P></BLOCKQUO=
TE><PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc =
****</PRE>&nbsp;=20
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1A280.F4016410--

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



From daemon@optimus.ietf.org  Mon Jan 21 09:30:32 2002
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 IAA09480
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 08:41:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07445
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 08:41: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 IAA06404;
	Mon, 21 Jan 2002 08:24:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06377
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 08:24:42 -0500 (EST)
Received: from sess01.rdp.asi.alcatel.es ([159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08706
	for <megaco@ietf.org>; Mon, 21 Jan 2002 08:24:37 -0500 (EST)
Received: from sers002.rpi.ses.alcatel.es (sers002 [159.23.193.30])
	by sess01.rdp.asi.alcatel.es (8.11.2/8.11.2) with ESMTP id g0LDO1722660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 14:24:01 +0100 (MET)
Received: from alcatel.es (sevsf075 [159.23.195.75])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id OAA20756
	for <megaco@ietf.org>; Mon, 21 Jan 2002 14:23:58 +0100 (MET)
Message-ID: <3C4C14AF.C1CD6A33@alcatel.es>
Date: Mon, 21 Jan 2002 14:16:31 +0100
From: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
Organization: ALCATEL
X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: [Megaco] Statistics on Move command
References: <4D79C746863DD51197690002A52CDA000102ADEE@zcard0kc.ca.nortel.com> <4.3.2.7.2.20020109100405.00b47de0@postoffice.worldnet.att.net>
Content-Type: multipart/alternative;
 boundary="------------95FC62D484B87245C131F25F"
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


--------------95FC62D484B87245C131F25F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

When a MOVE command is received on a termination.
Do we have to accumulate the statistics or we can reset them
for the new context?

Thanks in advance
Regards
Fernando



--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------95FC62D484B87245C131F25F
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi all,
<p>When a MOVE command is received on a termination.
<br>Do we have to accumulate the statistics or we can reset them
<br>for the new context?
<p>Thanks in advance
<br>Regards
<br>Fernando
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
Fernando Vallejo Lazaro
Phone:&nbsp; +34 91 330 8279
SW&nbsp; Wireline ASD-Madrid
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALCATEL</pre>
&nbsp;</html>

--------------95FC62D484B87245C131F25F--


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



From megaco-admin@ietf.org  Mon Jan 21 10:14:41 2002
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 KAA11908
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 10:14:41 -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 KAA10814;
	Mon, 21 Jan 2002 10:01:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10786
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 10:01:19 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11454
	for <megaco@ietf.org>; Mon, 21 Jan 2002 10:01:16 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LF0ld01133;
	Mon, 21 Jan 2002 10:00:48 -0500 (EST)
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 g0LF0ka13012;
	Mon, 21 Jan 2002 10:00:46 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXK93>; Mon, 21 Jan 2002 10:00:47 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Mon, 21 Jan 2002 10:00:46 -0500
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

While we're on the topic of Annex M.4, I realized while reading it that it
improperly (I think) includes some control terminations in the multiplex.
This may be water under the bridge now -- too late to do anything about it.

Anyway, Christer is asking for more than I would put into the core protocol
specification.  We should probably create an Informational RFC describing
multiplex use with examples, just as we should publish an Informational RFC
giving example call flows.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Monday, January 21, 2002 12:52 AM
To: Christian Groves
Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>I think that the H.324 package probably needs to be updated to say how
>this is done. I don't think its a core H.248 issue.

I agree. The idea was that this property would be defined in the H.324
package, and then used within each stream descriptor in the Mux
Termination.

>Perhaps an IG note could be added for the H324 package? I'd like to see a
reply from the
> H324 package authors on how they thought this was to be done.

>Are there any updates you'd like to see to proposed text on
MultiplexDescriptors that Tom posted?

First, as Tom already mentioned, it should be updated so that it also
includes emphemeral bearer terminations (RTP terminations, for example).

Second, it should in detail, on a message level, describe how the
multiplexed connection is set up. Now it only says "use a stream
descriptor" - which means everyone is going to understand it their own
way, and we are going to have lots of interop problems when people start
implementing this :)

Third, it should also describe in detail how the H.223 (or whatever
multiplex method is used) descriptor is used, ie which terminations are
included etc, depending on on which "side" of the multiplexer the
terminations are.

Fourth, I think the whole Annex M.4 misses some things, but that's
another discussion...

I understand if you want to get this document ready before february, but
please let us do this correct from the beginning :)


Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I have read the document a few times, but even by having stream
> > descriptors in the mux termination, I still don't understand how each of
> > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > supposed to be the same as the LCN number, or how is the mapping done?
> >
> > A very simple solution would be to add a "LCN property" (to the H.324
> > package, I assume) which would be used in the each stream descriptor to
> > specify to which LCN it is mapped.
> >
> > Comments?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > I mentioned that several of us have been discussing additional text
for
> > > Multiplex Descriptors.  I have placed the proposed text as marked up
changes
> > > in the Megaco FTP site.  According to your taste, you can download
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.doc
> > > or
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.pdf
> > >
> > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > proposed text needs a further update.  The supporting bearers
contained by a
> > > multiplexing termination can be ephemeral as well as physical.
However, I
> > > believe it would be essential that any ephemrals mentioned in a MUX
> > > descriptor already exist in the context, since their properties are
probably
> > > not directly inferrable from those of the multiplexing termination.
> > >
> > > Tom Taylor
> > > taylor@nortelnetworks.com
> > > Ph. +1 613 736 0961 (ESN 396 1490)
> > >
> > >
> > > _______________________________________________
> > > 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


From daemon@optimus.ietf.org  Mon Jan 21 10:14:42 2002
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 KAA11918
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 10:14:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11831
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 10:14:44 -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 KAA10814;
	Mon, 21 Jan 2002 10:01:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10786
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 10:01:19 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11454
	for <megaco@ietf.org>; Mon, 21 Jan 2002 10:01:16 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LF0ld01133;
	Mon, 21 Jan 2002 10:00:48 -0500 (EST)
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 g0LF0ka13012;
	Mon, 21 Jan 2002 10:00:46 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXK93>; Mon, 21 Jan 2002 10:00:47 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Mon, 21 Jan 2002 10:00:46 -0500
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

While we're on the topic of Annex M.4, I realized while reading it that it
improperly (I think) includes some control terminations in the multiplex.
This may be water under the bridge now -- too late to do anything about it.

Anyway, Christer is asking for more than I would put into the core protocol
specification.  We should probably create an Informational RFC describing
multiplex use with examples, just as we should publish an Informational RFC
giving example call flows.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Monday, January 21, 2002 12:52 AM
To: Christian Groves
Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>I think that the H.324 package probably needs to be updated to say how
>this is done. I don't think its a core H.248 issue.

I agree. The idea was that this property would be defined in the H.324
package, and then used within each stream descriptor in the Mux
Termination.

>Perhaps an IG note could be added for the H324 package? I'd like to see a
reply from the
> H324 package authors on how they thought this was to be done.

>Are there any updates you'd like to see to proposed text on
MultiplexDescriptors that Tom posted?

First, as Tom already mentioned, it should be updated so that it also
includes emphemeral bearer terminations (RTP terminations, for example).

Second, it should in detail, on a message level, describe how the
multiplexed connection is set up. Now it only says "use a stream
descriptor" - which means everyone is going to understand it their own
way, and we are going to have lots of interop problems when people start
implementing this :)

Third, it should also describe in detail how the H.223 (or whatever
multiplex method is used) descriptor is used, ie which terminations are
included etc, depending on on which "side" of the multiplexer the
terminations are.

Fourth, I think the whole Annex M.4 misses some things, but that's
another discussion...

I understand if you want to get this document ready before february, but
please let us do this correct from the beginning :)


Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I have read the document a few times, but even by having stream
> > descriptors in the mux termination, I still don't understand how each of
> > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > supposed to be the same as the LCN number, or how is the mapping done?
> >
> > A very simple solution would be to add a "LCN property" (to the H.324
> > package, I assume) which would be used in the each stream descriptor to
> > specify to which LCN it is mapped.
> >
> > Comments?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > I mentioned that several of us have been discussing additional text
for
> > > Multiplex Descriptors.  I have placed the proposed text as marked up
changes
> > > in the Megaco FTP site.  According to your taste, you can download
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.doc
> > > or
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > x64K.pdf
> > >
> > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > proposed text needs a further update.  The supporting bearers
contained by a
> > > multiplexing termination can be ephemeral as well as physical.
However, I
> > > believe it would be essential that any ephemrals mentioned in a MUX
> > > descriptor already exist in the context, since their properties are
probably
> > > not directly inferrable from those of the multiplexing termination.
> > >
> > > Tom Taylor
> > > taylor@nortelnetworks.com
> > > Ph. +1 613 736 0961 (ESN 396 1490)
> > >
> > >
> > > _______________________________________________
> > > 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



From megaco-admin@ietf.org  Mon Jan 21 10:49:19 2002
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 KAA13147
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 10:49:19 -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 KAA13246;
	Mon, 21 Jan 2002 10:38:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13214
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 10:38:39 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12766
	for <megaco@ietf.org>; Mon, 21 Jan 2002 10:38:22 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id JAA11183
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:46 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0LFbjm16962
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:45 -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 g0LFbDG14853
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:13 -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 g0LFbDT18514
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:13 -0600 (CST)
Message-ID: <3C4C35A8.E2F58977@alcatel.com>
Date: Mon, 21 Jan 2002 09:37:12 -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" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------F2E458D59459D9A9077B15FD"
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


--------------F2E458D59459D9A9077B15FD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


MG sends SC Graceful w/Delay and terminationID=ROOT.

If MG sends SC Restart w/Service Restorted and ROOT, does the MGC assume
that
1) SC Graceful w/Delay is being cancelled?
2) All terminations are back In Service?  Even the ones that were
originally OOS before the SC Graceful.


   1) Graceful - indicates that the specified Terminations will be taken
      out of service after the specified ServiceChangeDelay; established
      connections are not yet affected, but the Media Gateway Controller
      should refrain from establishing new connections and should
      attempt to gracefully tear down existing connections on the
      Termination(s) affected by the serviceChange command. The MG
      should set termination serviceState at the expiry of
      ServiceChangeDelay or the removal of the termination from an
      active context (whichever is first), to "out of service".


How should MGC implementation intepret the above highlighted statement?
Does this mean that MGC should not try to gracefully tear down existing
connections
before Delay timer expired?

But I think the above statement is telling MGC to try and gracefully tear
down
existing connections before Delay timer expired.

To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
until
Delay timer expired before it tries to tear down existing connections.

But after Delay timer expired, MG will put all terminations out of service.

Therefore there is no such thing as MGC gracefully tearing down existing
connections.


Christian Groves wrote:

> I don't see that we need to add anything. Why can't the MG just issue a
> SC with Restart, Service Restored? The specification already allows the
> MG to do this.
>
> Regards, Christian
>
> "Chuong N. Nguyen" wrote:
> >
> > Hi Tom
> >
> > What are the possibilites of defining a mechanism of cancelling
> > ServiceChange Graceful?
> > That is MG send SC Graceful w/Delay=time.
> > Before time expired, MG wants to cancel this ServiceChange.
> >
> > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > Graceful cancelled"?
> > 2) Done in V2 - new SC Method or Reason?
> > 3) Should be covered in draft-hss-megaco-control-association?
> >
> >
> > Thanks
> > Chuong
> >
> >
> >
> > --
> >   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 ****



--------------F2E458D59459D9A9077B15FD
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>MG sends SC Graceful w/Delay and terminationID=ROOT.
<p>If MG sends SC Restart w/Service Restorted and ROOT, does the MGC assume
that
<br>1) SC Graceful w/Delay is being cancelled?
<br>2) All terminations are back In Service?&nbsp; Even the ones that were
originally OOS before the SC Graceful.
<br>&nbsp;
<p>&nbsp;&nbsp; 1) Graceful - indicates that the specified Terminations
will be taken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out of service after the specified ServiceChangeDelay;
established
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connections are not yet affected, but
the Media Gateway Controller
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should refrain from establishing new
connections and s<b>hould</b>
<br><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attempt to gracefully tear down existing
connections on the</b>
<br><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Termination(s) affected by the serviceChange
command</b>. The MG
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should set termination serviceState
at the expiry of
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ServiceChangeDelay or the removal of
the termination from an
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; active context (whichever is first),
to "out of service".
<br>&nbsp;
<p>How should MGC implementation intepret the above highlighted statement?
<br>Does this mean that MGC should not try to gracefully tear down existing
connections
<br>before Delay timer expired?
<p>But I&nbsp;think the above statement is telling MGC&nbsp;to try and
gracefully tear down
<br>existing connections before Delay timer expired.
<p>To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
until
<br>Delay timer expired before it tries to tear down existing connections.
<p>But after Delay timer expired, MG&nbsp;will put all terminations out
of service.
<br>Therefore there is no such thing as MGC gracefully tearing down existing
connections.
<br>&nbsp;
<p>Christian Groves wrote:
<blockquote TYPE=CITE>I don't see that we need to add anything. Why can't
the MG just issue a
<br>SC with Restart, Service Restored? The specification already allows
the
<br>MG to do this.
<p>Regards, Christian
<p>"Chuong N. Nguyen" wrote:
<br>>
<br>> Hi Tom
<br>>
<br>> What are the possibilites of defining a mechanism of cancelling
<br>> ServiceChange Graceful?
<br>> That is MG send SC Graceful w/Delay=time.
<br>> Before time expired, MG wants to cancel this ServiceChange.
<br>>
<br>> 1) Can this be done in V1 by adding a new SC Reason like "916 SC
<br>> Graceful cancelled"?
<br>> 2) Done in V2 - new SC Method or Reason?
<br>> 3) Should be covered in draft-hss-megaco-control-association?
<br>>
<br>>
<br>> Thanks
<br>> Chuong
<br>>
<br>>
<br>>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------F2E458D59459D9A9077B15FD--


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


From daemon@optimus.ietf.org  Mon Jan 21 10:49:19 2002
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 KAA13157
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 10:49:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA13544
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 10:49:22 -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 KAA13246;
	Mon, 21 Jan 2002 10:38:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13214
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 10:38:39 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12766
	for <megaco@ietf.org>; Mon, 21 Jan 2002 10:38:22 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id JAA11183
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:46 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0LFbjm16962
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:45 -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 g0LFbDG14853
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:13 -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 g0LFbDT18514
	for <megaco@ietf.org>; Mon, 21 Jan 2002 09:37:13 -0600 (CST)
Message-ID: <3C4C35A8.E2F58977@alcatel.com>
Date: Mon, 21 Jan 2002 09:37:12 -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" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------F2E458D59459D9A9077B15FD"
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


--------------F2E458D59459D9A9077B15FD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


MG sends SC Graceful w/Delay and terminationID=ROOT.

If MG sends SC Restart w/Service Restorted and ROOT, does the MGC assume
that
1) SC Graceful w/Delay is being cancelled?
2) All terminations are back In Service?  Even the ones that were
originally OOS before the SC Graceful.


   1) Graceful - indicates that the specified Terminations will be taken
      out of service after the specified ServiceChangeDelay; established
      connections are not yet affected, but the Media Gateway Controller
      should refrain from establishing new connections and should
      attempt to gracefully tear down existing connections on the
      Termination(s) affected by the serviceChange command. The MG
      should set termination serviceState at the expiry of
      ServiceChangeDelay or the removal of the termination from an
      active context (whichever is first), to "out of service".


How should MGC implementation intepret the above highlighted statement?
Does this mean that MGC should not try to gracefully tear down existing
connections
before Delay timer expired?

But I think the above statement is telling MGC to try and gracefully tear
down
existing connections before Delay timer expired.

To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
until
Delay timer expired before it tries to tear down existing connections.

But after Delay timer expired, MG will put all terminations out of service.

Therefore there is no such thing as MGC gracefully tearing down existing
connections.


Christian Groves wrote:

> I don't see that we need to add anything. Why can't the MG just issue a
> SC with Restart, Service Restored? The specification already allows the
> MG to do this.
>
> Regards, Christian
>
> "Chuong N. Nguyen" wrote:
> >
> > Hi Tom
> >
> > What are the possibilites of defining a mechanism of cancelling
> > ServiceChange Graceful?
> > That is MG send SC Graceful w/Delay=time.
> > Before time expired, MG wants to cancel this ServiceChange.
> >
> > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > Graceful cancelled"?
> > 2) Done in V2 - new SC Method or Reason?
> > 3) Should be covered in draft-hss-megaco-control-association?
> >
> >
> > Thanks
> > Chuong
> >
> >
> >
> > --
> >   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 ****



--------------F2E458D59459D9A9077B15FD
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>MG sends SC Graceful w/Delay and terminationID=ROOT.
<p>If MG sends SC Restart w/Service Restorted and ROOT, does the MGC assume
that
<br>1) SC Graceful w/Delay is being cancelled?
<br>2) All terminations are back In Service?&nbsp; Even the ones that were
originally OOS before the SC Graceful.
<br>&nbsp;
<p>&nbsp;&nbsp; 1) Graceful - indicates that the specified Terminations
will be taken
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out of service after the specified ServiceChangeDelay;
established
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connections are not yet affected, but
the Media Gateway Controller
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should refrain from establishing new
connections and s<b>hould</b>
<br><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attempt to gracefully tear down existing
connections on the</b>
<br><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Termination(s) affected by the serviceChange
command</b>. The MG
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should set termination serviceState
at the expiry of
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ServiceChangeDelay or the removal of
the termination from an
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; active context (whichever is first),
to "out of service".
<br>&nbsp;
<p>How should MGC implementation intepret the above highlighted statement?
<br>Does this mean that MGC should not try to gracefully tear down existing
connections
<br>before Delay timer expired?
<p>But I&nbsp;think the above statement is telling MGC&nbsp;to try and
gracefully tear down
<br>existing connections before Delay timer expired.
<p>To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
until
<br>Delay timer expired before it tries to tear down existing connections.
<p>But after Delay timer expired, MG&nbsp;will put all terminations out
of service.
<br>Therefore there is no such thing as MGC gracefully tearing down existing
connections.
<br>&nbsp;
<p>Christian Groves wrote:
<blockquote TYPE=CITE>I don't see that we need to add anything. Why can't
the MG just issue a
<br>SC with Restart, Service Restored? The specification already allows
the
<br>MG to do this.
<p>Regards, Christian
<p>"Chuong N. Nguyen" wrote:
<br>>
<br>> Hi Tom
<br>>
<br>> What are the possibilites of defining a mechanism of cancelling
<br>> ServiceChange Graceful?
<br>> That is MG send SC Graceful w/Delay=time.
<br>> Before time expired, MG wants to cancel this ServiceChange.
<br>>
<br>> 1) Can this be done in V1 by adding a new SC Reason like "916 SC
<br>> Graceful cancelled"?
<br>> 2) Done in V2 - new SC Method or Reason?
<br>> 3) Should be covered in draft-hss-megaco-control-association?
<br>>
<br>>
<br>> Thanks
<br>> Chuong
<br>>
<br>>
<br>>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------F2E458D59459D9A9077B15FD--


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



From megaco-admin@ietf.org  Mon Jan 21 11:10:35 2002
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 LAA14277
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 11:10:30 -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 LAA14561;
	Mon, 21 Jan 2002 11:01:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14462
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 11:01:02 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LG0Vd17887
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:31 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LG0SL04637
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXNL8>; Mon, 21 Jan 2002 11:00:30 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 11:00:30 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Issues In H.248v2: Context Packages
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

I was waiting for others to raise issues for our contribution to SG 16, but
there hasn't been much addressed specifically to H.248v2.  This is the first
of a series of E-mails I am going to generate on the topic.

The sentiment at IETF 52 was that packages for context properties were the
one item that we would like to have SG 16 to defer until the full
implications are realized.  That is, it should not be included in H.248v2.
Can I confirm this view with the list?

Specific changes to current H.248v2 text (i.e. Dublin TD-47):

 - delete final bullet of section 6.1.1

 - delete final sentence of first paragraph of section 6.2.3

 - delete second sentence of second paragraph of section 6.2.3

 - delete the phrase "or Context" from the last sentence of second paragraph
of section 6.2.3

 - delete section 7.1.19 Context Attribute Descriptor and renumber the
subsequent section(s) accordingly

 - in section 7.2.9, remove references to ContextAttribute Descriptor as
follows:
   -- in the third paragraph, amend the final sentence to say "There are two
types of audit."
   -- in the paragraphs beginning "Value Audit:" and "Capabilities Audit:",
delete the phrase "the ContextAttribute Descriptor or"
   -- delete the paragraph beginning "Packages Audit"
   -- delete the Audit Packages column of the table

 - delete the phrase "and contexts" in the first paragraph of section 12

 - delete the sentence beginning "ContextAttribute is for ..." and also the
final sentence of the paragraph explaining "Defined in:" in section 12.1.2

 - delete the final sentence of the paragraph explaining "Characteristics:"
in section 12.1.2

 - in Annex A:
   -- delete the contextProp and contextPackages components added after the
extension marker in the ContextRequest production
   -- delete the contextPropAud, contextAttrDescriptorCapAud,
contextPropCapAud, and contextPackagesAud components added after the
extension marker in the ContextAttrAuditRequest production

 - in Annex B:
   -- delete the contextAttrDescriptor and packagesDescriptor terms from the
contextProperty production
   -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
IndAudContextAttrCap, and ContextAttrPackages terms from the
contextAuditProperties production
   -- delete the IndAudContextAttrCap, ContextAttrPackages, and
ContextAttrDescriptorCapAud productions
   -- delete the contextAttrDescriptor production
   -- delete the ContextAttrToken, ContextAudCapToken,
ContextAudDescriptorToken, and ContextAudValToken productions

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@optimus.ietf.org  Mon Jan 21 11:10:35 2002
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 LAA14290
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 11:10:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15233
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 11:10:38 -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 LAA14561;
	Mon, 21 Jan 2002 11:01:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14462
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 11:01:02 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LG0Vd17887
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:31 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LG0SL04637
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:00:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXNL8>; Mon, 21 Jan 2002 11:00:30 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAB@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 11:00:30 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Issues In H.248v2: Context Packages
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

I was waiting for others to raise issues for our contribution to SG 16, but
there hasn't been much addressed specifically to H.248v2.  This is the first
of a series of E-mails I am going to generate on the topic.

The sentiment at IETF 52 was that packages for context properties were the
one item that we would like to have SG 16 to defer until the full
implications are realized.  That is, it should not be included in H.248v2.
Can I confirm this view with the list?

Specific changes to current H.248v2 text (i.e. Dublin TD-47):

 - delete final bullet of section 6.1.1

 - delete final sentence of first paragraph of section 6.2.3

 - delete second sentence of second paragraph of section 6.2.3

 - delete the phrase "or Context" from the last sentence of second paragraph
of section 6.2.3

 - delete section 7.1.19 Context Attribute Descriptor and renumber the
subsequent section(s) accordingly

 - in section 7.2.9, remove references to ContextAttribute Descriptor as
follows:
   -- in the third paragraph, amend the final sentence to say "There are two
types of audit."
   -- in the paragraphs beginning "Value Audit:" and "Capabilities Audit:",
delete the phrase "the ContextAttribute Descriptor or"
   -- delete the paragraph beginning "Packages Audit"
   -- delete the Audit Packages column of the table

 - delete the phrase "and contexts" in the first paragraph of section 12

 - delete the sentence beginning "ContextAttribute is for ..." and also the
final sentence of the paragraph explaining "Defined in:" in section 12.1.2

 - delete the final sentence of the paragraph explaining "Characteristics:"
in section 12.1.2

 - in Annex A:
   -- delete the contextProp and contextPackages components added after the
extension marker in the ContextRequest production
   -- delete the contextPropAud, contextAttrDescriptorCapAud,
contextPropCapAud, and contextPackagesAud components added after the
extension marker in the ContextAttrAuditRequest production

 - in Annex B:
   -- delete the contextAttrDescriptor and packagesDescriptor terms from the
contextProperty production
   -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
IndAudContextAttrCap, and ContextAttrPackages terms from the
contextAuditProperties production
   -- delete the IndAudContextAttrCap, ContextAttrPackages, and
ContextAttrDescriptorCapAud productions
   -- delete the contextAttrDescriptor production
   -- delete the ContextAttrToken, ContextAudCapToken,
ContextAudDescriptorToken, and ContextAudValToken productions

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Mon Jan 21 11:58:09 2002
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 LAA16792
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 11:58:05 -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 LAA17232;
	Mon, 21 Jan 2002 11:49:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17206
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 11:49:11 -0500 (EST)
Received: from localhost ([218.55.130.23])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16365
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:49:06 -0500 (EST)
Message-Id: <200201211649.LAA16365@ietf.org>
Reply-To: naracom2002@naver.com
From: (ÁÖ)³ª¶óÄÞ<naracom2002@naver.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 22 Jan 2002 02:04:04 +0900
Subject: [Megaco] ¾È³çÇÏ¼¼¿©[È«º¸]
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

<html>
<head>
<title>¼±ºÒ¿ä±ÝÁ¦ ÂüÁ¶ÀÚ·áÁý</title>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
<meta name="generator" content="Namo WebEditor v4.0">
<style type="text/css">
<!--
td { font-family: "µ¸¿ò", "µ¸¿òÃ¼"; font-size: 12px; color: #000000; line-height: 120%}
-->
</style>
</head>
<body text="black" link="blue" vlink="purple" alink="red">
<div>
<table width="620" border="0" cellspacing="2" cellpadding="2" align="center">
<tr bgcolor="#FFFFFF">
<td>
<p>¾È³çÇÏ¼¼¿ä ÀúÈ£ÁØÀÌ¿¡¿ä<br>
ÀßÁö³»°í °è½ÃÁ®?<br>
ÁÁÀºÁ¤º¸°¡ ÀÌ·¸°Ô ¸áº¸³» µå·Á¿ä<br>
ÇÑ¹ø ²Ä²ÄÈ÷ µûÁ®º¸¼¼¿ä ¾Æ¸¶ ¸¹Àºµµ¿òµÉ°Å¿¡¿ä<br>
¾Æ·¡¿¡ ÆÄÀÏÃ·ºÎÇßÀ¸´Ï ÀÐ¾îº¸½Ã°í¿ä<br>
±×·³ ¶Ç ¸áµå¸±²²¿ä<br>
</td>
</tr>
</table>
<table width="623" border="0" cellspacing="0" cellpadding="0" align="center">
<tr valign="top">
<td height="218" background="http://www.copyi114.co.kr/nara/img01.gif"> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width="575" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="396" height="68"> ¼±ºÒ¿ä±ÝÁ¦¼­ºñ½º´Â ¾î´À³¯ °©ÀÚ±â ³ª¿Â ¼­ºñ½º°¡ ¾Æ´Ñ, ¼±Áø ¿©·¯³ª¶ó¿¡¼­´Â
ÀÌ¹Ì ±âÁ¸¿¡ ½Ç½ÃÇÏ°í´Â ¼­ºñ½º·Î È¸»çÀÇ ÀÔÀå¿¡¼­´Â ¾ÈÁ¤ÀûÀÌ¸ç ¹Ì³³ °ÆÁ¤ÀÌ ¾ø´Â È¸¿øÀ¯Ä¡¸¦ ÇÏ¿© È¸»çÀÇ ¾ÈÁ¤¼ºÀ» ²ÒÇÒ
¼ö ÀÖÀ¸¸ç, ÀÌ¿¡µû¸¥ °í°´Àº °¢Á¾ ÇýÅÃ ¹× ¼ö´çÀ» ¹Þ´Â °ÍÀÔ´Ï´Ù.<br>
Áï ¼±ºÒÁ¦¿ä±ÝÁ¦¶õ ¸ÕÀú ÀÏÁ¤ºÎºÐÀÇ Åë½Å·á¸¦ ³»°í Ä³½¬¹é(Çö±Ý)°ú ±âÅ¸ ¼ö´çÀ» ¹Þ´Â ¿ä±ÝÃ¼°èÀÌ¸ç, ÀÌ·ÎÀÎÇÑ ÇýÅÃÀ» °í°´¿¡°Ô
Å©°Ô´Â 35%¿¡ ÇØ´çµÇ´Â ºÎºÐÀ» ´Ù½Ã Çö±ÝÀ¸·Î µ¹·Áµå¸®°í ÀÖ½À´Ï´Ù. </td>
<td width="179" height="68" valign="bottom">
<div align="center"><a href="http://www.copyi114.co.kr/nara/news.htm" target="_blank"><img src="http://www.copyi114.co.kr/nara/img16.gif" width="145" height="67" border="0"></a></div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td background="http://www.copyi114.co.kr/nara/img02.gif">
<table width="620" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="17">&nbsp;</td>
<td width="561"> <img src="http://www.copyi114.co.kr/nara/img14.gif" width="175" height="22"><br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img15.gif" width="461" height="91"><br>
1. ¾Ç¼º¿¬Ã¼ ¿ä±ÝÀ¸·Î ÀÎÇÑ ±ÝÀ¶ <b><font color="#CC0000">½Å¿ëºÒ·®ÀÚÀÇ Áõ°¡.</font></b>
<br>
2. ÀÎÀû, ¹°ÀûÀ¸·Î<b><font color="#CC0000"> ¸¹Àº °ü¸®ºñ¿ë ÇÊ¿ä </font></b>(¿ä±Ý°íÁö,
Ã¤±Ç°ü¸® µî). <br>
3. ÀÌµ¿Åë½Å »ç¿ëÀÚ°¡ »ç¿ë¿ä±ÝÀÇ ÀÎÁö¾øÀÌ ¹«ºÐº°ÇÑ »ç¿ëÀ¸·Î ÀÎÇÑ <b><font color="#CC0000">°ú¼Òºñ
ÃÊ·¡</font></b>. <br>
<font color="#0066CC"><br>
<b>ÀÌ·¯ÇÑ, ¹®Á¦·Î ÀÎÇØ ¼¼°èÀûÀ¸·Î ÀÌµ¿Åë½ÅÀº ¼±ºÒ¿ä±ÝÁ¦·Î ÀüÈ¯µÇ°í ÀÖ½À´Ï´Ù.</b></font> <br>
<font color="#990000">¡Ø 2002³â¿¡´Â IMT2000 ¼­ºñ½º°¡ ½ÃÀÛµÇ¸ç, ±×¶§´Â Áö±Ý
»ç¿ë¿ä±ÝÀÇ 3~4¹è¿¡ ÀÌ¸£´Â ¼­ºñ½º ¿ä±ÝÀÌ »ç¿ëµÉ °ÍÀÌ¶ó°í ¿¹ÃøÇÏ°í ÀÖ½À´Ï´Ù. Åë½Å½ÃÀåÀÌ °³¹æµÇ¾úÀ½¿¡µµ
ºÒ±¸ÇÏ°í, ¿Ü±¹ÀÇ °Å´ëÅë½Å±â¾÷µéÀÌ Áö±Ý ÀáÀáÇÑ°ÍÀº ¹Ù·Î ÀÌ IMT2000 ½Ã´ëÀ» ±â´Ù¸®¸ç, ¿ì¸®³ª¶ó Åë½Å½ÃÀåÀ»
³Ñº¸°í ÀÖ´Â °ÍÀÔ´Ï´Ù. </font></td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img09.gif" width="161" height="23"> <br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img10.gif" width="399" height="271"></td>
</tr>
</table>
<b><img src="http://www.copyi114.co.kr/nara/img04.gif" width="231" height="21"></b>
<table border="0" width="496" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="100%" height="20">: °³ÀÎ´ë¸®Á¡À¸·Î ±¸¼º<br>
°íÁ¤µÈ Áö¿ª ´ë¸®Á¡À» Å»ÇÇÇÏ¿© Áö¿ª¿¡ »ó°ü¾øÀÌ ¿òÁ÷ÀÌ´Â ´ë¸®Á¡À¸·Î ±¸¼º </td>
</tr>
<tr>
<td width="100%" height="20">
<table border="0" width="500" bordercolor="#FFFFFF" bordercolorlight="#FFFFFF" bordercolordark="#FFFFFF" bgcolor="#666666" cellspacing="1" cellpadding="6" align="center">
<tr>
<td width="20%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#A6A6A6">
¡¡</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">ÀÏ¹Ý´ë¸®Á¡ </font></b>
</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">KTF ¼±ºÒ´ë¸®Á¡
</font></b>
</td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center">
<p align="center"><font color="#000000"><b>¹ü&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
À§</b></font>
</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">Áö¿ªº°
ÇÑ°è</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">Áö¿ª
Á¦ÇÑ¾øÀÌ Àü±¹</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
¼³</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">¸ÅÀå
ÀÓ´ë (º¸Áõ±Ý + ½Ã¼³ºñ µî)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¸ÅÀå
ºÒÇÊ¿ä</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>´ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
º¸</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">´Ü¸»±â
±¸¸Å¸¦ À§ÇØ ´ãº¸¹° Á¦°ø</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">´ãº¸
¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>°ü
¸® À¯ Áö</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®
ÀÎ¿ø ¹× °ü¸®ºñ °ú´Ù ÁöÃâ</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>¼ö&nbsp;&nbsp;
¼ö&nbsp;&nbsp; ·á</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®¼ö¼ö·á</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">È¸¿øÀå·Á±Ý</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;
Àå&nbsp;&nbsp; ¼º</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">½ÃÀå¼ºÀÌ
¾ø´Ù. (Æ÷È­»óÅÂ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¹«ÇÑÇÑ
½ÃÀå¼º (ÃÊ±â½ÃÀå ¼±Á¡)</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>ÇØ&nbsp;&nbsp;
Áö&nbsp;&nbsp; À²</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°í°´
ÀÌµ¿ÀÌ ¸¹´Ù.<br>
<br>
(´ë¸®Á¡°£ °ø¿ë½Ã½ºÅÛ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">°í°´ÀÌµ¿
¾øÀ½.<br>
<br>
(Àü¿ë½Ã½ºÅÛ)</font></td>
</tr>
</table>
<table border="0" width="501" align="center">
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img05.gif" width="147" height="38">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img06.gif" width="95" height="18"></td>
</tr>
<tr>
<td width="100%" height="48">
<p> &nbsp;<font color="#008000">¢º </font><b>»ç¿ëÀÌ ºÒÆíÇÏ´Ù</b>
: Á¢¼Ó¹øÈ£¿Í&nbsp; Ä«µå¹øÈ£¸¦ ÀÔ·ÂÇÑ ÈÄ »ç¿ëÇÏ¿©¾ß ÅëÈ­°¡ ¿¬°áµË´Ï´Ù. <br>
&nbsp;<font color="#008000">¢º </font><b>½Ã¿ÜÀüÈ­</b> :
±â¾÷, È¸»ç¿¡¼­ ¸¹ÀÌ »ç¿ë (¾à 2Á¶¿ø)&nbsp; <font color="#0000FF">°³ÀÎÀº
1°¡±¸´ç ¾à 4,600¿ø »ç¿ë</font> <br>
&nbsp;<font color="#008000">¢º </font><b>±¹Á¦ÀüÈ­</b> :
±â¾÷, ¹«¿ªÈ¸»ç, ¿ÀÆÄ»óµîÀÌ ¸¹ÀÌ »ç¿ë (¾à1Á¶¿ø) <font color="#0000FF">°³ÀÎ
»ç¿ëÀº ¹ÌºñÇÏ´Ù.</font>
</td>
</tr>
<tr>
<td width="100%"></td>
</tr>
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img07.gif" width="180" height="37">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img08.gif" width="125" height="18">
</td>
</tr>
<tr valign="top">
<td width="100%" height="67">&nbsp; &nbsp;<font color="#008000">¢º
</font><b><font color="#FF0000">»ç¿ëÀÌ Æí¸®ÇÏ´Ù.</font></b><font color="#0000FF">
: </font><font color="#000000">ÈÄºÒ ÀüÈ­ »ç¿ë°ú µ¿ÀÏ</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º </font><b><font color="#FF0000">2,750¸¸¸íÀÌ
³Ñ´Â ´ëºÎºÐÀÇ °í°´ÀÌ °³ÀÎÀ¸·Î ±¸¼ºµÇ¾î ÀÖ½À´Ï´Ù.</font></b><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><font color="#FF0000"><b> ¼±ºÒ½ÃÀåÀº ¹«ÇÑÇÕ´Ï´Ù.</b></font><font color="#0000FF">
: </font><font color="#000000">2750¸¸ ÈÄºÒ¿ä±Ý »ç¿ë°í°´</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><b><font color="#FF0000"> 1°¡±¸´ç 11¸¸¿ø ÀÌ»ó »ç¿ëÇÕ´Ï´Ù.
</font><font color="#000000">(1999³â Åë°è)</font></b></td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img18.gif" width="86" height="18">
<table width="480" border="0" cellspacing="2" cellpadding="2" align="center">
<tr>
<td height="305">
<table border="0" width="480" bgcolor="#000000" cellspacing="1" cellpadding="3">
<tr>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ä±Ý»óÇ°</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ÀÏ
±âº»·á</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ù
±âº»·á</font></b></td>
<td width="20%" bgcolor="#CCCCCC" align="center" height="15" colspan="3"><b><font color="#666666">±¹³»ÅëÈ­·á&nbsp;<br>
(¿ø/10ÃÊ)</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ºñ
°í</font></b></td>
</tr>
<tr>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">Æò»ó</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">ÇÒÀÎ</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">½É¾ß</font></b></td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
Ç¥ÁØ</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>533
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>16,000
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>18
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
¿¡ÀÌ½º</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>616
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>18,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>13
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒÇÁ¸®
200</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>1,183
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>35,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>17
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><font color="#FF0000"><b>200ºÐ
¹«·á</b></font></td>
</tr>
</table>
<center>
</center>
<p align="left">&nbsp; ¢º ¿ä±Ý»óÇ° º¯°æ½Ã Àû¿ë½ÃÁ¡ : º¯°æ°ú µ¿½Ã¿¡ º¯°æ¿ä±ÝÀ¸·Î Á¤»êµÇ³ª,
¿ù 1È¸¿¡ ÇÑÇÔ. <br>
&nbsp; ¢º <font color="#008000"><b>ÇÒ ÀÎ ½Ã °£ <br>
&nbsp;&nbsp;&nbsp; </b></font><font color="#800000">1) ¼±ºÒÇ¥ÁØ,
¼±ºÒ¿¡ÀÌ½º ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"> <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~
6 ½Ã (½É¾ß) / 6 ~ 12 (ÇÒÀÎ) / 12 ~ 24 (Æò»ó) &nbsp;&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0
~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ) <br>
&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#800000">2)
¼±ºÒÇÁ¸® 200 ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"><br>
</font><font color="#008000"><b> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</b></font><font color="#000000">- ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~ 6 ½Ã
(½É¾ß) / 6 ~ 8, 21 ~ 24 (ÇÒÀÎ) / 8 ~ 21 (Æò»ó)<br>
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;
- °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0 ~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ)</font>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img12.gif" width="144" height="20"><br>
<table width="480" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img13.gif" width="499" height="359">
<table border="0" width="496" bgcolor="#990000" cellspacing="1" cellpadding="3" align="center">
<tr>
<td width="487" bgcolor="#FFFFFF"> &nbsp;<font color="#008080"><b>KTF</b></font><font color="#000000">(ÇÑ±¹Åë½ÅÇÁ¸®ÅÚ)ÀÇ
Åº»ý ´ç½ÃºÎÅÍ ¸ðµç ½Ã½ºÅÛÀ» ´ã´çÇØ ¿Â &nbsp;<b>´ë¿ìÁ¤º¸½Ã½ºÅÛ</b>Àº&nbsp; <br>
&nbsp;±âÁ¸ ÀüÀÚ»ó°Å·¡ÀÇ ±â¹ÝºÎÀç·Î ¿À´Â ÀûÀÚ¿äÀÎÀ»&nbsp;<b>ÁÖ½ÄÈ¸»ç ³ª¶óÄÞ</b>ÀÇ
³×Æ®¿öÅ© ¸¶ÄÉÆÃÀ» &nbsp;<br>
&nbsp;ÅëÇÏ¿© </font><font color="#FF0000"><b>ÃÖ´Ü±â°£ ÃÖ´ëÈ¸¿ø</b></font><font color="#000000">ÀÇ</font><font color="#FF0000"><b>&nbsp;±â¹ÝÈ®º¸</b></font><font color="#000000">¸¦</font><font color="#FF0000"><b>
¸ñÇ¥</b></font><font color="#000000">·Î&nbsp; <b>KTF, ´ë¿ìÁ¤º¸½Ã½ºÅÛ,&nbsp;ÁÖ½ÄÈ¸»ç
<br>
&nbsp;³ª¶óÄÞÀÇ</b> </font><b><font color="#FF0000">Àü·«Àû Á¦ÈÞ</font></b><font color="#000000">¸¦
ÅëÇÏ¿©&nbsp;<br>
</font> ¼±Áø±¹Çü ¼±ºÒ¿ä±ÝÁ¦µµ
<div align="center">- <b><font color="#008080">KTF</font><font color="#000000">
016</font></b> ¼±ºÒ¿ä±ÝÁ¦µµ -</div>
<div align="right"><font color="#000000">¸¦&nbsp; Åº»ý½ÃÄ×½À´Ï´Ù.</font><font color="#000080">
</font> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img17.gif" width="262" height="21"> <br>
<table width="499" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
E-mail : corud2@dreamwiz.com</td>
</tr>
</table>
</td>
<td width="42">&nbsp;</td>
</tr>
</table>
</td>
</tr>
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img03.gif" width="619" height="31"></td>
</tr>
<tr>
<td>
<div align="center"><img height=10 src="http://www.enativespeaker.com/image/139-1.gif"
width=10> <font size=2>±ÍÇÏÀÇ E-MAILÀº °ü·Ã °Ô½ÃÆÇÀ» ÅëÇØ ¾Ë°Ô µÇ¾ú½À´Ï´Ù. <br>
¿øÄ¡ ¾Ê¾Ò´ø ¸ÞÀÏÀÌ¶ó¸é </font><a
href="mailto:naracom2002@hitel.net?subject=¼ö½Å°ÅºÎ"><font size=2><b><font
color=#0000ff>¿©±â</font></b></font></a><font size=2>¸¦ ´­·¯ ¾Ë·Á ÁÖ½Ã¸é ¾ÕÀ¸·Î´Â ¹ß¼ÛµÇÁö ¾Êµµ·Ï ÇÏ°Ú½À´Ï´Ù.</font>
<font
size=2></font></div>
</td>
</tr>
</table>
<br>
</div>
</body>
</html>

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


From daemon@optimus.ietf.org  Mon Jan 21 11:58:14 2002
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 LAA16801
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 11:58:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17545
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 11:58:13 -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 LAA17232;
	Mon, 21 Jan 2002 11:49:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17206
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 11:49:11 -0500 (EST)
Received: from localhost ([218.55.130.23])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16365
	for <megaco@ietf.org>; Mon, 21 Jan 2002 11:49:06 -0500 (EST)
Message-Id: <200201211649.LAA16365@ietf.org>
Reply-To: naracom2002@naver.com
From: (ÁÖ)³ª¶óÄÞ<naracom2002@naver.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 22 Jan 2002 02:04:04 +0900
Subject: [Megaco] ¾È³çÇÏ¼¼¿©[È«º¸]
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

<html>
<head>
<title>¼±ºÒ¿ä±ÝÁ¦ ÂüÁ¶ÀÚ·áÁý</title>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
<meta name="generator" content="Namo WebEditor v4.0">
<style type="text/css">
<!--
td { font-family: "µ¸¿ò", "µ¸¿òÃ¼"; font-size: 12px; color: #000000; line-height: 120%}
-->
</style>
</head>
<body text="black" link="blue" vlink="purple" alink="red">
<div>
<table width="620" border="0" cellspacing="2" cellpadding="2" align="center">
<tr bgcolor="#FFFFFF">
<td>
<p>¾È³çÇÏ¼¼¿ä ÀúÈ£ÁØÀÌ¿¡¿ä<br>
ÀßÁö³»°í °è½ÃÁ®?<br>
ÁÁÀºÁ¤º¸°¡ ÀÌ·¸°Ô ¸áº¸³» µå·Á¿ä<br>
ÇÑ¹ø ²Ä²ÄÈ÷ µûÁ®º¸¼¼¿ä ¾Æ¸¶ ¸¹Àºµµ¿òµÉ°Å¿¡¿ä<br>
¾Æ·¡¿¡ ÆÄÀÏÃ·ºÎÇßÀ¸´Ï ÀÐ¾îº¸½Ã°í¿ä<br>
±×·³ ¶Ç ¸áµå¸±²²¿ä<br>
</td>
</tr>
</table>
<table width="623" border="0" cellspacing="0" cellpadding="0" align="center">
<tr valign="top">
<td height="218" background="http://www.copyi114.co.kr/nara/img01.gif"> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width="575" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="396" height="68"> ¼±ºÒ¿ä±ÝÁ¦¼­ºñ½º´Â ¾î´À³¯ °©ÀÚ±â ³ª¿Â ¼­ºñ½º°¡ ¾Æ´Ñ, ¼±Áø ¿©·¯³ª¶ó¿¡¼­´Â
ÀÌ¹Ì ±âÁ¸¿¡ ½Ç½ÃÇÏ°í´Â ¼­ºñ½º·Î È¸»çÀÇ ÀÔÀå¿¡¼­´Â ¾ÈÁ¤ÀûÀÌ¸ç ¹Ì³³ °ÆÁ¤ÀÌ ¾ø´Â È¸¿øÀ¯Ä¡¸¦ ÇÏ¿© È¸»çÀÇ ¾ÈÁ¤¼ºÀ» ²ÒÇÒ
¼ö ÀÖÀ¸¸ç, ÀÌ¿¡µû¸¥ °í°´Àº °¢Á¾ ÇýÅÃ ¹× ¼ö´çÀ» ¹Þ´Â °ÍÀÔ´Ï´Ù.<br>
Áï ¼±ºÒÁ¦¿ä±ÝÁ¦¶õ ¸ÕÀú ÀÏÁ¤ºÎºÐÀÇ Åë½Å·á¸¦ ³»°í Ä³½¬¹é(Çö±Ý)°ú ±âÅ¸ ¼ö´çÀ» ¹Þ´Â ¿ä±ÝÃ¼°èÀÌ¸ç, ÀÌ·ÎÀÎÇÑ ÇýÅÃÀ» °í°´¿¡°Ô
Å©°Ô´Â 35%¿¡ ÇØ´çµÇ´Â ºÎºÐÀ» ´Ù½Ã Çö±ÝÀ¸·Î µ¹·Áµå¸®°í ÀÖ½À´Ï´Ù. </td>
<td width="179" height="68" valign="bottom">
<div align="center"><a href="http://www.copyi114.co.kr/nara/news.htm" target="_blank"><img src="http://www.copyi114.co.kr/nara/img16.gif" width="145" height="67" border="0"></a></div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td background="http://www.copyi114.co.kr/nara/img02.gif">
<table width="620" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="17">&nbsp;</td>
<td width="561"> <img src="http://www.copyi114.co.kr/nara/img14.gif" width="175" height="22"><br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img15.gif" width="461" height="91"><br>
1. ¾Ç¼º¿¬Ã¼ ¿ä±ÝÀ¸·Î ÀÎÇÑ ±ÝÀ¶ <b><font color="#CC0000">½Å¿ëºÒ·®ÀÚÀÇ Áõ°¡.</font></b>
<br>
2. ÀÎÀû, ¹°ÀûÀ¸·Î<b><font color="#CC0000"> ¸¹Àº °ü¸®ºñ¿ë ÇÊ¿ä </font></b>(¿ä±Ý°íÁö,
Ã¤±Ç°ü¸® µî). <br>
3. ÀÌµ¿Åë½Å »ç¿ëÀÚ°¡ »ç¿ë¿ä±ÝÀÇ ÀÎÁö¾øÀÌ ¹«ºÐº°ÇÑ »ç¿ëÀ¸·Î ÀÎÇÑ <b><font color="#CC0000">°ú¼Òºñ
ÃÊ·¡</font></b>. <br>
<font color="#0066CC"><br>
<b>ÀÌ·¯ÇÑ, ¹®Á¦·Î ÀÎÇØ ¼¼°èÀûÀ¸·Î ÀÌµ¿Åë½ÅÀº ¼±ºÒ¿ä±ÝÁ¦·Î ÀüÈ¯µÇ°í ÀÖ½À´Ï´Ù.</b></font> <br>
<font color="#990000">¡Ø 2002³â¿¡´Â IMT2000 ¼­ºñ½º°¡ ½ÃÀÛµÇ¸ç, ±×¶§´Â Áö±Ý
»ç¿ë¿ä±ÝÀÇ 3~4¹è¿¡ ÀÌ¸£´Â ¼­ºñ½º ¿ä±ÝÀÌ »ç¿ëµÉ °ÍÀÌ¶ó°í ¿¹ÃøÇÏ°í ÀÖ½À´Ï´Ù. Åë½Å½ÃÀåÀÌ °³¹æµÇ¾úÀ½¿¡µµ
ºÒ±¸ÇÏ°í, ¿Ü±¹ÀÇ °Å´ëÅë½Å±â¾÷µéÀÌ Áö±Ý ÀáÀáÇÑ°ÍÀº ¹Ù·Î ÀÌ IMT2000 ½Ã´ëÀ» ±â´Ù¸®¸ç, ¿ì¸®³ª¶ó Åë½Å½ÃÀåÀ»
³Ñº¸°í ÀÖ´Â °ÍÀÔ´Ï´Ù. </font></td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img09.gif" width="161" height="23"> <br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img10.gif" width="399" height="271"></td>
</tr>
</table>
<b><img src="http://www.copyi114.co.kr/nara/img04.gif" width="231" height="21"></b>
<table border="0" width="496" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="100%" height="20">: °³ÀÎ´ë¸®Á¡À¸·Î ±¸¼º<br>
°íÁ¤µÈ Áö¿ª ´ë¸®Á¡À» Å»ÇÇÇÏ¿© Áö¿ª¿¡ »ó°ü¾øÀÌ ¿òÁ÷ÀÌ´Â ´ë¸®Á¡À¸·Î ±¸¼º </td>
</tr>
<tr>
<td width="100%" height="20">
<table border="0" width="500" bordercolor="#FFFFFF" bordercolorlight="#FFFFFF" bordercolordark="#FFFFFF" bgcolor="#666666" cellspacing="1" cellpadding="6" align="center">
<tr>
<td width="20%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#A6A6A6">
¡¡</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">ÀÏ¹Ý´ë¸®Á¡ </font></b>
</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">KTF ¼±ºÒ´ë¸®Á¡
</font></b>
</td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center">
<p align="center"><font color="#000000"><b>¹ü&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
À§</b></font>
</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">Áö¿ªº°
ÇÑ°è</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">Áö¿ª
Á¦ÇÑ¾øÀÌ Àü±¹</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
¼³</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">¸ÅÀå
ÀÓ´ë (º¸Áõ±Ý + ½Ã¼³ºñ µî)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¸ÅÀå
ºÒÇÊ¿ä</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>´ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
º¸</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">´Ü¸»±â
±¸¸Å¸¦ À§ÇØ ´ãº¸¹° Á¦°ø</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">´ãº¸
¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>°ü
¸® À¯ Áö</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®
ÀÎ¿ø ¹× °ü¸®ºñ °ú´Ù ÁöÃâ</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>¼ö&nbsp;&nbsp;
¼ö&nbsp;&nbsp; ·á</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®¼ö¼ö·á</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">È¸¿øÀå·Á±Ý</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;
Àå&nbsp;&nbsp; ¼º</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">½ÃÀå¼ºÀÌ
¾ø´Ù. (Æ÷È­»óÅÂ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¹«ÇÑÇÑ
½ÃÀå¼º (ÃÊ±â½ÃÀå ¼±Á¡)</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>ÇØ&nbsp;&nbsp;
Áö&nbsp;&nbsp; À²</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°í°´
ÀÌµ¿ÀÌ ¸¹´Ù.<br>
<br>
(´ë¸®Á¡°£ °ø¿ë½Ã½ºÅÛ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">°í°´ÀÌµ¿
¾øÀ½.<br>
<br>
(Àü¿ë½Ã½ºÅÛ)</font></td>
</tr>
</table>
<table border="0" width="501" align="center">
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img05.gif" width="147" height="38">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img06.gif" width="95" height="18"></td>
</tr>
<tr>
<td width="100%" height="48">
<p> &nbsp;<font color="#008000">¢º </font><b>»ç¿ëÀÌ ºÒÆíÇÏ´Ù</b>
: Á¢¼Ó¹øÈ£¿Í&nbsp; Ä«µå¹øÈ£¸¦ ÀÔ·ÂÇÑ ÈÄ »ç¿ëÇÏ¿©¾ß ÅëÈ­°¡ ¿¬°áµË´Ï´Ù. <br>
&nbsp;<font color="#008000">¢º </font><b>½Ã¿ÜÀüÈ­</b> :
±â¾÷, È¸»ç¿¡¼­ ¸¹ÀÌ »ç¿ë (¾à 2Á¶¿ø)&nbsp; <font color="#0000FF">°³ÀÎÀº
1°¡±¸´ç ¾à 4,600¿ø »ç¿ë</font> <br>
&nbsp;<font color="#008000">¢º </font><b>±¹Á¦ÀüÈ­</b> :
±â¾÷, ¹«¿ªÈ¸»ç, ¿ÀÆÄ»óµîÀÌ ¸¹ÀÌ »ç¿ë (¾à1Á¶¿ø) <font color="#0000FF">°³ÀÎ
»ç¿ëÀº ¹ÌºñÇÏ´Ù.</font>
</td>
</tr>
<tr>
<td width="100%"></td>
</tr>
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img07.gif" width="180" height="37">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img08.gif" width="125" height="18">
</td>
</tr>
<tr valign="top">
<td width="100%" height="67">&nbsp; &nbsp;<font color="#008000">¢º
</font><b><font color="#FF0000">»ç¿ëÀÌ Æí¸®ÇÏ´Ù.</font></b><font color="#0000FF">
: </font><font color="#000000">ÈÄºÒ ÀüÈ­ »ç¿ë°ú µ¿ÀÏ</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º </font><b><font color="#FF0000">2,750¸¸¸íÀÌ
³Ñ´Â ´ëºÎºÐÀÇ °í°´ÀÌ °³ÀÎÀ¸·Î ±¸¼ºµÇ¾î ÀÖ½À´Ï´Ù.</font></b><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><font color="#FF0000"><b> ¼±ºÒ½ÃÀåÀº ¹«ÇÑÇÕ´Ï´Ù.</b></font><font color="#0000FF">
: </font><font color="#000000">2750¸¸ ÈÄºÒ¿ä±Ý »ç¿ë°í°´</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><b><font color="#FF0000"> 1°¡±¸´ç 11¸¸¿ø ÀÌ»ó »ç¿ëÇÕ´Ï´Ù.
</font><font color="#000000">(1999³â Åë°è)</font></b></td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img18.gif" width="86" height="18">
<table width="480" border="0" cellspacing="2" cellpadding="2" align="center">
<tr>
<td height="305">
<table border="0" width="480" bgcolor="#000000" cellspacing="1" cellpadding="3">
<tr>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ä±Ý»óÇ°</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ÀÏ
±âº»·á</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ù
±âº»·á</font></b></td>
<td width="20%" bgcolor="#CCCCCC" align="center" height="15" colspan="3"><b><font color="#666666">±¹³»ÅëÈ­·á&nbsp;<br>
(¿ø/10ÃÊ)</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ºñ
°í</font></b></td>
</tr>
<tr>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">Æò»ó</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">ÇÒÀÎ</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">½É¾ß</font></b></td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
Ç¥ÁØ</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>533
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>16,000
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>18
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
¿¡ÀÌ½º</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>616
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>18,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>13
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒÇÁ¸®
200</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>1,183
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>35,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>17
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><font color="#FF0000"><b>200ºÐ
¹«·á</b></font></td>
</tr>
</table>
<center>
</center>
<p align="left">&nbsp; ¢º ¿ä±Ý»óÇ° º¯°æ½Ã Àû¿ë½ÃÁ¡ : º¯°æ°ú µ¿½Ã¿¡ º¯°æ¿ä±ÝÀ¸·Î Á¤»êµÇ³ª,
¿ù 1È¸¿¡ ÇÑÇÔ. <br>
&nbsp; ¢º <font color="#008000"><b>ÇÒ ÀÎ ½Ã °£ <br>
&nbsp;&nbsp;&nbsp; </b></font><font color="#800000">1) ¼±ºÒÇ¥ÁØ,
¼±ºÒ¿¡ÀÌ½º ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"> <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~
6 ½Ã (½É¾ß) / 6 ~ 12 (ÇÒÀÎ) / 12 ~ 24 (Æò»ó) &nbsp;&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0
~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ) <br>
&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#800000">2)
¼±ºÒÇÁ¸® 200 ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"><br>
</font><font color="#008000"><b> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</b></font><font color="#000000">- ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~ 6 ½Ã
(½É¾ß) / 6 ~ 8, 21 ~ 24 (ÇÒÀÎ) / 8 ~ 21 (Æò»ó)<br>
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;
- °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0 ~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ)</font>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img12.gif" width="144" height="20"><br>
<table width="480" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img13.gif" width="499" height="359">
<table border="0" width="496" bgcolor="#990000" cellspacing="1" cellpadding="3" align="center">
<tr>
<td width="487" bgcolor="#FFFFFF"> &nbsp;<font color="#008080"><b>KTF</b></font><font color="#000000">(ÇÑ±¹Åë½ÅÇÁ¸®ÅÚ)ÀÇ
Åº»ý ´ç½ÃºÎÅÍ ¸ðµç ½Ã½ºÅÛÀ» ´ã´çÇØ ¿Â &nbsp;<b>´ë¿ìÁ¤º¸½Ã½ºÅÛ</b>Àº&nbsp; <br>
&nbsp;±âÁ¸ ÀüÀÚ»ó°Å·¡ÀÇ ±â¹ÝºÎÀç·Î ¿À´Â ÀûÀÚ¿äÀÎÀ»&nbsp;<b>ÁÖ½ÄÈ¸»ç ³ª¶óÄÞ</b>ÀÇ
³×Æ®¿öÅ© ¸¶ÄÉÆÃÀ» &nbsp;<br>
&nbsp;ÅëÇÏ¿© </font><font color="#FF0000"><b>ÃÖ´Ü±â°£ ÃÖ´ëÈ¸¿ø</b></font><font color="#000000">ÀÇ</font><font color="#FF0000"><b>&nbsp;±â¹ÝÈ®º¸</b></font><font color="#000000">¸¦</font><font color="#FF0000"><b>
¸ñÇ¥</b></font><font color="#000000">·Î&nbsp; <b>KTF, ´ë¿ìÁ¤º¸½Ã½ºÅÛ,&nbsp;ÁÖ½ÄÈ¸»ç
<br>
&nbsp;³ª¶óÄÞÀÇ</b> </font><b><font color="#FF0000">Àü·«Àû Á¦ÈÞ</font></b><font color="#000000">¸¦
ÅëÇÏ¿©&nbsp;<br>
</font> ¼±Áø±¹Çü ¼±ºÒ¿ä±ÝÁ¦µµ
<div align="center">- <b><font color="#008080">KTF</font><font color="#000000">
016</font></b> ¼±ºÒ¿ä±ÝÁ¦µµ -</div>
<div align="right"><font color="#000000">¸¦&nbsp; Åº»ý½ÃÄ×½À´Ï´Ù.</font><font color="#000080">
</font> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img17.gif" width="262" height="21"> <br>
<table width="499" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
E-mail : corud2@dreamwiz.com</td>
</tr>
</table>
</td>
<td width="42">&nbsp;</td>
</tr>
</table>
</td>
</tr>
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img03.gif" width="619" height="31"></td>
</tr>
<tr>
<td>
<div align="center"><img height=10 src="http://www.enativespeaker.com/image/139-1.gif"
width=10> <font size=2>±ÍÇÏÀÇ E-MAILÀº °ü·Ã °Ô½ÃÆÇÀ» ÅëÇØ ¾Ë°Ô µÇ¾ú½À´Ï´Ù. <br>
¿øÄ¡ ¾Ê¾Ò´ø ¸ÞÀÏÀÌ¶ó¸é </font><a
href="mailto:naracom2002@hitel.net?subject=¼ö½Å°ÅºÎ"><font size=2><b><font
color=#0000ff>¿©±â</font></b></font></a><font size=2>¸¦ ´­·¯ ¾Ë·Á ÁÖ½Ã¸é ¾ÕÀ¸·Î´Â ¹ß¼ÛµÇÁö ¾Êµµ·Ï ÇÏ°Ú½À´Ï´Ù.</font>
<font
size=2></font></div>
</td>
</tr>
</table>
<br>
</div>
</body>
</html>

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



From megaco-admin@ietf.org  Mon Jan 21 12:17:38 2002
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 MAA17362
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 12:17:37 -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 MAA19003;
	Mon, 21 Jan 2002 12:08:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18975
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 12:07:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17142
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LH7Rd18721
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:27 -0500 (EST)
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 g0LH7Qa21850
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXP3W>; Mon, 21 Jan 2002 12:07:25 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAD@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 12:07:22 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] H.248v2 Issue: Media Switching and/or Switching Parameters
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

The first paragraph of section 6.1 contains the following sentence:

"The Context describes the topology (who hears/sees whom) and the media
mixing and/or switching parameters if more than two Terminations are
involved in the association."

This sentence reads the way it does because at the time we thought SG 16
would eventually add such parameters.  The debate over the last year on MCU
decomposition has gone back and forth on this one.

Proposal: that SG 16 revisit this sentence when its views on MCU
decomposition become clearer, and delete all after "(who hears/sees whom)"
if this proves inapplicable.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@optimus.ietf.org  Mon Jan 21 12:17:43 2002
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 MAA17375
	for <megaco-archive@odin.ietf.org>; Mon, 21 Jan 2002 12:17:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA19190
	for megaco-archive@odin.ietf.org; Mon, 21 Jan 2002 12:17:42 -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 MAA19003;
	Mon, 21 Jan 2002 12:08:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18975
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 12:07:59 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17142
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LH7Rd18721
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:27 -0500 (EST)
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 g0LH7Qa21850
	for <megaco@ietf.org>; Mon, 21 Jan 2002 12:07:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXP3W>; Mon, 21 Jan 2002 12:07:25 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAD@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 12:07:22 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] H.248v2 Issue: Media Switching and/or Switching Parameters
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

The first paragraph of section 6.1 contains the following sentence:

"The Context describes the topology (who hears/sees whom) and the media
mixing and/or switching parameters if more than two Terminations are
involved in the association."

This sentence reads the way it does because at the time we thought SG 16
would eventually add such parameters.  The debate over the last year on MCU
decomposition has gone back and forth on this one.

Proposal: that SG 16 revisit this sentence when its views on MCU
decomposition become clearer, and delete all after "(who hears/sees whom)"
if this proves inapplicable.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Tue Jan 22 09:47:56 2002
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 JAA20211
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:47:56 -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 JAA09569;
	Tue, 22 Jan 2002 09:39:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29204
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 17:00:43 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26412
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:00:39 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0LM0fw12663
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:00:41 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LM0er6011209
	for <megaco@ietf.org>; Tue, 22 Jan 2002 00:00:40 +0200 (EET)
Message-ID: <3C4C8F8A.6BB0F10@lmf.ericsson.se>
Date: Tue, 22 Jan 2002 00:00:42 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Method is Disconnected
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: 7bit


Hi,

In V2, both serviceChangeMethod and serviceChangeReason are MANDATORY.

So, my questions is: if the Method value is 'Disconneced', what shall
the Reason value be? I can't find any which would fit...

Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Tue Jan 22 09:47:57 2002
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 JAA20221
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:47:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10858
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:48:00 -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 JAA09569;
	Tue, 22 Jan 2002 09:39:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29204
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 17:00:43 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26412
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:00:39 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0LM0fw12663
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:00:41 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LM0er6011209
	for <megaco@ietf.org>; Tue, 22 Jan 2002 00:00:40 +0200 (EET)
Message-ID: <3C4C8F8A.6BB0F10@lmf.ericsson.se>
Date: Tue, 22 Jan 2002 00:00:42 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Method is Disconnected
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: 7bit


Hi,

In V2, both serviceChangeMethod and serviceChangeReason are MANDATORY.

So, my questions is: if the Method value is 'Disconneced', what shall
the Reason value be? I can't find any which would fit...

Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Tue Jan 22 09:49:47 2002
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 JAA20344
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:49:43 -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 JAA09878;
	Tue, 22 Jan 2002 09:40:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09000
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:52 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01629;
	Tue, 22 Jan 2002 14:19:32 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13874;
	Tue, 22 Jan 2002 14:20:53 +1100 (EST)
Message-ID: <3C4CD931.7039B18C@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:14:57 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] H.248v2 Issue: Media Switching and/or Switching Parameters
References: <4D79C746863DD51197690002A52CDA000102AEAD@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

What is the problem with leaving "(who hears/sees whom)"? It is the
context which provides this. Whether it is implied or a certain property
of the termination/context is a completely different issue. I thought
that it reads that way because the context along with
streams/terminations/properties/other contexts all describe the
connection model in the MG. 

Regards, Christian

Tom-PT Taylor wrote:
> 
> The first paragraph of section 6.1 contains the following sentence:
> 
> "The Context describes the topology (who hears/sees whom) and the media
> mixing and/or switching parameters if more than two Terminations are
> involved in the association."
> 
> This sentence reads the way it does because at the time we thought SG 16
> would eventually add such parameters.  The debate over the last year on MCU
> decomposition has gone back and forth on this one.
> 
> Proposal: that SG 16 revisit this sentence when its views on MCU
> decomposition become clearer, and delete all after "(who hears/sees whom)"
> if this proves inapplicable.
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Tue Jan 22 09:49:48 2002
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 JAA20358
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:49:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10957
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:49:52 -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 JAA09878;
	Tue, 22 Jan 2002 09:40:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09000
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01660
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:52 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01629;
	Tue, 22 Jan 2002 14:19:32 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13874;
	Tue, 22 Jan 2002 14:20:53 +1100 (EST)
Message-ID: <3C4CD931.7039B18C@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:14:57 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] H.248v2 Issue: Media Switching and/or Switching Parameters
References: <4D79C746863DD51197690002A52CDA000102AEAD@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

What is the problem with leaving "(who hears/sees whom)"? It is the
context which provides this. Whether it is implied or a certain property
of the termination/context is a completely different issue. I thought
that it reads that way because the context along with
streams/terminations/properties/other contexts all describe the
connection model in the MG. 

Regards, Christian

Tom-PT Taylor wrote:
> 
> The first paragraph of section 6.1 contains the following sentence:
> 
> "The Context describes the topology (who hears/sees whom) and the media
> mixing and/or switching parameters if more than two Terminations are
> involved in the association."
> 
> This sentence reads the way it does because at the time we thought SG 16
> would eventually add such parameters.  The debate over the last year on MCU
> decomposition has gone back and forth on this one.
> 
> Proposal: that SG 16 revisit this sentence when its views on MCU
> decomposition become clearer, and delete all after "(who hears/sees whom)"
> if this proves inapplicable.
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 22 09:49:52 2002
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 JAA20376
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:49:52 -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 JAA09607;
	Tue, 22 Jan 2002 09:40:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29571
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 17:25:07 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26890
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:58 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LMOUd13965
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:30 -0500 (EST)
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 g0LMOTa09938
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXZGG>; Mon, 21 Jan 2002 17:24:29 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 17:24:28 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: TIPHON Release 4: Documents for WG3 Approval
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

FYI.  I'm sure they would accept outside comments if you have some.

-----Original Message-----
From: Richard Brennan [mailto:rbrennan@TELXXIS.COM]
Sent: Monday, January 21, 2002 2:35 PM
To: TIPHON_WG3@LIST.ETSI.FR
Subject: TIPHON Release 4: Documents for WG3 Approval


Dear all,

Two Release 4 documents based on new Work Items created at TIPHON 24
in November, reached stable draft at the TIPHON 25 meeting last week, and
have been referred to the Working Group 3 mailing list for Working Group
approval.

The documents are:

DTS/TIPHON-03027 V0.0.3
"TIPHON Release 4; Interface Protocol Requirements Definition;
TIPHON Extended MEGACO Package (EMP) Specification"
http://docbox.etsi.org/tech-org/tiphon/document/tiphon/07-drafts/WG3/DTS0302
7R4/V0.0.3

and

DTS/TIPHON-03028 V0.0.3
"TIPHON Release 4; Interface Protocol Requirements Definition;
Technology mapping of TIPHON architecture to Extended MEGACO Package"
http://docbox.etsi.org/tech-org/tiphon/document/tiphon/07-drafts/WG3/DTS0302
8R4/V0.0.3

Starting today, there will be a 4 week review period on the mailing list.
If no unresolved
comments are received by 18 February, 2002,  the documents will be
considered as
Working Group approved, placed under the Change Control process, and
submitted for TB
approval at the TIPHON 26 Plenary.

===================================
Richard Brennan - Telxxis LLC
Chairman ETSI TIPHON WG3
Office:         +1 650 655-2630
PCS/GSM:        +1 510 543-4726
mailto:rbrennan@telxxis.com
===================================

-------------------------------------------------------------------
Mail archive for TIPHON_WG3  can be browsed at the following url :

             http://list.etsi.fr/tiphon_wg3.html
-------------------------------------------------------------------

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


From megaco-admin@ietf.org  Tue Jan 22 09:51:24 2002
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 JAA20472
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:51:24 -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 JAA09509;
	Tue, 22 Jan 2002 09:39:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26943
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 15:56:39 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24176
	for <megaco@ietf.org>; Mon, 21 Jan 2002 15:56:36 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0LKuWw18037;
	Mon, 21 Jan 2002 21:56:32 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LKuVr6008433;
	Mon, 21 Jan 2002 22:56:31 +0200 (EET)
Message-ID: <3C4C8082.C34A8A0F@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 22:56:34 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>While we're on the topic of Annex M.4, I realized while reading it that it
>improperly (I think) includes some control terminations in the multiplex.
>This may be water under the bridge now -- too late to do anything about it.

It includes some properties, ie muxtbl_in/out properties, which are
defined in the LocalControl descriptor. The LocalControl descriptor,
again, is defined in a Stream Descriptor (default StreamID = 1 if no
descriptor is defined). So, one would have to specify a Stream
descriptor for the multiplexer itself... Strange. I don't know if you
were refering to the same issue.

Regards,

Christer Holmberg
Ericsson Finland

> 
> Anyway, Christer is asking for more than I would put into the core protocol
> specification.  We should probably create an Informational RFC describing
> multiplex use with examples, just as we should publish an Informational RFC
> giving example call flows.
> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Monday, January 21, 2002 12:52 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I think that the H.324 package probably needs to be updated to say how
> >this is done. I don't think its a core H.248 issue.
> 
> I agree. The idea was that this property would be defined in the H.324
> package, and then used within each stream descriptor in the Mux
> Termination.
> 
> >Perhaps an IG note could be added for the H324 package? I'd like to see a
> reply from the
> > H324 package authors on how they thought this was to be done.
> 
> >Are there any updates you'd like to see to proposed text on
> MultiplexDescriptors that Tom posted?
> 
> First, as Tom already mentioned, it should be updated so that it also
> includes emphemeral bearer terminations (RTP terminations, for example).
> 
> Second, it should in detail, on a message level, describe how the
> multiplexed connection is set up. Now it only says "use a stream
> descriptor" - which means everyone is going to understand it their own
> way, and we are going to have lots of interop problems when people start
> implementing this :)
> 
> Third, it should also describe in detail how the H.223 (or whatever
> multiplex method is used) descriptor is used, ie which terminations are
> included etc, depending on on which "side" of the multiplexer the
> terminations are.
> 
> Fourth, I think the whole Annex M.4 misses some things, but that's
> another discussion...
> 
> I understand if you want to get this document ready before february, but
> please let us do this correct from the beginning :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > I have read the document a few times, but even by having stream
> > > descriptors in the mux termination, I still don't understand how each of
> > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > supposed to be the same as the LCN number, or how is the mapping done?
> > >
> > > A very simple solution would be to add a "LCN property" (to the H.324
> > > package, I assume) which would be used in the each stream descriptor to
> > > specify to which LCN it is mapped.
> > >
> > > Comments?
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > I mentioned that several of us have been discussing additional text
> for
> > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> changes
> > > > in the Megaco FTP site.  According to your taste, you can download
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.doc
> > > > or
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.pdf
> > > >
> > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > proposed text needs a further update.  The supporting bearers
> contained by a
> > > > multiplexing termination can be ephemeral as well as physical.
> However, I
> > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > descriptor already exist in the context, since their properties are
> probably
> > > > not directly inferrable from those of the multiplexing termination.
> > > >
> > > > Tom Taylor
> > > > taylor@nortelnetworks.com
> > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > >
> > > >
> > > > _______________________________________________
> > > > 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


From daemon@optimus.ietf.org  Tue Jan 22 09:51:29 2002
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 JAA20479
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:51:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA11048
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:51:29 -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 JAA09509;
	Tue, 22 Jan 2002 09:39:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26943
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 15:56:39 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24176
	for <megaco@ietf.org>; Mon, 21 Jan 2002 15:56:36 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0LKuWw18037;
	Mon, 21 Jan 2002 21:56:32 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LKuVr6008433;
	Mon, 21 Jan 2002 22:56:31 +0200 (EET)
Message-ID: <3C4C8082.C34A8A0F@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 22:56:34 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>While we're on the topic of Annex M.4, I realized while reading it that it
>improperly (I think) includes some control terminations in the multiplex.
>This may be water under the bridge now -- too late to do anything about it.

It includes some properties, ie muxtbl_in/out properties, which are
defined in the LocalControl descriptor. The LocalControl descriptor,
again, is defined in a Stream Descriptor (default StreamID = 1 if no
descriptor is defined). So, one would have to specify a Stream
descriptor for the multiplexer itself... Strange. I don't know if you
were refering to the same issue.

Regards,

Christer Holmberg
Ericsson Finland

> 
> Anyway, Christer is asking for more than I would put into the core protocol
> specification.  We should probably create an Informational RFC describing
> multiplex use with examples, just as we should publish an Informational RFC
> giving example call flows.
> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Monday, January 21, 2002 12:52 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I think that the H.324 package probably needs to be updated to say how
> >this is done. I don't think its a core H.248 issue.
> 
> I agree. The idea was that this property would be defined in the H.324
> package, and then used within each stream descriptor in the Mux
> Termination.
> 
> >Perhaps an IG note could be added for the H324 package? I'd like to see a
> reply from the
> > H324 package authors on how they thought this was to be done.
> 
> >Are there any updates you'd like to see to proposed text on
> MultiplexDescriptors that Tom posted?
> 
> First, as Tom already mentioned, it should be updated so that it also
> includes emphemeral bearer terminations (RTP terminations, for example).
> 
> Second, it should in detail, on a message level, describe how the
> multiplexed connection is set up. Now it only says "use a stream
> descriptor" - which means everyone is going to understand it their own
> way, and we are going to have lots of interop problems when people start
> implementing this :)
> 
> Third, it should also describe in detail how the H.223 (or whatever
> multiplex method is used) descriptor is used, ie which terminations are
> included etc, depending on on which "side" of the multiplexer the
> terminations are.
> 
> Fourth, I think the whole Annex M.4 misses some things, but that's
> another discussion...
> 
> I understand if you want to get this document ready before february, but
> please let us do this correct from the beginning :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > I have read the document a few times, but even by having stream
> > > descriptors in the mux termination, I still don't understand how each of
> > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > supposed to be the same as the LCN number, or how is the mapping done?
> > >
> > > A very simple solution would be to add a "LCN property" (to the H.324
> > > package, I assume) which would be used in the each stream descriptor to
> > > specify to which LCN it is mapped.
> > >
> > > Comments?
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > I mentioned that several of us have been discussing additional text
> for
> > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> changes
> > > > in the Megaco FTP site.  According to your taste, you can download
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.doc
> > > > or
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.pdf
> > > >
> > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > proposed text needs a further update.  The supporting bearers
> contained by a
> > > > multiplexing termination can be ephemeral as well as physical.
> However, I
> > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > descriptor already exist in the context, since their properties are
> probably
> > > > not directly inferrable from those of the multiplexing termination.
> > > >
> > > > Tom Taylor
> > > > taylor@nortelnetworks.com
> > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > >
> > > >
> > > > _______________________________________________
> > > > 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



From megaco-admin@ietf.org  Tue Jan 22 09:51:52 2002
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 JAA20515
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:51:47 -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 JAA09480;
	Tue, 22 Jan 2002 09:39:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26735
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 15:45:27 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23726
	for <megaco@ietf.org>; Mon, 21 Jan 2002 15:45:21 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0LKj1IB019068;
	Mon, 21 Jan 2002 21:45:01 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LKj0r6008006;
	Mon, 21 Jan 2002 22:45:00 +0200 (EET)
Message-ID: <3C4C7DCE.AA438A49@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 22:45:02 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>While we're on the topic of Annex M.4, I realized while reading it that it
>improperly (I think) includes some control terminations in the multiplex.
>This may be water under the bridge now -- too late to do anything about it.
> 
>Anyway, Christer is asking for more than I would put into the core protocol
>specification.  We should probably create an Informational RFC describing
>multiplex use with examples, just as we should publish an Informational RFC
>giving example call flows.

Why not removing the whole multiplex chapter from the core protocol,
then, and putting it in a separate Annex, or something? The way it's
defined now (even by adding the proposed changes) doesn't help anyone.
You simply can't implement multiplexing with the info you get from that
text (you don't know how to map the LCNs, which btw also are
uni-dirctional, to specific terminations etc etc) - and that's NOT
enough in my opinion.

I thought that the ITU people always wanted to specify everything very
much in detail :)

Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Monday, January 21, 2002 12:52 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I think that the H.324 package probably needs to be updated to say how
> >this is done. I don't think its a core H.248 issue.
> 
> I agree. The idea was that this property would be defined in the H.324
> package, and then used within each stream descriptor in the Mux
> Termination.
> 
> >Perhaps an IG note could be added for the H324 package? I'd like to see a
> reply from the
> > H324 package authors on how they thought this was to be done.
> 
> >Are there any updates you'd like to see to proposed text on
> MultiplexDescriptors that Tom posted?
> 
> First, as Tom already mentioned, it should be updated so that it also
> includes emphemeral bearer terminations (RTP terminations, for example).
> 
> Second, it should in detail, on a message level, describe how the
> multiplexed connection is set up. Now it only says "use a stream
> descriptor" - which means everyone is going to understand it their own
> way, and we are going to have lots of interop problems when people start
> implementing this :)
> 
> Third, it should also describe in detail how the H.223 (or whatever
> multiplex method is used) descriptor is used, ie which terminations are
> included etc, depending on on which "side" of the multiplexer the
> terminations are.
> 
> Fourth, I think the whole Annex M.4 misses some things, but that's
> another discussion...
> 
> I understand if you want to get this document ready before february, but
> please let us do this correct from the beginning :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > I have read the document a few times, but even by having stream
> > > descriptors in the mux termination, I still don't understand how each of
> > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > supposed to be the same as the LCN number, or how is the mapping done?
> > >
> > > A very simple solution would be to add a "LCN property" (to the H.324
> > > package, I assume) which would be used in the each stream descriptor to
> > > specify to which LCN it is mapped.
> > >
> > > Comments?
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > I mentioned that several of us have been discussing additional text
> for
> > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> changes
> > > > in the Megaco FTP site.  According to your taste, you can download
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.doc
> > > > or
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.pdf
> > > >
> > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > proposed text needs a further update.  The supporting bearers
> contained by a
> > > > multiplexing termination can be ephemeral as well as physical.
> However, I
> > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > descriptor already exist in the context, since their properties are
> probably
> > > > not directly inferrable from those of the multiplexing termination.
> > > >
> > > > Tom Taylor
> > > > taylor@nortelnetworks.com
> > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > >
> > > >
> > > > _______________________________________________
> > > > 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


From daemon@optimus.ietf.org  Tue Jan 22 09:51:52 2002
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 JAA20526
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:51:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA11070
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:51:56 -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 JAA09480;
	Tue, 22 Jan 2002 09:39:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26735
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 15:45:27 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23726
	for <megaco@ietf.org>; Mon, 21 Jan 2002 15:45:21 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0LKj1IB019068;
	Mon, 21 Jan 2002 21:45:01 +0100 (MET)
Received: from lmf.ericsson.se ([131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0LKj0r6008006;
	Mon, 21 Jan 2002 22:45:00 +0200 (EET)
Message-ID: <3C4C7DCE.AA438A49@lmf.ericsson.se>
Date: Mon, 21 Jan 2002 22:45:02 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>While we're on the topic of Annex M.4, I realized while reading it that it
>improperly (I think) includes some control terminations in the multiplex.
>This may be water under the bridge now -- too late to do anything about it.
> 
>Anyway, Christer is asking for more than I would put into the core protocol
>specification.  We should probably create an Informational RFC describing
>multiplex use with examples, just as we should publish an Informational RFC
>giving example call flows.

Why not removing the whole multiplex chapter from the core protocol,
then, and putting it in a separate Annex, or something? The way it's
defined now (even by adding the proposed changes) doesn't help anyone.
You simply can't implement multiplexing with the info you get from that
text (you don't know how to map the LCNs, which btw also are
uni-dirctional, to specific terminations etc etc) - and that's NOT
enough in my opinion.

I thought that the ITU people always wanted to specify everything very
much in detail :)

Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Monday, January 21, 2002 12:52 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I think that the H.324 package probably needs to be updated to say how
> >this is done. I don't think its a core H.248 issue.
> 
> I agree. The idea was that this property would be defined in the H.324
> package, and then used within each stream descriptor in the Mux
> Termination.
> 
> >Perhaps an IG note could be added for the H324 package? I'd like to see a
> reply from the
> > H324 package authors on how they thought this was to be done.
> 
> >Are there any updates you'd like to see to proposed text on
> MultiplexDescriptors that Tom posted?
> 
> First, as Tom already mentioned, it should be updated so that it also
> includes emphemeral bearer terminations (RTP terminations, for example).
> 
> Second, it should in detail, on a message level, describe how the
> multiplexed connection is set up. Now it only says "use a stream
> descriptor" - which means everyone is going to understand it their own
> way, and we are going to have lots of interop problems when people start
> implementing this :)
> 
> Third, it should also describe in detail how the H.223 (or whatever
> multiplex method is used) descriptor is used, ie which terminations are
> included etc, depending on on which "side" of the multiplexer the
> terminations are.
> 
> Fourth, I think the whole Annex M.4 misses some things, but that's
> another discussion...
> 
> I understand if you want to get this document ready before february, but
> please let us do this correct from the beginning :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > I have read the document a few times, but even by having stream
> > > descriptors in the mux termination, I still don't understand how each of
> > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > supposed to be the same as the LCN number, or how is the mapping done?
> > >
> > > A very simple solution would be to add a "LCN property" (to the H.324
> > > package, I assume) which would be used in the each stream descriptor to
> > > specify to which LCN it is mapped.
> > >
> > > Comments?
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > I mentioned that several of us have been discussing additional text
> for
> > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> changes
> > > > in the Megaco FTP site.  According to your taste, you can download
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.doc
> > > > or
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > x64K.pdf
> > > >
> > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > proposed text needs a further update.  The supporting bearers
> contained by a
> > > > multiplexing termination can be ephemeral as well as physical.
> However, I
> > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > descriptor already exist in the context, since their properties are
> probably
> > > > not directly inferrable from those of the multiplexing termination.
> > > >
> > > > Tom Taylor
> > > > taylor@nortelnetworks.com
> > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > >
> > > >
> > > > _______________________________________________
> > > > 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



From megaco-admin@ietf.org  Tue Jan 22 09:57:59 2002
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 JAA21749
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:57:55 -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 JAA09926;
	Tue, 22 Jan 2002 09:40:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09002
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01661
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:53 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01650;
	Tue, 22 Jan 2002 14:19:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13878;
	Tue, 22 Jan 2002 14:20:54 +1100 (EST)
Message-ID: <3C4CDA6F.3DB0A2B8@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:20:15 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Issues In H.248v2: Context Packages
References: <4D79C746863DD51197690002A52CDA000102AEAB@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Tom,

How was the sentiment on the context property recorded at the meeting?
Was there a hum poll or similar? If you are asking the list to confirm
this what particular arguments are there for delaying this? What
implications haven't been studied?

Cheers, Christian

Tom-PT Taylor wrote:
> 
> I was waiting for others to raise issues for our contribution to SG 16, but
> there hasn't been much addressed specifically to H.248v2.  This is the first
> of a series of E-mails I am going to generate on the topic.
> 
> The sentiment at IETF 52 was that packages for context properties were the
> one item that we would like to have SG 16 to defer until the full
> implications are realized.  That is, it should not be included in H.248v2.
> Can I confirm this view with the list?
> 
> Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> 
>  - delete final bullet of section 6.1.1
> 
>  - delete final sentence of first paragraph of section 6.2.3
> 
>  - delete second sentence of second paragraph of section 6.2.3
> 
>  - delete the phrase "or Context" from the last sentence of second paragraph
> of section 6.2.3
> 
>  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> subsequent section(s) accordingly
> 
>  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> follows:
>    -- in the third paragraph, amend the final sentence to say "There are two
> types of audit."
>    -- in the paragraphs beginning "Value Audit:" and "Capabilities Audit:",
> delete the phrase "the ContextAttribute Descriptor or"
>    -- delete the paragraph beginning "Packages Audit"
>    -- delete the Audit Packages column of the table
> 
>  - delete the phrase "and contexts" in the first paragraph of section 12
> 
>  - delete the sentence beginning "ContextAttribute is for ..." and also the
> final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> 
>  - delete the final sentence of the paragraph explaining "Characteristics:"
> in section 12.1.2
> 
>  - in Annex A:
>    -- delete the contextProp and contextPackages components added after the
> extension marker in the ContextRequest production
>    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> contextPropCapAud, and contextPackagesAud components added after the
> extension marker in the ContextAttrAuditRequest production
> 
>  - in Annex B:
>    -- delete the contextAttrDescriptor and packagesDescriptor terms from the
> contextProperty production
>    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> IndAudContextAttrCap, and ContextAttrPackages terms from the
> contextAuditProperties production
>    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> ContextAttrDescriptorCapAud productions
>    -- delete the contextAttrDescriptor production
>    -- delete the ContextAttrToken, ContextAudCapToken,
> ContextAudDescriptorToken, and ContextAudValToken productions
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Tue Jan 22 09:58:04 2002
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 JAA21831
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:58:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA11417
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:58:04 -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 JAA09926;
	Tue, 22 Jan 2002 09:40:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09002
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01661
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:53 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01650;
	Tue, 22 Jan 2002 14:19:33 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13878;
	Tue, 22 Jan 2002 14:20:54 +1100 (EST)
Message-ID: <3C4CDA6F.3DB0A2B8@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:20:15 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Issues In H.248v2: Context Packages
References: <4D79C746863DD51197690002A52CDA000102AEAB@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Tom,

How was the sentiment on the context property recorded at the meeting?
Was there a hum poll or similar? If you are asking the list to confirm
this what particular arguments are there for delaying this? What
implications haven't been studied?

Cheers, Christian

Tom-PT Taylor wrote:
> 
> I was waiting for others to raise issues for our contribution to SG 16, but
> there hasn't been much addressed specifically to H.248v2.  This is the first
> of a series of E-mails I am going to generate on the topic.
> 
> The sentiment at IETF 52 was that packages for context properties were the
> one item that we would like to have SG 16 to defer until the full
> implications are realized.  That is, it should not be included in H.248v2.
> Can I confirm this view with the list?
> 
> Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> 
>  - delete final bullet of section 6.1.1
> 
>  - delete final sentence of first paragraph of section 6.2.3
> 
>  - delete second sentence of second paragraph of section 6.2.3
> 
>  - delete the phrase "or Context" from the last sentence of second paragraph
> of section 6.2.3
> 
>  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> subsequent section(s) accordingly
> 
>  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> follows:
>    -- in the third paragraph, amend the final sentence to say "There are two
> types of audit."
>    -- in the paragraphs beginning "Value Audit:" and "Capabilities Audit:",
> delete the phrase "the ContextAttribute Descriptor or"
>    -- delete the paragraph beginning "Packages Audit"
>    -- delete the Audit Packages column of the table
> 
>  - delete the phrase "and contexts" in the first paragraph of section 12
> 
>  - delete the sentence beginning "ContextAttribute is for ..." and also the
> final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> 
>  - delete the final sentence of the paragraph explaining "Characteristics:"
> in section 12.1.2
> 
>  - in Annex A:
>    -- delete the contextProp and contextPackages components added after the
> extension marker in the ContextRequest production
>    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> contextPropCapAud, and contextPackagesAud components added after the
> extension marker in the ContextAttrAuditRequest production
> 
>  - in Annex B:
>    -- delete the contextAttrDescriptor and packagesDescriptor terms from the
> contextProperty production
>    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> IndAudContextAttrCap, and ContextAttrPackages terms from the
> contextAuditProperties production
>    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> ContextAttrDescriptorCapAud productions
>    -- delete the contextAttrDescriptor production
>    -- delete the ContextAttrToken, ContextAudCapToken,
> ContextAudDescriptorToken, and ContextAudValToken productions
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 22 09:58:29 2002
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 JAA22066
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:58:29 -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 JAA09870;
	Tue, 22 Jan 2002 09:40:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA08995
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01659
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:52 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01605;
	Tue, 22 Jan 2002 14:19:31 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13870;
	Tue, 22 Jan 2002 14:20:52 +1100 (EST)
Message-ID: <3C4CD851.72F49970@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:11:13 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

There is a timing dependency here. If the MG issues a SC Graceful then
the MGC will act on it. There will be a finite time that the MGC
operates under graceful mode. If a SC Restart w/Service Restored or
Service Change Cancel is issued during the graceful the MGC can't undo
what it had done in that finite time but the connections that stayed up
can remain up. If the SC Restart w/service restored or Service Change
Cancel is not received before the delay times out then it pretty too
late as the terminations will be torn down.

I don't understand why you say that the MGC must wait until the
servicechange delay timesouts before gracefully tearing down
connections?

Christian


"Chuong N. Nguyen" wrote:
> 
> 
> MG sends SC Graceful w/Delay and terminationID=ROOT.
> 
> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> assume that
> 1) SC Graceful w/Delay is being cancelled?
> 2) All terminations are back In Service?  Even the ones that were
> originally OOS before the SC Graceful.
> 
> 
>    1) Graceful - indicates that the specified Terminations will be
> taken
>       out of service after the specified ServiceChangeDelay;
> established
>       connections are not yet affected, but the Media Gateway
> Controller
>       should refrain from establishing new connections and should
>       attempt to gracefully tear down existing connections on the
>       Termination(s) affected by the serviceChange command. The MG
>       should set termination serviceState at the expiry of
>       ServiceChangeDelay or the removal of the termination from an
>       active context (whichever is first), to "out of service".
> 
> 
> How should MGC implementation intepret the above highlighted
> statement?
> Does this mean that MGC should not try to gracefully tear down
> existing connections
> before Delay timer expired?
> 
> But I think the above statement is telling MGC to try and gracefully
> tear down
> existing connections before Delay timer expired.
> 
> To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> until
> Delay timer expired before it tries to tear down existing connections.
> 
> But after Delay timer expired, MG will put all terminations out of
> service.
> Therefore there is no such thing as MGC gracefully tearing down
> existing connections.
> 
> 
> Christian Groves wrote:
> 
> > I don't see that we need to add anything. Why can't the MG just
> > issue a
> > SC with Restart, Service Restored? The specification already allows
> > the
> > MG to do this.
> >
> > Regards, Christian
> >
> > "Chuong N. Nguyen" wrote:
> > >
> > > Hi Tom
> > >
> > > What are the possibilites of defining a mechanism of cancelling
> > > ServiceChange Graceful?
> > > That is MG send SC Graceful w/Delay=time.
> > > Before time expired, MG wants to cancel this ServiceChange.
> > >
> > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > Graceful cancelled"?
> > > 2) Done in V2 - new SC Method or Reason?
> > > 3) Should be covered in draft-hss-megaco-control-association?
> > >
> > >
> > > Thanks
> > > Chuong
> > >
> > >
> > >
> > > --
> > >   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


From daemon@optimus.ietf.org  Tue Jan 22 09:58:29 2002
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 JAA22077
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:58:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA11441
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:58:33 -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 JAA09870;
	Tue, 22 Jan 2002 09:40:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA08995
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:58 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01659
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:52 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01605;
	Tue, 22 Jan 2002 14:19:31 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13870;
	Tue, 22 Jan 2002 14:20:52 +1100 (EST)
Message-ID: <3C4CD851.72F49970@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:11:13 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

There is a timing dependency here. If the MG issues a SC Graceful then
the MGC will act on it. There will be a finite time that the MGC
operates under graceful mode. If a SC Restart w/Service Restored or
Service Change Cancel is issued during the graceful the MGC can't undo
what it had done in that finite time but the connections that stayed up
can remain up. If the SC Restart w/service restored or Service Change
Cancel is not received before the delay times out then it pretty too
late as the terminations will be torn down.

I don't understand why you say that the MGC must wait until the
servicechange delay timesouts before gracefully tearing down
connections?

Christian


"Chuong N. Nguyen" wrote:
> 
> 
> MG sends SC Graceful w/Delay and terminationID=ROOT.
> 
> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> assume that
> 1) SC Graceful w/Delay is being cancelled?
> 2) All terminations are back In Service?  Even the ones that were
> originally OOS before the SC Graceful.
> 
> 
>    1) Graceful - indicates that the specified Terminations will be
> taken
>       out of service after the specified ServiceChangeDelay;
> established
>       connections are not yet affected, but the Media Gateway
> Controller
>       should refrain from establishing new connections and should
>       attempt to gracefully tear down existing connections on the
>       Termination(s) affected by the serviceChange command. The MG
>       should set termination serviceState at the expiry of
>       ServiceChangeDelay or the removal of the termination from an
>       active context (whichever is first), to "out of service".
> 
> 
> How should MGC implementation intepret the above highlighted
> statement?
> Does this mean that MGC should not try to gracefully tear down
> existing connections
> before Delay timer expired?
> 
> But I think the above statement is telling MGC to try and gracefully
> tear down
> existing connections before Delay timer expired.
> 
> To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> until
> Delay timer expired before it tries to tear down existing connections.
> 
> But after Delay timer expired, MG will put all terminations out of
> service.
> Therefore there is no such thing as MGC gracefully tearing down
> existing connections.
> 
> 
> Christian Groves wrote:
> 
> > I don't see that we need to add anything. Why can't the MG just
> > issue a
> > SC with Restart, Service Restored? The specification already allows
> > the
> > MG to do this.
> >
> > Regards, Christian
> >
> > "Chuong N. Nguyen" wrote:
> > >
> > > Hi Tom
> > >
> > > What are the possibilites of defining a mechanism of cancelling
> > > ServiceChange Graceful?
> > > That is MG send SC Graceful w/Delay=time.
> > > Before time expired, MG wants to cancel this ServiceChange.
> > >
> > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > Graceful cancelled"?
> > > 2) Done in V2 - new SC Method or Reason?
> > > 3) Should be covered in draft-hss-megaco-control-association?
> > >
> > >
> > > Thanks
> > > Chuong
> > >
> > >
> > >
> > > --
> > >   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



From megaco-admin@ietf.org  Tue Jan 22 09:58:50 2002
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 JAA22276
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:58:50 -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 JAA09747;
	Tue, 22 Jan 2002 09:40:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA04193
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 19:36:49 -0500 (EST)
Received: from localhost ([218.55.130.23])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28968
	for <megaco@ietf.org>; Mon, 21 Jan 2002 19:36:44 -0500 (EST)
Message-Id: <200201220036.TAA28968@ietf.org>
Reply-To: naracom2002@naver.com
From: (ÁÖ)³ª¶óÄÞ<naracom2002@naver.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 22 Jan 2002 09:51:43 +0900
Subject: [Megaco] ¾È³çÇÏ¼¼¿ä[È«º¸]
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

<html>
<head>
<title>¼±ºÒ¿ä±ÝÁ¦ ÂüÁ¶ÀÚ·áÁý</title>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
<meta name="generator" content="Namo WebEditor v4.0">
<style type="text/css">
<!--
td { font-family: "µ¸¿ò", "µ¸¿òÃ¼"; font-size: 12px; color: #000000; line-height: 120%}
-->
</style>
</head>
<body text="black" link="blue" vlink="purple" alink="red">
<div>
<table width="620" border="0" cellspacing="2" cellpadding="2" align="center">
<tr bgcolor="#FFFFFF">
<td>
<p>¾È³çÇÏ¼¼¿ä ÀúÈ£ÁØÀÌ¿¡¿ä<br>
ÀßÁö³»°í °è½ÃÁ®?<br>
ÁÁÀºÁ¤º¸°¡ ÀÌ·¸°Ô ¸áº¸³» µå·Á¿ä<br>
ÇÑ¹ø ²Ä²ÄÈ÷ µûÁ®º¸¼¼¿ä ¾Æ¸¶ ¸¹Àºµµ¿òµÉ°Å¿¡¿ä<br>
¾Æ·¡¿¡ ÆÄÀÏÃ·ºÎÇßÀ¸´Ï ÀÐ¾îº¸½Ã°í¿ä<br>
±×·³ ¶Ç ¸áµå¸±²²¿ä<br>
</td>
</tr>
</table>
<table width="623" border="0" cellspacing="0" cellpadding="0" align="center">
<tr valign="top">
<td height="218" background="http://www.copyi114.co.kr/nara/img01.gif"> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width="575" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="396" height="68"> ¼±ºÒ¿ä±ÝÁ¦¼­ºñ½º´Â ¾î´À³¯ °©ÀÚ±â ³ª¿Â ¼­ºñ½º°¡ ¾Æ´Ñ, ¼±Áø ¿©·¯³ª¶ó¿¡¼­´Â
ÀÌ¹Ì ±âÁ¸¿¡ ½Ç½ÃÇÏ°í´Â ¼­ºñ½º·Î È¸»çÀÇ ÀÔÀå¿¡¼­´Â ¾ÈÁ¤ÀûÀÌ¸ç ¹Ì³³ °ÆÁ¤ÀÌ ¾ø´Â È¸¿øÀ¯Ä¡¸¦ ÇÏ¿© È¸»çÀÇ ¾ÈÁ¤¼ºÀ» ²ÒÇÒ
¼ö ÀÖÀ¸¸ç, ÀÌ¿¡µû¸¥ °í°´Àº °¢Á¾ ÇýÅÃ ¹× ¼ö´çÀ» ¹Þ´Â °ÍÀÔ´Ï´Ù.<br>
Áï ¼±ºÒÁ¦¿ä±ÝÁ¦¶õ ¸ÕÀú ÀÏÁ¤ºÎºÐÀÇ Åë½Å·á¸¦ ³»°í Ä³½¬¹é(Çö±Ý)°ú ±âÅ¸ ¼ö´çÀ» ¹Þ´Â ¿ä±ÝÃ¼°èÀÌ¸ç, ÀÌ·ÎÀÎÇÑ ÇýÅÃÀ» °í°´¿¡°Ô
Å©°Ô´Â 35%¿¡ ÇØ´çµÇ´Â ºÎºÐÀ» ´Ù½Ã Çö±ÝÀ¸·Î µ¹·Áµå¸®°í ÀÖ½À´Ï´Ù. </td>
<td width="179" height="68" valign="bottom">
<div align="center"><a href="http://www.copyi114.co.kr/nara/news.htm" target="_blank"><img src="http://www.copyi114.co.kr/nara/img16.gif" width="145" height="67" border="0"></a></div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td background="http://www.copyi114.co.kr/nara/img02.gif">
<table width="620" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="17">&nbsp;</td>
<td width="561"> <img src="http://www.copyi114.co.kr/nara/img14.gif" width="175" height="22"><br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img15.gif" width="461" height="91"><br>
1. ¾Ç¼º¿¬Ã¼ ¿ä±ÝÀ¸·Î ÀÎÇÑ ±ÝÀ¶ <b><font color="#CC0000">½Å¿ëºÒ·®ÀÚÀÇ Áõ°¡.</font></b>
<br>
2. ÀÎÀû, ¹°ÀûÀ¸·Î<b><font color="#CC0000"> ¸¹Àº °ü¸®ºñ¿ë ÇÊ¿ä </font></b>(¿ä±Ý°íÁö,
Ã¤±Ç°ü¸® µî). <br>
3. ÀÌµ¿Åë½Å »ç¿ëÀÚ°¡ »ç¿ë¿ä±ÝÀÇ ÀÎÁö¾øÀÌ ¹«ºÐº°ÇÑ »ç¿ëÀ¸·Î ÀÎÇÑ <b><font color="#CC0000">°ú¼Òºñ
ÃÊ·¡</font></b>. <br>
<font color="#0066CC"><br>
<b>ÀÌ·¯ÇÑ, ¹®Á¦·Î ÀÎÇØ ¼¼°èÀûÀ¸·Î ÀÌµ¿Åë½ÅÀº ¼±ºÒ¿ä±ÝÁ¦·Î ÀüÈ¯µÇ°í ÀÖ½À´Ï´Ù.</b></font> <br>
<font color="#990000">¡Ø 2002³â¿¡´Â IMT2000 ¼­ºñ½º°¡ ½ÃÀÛµÇ¸ç, ±×¶§´Â Áö±Ý
»ç¿ë¿ä±ÝÀÇ 3~4¹è¿¡ ÀÌ¸£´Â ¼­ºñ½º ¿ä±ÝÀÌ »ç¿ëµÉ °ÍÀÌ¶ó°í ¿¹ÃøÇÏ°í ÀÖ½À´Ï´Ù. Åë½Å½ÃÀåÀÌ °³¹æµÇ¾úÀ½¿¡µµ
ºÒ±¸ÇÏ°í, ¿Ü±¹ÀÇ °Å´ëÅë½Å±â¾÷µéÀÌ Áö±Ý ÀáÀáÇÑ°ÍÀº ¹Ù·Î ÀÌ IMT2000 ½Ã´ëÀ» ±â´Ù¸®¸ç, ¿ì¸®³ª¶ó Åë½Å½ÃÀåÀ»
³Ñº¸°í ÀÖ´Â °ÍÀÔ´Ï´Ù. </font></td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img09.gif" width="161" height="23"> <br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img10.gif" width="399" height="271"></td>
</tr>
</table>
<b><img src="http://www.copyi114.co.kr/nara/img04.gif" width="231" height="21"></b>
<table border="0" width="496" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="100%" height="20">: °³ÀÎ´ë¸®Á¡À¸·Î ±¸¼º<br>
°íÁ¤µÈ Áö¿ª ´ë¸®Á¡À» Å»ÇÇÇÏ¿© Áö¿ª¿¡ »ó°ü¾øÀÌ ¿òÁ÷ÀÌ´Â ´ë¸®Á¡À¸·Î ±¸¼º </td>
</tr>
<tr>
<td width="100%" height="20">
<table border="0" width="500" bordercolor="#FFFFFF" bordercolorlight="#FFFFFF" bordercolordark="#FFFFFF" bgcolor="#666666" cellspacing="1" cellpadding="6" align="center">
<tr>
<td width="20%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#A6A6A6">
¡¡</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">ÀÏ¹Ý´ë¸®Á¡ </font></b>
</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">KTF ¼±ºÒ´ë¸®Á¡
</font></b>
</td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center">
<p align="center"><font color="#000000"><b>¹ü&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
À§</b></font>
</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">Áö¿ªº°
ÇÑ°è</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">Áö¿ª
Á¦ÇÑ¾øÀÌ Àü±¹</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
¼³</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">¸ÅÀå
ÀÓ´ë (º¸Áõ±Ý + ½Ã¼³ºñ µî)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¸ÅÀå
ºÒÇÊ¿ä</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>´ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
º¸</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">´Ü¸»±â
±¸¸Å¸¦ À§ÇØ ´ãº¸¹° Á¦°ø</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">´ãº¸
¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>°ü
¸® À¯ Áö</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®
ÀÎ¿ø ¹× °ü¸®ºñ °ú´Ù ÁöÃâ</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>¼ö&nbsp;&nbsp;
¼ö&nbsp;&nbsp; ·á</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®¼ö¼ö·á</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">È¸¿øÀå·Á±Ý</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;
Àå&nbsp;&nbsp; ¼º</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">½ÃÀå¼ºÀÌ
¾ø´Ù. (Æ÷È­»óÅÂ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¹«ÇÑÇÑ
½ÃÀå¼º (ÃÊ±â½ÃÀå ¼±Á¡)</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>ÇØ&nbsp;&nbsp;
Áö&nbsp;&nbsp; À²</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°í°´
ÀÌµ¿ÀÌ ¸¹´Ù.<br>
<br>
(´ë¸®Á¡°£ °ø¿ë½Ã½ºÅÛ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">°í°´ÀÌµ¿
¾øÀ½.<br>
<br>
(Àü¿ë½Ã½ºÅÛ)</font></td>
</tr>
</table>
<table border="0" width="501" align="center">
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img05.gif" width="147" height="38">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img06.gif" width="95" height="18"></td>
</tr>
<tr>
<td width="100%" height="48">
<p> &nbsp;<font color="#008000">¢º </font><b>»ç¿ëÀÌ ºÒÆíÇÏ´Ù</b>
: Á¢¼Ó¹øÈ£¿Í&nbsp; Ä«µå¹øÈ£¸¦ ÀÔ·ÂÇÑ ÈÄ »ç¿ëÇÏ¿©¾ß ÅëÈ­°¡ ¿¬°áµË´Ï´Ù. <br>
&nbsp;<font color="#008000">¢º </font><b>½Ã¿ÜÀüÈ­</b> :
±â¾÷, È¸»ç¿¡¼­ ¸¹ÀÌ »ç¿ë (¾à 2Á¶¿ø)&nbsp; <font color="#0000FF">°³ÀÎÀº
1°¡±¸´ç ¾à 4,600¿ø »ç¿ë</font> <br>
&nbsp;<font color="#008000">¢º </font><b>±¹Á¦ÀüÈ­</b> :
±â¾÷, ¹«¿ªÈ¸»ç, ¿ÀÆÄ»óµîÀÌ ¸¹ÀÌ »ç¿ë (¾à1Á¶¿ø) <font color="#0000FF">°³ÀÎ
»ç¿ëÀº ¹ÌºñÇÏ´Ù.</font>
</td>
</tr>
<tr>
<td width="100%"></td>
</tr>
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img07.gif" width="180" height="37">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img08.gif" width="125" height="18">
</td>
</tr>
<tr valign="top">
<td width="100%" height="67">&nbsp; &nbsp;<font color="#008000">¢º
</font><b><font color="#FF0000">»ç¿ëÀÌ Æí¸®ÇÏ´Ù.</font></b><font color="#0000FF">
: </font><font color="#000000">ÈÄºÒ ÀüÈ­ »ç¿ë°ú µ¿ÀÏ</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º </font><b><font color="#FF0000">2,750¸¸¸íÀÌ
³Ñ´Â ´ëºÎºÐÀÇ °í°´ÀÌ °³ÀÎÀ¸·Î ±¸¼ºµÇ¾î ÀÖ½À´Ï´Ù.</font></b><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><font color="#FF0000"><b> ¼±ºÒ½ÃÀåÀº ¹«ÇÑÇÕ´Ï´Ù.</b></font><font color="#0000FF">
: </font><font color="#000000">2750¸¸ ÈÄºÒ¿ä±Ý »ç¿ë°í°´</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><b><font color="#FF0000"> 1°¡±¸´ç 11¸¸¿ø ÀÌ»ó »ç¿ëÇÕ´Ï´Ù.
</font><font color="#000000">(1999³â Åë°è)</font></b></td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img18.gif" width="86" height="18">
<table width="480" border="0" cellspacing="2" cellpadding="2" align="center">
<tr>
<td height="305">
<table border="0" width="480" bgcolor="#000000" cellspacing="1" cellpadding="3">
<tr>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ä±Ý»óÇ°</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ÀÏ
±âº»·á</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ù
±âº»·á</font></b></td>
<td width="20%" bgcolor="#CCCCCC" align="center" height="15" colspan="3"><b><font color="#666666">±¹³»ÅëÈ­·á&nbsp;<br>
(¿ø/10ÃÊ)</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ºñ
°í</font></b></td>
</tr>
<tr>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">Æò»ó</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">ÇÒÀÎ</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">½É¾ß</font></b></td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
Ç¥ÁØ</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>533
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>16,000
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>18
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
¿¡ÀÌ½º</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>616
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>18,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>13
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒÇÁ¸®
200</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>1,183
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>35,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>17
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><font color="#FF0000"><b>200ºÐ
¹«·á</b></font></td>
</tr>
</table>
<center>
</center>
<p align="left">&nbsp; ¢º ¿ä±Ý»óÇ° º¯°æ½Ã Àû¿ë½ÃÁ¡ : º¯°æ°ú µ¿½Ã¿¡ º¯°æ¿ä±ÝÀ¸·Î Á¤»êµÇ³ª,
¿ù 1È¸¿¡ ÇÑÇÔ. <br>
&nbsp; ¢º <font color="#008000"><b>ÇÒ ÀÎ ½Ã °£ <br>
&nbsp;&nbsp;&nbsp; </b></font><font color="#800000">1) ¼±ºÒÇ¥ÁØ,
¼±ºÒ¿¡ÀÌ½º ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"> <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~
6 ½Ã (½É¾ß) / 6 ~ 12 (ÇÒÀÎ) / 12 ~ 24 (Æò»ó) &nbsp;&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0
~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ) <br>
&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#800000">2)
¼±ºÒÇÁ¸® 200 ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"><br>
</font><font color="#008000"><b> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</b></font><font color="#000000">- ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~ 6 ½Ã
(½É¾ß) / 6 ~ 8, 21 ~ 24 (ÇÒÀÎ) / 8 ~ 21 (Æò»ó)<br>
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;
- °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0 ~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ)</font>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img12.gif" width="144" height="20"><br>
<table width="480" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img13.gif" width="499" height="359">
<table border="0" width="496" bgcolor="#990000" cellspacing="1" cellpadding="3" align="center">
<tr>
<td width="487" bgcolor="#FFFFFF"> &nbsp;<font color="#008080"><b>KTF</b></font><font color="#000000">(ÇÑ±¹Åë½ÅÇÁ¸®ÅÚ)ÀÇ
Åº»ý ´ç½ÃºÎÅÍ ¸ðµç ½Ã½ºÅÛÀ» ´ã´çÇØ ¿Â &nbsp;<b>´ë¿ìÁ¤º¸½Ã½ºÅÛ</b>Àº&nbsp; <br>
&nbsp;±âÁ¸ ÀüÀÚ»ó°Å·¡ÀÇ ±â¹ÝºÎÀç·Î ¿À´Â ÀûÀÚ¿äÀÎÀ»&nbsp;<b>ÁÖ½ÄÈ¸»ç ³ª¶óÄÞ</b>ÀÇ
³×Æ®¿öÅ© ¸¶ÄÉÆÃÀ» &nbsp;<br>
&nbsp;ÅëÇÏ¿© </font><font color="#FF0000"><b>ÃÖ´Ü±â°£ ÃÖ´ëÈ¸¿ø</b></font><font color="#000000">ÀÇ</font><font color="#FF0000"><b>&nbsp;±â¹ÝÈ®º¸</b></font><font color="#000000">¸¦</font><font color="#FF0000"><b>
¸ñÇ¥</b></font><font color="#000000">·Î&nbsp; <b>KTF, ´ë¿ìÁ¤º¸½Ã½ºÅÛ,&nbsp;ÁÖ½ÄÈ¸»ç
<br>
&nbsp;³ª¶óÄÞÀÇ</b> </font><b><font color="#FF0000">Àü·«Àû Á¦ÈÞ</font></b><font color="#000000">¸¦
ÅëÇÏ¿©&nbsp;<br>
</font> ¼±Áø±¹Çü ¼±ºÒ¿ä±ÝÁ¦µµ
<div align="center">- <b><font color="#008080">KTF</font><font color="#000000">
016</font></b> ¼±ºÒ¿ä±ÝÁ¦µµ -</div>
<div align="right"><font color="#000000">¸¦&nbsp; Åº»ý½ÃÄ×½À´Ï´Ù.</font><font color="#000080">
</font> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img17.gif" width="262" height="21"> <br>
<table width="499" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
E-mail : <a href="mailto:corud2@dreamwiz.com">corud2@dreamwiz.com
</tr>
</table>
</td>
<td width="42">&nbsp;</td>
</tr>
</table>
</td>
</tr>
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img03.gif" width="619" height="31"></td>
</tr>
<tr>
<td>
<div align="center"><img height=10 src="http://www.enativespeaker.com/image/139-1.gif"
width=10> <font size=2>±ÍÇÏÀÇ E-MAILÀº °ü·Ã °Ô½ÃÆÇÀ» ÅëÇØ ¾Ë°Ô µÇ¾ú½À´Ï´Ù. <br>
¿øÄ¡ ¾Ê¾Ò´ø ¸ÞÀÏÀÌ¶ó¸é </font><a
href="mailto:naracom2002@hitel.net?subject=¼ö½Å°ÅºÎ"><font size=2><b><font
color=#0000ff>¿©±â</font></b></font></a><font size=2>¸¦ ´­·¯ ¾Ë·Á ÁÖ½Ã¸é ¾ÕÀ¸·Î´Â ¹ß¼ÛµÇÁö ¾Êµµ·Ï ÇÏ°Ú½À´Ï´Ù.</font>
<font
size=2></font></div>
</td>
</tr>
</table>
<br>
</div>
</body>
</html>

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


From daemon@optimus.ietf.org  Tue Jan 22 09:58:50 2002
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 JAA22285
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:58:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA11466
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:58:54 -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 JAA09747;
	Tue, 22 Jan 2002 09:40:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA04193
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 19:36:49 -0500 (EST)
Received: from localhost ([218.55.130.23])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28968
	for <megaco@ietf.org>; Mon, 21 Jan 2002 19:36:44 -0500 (EST)
Message-Id: <200201220036.TAA28968@ietf.org>
Reply-To: naracom2002@naver.com
From: (ÁÖ)³ª¶óÄÞ<naracom2002@naver.com>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 22 Jan 2002 09:51:43 +0900
Subject: [Megaco] ¾È³çÇÏ¼¼¿ä[È«º¸]
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

<html>
<head>
<title>¼±ºÒ¿ä±ÝÁ¦ ÂüÁ¶ÀÚ·áÁý</title>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
<meta name="generator" content="Namo WebEditor v4.0">
<style type="text/css">
<!--
td { font-family: "µ¸¿ò", "µ¸¿òÃ¼"; font-size: 12px; color: #000000; line-height: 120%}
-->
</style>
</head>
<body text="black" link="blue" vlink="purple" alink="red">
<div>
<table width="620" border="0" cellspacing="2" cellpadding="2" align="center">
<tr bgcolor="#FFFFFF">
<td>
<p>¾È³çÇÏ¼¼¿ä ÀúÈ£ÁØÀÌ¿¡¿ä<br>
ÀßÁö³»°í °è½ÃÁ®?<br>
ÁÁÀºÁ¤º¸°¡ ÀÌ·¸°Ô ¸áº¸³» µå·Á¿ä<br>
ÇÑ¹ø ²Ä²ÄÈ÷ µûÁ®º¸¼¼¿ä ¾Æ¸¶ ¸¹Àºµµ¿òµÉ°Å¿¡¿ä<br>
¾Æ·¡¿¡ ÆÄÀÏÃ·ºÎÇßÀ¸´Ï ÀÐ¾îº¸½Ã°í¿ä<br>
±×·³ ¶Ç ¸áµå¸±²²¿ä<br>
</td>
</tr>
</table>
<table width="623" border="0" cellspacing="0" cellpadding="0" align="center">
<tr valign="top">
<td height="218" background="http://www.copyi114.co.kr/nara/img01.gif"> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<table width="575" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="396" height="68"> ¼±ºÒ¿ä±ÝÁ¦¼­ºñ½º´Â ¾î´À³¯ °©ÀÚ±â ³ª¿Â ¼­ºñ½º°¡ ¾Æ´Ñ, ¼±Áø ¿©·¯³ª¶ó¿¡¼­´Â
ÀÌ¹Ì ±âÁ¸¿¡ ½Ç½ÃÇÏ°í´Â ¼­ºñ½º·Î È¸»çÀÇ ÀÔÀå¿¡¼­´Â ¾ÈÁ¤ÀûÀÌ¸ç ¹Ì³³ °ÆÁ¤ÀÌ ¾ø´Â È¸¿øÀ¯Ä¡¸¦ ÇÏ¿© È¸»çÀÇ ¾ÈÁ¤¼ºÀ» ²ÒÇÒ
¼ö ÀÖÀ¸¸ç, ÀÌ¿¡µû¸¥ °í°´Àº °¢Á¾ ÇýÅÃ ¹× ¼ö´çÀ» ¹Þ´Â °ÍÀÔ´Ï´Ù.<br>
Áï ¼±ºÒÁ¦¿ä±ÝÁ¦¶õ ¸ÕÀú ÀÏÁ¤ºÎºÐÀÇ Åë½Å·á¸¦ ³»°í Ä³½¬¹é(Çö±Ý)°ú ±âÅ¸ ¼ö´çÀ» ¹Þ´Â ¿ä±ÝÃ¼°èÀÌ¸ç, ÀÌ·ÎÀÎÇÑ ÇýÅÃÀ» °í°´¿¡°Ô
Å©°Ô´Â 35%¿¡ ÇØ´çµÇ´Â ºÎºÐÀ» ´Ù½Ã Çö±ÝÀ¸·Î µ¹·Áµå¸®°í ÀÖ½À´Ï´Ù. </td>
<td width="179" height="68" valign="bottom">
<div align="center"><a href="http://www.copyi114.co.kr/nara/news.htm" target="_blank"><img src="http://www.copyi114.co.kr/nara/img16.gif" width="145" height="67" border="0"></a></div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td background="http://www.copyi114.co.kr/nara/img02.gif">
<table width="620" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="17">&nbsp;</td>
<td width="561"> <img src="http://www.copyi114.co.kr/nara/img14.gif" width="175" height="22"><br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img15.gif" width="461" height="91"><br>
1. ¾Ç¼º¿¬Ã¼ ¿ä±ÝÀ¸·Î ÀÎÇÑ ±ÝÀ¶ <b><font color="#CC0000">½Å¿ëºÒ·®ÀÚÀÇ Áõ°¡.</font></b>
<br>
2. ÀÎÀû, ¹°ÀûÀ¸·Î<b><font color="#CC0000"> ¸¹Àº °ü¸®ºñ¿ë ÇÊ¿ä </font></b>(¿ä±Ý°íÁö,
Ã¤±Ç°ü¸® µî). <br>
3. ÀÌµ¿Åë½Å »ç¿ëÀÚ°¡ »ç¿ë¿ä±ÝÀÇ ÀÎÁö¾øÀÌ ¹«ºÐº°ÇÑ »ç¿ëÀ¸·Î ÀÎÇÑ <b><font color="#CC0000">°ú¼Òºñ
ÃÊ·¡</font></b>. <br>
<font color="#0066CC"><br>
<b>ÀÌ·¯ÇÑ, ¹®Á¦·Î ÀÎÇØ ¼¼°èÀûÀ¸·Î ÀÌµ¿Åë½ÅÀº ¼±ºÒ¿ä±ÝÁ¦·Î ÀüÈ¯µÇ°í ÀÖ½À´Ï´Ù.</b></font> <br>
<font color="#990000">¡Ø 2002³â¿¡´Â IMT2000 ¼­ºñ½º°¡ ½ÃÀÛµÇ¸ç, ±×¶§´Â Áö±Ý
»ç¿ë¿ä±ÝÀÇ 3~4¹è¿¡ ÀÌ¸£´Â ¼­ºñ½º ¿ä±ÝÀÌ »ç¿ëµÉ °ÍÀÌ¶ó°í ¿¹ÃøÇÏ°í ÀÖ½À´Ï´Ù. Åë½Å½ÃÀåÀÌ °³¹æµÇ¾úÀ½¿¡µµ
ºÒ±¸ÇÏ°í, ¿Ü±¹ÀÇ °Å´ëÅë½Å±â¾÷µéÀÌ Áö±Ý ÀáÀáÇÑ°ÍÀº ¹Ù·Î ÀÌ IMT2000 ½Ã´ëÀ» ±â´Ù¸®¸ç, ¿ì¸®³ª¶ó Åë½Å½ÃÀåÀ»
³Ñº¸°í ÀÖ´Â °ÍÀÔ´Ï´Ù. </font></td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img09.gif" width="161" height="23"> <br>
<table width="493" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img10.gif" width="399" height="271"></td>
</tr>
</table>
<b><img src="http://www.copyi114.co.kr/nara/img04.gif" width="231" height="21"></b>
<table border="0" width="496" cellspacing="0" cellpadding="0" align="center">
<tr>
<td width="100%" height="20">: °³ÀÎ´ë¸®Á¡À¸·Î ±¸¼º<br>
°íÁ¤µÈ Áö¿ª ´ë¸®Á¡À» Å»ÇÇÇÏ¿© Áö¿ª¿¡ »ó°ü¾øÀÌ ¿òÁ÷ÀÌ´Â ´ë¸®Á¡À¸·Î ±¸¼º </td>
</tr>
<tr>
<td width="100%" height="20">
<table border="0" width="500" bordercolor="#FFFFFF" bordercolorlight="#FFFFFF" bordercolordark="#FFFFFF" bgcolor="#666666" cellspacing="1" cellpadding="6" align="center">
<tr>
<td width="20%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#A6A6A6">
¡¡</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">ÀÏ¹Ý´ë¸®Á¡ </font></b>
</td>
<td width="40%" height="30" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">
<p align="center"><b><font color="#003366">KTF ¼±ºÒ´ë¸®Á¡
</font></b>
</td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center">
<p align="center"><font color="#000000"><b>¹ü&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
À§</b></font>
</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">Áö¿ªº°
ÇÑ°è</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">Áö¿ª
Á¦ÇÑ¾øÀÌ Àü±¹</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
¼³</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">¸ÅÀå
ÀÓ´ë (º¸Áõ±Ý + ½Ã¼³ºñ µî)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¸ÅÀå
ºÒÇÊ¿ä</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>´ã&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
º¸</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">´Ü¸»±â
±¸¸Å¸¦ À§ÇØ ´ãº¸¹° Á¦°ø</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">´ãº¸
¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>°ü
¸® À¯ Áö</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®
ÀÎ¿ø ¹× °ü¸®ºñ °ú´Ù ÁöÃâ</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¾øÀ½</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>¼ö&nbsp;&nbsp;
¼ö&nbsp;&nbsp; ·á</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°ü¸®¼ö¼ö·á</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">È¸¿øÀå·Á±Ý</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>½Ã&nbsp;&nbsp;
Àå&nbsp;&nbsp; ¼º</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">½ÃÀå¼ºÀÌ
¾ø´Ù. (Æ÷È­»óÅÂ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">¹«ÇÑÇÑ
½ÃÀå¼º (ÃÊ±â½ÃÀå ¼±Á¡)</font></td>
</tr>
<tr>
<td width="20%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#F6F6F6" align="center"><font color="#000000"><b>ÇØ&nbsp;&nbsp;
Áö&nbsp;&nbsp; À²</b></font></td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF">°í°´
ÀÌµ¿ÀÌ ¸¹´Ù.<br>
<br>
(´ë¸®Á¡°£ °ø¿ë½Ã½ºÅÛ)</td>
<td width="40%" height="25" bordercolorlight="#008000" bordercolordark="#C9F5DD" bgcolor="#FFFFFF"><font color="#FF0000">°í°´ÀÌµ¿
¾øÀ½.<br>
<br>
(Àü¿ë½Ã½ºÅÛ)</font></td>
</tr>
</table>
<table border="0" width="501" align="center">
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img05.gif" width="147" height="38">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img06.gif" width="95" height="18"></td>
</tr>
<tr>
<td width="100%" height="48">
<p> &nbsp;<font color="#008000">¢º </font><b>»ç¿ëÀÌ ºÒÆíÇÏ´Ù</b>
: Á¢¼Ó¹øÈ£¿Í&nbsp; Ä«µå¹øÈ£¸¦ ÀÔ·ÂÇÑ ÈÄ »ç¿ëÇÏ¿©¾ß ÅëÈ­°¡ ¿¬°áµË´Ï´Ù. <br>
&nbsp;<font color="#008000">¢º </font><b>½Ã¿ÜÀüÈ­</b> :
±â¾÷, È¸»ç¿¡¼­ ¸¹ÀÌ »ç¿ë (¾à 2Á¶¿ø)&nbsp; <font color="#0000FF">°³ÀÎÀº
1°¡±¸´ç ¾à 4,600¿ø »ç¿ë</font> <br>
&nbsp;<font color="#008000">¢º </font><b>±¹Á¦ÀüÈ­</b> :
±â¾÷, ¹«¿ªÈ¸»ç, ¿ÀÆÄ»óµîÀÌ ¸¹ÀÌ »ç¿ë (¾à1Á¶¿ø) <font color="#0000FF">°³ÀÎ
»ç¿ëÀº ¹ÌºñÇÏ´Ù.</font>
</td>
</tr>
<tr>
<td width="100%"></td>
</tr>
<tr>
<td width="100%"><img border="0" src="http://www.copyi114.co.kr/nara/img07.gif" width="180" height="37">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<img border="0" src="http://www.copyi114.co.kr/nara/img08.gif" width="125" height="18">
</td>
</tr>
<tr valign="top">
<td width="100%" height="67">&nbsp; &nbsp;<font color="#008000">¢º
</font><b><font color="#FF0000">»ç¿ëÀÌ Æí¸®ÇÏ´Ù.</font></b><font color="#0000FF">
: </font><font color="#000000">ÈÄºÒ ÀüÈ­ »ç¿ë°ú µ¿ÀÏ</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º </font><b><font color="#FF0000">2,750¸¸¸íÀÌ
³Ñ´Â ´ëºÎºÐÀÇ °í°´ÀÌ °³ÀÎÀ¸·Î ±¸¼ºµÇ¾î ÀÖ½À´Ï´Ù.</font></b><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><font color="#FF0000"><b> ¼±ºÒ½ÃÀåÀº ¹«ÇÑÇÕ´Ï´Ù.</b></font><font color="#0000FF">
: </font><font color="#000000">2750¸¸ ÈÄºÒ¿ä±Ý »ç¿ë°í°´</font><font color="#0000FF">
<br>
&nbsp;</font><font color="#008000">¢º</font><font color="#0000FF">
</font><b><font color="#FF0000"> 1°¡±¸´ç 11¸¸¿ø ÀÌ»ó »ç¿ëÇÕ´Ï´Ù.
</font><font color="#000000">(1999³â Åë°è)</font></b></td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img18.gif" width="86" height="18">
<table width="480" border="0" cellspacing="2" cellpadding="2" align="center">
<tr>
<td height="305">
<table border="0" width="480" bgcolor="#000000" cellspacing="1" cellpadding="3">
<tr>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ä±Ý»óÇ°</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ÀÏ
±âº»·á</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">¿ù
±âº»·á</font></b></td>
<td width="20%" bgcolor="#CCCCCC" align="center" height="15" colspan="3"><b><font color="#666666">±¹³»ÅëÈ­·á&nbsp;<br>
(¿ø/10ÃÊ)</font></b></td>
<td width="100" bgcolor="#CCCCCC" align="center" height="30" rowspan="2"><b><font color="#666666">ºñ
°í</font></b></td>
</tr>
<tr>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">Æò»ó</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">ÇÒÀÎ</font></b></td>
<td width="50" bgcolor="#CCCCCC" align="center"><b><font color="#666666">½É¾ß</font></b></td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
Ç¥ÁØ</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>533
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>16,000
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>18
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒ
¿¡ÀÌ½º</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>616
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>18,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>15
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>13
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center">¡¡</td>
</tr>
<tr>
<td width="100" bgcolor="#F7F7F7" height="30" align="center"><b><font color="#000000">¼±ºÒÇÁ¸®
200</font></b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>1,183
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><b>35,500
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>17
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>14
¿ø</b></td>
<td width="50" bgcolor="#FFFFFF" align="center"><b>10
¿ø</b></td>
<td width="100" bgcolor="#FFFFFF" height="30" align="center"><font color="#FF0000"><b>200ºÐ
¹«·á</b></font></td>
</tr>
</table>
<center>
</center>
<p align="left">&nbsp; ¢º ¿ä±Ý»óÇ° º¯°æ½Ã Àû¿ë½ÃÁ¡ : º¯°æ°ú µ¿½Ã¿¡ º¯°æ¿ä±ÝÀ¸·Î Á¤»êµÇ³ª,
¿ù 1È¸¿¡ ÇÑÇÔ. <br>
&nbsp; ¢º <font color="#008000"><b>ÇÒ ÀÎ ½Ã °£ <br>
&nbsp;&nbsp;&nbsp; </b></font><font color="#800000">1) ¼±ºÒÇ¥ÁØ,
¼±ºÒ¿¡ÀÌ½º ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"> <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~
6 ½Ã (½É¾ß) / 6 ~ 12 (ÇÒÀÎ) / 12 ~ 24 (Æò»ó) &nbsp;&nbsp;&nbsp;&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0
~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ) <br>
&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#800000">2)
¼±ºÒÇÁ¸® 200 ¿ä±ÝÀÇ °æ¿ì</font><font color="#000000"><br>
</font><font color="#008000"><b> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</b></font><font color="#000000">- ÆòÀÏ (Åä¿äÀÏ Æ÷ÇÔ) : 0 ~ 6 ½Ã
(½É¾ß) / 6 ~ 8, 21 ~ 24 (ÇÒÀÎ) / 8 ~ 21 (Æò»ó)<br>
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;
- °øÈÞÀÏ (ÀÏ¿äÀÏ Æ÷ÇÔ) : 0 ~ 6½Ã (½É¾ß) / 6 ~ 24 (ÇÒÀÎ)</font>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img12.gif" width="144" height="20"><br>
<table width="480" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img13.gif" width="499" height="359">
<table border="0" width="496" bgcolor="#990000" cellspacing="1" cellpadding="3" align="center">
<tr>
<td width="487" bgcolor="#FFFFFF"> &nbsp;<font color="#008080"><b>KTF</b></font><font color="#000000">(ÇÑ±¹Åë½ÅÇÁ¸®ÅÚ)ÀÇ
Åº»ý ´ç½ÃºÎÅÍ ¸ðµç ½Ã½ºÅÛÀ» ´ã´çÇØ ¿Â &nbsp;<b>´ë¿ìÁ¤º¸½Ã½ºÅÛ</b>Àº&nbsp; <br>
&nbsp;±âÁ¸ ÀüÀÚ»ó°Å·¡ÀÇ ±â¹ÝºÎÀç·Î ¿À´Â ÀûÀÚ¿äÀÎÀ»&nbsp;<b>ÁÖ½ÄÈ¸»ç ³ª¶óÄÞ</b>ÀÇ
³×Æ®¿öÅ© ¸¶ÄÉÆÃÀ» &nbsp;<br>
&nbsp;ÅëÇÏ¿© </font><font color="#FF0000"><b>ÃÖ´Ü±â°£ ÃÖ´ëÈ¸¿ø</b></font><font color="#000000">ÀÇ</font><font color="#FF0000"><b>&nbsp;±â¹ÝÈ®º¸</b></font><font color="#000000">¸¦</font><font color="#FF0000"><b>
¸ñÇ¥</b></font><font color="#000000">·Î&nbsp; <b>KTF, ´ë¿ìÁ¤º¸½Ã½ºÅÛ,&nbsp;ÁÖ½ÄÈ¸»ç
<br>
&nbsp;³ª¶óÄÞÀÇ</b> </font><b><font color="#FF0000">Àü·«Àû Á¦ÈÞ</font></b><font color="#000000">¸¦
ÅëÇÏ¿©&nbsp;<br>
</font> ¼±Áø±¹Çü ¼±ºÒ¿ä±ÝÁ¦µµ
<div align="center">- <b><font color="#008080">KTF</font><font color="#000000">
016</font></b> ¼±ºÒ¿ä±ÝÁ¦µµ -</div>
<div align="right"><font color="#000000">¸¦&nbsp; Åº»ý½ÃÄ×½À´Ï´Ù.</font><font color="#000080">
</font> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
<img src="http://www.copyi114.co.kr/nara/img17.gif" width="262" height="21"> <br>
<table width="499" border="0" cellspacing="0" cellpadding="0" align="center">
<tr>
E-mail : <a href="mailto:corud2@dreamwiz.com">corud2@dreamwiz.com
</tr>
</table>
</td>
<td width="42">&nbsp;</td>
</tr>
</table>
</td>
</tr>
<tr>
<td><img src="http://www.copyi114.co.kr/nara/img03.gif" width="619" height="31"></td>
</tr>
<tr>
<td>
<div align="center"><img height=10 src="http://www.enativespeaker.com/image/139-1.gif"
width=10> <font size=2>±ÍÇÏÀÇ E-MAILÀº °ü·Ã °Ô½ÃÆÇÀ» ÅëÇØ ¾Ë°Ô µÇ¾ú½À´Ï´Ù. <br>
¿øÄ¡ ¾Ê¾Ò´ø ¸ÞÀÏÀÌ¶ó¸é </font><a
href="mailto:naracom2002@hitel.net?subject=¼ö½Å°ÅºÎ"><font size=2><b><font
color=#0000ff>¿©±â</font></b></font></a><font size=2>¸¦ ´­·¯ ¾Ë·Á ÁÖ½Ã¸é ¾ÕÀ¸·Î´Â ¹ß¼ÛµÇÁö ¾Êµµ·Ï ÇÏ°Ú½À´Ï´Ù.</font>
<font
size=2></font></div>
</td>
</tr>
</table>
<br>
</div>
</body>
</html>

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



From megaco-admin@ietf.org  Tue Jan 22 10:00:12 2002
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 KAA23030
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:00:08 -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 JAA09807;
	Tue, 22 Jan 2002 09:40:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA08984
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:45 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01653
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:39 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA00652;
	Tue, 22 Jan 2002 14:19:19 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13822;
	Tue, 22 Jan 2002 14:20:40 +1100 (EST)
Message-ID: <3C4B8175.D541B0A3@ericsson.com.au>
Date: Mon, 21 Jan 2002 13:48:21 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Open Issue 2: Replies to requests from failed MGC
References: <3B799EBD.F54C2B88@lucent.com> <3B80A153.4419D58E@ericsson.com> <3B812262.C78022C2@lucent.com> <3B821552.139ECF29@ericsson.com> <3C487749.33ED2EE7@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

I'm in a favour of a simple rule. However if you adopt the rule that the
replies ALWAYS go the addr/port from which the request came then you
need you should make a note that the failed MG probably will never
receive the replies, in which case sending them there is redundant.

If the new MGC doesn't have state of the transaction it will simply
discard the transaction responses. The MGC that doesn't have state it
will need some mechanism to clear calls or audit to find out state. From
a security point of view its probably not a problem because it will just
discard the message response.

An MGC that does have state will use the transaction response and
continue using the MG. As state is shared the secondary MGC should know
that the primary went down and will know to accept the transaction
responses.

The MG will know to send the response to the new secondary MGC because
it received an authenticated command from the primary MGC. Again I'm not
sure that there's a security problem.

THE underlying issue is your question 1: should the protocol use a
simple rule that replies ALWAYS go the the source from which the request
came, or have exceptions? From the above I think there's an exception.

Regards, Christian

Terry L Anderson wrote:
> 
> Here's a second open issue.  There were only 5 messages in this thread back in
> August but then it died without a resolution.  Yet it seems IMHO an important issue
> on which the current H.248 is inconsistent.
> 
> The issue is whether replies to requests from a failed MGC are sent to a secondary
> MGC or are sent to the failed MGC (in spite of likely failure) and whether replies
> go to the original MGC after a handoff or be sent to the new MGC.  See the original
> analysis of the current statements in H.248 near the bottom.  The conflict is
> between 9.1 and statements in D.1 and D.1.5 (that apply only to IP) with that
> statement in 11.5.
> 
> As explained below, the email archives show a previous discussion of the issue in
> Jan 2000 with the final statements suggesting 11.5 be changed and Tom seems to come
> to that conclusion in his reply below.
> 
> Admitted the rule that the reply should be sent to the MGC that is believed to have
> failed makes little sense, but I think that that real issues are:
> 
> 1. should the protocol use a simple rule that replies ALWAYS go the the addr/port
> from which the request came, or have exceptions?
> 
> 2. should the protocol assume that a Secondary MGC shares state with the Primary? or
> should that only be one possible design.
> 
> I argued for the simple rule to apply even to this case, since if Secondary and
> Primary do NOT share state, sending the reply to the secondary will do no good (it
> knows nothing about the request).
> 
> If we want to make the operation of pair (Primary and Secondary) that share state
> more efficient, perhaps we need to negotiate between the two cases at Registration.
> 
> To summarize:
> Option #1:
>     Change 11.5 to agree with 9.1 and D.1 and the "simple rule" (I actually proposed
> text in my original message near the bottom).
> 
> Option #2:
>     Introduce a way for MGC to specify in Registration response, which of two
> options to follow, (1) send all responses to sender, (2) send all responses to
> active MGC (after handoff or failover).  MGC would chose based on whether it shared
> state with its Secondary.  Change 11.5 (and 9.1, D.1) to use this information to
> choose between two behaviors on where to send responses.  This seems like a
> significant change to try to introduce into V1 through the IG.  If option #2 is
> preferred, perhaps we need to do Option #1 in V1 and introduce Option #2 in H.248v2.
> 
> Tom Taylor wrote:
> 
> > When we did that section 11.5 stuff, it was certainly in my mind that (assuming shared MGC state), the new MGC would take over from
> > the old at a certain point, including closing out old transactions.  I can see the catch: this makes message validation at the MG really
> > messy.  If there was no shared state, the old transactions would be cleared by resending them to the new MGC.  Maybe this is the
> > appropriate procedure in all cases and 11.5 should be changed.
> >
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > Please see comments below [CHG].
> >
> > Christian
> >
> > Terry L Anderson wrote:
> > >
> > > Christian Groves wrote:
> > >
> > > > G'Day Terry,
> > > >
> > > > A few points on this.
> > > >
> > > > o I think D.1.5 needs to be updated ie.
> > > >
> > > > "In order to account for the possibility of an undetected or in-progress
> > > > "failover", we modify the classic algorithm so that if the Media Gateway
> > > > receives a valid ServiceChange message announcing a failover".
> > > >
> > > > Shouldn't this state "handoff" instead of "failover" as handoff is sent
> > > > from the MGC to the MG?
> > >
> > > You are right.  Hadn't noticed this, but MG should never receive ServiceChange
> > > message announcing a failover".
> > >
> > > > o Given that the MGCs are maintaining state in a "handoff" situation I
> > > > find it strange that replies from the MG are sent to the "old MGC"
> > > > whilst the "new MGC" must send replies to the MG. If the "old MGC" has
> > > > died and can't actually receive the command reply how will the "new MGC"
> > > > know that a command has been executed?
> > >
> > > I thought we had agreed that replies would always be sent to source address of
> > > request (which would be "old MGC" in this case):
> > > - to keep simple consistent rule
> > > - because entity at another addr may not know about request
> > > - match rule for handoff
> >
> > [CHG] I'd like to keep things simple also but if simple means broken
> > then I'd rather something a little more complicated. I'm confused about
> > your comment on handoff because the text was talking about the handoff
> > case. Also the comment about the entity at another addr not knowing
> > about the request this is also true for the new entity sending a reply.
> > So we have an inconsistent rule, the new MGC can't know to receive a
> > reply but can know to send one.
> >
> > >
> > > This means of course that the in the event of an MGC failure, these
> > > transactions will fail (replies sent to old MGC will not be processed), but
> > > unless the new MGC shares transaction state with old the replies will be
> > > ignored anyway if sent to new MGC.  If these transactions fail, the new MGC
> > > should (through shared state or audit) should issue new transactions to
> > > accomplish the still needed task and these will succeed.
> >
> > [CHG] I think the real question we need to ask is do the MGCs share
> > state? If so then the new MGC shall be able to operate as the old one.
> > If not then the new MGC can't know anything. ie. it can't send or
> > receive replys from previous commands.
> >
> > >
> > > For handoff the rule works since the old MGC can send/accept replies for
> > > outstanding transactions before going out of service.
> >
> > [CHG] Yes but what happen if the MG sends a reply to a command received
> > before the service change after the acceptance of the service change?
> > The MGC may have already gone out of service.
> >
> > >
> > > Basically there are two stategies:
> > > 1) tie transactions to a specific MGC: all pending transactions between MG and
> > > old MGC (either direction) will complete with old MGC during a handoff and
> > > will fail during a failover.  MG may reissue new transactions with same
> > > actions for those that fail after registration with new MGC.  MGC may reissue
> > > new transactions with same actions for those that fail after determining they
> > > are still needed by shared state or audit.
> > >
> > > 2) tie transactions to collections of MGCs (primary and all secondaries): all
> > > pending transactions between MG and old MGC will be continued (if possible)
> > > with new MGC.  MG should send replies to new MGC and expect replies to its
> > > transactions from new MGC.
> > >
> > > Some current statements in H.248 seem to assume the first and others the
> > > second.  I dislike #2 because:
> > > a) it will only work if MGCs share transaction state.  Elsewhere H.248 allows
> > > but does not require MGCs to share state with its secondaries.  Although, I
> > > admit that all that will happen if they do not share state is that all pending
> > > transactions will fail, which is the same that will happen in #1 for
> > > failover.  #1, though allows pending transactions during handoff to succeed.
> > >
> > > b) it breaks our "all replies to source address" rule.  It requires that in
> > > this case we send replies to an address in the ServiceChange message or in
> > > provisioned secondary MGC list.  I believe that this breaks one of the hacks
> > > for working through NAT devices.
> > >
> > > #1 seemed to be the conclusion of all mail threads I found (3 or 4 since Jan
> > > 2000).
> >
> > [CHG] Perhaps what we need is option of both and describe the behaviour.
> > As I mentioned above it comes down to whether you support state sharing
> > or not.
> > I'm not particularly concerned about a general rule for NATs because its
> > a transport specific behaviour see my comment below.
> >
> > >
> > > > o Annex D is purely about IP transports, so I don't think we should take
> > > > it as a general guide to how the protocol works. We put transports in
> > > > Annexes so that we could have a common core protocol and use the Annexes
> > > > to tailor some procedures.
> > >
> > > I agree.  Perhaps, details describing this issue should be removed, allowing
> > > such to be stated in 7.2.8 and 11.5.  This also helps ensure that we treat TCP
> > > equally with UDP.  D.1.5 only applies to UDP but issues of where replies go
> > > should be same for both.
> > >
> > > > o Perhaps an exception to the rule is necessary. If you receive a
> > > > command from a valid, secure MGC telling you to you a new address then
> > > > what is the problem in using it?
> > >
> > > Of course you will use it for new transactions, the question is whether that
> > > new MGC can handle pending transactions (send or receive replies).
> > >
> > > > Cheers, Christian
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I hate to open this again.  I believe we have settled this but the IG
> > > > > does not seem to have a change.
> > > > >
> > > > > The issue is whether replies to requests from a failed MGC are sent to a
> > > > > secondary MGC or are sent to the failed MGC (in spite of likely
> > > > > failure).
> > > > >
> > > > > We have a number of statements (section 9.1, D.1, D.1.5) all of which
> > > > > say that replies must be sent to the address and port from which the
> > > > > request was sent.  I believe we are in agreement that this is a rule
> > > > > without exception.  But 11.5 pretty clearly contradicts this.
> > > > >     "Accordingly, commands in progress continue, TRANSACTION REPLIES ARE
> > > > > SENT TO THE NEW MGC (after a new control association is established),
> > > > > and the ..."
> > > > >
> > > > > The context does NOT sound like these replies are only replies to new
> > > > > requests (which would hardly need to be stated.  And so this seems to
> > > > > contradict the general principle or suggest an exception to the
> > > > > otherwise simple rule.  However, D.1.5 seems to be talking about exactly
> > > > > this same case and follows the general rule.
> > > > >
> > > > > This discrepancy appears to have been noticed as early as Jan 20, 2000
> > > > > by Shalini Philip and Brian Rosen's reply of Jan 21, 2000 suggested 11.5
> > > > > needed to be changed.  I see the same point raised a few more times in
> > > > > the archives.  And replies always seem to support the general rule.  I
> > > > > find no support for the 11.5 wording.  But I can find no correction to
> > > > > this in the IG (if its there could someone point out the item number).
> > > > >
> > > > > Are we in agreement that this wording is in error and should be changed
> > > > > to something like:
> > > > >
> > > > > "Accordingly, commands in progress continue and replies to all commands
> > > > > from the original MGC must be sent to source address and port from which
> > > > > they were sent (even if they are likely to fail). The MG should expect
> > > > > outstanding transaction replies from the new MGC."
> > > > >
> > > > > Do we still agree with the last sentence (from the last clause of the
> > > > > original)?  Should the new MGC (if it can) reply to transactions sent to
> > > > > the failed MGC (this, of course, will  happen only if the MGCs had
> > > > > shared state)?  These replies can still be sent to the addr/port from
> > > > > which they came (the MG) and so do not violate the general rule, but
> > > > > this does seem to fit with the general philosophy (which we would be
> > > > > changing) that the new MGC is taking over role of original even for
> > > > > pending transactions.
> > > > >
> > > > > --
> > > > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > > > ------------------------------------------------------------
> > > > > Terry L Anderson             mailto:tla@lucent.com
> > > > > Tel:908.582.7013   Fax:908.582.6729
> > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > >
> > > --
> > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla



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


From daemon@optimus.ietf.org  Tue Jan 22 10:00:13 2002
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 KAA23082
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:00:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11657
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 10:00: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 JAA09807;
	Tue, 22 Jan 2002 09:40:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA08984
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:20:45 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01653
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:39 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA00652;
	Tue, 22 Jan 2002 14:19:19 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13822;
	Tue, 22 Jan 2002 14:20:40 +1100 (EST)
Message-ID: <3C4B8175.D541B0A3@ericsson.com.au>
Date: Mon, 21 Jan 2002 13:48:21 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Open Issue 2: Replies to requests from failed MGC
References: <3B799EBD.F54C2B88@lucent.com> <3B80A153.4419D58E@ericsson.com> <3B812262.C78022C2@lucent.com> <3B821552.139ECF29@ericsson.com> <3C487749.33ED2EE7@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

I'm in a favour of a simple rule. However if you adopt the rule that the
replies ALWAYS go the addr/port from which the request came then you
need you should make a note that the failed MG probably will never
receive the replies, in which case sending them there is redundant.

If the new MGC doesn't have state of the transaction it will simply
discard the transaction responses. The MGC that doesn't have state it
will need some mechanism to clear calls or audit to find out state. From
a security point of view its probably not a problem because it will just
discard the message response.

An MGC that does have state will use the transaction response and
continue using the MG. As state is shared the secondary MGC should know
that the primary went down and will know to accept the transaction
responses.

The MG will know to send the response to the new secondary MGC because
it received an authenticated command from the primary MGC. Again I'm not
sure that there's a security problem.

THE underlying issue is your question 1: should the protocol use a
simple rule that replies ALWAYS go the the source from which the request
came, or have exceptions? From the above I think there's an exception.

Regards, Christian

Terry L Anderson wrote:
> 
> Here's a second open issue.  There were only 5 messages in this thread back in
> August but then it died without a resolution.  Yet it seems IMHO an important issue
> on which the current H.248 is inconsistent.
> 
> The issue is whether replies to requests from a failed MGC are sent to a secondary
> MGC or are sent to the failed MGC (in spite of likely failure) and whether replies
> go to the original MGC after a handoff or be sent to the new MGC.  See the original
> analysis of the current statements in H.248 near the bottom.  The conflict is
> between 9.1 and statements in D.1 and D.1.5 (that apply only to IP) with that
> statement in 11.5.
> 
> As explained below, the email archives show a previous discussion of the issue in
> Jan 2000 with the final statements suggesting 11.5 be changed and Tom seems to come
> to that conclusion in his reply below.
> 
> Admitted the rule that the reply should be sent to the MGC that is believed to have
> failed makes little sense, but I think that that real issues are:
> 
> 1. should the protocol use a simple rule that replies ALWAYS go the the addr/port
> from which the request came, or have exceptions?
> 
> 2. should the protocol assume that a Secondary MGC shares state with the Primary? or
> should that only be one possible design.
> 
> I argued for the simple rule to apply even to this case, since if Secondary and
> Primary do NOT share state, sending the reply to the secondary will do no good (it
> knows nothing about the request).
> 
> If we want to make the operation of pair (Primary and Secondary) that share state
> more efficient, perhaps we need to negotiate between the two cases at Registration.
> 
> To summarize:
> Option #1:
>     Change 11.5 to agree with 9.1 and D.1 and the "simple rule" (I actually proposed
> text in my original message near the bottom).
> 
> Option #2:
>     Introduce a way for MGC to specify in Registration response, which of two
> options to follow, (1) send all responses to sender, (2) send all responses to
> active MGC (after handoff or failover).  MGC would chose based on whether it shared
> state with its Secondary.  Change 11.5 (and 9.1, D.1) to use this information to
> choose between two behaviors on where to send responses.  This seems like a
> significant change to try to introduce into V1 through the IG.  If option #2 is
> preferred, perhaps we need to do Option #1 in V1 and introduce Option #2 in H.248v2.
> 
> Tom Taylor wrote:
> 
> > When we did that section 11.5 stuff, it was certainly in my mind that (assuming shared MGC state), the new MGC would take over from
> > the old at a certain point, including closing out old transactions.  I can see the catch: this makes message validation at the MG really
> > messy.  If there was no shared state, the old transactions would be cleared by resending them to the new MGC.  Maybe this is the
> > appropriate procedure in all cases and 11.5 should be changed.
> >
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > Please see comments below [CHG].
> >
> > Christian
> >
> > Terry L Anderson wrote:
> > >
> > > Christian Groves wrote:
> > >
> > > > G'Day Terry,
> > > >
> > > > A few points on this.
> > > >
> > > > o I think D.1.5 needs to be updated ie.
> > > >
> > > > "In order to account for the possibility of an undetected or in-progress
> > > > "failover", we modify the classic algorithm so that if the Media Gateway
> > > > receives a valid ServiceChange message announcing a failover".
> > > >
> > > > Shouldn't this state "handoff" instead of "failover" as handoff is sent
> > > > from the MGC to the MG?
> > >
> > > You are right.  Hadn't noticed this, but MG should never receive ServiceChange
> > > message announcing a failover".
> > >
> > > > o Given that the MGCs are maintaining state in a "handoff" situation I
> > > > find it strange that replies from the MG are sent to the "old MGC"
> > > > whilst the "new MGC" must send replies to the MG. If the "old MGC" has
> > > > died and can't actually receive the command reply how will the "new MGC"
> > > > know that a command has been executed?
> > >
> > > I thought we had agreed that replies would always be sent to source address of
> > > request (which would be "old MGC" in this case):
> > > - to keep simple consistent rule
> > > - because entity at another addr may not know about request
> > > - match rule for handoff
> >
> > [CHG] I'd like to keep things simple also but if simple means broken
> > then I'd rather something a little more complicated. I'm confused about
> > your comment on handoff because the text was talking about the handoff
> > case. Also the comment about the entity at another addr not knowing
> > about the request this is also true for the new entity sending a reply.
> > So we have an inconsistent rule, the new MGC can't know to receive a
> > reply but can know to send one.
> >
> > >
> > > This means of course that the in the event of an MGC failure, these
> > > transactions will fail (replies sent to old MGC will not be processed), but
> > > unless the new MGC shares transaction state with old the replies will be
> > > ignored anyway if sent to new MGC.  If these transactions fail, the new MGC
> > > should (through shared state or audit) should issue new transactions to
> > > accomplish the still needed task and these will succeed.
> >
> > [CHG] I think the real question we need to ask is do the MGCs share
> > state? If so then the new MGC shall be able to operate as the old one.
> > If not then the new MGC can't know anything. ie. it can't send or
> > receive replys from previous commands.
> >
> > >
> > > For handoff the rule works since the old MGC can send/accept replies for
> > > outstanding transactions before going out of service.
> >
> > [CHG] Yes but what happen if the MG sends a reply to a command received
> > before the service change after the acceptance of the service change?
> > The MGC may have already gone out of service.
> >
> > >
> > > Basically there are two stategies:
> > > 1) tie transactions to a specific MGC: all pending transactions between MG and
> > > old MGC (either direction) will complete with old MGC during a handoff and
> > > will fail during a failover.  MG may reissue new transactions with same
> > > actions for those that fail after registration with new MGC.  MGC may reissue
> > > new transactions with same actions for those that fail after determining they
> > > are still needed by shared state or audit.
> > >
> > > 2) tie transactions to collections of MGCs (primary and all secondaries): all
> > > pending transactions between MG and old MGC will be continued (if possible)
> > > with new MGC.  MG should send replies to new MGC and expect replies to its
> > > transactions from new MGC.
> > >
> > > Some current statements in H.248 seem to assume the first and others the
> > > second.  I dislike #2 because:
> > > a) it will only work if MGCs share transaction state.  Elsewhere H.248 allows
> > > but does not require MGCs to share state with its secondaries.  Although, I
> > > admit that all that will happen if they do not share state is that all pending
> > > transactions will fail, which is the same that will happen in #1 for
> > > failover.  #1, though allows pending transactions during handoff to succeed.
> > >
> > > b) it breaks our "all replies to source address" rule.  It requires that in
> > > this case we send replies to an address in the ServiceChange message or in
> > > provisioned secondary MGC list.  I believe that this breaks one of the hacks
> > > for working through NAT devices.
> > >
> > > #1 seemed to be the conclusion of all mail threads I found (3 or 4 since Jan
> > > 2000).
> >
> > [CHG] Perhaps what we need is option of both and describe the behaviour.
> > As I mentioned above it comes down to whether you support state sharing
> > or not.
> > I'm not particularly concerned about a general rule for NATs because its
> > a transport specific behaviour see my comment below.
> >
> > >
> > > > o Annex D is purely about IP transports, so I don't think we should take
> > > > it as a general guide to how the protocol works. We put transports in
> > > > Annexes so that we could have a common core protocol and use the Annexes
> > > > to tailor some procedures.
> > >
> > > I agree.  Perhaps, details describing this issue should be removed, allowing
> > > such to be stated in 7.2.8 and 11.5.  This also helps ensure that we treat TCP
> > > equally with UDP.  D.1.5 only applies to UDP but issues of where replies go
> > > should be same for both.
> > >
> > > > o Perhaps an exception to the rule is necessary. If you receive a
> > > > command from a valid, secure MGC telling you to you a new address then
> > > > what is the problem in using it?
> > >
> > > Of course you will use it for new transactions, the question is whether that
> > > new MGC can handle pending transactions (send or receive replies).
> > >
> > > > Cheers, Christian
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I hate to open this again.  I believe we have settled this but the IG
> > > > > does not seem to have a change.
> > > > >
> > > > > The issue is whether replies to requests from a failed MGC are sent to a
> > > > > secondary MGC or are sent to the failed MGC (in spite of likely
> > > > > failure).
> > > > >
> > > > > We have a number of statements (section 9.1, D.1, D.1.5) all of which
> > > > > say that replies must be sent to the address and port from which the
> > > > > request was sent.  I believe we are in agreement that this is a rule
> > > > > without exception.  But 11.5 pretty clearly contradicts this.
> > > > >     "Accordingly, commands in progress continue, TRANSACTION REPLIES ARE
> > > > > SENT TO THE NEW MGC (after a new control association is established),
> > > > > and the ..."
> > > > >
> > > > > The context does NOT sound like these replies are only replies to new
> > > > > requests (which would hardly need to be stated.  And so this seems to
> > > > > contradict the general principle or suggest an exception to the
> > > > > otherwise simple rule.  However, D.1.5 seems to be talking about exactly
> > > > > this same case and follows the general rule.
> > > > >
> > > > > This discrepancy appears to have been noticed as early as Jan 20, 2000
> > > > > by Shalini Philip and Brian Rosen's reply of Jan 21, 2000 suggested 11.5
> > > > > needed to be changed.  I see the same point raised a few more times in
> > > > > the archives.  And replies always seem to support the general rule.  I
> > > > > find no support for the 11.5 wording.  But I can find no correction to
> > > > > this in the IG (if its there could someone point out the item number).
> > > > >
> > > > > Are we in agreement that this wording is in error and should be changed
> > > > > to something like:
> > > > >
> > > > > "Accordingly, commands in progress continue and replies to all commands
> > > > > from the original MGC must be sent to source address and port from which
> > > > > they were sent (even if they are likely to fail). The MG should expect
> > > > > outstanding transaction replies from the new MGC."
> > > > >
> > > > > Do we still agree with the last sentence (from the last clause of the
> > > > > original)?  Should the new MGC (if it can) reply to transactions sent to
> > > > > the failed MGC (this, of course, will  happen only if the MGCs had
> > > > > shared state)?  These replies can still be sent to the addr/port from
> > > > > which they came (the MG) and so do not violate the general rule, but
> > > > > this does seem to fit with the general philosophy (which we would be
> > > > > changing) that the new MGC is taking over role of original even for
> > > > > pending transactions.
> > > > >
> > > > > --
> > > > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > > > ------------------------------------------------------------
> > > > > Terry L Anderson             mailto:tla@lucent.com
> > > > > Tel:908.582.7013   Fax:908.582.6729
> > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > >
> > > --
> > > Waiting for the other shoe to drop but hoping its a one legged man.
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla



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



From megaco-admin@ietf.org  Tue Jan 22 10:21:53 2002
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 KAA26121
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:21:53 -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 KAA12334;
	Tue, 22 Jan 2002 10:12:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06966
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:42:52 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17910
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:42:47 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MDhTE13179
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:13:29 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.004B3F81 ; Tue, 22 Jan 2002 19:11:54 +0530
X-Lotus-FromDomain: HSS
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B49.004B3C03.00@sandesh.hss.hns.com>
Date: Tue, 22 Jan 2002 19:13:40 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Query about local control descriptor properties
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



Hi Tom & list,

RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:

"If the MGC wishes to delete some information from the existing descriptor, it
merely resends the
   descriptor (in a Modify command) with the unwanted information stripped out."

Does the "unwanted information" refer to the properties which the MGC no more
requires to be set on the termination......

Please reply back...

Thanks,
Kapil Nayar



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


From daemon@optimus.ietf.org  Tue Jan 22 10:21:54 2002
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 KAA26130
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:21:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA12595
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 10:21:56 -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 KAA12334;
	Tue, 22 Jan 2002 10:12:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06966
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:42:52 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17910
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:42:47 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MDhTE13179
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:13:29 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.004B3F81 ; Tue, 22 Jan 2002 19:11:54 +0530
X-Lotus-FromDomain: HSS
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B49.004B3C03.00@sandesh.hss.hns.com>
Date: Tue, 22 Jan 2002 19:13:40 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Query about local control descriptor properties
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



Hi Tom & list,

RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:

"If the MGC wishes to delete some information from the existing descriptor, it
merely resends the
   descriptor (in a Modify command) with the unwanted information stripped out."

Does the "unwanted information" refer to the properties which the MGC no more
requires to be set on the termination......

Please reply back...

Thanks,
Kapil Nayar



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



From megaco-admin@ietf.org  Tue Jan 22 10:26:51 2002
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 KAA26277
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:26:51 -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 KAA12274;
	Tue, 22 Jan 2002 10:12:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06979
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:43:09 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17919
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:43:05 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MDgZS24450;
	Tue, 22 Jan 2002 08:42:35 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MDgXT12894;
	Tue, 22 Jan 2002 08:42:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY1C3>; Tue, 22 Jan 2002 08:42:34 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEB4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Issues In H.248v2: Context Packages
Date: Tue, 22 Jan 2002 08:42:32 -0500
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

It was done by show of hands.  This was the one item on the H.248v2 list for
which the balance of sentiment was clear to everyone in the room.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, January 21, 2002 10:20 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Issues In H.248v2: Context Packages


Hello Tom,

How was the sentiment on the context property recorded at the meeting?
Was there a hum poll or similar? If you are asking the list to confirm
this what particular arguments are there for delaying this? What
implications haven't been studied?

Cheers, Christian

Tom-PT Taylor wrote:
> 
> I was waiting for others to raise issues for our contribution to SG 16,
but
> there hasn't been much addressed specifically to H.248v2.  This is the
first
> of a series of E-mails I am going to generate on the topic.
> 
> The sentiment at IETF 52 was that packages for context properties were the
> one item that we would like to have SG 16 to defer until the full
> implications are realized.  That is, it should not be included in H.248v2.
> Can I confirm this view with the list?
> 
> Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> 
>  - delete final bullet of section 6.1.1
> 
>  - delete final sentence of first paragraph of section 6.2.3
> 
>  - delete second sentence of second paragraph of section 6.2.3
> 
>  - delete the phrase "or Context" from the last sentence of second
paragraph
> of section 6.2.3
> 
>  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> subsequent section(s) accordingly
> 
>  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> follows:
>    -- in the third paragraph, amend the final sentence to say "There are
two
> types of audit."
>    -- in the paragraphs beginning "Value Audit:" and "Capabilities
Audit:",
> delete the phrase "the ContextAttribute Descriptor or"
>    -- delete the paragraph beginning "Packages Audit"
>    -- delete the Audit Packages column of the table
> 
>  - delete the phrase "and contexts" in the first paragraph of section 12
> 
>  - delete the sentence beginning "ContextAttribute is for ..." and also
the
> final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> 
>  - delete the final sentence of the paragraph explaining
"Characteristics:"
> in section 12.1.2
> 
>  - in Annex A:
>    -- delete the contextProp and contextPackages components added after
the
> extension marker in the ContextRequest production
>    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> contextPropCapAud, and contextPackagesAud components added after the
> extension marker in the ContextAttrAuditRequest production
> 
>  - in Annex B:
>    -- delete the contextAttrDescriptor and packagesDescriptor terms from
the
> contextProperty production
>    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> IndAudContextAttrCap, and ContextAttrPackages terms from the
> contextAuditProperties production
>    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> ContextAttrDescriptorCapAud productions
>    -- delete the contextAttrDescriptor production
>    -- delete the ContextAttrToken, ContextAudCapToken,
> ContextAudDescriptorToken, and ContextAudValToken productions
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Tue Jan 22 10:26:52 2002
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 KAA26287
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 10:26:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA12851
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 10:26:54 -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 KAA12274;
	Tue, 22 Jan 2002 10:12:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06979
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:43:09 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17919
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:43:05 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MDgZS24450;
	Tue, 22 Jan 2002 08:42:35 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MDgXT12894;
	Tue, 22 Jan 2002 08:42:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY1C3>; Tue, 22 Jan 2002 08:42:34 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEB4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Issues In H.248v2: Context Packages
Date: Tue, 22 Jan 2002 08:42:32 -0500
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

It was done by show of hands.  This was the one item on the H.248v2 list for
which the balance of sentiment was clear to everyone in the room.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, January 21, 2002 10:20 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Issues In H.248v2: Context Packages


Hello Tom,

How was the sentiment on the context property recorded at the meeting?
Was there a hum poll or similar? If you are asking the list to confirm
this what particular arguments are there for delaying this? What
implications haven't been studied?

Cheers, Christian

Tom-PT Taylor wrote:
> 
> I was waiting for others to raise issues for our contribution to SG 16,
but
> there hasn't been much addressed specifically to H.248v2.  This is the
first
> of a series of E-mails I am going to generate on the topic.
> 
> The sentiment at IETF 52 was that packages for context properties were the
> one item that we would like to have SG 16 to defer until the full
> implications are realized.  That is, it should not be included in H.248v2.
> Can I confirm this view with the list?
> 
> Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> 
>  - delete final bullet of section 6.1.1
> 
>  - delete final sentence of first paragraph of section 6.2.3
> 
>  - delete second sentence of second paragraph of section 6.2.3
> 
>  - delete the phrase "or Context" from the last sentence of second
paragraph
> of section 6.2.3
> 
>  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> subsequent section(s) accordingly
> 
>  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> follows:
>    -- in the third paragraph, amend the final sentence to say "There are
two
> types of audit."
>    -- in the paragraphs beginning "Value Audit:" and "Capabilities
Audit:",
> delete the phrase "the ContextAttribute Descriptor or"
>    -- delete the paragraph beginning "Packages Audit"
>    -- delete the Audit Packages column of the table
> 
>  - delete the phrase "and contexts" in the first paragraph of section 12
> 
>  - delete the sentence beginning "ContextAttribute is for ..." and also
the
> final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> 
>  - delete the final sentence of the paragraph explaining
"Characteristics:"
> in section 12.1.2
> 
>  - in Annex A:
>    -- delete the contextProp and contextPackages components added after
the
> extension marker in the ContextRequest production
>    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> contextPropCapAud, and contextPackagesAud components added after the
> extension marker in the ContextAttrAuditRequest production
> 
>  - in Annex B:
>    -- delete the contextAttrDescriptor and packagesDescriptor terms from
the
> contextProperty production
>    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> IndAudContextAttrCap, and ContextAttrPackages terms from the
> contextAuditProperties production
>    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> ContextAttrDescriptorCapAud productions
>    -- delete the contextAttrDescriptor production
>    -- delete the ContextAttrToken, ContextAudCapToken,
> ContextAudDescriptorToken, and ContextAudValToken productions
> 
> Tom Taylor
> taylor@nortelnetworks.com
> Ph. +1 613 736 0961 (ESN 396 1490)
> 
> 
> _______________________________________________
> 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



From daemon@optimus.ietf.org  Tue Jan 22 10:56:34 2002
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 JAA20385
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 09:49:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10975
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 09:49:57 -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 JAA09607;
	Tue, 22 Jan 2002 09:40:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29571
	for <megaco@optimus.ietf.org>; Mon, 21 Jan 2002 17:25:07 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26890
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:58 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0LMOUd13965
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:30 -0500 (EST)
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 g0LMOTa09938
	for <megaco@ietf.org>; Mon, 21 Jan 2002 17:24:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZXZGG>; Mon, 21 Jan 2002 17:24:29 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEAF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 21 Jan 2002 17:24:28 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: TIPHON Release 4: Documents for WG3 Approval
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

FYI.  I'm sure they would accept outside comments if you have some.

-----Original Message-----
From: Richard Brennan [mailto:rbrennan@TELXXIS.COM]
Sent: Monday, January 21, 2002 2:35 PM
To: TIPHON_WG3@LIST.ETSI.FR
Subject: TIPHON Release 4: Documents for WG3 Approval


Dear all,

Two Release 4 documents based on new Work Items created at TIPHON 24
in November, reached stable draft at the TIPHON 25 meeting last week, and
have been referred to the Working Group 3 mailing list for Working Group
approval.

The documents are:

DTS/TIPHON-03027 V0.0.3
"TIPHON Release 4; Interface Protocol Requirements Definition;
TIPHON Extended MEGACO Package (EMP) Specification"
http://docbox.etsi.org/tech-org/tiphon/document/tiphon/07-drafts/WG3/DTS0302
7R4/V0.0.3

and

DTS/TIPHON-03028 V0.0.3
"TIPHON Release 4; Interface Protocol Requirements Definition;
Technology mapping of TIPHON architecture to Extended MEGACO Package"
http://docbox.etsi.org/tech-org/tiphon/document/tiphon/07-drafts/WG3/DTS0302
8R4/V0.0.3

Starting today, there will be a 4 week review period on the mailing list.
If no unresolved
comments are received by 18 February, 2002,  the documents will be
considered as
Working Group approved, placed under the Change Control process, and
submitted for TB
approval at the TIPHON 26 Plenary.

===================================
Richard Brennan - Telxxis LLC
Chairman ETSI TIPHON WG3
Office:         +1 650 655-2630
PCS/GSM:        +1 510 543-4726
mailto:rbrennan@telxxis.com
===================================

-------------------------------------------------------------------
Mail archive for TIPHON_WG3  can be browsed at the following url :

             http://list.etsi.fr/tiphon_wg3.html
-------------------------------------------------------------------

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



From megaco-admin@ietf.org  Tue Jan 22 11:23:36 2002
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 LAA28862
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 11:23:36 -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 LAA15405;
	Tue, 22 Jan 2002 11:03:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15377
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 11:03:19 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27855
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:03:16 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id KAA03447;
	Tue, 22 Jan 2002 10:02:49 -0600 (CST)
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 g0MG2ms12480;
	Tue, 22 Jan 2002 10:02:48 -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 g0MG23G17612;
	Tue, 22 Jan 2002 10:02:03 -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 g0MG23T06664;
	Tue, 22 Jan 2002 10:02:03 -0600 (CST)
Message-ID: <3C4D8CFB.49CD5FF9@alcatel.com>
Date: Tue, 22 Jan 2002 10:02:03 -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: Christian Groves <Christian.Groves@ericsson.com.au>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com> <3C4CD851.72F49970@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------073542A36286936D7F08EEA4"
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


--------------073542A36286936D7F08EEA4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Maybe I need a clarification on what

     should attempt to gracefully tear down existing connections on
     the
     Termination(s) affected by the serviceChange command.

Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers hang
up normally and then
put the termination OOS after subscribers hang up (before delay timer
expired)?

Or MGC starts releasing the calls whether the subscribers hang up or not?

Thanks
Chuong

Christian Groves wrote:

> There is a timing dependency here. If the MG issues a SC Graceful then
> the MGC will act on it. There will be a finite time that the MGC
> operates under graceful mode. If a SC Restart w/Service Restored or
> Service Change Cancel is issued during the graceful the MGC can't undo
> what it had done in that finite time but the connections that stayed up
> can remain up. If the SC Restart w/service restored or Service Change
> Cancel is not received before the delay times out then it pretty too
> late as the terminations will be torn down.
>
> I don't understand why you say that the MGC must wait until the
> servicechange delay timesouts before gracefully tearing down
> connections?
>
> Christian
>
> "Chuong N. Nguyen" wrote:
> >
> >
> > MG sends SC Graceful w/Delay and terminationID=ROOT.
> >
> > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > assume that
> > 1) SC Graceful w/Delay is being cancelled?
> > 2) All terminations are back In Service?  Even the ones that were
> > originally OOS before the SC Graceful.
> >
> >
> >    1) Graceful - indicates that the specified Terminations will be
> > taken
> >       out of service after the specified ServiceChangeDelay;
> > established
> >       connections are not yet affected, but the Media Gateway
> > Controller
> >       should refrain from establishing new connections and should
> >       attempt to gracefully tear down existing connections on the
> >       Termination(s) affected by the serviceChange command. The MG
> >       should set termination serviceState at the expiry of
> >       ServiceChangeDelay or the removal of the termination from an
> >       active context (whichever is first), to "out of service".
> >
> >
> > How should MGC implementation intepret the above highlighted
> > statement?
> > Does this mean that MGC should not try to gracefully tear down
> > existing connections
> > before Delay timer expired?
> >
> > But I think the above statement is telling MGC to try and gracefully
> > tear down
> > existing connections before Delay timer expired.
> >
> > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > until
> > Delay timer expired before it tries to tear down existing connections.
> >
> > But after Delay timer expired, MG will put all terminations out of
> > service.
> > Therefore there is no such thing as MGC gracefully tearing down
> > existing connections.
> >
> >
> > Christian Groves wrote:
> >
> > > I don't see that we need to add anything. Why can't the MG just
> > > issue a
> > > SC with Restart, Service Restored? The specification already allows
> > > the
> > > MG to do this.
> > >
> > > Regards, Christian
> > >
> > > "Chuong N. Nguyen" wrote:
> > > >
> > > > Hi Tom
> > > >
> > > > What are the possibilites of defining a mechanism of cancelling
> > > > ServiceChange Graceful?
> > > > That is MG send SC Graceful w/Delay=time.
> > > > Before time expired, MG wants to cancel this ServiceChange.
> > > >
> > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > Graceful cancelled"?
> > > > 2) Done in V2 - new SC Method or Reason?
> > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > >
> > > >
> > > > Thanks
> > > > Chuong
> > > >
> > > >
> > > >
> > > > --
> > > >   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 ****
> >
> >

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



--------------073542A36286936D7F08EEA4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Maybe I&nbsp;need a clarification on what
<blockquote>should attempt to gracefully tear down existing connections
on the
<br>Termination(s) affected by the serviceChange command.</blockquote>
Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers
hang up normally and then
<br>put the termination OOS after subscribers hang up (before delay timer
expired)?
<p>Or MGC starts releasing the calls whether the subscribers hang up or
not?
<p>Thanks
<br>Chuong
<p>Christian Groves wrote:
<blockquote TYPE=CITE>There is a timing dependency here. If the MG issues
a SC Graceful then
<br>the MGC will act on it. There will be a finite time that the MGC
<br>operates under graceful mode. If a SC Restart w/Service Restored or
<br>Service Change Cancel is issued during the graceful the MGC can't undo
<br>what it had done in that finite time but the connections that stayed
up
<br>can remain up. If the SC Restart w/service restored or Service Change
<br>Cancel is not received before the delay times out then it pretty too
<br>late as the terminations will be torn down.
<p>I don't understand why you say that the MGC must wait until the
<br>servicechange delay timesouts before gracefully tearing down
<br>connections?
<p>Christian
<p>"Chuong N. Nguyen" wrote:
<br>>
<br>>
<br>> MG sends SC Graceful w/Delay and terminationID=ROOT.
<br>>
<br>> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
<br>> assume that
<br>> 1) SC Graceful w/Delay is being cancelled?
<br>> 2) All terminations are back In Service?&nbsp; Even the ones that
were
<br>> originally OOS before the SC Graceful.
<br>>
<br>>
<br>>&nbsp;&nbsp;&nbsp; 1) Graceful - indicates that the specified Terminations
will be
<br>> taken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out of service after the specified
ServiceChangeDelay;
<br>> established
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connections are not yet affected,
but the Media Gateway
<br>> Controller
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should refrain from establishing
new connections and should
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attempt to gracefully tear down
existing connections on the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Termination(s) affected by the
serviceChange command. The MG
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should set termination serviceState
at the expiry of
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ServiceChangeDelay or the removal
of the termination from an
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; active context (whichever is
first), to "out of service".
<br>>
<br>>
<br>> How should MGC implementation intepret the above highlighted
<br>> statement?
<br>> Does this mean that MGC should not try to gracefully tear down
<br>> existing connections
<br>> before Delay timer expired?
<br>>
<br>> But I think the above statement is telling MGC to try and gracefully
<br>> tear down
<br>> existing connections before Delay timer expired.
<br>>
<br>> To be able to cancel Graceful w/Delay, it seems that MGC needs to
wait
<br>> until
<br>> Delay timer expired before it tries to tear down existing connections.
<br>>
<br>> But after Delay timer expired, MG will put all terminations out of
<br>> service.
<br>> Therefore there is no such thing as MGC gracefully tearing down
<br>> existing connections.
<br>>
<br>>
<br>> Christian Groves wrote:
<br>>
<br>> > I don't see that we need to add anything. Why can't the MG just
<br>> > issue a
<br>> > SC with Restart, Service Restored? The specification already allows
<br>> > the
<br>> > MG to do this.
<br>> >
<br>> > Regards, Christian
<br>> >
<br>> > "Chuong N. Nguyen" wrote:
<br>> > >
<br>> > > Hi Tom
<br>> > >
<br>> > > What are the possibilites of defining a mechanism of cancelling
<br>> > > ServiceChange Graceful?
<br>> > > That is MG send SC Graceful w/Delay=time.
<br>> > > Before time expired, MG wants to cancel this ServiceChange.
<br>> > >
<br>> > > 1) Can this be done in V1 by adding a new SC Reason like "916
SC
<br>> > > Graceful cancelled"?
<br>> > > 2) Done in V2 - new SC Method or Reason?
<br>> > > 3) Should be covered in draft-hss-megaco-control-association?
<br>> > >
<br>> > >
<br>> > > Thanks
<br>> > > Chuong
<br>> > >
<br>> > >
<br>> > >
<br>> > > --
<br>> > >&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet:
<br>> > Chuong.Nguyen@usa.alcatel.com
<br>> > >&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972)
<br>> > 519-4613
<br>> > >&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc
<br>> > ****
<br>> > >
<br>> > >
<br>>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------073542A36286936D7F08EEA4--


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


From daemon@optimus.ietf.org  Tue Jan 22 11:23:43 2002
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 LAA28872
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 11:23:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA19437
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 11:23:40 -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 LAA15405;
	Tue, 22 Jan 2002 11:03:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15377
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 11:03:19 -0500 (EST)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27855
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:03:16 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id KAA03447;
	Tue, 22 Jan 2002 10:02:49 -0600 (CST)
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 g0MG2ms12480;
	Tue, 22 Jan 2002 10:02:48 -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 g0MG23G17612;
	Tue, 22 Jan 2002 10:02:03 -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 g0MG23T06664;
	Tue, 22 Jan 2002 10:02:03 -0600 (CST)
Message-ID: <3C4D8CFB.49CD5FF9@alcatel.com>
Date: Tue, 22 Jan 2002 10:02:03 -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: Christian Groves <Christian.Groves@ericsson.com.au>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com> <3C4CD851.72F49970@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------073542A36286936D7F08EEA4"
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


--------------073542A36286936D7F08EEA4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Maybe I need a clarification on what

     should attempt to gracefully tear down existing connections on
     the
     Termination(s) affected by the serviceChange command.

Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers hang
up normally and then
put the termination OOS after subscribers hang up (before delay timer
expired)?

Or MGC starts releasing the calls whether the subscribers hang up or not?

Thanks
Chuong

Christian Groves wrote:

> There is a timing dependency here. If the MG issues a SC Graceful then
> the MGC will act on it. There will be a finite time that the MGC
> operates under graceful mode. If a SC Restart w/Service Restored or
> Service Change Cancel is issued during the graceful the MGC can't undo
> what it had done in that finite time but the connections that stayed up
> can remain up. If the SC Restart w/service restored or Service Change
> Cancel is not received before the delay times out then it pretty too
> late as the terminations will be torn down.
>
> I don't understand why you say that the MGC must wait until the
> servicechange delay timesouts before gracefully tearing down
> connections?
>
> Christian
>
> "Chuong N. Nguyen" wrote:
> >
> >
> > MG sends SC Graceful w/Delay and terminationID=ROOT.
> >
> > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > assume that
> > 1) SC Graceful w/Delay is being cancelled?
> > 2) All terminations are back In Service?  Even the ones that were
> > originally OOS before the SC Graceful.
> >
> >
> >    1) Graceful - indicates that the specified Terminations will be
> > taken
> >       out of service after the specified ServiceChangeDelay;
> > established
> >       connections are not yet affected, but the Media Gateway
> > Controller
> >       should refrain from establishing new connections and should
> >       attempt to gracefully tear down existing connections on the
> >       Termination(s) affected by the serviceChange command. The MG
> >       should set termination serviceState at the expiry of
> >       ServiceChangeDelay or the removal of the termination from an
> >       active context (whichever is first), to "out of service".
> >
> >
> > How should MGC implementation intepret the above highlighted
> > statement?
> > Does this mean that MGC should not try to gracefully tear down
> > existing connections
> > before Delay timer expired?
> >
> > But I think the above statement is telling MGC to try and gracefully
> > tear down
> > existing connections before Delay timer expired.
> >
> > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > until
> > Delay timer expired before it tries to tear down existing connections.
> >
> > But after Delay timer expired, MG will put all terminations out of
> > service.
> > Therefore there is no such thing as MGC gracefully tearing down
> > existing connections.
> >
> >
> > Christian Groves wrote:
> >
> > > I don't see that we need to add anything. Why can't the MG just
> > > issue a
> > > SC with Restart, Service Restored? The specification already allows
> > > the
> > > MG to do this.
> > >
> > > Regards, Christian
> > >
> > > "Chuong N. Nguyen" wrote:
> > > >
> > > > Hi Tom
> > > >
> > > > What are the possibilites of defining a mechanism of cancelling
> > > > ServiceChange Graceful?
> > > > That is MG send SC Graceful w/Delay=time.
> > > > Before time expired, MG wants to cancel this ServiceChange.
> > > >
> > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > Graceful cancelled"?
> > > > 2) Done in V2 - new SC Method or Reason?
> > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > >
> > > >
> > > > Thanks
> > > > Chuong
> > > >
> > > >
> > > >
> > > > --
> > > >   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 ****
> >
> >

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



--------------073542A36286936D7F08EEA4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Maybe I&nbsp;need a clarification on what
<blockquote>should attempt to gracefully tear down existing connections
on the
<br>Termination(s) affected by the serviceChange command.</blockquote>
Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers
hang up normally and then
<br>put the termination OOS after subscribers hang up (before delay timer
expired)?
<p>Or MGC starts releasing the calls whether the subscribers hang up or
not?
<p>Thanks
<br>Chuong
<p>Christian Groves wrote:
<blockquote TYPE=CITE>There is a timing dependency here. If the MG issues
a SC Graceful then
<br>the MGC will act on it. There will be a finite time that the MGC
<br>operates under graceful mode. If a SC Restart w/Service Restored or
<br>Service Change Cancel is issued during the graceful the MGC can't undo
<br>what it had done in that finite time but the connections that stayed
up
<br>can remain up. If the SC Restart w/service restored or Service Change
<br>Cancel is not received before the delay times out then it pretty too
<br>late as the terminations will be torn down.
<p>I don't understand why you say that the MGC must wait until the
<br>servicechange delay timesouts before gracefully tearing down
<br>connections?
<p>Christian
<p>"Chuong N. Nguyen" wrote:
<br>>
<br>>
<br>> MG sends SC Graceful w/Delay and terminationID=ROOT.
<br>>
<br>> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
<br>> assume that
<br>> 1) SC Graceful w/Delay is being cancelled?
<br>> 2) All terminations are back In Service?&nbsp; Even the ones that
were
<br>> originally OOS before the SC Graceful.
<br>>
<br>>
<br>>&nbsp;&nbsp;&nbsp; 1) Graceful - indicates that the specified Terminations
will be
<br>> taken
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out of service after the specified
ServiceChangeDelay;
<br>> established
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connections are not yet affected,
but the Media Gateway
<br>> Controller
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should refrain from establishing
new connections and should
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attempt to gracefully tear down
existing connections on the
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Termination(s) affected by the
serviceChange command. The MG
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should set termination serviceState
at the expiry of
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ServiceChangeDelay or the removal
of the termination from an
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; active context (whichever is
first), to "out of service".
<br>>
<br>>
<br>> How should MGC implementation intepret the above highlighted
<br>> statement?
<br>> Does this mean that MGC should not try to gracefully tear down
<br>> existing connections
<br>> before Delay timer expired?
<br>>
<br>> But I think the above statement is telling MGC to try and gracefully
<br>> tear down
<br>> existing connections before Delay timer expired.
<br>>
<br>> To be able to cancel Graceful w/Delay, it seems that MGC needs to
wait
<br>> until
<br>> Delay timer expired before it tries to tear down existing connections.
<br>>
<br>> But after Delay timer expired, MG will put all terminations out of
<br>> service.
<br>> Therefore there is no such thing as MGC gracefully tearing down
<br>> existing connections.
<br>>
<br>>
<br>> Christian Groves wrote:
<br>>
<br>> > I don't see that we need to add anything. Why can't the MG just
<br>> > issue a
<br>> > SC with Restart, Service Restored? The specification already allows
<br>> > the
<br>> > MG to do this.
<br>> >
<br>> > Regards, Christian
<br>> >
<br>> > "Chuong N. Nguyen" wrote:
<br>> > >
<br>> > > Hi Tom
<br>> > >
<br>> > > What are the possibilites of defining a mechanism of cancelling
<br>> > > ServiceChange Graceful?
<br>> > > That is MG send SC Graceful w/Delay=time.
<br>> > > Before time expired, MG wants to cancel this ServiceChange.
<br>> > >
<br>> > > 1) Can this be done in V1 by adding a new SC Reason like "916
SC
<br>> > > Graceful cancelled"?
<br>> > > 2) Done in V2 - new SC Method or Reason?
<br>> > > 3) Should be covered in draft-hss-megaco-control-association?
<br>> > >
<br>> > >
<br>> > > Thanks
<br>> > > Chuong
<br>> > >
<br>> > >
<br>> > >
<br>> > > --
<br>> > >&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet:
<br>> > Chuong.Nguyen@usa.alcatel.com
<br>> > >&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972)
<br>> > 519-4613
<br>> > >&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc
<br>> > ****
<br>> > >
<br>> > >
<br>>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------073542A36286936D7F08EEA4--


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



From megaco-admin@ietf.org  Tue Jan 22 12:15:02 2002
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 MAA01060
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:15:02 -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 LAA23151;
	Tue, 22 Jan 2002 11:55:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23105
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 11:55:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00114
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:55:11 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MGshS11559
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:54:43 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MGseT06734
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:54:41 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYM26>; Tue, 22 Jan 2002 11:54:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC0@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 22 Jan 2002 11:54:40 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Restrict Posting To Members
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

Is the spam level high enough that I should restrict posting to members only
for a little while?  It would mean that postinmgs from non-members would be
automatically routed to me for approval, and might be delayed for a few
hours to a day until I notice them. 

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@optimus.ietf.org  Tue Jan 22 12:15:02 2002
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 MAA01072
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:15:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA29681
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:15:06 -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 LAA23151;
	Tue, 22 Jan 2002 11:55:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23105
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 11:55:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00114
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:55:11 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MGshS11559
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:54:43 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MGseT06734
	for <megaco@ietf.org>; Tue, 22 Jan 2002 11:54:41 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYM26>; Tue, 22 Jan 2002 11:54:41 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC0@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 22 Jan 2002 11:54:40 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Restrict Posting To Members
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

Is the spam level high enough that I should restrict posting to members only
for a little while?  It would mean that postinmgs from non-members would be
automatically routed to me for approval, and might be delayed for a few
hours to a day until I notice them. 

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Tue Jan 22 12:16:10 2002
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 MAA01197
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:16:10 -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 JAA10272;
	Tue, 22 Jan 2002 09:41:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05279
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 07:47:08 -0500 (EST)
Received: from mailweb9.rediffmail.com ([203.199.83.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA16516
	for <megaco@ietf.org>; Tue, 22 Jan 2002 07:47:03 -0500 (EST)
Received: (qmail 18678 invoked by uid 510); 22 Jan 2002 12:45:20 -0000
Date: 22 Jan 2002 12:45:20 -0000
Message-ID: <20020122124520.18677.qmail@mailweb9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 22 Jan 2002 12:45:20 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA05280
Subject: [Megaco] test - ignore this
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


 


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


From daemon@optimus.ietf.org  Tue Jan 22 12:16:16 2002
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 MAA01207
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:16:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA29770
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:16:14 -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 JAA10272;
	Tue, 22 Jan 2002 09:41:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05279
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 07:47:08 -0500 (EST)
Received: from mailweb9.rediffmail.com ([203.199.83.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA16516
	for <megaco@ietf.org>; Tue, 22 Jan 2002 07:47:03 -0500 (EST)
Received: (qmail 18678 invoked by uid 510); 22 Jan 2002 12:45:20 -0000
Date: 22 Jan 2002 12:45:20 -0000
Message-ID: <20020122124520.18677.qmail@mailweb9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 22 Jan 2002 12:45:20 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA05280
Subject: [Megaco] test - ignore this
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


 


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



From megaco-admin@ietf.org  Tue Jan 22 12:26:55 2002
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 MAA01450
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:26:54 -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 JAA10228;
	Tue, 22 Jan 2002 09:41:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA25229
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 02:59:51 -0500 (EST)
Received: from mailFA4.rediffmail.com ([202.54.124.149])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA13426
	for <megaco@ietf.org>; Tue, 22 Jan 2002 02:59:48 -0500 (EST)
Received: (qmail 2743 invoked by uid 510); 22 Jan 2002 08:00:14 -0000
Date: 22 Jan 2002 08:00:14 -0000
Message-ID: <20020122080014.2742.qmail@mailFA4.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 22 Jan 2002 08:00:14 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA25230
Subject: [Megaco] PRIORITY FIELD IN CONTEXT ATTRIBUTE
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


hi all

  I am a newbie in megaco and while going through the documents, I have seen one field in context attribute called priority. What is it used for in a typical MG.

regs
vdy 


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


From daemon@optimus.ietf.org  Tue Jan 22 12:26:55 2002
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 MAA01461
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:26:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00086
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:26: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 JAA10228;
	Tue, 22 Jan 2002 09:41:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA25229
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 02:59:51 -0500 (EST)
Received: from mailFA4.rediffmail.com ([202.54.124.149])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA13426
	for <megaco@ietf.org>; Tue, 22 Jan 2002 02:59:48 -0500 (EST)
Received: (qmail 2743 invoked by uid 510); 22 Jan 2002 08:00:14 -0000
Date: 22 Jan 2002 08:00:14 -0000
Message-ID: <20020122080014.2742.qmail@mailFA4.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 22 Jan 2002 08:00:14 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA25230
Subject: [Megaco] PRIORITY FIELD IN CONTEXT ATTRIBUTE
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


hi all

  I am a newbie in megaco and while going through the documents, I have seen one field in context attribute called priority. What is it used for in a typical MG.

regs
vdy 


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



From megaco-admin@ietf.org  Tue Jan 22 12:28:57 2002
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 MAA01545
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:28:57 -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 JAA10291;
	Tue, 22 Jan 2002 09:41:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02315
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 06:16:35 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15573
	for <megaco@ietf.org>; Tue, 22 Jan 2002 06:16:29 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001736357@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 22 Jan 2002 17:01:02 +0530
Received: from ranabk (ranabk.future.futsoft.com [10.2.7.7])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0MBFju17944
	for <megaco@ietf.org>; Tue, 22 Jan 2002 16:45:45 +0530
Reply-To: <ranabk@future.futsoft.com>
From: "ranabk" <ranabk@future.futsoft.com>
To: <megaco@ietf.org>
Date: Tue, 22 Jan 2002 16:45:57 +0530
Message-Id: <002501c1a336$2b2cc3c0$0707020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Use of MUX descriptor
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: 7bit

We are exploring the use of MUX descriptors in ADD , MODIFY coomands .
Is there any specific event on which mux descriptors will be modified or
applied .
What is the pre condition to ADD with H221, H223, H226 mux descriptors ?

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


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


From daemon@optimus.ietf.org  Tue Jan 22 12:28:58 2002
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 MAA01556
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:28:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00169
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:29:01 -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 JAA10291;
	Tue, 22 Jan 2002 09:41:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02315
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 06:16:35 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15573
	for <megaco@ietf.org>; Tue, 22 Jan 2002 06:16:29 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001736357@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Tue, 22 Jan 2002 17:01:02 +0530
Received: from ranabk (ranabk.future.futsoft.com [10.2.7.7])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0MBFju17944
	for <megaco@ietf.org>; Tue, 22 Jan 2002 16:45:45 +0530
Reply-To: <ranabk@future.futsoft.com>
From: "ranabk" <ranabk@future.futsoft.com>
To: <megaco@ietf.org>
Date: Tue, 22 Jan 2002 16:45:57 +0530
Message-Id: <002501c1a336$2b2cc3c0$0707020a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Use of MUX descriptor
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: 7bit

We are exploring the use of MUX descriptors in ADD , MODIFY coomands .
Is there any specific event on which mux descriptors will be modified or
applied .
What is the pre condition to ADD with H221, H223, H226 mux descriptors ?

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


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



From megaco-admin@ietf.org  Tue Jan 22 12:34:27 2002
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 MAA01651
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:34:22 -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 JAA10520;
	Tue, 22 Jan 2002 09:42:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07174
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:54:42 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18246
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:54:37 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MDtJE13901
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:25:19 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.004C4969 ; Tue, 22 Jan 2002 19:23:15 +0530
X-Lotus-FromDomain: HSS
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B49.004C39B1.00@sandesh.hss.hns.com>
Date: Tue, 22 Jan 2002 19:24:24 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Query about streamID 0
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



Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?
Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






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


From daemon@optimus.ietf.org  Tue Jan 22 12:34:28 2002
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 MAA01662
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:34:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00678
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:34:31 -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 JAA10520;
	Tue, 22 Jan 2002 09:42:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07174
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:54:42 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18246
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:54:37 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MDtJE13901
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:25:19 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.004C4969 ; Tue, 22 Jan 2002 19:23:15 +0530
X-Lotus-FromDomain: HSS
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B49.004C39B1.00@sandesh.hss.hns.com>
Date: Tue, 22 Jan 2002 19:24:24 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Megaco] Query about streamID 0
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



Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?
Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






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



From megaco-admin@ietf.org  Tue Jan 22 12:40:08 2002
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 MAA01797
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:40:03 -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 JAA10348;
	Tue, 22 Jan 2002 09:41:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06842
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:40:43 -0500 (EST)
Received: from mail.deldsl.com ([202.131.154.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17846
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:40:37 -0500 (EST)
Received: from dexceldesigns.com ([202.131.154.196])
	by mail.deldsl.com (8.11.0/8.8.7) with ESMTP id g0MJ4wX30251
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:04:58 GMT
Message-ID: <001001c1a34b$554674c0$12010a64@domain.dexceldesigns.com>
From: Narendra Babu <narendra@dexceldesigns.com>
To: <megaco@ietf.org>
Date: Tue, 22 Jan 2002 19:17:29 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;	boundary="----=_NextPart_000_000D_01C1A379.6EE95400"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailserver: Sent using PostMaster (v4.1.10)
Subject: [Megaco] Clarification  for interim AH implementation (authentication header)
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

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C1A379.6EE95400
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all

I have a doubt in security issue for Megaco.The RFC states
that we have to follow interim AH i,e through authentication header =
present within the megaco message.

            If  we  follow that track we will come across with
authentication data field present in the message.To fill this
we have to find ICV on whole transaction and synthesized
IP header (refer page no 69 of RFC).There are two algorithms to =
calculate ICV   1) HMAC-MD5-96
                                                                         =
                                          2) HMAC-SHA-1-96        =20

My doubt is how the receiving side will come to know whether HMAC-MD5-96 =
 or HMAC-SHA-1-96  is used in the received message?

Can we get reference design for Interim AH anywhere ?

                                        Expecting your replies soon !

Thanks in Advance

Narendra




------=_NextPart_000_000D_01C1A379.6EE95400
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a doubt in security issue for =
Megaco.The RFC=20
states</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that we have to follow interim AH =
i,e&nbsp;through=20
authentication header present within the megaco message.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; If&nbsp; we&nbsp; follow that track we will come =
across=20
with</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>authentication data field present in =
the message.To=20
fill this</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we have to find ICV&nbsp;on whole =
transaction and=20
synthesized</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IP header (refer page no 69 of =
RFC).There are two=20
algorithms to calculate ICV&nbsp;  1) HMAC-MD5-96</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;2)=20
HMAC-SHA-1-96&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>My doubt is how the receiving side =
will&nbsp;come=20
to know&nbsp;whether <STRONG><EM>HMAC-MD5-96&nbsp; </EM></STRONG>or=20
<STRONG><EM>HMAC-SHA-1-96</EM></STRONG>&nbsp; is used in the received=20
message?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><EM>Can we get reference design =
for Interim=20
AH anywhere ?</EM></STRONG></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><EM>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
</EM></STRONG>Expecting your replies soon !</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in Advance</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Narendra</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

<br>--------------------------------------------------------------<br>Dexcel Electronics Designs (P) Ltd., Bangalore, India<br>
------=_NextPart_000_000D_01C1A379.6EE95400--


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


From daemon@optimus.ietf.org  Tue Jan 22 12:40:08 2002
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 MAA01813
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:40:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA00813
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:40:10 -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 JAA10348;
	Tue, 22 Jan 2002 09:41:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06842
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 08:40:43 -0500 (EST)
Received: from mail.deldsl.com ([202.131.154.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17846
	for <megaco@ietf.org>; Tue, 22 Jan 2002 08:40:37 -0500 (EST)
Received: from dexceldesigns.com ([202.131.154.196])
	by mail.deldsl.com (8.11.0/8.8.7) with ESMTP id g0MJ4wX30251
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:04:58 GMT
Message-ID: <001001c1a34b$554674c0$12010a64@domain.dexceldesigns.com>
From: Narendra Babu <narendra@dexceldesigns.com>
To: <megaco@ietf.org>
Date: Tue, 22 Jan 2002 19:17:29 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;	boundary="----=_NextPart_000_000D_01C1A379.6EE95400"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailserver: Sent using PostMaster (v4.1.10)
Subject: [Megaco] Clarification  for interim AH implementation (authentication header)
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

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C1A379.6EE95400
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all

I have a doubt in security issue for Megaco.The RFC states
that we have to follow interim AH i,e through authentication header =
present within the megaco message.

            If  we  follow that track we will come across with
authentication data field present in the message.To fill this
we have to find ICV on whole transaction and synthesized
IP header (refer page no 69 of RFC).There are two algorithms to =
calculate ICV   1) HMAC-MD5-96
                                                                         =
                                          2) HMAC-SHA-1-96        =20

My doubt is how the receiving side will come to know whether HMAC-MD5-96 =
 or HMAC-SHA-1-96  is used in the received message?

Can we get reference design for Interim AH anywhere ?

                                        Expecting your replies soon !

Thanks in Advance

Narendra




------=_NextPart_000_000D_01C1A379.6EE95400
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a doubt in security issue for =
Megaco.The RFC=20
states</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that we have to follow interim AH =
i,e&nbsp;through=20
authentication header present within the megaco message.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; If&nbsp; we&nbsp; follow that track we will come =
across=20
with</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>authentication data field present in =
the message.To=20
fill this</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we have to find ICV&nbsp;on whole =
transaction and=20
synthesized</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>IP header (refer page no 69 of =
RFC).There are two=20
algorithms to calculate ICV&nbsp;  1) HMAC-MD5-96</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;2)=20
HMAC-SHA-1-96&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>My doubt is how the receiving side =
will&nbsp;come=20
to know&nbsp;whether <STRONG><EM>HMAC-MD5-96&nbsp; </EM></STRONG>or=20
<STRONG><EM>HMAC-SHA-1-96</EM></STRONG>&nbsp; is used in the received=20
message?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><EM>Can we get reference design =
for Interim=20
AH anywhere ?</EM></STRONG></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><EM>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
</EM></STRONG>Expecting your replies soon !</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in Advance</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Narendra</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

<br>--------------------------------------------------------------<br>Dexcel Electronics Designs (P) Ltd., Bangalore, India<br>
------=_NextPart_000_000D_01C1A379.6EE95400--


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



From megaco-admin@ietf.org  Tue Jan 22 12:45:17 2002
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 MAA01972
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:45:16 -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 JAA10037;
	Tue, 22 Jan 2002 09:41:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09010
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:21:01 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01666
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:54 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01713;
	Tue, 22 Jan 2002 14:19:35 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13866;
	Tue, 22 Jan 2002 14:20:50 +1100 (EST)
Message-ID: <3C4CD6B5.949BAF4F@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:04:21 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com> <3C4C7DCE.AA438A49@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Christer, 

I don't think we can remove the whole chapter from the protocol at this
stage. I agree with Tom that we can do some call flows in a seperate
annex. I'll add some text on the euphemeral terminations to the proposed
clarification.

Regards, Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> >While we're on the topic of Annex M.4, I realized while reading it that it
> >improperly (I think) includes some control terminations in the multiplex.
> >This may be water under the bridge now -- too late to do anything about it.
> >
> >Anyway, Christer is asking for more than I would put into the core protocol
> >specification.  We should probably create an Informational RFC describing
> >multiplex use with examples, just as we should publish an Informational RFC
> >giving example call flows.
> 
> Why not removing the whole multiplex chapter from the core protocol,
> then, and putting it in a separate Annex, or something? The way it's
> defined now (even by adding the proposed changes) doesn't help anyone.
> You simply can't implement multiplexing with the info you get from that
> text (you don't know how to map the LCNs, which btw also are
> uni-dirctional, to specific terminations etc etc) - and that's NOT
> enough in my opinion.
> 
> I thought that the ITU people always wanted to specify everything very
> much in detail :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Monday, January 21, 2002 12:52 AM
> > To: Christian Groves
> > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> >
> > Hi,
> >
> > >I think that the H.324 package probably needs to be updated to say how
> > >this is done. I don't think its a core H.248 issue.
> >
> > I agree. The idea was that this property would be defined in the H.324
> > package, and then used within each stream descriptor in the Mux
> > Termination.
> >
> > >Perhaps an IG note could be added for the H324 package? I'd like to see a
> > reply from the
> > > H324 package authors on how they thought this was to be done.
> >
> > >Are there any updates you'd like to see to proposed text on
> > MultiplexDescriptors that Tom posted?
> >
> > First, as Tom already mentioned, it should be updated so that it also
> > includes emphemeral bearer terminations (RTP terminations, for example).
> >
> > Second, it should in detail, on a message level, describe how the
> > multiplexed connection is set up. Now it only says "use a stream
> > descriptor" - which means everyone is going to understand it their own
> > way, and we are going to have lots of interop problems when people start
> > implementing this :)
> >
> > Third, it should also describe in detail how the H.223 (or whatever
> > multiplex method is used) descriptor is used, ie which terminations are
> > included etc, depending on on which "side" of the multiplexer the
> > terminations are.
> >
> > Fourth, I think the whole Annex M.4 misses some things, but that's
> > another discussion...
> >
> > I understand if you want to get this document ready before february, but
> > please let us do this correct from the beginning :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > Regards, Christian
> > >
> > > Christer Holmberg wrote:
> > > >
> > > > Hi,
> > > >
> > > > I have read the document a few times, but even by having stream
> > > > descriptors in the mux termination, I still don't understand how each of
> > > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > > supposed to be the same as the LCN number, or how is the mapping done?
> > > >
> > > > A very simple solution would be to add a "LCN property" (to the H.324
> > > > package, I assume) which would be used in the each stream descriptor to
> > > > specify to which LCN it is mapped.
> > > >
> > > > Comments?
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > Tom-PT Taylor wrote:
> > > > >
> > > > > I mentioned that several of us have been discussing additional text
> > for
> > > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> > changes
> > > > > in the Megaco FTP site.  According to your taste, you can download
> > > > >
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > x64K.doc
> > > > > or
> > > > >
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > x64K.pdf
> > > > >
> > > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > > proposed text needs a further update.  The supporting bearers
> > contained by a
> > > > > multiplexing termination can be ephemeral as well as physical.
> > However, I
> > > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > > descriptor already exist in the context, since their properties are
> > probably
> > > > > not directly inferrable from those of the multiplexing termination.
> > > > >
> > > > > Tom Taylor
> > > > > taylor@nortelnetworks.com
> > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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


From daemon@optimus.ietf.org  Tue Jan 22 12:45:22 2002
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 MAA01982
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:45:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA01046
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:45:19 -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 JAA10037;
	Tue, 22 Jan 2002 09:41:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09010
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 22:21:01 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01666
	for <megaco@ietf.org>; Mon, 21 Jan 2002 22:20:54 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA01713;
	Tue, 22 Jan 2002 14:19:35 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA13866;
	Tue, 22 Jan 2002 14:20:50 +1100 (EST)
Message-ID: <3C4CD6B5.949BAF4F@ericsson.com.au>
Date: Tue, 22 Jan 2002 14:04:21 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com> <3C4C7DCE.AA438A49@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Christer, 

I don't think we can remove the whole chapter from the protocol at this
stage. I agree with Tom that we can do some call flows in a seperate
annex. I'll add some text on the euphemeral terminations to the proposed
clarification.

Regards, Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> >While we're on the topic of Annex M.4, I realized while reading it that it
> >improperly (I think) includes some control terminations in the multiplex.
> >This may be water under the bridge now -- too late to do anything about it.
> >
> >Anyway, Christer is asking for more than I would put into the core protocol
> >specification.  We should probably create an Informational RFC describing
> >multiplex use with examples, just as we should publish an Informational RFC
> >giving example call flows.
> 
> Why not removing the whole multiplex chapter from the core protocol,
> then, and putting it in a separate Annex, or something? The way it's
> defined now (even by adding the proposed changes) doesn't help anyone.
> You simply can't implement multiplexing with the info you get from that
> text (you don't know how to map the LCNs, which btw also are
> uni-dirctional, to specific terminations etc etc) - and that's NOT
> enough in my opinion.
> 
> I thought that the ITU people always wanted to specify everything very
> much in detail :)
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Monday, January 21, 2002 12:52 AM
> > To: Christian Groves
> > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> >
> > Hi,
> >
> > >I think that the H.324 package probably needs to be updated to say how
> > >this is done. I don't think its a core H.248 issue.
> >
> > I agree. The idea was that this property would be defined in the H.324
> > package, and then used within each stream descriptor in the Mux
> > Termination.
> >
> > >Perhaps an IG note could be added for the H324 package? I'd like to see a
> > reply from the
> > > H324 package authors on how they thought this was to be done.
> >
> > >Are there any updates you'd like to see to proposed text on
> > MultiplexDescriptors that Tom posted?
> >
> > First, as Tom already mentioned, it should be updated so that it also
> > includes emphemeral bearer terminations (RTP terminations, for example).
> >
> > Second, it should in detail, on a message level, describe how the
> > multiplexed connection is set up. Now it only says "use a stream
> > descriptor" - which means everyone is going to understand it their own
> > way, and we are going to have lots of interop problems when people start
> > implementing this :)
> >
> > Third, it should also describe in detail how the H.223 (or whatever
> > multiplex method is used) descriptor is used, ie which terminations are
> > included etc, depending on on which "side" of the multiplexer the
> > terminations are.
> >
> > Fourth, I think the whole Annex M.4 misses some things, but that's
> > another discussion...
> >
> > I understand if you want to get this document ready before february, but
> > please let us do this correct from the beginning :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > Regards, Christian
> > >
> > > Christer Holmberg wrote:
> > > >
> > > > Hi,
> > > >
> > > > I have read the document a few times, but even by having stream
> > > > descriptors in the mux termination, I still don't understand how each of
> > > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > > supposed to be the same as the LCN number, or how is the mapping done?
> > > >
> > > > A very simple solution would be to add a "LCN property" (to the H.324
> > > > package, I assume) which would be used in the each stream descriptor to
> > > > specify to which LCN it is mapped.
> > > >
> > > > Comments?
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > Tom-PT Taylor wrote:
> > > > >
> > > > > I mentioned that several of us have been discussing additional text
> > for
> > > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> > changes
> > > > > in the Megaco FTP site.  According to your taste, you can download
> > > > >
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > x64K.doc
> > > > > or
> > > > >
> > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > x64K.pdf
> > > > >
> > > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > > proposed text needs a further update.  The supporting bearers
> > contained by a
> > > > > multiplexing termination can be ephemeral as well as physical.
> > However, I
> > > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > > descriptor already exist in the context, since their properties are
> > probably
> > > > > not directly inferrable from those of the multiplexing termination.
> > > > >
> > > > > Tom Taylor
> > > > > taylor@nortelnetworks.com
> > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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



From megaco-admin@ietf.org  Tue Jan 22 12:49:34 2002
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 MAA02133
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:49:34 -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 JAA10166;
	Tue, 22 Jan 2002 09:41:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24910
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 02:35:41 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13199
	for <megaco@ietf.org>; Tue, 22 Jan 2002 02:35:38 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0M7ZLIB023199;
	Tue, 22 Jan 2002 08:35:21 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0M7ZLr6006308;
	Tue, 22 Jan 2002 09:35:21 +0200 (EET)
Message-ID: <3C4D1638.12744F3F@lmf.ericsson.se>
Date: Tue, 22 Jan 2002 09:35:20 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com> <3C4C7DCE.AA438A49@lmf.ericsson.se> <3C4CD6B5.949BAF4F@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I don't think we can remove the whole chapter from the protocol at this
>stage. I agree with Tom that we can do some call flows in a seperate
>annex.

Oki.

>I'll add some text on the euphemeral terminations to the proposed clarification.

So, we shouldn't say anything about the Stream Descriptors in the Mux
Termination? How they are mapped to the LCNs etc? Personally I don't
care if it's said in the core spec, or in a separate Annex, but I don't
understand what the purpose is to put stuff in the core which nobody can
use :)

Does anyone know if there has been any response on this issue from SG16?

Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > >While we're on the topic of Annex M.4, I realized while reading it that it
> > >improperly (I think) includes some control terminations in the multiplex.
> > >This may be water under the bridge now -- too late to do anything about it.
> > >
> > >Anyway, Christer is asking for more than I would put into the core protocol
> > >specification.  We should probably create an Informational RFC describing
> > >multiplex use with examples, just as we should publish an Informational RFC
> > >giving example call flows.
> >
> > Why not removing the whole multiplex chapter from the core protocol,
> > then, and putting it in a separate Annex, or something? The way it's
> > defined now (even by adding the proposed changes) doesn't help anyone.
> > You simply can't implement multiplexing with the info you get from that
> > text (you don't know how to map the LCNs, which btw also are
> > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > enough in my opinion.
> >
> > I thought that the ITU people always wanted to specify everything very
> > much in detail :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Monday, January 21, 2002 12:52 AM
> > > To: Christian Groves
> > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > >
> > > Hi,
> > >
> > > >I think that the H.324 package probably needs to be updated to say how
> > > >this is done. I don't think its a core H.248 issue.
> > >
> > > I agree. The idea was that this property would be defined in the H.324
> > > package, and then used within each stream descriptor in the Mux
> > > Termination.
> > >
> > > >Perhaps an IG note could be added for the H324 package? I'd like to see a
> > > reply from the
> > > > H324 package authors on how they thought this was to be done.
> > >
> > > >Are there any updates you'd like to see to proposed text on
> > > MultiplexDescriptors that Tom posted?
> > >
> > > First, as Tom already mentioned, it should be updated so that it also
> > > includes emphemeral bearer terminations (RTP terminations, for example).
> > >
> > > Second, it should in detail, on a message level, describe how the
> > > multiplexed connection is set up. Now it only says "use a stream
> > > descriptor" - which means everyone is going to understand it their own
> > > way, and we are going to have lots of interop problems when people start
> > > implementing this :)
> > >
> > > Third, it should also describe in detail how the H.223 (or whatever
> > > multiplex method is used) descriptor is used, ie which terminations are
> > > included etc, depending on on which "side" of the multiplexer the
> > > terminations are.
> > >
> > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > another discussion...
> > >
> > > I understand if you want to get this document ready before february, but
> > > please let us do this correct from the beginning :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Christer Holmberg wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have read the document a few times, but even by having stream
> > > > > descriptors in the mux termination, I still don't understand how each of
> > > > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > > > supposed to be the same as the LCN number, or how is the mapping done?
> > > > >
> > > > > A very simple solution would be to add a "LCN property" (to the H.324
> > > > > package, I assume) which would be used in the each stream descriptor to
> > > > > specify to which LCN it is mapped.
> > > > >
> > > > > Comments?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > Tom-PT Taylor wrote:
> > > > > >
> > > > > > I mentioned that several of us have been discussing additional text
> > > for
> > > > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> > > changes
> > > > > > in the Megaco FTP site.  According to your taste, you can download
> > > > > >
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.doc
> > > > > > or
> > > > > >
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.pdf
> > > > > >
> > > > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > > > proposed text needs a further update.  The supporting bearers
> > > contained by a
> > > > > > multiplexing termination can be ephemeral as well as physical.
> > > However, I
> > > > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > > > descriptor already exist in the context, since their properties are
> > > probably
> > > > > > not directly inferrable from those of the multiplexing termination.
> > > > > >
> > > > > > Tom Taylor
> > > > > > taylor@nortelnetworks.com
> > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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


From daemon@optimus.ietf.org  Tue Jan 22 12:49:39 2002
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 MAA02144
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 12:49:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA01149
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 12:49:36 -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 JAA10166;
	Tue, 22 Jan 2002 09:41:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24910
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 02:35:41 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13199
	for <megaco@ietf.org>; Tue, 22 Jan 2002 02:35:38 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0M7ZLIB023199;
	Tue, 22 Jan 2002 08:35:21 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0M7ZLr6006308;
	Tue, 22 Jan 2002 09:35:21 +0200 (EET)
Message-ID: <3C4D1638.12744F3F@lmf.ericsson.se>
Date: Tue, 22 Jan 2002 09:35:20 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEA8@zcard0kc.ca.nortel.com> <3C4C7DCE.AA438A49@lmf.ericsson.se> <3C4CD6B5.949BAF4F@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I don't think we can remove the whole chapter from the protocol at this
>stage. I agree with Tom that we can do some call flows in a seperate
>annex.

Oki.

>I'll add some text on the euphemeral terminations to the proposed clarification.

So, we shouldn't say anything about the Stream Descriptors in the Mux
Termination? How they are mapped to the LCNs etc? Personally I don't
care if it's said in the core spec, or in a separate Annex, but I don't
understand what the purpose is to put stuff in the core which nobody can
use :)

Does anyone know if there has been any response on this issue from SG16?

Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > >While we're on the topic of Annex M.4, I realized while reading it that it
> > >improperly (I think) includes some control terminations in the multiplex.
> > >This may be water under the bridge now -- too late to do anything about it.
> > >
> > >Anyway, Christer is asking for more than I would put into the core protocol
> > >specification.  We should probably create an Informational RFC describing
> > >multiplex use with examples, just as we should publish an Informational RFC
> > >giving example call flows.
> >
> > Why not removing the whole multiplex chapter from the core protocol,
> > then, and putting it in a separate Annex, or something? The way it's
> > defined now (even by adding the proposed changes) doesn't help anyone.
> > You simply can't implement multiplexing with the info you get from that
> > text (you don't know how to map the LCNs, which btw also are
> > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > enough in my opinion.
> >
> > I thought that the ITU people always wanted to specify everything very
> > much in detail :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Monday, January 21, 2002 12:52 AM
> > > To: Christian Groves
> > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > >
> > > Hi,
> > >
> > > >I think that the H.324 package probably needs to be updated to say how
> > > >this is done. I don't think its a core H.248 issue.
> > >
> > > I agree. The idea was that this property would be defined in the H.324
> > > package, and then used within each stream descriptor in the Mux
> > > Termination.
> > >
> > > >Perhaps an IG note could be added for the H324 package? I'd like to see a
> > > reply from the
> > > > H324 package authors on how they thought this was to be done.
> > >
> > > >Are there any updates you'd like to see to proposed text on
> > > MultiplexDescriptors that Tom posted?
> > >
> > > First, as Tom already mentioned, it should be updated so that it also
> > > includes emphemeral bearer terminations (RTP terminations, for example).
> > >
> > > Second, it should in detail, on a message level, describe how the
> > > multiplexed connection is set up. Now it only says "use a stream
> > > descriptor" - which means everyone is going to understand it their own
> > > way, and we are going to have lots of interop problems when people start
> > > implementing this :)
> > >
> > > Third, it should also describe in detail how the H.223 (or whatever
> > > multiplex method is used) descriptor is used, ie which terminations are
> > > included etc, depending on on which "side" of the multiplexer the
> > > terminations are.
> > >
> > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > another discussion...
> > >
> > > I understand if you want to get this document ready before february, but
> > > please let us do this correct from the beginning :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Christer Holmberg wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have read the document a few times, but even by having stream
> > > > > descriptors in the mux termination, I still don't understand how each of
> > > > > those stream descriptors are mapped to specific LNCs. Is the StreamID
> > > > > supposed to be the same as the LCN number, or how is the mapping done?
> > > > >
> > > > > A very simple solution would be to add a "LCN property" (to the H.324
> > > > > package, I assume) which would be used in the each stream descriptor to
> > > > > specify to which LCN it is mapped.
> > > > >
> > > > > Comments?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > Tom-PT Taylor wrote:
> > > > > >
> > > > > > I mentioned that several of us have been discussing additional text
> > > for
> > > > > > Multiplex Descriptors.  I have placed the proposed text as marked up
> > > changes
> > > > > > in the Megaco FTP site.  According to your taste, you can download
> > > > > >
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.doc
> > > > > > or
> > > > > >
> > > ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.pdf
> > > > > >
> > > > > > Based on my reply to Christer Holm yesterday (see "LCN Mapping"), this
> > > > > > proposed text needs a further update.  The supporting bearers
> > > contained by a
> > > > > > multiplexing termination can be ephemeral as well as physical.
> > > However, I
> > > > > > believe it would be essential that any ephemrals mentioned in a MUX
> > > > > > descriptor already exist in the context, since their properties are
> > > probably
> > > > > > not directly inferrable from those of the multiplexing termination.
> > > > > >
> > > > > > Tom Taylor
> > > > > > taylor@nortelnetworks.com
> > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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



From megaco-admin@ietf.org  Tue Jan 22 13:10:04 2002
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 NAA02580
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:10:04 -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 JAA10125;
	Tue, 22 Jan 2002 09:41:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10670
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 23:10:28 -0500 (EST)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03220
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:10:25 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0M4ARh27589;
	Mon, 21 Jan 2002 23:10:28 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.112])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id XAA27476;
	Mon, 21 Jan 2002 23:10:23 -0500 (EST)
Message-ID: <3C4CE577.DB72E231@lucent.com>
Date: Mon, 21 Jan 2002 23:07:20 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------92EBACE86749387E4A04514D"
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

This is a multi-part message in MIME format.
--------------92EBACE86749387E4A04514D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Christian Groves wrote:

> G'Day Terry,
>
> We already have this functionality in H.248 "Reserve Group" and "Reserve
> Value". It allows the FID concept (group ID).

Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
thought they they simply allowed MGC to specify whether MGC should choose one choice or
all choices it can support  among alternatives in a single stream (as well as reserving
the resources for those in reply).  I've always assumed that this was simply a first
step in negotiation and before the call was fully setup a single Group would be chosen
by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
believe that a call will function with multiple groups still present?  If so, where do
we specify the semantics?  With Local, would we mix the RTP received in each group?
With Remote, would we send to ALL groups?

I think Reserve Group and Reserve Value are in the subject line only because the
original question on this topic lead to the noticing the single m line restriction and
FID was an additional reason for concern about this.  I should have changed the subject
before continuing the discussion of multiple m lines.

I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
streams are grouped into a single media stream (or streams are coordinated such as video
and audio for lip sync), but let's look at the grouping of RTP streams.  The
archetypical example, given in the FID draft is where a single audio media stream is
split into seperate RTP sessions, one carrying DTMF and the other voice, using different
encoding and sent to different ipaddr/port locations (or the reverse where to RTP
sessions are combined into one.

I don't seen how Reserve Group and Reserve Value help with this, but there may be a
question of whether H.248's Context is sufficient to provide the FID functionality.  FID
specifies that an inbound media stream is sent using all m lines in the flow (group).
This is essentially equivalent to using distinct terminations for each m line and
putting all the terminations in the same context with appropriate topology descriptor.
FID does have some restrictions on the use of each m line that are a little different.
It assumes that the flow will be encoded using a single codec and sent only to the m
lines supporting that codec.  This seems to be intended to separate things like DTMF -
if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
lines containing phone-event and not to those with only voice codecs.  I don't see how
to indicate this behavior with additional terminations in the context, where it would
seem that the DTMF tone should be sent to all indicated terminations with corresponding
codec (that is, telephone-event to one AND codec encoded tone to other).

The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
single SDP description.  I would think that audio and video whould still need to be in
distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
need some statement how to do this in H.248 since we do NOT want the entire session in a
single Stream Descriptor.

Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
suggest other reasons we need it or how it would be used.


> With regards to sending
> DTMF I thought that we used the signal mechanism for that. So I don't
> think we need a change.

I believe that there is need for both mechanisms: sending DTMF through signaling channel
(events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
The RTP method is often preferable when DTMF is being passed through to far PSTN and
there is no need to process it in a MGC (or routing GK).  It travels much faster and is
much easier to coordinate time when regenerating the tones in the media channel.  There
is currently no mechanism (that I know of) like the recent additions to H.245 to carry
the RTP timestamp in the event notification and signal descriptor, in order to re-insert
the DTMF at the correct time in the media channel.

>
>
> Regards, Christian
>
> Troy Cauble wrote:
> >
> > Terry L Anderson wrote:
> > >
> > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > the statement was that multiple media streams in SDP should not occur in a
> > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > too restrictive.
> > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > distinct payload.  It also supports sending this payload to a different
> > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > again requires multiple media (m) lines in the SDP.
> > >
> > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > bullets):
> > >
> > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > single session description MUST NOT include more than one media description
> > > ("m=" line).  Any additional media streams for a termination must appear in
> > > distinct Stream Descriptors.
> > >
> > > Perhaps we could change this to read:
> > >
> > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > single session description MUST NOT specify multiple streams.  This often means
> > > that the session description will contain only a single media description ("m="
> > > line).  However, where media descriptions are grouped and refer to a single,
> > > logical media stream but where payload packets may be sent to different
> > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > Descriptors.
> > > --------
> > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > Informative References, but I think this helps clarify the intent with an
> > > example.  We cannot refer to FID as it is not yet an RFC.
> >
> > I have no problem with the intent of this change.  You have to
> > change the language to allow certain cases.  But the language
> > is getting very fuzzy.
> >
> > How do I tell a "single, logical media stream" from "multiple streams"?
> >
> > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > audio + video is "multiple streams"?
> >
> > When would an MG be handling multiple streams on a termination
> > that are not "logically" related in some way?
> >
> > Doesn't this really mean I can put as many "streams" as I want
> > in my SDP and have just one StreamDescriptor?
> >
> > -troy
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------92EBACE86749387E4A04514D
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------92EBACE86749387E4A04514D--


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


From daemon@ns.ietf.org  Tue Jan 22 13:10:05 2002
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 NAA02591
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:10:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02256
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:10:06 -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 JAA10125;
	Tue, 22 Jan 2002 09:41:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10670
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 23:10:28 -0500 (EST)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03220
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:10:25 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0M4ARh27589;
	Mon, 21 Jan 2002 23:10:28 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.112])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id XAA27476;
	Mon, 21 Jan 2002 23:10:23 -0500 (EST)
Message-ID: <3C4CE577.DB72E231@lucent.com>
Date: Mon, 21 Jan 2002 23:07:20 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------92EBACE86749387E4A04514D"
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

This is a multi-part message in MIME format.
--------------92EBACE86749387E4A04514D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Christian Groves wrote:

> G'Day Terry,
>
> We already have this functionality in H.248 "Reserve Group" and "Reserve
> Value". It allows the FID concept (group ID).

Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
thought they they simply allowed MGC to specify whether MGC should choose one choice or
all choices it can support  among alternatives in a single stream (as well as reserving
the resources for those in reply).  I've always assumed that this was simply a first
step in negotiation and before the call was fully setup a single Group would be chosen
by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
believe that a call will function with multiple groups still present?  If so, where do
we specify the semantics?  With Local, would we mix the RTP received in each group?
With Remote, would we send to ALL groups?

I think Reserve Group and Reserve Value are in the subject line only because the
original question on this topic lead to the noticing the single m line restriction and
FID was an additional reason for concern about this.  I should have changed the subject
before continuing the discussion of multiple m lines.

I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
streams are grouped into a single media stream (or streams are coordinated such as video
and audio for lip sync), but let's look at the grouping of RTP streams.  The
archetypical example, given in the FID draft is where a single audio media stream is
split into seperate RTP sessions, one carrying DTMF and the other voice, using different
encoding and sent to different ipaddr/port locations (or the reverse where to RTP
sessions are combined into one.

I don't seen how Reserve Group and Reserve Value help with this, but there may be a
question of whether H.248's Context is sufficient to provide the FID functionality.  FID
specifies that an inbound media stream is sent using all m lines in the flow (group).
This is essentially equivalent to using distinct terminations for each m line and
putting all the terminations in the same context with appropriate topology descriptor.
FID does have some restrictions on the use of each m line that are a little different.
It assumes that the flow will be encoded using a single codec and sent only to the m
lines supporting that codec.  This seems to be intended to separate things like DTMF -
if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
lines containing phone-event and not to those with only voice codecs.  I don't see how
to indicate this behavior with additional terminations in the context, where it would
seem that the DTMF tone should be sent to all indicated terminations with corresponding
codec (that is, telephone-event to one AND codec encoded tone to other).

The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
single SDP description.  I would think that audio and video whould still need to be in
distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
need some statement how to do this in H.248 since we do NOT want the entire session in a
single Stream Descriptor.

Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
suggest other reasons we need it or how it would be used.


> With regards to sending
> DTMF I thought that we used the signal mechanism for that. So I don't
> think we need a change.

I believe that there is need for both mechanisms: sending DTMF through signaling channel
(events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
The RTP method is often preferable when DTMF is being passed through to far PSTN and
there is no need to process it in a MGC (or routing GK).  It travels much faster and is
much easier to coordinate time when regenerating the tones in the media channel.  There
is currently no mechanism (that I know of) like the recent additions to H.245 to carry
the RTP timestamp in the event notification and signal descriptor, in order to re-insert
the DTMF at the correct time in the media channel.

>
>
> Regards, Christian
>
> Troy Cauble wrote:
> >
> > Terry L Anderson wrote:
> > >
> > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > the statement was that multiple media streams in SDP should not occur in a
> > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > too restrictive.
> > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > distinct payload.  It also supports sending this payload to a different
> > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > again requires multiple media (m) lines in the SDP.
> > >
> > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > bullets):
> > >
> > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > single session description MUST NOT include more than one media description
> > > ("m=" line).  Any additional media streams for a termination must appear in
> > > distinct Stream Descriptors.
> > >
> > > Perhaps we could change this to read:
> > >
> > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > single session description MUST NOT specify multiple streams.  This often means
> > > that the session description will contain only a single media description ("m="
> > > line).  However, where media descriptions are grouped and refer to a single,
> > > logical media stream but where payload packets may be sent to different
> > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > Descriptors.
> > > --------
> > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > Informative References, but I think this helps clarify the intent with an
> > > example.  We cannot refer to FID as it is not yet an RFC.
> >
> > I have no problem with the intent of this change.  You have to
> > change the language to allow certain cases.  But the language
> > is getting very fuzzy.
> >
> > How do I tell a "single, logical media stream" from "multiple streams"?
> >
> > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > audio + video is "multiple streams"?
> >
> > When would an MG be handling multiple streams on a termination
> > that are not "logically" related in some way?
> >
> > Doesn't this really mean I can put as many "streams" as I want
> > in my SDP and have just one StreamDescriptor?
> >
> > -troy
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------92EBACE86749387E4A04514D
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------92EBACE86749387E4A04514D--


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



From megaco-admin@ietf.org  Tue Jan 22 13:10:18 2002
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 NAA02615
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:10:18 -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 MAA01207;
	Tue, 22 Jan 2002 12:51:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01178
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 12:51:20 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02193
	for <megaco@ietf.org>; Tue, 22 Jan 2002 12:51:17 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MHolS15760;
	Tue, 22 Jan 2002 12:50:47 -0500 (EST)
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 g0MHojS13638;
	Tue, 22 Jan 2002 12:50:45 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYN9S>; Tue, 22 Jan 2002 12:50:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC5@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Tue, 22 Jan 2002 12:50:42 -0500
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

The LCNs are specific to one application, not a general multiplexing issue.
(Although I suppose a similar issue arises with H.320, I also think H.320
would need its own annex.)  I think the mapping has to be described in Annex
M.4 for H.324.  The most obvious solution is as Christer indicated: an LCN
property in LocalControl. 

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Tuesday, January 22, 2002 2:35 AM
To: Christian Groves
Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>I don't think we can remove the whole chapter from the protocol at this
>stage. I agree with Tom that we can do some call flows in a seperate
>annex.

Oki.

>I'll add some text on the euphemeral terminations to the proposed
clarification.

So, we shouldn't say anything about the Stream Descriptors in the Mux
Termination? How they are mapped to the LCNs etc? Personally I don't
care if it's said in the core spec, or in a separate Annex, but I don't
understand what the purpose is to put stuff in the core which nobody can
use :)

Does anyone know if there has been any response on this issue from SG16?

Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > >While we're on the topic of Annex M.4, I realized while reading it that
it
> > >improperly (I think) includes some control terminations in the
multiplex.
> > >This may be water under the bridge now -- too late to do anything about
it.
> > >
> > >Anyway, Christer is asking for more than I would put into the core
protocol
> > >specification.  We should probably create an Informational RFC
describing
> > >multiplex use with examples, just as we should publish an Informational
RFC
> > >giving example call flows.
> >
> > Why not removing the whole multiplex chapter from the core protocol,
> > then, and putting it in a separate Annex, or something? The way it's
> > defined now (even by adding the proposed changes) doesn't help anyone.
> > You simply can't implement multiplexing with the info you get from that
> > text (you don't know how to map the LCNs, which btw also are
> > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > enough in my opinion.
> >
> > I thought that the ITU people always wanted to specify everything very
> > much in detail :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Monday, January 21, 2002 12:52 AM
> > > To: Christian Groves
> > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > >
> > > Hi,
> > >
> > > >I think that the H.324 package probably needs to be updated to say
how
> > > >this is done. I don't think its a core H.248 issue.
> > >
> > > I agree. The idea was that this property would be defined in the H.324
> > > package, and then used within each stream descriptor in the Mux
> > > Termination.
> > >
> > > >Perhaps an IG note could be added for the H324 package? I'd like to
see a
> > > reply from the
> > > > H324 package authors on how they thought this was to be done.
> > >
> > > >Are there any updates you'd like to see to proposed text on
> > > MultiplexDescriptors that Tom posted?
> > >
> > > First, as Tom already mentioned, it should be updated so that it also
> > > includes emphemeral bearer terminations (RTP terminations, for
example).
> > >
> > > Second, it should in detail, on a message level, describe how the
> > > multiplexed connection is set up. Now it only says "use a stream
> > > descriptor" - which means everyone is going to understand it their own
> > > way, and we are going to have lots of interop problems when people
start
> > > implementing this :)
> > >
> > > Third, it should also describe in detail how the H.223 (or whatever
> > > multiplex method is used) descriptor is used, ie which terminations
are
> > > included etc, depending on on which "side" of the multiplexer the
> > > terminations are.
> > >
> > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > another discussion...
> > >
> > > I understand if you want to get this document ready before february,
but
> > > please let us do this correct from the beginning :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Christer Holmberg wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have read the document a few times, but even by having stream
> > > > > descriptors in the mux termination, I still don't understand how
each of
> > > > > those stream descriptors are mapped to specific LNCs. Is the
StreamID
> > > > > supposed to be the same as the LCN number, or how is the mapping
done?
> > > > >
> > > > > A very simple solution would be to add a "LCN property" (to the
H.324
> > > > > package, I assume) which would be used in the each stream
descriptor to
> > > > > specify to which LCN it is mapped.
> > > > >
> > > > > Comments?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > Tom-PT Taylor wrote:
> > > > > >
> > > > > > I mentioned that several of us have been discussing additional
text
> > > for
> > > > > > Multiplex Descriptors.  I have placed the proposed text as
marked up
> > > changes
> > > > > > in the Megaco FTP site.  According to your taste, you can
download
> > > > > >
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.doc
> > > > > > or
> > > > > >
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.pdf
> > > > > >
> > > > > > Based on my reply to Christer Holm yesterday (see "LCN
Mapping"), this
> > > > > > proposed text needs a further update.  The supporting bearers
> > > contained by a
> > > > > > multiplexing termination can be ephemeral as well as physical.
> > > However, I
> > > > > > believe it would be essential that any ephemrals mentioned in a
MUX
> > > > > > descriptor already exist in the context, since their properties
are
> > > probably
> > > > > > not directly inferrable from those of the multiplexing
termination.
> > > > > >
> > > > > > Tom Taylor
> > > > > > taylor@nortelnetworks.com
> > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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


From daemon@ns.ietf.org  Tue Jan 22 13:10:19 2002
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 NAA02625
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:10:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02273
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:10:21 -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 MAA01207;
	Tue, 22 Jan 2002 12:51:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01178
	for <megaco@optimus.ietf.org>; Tue, 22 Jan 2002 12:51:20 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02193
	for <megaco@ietf.org>; Tue, 22 Jan 2002 12:51:17 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MHolS15760;
	Tue, 22 Jan 2002 12:50:47 -0500 (EST)
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 g0MHojS13638;
	Tue, 22 Jan 2002 12:50:45 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYN9S>; Tue, 22 Jan 2002 12:50:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC5@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Tue, 22 Jan 2002 12:50:42 -0500
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

The LCNs are specific to one application, not a general multiplexing issue.
(Although I suppose a similar issue arises with H.320, I also think H.320
would need its own annex.)  I think the mapping has to be described in Annex
M.4 for H.324.  The most obvious solution is as Christer indicated: an LCN
property in LocalControl. 

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Tuesday, January 22, 2002 2:35 AM
To: Christian Groves
Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>I don't think we can remove the whole chapter from the protocol at this
>stage. I agree with Tom that we can do some call flows in a seperate
>annex.

Oki.

>I'll add some text on the euphemeral terminations to the proposed
clarification.

So, we shouldn't say anything about the Stream Descriptors in the Mux
Termination? How they are mapped to the LCNs etc? Personally I don't
care if it's said in the core spec, or in a separate Annex, but I don't
understand what the purpose is to put stuff in the core which nobody can
use :)

Does anyone know if there has been any response on this issue from SG16?

Regards,

Christer Holmberg
Ericsson Finland


> 
> Regards, Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > >While we're on the topic of Annex M.4, I realized while reading it that
it
> > >improperly (I think) includes some control terminations in the
multiplex.
> > >This may be water under the bridge now -- too late to do anything about
it.
> > >
> > >Anyway, Christer is asking for more than I would put into the core
protocol
> > >specification.  We should probably create an Informational RFC
describing
> > >multiplex use with examples, just as we should publish an Informational
RFC
> > >giving example call flows.
> >
> > Why not removing the whole multiplex chapter from the core protocol,
> > then, and putting it in a separate Annex, or something? The way it's
> > defined now (even by adding the proposed changes) doesn't help anyone.
> > You simply can't implement multiplexing with the info you get from that
> > text (you don't know how to map the LCNs, which btw also are
> > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > enough in my opinion.
> >
> > I thought that the ITU people always wanted to specify everything very
> > much in detail :)
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Monday, January 21, 2002 12:52 AM
> > > To: Christian Groves
> > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > >
> > > Hi,
> > >
> > > >I think that the H.324 package probably needs to be updated to say
how
> > > >this is done. I don't think its a core H.248 issue.
> > >
> > > I agree. The idea was that this property would be defined in the H.324
> > > package, and then used within each stream descriptor in the Mux
> > > Termination.
> > >
> > > >Perhaps an IG note could be added for the H324 package? I'd like to
see a
> > > reply from the
> > > > H324 package authors on how they thought this was to be done.
> > >
> > > >Are there any updates you'd like to see to proposed text on
> > > MultiplexDescriptors that Tom posted?
> > >
> > > First, as Tom already mentioned, it should be updated so that it also
> > > includes emphemeral bearer terminations (RTP terminations, for
example).
> > >
> > > Second, it should in detail, on a message level, describe how the
> > > multiplexed connection is set up. Now it only says "use a stream
> > > descriptor" - which means everyone is going to understand it their own
> > > way, and we are going to have lots of interop problems when people
start
> > > implementing this :)
> > >
> > > Third, it should also describe in detail how the H.223 (or whatever
> > > multiplex method is used) descriptor is used, ie which terminations
are
> > > included etc, depending on on which "side" of the multiplexer the
> > > terminations are.
> > >
> > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > another discussion...
> > >
> > > I understand if you want to get this document ready before february,
but
> > > please let us do this correct from the beginning :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Christer Holmberg wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have read the document a few times, but even by having stream
> > > > > descriptors in the mux termination, I still don't understand how
each of
> > > > > those stream descriptors are mapped to specific LNCs. Is the
StreamID
> > > > > supposed to be the same as the LCN number, or how is the mapping
done?
> > > > >
> > > > > A very simple solution would be to add a "LCN property" (to the
H.324
> > > > > package, I assume) which would be used in the each stream
descriptor to
> > > > > specify to which LCN it is mapped.
> > > > >
> > > > > Comments?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > Tom-PT Taylor wrote:
> > > > > >
> > > > > > I mentioned that several of us have been discussing additional
text
> > > for
> > > > > > Multiplex Descriptors.  I have placed the proposed text as
marked up
> > > changes
> > > > > > in the Megaco FTP site.  According to your taste, you can
download
> > > > > >
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.doc
> > > > > > or
> > > > > >
> > >
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > x64K.pdf
> > > > > >
> > > > > > Based on my reply to Christer Holm yesterday (see "LCN
Mapping"), this
> > > > > > proposed text needs a further update.  The supporting bearers
> > > contained by a
> > > > > > multiplexing termination can be ephemeral as well as physical.
> > > However, I
> > > > > > believe it would be essential that any ephemrals mentioned in a
MUX
> > > > > > descriptor already exist in the context, since their properties
are
> > > probably
> > > > > > not directly inferrable from those of the multiplexing
termination.
> > > > > >
> > > > > > Tom Taylor
> > > > > > taylor@nortelnetworks.com
> > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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



From megaco-admin@ietf.org  Tue Jan 22 13:18:18 2002
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 NAA02998
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:18:18 -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 NAA02171;
	Tue, 22 Jan 2002 13:05:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02141
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:05:36 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02477
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:05:33 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MI53S02820;
	Tue, 22 Jan 2002 13:05:04 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MI51T17084;
	Tue, 22 Jan 2002 13:05:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY3L0>; Tue, 22 Jan 2002 13:05:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Tue, 22 Jan 2002 13:05:00 -0500
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

Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.  On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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


From daemon@ns.ietf.org  Tue Jan 22 13:18:19 2002
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 NAA03009
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:18:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02557
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:18:21 -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 NAA02171;
	Tue, 22 Jan 2002 13:05:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02141
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:05:36 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02477
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:05:33 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MI53S02820;
	Tue, 22 Jan 2002 13:05:04 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MI51T17084;
	Tue, 22 Jan 2002 13:05:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY3L0>; Tue, 22 Jan 2002 13:05:02 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Tue, 22 Jan 2002 13:05:00 -0500
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

Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.  On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 22 13:18:58 2002
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 NAA03027
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:18: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 JAA10138;
	Tue, 22 Jan 2002 09:41:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11654
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 23:53:10 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03656
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:53:06 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA12178;
	Tue, 22 Jan 2002 15:51:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA07863;
	Tue, 22 Jan 2002 15:53:08 +1100 (EST)
Message-ID: <3C4CF10E.94668923@ericsson.com.au>
Date: Tue, 22 Jan 2002 15:56:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

Reserve Group and Reserve Value give you the ability to support all
choices in a single stream. One use is in the case of negotiation but
the text doesn't limit you to this case. I see FID can be implemented
with reserve group because you can have seperate RTP in different groups
being part of the one logical stream. One group can specify DTMF,
another can specify audio codec and you can set  them to different
IP/port combinations if you wish but these will all be part of the same
stream descriptor.

If we map the FID groups into different H.248 stream IDs then we don't
have the problem with the ("m=") that was in the email that kicked off
this discussion. I don't see the reason why to use distinct terminations
for each m= line. In terms of specifying synchronisation, a statement
was already added in v1 7.1.4 "Multiple streams exiting a termination
shall be synchronized with each other."

Thus I don't a reason to make changes.

Regards, Christian

Terry L Anderson wrote:
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > Value". It allows the FID concept (group ID).
> 
> Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> thought they they simply allowed MGC to specify whether MGC should choose one choice or
> all choices it can support  among alternatives in a single stream (as well as reserving
> the resources for those in reply).  I've always assumed that this was simply a first
> step in negotiation and before the call was fully setup a single Group would be chosen
> by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> believe that a call will function with multiple groups still present?  If so, where do
> we specify the semantics?  With Local, would we mix the RTP received in each group?
> With Remote, would we send to ALL groups?
> 
> I think Reserve Group and Reserve Value are in the subject line only because the
> original question on this topic lead to the noticing the single m line restriction and
> FID was an additional reason for concern about this.  I should have changed the subject
> before continuing the discussion of multiple m lines.
> 
> I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> streams are grouped into a single media stream (or streams are coordinated such as video
> and audio for lip sync), but let's look at the grouping of RTP streams.  The
> archetypical example, given in the FID draft is where a single audio media stream is
> split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> sessions are combined into one.
> 
> I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> specifies that an inbound media stream is sent using all m lines in the flow (group).
> This is essentially equivalent to using distinct terminations for each m line and
> putting all the terminations in the same context with appropriate topology descriptor.
> FID does have some restrictions on the use of each m line that are a little different.
> It assumes that the flow will be encoded using a single codec and sent only to the m
> lines supporting that codec.  This seems to be intended to separate things like DTMF -
> if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> lines containing phone-event and not to those with only voice codecs.  I don't see how
> to indicate this behavior with additional terminations in the context, where it would
> seem that the DTMF tone should be sent to all indicated terminations with corresponding
> codec (that is, telephone-event to one AND codec encoded tone to other).
> 
> The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> single SDP description.  I would think that audio and video whould still need to be in
> distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> need some statement how to do this in H.248 since we do NOT want the entire session in a
> single Stream Descriptor.
> 
> Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> suggest other reasons we need it or how it would be used.
> 
> > With regards to sending
> > DTMF I thought that we used the signal mechanism for that. So I don't
> > think we need a change.
> 
> I believe that there is need for both mechanisms: sending DTMF through signaling channel
> (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> The RTP method is often preferable when DTMF is being passed through to far PSTN and
> there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> much easier to coordinate time when regenerating the tones in the media channel.  There
> is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> the DTMF at the correct time in the media channel.
> 
> >
> >
> > Regards, Christian
> >
> > Troy Cauble wrote:
> > >
> > > Terry L Anderson wrote:
> > > >
> > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > the statement was that multiple media streams in SDP should not occur in a
> > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > too restrictive.
> > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > distinct payload.  It also supports sending this payload to a different
> > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > again requires multiple media (m) lines in the SDP.
> > > >
> > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > bullets):
> > > >
> > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > single session description MUST NOT include more than one media description
> > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > distinct Stream Descriptors.
> > > >
> > > > Perhaps we could change this to read:
> > > >
> > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > single session description MUST NOT specify multiple streams.  This often means
> > > > that the session description will contain only a single media description ("m="
> > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > logical media stream but where payload packets may be sent to different
> > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > Descriptors.
> > > > --------
> > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > Informative References, but I think this helps clarify the intent with an
> > > > example.  We cannot refer to FID as it is not yet an RFC.
> > >
> > > I have no problem with the intent of this change.  You have to
> > > change the language to allow certain cases.  But the language
> > > is getting very fuzzy.
> > >
> > > How do I tell a "single, logical media stream" from "multiple streams"?
> > >
> > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > audio + video is "multiple streams"?
> > >
> > > When would an MG be handling multiple streams on a termination
> > > that are not "logically" related in some way?
> > >
> > > Doesn't this really mean I can put as many "streams" as I want
> > > in my SDP and have just one StreamDescriptor?
> > >
> > > -troy
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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


From daemon@ns.ietf.org  Tue Jan 22 13:18:59 2002
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 NAA03038
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:18:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02573
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:19:01 -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 JAA10138;
	Tue, 22 Jan 2002 09:41:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11654
	for <megaco@ns.ietf.org>; Mon, 21 Jan 2002 23:53:10 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03656
	for <megaco@ietf.org>; Mon, 21 Jan 2002 23:53:06 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA12178;
	Tue, 22 Jan 2002 15:51:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA07863;
	Tue, 22 Jan 2002 15:53:08 +1100 (EST)
Message-ID: <3C4CF10E.94668923@ericsson.com.au>
Date: Tue, 22 Jan 2002 15:56:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

Reserve Group and Reserve Value give you the ability to support all
choices in a single stream. One use is in the case of negotiation but
the text doesn't limit you to this case. I see FID can be implemented
with reserve group because you can have seperate RTP in different groups
being part of the one logical stream. One group can specify DTMF,
another can specify audio codec and you can set  them to different
IP/port combinations if you wish but these will all be part of the same
stream descriptor.

If we map the FID groups into different H.248 stream IDs then we don't
have the problem with the ("m=") that was in the email that kicked off
this discussion. I don't see the reason why to use distinct terminations
for each m= line. In terms of specifying synchronisation, a statement
was already added in v1 7.1.4 "Multiple streams exiting a termination
shall be synchronized with each other."

Thus I don't a reason to make changes.

Regards, Christian

Terry L Anderson wrote:
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > Value". It allows the FID concept (group ID).
> 
> Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> thought they they simply allowed MGC to specify whether MGC should choose one choice or
> all choices it can support  among alternatives in a single stream (as well as reserving
> the resources for those in reply).  I've always assumed that this was simply a first
> step in negotiation and before the call was fully setup a single Group would be chosen
> by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> believe that a call will function with multiple groups still present?  If so, where do
> we specify the semantics?  With Local, would we mix the RTP received in each group?
> With Remote, would we send to ALL groups?
> 
> I think Reserve Group and Reserve Value are in the subject line only because the
> original question on this topic lead to the noticing the single m line restriction and
> FID was an additional reason for concern about this.  I should have changed the subject
> before continuing the discussion of multiple m lines.
> 
> I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> streams are grouped into a single media stream (or streams are coordinated such as video
> and audio for lip sync), but let's look at the grouping of RTP streams.  The
> archetypical example, given in the FID draft is where a single audio media stream is
> split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> sessions are combined into one.
> 
> I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> specifies that an inbound media stream is sent using all m lines in the flow (group).
> This is essentially equivalent to using distinct terminations for each m line and
> putting all the terminations in the same context with appropriate topology descriptor.
> FID does have some restrictions on the use of each m line that are a little different.
> It assumes that the flow will be encoded using a single codec and sent only to the m
> lines supporting that codec.  This seems to be intended to separate things like DTMF -
> if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> lines containing phone-event and not to those with only voice codecs.  I don't see how
> to indicate this behavior with additional terminations in the context, where it would
> seem that the DTMF tone should be sent to all indicated terminations with corresponding
> codec (that is, telephone-event to one AND codec encoded tone to other).
> 
> The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> single SDP description.  I would think that audio and video whould still need to be in
> distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> need some statement how to do this in H.248 since we do NOT want the entire session in a
> single Stream Descriptor.
> 
> Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> suggest other reasons we need it or how it would be used.
> 
> > With regards to sending
> > DTMF I thought that we used the signal mechanism for that. So I don't
> > think we need a change.
> 
> I believe that there is need for both mechanisms: sending DTMF through signaling channel
> (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> The RTP method is often preferable when DTMF is being passed through to far PSTN and
> there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> much easier to coordinate time when regenerating the tones in the media channel.  There
> is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> the DTMF at the correct time in the media channel.
> 
> >
> >
> > Regards, Christian
> >
> > Troy Cauble wrote:
> > >
> > > Terry L Anderson wrote:
> > > >
> > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > the statement was that multiple media streams in SDP should not occur in a
> > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > too restrictive.
> > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > distinct payload.  It also supports sending this payload to a different
> > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > again requires multiple media (m) lines in the SDP.
> > > >
> > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > bullets):
> > > >
> > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > single session description MUST NOT include more than one media description
> > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > distinct Stream Descriptors.
> > > >
> > > > Perhaps we could change this to read:
> > > >
> > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > single session description MUST NOT specify multiple streams.  This often means
> > > > that the session description will contain only a single media description ("m="
> > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > logical media stream but where payload packets may be sent to different
> > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > Descriptors.
> > > > --------
> > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > Informative References, but I think this helps clarify the intent with an
> > > > example.  We cannot refer to FID as it is not yet an RFC.
> > >
> > > I have no problem with the intent of this change.  You have to
> > > change the language to allow certain cases.  But the language
> > > is getting very fuzzy.
> > >
> > > How do I tell a "single, logical media stream" from "multiple streams"?
> > >
> > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > audio + video is "multiple streams"?
> > >
> > > When would an MG be handling multiple streams on a termination
> > > that are not "logically" related in some way?
> > >
> > > Doesn't this really mean I can put as many "streams" as I want
> > > in my SDP and have just one StreamDescriptor?
> > >
> > > -troy
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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



From megaco-admin@ietf.org  Tue Jan 22 13:37:22 2002
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 NAA04029
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:37:22 -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 NAA02644;
	Tue, 22 Jan 2002 13:20:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02612
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:20:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03117
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:20:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIJgS05850;
	Tue, 22 Jan 2002 13:19:42 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIJdT17994;
	Tue, 22 Jan 2002 13:19:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY373>; Tue, 22 Jan 2002 13:19:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] DOUBT ABUOT ACK
Date: Tue, 22 Jan 2002 13:19:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A371.59E5D130"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A371.59E5D130
Content-Type: text/plain;
	charset="ISO-8859-1"

ACK is used only when you have unreliable transport such as UDP, and is
needed to assure delivery of replies.  REP, of course, assures both that the
request has been delivered (a function that can also be performed by
reliable transport) and that the application has recognized and processed
it.  PEND can also be interpreted as functioning both at the transport and
the application level. 

-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Friday, January 18, 2002 1:36 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT ABUOT ACK



hi

   Every transaction request should be responded with ACK/REP/PEND. But in
the example given in RFC, 
places where ACK is expected also reply is sent. Why is it happened here so
-  or is that the correct sequence .. ?

sree 


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

------_=_NextPart_001_01C1A371.59E5D130
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] DOUBT ABUOT ACK</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>ACK is used only when you have unreliable transport =
such as UDP, and is needed to assure delivery of replies.&nbsp; REP, of =
course, assures both that the request has been delivered (a function =
that can also be performed by reliable transport) and that the =
application has recognized and processed it.&nbsp; PEND can also be =
interpreted as functioning both at the transport and the application =
level. </FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: sree gk [<A =
HREF=3D"mailto:sgk73@rediffmail.com">mailto:sgk73@rediffmail.com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Sent: Friday, January 18, 2002 1:36 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] DOUBT ABUOT ACK</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>hi</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Every transaction request should be =
responded with ACK/REP/PEND. But in the example given in RFC, </FONT>
<BR><FONT SIZE=3D2>places where ACK is expected also reply is sent. Why =
is it happened here so -&nbsp; or is that the correct sequence .. =
?</FONT>
</P>

<P><FONT SIZE=3D2>sree </FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A371.59E5D130--

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


From daemon@ns.ietf.org  Tue Jan 22 13:37:22 2002
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 NAA04040
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:37:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA03542
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:37:25 -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 NAA02644;
	Tue, 22 Jan 2002 13:20:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02612
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:20:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03117
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:20:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIJgS05850;
	Tue, 22 Jan 2002 13:19:42 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIJdT17994;
	Tue, 22 Jan 2002 13:19:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY373>; Tue, 22 Jan 2002 13:19:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] DOUBT ABUOT ACK
Date: Tue, 22 Jan 2002 13:19:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A371.59E5D130"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A371.59E5D130
Content-Type: text/plain;
	charset="ISO-8859-1"

ACK is used only when you have unreliable transport such as UDP, and is
needed to assure delivery of replies.  REP, of course, assures both that the
request has been delivered (a function that can also be performed by
reliable transport) and that the application has recognized and processed
it.  PEND can also be interpreted as functioning both at the transport and
the application level. 

-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Friday, January 18, 2002 1:36 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT ABUOT ACK



hi

   Every transaction request should be responded with ACK/REP/PEND. But in
the example given in RFC, 
places where ACK is expected also reply is sent. Why is it happened here so
-  or is that the correct sequence .. ?

sree 


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

------_=_NextPart_001_01C1A371.59E5D130
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] DOUBT ABUOT ACK</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>ACK is used only when you have unreliable transport =
such as UDP, and is needed to assure delivery of replies.&nbsp; REP, of =
course, assures both that the request has been delivered (a function =
that can also be performed by reliable transport) and that the =
application has recognized and processed it.&nbsp; PEND can also be =
interpreted as functioning both at the transport and the application =
level. </FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: sree gk [<A =
HREF=3D"mailto:sgk73@rediffmail.com">mailto:sgk73@rediffmail.com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Sent: Friday, January 18, 2002 1:36 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] DOUBT ABUOT ACK</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>hi</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Every transaction request should be =
responded with ACK/REP/PEND. But in the example given in RFC, </FONT>
<BR><FONT SIZE=3D2>places where ACK is expected also reply is sent. Why =
is it happened here so -&nbsp; or is that the correct sequence .. =
?</FONT>
</P>

<P><FONT SIZE=3D2>sree </FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A371.59E5D130--

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



From megaco-admin@ietf.org  Tue Jan 22 13:47:53 2002
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 NAA04357
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:47:52 -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 NAA02790;
	Tue, 22 Jan 2002 13:27:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02763
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:27:12 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03522
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:27:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIPuS06918;
	Tue, 22 Jan 2002 13:25:57 -0500 (EST)
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 g0MIPsS15857;
	Tue, 22 Jan 2002 13:25:54 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYPCK>; Tue, 22 Jan 2002 13:25:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: megaco@ietf.org
Cc: "'Matt Holdrege'" <matt.holdrege@verizon.net>,
        Narendra Babu
	 <narendra@dexceldesigns.com>,
        "'Kaul, Bharat'" <bharat@trillium.com>
Subject: RE: [Megaco] Regarding IPsec and interim AH
Date: Tue, 22 Jan 2002 13:25:52 -0500
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

Would people accept deprecation?  How many implementations are out there
using interim AH and unable to switch to full IPSEC?  People can reply to me
privately if they wish.

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Friday, January 18, 2002 6:12 PM
To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
Subject: RE: [Megaco] Regarding IPsec and interim AH


I remember long time back on this list it was being discussed that AH scheme
will be deprecated. However, I still see its mention in v2.

- Bharat

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Friday, January 18, 2002 5:26 AM
To: Narendra Babu; megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH


At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


_______________________________________________
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


From daemon@ns.ietf.org  Tue Jan 22 13:47:53 2002
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 NAA04366
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:47:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA03992
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:47:55 -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 NAA02790;
	Tue, 22 Jan 2002 13:27:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02763
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:27:12 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03522
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:27:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MIPuS06918;
	Tue, 22 Jan 2002 13:25:57 -0500 (EST)
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 g0MIPsS15857;
	Tue, 22 Jan 2002 13:25:54 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYPCK>; Tue, 22 Jan 2002 13:25:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEC9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: megaco@ietf.org
Cc: "'Matt Holdrege'" <matt.holdrege@verizon.net>,
        Narendra Babu
	 <narendra@dexceldesigns.com>,
        "'Kaul, Bharat'" <bharat@trillium.com>
Subject: RE: [Megaco] Regarding IPsec and interim AH
Date: Tue, 22 Jan 2002 13:25:52 -0500
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

Would people accept deprecation?  How many implementations are out there
using interim AH and unable to switch to full IPSEC?  People can reply to me
privately if they wish.

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Friday, January 18, 2002 6:12 PM
To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
Subject: RE: [Megaco] Regarding IPsec and interim AH


I remember long time back on this list it was being discussed that AH scheme
will be deprecated. However, I still see its mention in v2.

- Bharat

-----Original Message-----
From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
Sent: Friday, January 18, 2002 5:26 AM
To: Narendra Babu; megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH


At 10:36 PM 1/17/2002, Narendra Babu wrote:
>Hi all,
>
>         I am a newbie to this mail list as well as megaco.
>
>We are developing a megaco stack.My doubt is whether
>we have to implement full IPsec(RFC 2401-RFC 2411) or
>only interim AH as a secrity support? Please clarify  this as early as 
>possible.

I always thought interim AH wasn't a good idea and I think it is now 
clarified as a temporary scheme that is no longer needed. So your choices 
are IPsec or perhaps some less onerous scheme such as SSH.

Anybody else?


_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 22 13:54:47 2002
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 NAA04791
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:54:47 -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 NAA03773;
	Tue, 22 Jan 2002 13:41:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03742
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:41:28 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04190
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:41:23 -0500 (EST)
From: prjain@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MIg5E25591
	for <megaco@ietf.org>; Wed, 23 Jan 2002 00:12:05 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.006692E3 ; Wed, 23 Jan 2002 00:10:22 +0530
X-Lotus-FromDomain: HSS
To: "megaco@ietf.org" <megaco@ietf.org>
Message-ID: <65256B49.006682AD.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 00:11:35 +0530
Subject: Re: [Megaco] Cancel ServiceChange Graceful
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x"
Content-Disposition: inline
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

--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




Hi Chuong/list,

Answering to your first question, we think that there can be two interpretations
here.

1.  One  is that "SC Restart w/Service Restorted and ROOT"
   means "SC Graceful w/Delay is being cancelled" and MGC should behave
   accordingly.

2.  The other view may be that we are trying to overload the reason as "Service
Restored" for two different scenarios.
     The service change reason as "Service Restored" can be used by MG in one
scenario, wherein MG comes up afresh with no calls running over all the
associated terminations but they all are in  In-service state.
     The second scenario (what we are currently discussing) in which calls are
still active and MG just wants to cancel the last generated "Graceful Shutdown"
request.
     Due to the overloading of the reason as "Service Restored", how would MGC
come to know about the state of those terminations, which were earlier
"out-of-service" even before the "graceful shutdown" request was generated.


The above two bullets clearly convey that one should either define one more
"Service Change Method" (may be 'cancel-graceful" as suggested by you and use
reason as "Service Restored") or use method as "Restart" and use reason "Service
Restored" but define a new service change reason for Cold Start of MG.

Thus we can have the following reason-method combinations.
1. Restart - Cold Start   (no configuration data preserved, no calls)
2. Restart - Cold Boot   (configuration data preserved, no calls)
3. Restart - Warm Boot  (configuration data preserved, calls preserved,
transactions may be lost)
4. Restart - Service Restored   (configuration data preserved, calls preserved,
cacelling the "graceful shutdown" request and the last set of "In-service"
terminations, before "graceful shutdown" was initiated, are still In-service)

Please comment.

Thanks and Regards,
Prashant Jain
Vivek Bansal


>
> "Chuong N. Nguyen" wrote:

> >
> >
> > MG sends SC Graceful w/Delay and terminationID=ROOT.
> >
> > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > assume that
> > 1) SC Graceful w/Delay is being cancelled?
> > 2) All terminations are back In Service?  Even the ones that were
> > originally OOS before the SC Graceful.
> >
> >
> >    1) Graceful - indicates that the specified Terminations will be
> > taken
> >       out of service after the specified ServiceChangeDelay;
> > established
> >       connections are not yet affected, but the Media Gateway
> > Controller
> >       should refrain from establishing new connections and should
> >       attempt to gracefully tear down existing connections on the
> >       Termination(s) affected by the serviceChange command. The MG
> >       should set termination serviceState at the expiry of
> >       ServiceChangeDelay or the removal of the termination from an
> >       active context (whichever is first), to "out of service".
> >
> >
> > How should MGC implementation intepret the above highlighted
> > statement?
> > Does this mean that MGC should not try to gracefully tear down
> > existing connections
> > before Delay timer expired?
> >
> > But I think the above statement is telling MGC to try and gracefully
> > tear down
> > existing connections before Delay timer expired.
> >
> > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > until
> > Delay timer expired before it tries to tear down existing connections.
> >
> > But after Delay timer expired, MG will put all terminations out of
> > service.
> > Therefore there is no such thing as MGC gracefully tearing down
> > existing connections.
> >
> >
> > Christian Groves wrote:
> >
> > > I don't see that we need to add anything. Why can't the MG just
> > > issue a
> > > SC with Restart, Service Restored? The specification already allows
> > > the
> > > MG to do this.
> > >
> > > Regards, Christian
> > >
> > > "Chuong N. Nguyen" wrote:
> > > >
> > > > Hi Tom
> > > >
> > > > What are the possibilites of defining a mechanism of cancelling
> > > > ServiceChange Graceful?
> > > > That is MG send SC Graceful w/Delay=time.
> > > > Before time expired, MG wants to cancel this ServiceChange.
> > > >
> > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > Graceful cancelled"?
> > > > 2) Done in V2 - new SC Method or Reason?
> > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > >
> > > >
> > > > Thanks
> > > > Chuong
> > > >
> > > >
> > > >
> > > > --
> > > >   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 ****
> >
> >

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




--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/html; 
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFkb2N0eXBlIGh0bWwgcHVibGljICItLy93M2MvL2R0ZCBodG1sIDQuMCB0cmFuc2l0aW9uYWwv
L2VuIj4NCjxodG1sPg0KJm5ic3A7DQo8YnI+TWF5YmUgSSZuYnNwO25lZWQgYSBjbGFyaWZpY2F0
aW9uIG9uIHdoYXQNCjxibG9ja3F1b3RlPnNob3VsZCBhdHRlbXB0IHRvIGdyYWNlZnVsbHkgdGVh
ciBkb3duIGV4aXN0aW5nIGNvbm5lY3Rpb25zDQpvbiB0aGUNCjxicj5UZXJtaW5hdGlvbihzKSBh
ZmZlY3RlZCBieSB0aGUgc2VydmljZUNoYW5nZSBjb21tYW5kLjwvYmxvY2txdW90ZT4NCkRvZXMg
dGhlIE1HQyBqdXN0IGRvIGEgQ0FNUF9PTi1PT1MgLSB0aGF0IGlzIHdhaXQgdW50aWwgdGhlIHN1
YmNyaWJlcnMNCmhhbmcgdXAgbm9ybWFsbHkgYW5kIHRoZW4NCjxicj5wdXQgdGhlIHRlcm1pbmF0
aW9uIE9PUyBhZnRlciBzdWJzY3JpYmVycyBoYW5nIHVwIChiZWZvcmUgZGVsYXkgdGltZXINCmV4
cGlyZWQpPw0KPHA+T3IgTUdDIHN0YXJ0cyByZWxlYXNpbmcgdGhlIGNhbGxzIHdoZXRoZXIgdGhl
IHN1YnNjcmliZXJzIGhhbmcgdXAgb3INCm5vdD8NCjxwPlRoYW5rcw0KPGJyPkNodW9uZw0KPHA+
Q2hyaXN0aWFuIEdyb3ZlcyB3cm90ZToNCjxibG9ja3F1b3RlIFRZUEU9Q0lURT5UaGVyZSBpcyBh
IHRpbWluZyBkZXBlbmRlbmN5IGhlcmUuIElmIHRoZSBNRyBpc3N1ZXMNCmEgU0MgR3JhY2VmdWwg
dGhlbg0KPGJyPnRoZSBNR0Mgd2lsbCBhY3Qgb24gaXQuIFRoZXJlIHdpbGwgYmUgYSBmaW5pdGUg
dGltZSB0aGF0IHRoZSBNR0MNCjxicj5vcGVyYXRlcyB1bmRlciBncmFjZWZ1bCBtb2RlLiBJZiBh
IFNDIFJlc3RhcnQgdy9TZXJ2aWNlIFJlc3RvcmVkIG9yDQo8YnI+U2VydmljZSBDaGFuZ2UgQ2Fu
Y2VsIGlzIGlzc3VlZCBkdXJpbmcgdGhlIGdyYWNlZnVsIHRoZSBNR0MgY2FuJ3QgdW5kbw0KPGJy
PndoYXQgaXQgaGFkIGRvbmUgaW4gdGhhdCBmaW5pdGUgdGltZSBidXQgdGhlIGNvbm5lY3Rpb25z
IHRoYXQgc3RheWVkDQp1cA0KPGJyPmNhbiByZW1haW4gdXAuIElmIHRoZSBTQyBSZXN0YXJ0IHcv
c2VydmljZSByZXN0b3JlZCBvciBTZXJ2aWNlIENoYW5nZQ0KPGJyPkNhbmNlbCBpcyBub3QgcmVj
ZWl2ZWQgYmVmb3JlIHRoZSBkZWxheSB0aW1lcyBvdXQgdGhlbiBpdCBwcmV0dHkgdG9vDQo8YnI+
bGF0ZSBhcyB0aGUgdGVybWluYXRpb25zIHdpbGwgYmUgdG9ybiBkb3duLg0KPHA+SSBkb24ndCB1
bmRlcnN0YW5kIHdoeSB5b3Ugc2F5IHRoYXQgdGhlIE1HQyBtdXN0IHdhaXQgdW50aWwgdGhlDQo8
YnI+c2VydmljZWNoYW5nZSBkZWxheSB0aW1lc291dHMgYmVmb3JlIGdyYWNlZnVsbHkgdGVhcmlu
ZyBkb3duDQo8YnI+Y29ubmVjdGlvbnM/DQo8cD5DaHJpc3RpYW4NCjxwPiJDaHVvbmcgTi4gTmd1
eWVuIiB3cm90ZToNCjxicj4+DQo8YnI+Pg0KPGJyPj4gTUcgc2VuZHMgU0MgR3JhY2VmdWwgdy9E
ZWxheSBhbmQgdGVybWluYXRpb25JRD1ST09ULg0KPGJyPj4NCjxicj4+IElmIE1HIHNlbmRzIFND
IFJlc3RhcnQgdy9TZXJ2aWNlIFJlc3RvcnRlZCBhbmQgUk9PVCwgZG9lcyB0aGUgTUdDDQo8YnI+
PiBhc3N1bWUgdGhhdA0KPGJyPj4gMSkgU0MgR3JhY2VmdWwgdy9EZWxheSBpcyBiZWluZyBjYW5j
ZWxsZWQ/DQo8YnI+PiAyKSBBbGwgdGVybWluYXRpb25zIGFyZSBiYWNrIEluIFNlcnZpY2U/Jm5i
c3A7IEV2ZW4gdGhlIG9uZXMgdGhhdA0Kd2VyZQ0KPGJyPj4gb3JpZ2luYWxseSBPT1MgYmVmb3Jl
IHRoZSBTQyBHcmFjZWZ1bC4NCjxicj4+DQo8YnI+Pg0KPGJyPj4mbmJzcDsmbmJzcDsmbmJzcDsg
MSkgR3JhY2VmdWwgLSBpbmRpY2F0ZXMgdGhhdCB0aGUgc3BlY2lmaWVkIFRlcm1pbmF0aW9ucw0K
d2lsbCBiZQ0KPGJyPj4gdGFrZW4NCjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IG91dCBvZiBzZXJ2aWNlIGFmdGVyIHRoZSBzcGVjaWZpZWQNClNlcnZpY2VDaGFuZ2VE
ZWxheTsNCjxicj4+IGVzdGFibGlzaGVkDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBjb25uZWN0aW9ucyBhcmUgbm90IHlldCBhZmZlY3RlZCwNCmJ1dCB0aGUgTWVk
aWEgR2F0ZXdheQ0KPGJyPj4gQ29udHJvbGxlcg0KPGJyPj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgc2hvdWxkIHJlZnJhaW4gZnJvbSBlc3RhYmxpc2hpbmcNCm5ldyBjb25u
ZWN0aW9ucyBhbmQgc2hvdWxkDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBhdHRlbXB0IHRvIGdyYWNlZnVsbHkgdGVhciBkb3duDQpleGlzdGluZyBjb25uZWN0aW9u
cyBvbiB0aGUNCjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRlcm1p
bmF0aW9uKHMpIGFmZmVjdGVkIGJ5IHRoZQ0Kc2VydmljZUNoYW5nZSBjb21tYW5kLiBUaGUgTUcN
Cjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNob3VsZCBzZXQgdGVy
bWluYXRpb24gc2VydmljZVN0YXRlDQphdCB0aGUgZXhwaXJ5IG9mDQo8YnI+PiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBTZXJ2aWNlQ2hhbmdlRGVsYXkgb3IgdGhlIHJlbW92
YWwNCm9mIHRoZSB0ZXJtaW5hdGlvbiBmcm9tIGFuDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBhY3RpdmUgY29udGV4dCAod2hpY2hldmVyIGlzDQpmaXJzdCksIHRv
ICJvdXQgb2Ygc2VydmljZSIuDQo8YnI+Pg0KPGJyPj4NCjxicj4+IEhvdyBzaG91bGQgTUdDIGlt
cGxlbWVudGF0aW9uIGludGVwcmV0IHRoZSBhYm92ZSBoaWdobGlnaHRlZA0KPGJyPj4gc3RhdGVt
ZW50Pw0KPGJyPj4gRG9lcyB0aGlzIG1lYW4gdGhhdCBNR0Mgc2hvdWxkIG5vdCB0cnkgdG8gZ3Jh
Y2VmdWxseSB0ZWFyIGRvd24NCjxicj4+IGV4aXN0aW5nIGNvbm5lY3Rpb25zDQo8YnI+PiBiZWZv
cmUgRGVsYXkgdGltZXIgZXhwaXJlZD8NCjxicj4+DQo8YnI+PiBCdXQgSSB0aGluayB0aGUgYWJv
dmUgc3RhdGVtZW50IGlzIHRlbGxpbmcgTUdDIHRvIHRyeSBhbmQgZ3JhY2VmdWxseQ0KPGJyPj4g
dGVhciBkb3duDQo8YnI+PiBleGlzdGluZyBjb25uZWN0aW9ucyBiZWZvcmUgRGVsYXkgdGltZXIg
ZXhwaXJlZC4NCjxicj4+DQo8YnI+PiBUbyBiZSBhYmxlIHRvIGNhbmNlbCBHcmFjZWZ1bCB3L0Rl
bGF5LCBpdCBzZWVtcyB0aGF0IE1HQyBuZWVkcyB0bw0Kd2FpdA0KPGJyPj4gdW50aWwNCjxicj4+
IERlbGF5IHRpbWVyIGV4cGlyZWQgYmVmb3JlIGl0IHRyaWVzIHRvIHRlYXIgZG93biBleGlzdGlu
ZyBjb25uZWN0aW9ucy4NCjxicj4+DQo8YnI+PiBCdXQgYWZ0ZXIgRGVsYXkgdGltZXIgZXhwaXJl
ZCwgTUcgd2lsbCBwdXQgYWxsIHRlcm1pbmF0aW9ucyBvdXQgb2YNCjxicj4+IHNlcnZpY2UuDQo8
YnI+PiBUaGVyZWZvcmUgdGhlcmUgaXMgbm8gc3VjaCB0aGluZyBhcyBNR0MgZ3JhY2VmdWxseSB0
ZWFyaW5nIGRvd24NCjxicj4+IGV4aXN0aW5nIGNvbm5lY3Rpb25zLg0KPGJyPj4NCjxicj4+DQo8
YnI+PiBDaHJpc3RpYW4gR3JvdmVzIHdyb3RlOg0KPGJyPj4NCjxicj4+ID4gSSBkb24ndCBzZWUg
dGhhdCB3ZSBuZWVkIHRvIGFkZCBhbnl0aGluZy4gV2h5IGNhbid0IHRoZSBNRyBqdXN0DQo8YnI+
PiA+IGlzc3VlIGENCjxicj4+ID4gU0Mgd2l0aCBSZXN0YXJ0LCBTZXJ2aWNlIFJlc3RvcmVkPyBU
aGUgc3BlY2lmaWNhdGlvbiBhbHJlYWR5IGFsbG93cw0KPGJyPj4gPiB0aGUNCjxicj4+ID4gTUcg
dG8gZG8gdGhpcy4NCjxicj4+ID4NCjxicj4+ID4gUmVnYXJkcywgQ2hyaXN0aWFuDQo8YnI+PiA+
DQo8YnI+PiA+ICJDaHVvbmcgTi4gTmd1eWVuIiB3cm90ZToNCjxicj4+ID4gPg0KPGJyPj4gPiA+
IEhpIFRvbQ0KPGJyPj4gPiA+DQo8YnI+PiA+ID4gV2hhdCBhcmUgdGhlIHBvc3NpYmlsaXRlcyBv
ZiBkZWZpbmluZyBhIG1lY2hhbmlzbSBvZiBjYW5jZWxsaW5nDQo8YnI+PiA+ID4gU2VydmljZUNo
YW5nZSBHcmFjZWZ1bD8NCjxicj4+ID4gPiBUaGF0IGlzIE1HIHNlbmQgU0MgR3JhY2VmdWwgdy9E
ZWxheT10aW1lLg0KPGJyPj4gPiA+IEJlZm9yZSB0aW1lIGV4cGlyZWQsIE1HIHdhbnRzIHRvIGNh
bmNlbCB0aGlzIFNlcnZpY2VDaGFuZ2UuDQo8YnI+PiA+ID4NCjxicj4+ID4gPiAxKSBDYW4gdGhp
cyBiZSBkb25lIGluIFYxIGJ5IGFkZGluZyBhIG5ldyBTQyBSZWFzb24gbGlrZSAiOTE2DQpTQw0K
PGJyPj4gPiA+IEdyYWNlZnVsIGNhbmNlbGxlZCI/DQo8YnI+PiA+ID4gMikgRG9uZSBpbiBWMiAt
IG5ldyBTQyBNZXRob2Qgb3IgUmVhc29uPw0KPGJyPj4gPiA+IDMpIFNob3VsZCBiZSBjb3ZlcmVk
IGluIGRyYWZ0LWhzcy1tZWdhY28tY29udHJvbC1hc3NvY2lhdGlvbj8NCjxicj4+ID4gPg0KPGJy
Pj4gPiA+DQo8YnI+PiA+ID4gVGhhbmtzDQo8YnI+PiA+ID4gQ2h1b25nDQo8YnI+PiA+ID4NCjxi
cj4+ID4gPg0KPGJyPj4gPiA+DQo8YnI+PiA+ID4gLS0NCjxicj4+ID4gPiZuYnNwOyZuYnNwOyBB
bGNhdGVsIFVTQSwgSW5jJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpJbnRlcm5ldDoNCjxicj4+ID4gQ2h1b25n
Lk5ndXllbkB1c2EuYWxjYXRlbC5jb20NCjxicj4+ID4gPiZuYnNwOyZuYnNwOyAxMDAwIENvaXQg
Um9hZCBQbGFubywgVGV4YXMgNzUwNzUmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNClBob25lOiZuYnNwOyZuYnNwOyZuYnNwOyAoOTcy
KQ0KPGJyPj4gPiA1MTktNDYxMw0KPGJyPj4gPiA+Jm5ic3A7Jm5ic3A7ICoqKiogVGhlIG9waW5p
b25zIGV4cHJlc3NlZCBhcmUgbm90IHRob3NlIG9mIEFsY2F0ZWwNClVTQSwgSW5jDQo8YnI+PiA+
ICoqKioNCjxicj4+ID4gPg0KPGJyPj4gPiA+DQo8YnI+Pg0KPGJyPj4gLS0NCjxicj4+Jm5ic3A7
Jm5ic3A7IEFsY2F0ZWwgVVNBLCBJbmMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCkludGVybmV0OiBDaHVvbmcu
Tmd1eWVuQHVzYS5hbGNhdGVsLmNvbQ0KPGJyPj4mbmJzcDsmbmJzcDsgMTAwMCBDb2l0IFJvYWQg
UGxhbm8sIFRleGFzIDc1MDc1Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpQaG9uZTombmJzcDsmbmJzcDsmbmJzcDsgKDk3MikgNTE5
LTQ2MTMNCjxicj4+Jm5ic3A7Jm5ic3A7ICoqKiogVGhlIG9waW5pb25zIGV4cHJlc3NlZCBhcmUg
bm90IHRob3NlIG9mIEFsY2F0ZWwNClVTQSwgSW5jICoqKioNCjxicj4+DQo8YnI+PjwvYmxvY2tx
dW90ZT4NCg0KPHByZT4tLSZuYnNwOw0KJm5ic3A7IEFsY2F0ZWwgVVNBLCBJbmMmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgSW50ZXJuZXQ6IENodW9uZy5OZ3V5ZW5AdXNhLmFsY2F0ZWwuY29tDQombmJzcDsgMTAw
MCBDb2l0IFJvYWQgUGxhbm8sIFRleGFzIDc1MDc1Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBob25lOiZuYnNwOyZuYnNwOyZuYnNw
OyAoOTcyKSA1MTktNDYxMw0KJm5ic3A7ICoqKiogVGhlIG9waW5pb25zIGV4cHJlc3NlZCBhcmUg
bm90IHRob3NlIG9mIEFsY2F0ZWwgVVNBLCBJbmMgKioqKjwvcHJlPg0KJm5ic3A7PC9odG1sPg0K
DQo=

--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline








"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."




--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x--


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


From daemon@ns.ietf.org  Tue Jan 22 13:54:57 2002
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 NAA04800
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 13:54:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA04416
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 13:54:50 -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 NAA03773;
	Tue, 22 Jan 2002 13:41:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03742
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:41:28 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04190
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:41:23 -0500 (EST)
From: prjain@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MIg5E25591
	for <megaco@ietf.org>; Wed, 23 Jan 2002 00:12:05 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.006692E3 ; Wed, 23 Jan 2002 00:10:22 +0530
X-Lotus-FromDomain: HSS
To: "megaco@ietf.org" <megaco@ietf.org>
Message-ID: <65256B49.006682AD.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 00:11:35 +0530
Subject: Re: [Megaco] Cancel ServiceChange Graceful
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x"
Content-Disposition: inline
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

--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline




Hi Chuong/list,

Answering to your first question, we think that there can be two interpretations
here.

1.  One  is that "SC Restart w/Service Restorted and ROOT"
   means "SC Graceful w/Delay is being cancelled" and MGC should behave
   accordingly.

2.  The other view may be that we are trying to overload the reason as "Service
Restored" for two different scenarios.
     The service change reason as "Service Restored" can be used by MG in one
scenario, wherein MG comes up afresh with no calls running over all the
associated terminations but they all are in  In-service state.
     The second scenario (what we are currently discussing) in which calls are
still active and MG just wants to cancel the last generated "Graceful Shutdown"
request.
     Due to the overloading of the reason as "Service Restored", how would MGC
come to know about the state of those terminations, which were earlier
"out-of-service" even before the "graceful shutdown" request was generated.


The above two bullets clearly convey that one should either define one more
"Service Change Method" (may be 'cancel-graceful" as suggested by you and use
reason as "Service Restored") or use method as "Restart" and use reason "Service
Restored" but define a new service change reason for Cold Start of MG.

Thus we can have the following reason-method combinations.
1. Restart - Cold Start   (no configuration data preserved, no calls)
2. Restart - Cold Boot   (configuration data preserved, no calls)
3. Restart - Warm Boot  (configuration data preserved, calls preserved,
transactions may be lost)
4. Restart - Service Restored   (configuration data preserved, calls preserved,
cacelling the "graceful shutdown" request and the last set of "In-service"
terminations, before "graceful shutdown" was initiated, are still In-service)

Please comment.

Thanks and Regards,
Prashant Jain
Vivek Bansal


>
> "Chuong N. Nguyen" wrote:

> >
> >
> > MG sends SC Graceful w/Delay and terminationID=ROOT.
> >
> > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > assume that
> > 1) SC Graceful w/Delay is being cancelled?
> > 2) All terminations are back In Service?  Even the ones that were
> > originally OOS before the SC Graceful.
> >
> >
> >    1) Graceful - indicates that the specified Terminations will be
> > taken
> >       out of service after the specified ServiceChangeDelay;
> > established
> >       connections are not yet affected, but the Media Gateway
> > Controller
> >       should refrain from establishing new connections and should
> >       attempt to gracefully tear down existing connections on the
> >       Termination(s) affected by the serviceChange command. The MG
> >       should set termination serviceState at the expiry of
> >       ServiceChangeDelay or the removal of the termination from an
> >       active context (whichever is first), to "out of service".
> >
> >
> > How should MGC implementation intepret the above highlighted
> > statement?
> > Does this mean that MGC should not try to gracefully tear down
> > existing connections
> > before Delay timer expired?
> >
> > But I think the above statement is telling MGC to try and gracefully
> > tear down
> > existing connections before Delay timer expired.
> >
> > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > until
> > Delay timer expired before it tries to tear down existing connections.
> >
> > But after Delay timer expired, MG will put all terminations out of
> > service.
> > Therefore there is no such thing as MGC gracefully tearing down
> > existing connections.
> >
> >
> > Christian Groves wrote:
> >
> > > I don't see that we need to add anything. Why can't the MG just
> > > issue a
> > > SC with Restart, Service Restored? The specification already allows
> > > the
> > > MG to do this.
> > >
> > > Regards, Christian
> > >
> > > "Chuong N. Nguyen" wrote:
> > > >
> > > > Hi Tom
> > > >
> > > > What are the possibilites of defining a mechanism of cancelling
> > > > ServiceChange Graceful?
> > > > That is MG send SC Graceful w/Delay=time.
> > > > Before time expired, MG wants to cancel this ServiceChange.
> > > >
> > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > Graceful cancelled"?
> > > > 2) Done in V2 - new SC Method or Reason?
> > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > >
> > > >
> > > > Thanks
> > > > Chuong
> > > >
> > > >
> > > >
> > > > --
> > > >   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 ****
> >
> >

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




--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/html; 
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFkb2N0eXBlIGh0bWwgcHVibGljICItLy93M2MvL2R0ZCBodG1sIDQuMCB0cmFuc2l0aW9uYWwv
L2VuIj4NCjxodG1sPg0KJm5ic3A7DQo8YnI+TWF5YmUgSSZuYnNwO25lZWQgYSBjbGFyaWZpY2F0
aW9uIG9uIHdoYXQNCjxibG9ja3F1b3RlPnNob3VsZCBhdHRlbXB0IHRvIGdyYWNlZnVsbHkgdGVh
ciBkb3duIGV4aXN0aW5nIGNvbm5lY3Rpb25zDQpvbiB0aGUNCjxicj5UZXJtaW5hdGlvbihzKSBh
ZmZlY3RlZCBieSB0aGUgc2VydmljZUNoYW5nZSBjb21tYW5kLjwvYmxvY2txdW90ZT4NCkRvZXMg
dGhlIE1HQyBqdXN0IGRvIGEgQ0FNUF9PTi1PT1MgLSB0aGF0IGlzIHdhaXQgdW50aWwgdGhlIHN1
YmNyaWJlcnMNCmhhbmcgdXAgbm9ybWFsbHkgYW5kIHRoZW4NCjxicj5wdXQgdGhlIHRlcm1pbmF0
aW9uIE9PUyBhZnRlciBzdWJzY3JpYmVycyBoYW5nIHVwIChiZWZvcmUgZGVsYXkgdGltZXINCmV4
cGlyZWQpPw0KPHA+T3IgTUdDIHN0YXJ0cyByZWxlYXNpbmcgdGhlIGNhbGxzIHdoZXRoZXIgdGhl
IHN1YnNjcmliZXJzIGhhbmcgdXAgb3INCm5vdD8NCjxwPlRoYW5rcw0KPGJyPkNodW9uZw0KPHA+
Q2hyaXN0aWFuIEdyb3ZlcyB3cm90ZToNCjxibG9ja3F1b3RlIFRZUEU9Q0lURT5UaGVyZSBpcyBh
IHRpbWluZyBkZXBlbmRlbmN5IGhlcmUuIElmIHRoZSBNRyBpc3N1ZXMNCmEgU0MgR3JhY2VmdWwg
dGhlbg0KPGJyPnRoZSBNR0Mgd2lsbCBhY3Qgb24gaXQuIFRoZXJlIHdpbGwgYmUgYSBmaW5pdGUg
dGltZSB0aGF0IHRoZSBNR0MNCjxicj5vcGVyYXRlcyB1bmRlciBncmFjZWZ1bCBtb2RlLiBJZiBh
IFNDIFJlc3RhcnQgdy9TZXJ2aWNlIFJlc3RvcmVkIG9yDQo8YnI+U2VydmljZSBDaGFuZ2UgQ2Fu
Y2VsIGlzIGlzc3VlZCBkdXJpbmcgdGhlIGdyYWNlZnVsIHRoZSBNR0MgY2FuJ3QgdW5kbw0KPGJy
PndoYXQgaXQgaGFkIGRvbmUgaW4gdGhhdCBmaW5pdGUgdGltZSBidXQgdGhlIGNvbm5lY3Rpb25z
IHRoYXQgc3RheWVkDQp1cA0KPGJyPmNhbiByZW1haW4gdXAuIElmIHRoZSBTQyBSZXN0YXJ0IHcv
c2VydmljZSByZXN0b3JlZCBvciBTZXJ2aWNlIENoYW5nZQ0KPGJyPkNhbmNlbCBpcyBub3QgcmVj
ZWl2ZWQgYmVmb3JlIHRoZSBkZWxheSB0aW1lcyBvdXQgdGhlbiBpdCBwcmV0dHkgdG9vDQo8YnI+
bGF0ZSBhcyB0aGUgdGVybWluYXRpb25zIHdpbGwgYmUgdG9ybiBkb3duLg0KPHA+SSBkb24ndCB1
bmRlcnN0YW5kIHdoeSB5b3Ugc2F5IHRoYXQgdGhlIE1HQyBtdXN0IHdhaXQgdW50aWwgdGhlDQo8
YnI+c2VydmljZWNoYW5nZSBkZWxheSB0aW1lc291dHMgYmVmb3JlIGdyYWNlZnVsbHkgdGVhcmlu
ZyBkb3duDQo8YnI+Y29ubmVjdGlvbnM/DQo8cD5DaHJpc3RpYW4NCjxwPiJDaHVvbmcgTi4gTmd1
eWVuIiB3cm90ZToNCjxicj4+DQo8YnI+Pg0KPGJyPj4gTUcgc2VuZHMgU0MgR3JhY2VmdWwgdy9E
ZWxheSBhbmQgdGVybWluYXRpb25JRD1ST09ULg0KPGJyPj4NCjxicj4+IElmIE1HIHNlbmRzIFND
IFJlc3RhcnQgdy9TZXJ2aWNlIFJlc3RvcnRlZCBhbmQgUk9PVCwgZG9lcyB0aGUgTUdDDQo8YnI+
PiBhc3N1bWUgdGhhdA0KPGJyPj4gMSkgU0MgR3JhY2VmdWwgdy9EZWxheSBpcyBiZWluZyBjYW5j
ZWxsZWQ/DQo8YnI+PiAyKSBBbGwgdGVybWluYXRpb25zIGFyZSBiYWNrIEluIFNlcnZpY2U/Jm5i
c3A7IEV2ZW4gdGhlIG9uZXMgdGhhdA0Kd2VyZQ0KPGJyPj4gb3JpZ2luYWxseSBPT1MgYmVmb3Jl
IHRoZSBTQyBHcmFjZWZ1bC4NCjxicj4+DQo8YnI+Pg0KPGJyPj4mbmJzcDsmbmJzcDsmbmJzcDsg
MSkgR3JhY2VmdWwgLSBpbmRpY2F0ZXMgdGhhdCB0aGUgc3BlY2lmaWVkIFRlcm1pbmF0aW9ucw0K
d2lsbCBiZQ0KPGJyPj4gdGFrZW4NCjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IG91dCBvZiBzZXJ2aWNlIGFmdGVyIHRoZSBzcGVjaWZpZWQNClNlcnZpY2VDaGFuZ2VE
ZWxheTsNCjxicj4+IGVzdGFibGlzaGVkDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBjb25uZWN0aW9ucyBhcmUgbm90IHlldCBhZmZlY3RlZCwNCmJ1dCB0aGUgTWVk
aWEgR2F0ZXdheQ0KPGJyPj4gQ29udHJvbGxlcg0KPGJyPj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgc2hvdWxkIHJlZnJhaW4gZnJvbSBlc3RhYmxpc2hpbmcNCm5ldyBjb25u
ZWN0aW9ucyBhbmQgc2hvdWxkDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBhdHRlbXB0IHRvIGdyYWNlZnVsbHkgdGVhciBkb3duDQpleGlzdGluZyBjb25uZWN0aW9u
cyBvbiB0aGUNCjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRlcm1p
bmF0aW9uKHMpIGFmZmVjdGVkIGJ5IHRoZQ0Kc2VydmljZUNoYW5nZSBjb21tYW5kLiBUaGUgTUcN
Cjxicj4+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNob3VsZCBzZXQgdGVy
bWluYXRpb24gc2VydmljZVN0YXRlDQphdCB0aGUgZXhwaXJ5IG9mDQo8YnI+PiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBTZXJ2aWNlQ2hhbmdlRGVsYXkgb3IgdGhlIHJlbW92
YWwNCm9mIHRoZSB0ZXJtaW5hdGlvbiBmcm9tIGFuDQo8YnI+PiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBhY3RpdmUgY29udGV4dCAod2hpY2hldmVyIGlzDQpmaXJzdCksIHRv
ICJvdXQgb2Ygc2VydmljZSIuDQo8YnI+Pg0KPGJyPj4NCjxicj4+IEhvdyBzaG91bGQgTUdDIGlt
cGxlbWVudGF0aW9uIGludGVwcmV0IHRoZSBhYm92ZSBoaWdobGlnaHRlZA0KPGJyPj4gc3RhdGVt
ZW50Pw0KPGJyPj4gRG9lcyB0aGlzIG1lYW4gdGhhdCBNR0Mgc2hvdWxkIG5vdCB0cnkgdG8gZ3Jh
Y2VmdWxseSB0ZWFyIGRvd24NCjxicj4+IGV4aXN0aW5nIGNvbm5lY3Rpb25zDQo8YnI+PiBiZWZv
cmUgRGVsYXkgdGltZXIgZXhwaXJlZD8NCjxicj4+DQo8YnI+PiBCdXQgSSB0aGluayB0aGUgYWJv
dmUgc3RhdGVtZW50IGlzIHRlbGxpbmcgTUdDIHRvIHRyeSBhbmQgZ3JhY2VmdWxseQ0KPGJyPj4g
dGVhciBkb3duDQo8YnI+PiBleGlzdGluZyBjb25uZWN0aW9ucyBiZWZvcmUgRGVsYXkgdGltZXIg
ZXhwaXJlZC4NCjxicj4+DQo8YnI+PiBUbyBiZSBhYmxlIHRvIGNhbmNlbCBHcmFjZWZ1bCB3L0Rl
bGF5LCBpdCBzZWVtcyB0aGF0IE1HQyBuZWVkcyB0bw0Kd2FpdA0KPGJyPj4gdW50aWwNCjxicj4+
IERlbGF5IHRpbWVyIGV4cGlyZWQgYmVmb3JlIGl0IHRyaWVzIHRvIHRlYXIgZG93biBleGlzdGlu
ZyBjb25uZWN0aW9ucy4NCjxicj4+DQo8YnI+PiBCdXQgYWZ0ZXIgRGVsYXkgdGltZXIgZXhwaXJl
ZCwgTUcgd2lsbCBwdXQgYWxsIHRlcm1pbmF0aW9ucyBvdXQgb2YNCjxicj4+IHNlcnZpY2UuDQo8
YnI+PiBUaGVyZWZvcmUgdGhlcmUgaXMgbm8gc3VjaCB0aGluZyBhcyBNR0MgZ3JhY2VmdWxseSB0
ZWFyaW5nIGRvd24NCjxicj4+IGV4aXN0aW5nIGNvbm5lY3Rpb25zLg0KPGJyPj4NCjxicj4+DQo8
YnI+PiBDaHJpc3RpYW4gR3JvdmVzIHdyb3RlOg0KPGJyPj4NCjxicj4+ID4gSSBkb24ndCBzZWUg
dGhhdCB3ZSBuZWVkIHRvIGFkZCBhbnl0aGluZy4gV2h5IGNhbid0IHRoZSBNRyBqdXN0DQo8YnI+
PiA+IGlzc3VlIGENCjxicj4+ID4gU0Mgd2l0aCBSZXN0YXJ0LCBTZXJ2aWNlIFJlc3RvcmVkPyBU
aGUgc3BlY2lmaWNhdGlvbiBhbHJlYWR5IGFsbG93cw0KPGJyPj4gPiB0aGUNCjxicj4+ID4gTUcg
dG8gZG8gdGhpcy4NCjxicj4+ID4NCjxicj4+ID4gUmVnYXJkcywgQ2hyaXN0aWFuDQo8YnI+PiA+
DQo8YnI+PiA+ICJDaHVvbmcgTi4gTmd1eWVuIiB3cm90ZToNCjxicj4+ID4gPg0KPGJyPj4gPiA+
IEhpIFRvbQ0KPGJyPj4gPiA+DQo8YnI+PiA+ID4gV2hhdCBhcmUgdGhlIHBvc3NpYmlsaXRlcyBv
ZiBkZWZpbmluZyBhIG1lY2hhbmlzbSBvZiBjYW5jZWxsaW5nDQo8YnI+PiA+ID4gU2VydmljZUNo
YW5nZSBHcmFjZWZ1bD8NCjxicj4+ID4gPiBUaGF0IGlzIE1HIHNlbmQgU0MgR3JhY2VmdWwgdy9E
ZWxheT10aW1lLg0KPGJyPj4gPiA+IEJlZm9yZSB0aW1lIGV4cGlyZWQsIE1HIHdhbnRzIHRvIGNh
bmNlbCB0aGlzIFNlcnZpY2VDaGFuZ2UuDQo8YnI+PiA+ID4NCjxicj4+ID4gPiAxKSBDYW4gdGhp
cyBiZSBkb25lIGluIFYxIGJ5IGFkZGluZyBhIG5ldyBTQyBSZWFzb24gbGlrZSAiOTE2DQpTQw0K
PGJyPj4gPiA+IEdyYWNlZnVsIGNhbmNlbGxlZCI/DQo8YnI+PiA+ID4gMikgRG9uZSBpbiBWMiAt
IG5ldyBTQyBNZXRob2Qgb3IgUmVhc29uPw0KPGJyPj4gPiA+IDMpIFNob3VsZCBiZSBjb3ZlcmVk
IGluIGRyYWZ0LWhzcy1tZWdhY28tY29udHJvbC1hc3NvY2lhdGlvbj8NCjxicj4+ID4gPg0KPGJy
Pj4gPiA+DQo8YnI+PiA+ID4gVGhhbmtzDQo8YnI+PiA+ID4gQ2h1b25nDQo8YnI+PiA+ID4NCjxi
cj4+ID4gPg0KPGJyPj4gPiA+DQo8YnI+PiA+ID4gLS0NCjxicj4+ID4gPiZuYnNwOyZuYnNwOyBB
bGNhdGVsIFVTQSwgSW5jJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpJbnRlcm5ldDoNCjxicj4+ID4gQ2h1b25n
Lk5ndXllbkB1c2EuYWxjYXRlbC5jb20NCjxicj4+ID4gPiZuYnNwOyZuYnNwOyAxMDAwIENvaXQg
Um9hZCBQbGFubywgVGV4YXMgNzUwNzUmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNClBob25lOiZuYnNwOyZuYnNwOyZuYnNwOyAoOTcy
KQ0KPGJyPj4gPiA1MTktNDYxMw0KPGJyPj4gPiA+Jm5ic3A7Jm5ic3A7ICoqKiogVGhlIG9waW5p
b25zIGV4cHJlc3NlZCBhcmUgbm90IHRob3NlIG9mIEFsY2F0ZWwNClVTQSwgSW5jDQo8YnI+PiA+
ICoqKioNCjxicj4+ID4gPg0KPGJyPj4gPiA+DQo8YnI+Pg0KPGJyPj4gLS0NCjxicj4+Jm5ic3A7
Jm5ic3A7IEFsY2F0ZWwgVVNBLCBJbmMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCkludGVybmV0OiBDaHVvbmcu
Tmd1eWVuQHVzYS5hbGNhdGVsLmNvbQ0KPGJyPj4mbmJzcDsmbmJzcDsgMTAwMCBDb2l0IFJvYWQg
UGxhbm8sIFRleGFzIDc1MDc1Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQpQaG9uZTombmJzcDsmbmJzcDsmbmJzcDsgKDk3MikgNTE5
LTQ2MTMNCjxicj4+Jm5ic3A7Jm5ic3A7ICoqKiogVGhlIG9waW5pb25zIGV4cHJlc3NlZCBhcmUg
bm90IHRob3NlIG9mIEFsY2F0ZWwNClVTQSwgSW5jICoqKioNCjxicj4+DQo8YnI+PjwvYmxvY2tx
dW90ZT4NCg0KPHByZT4tLSZuYnNwOw0KJm5ic3A7IEFsY2F0ZWwgVVNBLCBJbmMmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgSW50ZXJuZXQ6IENodW9uZy5OZ3V5ZW5AdXNhLmFsY2F0ZWwuY29tDQombmJzcDsgMTAw
MCBDb2l0IFJvYWQgUGxhbm8sIFRleGFzIDc1MDc1Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFBob25lOiZuYnNwOyZuYnNwOyZuYnNw
OyAoOTcyKSA1MTktNDYxMw0KJm5ic3A7ICoqKiogVGhlIG9waW5pb25zIGV4cHJlc3NlZCBhcmUg
bm90IHRob3NlIG9mIEFsY2F0ZWwgVVNBLCBJbmMgKioqKjwvcHJlPg0KJm5ic3A7PC9odG1sPg0K
DQo=

--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline








"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."




--0__=BkHoHihdV0wAXPQV5fOaKvpCxEUXUxVcjRqSgN7GYXhGk8j48NUjkI2x--


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



From megaco-admin@ietf.org  Tue Jan 22 14:05:36 2002
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 OAA05263
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:05:35 -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 NAA04253;
	Tue, 22 Jan 2002 13:49:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04141
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:49:53 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04452
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:49:49 -0500 (EST)
From: prjain@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MIoSE25859;
	Wed, 23 Jan 2002 00:20:28 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.006759B5 ; Wed, 23 Jan 2002 00:18:51 +0530
X-Lotus-FromDomain: HSS
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
cc: megaco@ietf.org
Message-ID: <65256B49.00675766.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 00:20:40 +0530
Subject: Re: [Megaco] Method is Disconnected
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi,
     In our opinion, we should use the following two reasons.
     1. Warm Boot.
     2. Service Restored.

     The use of other reasons seem to be bit irrelevant with the "disconnected"
service change method since this method should be used only in the case of
transient failures.

Thanks and Regards,
Prashant Jain






Christer Holmberg <christer.holmberg@lmf.ericsson.se> on 01/22/2002 03:00:42 AM

To:   megaco@ietf.org
cc:    (bcc: Prashant Jain/HSS)

Subject:  [Megaco] Method is Disconnected





Hi,

In V2, both serviceChangeMethod and serviceChangeReason are MANDATORY.

So, my questions is: if the Method value is 'Disconneced', what shall
the Reason value be? I can't find any which would fit...

Regards,

Christer Holmberg
Ericsson Finland

_______________________________________________
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


From megaco-admin@ietf.org  Tue Jan 22 14:31:40 2002
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 OAA06813
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:31:40 -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 OAA06003;
	Tue, 22 Jan 2002 14:17:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05978
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:17:46 -0500 (EST)
Received: from NS1.US.PRSERV.NET ([64.180.246.83])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05875
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:17:43 -0500 (EST)
From: sydney@vkistudios.org
Message-Id: <200201221917.OAA05875@ietf.org>
Reply-To: seo@vkistudios.org
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Date: Tue, 22 Jan 2002 11:21:16 -0800
Subject: [Megaco] ADV: Professional Internet Marketing
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

<HTML>
<HEAD>
<TITLE>Professional Internet Marketing, VKI Studios 1-866-733-8899</TITLE>
<META name="description" content="A web services company specializing dynamic Internet marketing">
<META name="keywords" content="Dynamic Internet Marketing">
<META http-equiv="CONTENT-LANGUAGE" content="English">
<META name="RATING" content="General">
<META name="distribution" content="global">
<META name="copyright" content="copyright 2002, VKI Studios">
<META name="robots" content="index,follow">
<META http-equiv=Expires content="O">
<LINK rel="stylesheet" href="http://www.vkistudios.com/css/vki.css" type="text/css">
</HEAD>

<BODY bgcolor="#FFFFFF" text="#000000" link="#990000" vlink="663333">
<TABLE width="550" border="0" cellspacing="0" cellpadding="2" align="center">
  <TR> 
    <TD class="newsletter" bgcolor="006699" width="190" align="center"> 
      <P><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><BR>
        <IMG src="http://www.vkistudios.com/images/h_internet_mkt.gif" width="183" height="37" alt="VKI Studios - Internet Marketing Is Mission Critical For Your Business" border="0"></A><BR>
        <OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="183" height="20">
          <PARAM name=movie value="http://www.vkistudios.com/swf/ani_email.swf">
          <PARAM name=quality value=high>
          <PARAM name="BGCOLOR" value="006699">
          <EMBED src="http://www.vkistudios.com/swf/ani_email.swf" quality=high pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="183" height="20" bgcolor="006699">
          </EMBED> 
        </OBJECT><BR>
        &nbsp;</B></P>
    </TD>
    <TD class="promo_header" bgcolor="006699" valign="top" align="right" width="360"><FONT color="#FFFFFF"><B>1-866-733-8899</B></FONT>&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P><IMG src="http://www.vkistudios.com/images/shim_email0.gif" width="1" height="17"><B><FONT color="006699">&quot;VKI 
        increased our web traffic by 550%</FONT></B> which resulted in a 20% increase 
        in revenues in less than six months.&quot; John Keith-King, Curator, Granville 
        Island Museums.</P>
      <P>Would you like to see if you can achieve similar results? <BR>
        Call us at 1-866-733-8899 or fill out our <A href="http://www.vkistudios.com/form_internet_mkt.html">online 
        consultation</A> and receive a <B><FONT color="006699"><BR>
        FREE Search Engine Report<FONT size="-1"> (value $75.00)</FONT></FONT></B></P>
      <P><FONT color="#006699"><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><IMG src="http://www.vkistudios.com/images/button_guarantee.gif" width="185" height="29" alt="Results Guaranteed" border="0"></A></B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2">&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" valign="bottom" colspan="2"> 
      <P><FONT color="#006699"><B>THE BENEFITS</B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Your website will become <FONT color="006699"><B>highly visible</B></FONT></LI>
        <LI>Your <FONT color="006699"><B>traffic will grow</B></FONT> exponentially</LI>
        <LI>Measurable and <FONT color="006699"><B>trackable results</B></FONT></LI>
        <LI>You will have an ongoing <FONT color="006699"><B>strategy that adapts 
          </B></FONT>as search engines change<BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B> THE ELEVATION</B></FONT></TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI> Strategy development</LI>
        <LI>Keyword Formulation</LI>
        <LI>Creation of keyword &amp; description META tags</LI>
        <LI>Creation of keyword entry pages</LI>
        <LI>FTP file transfer to server</LI>
        <LI>Submission of web address (URL) to search engines</LI>
        <LI>Submission of web address (URL) to directory sites<BR>
          <A href="http://www.vkistudios.com/se_phase1.html">more info</A><BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B>THE PUSH</B></FONT> 
      - ongoing maintenance includes:</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Optimization - HTML optimization to be search engine friendly</LI>
        <LI>Submission - Proper submission protocol for each individual engine</LI>
        <LI>Registration - Verification of successful submissions</LI>
        <LI>Monitoring - Evaluation of server file logs for search engine activity</LI>
        <LI>Positioning - Fine-tuning of submitted pages</LI>
        <LI>Maintenance - Continuous attendance to all the above actions<BR>
          <A href="http://www.vkistudios.com/form_internet_mkt.html">Online consultation</A> 
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>Many Search Engines are moving to paid listings so <B><FONT color="006699">ACT 
        NOW!</FONT></B><BR>
        <A href="http://www.vkistudios.com/form_internet_mkt.html">Contact us 
        today to take advantage of our limited time offer.</A></P>
      <P>Please call us: 1-866-733-8899 or (604) 733-1474 - <A href="http://www.vkistudios.com" target="_blank">VKI 
        Studios Inc.</A></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>&nbsp;</P>
    </TD>
  </TR>
  <TR>
    <TD class="newsletter" colspan="2">If you do not wish to receive further mailings, 
      please <A href="http://www.vkistudios.com/remove/unsubscribe.html">unsubscribe 
      here.</A></TD>
  </TR>
</TABLE>
<P>&nbsp;</P>
</BODY>
</HTML>

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


From daemon@ns.ietf.org  Tue Jan 22 14:31:41 2002
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 OAA06826
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:31:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA07493
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 14:31:43 -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 OAA06003;
	Tue, 22 Jan 2002 14:17:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05978
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:17:46 -0500 (EST)
Received: from NS1.US.PRSERV.NET ([64.180.246.83])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05875
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:17:43 -0500 (EST)
From: sydney@vkistudios.org
Message-Id: <200201221917.OAA05875@ietf.org>
Reply-To: seo@vkistudios.org
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Date: Tue, 22 Jan 2002 11:21:16 -0800
Subject: [Megaco] ADV: Professional Internet Marketing
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

<HTML>
<HEAD>
<TITLE>Professional Internet Marketing, VKI Studios 1-866-733-8899</TITLE>
<META name="description" content="A web services company specializing dynamic Internet marketing">
<META name="keywords" content="Dynamic Internet Marketing">
<META http-equiv="CONTENT-LANGUAGE" content="English">
<META name="RATING" content="General">
<META name="distribution" content="global">
<META name="copyright" content="copyright 2002, VKI Studios">
<META name="robots" content="index,follow">
<META http-equiv=Expires content="O">
<LINK rel="stylesheet" href="http://www.vkistudios.com/css/vki.css" type="text/css">
</HEAD>

<BODY bgcolor="#FFFFFF" text="#000000" link="#990000" vlink="663333">
<TABLE width="550" border="0" cellspacing="0" cellpadding="2" align="center">
  <TR> 
    <TD class="newsletter" bgcolor="006699" width="190" align="center"> 
      <P><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><BR>
        <IMG src="http://www.vkistudios.com/images/h_internet_mkt.gif" width="183" height="37" alt="VKI Studios - Internet Marketing Is Mission Critical For Your Business" border="0"></A><BR>
        <OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="183" height="20">
          <PARAM name=movie value="http://www.vkistudios.com/swf/ani_email.swf">
          <PARAM name=quality value=high>
          <PARAM name="BGCOLOR" value="006699">
          <EMBED src="http://www.vkistudios.com/swf/ani_email.swf" quality=high pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="183" height="20" bgcolor="006699">
          </EMBED> 
        </OBJECT><BR>
        &nbsp;</B></P>
    </TD>
    <TD class="promo_header" bgcolor="006699" valign="top" align="right" width="360"><FONT color="#FFFFFF"><B>1-866-733-8899</B></FONT>&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P><IMG src="http://www.vkistudios.com/images/shim_email0.gif" width="1" height="17"><B><FONT color="006699">&quot;VKI 
        increased our web traffic by 550%</FONT></B> which resulted in a 20% increase 
        in revenues in less than six months.&quot; John Keith-King, Curator, Granville 
        Island Museums.</P>
      <P>Would you like to see if you can achieve similar results? <BR>
        Call us at 1-866-733-8899 or fill out our <A href="http://www.vkistudios.com/form_internet_mkt.html">online 
        consultation</A> and receive a <B><FONT color="006699"><BR>
        FREE Search Engine Report<FONT size="-1"> (value $75.00)</FONT></FONT></B></P>
      <P><FONT color="#006699"><B><A href="http://www.vkistudios.com/form_internet_mkt.html"><IMG src="http://www.vkistudios.com/images/button_guarantee.gif" width="185" height="29" alt="Results Guaranteed" border="0"></A></B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2">&nbsp;</TD>
  </TR>
  <TR> 
    <TD class="newsletter" valign="bottom" colspan="2"> 
      <P><FONT color="#006699"><B>THE BENEFITS</B></FONT></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Your website will become <FONT color="006699"><B>highly visible</B></FONT></LI>
        <LI>Your <FONT color="006699"><B>traffic will grow</B></FONT> exponentially</LI>
        <LI>Measurable and <FONT color="006699"><B>trackable results</B></FONT></LI>
        <LI>You will have an ongoing <FONT color="006699"><B>strategy that adapts 
          </B></FONT>as search engines change<BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B> THE ELEVATION</B></FONT></TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI> Strategy development</LI>
        <LI>Keyword Formulation</LI>
        <LI>Creation of keyword &amp; description META tags</LI>
        <LI>Creation of keyword entry pages</LI>
        <LI>FTP file transfer to server</LI>
        <LI>Submission of web address (URL) to search engines</LI>
        <LI>Submission of web address (URL) to directory sites<BR>
          <A href="http://www.vkistudios.com/se_phase1.html">more info</A><BR>
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"><FONT color="#006699"><B>THE PUSH</B></FONT> 
      - ongoing maintenance includes:</TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <UL>
        <LI>Optimization - HTML optimization to be search engine friendly</LI>
        <LI>Submission - Proper submission protocol for each individual engine</LI>
        <LI>Registration - Verification of successful submissions</LI>
        <LI>Monitoring - Evaluation of server file logs for search engine activity</LI>
        <LI>Positioning - Fine-tuning of submitted pages</LI>
        <LI>Maintenance - Continuous attendance to all the above actions<BR>
          <A href="http://www.vkistudios.com/form_internet_mkt.html">Online consultation</A> 
        </LI>
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>Many Search Engines are moving to paid listings so <B><FONT color="006699">ACT 
        NOW!</FONT></B><BR>
        <A href="http://www.vkistudios.com/form_internet_mkt.html">Contact us 
        today to take advantage of our limited time offer.</A></P>
      <P>Please call us: 1-866-733-8899 or (604) 733-1474 - <A href="http://www.vkistudios.com" target="_blank">VKI 
        Studios Inc.</A></P>
    </TD>
  </TR>
  <TR> 
    <TD class="newsletter" colspan="2"> 
      <P>&nbsp;</P>
    </TD>
  </TR>
  <TR>
    <TD class="newsletter" colspan="2">If you do not wish to receive further mailings, 
      please <A href="http://www.vkistudios.com/remove/unsubscribe.html">unsubscribe 
      here.</A></TD>
  </TR>
</TABLE>
<P>&nbsp;</P>
</BODY>
</HTML>

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



From daemon@ns.ietf.org  Tue Jan 22 14:31:42 2002
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 OAA06836
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:31:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA07498
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 14:31:44 -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 OAA05851;
	Tue, 22 Jan 2002 14:13:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05821
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:13:51 -0500 (EST)
Received: from revere.sonusnet.com (mail.sonusnet.com [208.45.178.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05670
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:13:47 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3 [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0MJ1AH15061;
	Tue, 22 Jan 2002 14:01:11 -0500 (EST)
Received: from matt.verizon.net (Matt.sonusnet.com [10.128.130.67]) by sonusdc3.sonusnet.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id DATJ4C31; Tue, 22 Jan 2002 14:01:15 -0500
Message-Id: <5.1.0.14.2.20020122105753.0229a720@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 22 Jan 2002 11:00:39 -0800
To: "Tom-PT Taylor"<taylor@nortelnetworks.com>, megaco@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: [Megaco] Regarding IPsec and interim AH
In-Reply-To: <4D79C746863DD51197690002A52CDA000102AEC9@zcard0kc.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Since I think it never should have been there, I can certainly make a 
motion to depreciate it. I don't know how important it is to depreciate it, 
but it certainly couldn't hurt. At least it would/could stop all the 
questions about it.


At 10:25 AM 1/22/2002, Tom-PT Taylor wrote:
>Would people accept deprecation?  How many implementations are out there
>using interim AH and unable to switch to full IPSEC?  People can reply to me
>privately if they wish.
>
>-----Original Message-----
>From: Kaul, Bharat [mailto:bharat@trillium.com]
>Sent: Friday, January 18, 2002 6:12 PM
>To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
>Subject: RE: [Megaco] Regarding IPsec and interim AH
>
>
>I remember long time back on this list it was being discussed that AH scheme
>will be deprecated. However, I still see its mention in v2.
>
>- Bharat
>
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Friday, January 18, 2002 5:26 AM
>To: Narendra Babu; megaco@ietf.org
>Subject: Re: [Megaco] Regarding IPsec and interim AH
>
>
>At 10:36 PM 1/17/2002, Narendra Babu wrote:
> >Hi all,
> >
> >         I am a newbie to this mail list as well as megaco.
> >
> >We are developing a megaco stack.My doubt is whether
> >we have to implement full IPsec(RFC 2401-RFC 2411) or
> >only interim AH as a secrity support? Please clarify  this as early as
> >possible.
>
>I always thought interim AH wasn't a good idea and I think it is now
>clarified as a temporary scheme that is no longer needed. So your choices
>are IPsec or perhaps some less onerous scheme such as SSH.
>
>Anybody else?
>
>
>_______________________________________________
>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



From megaco-admin@ietf.org  Tue Jan 22 14:52:59 2002
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 OAA08020
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:52:59 -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 OAA07997;
	Tue, 22 Jan 2002 14:36:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07965
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:36:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07146
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:36:21 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MJZpS29031;
	Tue, 22 Jan 2002 14:35:52 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MJZnT26256;
	Tue, 22 Jan 2002 14:35:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYS1V>; Tue, 22 Jan 2002 14:35:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AECA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Kaul, Bharat'" <bharat@trillium.com>,
        "'fandreas@cisco.com'"
	 <fandreas@cisco.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Tue, 22 Jan 2002 14:35:49 -0500
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

I finally made the effort to track down the original issue that led to the
specification of immAckRequired back in Feb'00.  Here is the reason as
stated at the time (from a Chip Sharp/Flemming Andreasen intervention):

<begin>

Section:        D.1.4
Category:       Technical
Issue:          The draft text specifies that receipt of a provisional
response
will imply a switch to a longer repetition timer for the transaction.
However, there is no other reliability mechanism in place to detect the
loss of the final response for that transaction, and consequently a lost
final response may not be detected for a while (depends on the longer
repetition timer). This leads to suboptimal behaviour of the protocol with
unnecessary long time-outs.
Proposal:       It is proposed, that a final response issued after a
provisional
response requires an immediate confirmation to enable rapid detection of a
lost final response. Since the provisional response itself may be lost,
this implies that the final response should include an indication that a
response acknowledgement is required (immediately).

<end>

The implication is that it's not just a matter of the response sender's
convenience (i.e. faster clearing of buffers), but of ensuring that the
response is retransmitted as quickly as possible in the event of loss.  The
problem is that we don't actually have any text which says that the
responder should retransmit responses of its own accord.  J K Ramchandra
appears to be right in saying that responses are retransmitted only when
retransmitted requests are received.

Flemming, is this an oversight and departure from what was really intended?
People in general: do we agree on this interpretation, and is it adequate? 

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Friday, January 18, 2002 6:15 PM
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.


Agreed...I don't see any reason to develop retransmission mechanisms for the
responses just because immAck was sent and we are not receiving replies.
immAck is just a request which may or may not get fulfilled and doesn't
affect any protocol operation.

- Bharat

-----Original Message-----
From: J K Ramchandra [mailto:jkr@ipgen-india.com]
Sent: Friday, January 18, 2002 2:49 PM
To: vibansal@hss.hns.com; Christian.Groves@ericsson.com.au;
taylor@nortelnetworks.com; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


Hi all,

I think we are heading somewhere here. If I remember correctly, the sole
purpose
of responseAck is to reduce the overall memory consumption. The entity
sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till
long
timer to clean up these buffer. Normally, the response ack is appended with
the
next message sent towards that destination (MG/MGC). By setting
immAckRequired
flag in the response, it is requesting to send it immediately (not waiting
till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could
be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but
simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after
one
or more transaction Pending was sent), I believe, is due to the fact that
this
specific transaction has already  active for quite some time and better to
be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will
retransmit
the response only when the repeated request is received. This is the case
with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't
see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving
side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN


_______________________________________________
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


From daemon@ns.ietf.org  Tue Jan 22 14:53:00 2002
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 OAA08034
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:53:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA08579
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 14:53:03 -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 OAA07997;
	Tue, 22 Jan 2002 14:36:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07965
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:36:25 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07146
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:36:21 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MJZpS29031;
	Tue, 22 Jan 2002 14:35:52 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MJZnT26256;
	Tue, 22 Jan 2002 14:35:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYS1V>; Tue, 22 Jan 2002 14:35:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AECA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Kaul, Bharat'" <bharat@trillium.com>,
        "'fandreas@cisco.com'"
	 <fandreas@cisco.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.
Date: Tue, 22 Jan 2002 14:35:49 -0500
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

I finally made the effort to track down the original issue that led to the
specification of immAckRequired back in Feb'00.  Here is the reason as
stated at the time (from a Chip Sharp/Flemming Andreasen intervention):

<begin>

Section:        D.1.4
Category:       Technical
Issue:          The draft text specifies that receipt of a provisional
response
will imply a switch to a longer repetition timer for the transaction.
However, there is no other reliability mechanism in place to detect the
loss of the final response for that transaction, and consequently a lost
final response may not be detected for a while (depends on the longer
repetition timer). This leads to suboptimal behaviour of the protocol with
unnecessary long time-outs.
Proposal:       It is proposed, that a final response issued after a
provisional
response requires an immediate confirmation to enable rapid detection of a
lost final response. Since the provisional response itself may be lost,
this implies that the final response should include an indication that a
response acknowledgement is required (immediately).

<end>

The implication is that it's not just a matter of the response sender's
convenience (i.e. faster clearing of buffers), but of ensuring that the
response is retransmitted as quickly as possible in the event of loss.  The
problem is that we don't actually have any text which says that the
responder should retransmit responses of its own accord.  J K Ramchandra
appears to be right in saying that responses are retransmitted only when
retransmitted requests are received.

Flemming, is this an oversight and departure from what was really intended?
People in general: do we agree on this interpretation, and is it adequate? 

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Friday, January 18, 2002 6:15 PM
To: megaco@ietf.org
Subject: RE: [Megaco] Doubt regarding immAckRequired field.


Agreed...I don't see any reason to develop retransmission mechanisms for the
responses just because immAck was sent and we are not receiving replies.
immAck is just a request which may or may not get fulfilled and doesn't
affect any protocol operation.

- Bharat

-----Original Message-----
From: J K Ramchandra [mailto:jkr@ipgen-india.com]
Sent: Friday, January 18, 2002 2:49 PM
To: vibansal@hss.hns.com; Christian.Groves@ericsson.com.au;
taylor@nortelnetworks.com; megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.


Hi all,

I think we are heading somewhere here. If I remember correctly, the sole
purpose
of responseAck is to reduce the overall memory consumption. The entity
sending
the response (transaction Reply) can clean up its response buffer once
responsAck is received for that transaction. Otherwise it has to wait till
long
timer to clean up these buffer. Normally, the response ack is appended with
the
next message sent towards that destination (MG/MGC). By setting
immAckRequired
flag in the response, it is requesting to send it immediately (not waiting
till
the next message). Probably, the receving entity will send a stand-alone
response ack message back.

Now, let us see what is the impact of not receiving responseAck. This could
be
due to two reasons:
a. The response with immAckRequired field has not reached the remote entity,
b. The remote entity receved the response with immAckRequired field, but
simply
ignored it and not sent the responseAck back.

In case 'a', the remote entity will re-transmit the transation request and
everything should be OK this time. No harm done.

In case 'b', the response buffers are held till long timer. Except for this
longer holding of buffers, no other damage here as well. I don't see why
responding entity WAIT for his response to reach the destination. It is
orginator who care about the response.

The reason for setting the immAckRequired in the final response (i.e. after
one
or more transaction Pending was sent), I believe, is due to the fact that
this
specific transaction has already  active for quite some time and better to
be
cleaned up with the immediate response ack.

The re-transmission is always initiated by the entity who is initiating the
transaction request as specified in the D.1.3. Responding entity will
retransmit
the response only when the repeated request is received. This is the case
with
most of the protocols (mgcp, SIP or any of the PSTN protocols) and I don't
see
why we have to invent re-transmission  mechanism on the responding side. A
simple long timer based clean up is sufficient currently on the receving
side
and it is better be that way.

Am I missing something here?

Regards,

J K Ramachandra,
IPGEN


_______________________________________________
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



From daemon@ns.ietf.org  Tue Jan 22 14:59:12 2002
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 OAA05269
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:05:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05537
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 14:05:38 -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 NAA04253;
	Tue, 22 Jan 2002 13:49:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04141
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 13:49:53 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04452
	for <megaco@ietf.org>; Tue, 22 Jan 2002 13:49:49 -0500 (EST)
From: prjain@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0MIoSE25859;
	Wed, 23 Jan 2002 00:20:28 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B49.006759B5 ; Wed, 23 Jan 2002 00:18:51 +0530
X-Lotus-FromDomain: HSS
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
cc: megaco@ietf.org
Message-ID: <65256B49.00675766.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 00:20:40 +0530
Subject: Re: [Megaco] Method is Disconnected
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi,
     In our opinion, we should use the following two reasons.
     1. Warm Boot.
     2. Service Restored.

     The use of other reasons seem to be bit irrelevant with the "disconnected"
service change method since this method should be used only in the case of
transient failures.

Thanks and Regards,
Prashant Jain






Christer Holmberg <christer.holmberg@lmf.ericsson.se> on 01/22/2002 03:00:42 AM

To:   megaco@ietf.org
cc:    (bcc: Prashant Jain/HSS)

Subject:  [Megaco] Method is Disconnected





Hi,

In V2, both serviceChangeMethod and serviceChangeReason are MANDATORY.

So, my questions is: if the Method value is 'Disconneced', what shall
the Reason value be? I can't find any which would fit...

Regards,

Christer Holmberg
Ericsson Finland

_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 22 15:30:44 2002
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 OAA06814
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 14:31:40 -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 OAA05851;
	Tue, 22 Jan 2002 14:13:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05821
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 14:13:51 -0500 (EST)
Received: from revere.sonusnet.com (mail.sonusnet.com [208.45.178.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05670
	for <megaco@ietf.org>; Tue, 22 Jan 2002 14:13:47 -0500 (EST)
Received: from sonusdc3.sonusnet.com (sonusdc3 [10.128.32.53])
	by revere.sonusnet.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0MJ1AH15061;
	Tue, 22 Jan 2002 14:01:11 -0500 (EST)
Received: from matt.verizon.net (Matt.sonusnet.com [10.128.130.67]) by sonusdc3.sonusnet.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id DATJ4C31; Tue, 22 Jan 2002 14:01:15 -0500
Message-Id: <5.1.0.14.2.20020122105753.0229a720@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 22 Jan 2002 11:00:39 -0800
To: "Tom-PT Taylor"<taylor@nortelnetworks.com>, megaco@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: [Megaco] Regarding IPsec and interim AH
In-Reply-To: <4D79C746863DD51197690002A52CDA000102AEC9@zcard0kc.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

Since I think it never should have been there, I can certainly make a 
motion to depreciate it. I don't know how important it is to depreciate it, 
but it certainly couldn't hurt. At least it would/could stop all the 
questions about it.


At 10:25 AM 1/22/2002, Tom-PT Taylor wrote:
>Would people accept deprecation?  How many implementations are out there
>using interim AH and unable to switch to full IPSEC?  People can reply to me
>privately if they wish.
>
>-----Original Message-----
>From: Kaul, Bharat [mailto:bharat@trillium.com]
>Sent: Friday, January 18, 2002 6:12 PM
>To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
>Subject: RE: [Megaco] Regarding IPsec and interim AH
>
>
>I remember long time back on this list it was being discussed that AH scheme
>will be deprecated. However, I still see its mention in v2.
>
>- Bharat
>
>-----Original Message-----
>From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
>Sent: Friday, January 18, 2002 5:26 AM
>To: Narendra Babu; megaco@ietf.org
>Subject: Re: [Megaco] Regarding IPsec and interim AH
>
>
>At 10:36 PM 1/17/2002, Narendra Babu wrote:
> >Hi all,
> >
> >         I am a newbie to this mail list as well as megaco.
> >
> >We are developing a megaco stack.My doubt is whether
> >we have to implement full IPsec(RFC 2401-RFC 2411) or
> >only interim AH as a secrity support? Please clarify  this as early as
> >possible.
>
>I always thought interim AH wasn't a good idea and I think it is now
>clarified as a temporary scheme that is no longer needed. So your choices
>are IPsec or perhaps some less onerous scheme such as SSH.
>
>Anybody else?
>
>
>_______________________________________________
>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


From megaco-admin@ietf.org  Tue Jan 22 17:02:03 2002
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 RAA12581
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:02:03 -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 QAA13922;
	Tue, 22 Jan 2002 16:44:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13891
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 16:44:19 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11774
	for <megaco@ietf.org>; Tue, 22 Jan 2002 16:44:14 -0500 (EST)
Received: from cisco.com (ssh-sj1.cisco.com [171.68.225.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA24932; Tue, 22 Jan 2002 13:41:57 -0800 (PST)
Message-ID: <3C4DDCBB.2E19BB73@cisco.com>
Date: Tue, 22 Jan 2002 16:42:20 -0500
From: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Kaul, Bharat'" <bharat@trillium.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <4D79C746863DD51197690002A52CDA000102AECA@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit



Tom-PT Taylor wrote:

> I finally made the effort to track down the original issue that led to the
> specification of immAckRequired back in Feb'00.  Here is the reason as
> stated at the time (from a Chip Sharp/Flemming Andreasen intervention):
>
> <begin>
>
> Section:        D.1.4
> Category:       Technical
> Issue:          The draft text specifies that receipt of a provisional
> response
> will imply a switch to a longer repetition timer for the transaction.
> However, there is no other reliability mechanism in place to detect the
> loss of the final response for that transaction, and consequently a lost
> final response may not be detected for a while (depends on the longer
> repetition timer). This leads to suboptimal behaviour of the protocol with
> unnecessary long time-outs.
> Proposal:       It is proposed, that a final response issued after a
> provisional
> response requires an immediate confirmation to enable rapid detection of a
> lost final response. Since the provisional response itself may be lost,
> this implies that the final response should include an indication that a
> response acknowledgement is required (immediately).
>
> <end>
>
> The implication is that it's not just a matter of the response sender's
> convenience (i.e. faster clearing of buffers), but of ensuring that the
> response is retransmitted as quickly as possible in the event of loss.  The
> problem is that we don't actually have any text which says that the
> responder should retransmit responses of its own accord.  J K Ramchandra
> appears to be right in saying that responses are retransmitted only when
> retransmitted requests are received.
>
> Flemming, is this an oversight and departure from what was really intended?

Yes. The idea was, that upon receiving a provisional response, you switch to a
longer repetition timer aimed at detecting endpoint/termination failures as
opposed to transmission problems. If you don't employ active retransmission of
the final response, a lost final response will only be resent at the long
transaction retransmit interval, which is suboptimal. Depending on the timer
values involved, it could even lead to the transaction timing out (incorrectly).

-- Flemming


>


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


From daemon@ns.ietf.org  Tue Jan 22 17:02:04 2002
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 RAA12589
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:02:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA15202
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 17:02:08 -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 QAA13922;
	Tue, 22 Jan 2002 16:44:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13891
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 16:44:19 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11774
	for <megaco@ietf.org>; Tue, 22 Jan 2002 16:44:14 -0500 (EST)
Received: from cisco.com (ssh-sj1.cisco.com [171.68.225.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA24932; Tue, 22 Jan 2002 13:41:57 -0800 (PST)
Message-ID: <3C4DDCBB.2E19BB73@cisco.com>
Date: Tue, 22 Jan 2002 16:42:20 -0500
From: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Kaul, Bharat'" <bharat@trillium.com>, megaco@ietf.org
Subject: Re: [Megaco] Doubt regarding immAckRequired field.
References: <4D79C746863DD51197690002A52CDA000102AECA@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit



Tom-PT Taylor wrote:

> I finally made the effort to track down the original issue that led to the
> specification of immAckRequired back in Feb'00.  Here is the reason as
> stated at the time (from a Chip Sharp/Flemming Andreasen intervention):
>
> <begin>
>
> Section:        D.1.4
> Category:       Technical
> Issue:          The draft text specifies that receipt of a provisional
> response
> will imply a switch to a longer repetition timer for the transaction.
> However, there is no other reliability mechanism in place to detect the
> loss of the final response for that transaction, and consequently a lost
> final response may not be detected for a while (depends on the longer
> repetition timer). This leads to suboptimal behaviour of the protocol with
> unnecessary long time-outs.
> Proposal:       It is proposed, that a final response issued after a
> provisional
> response requires an immediate confirmation to enable rapid detection of a
> lost final response. Since the provisional response itself may be lost,
> this implies that the final response should include an indication that a
> response acknowledgement is required (immediately).
>
> <end>
>
> The implication is that it's not just a matter of the response sender's
> convenience (i.e. faster clearing of buffers), but of ensuring that the
> response is retransmitted as quickly as possible in the event of loss.  The
> problem is that we don't actually have any text which says that the
> responder should retransmit responses of its own accord.  J K Ramchandra
> appears to be right in saying that responses are retransmitted only when
> retransmitted requests are received.
>
> Flemming, is this an oversight and departure from what was really intended?

Yes. The idea was, that upon receiving a provisional response, you switch to a
longer repetition timer aimed at detecting endpoint/termination failures as
opposed to transmission problems. If you don't employ active retransmission of
the final response, a lost final response will only be resent at the long
transaction retransmit interval, which is suboptimal. Depending on the timer
values involved, it could even lead to the transaction timing out (incorrectly).

-- Flemming


>


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



From megaco-admin@ietf.org  Tue Jan 22 17:48:33 2002
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 RAA13599
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:48:33 -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 RAA16190;
	Tue, 22 Jan 2002 17:40:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16098
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:40:39 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13506
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:40:35 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMe7S11849;
	Tue, 22 Jan 2002 17:40:07 -0500 (EST)
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 g0MMe6S29652;
	Tue, 22 Jan 2002 17:40:06 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYXZG>; Tue, 22 Jan 2002 17:40:06 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Stefanioros Nikolaos'" <Nikolaos.Stefanioros@siemens.gr>,
        megaco@ietf.org
Subject: RE: [Megaco] Question regarding ServiceChange command.
Date: Tue, 22 Jan 2002 17:40:04 -0500
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

This is a matter of configuration.  If no port is configured, the MG must
use the default port.

-----Original Message-----
From: Stefanioros Nikolaos [mailto:Nikolaos.Stefanioros@siemens.gr]
Sent: Friday, January 18, 2002 2:56 AM
To: megaco@ietf.org
Subject: [Megaco] Question regarding ServiceChange command.


Hi everybody,

could someone give me an answer to the following question?

In case of "cold start", the MG sends a ServiceChange command towards its
primary MGC. This ServiceChange command should be sent to the default port
of MGC (2944 for Text encoded or 2945 for Binary encoded messages) or to any
other port of MGC?

Regards.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 942 980181
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



_______________________________________________
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


From daemon@ns.ietf.org  Tue Jan 22 17:48:40 2002
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 RAA13615
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:48:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16436
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 17:48:36 -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 RAA16190;
	Tue, 22 Jan 2002 17:40:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16098
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:40:39 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13506
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:40:35 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMe7S11849;
	Tue, 22 Jan 2002 17:40:07 -0500 (EST)
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 g0MMe6S29652;
	Tue, 22 Jan 2002 17:40:06 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYXZG>; Tue, 22 Jan 2002 17:40:06 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Stefanioros Nikolaos'" <Nikolaos.Stefanioros@siemens.gr>,
        megaco@ietf.org
Subject: RE: [Megaco] Question regarding ServiceChange command.
Date: Tue, 22 Jan 2002 17:40:04 -0500
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

This is a matter of configuration.  If no port is configured, the MG must
use the default port.

-----Original Message-----
From: Stefanioros Nikolaos [mailto:Nikolaos.Stefanioros@siemens.gr]
Sent: Friday, January 18, 2002 2:56 AM
To: megaco@ietf.org
Subject: [Megaco] Question regarding ServiceChange command.


Hi everybody,

could someone give me an answer to the following question?

In case of "cold start", the MG sends a ServiceChange command towards its
primary MGC. This ServiceChange command should be sent to the default port
of MGC (2944 for Text encoded or 2945 for Binary encoded messages) or to any
other port of MGC?

Regards.

..................................................................
Mit freundlichem Gruss / kind regards
Nikolaos Stefanioros
Siemens A.E.
Development, Innovations & Projects
Software Center I&C Networks
Promitheos Str. 12
GR-145 64 Nea Kifissia / Athens
Greece
Tel.: +30 10 6864 380
Fax: +30 10 6247 978
Mobile : +30 942 980181
mailto:Nikolaos.Stefanioros@siemens.gr
..................................................................



_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 22 17:52:40 2002
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 RAA13754
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:52:39 -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 RAA16020;
	Tue, 22 Jan 2002 17:34:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA15989
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:34:46 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13396
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:34:43 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0MMYi618718;
	Tue, 22 Jan 2002 17:34:45 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id RAA03643;
	Tue, 22 Jan 2002 17:34:43 -0500 (EST)
Message-ID: <3C4DE848.7665C53D@lucent.com>
Date: Tue, 22 Jan 2002 17:31:37 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------F6480557F6828CC3A832B3BF"
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

This is a multi-part message in MIME format.
--------------F6480557F6828CC3A832B3BF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
through a later Modify.  I can see an advantage to using this feature rather than FID,
although we would be going a different direction that other protocols using SDP (SIP, etc)
just as we are for negotation.  But I think that the semantics need to be specified in the
protocol.

If a Stream has multiple groups:
1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
to all?  It IS stated that
    "(c) If multiple gropus of properties are present in a Local or Remote descriptor or
multiple values within a group, the order of preference is descending."

I assumed that this was preference for choosing for the reply, but if media begins to flow
with multiple groups present this could be interpretted as preference for deciding which to
use for a media packet.

If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
using all codecs, one can send using any of them but left most is preferred.  Is this your
interpretation of multiple groups as well: send to one, first preferred?  When would you send
to other than first?  Only when the first did not have a payload suitable?

2) In Remote, this requires receiving packets on multiple ports and mixing them.  An MG that
cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But how
can it indicate that it cannot accept multiple groups that would require mixing?

I cannot see how all this


Christian Groves wrote:

> G'Day Terry,
>
> Reserve Group and Reserve Value give you the ability to support all
> choices in a single stream. One use is in the case of negotiation but
> the text doesn't limit you to this case. I see FID can be implemented
> with reserve group because you can have seperate RTP in different groups
> being part of the one logical stream. One group can specify DTMF,
> another can specify audio codec and you can set  them to different
> IP/port combinations if you wish but these will all be part of the same
> stream descriptor.
>
> If we map the FID groups into different H.248 stream IDs then we don't
> have the problem with the ("m=") that was in the email that kicked off
> this discussion. I don't see the reason why to use distinct terminations
> for each m= line. In terms of specifying synchronisation, a statement
> was already added in v1 7.1.4 "Multiple streams exiting a termination
> shall be synchronized with each other."
>
> Thus I don't a reason to make changes.
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > Value". It allows the FID concept (group ID).
> >
> > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > all choices it can support  among alternatives in a single stream (as well as reserving
> > the resources for those in reply).  I've always assumed that this was simply a first
> > step in negotiation and before the call was fully setup a single Group would be chosen
> > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > believe that a call will function with multiple groups still present?  If so, where do
> > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > With Remote, would we send to ALL groups?
> >
> > I think Reserve Group and Reserve Value are in the subject line only because the
> > original question on this topic lead to the noticing the single m line restriction and
> > FID was an additional reason for concern about this.  I should have changed the subject
> > before continuing the discussion of multiple m lines.
> >
> > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > streams are grouped into a single media stream (or streams are coordinated such as video
> > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > archetypical example, given in the FID draft is where a single audio media stream is
> > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > sessions are combined into one.
> >
> > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > This is essentially equivalent to using distinct terminations for each m line and
> > putting all the terminations in the same context with appropriate topology descriptor.
> > FID does have some restrictions on the use of each m line that are a little different.
> > It assumes that the flow will be encoded using a single codec and sent only to the m
> > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > to indicate this behavior with additional terminations in the context, where it would
> > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > codec (that is, telephone-event to one AND codec encoded tone to other).
> >
> > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > single SDP description.  I would think that audio and video whould still need to be in
> > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > single Stream Descriptor.
> >
> > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > suggest other reasons we need it or how it would be used.
> >
> > > With regards to sending
> > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > think we need a change.
> >
> > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > much easier to coordinate time when regenerating the tones in the media channel.  There
> > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > the DTMF at the correct time in the media channel.
> >
> > >
> > >
> > > Regards, Christian
> > >
> > > Troy Cauble wrote:
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > too restrictive.
> > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > distinct payload.  It also supports sending this payload to a different
> > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > again requires multiple media (m) lines in the SDP.
> > > > >
> > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > bullets):
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT include more than one media description
> > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > distinct Stream Descriptors.
> > > > >
> > > > > Perhaps we could change this to read:
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > that the session description will contain only a single media description ("m="
> > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > logical media stream but where payload packets may be sent to different
> > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > Descriptors.
> > > > > --------
> > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > Informative References, but I think this helps clarify the intent with an
> > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > >
> > > > I have no problem with the intent of this change.  You have to
> > > > change the language to allow certain cases.  But the language
> > > > is getting very fuzzy.
> > > >
> > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > >
> > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > audio + video is "multiple streams"?
> > > >
> > > > When would an MG be handling multiple streams on a termination
> > > > that are not "logically" related in some way?
> > > >
> > > > Doesn't this really mean I can put as many "streams" as I want
> > > > in my SDP and have just one StreamDescriptor?
> > > >
> > > > -troy
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------F6480557F6828CC3A832B3BF
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------F6480557F6828CC3A832B3BF--


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


From daemon@ns.ietf.org  Tue Jan 22 17:52:40 2002
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 RAA13765
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:52:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16612
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 17:52:43 -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 RAA16020;
	Tue, 22 Jan 2002 17:34:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA15989
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:34:46 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13396
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:34:43 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0MMYi618718;
	Tue, 22 Jan 2002 17:34:45 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id RAA03643;
	Tue, 22 Jan 2002 17:34:43 -0500 (EST)
Message-ID: <3C4DE848.7665C53D@lucent.com>
Date: Tue, 22 Jan 2002 17:31:37 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------F6480557F6828CC3A832B3BF"
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

This is a multi-part message in MIME format.
--------------F6480557F6828CC3A832B3BF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
through a later Modify.  I can see an advantage to using this feature rather than FID,
although we would be going a different direction that other protocols using SDP (SIP, etc)
just as we are for negotation.  But I think that the semantics need to be specified in the
protocol.

If a Stream has multiple groups:
1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
to all?  It IS stated that
    "(c) If multiple gropus of properties are present in a Local or Remote descriptor or
multiple values within a group, the order of preference is descending."

I assumed that this was preference for choosing for the reply, but if media begins to flow
with multiple groups present this could be interpretted as preference for deciding which to
use for a media packet.

If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
using all codecs, one can send using any of them but left most is preferred.  Is this your
interpretation of multiple groups as well: send to one, first preferred?  When would you send
to other than first?  Only when the first did not have a payload suitable?

2) In Remote, this requires receiving packets on multiple ports and mixing them.  An MG that
cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But how
can it indicate that it cannot accept multiple groups that would require mixing?

I cannot see how all this


Christian Groves wrote:

> G'Day Terry,
>
> Reserve Group and Reserve Value give you the ability to support all
> choices in a single stream. One use is in the case of negotiation but
> the text doesn't limit you to this case. I see FID can be implemented
> with reserve group because you can have seperate RTP in different groups
> being part of the one logical stream. One group can specify DTMF,
> another can specify audio codec and you can set  them to different
> IP/port combinations if you wish but these will all be part of the same
> stream descriptor.
>
> If we map the FID groups into different H.248 stream IDs then we don't
> have the problem with the ("m=") that was in the email that kicked off
> this discussion. I don't see the reason why to use distinct terminations
> for each m= line. In terms of specifying synchronisation, a statement
> was already added in v1 7.1.4 "Multiple streams exiting a termination
> shall be synchronized with each other."
>
> Thus I don't a reason to make changes.
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > Value". It allows the FID concept (group ID).
> >
> > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > all choices it can support  among alternatives in a single stream (as well as reserving
> > the resources for those in reply).  I've always assumed that this was simply a first
> > step in negotiation and before the call was fully setup a single Group would be chosen
> > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > believe that a call will function with multiple groups still present?  If so, where do
> > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > With Remote, would we send to ALL groups?
> >
> > I think Reserve Group and Reserve Value are in the subject line only because the
> > original question on this topic lead to the noticing the single m line restriction and
> > FID was an additional reason for concern about this.  I should have changed the subject
> > before continuing the discussion of multiple m lines.
> >
> > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > streams are grouped into a single media stream (or streams are coordinated such as video
> > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > archetypical example, given in the FID draft is where a single audio media stream is
> > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > sessions are combined into one.
> >
> > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > This is essentially equivalent to using distinct terminations for each m line and
> > putting all the terminations in the same context with appropriate topology descriptor.
> > FID does have some restrictions on the use of each m line that are a little different.
> > It assumes that the flow will be encoded using a single codec and sent only to the m
> > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > to indicate this behavior with additional terminations in the context, where it would
> > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > codec (that is, telephone-event to one AND codec encoded tone to other).
> >
> > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > single SDP description.  I would think that audio and video whould still need to be in
> > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > single Stream Descriptor.
> >
> > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > suggest other reasons we need it or how it would be used.
> >
> > > With regards to sending
> > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > think we need a change.
> >
> > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > much easier to coordinate time when regenerating the tones in the media channel.  There
> > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > the DTMF at the correct time in the media channel.
> >
> > >
> > >
> > > Regards, Christian
> > >
> > > Troy Cauble wrote:
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > too restrictive.
> > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > distinct payload.  It also supports sending this payload to a different
> > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > again requires multiple media (m) lines in the SDP.
> > > > >
> > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > bullets):
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT include more than one media description
> > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > distinct Stream Descriptors.
> > > > >
> > > > > Perhaps we could change this to read:
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > that the session description will contain only a single media description ("m="
> > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > logical media stream but where payload packets may be sent to different
> > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > Descriptors.
> > > > > --------
> > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > Informative References, but I think this helps clarify the intent with an
> > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > >
> > > > I have no problem with the intent of this change.  You have to
> > > > change the language to allow certain cases.  But the language
> > > > is getting very fuzzy.
> > > >
> > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > >
> > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > audio + video is "multiple streams"?
> > > >
> > > > When would an MG be handling multiple streams on a termination
> > > > that are not "logically" related in some way?
> > > >
> > > > Doesn't this really mean I can put as many "streams" as I want
> > > > in my SDP and have just one StreamDescriptor?
> > > >
> > > > -troy
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------F6480557F6828CC3A832B3BF
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------F6480557F6828CC3A832B3BF--


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



From megaco-admin@ietf.org  Tue Jan 22 17:55:32 2002
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 RAA13830
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:55:32 -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 RAA16353;
	Tue, 22 Jan 2002 17:45:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16321
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:45:46 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13575
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:45:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMjES12269;
	Tue, 22 Jan 2002 17:45:14 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMjCT14874;
	Tue, 22 Jan 2002 17:45:12 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYX91>; Tue, 22 Jan 2002 17:45:04 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] ***In CASE of faulti address .. ?
Date: Tue, 22 Jan 2002 17:44:58 -0500
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

The protocol talks about digit maps, which may either be configured in the
MG or passed to it by the MGC.  The MGC activates monitoring of dialled
digits against a particular digit map.  The procedure when no pattern is
matched is spelled out in section 7.1.14 of the specification (RFC
3015/H.248v1).



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Friday, January 18, 2002 7:50 AM
To: megaco@ietf.org
Subject: [Megaco] ***In CASE of faulti address .. ?



Hi all

 I have a doubt about a sequence in MG side. In case MG detects a faulty
number which 1user has dialed ( no match in dial plan ). Then how should MG
react to such a case. ? Should he intimate MGc about the faulti number
detection .. ?

regs
sree 


_______________________________________________
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


From daemon@ns.ietf.org  Tue Jan 22 17:55:33 2002
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 RAA13838
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:55:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16736
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 17:55:35 -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 RAA16353;
	Tue, 22 Jan 2002 17:45:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16321
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:45:46 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13575
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:45:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMjES12269;
	Tue, 22 Jan 2002 17:45:14 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0MMjCT14874;
	Tue, 22 Jan 2002 17:45:12 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZYX91>; Tue, 22 Jan 2002 17:45:04 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'sree  gk'" <sgk73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] ***In CASE of faulti address .. ?
Date: Tue, 22 Jan 2002 17:44:58 -0500
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

The protocol talks about digit maps, which may either be configured in the
MG or passed to it by the MGC.  The MGC activates monitoring of dialled
digits against a particular digit map.  The procedure when no pattern is
matched is spelled out in section 7.1.14 of the specification (RFC
3015/H.248v1).



-----Original Message-----
From: sree gk [mailto:sgk73@rediffmail.com]
Sent: Friday, January 18, 2002 7:50 AM
To: megaco@ietf.org
Subject: [Megaco] ***In CASE of faulti address .. ?



Hi all

 I have a doubt about a sequence in MG side. In case MG detects a faulty
number which 1user has dialed ( no match in dial plan ). Then how should MG
react to such a case. ? Should he intimate MGc about the faulti number
detection .. ?

regs
sree 


_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 22 17:56:33 2002
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 RAA13881
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:56:28 -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 RAA16310;
	Tue, 22 Jan 2002 17:45:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16281
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:45:35 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13571
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:45:31 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0MMjX622411;
	Tue, 22 Jan 2002 17:45:33 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id RAA04143;
	Tue, 22 Jan 2002 17:45:33 -0500 (EST)
Message-ID: <3C4DEAD2.8CCBFBE0@lucent.com>
Date: Tue, 22 Jan 2002 17:42:26 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------9EDE38A91477D8FAA1F9919F"
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

This is a multi-part message in MIME format.
--------------9EDE38A91477D8FAA1F9919F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
through a later Modify.  I can see an advantage to using this feature rather than FID,
although we would be going a different direction that other protocols using SDP (SIP, etc)
just as we are for negotation.  But I think that the semantics need to be specified in the
protocol.

If a Stream has multiple groups:
1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
to all?  It IS stated that
    "(c) If multiple groups of properties are present in a Local or Remote descriptor or
multiple values within a group, the order of preference is descending."

I assumed that this was preference for choosing for the reply, but if media begins to flow
with multiple groups present this could be interpretted as preference for deciding which to
use for a media packet.

If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
using all codecs, one can send using any of them but left most is preferred.  Is this your
interpretation of multiple groups as well: send to one, first preferred?  When would you send
to other than first?  Only when the first did not have a payload suitable?  [FID supports
sending to multiple if they have the same payload.]

2) In Remote, does this requires receiving packets on multiple ports and mixing them?  An MG
that cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But
how can it indicate that it cannot accept multiple groups that would require mixing?

If is what H.248 intends with ReserveGroup it seems that the behavior must be much more
specified than it is in 7.1.8.


Christian Groves wrote:

> G'Day Terry,
>
> Reserve Group and Reserve Value give you the ability to support all
> choices in a single stream. One use is in the case of negotiation but
> the text doesn't limit you to this case. I see FID can be implemented
> with reserve group because you can have seperate RTP in different groups
> being part of the one logical stream. One group can specify DTMF,
> another can specify audio codec and you can set  them to different
> IP/port combinations if you wish but these will all be part of the same
> stream descriptor.
>
> If we map the FID groups into different H.248 stream IDs then we don't
> have the problem with the ("m=") that was in the email that kicked off
> this discussion. I don't see the reason why to use distinct terminations
> for each m= line. In terms of specifying synchronisation, a statement
> was already added in v1 7.1.4 "Multiple streams exiting a termination
> shall be synchronized with each other."
>
> Thus I don't a reason to make changes.
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > Value". It allows the FID concept (group ID).
> >
> > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > all choices it can support  among alternatives in a single stream (as well as reserving
> > the resources for those in reply).  I've always assumed that this was simply a first
> > step in negotiation and before the call was fully setup a single Group would be chosen
> > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > believe that a call will function with multiple groups still present?  If so, where do
> > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > With Remote, would we send to ALL groups?
> >
> > I think Reserve Group and Reserve Value are in the subject line only because the
> > original question on this topic lead to the noticing the single m line restriction and
> > FID was an additional reason for concern about this.  I should have changed the subject
> > before continuing the discussion of multiple m lines.
> >
> > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > streams are grouped into a single media stream (or streams are coordinated such as video
> > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > archetypical example, given in the FID draft is where a single audio media stream is
> > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > sessions are combined into one.
> >
> > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > This is essentially equivalent to using distinct terminations for each m line and
> > putting all the terminations in the same context with appropriate topology descriptor.
> > FID does have some restrictions on the use of each m line that are a little different.
> > It assumes that the flow will be encoded using a single codec and sent only to the m
> > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > to indicate this behavior with additional terminations in the context, where it would
> > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > codec (that is, telephone-event to one AND codec encoded tone to other).
> >
> > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > single SDP description.  I would think that audio and video whould still need to be in
> > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > single Stream Descriptor.
> >
> > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > suggest other reasons we need it or how it would be used.
> >
> > > With regards to sending
> > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > think we need a change.
> >
> > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > much easier to coordinate time when regenerating the tones in the media channel.  There
> > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > the DTMF at the correct time in the media channel.
> >
> > >
> > >
> > > Regards, Christian
> > >
> > > Troy Cauble wrote:
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > too restrictive.
> > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > distinct payload.  It also supports sending this payload to a different
> > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > again requires multiple media (m) lines in the SDP.
> > > > >
> > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > bullets):
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT include more than one media description
> > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > distinct Stream Descriptors.
> > > > >
> > > > > Perhaps we could change this to read:
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > that the session description will contain only a single media description ("m="
> > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > logical media stream but where payload packets may be sent to different
> > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > Descriptors.
> > > > > --------
> > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > Informative References, but I think this helps clarify the intent with an
> > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > >
> > > > I have no problem with the intent of this change.  You have to
> > > > change the language to allow certain cases.  But the language
> > > > is getting very fuzzy.
> > > >
> > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > >
> > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > audio + video is "multiple streams"?
> > > >
> > > > When would an MG be handling multiple streams on a termination
> > > > that are not "logically" related in some way?
> > > >
> > > > Doesn't this really mean I can put as many "streams" as I want
> > > > in my SDP and have just one StreamDescriptor?
> > > >
> > > > -troy
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------9EDE38A91477D8FAA1F9919F
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------9EDE38A91477D8FAA1F9919F--


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


From daemon@ns.ietf.org  Tue Jan 22 17:56:34 2002
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 RAA13891
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 17:56:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16755
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 17:56:36 -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 RAA16310;
	Tue, 22 Jan 2002 17:45:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16281
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 17:45:35 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13571
	for <megaco@ietf.org>; Tue, 22 Jan 2002 17:45:31 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0MMjX622411;
	Tue, 22 Jan 2002 17:45:33 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id RAA04143;
	Tue, 22 Jan 2002 17:45:33 -0500 (EST)
Message-ID: <3C4DEAD2.8CCBFBE0@lucent.com>
Date: Tue, 22 Jan 2002 17:42:26 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------9EDE38A91477D8FAA1F9919F"
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

This is a multi-part message in MIME format.
--------------9EDE38A91477D8FAA1F9919F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
through a later Modify.  I can see an advantage to using this feature rather than FID,
although we would be going a different direction that other protocols using SDP (SIP, etc)
just as we are for negotation.  But I think that the semantics need to be specified in the
protocol.

If a Stream has multiple groups:
1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
to all?  It IS stated that
    "(c) If multiple groups of properties are present in a Local or Remote descriptor or
multiple values within a group, the order of preference is descending."

I assumed that this was preference for choosing for the reply, but if media begins to flow
with multiple groups present this could be interpretted as preference for deciding which to
use for a media packet.

If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
using all codecs, one can send using any of them but left most is preferred.  Is this your
interpretation of multiple groups as well: send to one, first preferred?  When would you send
to other than first?  Only when the first did not have a payload suitable?  [FID supports
sending to multiple if they have the same payload.]

2) In Remote, does this requires receiving packets on multiple ports and mixing them?  An MG
that cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But
how can it indicate that it cannot accept multiple groups that would require mixing?

If is what H.248 intends with ReserveGroup it seems that the behavior must be much more
specified than it is in 7.1.8.


Christian Groves wrote:

> G'Day Terry,
>
> Reserve Group and Reserve Value give you the ability to support all
> choices in a single stream. One use is in the case of negotiation but
> the text doesn't limit you to this case. I see FID can be implemented
> with reserve group because you can have seperate RTP in different groups
> being part of the one logical stream. One group can specify DTMF,
> another can specify audio codec and you can set  them to different
> IP/port combinations if you wish but these will all be part of the same
> stream descriptor.
>
> If we map the FID groups into different H.248 stream IDs then we don't
> have the problem with the ("m=") that was in the email that kicked off
> this discussion. I don't see the reason why to use distinct terminations
> for each m= line. In terms of specifying synchronisation, a statement
> was already added in v1 7.1.4 "Multiple streams exiting a termination
> shall be synchronized with each other."
>
> Thus I don't a reason to make changes.
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry,
> > >
> > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > Value". It allows the FID concept (group ID).
> >
> > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > all choices it can support  among alternatives in a single stream (as well as reserving
> > the resources for those in reply).  I've always assumed that this was simply a first
> > step in negotiation and before the call was fully setup a single Group would be chosen
> > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > believe that a call will function with multiple groups still present?  If so, where do
> > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > With Remote, would we send to ALL groups?
> >
> > I think Reserve Group and Reserve Value are in the subject line only because the
> > original question on this topic lead to the noticing the single m line restriction and
> > FID was an additional reason for concern about this.  I should have changed the subject
> > before continuing the discussion of multiple m lines.
> >
> > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > streams are grouped into a single media stream (or streams are coordinated such as video
> > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > archetypical example, given in the FID draft is where a single audio media stream is
> > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > sessions are combined into one.
> >
> > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > This is essentially equivalent to using distinct terminations for each m line and
> > putting all the terminations in the same context with appropriate topology descriptor.
> > FID does have some restrictions on the use of each m line that are a little different.
> > It assumes that the flow will be encoded using a single codec and sent only to the m
> > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > to indicate this behavior with additional terminations in the context, where it would
> > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > codec (that is, telephone-event to one AND codec encoded tone to other).
> >
> > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > single SDP description.  I would think that audio and video whould still need to be in
> > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > single Stream Descriptor.
> >
> > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > suggest other reasons we need it or how it would be used.
> >
> > > With regards to sending
> > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > think we need a change.
> >
> > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > much easier to coordinate time when regenerating the tones in the media channel.  There
> > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > the DTMF at the correct time in the media channel.
> >
> > >
> > >
> > > Regards, Christian
> > >
> > > Troy Cauble wrote:
> > > >
> > > > Terry L Anderson wrote:
> > > > >
> > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > too restrictive.
> > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > distinct payload.  It also supports sending this payload to a different
> > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > again requires multiple media (m) lines in the SDP.
> > > > >
> > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > bullets):
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT include more than one media description
> > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > distinct Stream Descriptors.
> > > > >
> > > > > Perhaps we could change this to read:
> > > > >
> > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > that the session description will contain only a single media description ("m="
> > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > logical media stream but where payload packets may be sent to different
> > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > Descriptors.
> > > > > --------
> > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > Informative References, but I think this helps clarify the intent with an
> > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > >
> > > > I have no problem with the intent of this change.  You have to
> > > > change the language to allow certain cases.  But the language
> > > > is getting very fuzzy.
> > > >
> > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > >
> > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > audio + video is "multiple streams"?
> > > >
> > > > When would an MG be handling multiple streams on a termination
> > > > that are not "logically" related in some way?
> > > >
> > > > Doesn't this really mean I can put as many "streams" as I want
> > > > in my SDP and have just one StreamDescriptor?
> > > >
> > > > -troy
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------9EDE38A91477D8FAA1F9919F
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------9EDE38A91477D8FAA1F9919F--


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



From megaco-admin@ietf.org  Tue Jan 22 19:56:42 2002
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 TAA15877
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 19:56:42 -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 TAA19991;
	Tue, 22 Jan 2002 19:35:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19962
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 19:35:44 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15488
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:35:40 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA13346
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:34:19 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA12400
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:35:40 +1100 (EST)
Message-ID: <3C4E063F.90D3E460@ericsson.com.au>
Date: Wed, 23 Jan 2002 11:39:27 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <65256B49.004B3C03.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Kapil,

Yes that applies the properties which the MGC doesn't want anymore.

Regards, Christian

knayar@hss.hns.com wrote:
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
> 
> "If the MGC wishes to delete some information from the existing descriptor, it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped out."
> 
> Does the "unwanted information" refer to the properties which the MGC no more
> requires to be set on the termination......
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> _______________________________________________
> 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


From daemon@ns.ietf.org  Tue Jan 22 19:56:43 2002
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 TAA15888
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 19:56:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA20465
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 19:56:45 -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 TAA19991;
	Tue, 22 Jan 2002 19:35:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19962
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 19:35:44 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15488
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:35:40 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA13346
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:34:19 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA12400
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:35:40 +1100 (EST)
Message-ID: <3C4E063F.90D3E460@ericsson.com.au>
Date: Wed, 23 Jan 2002 11:39:27 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <65256B49.004B3C03.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Kapil,

Yes that applies the properties which the MGC doesn't want anymore.

Regards, Christian

knayar@hss.hns.com wrote:
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
> 
> "If the MGC wishes to delete some information from the existing descriptor, it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped out."
> 
> Does the "unwanted information" refer to the properties which the MGC no more
> requires to be set on the termination......
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 22 20:13:29 2002
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 UAA16261
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 20:13:29 -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 TAA20227;
	Tue, 22 Jan 2002 19:48:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20201
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 19:48:00 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15674
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:47:57 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA15754;
	Wed, 23 Jan 2002 11:46:36 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA15384;
	Wed, 23 Jan 2002 11:47:57 +1100 (EST)
Message-ID: <3C4E0920.9D9D2615@ericsson.com.au>
Date: Wed, 23 Jan 2002 11:51:44 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Issues In H.248v2: Context Packages
References: <4D79C746863DD51197690002A52CDA000102AEB4@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

That's fine however as I mentioned in the email below could you send a
list of reasons why to remove context properties. Not all 1200 people on
the mailing list were at the meeting so I wouldn't expect them to
confirm the show of hands without any information on what they're
actually confirming?

Are all the arguments given in the meeting report? Are they a seperate
contribution/draft?

Regards, Christian

Tom-PT Taylor wrote:
> 
> It was done by show of hands.  This was the one item on the H.248v2 list for
> which the balance of sentiment was clear to everyone in the room.
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 21, 2002 10:20 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Issues In H.248v2: Context Packages
> 
> Hello Tom,
> 
> How was the sentiment on the context property recorded at the meeting?
> Was there a hum poll or similar? If you are asking the list to confirm
> this what particular arguments are there for delaying this? What
> implications haven't been studied?
> 
> Cheers, Christian
> 
> Tom-PT Taylor wrote:
> >
> > I was waiting for others to raise issues for our contribution to SG 16,
> but
> > there hasn't been much addressed specifically to H.248v2.  This is the
> first
> > of a series of E-mails I am going to generate on the topic.
> >
> > The sentiment at IETF 52 was that packages for context properties were the
> > one item that we would like to have SG 16 to defer until the full
> > implications are realized.  That is, it should not be included in H.248v2.
> > Can I confirm this view with the list?
> >
> > Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> >
> >  - delete final bullet of section 6.1.1
> >
> >  - delete final sentence of first paragraph of section 6.2.3
> >
> >  - delete second sentence of second paragraph of section 6.2.3
> >
> >  - delete the phrase "or Context" from the last sentence of second
> paragraph
> > of section 6.2.3
> >
> >  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> > subsequent section(s) accordingly
> >
> >  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> > follows:
> >    -- in the third paragraph, amend the final sentence to say "There are
> two
> > types of audit."
> >    -- in the paragraphs beginning "Value Audit:" and "Capabilities
> Audit:",
> > delete the phrase "the ContextAttribute Descriptor or"
> >    -- delete the paragraph beginning "Packages Audit"
> >    -- delete the Audit Packages column of the table
> >
> >  - delete the phrase "and contexts" in the first paragraph of section 12
> >
> >  - delete the sentence beginning "ContextAttribute is for ..." and also
> the
> > final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> >
> >  - delete the final sentence of the paragraph explaining
> "Characteristics:"
> > in section 12.1.2
> >
> >  - in Annex A:
> >    -- delete the contextProp and contextPackages components added after
> the
> > extension marker in the ContextRequest production
> >    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> > contextPropCapAud, and contextPackagesAud components added after the
> > extension marker in the ContextAttrAuditRequest production
> >
> >  - in Annex B:
> >    -- delete the contextAttrDescriptor and packagesDescriptor terms from
> the
> > contextProperty production
> >    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> > IndAudContextAttrCap, and ContextAttrPackages terms from the
> > contextAuditProperties production
> >    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> > ContextAttrDescriptorCapAud productions
> >    -- delete the contextAttrDescriptor production
> >    -- delete the ContextAttrToken, ContextAudCapToken,
> > ContextAudDescriptorToken, and ContextAudValToken productions
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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


From daemon@ns.ietf.org  Tue Jan 22 20:13:30 2002
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 UAA16272
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 20:13:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA21130
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 20:13:32 -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 TAA20227;
	Tue, 22 Jan 2002 19:48:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20201
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 19:48:00 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15674
	for <megaco@ietf.org>; Tue, 22 Jan 2002 19:47:57 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA15754;
	Wed, 23 Jan 2002 11:46:36 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA15384;
	Wed, 23 Jan 2002 11:47:57 +1100 (EST)
Message-ID: <3C4E0920.9D9D2615@ericsson.com.au>
Date: Wed, 23 Jan 2002 11:51:44 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Issues In H.248v2: Context Packages
References: <4D79C746863DD51197690002A52CDA000102AEB4@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

That's fine however as I mentioned in the email below could you send a
list of reasons why to remove context properties. Not all 1200 people on
the mailing list were at the meeting so I wouldn't expect them to
confirm the show of hands without any information on what they're
actually confirming?

Are all the arguments given in the meeting report? Are they a seperate
contribution/draft?

Regards, Christian

Tom-PT Taylor wrote:
> 
> It was done by show of hands.  This was the one item on the H.248v2 list for
> which the balance of sentiment was clear to everyone in the room.
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 21, 2002 10:20 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Issues In H.248v2: Context Packages
> 
> Hello Tom,
> 
> How was the sentiment on the context property recorded at the meeting?
> Was there a hum poll or similar? If you are asking the list to confirm
> this what particular arguments are there for delaying this? What
> implications haven't been studied?
> 
> Cheers, Christian
> 
> Tom-PT Taylor wrote:
> >
> > I was waiting for others to raise issues for our contribution to SG 16,
> but
> > there hasn't been much addressed specifically to H.248v2.  This is the
> first
> > of a series of E-mails I am going to generate on the topic.
> >
> > The sentiment at IETF 52 was that packages for context properties were the
> > one item that we would like to have SG 16 to defer until the full
> > implications are realized.  That is, it should not be included in H.248v2.
> > Can I confirm this view with the list?
> >
> > Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> >
> >  - delete final bullet of section 6.1.1
> >
> >  - delete final sentence of first paragraph of section 6.2.3
> >
> >  - delete second sentence of second paragraph of section 6.2.3
> >
> >  - delete the phrase "or Context" from the last sentence of second
> paragraph
> > of section 6.2.3
> >
> >  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> > subsequent section(s) accordingly
> >
> >  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> > follows:
> >    -- in the third paragraph, amend the final sentence to say "There are
> two
> > types of audit."
> >    -- in the paragraphs beginning "Value Audit:" and "Capabilities
> Audit:",
> > delete the phrase "the ContextAttribute Descriptor or"
> >    -- delete the paragraph beginning "Packages Audit"
> >    -- delete the Audit Packages column of the table
> >
> >  - delete the phrase "and contexts" in the first paragraph of section 12
> >
> >  - delete the sentence beginning "ContextAttribute is for ..." and also
> the
> > final sentence of the paragraph explaining "Defined in:" in section 12.1.2
> >
> >  - delete the final sentence of the paragraph explaining
> "Characteristics:"
> > in section 12.1.2
> >
> >  - in Annex A:
> >    -- delete the contextProp and contextPackages components added after
> the
> > extension marker in the ContextRequest production
> >    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> > contextPropCapAud, and contextPackagesAud components added after the
> > extension marker in the ContextAttrAuditRequest production
> >
> >  - in Annex B:
> >    -- delete the contextAttrDescriptor and packagesDescriptor terms from
> the
> > contextProperty production
> >    -- delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
> > IndAudContextAttrCap, and ContextAttrPackages terms from the
> > contextAuditProperties production
> >    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> > ContextAttrDescriptorCapAud productions
> >    -- delete the contextAttrDescriptor production
> >    -- delete the ContextAttrToken, ContextAudCapToken,
> > ContextAudDescriptorToken, and ContextAudValToken productions
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Tue Jan 22 20:49:00 2002
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 UAA16955
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 20:48:59 -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 UAA21411;
	Tue, 22 Jan 2002 20:26:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA21382
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 20:26:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16624
	for <megaco@ietf.org>; Tue, 22 Jan 2002 20:26:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0N1PoS27621;
	Tue, 22 Jan 2002 20:25:50 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0N1PmT21059;
	Tue, 22 Jan 2002 20:25:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY55R>; Tue, 22 Jan 2002 20:25:49 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Issues In H.248v2: Context Packages
Date: Tue, 22 Jan 2002 20:25:48 -0500
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

The question put to the meeting was (for each feature) whether this
represented too large an increment to the base protocol at this time.  This
was a matter of individual judgement: in terms of potential implementation
burden, potential interoperability problems, potential impact on the
coherence of the protocol.  There weren't really any arguments put forward
other than what the list has seen already.

In any event, it is the WG Chair's job to judge consensus on the list.  The
IETF in its Chair's training provides helpful hints on how to do this.  I
will say now that it will take a few voices to convince me that the WG as a
whole has an opinion which differs from that shown at the meeting.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Tuesday, January 22, 2002 7:52 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Issues In H.248v2: Context Packages


G'Day Tom,

That's fine however as I mentioned in the email below could you send a
list of reasons why to remove context properties. Not all 1200 people on
the mailing list were at the meeting so I wouldn't expect them to
confirm the show of hands without any information on what they're
actually confirming?

Are all the arguments given in the meeting report? Are they a seperate
contribution/draft?

Regards, Christian

Tom-PT Taylor wrote:
> 
> It was done by show of hands.  This was the one item on the H.248v2 list
for
> which the balance of sentiment was clear to everyone in the room.
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 21, 2002 10:20 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Issues In H.248v2: Context Packages
> 
> Hello Tom,
> 
> How was the sentiment on the context property recorded at the meeting?
> Was there a hum poll or similar? If you are asking the list to confirm
> this what particular arguments are there for delaying this? What
> implications haven't been studied?
> 
> Cheers, Christian
> 
> Tom-PT Taylor wrote:
> >
> > I was waiting for others to raise issues for our contribution to SG 16,
> but
> > there hasn't been much addressed specifically to H.248v2.  This is the
> first
> > of a series of E-mails I am going to generate on the topic.
> >
> > The sentiment at IETF 52 was that packages for context properties were
the
> > one item that we would like to have SG 16 to defer until the full
> > implications are realized.  That is, it should not be included in
H.248v2.
> > Can I confirm this view with the list?
> >
> > Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> >
> >  - delete final bullet of section 6.1.1
> >
> >  - delete final sentence of first paragraph of section 6.2.3
> >
> >  - delete second sentence of second paragraph of section 6.2.3
> >
> >  - delete the phrase "or Context" from the last sentence of second
> paragraph
> > of section 6.2.3
> >
> >  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> > subsequent section(s) accordingly
> >
> >  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> > follows:
> >    -- in the third paragraph, amend the final sentence to say "There are
> two
> > types of audit."
> >    -- in the paragraphs beginning "Value Audit:" and "Capabilities
> Audit:",
> > delete the phrase "the ContextAttribute Descriptor or"
> >    -- delete the paragraph beginning "Packages Audit"
> >    -- delete the Audit Packages column of the table
> >
> >  - delete the phrase "and contexts" in the first paragraph of section 12
> >
> >  - delete the sentence beginning "ContextAttribute is for ..." and also
> the
> > final sentence of the paragraph explaining "Defined in:" in section
12.1.2
> >
> >  - delete the final sentence of the paragraph explaining
> "Characteristics:"
> > in section 12.1.2
> >
> >  - in Annex A:
> >    -- delete the contextProp and contextPackages components added after
> the
> > extension marker in the ContextRequest production
> >    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> > contextPropCapAud, and contextPackagesAud components added after the
> > extension marker in the ContextAttrAuditRequest production
> >
> >  - in Annex B:
> >    -- delete the contextAttrDescriptor and packagesDescriptor terms from
> the
> > contextProperty production
> >    -- delete the IndAudcontextAttrDescriptor,
ContextAttrDescriptorCapAud,
> > IndAudContextAttrCap, and ContextAttrPackages terms from the
> > contextAuditProperties production
> >    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> > ContextAttrDescriptorCapAud productions
> >    -- delete the contextAttrDescriptor production
> >    -- delete the ContextAttrToken, ContextAudCapToken,
> > ContextAudDescriptorToken, and ContextAudValToken productions
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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


From daemon@ns.ietf.org  Tue Jan 22 20:49:01 2002
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 UAA16964
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 20:49:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA22374
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 20:49:03 -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 UAA21411;
	Tue, 22 Jan 2002 20:26:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA21382
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 20:26:23 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16624
	for <megaco@ietf.org>; Tue, 22 Jan 2002 20:26:20 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0N1PoS27621;
	Tue, 22 Jan 2002 20:25:50 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0N1PmT21059;
	Tue, 22 Jan 2002 20:25:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZY55R>; Tue, 22 Jan 2002 20:25:49 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Issues In H.248v2: Context Packages
Date: Tue, 22 Jan 2002 20:25:48 -0500
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

The question put to the meeting was (for each feature) whether this
represented too large an increment to the base protocol at this time.  This
was a matter of individual judgement: in terms of potential implementation
burden, potential interoperability problems, potential impact on the
coherence of the protocol.  There weren't really any arguments put forward
other than what the list has seen already.

In any event, it is the WG Chair's job to judge consensus on the list.  The
IETF in its Chair's training provides helpful hints on how to do this.  I
will say now that it will take a few voices to convince me that the WG as a
whole has an opinion which differs from that shown at the meeting.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Tuesday, January 22, 2002 7:52 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Issues In H.248v2: Context Packages


G'Day Tom,

That's fine however as I mentioned in the email below could you send a
list of reasons why to remove context properties. Not all 1200 people on
the mailing list were at the meeting so I wouldn't expect them to
confirm the show of hands without any information on what they're
actually confirming?

Are all the arguments given in the meeting report? Are they a seperate
contribution/draft?

Regards, Christian

Tom-PT Taylor wrote:
> 
> It was done by show of hands.  This was the one item on the H.248v2 list
for
> which the balance of sentiment was clear to everyone in the room.
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 21, 2002 10:20 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Issues In H.248v2: Context Packages
> 
> Hello Tom,
> 
> How was the sentiment on the context property recorded at the meeting?
> Was there a hum poll or similar? If you are asking the list to confirm
> this what particular arguments are there for delaying this? What
> implications haven't been studied?
> 
> Cheers, Christian
> 
> Tom-PT Taylor wrote:
> >
> > I was waiting for others to raise issues for our contribution to SG 16,
> but
> > there hasn't been much addressed specifically to H.248v2.  This is the
> first
> > of a series of E-mails I am going to generate on the topic.
> >
> > The sentiment at IETF 52 was that packages for context properties were
the
> > one item that we would like to have SG 16 to defer until the full
> > implications are realized.  That is, it should not be included in
H.248v2.
> > Can I confirm this view with the list?
> >
> > Specific changes to current H.248v2 text (i.e. Dublin TD-47):
> >
> >  - delete final bullet of section 6.1.1
> >
> >  - delete final sentence of first paragraph of section 6.2.3
> >
> >  - delete second sentence of second paragraph of section 6.2.3
> >
> >  - delete the phrase "or Context" from the last sentence of second
> paragraph
> > of section 6.2.3
> >
> >  - delete section 7.1.19 Context Attribute Descriptor and renumber the
> > subsequent section(s) accordingly
> >
> >  - in section 7.2.9, remove references to ContextAttribute Descriptor as
> > follows:
> >    -- in the third paragraph, amend the final sentence to say "There are
> two
> > types of audit."
> >    -- in the paragraphs beginning "Value Audit:" and "Capabilities
> Audit:",
> > delete the phrase "the ContextAttribute Descriptor or"
> >    -- delete the paragraph beginning "Packages Audit"
> >    -- delete the Audit Packages column of the table
> >
> >  - delete the phrase "and contexts" in the first paragraph of section 12
> >
> >  - delete the sentence beginning "ContextAttribute is for ..." and also
> the
> > final sentence of the paragraph explaining "Defined in:" in section
12.1.2
> >
> >  - delete the final sentence of the paragraph explaining
> "Characteristics:"
> > in section 12.1.2
> >
> >  - in Annex A:
> >    -- delete the contextProp and contextPackages components added after
> the
> > extension marker in the ContextRequest production
> >    -- delete the contextPropAud, contextAttrDescriptorCapAud,
> > contextPropCapAud, and contextPackagesAud components added after the
> > extension marker in the ContextAttrAuditRequest production
> >
> >  - in Annex B:
> >    -- delete the contextAttrDescriptor and packagesDescriptor terms from
> the
> > contextProperty production
> >    -- delete the IndAudcontextAttrDescriptor,
ContextAttrDescriptorCapAud,
> > IndAudContextAttrCap, and ContextAttrPackages terms from the
> > contextAuditProperties production
> >    -- delete the IndAudContextAttrCap, ContextAttrPackages, and
> > ContextAttrDescriptorCapAud productions
> >    -- delete the contextAttrDescriptor production
> >    -- delete the ContextAttrToken, ContextAudCapToken,
> > ContextAudDescriptorToken, and ContextAudValToken productions
> >
> > Tom Taylor
> > taylor@nortelnetworks.com
> > Ph. +1 613 736 0961 (ESN 396 1490)
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Tue Jan 22 21:56:44 2002
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 VAA18981
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 21:56:44 -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 VAA24743;
	Tue, 22 Jan 2002 21:47:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24714
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:52 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18769
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:47 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03673;
	Wed, 23 Jan 2002 13:46:26 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23345;
	Wed, 23 Jan 2002 13:47:48 +1100 (EST)
Message-ID: <3C4E2534.141C427F@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:32 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: prjain@hss.hns.com
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <65256B49.006682AD.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello,

Please see my answer below.

Regards, Christian

prjain@hss.hns.com wrote:
> 
> Hi Chuong/list,
> 
> Answering to your first question, we think that there can be two interpretations
> here.
> 
> 1.  One  is that "SC Restart w/Service Restorted and ROOT"
>    means "SC Graceful w/Delay is being cancelled" and MGC should behave
>    accordingly.
> 
> 2.  The other view may be that we are trying to overload the reason as "Service
> Restored" for two different scenarios.
>      The service change reason as "Service Restored" can be used by MG in one
> scenario, wherein MG comes up afresh with no calls running over all the
> associated terminations but they all are in  In-service state.
>      The second scenario (what we are currently discussing) in which calls are
> still active and MG just wants to cancel the last generated "Graceful Shutdown"
> request.
>      Due to the overloading of the reason as "Service Restored", how would MGC
> come to know about the state of those terminations, which were earlier
> "out-of-service" even before the "graceful shutdown" request was generated.

[CHG] The MGC has a picture of the states of the MG. If other
terminations were OOS then the MGC should have previously been told of
this by other service changes. The MGC can easily distinguish between
the two conditions because it will be in a different state because it
has already received a ServiceChange Graceful from the MG. The MGC will
have to have a timer with the delay period because it will have to
perform different actions.

> 
> The above two bullets clearly convey that one should either define one more
> "Service Change Method" (may be 'cancel-graceful" as suggested by you and use
> reason as "Service Restored") or use method as "Restart" and use reason "Service
> Restored" but define a new service change reason for Cold Start of MG.
> 
> Thus we can have the following reason-method combinations.
> 1. Restart - Cold Start   (no configuration data preserved, no calls)
> 2. Restart - Cold Boot   (configuration data preserved, no calls)
> 3. Restart - Warm Boot  (configuration data preserved, calls preserved,
> transactions may be lost)
> 4. Restart - Service Restored   (configuration data preserved, calls preserved,
> cacelling the "graceful shutdown" request and the last set of "In-service"
> terminations, before "graceful shutdown" was initiated, are still In-service)
> 
> Please comment.
> 
> Thanks and Regards,
> Prashant Jain
> Vivek Bansal
> 
> >
> > "Chuong N. Nguyen" wrote:
> 
> > >
> > >
> > > MG sends SC Graceful w/Delay and terminationID=ROOT.
> > >
> > > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > > assume that
> > > 1) SC Graceful w/Delay is being cancelled?
> > > 2) All terminations are back In Service?  Even the ones that were
> > > originally OOS before the SC Graceful.
> > >
> > >
> > >    1) Graceful - indicates that the specified Terminations will be
> > > taken
> > >       out of service after the specified ServiceChangeDelay;
> > > established
> > >       connections are not yet affected, but the Media Gateway
> > > Controller
> > >       should refrain from establishing new connections and should
> > >       attempt to gracefully tear down existing connections on the
> > >       Termination(s) affected by the serviceChange command. The MG
> > >       should set termination serviceState at the expiry of
> > >       ServiceChangeDelay or the removal of the termination from an
> > >       active context (whichever is first), to "out of service".
> > >
> > >
> > > How should MGC implementation intepret the above highlighted
> > > statement?
> > > Does this mean that MGC should not try to gracefully tear down
> > > existing connections
> > > before Delay timer expired?
> > >
> > > But I think the above statement is telling MGC to try and gracefully
> > > tear down
> > > existing connections before Delay timer expired.
> > >
> > > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > > until
> > > Delay timer expired before it tries to tear down existing connections.
> > >
> > > But after Delay timer expired, MG will put all terminations out of
> > > service.
> > > Therefore there is no such thing as MGC gracefully tearing down
> > > existing connections.
> > >
> > >
> > > Christian Groves wrote:
> > >
> > > > I don't see that we need to add anything. Why can't the MG just
> > > > issue a
> > > > SC with Restart, Service Restored? The specification already allows
> > > > the
> > > > MG to do this.
> > > >
> > > > Regards, Christian
> > > >
> > > > "Chuong N. Nguyen" wrote:
> > > > >
> > > > > Hi Tom
> > > > >
> > > > > What are the possibilites of defining a mechanism of cancelling
> > > > > ServiceChange Graceful?
> > > > > That is MG send SC Graceful w/Delay=time.
> > > > > Before time expired, MG wants to cancel this ServiceChange.
> > > > >
> > > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > > Graceful cancelled"?
> > > > > 2) Done in V2 - new SC Method or Reason?
> > > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > > >
> > > > >
> > > > > Thanks
> > > > > Chuong
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >   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 ****
> > >
> > >
> 
> --
>   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 ****
> 
>   ------------------------------------------------------------------------
>                   Name: att1.htm
>    att1.htm       Type: Hypertext Markup Language (text/html)
>               Encoding: base64
>            Description: Internet HTML
> 
>   ------------------------------------------------------------------------
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and should
> not be circulated or used for any purpose other than for what it is intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."

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


From daemon@ns.ietf.org  Tue Jan 22 21:56:45 2002
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 VAA18994
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 21:56:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA25329
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 21:56:48 -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 VAA24743;
	Tue, 22 Jan 2002 21:47:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24714
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:52 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18769
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:47 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03673;
	Wed, 23 Jan 2002 13:46:26 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23345;
	Wed, 23 Jan 2002 13:47:48 +1100 (EST)
Message-ID: <3C4E2534.141C427F@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:32 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: prjain@hss.hns.com
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <65256B49.006682AD.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello,

Please see my answer below.

Regards, Christian

prjain@hss.hns.com wrote:
> 
> Hi Chuong/list,
> 
> Answering to your first question, we think that there can be two interpretations
> here.
> 
> 1.  One  is that "SC Restart w/Service Restorted and ROOT"
>    means "SC Graceful w/Delay is being cancelled" and MGC should behave
>    accordingly.
> 
> 2.  The other view may be that we are trying to overload the reason as "Service
> Restored" for two different scenarios.
>      The service change reason as "Service Restored" can be used by MG in one
> scenario, wherein MG comes up afresh with no calls running over all the
> associated terminations but they all are in  In-service state.
>      The second scenario (what we are currently discussing) in which calls are
> still active and MG just wants to cancel the last generated "Graceful Shutdown"
> request.
>      Due to the overloading of the reason as "Service Restored", how would MGC
> come to know about the state of those terminations, which were earlier
> "out-of-service" even before the "graceful shutdown" request was generated.

[CHG] The MGC has a picture of the states of the MG. If other
terminations were OOS then the MGC should have previously been told of
this by other service changes. The MGC can easily distinguish between
the two conditions because it will be in a different state because it
has already received a ServiceChange Graceful from the MG. The MGC will
have to have a timer with the delay period because it will have to
perform different actions.

> 
> The above two bullets clearly convey that one should either define one more
> "Service Change Method" (may be 'cancel-graceful" as suggested by you and use
> reason as "Service Restored") or use method as "Restart" and use reason "Service
> Restored" but define a new service change reason for Cold Start of MG.
> 
> Thus we can have the following reason-method combinations.
> 1. Restart - Cold Start   (no configuration data preserved, no calls)
> 2. Restart - Cold Boot   (configuration data preserved, no calls)
> 3. Restart - Warm Boot  (configuration data preserved, calls preserved,
> transactions may be lost)
> 4. Restart - Service Restored   (configuration data preserved, calls preserved,
> cacelling the "graceful shutdown" request and the last set of "In-service"
> terminations, before "graceful shutdown" was initiated, are still In-service)
> 
> Please comment.
> 
> Thanks and Regards,
> Prashant Jain
> Vivek Bansal
> 
> >
> > "Chuong N. Nguyen" wrote:
> 
> > >
> > >
> > > MG sends SC Graceful w/Delay and terminationID=ROOT.
> > >
> > > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > > assume that
> > > 1) SC Graceful w/Delay is being cancelled?
> > > 2) All terminations are back In Service?  Even the ones that were
> > > originally OOS before the SC Graceful.
> > >
> > >
> > >    1) Graceful - indicates that the specified Terminations will be
> > > taken
> > >       out of service after the specified ServiceChangeDelay;
> > > established
> > >       connections are not yet affected, but the Media Gateway
> > > Controller
> > >       should refrain from establishing new connections and should
> > >       attempt to gracefully tear down existing connections on the
> > >       Termination(s) affected by the serviceChange command. The MG
> > >       should set termination serviceState at the expiry of
> > >       ServiceChangeDelay or the removal of the termination from an
> > >       active context (whichever is first), to "out of service".
> > >
> > >
> > > How should MGC implementation intepret the above highlighted
> > > statement?
> > > Does this mean that MGC should not try to gracefully tear down
> > > existing connections
> > > before Delay timer expired?
> > >
> > > But I think the above statement is telling MGC to try and gracefully
> > > tear down
> > > existing connections before Delay timer expired.
> > >
> > > To be able to cancel Graceful w/Delay, it seems that MGC needs to wait
> > > until
> > > Delay timer expired before it tries to tear down existing connections.
> > >
> > > But after Delay timer expired, MG will put all terminations out of
> > > service.
> > > Therefore there is no such thing as MGC gracefully tearing down
> > > existing connections.
> > >
> > >
> > > Christian Groves wrote:
> > >
> > > > I don't see that we need to add anything. Why can't the MG just
> > > > issue a
> > > > SC with Restart, Service Restored? The specification already allows
> > > > the
> > > > MG to do this.
> > > >
> > > > Regards, Christian
> > > >
> > > > "Chuong N. Nguyen" wrote:
> > > > >
> > > > > Hi Tom
> > > > >
> > > > > What are the possibilites of defining a mechanism of cancelling
> > > > > ServiceChange Graceful?
> > > > > That is MG send SC Graceful w/Delay=time.
> > > > > Before time expired, MG wants to cancel this ServiceChange.
> > > > >
> > > > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC
> > > > > Graceful cancelled"?
> > > > > 2) Done in V2 - new SC Method or Reason?
> > > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > > >
> > > > >
> > > > > Thanks
> > > > > Chuong
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >   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 ****
> > >
> > >
> 
> --
>   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 ****
> 
>   ------------------------------------------------------------------------
>                   Name: att1.htm
>    att1.htm       Type: Hypertext Markup Language (text/html)
>               Encoding: base64
>            Description: Internet HTML
> 
>   ------------------------------------------------------------------------
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and should
> not be circulated or used for any purpose other than for what it is intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."

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



From megaco-admin@ietf.org  Tue Jan 22 21:56:52 2002
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 VAA19009
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 21:56:52 -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 VAA24703;
	Tue, 22 Jan 2002 21:47:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24612
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:42 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18766
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:37 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03642
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:46:17 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23306
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:47:38 +1100 (EST)
Message-ID: <3C4E252A.E3D401AC@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:22 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com> <3C4CD851.72F49970@ericsson.com.au> <3C4D8CFB.49CD5FF9@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Chuong,

The MGC could take several actions:
o not accept new calls to the MG. This has the effect of reducing
traffic.
o wait for subscribers to hand up normally.
o play a notification to subscribers that service will be interrupted
and then remove the termination.
o more?

So what the MGC does is largely application/service dependent.

Regards, Christian

"Chuong N. Nguyen" wrote:
> 
> 
> Maybe I need a clarification on what
> 
>      should attempt to gracefully tear down existing connections
>      on the
>      Termination(s) affected by the serviceChange command.
> 
> Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers
> hang up normally and then
> put the termination OOS after subscribers hang up (before delay timer
> expired)?
> 
> Or MGC starts releasing the calls whether the subscribers hang up or
> not?
> 
> Thanks
> Chuong
> 
> Christian Groves wrote:
> 
> > There is a timing dependency here. If the MG issues a SC Graceful
> > then
> > the MGC will act on it. There will be a finite time that the MGC
> > operates under graceful mode. If a SC Restart w/Service Restored or
> > Service Change Cancel is issued during the graceful the MGC can't
> > undo
> > what it had done in that finite time but the connections that stayed
> > up
> > can remain up. If the SC Restart w/service restored or Service
> > Change
> > Cancel is not received before the delay times out then it pretty too
> >
> > late as the terminations will be torn down.
> >
> > I don't understand why you say that the MGC must wait until the
> > servicechange delay timesouts before gracefully tearing down
> > connections?
> >
> > Christian
> >
> > "Chuong N. Nguyen" wrote:
> > >
> > >
> > > MG sends SC Graceful w/Delay and terminationID=ROOT.
> > >
> > > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > > assume that
> > > 1) SC Graceful w/Delay is being cancelled?
> > > 2) All terminations are back In Service?  Even the ones that were
> > > originally OOS before the SC Graceful.
> > >
> > >
> > >    1) Graceful - indicates that the specified Terminations will be
> >
> > > taken
> > >       out of service after the specified ServiceChangeDelay;
> > > established
> > >       connections are not yet affected, but the Media Gateway
> > > Controller
> > >       should refrain from establishing new connections and should
> > >       attempt to gracefully tear down existing connections on the
> > >       Termination(s) affected by the serviceChange command. The MG
> >
> > >       should set termination serviceState at the expiry of
> > >       ServiceChangeDelay or the removal of the termination from an
> >
> > >       active context (whichever is first), to "out of service".
> > >
> > >
> > > How should MGC implementation intepret the above highlighted
> > > statement?
> > > Does this mean that MGC should not try to gracefully tear down
> > > existing connections
> > > before Delay timer expired?
> > >
> > > But I think the above statement is telling MGC to try and
> > gracefully
> > > tear down
> > > existing connections before Delay timer expired.
> > >
> > > To be able to cancel Graceful w/Delay, it seems that MGC needs to
> > wait
> > > until
> > > Delay timer expired before it tries to tear down existing
> > connections.
> > >
> > > But after Delay timer expired, MG will put all terminations out of
> >
> > > service.
> > > Therefore there is no such thing as MGC gracefully tearing down
> > > existing connections.
> > >
> > >
> > > Christian Groves wrote:
> > >
> > > > I don't see that we need to add anything. Why can't the MG just
> > > > issue a
> > > > SC with Restart, Service Restored? The specification already
> > allows
> > > > the
> > > > MG to do this.
> > > >
> > > > Regards, Christian
> > > >
> > > > "Chuong N. Nguyen" wrote:
> > > > >
> > > > > Hi Tom
> > > > >
> > > > > What are the possibilites of defining a mechanism of
> > cancelling
> > > > > ServiceChange Graceful?
> > > > > That is MG send SC Graceful w/Delay=time.
> > > > > Before time expired, MG wants to cancel this ServiceChange.
> > > > >
> > > > > 1) Can this be done in V1 by adding a new SC Reason like "916
> > SC
> > > > > Graceful cancelled"?
> > > > > 2) Done in V2 - new SC Method or Reason?
> > > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > > >
> > > > >
> > > > > Thanks
> > > > > Chuong
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >   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
> > ****
> > >
> > >
> 
> --
>   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


From daemon@ns.ietf.org  Tue Jan 22 21:56:53 2002
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 VAA19019
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 21:56:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA25343
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 21:56:56 -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 VAA24703;
	Tue, 22 Jan 2002 21:47:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24612
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:42 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18766
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:37 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03642
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:46:17 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23306
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:47:38 +1100 (EST)
Message-ID: <3C4E252A.E3D401AC@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:22 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Cancel ServiceChange Graceful
References: <3C4B40E7.F79408DC@alcatel.com> <3C4B87B2.B3F81BA2@ericsson.com.au> <3C4C35A8.E2F58977@alcatel.com> <3C4CD851.72F49970@ericsson.com.au> <3C4D8CFB.49CD5FF9@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Chuong,

The MGC could take several actions:
o not accept new calls to the MG. This has the effect of reducing
traffic.
o wait for subscribers to hand up normally.
o play a notification to subscribers that service will be interrupted
and then remove the termination.
o more?

So what the MGC does is largely application/service dependent.

Regards, Christian

"Chuong N. Nguyen" wrote:
> 
> 
> Maybe I need a clarification on what
> 
>      should attempt to gracefully tear down existing connections
>      on the
>      Termination(s) affected by the serviceChange command.
> 
> Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers
> hang up normally and then
> put the termination OOS after subscribers hang up (before delay timer
> expired)?
> 
> Or MGC starts releasing the calls whether the subscribers hang up or
> not?
> 
> Thanks
> Chuong
> 
> Christian Groves wrote:
> 
> > There is a timing dependency here. If the MG issues a SC Graceful
> > then
> > the MGC will act on it. There will be a finite time that the MGC
> > operates under graceful mode. If a SC Restart w/Service Restored or
> > Service Change Cancel is issued during the graceful the MGC can't
> > undo
> > what it had done in that finite time but the connections that stayed
> > up
> > can remain up. If the SC Restart w/service restored or Service
> > Change
> > Cancel is not received before the delay times out then it pretty too
> >
> > late as the terminations will be torn down.
> >
> > I don't understand why you say that the MGC must wait until the
> > servicechange delay timesouts before gracefully tearing down
> > connections?
> >
> > Christian
> >
> > "Chuong N. Nguyen" wrote:
> > >
> > >
> > > MG sends SC Graceful w/Delay and terminationID=ROOT.
> > >
> > > If MG sends SC Restart w/Service Restorted and ROOT, does the MGC
> > > assume that
> > > 1) SC Graceful w/Delay is being cancelled?
> > > 2) All terminations are back In Service?  Even the ones that were
> > > originally OOS before the SC Graceful.
> > >
> > >
> > >    1) Graceful - indicates that the specified Terminations will be
> >
> > > taken
> > >       out of service after the specified ServiceChangeDelay;
> > > established
> > >       connections are not yet affected, but the Media Gateway
> > > Controller
> > >       should refrain from establishing new connections and should
> > >       attempt to gracefully tear down existing connections on the
> > >       Termination(s) affected by the serviceChange command. The MG
> >
> > >       should set termination serviceState at the expiry of
> > >       ServiceChangeDelay or the removal of the termination from an
> >
> > >       active context (whichever is first), to "out of service".
> > >
> > >
> > > How should MGC implementation intepret the above highlighted
> > > statement?
> > > Does this mean that MGC should not try to gracefully tear down
> > > existing connections
> > > before Delay timer expired?
> > >
> > > But I think the above statement is telling MGC to try and
> > gracefully
> > > tear down
> > > existing connections before Delay timer expired.
> > >
> > > To be able to cancel Graceful w/Delay, it seems that MGC needs to
> > wait
> > > until
> > > Delay timer expired before it tries to tear down existing
> > connections.
> > >
> > > But after Delay timer expired, MG will put all terminations out of
> >
> > > service.
> > > Therefore there is no such thing as MGC gracefully tearing down
> > > existing connections.
> > >
> > >
> > > Christian Groves wrote:
> > >
> > > > I don't see that we need to add anything. Why can't the MG just
> > > > issue a
> > > > SC with Restart, Service Restored? The specification already
> > allows
> > > > the
> > > > MG to do this.
> > > >
> > > > Regards, Christian
> > > >
> > > > "Chuong N. Nguyen" wrote:
> > > > >
> > > > > Hi Tom
> > > > >
> > > > > What are the possibilites of defining a mechanism of
> > cancelling
> > > > > ServiceChange Graceful?
> > > > > That is MG send SC Graceful w/Delay=time.
> > > > > Before time expired, MG wants to cancel this ServiceChange.
> > > > >
> > > > > 1) Can this be done in V1 by adding a new SC Reason like "916
> > SC
> > > > > Graceful cancelled"?
> > > > > 2) Done in V2 - new SC Method or Reason?
> > > > > 3) Should be covered in draft-hss-megaco-control-association?
> > > > >
> > > > >
> > > > > Thanks
> > > > > Chuong
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >   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
> > ****
> > >
> > >
> 
> --
>   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



From megaco-admin@ietf.org  Tue Jan 22 22:09:29 2002
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 WAA19218
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 22:09:28 -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 VAA24570;
	Tue, 22 Jan 2002 21:47:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24542
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:15 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18754
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03609
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:45:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23247
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:47:10 +1100 (EST)
Message-ID: <3C4E250E.4A5AA13C@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:50:54 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH
References: <5.1.0.14.2.20020122105753.0229a720@mail.verizon.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

We're not using AH so for us deprecation isn't a problem. How much would
be
deprecated? Just the procedural text ie. 10.2 or the ASN and ABNF
syntax? If we remove the syntax then we won't be backwards compatible,
this I think would be a problem for people who already have v1 stacks.

Regards, Christian

Matt Holdrege wrote:
> 
> Since I think it never should have been there, I can certainly make a
> motion to depreciate it. I don't know how important it is to depreciate it,
> but it certainly couldn't hurt. At least it would/could stop all the
> questions about it.
> 
> At 10:25 AM 1/22/2002, Tom-PT Taylor wrote:
> >Would people accept deprecation?  How many implementations are out there
> >using interim AH and unable to switch to full IPSEC?  People can reply to me
> >privately if they wish.
> >
> >-----Original Message-----
> >From: Kaul, Bharat [mailto:bharat@trillium.com]
> >Sent: Friday, January 18, 2002 6:12 PM
> >To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
> >Subject: RE: [Megaco] Regarding IPsec and interim AH
> >
> >
> >I remember long time back on this list it was being discussed that AH scheme
> >will be deprecated. However, I still see its mention in v2.
> >
> >- Bharat
> >
> >-----Original Message-----
> >From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
> >Sent: Friday, January 18, 2002 5:26 AM
> >To: Narendra Babu; megaco@ietf.org
> >Subject: Re: [Megaco] Regarding IPsec and interim AH
> >
> >
> >At 10:36 PM 1/17/2002, Narendra Babu wrote:
> > >Hi all,
> > >
> > >         I am a newbie to this mail list as well as megaco.
> > >
> > >We are developing a megaco stack.My doubt is whether
> > >we have to implement full IPsec(RFC 2401-RFC 2411) or
> > >only interim AH as a secrity support? Please clarify  this as early as
> > >possible.
> >
> >I always thought interim AH wasn't a good idea and I think it is now
> >clarified as a temporary scheme that is no longer needed. So your choices
> >are IPsec or perhaps some less onerous scheme such as SSH.
> >
> >Anybody else?
> >
> >
> >_______________________________________________
> >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


From daemon@ns.ietf.org  Tue Jan 22 22:09:29 2002
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 WAA19228
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 22:09:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA25996
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 22:09:32 -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 VAA24570;
	Tue, 22 Jan 2002 21:47:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24542
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:47:15 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18754
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:47:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03609
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:45:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23247
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:47:10 +1100 (EST)
Message-ID: <3C4E250E.4A5AA13C@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:50:54 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Regarding IPsec and interim AH
References: <5.1.0.14.2.20020122105753.0229a720@mail.verizon.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

We're not using AH so for us deprecation isn't a problem. How much would
be
deprecated? Just the procedural text ie. 10.2 or the ASN and ABNF
syntax? If we remove the syntax then we won't be backwards compatible,
this I think would be a problem for people who already have v1 stacks.

Regards, Christian

Matt Holdrege wrote:
> 
> Since I think it never should have been there, I can certainly make a
> motion to depreciate it. I don't know how important it is to depreciate it,
> but it certainly couldn't hurt. At least it would/could stop all the
> questions about it.
> 
> At 10:25 AM 1/22/2002, Tom-PT Taylor wrote:
> >Would people accept deprecation?  How many implementations are out there
> >using interim AH and unable to switch to full IPSEC?  People can reply to me
> >privately if they wish.
> >
> >-----Original Message-----
> >From: Kaul, Bharat [mailto:bharat@trillium.com]
> >Sent: Friday, January 18, 2002 6:12 PM
> >To: 'Matt Holdrege'; Narendra Babu; megaco@ietf.org
> >Subject: RE: [Megaco] Regarding IPsec and interim AH
> >
> >
> >I remember long time back on this list it was being discussed that AH scheme
> >will be deprecated. However, I still see its mention in v2.
> >
> >- Bharat
> >
> >-----Original Message-----
> >From: Matt Holdrege [mailto:matt.holdrege@verizon.net]
> >Sent: Friday, January 18, 2002 5:26 AM
> >To: Narendra Babu; megaco@ietf.org
> >Subject: Re: [Megaco] Regarding IPsec and interim AH
> >
> >
> >At 10:36 PM 1/17/2002, Narendra Babu wrote:
> > >Hi all,
> > >
> > >         I am a newbie to this mail list as well as megaco.
> > >
> > >We are developing a megaco stack.My doubt is whether
> > >we have to implement full IPsec(RFC 2401-RFC 2411) or
> > >only interim AH as a secrity support? Please clarify  this as early as
> > >possible.
> >
> >I always thought interim AH wasn't a good idea and I think it is now
> >clarified as a temporary scheme that is no longer needed. So your choices
> >are IPsec or perhaps some less onerous scheme such as SSH.
> >
> >Anybody else?
> >
> >
> >_______________________________________________
> >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



From megaco-admin@ietf.org  Tue Jan 22 22:10:18 2002
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 WAA19256
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 22:10:13 -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 VAA24836;
	Tue, 22 Jan 2002 21:48:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24809
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:48:06 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18782
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:48:01 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03725;
	Wed, 23 Jan 2002 13:46:41 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23428;
	Wed, 23 Jan 2002 13:48:03 +1100 (EST)
Message-ID: <3C4E2543.23258026@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au> <3C4DEAD2.8CCBFBE0@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

See my replies below.

Christian

Terry L Anderson wrote:
> 
> Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
> 7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
> through a later Modify.  I can see an advantage to using this feature rather than FID,
> although we would be going a different direction that other protocols using SDP (SIP, etc)
> just as we are for negotation.  But I think that the semantics need to be specified in the
> protocol.

[CHG] Can you point out the text in 7.1.8 where it says that you should
do a modify after reserve group? I'm puzzled on what semantics need to
be added. The note in 7.1.8 gives an example that the MG can encode /
decode according to the groups. You could see DTMF as one codec, GSM EFR
RTP as the other.

> 
> If a Stream has multiple groups:
> 1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
> to all?  It IS stated that
>     "(c) If multiple groups of properties are present in a Local or Remote descriptor or
> multiple values within a group, the order of preference is descending."
> 
> I assumed that this was preference for choosing for the reply, but if media begins to flow
> with multiple groups present this could be interpretted as preference for deciding which to
> use for a media packet.

[CHG] I think this is where the confusion lies. ReserveGroups True -
means that the MG supports all the groups. It is not overloading a
descriptor so that the MG chooses one of the groups. ReserveGroup False
- means that the MG chooses one alternative.

> 
> If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
> using all codecs, one can send using any of them but left most is preferred.  Is this your
> interpretation of multiple groups as well: send to one, first preferred?  When would you send
> to other than first?  Only when the first did not have a payload suitable?  [FID supports
> sending to multiple if they have the same payload.]

[CHG] Yes this is my interpretation - groups enables the MG to choose to
send/receive the preferred codec however it should reserve resources in
case it receives another format ie. DTMF

> 
> 2) In Remote, does this requires receiving packets on multiple ports and mixing them?  An MG
> that cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But
> how can it indicate that it cannot accept multiple groups that would require mixing?

[CHG] No it does not involve mixing.

> 
> If is what H.248 intends with ReserveGroup it seems that the behavior must be much more
> specified than it is in 7.1.8.
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > Reserve Group and Reserve Value give you the ability to support all
> > choices in a single stream. One use is in the case of negotiation but
> > the text doesn't limit you to this case. I see FID can be implemented
> > with reserve group because you can have seperate RTP in different groups
> > being part of the one logical stream. One group can specify DTMF,
> > another can specify audio codec and you can set  them to different
> > IP/port combinations if you wish but these will all be part of the same
> > stream descriptor.
> >
> > If we map the FID groups into different H.248 stream IDs then we don't
> > have the problem with the ("m=") that was in the email that kicked off
> > this discussion. I don't see the reason why to use distinct terminations
> > for each m= line. In terms of specifying synchronisation, a statement
> > was already added in v1 7.1.4 "Multiple streams exiting a termination
> > shall be synchronized with each other."
> >
> > Thus I don't a reason to make changes.
> >
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > Christian Groves wrote:
> > >
> > > > G'Day Terry,
> > > >
> > > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > > Value". It allows the FID concept (group ID).
> > >
> > > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > > all choices it can support  among alternatives in a single stream (as well as reserving
> > > the resources for those in reply).  I've always assumed that this was simply a first
> > > step in negotiation and before the call was fully setup a single Group would be chosen
> > > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > > believe that a call will function with multiple groups still present?  If so, where do
> > > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > > With Remote, would we send to ALL groups?
> > >
> > > I think Reserve Group and Reserve Value are in the subject line only because the
> > > original question on this topic lead to the noticing the single m line restriction and
> > > FID was an additional reason for concern about this.  I should have changed the subject
> > > before continuing the discussion of multiple m lines.
> > >
> > > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > > streams are grouped into a single media stream (or streams are coordinated such as video
> > > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > > archetypical example, given in the FID draft is where a single audio media stream is
> > > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > > sessions are combined into one.
> > >
> > > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > > This is essentially equivalent to using distinct terminations for each m line and
> > > putting all the terminations in the same context with appropriate topology descriptor.
> > > FID does have some restrictions on the use of each m line that are a little different.
> > > It assumes that the flow will be encoded using a single codec and sent only to the m
> > > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > > to indicate this behavior with additional terminations in the context, where it would
> > > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > > codec (that is, telephone-event to one AND codec encoded tone to other).
> > >
> > > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > > single SDP description.  I would think that audio and video whould still need to be in
> > > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > > single Stream Descriptor.
> > >
> > > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > > suggest other reasons we need it or how it would be used.
> > >
> > > > With regards to sending
> > > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > > think we need a change.
> > >
> > > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > > much easier to coordinate time when regenerating the tones in the media channel.  There
> > > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > > the DTMF at the correct time in the media channel.
> > >
> > > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Troy Cauble wrote:
> > > > >
> > > > > Terry L Anderson wrote:
> > > > > >
> > > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > > too restrictive.
> > > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > > distinct payload.  It also supports sending this payload to a different
> > > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > > again requires multiple media (m) lines in the SDP.
> > > > > >
> > > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > > bullets):
> > > > > >
> > > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > > single session description MUST NOT include more than one media description
> > > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > > distinct Stream Descriptors.
> > > > > >
> > > > > > Perhaps we could change this to read:
> > > > > >
> > > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > > that the session description will contain only a single media description ("m="
> > > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > > logical media stream but where payload packets may be sent to different
> > > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > > Descriptors.
> > > > > > --------
> > > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > > Informative References, but I think this helps clarify the intent with an
> > > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > > >
> > > > > I have no problem with the intent of this change.  You have to
> > > > > change the language to allow certain cases.  But the language
> > > > > is getting very fuzzy.
> > > > >
> > > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > > >
> > > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > > audio + video is "multiple streams"?
> > > > >
> > > > > When would an MG be handling multiple streams on a termination
> > > > > that are not "logically" related in some way?
> > > > >
> > > > > Doesn't this really mean I can put as many "streams" as I want
> > > > > in my SDP and have just one StreamDescriptor?
> > > > >
> > > > > -troy
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing list
> > > > > Megaco@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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


From daemon@ns.ietf.org  Tue Jan 22 22:10:23 2002
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 WAA19266
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jan 2002 22:10:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA26029
	for megaco-archive@odin.ietf.org; Tue, 22 Jan 2002 22:10:22 -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 VAA24836;
	Tue, 22 Jan 2002 21:48:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24809
	for <megaco@ns.ietf.org>; Tue, 22 Jan 2002 21:48:06 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18782
	for <megaco@ietf.org>; Tue, 22 Jan 2002 21:48:01 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA03725;
	Wed, 23 Jan 2002 13:46:41 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA23428;
	Wed, 23 Jan 2002 13:48:03 +1100 (EST)
Message-ID: <3C4E2543.23258026@ericsson.com.au>
Date: Wed, 23 Jan 2002 13:51:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group
References: <4D79C746863DD51197690002A52CDA000102ADC8@zcard0kc.ca.nortel.com> <3C488864.C76505EB@lucent.com> <3C4893DB.BE8C2888@bell-labs.com> <3C4B87A6.8F82385A@ericsson.com.au> <3C4CE577.DB72E231@lucent.com> <3C4CF10E.94668923@ericsson.com.au> <3C4DEAD2.8CCBFBE0@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

See my replies below.

Christian

Terry L Anderson wrote:
> 
> Ok, but this is a totally new concept to me.  I see nothing in the description of groups in
> 7.1.8 or elsewhere that specifies the meaning of multiple groups that are never reduced
> through a later Modify.  I can see an advantage to using this feature rather than FID,
> although we would be going a different direction that other protocols using SDP (SIP, etc)
> just as we are for negotation.  But I think that the semantics need to be specified in the
> protocol.

[CHG] Can you point out the text in 7.1.8 where it says that you should
do a modify after reserve group? I'm puzzled on what semantics need to
be added. The note in 7.1.8 gives an example that the MG can encode /
decode according to the groups. You could see DTMF as one codec, GSM EFR
RTP as the other.

> 
> If a Stream has multiple groups:
> 1) in Local, does MG choose one to send a media packet or duplicate the media packet and sent
> to all?  It IS stated that
>     "(c) If multiple groups of properties are present in a Local or Remote descriptor or
> multiple values within a group, the order of preference is descending."
> 
> I assumed that this was preference for choosing for the reply, but if media begins to flow
> with multiple groups present this could be interpretted as preference for deciding which to
> use for a media packet.

[CHG] I think this is where the confusion lies. ReserveGroups True -
means that the MG supports all the groups. It is not overloading a
descriptor so that the MG chooses one of the groups. ReserveGroup False
- means that the MG chooses one alternative.

> 
> If multiple payload types (ReserveValue = true) exist on a single m line, one does NOT send
> using all codecs, one can send using any of them but left most is preferred.  Is this your
> interpretation of multiple groups as well: send to one, first preferred?  When would you send
> to other than first?  Only when the first did not have a payload suitable?  [FID supports
> sending to multiple if they have the same payload.]

[CHG] Yes this is my interpretation - groups enables the MG to choose to
send/receive the preferred codec however it should reserve resources in
case it receives another format ie. DTMF

> 
> 2) In Remote, does this requires receiving packets on multiple ports and mixing them?  An MG
> that cannot support mixing can set root/MaxTerminationsPerContext to 2 to indicate this.  But
> how can it indicate that it cannot accept multiple groups that would require mixing?

[CHG] No it does not involve mixing.

> 
> If is what H.248 intends with ReserveGroup it seems that the behavior must be much more
> specified than it is in 7.1.8.
> 
> Christian Groves wrote:
> 
> > G'Day Terry,
> >
> > Reserve Group and Reserve Value give you the ability to support all
> > choices in a single stream. One use is in the case of negotiation but
> > the text doesn't limit you to this case. I see FID can be implemented
> > with reserve group because you can have seperate RTP in different groups
> > being part of the one logical stream. One group can specify DTMF,
> > another can specify audio codec and you can set  them to different
> > IP/port combinations if you wish but these will all be part of the same
> > stream descriptor.
> >
> > If we map the FID groups into different H.248 stream IDs then we don't
> > have the problem with the ("m=") that was in the email that kicked off
> > this discussion. I don't see the reason why to use distinct terminations
> > for each m= line. In terms of specifying synchronisation, a statement
> > was already added in v1 7.1.4 "Multiple streams exiting a termination
> > shall be synchronized with each other."
> >
> > Thus I don't a reason to make changes.
> >
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > Christian Groves wrote:
> > >
> > > > G'Day Terry,
> > > >
> > > > We already have this functionality in H.248 "Reserve Group" and "Reserve
> > > > Value". It allows the FID concept (group ID).
> > >
> > > Perhaps I do not understand some mechanism in Reserve Group and Reserve Value, but I
> > > thought they they simply allowed MGC to specify whether MGC should choose one choice or
> > > all choices it can support  among alternatives in a single stream (as well as reserving
> > > the resources for those in reply).  I've always assumed that this was simply a first
> > > step in negotiation and before the call was fully setup a single Group would be chosen
> > > by a later Modify with ReserveGroup=false. All examples I've seen do this.  Do you
> > > believe that a call will function with multiple groups still present?  If so, where do
> > > we specify the semantics?  With Local, would we mix the RTP received in each group?
> > > With Remote, would we send to ALL groups?
> > >
> > > I think Reserve Group and Reserve Value are in the subject line only because the
> > > original question on this topic lead to the noticing the single m line restriction and
> > > FID was an additional reason for concern about this.  I should have changed the subject
> > > before continuing the discussion of multiple m lines.
> > >
> > > I don't see that ReserveGroup/Value has anything to do with FID, where multiple RTP
> > > streams are grouped into a single media stream (or streams are coordinated such as video
> > > and audio for lip sync), but let's look at the grouping of RTP streams.  The
> > > archetypical example, given in the FID draft is where a single audio media stream is
> > > split into seperate RTP sessions, one carrying DTMF and the other voice, using different
> > > encoding and sent to different ipaddr/port locations (or the reverse where to RTP
> > > sessions are combined into one.
> > >
> > > I don't seen how Reserve Group and Reserve Value help with this, but there may be a
> > > question of whether H.248's Context is sufficient to provide the FID functionality.  FID
> > > specifies that an inbound media stream is sent using all m lines in the flow (group).
> > > This is essentially equivalent to using distinct terminations for each m line and
> > > putting all the terminations in the same context with appropriate topology descriptor.
> > > FID does have some restrictions on the use of each m line that are a little different.
> > > It assumes that the flow will be encoded using a single codec and sent only to the m
> > > lines supporting that codec.  This seems to be intended to separate things like DTMF -
> > > if phone-event is used for DTMF tones, then those RTP packets are sent ONLY to the m
> > > lines containing phone-event and not to those with only voice codecs.  I don't see how
> > > to indicate this behavior with additional terminations in the context, where it would
> > > seem that the DTMF tone should be sent to all indicated terminations with corresponding
> > > codec (that is, telephone-event to one AND codec encoded tone to other).
> > >
> > > The media synch use of FID (lip synch etc) would not seem to need multiple m lines in a
> > > single SDP description.  I would think that audio and video whould still need to be in
> > > distinct Stream Descriptors but fid used to link them for synch.  I would think we'd
> > > need some statement how to do this in H.248 since we do NOT want the entire session in a
> > > single Stream Descriptor.
> > >
> > > Tom Taylor and Brian Rosen both suggested we needed to support FID.  Perhaps they can
> > > suggest other reasons we need it or how it would be used.
> > >
> > > > With regards to sending
> > > > DTMF I thought that we used the signal mechanism for that. So I don't
> > > > think we need a change.
> > >
> > > I believe that there is need for both mechanisms: sending DTMF through signaling channel
> > > (events & signals) or media channel (RTP using RFC 2833).  This is equivalent to the
> > > H.323 case where DTMF can be sent using H.245 signaling (UserInputIndication) or RTP.
> > > The RTP method is often preferable when DTMF is being passed through to far PSTN and
> > > there is no need to process it in a MGC (or routing GK).  It travels much faster and is
> > > much easier to coordinate time when regenerating the tones in the media channel.  There
> > > is currently no mechanism (that I know of) like the recent additions to H.245 to carry
> > > the RTP timestamp in the event notification and signal descriptor, in order to re-insert
> > > the DTMF at the correct time in the media channel.
> > >
> > > >
> > > >
> > > > Regards, Christian
> > > >
> > > > Troy Cauble wrote:
> > > > >
> > > > > Terry L Anderson wrote:
> > > > > >
> > > > > > I am designating this issue as open issue #3.  Tom suggests that we change a
> > > > > > statement that is proposed for the IG 6.98 (not yet approved).  The intent of
> > > > > > the statement was that multiple media streams in SDP should not occur in a
> > > > > > single H.248 StreamDescriptor, but defining this in terms of a single m line is
> > > > > > too restrictive.
> > > > > > (1) FID allows grouping multiple media lines (m lines) into a single media
> > > > > > stream and this should be allowed in a single H.248 StreamDescriptor.
> > > > > > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent using a
> > > > > > distinct payload.  It also supports sending this payload to a different
> > > > > > ipaddr/port than that used for voice.  This in essence "forks" the media stream
> > > > > > coming from one termination (eg. PSTN) into two output streams, one containing
> > > > > > voice RTP and the other containing DTMF (or other telephone event RTP, sent to
> > > > > > (possibly) two different ipaddr/ports.  This is similar in concept to FID and
> > > > > > again requires multiple media (m) lines in the SDP.
> > > > > >
> > > > > > The current IG draft adds the following to 7.1.8 (right under the first set of
> > > > > > bullets):
> > > > > >
> > > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > > single session description MUST NOT include more than one media description
> > > > > > ("m=" line).  Any additional media streams for a termination must appear in
> > > > > > distinct Stream Descriptors.
> > > > > >
> > > > > > Perhaps we could change this to read:
> > > > > >
> > > > > > A Stream Descriptor specifies a single bi-directional media stream and so a
> > > > > > single session description MUST NOT specify multiple streams.  This often means
> > > > > > that the session description will contain only a single media description ("m="
> > > > > > line).  However, where media descriptions are grouped and refer to a single,
> > > > > > logical media stream but where payload packets may be sent to different
> > > > > > transport addresses, multiple media description lines may be required (e.g., RFC
> > > > > > 2833).  Any additional, non-grouped media streams MUST appear in distinct Stream
> > > > > > Descriptors.
> > > > > > --------
> > > > > > If we refer to RFC 2833, a reference will have to be added to section 2.2
> > > > > > Informative References, but I think this helps clarify the intent with an
> > > > > > example.  We cannot refer to FID as it is not yet an RFC.
> > > > >
> > > > > I have no problem with the intent of this change.  You have to
> > > > > change the language to allow certain cases.  But the language
> > > > > is getting very fuzzy.
> > > > >
> > > > > How do I tell a "single, logical media stream" from "multiple streams"?
> > > > >
> > > > > Why is voice & RFC2833 DTMF a "single, logical stream", when
> > > > > audio + video is "multiple streams"?
> > > > >
> > > > > When would an MG be handling multiple streams on a termination
> > > > > that are not "logically" related in some way?
> > > > >
> > > > > Doesn't this really mean I can put as many "streams" as I want
> > > > > in my SDP and have just one StreamDescriptor?
> > > > >
> > > > > -troy
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing list
> > > > > Megaco@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> 
> --
> 
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

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



From megaco-admin@ietf.org  Wed Jan 23 03:45:25 2002
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 DAA03932
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 03:45:25 -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 DAA14695;
	Wed, 23 Jan 2002 03:24:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA14664
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 03:24:42 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03668
	for <megaco@ietf.org>; Wed, 23 Jan 2002 03:24:39 -0500 (EST)
Received: through eSafe SMTP Relay 1011594165; Wed Jan 23 10:41:22 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FZTB>; Wed, 23 Jan 2002 10:15:35 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189CFAD@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Date: Wed, 23 Jan 2002 10:15:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A3E6.21C88700"
Subject: [Megaco] misleading ABNF comment on stream descriptor?
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A3E6.21C88700
Content-Type: text/plain;
	charset="iso-8859-1"

Here is something from the archive which was never answered.  I think the
answer to Steven's question is that section 7.1.4 is right and the comment
in the ABNF is wrong, as the ASN.1 definition allows multiple stream
descriptors per media descriptor.  Will the comment in the ABNF be changed?


Raphael Tryster


From: Steven Weisz <sweisz@mediatrix.com>
To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
Subject: Clarification on Media Descriptor needed.
Date: Tue, 24 Apr 2001 13:32:09 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-megaco@pit.comms.marconi.com
Precedence: bulk

Hi List,

I need some clarification regarding the Media Descriptor. Specifically in
section 7.1.4, paragraph 1 the protocol states:

  "The Media Descriptor specifies the parameters for all the media
   streams.  These parameters are structured into two descriptors, a
   Termination State Descriptor, which specifies the properties of a
   termination that are not stream dependent, and one or more Stream
   Descriptors each of which describes a single media stream."

This states that a Media Descriptor has one or more Stream Descriptors
associated with it. However, in the ABNF we have:

  "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
                        RBRKT

   ; at-most-once per item
   ; and either streamParm or streamDescriptor but not both
   mediaParm            = (streamParm / streamDescriptor /
                           terminationStateDescriptor)"

Which to me seems to say that we have only one Stream Descriptor associated
with it (as indicated by the comment "; at-most-once per item".

Am I interpreting the ABNF correctly?

thanks,

Steven Weisz



------_=_NextPart_001_01C1A3E6.21C88700
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>misleading ABNF comment on stream descriptor?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Here is something from the archive which=
 was never answered.&nbsp; I think the answer to Steven's question is tha=
t section 7.1.4 is right and the comment in the ABNF is wrong, as the ASN=

sp; Will the comment in the ABNF be changed?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">From: Steven Weisz &lt;sweisz@mediatrix.=
com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: &quot;Megaco Mailing List (E-mail)&=
quot; &lt;megaco@fore.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: Clarification on Media Descrip=
tor needed.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Date: Tue, 24 Apr 2001 13:32:09 -0400</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">MIME-Version: 1.0</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">X-Mailer: Internet Mail Service (5.5.26=
50.21)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Type: text/plain;</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 FACE=3D"Ari=
al">charset=3D&quot;iso-8859-1&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sender: owner-megaco@pit.comms.marconi.=
com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Precedence: bulk</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi List,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I need some clarification regarding the =
Media Descriptor. Specifically in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">section 7.1.4, paragraph 1 the protocol=
 states:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; &quot;The Media Descriptor specif=
ies the parameters for all the media</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; streams.&nbsp; These param=
eters are structured into two descriptors, a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Termination State Descript=
or, which specifies the properties of a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; termination that are not s=
tream dependent, and one or more Stream</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Descriptors each of which =
describes a single media stream.&quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This states that a Media Descriptor has =
one or more Stream Descriptors</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">associated with it. However, in the ABN=
F we have:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; &quot;mediaDescriptor =3D MediaTo=
ken LBRKT mediaParm *(COMMA mediaParm)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; RBRKT</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ; at-most-once per item</FO=
NT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ; and either streamParm or=
 streamDescriptor but not both</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; mediaParm&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D (streamParm / strea=
mDescriptor /</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; terminationStateDescriptor)&=
quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Which to me seems to say that we have on=
ly one Stream Descriptor associated</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with it (as indicated by the comment &q=
uot;; at-most-once per item&quot;.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Am I interpreting the ABNF correctly?</F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">thanks,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Steven Weisz</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1A3E6.21C88700--

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


From daemon@optimus.ietf.org  Wed Jan 23 03:45:26 2002
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 DAA03942
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 03:45:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA15591
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 03:45:27 -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 DAA14695;
	Wed, 23 Jan 2002 03:24:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA14664
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 03:24:42 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03668
	for <megaco@ietf.org>; Wed, 23 Jan 2002 03:24:39 -0500 (EST)
Received: through eSafe SMTP Relay 1011594165; Wed Jan 23 10:41:22 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FZTB>; Wed, 23 Jan 2002 10:15:35 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189CFAD@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Date: Wed, 23 Jan 2002 10:15:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A3E6.21C88700"
Subject: [Megaco] misleading ABNF comment on stream descriptor?
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A3E6.21C88700
Content-Type: text/plain;
	charset="iso-8859-1"

Here is something from the archive which was never answered.  I think the
answer to Steven's question is that section 7.1.4 is right and the comment
in the ABNF is wrong, as the ASN.1 definition allows multiple stream
descriptors per media descriptor.  Will the comment in the ABNF be changed?


Raphael Tryster


From: Steven Weisz <sweisz@mediatrix.com>
To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
Subject: Clarification on Media Descriptor needed.
Date: Tue, 24 Apr 2001 13:32:09 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-megaco@pit.comms.marconi.com
Precedence: bulk

Hi List,

I need some clarification regarding the Media Descriptor. Specifically in
section 7.1.4, paragraph 1 the protocol states:

  "The Media Descriptor specifies the parameters for all the media
   streams.  These parameters are structured into two descriptors, a
   Termination State Descriptor, which specifies the properties of a
   termination that are not stream dependent, and one or more Stream
   Descriptors each of which describes a single media stream."

This states that a Media Descriptor has one or more Stream Descriptors
associated with it. However, in the ABNF we have:

  "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
                        RBRKT

   ; at-most-once per item
   ; and either streamParm or streamDescriptor but not both
   mediaParm            = (streamParm / streamDescriptor /
                           terminationStateDescriptor)"

Which to me seems to say that we have only one Stream Descriptor associated
with it (as indicated by the comment "; at-most-once per item".

Am I interpreting the ABNF correctly?

thanks,

Steven Weisz



------_=_NextPart_001_01C1A3E6.21C88700
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>misleading ABNF comment on stream descriptor?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Here is something from the archive which=
 was never answered.&nbsp; I think the answer to Steven's question is tha=
t section 7.1.4 is right and the comment in the ABNF is wrong, as the ASN=

sp; Will the comment in the ABNF be changed?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">From: Steven Weisz &lt;sweisz@mediatrix.=
com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: &quot;Megaco Mailing List (E-mail)&=
quot; &lt;megaco@fore.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: Clarification on Media Descrip=
tor needed.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Date: Tue, 24 Apr 2001 13:32:09 -0400</=
FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">MIME-Version: 1.0</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">X-Mailer: Internet Mail Service (5.5.26=
50.21)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Type: text/plain;</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 FACE=3D"Ari=
al">charset=3D&quot;iso-8859-1&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sender: owner-megaco@pit.comms.marconi.=
com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Precedence: bulk</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi List,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I need some clarification regarding the =
Media Descriptor. Specifically in</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">section 7.1.4, paragraph 1 the protocol=
 states:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; &quot;The Media Descriptor specif=
ies the parameters for all the media</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; streams.&nbsp; These param=
eters are structured into two descriptors, a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Termination State Descript=
or, which specifies the properties of a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; termination that are not s=
tream dependent, and one or more Stream</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Descriptors each of which =
describes a single media stream.&quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This states that a Media Descriptor has =
one or more Stream Descriptors</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">associated with it. However, in the ABN=
F we have:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; &quot;mediaDescriptor =3D MediaTo=
ken LBRKT mediaParm *(COMMA mediaParm)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; RBRKT</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ; at-most-once per item</FO=
NT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ; and either streamParm or=
 streamDescriptor but not both</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; mediaParm&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D (streamParm / strea=
mDescriptor /</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; terminationStateDescriptor)&=
quot;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Which to me seems to say that we have on=
ly one Stream Descriptor associated</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with it (as indicated by the comment &q=
uot;; at-most-once per item&quot;.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Am I interpreting the ABNF correctly?</F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">thanks,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Steven Weisz</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1A3E6.21C88700--

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



From megaco-admin@ietf.org  Wed Jan 23 03:53:32 2002
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 DAA04037
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 03:53:32 -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 DAA15494;
	Wed, 23 Jan 2002 03:41:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA15409
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 03:41:06 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03882
	for <megaco@ietf.org>; Wed, 23 Jan 2002 03:41:03 -0500 (EST)
Received: through eSafe SMTP Relay 1011594165; Wed Jan 23 10:57:46 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FZT7>; Wed, 23 Jan 2002 10:31:59 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Subject: RE: [Megaco] misleading ABNF comment on stream descriptor?
Date: Wed, 23 Jan 2002 10:31:58 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A3E8.6C040EF0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A3E8.6C040EF0
Content-Type: text/plain;
	charset="iso-8859-1"

The previous posting came out garbled.

	Here is something from the archive which was never answered.  I
think the answer to Steven's question is that section 7.1.4 is right and the
comment in the ABNF is wrong, as the ASN.1 definition allows multiple stream
descriptors per media descriptor.  Will the comment in the ABNF be changed?

	
	Raphael Tryster 


	From: Steven Weisz <sweisz@mediatrix.com> 
	To: "Megaco Mailing List (E-mail)" <megaco@fore.com> 
	Subject: Clarification on Media Descriptor needed. 
	Date: Tue, 24 Apr 2001 13:32:09 -0400 
	MIME-Version: 1.0 
	X-Mailer: Internet Mail Service (5.5.2650.21) 
	Content-Type: text/plain; 
	        charset="iso-8859-1" 
	Sender: owner-megaco@pit.comms.marconi.com 
	Precedence: bulk 

	Hi List, 

	I need some clarification regarding the Media Descriptor.
Specifically in 
	section 7.1.4, paragraph 1 the protocol states: 

	  "The Media Descriptor specifies the parameters for all the media 
	   streams.  These parameters are structured into two descriptors, a

	   Termination State Descriptor, which specifies the properties of a

	   termination that are not stream dependent, and one or more Stream

	   Descriptors each of which describes a single media stream." 

	This states that a Media Descriptor has one or more Stream
Descriptors 
	associated with it. However, in the ABNF we have: 

	  "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm) 
	                        RBRKT 

	   ; at-most-once per item 
	   ; and either streamParm or streamDescriptor but not both 
	   mediaParm            = (streamParm / streamDescriptor / 
	                           terminationStateDescriptor)" 

	Which to me seems to say that we have only one Stream Descriptor
associated 
	with it (as indicated by the comment "; at-most-once per item". 

	Am I interpreting the ABNF correctly? 

	thanks, 

	Steven Weisz 

	

------_=_NextPart_001_01C1A3E8.6C040EF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] misleading ABNF comment on stream descriptor?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">The previous posting came out garbled.</=
FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Here is something from the archive which=
 was never answered.&nbsp; I think the answer to Steven's question is tha=
t section 7.1.4 is right and the comment in the ABNF is wrong, as the ASN=

sp; Will the comment in the ABNF be changed?</FONT></P>

<P><A NAME=3D"_MailData"></A>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT><FONT FACE=3D"Ar=
ial"> </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">From: Steven Weisz &lt;sweisz@mediatrix.=
com&gt;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">To: &quot;Megaco Mailing List (E-mai=
l)&quot; &lt;megaco@fore.com&gt;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Subject: Clarification on Media Desc=
riptor needed.</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Date: Tue, 24 Apr 2001 13:32:09 -040=
0</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">MIME-Version: 1.0</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">X-Mailer: Internet Mail Service (5.5=

</FONT><FONT SIZE=3D2 FACE=3D"Arial">Content-Type: text/plain;</FONT><FON=
T FACE=3D"Arial"><BR>
=A0=A0=A0=A0=A0=A0=A0</FONT> <FONT SIZE=3D2 FACE=3D"Arial">charset=3D&quo=
t;iso-8859-1&quot;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Sender: owner-megaco@pit.comms.marco=
ni.com</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Precedence: bulk</FONT><FONT FACE=3D=
"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi List,</FONT><FONT FACE=3D"Arial"> </F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I need some clarification regarding the =
Media Descriptor. Specifically in</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">section 7.1.4, paragraph 1 the proto=
col states:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0 &quot;The Media Descriptor specifies=
 the parameters for all the media</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 streams.=A0 These parameters =
are structured into two descriptors, a</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 Termination State Descriptor,=
 which specifies the properties of a</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 termination that are not stre=
am dependent, and one or more Stream</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 Descriptors each of which des=
cribes a single media stream.&quot;</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This states that a Media Descriptor has =
one or more Stream Descriptors</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">associated with it. However, in the =
ABNF we have:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0 &quot;mediaDescriptor =3D MediaToken=
 LBRKT mediaParm *(COMMA mediaParm)</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RBRKT</FONT><FONT FACE=3D"Arial"> </FON=
T>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 ; at-most-once per item</FONT><FO=
NT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 ; and either streamParm or st=
reamDescriptor but not both</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 mediaParm=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 =3D (streamParm / streamDescriptor /</FONT><FONT FACE=3D"Ari=
al"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 terminationStateDescriptor)&qu=
ot;</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Which to me seems to say that we have on=
ly one Stream Descriptor associated</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">with it (as indicated by the comment=
 &quot;; at-most-once per item&quot;.</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Am I interpreting the ABNF correctly?</F=
ONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">thanks,</FONT><FONT FACE=3D"Arial"> </FO=
NT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Steven Weisz</FONT><FONT FACE=3D"Arial">=
 </FONT>
</P>

<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1A3E8.6C040EF0--

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


From daemon@optimus.ietf.org  Wed Jan 23 03:53:33 2002
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 DAA04046
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 03:53:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA15765
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 03:53:34 -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 DAA15494;
	Wed, 23 Jan 2002 03:41:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA15409
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 03:41:06 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03882
	for <megaco@ietf.org>; Wed, 23 Jan 2002 03:41:03 -0500 (EST)
Received: through eSafe SMTP Relay 1011594165; Wed Jan 23 10:57:46 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6FZT7>; Wed, 23 Jan 2002 10:31:59 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: megaco@ietf.org
Subject: RE: [Megaco] misleading ABNF comment on stream descriptor?
Date: Wed, 23 Jan 2002 10:31:58 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A3E8.6C040EF0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A3E8.6C040EF0
Content-Type: text/plain;
	charset="iso-8859-1"

The previous posting came out garbled.

	Here is something from the archive which was never answered.  I
think the answer to Steven's question is that section 7.1.4 is right and the
comment in the ABNF is wrong, as the ASN.1 definition allows multiple stream
descriptors per media descriptor.  Will the comment in the ABNF be changed?

	
	Raphael Tryster 


	From: Steven Weisz <sweisz@mediatrix.com> 
	To: "Megaco Mailing List (E-mail)" <megaco@fore.com> 
	Subject: Clarification on Media Descriptor needed. 
	Date: Tue, 24 Apr 2001 13:32:09 -0400 
	MIME-Version: 1.0 
	X-Mailer: Internet Mail Service (5.5.2650.21) 
	Content-Type: text/plain; 
	        charset="iso-8859-1" 
	Sender: owner-megaco@pit.comms.marconi.com 
	Precedence: bulk 

	Hi List, 

	I need some clarification regarding the Media Descriptor.
Specifically in 
	section 7.1.4, paragraph 1 the protocol states: 

	  "The Media Descriptor specifies the parameters for all the media 
	   streams.  These parameters are structured into two descriptors, a

	   Termination State Descriptor, which specifies the properties of a

	   termination that are not stream dependent, and one or more Stream

	   Descriptors each of which describes a single media stream." 

	This states that a Media Descriptor has one or more Stream
Descriptors 
	associated with it. However, in the ABNF we have: 

	  "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm) 
	                        RBRKT 

	   ; at-most-once per item 
	   ; and either streamParm or streamDescriptor but not both 
	   mediaParm            = (streamParm / streamDescriptor / 
	                           terminationStateDescriptor)" 

	Which to me seems to say that we have only one Stream Descriptor
associated 
	with it (as indicated by the comment "; at-most-once per item". 

	Am I interpreting the ABNF correctly? 

	thanks, 

	Steven Weisz 

	

------_=_NextPart_001_01C1A3E8.6C040EF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] misleading ABNF comment on stream descriptor?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">The previous posting came out garbled.</=
FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Here is something from the archive which=
 was never answered.&nbsp; I think the answer to Steven's question is tha=
t section 7.1.4 is right and the comment in the ABNF is wrong, as the ASN=

sp; Will the comment in the ABNF be changed?</FONT></P>

<P><A NAME=3D"_MailData"></A>
<BR><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT><FONT FACE=3D"Ar=
ial"> </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">From: Steven Weisz &lt;sweisz@mediatrix.=
com&gt;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">To: &quot;Megaco Mailing List (E-mai=
l)&quot; &lt;megaco@fore.com&gt;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Subject: Clarification on Media Desc=
riptor needed.</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Date: Tue, 24 Apr 2001 13:32:09 -040=
0</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">MIME-Version: 1.0</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">X-Mailer: Internet Mail Service (5.5=

</FONT><FONT SIZE=3D2 FACE=3D"Arial">Content-Type: text/plain;</FONT><FON=
T FACE=3D"Arial"><BR>
=A0=A0=A0=A0=A0=A0=A0</FONT> <FONT SIZE=3D2 FACE=3D"Arial">charset=3D&quo=
t;iso-8859-1&quot;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Sender: owner-megaco@pit.comms.marco=
ni.com</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">Precedence: bulk</FONT><FONT FACE=3D=
"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi List,</FONT><FONT FACE=3D"Arial"> </F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I need some clarification regarding the =
Media Descriptor. Specifically in</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">section 7.1.4, paragraph 1 the proto=
col states:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0 &quot;The Media Descriptor specifies=
 the parameters for all the media</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 streams.=A0 These parameters =
are structured into two descriptors, a</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 Termination State Descriptor,=
 which specifies the properties of a</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 termination that are not stre=
am dependent, and one or more Stream</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 Descriptors each of which des=
cribes a single media stream.&quot;</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This states that a Media Descriptor has =
one or more Stream Descriptors</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">associated with it. However, in the =
ABNF we have:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0 &quot;mediaDescriptor =3D MediaToken=
 LBRKT mediaParm *(COMMA mediaParm)</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RBRKT</FONT><FONT FACE=3D"Arial"> </FON=
T>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 ; at-most-once per item</FONT><FO=
NT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 ; and either streamParm or st=
reamDescriptor but not both</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0 mediaParm=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 =3D (streamParm / streamDescriptor /</FONT><FONT FACE=3D"Ari=
al"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 terminationStateDescriptor)&qu=
ot;</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Which to me seems to say that we have on=
ly one Stream Descriptor associated</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Arial">with it (as indicated by the comment=
 &quot;; at-most-once per item&quot;.</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Am I interpreting the ABNF correctly?</F=
ONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">thanks,</FONT><FONT FACE=3D"Arial"> </FO=
NT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Steven Weisz</FONT><FONT FACE=3D"Arial">=
 </FONT>
</P>

<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1A3E8.6C040EF0--

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



From megaco-admin@ietf.org  Wed Jan 23 08:12:07 2002
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 IAA07392
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 08:12:07 -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 IAA24654;
	Wed, 23 Jan 2002 08:03:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24626
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:03:07 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06937
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:03:04 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0ND34IB022028
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:03:04 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0ND33r6013525
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:03:03 +0200 (EET)
Message-ID: <3C4EB485.85390B69@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 15:03:01 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Annex M.4 vs H.248
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: 7bit


Hi,

More on the multiplexing issue.

When I had yet another look at Annex M.4, I noticed the following thing:
it doesn't use a Multiplex Termination in the first place. The
multiplexing is handled by the TDM/H.324 termination, by setting the
properties (mux level etc) defined in the H324 package.

Is the reason that we simply don't need a Multiplex Termination in that
case, since we only have a SINGLE incoming multiplexed bearer?

IF that is the case, I think it should be written in the updated text on
multiplexing.

Or, have I missunderstood something?


Regards,

Christer Holmberg
Ericsson Finland

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


From daemon@optimus.ietf.org  Wed Jan 23 08:12:07 2002
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 IAA07402
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 08:12:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA24794
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 08:12:09 -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 IAA24654;
	Wed, 23 Jan 2002 08:03:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24626
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:03:07 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06937
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:03:04 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g0ND34IB022028
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:03:04 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0ND33r6013525
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:03:03 +0200 (EET)
Message-ID: <3C4EB485.85390B69@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 15:03:01 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Annex M.4 vs H.248
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: 7bit


Hi,

More on the multiplexing issue.

When I had yet another look at Annex M.4, I noticed the following thing:
it doesn't use a Multiplex Termination in the first place. The
multiplexing is handled by the TDM/H.324 termination, by setting the
properties (mux level etc) defined in the H324 package.

Is the reason that we simply don't need a Multiplex Termination in that
case, since we only have a SINGLE incoming multiplexed bearer?

IF that is the case, I think it should be written in the updated text on
multiplexing.

Or, have I missunderstood something?


Regards,

Christer Holmberg
Ericsson Finland

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



From megaco-admin@ietf.org  Wed Jan 23 08:35:19 2002
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 IAA07803
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 08:35:19 -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 IAA25082;
	Wed, 23 Jan 2002 08:25:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA25052
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:25:12 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07635
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:25:09 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0NDP3w25665;
	Wed, 23 Jan 2002 14:25:03 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0NDP3r6015307;
	Wed, 23 Jan 2002 15:25:03 +0200 (EET)
Message-ID: <3C4EB9AD.8E7BC8CC@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 15:25:01 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEC5@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>The LCNs are specific to one application, not a general multiplexing issue.
>(Although I suppose a similar issue arises with H.320, I also think H.320
>would need its own annex.)  I think the mapping has to be described in Annex
>M.4 for H.324.

As long as it's somewhere :)

>The most obvious solution is as Christer indicated: an LCN property in LocalControl.

Actually, I am not sure LocalControl is the correct place. Annex M.4
specifies the multiplex properties in the TerminationState descriptor,
so this information could be there. Note that Annex M.4 does not use a
Multiplex Termination (the multiplexing is done in the TDM termination),
and there are no stream descriptors defined for the LCNs. IF a
Multiplexing Termination is used, according to the H.248 core spec,
separate stream descriptor shall be defined for each LCN, and in that
case it could be a property in LocalControl.

Also, is there a specific reason why the H245 Message event, defined in
the H.245 Package (M4.5) can't be used for the H.245 backhauling???


Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Tuesday, January 22, 2002 2:35 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I don't think we can remove the whole chapter from the protocol at this
> >stage. I agree with Tom that we can do some call flows in a seperate
> >annex.
> 
> Oki.
> 
> >I'll add some text on the euphemeral terminations to the proposed
> clarification.
> 
> So, we shouldn't say anything about the Stream Descriptors in the Mux
> Termination? How they are mapped to the LCNs etc? Personally I don't
> care if it's said in the core spec, or in a separate Annex, but I don't
> understand what the purpose is to put stuff in the core which nobody can
> use :)
> 
> Does anyone know if there has been any response on this issue from SG16?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > >While we're on the topic of Annex M.4, I realized while reading it that
> it
> > > >improperly (I think) includes some control terminations in the
> multiplex.
> > > >This may be water under the bridge now -- too late to do anything about
> it.
> > > >
> > > >Anyway, Christer is asking for more than I would put into the core
> protocol
> > > >specification.  We should probably create an Informational RFC
> describing
> > > >multiplex use with examples, just as we should publish an Informational
> RFC
> > > >giving example call flows.
> > >
> > > Why not removing the whole multiplex chapter from the core protocol,
> > > then, and putting it in a separate Annex, or something? The way it's
> > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > You simply can't implement multiplexing with the info you get from that
> > > text (you don't know how to map the LCNs, which btw also are
> > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > enough in my opinion.
> > >
> > > I thought that the ITU people always wanted to specify everything very
> > > much in detail :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > -----Original Message-----
> > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > To: Christian Groves
> > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > >
> > > > Hi,
> > > >
> > > > >I think that the H.324 package probably needs to be updated to say
> how
> > > > >this is done. I don't think its a core H.248 issue.
> > > >
> > > > I agree. The idea was that this property would be defined in the H.324
> > > > package, and then used within each stream descriptor in the Mux
> > > > Termination.
> > > >
> > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> see a
> > > > reply from the
> > > > > H324 package authors on how they thought this was to be done.
> > > >
> > > > >Are there any updates you'd like to see to proposed text on
> > > > MultiplexDescriptors that Tom posted?
> > > >
> > > > First, as Tom already mentioned, it should be updated so that it also
> > > > includes emphemeral bearer terminations (RTP terminations, for
> example).
> > > >
> > > > Second, it should in detail, on a message level, describe how the
> > > > multiplexed connection is set up. Now it only says "use a stream
> > > > descriptor" - which means everyone is going to understand it their own
> > > > way, and we are going to have lots of interop problems when people
> start
> > > > implementing this :)
> > > >
> > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > multiplex method is used) descriptor is used, ie which terminations
> are
> > > > included etc, depending on on which "side" of the multiplexer the
> > > > terminations are.
> > > >
> > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > another discussion...
> > > >
> > > > I understand if you want to get this document ready before february,
> but
> > > > please let us do this correct from the beginning :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > Regards, Christian
> > > > >
> > > > > Christer Holmberg wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have read the document a few times, but even by having stream
> > > > > > descriptors in the mux termination, I still don't understand how
> each of
> > > > > > those stream descriptors are mapped to specific LNCs. Is the
> StreamID
> > > > > > supposed to be the same as the LCN number, or how is the mapping
> done?
> > > > > >
> > > > > > A very simple solution would be to add a "LCN property" (to the
> H.324
> > > > > > package, I assume) which would be used in the each stream
> descriptor to
> > > > > > specify to which LCN it is mapped.
> > > > > >
> > > > > > Comments?
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Christer Holmberg
> > > > > > Ericsson Finland
> > > > > >
> > > > > > Tom-PT Taylor wrote:
> > > > > > >
> > > > > > > I mentioned that several of us have been discussing additional
> text
> > > > for
> > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> marked up
> > > > changes
> > > > > > > in the Megaco FTP site.  According to your taste, you can
> download
> > > > > > >
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.doc
> > > > > > > or
> > > > > > >
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.pdf
> > > > > > >
> > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> Mapping"), this
> > > > > > > proposed text needs a further update.  The supporting bearers
> > > > contained by a
> > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > However, I
> > > > > > > believe it would be essential that any ephemrals mentioned in a
> MUX
> > > > > > > descriptor already exist in the context, since their properties
> are
> > > > probably
> > > > > > > not directly inferrable from those of the multiplexing
> termination.
> > > > > > >
> > > > > > > Tom Taylor
> > > > > > > taylor@nortelnetworks.com
> > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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


From megaco-admin@ietf.org  Wed Jan 23 09:05:15 2002
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 JAA08754
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:05:15 -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 IAA26303;
	Wed, 23 Jan 2002 08:57:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26280
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:57:08 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08391
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:56:55 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0NDunE05906;
	Wed, 23 Jan 2002 19:27:05 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4A.004C6903 ; Wed, 23 Jan 2002 19:24:36 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4A.004C49FF.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 19:25:11 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical terminations,
since electrical signals are more appropriate for physical terminations.
And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command? A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.



Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 23 09:05:15 2002
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 JAA08764
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:05:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA27045
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 09:05:18 -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 IAA26303;
	Wed, 23 Jan 2002 08:57:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26280
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:57:08 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08391
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:56:55 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0NDunE05906;
	Wed, 23 Jan 2002 19:27:05 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4A.004C6903 ; Wed, 23 Jan 2002 19:24:36 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4A.004C49FF.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 19:25:11 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical terminations,
since electrical signals are more appropriate for physical terminations.
And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command? A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.



Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 23 09:22:29 2002
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 JAA09473
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:22:29 -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 JAA27092;
	Wed, 23 Jan 2002 09:05:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27062
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:05:44 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08821
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:05:38 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0NE5bE06376;
	Wed, 23 Jan 2002 19:35:41 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4A.004D4332 ; Wed, 23 Jan 2002 19:33:54 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: megaco ietf <megaco@ietf.org>
Message-ID: <65256B4A.004D1EF0.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 19:34:17 +0530
Subject: Re: [Megaco] Query about local control descriptor properties
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Christian

Does it boil down to that MGC wants the excluded properties to be "reset" (made
NULL or switched OFF).
Example:
gain control is a provisioned value, and assuming this value is provisioned at
MG to be 20.
MGC explicitly mentions the value to be (tdmc/gain =40) in a local control
descriptor.
MG sets it to 40.
MGC deletes the property (tdmc/gain) from the local control descriptor.
MG sets it to 0.
Is this correct ?

Thanks,
-Kapil Nayar






Christian Groves <Christian.Groves@ericsson.com.au> on 01/23/2002 06:09:27 AM

To:   megaco ietf <megaco@ietf.org>
cc:    (bcc: Kapil Nayar/HSS)

Subject:  Re: [Megaco] Query about local control descriptor properties




Hello Kapil,

Yes that applies the properties which the MGC doesn't want anymore.

Regards, Christian

knayar@hss.hns.com wrote:
>
> Hi Tom & list,
>
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
>
> "If the MGC wishes to delete some information from the existing descriptor, it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped
out."
>
> Does the "unwanted information" refer to the properties which the MGC no more
> requires to be set on the termination......
>
> Please reply back...
>
> Thanks,
> Kapil Nayar
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan 23 09:22:29 2002
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 JAA09483
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:22:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA27493
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 09:22:30 -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 JAA27092;
	Wed, 23 Jan 2002 09:05:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27062
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:05:44 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08821
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:05:38 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0NE5bE06376;
	Wed, 23 Jan 2002 19:35:41 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4A.004D4332 ; Wed, 23 Jan 2002 19:33:54 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: megaco ietf <megaco@ietf.org>
Message-ID: <65256B4A.004D1EF0.00@sandesh.hss.hns.com>
Date: Wed, 23 Jan 2002 19:34:17 +0530
Subject: Re: [Megaco] Query about local control descriptor properties
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Christian

Does it boil down to that MGC wants the excluded properties to be "reset" (made
NULL or switched OFF).
Example:
gain control is a provisioned value, and assuming this value is provisioned at
MG to be 20.
MGC explicitly mentions the value to be (tdmc/gain =40) in a local control
descriptor.
MG sets it to 40.
MGC deletes the property (tdmc/gain) from the local control descriptor.
MG sets it to 0.
Is this correct ?

Thanks,
-Kapil Nayar






Christian Groves <Christian.Groves@ericsson.com.au> on 01/23/2002 06:09:27 AM

To:   megaco ietf <megaco@ietf.org>
cc:    (bcc: Kapil Nayar/HSS)

Subject:  Re: [Megaco] Query about local control descriptor properties




Hello Kapil,

Yes that applies the properties which the MGC doesn't want anymore.

Regards, Christian

knayar@hss.hns.com wrote:
>
> Hi Tom & list,
>
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
>
> "If the MGC wishes to delete some information from the existing descriptor, it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped
out."
>
> Does the "unwanted information" refer to the properties which the MGC no more
> requires to be set on the termination......
>
> Please reply back...
>
> Thanks,
> Kapil Nayar
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan 23 09:22:35 2002
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 JAA09517
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:22:35 -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 JAA27164;
	Wed, 23 Jan 2002 09:06: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 JAA27138
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:06:57 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08930
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:06:53 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NE6Nd28068;
	Wed, 23 Jan 2002 09:06:23 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NE6Jn08629;
	Wed, 23 Jan 2002 09:06:20 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZACZ>; Wed, 23 Jan 2002 09:06:21 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre
	 <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Wed, 23 Jan 2002 09:06:18 -0500
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

Those multiplex properties you're talking about are a global characteristic
of H.324 systems.  It makes good sense to put them into TerminationState
because they describe transport on the exterior side, not the context side
of the termination.

I don't have time to follow through on this today, but perhaps I'll tackle a
complete description of the H.324 application when I have an idle moment.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Wednesday, January 23, 2002 8:25 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Christian Groves; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>The LCNs are specific to one application, not a general multiplexing issue.
>(Although I suppose a similar issue arises with H.320, I also think H.320
>would need its own annex.)  I think the mapping has to be described in
Annex
>M.4 for H.324.

As long as it's somewhere :)

>The most obvious solution is as Christer indicated: an LCN property in
LocalControl.

Actually, I am not sure LocalControl is the correct place. Annex M.4
specifies the multiplex properties in the TerminationState descriptor,
so this information could be there. Note that Annex M.4 does not use a
Multiplex Termination (the multiplexing is done in the TDM termination),
and there are no stream descriptors defined for the LCNs. IF a
Multiplexing Termination is used, according to the H.248 core spec,
separate stream descriptor shall be defined for each LCN, and in that
case it could be a property in LocalControl.

Also, is there a specific reason why the H245 Message event, defined in
the H.245 Package (M4.5) can't be used for the H.245 backhauling???


Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Tuesday, January 22, 2002 2:35 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I don't think we can remove the whole chapter from the protocol at this
> >stage. I agree with Tom that we can do some call flows in a seperate
> >annex.
> 
> Oki.
> 
> >I'll add some text on the euphemeral terminations to the proposed
> clarification.
> 
> So, we shouldn't say anything about the Stream Descriptors in the Mux
> Termination? How they are mapped to the LCNs etc? Personally I don't
> care if it's said in the core spec, or in a separate Annex, but I don't
> understand what the purpose is to put stuff in the core which nobody can
> use :)
> 
> Does anyone know if there has been any response on this issue from SG16?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > >While we're on the topic of Annex M.4, I realized while reading it
that
> it
> > > >improperly (I think) includes some control terminations in the
> multiplex.
> > > >This may be water under the bridge now -- too late to do anything
about
> it.
> > > >
> > > >Anyway, Christer is asking for more than I would put into the core
> protocol
> > > >specification.  We should probably create an Informational RFC
> describing
> > > >multiplex use with examples, just as we should publish an
Informational
> RFC
> > > >giving example call flows.
> > >
> > > Why not removing the whole multiplex chapter from the core protocol,
> > > then, and putting it in a separate Annex, or something? The way it's
> > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > You simply can't implement multiplexing with the info you get from
that
> > > text (you don't know how to map the LCNs, which btw also are
> > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > enough in my opinion.
> > >
> > > I thought that the ITU people always wanted to specify everything very
> > > much in detail :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > -----Original Message-----
> > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > To: Christian Groves
> > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > >
> > > > Hi,
> > > >
> > > > >I think that the H.324 package probably needs to be updated to say
> how
> > > > >this is done. I don't think its a core H.248 issue.
> > > >
> > > > I agree. The idea was that this property would be defined in the
H.324
> > > > package, and then used within each stream descriptor in the Mux
> > > > Termination.
> > > >
> > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> see a
> > > > reply from the
> > > > > H324 package authors on how they thought this was to be done.
> > > >
> > > > >Are there any updates you'd like to see to proposed text on
> > > > MultiplexDescriptors that Tom posted?
> > > >
> > > > First, as Tom already mentioned, it should be updated so that it
also
> > > > includes emphemeral bearer terminations (RTP terminations, for
> example).
> > > >
> > > > Second, it should in detail, on a message level, describe how the
> > > > multiplexed connection is set up. Now it only says "use a stream
> > > > descriptor" - which means everyone is going to understand it their
own
> > > > way, and we are going to have lots of interop problems when people
> start
> > > > implementing this :)
> > > >
> > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > multiplex method is used) descriptor is used, ie which terminations
> are
> > > > included etc, depending on on which "side" of the multiplexer the
> > > > terminations are.
> > > >
> > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > another discussion...
> > > >
> > > > I understand if you want to get this document ready before february,
> but
> > > > please let us do this correct from the beginning :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > Regards, Christian
> > > > >
> > > > > Christer Holmberg wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have read the document a few times, but even by having stream
> > > > > > descriptors in the mux termination, I still don't understand how
> each of
> > > > > > those stream descriptors are mapped to specific LNCs. Is the
> StreamID
> > > > > > supposed to be the same as the LCN number, or how is the mapping
> done?
> > > > > >
> > > > > > A very simple solution would be to add a "LCN property" (to the
> H.324
> > > > > > package, I assume) which would be used in the each stream
> descriptor to
> > > > > > specify to which LCN it is mapped.
> > > > > >
> > > > > > Comments?
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Christer Holmberg
> > > > > > Ericsson Finland
> > > > > >
> > > > > > Tom-PT Taylor wrote:
> > > > > > >
> > > > > > > I mentioned that several of us have been discussing additional
> text
> > > > for
> > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> marked up
> > > > changes
> > > > > > > in the Megaco FTP site.  According to your taste, you can
> download
> > > > > > >
> > > >
>
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.doc
> > > > > > > or
> > > > > > >
> > > >
>
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.pdf
> > > > > > >
> > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> Mapping"), this
> > > > > > > proposed text needs a further update.  The supporting bearers
> > > > contained by a
> > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > However, I
> > > > > > > believe it would be essential that any ephemrals mentioned in
a
> MUX
> > > > > > > descriptor already exist in the context, since their
properties
> are
> > > > probably
> > > > > > > not directly inferrable from those of the multiplexing
> termination.
> > > > > > >
> > > > > > > Tom Taylor
> > > > > > > taylor@nortelnetworks.com
> > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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


From daemon@optimus.ietf.org  Wed Jan 23 09:22:36 2002
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 JAA09526
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:22:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA27521
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 09:22:36 -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 JAA27164;
	Wed, 23 Jan 2002 09:06: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 JAA27138
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:06:57 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08930
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:06:53 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NE6Nd28068;
	Wed, 23 Jan 2002 09:06:23 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NE6Jn08629;
	Wed, 23 Jan 2002 09:06:20 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZACZ>; Wed, 23 Jan 2002 09:06:21 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED8@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre
	 <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] Clarification Of Multiplex Descriptor Text
Date: Wed, 23 Jan 2002 09:06:18 -0500
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

Those multiplex properties you're talking about are a global characteristic
of H.324 systems.  It makes good sense to put them into TerminationState
because they describe transport on the exterior side, not the context side
of the termination.

I don't have time to follow through on this today, but perhaps I'll tackle a
complete description of the H.324 application when I have an idle moment.

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Wednesday, January 23, 2002 8:25 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Christian Groves; Clifford Sayre; megaco ietf
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text



Hi,

>The LCNs are specific to one application, not a general multiplexing issue.
>(Although I suppose a similar issue arises with H.320, I also think H.320
>would need its own annex.)  I think the mapping has to be described in
Annex
>M.4 for H.324.

As long as it's somewhere :)

>The most obvious solution is as Christer indicated: an LCN property in
LocalControl.

Actually, I am not sure LocalControl is the correct place. Annex M.4
specifies the multiplex properties in the TerminationState descriptor,
so this information could be there. Note that Annex M.4 does not use a
Multiplex Termination (the multiplexing is done in the TDM termination),
and there are no stream descriptors defined for the LCNs. IF a
Multiplexing Termination is used, according to the H.248 core spec,
separate stream descriptor shall be defined for each LCN, and in that
case it could be a property in LocalControl.

Also, is there a specific reason why the H245 Message event, defined in
the H.245 Package (M4.5) can't be used for the H.245 backhauling???


Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Tuesday, January 22, 2002 2:35 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I don't think we can remove the whole chapter from the protocol at this
> >stage. I agree with Tom that we can do some call flows in a seperate
> >annex.
> 
> Oki.
> 
> >I'll add some text on the euphemeral terminations to the proposed
> clarification.
> 
> So, we shouldn't say anything about the Stream Descriptors in the Mux
> Termination? How they are mapped to the LCNs etc? Personally I don't
> care if it's said in the core spec, or in a separate Annex, but I don't
> understand what the purpose is to put stuff in the core which nobody can
> use :)
> 
> Does anyone know if there has been any response on this issue from SG16?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > >While we're on the topic of Annex M.4, I realized while reading it
that
> it
> > > >improperly (I think) includes some control terminations in the
> multiplex.
> > > >This may be water under the bridge now -- too late to do anything
about
> it.
> > > >
> > > >Anyway, Christer is asking for more than I would put into the core
> protocol
> > > >specification.  We should probably create an Informational RFC
> describing
> > > >multiplex use with examples, just as we should publish an
Informational
> RFC
> > > >giving example call flows.
> > >
> > > Why not removing the whole multiplex chapter from the core protocol,
> > > then, and putting it in a separate Annex, or something? The way it's
> > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > You simply can't implement multiplexing with the info you get from
that
> > > text (you don't know how to map the LCNs, which btw also are
> > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > enough in my opinion.
> > >
> > > I thought that the ITU people always wanted to specify everything very
> > > much in detail :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > -----Original Message-----
> > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > To: Christian Groves
> > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > >
> > > > Hi,
> > > >
> > > > >I think that the H.324 package probably needs to be updated to say
> how
> > > > >this is done. I don't think its a core H.248 issue.
> > > >
> > > > I agree. The idea was that this property would be defined in the
H.324
> > > > package, and then used within each stream descriptor in the Mux
> > > > Termination.
> > > >
> > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> see a
> > > > reply from the
> > > > > H324 package authors on how they thought this was to be done.
> > > >
> > > > >Are there any updates you'd like to see to proposed text on
> > > > MultiplexDescriptors that Tom posted?
> > > >
> > > > First, as Tom already mentioned, it should be updated so that it
also
> > > > includes emphemeral bearer terminations (RTP terminations, for
> example).
> > > >
> > > > Second, it should in detail, on a message level, describe how the
> > > > multiplexed connection is set up. Now it only says "use a stream
> > > > descriptor" - which means everyone is going to understand it their
own
> > > > way, and we are going to have lots of interop problems when people
> start
> > > > implementing this :)
> > > >
> > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > multiplex method is used) descriptor is used, ie which terminations
> are
> > > > included etc, depending on on which "side" of the multiplexer the
> > > > terminations are.
> > > >
> > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > another discussion...
> > > >
> > > > I understand if you want to get this document ready before february,
> but
> > > > please let us do this correct from the beginning :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > Regards, Christian
> > > > >
> > > > > Christer Holmberg wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have read the document a few times, but even by having stream
> > > > > > descriptors in the mux termination, I still don't understand how
> each of
> > > > > > those stream descriptors are mapped to specific LNCs. Is the
> StreamID
> > > > > > supposed to be the same as the LCN number, or how is the mapping
> done?
> > > > > >
> > > > > > A very simple solution would be to add a "LCN property" (to the
> H.324
> > > > > > package, I assume) which would be used in the each stream
> descriptor to
> > > > > > specify to which LCN it is mapped.
> > > > > >
> > > > > > Comments?
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Christer Holmberg
> > > > > > Ericsson Finland
> > > > > >
> > > > > > Tom-PT Taylor wrote:
> > > > > > >
> > > > > > > I mentioned that several of us have been discussing additional
> text
> > > > for
> > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> marked up
> > > > changes
> > > > > > > in the Megaco FTP site.  According to your taste, you can
> download
> > > > > > >
> > > >
>
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.doc
> > > > > > > or
> > > > > > >
> > > >
>
ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.pdf
> > > > > > >
> > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> Mapping"), this
> > > > > > > proposed text needs a further update.  The supporting bearers
> > > > contained by a
> > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > However, I
> > > > > > > believe it would be essential that any ephemrals mentioned in
a
> MUX
> > > > > > > descriptor already exist in the context, since their
properties
> are
> > > > probably
> > > > > > > not directly inferrable from those of the multiplexing
> termination.
> > > > > > >
> > > > > > > Tom Taylor
> > > > > > > taylor@nortelnetworks.com
> > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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



From megaco-admin@ietf.org  Wed Jan 23 09:45:50 2002
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 JAA10699
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:45:50 -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 JAA28225;
	Wed, 23 Jan 2002 09:31:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28136
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:31:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10223
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:31:13 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NEUed07668;
	Wed, 23 Jan 2002 09:30:40 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NEUcn10411;
	Wed, 23 Jan 2002 09:30:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZBAQ>; Wed, 23 Jan 2002 09:30:39 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Wed, 23 Jan 2002 09:30:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A41A.86A74A60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A41A.86A74A60
Content-Type: text/plain;
	charset="ISO-8859-1"

Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.  
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command? 
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.  
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds. 



Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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





------_=_NextPart_001_01C1A41A.86A74A60
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Query about streamID 0</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi.&nbsp; See new comments [PTT2] below.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: knayar@hss.hns.com [<A =
HREF=3D"mailto:knayar@hss.hns.com">mailto:knayar@hss.hns.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, January 23, 2002 8:55 AM</FONT>
<BR><FONT SIZE=3D2>To: Taylor, Tom-PT [CAR:B800:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Query about streamID 0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi Tom</FONT>
</P>

<P><FONT SIZE=3D2>my comments embedded.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&quot;Tom-PT Taylor&quot; =
&lt;taylor@nortelnetworks.com&gt; on 01/22/2002 11:35:00 PM</FONT>
</P>

<P><FONT SIZE=3D2>To:&nbsp;&nbsp; Kapil Nayar/HSS@HSS, =
&quot;'megaco@ietf.org'&quot; &lt;megaco@ietf.org&gt;</FONT>
<BR><FONT SIZE=3D2>cc:</FONT>
</P>

<P><FONT SIZE=3D2>Subject:&nbsp; RE: [Megaco] Query about streamID =
0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: knayar@hss.hns.com [<A =
HREF=3D"mailto:knayar@hss.hns.com">mailto:knayar@hss.hns.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Tuesday, January 22, 2002 8:54 AM</FONT>
<BR><FONT SIZE=3D2>To: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Query about streamID 0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi Tom &amp; list,</FONT>
</P>

<P><FONT SIZE=3D2>RFC 3015 Section 7.1.9 Event Descriptor &amp; 7.1.11 =
Signal Descriptor mentions:</FONT>
</P>

<P><FONT SIZE=3D2>&quot;The default streamID is 0, indicating that the =
event to be detected is not</FONT>
<BR><FONT SIZE=3D2>related to a particular media stream.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Does the &quot;streamID 0&quot; refer to the complete =
termination (which means all the</FONT>
<BR><FONT SIZE=3D2>active streams on the termination) ?</FONT>
</P>

<P><FONT SIZE=3D2>[PTT] No.&nbsp; It really means as it says, that the =
event or signal is not</FONT>
<BR><FONT SIZE=3D2>associated with any specific stream.&nbsp; An =
example is an electrical signal</FONT>
<BR><FONT SIZE=3D2>such as off-hook.</FONT>
<BR><FONT SIZE=3D2>[KN] Does that mean that stream 0 is possible for =
only physical terminations,</FONT>
<BR><FONT SIZE=3D2>since electrical signals are more appropriate for =
physical terminations.</FONT>
<BR><FONT SIZE=3D2>[PTT2] There can be applications of streamId 0 on =
ephemerals which don't relate to specific streams.&nbsp; Electrical =
signals were just an example.&nbsp; I suspect I could find a good =
example in one of my NAS packages of something more abstract, but I =
won't take the time.&nbsp; Just accept that we don't want to foreclose =
the possibility of using this on ephemerals.</FONT></P>

<P><FONT SIZE=3D2>And, if some event is required to be detected on the =
ephemeral termination,</FONT>
<BR><FONT SIZE=3D2>the event descriptor should clearly identify which =
stream it is required on.</FONT>
<BR><FONT SIZE=3D2>(i.e., MGC cannot send an events descriptor for =
ephemeral termination without</FONT>
<BR><FONT SIZE=3D2>stream ID parameter since that defaults to stream ID =
0, which may not be</FONT>
<BR><FONT SIZE=3D2>applicable).</FONT>
<BR><FONT SIZE=3D2>[PTT2] That has to be thought through for all =
terminations.&nbsp; </FONT>
<BR><FONT SIZE=3D2>*** IG issue: It does strike me that you can know in =
advance (by definition of the event or signal) whether streamId=3D0 =
will apply.&nbsp; We should therefore make it requirement to specify =
this in package definitions.</FONT></P>

<P><FONT SIZE=3D2>[PTT] On the other hand, an audio signal such as a =
DTMF tone is</FONT>
<BR><FONT SIZE=3D2>associated with an audio stream.&nbsp; (But I bet =
nobody has bothered to specify</FONT>
<BR><FONT SIZE=3D2>stream 1 for DTMF events when they are using a =
default streamId for audio.</FONT>
<BR><FONT SIZE=3D2>They should!)</FONT>
<BR><FONT SIZE=3D2>[KN] Does that mean that before sending DTMFdet =
(dd/&lt;?&gt;) in events descriptor,</FONT>
<BR><FONT SIZE=3D2>MGC should have already created the stream 1 thru' =
the media descriptor</FONT>
<BR><FONT SIZE=3D2>in a previous command? </FONT>
<BR><FONT SIZE=3D2>[PTT2] StreamId=3D1 is the default stream created if =
you don't use a stream descriptor, but just specify Local, Remote, and =
LocalControl.</FONT></P>

<P><FONT SIZE=3D2>*** IG issue: would it make more sense to have =
streamId=3D0 as the default for signals and events, or have =
streamId=3D1 as the default?</FONT></P>

<P><FONT SIZE=3D2>A related doubt is...if an event descriptor =
refers</FONT>
<BR><FONT SIZE=3D2>to a stream ID which is not previously created by =
the MGC, MG should</FONT>
<BR><FONT SIZE=3D2>return an error.</FONT>
<BR><FONT SIZE=3D2>[PTT2] I'm not sure.&nbsp; Remember that streamIds =
are really a context property.&nbsp; If a given streamId is supported =
somewhere in the context, then referring to that streamId at a given =
termination implies that the termination also supports it.&nbsp; That =
means it could detect events or send signals on the stream even if it =
doesn't know how to handle the media flows on that stream.&nbsp; I =
suppose if this is the first mention of the streamId in the context, it =
might be appropriate to reject the command.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>***IG issue: The implication is that within any =
command, Stream Descriptors for new streams MUST appear before Signals =
and Events descriptors referring to those StreamIds. </FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Can MGC send streamID value 0 in a MEGACO command/ =
descriptor. eg: media</FONT>
<BR><FONT SIZE=3D2>descriptor, event descriptor, signal descriptor =
?</FONT>
</P>

<P><FONT SIZE=3D2>[PTT] Logically, you cannot use streamId =3D 0 in a =
media descriptor and be</FONT>
<BR><FONT SIZE=3D2>consistent with the meaning of that streamId for =
events and signals.&nbsp; We</FONT>
<BR><FONT SIZE=3D2>should have a note to the effect that streamId=3D0 =
is reserved in sections</FONT>
<BR><FONT SIZE=3D2>7.1.4 (for thoroughness) and 7.1.6.</FONT>
</P>

<P><FONT SIZE=3D2>You can specify streamId=3D0 in a signals or events =
descriptor, but that's the</FONT>
<BR><FONT SIZE=3D2>same as leaving it unspecified.</FONT>
</P>

<P><FONT SIZE=3D2>Please reply back...</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Kapil Nayar</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&quot;DISCLAIMER: This message is proprietary to =
Hughes Software Systmes Limited</FONT>
<BR><FONT SIZE=3D2>(HSS) and is intended solely for the use of the =
individual&nbsp; to whom it is</FONT>
<BR><FONT SIZE=3D2>addressed. It may contain&nbsp; privileged or =
confidential information&nbsp; and</FONT>
<BR><FONT SIZE=3D2>should</FONT>
<BR><FONT SIZE=3D2>not be circulated or used for any purpose other than =
for what it is</FONT>
<BR><FONT SIZE=3D2>intended.If</FONT>
<BR><FONT SIZE=3D2>you have received this message in error, please =
notify the originator</FONT>
<BR><FONT SIZE=3D2>immediately. If you are not the intended recipient, =
you are notified that</FONT>
<BR><FONT SIZE=3D2>you</FONT>
<BR><FONT SIZE=3D2>are strictly prohibited from using, copying, =
altering, or disclosing the</FONT>
<BR><FONT SIZE=3D2>contents of this message. HSS accepts no =
responsibility for loss or damage</FONT>
<BR><FONT SIZE=3D2>arising from the use of the information transimitted =
by this email including</FONT>
<BR><FONT SIZE=3D2>damage from virus.&quot;</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"https://www1.ietf.org/mailman/listinfo/meg=
aco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1A41A.86A74A60--

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


From daemon@optimus.ietf.org  Wed Jan 23 09:45:53 2002
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 IAA07816
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 08:35:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA25877
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 08:35:22 -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 IAA25082;
	Wed, 23 Jan 2002 08:25:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA25052
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 08:25:12 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07635
	for <megaco@ietf.org>; Wed, 23 Jan 2002 08:25:09 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0NDP3w25665;
	Wed, 23 Jan 2002 14:25:03 +0100 (MET)
Received: from lmf.ericsson.se (E005004B52C74.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0NDP3r6015307;
	Wed, 23 Jan 2002 15:25:03 +0200 (EET)
Message-ID: <3C4EB9AD.8E7BC8CC@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 15:25:01 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AEC5@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>The LCNs are specific to one application, not a general multiplexing issue.
>(Although I suppose a similar issue arises with H.320, I also think H.320
>would need its own annex.)  I think the mapping has to be described in Annex
>M.4 for H.324.

As long as it's somewhere :)

>The most obvious solution is as Christer indicated: an LCN property in LocalControl.

Actually, I am not sure LocalControl is the correct place. Annex M.4
specifies the multiplex properties in the TerminationState descriptor,
so this information could be there. Note that Annex M.4 does not use a
Multiplex Termination (the multiplexing is done in the TDM termination),
and there are no stream descriptors defined for the LCNs. IF a
Multiplexing Termination is used, according to the H.248 core spec,
separate stream descriptor shall be defined for each LCN, and in that
case it could be a property in LocalControl.

Also, is there a specific reason why the H245 Message event, defined in
the H.245 Package (M4.5) can't be used for the H.245 backhauling???


Regards,

Christer Holmberg
Ericsson Finland



> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Tuesday, January 22, 2002 2:35 AM
> To: Christian Groves
> Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >I don't think we can remove the whole chapter from the protocol at this
> >stage. I agree with Tom that we can do some call flows in a seperate
> >annex.
> 
> Oki.
> 
> >I'll add some text on the euphemeral terminations to the proposed
> clarification.
> 
> So, we shouldn't say anything about the Stream Descriptors in the Mux
> Termination? How they are mapped to the LCNs etc? Personally I don't
> care if it's said in the core spec, or in a separate Annex, but I don't
> understand what the purpose is to put stuff in the core which nobody can
> use :)
> 
> Does anyone know if there has been any response on this issue from SG16?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > Regards, Christian
> >
> > Christer Holmberg wrote:
> > >
> > > Hi,
> > >
> > > >While we're on the topic of Annex M.4, I realized while reading it that
> it
> > > >improperly (I think) includes some control terminations in the
> multiplex.
> > > >This may be water under the bridge now -- too late to do anything about
> it.
> > > >
> > > >Anyway, Christer is asking for more than I would put into the core
> protocol
> > > >specification.  We should probably create an Informational RFC
> describing
> > > >multiplex use with examples, just as we should publish an Informational
> RFC
> > > >giving example call flows.
> > >
> > > Why not removing the whole multiplex chapter from the core protocol,
> > > then, and putting it in a separate Annex, or something? The way it's
> > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > You simply can't implement multiplexing with the info you get from that
> > > text (you don't know how to map the LCNs, which btw also are
> > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > enough in my opinion.
> > >
> > > I thought that the ITU people always wanted to specify everything very
> > > much in detail :)
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > >
> > > > -----Original Message-----
> > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > To: Christian Groves
> > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > >
> > > > Hi,
> > > >
> > > > >I think that the H.324 package probably needs to be updated to say
> how
> > > > >this is done. I don't think its a core H.248 issue.
> > > >
> > > > I agree. The idea was that this property would be defined in the H.324
> > > > package, and then used within each stream descriptor in the Mux
> > > > Termination.
> > > >
> > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> see a
> > > > reply from the
> > > > > H324 package authors on how they thought this was to be done.
> > > >
> > > > >Are there any updates you'd like to see to proposed text on
> > > > MultiplexDescriptors that Tom posted?
> > > >
> > > > First, as Tom already mentioned, it should be updated so that it also
> > > > includes emphemeral bearer terminations (RTP terminations, for
> example).
> > > >
> > > > Second, it should in detail, on a message level, describe how the
> > > > multiplexed connection is set up. Now it only says "use a stream
> > > > descriptor" - which means everyone is going to understand it their own
> > > > way, and we are going to have lots of interop problems when people
> start
> > > > implementing this :)
> > > >
> > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > multiplex method is used) descriptor is used, ie which terminations
> are
> > > > included etc, depending on on which "side" of the multiplexer the
> > > > terminations are.
> > > >
> > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > another discussion...
> > > >
> > > > I understand if you want to get this document ready before february,
> but
> > > > please let us do this correct from the beginning :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > Regards, Christian
> > > > >
> > > > > Christer Holmberg wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have read the document a few times, but even by having stream
> > > > > > descriptors in the mux termination, I still don't understand how
> each of
> > > > > > those stream descriptors are mapped to specific LNCs. Is the
> StreamID
> > > > > > supposed to be the same as the LCN number, or how is the mapping
> done?
> > > > > >
> > > > > > A very simple solution would be to add a "LCN property" (to the
> H.324
> > > > > > package, I assume) which would be used in the each stream
> descriptor to
> > > > > > specify to which LCN it is mapped.
> > > > > >
> > > > > > Comments?
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Christer Holmberg
> > > > > > Ericsson Finland
> > > > > >
> > > > > > Tom-PT Taylor wrote:
> > > > > > >
> > > > > > > I mentioned that several of us have been discussing additional
> text
> > > > for
> > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> marked up
> > > > changes
> > > > > > > in the Megaco FTP site.  According to your taste, you can
> download
> > > > > > >
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.doc
> > > > > > > or
> > > > > > >
> > > >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > x64K.pdf
> > > > > > >
> > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> Mapping"), this
> > > > > > > proposed text needs a further update.  The supporting bearers
> > > > contained by a
> > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > However, I
> > > > > > > believe it would be essential that any ephemrals mentioned in a
> MUX
> > > > > > > descriptor already exist in the context, since their properties
> are
> > > > probably
> > > > > > > not directly inferrable from those of the multiplexing
> termination.
> > > > > > >
> > > > > > > Tom Taylor
> > > > > > > taylor@nortelnetworks.com
> > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > 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



From daemon@optimus.ietf.org  Wed Jan 23 09:45:55 2002
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 JAA10712
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 09:45:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA28755
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 09:45:51 -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 JAA28225;
	Wed, 23 Jan 2002 09:31:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28136
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:31:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10223
	for <megaco@ietf.org>; Wed, 23 Jan 2002 09:31:13 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NEUed07668;
	Wed, 23 Jan 2002 09:30:40 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NEUcn10411;
	Wed, 23 Jan 2002 09:30:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZBAQ>; Wed, 23 Jan 2002 09:30:39 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AED9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Wed, 23 Jan 2002 09:30:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A41A.86A74A60"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A41A.86A74A60
Content-Type: text/plain;
	charset="ISO-8859-1"

Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.  
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command? 
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.  
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds. 



Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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





------_=_NextPart_001_01C1A41A.86A74A60
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Query about streamID 0</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi.&nbsp; See new comments [PTT2] below.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: knayar@hss.hns.com [<A =
HREF=3D"mailto:knayar@hss.hns.com">mailto:knayar@hss.hns.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, January 23, 2002 8:55 AM</FONT>
<BR><FONT SIZE=3D2>To: Taylor, Tom-PT [CAR:B800:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Query about streamID 0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi Tom</FONT>
</P>

<P><FONT SIZE=3D2>my comments embedded.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&quot;Tom-PT Taylor&quot; =
&lt;taylor@nortelnetworks.com&gt; on 01/22/2002 11:35:00 PM</FONT>
</P>

<P><FONT SIZE=3D2>To:&nbsp;&nbsp; Kapil Nayar/HSS@HSS, =
&quot;'megaco@ietf.org'&quot; &lt;megaco@ietf.org&gt;</FONT>
<BR><FONT SIZE=3D2>cc:</FONT>
</P>

<P><FONT SIZE=3D2>Subject:&nbsp; RE: [Megaco] Query about streamID =
0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: knayar@hss.hns.com [<A =
HREF=3D"mailto:knayar@hss.hns.com">mailto:knayar@hss.hns.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Tuesday, January 22, 2002 8:54 AM</FONT>
<BR><FONT SIZE=3D2>To: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Query about streamID 0</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi Tom &amp; list,</FONT>
</P>

<P><FONT SIZE=3D2>RFC 3015 Section 7.1.9 Event Descriptor &amp; 7.1.11 =
Signal Descriptor mentions:</FONT>
</P>

<P><FONT SIZE=3D2>&quot;The default streamID is 0, indicating that the =
event to be detected is not</FONT>
<BR><FONT SIZE=3D2>related to a particular media stream.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Does the &quot;streamID 0&quot; refer to the complete =
termination (which means all the</FONT>
<BR><FONT SIZE=3D2>active streams on the termination) ?</FONT>
</P>

<P><FONT SIZE=3D2>[PTT] No.&nbsp; It really means as it says, that the =
event or signal is not</FONT>
<BR><FONT SIZE=3D2>associated with any specific stream.&nbsp; An =
example is an electrical signal</FONT>
<BR><FONT SIZE=3D2>such as off-hook.</FONT>
<BR><FONT SIZE=3D2>[KN] Does that mean that stream 0 is possible for =
only physical terminations,</FONT>
<BR><FONT SIZE=3D2>since electrical signals are more appropriate for =
physical terminations.</FONT>
<BR><FONT SIZE=3D2>[PTT2] There can be applications of streamId 0 on =
ephemerals which don't relate to specific streams.&nbsp; Electrical =
signals were just an example.&nbsp; I suspect I could find a good =
example in one of my NAS packages of something more abstract, but I =
won't take the time.&nbsp; Just accept that we don't want to foreclose =
the possibility of using this on ephemerals.</FONT></P>

<P><FONT SIZE=3D2>And, if some event is required to be detected on the =
ephemeral termination,</FONT>
<BR><FONT SIZE=3D2>the event descriptor should clearly identify which =
stream it is required on.</FONT>
<BR><FONT SIZE=3D2>(i.e., MGC cannot send an events descriptor for =
ephemeral termination without</FONT>
<BR><FONT SIZE=3D2>stream ID parameter since that defaults to stream ID =
0, which may not be</FONT>
<BR><FONT SIZE=3D2>applicable).</FONT>
<BR><FONT SIZE=3D2>[PTT2] That has to be thought through for all =
terminations.&nbsp; </FONT>
<BR><FONT SIZE=3D2>*** IG issue: It does strike me that you can know in =
advance (by definition of the event or signal) whether streamId=3D0 =
will apply.&nbsp; We should therefore make it requirement to specify =
this in package definitions.</FONT></P>

<P><FONT SIZE=3D2>[PTT] On the other hand, an audio signal such as a =
DTMF tone is</FONT>
<BR><FONT SIZE=3D2>associated with an audio stream.&nbsp; (But I bet =
nobody has bothered to specify</FONT>
<BR><FONT SIZE=3D2>stream 1 for DTMF events when they are using a =
default streamId for audio.</FONT>
<BR><FONT SIZE=3D2>They should!)</FONT>
<BR><FONT SIZE=3D2>[KN] Does that mean that before sending DTMFdet =
(dd/&lt;?&gt;) in events descriptor,</FONT>
<BR><FONT SIZE=3D2>MGC should have already created the stream 1 thru' =
the media descriptor</FONT>
<BR><FONT SIZE=3D2>in a previous command? </FONT>
<BR><FONT SIZE=3D2>[PTT2] StreamId=3D1 is the default stream created if =
you don't use a stream descriptor, but just specify Local, Remote, and =
LocalControl.</FONT></P>

<P><FONT SIZE=3D2>*** IG issue: would it make more sense to have =
streamId=3D0 as the default for signals and events, or have =
streamId=3D1 as the default?</FONT></P>

<P><FONT SIZE=3D2>A related doubt is...if an event descriptor =
refers</FONT>
<BR><FONT SIZE=3D2>to a stream ID which is not previously created by =
the MGC, MG should</FONT>
<BR><FONT SIZE=3D2>return an error.</FONT>
<BR><FONT SIZE=3D2>[PTT2] I'm not sure.&nbsp; Remember that streamIds =
are really a context property.&nbsp; If a given streamId is supported =
somewhere in the context, then referring to that streamId at a given =
termination implies that the termination also supports it.&nbsp; That =
means it could detect events or send signals on the stream even if it =
doesn't know how to handle the media flows on that stream.&nbsp; I =
suppose if this is the first mention of the streamId in the context, it =
might be appropriate to reject the command.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>***IG issue: The implication is that within any =
command, Stream Descriptors for new streams MUST appear before Signals =
and Events descriptors referring to those StreamIds. </FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Can MGC send streamID value 0 in a MEGACO command/ =
descriptor. eg: media</FONT>
<BR><FONT SIZE=3D2>descriptor, event descriptor, signal descriptor =
?</FONT>
</P>

<P><FONT SIZE=3D2>[PTT] Logically, you cannot use streamId =3D 0 in a =
media descriptor and be</FONT>
<BR><FONT SIZE=3D2>consistent with the meaning of that streamId for =
events and signals.&nbsp; We</FONT>
<BR><FONT SIZE=3D2>should have a note to the effect that streamId=3D0 =
is reserved in sections</FONT>
<BR><FONT SIZE=3D2>7.1.4 (for thoroughness) and 7.1.6.</FONT>
</P>

<P><FONT SIZE=3D2>You can specify streamId=3D0 in a signals or events =
descriptor, but that's the</FONT>
<BR><FONT SIZE=3D2>same as leaving it unspecified.</FONT>
</P>

<P><FONT SIZE=3D2>Please reply back...</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Kapil Nayar</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&quot;DISCLAIMER: This message is proprietary to =
Hughes Software Systmes Limited</FONT>
<BR><FONT SIZE=3D2>(HSS) and is intended solely for the use of the =
individual&nbsp; to whom it is</FONT>
<BR><FONT SIZE=3D2>addressed. It may contain&nbsp; privileged or =
confidential information&nbsp; and</FONT>
<BR><FONT SIZE=3D2>should</FONT>
<BR><FONT SIZE=3D2>not be circulated or used for any purpose other than =
for what it is</FONT>
<BR><FONT SIZE=3D2>intended.If</FONT>
<BR><FONT SIZE=3D2>you have received this message in error, please =
notify the originator</FONT>
<BR><FONT SIZE=3D2>immediately. If you are not the intended recipient, =
you are notified that</FONT>
<BR><FONT SIZE=3D2>you</FONT>
<BR><FONT SIZE=3D2>are strictly prohibited from using, copying, =
altering, or disclosing the</FONT>
<BR><FONT SIZE=3D2>contents of this message. HSS accepts no =
responsibility for loss or damage</FONT>
<BR><FONT SIZE=3D2>arising from the use of the information transimitted =
by this email including</FONT>
<BR><FONT SIZE=3D2>damage from virus.&quot;</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"https://www1.ietf.org/mailman/listinfo/meg=
aco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1A41A.86A74A60--

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



From megaco-admin@ietf.org  Wed Jan 23 10:05:40 2002
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 KAA11450
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 10:05:40 -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 JAA29066;
	Wed, 23 Jan 2002 09:56:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29041
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:56:37 -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 JAA11010
	for <Megaco@ietf.org>; Wed, 23 Jan 2002 09:56:34 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA03414;
	Wed, 23 Jan 2002 15:54:56 +0100 (MET)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA28874;
	Wed, 23 Jan 2002 15:54:57 +0100 (MET)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <ZWXST47J>; Wed, 23 Jan 2002 15:54:56 +0100
Message-ID: <E01FD2A7A400D511A97C0008C791E2DF27B2C2@MCHH262E>
From: Leis Peter <Peter.Leis@icn.siemens.de>
To: "'Megaco@ietf.org'" <Megaco@ietf.org>
Cc: "'Christian.Groves@ericsson.com.au'"
	 <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor
	 <taylor@NORTELNETWORKS.COM>,
        Terry Anderson <tla@lucent.com>
Date: Wed, 23 Jan 2002 15:54:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] question on ServiceChange
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

hi,

back in november there was a discussion about MG accepting a ServiceChange from a MGC
currently not controlling it. I want to stress this issue once again. In addition I will provide
a delayed contribution to the SG-16 meeting in Geneva to start a discussion there. 
Here some thoughts:

Indroduction:

This contribution proposes that a MG controlled by MGC1 (primary) and MGC2 (secondary) is allowed to accept a ServiceChange with method = Handoff  from MGC2 (assuming MGC2 detects that MGC1 has failed).

Disussion:

H.248/RFC3051 describes the behavior of the MG/MGC in case of MGC Failure as follows:
'If the MG detects a failure of its controlling MGC, it attempts to contact the next MGC on its pre-provisioned list.  It starts its attempts at the beginning (Primary MGC), unless that was the MGC that failed, in which case it starts at its first Secondary MGC.  It sends a ServiceChange message with a "Failover" method and a " MGC Impending Failure" reason.  

In partial failure, or manual maintenance reasons, an MGC may wish to direct its controlled MGs to use a different MGC.  To do so, it sends a ServiceChange method to the MG with a "HandOff" method, and its designated replacement in ServiceChangeMgcId. The MG should send a ServiceChange message with a "Handoff" method and a "MGC directed change" reason to the designated MGC.  If it fails to get a reply, or fails to see an Audit command subsequently, it should behave as if its MGC failed, and start contacting secondary MGCs.  If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in section 9.2 and then start contacting its primary, and if necessary, its secondary MGCs again.'

In a UDP environment this leads to the following situation:
If the primary MGC1 fails without being able to send a ServiceChange method with a "HandOff"method then it will take LONG-TIMER (the recommendation suggests 30 sec) till MG will detect the death of MGC1 and sending the ServiceChange to the secondary MGC. This means that the MTBF is quite long. 

Improvement:
This behavior could be improved if the secondary MGC would be allowed to take over the control once it has detected the death of the primary MGC. It is assumed that this happens sooner than the detection by the MG. For this mechanism the MG would have to accept a ServiceChange method with a "HandOff" sent by the secondary MGC and establish the control association to this MGC. 

Use cases:
In an environment where the MGC's are 'controlled' in a centralized manner the control association MGC-MG could be maintained more efficient by the MGC's. This way the switchover from MGC1 to MGC2 can be achieved fast and a short MTBF will be possible.

Implications:
Once the MG has accepted the ServiceChange method with 'HandOff" from the secondary MGC it has to discard all call related requests from its previously controlling MGC.
Once the MG has accepted the ServiceChange method with 'HandOff' all currently outstanding Transactions to MGC1 have to be deleted.
Handling of state information between MGC1 and MGC2 is out of scope of the recommendation

Proposal:

Make the following additions in H.248v2 in section 11.5:

If a secondary MGC detects the death failure of the primary MGC (detection mechanism out of scope of this recommendation) and the transport of the protocol is done via UDP it may send a ServiceChange method to the MG with a "HandOff" method, and its own MgcId in ServiceChangeMgcId. The MG may accept the ServiceChange method Request from this MGC currently not controlling it if this MGC is contained in the MG's preconfigured MGC list and establish the control relation. To do so the MG should first send a ServiceChangeReply. Afterwards the MG should send a ServiceChange message with a "Handoff" method and a "MGC directed change" reason to the specified MGC (to be inline with the current mechanism). After the control relation is established the MGC should initiate an AuditValue command in order to retrieve the current call data from the MG.



Any comments/ideas on this???

regards,
Peter


 


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


From daemon@optimus.ietf.org  Wed Jan 23 10:05:41 2002
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 KAA11459
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 10:05:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA29634
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 10:05:41 -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 JAA29066;
	Wed, 23 Jan 2002 09:56:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29041
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 09:56:37 -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 JAA11010
	for <Megaco@ietf.org>; Wed, 23 Jan 2002 09:56:34 -0500 (EST)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA03414;
	Wed, 23 Jan 2002 15:54:56 +0100 (MET)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA28874;
	Wed, 23 Jan 2002 15:54:57 +0100 (MET)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <ZWXST47J>; Wed, 23 Jan 2002 15:54:56 +0100
Message-ID: <E01FD2A7A400D511A97C0008C791E2DF27B2C2@MCHH262E>
From: Leis Peter <Peter.Leis@icn.siemens.de>
To: "'Megaco@ietf.org'" <Megaco@ietf.org>
Cc: "'Christian.Groves@ericsson.com.au'"
	 <Christian.Groves@ericsson.com.au>,
        Tom-PT Taylor
	 <taylor@NORTELNETWORKS.COM>,
        Terry Anderson <tla@lucent.com>
Date: Wed, 23 Jan 2002 15:54:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] question on ServiceChange
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

hi,

back in november there was a discussion about MG accepting a ServiceChange from a MGC
currently not controlling it. I want to stress this issue once again. In addition I will provide
a delayed contribution to the SG-16 meeting in Geneva to start a discussion there. 
Here some thoughts:

Indroduction:

This contribution proposes that a MG controlled by MGC1 (primary) and MGC2 (secondary) is allowed to accept a ServiceChange with method = Handoff  from MGC2 (assuming MGC2 detects that MGC1 has failed).

Disussion:

H.248/RFC3051 describes the behavior of the MG/MGC in case of MGC Failure as follows:
'If the MG detects a failure of its controlling MGC, it attempts to contact the next MGC on its pre-provisioned list.  It starts its attempts at the beginning (Primary MGC), unless that was the MGC that failed, in which case it starts at its first Secondary MGC.  It sends a ServiceChange message with a "Failover" method and a " MGC Impending Failure" reason.  

In partial failure, or manual maintenance reasons, an MGC may wish to direct its controlled MGs to use a different MGC.  To do so, it sends a ServiceChange method to the MG with a "HandOff" method, and its designated replacement in ServiceChangeMgcId. The MG should send a ServiceChange message with a "Handoff" method and a "MGC directed change" reason to the designated MGC.  If it fails to get a reply, or fails to see an Audit command subsequently, it should behave as if its MGC failed, and start contacting secondary MGCs.  If the MG is unable to establish a control relationship with any MGC, it shall wait a random amount of time as described in section 9.2 and then start contacting its primary, and if necessary, its secondary MGCs again.'

In a UDP environment this leads to the following situation:
If the primary MGC1 fails without being able to send a ServiceChange method with a "HandOff"method then it will take LONG-TIMER (the recommendation suggests 30 sec) till MG will detect the death of MGC1 and sending the ServiceChange to the secondary MGC. This means that the MTBF is quite long. 

Improvement:
This behavior could be improved if the secondary MGC would be allowed to take over the control once it has detected the death of the primary MGC. It is assumed that this happens sooner than the detection by the MG. For this mechanism the MG would have to accept a ServiceChange method with a "HandOff" sent by the secondary MGC and establish the control association to this MGC. 

Use cases:
In an environment where the MGC's are 'controlled' in a centralized manner the control association MGC-MG could be maintained more efficient by the MGC's. This way the switchover from MGC1 to MGC2 can be achieved fast and a short MTBF will be possible.

Implications:
Once the MG has accepted the ServiceChange method with 'HandOff" from the secondary MGC it has to discard all call related requests from its previously controlling MGC.
Once the MG has accepted the ServiceChange method with 'HandOff' all currently outstanding Transactions to MGC1 have to be deleted.
Handling of state information between MGC1 and MGC2 is out of scope of the recommendation

Proposal:

Make the following additions in H.248v2 in section 11.5:

If a secondary MGC detects the death failure of the primary MGC (detection mechanism out of scope of this recommendation) and the transport of the protocol is done via UDP it may send a ServiceChange method to the MG with a "HandOff" method, and its own MgcId in ServiceChangeMgcId. The MG may accept the ServiceChange method Request from this MGC currently not controlling it if this MGC is contained in the MG's preconfigured MGC list and establish the control relation. To do so the MG should first send a ServiceChangeReply. Afterwards the MG should send a ServiceChange message with a "Handoff" method and a "MGC directed change" reason to the specified MGC (to be inline with the current mechanism). After the control relation is established the MGC should initiate an AuditValue command in order to retrieve the current call data from the MG.



Any comments/ideas on this???

regards,
Peter


 


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



From megaco-admin@ietf.org  Wed Jan 23 10:50:52 2002
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 KAA13264
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 10:50:52 -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 KAA00949;
	Wed, 23 Jan 2002 10:42:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00920
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 10:42:23 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12922
	for <megaco@ietf.org>; Wed, 23 Jan 2002 10:42:21 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NFfUF17623
	for <megaco@ietf.org>; Wed, 23 Jan 2002 10:41:30 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id KAA19637; Wed, 23 Jan 2002 10:41:26 -0500 (EST)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id KAA19628; Wed, 23 Jan 2002 10:41:22 -0500 (EST)
Message-ID: <3C4ED8FB.9C9B5100@bell-labs.com>
Date: Wed, 23 Jan 2002 10:38:35 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Raphael Tryster <raphael@tdsoft.com>
Original-CC: megaco@ietf.org
Subject: Re: [Megaco] misleading ABNF comment on stream descriptor?
References: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


I agree that the ABNF comment is incorrect.

It should be

        ; at-most-one terminationStateDescriptor
        ; and either streamParm(s) or streamDescriptor(s) but not both


-troy


> Raphael Tryster wrote:
> 
> The previous posting came out garbled.
> 
>      Here is something from the archive which was never answered.  I think
>      the answer to Steven's question is that section 7.1.4 is right and the
>      comment in the ABNF is wrong, as the ASN sp; Will the comment in the
>      ABNF be changed?
> 
>      Raphael Tryster
> 
>      From: Steven Weisz <sweisz@mediatrix.com>
>      To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
>      Subject: Clarification on Media Descriptor needed.
>      Date: Tue, 24 Apr 2001 13:32:09 -0400
>      MIME-Version: 1.0
>      X-Mailer: Internet Mail Service (5.5 Content-Type: text/plain;
>              charset="iso-8859-1"
>      Sender: owner-megaco@pit.comms.marconi.com
>      Precedence: bulk
> 
>      Hi List,
> 
>      I need some clarification regarding the Media Descriptor. Specifically
>      in
>      section 7.1.4, paragraph 1 the protocol states:
> 
>        "The Media Descriptor specifies the parameters for all the media
>         streams.  These parameters are structured into two descriptors, a
>         Termination State Descriptor, which specifies the properties of a
>         termination that are not stream dependent, and one or more Stream
>         Descriptors each of which describes a single media stream."
> 
>      This states that a Media Descriptor has one or more Stream Descriptors
>      associated with it. However, in the ABNF we have:
> 
>        "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
>                              RBRKT
> 
>         ; at-most-once per item
>         ; and either streamParm or streamDescriptor but not both
>         mediaParm            = (streamParm / streamDescriptor /
>                                 terminationStateDescriptor)"
> 
>      Which to me seems to say that we have only one Stream Descriptor
>      associated
>      with it (as indicated by the comment "; at-most-once per item".
> 
>      Am I interpreting the ABNF correctly?
> 
>      thanks,
> 
>      Steven Weisz

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


From daemon@optimus.ietf.org  Wed Jan 23 10:50:53 2002
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 KAA13273
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 10:50:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01247
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 10:50:54 -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 KAA00949;
	Wed, 23 Jan 2002 10:42:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00920
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 10:42:23 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12922
	for <megaco@ietf.org>; Wed, 23 Jan 2002 10:42:21 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NFfUF17623
	for <megaco@ietf.org>; Wed, 23 Jan 2002 10:41:30 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id KAA19637; Wed, 23 Jan 2002 10:41:26 -0500 (EST)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id KAA19628; Wed, 23 Jan 2002 10:41:22 -0500 (EST)
Message-ID: <3C4ED8FB.9C9B5100@bell-labs.com>
Date: Wed, 23 Jan 2002 10:38:35 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Raphael Tryster <raphael@tdsoft.com>
Original-CC: megaco@ietf.org
Subject: Re: [Megaco] misleading ABNF comment on stream descriptor?
References: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


I agree that the ABNF comment is incorrect.

It should be

        ; at-most-one terminationStateDescriptor
        ; and either streamParm(s) or streamDescriptor(s) but not both


-troy


> Raphael Tryster wrote:
> 
> The previous posting came out garbled.
> 
>      Here is something from the archive which was never answered.  I think
>      the answer to Steven's question is that section 7.1.4 is right and the
>      comment in the ABNF is wrong, as the ASN sp; Will the comment in the
>      ABNF be changed?
> 
>      Raphael Tryster
> 
>      From: Steven Weisz <sweisz@mediatrix.com>
>      To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
>      Subject: Clarification on Media Descriptor needed.
>      Date: Tue, 24 Apr 2001 13:32:09 -0400
>      MIME-Version: 1.0
>      X-Mailer: Internet Mail Service (5.5 Content-Type: text/plain;
>              charset="iso-8859-1"
>      Sender: owner-megaco@pit.comms.marconi.com
>      Precedence: bulk
> 
>      Hi List,
> 
>      I need some clarification regarding the Media Descriptor. Specifically
>      in
>      section 7.1.4, paragraph 1 the protocol states:
> 
>        "The Media Descriptor specifies the parameters for all the media
>         streams.  These parameters are structured into two descriptors, a
>         Termination State Descriptor, which specifies the properties of a
>         termination that are not stream dependent, and one or more Stream
>         Descriptors each of which describes a single media stream."
> 
>      This states that a Media Descriptor has one or more Stream Descriptors
>      associated with it. However, in the ABNF we have:
> 
>        "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
>                              RBRKT
> 
>         ; at-most-once per item
>         ; and either streamParm or streamDescriptor but not both
>         mediaParm            = (streamParm / streamDescriptor /
>                                 terminationStateDescriptor)"
> 
>      Which to me seems to say that we have only one Stream Descriptor
>      associated
>      with it (as indicated by the comment "; at-most-once per item".
> 
>      Am I interpreting the ABNF correctly?
> 
>      thanks,
> 
>      Steven Weisz

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



From megaco-admin@ietf.org  Wed Jan 23 11:48:26 2002
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 LAA15885
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 11:48:26 -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 LAA03795;
	Wed, 23 Jan 2002 11:39:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03769
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 11:39:43 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15571
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:40 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NGdf701237
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:41 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA04921
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:39 -0500 (EST)
Message-ID: <3C4EE692.D477AFDF@lucent.com>
Date: Wed, 23 Jan 2002 11:36:34 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco Mailing List <megaco@ietf.org>
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------FE3A1FD525CA13397F011328"
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in Transaction Reply.
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

This is a multi-part message in MIME format.
--------------FE3A1FD525CA13397F011328
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm copying the list (and designating it as open issue #4) since it has become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
since commandReply there is a comma separated list, but it does NOT allow both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------FE3A1FD525CA13397F011328
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------FE3A1FD525CA13397F011328--


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


From daemon@optimus.ietf.org  Wed Jan 23 11:48:32 2002
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 LAA15894
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 11:48:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA04108
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 11:48:29 -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 LAA03795;
	Wed, 23 Jan 2002 11:39:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03769
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 11:39:43 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15571
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:40 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NGdf701237
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:41 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA04921
	for <megaco@ietf.org>; Wed, 23 Jan 2002 11:39:39 -0500 (EST)
Message-ID: <3C4EE692.D477AFDF@lucent.com>
Date: Wed, 23 Jan 2002 11:36:34 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco Mailing List <megaco@ietf.org>
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------FE3A1FD525CA13397F011328"
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in Transaction Reply.
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

This is a multi-part message in MIME format.
--------------FE3A1FD525CA13397F011328
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm copying the list (and designating it as open issue #4) since it has become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
since commandReply there is a comma separated list, but it does NOT allow both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------FE3A1FD525CA13397F011328
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------FE3A1FD525CA13397F011328--


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



From megaco-admin@ietf.org  Wed Jan 23 12:38:24 2002
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 MAA17729
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 12:38:24 -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 MAA06640;
	Wed, 23 Jan 2002 12:29:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06605
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 12:29:00 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17362
	for <megaco@ietf.org>; Wed, 23 Jan 2002 12:28:50 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0NHShw09721;
	Wed, 23 Jan 2002 18:28:43 +0100 (MET)
Received: from lmf.ericsson.se (lmf05397pc.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0NHSfr6029128;
	Wed, 23 Jan 2002 19:28:41 +0200 (EET)
Message-ID: <3C4EF2C8.CFABC3F1@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 19:28:40 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AED8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>Those multiplex properties you're talking about are a global characteristic
>of H.324 systems.  It makes good sense to put them into TerminationState
>because they describe transport on the exterior side, not the context side
>of the termination.

I would say that properties related to the LCNs describe transport on
the context side, since they specify mappings to streams within the
Context. So, those kind of parameters should maybe (no matter if the
multiplexing is handled by the TDM termination or a specific
Multiplexing Termination) be defined in LocalControl, after all. We
should remember that LCN-to-Stream mapping is not a global
characteristic - they are specific for each stream.
 
>I don't have time to follow through on this today, but perhaps I'll tackle a
>complete description of the H.324 application when I have an idle moment.

Thanks!

Regards,

Christer Holmberg
Ericsson Finland

> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Wednesday, January 23, 2002 8:25 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: Christian Groves; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >The LCNs are specific to one application, not a general multiplexing issue.
> >(Although I suppose a similar issue arises with H.320, I also think H.320
> >would need its own annex.)  I think the mapping has to be described in
> Annex
> >M.4 for H.324.
> 
> As long as it's somewhere :)
> 
> >The most obvious solution is as Christer indicated: an LCN property in
> LocalControl.
> 
> Actually, I am not sure LocalControl is the correct place. Annex M.4
> specifies the multiplex properties in the TerminationState descriptor,
> so this information could be there. Note that Annex M.4 does not use a
> Multiplex Termination (the multiplexing is done in the TDM termination),
> and there are no stream descriptors defined for the LCNs. IF a
> Multiplexing Termination is used, according to the H.248 core spec,
> separate stream descriptor shall be defined for each LCN, and in that
> case it could be a property in LocalControl.
> 
> Also, is there a specific reason why the H245 Message event, defined in
> the H.245 Package (M4.5) can't be used for the H.245 backhauling???
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Tuesday, January 22, 2002 2:35 AM
> > To: Christian Groves
> > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> >
> > Hi,
> >
> > >I don't think we can remove the whole chapter from the protocol at this
> > >stage. I agree with Tom that we can do some call flows in a seperate
> > >annex.
> >
> > Oki.
> >
> > >I'll add some text on the euphemeral terminations to the proposed
> > clarification.
> >
> > So, we shouldn't say anything about the Stream Descriptors in the Mux
> > Termination? How they are mapped to the LCNs etc? Personally I don't
> > care if it's said in the core spec, or in a separate Annex, but I don't
> > understand what the purpose is to put stuff in the core which nobody can
> > use :)
> >
> > Does anyone know if there has been any response on this issue from SG16?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > Regards, Christian
> > >
> > > Christer Holmberg wrote:
> > > >
> > > > Hi,
> > > >
> > > > >While we're on the topic of Annex M.4, I realized while reading it
> that
> > it
> > > > >improperly (I think) includes some control terminations in the
> > multiplex.
> > > > >This may be water under the bridge now -- too late to do anything
> about
> > it.
> > > > >
> > > > >Anyway, Christer is asking for more than I would put into the core
> > protocol
> > > > >specification.  We should probably create an Informational RFC
> > describing
> > > > >multiplex use with examples, just as we should publish an
> Informational
> > RFC
> > > > >giving example call flows.
> > > >
> > > > Why not removing the whole multiplex chapter from the core protocol,
> > > > then, and putting it in a separate Annex, or something? The way it's
> > > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > > You simply can't implement multiplexing with the info you get from
> that
> > > > text (you don't know how to map the LCNs, which btw also are
> > > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > > enough in my opinion.
> > > >
> > > > I thought that the ITU people always wanted to specify everything very
> > > > much in detail :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > > To: Christian Groves
> > > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > > >
> > > > > Hi,
> > > > >
> > > > > >I think that the H.324 package probably needs to be updated to say
> > how
> > > > > >this is done. I don't think its a core H.248 issue.
> > > > >
> > > > > I agree. The idea was that this property would be defined in the
> H.324
> > > > > package, and then used within each stream descriptor in the Mux
> > > > > Termination.
> > > > >
> > > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> > see a
> > > > > reply from the
> > > > > > H324 package authors on how they thought this was to be done.
> > > > >
> > > > > >Are there any updates you'd like to see to proposed text on
> > > > > MultiplexDescriptors that Tom posted?
> > > > >
> > > > > First, as Tom already mentioned, it should be updated so that it
> also
> > > > > includes emphemeral bearer terminations (RTP terminations, for
> > example).
> > > > >
> > > > > Second, it should in detail, on a message level, describe how the
> > > > > multiplexed connection is set up. Now it only says "use a stream
> > > > > descriptor" - which means everyone is going to understand it their
> own
> > > > > way, and we are going to have lots of interop problems when people
> > start
> > > > > implementing this :)
> > > > >
> > > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > > multiplex method is used) descriptor is used, ie which terminations
> > are
> > > > > included etc, depending on on which "side" of the multiplexer the
> > > > > terminations are.
> > > > >
> > > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > > another discussion...
> > > > >
> > > > > I understand if you want to get this document ready before february,
> > but
> > > > > please let us do this correct from the beginning :)
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > >
> > > > > > Regards, Christian
> > > > > >
> > > > > > Christer Holmberg wrote:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have read the document a few times, but even by having stream
> > > > > > > descriptors in the mux termination, I still don't understand how
> > each of
> > > > > > > those stream descriptors are mapped to specific LNCs. Is the
> > StreamID
> > > > > > > supposed to be the same as the LCN number, or how is the mapping
> > done?
> > > > > > >
> > > > > > > A very simple solution would be to add a "LCN property" (to the
> > H.324
> > > > > > > package, I assume) which would be used in the each stream
> > descriptor to
> > > > > > > specify to which LCN it is mapped.
> > > > > > >
> > > > > > > Comments?
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Christer Holmberg
> > > > > > > Ericsson Finland
> > > > > > >
> > > > > > > Tom-PT Taylor wrote:
> > > > > > > >
> > > > > > > > I mentioned that several of us have been discussing additional
> > text
> > > > > for
> > > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> > marked up
> > > > > changes
> > > > > > > > in the Megaco FTP site.  According to your taste, you can
> > download
> > > > > > > >
> > > > >
> >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > > x64K.doc
> > > > > > > > or
> > > > > > > >
> > > > >
> >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > > x64K.pdf
> > > > > > > >
> > > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> > Mapping"), this
> > > > > > > > proposed text needs a further update.  The supporting bearers
> > > > > contained by a
> > > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > > However, I
> > > > > > > > believe it would be essential that any ephemrals mentioned in
> a
> > MUX
> > > > > > > > descriptor already exist in the context, since their
> properties
> > are
> > > > > probably
> > > > > > > > not directly inferrable from those of the multiplexing
> > termination.
> > > > > > > >
> > > > > > > > Tom Taylor
> > > > > > > > taylor@nortelnetworks.com
> > > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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


From daemon@optimus.ietf.org  Wed Jan 23 12:38:25 2002
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 MAA17738
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 12:38:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA07352
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 12:38:28 -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 MAA06640;
	Wed, 23 Jan 2002 12:29:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06605
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 12:29:00 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17362
	for <megaco@ietf.org>; Wed, 23 Jan 2002 12:28:50 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0NHShw09721;
	Wed, 23 Jan 2002 18:28:43 +0100 (MET)
Received: from lmf.ericsson.se (lmf05397pc.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0NHSfr6029128;
	Wed, 23 Jan 2002 19:28:41 +0200 (EET)
Message-ID: <3C4EF2C8.CFABC3F1@lmf.ericsson.se>
Date: Wed, 23 Jan 2002 19:28:40 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Christian Groves <Christian.Groves@ericsson.com.au>,
        Clifford Sayre <clsayre@lucent.com>, megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
References: <4D79C746863DD51197690002A52CDA000102AED8@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>Those multiplex properties you're talking about are a global characteristic
>of H.324 systems.  It makes good sense to put them into TerminationState
>because they describe transport on the exterior side, not the context side
>of the termination.

I would say that properties related to the LCNs describe transport on
the context side, since they specify mappings to streams within the
Context. So, those kind of parameters should maybe (no matter if the
multiplexing is handled by the TDM termination or a specific
Multiplexing Termination) be defined in LocalControl, after all. We
should remember that LCN-to-Stream mapping is not a global
characteristic - they are specific for each stream.
 
>I don't have time to follow through on this today, but perhaps I'll tackle a
>complete description of the H.324 application when I have an idle moment.

Thanks!

Regards,

Christer Holmberg
Ericsson Finland

> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Wednesday, January 23, 2002 8:25 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: Christian Groves; Clifford Sayre; megaco ietf
> Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> 
> Hi,
> 
> >The LCNs are specific to one application, not a general multiplexing issue.
> >(Although I suppose a similar issue arises with H.320, I also think H.320
> >would need its own annex.)  I think the mapping has to be described in
> Annex
> >M.4 for H.324.
> 
> As long as it's somewhere :)
> 
> >The most obvious solution is as Christer indicated: an LCN property in
> LocalControl.
> 
> Actually, I am not sure LocalControl is the correct place. Annex M.4
> specifies the multiplex properties in the TerminationState descriptor,
> so this information could be there. Note that Annex M.4 does not use a
> Multiplex Termination (the multiplexing is done in the TDM termination),
> and there are no stream descriptors defined for the LCNs. IF a
> Multiplexing Termination is used, according to the H.248 core spec,
> separate stream descriptor shall be defined for each LCN, and in that
> case it could be a property in LocalControl.
> 
> Also, is there a specific reason why the H245 Message event, defined in
> the H.245 Package (M4.5) can't be used for the H.245 backhauling???
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Tuesday, January 22, 2002 2:35 AM
> > To: Christian Groves
> > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> >
> > Hi,
> >
> > >I don't think we can remove the whole chapter from the protocol at this
> > >stage. I agree with Tom that we can do some call flows in a seperate
> > >annex.
> >
> > Oki.
> >
> > >I'll add some text on the euphemeral terminations to the proposed
> > clarification.
> >
> > So, we shouldn't say anything about the Stream Descriptors in the Mux
> > Termination? How they are mapped to the LCNs etc? Personally I don't
> > care if it's said in the core spec, or in a separate Annex, but I don't
> > understand what the purpose is to put stuff in the core which nobody can
> > use :)
> >
> > Does anyone know if there has been any response on this issue from SG16?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > >
> > > Regards, Christian
> > >
> > > Christer Holmberg wrote:
> > > >
> > > > Hi,
> > > >
> > > > >While we're on the topic of Annex M.4, I realized while reading it
> that
> > it
> > > > >improperly (I think) includes some control terminations in the
> > multiplex.
> > > > >This may be water under the bridge now -- too late to do anything
> about
> > it.
> > > > >
> > > > >Anyway, Christer is asking for more than I would put into the core
> > protocol
> > > > >specification.  We should probably create an Informational RFC
> > describing
> > > > >multiplex use with examples, just as we should publish an
> Informational
> > RFC
> > > > >giving example call flows.
> > > >
> > > > Why not removing the whole multiplex chapter from the core protocol,
> > > > then, and putting it in a separate Annex, or something? The way it's
> > > > defined now (even by adding the proposed changes) doesn't help anyone.
> > > > You simply can't implement multiplexing with the info you get from
> that
> > > > text (you don't know how to map the LCNs, which btw also are
> > > > uni-dirctional, to specific terminations etc etc) - and that's NOT
> > > > enough in my opinion.
> > > >
> > > > I thought that the ITU people always wanted to specify everything very
> > > > much in detail :)
> > > >
> > > > Regards,
> > > >
> > > > Christer Holmberg
> > > > Ericsson Finland
> > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > > > Sent: Monday, January 21, 2002 12:52 AM
> > > > > To: Christian Groves
> > > > > Cc: Taylor, Tom-PT [CAR:B800:EXCH]; Clifford Sayre; megaco ietf
> > > > > Subject: Re: [Megaco] Clarification Of Multiplex Descriptor Text
> > > > >
> > > > > Hi,
> > > > >
> > > > > >I think that the H.324 package probably needs to be updated to say
> > how
> > > > > >this is done. I don't think its a core H.248 issue.
> > > > >
> > > > > I agree. The idea was that this property would be defined in the
> H.324
> > > > > package, and then used within each stream descriptor in the Mux
> > > > > Termination.
> > > > >
> > > > > >Perhaps an IG note could be added for the H324 package? I'd like to
> > see a
> > > > > reply from the
> > > > > > H324 package authors on how they thought this was to be done.
> > > > >
> > > > > >Are there any updates you'd like to see to proposed text on
> > > > > MultiplexDescriptors that Tom posted?
> > > > >
> > > > > First, as Tom already mentioned, it should be updated so that it
> also
> > > > > includes emphemeral bearer terminations (RTP terminations, for
> > example).
> > > > >
> > > > > Second, it should in detail, on a message level, describe how the
> > > > > multiplexed connection is set up. Now it only says "use a stream
> > > > > descriptor" - which means everyone is going to understand it their
> own
> > > > > way, and we are going to have lots of interop problems when people
> > start
> > > > > implementing this :)
> > > > >
> > > > > Third, it should also describe in detail how the H.223 (or whatever
> > > > > multiplex method is used) descriptor is used, ie which terminations
> > are
> > > > > included etc, depending on on which "side" of the multiplexer the
> > > > > terminations are.
> > > > >
> > > > > Fourth, I think the whole Annex M.4 misses some things, but that's
> > > > > another discussion...
> > > > >
> > > > > I understand if you want to get this document ready before february,
> > but
> > > > > please let us do this correct from the beginning :)
> > > > >
> > > > > Regards,
> > > > >
> > > > > Christer Holmberg
> > > > > Ericsson Finland
> > > > >
> > > > > >
> > > > > > Regards, Christian
> > > > > >
> > > > > > Christer Holmberg wrote:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have read the document a few times, but even by having stream
> > > > > > > descriptors in the mux termination, I still don't understand how
> > each of
> > > > > > > those stream descriptors are mapped to specific LNCs. Is the
> > StreamID
> > > > > > > supposed to be the same as the LCN number, or how is the mapping
> > done?
> > > > > > >
> > > > > > > A very simple solution would be to add a "LCN property" (to the
> > H.324
> > > > > > > package, I assume) which would be used in the each stream
> > descriptor to
> > > > > > > specify to which LCN it is mapped.
> > > > > > >
> > > > > > > Comments?
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Christer Holmberg
> > > > > > > Ericsson Finland
> > > > > > >
> > > > > > > Tom-PT Taylor wrote:
> > > > > > > >
> > > > > > > > I mentioned that several of us have been discussing additional
> > text
> > > > > for
> > > > > > > > Multiplex Descriptors.  I have placed the proposed text as
> > marked up
> > > > > changes
> > > > > > > > in the Megaco FTP site.  According to your taste, you can
> > download
> > > > > > > >
> > > > >
> >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > > x64K.doc
> > > > > > > > or
> > > > > > > >
> > > > >
> >
> ftp://standards.nortelnetworks.com/megaco/docs/Current/MuxDescription_with_N
> > > > > > > > x64K.pdf
> > > > > > > >
> > > > > > > > Based on my reply to Christer Holm yesterday (see "LCN
> > Mapping"), this
> > > > > > > > proposed text needs a further update.  The supporting bearers
> > > > > contained by a
> > > > > > > > multiplexing termination can be ephemeral as well as physical.
> > > > > However, I
> > > > > > > > believe it would be essential that any ephemrals mentioned in
> a
> > MUX
> > > > > > > > descriptor already exist in the context, since their
> properties
> > are
> > > > > probably
> > > > > > > > not directly inferrable from those of the multiplexing
> > termination.
> > > > > > > >
> > > > > > > > Tom Taylor
> > > > > > > > taylor@nortelnetworks.com
> > > > > > > > Ph. +1 613 736 0961 (ESN 396 1490)
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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



From megaco-admin@ietf.org  Wed Jan 23 12:55:43 2002
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 MAA18378
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 12:55:43 -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 MAA07519;
	Wed, 23 Jan 2002 12:42:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07490
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 12:42:04 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17869
	for <megaco@ietf.org>; Wed, 23 Jan 2002 12:42:03 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NHfXZ19644;
	Wed, 23 Jan 2002 12:41:33 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id MAA07235;
	Wed, 23 Jan 2002 12:41:30 -0500 (EST)
Message-ID: <3C4EF510.8D99EC73@lucent.com>
Date: Wed, 23 Jan 2002 12:38:24 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Troy Cauble <troy@bell-labs.com>
CC: Raphael Tryster <raphael@tdsoft.com>, megaco@ietf.org
Subject: Re: [Megaco] Open Issue #5: misleading ABNF comment on stream 
 descriptor?
References: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange> <3C4ED8FB.9C9B5100@bell-labs.com>
Content-Type: multipart/mixed;
 boundary="------------EC87BA6825CA70FE3EC38AB5"
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

This is a multi-part message in MIME format.
--------------EC87BA6825CA70FE3EC38AB5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I agree that Troy's statement is correct.  This was the intent of IG 6.75 but the
change did not completely fix the interpretation.  I believe Troy's is better.
Unless I hear an objection I will add this to the IG.

Isn't there also a problem with the comment above streamParm?
; at-most-once
shouldn't it be
;at-most-once per item
we need the possibility of all three Descriptors.



Troy Cauble wrote:

> I agree that the ABNF comment is incorrect.
>
> It should be
>
>         ; at-most-one terminationStateDescriptor
>         ; and either streamParm(s) or streamDescriptor(s) but not both
>
> -troy
>
> > Raphael Tryster wrote:
> >
> > The previous posting came out garbled.
> >
> >      Here is something from the archive which was never answered.  I think
> >      the answer to Steven's question is that section 7.1.4 is right and the
> >      comment in the ABNF is wrong, as the ASN sp; Will the comment in the
> >      ABNF be changed?
> >
> >      Raphael Tryster
> >
> >      From: Steven Weisz <sweisz@mediatrix.com>
> >      To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
> >      Subject: Clarification on Media Descriptor needed.
> >      Date: Tue, 24 Apr 2001 13:32:09 -0400
> >      MIME-Version: 1.0
> >      X-Mailer: Internet Mail Service (5.5 Content-Type: text/plain;
> >              charset="iso-8859-1"
> >      Sender: owner-megaco@pit.comms.marconi.com
> >      Precedence: bulk
> >
> >      Hi List,
> >
> >      I need some clarification regarding the Media Descriptor. Specifically
> >      in
> >      section 7.1.4, paragraph 1 the protocol states:
> >
> >        "The Media Descriptor specifies the parameters for all the media
> >         streams.  These parameters are structured into two descriptors, a
> >         Termination State Descriptor, which specifies the properties of a
> >         termination that are not stream dependent, and one or more Stream
> >         Descriptors each of which describes a single media stream."
> >
> >      This states that a Media Descriptor has one or more Stream Descriptors
> >      associated with it. However, in the ABNF we have:
> >
> >        "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
> >                              RBRKT
> >
> >         ; at-most-once per item
> >         ; and either streamParm or streamDescriptor but not both
> >         mediaParm            = (streamParm / streamDescriptor /
> >                                 terminationStateDescriptor)"
> >
> >      Which to me seems to say that we have only one Stream Descriptor
> >      associated
> >      with it (as indicated by the comment "; at-most-once per item".
> >
> >      Am I interpreting the ABNF correctly?
> >
> >      thanks,
> >
> >      Steven Weisz
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------EC87BA6825CA70FE3EC38AB5
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------EC87BA6825CA70FE3EC38AB5--


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


From daemon@optimus.ietf.org  Wed Jan 23 12:55:43 2002
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 MAA18389
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 12:55:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA07971
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 12:55:44 -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 MAA07519;
	Wed, 23 Jan 2002 12:42:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07490
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 12:42:04 -0500 (EST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17869
	for <megaco@ietf.org>; Wed, 23 Jan 2002 12:42:03 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NHfXZ19644;
	Wed, 23 Jan 2002 12:41:33 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id MAA07235;
	Wed, 23 Jan 2002 12:41:30 -0500 (EST)
Message-ID: <3C4EF510.8D99EC73@lucent.com>
Date: Wed, 23 Jan 2002 12:38:24 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Troy Cauble <troy@bell-labs.com>
CC: Raphael Tryster <raphael@tdsoft.com>, megaco@ietf.org
Subject: Re: [Megaco] Open Issue #5: misleading ABNF comment on stream 
 descriptor?
References: <B1584457374ED211B7A90008C7242DEF0189CFC1@Exchange> <3C4ED8FB.9C9B5100@bell-labs.com>
Content-Type: multipart/mixed;
 boundary="------------EC87BA6825CA70FE3EC38AB5"
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

This is a multi-part message in MIME format.
--------------EC87BA6825CA70FE3EC38AB5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I agree that Troy's statement is correct.  This was the intent of IG 6.75 but the
change did not completely fix the interpretation.  I believe Troy's is better.
Unless I hear an objection I will add this to the IG.

Isn't there also a problem with the comment above streamParm?
; at-most-once
shouldn't it be
;at-most-once per item
we need the possibility of all three Descriptors.



Troy Cauble wrote:

> I agree that the ABNF comment is incorrect.
>
> It should be
>
>         ; at-most-one terminationStateDescriptor
>         ; and either streamParm(s) or streamDescriptor(s) but not both
>
> -troy
>
> > Raphael Tryster wrote:
> >
> > The previous posting came out garbled.
> >
> >      Here is something from the archive which was never answered.  I think
> >      the answer to Steven's question is that section 7.1.4 is right and the
> >      comment in the ABNF is wrong, as the ASN sp; Will the comment in the
> >      ABNF be changed?
> >
> >      Raphael Tryster
> >
> >      From: Steven Weisz <sweisz@mediatrix.com>
> >      To: "Megaco Mailing List (E-mail)" <megaco@fore.com>
> >      Subject: Clarification on Media Descriptor needed.
> >      Date: Tue, 24 Apr 2001 13:32:09 -0400
> >      MIME-Version: 1.0
> >      X-Mailer: Internet Mail Service (5.5 Content-Type: text/plain;
> >              charset="iso-8859-1"
> >      Sender: owner-megaco@pit.comms.marconi.com
> >      Precedence: bulk
> >
> >      Hi List,
> >
> >      I need some clarification regarding the Media Descriptor. Specifically
> >      in
> >      section 7.1.4, paragraph 1 the protocol states:
> >
> >        "The Media Descriptor specifies the parameters for all the media
> >         streams.  These parameters are structured into two descriptors, a
> >         Termination State Descriptor, which specifies the properties of a
> >         termination that are not stream dependent, and one or more Stream
> >         Descriptors each of which describes a single media stream."
> >
> >      This states that a Media Descriptor has one or more Stream Descriptors
> >      associated with it. However, in the ABNF we have:
> >
> >        "mediaDescriptor = MediaToken LBRKT mediaParm *(COMMA mediaParm)
> >                              RBRKT
> >
> >         ; at-most-once per item
> >         ; and either streamParm or streamDescriptor but not both
> >         mediaParm            = (streamParm / streamDescriptor /
> >                                 terminationStateDescriptor)"
> >
> >      Which to me seems to say that we have only one Stream Descriptor
> >      associated
> >      with it (as indicated by the comment "; at-most-once per item".
> >
> >      Am I interpreting the ABNF correctly?
> >
> >      thanks,
> >
> >      Steven Weisz
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------EC87BA6825CA70FE3EC38AB5
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------EC87BA6825CA70FE3EC38AB5--


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



From megaco-admin@ietf.org  Wed Jan 23 13:26:29 2002
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 NAA19424
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 13:26:25 -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 NAA09161;
	Wed, 23 Jan 2002 13:10:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA09138
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 13:10:50 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18930
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:10:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NIAEd04419;
	Wed, 23 Jan 2002 13:10:15 -0500 (EST)
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 g0NIADV00052;
	Wed, 23 Jan 2002 13:10:13 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZ2FT>; Wed, 23 Jan 2002 13:10:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEE7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        Megaco Mailing List
	 <megaco@ietf.org>
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	Transaction Reply.
Date: Wed, 23 Jan 2002 13:10:13 -0500
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

I half-prepared a reply on this issue back when it was first raised, but
didn't get around to finishing it.  The real issue is what to do when there
has been an unrecognizable command.  If you follow through the ABNF all
other cases are covered, because auditReturnParameter includes
errorDescriptor as one of its alternatives.

I'd suggest an ABNF correction of the form:

actionReply = CtxToken EQUAL ContextID LBRKT
             1*( errorDescriptor / commandReply ) RBRKT

with a comment that multiple errorDescriptors would be allowed only if all
except the last pertained to commands that had the "O-" (optional) prefix.


-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 11:37 AM
To: Megaco Mailing List
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
Transaction Reply.


I'm copying the list (and designating it as open issue #4) since it has
become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the
ABNF
since commandReply there is a comma separated list, but it does NOT allow
both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a
list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


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


From daemon@optimus.ietf.org  Wed Jan 23 13:26:30 2002
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 NAA19431
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 13:26:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA09885
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 13:26:31 -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 NAA09161;
	Wed, 23 Jan 2002 13:10:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA09138
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 13:10:50 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18930
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:10:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NIAEd04419;
	Wed, 23 Jan 2002 13:10:15 -0500 (EST)
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 g0NIADV00052;
	Wed, 23 Jan 2002 13:10:13 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZ2FT>; Wed, 23 Jan 2002 13:10:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEE7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        Megaco Mailing List
	 <megaco@ietf.org>
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	Transaction Reply.
Date: Wed, 23 Jan 2002 13:10:13 -0500
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

I half-prepared a reply on this issue back when it was first raised, but
didn't get around to finishing it.  The real issue is what to do when there
has been an unrecognizable command.  If you follow through the ABNF all
other cases are covered, because auditReturnParameter includes
errorDescriptor as one of its alternatives.

I'd suggest an ABNF correction of the form:

actionReply = CtxToken EQUAL ContextID LBRKT
             1*( errorDescriptor / commandReply ) RBRKT

with a comment that multiple errorDescriptors would be allowed only if all
except the last pertained to commands that had the "O-" (optional) prefix.


-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 11:37 AM
To: Megaco Mailing List
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
Transaction Reply.


I'm copying the list (and designating it as open issue #4) since it has
become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the
ABNF
since commandReply there is a comma separated list, but it does NOT allow
both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a
list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


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



From megaco-admin@ietf.org  Wed Jan 23 14:11:26 2002
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 OAA21052
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:11:21 -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 NAA11658;
	Wed, 23 Jan 2002 13:57:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11631
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 13:57:23 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20578
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:57:20 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NIvKx23592
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:57:20 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id NAA23188; Wed, 23 Jan 2002 13:57:16 -0500 (EST)
Cc: Megaco Mailing List <megaco@ietf.org>
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id NAA23169; Wed, 23 Jan 2002 13:57:15 -0500 (EST)
Message-ID: <3C4F06E3.DA930453@bell-labs.com>
Date: Wed, 23 Jan 2002 13:54:27 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
Original-CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com> <3C4EE692.D477AFDF@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Terry L Anderson wrote:
> 
> I'm copying the list (and designating it as open issue #4) since it has become
> an IG issue.  See below.
> 
> Christian Groves wrote:
> 
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
> 
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
> since commandReply there is a comma separated list, but it does NOT allow both
> commandReply AND errorDescriptor as the ASN.1 does.
> 
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> done this and it would solve the problem of no way to return replies for the
> successes along with the error.

Question:  Are we sure the ASN.1 is more correct than the ABNF?

I believe there are many either/or choices in the ABNF that were
spec'ed less specifically as as OPTIONALs in ASN.1.  I'm guessing
this was either laziness or the desire to not nest the ASN.1 even 
deeper.


> 
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT

What is the precedence between '/' and 'COMMA' ?

You should spec either

                         ( ( errorDescriptor / commandReply /
                             commandReply ) COMMA errorDescriptor ) RBRKT

                         ( errorDescriptor / commandReply /
                             ( commandReply COMMA errorDescriptor ) ) RBRKT

-troy

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


From daemon@optimus.ietf.org  Wed Jan 23 14:11:26 2002
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 OAA21062
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:11:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA12686
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 14:11:28 -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 NAA11658;
	Wed, 23 Jan 2002 13:57:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11631
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 13:57:23 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20578
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:57:20 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NIvKx23592
	for <megaco@ietf.org>; Wed, 23 Jan 2002 13:57:20 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id NAA23188; Wed, 23 Jan 2002 13:57:16 -0500 (EST)
Cc: Megaco Mailing List <megaco@ietf.org>
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id NAA23169; Wed, 23 Jan 2002 13:57:15 -0500 (EST)
Message-ID: <3C4F06E3.DA930453@bell-labs.com>
Date: Wed, 23 Jan 2002 13:54:27 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
Original-CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com> <3C4EE692.D477AFDF@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Terry L Anderson wrote:
> 
> I'm copying the list (and designating it as open issue #4) since it has become
> an IG issue.  See below.
> 
> Christian Groves wrote:
> 
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
> 
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
> since commandReply there is a comma separated list, but it does NOT allow both
> commandReply AND errorDescriptor as the ASN.1 does.
> 
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> done this and it would solve the problem of no way to return replies for the
> successes along with the error.

Question:  Are we sure the ASN.1 is more correct than the ABNF?

I believe there are many either/or choices in the ABNF that were
spec'ed less specifically as as OPTIONALs in ASN.1.  I'm guessing
this was either laziness or the desire to not nest the ASN.1 even 
deeper.


> 
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT

What is the precedence between '/' and 'COMMA' ?

You should spec either

                         ( ( errorDescriptor / commandReply /
                             commandReply ) COMMA errorDescriptor ) RBRKT

                         ( errorDescriptor / commandReply /
                             ( commandReply COMMA errorDescriptor ) ) RBRKT

-troy

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



From megaco-admin@ietf.org  Wed Jan 23 14:53:30 2002
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 OAA22589
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:53:30 -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 OAA13754;
	Wed, 23 Jan 2002 14:38:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13655
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:38:06 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21936
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:38:03 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NJbXh06733;
	Wed, 23 Jan 2002 14:37:34 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA11936;
	Wed, 23 Jan 2002 14:37:33 -0500 (EST)
Message-ID: <3C4F1042.BE575D9D@lucent.com>
Date: Wed, 23 Jan 2002 14:34:26 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <4D79C746863DD51197690002A52CDA000102AEE7@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------A25728544C2B8FF4CD61832E"
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

This is a multi-part message in MIME format.
--------------A25728544C2B8FF4CD61832E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think my change is more focused.  We do not need multiple commandReply
instances since it is already a comma separated list.  If we support multiple
errorDescriptor instances we would need to change ASN.1 too, since it does NOT.

Also your change would need a separator (eg. COMMA) between instances.  If we
really want multiple instances of each it would be easier to add errorDescriptor
to commandReplys so they could appear in the commandReplyList which already has
the separator.  But again this would introduce a new difference from ASN.1

I think simply matching the ASN.1 (as I tried to do) takes care of the one need.

Tom-PT Taylor wrote:

> I half-prepared a reply on this issue back when it was first raised, but
> didn't get around to finishing it.  The real issue is what to do when there
> has been an unrecognizable command.  If you follow through the ABNF all
> other cases are covered, because auditReturnParameter includes
> errorDescriptor as one of its alternatives.
>
> I'd suggest an ABNF correction of the form:
>
> actionReply = CtxToken EQUAL ContextID LBRKT
>              1*( errorDescriptor / commandReply ) RBRKT
>
> with a comment that multiple errorDescriptors would be allowed only if all
> except the last pertained to commands that had the "O-" (optional) prefix.
>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Wednesday, January 23, 2002 11:37 AM
> To: Megaco Mailing List
> Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
> Transaction Reply.
>
> I'm copying the list (and designating it as open issue #4) since it has
> become
> an IG issue.  See below.
>
> Christian Groves wrote:
>
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
>
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the
> ABNF
> since commandReply there is a comma separated list, but it does NOT allow
> both
> commandReply AND errorDescriptor as the ASN.1 does.
>
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> done this and it would solve the problem of no way to return replies for the
> successes along with the error.
>
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT
>
> The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
> would be clearer if errorDescriptor came after commandReply (which is a
> list),
> so I am suggesting the order above for ABNF where the error looks more like
> part of the reply sequence.
>
> > So in the case Sundar talks about you would send an error for "Syntax
> > error in action" and also return the commandReply for the command that
> > the MG processed.
> >
> > With regards to 6.84, "last action REPLY" does make things clearer but I
> > don't think other changes are needed.
>
> you don't think the other changes IN 6.84 are needed or other changes TO
> 6.84???
>
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > ErrorDescriptor is available at several levels in a reply including
> > > action and most command. Discussion of where the errorDescriptor should
> > > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> > >
> > > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > > the actionReply.  I guess I would argue that this is NOT a legal action,
> > > since it contains an unknown command.
> > >
> > > The next sentence deals with a special case where the end of an action
> > > cannot be determined, but this is not really the case here.  IG 6.84
> > > modified this sentence to refer to the case where one or more COMMANDS
> > > in the action can be parsed, and so it might be tempting to follow this
> > > case, but on reading it, I think the change is wrong.
> > >
> > > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > > you turned it over to me, and was suggested by Paul Long, but I do not
> > > see how it works.  The rest of the sentence still refers to Action ("422
> > > syntax Error in ACTION as the last ACTION for the transaction" - I
> > > believe it should be "last action REPLY for").  I believe that it WAS
> > > intended to say "Action" as it did before 6.84, and only means that if
> > > other PRECEDING Actions in the transaction before the one with
> > > failed-end-parse should be processed but the entire failed Action must
> > > result in an actionReply of ErrorDescriptor.  As modified the processed
> > > Commands cannot return replies because of the action reply containing
> > > the error.
> > >
> > > There are two cases if a command cannot be parsed.  (1) If the command
> > > type can be determined but there is a parse failure inside (eg, Add,
> > > Move, Modify, Subtract), then we have the valid command token and can
> > > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > > for audit, notify, and serviceChangeRequest.
> > >
> > > (2) parse (as above) fails without a valid command type.  Here we have
> > > no command token to use in any of the *Reply and there is no
> > > errorDescriptor in commandReplys, so one is forced to use the one in
> > > actionReply and fail the entire action.  It would have been nice to have
> > > errorDescriptor in commandReplys to take care of this case.
> > >
> > > Except for this last case one could fix the IG6.84 item by changing the
> > > other instance of "Action" to command as well ('in the last command
> > > reply'), but perhaps this should be stated for both the action and
> > > command level.
> > >
> > > Sundareswaram P V wrote:
> > >
> > > > Hi,     cud u help in having a solution for the same. The following is
> > > > the Query.  consider the example message below. MEGACO/1
> > > > [125.125.125.111]:55555
> > > > Transaction = 50009 {
> > > >    Context = 5000 {
> > > >       Subtract = A5555 {
> > > >          Statistics {
> > > >             ........
> > > >          }
> > > >        },
> > > >        abc = A5556 {                    // --- Command request type is
> > > > Corrupted                    // instead of subtract it become 'abc'
> > > >                Statistics {
> > > >                   ......
> > > >                     nt/os=62345, ; octets sent
> > > >                     rtp/pr=780, ; packets received
> > > >                     nt/or=45123, ; octets received
> > > >                }
> > > >            }
> > > >         }
> > > >      }     The problem is as follows :         In the same context we
> > > > have two commands. the first command get parsed well and will be
> > > > inserted in to the Action Request while in the second command, the
> > > > command type it self is corrupted. so how, do i form the ActionReply
> > > > :         as the RFC 3015 states :             action reply = CtxToken
> > > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > > Command Reply) RBRKT             but as such for an action request i
> > > > can send only one action reply. but the syntax above doesn't allow me
> > > > to set both an error descriptor and an command reply with in an action
> > > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > > advance. rgds,Sundar.
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson              mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------A25728544C2B8FF4CD61832E
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------A25728544C2B8FF4CD61832E--


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


From daemon@optimus.ietf.org  Wed Jan 23 14:53:31 2002
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 OAA22599
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:53:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14088
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 14:53:33 -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 OAA13754;
	Wed, 23 Jan 2002 14:38:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13655
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:38:06 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21936
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:38:03 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NJbXh06733;
	Wed, 23 Jan 2002 14:37:34 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA11936;
	Wed, 23 Jan 2002 14:37:33 -0500 (EST)
Message-ID: <3C4F1042.BE575D9D@lucent.com>
Date: Wed, 23 Jan 2002 14:34:26 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <4D79C746863DD51197690002A52CDA000102AEE7@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------A25728544C2B8FF4CD61832E"
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

This is a multi-part message in MIME format.
--------------A25728544C2B8FF4CD61832E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think my change is more focused.  We do not need multiple commandReply
instances since it is already a comma separated list.  If we support multiple
errorDescriptor instances we would need to change ASN.1 too, since it does NOT.

Also your change would need a separator (eg. COMMA) between instances.  If we
really want multiple instances of each it would be easier to add errorDescriptor
to commandReplys so they could appear in the commandReplyList which already has
the separator.  But again this would introduce a new difference from ASN.1

I think simply matching the ASN.1 (as I tried to do) takes care of the one need.

Tom-PT Taylor wrote:

> I half-prepared a reply on this issue back when it was first raised, but
> didn't get around to finishing it.  The real issue is what to do when there
> has been an unrecognizable command.  If you follow through the ABNF all
> other cases are covered, because auditReturnParameter includes
> errorDescriptor as one of its alternatives.
>
> I'd suggest an ABNF correction of the form:
>
> actionReply = CtxToken EQUAL ContextID LBRKT
>              1*( errorDescriptor / commandReply ) RBRKT
>
> with a comment that multiple errorDescriptors would be allowed only if all
> except the last pertained to commands that had the "O-" (optional) prefix.
>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Wednesday, January 23, 2002 11:37 AM
> To: Megaco Mailing List
> Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
> Transaction Reply.
>
> I'm copying the list (and designating it as open issue #4) since it has
> become
> an IG issue.  See below.
>
> Christian Groves wrote:
>
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
>
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the
> ABNF
> since commandReply there is a comma separated list, but it does NOT allow
> both
> commandReply AND errorDescriptor as the ASN.1 does.
>
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> done this and it would solve the problem of no way to return replies for the
> successes along with the error.
>
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT
>
> The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
> would be clearer if errorDescriptor came after commandReply (which is a
> list),
> so I am suggesting the order above for ABNF where the error looks more like
> part of the reply sequence.
>
> > So in the case Sundar talks about you would send an error for "Syntax
> > error in action" and also return the commandReply for the command that
> > the MG processed.
> >
> > With regards to 6.84, "last action REPLY" does make things clearer but I
> > don't think other changes are needed.
>
> you don't think the other changes IN 6.84 are needed or other changes TO
> 6.84???
>
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > ErrorDescriptor is available at several levels in a reply including
> > > action and most command. Discussion of where the errorDescriptor should
> > > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> > >
> > > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > > the actionReply.  I guess I would argue that this is NOT a legal action,
> > > since it contains an unknown command.
> > >
> > > The next sentence deals with a special case where the end of an action
> > > cannot be determined, but this is not really the case here.  IG 6.84
> > > modified this sentence to refer to the case where one or more COMMANDS
> > > in the action can be parsed, and so it might be tempting to follow this
> > > case, but on reading it, I think the change is wrong.
> > >
> > > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > > you turned it over to me, and was suggested by Paul Long, but I do not
> > > see how it works.  The rest of the sentence still refers to Action ("422
> > > syntax Error in ACTION as the last ACTION for the transaction" - I
> > > believe it should be "last action REPLY for").  I believe that it WAS
> > > intended to say "Action" as it did before 6.84, and only means that if
> > > other PRECEDING Actions in the transaction before the one with
> > > failed-end-parse should be processed but the entire failed Action must
> > > result in an actionReply of ErrorDescriptor.  As modified the processed
> > > Commands cannot return replies because of the action reply containing
> > > the error.
> > >
> > > There are two cases if a command cannot be parsed.  (1) If the command
> > > type can be determined but there is a parse failure inside (eg, Add,
> > > Move, Modify, Subtract), then we have the valid command token and can
> > > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > > for audit, notify, and serviceChangeRequest.
> > >
> > > (2) parse (as above) fails without a valid command type.  Here we have
> > > no command token to use in any of the *Reply and there is no
> > > errorDescriptor in commandReplys, so one is forced to use the one in
> > > actionReply and fail the entire action.  It would have been nice to have
> > > errorDescriptor in commandReplys to take care of this case.
> > >
> > > Except for this last case one could fix the IG6.84 item by changing the
> > > other instance of "Action" to command as well ('in the last command
> > > reply'), but perhaps this should be stated for both the action and
> > > command level.
> > >
> > > Sundareswaram P V wrote:
> > >
> > > > Hi,     cud u help in having a solution for the same. The following is
> > > > the Query.  consider the example message below. MEGACO/1
> > > > [125.125.125.111]:55555
> > > > Transaction = 50009 {
> > > >    Context = 5000 {
> > > >       Subtract = A5555 {
> > > >          Statistics {
> > > >             ........
> > > >          }
> > > >        },
> > > >        abc = A5556 {                    // --- Command request type is
> > > > Corrupted                    // instead of subtract it become 'abc'
> > > >                Statistics {
> > > >                   ......
> > > >                     nt/os=62345, ; octets sent
> > > >                     rtp/pr=780, ; packets received
> > > >                     nt/or=45123, ; octets received
> > > >                }
> > > >            }
> > > >         }
> > > >      }     The problem is as follows :         In the same context we
> > > > have two commands. the first command get parsed well and will be
> > > > inserted in to the Action Request while in the second command, the
> > > > command type it self is corrupted. so how, do i form the ActionReply
> > > > :         as the RFC 3015 states :             action reply = CtxToken
> > > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > > Command Reply) RBRKT             but as such for an action request i
> > > > can send only one action reply. but the syntax above doesn't allow me
> > > > to set both an error descriptor and an command reply with in an action
> > > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > > advance. rgds,Sundar.
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson              mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------A25728544C2B8FF4CD61832E
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------A25728544C2B8FF4CD61832E--


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



From megaco-admin@ietf.org  Wed Jan 23 14:56:17 2002
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 OAA22702
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:56: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 OAA13934;
	Wed, 23 Jan 2002 14:47:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13905
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:47:22 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22360
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:47:19 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJkWd29278;
	Wed, 23 Jan 2002 14:46:32 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJkTn16928;
	Wed, 23 Jan 2002 14:46:30 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZLBV>; Wed, 23 Jan 2002 14:46:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEE9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Cc: "'Troy Cauble'" <troy@bell-labs.com>, Terry L Anderson <tla@lucent.com>
Subject: FW: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	 Transaction Reply.
Date: Wed, 23 Jan 2002 14:46:31 -0500
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

Reading Troy's note on the subject reminded me of the COMMAs I missed from
my proposal.  I amend that proposal to say

actionReply = CtxToken EQUAL ContextID LBRKT
           ( errorDescriptor / commandReply )  
          *( COMMA (errorDescriptor / commandReply) ) RBRKT
          ; errorDescriptor can occur more than once only if all instances
but the
          ; last pertain to optional commands (i.e. prefixed by "O-")



-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Wednesday, January 23, 2002 1:10 PM
To: 'Terry L Anderson'; Megaco Mailing List
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error
in Transaction Reply.


I half-prepared a reply on this issue back when it was first raised, but
didn't get around to finishing it.  The real issue is what to do when there
has been an unrecognizable command.  If you follow through the ABNF all
other cases are covered, because auditReturnParameter includes
errorDescriptor as one of its alternatives.

I'd suggest an ABNF correction of the form:

actionReply = CtxToken EQUAL ContextID LBRKT
             1*( errorDescriptor / commandReply ) RBRKT

with a comment that multiple errorDescriptors would be allowed only if all
except the last pertained to commands that had the "O-" (optional) prefix.


-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 11:37 AM
To: Megaco Mailing List
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
Transaction Reply.


I'm copying the list (and designating it as open issue #4) since it has
become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the
ABNF
since commandReply there is a comma separated list, but it does NOT allow
both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a
list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 23 14:56:18 2002
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 OAA22711
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:56:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14329
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 14:56:19 -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 OAA13934;
	Wed, 23 Jan 2002 14:47:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13905
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:47:22 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22360
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:47:19 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJkWd29278;
	Wed, 23 Jan 2002 14:46:32 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJkTn16928;
	Wed, 23 Jan 2002 14:46:30 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZLBV>; Wed, 23 Jan 2002 14:46:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEE9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Cc: "'Troy Cauble'" <troy@bell-labs.com>, Terry L Anderson <tla@lucent.com>
Subject: FW: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	 Transaction Reply.
Date: Wed, 23 Jan 2002 14:46:31 -0500
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

Reading Troy's note on the subject reminded me of the COMMAs I missed from
my proposal.  I amend that proposal to say

actionReply = CtxToken EQUAL ContextID LBRKT
           ( errorDescriptor / commandReply )  
          *( COMMA (errorDescriptor / commandReply) ) RBRKT
          ; errorDescriptor can occur more than once only if all instances
but the
          ; last pertain to optional commands (i.e. prefixed by "O-")



-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Wednesday, January 23, 2002 1:10 PM
To: 'Terry L Anderson'; Megaco Mailing List
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error
in Transaction Reply.


I half-prepared a reply on this issue back when it was first raised, but
didn't get around to finishing it.  The real issue is what to do when there
has been an unrecognizable command.  If you follow through the ABNF all
other cases are covered, because auditReturnParameter includes
errorDescriptor as one of its alternatives.

I'd suggest an ABNF correction of the form:

actionReply = CtxToken EQUAL ContextID LBRKT
             1*( errorDescriptor / commandReply ) RBRKT

with a comment that multiple errorDescriptors would be allowed only if all
except the last pertained to commands that had the "O-" (optional) prefix.


-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 11:37 AM
To: Megaco Mailing List
Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
Transaction Reply.


I'm copying the list (and designating it as open issue #4) since it has
become
an IG issue.  See below.

Christian Groves wrote:

> G'Day Terry and Sundar,
>
> The binary coding allows you to send an ErrorDescriptor and a sequence
> of commandReplies.
>
> ActionReply ::= SEQUENCE
> {
>         contextId               ContextID,
>         errorDescriptor ErrorDescriptor OPTIONAL,
>         contextReply    ContextRequest OPTIONAL,
>         commandReply    SEQUENCE OF CommandReply
> }

Oh, I hadn't noticed the difference.  The sequence is also allowed in the
ABNF
since commandReply there is a comma separated list, but it does NOT allow
both
commandReply AND errorDescriptor as the ASN.1 does.

Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
done this and it would solve the problem of no way to return replies for the
successes along with the error.

The change making it most like the ASN.1 would be:
actionReply    = CtxToken EQUAL ContextID LBRKT
                        ( errorDescriptor / commandReply /
                            commandReply COMMA errorDescriptor ) RBRKT

The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
would be clearer if errorDescriptor came after commandReply (which is a
list),
so I am suggesting the order above for ABNF where the error looks more like
part of the reply sequence.

> So in the case Sundar talks about you would send an error for "Syntax
> error in action" and also return the commandReply for the command that
> the MG processed.
>
> With regards to 6.84, "last action REPLY" does make things clearer but I
> don't think other changes are needed.

you don't think the other changes IN 6.84 are needed or other changes TO
6.84???

> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > ErrorDescriptor is available at several levels in a reply including
> > action and most command. Discussion of where the errorDescriptor should
> > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> >
> > 8.2.2 says that if MG cannot determine a legal action it returns 422 as
> > the actionReply.  I guess I would argue that this is NOT a legal action,
> > since it contains an unknown command.
> >
> > The next sentence deals with a special case where the end of an action
> > cannot be determined, but this is not really the case here.  IG 6.84
> > modified this sentence to refer to the case where one or more COMMANDS
> > in the action can be parsed, and so it might be tempting to follow this
> > case, but on reading it, I think the change is wrong.
> >
> > Christian, IG 6.84 was approved in Porto Seguro, one of the last before
> > you turned it over to me, and was suggested by Paul Long, but I do not
> > see how it works.  The rest of the sentence still refers to Action ("422
> > syntax Error in ACTION as the last ACTION for the transaction" - I
> > believe it should be "last action REPLY for").  I believe that it WAS
> > intended to say "Action" as it did before 6.84, and only means that if
> > other PRECEDING Actions in the transaction before the one with
> > failed-end-parse should be processed but the entire failed Action must
> > result in an actionReply of ErrorDescriptor.  As modified the processed
> > Commands cannot return replies because of the action reply containing
> > the error.
> >
> > There are two cases if a command cannot be parsed.  (1) If the command
> > type can be determined but there is a parse failure inside (eg, Add,
> > Move, Modify, Subtract), then we have the valid command token and can
> > use the errorDescriptor (in terminationAudit) in ammsReply and similarly
> > for audit, notify, and serviceChangeRequest.
> >
> > (2) parse (as above) fails without a valid command type.  Here we have
> > no command token to use in any of the *Reply and there is no
> > errorDescriptor in commandReplys, so one is forced to use the one in
> > actionReply and fail the entire action.  It would have been nice to have
> > errorDescriptor in commandReplys to take care of this case.
> >
> > Except for this last case one could fix the IG6.84 item by changing the
> > other instance of "Action" to command as well ('in the last command
> > reply'), but perhaps this should be stated for both the action and
> > command level.
> >
> > Sundareswaram P V wrote:
> >
> > > Hi,     cud u help in having a solution for the same. The following is
> > > the Query.  consider the example message below. MEGACO/1
> > > [125.125.125.111]:55555
> > > Transaction = 50009 {
> > >    Context = 5000 {
> > >       Subtract = A5555 {
> > >          Statistics {
> > >             ........
> > >          }
> > >        },
> > >        abc = A5556 {                    // --- Command request type is
> > > Corrupted                    // instead of subtract it become 'abc'
> > >                Statistics {
> > >                   ......
> > >                     nt/os=62345, ; octets sent
> > >                     rtp/pr=780, ; packets received
> > >                     nt/or=45123, ; octets received
> > >                }
> > >            }
> > >         }
> > >      }     The problem is as follows :         In the same context we
> > > have two commands. the first command get parsed well and will be
> > > inserted in to the Action Request while in the second command, the
> > > command type it self is corrupted. so how, do i form the ActionReply
> > > :         as the RFC 3015 states :             action reply = CtxToken
> > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > Command Reply) RBRKT             but as such for an action request i
> > > can send only one action reply. but the syntax above doesn't allow me
> > > to set both an error descriptor and an command reply with in an action
> > > reply.             cud any one help me resolve the issue  ??  thanx in
> > > advance. rgds,Sundar.
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson              mailto:tla@lucent.com
> > Tel:908.582.7013   Fax:908.582.6729
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 23 15:02:52 2002
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 PAA23018
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:02:52 -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 OAA14160;
	Wed, 23 Jan 2002 14:54:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14131
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:54:12 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22674
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:54:09 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NJreh13940
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:53:40 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA12762;
	Wed, 23 Jan 2002 14:53:38 -0500 (EST)
Message-ID: <3C4F1407.939A9733@lucent.com>
Date: Wed, 23 Jan 2002 14:50:31 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Troy Cauble <troy@bell-labs.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com> <3C4EE692.D477AFDF@lucent.com> <3C4F06E3.DA930453@bell-labs.com>
Content-Type: multipart/mixed;
 boundary="------------66D085856B7EBF9314750E50"
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

This is a multi-part message in MIME format.
--------------66D085856B7EBF9314750E50
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Troy Cauble wrote:

> Terry L Anderson wrote:
> >
> > I'm copying the list (and designating it as open issue #4) since it has become
> > an IG issue.  See below.
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry and Sundar,
> > >
> > > The binary coding allows you to send an ErrorDescriptor and a sequence
> > > of commandReplies.
> > >
> > > ActionReply ::= SEQUENCE
> > > {
> > >         contextId               ContextID,
> > >         errorDescriptor ErrorDescriptor OPTIONAL,
> > >         contextReply    ContextRequest OPTIONAL,
> > >         commandReply    SEQUENCE OF CommandReply
> > > }
> >
> > Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
> > since commandReply there is a comma separated list, but it does NOT allow both
> > commandReply AND errorDescriptor as the ASN.1 does.
> >
> > Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> > done this and it would solve the problem of no way to return replies for the
> > successes along with the error.
>
> Question:  Are we sure the ASN.1 is more correct than the ABNF?

That's why I put "correct" in quotes, but in this case it started by observing
required functionality to be missing in ABNF and discovering that ASN.1 did NOT have
the problem.  So I am not sure whether the "correct" form in ASN.1 was intentional
or accidental but it is what we need.

> I believe there are many either/or choices in the ABNF that were
> spec'ed less specifically as as OPTIONALs in ASN.1.  I'm guessing
> this was either laziness or the desire to not nest the ASN.1 even
> deeper.
>
> >
> > The change making it most like the ASN.1 would be:
> > actionReply    = CtxToken EQUAL ContextID LBRKT
> >                         ( errorDescriptor / commandReply /
> >                             commandReply COMMA errorDescriptor ) RBRKT
>
> What is the precedence between '/' and 'COMMA' ?
>
> You should spec either
>
>                          ( ( errorDescriptor / commandReply /
>                              commandReply ) COMMA errorDescriptor ) RBRKT
>
>                          ( errorDescriptor / commandReply /
>                              ( commandReply COMMA errorDescriptor ) ) RBRKT

I meant the later.  You are right, I need the extra ().

>
>
> -troy

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------66D085856B7EBF9314750E50
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------66D085856B7EBF9314750E50--


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


From daemon@optimus.ietf.org  Wed Jan 23 15:02:52 2002
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 PAA23028
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:02:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA14860
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 15:02:54 -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 OAA14160;
	Wed, 23 Jan 2002 14:54:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14131
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:54:12 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22674
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:54:09 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0NJreh13940
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:53:40 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA12762;
	Wed, 23 Jan 2002 14:53:38 -0500 (EST)
Message-ID: <3C4F1407.939A9733@lucent.com>
Date: Wed, 23 Jan 2002 14:50:31 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Troy Cauble <troy@bell-labs.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
 Transaction Reply.
References: <023d01c1a36d$78b11b00$554810ac@netbrahma.com> <3C4DC3E9.6F7FAE39@lucent.com> <3C4E29F0.B712A830@ericsson.com.au> <3C4EE2E7.8BE354B3@lucent.com> <3C4EE692.D477AFDF@lucent.com> <3C4F06E3.DA930453@bell-labs.com>
Content-Type: multipart/mixed;
 boundary="------------66D085856B7EBF9314750E50"
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

This is a multi-part message in MIME format.
--------------66D085856B7EBF9314750E50
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Troy Cauble wrote:

> Terry L Anderson wrote:
> >
> > I'm copying the list (and designating it as open issue #4) since it has become
> > an IG issue.  See below.
> >
> > Christian Groves wrote:
> >
> > > G'Day Terry and Sundar,
> > >
> > > The binary coding allows you to send an ErrorDescriptor and a sequence
> > > of commandReplies.
> > >
> > > ActionReply ::= SEQUENCE
> > > {
> > >         contextId               ContextID,
> > >         errorDescriptor ErrorDescriptor OPTIONAL,
> > >         contextReply    ContextRequest OPTIONAL,
> > >         commandReply    SEQUENCE OF CommandReply
> > > }
> >
> > Oh, I hadn't noticed the difference.  The sequence is also allowed in the ABNF
> > since commandReply there is a comma separated list, but it does NOT allow both
> > commandReply AND errorDescriptor as the ASN.1 does.
> >
> > Do you think we should "correct" the ABNF to agree with ASN.1.  We've often
> > done this and it would solve the problem of no way to return replies for the
> > successes along with the error.
>
> Question:  Are we sure the ASN.1 is more correct than the ABNF?

That's why I put "correct" in quotes, but in this case it started by observing
required functionality to be missing in ABNF and discovering that ASN.1 did NOT have
the problem.  So I am not sure whether the "correct" form in ASN.1 was intentional
or accidental but it is what we need.

> I believe there are many either/or choices in the ABNF that were
> spec'ed less specifically as as OPTIONALs in ASN.1.  I'm guessing
> this was either laziness or the desire to not nest the ASN.1 even
> deeper.
>
> >
> > The change making it most like the ASN.1 would be:
> > actionReply    = CtxToken EQUAL ContextID LBRKT
> >                         ( errorDescriptor / commandReply /
> >                             commandReply COMMA errorDescriptor ) RBRKT
>
> What is the precedence between '/' and 'COMMA' ?
>
> You should spec either
>
>                          ( ( errorDescriptor / commandReply /
>                              commandReply ) COMMA errorDescriptor ) RBRKT
>
>                          ( errorDescriptor / commandReply /
>                              ( commandReply COMMA errorDescriptor ) ) RBRKT

I meant the later.  You are right, I need the extra ().

>
>
> -troy

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------66D085856B7EBF9314750E50
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------66D085856B7EBF9314750E50--


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



From megaco-admin@ietf.org  Wed Jan 23 15:05:45 2002
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 PAA23098
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:05:45 -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 OAA14281;
	Wed, 23 Jan 2002 14:55:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14179
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:55:18 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22687
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:55:15 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJsid00374;
	Wed, 23 Jan 2002 14:54:44 -0500 (EST)
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 g0NJsgV06396;
	Wed, 23 Jan 2002 14:54:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZLJP>; Wed, 23 Jan 2002 14:54:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEEA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>
Cc: Megaco Mailing List <megaco@ietf.org>
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	 Transaction Reply.
Date: Wed, 23 Jan 2002 14:54:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A447.CC5DFEF0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A447.CC5DFEF0
Content-Type: text/plain;
	charset="ISO-8859-1"

I got this after dispatching my last note, and of course failed to read
Troy's very well.  I'm being terribly careless -- you're right about the
fact that commandReply is an aggregate itself.

So I buy your proposal and am prepared to ignore the case where there are
multiple "unknown command" errors with all but the last marked optional.  If
someone does that to the protocol, they deserve what they get.

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 2:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Megaco Mailing List
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error
in Transaction Reply.


I think my change is more focused.  We do not need multiple commandReply
instances since it is already a comma separated list.  If we support
multiple
errorDescriptor instances we would need to change ASN.1 too, since it does
NOT.

Also your change would need a separator (eg. COMMA) between instances.  If
we
really want multiple instances of each it would be easier to add
errorDescriptor
to commandReplys so they could appear in the commandReplyList which already
has
the separator.  But again this would introduce a new difference from ASN.1

I think simply matching the ASN.1 (as I tried to do) takes care of the one
need.

Tom-PT Taylor wrote:

> I half-prepared a reply on this issue back when it was first raised, but
> didn't get around to finishing it.  The real issue is what to do when
there
> has been an unrecognizable command.  If you follow through the ABNF all
> other cases are covered, because auditReturnParameter includes
> errorDescriptor as one of its alternatives.
>
> I'd suggest an ABNF correction of the form:
>
> actionReply = CtxToken EQUAL ContextID LBRKT
>              1*( errorDescriptor / commandReply ) RBRKT
>
> with a comment that multiple errorDescriptors would be allowed only if all
> except the last pertained to commands that had the "O-" (optional) prefix.
>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Wednesday, January 23, 2002 11:37 AM
> To: Megaco Mailing List
> Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
> Transaction Reply.
>
> I'm copying the list (and designating it as open issue #4) since it has
> become
> an IG issue.  See below.
>
> Christian Groves wrote:
>
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
>
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the
> ABNF
> since commandReply there is a comma separated list, but it does NOT allow
> both
> commandReply AND errorDescriptor as the ASN.1 does.
>
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've
often
> done this and it would solve the problem of no way to return replies for
the
> successes along with the error.
>
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT
>
> The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
> would be clearer if errorDescriptor came after commandReply (which is a
> list),
> so I am suggesting the order above for ABNF where the error looks more
like
> part of the reply sequence.
>
> > So in the case Sundar talks about you would send an error for "Syntax
> > error in action" and also return the commandReply for the command that
> > the MG processed.
> >
> > With regards to 6.84, "last action REPLY" does make things clearer but I
> > don't think other changes are needed.
>
> you don't think the other changes IN 6.84 are needed or other changes TO
> 6.84???
>
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > ErrorDescriptor is available at several levels in a reply including
> > > action and most command. Discussion of where the errorDescriptor
should
> > > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> > >
> > > 8.2.2 says that if MG cannot determine a legal action it returns 422
as
> > > the actionReply.  I guess I would argue that this is NOT a legal
action,
> > > since it contains an unknown command.
> > >
> > > The next sentence deals with a special case where the end of an action
> > > cannot be determined, but this is not really the case here.  IG 6.84
> > > modified this sentence to refer to the case where one or more COMMANDS
> > > in the action can be parsed, and so it might be tempting to follow
this
> > > case, but on reading it, I think the change is wrong.
> > >
> > > Christian, IG 6.84 was approved in Porto Seguro, one of the last
before
> > > you turned it over to me, and was suggested by Paul Long, but I do not
> > > see how it works.  The rest of the sentence still refers to Action
("422
> > > syntax Error in ACTION as the last ACTION for the transaction" - I
> > > believe it should be "last action REPLY for").  I believe that it WAS
> > > intended to say "Action" as it did before 6.84, and only means that if
> > > other PRECEDING Actions in the transaction before the one with
> > > failed-end-parse should be processed but the entire failed Action must
> > > result in an actionReply of ErrorDescriptor.  As modified the
processed
> > > Commands cannot return replies because of the action reply containing
> > > the error.
> > >
> > > There are two cases if a command cannot be parsed.  (1) If the command
> > > type can be determined but there is a parse failure inside (eg, Add,
> > > Move, Modify, Subtract), then we have the valid command token and can
> > > use the errorDescriptor (in terminationAudit) in ammsReply and
similarly
> > > for audit, notify, and serviceChangeRequest.
> > >
> > > (2) parse (as above) fails without a valid command type.  Here we have
> > > no command token to use in any of the *Reply and there is no
> > > errorDescriptor in commandReplys, so one is forced to use the one in
> > > actionReply and fail the entire action.  It would have been nice to
have
> > > errorDescriptor in commandReplys to take care of this case.
> > >
> > > Except for this last case one could fix the IG6.84 item by changing
the
> > > other instance of "Action" to command as well ('in the last command
> > > reply'), but perhaps this should be stated for both the action and
> > > command level.
> > >
> > > Sundareswaram P V wrote:
> > >
> > > > Hi,     cud u help in having a solution for the same. The following
is
> > > > the Query.  consider the example message below. MEGACO/1
> > > > [125.125.125.111]:55555
> > > > Transaction = 50009 {
> > > >    Context = 5000 {
> > > >       Subtract = A5555 {
> > > >          Statistics {
> > > >             ........
> > > >          }
> > > >        },
> > > >        abc = A5556 {                    // --- Command request type
is
> > > > Corrupted                    // instead of subtract it become 'abc'
> > > >                Statistics {
> > > >                   ......
> > > >                     nt/os=62345, ; octets sent
> > > >                     rtp/pr=780, ; packets received
> > > >                     nt/or=45123, ; octets received
> > > >                }
> > > >            }
> > > >         }
> > > >      }     The problem is as follows :         In the same context
we
> > > > have two commands. the first command get parsed well and will be
> > > > inserted in to the Action Request while in the second command, the
> > > > command type it self is corrupted. so how, do i form the ActionReply
> > > > :         as the RFC 3015 states :             action reply =
CtxToken
> > > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > > Command Reply) RBRKT             but as such for an action request i
> > > > can send only one action reply. but the syntax above doesn't allow
me
> > > > to set both an error descriptor and an command reply with in an
action
> > > > reply.             cud any one help me resolve the issue  ??  thanx
in
> > > > advance. rgds,Sundar.
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson              mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


------_=_NextPart_001_01C1A447.CC5DFEF0
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in =
 Transaction Reply.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I got this after dispatching my last note, and of =
course failed to read Troy's very well.&nbsp; I'm being terribly =
careless -- you're right about the fact that commandReply is an =
aggregate itself.</FONT></P>

<P><FONT SIZE=3D2>So I buy your proposal and am prepared to ignore the =
case where there are multiple &quot;unknown command&quot; errors with =
all but the last marked optional.&nbsp; If someone does that to the =
protocol, they deserve what they get.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 23, 2002 2:34 PM</FONT>
<BR><FONT SIZE=3D2>To: Taylor, Tom-PT [CAR:B800:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: Megaco Mailing List</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Re: Open Issue #4: Doubt =
regarding sending Error</FONT>
<BR><FONT SIZE=3D2>in Transaction Reply.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I think my change is more focused.&nbsp; We do not =
need multiple commandReply</FONT>
<BR><FONT SIZE=3D2>instances since it is already a comma separated =
list.&nbsp; If we support multiple</FONT>
<BR><FONT SIZE=3D2>errorDescriptor instances we would need to change =
ASN.1 too, since it does NOT.</FONT>
</P>

<P><FONT SIZE=3D2>Also your change would need a separator (eg. COMMA) =
between instances.&nbsp; If we</FONT>
<BR><FONT SIZE=3D2>really want multiple instances of each it would be =
easier to add errorDescriptor</FONT>
<BR><FONT SIZE=3D2>to commandReplys so they could appear in the =
commandReplyList which already has</FONT>
<BR><FONT SIZE=3D2>the separator.&nbsp; But again this would introduce =
a new difference from ASN.1</FONT>
</P>

<P><FONT SIZE=3D2>I think simply matching the ASN.1 (as I tried to do) =
takes care of the one need.</FONT>
</P>

<P><FONT SIZE=3D2>Tom-PT Taylor wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; I half-prepared a reply on this issue back when =
it was first raised, but</FONT>
<BR><FONT SIZE=3D2>&gt; didn't get around to finishing it.&nbsp; The =
real issue is what to do when there</FONT>
<BR><FONT SIZE=3D2>&gt; has been an unrecognizable command.&nbsp; If =
you follow through the ABNF all</FONT>
<BR><FONT SIZE=3D2>&gt; other cases are covered, because =
auditReturnParameter includes</FONT>
<BR><FONT SIZE=3D2>&gt; errorDescriptor as one of its =
alternatives.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I'd suggest an ABNF correction of the =
form:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; actionReply =3D CtxToken EQUAL ContextID =
LBRKT</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 1*( errorDescriptor / commandReply ) RBRKT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; with a comment that multiple errorDescriptors =
would be allowed only if all</FONT>
<BR><FONT SIZE=3D2>&gt; except the last pertained to commands that had =
the &quot;O-&quot; (optional) prefix.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, January 23, 2002 11:37 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Megaco Mailing List</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Megaco] Re: Open Issue #4: Doubt =
regarding sending Error in</FONT>
<BR><FONT SIZE=3D2>&gt; Transaction Reply.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I'm copying the list (and designating it as =
open issue #4) since it has</FONT>
<BR><FONT SIZE=3D2>&gt; become</FONT>
<BR><FONT SIZE=3D2>&gt; an IG issue.&nbsp; See below.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Christian Groves wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; G'Day Terry and Sundar,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The binary coding allows you to send an =
ErrorDescriptor and a sequence</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of commandReplies.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ActionReply ::=3D SEQUENCE</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; {</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
contextId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; ContextID,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; errorDescriptor =
ErrorDescriptor OPTIONAL,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
contextReply&nbsp;&nbsp;&nbsp; ContextRequest OPTIONAL,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
commandReply&nbsp;&nbsp;&nbsp; SEQUENCE OF CommandReply</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; }</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Oh, I hadn't noticed the difference.&nbsp; The =
sequence is also allowed in the</FONT>
<BR><FONT SIZE=3D2>&gt; ABNF</FONT>
<BR><FONT SIZE=3D2>&gt; since commandReply there is a comma separated =
list, but it does NOT allow</FONT>
<BR><FONT SIZE=3D2>&gt; both</FONT>
<BR><FONT SIZE=3D2>&gt; commandReply AND errorDescriptor as the ASN.1 =
does.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Do you think we should &quot;correct&quot; the =
ABNF to agree with ASN.1.&nbsp; We've often</FONT>
<BR><FONT SIZE=3D2>&gt; done this and it would solve the problem of no =
way to return replies for the</FONT>
<BR><FONT SIZE=3D2>&gt; successes along with the error.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The change making it most like the ASN.1 would =
be:</FONT>
<BR><FONT SIZE=3D2>&gt; actionReply&nbsp;&nbsp;&nbsp; =3D CtxToken =
EQUAL ContextID LBRKT</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; ( errorDescriptor / commandReply /</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; commandReply COMMA =
errorDescriptor ) RBRKT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The ASN.1 encodes the errorDescriptor first, =
but the description in 8.2.2</FONT>
<BR><FONT SIZE=3D2>&gt; would be clearer if errorDescriptor came after =
commandReply (which is a</FONT>
<BR><FONT SIZE=3D2>&gt; list),</FONT>
<BR><FONT SIZE=3D2>&gt; so I am suggesting the order above for ABNF =
where the error looks more like</FONT>
<BR><FONT SIZE=3D2>&gt; part of the reply sequence.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So in the case Sundar talks about you =
would send an error for &quot;Syntax</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; error in action&quot; and also return the =
commandReply for the command that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the MG processed.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; With regards to 6.84, &quot;last action =
REPLY&quot; does make things clearer but I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; don't think other changes are =
needed.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; you don't think the other changes IN 6.84 are =
needed or other changes TO</FONT>
<BR><FONT SIZE=3D2>&gt; 6.84???</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Terry L Anderson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ErrorDescriptor is available at =
several levels in a reply including</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; action and most command. Discussion =
of where the errorDescriptor should</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; appear in the reply is in 7.1.19, 8.0 =
and 8.2.2.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 8.2.2 says that if MG cannot =
determine a legal action it returns 422 as</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the actionReply.&nbsp; I guess I =
would argue that this is NOT a legal action,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; since it contains an unknown =
command.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The next sentence deals with a =
special case where the end of an action</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; cannot be determined, but this is not =
really the case here.&nbsp; IG 6.84</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; modified this sentence to refer to =
the case where one or more COMMANDS</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; in the action can be parsed, and so =
it might be tempting to follow this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; case, but on reading it, I think the =
change is wrong.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Christian, IG 6.84 was approved in =
Porto Seguro, one of the last before</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; you turned it over to me, and was =
suggested by Paul Long, but I do not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; see how it works.&nbsp; The rest of =
the sentence still refers to Action (&quot;422</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; syntax Error in ACTION as the last =
ACTION for the transaction&quot; - I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; believe it should be &quot;last =
action REPLY for&quot;).&nbsp; I believe that it WAS</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; intended to say &quot;Action&quot; as =
it did before 6.84, and only means that if</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; other PRECEDING Actions in the =
transaction before the one with</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; failed-end-parse should be processed =
but the entire failed Action must</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; result in an actionReply of =
ErrorDescriptor.&nbsp; As modified the processed</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Commands cannot return replies =
because of the action reply containing</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the error.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; There are two cases if a command =
cannot be parsed.&nbsp; (1) If the command</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; type can be determined but there is a =
parse failure inside (eg, Add,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Move, Modify, Subtract), then we have =
the valid command token and can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; use the errorDescriptor (in =
terminationAudit) in ammsReply and similarly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; for audit, notify, and =
serviceChangeRequest.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (2) parse (as above) fails without a =
valid command type.&nbsp; Here we have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; no command token to use in any of the =
*Reply and there is no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; errorDescriptor in commandReplys, so =
one is forced to use the one in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; actionReply and fail the entire =
action.&nbsp; It would have been nice to have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; errorDescriptor in commandReplys to =
take care of this case.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Except for this last case one could =
fix the IG6.84 item by changing the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; other instance of &quot;Action&quot; =
to command as well ('in the last command</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; reply'), but perhaps this should be =
stated for both the action and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; command level.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sundareswaram P V wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Hi,&nbsp;&nbsp;&nbsp;&nbsp; cud =
u help in having a solution for the same. The following is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the Query.&nbsp; consider the =
example message below. MEGACO/1</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; [125.125.125.111]:55555</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Transaction =3D 50009 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; Context =3D =
5000 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subtract =3D A5555 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics =
{</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; ........</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; abc =3D A5556 =
{&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // --- Command request type =
is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
Corrupted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // instead of =
subtract it become 'abc'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Statistics {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ......</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nt/os=3D62345, ; =
octets sent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rtp/pr=3D780, ; =
packets received</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nt/or=3D45123, ; =
octets received</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}&nbsp;&nbsp;&nbsp;&nbsp; The problem is as follows =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the same context =
we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; have two commands. the first =
command get parsed well and will be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; inserted in to the Action =
Request while in the second command, the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; command type it self is =
corrupted. so how, do i form the ActionReply</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as the RFC 3015 =
states =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; action reply =3D CtxToken</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; EQUAL ContextID =
LBRKT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; (ErrorDescriptor /</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Command Reply) =
RBRKT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; but as such for an action request i</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; can send only one action reply. =
but the syntax above doesn't allow me</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to set both an error descriptor =
and an command reply with in an action</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
reply.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; cud any one help me resolve the issue&nbsp; ??&nbsp; thanx =
in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; advance. rgds,Sundar.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Tel:908.582.7013&nbsp;&nbsp; =
Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Lucent Technologies/INS/Voice Over IP =
Access Networks</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Rm 2B-121, 600 Mountain Av, Murray =
Hill, NJ 07974</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; --</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; Tel:908.582.7013&nbsp;&nbsp; =
Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>&gt; Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>&gt; Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

<P><FONT SIZE=3D2>--</FONT>
</P>

<P><FONT =
SIZE=3D2>------------------------------------------------------------</F=
ONT>
<BR><FONT SIZE=3D2>Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A447.CC5DFEF0--

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


From daemon@optimus.ietf.org  Wed Jan 23 15:05:46 2002
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 PAA23105
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:05:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA14915
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 15:05:48 -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 OAA14281;
	Wed, 23 Jan 2002 14:55:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14179
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 14:55:18 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22687
	for <megaco@ietf.org>; Wed, 23 Jan 2002 14:55:15 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NJsid00374;
	Wed, 23 Jan 2002 14:54:44 -0500 (EST)
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 g0NJsgV06396;
	Wed, 23 Jan 2002 14:54:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZLJP>; Wed, 23 Jan 2002 14:54:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEEA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>
Cc: Megaco Mailing List <megaco@ietf.org>
Subject: RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in 
	 Transaction Reply.
Date: Wed, 23 Jan 2002 14:54:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A447.CC5DFEF0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A447.CC5DFEF0
Content-Type: text/plain;
	charset="ISO-8859-1"

I got this after dispatching my last note, and of course failed to read
Troy's very well.  I'm being terribly careless -- you're right about the
fact that commandReply is an aggregate itself.

So I buy your proposal and am prepared to ignore the case where there are
multiple "unknown command" errors with all but the last marked optional.  If
someone does that to the protocol, they deserve what they get.

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Wednesday, January 23, 2002 2:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Megaco Mailing List
Subject: Re: [Megaco] Re: Open Issue #4: Doubt regarding sending Error
in Transaction Reply.


I think my change is more focused.  We do not need multiple commandReply
instances since it is already a comma separated list.  If we support
multiple
errorDescriptor instances we would need to change ASN.1 too, since it does
NOT.

Also your change would need a separator (eg. COMMA) between instances.  If
we
really want multiple instances of each it would be easier to add
errorDescriptor
to commandReplys so they could appear in the commandReplyList which already
has
the separator.  But again this would introduce a new difference from ASN.1

I think simply matching the ASN.1 (as I tried to do) takes care of the one
need.

Tom-PT Taylor wrote:

> I half-prepared a reply on this issue back when it was first raised, but
> didn't get around to finishing it.  The real issue is what to do when
there
> has been an unrecognizable command.  If you follow through the ABNF all
> other cases are covered, because auditReturnParameter includes
> errorDescriptor as one of its alternatives.
>
> I'd suggest an ABNF correction of the form:
>
> actionReply = CtxToken EQUAL ContextID LBRKT
>              1*( errorDescriptor / commandReply ) RBRKT
>
> with a comment that multiple errorDescriptors would be allowed only if all
> except the last pertained to commands that had the "O-" (optional) prefix.
>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Wednesday, January 23, 2002 11:37 AM
> To: Megaco Mailing List
> Subject: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in
> Transaction Reply.
>
> I'm copying the list (and designating it as open issue #4) since it has
> become
> an IG issue.  See below.
>
> Christian Groves wrote:
>
> > G'Day Terry and Sundar,
> >
> > The binary coding allows you to send an ErrorDescriptor and a sequence
> > of commandReplies.
> >
> > ActionReply ::= SEQUENCE
> > {
> >         contextId               ContextID,
> >         errorDescriptor ErrorDescriptor OPTIONAL,
> >         contextReply    ContextRequest OPTIONAL,
> >         commandReply    SEQUENCE OF CommandReply
> > }
>
> Oh, I hadn't noticed the difference.  The sequence is also allowed in the
> ABNF
> since commandReply there is a comma separated list, but it does NOT allow
> both
> commandReply AND errorDescriptor as the ASN.1 does.
>
> Do you think we should "correct" the ABNF to agree with ASN.1.  We've
often
> done this and it would solve the problem of no way to return replies for
the
> successes along with the error.
>
> The change making it most like the ASN.1 would be:
> actionReply    = CtxToken EQUAL ContextID LBRKT
>                         ( errorDescriptor / commandReply /
>                             commandReply COMMA errorDescriptor ) RBRKT
>
> The ASN.1 encodes the errorDescriptor first, but the description in 8.2.2
> would be clearer if errorDescriptor came after commandReply (which is a
> list),
> so I am suggesting the order above for ABNF where the error looks more
like
> part of the reply sequence.
>
> > So in the case Sundar talks about you would send an error for "Syntax
> > error in action" and also return the commandReply for the command that
> > the MG processed.
> >
> > With regards to 6.84, "last action REPLY" does make things clearer but I
> > don't think other changes are needed.
>
> you don't think the other changes IN 6.84 are needed or other changes TO
> 6.84???
>
> > Regards, Christian
> >
> > Terry L Anderson wrote:
> > >
> > > ErrorDescriptor is available at several levels in a reply including
> > > action and most command. Discussion of where the errorDescriptor
should
> > > appear in the reply is in 7.1.19, 8.0 and 8.2.2.
> > >
> > > 8.2.2 says that if MG cannot determine a legal action it returns 422
as
> > > the actionReply.  I guess I would argue that this is NOT a legal
action,
> > > since it contains an unknown command.
> > >
> > > The next sentence deals with a special case where the end of an action
> > > cannot be determined, but this is not really the case here.  IG 6.84
> > > modified this sentence to refer to the case where one or more COMMANDS
> > > in the action can be parsed, and so it might be tempting to follow
this
> > > case, but on reading it, I think the change is wrong.
> > >
> > > Christian, IG 6.84 was approved in Porto Seguro, one of the last
before
> > > you turned it over to me, and was suggested by Paul Long, but I do not
> > > see how it works.  The rest of the sentence still refers to Action
("422
> > > syntax Error in ACTION as the last ACTION for the transaction" - I
> > > believe it should be "last action REPLY for").  I believe that it WAS
> > > intended to say "Action" as it did before 6.84, and only means that if
> > > other PRECEDING Actions in the transaction before the one with
> > > failed-end-parse should be processed but the entire failed Action must
> > > result in an actionReply of ErrorDescriptor.  As modified the
processed
> > > Commands cannot return replies because of the action reply containing
> > > the error.
> > >
> > > There are two cases if a command cannot be parsed.  (1) If the command
> > > type can be determined but there is a parse failure inside (eg, Add,
> > > Move, Modify, Subtract), then we have the valid command token and can
> > > use the errorDescriptor (in terminationAudit) in ammsReply and
similarly
> > > for audit, notify, and serviceChangeRequest.
> > >
> > > (2) parse (as above) fails without a valid command type.  Here we have
> > > no command token to use in any of the *Reply and there is no
> > > errorDescriptor in commandReplys, so one is forced to use the one in
> > > actionReply and fail the entire action.  It would have been nice to
have
> > > errorDescriptor in commandReplys to take care of this case.
> > >
> > > Except for this last case one could fix the IG6.84 item by changing
the
> > > other instance of "Action" to command as well ('in the last command
> > > reply'), but perhaps this should be stated for both the action and
> > > command level.
> > >
> > > Sundareswaram P V wrote:
> > >
> > > > Hi,     cud u help in having a solution for the same. The following
is
> > > > the Query.  consider the example message below. MEGACO/1
> > > > [125.125.125.111]:55555
> > > > Transaction = 50009 {
> > > >    Context = 5000 {
> > > >       Subtract = A5555 {
> > > >          Statistics {
> > > >             ........
> > > >          }
> > > >        },
> > > >        abc = A5556 {                    // --- Command request type
is
> > > > Corrupted                    // instead of subtract it become 'abc'
> > > >                Statistics {
> > > >                   ......
> > > >                     nt/os=62345, ; octets sent
> > > >                     rtp/pr=780, ; packets received
> > > >                     nt/or=45123, ; octets received
> > > >                }
> > > >            }
> > > >         }
> > > >      }     The problem is as follows :         In the same context
we
> > > > have two commands. the first command get parsed well and will be
> > > > inserted in to the Action Request while in the second command, the
> > > > command type it self is corrupted. so how, do i form the ActionReply
> > > > :         as the RFC 3015 states :             action reply =
CtxToken
> > > > EQUAL ContextID LBRKT                          (ErrorDescriptor /
> > > > Command Reply) RBRKT             but as such for an action request i
> > > > can send only one action reply. but the syntax above doesn't allow
me
> > > > to set both an error descriptor and an command reply with in an
action
> > > > reply.             cud any one help me resolve the issue  ??  thanx
in
> > > > advance. rgds,Sundar.
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson              mailto:tla@lucent.com
> > > Tel:908.582.7013   Fax:908.582.6729
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:908.582.7013   Fax:908.582.6729
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
> http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


------_=_NextPart_001_01C1A447.CC5DFEF0
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Re: Open Issue #4: Doubt regarding sending Error in =
 Transaction Reply.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I got this after dispatching my last note, and of =
course failed to read Troy's very well.&nbsp; I'm being terribly =
careless -- you're right about the fact that commandReply is an =
aggregate itself.</FONT></P>

<P><FONT SIZE=3D2>So I buy your proposal and am prepared to ignore the =
case where there are multiple &quot;unknown command&quot; errors with =
all but the last marked optional.&nbsp; If someone does that to the =
protocol, they deserve what they get.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 23, 2002 2:34 PM</FONT>
<BR><FONT SIZE=3D2>To: Taylor, Tom-PT [CAR:B800:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: Megaco Mailing List</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Re: Open Issue #4: Doubt =
regarding sending Error</FONT>
<BR><FONT SIZE=3D2>in Transaction Reply.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I think my change is more focused.&nbsp; We do not =
need multiple commandReply</FONT>
<BR><FONT SIZE=3D2>instances since it is already a comma separated =
list.&nbsp; If we support multiple</FONT>
<BR><FONT SIZE=3D2>errorDescriptor instances we would need to change =
ASN.1 too, since it does NOT.</FONT>
</P>

<P><FONT SIZE=3D2>Also your change would need a separator (eg. COMMA) =
between instances.&nbsp; If we</FONT>
<BR><FONT SIZE=3D2>really want multiple instances of each it would be =
easier to add errorDescriptor</FONT>
<BR><FONT SIZE=3D2>to commandReplys so they could appear in the =
commandReplyList which already has</FONT>
<BR><FONT SIZE=3D2>the separator.&nbsp; But again this would introduce =
a new difference from ASN.1</FONT>
</P>

<P><FONT SIZE=3D2>I think simply matching the ASN.1 (as I tried to do) =
takes care of the one need.</FONT>
</P>

<P><FONT SIZE=3D2>Tom-PT Taylor wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; I half-prepared a reply on this issue back when =
it was first raised, but</FONT>
<BR><FONT SIZE=3D2>&gt; didn't get around to finishing it.&nbsp; The =
real issue is what to do when there</FONT>
<BR><FONT SIZE=3D2>&gt; has been an unrecognizable command.&nbsp; If =
you follow through the ABNF all</FONT>
<BR><FONT SIZE=3D2>&gt; other cases are covered, because =
auditReturnParameter includes</FONT>
<BR><FONT SIZE=3D2>&gt; errorDescriptor as one of its =
alternatives.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I'd suggest an ABNF correction of the =
form:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; actionReply =3D CtxToken EQUAL ContextID =
LBRKT</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; 1*( errorDescriptor / commandReply ) RBRKT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; with a comment that multiple errorDescriptors =
would be allowed only if all</FONT>
<BR><FONT SIZE=3D2>&gt; except the last pertained to commands that had =
the &quot;O-&quot; (optional) prefix.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, January 23, 2002 11:37 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Megaco Mailing List</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Megaco] Re: Open Issue #4: Doubt =
regarding sending Error in</FONT>
<BR><FONT SIZE=3D2>&gt; Transaction Reply.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I'm copying the list (and designating it as =
open issue #4) since it has</FONT>
<BR><FONT SIZE=3D2>&gt; become</FONT>
<BR><FONT SIZE=3D2>&gt; an IG issue.&nbsp; See below.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Christian Groves wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; G'Day Terry and Sundar,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The binary coding allows you to send an =
ErrorDescriptor and a sequence</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of commandReplies.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ActionReply ::=3D SEQUENCE</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; {</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
contextId&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; ContextID,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; errorDescriptor =
ErrorDescriptor OPTIONAL,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
contextReply&nbsp;&nbsp;&nbsp; ContextRequest OPTIONAL,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
commandReply&nbsp;&nbsp;&nbsp; SEQUENCE OF CommandReply</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; }</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Oh, I hadn't noticed the difference.&nbsp; The =
sequence is also allowed in the</FONT>
<BR><FONT SIZE=3D2>&gt; ABNF</FONT>
<BR><FONT SIZE=3D2>&gt; since commandReply there is a comma separated =
list, but it does NOT allow</FONT>
<BR><FONT SIZE=3D2>&gt; both</FONT>
<BR><FONT SIZE=3D2>&gt; commandReply AND errorDescriptor as the ASN.1 =
does.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Do you think we should &quot;correct&quot; the =
ABNF to agree with ASN.1.&nbsp; We've often</FONT>
<BR><FONT SIZE=3D2>&gt; done this and it would solve the problem of no =
way to return replies for the</FONT>
<BR><FONT SIZE=3D2>&gt; successes along with the error.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The change making it most like the ASN.1 would =
be:</FONT>
<BR><FONT SIZE=3D2>&gt; actionReply&nbsp;&nbsp;&nbsp; =3D CtxToken =
EQUAL ContextID LBRKT</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; ( errorDescriptor / commandReply /</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; commandReply COMMA =
errorDescriptor ) RBRKT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The ASN.1 encodes the errorDescriptor first, =
but the description in 8.2.2</FONT>
<BR><FONT SIZE=3D2>&gt; would be clearer if errorDescriptor came after =
commandReply (which is a</FONT>
<BR><FONT SIZE=3D2>&gt; list),</FONT>
<BR><FONT SIZE=3D2>&gt; so I am suggesting the order above for ABNF =
where the error looks more like</FONT>
<BR><FONT SIZE=3D2>&gt; part of the reply sequence.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So in the case Sundar talks about you =
would send an error for &quot;Syntax</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; error in action&quot; and also return the =
commandReply for the command that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the MG processed.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; With regards to 6.84, &quot;last action =
REPLY&quot; does make things clearer but I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; don't think other changes are =
needed.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; you don't think the other changes IN 6.84 are =
needed or other changes TO</FONT>
<BR><FONT SIZE=3D2>&gt; 6.84???</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Terry L Anderson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; ErrorDescriptor is available at =
several levels in a reply including</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; action and most command. Discussion =
of where the errorDescriptor should</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; appear in the reply is in 7.1.19, 8.0 =
and 8.2.2.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 8.2.2 says that if MG cannot =
determine a legal action it returns 422 as</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the actionReply.&nbsp; I guess I =
would argue that this is NOT a legal action,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; since it contains an unknown =
command.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The next sentence deals with a =
special case where the end of an action</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; cannot be determined, but this is not =
really the case here.&nbsp; IG 6.84</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; modified this sentence to refer to =
the case where one or more COMMANDS</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; in the action can be parsed, and so =
it might be tempting to follow this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; case, but on reading it, I think the =
change is wrong.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Christian, IG 6.84 was approved in =
Porto Seguro, one of the last before</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; you turned it over to me, and was =
suggested by Paul Long, but I do not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; see how it works.&nbsp; The rest of =
the sentence still refers to Action (&quot;422</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; syntax Error in ACTION as the last =
ACTION for the transaction&quot; - I</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; believe it should be &quot;last =
action REPLY for&quot;).&nbsp; I believe that it WAS</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; intended to say &quot;Action&quot; as =
it did before 6.84, and only means that if</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; other PRECEDING Actions in the =
transaction before the one with</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; failed-end-parse should be processed =
but the entire failed Action must</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; result in an actionReply of =
ErrorDescriptor.&nbsp; As modified the processed</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Commands cannot return replies =
because of the action reply containing</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the error.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; There are two cases if a command =
cannot be parsed.&nbsp; (1) If the command</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; type can be determined but there is a =
parse failure inside (eg, Add,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Move, Modify, Subtract), then we have =
the valid command token and can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; use the errorDescriptor (in =
terminationAudit) in ammsReply and similarly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; for audit, notify, and =
serviceChangeRequest.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (2) parse (as above) fails without a =
valid command type.&nbsp; Here we have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; no command token to use in any of the =
*Reply and there is no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; errorDescriptor in commandReplys, so =
one is forced to use the one in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; actionReply and fail the entire =
action.&nbsp; It would have been nice to have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; errorDescriptor in commandReplys to =
take care of this case.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Except for this last case one could =
fix the IG6.84 item by changing the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; other instance of &quot;Action&quot; =
to command as well ('in the last command</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; reply'), but perhaps this should be =
stated for both the action and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; command level.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sundareswaram P V wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Hi,&nbsp;&nbsp;&nbsp;&nbsp; cud =
u help in having a solution for the same. The following is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the Query.&nbsp; consider the =
example message below. MEGACO/1</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; [125.125.125.111]:55555</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Transaction =3D 50009 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; Context =3D =
5000 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subtract =3D A5555 {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistics =
{</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; ........</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; abc =3D A5556 =
{&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // --- Command request type =
is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
Corrupted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // instead of =
subtract it become 'abc'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Statistics {</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ......</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nt/os=3D62345, ; =
octets sent</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rtp/pr=3D780, ; =
packets received</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nt/or=3D45123, ; =
octets received</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}&nbsp;&nbsp;&nbsp;&nbsp; The problem is as follows =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the same context =
we</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; have two commands. the first =
command get parsed well and will be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; inserted in to the Action =
Request while in the second command, the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; command type it self is =
corrupted. so how, do i form the ActionReply</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as the RFC 3015 =
states =
:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; action reply =3D CtxToken</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; EQUAL ContextID =
LBRKT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; (ErrorDescriptor /</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Command Reply) =
RBRKT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; but as such for an action request i</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; can send only one action reply. =
but the syntax above doesn't allow me</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to set both an error descriptor =
and an command reply with in an action</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; =
reply.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; cud any one help me resolve the issue&nbsp; ??&nbsp; thanx =
in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; advance. rgds,Sundar.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Tel:908.582.7013&nbsp;&nbsp; =
Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Lucent Technologies/INS/Voice Over IP =
Access Networks</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Rm 2B-121, 600 Mountain Av, Murray =
Hill, NJ 07974</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; --</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
------------------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; Tel:908.582.7013&nbsp;&nbsp; =
Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>&gt; Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>&gt; Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

<P><FONT SIZE=3D2>--</FONT>
</P>

<P><FONT =
SIZE=3D2>------------------------------------------------------------</F=
ONT>
<BR><FONT SIZE=3D2>Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A447.CC5DFEF0--

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



From megaco-admin@ietf.org  Wed Jan 23 15:16:51 2002
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 PAA23539
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:16:51 -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 PAA14966;
	Wed, 23 Jan 2002 15:07:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14932
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 15:06:58 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23179
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:06:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NK6Od10158;
	Wed, 23 Jan 2002 15:06:24 -0500 (EST)
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 g0NK6MV07084;
	Wed, 23 Jan 2002 15:06:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZL4F>; Wed, 23 Jan 2002 15:06:23 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEEC@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'ranabk@future.futsoft.com'" <ranabk@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Use of MUX descriptor
Date: Wed, 23 Jan 2002 15:06:23 -0500
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

You should think about the typical sequence for establishing a multimedia
conference at an MCU.  On the GSTN side, it will begin with one circuit,
with others added by separate calls.  You will thus have to modify the MUX
descriptors as new bearers are added.  In H.226/H.223 case I described in a
previous E-mail, you would have to create the H.226 multiplexing termination
first, before you could name it in the Mux descriptor for the H.223
multiplexing termination.  New bearers added to the H.226 multiplex would
not require any modification of the H.223 MUX descriptor, but could change
some of the other properties of the termination.



-----Original Message-----
From: ranabk [mailto:ranabk@future.futsoft.com]
Sent: Tuesday, January 22, 2002 6:16 AM
To: megaco@ietf.org
Subject: [Megaco] Use of MUX descriptor


We are exploring the use of MUX descriptors in ADD , MODIFY coomands .
Is there any specific event on which mux descriptors will be modified or
applied .
What is the pre condition to ADD with H221, H223, H226 mux descriptors ?

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 23 15:16:52 2002
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 PAA23546
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:16:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA15183
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 15:16:54 -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 PAA14966;
	Wed, 23 Jan 2002 15:07:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14932
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 15:06:58 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23179
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:06:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NK6Od10158;
	Wed, 23 Jan 2002 15:06:24 -0500 (EST)
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 g0NK6MV07084;
	Wed, 23 Jan 2002 15:06:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZL4F>; Wed, 23 Jan 2002 15:06:23 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEEC@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'ranabk@future.futsoft.com'" <ranabk@future.futsoft.com>, megaco@ietf.org
Subject: RE: [Megaco] Use of MUX descriptor
Date: Wed, 23 Jan 2002 15:06:23 -0500
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

You should think about the typical sequence for establishing a multimedia
conference at an MCU.  On the GSTN side, it will begin with one circuit,
with others added by separate calls.  You will thus have to modify the MUX
descriptors as new bearers are added.  In H.226/H.223 case I described in a
previous E-mail, you would have to create the H.226 multiplexing termination
first, before you could name it in the Mux descriptor for the H.223
multiplexing termination.  New bearers added to the H.226 multiplex would
not require any modification of the H.223 MUX descriptor, but could change
some of the other properties of the termination.



-----Original Message-----
From: ranabk [mailto:ranabk@future.futsoft.com]
Sent: Tuesday, January 22, 2002 6:16 AM
To: megaco@ietf.org
Subject: [Megaco] Use of MUX descriptor


We are exploring the use of MUX descriptors in ADD , MODIFY coomands .
Is there any specific event on which mux descriptors will be modified or
applied .
What is the pre condition to ADD with H221, H223, H226 mux descriptors ?

BR
B.K.Rana

----------------------------------------------------------------------------
-----
Basanta Kumar Rana
Project Manager ,
480/1,Nandanam , Mount Road ,
Chennai,India , 600035
Phone : +91-044-4330550 - Extn 411
Email : ranabk@future.futsoft.com


_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 23 15:25:49 2002
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 PAA23942
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:25:49 -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 PAA15375;
	Wed, 23 Jan 2002 15:18:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15345
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 15:18:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23619
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:18:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NKHcd11413;
	Wed, 23 Jan 2002 15:17:38 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NKHan21891;
	Wed, 23 Jan 2002 15:17:36 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZL9M>; Wed, 23 Jan 2002 15:17:37 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEED@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>,
        Terry L Anderson <tla@lucent.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Open Issue #3: Reserve Value and Reserve Group
Date: Wed, 23 Jan 2002 15:17:38 -0500
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

ReserveValue and ReserveGroup actually go a little beyond FID, I think.
Regardless, their use means that the MGC may have to do a translation
between the SDP sent to the MG and the SDP used in negotiating with the far
end.  I think a number of MGC vendors would prefer not to look at the
details of SDP, but just pass them through.

On DTMF, the choice of whether to handle in the signalling path or in the
media path is an old architectural issue.  We can't foreclose the RFC 2833
approach.

May I suggest that the defining characteristic of a media stream is that
only one media format (e.g. payload type) will flow in a given direction at
any given instant?

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Sunday, January 20, 2002 10:15 PM
To: Terry L Anderson
Cc: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group


G'Day Terry,

We already have this functionality in H.248 "Reserve Group" and "Reserve
Value". It allows the FID concept (group ID). With regards to sending
DTMF I thought that we used the signal mechanism for that. So I don't
think we need a change.

Regards, Christian

Troy Cauble wrote:
> 
> Terry L Anderson wrote:
> >
> > I am designating this issue as open issue #3.  Tom suggests that we
change a
> > statement that is proposed for the IG 6.98 (not yet approved).  The
intent of
> > the statement was that multiple media streams in SDP should not occur in
a
> > single H.248 StreamDescriptor, but defining this in terms of a single m
line is
> > too restrictive.
> > (1) FID allows grouping multiple media lines (m lines) into a single
media
> > stream and this should be allowed in a single H.248 StreamDescriptor.
> > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent
using a
> > distinct payload.  It also supports sending this payload to a different
> > ipaddr/port than that used for voice.  This in essence "forks" the media
stream
> > coming from one termination (eg. PSTN) into two output streams, one
containing
> > voice RTP and the other containing DTMF (or other telephone event RTP,
sent to
> > (possibly) two different ipaddr/ports.  This is similar in concept to
FID and
> > again requires multiple media (m) lines in the SDP.
> >
> > The current IG draft adds the following to 7.1.8 (right under the first
set of
> > bullets):
> >
> > A Stream Descriptor specifies a single bi-directional media stream and
so a
> > single session description MUST NOT include more than one media
description
> > ("m=" line).  Any additional media streams for a termination must appear
in
> > distinct Stream Descriptors.
> >
> > Perhaps we could change this to read:
> >
> > A Stream Descriptor specifies a single bi-directional media stream and
so a
> > single session description MUST NOT specify multiple streams.  This
often means
> > that the session description will contain only a single media
description ("m="
> > line).  However, where media descriptions are grouped and refer to a
single,
> > logical media stream but where payload packets may be sent to different
> > transport addresses, multiple media description lines may be required
(e.g., RFC
> > 2833).  Any additional, non-grouped media streams MUST appear in
distinct Stream
> > Descriptors.
> > --------
> > If we refer to RFC 2833, a reference will have to be added to section
2.2
> > Informative References, but I think this helps clarify the intent with
an
> > example.  We cannot refer to FID as it is not yet an RFC.
> 
> I have no problem with the intent of this change.  You have to
> change the language to allow certain cases.  But the language
> is getting very fuzzy.
> 
> How do I tell a "single, logical media stream" from "multiple streams"?
> 
> Why is voice & RFC2833 DTMF a "single, logical stream", when
> audio + video is "multiple streams"?
> 
> When would an MG be handling multiple streams on a termination
> that are not "logically" related in some way?
> 
> Doesn't this really mean I can put as many "streams" as I want
> in my SDP and have just one StreamDescriptor?
> 
> -troy
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan 23 15:25:50 2002
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 PAA23952
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 15:25:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA15841
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 15:25:52 -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 PAA15375;
	Wed, 23 Jan 2002 15:18:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15345
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 15:18:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23619
	for <megaco@ietf.org>; Wed, 23 Jan 2002 15:18:12 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NKHcd11413;
	Wed, 23 Jan 2002 15:17:38 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NKHan21891;
	Wed, 23 Jan 2002 15:17:36 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZL9M>; Wed, 23 Jan 2002 15:17:37 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEED@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>,
        Terry L Anderson <tla@lucent.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Open Issue #3: Reserve Value and Reserve Group
Date: Wed, 23 Jan 2002 15:17:38 -0500
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

ReserveValue and ReserveGroup actually go a little beyond FID, I think.
Regardless, their use means that the MGC may have to do a translation
between the SDP sent to the MG and the SDP used in negotiating with the far
end.  I think a number of MGC vendors would prefer not to look at the
details of SDP, but just pass them through.

On DTMF, the choice of whether to handle in the signalling path or in the
media path is an old architectural issue.  We can't foreclose the RFC 2833
approach.

May I suggest that the defining characteristic of a media stream is that
only one media format (e.g. payload type) will flow in a given direction at
any given instant?

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Sunday, January 20, 2002 10:15 PM
To: Terry L Anderson
Cc: megaco@ietf.org
Subject: Re: [Megaco] Open Issue #3: Reserve Value and Reserve Group


G'Day Terry,

We already have this functionality in H.248 "Reserve Group" and "Reserve
Value". It allows the FID concept (group ID). With regards to sending
DTMF I thought that we used the signal mechanism for that. So I don't
think we need a change.

Regards, Christian

Troy Cauble wrote:
> 
> Terry L Anderson wrote:
> >
> > I am designating this issue as open issue #3.  Tom suggests that we
change a
> > statement that is proposed for the IG 6.98 (not yet approved).  The
intent of
> > the statement was that multiple media streams in SDP should not occur in
a
> > single H.248 StreamDescriptor, but defining this in terms of a single m
line is
> > too restrictive.
> > (1) FID allows grouping multiple media lines (m lines) into a single
media
> > stream and this should be allowed in a single H.248 StreamDescriptor.
> > (2) RFC 2833 supports DTMF (and other telephone event tones) being sent
using a
> > distinct payload.  It also supports sending this payload to a different
> > ipaddr/port than that used for voice.  This in essence "forks" the media
stream
> > coming from one termination (eg. PSTN) into two output streams, one
containing
> > voice RTP and the other containing DTMF (or other telephone event RTP,
sent to
> > (possibly) two different ipaddr/ports.  This is similar in concept to
FID and
> > again requires multiple media (m) lines in the SDP.
> >
> > The current IG draft adds the following to 7.1.8 (right under the first
set of
> > bullets):
> >
> > A Stream Descriptor specifies a single bi-directional media stream and
so a
> > single session description MUST NOT include more than one media
description
> > ("m=" line).  Any additional media streams for a termination must appear
in
> > distinct Stream Descriptors.
> >
> > Perhaps we could change this to read:
> >
> > A Stream Descriptor specifies a single bi-directional media stream and
so a
> > single session description MUST NOT specify multiple streams.  This
often means
> > that the session description will contain only a single media
description ("m="
> > line).  However, where media descriptions are grouped and refer to a
single,
> > logical media stream but where payload packets may be sent to different
> > transport addresses, multiple media description lines may be required
(e.g., RFC
> > 2833).  Any additional, non-grouped media streams MUST appear in
distinct Stream
> > Descriptors.
> > --------
> > If we refer to RFC 2833, a reference will have to be added to section
2.2
> > Informative References, but I think this helps clarify the intent with
an
> > example.  We cannot refer to FID as it is not yet an RFC.
> 
> I have no problem with the intent of this change.  You have to
> change the language to allow certain cases.  But the language
> is getting very fuzzy.
> 
> How do I tell a "single, logical media stream" from "multiple streams"?
> 
> Why is voice & RFC2833 DTMF a "single, logical stream", when
> audio + video is "multiple streams"?
> 
> When would an MG be handling multiple streams on a termination
> that are not "logically" related in some way?
> 
> Doesn't this really mean I can put as many "streams" as I want
> in my SDP and have just one StreamDescriptor?
> 
> -troy
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan 23 16:22:10 2002
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 QAA25910
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 16:22:06 -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 QAA18015;
	Wed, 23 Jan 2002 16:13:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17983
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 16:13:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25624
	for <megaco@ietf.org>; Wed, 23 Jan 2002 16:13:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLCUd24439;
	Wed, 23 Jan 2002 16:12:30 -0500 (EST)
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 g0NLCSV10603;
	Wed, 23 Jan 2002 16:12:28 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZNMS>; Wed, 23 Jan 2002 16:12:29 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEF3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        Christian Groves
	 <Christian.Groves@ericsson.com.au>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Cancel ServiceChange Graceful
Date: Wed, 23 Jan 2002 16:12:29 -0500
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

SC Graceful from the MG should mean that the MGC won't direct any new calls
to it, no more than that until expiry of the grace period.

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, January 22, 2002 11:02 AM
To: Christian Groves
Cc: megaco@ietf.org
Subject: Re: [Megaco] Cancel ServiceChange Graceful


  
Maybe I need a clarification on what 
should attempt to gracefully tear down existing connections on the 
Termination(s) affected by the serviceChange command.
Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers hang
up normally and then 
put the termination OOS after subscribers hang up (before delay timer
expired)? 
Or MGC starts releasing the calls whether the subscribers hang up or not? 
Thanks 
Chuong 
Christian Groves wrote: 
There is a timing dependency here. If the MG issues a SC Graceful then 
the MGC will act on it. There will be a finite time that the MGC 
operates under graceful mode. If a SC Restart w/Service Restored or 
Service Change Cancel is issued during the graceful the MGC can't undo 
what it had done in that finite time but the connections that stayed up 
can remain up. If the SC Restart w/service restored or Service Change 
Cancel is not received before the delay times out then it pretty too 
late as the terminations will be torn down. 
I don't understand why you say that the MGC must wait until the 
servicechange delay timesouts before gracefully tearing down 
connections? 
Christian 
"Chuong N. Nguyen" wrote: 
> 
> 
> MG sends SC Graceful w/Delay and terminationID=ROOT. 
> 
> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC 
> assume that 
> 1) SC Graceful w/Delay is being cancelled? 
> 2) All terminations are back In Service?  Even the ones that were 
> originally OOS before the SC Graceful. 
> 
> 
>    1) Graceful - indicates that the specified Terminations will be 
> taken 
>       out of service after the specified ServiceChangeDelay; 
> established 
>       connections are not yet affected, but the Media Gateway 
> Controller 
>       should refrain from establishing new connections and should 
>       attempt to gracefully tear down existing connections on the 
>       Termination(s) affected by the serviceChange command. The MG 
>       should set termination serviceState at the expiry of 
>       ServiceChangeDelay or the removal of the termination from an 
>       active context (whichever is first), to "out of service". 
> 
> 
> How should MGC implementation intepret the above highlighted 
> statement? 
> Does this mean that MGC should not try to gracefully tear down 
> existing connections 
> before Delay timer expired? 
> 
> But I think the above statement is telling MGC to try and gracefully 
> tear down 
> existing connections before Delay timer expired. 
> 
> To be able to cancel Graceful w/Delay, it seems that MGC needs to wait 
> until 
> Delay timer expired before it tries to tear down existing connections. 
> 
> But after Delay timer expired, MG will put all terminations out of 
> service. 
> Therefore there is no such thing as MGC gracefully tearing down 
> existing connections. 
> 
> 
> Christian Groves wrote: 
> 
> > I don't see that we need to add anything. Why can't the MG just 
> > issue a 
> > SC with Restart, Service Restored? The specification already allows 
> > the 
> > MG to do this. 
> > 
> > Regards, Christian 
> > 
> > "Chuong N. Nguyen" wrote: 
> > > 
> > > Hi Tom 
> > > 
> > > What are the possibilites of defining a mechanism of cancelling 
> > > ServiceChange Graceful? 
> > > That is MG send SC Graceful w/Delay=time. 
> > > Before time expired, MG wants to cancel this ServiceChange. 
> > > 
> > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC 
> > > Graceful cancelled"? 
> > > 2) Done in V2 - new SC Method or Reason? 
> > > 3) Should be covered in draft-hss-megaco-control-association? 
> > > 
> > > 
> > > Thanks 
> > > Chuong 
> > > 
> > > 
> > > 
> > > -- 
> > >   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 **** 
> 
>
-- 
  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


From daemon@optimus.ietf.org  Wed Jan 23 16:22:16 2002
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 QAA25926
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 16:22:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA18217
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 16:22:14 -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 QAA18015;
	Wed, 23 Jan 2002 16:13:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17983
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 16:13:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25624
	for <megaco@ietf.org>; Wed, 23 Jan 2002 16:13:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLCUd24439;
	Wed, 23 Jan 2002 16:12:30 -0500 (EST)
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 g0NLCSV10603;
	Wed, 23 Jan 2002 16:12:28 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZNMS>; Wed, 23 Jan 2002 16:12:29 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEF3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        Christian Groves
	 <Christian.Groves@ericsson.com.au>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Cancel ServiceChange Graceful
Date: Wed, 23 Jan 2002 16:12:29 -0500
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

SC Graceful from the MG should mean that the MGC won't direct any new calls
to it, no more than that until expiry of the grace period.

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, January 22, 2002 11:02 AM
To: Christian Groves
Cc: megaco@ietf.org
Subject: Re: [Megaco] Cancel ServiceChange Graceful


  
Maybe I need a clarification on what 
should attempt to gracefully tear down existing connections on the 
Termination(s) affected by the serviceChange command.
Does the MGC just do a CAMP_ON-OOS - that is wait until the subcribers hang
up normally and then 
put the termination OOS after subscribers hang up (before delay timer
expired)? 
Or MGC starts releasing the calls whether the subscribers hang up or not? 
Thanks 
Chuong 
Christian Groves wrote: 
There is a timing dependency here. If the MG issues a SC Graceful then 
the MGC will act on it. There will be a finite time that the MGC 
operates under graceful mode. If a SC Restart w/Service Restored or 
Service Change Cancel is issued during the graceful the MGC can't undo 
what it had done in that finite time but the connections that stayed up 
can remain up. If the SC Restart w/service restored or Service Change 
Cancel is not received before the delay times out then it pretty too 
late as the terminations will be torn down. 
I don't understand why you say that the MGC must wait until the 
servicechange delay timesouts before gracefully tearing down 
connections? 
Christian 
"Chuong N. Nguyen" wrote: 
> 
> 
> MG sends SC Graceful w/Delay and terminationID=ROOT. 
> 
> If MG sends SC Restart w/Service Restorted and ROOT, does the MGC 
> assume that 
> 1) SC Graceful w/Delay is being cancelled? 
> 2) All terminations are back In Service?  Even the ones that were 
> originally OOS before the SC Graceful. 
> 
> 
>    1) Graceful - indicates that the specified Terminations will be 
> taken 
>       out of service after the specified ServiceChangeDelay; 
> established 
>       connections are not yet affected, but the Media Gateway 
> Controller 
>       should refrain from establishing new connections and should 
>       attempt to gracefully tear down existing connections on the 
>       Termination(s) affected by the serviceChange command. The MG 
>       should set termination serviceState at the expiry of 
>       ServiceChangeDelay or the removal of the termination from an 
>       active context (whichever is first), to "out of service". 
> 
> 
> How should MGC implementation intepret the above highlighted 
> statement? 
> Does this mean that MGC should not try to gracefully tear down 
> existing connections 
> before Delay timer expired? 
> 
> But I think the above statement is telling MGC to try and gracefully 
> tear down 
> existing connections before Delay timer expired. 
> 
> To be able to cancel Graceful w/Delay, it seems that MGC needs to wait 
> until 
> Delay timer expired before it tries to tear down existing connections. 
> 
> But after Delay timer expired, MG will put all terminations out of 
> service. 
> Therefore there is no such thing as MGC gracefully tearing down 
> existing connections. 
> 
> 
> Christian Groves wrote: 
> 
> > I don't see that we need to add anything. Why can't the MG just 
> > issue a 
> > SC with Restart, Service Restored? The specification already allows 
> > the 
> > MG to do this. 
> > 
> > Regards, Christian 
> > 
> > "Chuong N. Nguyen" wrote: 
> > > 
> > > Hi Tom 
> > > 
> > > What are the possibilites of defining a mechanism of cancelling 
> > > ServiceChange Graceful? 
> > > That is MG send SC Graceful w/Delay=time. 
> > > Before time expired, MG wants to cancel this ServiceChange. 
> > > 
> > > 1) Can this be done in V1 by adding a new SC Reason like "916 SC 
> > > Graceful cancelled"? 
> > > 2) Done in V2 - new SC Method or Reason? 
> > > 3) Should be covered in draft-hss-megaco-control-association? 
> > > 
> > > 
> > > Thanks 
> > > Chuong 
> > > 
> > > 
> > > 
> > > -- 
> > >   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 **** 
> 
>
-- 
  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



From megaco-admin@ietf.org  Wed Jan 23 16:36:41 2002
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 QAA26632
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 16:36:41 -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 QAA18298;
	Wed, 23 Jan 2002 16:24:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18267
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 16:24:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26028
	for <megaco@ietf.org>; Wed, 23 Jan 2002 16:24:29 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLNxd25695;
	Wed, 23 Jan 2002 16:23:59 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLNvn28092;
	Wed, 23 Jan 2002 16:23:57 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZNVF>; Wed, 23 Jan 2002 16:23:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEF4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about local control descriptor properties
Date: Wed, 23 Jan 2002 16:23:59 -0500
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

The answer to your question is yes, (and I didn't receive Christian's
similar answer) but I am a bit worried about whether it is clear how this
works.  

(1) What it does it mean if ReserveValue is unspecified in a modified
descriptor?  I would think it means that ReserveValue reverts to default
(i.e. false).

(2) What does it mean if a package-defined property is no longer specified
in a modified descriptor?  The answer again could be reversion to default,
or it could mean that the property is absent, or it could mean that the
property is present but its value is undefined.  Let's look at the
implications of these three alternatives.

(a) If a package-defined property is dropped from LocalControl, it takes on
the default value specified by the package or provisioned in the MG.  The
implicit assumption is that the termination continues to support the
package.  The question in my mind is how long package support continues.  It
seems to me that, while some packages may be supported for the entire life
of a termination, others may apply only during a single call and will have
unexpected effects if they persist beyond that call.  What do other people
think about this?

(b) The dropped property is no longer present on the termination.  To
support this interpretation we would need to say for every property that the
MG tracks its presence/absence as well as its value if present.  This
approach says nothing about whether we assume that the package continues to
be supported on the termination.

(c) The dropped property is present but its value is undefined.  I find this
unappealing.  Like (a), it implies continued support of the parent package,
but doesn't have the advantage of a consistent story for physical
terminations passing to and from the NULL context.

So: anyone else want to tackle this?  

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:44 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about local control descriptor properties




Hi Tom & list,

RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:

"If the MGC wishes to delete some information from the existing descriptor,
it
merely resends the
   descriptor (in a Modify command) with the unwanted information stripped
out."

Does the "unwanted information" refer to the properties which the MGC no
more
requires to be set on the termination......

Please reply back...

Thanks,
Kapil Nayar



_______________________________________________
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


From daemon@optimus.ietf.org  Wed Jan 23 16:36:43 2002
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 QAA26643
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 16:36:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA19051
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 16:36:43 -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 QAA18298;
	Wed, 23 Jan 2002 16:24:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18267
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 16:24:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26028
	for <megaco@ietf.org>; Wed, 23 Jan 2002 16:24:29 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLNxd25695;
	Wed, 23 Jan 2002 16:23:59 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0NLNvn28092;
	Wed, 23 Jan 2002 16:23:57 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZZNVF>; Wed, 23 Jan 2002 16:23:59 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEF4@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about local control descriptor properties
Date: Wed, 23 Jan 2002 16:23:59 -0500
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

The answer to your question is yes, (and I didn't receive Christian's
similar answer) but I am a bit worried about whether it is clear how this
works.  

(1) What it does it mean if ReserveValue is unspecified in a modified
descriptor?  I would think it means that ReserveValue reverts to default
(i.e. false).

(2) What does it mean if a package-defined property is no longer specified
in a modified descriptor?  The answer again could be reversion to default,
or it could mean that the property is absent, or it could mean that the
property is present but its value is undefined.  Let's look at the
implications of these three alternatives.

(a) If a package-defined property is dropped from LocalControl, it takes on
the default value specified by the package or provisioned in the MG.  The
implicit assumption is that the termination continues to support the
package.  The question in my mind is how long package support continues.  It
seems to me that, while some packages may be supported for the entire life
of a termination, others may apply only during a single call and will have
unexpected effects if they persist beyond that call.  What do other people
think about this?

(b) The dropped property is no longer present on the termination.  To
support this interpretation we would need to say for every property that the
MG tracks its presence/absence as well as its value if present.  This
approach says nothing about whether we assume that the package continues to
be supported on the termination.

(c) The dropped property is present but its value is undefined.  I find this
unappealing.  Like (a), it implies continued support of the parent package,
but doesn't have the advantage of a consistent story for physical
terminations passing to and from the NULL context.

So: anyone else want to tackle this?  

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:44 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about local control descriptor properties




Hi Tom & list,

RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:

"If the MGC wishes to delete some information from the existing descriptor,
it
merely resends the
   descriptor (in a Modify command) with the unwanted information stripped
out."

Does the "unwanted information" refer to the properties which the MGC no
more
requires to be set on the termination......

Please reply back...

Thanks,
Kapil Nayar



_______________________________________________
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



From megaco-admin@ietf.org  Wed Jan 23 23:24:53 2002
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 XAA05290
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 23:24:53 -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 XAA00359;
	Wed, 23 Jan 2002 23:02:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA00327
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 23:02:17 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04897
	for <megaco@ietf.org>; Wed, 23 Jan 2002 23:02:11 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA25329;
	Thu, 24 Jan 2002 15:00:46 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA13294;
	Thu, 24 Jan 2002 15:02:05 +1100 (EST)
Message-ID: <3C4F8821.8940522@ericsson.com.au>
Date: Thu, 24 Jan 2002 15:05:53 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AEF4@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

I think the easiest reply is that:
o In general reserveValue, reserveGroup and streammode return to default
as the these cannot disappear from a termination. 
o For package-defined properties the property is removed/absent. a)
below can't work because not every property has a default. It then leads
to c) where the value is unknown and this is not desirable.

Regards,
Christian

Tom-PT Taylor wrote:
> 
> The answer to your question is yes, (and I didn't receive Christian's
> similar answer) but I am a bit worried about whether it is clear how this
> works.
> 
> (1) What it does it mean if ReserveValue is unspecified in a modified
> descriptor?  I would think it means that ReserveValue reverts to default
> (i.e. false).

[CHG] 

> 
> (2) What does it mean if a package-defined property is no longer specified
> in a modified descriptor?  The answer again could be reversion to default,
> or it could mean that the property is absent, or it could mean that the
> property is present but its value is undefined.  Let's look at the
> implications of these three alternatives.
> 
> (a) If a package-defined property is dropped from LocalControl, it takes on
> the default value specified by the package or provisioned in the MG.  The
> implicit assumption is that the termination continues to support the
> package.  The question in my mind is how long package support continues.  It
> seems to me that, while some packages may be supported for the entire life
> of a termination, others may apply only during a single call and will have
> unexpected effects if they persist beyond that call.  What do other people
> think about this?
> 
> (b) The dropped property is no longer present on the termination.  To
> support this interpretation we would need to say for every property that the
> MG tracks its presence/absence as well as its value if present.  This
> approach says nothing about whether we assume that the package continues to
> be supported on the termination.
> 
> (c) The dropped property is present but its value is undefined.  I find this
> unappealing.  Like (a), it implies continued support of the parent package,
> but doesn't have the advantage of a consistent story for physical
> terminations passing to and from the NULL context.
> 
> So: anyone else want to tackle this?
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:44 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about local control descriptor properties
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
> 
> "If the MGC wishes to delete some information from the existing descriptor,
> it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped
> out."
> 
> Does the "unwanted information" refer to the properties which the MGC no
> more
> requires to be set on the termination......
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan 24 00:15:59 2002
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 XAA05297
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jan 2002 23:24:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA00734
	for megaco-archive@odin.ietf.org; Wed, 23 Jan 2002 23:24:57 -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 XAA00359;
	Wed, 23 Jan 2002 23:02:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA00327
	for <megaco@optimus.ietf.org>; Wed, 23 Jan 2002 23:02:17 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04897
	for <megaco@ietf.org>; Wed, 23 Jan 2002 23:02:11 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA25329;
	Thu, 24 Jan 2002 15:00:46 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA13294;
	Thu, 24 Jan 2002 15:02:05 +1100 (EST)
Message-ID: <3C4F8821.8940522@ericsson.com.au>
Date: Thu, 24 Jan 2002 15:05:53 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AEF4@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

I think the easiest reply is that:
o In general reserveValue, reserveGroup and streammode return to default
as the these cannot disappear from a termination. 
o For package-defined properties the property is removed/absent. a)
below can't work because not every property has a default. It then leads
to c) where the value is unknown and this is not desirable.

Regards,
Christian

Tom-PT Taylor wrote:
> 
> The answer to your question is yes, (and I didn't receive Christian's
> similar answer) but I am a bit worried about whether it is clear how this
> works.
> 
> (1) What it does it mean if ReserveValue is unspecified in a modified
> descriptor?  I would think it means that ReserveValue reverts to default
> (i.e. false).

[CHG] 

> 
> (2) What does it mean if a package-defined property is no longer specified
> in a modified descriptor?  The answer again could be reversion to default,
> or it could mean that the property is absent, or it could mean that the
> property is present but its value is undefined.  Let's look at the
> implications of these three alternatives.
> 
> (a) If a package-defined property is dropped from LocalControl, it takes on
> the default value specified by the package or provisioned in the MG.  The
> implicit assumption is that the termination continues to support the
> package.  The question in my mind is how long package support continues.  It
> seems to me that, while some packages may be supported for the entire life
> of a termination, others may apply only during a single call and will have
> unexpected effects if they persist beyond that call.  What do other people
> think about this?
> 
> (b) The dropped property is no longer present on the termination.  To
> support this interpretation we would need to say for every property that the
> MG tracks its presence/absence as well as its value if present.  This
> approach says nothing about whether we assume that the package continues to
> be supported on the termination.
> 
> (c) The dropped property is present but its value is undefined.  I find this
> unappealing.  Like (a), it implies continued support of the parent package,
> but doesn't have the advantage of a consistent story for physical
> terminations passing to and from the NULL context.
> 
> So: anyone else want to tackle this?
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:44 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about local control descriptor properties
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.7 LocalControl Descriptor mentions:
> 
> "If the MGC wishes to delete some information from the existing descriptor,
> it
> merely resends the
>    descriptor (in a Modify command) with the unwanted information stripped
> out."
> 
> Does the "unwanted information" refer to the properties which the MGC no
> more
> requires to be set on the termination......
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan 24 01:47:49 2002
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 BAA08089
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 01:47:49 -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 BAA14123;
	Thu, 24 Jan 2002 01:34:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA14096
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 01:34:22 -0500 (EST)
Received: from localhost ([211.117.232.146])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07941
	for <megaco@ietf.org>; Thu, 24 Jan 2002 01:34:16 -0500 (EST)
Message-Id: <200201240634.BAA07941@ietf.org>
Reply-To: office7000@yahoo.co.kr
From: Ã¢¾÷Á¤º¸<office7000@yahoo.co.kr>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Thu, 24 Jan 2002 15:34:22 +0900
Subject: [Megaco] [±¤°í] µ· µÇ´Â »ç¾÷Á¤º¸ÀÔ´Ï´Ù
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

<html>

<head>
<meta http-equiv="content-type" content="text/html; charset=euc-kr">
<title>±ÍÇÏÀÇ Ã¢¾÷À» µ½°Ú½À´Ï´Ù.  </title>
<meta name="generator" content="Namo WebEditor v5.0">
<meta name="description" content="ÇÑ ¹®´ÜÀ¸·Î µÈ º»¹®ÀÌ ÀÖ´Â ¹®¼­ ¿ä¼ÒÀÔ´Ï´Ù.">
</head>

<body bgcolor="white" text="black" link="blue" vlink="purple" alink="red">
                <table border="0" width="621" align="center" bgcolor="white">
                    <tr>
                        <td colspan="2" width="617">
            <p align="center">                            <a href="http://700office.com"><img src="http://www.700office.com/board/icon/gu.gif" width="295" height="43" border="0"></a></p>
                        </td>
                    </tr>
                    <tr>
                        <td width="19">
                            <p>&nbsp;</p>
                        </td>
                        <td width="596" bgcolor="#F6F6F6">
                            <p>&nbsp;<font face="µ¸¿ò" size="2">±ÍÇÏÀÇ Ã¢¾÷À» 
                            µ½°Ú½À´Ï´Ù. &nbsp;</font></p>
            <p><font face="µ¸¿ò" size="2">&nbsp;ÀúÈñ (ÁÖ)³ª·¡Á¤º¸¿¡¼­´Â ÀüÈ­Á¤º¸ 
                            Ã¢¾÷ÀÚ¸¦ ¸ð½Ê´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">&nbsp;º» &nbsp;»ç¾÷¼Ò¿¡¼­ º¸À¯ÇÑ 
                            ¾ÆÀÌÅÛÀ» µå¸±¼öµµ ÀÖ½À´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">±ÍÇÏ²²¼­ °èÈ¹ÇÏ½Å ¾ÆÀÌÅÛÀ» 
                            ¼öÀÍ¼º ÀÖ´Â »ç¾÷À¸·Î ¸¸µé¾î µå¸®°Ú½À´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">¼ö³â°£ÀÇ 
                            ±â¼ú°ú ³ëÇÏ¿ì·Î ÃÖ¼±À» ´ÙÇÏ¸ç, °í°´ÀÇ ÀÌÀÍ°ú »ç¾÷ÀÇ 
                            ¹ßÀüÀ» À§ÇØ ³ë·ÂÇÏ´Â ±â¾÷À¸·Î</font></p>
            <p> <font face="µ¸¿ò" size="2">±ÍÇÏÀÇ °ç¿¡ ³¡±îÁö 
                            ³²°Ú½À´Ï´Ù.</font></p>
            <p style="line-height:20px;" align="left"><font size="4" face="µ¸¿ò" color="blue"><b>ÀüÈ­Á¤º¸(700, 
                            060, 800, 0600)Æ¯Â¡</b></font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="±¼¸²">&nbsp;&nbsp;</font><font size="2" face="µ¸¿ò" color="#0066FF">1. 
                            Æ¯º°ÇÑ ÀÚ°ÝÀ» ¿äÇÏÁö ¾Ê½À´Ï´Ù.(»ç¾÷ÀÚ µî·ÏÁõ ÇÊ¿ä)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;2. 
                            ¼ö±ÝÀÇ ÇÊ¿ä¼ºÀÌ ¾ø½À´Ï´Ù.(°¢ Åë½Å»ç ¼ö±Ý´ëÇà)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;3. 
                            Å¸ »ç¾÷º¸´Ù ¿î¿µ°ú °ü¸®°¡ Æí¸®ÇÕ´Ï´Ù.(ÀüÈ­·Î °ü¸®°¡´É)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;4. 
                            ±ÍÇÏ¸¸ÀÇ ³ëÇÏ¿ì·Î Á¤º¸¸¦ Á¦°øÇÕ´Ï´Ù.(¾ÆÀÌÅÛÁ¦°ø)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;5. 
                            »ç¾÷¼º Å¸´ç¿©ºÎ Á¶»ç.(½ÃÀå¼º Á¶»ç ´ëÇà)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;6. 
                            Ã¢¾÷ÀÚ±ÝÁö¿ø.(Ã¢¾÷ÀÚ±ÝÀÇ 50%Áö¿ø, ¼öÀÍ±Ý Ã¢ÃâÈÄ¿¡ 
                            ¼ö±Ý)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;7. 
                            »ç¾÷ÀÇ Áö¼Ó¼º.(½Ã½ºÅÛ º»»ç °ü¸®. »ç¾÷ÀÚ´Â ±âÈ¹°ú 
                            ±¤°í)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;8. 
                            »ç¾÷ÀÇ ¾ÈÀü¼º.(ÇÑ±¹Åë½Å, ÇÏ³ª·ÎÅë½Å, µ¥ÀÌÄÞµî°ú 
                            ¿¬°èÇÏ¿© »ç¾÷¿µÀ§)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;9. 
                            º»»çÀÇ Áö¿ø.((ÁÖ)³ª·¡¿¡¼­ »ç¾÷ÀÚµî·Ï½ÅÃ», ½Ã½ºÅÛÁ¦ÀÛ, 
                            ¿î¿µ, °ü¸®)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;10. 
                            ÀåºñÀÓ´ë.(±Ý3,100,000¿øÀ¸·Î ÀåºñÀÏÃ¼¿Í ÇÁ·Î±×·¥À» 
                            Á¦°øÇÕ´Ï´Ù.) </font></p>
            <p style="line-height:5px;" align="left">&nbsp;</p>
<TABLE cellSpacing=0 cellPadding=0 width="539" align=center border=0 bordercolor="#CCCCCC">
<TBODY>
<TR>
<TD width="237" bgColor=#eeeef7 height="65">
<P style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; LINE-HEIGHT: 150%"><img src="http://www.700office.com/neww.gif" width="50" height="15" border="0"> 
                                        <a href="mailto:skylove0028@dreamwiz.com"><font color="blue">&quot;</font><font color="blue" size="2">±¤°í¸ÞÀÏ´ëÇà</font></a><span style="font-size:9pt;"><a href="mailto:skylove0028@dreamwiz.com"><font face="µ¸¿ò" color="blue">&quot; &nbsp;¸µÅ©ÇØÁÖ¼¼¿ä 
                                        </font></a></span><FONT 
color=#0033ff><SPAN style="FONT-SIZE: 9pt">&nbsp;</SPAN></FONT> 
</P></TD>
<TD width="302" height="65">
<SPAN style="FONT-SIZE: 9pt"><FONT face=µ¸¿ò>°¡Àå ºü¸¥ 
±¤°íÈ¿°úÀÔ´Ï´Ù. ºü¸¥ ½Ã°£¾È¿¡ È®½ÇÇÑ È¿°ú¸¦ º¸½Ç¼ö ÀÖ½À´Ï´Ù. ÀÌº¸´Ù &nbsp;¶Ù¾î³­ 
±¤°íÈ¿°ú¸¦ ±â´ëÇÒ ¼ö ¾ø½À´Ï´Ù. ÀúÈñ È¸¿ø¿¡ ÇÑÇÏ¿© ÈÄºÒ·Î °áÀç ¹Þ½À´Ï´Ù.</FONT></SPAN></TD></TR>
<TR>
<TD width="237">
&nbsp;</TD>
<TD width="302">
<TABLE cellSpacing=0 cellPadding=0 width=288 border=0>
<TBODY>
<TR>
<TD width=10 height="11">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </TD>
<TD width=278 height="11">&nbsp;</TD></TR></TBODY></TABLE>
<P></P></TD></TR></TBODY></TABLE>
<TABLE width="100%" bgColor=#ffffff text="#000000">
<TBODY>
<TR>
<TD vAlign=top width="588">
<TABLE cellSpacing=0 width=590 border=0>
<TBODY>
<TR>
<TD bgColor=#999999>
<TABLE cellSpacing=0 width="100%" border="1" bordercolordark="black" bordercolorlight="black">
<TBODY>
<TR>
<TD vAlign=top align=middle bgColor=#ffffff>                            <p style="line-height:20px;" align="center"><SPAN style="FONT-SIZE: 9pt">&nbsp;±ÍÇÏÀÇ ¸ÞÀÏÁÖ¼Ò´Â À¥¼­ÇÎÁß, <B>http://www.xxxxxxxx.com/</B> 
<BR>¿¡¼­ ¾Ë°Ô µÈ°ÍÀÌ¸ç, E-Mail ÁÖ¼Ò ¿Ü¿¡, ´Ù¸¥ Á¤º¸´Â °®°í ÀÖÁö ¾Ê½À´Ï´Ù.<BR>Á¤ÅëºÎ ±Ç°í»çÇ×¿¡ ÀÇ°Å Á¦¸ñ¿¡ 
</SPAN><B><SPAN style="FONT-SIZE: 9pt">[±¤°í]</SPAN></B><SPAN style="FONT-SIZE: 9pt">¶ó°í Ç¥±âÇÑ ¸ÞÀÏÀÔ´Ï´Ù. ¿øÄ¡ ¾ÊÀ¸¸é </SPAN><A 
href="mailto:joki@borahome.net?subject=¼ö½Å°ÅºÎ" target=new><B><SPAN 
style="FONT-SIZE: 9pt">,</SPAN></B></A><A 
href="mailto:office7000@yahoo.co.kr?subject=¼ö½Å°ÅºÎ" target=new><B><SPAN 
style="FONT-SIZE: 9pt"><FONT color=red>¼ö½Å°ÅºÎ</FONT></SPAN></B></A><SPAN style="FONT-SIZE: 9pt">¸¦ ´­·¯ÁÖ¼¼¿ä</SPAN> 
</p>
</TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>
            <p style="line-height:20px;" align="center"><SPAN style="FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></p>
                        </td>
                    </tr>
                </table>
<p>&nbsp;</p>
</body>




</html>

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


From daemon@optimus.ietf.org  Thu Jan 24 01:47:50 2002
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 BAA08099
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 01:47:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA14453
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 01:47:51 -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 BAA14123;
	Thu, 24 Jan 2002 01:34:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA14096
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 01:34:22 -0500 (EST)
Received: from localhost ([211.117.232.146])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07941
	for <megaco@ietf.org>; Thu, 24 Jan 2002 01:34:16 -0500 (EST)
Message-Id: <200201240634.BAA07941@ietf.org>
Reply-To: office7000@yahoo.co.kr
From: Ã¢¾÷Á¤º¸<office7000@yahoo.co.kr>
To: megaco@ietf.org
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Thu, 24 Jan 2002 15:34:22 +0900
Subject: [Megaco] [±¤°í] µ· µÇ´Â »ç¾÷Á¤º¸ÀÔ´Ï´Ù
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

<html>

<head>
<meta http-equiv="content-type" content="text/html; charset=euc-kr">
<title>±ÍÇÏÀÇ Ã¢¾÷À» µ½°Ú½À´Ï´Ù.  </title>
<meta name="generator" content="Namo WebEditor v5.0">
<meta name="description" content="ÇÑ ¹®´ÜÀ¸·Î µÈ º»¹®ÀÌ ÀÖ´Â ¹®¼­ ¿ä¼ÒÀÔ´Ï´Ù.">
</head>

<body bgcolor="white" text="black" link="blue" vlink="purple" alink="red">
                <table border="0" width="621" align="center" bgcolor="white">
                    <tr>
                        <td colspan="2" width="617">
            <p align="center">                            <a href="http://700office.com"><img src="http://www.700office.com/board/icon/gu.gif" width="295" height="43" border="0"></a></p>
                        </td>
                    </tr>
                    <tr>
                        <td width="19">
                            <p>&nbsp;</p>
                        </td>
                        <td width="596" bgcolor="#F6F6F6">
                            <p>&nbsp;<font face="µ¸¿ò" size="2">±ÍÇÏÀÇ Ã¢¾÷À» 
                            µ½°Ú½À´Ï´Ù. &nbsp;</font></p>
            <p><font face="µ¸¿ò" size="2">&nbsp;ÀúÈñ (ÁÖ)³ª·¡Á¤º¸¿¡¼­´Â ÀüÈ­Á¤º¸ 
                            Ã¢¾÷ÀÚ¸¦ ¸ð½Ê´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">&nbsp;º» &nbsp;»ç¾÷¼Ò¿¡¼­ º¸À¯ÇÑ 
                            ¾ÆÀÌÅÛÀ» µå¸±¼öµµ ÀÖ½À´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">±ÍÇÏ²²¼­ °èÈ¹ÇÏ½Å ¾ÆÀÌÅÛÀ» 
                            ¼öÀÍ¼º ÀÖ´Â »ç¾÷À¸·Î ¸¸µé¾î µå¸®°Ú½À´Ï´Ù. </font></p>
            <p><font face="µ¸¿ò" size="2">¼ö³â°£ÀÇ 
                            ±â¼ú°ú ³ëÇÏ¿ì·Î ÃÖ¼±À» ´ÙÇÏ¸ç, °í°´ÀÇ ÀÌÀÍ°ú »ç¾÷ÀÇ 
                            ¹ßÀüÀ» À§ÇØ ³ë·ÂÇÏ´Â ±â¾÷À¸·Î</font></p>
            <p> <font face="µ¸¿ò" size="2">±ÍÇÏÀÇ °ç¿¡ ³¡±îÁö 
                            ³²°Ú½À´Ï´Ù.</font></p>
            <p style="line-height:20px;" align="left"><font size="4" face="µ¸¿ò" color="blue"><b>ÀüÈ­Á¤º¸(700, 
                            060, 800, 0600)Æ¯Â¡</b></font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="±¼¸²">&nbsp;&nbsp;</font><font size="2" face="µ¸¿ò" color="#0066FF">1. 
                            Æ¯º°ÇÑ ÀÚ°ÝÀ» ¿äÇÏÁö ¾Ê½À´Ï´Ù.(»ç¾÷ÀÚ µî·ÏÁõ ÇÊ¿ä)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;2. 
                            ¼ö±ÝÀÇ ÇÊ¿ä¼ºÀÌ ¾ø½À´Ï´Ù.(°¢ Åë½Å»ç ¼ö±Ý´ëÇà)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;3. 
                            Å¸ »ç¾÷º¸´Ù ¿î¿µ°ú °ü¸®°¡ Æí¸®ÇÕ´Ï´Ù.(ÀüÈ­·Î °ü¸®°¡´É)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;4. 
                            ±ÍÇÏ¸¸ÀÇ ³ëÇÏ¿ì·Î Á¤º¸¸¦ Á¦°øÇÕ´Ï´Ù.(¾ÆÀÌÅÛÁ¦°ø)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;5. 
                            »ç¾÷¼º Å¸´ç¿©ºÎ Á¶»ç.(½ÃÀå¼º Á¶»ç ´ëÇà)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;6. 
                            Ã¢¾÷ÀÚ±ÝÁö¿ø.(Ã¢¾÷ÀÚ±ÝÀÇ 50%Áö¿ø, ¼öÀÍ±Ý Ã¢ÃâÈÄ¿¡ 
                            ¼ö±Ý)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;7. 
                            »ç¾÷ÀÇ Áö¼Ó¼º.(½Ã½ºÅÛ º»»ç °ü¸®. »ç¾÷ÀÚ´Â ±âÈ¹°ú 
                            ±¤°í)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;8. 
                            »ç¾÷ÀÇ ¾ÈÀü¼º.(ÇÑ±¹Åë½Å, ÇÏ³ª·ÎÅë½Å, µ¥ÀÌÄÞµî°ú 
                            ¿¬°èÇÏ¿© »ç¾÷¿µÀ§)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;&nbsp;9. 
                            º»»çÀÇ Áö¿ø.((ÁÖ)³ª·¡¿¡¼­ »ç¾÷ÀÚµî·Ï½ÅÃ», ½Ã½ºÅÛÁ¦ÀÛ, 
                            ¿î¿µ, °ü¸®)</font></p>
                            <p style="line-height:5px;" align="left"><font size="2" face="µ¸¿ò" color="#0066FF">&nbsp;10. 
                            ÀåºñÀÓ´ë.(±Ý3,100,000¿øÀ¸·Î ÀåºñÀÏÃ¼¿Í ÇÁ·Î±×·¥À» 
                            Á¦°øÇÕ´Ï´Ù.) </font></p>
            <p style="line-height:5px;" align="left">&nbsp;</p>
<TABLE cellSpacing=0 cellPadding=0 width="539" align=center border=0 bordercolor="#CCCCCC">
<TBODY>
<TR>
<TD width="237" bgColor=#eeeef7 height="65">
<P style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; LINE-HEIGHT: 150%"><img src="http://www.700office.com/neww.gif" width="50" height="15" border="0"> 
                                        <a href="mailto:skylove0028@dreamwiz.com"><font color="blue">&quot;</font><font color="blue" size="2">±¤°í¸ÞÀÏ´ëÇà</font></a><span style="font-size:9pt;"><a href="mailto:skylove0028@dreamwiz.com"><font face="µ¸¿ò" color="blue">&quot; &nbsp;¸µÅ©ÇØÁÖ¼¼¿ä 
                                        </font></a></span><FONT 
color=#0033ff><SPAN style="FONT-SIZE: 9pt">&nbsp;</SPAN></FONT> 
</P></TD>
<TD width="302" height="65">
<SPAN style="FONT-SIZE: 9pt"><FONT face=µ¸¿ò>°¡Àå ºü¸¥ 
±¤°íÈ¿°úÀÔ´Ï´Ù. ºü¸¥ ½Ã°£¾È¿¡ È®½ÇÇÑ È¿°ú¸¦ º¸½Ç¼ö ÀÖ½À´Ï´Ù. ÀÌº¸´Ù &nbsp;¶Ù¾î³­ 
±¤°íÈ¿°ú¸¦ ±â´ëÇÒ ¼ö ¾ø½À´Ï´Ù. ÀúÈñ È¸¿ø¿¡ ÇÑÇÏ¿© ÈÄºÒ·Î °áÀç ¹Þ½À´Ï´Ù.</FONT></SPAN></TD></TR>
<TR>
<TD width="237">
&nbsp;</TD>
<TD width="302">
<TABLE cellSpacing=0 cellPadding=0 width=288 border=0>
<TBODY>
<TR>
<TD width=10 height="11">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </TD>
<TD width=278 height="11">&nbsp;</TD></TR></TBODY></TABLE>
<P></P></TD></TR></TBODY></TABLE>
<TABLE width="100%" bgColor=#ffffff text="#000000">
<TBODY>
<TR>
<TD vAlign=top width="588">
<TABLE cellSpacing=0 width=590 border=0>
<TBODY>
<TR>
<TD bgColor=#999999>
<TABLE cellSpacing=0 width="100%" border="1" bordercolordark="black" bordercolorlight="black">
<TBODY>
<TR>
<TD vAlign=top align=middle bgColor=#ffffff>                            <p style="line-height:20px;" align="center"><SPAN style="FONT-SIZE: 9pt">&nbsp;±ÍÇÏÀÇ ¸ÞÀÏÁÖ¼Ò´Â À¥¼­ÇÎÁß, <B>http://www.xxxxxxxx.com/</B> 
<BR>¿¡¼­ ¾Ë°Ô µÈ°ÍÀÌ¸ç, E-Mail ÁÖ¼Ò ¿Ü¿¡, ´Ù¸¥ Á¤º¸´Â °®°í ÀÖÁö ¾Ê½À´Ï´Ù.<BR>Á¤ÅëºÎ ±Ç°í»çÇ×¿¡ ÀÇ°Å Á¦¸ñ¿¡ 
</SPAN><B><SPAN style="FONT-SIZE: 9pt">[±¤°í]</SPAN></B><SPAN style="FONT-SIZE: 9pt">¶ó°í Ç¥±âÇÑ ¸ÞÀÏÀÔ´Ï´Ù. ¿øÄ¡ ¾ÊÀ¸¸é </SPAN><A 
href="mailto:joki@borahome.net?subject=¼ö½Å°ÅºÎ" target=new><B><SPAN 
style="FONT-SIZE: 9pt">,</SPAN></B></A><A 
href="mailto:office7000@yahoo.co.kr?subject=¼ö½Å°ÅºÎ" target=new><B><SPAN 
style="FONT-SIZE: 9pt"><FONT color=red>¼ö½Å°ÅºÎ</FONT></SPAN></B></A><SPAN style="FONT-SIZE: 9pt">¸¦ ´­·¯ÁÖ¼¼¿ä</SPAN> 
</p>
</TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>
            <p style="line-height:20px;" align="center"><SPAN style="FONT-SIZE: 9pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></p>
                        </td>
                    </tr>
                </table>
<p>&nbsp;</p>
</body>




</html>

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



From megaco-admin@ietf.org  Thu Jan 24 05:59:31 2002
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 FAA19376
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 05:59:31 -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 FAA22635;
	Thu, 24 Jan 2002 05:48:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22537
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 05:48:31 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19220
	for <megaco@ietf.org>; Thu, 24 Jan 2002 05:48:25 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0OAmmE16433;
	Thu, 24 Jan 2002 16:18:48 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4B.003B3F95 ; Thu, 24 Jan 2002 16:17:09 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4B.003B3EBC.00@sandesh.hss.hns.com>
Date: Thu, 24 Jan 2002 16:19:03 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY"
Content-Disposition: inline
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

--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2 aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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






--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY
Content-type: text/html; 
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PUlTTy04ODU5LTEiPg0KPE1FVEEgTkFNRT0iR2VuZXJhdG9yIiBDT05URU5U
PSJNUyBFeGNoYW5nZSBTZXJ2ZXIgdmVyc2lvbiA1LjUuMjY1NC44OSI+DQo8VElUTEU+UkU6IFtN
ZWdhY29dIFF1ZXJ5IGFib3V0IHN0cmVhbUlEIDA8L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+DQoN
CjxQPjxGT05UIFNJWkU9Mj5IaS4mbmJzcDsgU2VlIG5ldyBjb21tZW50cyBbUFRUMl0gYmVsb3cu
PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS08L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPkZyb206IGtuYXlhckBoc3MuaG5zLmNvbSBbPEEg
SFJFRj0ibWFpbHRvOmtuYXlhckBoc3MuaG5zLmNvbSI+bWFpbHRvOmtuYXlhckBoc3MuaG5zLmNv
bTwvQT5dPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5TZW50OiBXZWRuZXNkYXksIEphbnVhcnkg
MjMsIDIwMDIgODo1NSBBTTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+VG86IFRheWxvciwgVG9t
LVBUIFtDQVI6QjgwMDpFWENIXTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+Q2M6ICdtZWdhY29A
aWV0Zi5vcmcnPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5TdWJqZWN0OiBSRTogW01lZ2Fjb10g
UXVlcnkgYWJvdXQgc3RyZWFtSUQgMDwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0K
PFA+PEZPTlQgU0laRT0yPkhpIFRvbTwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPm15
IGNvbW1lbnRzIGVtYmVkZGVkLjwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0KPFA+
PEZPTlQgU0laRT0yPiZxdW90O1RvbS1QVCBUYXlsb3ImcXVvdDsgJmx0O3RheWxvckBub3J0ZWxu
ZXR3b3Jrcy5jb20mZ3Q7IG9uIDAxLzIyLzIwMDIgMTE6MzU6MDAgUE08L0ZPTlQ+DQo8L1A+DQoN
CjxQPjxGT05UIFNJWkU9Mj5UbzombmJzcDsmbmJzcDsgS2FwaWwgTmF5YXIvSFNTQEhTUywgJnF1
b3Q7J21lZ2Fjb0BpZXRmLm9yZycmcXVvdDsgJmx0O21lZ2Fjb0BpZXRmLm9yZyZndDs8L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPmNjOjwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPlN1
YmplY3Q6Jm5ic3A7IFJFOiBbTWVnYWNvXSBRdWVyeSBhYm91dCBzdHJlYW1JRCAwPC9GT05UPg0K
PC9QPg0KPEJSPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpFPTI+SGkuPC9GT05UPg0KPC9Q
Pg0KDQo8UD48Rk9OVCBTSVpFPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08L0ZPTlQ+DQo8
QlI+PEZPTlQgU0laRT0yPkZyb206IGtuYXlhckBoc3MuaG5zLmNvbSBbPEEgSFJFRj0ibWFpbHRv
OmtuYXlhckBoc3MuaG5zLmNvbSI+bWFpbHRvOmtuYXlhckBoc3MuaG5zLmNvbTwvQT5dPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj5TZW50OiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDAyIDg6NTQg
QU08L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPlRvOiAnbWVnYWNvQGlldGYub3JnJzwvRk9OVD4N
CjxCUj48Rk9OVCBTSVpFPTI+U3ViamVjdDogW01lZ2Fjb10gUXVlcnkgYWJvdXQgc3RyZWFtSUQg
MDwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0KPFA+PEZPTlQgU0laRT0yPkhpIFRv
bSAmYW1wOyBsaXN0LDwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPlJGQyAzMDE1IFNl
Y3Rpb24gNy4xLjkgRXZlbnQgRGVzY3JpcHRvciAmYW1wOyA3LjEuMTEgU2lnbmFsIERlc2NyaXB0
b3IgbWVudGlvbnM6PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+JnF1b3Q7VGhlIGRl
ZmF1bHQgc3RyZWFtSUQgaXMgMCwgaW5kaWNhdGluZyB0aGF0IHRoZSBldmVudCB0byBiZSBkZXRl
Y3RlZCBpcyBub3Q8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnJlbGF0ZWQgdG8gYSBwYXJ0aWN1
bGFyIG1lZGlhIHN0cmVhbS4mcXVvdDs8L0ZPTlQ+DQo8L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5E
b2VzIHRoZSAmcXVvdDtzdHJlYW1JRCAwJnF1b3Q7IHJlZmVyIHRvIHRoZSBjb21wbGV0ZSB0ZXJt
aW5hdGlvbiAod2hpY2ggbWVhbnMgYWxsIHRoZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+YWN0
aXZlIHN0cmVhbXMgb24gdGhlIHRlcm1pbmF0aW9uKSA/PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9O
VCBTSVpFPTI+W1BUVF0gTm8uJm5ic3A7IEl0IHJlYWxseSBtZWFucyBhcyBpdCBzYXlzLCB0aGF0
IHRoZSBldmVudCBvciBzaWduYWwgaXMgbm90PC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5hc3Nv
Y2lhdGVkIHdpdGggYW55IHNwZWNpZmljIHN0cmVhbS4mbmJzcDsgQW4gZXhhbXBsZSBpcyBhbiBl
bGVjdHJpY2FsIHNpZ25hbDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+c3VjaCBhcyBvZmYtaG9v
ay48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPltLTl0gRG9lcyB0aGF0IG1lYW4gdGhhdCBzdHJl
YW0gMCBpcyBwb3NzaWJsZSBmb3Igb25seSBwaHlzaWNhbCB0ZXJtaW5hdGlvbnMsPC9GT05UPg0K
PEJSPjxGT05UIFNJWkU9Mj5zaW5jZSBlbGVjdHJpY2FsIHNpZ25hbHMgYXJlIG1vcmUgYXBwcm9w
cmlhdGUgZm9yIHBoeXNpY2FsIHRlcm1pbmF0aW9ucy48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0y
PltQVFQyXSBUaGVyZSBjYW4gYmUgYXBwbGljYXRpb25zIG9mIHN0cmVhbUlkIDAgb24gZXBoZW1l
cmFscyB3aGljaCBkb24ndCByZWxhdGUgdG8gc3BlY2lmaWMgc3RyZWFtcy4mbmJzcDsgRWxlY3Ry
aWNhbCBzaWduYWxzIHdlcmUganVzdCBhbiBleGFtcGxlLiZuYnNwOyBJIHN1c3BlY3QgSSBjb3Vs
ZCBmaW5kIGEgZ29vZCBleGFtcGxlIGluIG9uZSBvZiBteSBOQVMgcGFja2FnZXMgb2Ygc29tZXRo
aW5nIG1vcmUgYWJzdHJhY3QsIGJ1dCBJIHdvbid0IHRha2UgdGhlIHRpbWUuJm5ic3A7IEp1c3Qg
YWNjZXB0IHRoYXQgd2UgZG9uJ3Qgd2FudCB0byBmb3JlY2xvc2UgdGhlIHBvc3NpYmlsaXR5IG9m
IHVzaW5nIHRoaXMgb24gZXBoZW1lcmFscy48L0ZPTlQ+PC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+
QW5kLCBpZiBzb21lIGV2ZW50IGlzIHJlcXVpcmVkIHRvIGJlIGRldGVjdGVkIG9uIHRoZSBlcGhl
bWVyYWwgdGVybWluYXRpb24sPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj50aGUgZXZlbnQgZGVz
Y3JpcHRvciBzaG91bGQgY2xlYXJseSBpZGVudGlmeSB3aGljaCBzdHJlYW0gaXQgaXMgcmVxdWly
ZWQgb24uPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj4oaS5lLiwgTUdDIGNhbm5vdCBzZW5kIGFu
IGV2ZW50cyBkZXNjcmlwdG9yIGZvciBlcGhlbWVyYWwgdGVybWluYXRpb24gd2l0aG91dDwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+c3RyZWFtIElEIHBhcmFtZXRlciBzaW5jZSB0aGF0IGRlZmF1
bHRzIHRvIHN0cmVhbSBJRCAwLCB3aGljaCBtYXkgbm90IGJlPC9GT05UPg0KPEJSPjxGT05UIFNJ
WkU9Mj5hcHBsaWNhYmxlKS48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPltQVFQyXSBUaGF0IGhh
cyB0byBiZSB0aG91Z2h0IHRocm91Z2ggZm9yIGFsbCB0ZXJtaW5hdGlvbnMuJm5ic3A7IDwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+KioqIElHIGlzc3VlOiBJdCBkb2VzIHN0cmlrZSBtZSB0aGF0
IHlvdSBjYW4ga25vdyBpbiBhZHZhbmNlIChieSBkZWZpbml0aW9uIG9mIHRoZSBldmVudCBvciBz
aWduYWwpIHdoZXRoZXIgc3RyZWFtSWQ9MCB3aWxsIGFwcGx5LiZuYnNwOyBXZSBzaG91bGQgdGhl
cmVmb3JlIG1ha2UgaXQgcmVxdWlyZW1lbnQgdG8gc3BlY2lmeSB0aGlzIGluIHBhY2thZ2UgZGVm
aW5pdGlvbnMuPC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPltQVFRdIE9uIHRoZSBvdGhl
ciBoYW5kLCBhbiBhdWRpbyBzaWduYWwgc3VjaCBhcyBhIERUTUYgdG9uZSBpczwvRk9OVD4NCjxC
Uj48Rk9OVCBTSVpFPTI+YXNzb2NpYXRlZCB3aXRoIGFuIGF1ZGlvIHN0cmVhbS4mbmJzcDsgKEJ1
dCBJIGJldCBub2JvZHkgaGFzIGJvdGhlcmVkIHRvIHNwZWNpZnk8L0ZPTlQ+DQo8QlI+PEZPTlQg
U0laRT0yPnN0cmVhbSAxIGZvciBEVE1GIGV2ZW50cyB3aGVuIHRoZXkgYXJlIHVzaW5nIGEgZGVm
YXVsdCBzdHJlYW1JZCBmb3IgYXVkaW8uPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5UaGV5IHNo
b3VsZCEpPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5bS05dIERvZXMgdGhhdCBtZWFuIHRoYXQg
YmVmb3JlIHNlbmRpbmcgRFRNRmRldCAoZGQvJmx0Oz8mZ3Q7KSBpbiBldmVudHMgZGVzY3JpcHRv
ciw8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPk1HQyBzaG91bGQgaGF2ZSBhbHJlYWR5IGNyZWF0
ZWQgdGhlIHN0cmVhbSAxIHRocnUnIHRoZSBtZWRpYSBkZXNjcmlwdG9yPC9GT05UPg0KPEJSPjxG
T05UIFNJWkU9Mj5pbiBhIHByZXZpb3VzIGNvbW1hbmQ/IDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpF
PTI+W1BUVDJdIFN0cmVhbUlkPTEgaXMgdGhlIGRlZmF1bHQgc3RyZWFtIGNyZWF0ZWQgaWYgeW91
IGRvbid0IHVzZSBhIHN0cmVhbSBkZXNjcmlwdG9yLCBidXQganVzdCBzcGVjaWZ5IExvY2FsLCBS
ZW1vdGUsIGFuZCBMb2NhbENvbnRyb2wuPC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPioq
KiBJRyBpc3N1ZTogd291bGQgaXQgbWFrZSBtb3JlIHNlbnNlIHRvIGhhdmUgc3RyZWFtSWQ9MCBh
cyB0aGUgZGVmYXVsdCBmb3Igc2lnbmFscyBhbmQgZXZlbnRzLCBvciBoYXZlIHN0cmVhbUlkPTEg
YXMgdGhlIGRlZmF1bHQ/PC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPkEgcmVsYXRlZCBk
b3VidCBpcy4uLmlmIGFuIGV2ZW50IGRlc2NyaXB0b3IgcmVmZXJzPC9GT05UPg0KPEJSPjxGT05U
IFNJWkU9Mj50byBhIHN0cmVhbSBJRCB3aGljaCBpcyBub3QgcHJldmlvdXNseSBjcmVhdGVkIGJ5
IHRoZSBNR0MsIE1HIHNob3VsZDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+cmV0dXJuIGFuIGVy
cm9yLjwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+W1BUVDJdIEknbSBub3Qgc3VyZS4mbmJzcDsg
UmVtZW1iZXIgdGhhdCBzdHJlYW1JZHMgYXJlIHJlYWxseSBhIGNvbnRleHQgcHJvcGVydHkuJm5i
c3A7IElmIGEgZ2l2ZW4gc3RyZWFtSWQgaXMgc3VwcG9ydGVkIHNvbWV3aGVyZSBpbiB0aGUgY29u
dGV4dCwgdGhlbiByZWZlcnJpbmcgdG8gdGhhdCBzdHJlYW1JZCBhdCBhIGdpdmVuIHRlcm1pbmF0
aW9uIGltcGxpZXMgdGhhdCB0aGUgdGVybWluYXRpb24gYWxzbyBzdXBwb3J0cyBpdC4mbmJzcDsg
VGhhdCBtZWFucyBpdCBjb3VsZCBkZXRlY3QgZXZlbnRzIG9yIHNlbmQgc2lnbmFscyBvbiB0aGUg
c3RyZWFtIGV2ZW4gaWYgaXQgZG9lc24ndCBrbm93IGhvdyB0byBoYW5kbGUgdGhlIG1lZGlhIGZs
b3dzIG9uIHRoYXQgc3RyZWFtLiZuYnNwOyBJIHN1cHBvc2UgaWYgdGhpcyBpcyB0aGUgZmlyc3Qg
bWVudGlvbiBvZiB0aGUgc3RyZWFtSWQgaW4gdGhlIGNvbnRleHQsIGl0IG1pZ2h0IGJlIGFwcHJv
cHJpYXRlIHRvIHJlamVjdCB0aGUgY29tbWFuZC4mbmJzcDsgPC9GT05UPjwvUD4NCg0KPFA+PEZP
TlQgU0laRT0yPioqKklHIGlzc3VlOiBUaGUgaW1wbGljYXRpb24gaXMgdGhhdCB3aXRoaW4gYW55
IGNvbW1hbmQsIFN0cmVhbSBEZXNjcmlwdG9ycyBmb3IgbmV3IHN0cmVhbXMgTVVTVCBhcHBlYXIg
YmVmb3JlIFNpZ25hbHMgYW5kIEV2ZW50cyBkZXNjcmlwdG9ycyByZWZlcnJpbmcgdG8gdGhvc2Ug
U3RyZWFtSWRzLiA8L0ZPTlQ+PC9QPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpFPTI+Q2Fu
IE1HQyBzZW5kIHN0cmVhbUlEIHZhbHVlIDAgaW4gYSBNRUdBQ08gY29tbWFuZC8gZGVzY3JpcHRv
ci4gZWc6IG1lZGlhPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5kZXNjcmlwdG9yLCBldmVudCBk
ZXNjcmlwdG9yLCBzaWduYWwgZGVzY3JpcHRvciA/PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBT
SVpFPTI+W1BUVF0gTG9naWNhbGx5LCB5b3UgY2Fubm90IHVzZSBzdHJlYW1JZCA9IDAgaW4gYSBt
ZWRpYSBkZXNjcmlwdG9yIGFuZCBiZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+Y29uc2lzdGVu
dCB3aXRoIHRoZSBtZWFuaW5nIG9mIHRoYXQgc3RyZWFtSWQgZm9yIGV2ZW50cyBhbmQgc2lnbmFs
cy4mbmJzcDsgV2U8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnNob3VsZCBoYXZlIGEgbm90ZSB0
byB0aGUgZWZmZWN0IHRoYXQgc3RyZWFtSWQ9MCBpcyByZXNlcnZlZCBpbiBzZWN0aW9uczwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+Ny4xLjQgKGZvciB0aG9yb3VnaG5lc3MpIGFuZCA3LjEuNi48
L0ZPTlQ+DQo8L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5Zb3UgY2FuIHNwZWNpZnkgc3RyZWFtSWQ9
MCBpbiBhIHNpZ25hbHMgb3IgZXZlbnRzIGRlc2NyaXB0b3IsIGJ1dCB0aGF0J3MgdGhlPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj5zYW1lIGFzIGxlYXZpbmcgaXQgdW5zcGVjaWZpZWQuPC9GT05U
Pg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+UGxlYXNlIHJlcGx5IGJhY2suLi48L0ZPTlQ+DQo8
L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5UaGFua3MsPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5L
YXBpbCBOYXlhcjwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCg0KPFA+PEZPTlQgU0laRT0yPiZx
dW90O0RJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBpcyBwcm9wcmlldGFyeSB0byBIdWdoZXMgU29m
dHdhcmUgU3lzdG1lcyBMaW1pdGVkPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj4oSFNTKSBhbmQg
aXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsJm5ic3A7IHRv
IHdob20gaXQgaXM8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPmFkZHJlc3NlZC4gSXQgbWF5IGNv
bnRhaW4mbmJzcDsgcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24mbmJzcDsg
YW5kPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5zaG91bGQ8L0ZPTlQ+DQo8QlI+PEZPTlQgU0la
RT0yPm5vdCBiZSBjaXJjdWxhdGVkIG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRoYW4g
Zm9yIHdoYXQgaXQgaXM8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPmludGVuZGVkLklmPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj55b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1lc3NhZ2UgaW4gZXJy
b3IsIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3I8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0y
PmltbWVkaWF0ZWx5LiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3Ug
YXJlIG5vdGlmaWVkIHRoYXQ8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnlvdTwvRk9OVD4NCjxC
Uj48Rk9OVCBTSVpFPTI+YXJlIHN0cmljdGx5IHByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWlu
ZywgYWx0ZXJpbmcsIG9yIGRpc2Nsb3NpbmcgdGhlPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5j
b250ZW50cyBvZiB0aGlzIG1lc3NhZ2UuIEhTUyBhY2NlcHRzIG5vIHJlc3BvbnNpYmlsaXR5IGZv
ciBsb3NzIG9yIGRhbWFnZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+YXJpc2luZyBmcm9tIHRo
ZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zaW1pdHRlZCBieSB0aGlzIGVtYWlsIGluY2x1
ZGluZzwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+ZGFtYWdlIGZyb20gdmlydXMuJnF1b3Q7PC9G
T05UPg0KPC9QPg0KPEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpF
PTI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPk1lZ2FjbyBtYWlsaW5nIGxpc3Q8L0ZPTlQ+DQo8QlI+PEZPTlQg
U0laRT0yPk1lZ2Fjb0BpZXRmLm9yZzwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+PEEgSFJFRj0i
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWVnYWNvIiBUQVJHRVQ9Il9i
bGFuayI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWVnYWNvPC9BPjwv
Rk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5NZWdhY28gbWFp
bGluZyBsaXN0PC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5NZWdhY29AaWV0Zi5vcmc8L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPjxBIEhSRUY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21lZ2FjbyIgVEFSR0VUPSJfYmxhbmsiPmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21lZ2FjbzwvQT48L0ZPTlQ+DQo8L1A+DQo8QlI+DQo8QlI+DQo8QlI+
DQoNCjwvQk9EWT4NCjwvSFRNTD4NCg==

--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY--


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


From daemon@optimus.ietf.org  Thu Jan 24 05:59:32 2002
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 FAA19386
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 05:59:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA22811
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 05:59:35 -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 FAA22635;
	Thu, 24 Jan 2002 05:48:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22537
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 05:48:31 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19220
	for <megaco@ietf.org>; Thu, 24 Jan 2002 05:48:25 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0OAmmE16433;
	Thu, 24 Jan 2002 16:18:48 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4B.003B3F95 ; Thu, 24 Jan 2002 16:17:09 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4B.003B3EBC.00@sandesh.hss.hns.com>
Date: Thu, 24 Jan 2002 16:19:03 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY"
Content-Disposition: inline
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

--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2 aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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






--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY
Content-type: text/html; 
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PUlTTy04ODU5LTEiPg0KPE1FVEEgTkFNRT0iR2VuZXJhdG9yIiBDT05URU5U
PSJNUyBFeGNoYW5nZSBTZXJ2ZXIgdmVyc2lvbiA1LjUuMjY1NC44OSI+DQo8VElUTEU+UkU6IFtN
ZWdhY29dIFF1ZXJ5IGFib3V0IHN0cmVhbUlEIDA8L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+DQoN
CjxQPjxGT05UIFNJWkU9Mj5IaS4mbmJzcDsgU2VlIG5ldyBjb21tZW50cyBbUFRUMl0gYmVsb3cu
PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS08L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPkZyb206IGtuYXlhckBoc3MuaG5zLmNvbSBbPEEg
SFJFRj0ibWFpbHRvOmtuYXlhckBoc3MuaG5zLmNvbSI+bWFpbHRvOmtuYXlhckBoc3MuaG5zLmNv
bTwvQT5dPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5TZW50OiBXZWRuZXNkYXksIEphbnVhcnkg
MjMsIDIwMDIgODo1NSBBTTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+VG86IFRheWxvciwgVG9t
LVBUIFtDQVI6QjgwMDpFWENIXTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+Q2M6ICdtZWdhY29A
aWV0Zi5vcmcnPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5TdWJqZWN0OiBSRTogW01lZ2Fjb10g
UXVlcnkgYWJvdXQgc3RyZWFtSUQgMDwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0K
PFA+PEZPTlQgU0laRT0yPkhpIFRvbTwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPm15
IGNvbW1lbnRzIGVtYmVkZGVkLjwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0KPFA+
PEZPTlQgU0laRT0yPiZxdW90O1RvbS1QVCBUYXlsb3ImcXVvdDsgJmx0O3RheWxvckBub3J0ZWxu
ZXR3b3Jrcy5jb20mZ3Q7IG9uIDAxLzIyLzIwMDIgMTE6MzU6MDAgUE08L0ZPTlQ+DQo8L1A+DQoN
CjxQPjxGT05UIFNJWkU9Mj5UbzombmJzcDsmbmJzcDsgS2FwaWwgTmF5YXIvSFNTQEhTUywgJnF1
b3Q7J21lZ2Fjb0BpZXRmLm9yZycmcXVvdDsgJmx0O21lZ2Fjb0BpZXRmLm9yZyZndDs8L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPmNjOjwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPlN1
YmplY3Q6Jm5ic3A7IFJFOiBbTWVnYWNvXSBRdWVyeSBhYm91dCBzdHJlYW1JRCAwPC9GT05UPg0K
PC9QPg0KPEJSPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpFPTI+SGkuPC9GT05UPg0KPC9Q
Pg0KDQo8UD48Rk9OVCBTSVpFPTI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08L0ZPTlQ+DQo8
QlI+PEZPTlQgU0laRT0yPkZyb206IGtuYXlhckBoc3MuaG5zLmNvbSBbPEEgSFJFRj0ibWFpbHRv
OmtuYXlhckBoc3MuaG5zLmNvbSI+bWFpbHRvOmtuYXlhckBoc3MuaG5zLmNvbTwvQT5dPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj5TZW50OiBUdWVzZGF5LCBKYW51YXJ5IDIyLCAyMDAyIDg6NTQg
QU08L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPlRvOiAnbWVnYWNvQGlldGYub3JnJzwvRk9OVD4N
CjxCUj48Rk9OVCBTSVpFPTI+U3ViamVjdDogW01lZ2Fjb10gUXVlcnkgYWJvdXQgc3RyZWFtSUQg
MDwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCjxCUj4NCg0KPFA+PEZPTlQgU0laRT0yPkhpIFRv
bSAmYW1wOyBsaXN0LDwvRk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPlJGQyAzMDE1IFNl
Y3Rpb24gNy4xLjkgRXZlbnQgRGVzY3JpcHRvciAmYW1wOyA3LjEuMTEgU2lnbmFsIERlc2NyaXB0
b3IgbWVudGlvbnM6PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+JnF1b3Q7VGhlIGRl
ZmF1bHQgc3RyZWFtSUQgaXMgMCwgaW5kaWNhdGluZyB0aGF0IHRoZSBldmVudCB0byBiZSBkZXRl
Y3RlZCBpcyBub3Q8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnJlbGF0ZWQgdG8gYSBwYXJ0aWN1
bGFyIG1lZGlhIHN0cmVhbS4mcXVvdDs8L0ZPTlQ+DQo8L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5E
b2VzIHRoZSAmcXVvdDtzdHJlYW1JRCAwJnF1b3Q7IHJlZmVyIHRvIHRoZSBjb21wbGV0ZSB0ZXJt
aW5hdGlvbiAod2hpY2ggbWVhbnMgYWxsIHRoZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+YWN0
aXZlIHN0cmVhbXMgb24gdGhlIHRlcm1pbmF0aW9uKSA/PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9O
VCBTSVpFPTI+W1BUVF0gTm8uJm5ic3A7IEl0IHJlYWxseSBtZWFucyBhcyBpdCBzYXlzLCB0aGF0
IHRoZSBldmVudCBvciBzaWduYWwgaXMgbm90PC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5hc3Nv
Y2lhdGVkIHdpdGggYW55IHNwZWNpZmljIHN0cmVhbS4mbmJzcDsgQW4gZXhhbXBsZSBpcyBhbiBl
bGVjdHJpY2FsIHNpZ25hbDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+c3VjaCBhcyBvZmYtaG9v
ay48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPltLTl0gRG9lcyB0aGF0IG1lYW4gdGhhdCBzdHJl
YW0gMCBpcyBwb3NzaWJsZSBmb3Igb25seSBwaHlzaWNhbCB0ZXJtaW5hdGlvbnMsPC9GT05UPg0K
PEJSPjxGT05UIFNJWkU9Mj5zaW5jZSBlbGVjdHJpY2FsIHNpZ25hbHMgYXJlIG1vcmUgYXBwcm9w
cmlhdGUgZm9yIHBoeXNpY2FsIHRlcm1pbmF0aW9ucy48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0y
PltQVFQyXSBUaGVyZSBjYW4gYmUgYXBwbGljYXRpb25zIG9mIHN0cmVhbUlkIDAgb24gZXBoZW1l
cmFscyB3aGljaCBkb24ndCByZWxhdGUgdG8gc3BlY2lmaWMgc3RyZWFtcy4mbmJzcDsgRWxlY3Ry
aWNhbCBzaWduYWxzIHdlcmUganVzdCBhbiBleGFtcGxlLiZuYnNwOyBJIHN1c3BlY3QgSSBjb3Vs
ZCBmaW5kIGEgZ29vZCBleGFtcGxlIGluIG9uZSBvZiBteSBOQVMgcGFja2FnZXMgb2Ygc29tZXRo
aW5nIG1vcmUgYWJzdHJhY3QsIGJ1dCBJIHdvbid0IHRha2UgdGhlIHRpbWUuJm5ic3A7IEp1c3Qg
YWNjZXB0IHRoYXQgd2UgZG9uJ3Qgd2FudCB0byBmb3JlY2xvc2UgdGhlIHBvc3NpYmlsaXR5IG9m
IHVzaW5nIHRoaXMgb24gZXBoZW1lcmFscy48L0ZPTlQ+PC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+
QW5kLCBpZiBzb21lIGV2ZW50IGlzIHJlcXVpcmVkIHRvIGJlIGRldGVjdGVkIG9uIHRoZSBlcGhl
bWVyYWwgdGVybWluYXRpb24sPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj50aGUgZXZlbnQgZGVz
Y3JpcHRvciBzaG91bGQgY2xlYXJseSBpZGVudGlmeSB3aGljaCBzdHJlYW0gaXQgaXMgcmVxdWly
ZWQgb24uPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj4oaS5lLiwgTUdDIGNhbm5vdCBzZW5kIGFu
IGV2ZW50cyBkZXNjcmlwdG9yIGZvciBlcGhlbWVyYWwgdGVybWluYXRpb24gd2l0aG91dDwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+c3RyZWFtIElEIHBhcmFtZXRlciBzaW5jZSB0aGF0IGRlZmF1
bHRzIHRvIHN0cmVhbSBJRCAwLCB3aGljaCBtYXkgbm90IGJlPC9GT05UPg0KPEJSPjxGT05UIFNJ
WkU9Mj5hcHBsaWNhYmxlKS48L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPltQVFQyXSBUaGF0IGhh
cyB0byBiZSB0aG91Z2h0IHRocm91Z2ggZm9yIGFsbCB0ZXJtaW5hdGlvbnMuJm5ic3A7IDwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+KioqIElHIGlzc3VlOiBJdCBkb2VzIHN0cmlrZSBtZSB0aGF0
IHlvdSBjYW4ga25vdyBpbiBhZHZhbmNlIChieSBkZWZpbml0aW9uIG9mIHRoZSBldmVudCBvciBz
aWduYWwpIHdoZXRoZXIgc3RyZWFtSWQ9MCB3aWxsIGFwcGx5LiZuYnNwOyBXZSBzaG91bGQgdGhl
cmVmb3JlIG1ha2UgaXQgcmVxdWlyZW1lbnQgdG8gc3BlY2lmeSB0aGlzIGluIHBhY2thZ2UgZGVm
aW5pdGlvbnMuPC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPltQVFRdIE9uIHRoZSBvdGhl
ciBoYW5kLCBhbiBhdWRpbyBzaWduYWwgc3VjaCBhcyBhIERUTUYgdG9uZSBpczwvRk9OVD4NCjxC
Uj48Rk9OVCBTSVpFPTI+YXNzb2NpYXRlZCB3aXRoIGFuIGF1ZGlvIHN0cmVhbS4mbmJzcDsgKEJ1
dCBJIGJldCBub2JvZHkgaGFzIGJvdGhlcmVkIHRvIHNwZWNpZnk8L0ZPTlQ+DQo8QlI+PEZPTlQg
U0laRT0yPnN0cmVhbSAxIGZvciBEVE1GIGV2ZW50cyB3aGVuIHRoZXkgYXJlIHVzaW5nIGEgZGVm
YXVsdCBzdHJlYW1JZCBmb3IgYXVkaW8uPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5UaGV5IHNo
b3VsZCEpPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5bS05dIERvZXMgdGhhdCBtZWFuIHRoYXQg
YmVmb3JlIHNlbmRpbmcgRFRNRmRldCAoZGQvJmx0Oz8mZ3Q7KSBpbiBldmVudHMgZGVzY3JpcHRv
ciw8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPk1HQyBzaG91bGQgaGF2ZSBhbHJlYWR5IGNyZWF0
ZWQgdGhlIHN0cmVhbSAxIHRocnUnIHRoZSBtZWRpYSBkZXNjcmlwdG9yPC9GT05UPg0KPEJSPjxG
T05UIFNJWkU9Mj5pbiBhIHByZXZpb3VzIGNvbW1hbmQ/IDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpF
PTI+W1BUVDJdIFN0cmVhbUlkPTEgaXMgdGhlIGRlZmF1bHQgc3RyZWFtIGNyZWF0ZWQgaWYgeW91
IGRvbid0IHVzZSBhIHN0cmVhbSBkZXNjcmlwdG9yLCBidXQganVzdCBzcGVjaWZ5IExvY2FsLCBS
ZW1vdGUsIGFuZCBMb2NhbENvbnRyb2wuPC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPioq
KiBJRyBpc3N1ZTogd291bGQgaXQgbWFrZSBtb3JlIHNlbnNlIHRvIGhhdmUgc3RyZWFtSWQ9MCBh
cyB0aGUgZGVmYXVsdCBmb3Igc2lnbmFscyBhbmQgZXZlbnRzLCBvciBoYXZlIHN0cmVhbUlkPTEg
YXMgdGhlIGRlZmF1bHQ/PC9GT05UPjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPkEgcmVsYXRlZCBk
b3VidCBpcy4uLmlmIGFuIGV2ZW50IGRlc2NyaXB0b3IgcmVmZXJzPC9GT05UPg0KPEJSPjxGT05U
IFNJWkU9Mj50byBhIHN0cmVhbSBJRCB3aGljaCBpcyBub3QgcHJldmlvdXNseSBjcmVhdGVkIGJ5
IHRoZSBNR0MsIE1HIHNob3VsZDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+cmV0dXJuIGFuIGVy
cm9yLjwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+W1BUVDJdIEknbSBub3Qgc3VyZS4mbmJzcDsg
UmVtZW1iZXIgdGhhdCBzdHJlYW1JZHMgYXJlIHJlYWxseSBhIGNvbnRleHQgcHJvcGVydHkuJm5i
c3A7IElmIGEgZ2l2ZW4gc3RyZWFtSWQgaXMgc3VwcG9ydGVkIHNvbWV3aGVyZSBpbiB0aGUgY29u
dGV4dCwgdGhlbiByZWZlcnJpbmcgdG8gdGhhdCBzdHJlYW1JZCBhdCBhIGdpdmVuIHRlcm1pbmF0
aW9uIGltcGxpZXMgdGhhdCB0aGUgdGVybWluYXRpb24gYWxzbyBzdXBwb3J0cyBpdC4mbmJzcDsg
VGhhdCBtZWFucyBpdCBjb3VsZCBkZXRlY3QgZXZlbnRzIG9yIHNlbmQgc2lnbmFscyBvbiB0aGUg
c3RyZWFtIGV2ZW4gaWYgaXQgZG9lc24ndCBrbm93IGhvdyB0byBoYW5kbGUgdGhlIG1lZGlhIGZs
b3dzIG9uIHRoYXQgc3RyZWFtLiZuYnNwOyBJIHN1cHBvc2UgaWYgdGhpcyBpcyB0aGUgZmlyc3Qg
bWVudGlvbiBvZiB0aGUgc3RyZWFtSWQgaW4gdGhlIGNvbnRleHQsIGl0IG1pZ2h0IGJlIGFwcHJv
cHJpYXRlIHRvIHJlamVjdCB0aGUgY29tbWFuZC4mbmJzcDsgPC9GT05UPjwvUD4NCg0KPFA+PEZP
TlQgU0laRT0yPioqKklHIGlzc3VlOiBUaGUgaW1wbGljYXRpb24gaXMgdGhhdCB3aXRoaW4gYW55
IGNvbW1hbmQsIFN0cmVhbSBEZXNjcmlwdG9ycyBmb3IgbmV3IHN0cmVhbXMgTVVTVCBhcHBlYXIg
YmVmb3JlIFNpZ25hbHMgYW5kIEV2ZW50cyBkZXNjcmlwdG9ycyByZWZlcnJpbmcgdG8gdGhvc2Ug
U3RyZWFtSWRzLiA8L0ZPTlQ+PC9QPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpFPTI+Q2Fu
IE1HQyBzZW5kIHN0cmVhbUlEIHZhbHVlIDAgaW4gYSBNRUdBQ08gY29tbWFuZC8gZGVzY3JpcHRv
ci4gZWc6IG1lZGlhPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5kZXNjcmlwdG9yLCBldmVudCBk
ZXNjcmlwdG9yLCBzaWduYWwgZGVzY3JpcHRvciA/PC9GT05UPg0KPC9QPg0KDQo8UD48Rk9OVCBT
SVpFPTI+W1BUVF0gTG9naWNhbGx5LCB5b3UgY2Fubm90IHVzZSBzdHJlYW1JZCA9IDAgaW4gYSBt
ZWRpYSBkZXNjcmlwdG9yIGFuZCBiZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+Y29uc2lzdGVu
dCB3aXRoIHRoZSBtZWFuaW5nIG9mIHRoYXQgc3RyZWFtSWQgZm9yIGV2ZW50cyBhbmQgc2lnbmFs
cy4mbmJzcDsgV2U8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnNob3VsZCBoYXZlIGEgbm90ZSB0
byB0aGUgZWZmZWN0IHRoYXQgc3RyZWFtSWQ9MCBpcyByZXNlcnZlZCBpbiBzZWN0aW9uczwvRk9O
VD4NCjxCUj48Rk9OVCBTSVpFPTI+Ny4xLjQgKGZvciB0aG9yb3VnaG5lc3MpIGFuZCA3LjEuNi48
L0ZPTlQ+DQo8L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5Zb3UgY2FuIHNwZWNpZnkgc3RyZWFtSWQ9
MCBpbiBhIHNpZ25hbHMgb3IgZXZlbnRzIGRlc2NyaXB0b3IsIGJ1dCB0aGF0J3MgdGhlPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj5zYW1lIGFzIGxlYXZpbmcgaXQgdW5zcGVjaWZpZWQuPC9GT05U
Pg0KPC9QPg0KDQo8UD48Rk9OVCBTSVpFPTI+UGxlYXNlIHJlcGx5IGJhY2suLi48L0ZPTlQ+DQo8
L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj5UaGFua3MsPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5L
YXBpbCBOYXlhcjwvRk9OVD4NCjwvUD4NCjxCUj4NCjxCUj4NCg0KPFA+PEZPTlQgU0laRT0yPiZx
dW90O0RJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBpcyBwcm9wcmlldGFyeSB0byBIdWdoZXMgU29m
dHdhcmUgU3lzdG1lcyBMaW1pdGVkPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj4oSFNTKSBhbmQg
aXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsJm5ic3A7IHRv
IHdob20gaXQgaXM8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPmFkZHJlc3NlZC4gSXQgbWF5IGNv
bnRhaW4mbmJzcDsgcHJpdmlsZWdlZCBvciBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24mbmJzcDsg
YW5kPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5zaG91bGQ8L0ZPTlQ+DQo8QlI+PEZPTlQgU0la
RT0yPm5vdCBiZSBjaXJjdWxhdGVkIG9yIHVzZWQgZm9yIGFueSBwdXJwb3NlIG90aGVyIHRoYW4g
Zm9yIHdoYXQgaXQgaXM8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPmludGVuZGVkLklmPC9GT05U
Pg0KPEJSPjxGT05UIFNJWkU9Mj55b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1lc3NhZ2UgaW4gZXJy
b3IsIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3I8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0y
PmltbWVkaWF0ZWx5LiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3Ug
YXJlIG5vdGlmaWVkIHRoYXQ8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnlvdTwvRk9OVD4NCjxC
Uj48Rk9OVCBTSVpFPTI+YXJlIHN0cmljdGx5IHByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWlu
ZywgYWx0ZXJpbmcsIG9yIGRpc2Nsb3NpbmcgdGhlPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5j
b250ZW50cyBvZiB0aGlzIG1lc3NhZ2UuIEhTUyBhY2NlcHRzIG5vIHJlc3BvbnNpYmlsaXR5IGZv
ciBsb3NzIG9yIGRhbWFnZTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+YXJpc2luZyBmcm9tIHRo
ZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zaW1pdHRlZCBieSB0aGlzIGVtYWlsIGluY2x1
ZGluZzwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+ZGFtYWdlIGZyb20gdmlydXMuJnF1b3Q7PC9G
T05UPg0KPC9QPg0KPEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KDQo8UD48Rk9OVCBTSVpF
PTI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPk1lZ2FjbyBtYWlsaW5nIGxpc3Q8L0ZPTlQ+DQo8QlI+PEZPTlQg
U0laRT0yPk1lZ2Fjb0BpZXRmLm9yZzwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+PEEgSFJFRj0i
aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWVnYWNvIiBUQVJHRVQ9Il9i
bGFuayI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWVnYWNvPC9BPjwv
Rk9OVD4NCjwvUD4NCg0KPFA+PEZPTlQgU0laRT0yPl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5NZWdhY28gbWFp
bGluZyBsaXN0PC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj5NZWdhY29AaWV0Zi5vcmc8L0ZPTlQ+
DQo8QlI+PEZPTlQgU0laRT0yPjxBIEhSRUY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21lZ2FjbyIgVEFSR0VUPSJfYmxhbmsiPmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21lZ2FjbzwvQT48L0ZPTlQ+DQo8L1A+DQo8QlI+DQo8QlI+DQo8QlI+
DQoNCjwvQk9EWT4NCjwvSFRNTD4NCg==

--0__=ATx4LiHoKo7yZYxD6fIWuO2nu3D38lD0MuGczPnh8JCYuAGkNqh6gjbY--


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



From megaco-admin@ietf.org  Thu Jan 24 07:00:29 2002
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 HAA19991
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 07:00:29 -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 GAA24341;
	Thu, 24 Jan 2002 06:44:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24310
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 06:44:14 -0500 (EST)
Received: from cvis21.Marconicomms.com (cvis21.marconicomms.com [195.99.244.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19836
	for <megaco@ietf.org>; Thu, 24 Jan 2002 06:44:11 -0500 (EST)
Received: from cvis05.marconicomms.com (unverified) by cvis21.Marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f4359958a4b78474@cvis21.Marconicomms.com> for <megaco@ietf.org>;
 Thu, 24 Jan 2002 11:43:32 +0000
Received: from cvdgwy01.uk.marconicomms.com by cvis05.marconicomms.com with ESMTP
 (8.10.2+Sun/cvms-34) id g0OBhcK04930; Thu, 24 Jan 2002 11:43:38 GMT
Subject: RE: [Megaco] Query about local control descriptor properties
To: taylor@nortelnetworks.com
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
From: "Wayne Cutler" <Wayne.Cutler@marconi.com>
Date: Thu, 24 Jan 2002 11:43:34 +0000
Message-ID: <OFA1731B2B.C2D26F93-ON80256B4B.003A8478@uk.marconicomms.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.8 |June 18, 2001) at
 24/01/2002 11:43:33
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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


Some thoughts (in line) on the following:-

>(2) What does it mean if a package-defined property is no longer specified
>in a modified descriptor?  The answer again could be reversion to default,
>or it could mean that the property is absent, or it could mean that the
>property is present but its value is undefined.  Let's look at the
>implications of these three alternatives.

>(a) If a package-defined property is dropped from LocalControl, it takes
on
>the default value specified by the package or provisioned in the MG.  The
>implicit assumption is that the termination continues to support the
>package.  The question in my mind is how long package support continues.
It
>seems to me that, while some packages may be supported for the entire life
>of a termination, others may apply only during a single call and will have
>unexpected effects if they persist beyond that call.  What do other people
>think about this?

I think that Packages are attributes of a termination and so package
support
should continue as long as the termination is present/exists. For example,
if an ephemeral
termination is destroyed, then there is no longer Package support against
that
termination. MGs don't want to know about "calls" and should not IMO make
assumptions
about lifetimes of Packages. To be safe, it seems best to have the MGC be
explicit in
terms of what it wants an MG to do and the MG just gets on with it. I think
that this means
that the MG may end up holding data/attributes that aren't doing any good -
but is also doing
no harm (e.g.  tdm/ec is left at OFF at the end of a call, and would be
switched back on by the
MGC for the next call/connection).

>(b) The dropped property is no longer present on the termination.  To
>support this interpretation we would need to say for every property that
the
>MG tracks its presence/absence as well as its value if present.  This
>approach says nothing about whether we assume that the package continues
to
>be supported on the termination.

Properties are to do with storing data against a termination. So, I'm
confused by the property no longer being "present". Rather, isn't it a case
that the a given property is always present
for an existing termination but may currently hold a null/default value?

>(c) The dropped property is present but its value is undefined.  I find
this
>unappealing.  Like (a), it implies continued support of the parent
package,
>but doesn't have the advantage of a consistent story for physical
>terminations passing to and from the NULL context.


What about an option d) that would regard an absent Property as meaning
"leave the existing value unchanged"?


As a related question, I note that section 7.1.7 (Local Control Desc.)of
the spec.
says that:-

"A new setting of the LocalControl Descriptor completely replaces the
previous setting of that descriptor in the MG.  Thus to retain information
from
the previous setting the MGC must include that information in the new
setting".

Similar statements are made for the Events & Signals Descriptors.

In the case where an MG supports a number of packages, this text is saying
that an MGC
wishing to change data/attributes in one Package in a given Descriptor is
forced to repeat any previous data against any other Packages. This is
perverse. So, can this text be qualified to say that the new Descriptor
replaces only data relating to Packages present in the new/latest message?

Regards,
Wayne.






------------
This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.

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


From daemon@optimus.ietf.org  Thu Jan 24 07:00:30 2002
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 HAA20002
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 07:00:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA24860
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 07:00:32 -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 GAA24341;
	Thu, 24 Jan 2002 06:44:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24310
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 06:44:14 -0500 (EST)
Received: from cvis21.Marconicomms.com (cvis21.marconicomms.com [195.99.244.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19836
	for <megaco@ietf.org>; Thu, 24 Jan 2002 06:44:11 -0500 (EST)
Received: from cvis05.marconicomms.com (unverified) by cvis21.Marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f4359958a4b78474@cvis21.Marconicomms.com> for <megaco@ietf.org>;
 Thu, 24 Jan 2002 11:43:32 +0000
Received: from cvdgwy01.uk.marconicomms.com by cvis05.marconicomms.com with ESMTP
 (8.10.2+Sun/cvms-34) id g0OBhcK04930; Thu, 24 Jan 2002 11:43:38 GMT
Subject: RE: [Megaco] Query about local control descriptor properties
To: taylor@nortelnetworks.com
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
From: "Wayne Cutler" <Wayne.Cutler@marconi.com>
Date: Thu, 24 Jan 2002 11:43:34 +0000
Message-ID: <OFA1731B2B.C2D26F93-ON80256B4B.003A8478@uk.marconicomms.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.8 |June 18, 2001) at
 24/01/2002 11:43:33
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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


Some thoughts (in line) on the following:-

>(2) What does it mean if a package-defined property is no longer specified
>in a modified descriptor?  The answer again could be reversion to default,
>or it could mean that the property is absent, or it could mean that the
>property is present but its value is undefined.  Let's look at the
>implications of these three alternatives.

>(a) If a package-defined property is dropped from LocalControl, it takes
on
>the default value specified by the package or provisioned in the MG.  The
>implicit assumption is that the termination continues to support the
>package.  The question in my mind is how long package support continues.
It
>seems to me that, while some packages may be supported for the entire life
>of a termination, others may apply only during a single call and will have
>unexpected effects if they persist beyond that call.  What do other people
>think about this?

I think that Packages are attributes of a termination and so package
support
should continue as long as the termination is present/exists. For example,
if an ephemeral
termination is destroyed, then there is no longer Package support against
that
termination. MGs don't want to know about "calls" and should not IMO make
assumptions
about lifetimes of Packages. To be safe, it seems best to have the MGC be
explicit in
terms of what it wants an MG to do and the MG just gets on with it. I think
that this means
that the MG may end up holding data/attributes that aren't doing any good -
but is also doing
no harm (e.g.  tdm/ec is left at OFF at the end of a call, and would be
switched back on by the
MGC for the next call/connection).

>(b) The dropped property is no longer present on the termination.  To
>support this interpretation we would need to say for every property that
the
>MG tracks its presence/absence as well as its value if present.  This
>approach says nothing about whether we assume that the package continues
to
>be supported on the termination.

Properties are to do with storing data against a termination. So, I'm
confused by the property no longer being "present". Rather, isn't it a case
that the a given property is always present
for an existing termination but may currently hold a null/default value?

>(c) The dropped property is present but its value is undefined.  I find
this
>unappealing.  Like (a), it implies continued support of the parent
package,
>but doesn't have the advantage of a consistent story for physical
>terminations passing to and from the NULL context.


What about an option d) that would regard an absent Property as meaning
"leave the existing value unchanged"?


As a related question, I note that section 7.1.7 (Local Control Desc.)of
the spec.
says that:-

"A new setting of the LocalControl Descriptor completely replaces the
previous setting of that descriptor in the MG.  Thus to retain information
from
the previous setting the MGC must include that information in the new
setting".

Similar statements are made for the Events & Signals Descriptors.

In the case where an MG supports a number of packages, this text is saying
that an MGC
wishing to change data/attributes in one Package in a given Descriptor is
forced to repeat any previous data against any other Packages. This is
perverse. So, can this text be qualified to say that the new Descriptor
replaces only data relating to Packages present in the new/latest message?

Regards,
Wayne.






------------
This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.

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



From megaco-admin@ietf.org  Thu Jan 24 07:16:48 2002
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 HAA20145
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 07:16:48 -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 HAA25104;
	Thu, 24 Jan 2002 07:08:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25074
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 07:08:22 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20055
	for <megaco@ietf.org>; Thu, 24 Jan 2002 07:08:19 -0500 (EST)
From: guoyou.he@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0OC8Wn14525
	for <megaco@ietf.org>; Thu, 24 Jan 2002 14:08:32 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58a53c0efaac158f21082@esvir01nok.ntc.nokia.com>;
 Thu, 24 Jan 2002 14:08:18 +0200
Received: from esebe002.NOE.Nokia.com ([172.21.138.17]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 24 Jan 2002 14:08:18 +0200
x-mimeole: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 24 Jan 2002 14:08:18 +0200
Message-ID: <7238A5BA4C7C7F4DA40EC7525B364BA43407E4@esebe002.NOE.Nokia.com>
Thread-Topic: indAudsignalListParm
Thread-Index: AcGkz85rljXPhxCnEdaaKABQBMXg3A==
To: <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 24 Jan 2002 12:08:18.0698 (UTC) FILETIME=[CF58E6A0:01C1A4CF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA25075
Subject: [Megaco] indAudsignalListParm
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

Hello,
I have not found the defination on "indAudsignalListParm" on Page 114 of H.248 V2. Has it been defined somewhere?

Bedt regards, Guoyou He


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


From daemon@optimus.ietf.org  Thu Jan 24 07:16:49 2002
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 HAA20154
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 07:16:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA25245
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 07:16:51 -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 HAA25104;
	Thu, 24 Jan 2002 07:08:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25074
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 07:08:22 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20055
	for <megaco@ietf.org>; Thu, 24 Jan 2002 07:08:19 -0500 (EST)
From: guoyou.he@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0OC8Wn14525
	for <megaco@ietf.org>; Thu, 24 Jan 2002 14:08:32 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58a53c0efaac158f21082@esvir01nok.ntc.nokia.com>;
 Thu, 24 Jan 2002 14:08:18 +0200
Received: from esebe002.NOE.Nokia.com ([172.21.138.17]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 24 Jan 2002 14:08:18 +0200
x-mimeole: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 24 Jan 2002 14:08:18 +0200
Message-ID: <7238A5BA4C7C7F4DA40EC7525B364BA43407E4@esebe002.NOE.Nokia.com>
Thread-Topic: indAudsignalListParm
Thread-Index: AcGkz85rljXPhxCnEdaaKABQBMXg3A==
To: <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 24 Jan 2002 12:08:18.0698 (UTC) FILETIME=[CF58E6A0:01C1A4CF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA25075
Subject: [Megaco] indAudsignalListParm
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

Hello,
I have not found the defination on "indAudsignalListParm" on Page 114 of H.248 V2. Has it been defined somewhere?

Bedt regards, Guoyou He


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



From megaco-admin@ietf.org  Thu Jan 24 08:32:35 2002
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 IAA21076
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 08:32:34 -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 IAA27051;
	Thu, 24 Jan 2002 08:18:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27018
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 08:18:08 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20818
	for <megaco@ietf.org>; Thu, 24 Jan 2002 08:18:04 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0ODHaj03640
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:17:36 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58a57bc864ac158f254fc@esvir05nok.ntc.nokia.com>;
 Thu, 24 Jan 2002 15:17:54 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 24 Jan 2002 15:17:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Megaco] indAudsignalListParm
Date: Thu, 24 Jan 2002 15:17:54 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEFB66561@esebe004.NOE.Nokia.com>
Thread-Topic: indAudsignalListParm
Thread-Index: AcGkz85rljXPhxCnEdaaKABQBMXg3AACY/Pw
To: <guoyou.he@nokia.com>, <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 24 Jan 2002 13:17:54.0954 (UTC) FILETIME=[8896FEA0:01C1A4D9]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA27019
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

Hi Guoyou,

IndAudsignalListParm is missing. Please refer to the mail below from Marcello.

Thanks,
Sunesh


-----Original Message-----
From:	ext Marcello Pantaleo (EED) [mailto:Marcello.Pantaleo@eed.ericsson.se]
Sent:	14. January 2002 13:53
To:	Kumra Sunesh (NET/Helsinki)
Cc:	megaco@ietf.org
Subject:	RE: comment in v2

Hi Sunesh,

yes, you're right. indAudsignalListParm is not defined.
I think it should be:
indAudsignalListParm       = indAudsignalRequest
I'll fix it.
Regards,
Marcello


		-----Original Message-----
		From:	He Guoyou (NET-INP/Helsinki) 
		Sent:	24. January 2002 14:08
		To:	Christian.Groves@ericsson.com.au
		Cc:	megaco@ietf.org
		Subject:	[Megaco] indAudsignalListParm

		Hello,
		I have not found the defination on "indAudsignalListParm" on Page 114 of H.248 V2. Has it been defined somewhere?

		Bedt regards, Guoyou He


		_______________________________________________
		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


From daemon@optimus.ietf.org  Thu Jan 24 08:32:40 2002
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 IAA21084
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 08:32:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA27700
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 08:32:38 -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 IAA27051;
	Thu, 24 Jan 2002 08:18:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27018
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 08:18:08 -0500 (EST)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20818
	for <megaco@ietf.org>; Thu, 24 Jan 2002 08:18:04 -0500 (EST)
From: Sunesh.Kumra@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0ODHaj03640
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:17:36 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58a57bc864ac158f254fc@esvir05nok.ntc.nokia.com>;
 Thu, 24 Jan 2002 15:17:54 +0200
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 24 Jan 2002 15:17:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Megaco] indAudsignalListParm
Date: Thu, 24 Jan 2002 15:17:54 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEFB66561@esebe004.NOE.Nokia.com>
Thread-Topic: indAudsignalListParm
Thread-Index: AcGkz85rljXPhxCnEdaaKABQBMXg3AACY/Pw
To: <guoyou.he@nokia.com>, <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 24 Jan 2002 13:17:54.0954 (UTC) FILETIME=[8896FEA0:01C1A4D9]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA27019
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

Hi Guoyou,

IndAudsignalListParm is missing. Please refer to the mail below from Marcello.

Thanks,
Sunesh


-----Original Message-----
From:	ext Marcello Pantaleo (EED) [mailto:Marcello.Pantaleo@eed.ericsson.se]
Sent:	14. January 2002 13:53
To:	Kumra Sunesh (NET/Helsinki)
Cc:	megaco@ietf.org
Subject:	RE: comment in v2

Hi Sunesh,

yes, you're right. indAudsignalListParm is not defined.
I think it should be:
indAudsignalListParm       = indAudsignalRequest
I'll fix it.
Regards,
Marcello


		-----Original Message-----
		From:	He Guoyou (NET-INP/Helsinki) 
		Sent:	24. January 2002 14:08
		To:	Christian.Groves@ericsson.com.au
		Cc:	megaco@ietf.org
		Subject:	[Megaco] indAudsignalListParm

		Hello,
		I have not found the defination on "indAudsignalListParm" on Page 114 of H.248 V2. Has it been defined somewhere?

		Bedt regards, Guoyou He


		_______________________________________________
		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



From megaco-admin@ietf.org  Thu Jan 24 10:29:07 2002
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 KAA23646
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 10:29:07 -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 KAA02741;
	Thu, 24 Jan 2002 10:18:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02712
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 10:18:16 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23485
	for <megaco@ietf.org>; Thu, 24 Jan 2002 10:18:00 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0OFGab05198
	for <megaco@ietf.org>; Thu, 24 Jan 2002 20:46:37 +0530 (IST)
Received: from wipro.com ([192.168.178.139]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQG7ST01.UBT for <megaco@ietf.org>; Thu, 24 Jan 2002
          20:47:17 +0530 
Message-ID: <3C502530.5C804252@wipro.com>
Date: Thu, 24 Jan 2002 20:46:00 +0530
From: "Shashi Kumar" <shashi.kumar@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "'megaco@ietf.org'" <megaco@ietf.org>
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8"
Subject: [Megaco] StreamID and interconnect
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi List,

   We have following question's on StreamID and connections of streams.

1.  Having a same stream ID is the only way to indicate which media
flows are interconnected?
2.  Is StreamID generation is implementation dependent?
3.  Can a Termination support two streams with same StreamID?


Thanks,
Shashi
Wipro Technologies
Bangalore

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8--

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


From daemon@ns.ietf.org  Thu Jan 24 10:29:08 2002
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 KAA23656
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 10:29:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02978
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 10:29:11 -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 KAA02741;
	Thu, 24 Jan 2002 10:18:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02712
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 10:18:16 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23485
	for <megaco@ietf.org>; Thu, 24 Jan 2002 10:18:00 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0OFGab05198
	for <megaco@ietf.org>; Thu, 24 Jan 2002 20:46:37 +0530 (IST)
Received: from wipro.com ([192.168.178.139]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQG7ST01.UBT for <megaco@ietf.org>; Thu, 24 Jan 2002
          20:47:17 +0530 
Message-ID: <3C502530.5C804252@wipro.com>
Date: Thu, 24 Jan 2002 20:46:00 +0530
From: "Shashi Kumar" <shashi.kumar@wipro.com>
Organization: Wipro Technologies
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "'megaco@ietf.org'" <megaco@ietf.org>
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8"
Subject: [Megaco] StreamID and interconnect
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


This is a multi-part message in MIME format.

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi List,

   We have following question's on StreamID and connections of streams.

1.  Having a same stream ID is the only way to indicate which media
flows are interconnected?
2.  Is StreamID generation is implementation dependent?
3.  Can a Termination support two streams with same StreamID?


Thanks,
Shashi
Wipro Technologies
Bangalore

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-8a624bb7-10d6-11d6-a941-00b0d0d06be8--

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



From megaco-admin@ietf.org  Thu Jan 24 10:45:41 2002
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 KAA24146
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 10:45:41 -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 KAA03656;
	Thu, 24 Jan 2002 10:38:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03624
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 10:38:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23900
	for <megaco@ietf.org>; Thu, 24 Jan 2002 10:38:13 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OFbic05749;
	Thu, 24 Jan 2002 10:37:45 -0500 (EST)
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 g0OFbht04485;
	Thu, 24 Jan 2002 10:37:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ5QAC>; Thu, 24 Jan 2002 10:37:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEFC@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Thu, 24 Jan 2002 10:37:47 -0500
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

You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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


From daemon@ns.ietf.org  Thu Jan 24 10:45:42 2002
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 KAA24155
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 10:45:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA03996
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 10:45:43 -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 KAA03656;
	Thu, 24 Jan 2002 10:38:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03624
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 10:38:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23900
	for <megaco@ietf.org>; Thu, 24 Jan 2002 10:38:13 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OFbic05749;
	Thu, 24 Jan 2002 10:37:45 -0500 (EST)
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 g0OFbht04485;
	Thu, 24 Jan 2002 10:37:43 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ5QAC>; Thu, 24 Jan 2002 10:37:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AEFC@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Thu, 24 Jan 2002 10:37:47 -0500
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

You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 24 13:53:08 2002
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 NAA02094
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 13:53:08 -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 NAA14428;
	Thu, 24 Jan 2002 13:44:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14398
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 13:44:01 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01770
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OIhOc13936
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:25 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OIhM504702
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ55X5>; Thu, 24 Jan 2002 13:43:25 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF02@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shashi Kumar'" <shashi.kumar@wipro.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] StreamID and interconnect
Date: Thu, 24 Jan 2002 13:43:27 -0500
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

Replies below.

-----Original Message-----
From: Shashi Kumar [mailto:shashi.kumar@wipro.com]
Sent: Thursday, January 24, 2002 10:16 AM
To: 'megaco@ietf.org'
Subject: [Megaco] StreamID and interconnect


Hi List,

   We have following question's on StreamID and connections of streams.

1.  Having a same stream ID is the only way to indicate which media
flows are interconnected?
[PTT]  Yes, that is correct.

2.  Is StreamID generation is implementation dependent?
[PTT]  Yes.  The protocol defines the interface between the MGC and the MG.
How the MGC chooses to use that interface is up to the implementation.

3.  Can a Termination support two streams with same StreamID?
[PTT]  No.


Thanks,
Shashi
Wipro Technologies
Bangalore

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


From daemon@ns.ietf.org  Thu Jan 24 13:53:08 2002
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 NAA02102
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 13:53:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14693
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 13:53:10 -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 NAA14428;
	Thu, 24 Jan 2002 13:44:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14398
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 13:44:01 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01770
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OIhOc13936
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:25 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OIhM504702
	for <megaco@ietf.org>; Thu, 24 Jan 2002 13:43:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ55X5>; Thu, 24 Jan 2002 13:43:25 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF02@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Shashi Kumar'" <shashi.kumar@wipro.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] StreamID and interconnect
Date: Thu, 24 Jan 2002 13:43:27 -0500
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

Replies below.

-----Original Message-----
From: Shashi Kumar [mailto:shashi.kumar@wipro.com]
Sent: Thursday, January 24, 2002 10:16 AM
To: 'megaco@ietf.org'
Subject: [Megaco] StreamID and interconnect


Hi List,

   We have following question's on StreamID and connections of streams.

1.  Having a same stream ID is the only way to indicate which media
flows are interconnected?
[PTT]  Yes, that is correct.

2.  Is StreamID generation is implementation dependent?
[PTT]  Yes.  The protocol defines the interface between the MGC and the MG.
How the MGC chooses to use that interface is up to the implementation.

3.  Can a Termination support two streams with same StreamID?
[PTT]  No.


Thanks,
Shashi
Wipro Technologies
Bangalore

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



From megaco-admin@ietf.org  Thu Jan 24 16:01:23 2002
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 QAA05737
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 16:01:23 -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 PAA21888;
	Thu, 24 Jan 2002 15:53:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21839
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 15:53:05 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05374
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:53:01 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OKqXh09587
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:52:33 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OKqVP17806
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:52:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ59KA>; Thu, 24 Jan 2002 15:52:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF04@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 24 Jan 2002 15:52:34 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Megaco Contribution Regarding H.248v2
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

I am sending the following contribution to the ITU-T on behalf of Megaco.
This will be in addition to any points Terry Anderson and Marcello Pantaleo
pick up in their Editors' drafts.

TITLE:	Communication From IETF Megaco Working Group: Comments On H.248v2
___________________


INTRODUCTION

This communication conveys observations on H.248 version 2 which the IETF
Megaco Working Group would like Q. 3/16 to act upon before approving the
updated Recommendation.  The Working Group has identified two points:

·	The Working Group consensus is that the introduction of context
packages would be premature at this point, and accordingly they should not
be included in H.248v2.

·	On a more specific level, the new table in section 7.2.9 erroneously
indicates that an audit with contextID ALL always returns a response which
is the union of responses across all contexts.  This is inconsistent with
existing text in section 7.2.5, which requires specific tagging ("W-" in the
text encoding) to obtain a union of responses across individual entities.

CONTEXT PACKAGES

The Megaco Working Group asks that the proposal to allow context packages be
removed from the H.248v2 text.  The basic concern is the potential impact on
the coherence of the protocol.  There is a view that no requirement has yet
been demonstrated for further context properties, let alone an open-ended
capability to define such properties.

The Megaco request requires the following changes to H.248v2 (as reflected
in TD-47 out of the Dublin meeting):

·	delete final bullet of section 6.1.1
·	delete final sentence of first paragraph of section 6.2.3
·	delete second sentence of second paragraph of section 6.2.3
·	delete the phrase "or Context" from the last sentence of second
paragraph of section 6.2.3
·	delete section 7.1.19 Context Attribute Descriptor and renumber the
subsequent section(s) accordingly
·	in section 7.2.9, remove references to ContextAttribute Descriptor
as follows:
o	in the third paragraph, amend the final sentence to say "There are
two types of audit."
o	in the paragraphs beginning "Value Audit:" and "Capabilities
Audit:", delete the phrase "the ContextAttribute Descriptor or"
o	delete the paragraph beginning "Packages Audit"
o	delete the Audit Packages column of the table
·	delete the phrase "and contexts" in the first paragraph of section
12
·	delete the sentence beginning "ContextAttribute is for ..." and also
the final sentence of the paragraph explaining "Defined in:" in section
12.1.2
·	delete the final sentence of the paragraph explaining
"Characteristics:" in section 12.1.2
·	in Annex A:
o	delete the contextProp and contextPackages components added after
the extension marker in the ContextRequest production
o	delete the contextPropAud, contextAttrDescriptorCapAud,
contextPropCapAud, and contextPackagesAud components added after the
extension marker in the ContextAttrAuditRequest production
·	in Annex B:
o	delete the contextAttrDescriptor and packagesDescriptor terms from
the contextProperty production
o	delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
IndAudContextAttrCap, and ContextAttrPackages terms from the
contextAuditProperties production
o	delete the IndAudContextAttrCap, ContextAttrPackages, and
ContextAttrDescriptorCapAud productions
o	delete the contextAttrDescriptor production
o	delete the ContextAttrToken, ContextAudCapToken,
ContextAudDescriptorToken, and ContextAudValToken productions

CONTEXT AUDITS WITH WILDCARD

New text in section 7.2.9 indicates the results expected when context
properties are audited.  One case dealt with is that when the contextID
specified is ALL.  The table indicates that the audit response will be the
union of results over all contexts.  This is inconsistent with section
7.2.5, which allows the MGC explicit control over the form of the response.
The default response is that results are listed in multiple actionReplys.  A
union of responses is obtained only if the "W-" tag or the binary equivalent
is used.
Megaco requests that the table of section 7.2.9 be corrected to indicate
that results for an ALL contextID are presented through an actionReply per
context unless the W- tag or its binary equivalent is used.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@ns.ietf.org  Thu Jan 24 16:01:24 2002
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 QAA05748
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 16:01:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA22681
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 16:01:27 -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 PAA21888;
	Thu, 24 Jan 2002 15:53:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21839
	for <megaco@ns.ietf.org>; Thu, 24 Jan 2002 15:53:05 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05374
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:53:01 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OKqXh09587
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:52:33 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0OKqVP17806
	for <megaco@ietf.org>; Thu, 24 Jan 2002 15:52:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ59KA>; Thu, 24 Jan 2002 15:52:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF04@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 24 Jan 2002 15:52:34 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Megaco Contribution Regarding H.248v2
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

I am sending the following contribution to the ITU-T on behalf of Megaco.
This will be in addition to any points Terry Anderson and Marcello Pantaleo
pick up in their Editors' drafts.

TITLE:	Communication From IETF Megaco Working Group: Comments On H.248v2
___________________


INTRODUCTION

This communication conveys observations on H.248 version 2 which the IETF
Megaco Working Group would like Q. 3/16 to act upon before approving the
updated Recommendation.  The Working Group has identified two points:

·	The Working Group consensus is that the introduction of context
packages would be premature at this point, and accordingly they should not
be included in H.248v2.

·	On a more specific level, the new table in section 7.2.9 erroneously
indicates that an audit with contextID ALL always returns a response which
is the union of responses across all contexts.  This is inconsistent with
existing text in section 7.2.5, which requires specific tagging ("W-" in the
text encoding) to obtain a union of responses across individual entities.

CONTEXT PACKAGES

The Megaco Working Group asks that the proposal to allow context packages be
removed from the H.248v2 text.  The basic concern is the potential impact on
the coherence of the protocol.  There is a view that no requirement has yet
been demonstrated for further context properties, let alone an open-ended
capability to define such properties.

The Megaco request requires the following changes to H.248v2 (as reflected
in TD-47 out of the Dublin meeting):

·	delete final bullet of section 6.1.1
·	delete final sentence of first paragraph of section 6.2.3
·	delete second sentence of second paragraph of section 6.2.3
·	delete the phrase "or Context" from the last sentence of second
paragraph of section 6.2.3
·	delete section 7.1.19 Context Attribute Descriptor and renumber the
subsequent section(s) accordingly
·	in section 7.2.9, remove references to ContextAttribute Descriptor
as follows:
o	in the third paragraph, amend the final sentence to say "There are
two types of audit."
o	in the paragraphs beginning "Value Audit:" and "Capabilities
Audit:", delete the phrase "the ContextAttribute Descriptor or"
o	delete the paragraph beginning "Packages Audit"
o	delete the Audit Packages column of the table
·	delete the phrase "and contexts" in the first paragraph of section
12
·	delete the sentence beginning "ContextAttribute is for ..." and also
the final sentence of the paragraph explaining "Defined in:" in section
12.1.2
·	delete the final sentence of the paragraph explaining
"Characteristics:" in section 12.1.2
·	in Annex A:
o	delete the contextProp and contextPackages components added after
the extension marker in the ContextRequest production
o	delete the contextPropAud, contextAttrDescriptorCapAud,
contextPropCapAud, and contextPackagesAud components added after the
extension marker in the ContextAttrAuditRequest production
·	in Annex B:
o	delete the contextAttrDescriptor and packagesDescriptor terms from
the contextProperty production
o	delete the IndAudcontextAttrDescriptor, ContextAttrDescriptorCapAud,
IndAudContextAttrCap, and ContextAttrPackages terms from the
contextAuditProperties production
o	delete the IndAudContextAttrCap, ContextAttrPackages, and
ContextAttrDescriptorCapAud productions
o	delete the contextAttrDescriptor production
o	delete the ContextAttrToken, ContextAudCapToken,
ContextAudDescriptorToken, and ContextAudValToken productions

CONTEXT AUDITS WITH WILDCARD

New text in section 7.2.9 indicates the results expected when context
properties are audited.  One case dealt with is that when the contextID
specified is ALL.  The table indicates that the audit response will be the
union of results over all contexts.  This is inconsistent with section
7.2.5, which allows the MGC explicit control over the form of the response.
The default response is that results are listed in multiple actionReplys.  A
union of responses is obtained only if the "W-" tag or the binary equivalent
is used.
Megaco requests that the table of section 7.2.9 be corrected to indicate
that results for an ALL contextID are presented through an actionReply per
context unless the W- tag or its binary equivalent is used.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Thu Jan 24 23:57:42 2002
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 XAA16355
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 23:57:42 -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 XAA14258;
	Thu, 24 Jan 2002 23:43:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA14229
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 23:43:56 -0500 (EST)
Received: from mailweb10.rediffmail.com ([203.199.83.22])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA16186
	for <megaco@ietf.org>; Thu, 24 Jan 2002 23:43:50 -0500 (EST)
Received: (qmail 25681 invoked by uid 510); 25 Jan 2002 04:44:55 -0000
Date: 25 Jan 2002 04:44:55 -0000
Message-ID: <20020125044455.25680.qmail@mailweb10.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 25 Jan 2002 04:44:55 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA14230
Subject: [Megaco] ****ERROR condition
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


hi 

    If an optional command is failed we can go ahead with processing with other commands according to RFC. But if one optional command fails, how do we specify it in the response..? Error descriptor is available only in the action level. we do not have error descriptor in command level. So if an optional command fails, we cannot specify error in the reply. But at the same time if we do not specify error condition, MGC will think that the command is success. How do we handle this situation.. ?

   # What for this Notify reply is used.. ?

regs
vdy 


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


From daemon@optimus.ietf.org  Thu Jan 24 23:57:43 2002
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 XAA16364
	for <megaco-archive@odin.ietf.org>; Thu, 24 Jan 2002 23:57:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA14458
	for megaco-archive@odin.ietf.org; Thu, 24 Jan 2002 23:57:47 -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 XAA14258;
	Thu, 24 Jan 2002 23:43:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA14229
	for <megaco@optimus.ietf.org>; Thu, 24 Jan 2002 23:43:56 -0500 (EST)
Received: from mailweb10.rediffmail.com ([203.199.83.22])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA16186
	for <megaco@ietf.org>; Thu, 24 Jan 2002 23:43:50 -0500 (EST)
Received: (qmail 25681 invoked by uid 510); 25 Jan 2002 04:44:55 -0000
Date: 25 Jan 2002 04:44:55 -0000
Message-ID: <20020125044455.25680.qmail@mailweb10.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 25 Jan 2002 04:44:55 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA14230
Subject: [Megaco] ****ERROR condition
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


hi 

    If an optional command is failed we can go ahead with processing with other commands according to RFC. But if one optional command fails, how do we specify it in the response..? Error descriptor is available only in the action level. we do not have error descriptor in command level. So if an optional command fails, we cannot specify error in the reply. But at the same time if we do not specify error condition, MGC will think that the command is success. How do we handle this situation.. ?

   # What for this Notify reply is used.. ?

regs
vdy 


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



From megaco-admin@ietf.org  Fri Jan 25 00:54:15 2002
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 AAA17262
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 00:54:15 -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 AAA16606;
	Fri, 25 Jan 2002 00:42:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA16575
	for <megaco@optimus.ietf.org>; Fri, 25 Jan 2002 00:42:38 -0500 (EST)
Received: from web13006.mail.yahoo.com (web13006.mail.yahoo.com [216.136.174.16])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17085
	for <megaco@ietf.org>; Fri, 25 Jan 2002 00:42:35 -0500 (EST)
Message-ID: <20020125054236.23733.qmail@web13006.mail.yahoo.com>
Received: from [203.199.199.250] by web13006.mail.yahoo.com via HTTP; Thu, 24 Jan 2002 21:42:36 PST
Date: Thu, 24 Jan 2002 21:42:36 -0800 (PST)
From: James L <james_lfr@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Megaco Mib draft reg.
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

Hi List,
 
I am looking for MEGCO-MIB draft and  found that the
existing one on IETF site expired by Nov 2001.
 
Any update is coming up soon ?
 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-02.txt
 
Regards
James

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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


From daemon@optimus.ietf.org  Fri Jan 25 00:54:16 2002
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 AAA17273
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 00:54:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA17072
	for megaco-archive@odin.ietf.org; Fri, 25 Jan 2002 00:54: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 AAA16606;
	Fri, 25 Jan 2002 00:42:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA16575
	for <megaco@optimus.ietf.org>; Fri, 25 Jan 2002 00:42:38 -0500 (EST)
Received: from web13006.mail.yahoo.com (web13006.mail.yahoo.com [216.136.174.16])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17085
	for <megaco@ietf.org>; Fri, 25 Jan 2002 00:42:35 -0500 (EST)
Message-ID: <20020125054236.23733.qmail@web13006.mail.yahoo.com>
Received: from [203.199.199.250] by web13006.mail.yahoo.com via HTTP; Thu, 24 Jan 2002 21:42:36 PST
Date: Thu, 24 Jan 2002 21:42:36 -0800 (PST)
From: James L <james_lfr@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Megaco Mib draft reg.
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

Hi List,
 
I am looking for MEGCO-MIB draft and  found that the
existing one on IETF site expired by Nov 2001.
 
Any update is coming up soon ?
 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-mib-02.txt
 
Regards
James

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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



From megaco-admin@ietf.org  Fri Jan 25 08:54:00 2002
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 IAA02672
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 08:53:55 -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 IAA14792;
	Fri, 25 Jan 2002 08:42:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA14761
	for <megaco@optimus.ietf.org>; Fri, 25 Jan 2002 08:42:18 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02370
	for <megaco@ietf.org>; Fri, 25 Jan 2002 08:42:13 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0PDgDB13187;
	Fri, 25 Jan 2002 08:42:13 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA05891;
	Fri, 25 Jan 2002 08:42:12 -0500 (EST)
Message-ID: <3C515FF9.FB3675C8@lucent.com>
Date: Fri, 25 Jan 2002 08:39:06 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ****ERROR condition
References: <20020125044455.25680.qmail@mailweb10.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------915367639E44D2F121EEE904"
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

This is a multi-part message in MIME format.
--------------915367639E44D2F121EEE904
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

There IS an errorDescriptor at in every command Reply (as long as the command name is parsed - the exception is being fixed.  See recent discussion about open issue #4: Doubt regarding sending Error in Transaction Reply).  For example, ammsReply contains terminationAudit which contains auditReturnParameter which can be errorDescriptor.

vidya g wrote:

> hi
>
>     If an optional command is failed we can go ahead with processing with other commands according to RFC. But if one optional command fails, how do we specify it in the response..? Error descriptor is available only in the action level. we do not have error descriptor in command level. So if an optional command fails, we cannot specify error in the reply. But at the same time if we do not specify error condition, MGC will think that the command is success. How do we handle this situation.. ?
>
>    # What for this Notify reply is used.. ?
>
> regs
> vdy
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------915367639E44D2F121EEE904
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------915367639E44D2F121EEE904--


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


From daemon@optimus.ietf.org  Fri Jan 25 08:54:01 2002
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 IAA02682
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 08:54:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA15120
	for megaco-archive@odin.ietf.org; Fri, 25 Jan 2002 08:54:04 -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 IAA14792;
	Fri, 25 Jan 2002 08:42:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA14761
	for <megaco@optimus.ietf.org>; Fri, 25 Jan 2002 08:42:18 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02370
	for <megaco@ietf.org>; Fri, 25 Jan 2002 08:42:13 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0PDgDB13187;
	Fri, 25 Jan 2002 08:42:13 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA05891;
	Fri, 25 Jan 2002 08:42:12 -0500 (EST)
Message-ID: <3C515FF9.FB3675C8@lucent.com>
Date: Fri, 25 Jan 2002 08:39:06 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ****ERROR condition
References: <20020125044455.25680.qmail@mailweb10.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------915367639E44D2F121EEE904"
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

This is a multi-part message in MIME format.
--------------915367639E44D2F121EEE904
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

There IS an errorDescriptor at in every command Reply (as long as the command name is parsed - the exception is being fixed.  See recent discussion about open issue #4: Doubt regarding sending Error in Transaction Reply).  For example, ammsReply contains terminationAudit which contains auditReturnParameter which can be errorDescriptor.

vidya g wrote:

> hi
>
>     If an optional command is failed we can go ahead with processing with other commands according to RFC. But if one optional command fails, how do we specify it in the response..? Error descriptor is available only in the action level. we do not have error descriptor in command level. So if an optional command fails, we cannot specify error in the reply. But at the same time if we do not specify error condition, MGC will think that the command is success. How do we handle this situation.. ?
>
>    # What for this Notify reply is used.. ?
>
> regs
> vdy
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------915367639E44D2F121EEE904
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------915367639E44D2F121EEE904--


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



From megaco-admin@ietf.org  Fri Jan 25 14:24:31 2002
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 OAA11818
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 14:24:27 -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 OAA04024;
	Fri, 25 Jan 2002 14:15:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA03995
	for <megaco@ns.ietf.org>; Fri, 25 Jan 2002 14:15:33 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11523
	for <megaco@ietf.org>; Fri, 25 Jan 2002 14:15:27 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0PJElg19840;
	Fri, 25 Jan 2002 14:14:51 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAW10N>; Fri, 25 Jan 2002 14:14:48 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01B1BA5A@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: PSK Chakravarthi <pchakrav@ssd.usa.alcatel.com>, megaco@ietf.org,
        Al Varney <varney@ieee.org>
Subject: RE: [Megaco] Megaco CAS
Date: Fri, 25 Jan 2002 14:14:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A5D4.90037500"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A5D4.90037500
Content-Type: text/plain;
	charset="iso-8859-1"

All,

We have a new version of the draft that is awaiting IANA registration before
I publish it again.  We will include the coding parameter as optional, as
suggested.

As to other comments in the thread... the package does not define the
granularity of any provisioning (either per-term, or per-MG).  This was
worded intentionally to avoid imposing an implementation upon an MG.  For
certain items, it should be apparent to the vendor what type of provisioning
is appropriate, given the implementation. I can envision per-MG, per-DS0, or
even per-group-of-DS0s.

And, the statement about attempting to force DTMF over an MF trunk is
certainly outside the scope of CAS.  However, the addition of the coding
parameter will allow this behavior, if desired.

Kevin

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Thursday, January 10, 2002 3:17 AM
To: megaco@ietf.org; Al Varney
Subject: Re: [Megaco] Megaco CAS


Al Varney,

I think optional is OK.  Default coding type for a termination should be
provisioned in MG.  If MGC want to override, it can use optional parameter
"ac".

Thanks
Chak
----- Original Message -----
From: "Al Varney" <varney@ieee.org>
To: <megaco@ietf.org>
Sent: Wednesday, January 09, 2002 10:18 PM
Subject: Re: [Megaco] Megaco CAS


> Chak,
>     At first, I thought the Description of "provisioned" frequency,
> cadence, etc. could be clarified as a per-trunk attribute (not per MG, as
> some might read it).  That is, MF trunks always used MF signaling, etc.
On
> further reflection, this is insufficient to emulate some forms of older
> signaling used in the USA.  For example, some circuits signal using Dial
> Pulse in a first stage, followed by MF in the second.  Also, it might be
> useful to force DTMF signaling over an MF trunk which is already connected
> on a call (although that goes beyond the function typically associated
with
> the acronym "CAS").
>
>     So I'm agreeing with you, with a small suggestion below:
>
> At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
> >I think we can have another parameter as given below:
> >
> >         Parameter Name: Address Type
> >         ParameterID: at (0x0003)
> >         Description: Specifies Type of address digits.
> >         Type: enumeration
> >         Possible Values:
> >         "DTMF"  (0x0000)  DTMF Digits
> >         "MF"       (0x0001)  MF Digits
> >         "DP"        (0x0002)  Dial Pulse Digits
>
>     It might be less confusing if the word "Type" was not used in the Name
> or Description, since it is part of the meta-language of MEGACO
> packages.  I used "Coding" below, but another word might be better.  Also,
> you offered no default text in the Description -- did you really want
> "Address Type" to be included in every use of "addr"?
>
>       Alternative Name/ID/Description for consideration:
>   Parameter Name: Address Coding
>   ParameterID: ac (0x0003)
>   Description: Specifies the coding of Digit String parameter
>            in tones or DC pulses.  Address Coding is optional;
>            if not provided, the MG uses the value provisioned
>            as an attribute of the circuit associated with the
>            signal.
>
>     Would it be useful to mention an error case if Address Coding is not
> present and the "circuit" has no 'ac' value provisioned?  (For example,
> could CAS package be used to signal over an ephemeral?)
>
>     On second thought, having 'ac' optional might be a mistake.  It forces
> the MGC to "know" the coding for every circuit.  (The
> provisioned-per-MG-circuit option allows the MGC to be ignorant of the
> coding.)  I think it unlikely that the MGC could be ignorant of MF vs.
DTMF
> vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is
> just asking for an error.
>
> Al Varney - varney@ieee.org
>
> > > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > > Hi List,
> > > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > > 6.4.5
> > >     Signal Name: Address
> > >     SignalID: addr (0x0005)
> > >     Description: Applies the address signals in the form of either
> > >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> > >           frequency, cadence, duration and amplitude values for the
> > >           multi-frequency tones that convey the address information
are
> > >           provisioned in the MG.
> > >     Signal Type: (BR) Brief
> > >     Duration: Provisioned
> > >     Additional Parameters:
> > >         Parameter Name: Digit String
> > >         ParameterID: ds (0x0001)
> > >         Description: The digit string that needs to be sent as address
> > >           signals.
> > >         Type: string of digits.
> > >         Possible Values: a sequence of the characters "0" through "9"
> > >           as well as "A" through "H" ("A" through "H" used for MF
> > >           signalling - refer to the symbols defined for the digit map
> > >           in the MF Tone Detection package).
> > >         Parameter Name: Address Delay
> > >         ParameterID: ad (0x0002)
> > >         Description: Specifies a timed delay that is applied prior to
> > >           signalling the address. The address delay is optional. If
the
> > >           address delay parameter is not provided, the MG uses the
> > >           provisioned value by default.
> > >         Type: integer
> > >         Possible Values: 0 and up in milliseconds
> > >
> > > Question:
> > > MGC can instruct gateway to out pulse digits either in DTMF or MF or
dial
> > > pulse.
> > > How MGC can tell gateway about the mode of the digits is MF or DTMF or
Dial
> > > Pulse?
>
>
> _______________________________________________
> 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

------_=_NextPart_001_01C1A5D4.90037500
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Megaco CAS</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>We have a new version of the draft that is awaiting =
IANA registration before I publish it again.&nbsp; We will include the =
coding parameter as optional, as suggested.</FONT></P>

<P><FONT SIZE=3D2>As to other comments in the thread... the package =
does not define the granularity of any provisioning (either per-term, =
or per-MG).&nbsp; This was worded intentionally to avoid imposing an =
implementation upon an MG.&nbsp; For certain items, it should be =
apparent to the vendor what type of provisioning is appropriate, given =
the implementation. I can envision per-MG, per-DS0, or even =
per-group-of-DS0s.</FONT></P>

<P><FONT SIZE=3D2>And, the statement about attempting to force DTMF =
over an MF trunk is certainly outside the scope of CAS.&nbsp; However, =
the addition of the coding parameter will allow this behavior, if =
desired.</FONT></P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: PSK Chakravarthi [<A =
HREF=3D"mailto:pchakrav@ssd.usa.alcatel.com">mailto:pchakrav@ssd.usa.alc=
atel.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 10, 2002 3:17 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org; Al Varney</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Megaco CAS</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Al Varney,</FONT>
</P>

<P><FONT SIZE=3D2>I think optional is OK.&nbsp; Default coding type for =
a termination should be</FONT>
<BR><FONT SIZE=3D2>provisioned in MG.&nbsp; If MGC want to override, it =
can use optional parameter &quot;ac&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks</FONT>
<BR><FONT SIZE=3D2>Chak</FONT>
<BR><FONT SIZE=3D2>----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>From: &quot;Al Varney&quot; =
&lt;varney@ieee.org&gt;</FONT>
<BR><FONT SIZE=3D2>To: &lt;megaco@ietf.org&gt;</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 09, 2002 10:18 PM</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Megaco CAS</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; Chak,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; At first, I thought the =
Description of &quot;provisioned&quot; frequency,</FONT>
<BR><FONT SIZE=3D2>&gt; cadence, etc. could be clarified as a per-trunk =
attribute (not per MG, as</FONT>
<BR><FONT SIZE=3D2>&gt; some might read it).&nbsp; That is, MF trunks =
always used MF signaling, etc.&nbsp; On</FONT>
<BR><FONT SIZE=3D2>&gt; further reflection, this is insufficient to =
emulate some forms of older</FONT>
<BR><FONT SIZE=3D2>&gt; signaling used in the USA.&nbsp; For example, =
some circuits signal using Dial</FONT>
<BR><FONT SIZE=3D2>&gt; Pulse in a first stage, followed by MF in the =
second.&nbsp; Also, it might be</FONT>
<BR><FONT SIZE=3D2>&gt; useful to force DTMF signaling over an MF trunk =
which is already connected</FONT>
<BR><FONT SIZE=3D2>&gt; on a call (although that goes beyond the =
function typically associated with</FONT>
<BR><FONT SIZE=3D2>&gt; the acronym &quot;CAS&quot;).</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; So I'm agreeing with =
you, with a small suggestion below:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; At 12:56 PM 1/9/02 +0530, PSK Chakravarthi =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I think we can have another parameter as =
given below:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Address Type</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: at =
(0x0003)</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Specifies Type of address digits.</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
enumeration</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible =
Values:</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;DTMF&quot;&nbsp; (0x0000)&nbsp; DTMF Digits</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;MF&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0x0001)&nbsp; MF =
Digits</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;DP&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0x0002)&nbsp; =
Dial Pulse Digits</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; It might be less =
confusing if the word &quot;Type&quot; was not used in the Name</FONT>
<BR><FONT SIZE=3D2>&gt; or Description, since it is part of the =
meta-language of MEGACO</FONT>
<BR><FONT SIZE=3D2>&gt; packages.&nbsp; I used &quot;Coding&quot; =
below, but another word might be better.&nbsp; Also,</FONT>
<BR><FONT SIZE=3D2>&gt; you offered no default text in the Description =
-- did you really want</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Address Type&quot; to be included in =
every use of &quot;addr&quot;?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alternative =
Name/ID/Description for consideration:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Parameter Name: Address =
Coding</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; ParameterID: ac (0x0003)</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Description: Specifies the coding =
of Digit String parameter</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; in tones or DC pulses.&nbsp; Address Coding is optional;</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; if not provided, the MG uses the value provisioned</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; as an attribute of the circuit associated with the</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; signal.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Would it be useful to =
mention an error case if Address Coding is not</FONT>
<BR><FONT SIZE=3D2>&gt; present and the &quot;circuit&quot; has no 'ac' =
value provisioned?&nbsp; (For example,</FONT>
<BR><FONT SIZE=3D2>&gt; could CAS package be used to signal over an =
ephemeral?)</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; On second thought, =
having 'ac' optional might be a mistake.&nbsp; It forces</FONT>
<BR><FONT SIZE=3D2>&gt; the MGC to &quot;know&quot; the coding for =
every circuit.&nbsp; (The</FONT>
<BR><FONT SIZE=3D2>&gt; provisioned-per-MG-circuit option allows the =
MGC to be ignorant of the</FONT>
<BR><FONT SIZE=3D2>&gt; coding.)&nbsp; I think it unlikely that the MGC =
could be ignorant of MF vs. DTMF</FONT>
<BR><FONT SIZE=3D2>&gt; vs. DP for a given circuit, and provisioning in =
2 places (MG and MGC) is</FONT>
<BR><FONT SIZE=3D2>&gt; just asking for an error.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Al Varney - varney@ieee.org</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: PSK Chakravarthi [<A =
HREF=3D"mailto:pchakrav@ssd.usa.alcatel.com">mailto:pchakrav@ssd.usa.alc=
atel.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Hi List,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; As per =
draft-manyfolks-megaco-caspackage-01.txt Section</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 6.4.5</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Signal Name: =
Address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; SignalID: =
addr (0x0005)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Applies the address signals in the form of either</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; DTMF, dial-pulse or MF-tones on the trunk. The =
actual</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
frequency, cadence, duration and amplitude values for the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multi-frequency tones that convey the address information are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
provisioned in the MG.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Signal Type: =
(BR) Brief</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Duration: =
Provisioned</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Additional =
Parameters:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Digit String</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ds =
(0x0001)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: The =
digit string that needs to be sent as address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signals.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: string of =
digits.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: a =
sequence of the characters &quot;0&quot; through &quot;9&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as =
well as &quot;A&quot; through &quot;H&quot; (&quot;A&quot; through =
&quot;H&quot; used for MF</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signalling - refer to the symbols defined for the digit map</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the =
MF Tone Detection package).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Address Delay</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ad =
(0x0002)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Specifies a timed delay that is applied prior to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signalling the address. The address delay is optional. If the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
address delay parameter is not provided, the MG uses the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
provisioned value by default.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
integer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: 0 =
and up in milliseconds</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Question:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; MGC can instruct gateway to out pulse =
digits either in DTMF or MF or dial</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pulse.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; How MGC can tell gateway about the =
mode of the digits is MF or DTMF or</FONT>
<BR><FONT SIZE=3D2>Dial</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Pulse?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A5D4.90037500--

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


From daemon@ns.ietf.org  Fri Jan 25 14:24:32 2002
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 OAA11834
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 14:24:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA04422
	for megaco-archive@odin.ietf.org; Fri, 25 Jan 2002 14:24:34 -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 OAA04024;
	Fri, 25 Jan 2002 14:15:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA03995
	for <megaco@ns.ietf.org>; Fri, 25 Jan 2002 14:15:33 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11523
	for <megaco@ietf.org>; Fri, 25 Jan 2002 14:15:27 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0PJElg19840;
	Fri, 25 Jan 2002 14:14:51 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAW10N>; Fri, 25 Jan 2002 14:14:48 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01B1BA5A@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: PSK Chakravarthi <pchakrav@ssd.usa.alcatel.com>, megaco@ietf.org,
        Al Varney <varney@ieee.org>
Subject: RE: [Megaco] Megaco CAS
Date: Fri, 25 Jan 2002 14:14:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A5D4.90037500"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A5D4.90037500
Content-Type: text/plain;
	charset="iso-8859-1"

All,

We have a new version of the draft that is awaiting IANA registration before
I publish it again.  We will include the coding parameter as optional, as
suggested.

As to other comments in the thread... the package does not define the
granularity of any provisioning (either per-term, or per-MG).  This was
worded intentionally to avoid imposing an implementation upon an MG.  For
certain items, it should be apparent to the vendor what type of provisioning
is appropriate, given the implementation. I can envision per-MG, per-DS0, or
even per-group-of-DS0s.

And, the statement about attempting to force DTMF over an MF trunk is
certainly outside the scope of CAS.  However, the addition of the coding
parameter will allow this behavior, if desired.

Kevin

-----Original Message-----
From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
Sent: Thursday, January 10, 2002 3:17 AM
To: megaco@ietf.org; Al Varney
Subject: Re: [Megaco] Megaco CAS


Al Varney,

I think optional is OK.  Default coding type for a termination should be
provisioned in MG.  If MGC want to override, it can use optional parameter
"ac".

Thanks
Chak
----- Original Message -----
From: "Al Varney" <varney@ieee.org>
To: <megaco@ietf.org>
Sent: Wednesday, January 09, 2002 10:18 PM
Subject: Re: [Megaco] Megaco CAS


> Chak,
>     At first, I thought the Description of "provisioned" frequency,
> cadence, etc. could be clarified as a per-trunk attribute (not per MG, as
> some might read it).  That is, MF trunks always used MF signaling, etc.
On
> further reflection, this is insufficient to emulate some forms of older
> signaling used in the USA.  For example, some circuits signal using Dial
> Pulse in a first stage, followed by MF in the second.  Also, it might be
> useful to force DTMF signaling over an MF trunk which is already connected
> on a call (although that goes beyond the function typically associated
with
> the acronym "CAS").
>
>     So I'm agreeing with you, with a small suggestion below:
>
> At 12:56 PM 1/9/02 +0530, PSK Chakravarthi wrote:
> >I think we can have another parameter as given below:
> >
> >         Parameter Name: Address Type
> >         ParameterID: at (0x0003)
> >         Description: Specifies Type of address digits.
> >         Type: enumeration
> >         Possible Values:
> >         "DTMF"  (0x0000)  DTMF Digits
> >         "MF"       (0x0001)  MF Digits
> >         "DP"        (0x0002)  Dial Pulse Digits
>
>     It might be less confusing if the word "Type" was not used in the Name
> or Description, since it is part of the meta-language of MEGACO
> packages.  I used "Coding" below, but another word might be better.  Also,
> you offered no default text in the Description -- did you really want
> "Address Type" to be included in every use of "addr"?
>
>       Alternative Name/ID/Description for consideration:
>   Parameter Name: Address Coding
>   ParameterID: ac (0x0003)
>   Description: Specifies the coding of Digit String parameter
>            in tones or DC pulses.  Address Coding is optional;
>            if not provided, the MG uses the value provisioned
>            as an attribute of the circuit associated with the
>            signal.
>
>     Would it be useful to mention an error case if Address Coding is not
> present and the "circuit" has no 'ac' value provisioned?  (For example,
> could CAS package be used to signal over an ephemeral?)
>
>     On second thought, having 'ac' optional might be a mistake.  It forces
> the MGC to "know" the coding for every circuit.  (The
> provisioned-per-MG-circuit option allows the MGC to be ignorant of the
> coding.)  I think it unlikely that the MGC could be ignorant of MF vs.
DTMF
> vs. DP for a given circuit, and provisioning in 2 places (MG and MGC) is
> just asking for an error.
>
> Al Varney - varney@ieee.org
>
> > > From: PSK Chakravarthi [mailto:pchakrav@ssd.usa.alcatel.com]
> > > Hi List,
> > > As per draft-manyfolks-megaco-caspackage-01.txt Section
> > > 6.4.5
> > >     Signal Name: Address
> > >     SignalID: addr (0x0005)
> > >     Description: Applies the address signals in the form of either
> > >           DTMF, dial-pulse or MF-tones on the trunk. The actual
> > >           frequency, cadence, duration and amplitude values for the
> > >           multi-frequency tones that convey the address information
are
> > >           provisioned in the MG.
> > >     Signal Type: (BR) Brief
> > >     Duration: Provisioned
> > >     Additional Parameters:
> > >         Parameter Name: Digit String
> > >         ParameterID: ds (0x0001)
> > >         Description: The digit string that needs to be sent as address
> > >           signals.
> > >         Type: string of digits.
> > >         Possible Values: a sequence of the characters "0" through "9"
> > >           as well as "A" through "H" ("A" through "H" used for MF
> > >           signalling - refer to the symbols defined for the digit map
> > >           in the MF Tone Detection package).
> > >         Parameter Name: Address Delay
> > >         ParameterID: ad (0x0002)
> > >         Description: Specifies a timed delay that is applied prior to
> > >           signalling the address. The address delay is optional. If
the
> > >           address delay parameter is not provided, the MG uses the
> > >           provisioned value by default.
> > >         Type: integer
> > >         Possible Values: 0 and up in milliseconds
> > >
> > > Question:
> > > MGC can instruct gateway to out pulse digits either in DTMF or MF or
dial
> > > pulse.
> > > How MGC can tell gateway about the mode of the digits is MF or DTMF or
Dial
> > > Pulse?
>
>
> _______________________________________________
> 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

------_=_NextPart_001_01C1A5D4.90037500
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Megaco CAS</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>All,</FONT>
</P>

<P><FONT SIZE=3D2>We have a new version of the draft that is awaiting =
IANA registration before I publish it again.&nbsp; We will include the =
coding parameter as optional, as suggested.</FONT></P>

<P><FONT SIZE=3D2>As to other comments in the thread... the package =
does not define the granularity of any provisioning (either per-term, =
or per-MG).&nbsp; This was worded intentionally to avoid imposing an =
implementation upon an MG.&nbsp; For certain items, it should be =
apparent to the vendor what type of provisioning is appropriate, given =
the implementation. I can envision per-MG, per-DS0, or even =
per-group-of-DS0s.</FONT></P>

<P><FONT SIZE=3D2>And, the statement about attempting to force DTMF =
over an MF trunk is certainly outside the scope of CAS.&nbsp; However, =
the addition of the coding parameter will allow this behavior, if =
desired.</FONT></P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: PSK Chakravarthi [<A =
HREF=3D"mailto:pchakrav@ssd.usa.alcatel.com">mailto:pchakrav@ssd.usa.alc=
atel.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, January 10, 2002 3:17 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org; Al Varney</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Megaco CAS</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Al Varney,</FONT>
</P>

<P><FONT SIZE=3D2>I think optional is OK.&nbsp; Default coding type for =
a termination should be</FONT>
<BR><FONT SIZE=3D2>provisioned in MG.&nbsp; If MGC want to override, it =
can use optional parameter &quot;ac&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks</FONT>
<BR><FONT SIZE=3D2>Chak</FONT>
<BR><FONT SIZE=3D2>----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>From: &quot;Al Varney&quot; =
&lt;varney@ieee.org&gt;</FONT>
<BR><FONT SIZE=3D2>To: &lt;megaco@ietf.org&gt;</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 09, 2002 10:18 PM</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Megaco CAS</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; Chak,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; At first, I thought the =
Description of &quot;provisioned&quot; frequency,</FONT>
<BR><FONT SIZE=3D2>&gt; cadence, etc. could be clarified as a per-trunk =
attribute (not per MG, as</FONT>
<BR><FONT SIZE=3D2>&gt; some might read it).&nbsp; That is, MF trunks =
always used MF signaling, etc.&nbsp; On</FONT>
<BR><FONT SIZE=3D2>&gt; further reflection, this is insufficient to =
emulate some forms of older</FONT>
<BR><FONT SIZE=3D2>&gt; signaling used in the USA.&nbsp; For example, =
some circuits signal using Dial</FONT>
<BR><FONT SIZE=3D2>&gt; Pulse in a first stage, followed by MF in the =
second.&nbsp; Also, it might be</FONT>
<BR><FONT SIZE=3D2>&gt; useful to force DTMF signaling over an MF trunk =
which is already connected</FONT>
<BR><FONT SIZE=3D2>&gt; on a call (although that goes beyond the =
function typically associated with</FONT>
<BR><FONT SIZE=3D2>&gt; the acronym &quot;CAS&quot;).</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; So I'm agreeing with =
you, with a small suggestion below:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; At 12:56 PM 1/9/02 +0530, PSK Chakravarthi =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I think we can have another parameter as =
given below:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Address Type</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: at =
(0x0003)</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Specifies Type of address digits.</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
enumeration</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible =
Values:</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;DTMF&quot;&nbsp; (0x0000)&nbsp; DTMF Digits</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;MF&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0x0001)&nbsp; MF =
Digits</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;DP&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0x0002)&nbsp; =
Dial Pulse Digits</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; It might be less =
confusing if the word &quot;Type&quot; was not used in the Name</FONT>
<BR><FONT SIZE=3D2>&gt; or Description, since it is part of the =
meta-language of MEGACO</FONT>
<BR><FONT SIZE=3D2>&gt; packages.&nbsp; I used &quot;Coding&quot; =
below, but another word might be better.&nbsp; Also,</FONT>
<BR><FONT SIZE=3D2>&gt; you offered no default text in the Description =
-- did you really want</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Address Type&quot; to be included in =
every use of &quot;addr&quot;?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Alternative =
Name/ID/Description for consideration:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Parameter Name: Address =
Coding</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; ParameterID: ac (0x0003)</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Description: Specifies the coding =
of Digit String parameter</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; in tones or DC pulses.&nbsp; Address Coding is optional;</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; if not provided, the MG uses the value provisioned</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; as an attribute of the circuit associated with the</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; signal.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Would it be useful to =
mention an error case if Address Coding is not</FONT>
<BR><FONT SIZE=3D2>&gt; present and the &quot;circuit&quot; has no 'ac' =
value provisioned?&nbsp; (For example,</FONT>
<BR><FONT SIZE=3D2>&gt; could CAS package be used to signal over an =
ephemeral?)</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; On second thought, =
having 'ac' optional might be a mistake.&nbsp; It forces</FONT>
<BR><FONT SIZE=3D2>&gt; the MGC to &quot;know&quot; the coding for =
every circuit.&nbsp; (The</FONT>
<BR><FONT SIZE=3D2>&gt; provisioned-per-MG-circuit option allows the =
MGC to be ignorant of the</FONT>
<BR><FONT SIZE=3D2>&gt; coding.)&nbsp; I think it unlikely that the MGC =
could be ignorant of MF vs. DTMF</FONT>
<BR><FONT SIZE=3D2>&gt; vs. DP for a given circuit, and provisioning in =
2 places (MG and MGC) is</FONT>
<BR><FONT SIZE=3D2>&gt; just asking for an error.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Al Varney - varney@ieee.org</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; From: PSK Chakravarthi [<A =
HREF=3D"mailto:pchakrav@ssd.usa.alcatel.com">mailto:pchakrav@ssd.usa.alc=
atel.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Hi List,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; As per =
draft-manyfolks-megaco-caspackage-01.txt Section</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 6.4.5</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Signal Name: =
Address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; SignalID: =
addr (0x0005)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Applies the address signals in the form of either</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; DTMF, dial-pulse or MF-tones on the trunk. The =
actual</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
frequency, cadence, duration and amplitude values for the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multi-frequency tones that convey the address information are</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
provisioned in the MG.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Signal Type: =
(BR) Brief</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Duration: =
Provisioned</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Additional =
Parameters:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Digit String</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ds =
(0x0001)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: The =
digit string that needs to be sent as address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signals.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: string of =
digits.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: a =
sequence of the characters &quot;0&quot; through &quot;9&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as =
well as &quot;A&quot; through &quot;H&quot; (&quot;A&quot; through =
&quot;H&quot; used for MF</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signalling - refer to the symbols defined for the digit map</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the =
MF Tone Detection package).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parameter Name: =
Address Delay</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ParameterID: ad =
(0x0002)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description: =
Specifies a timed delay that is applied prior to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signalling the address. The address delay is optional. If the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
address delay parameter is not provided, the MG uses the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
provisioned value by default.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type: =
integer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Possible Values: 0 =
and up in milliseconds</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Question:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; MGC can instruct gateway to out pulse =
digits either in DTMF or MF or dial</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pulse.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; How MGC can tell gateway about the =
mode of the digits is MF or DTMF or</FONT>
<BR><FONT SIZE=3D2>Dial</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Pulse?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A5D4.90037500--

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



From megaco-admin@ietf.org  Fri Jan 25 17:18:14 2002
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 RAA16193
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 17:18:14 -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 RAA13941;
	Fri, 25 Jan 2002 17:09:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA13826
	for <megaco@ns.ietf.org>; Fri, 25 Jan 2002 17:09:06 -0500 (EST)
Received: from flyingfox.snowshore.com (flyingfox.snowshore.com [216.57.133.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15842;
	Fri, 25 Jan 2002 17:09:01 -0500 (EST)
Received: from eburger (keeper.snowshore.com [216.57.133.4])
	by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g0PM8xB10623;
	Fri, 25 Jan 2002 17:08:59 -0500 (EST)
Reply-To: <eburger@snowshore.com>
From: "Eric Burger" <eburger@snowshore.com>
To: <mrcp@snowshore.com>, <ietf-announce@ietf.org>
Cc: <mrcp@external.cisco.com>, <mmusic@ietf.org>, "Sipping" <sipping@ietf.org>,
        <megaco@ietf.org>
Date: Fri, 25 Jan 2002 17:08:58 -0500
Message-ID: <EEEDJPFPPHPFKDDLLMOKIEPDDGAA.eburger@snowshore.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Media Resource Control (MRCP) BOF
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: 7bit

Multimedia Resource Control (mrcp) BOF

Chairs
------
Eric Burger <eburger@snowshore.com>
David Oran <oran@cisco.com>


BOF Description
----------------
Many multimedia applications can benefit from having ASR and TTS processing
available as a distributed, network resource. To date, there are a number of
proprietary ASR and TTS API's, as well as two IETF drafts, that address this
problem. However, there are serious deficiencies to the existing drafts
relating to MRCP. In particular, they mix the semantics of existing
protocols yet are close enough to other protocols as to be confusing to the
implementer.

The MRCP BOF will examine whether the IETF should charter a Working Group to
develop protocols to support distributed media processing of audio streams.
There are multiple IETF protocols for establishment and termination of media
sessions (SIP), low-level media control (MGCP and megaco), and media record
and playback (RTSP). The focus of this working group is to develop protocols
to support Automated Speech Recognition (ASR) and rendering text into audio,
a.k.a. Text-to-Speech (TTS). The working group will only focus on the
distributed control of ASR and TTS servers.

The working group will develop an informational RFC detailing the
architecture and requirements for distributed ASR and TTS control. The
working group will then examine existing media-related protocols, especially
RTSP, for suitability as a protocol for carriage of ASR and TTS control.
Then, the working group will propose extensions to existing protocols or the
development of new protocols, as appropriate, to meet the requirements
specified in the informational RFC.

The protocol will assume RTP carriage of media. Assuming session-oriented
media transport, the protocol will use SDP to describe the session.

The working group will not be investigating distributed speech recognition
(DSR), as exemplified by the ETSI Aurora project. The working group will not
be recreating functionality available in other protocols, such as SIP or
SDP. The working group will offer changes to existing protocols, with the
possible exception of RTSP, to the appropriate IETF work group for
consideration. This working group will explore modifications to RTSP, if
required.

The intention is to disband the work group within one year of chartering.

Goals and Milestones
--------------------
Mar 02	BOF at 53rd IETF
Jul 02	Informational Requirements RFC Published
Dec 02	Submit Internet Draft(s) Analyzing Existing Protocols
Dec 02	Submit Internet Draft Describing New Protocol (if required)
Mar 03	Drafts to IESG


Reading List
------------
"MRCP: Media Resource Control Protocol", draft-shanmugham-mrcp-01.txt
"Using Media Resource Control Protocol over SIP",
draft-robinson-mrcp-sip-00.txt


Mailing List
------------
The discussion list for MRCP is at mrcp@snowshore.com. To subscribe, send a
request to:
	majordomo@snowshore.com
with
	subscribe mrcp
in the body.

The list archive is at
http://flyingfox.snowshore.com/mrcp_archive/maillist.html

N.B.: This list replaces the mrcp@external.cisco.com list.


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


From daemon@ns.ietf.org  Fri Jan 25 18:22:15 2002
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 RAA16204
	for <megaco-archive@odin.ietf.org>; Fri, 25 Jan 2002 17:18:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA14242
	for megaco-archive@odin.ietf.org; Fri, 25 Jan 2002 17:18:19 -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 RAA13941;
	Fri, 25 Jan 2002 17:09:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA13826
	for <megaco@ns.ietf.org>; Fri, 25 Jan 2002 17:09:06 -0500 (EST)
Received: from flyingfox.snowshore.com (flyingfox.snowshore.com [216.57.133.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15842;
	Fri, 25 Jan 2002 17:09:01 -0500 (EST)
Received: from eburger (keeper.snowshore.com [216.57.133.4])
	by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g0PM8xB10623;
	Fri, 25 Jan 2002 17:08:59 -0500 (EST)
Reply-To: <eburger@snowshore.com>
From: "Eric Burger" <eburger@snowshore.com>
To: <mrcp@snowshore.com>, <ietf-announce@ietf.org>
Cc: <mrcp@external.cisco.com>, <mmusic@ietf.org>, "Sipping" <sipping@ietf.org>,
        <megaco@ietf.org>
Date: Fri, 25 Jan 2002 17:08:58 -0500
Message-ID: <EEEDJPFPPHPFKDDLLMOKIEPDDGAA.eburger@snowshore.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Media Resource Control (MRCP) BOF
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: 7bit

Multimedia Resource Control (mrcp) BOF

Chairs
------
Eric Burger <eburger@snowshore.com>
David Oran <oran@cisco.com>


BOF Description
----------------
Many multimedia applications can benefit from having ASR and TTS processing
available as a distributed, network resource. To date, there are a number of
proprietary ASR and TTS API's, as well as two IETF drafts, that address this
problem. However, there are serious deficiencies to the existing drafts
relating to MRCP. In particular, they mix the semantics of existing
protocols yet are close enough to other protocols as to be confusing to the
implementer.

The MRCP BOF will examine whether the IETF should charter a Working Group to
develop protocols to support distributed media processing of audio streams.
There are multiple IETF protocols for establishment and termination of media
sessions (SIP), low-level media control (MGCP and megaco), and media record
and playback (RTSP). The focus of this working group is to develop protocols
to support Automated Speech Recognition (ASR) and rendering text into audio,
a.k.a. Text-to-Speech (TTS). The working group will only focus on the
distributed control of ASR and TTS servers.

The working group will develop an informational RFC detailing the
architecture and requirements for distributed ASR and TTS control. The
working group will then examine existing media-related protocols, especially
RTSP, for suitability as a protocol for carriage of ASR and TTS control.
Then, the working group will propose extensions to existing protocols or the
development of new protocols, as appropriate, to meet the requirements
specified in the informational RFC.

The protocol will assume RTP carriage of media. Assuming session-oriented
media transport, the protocol will use SDP to describe the session.

The working group will not be investigating distributed speech recognition
(DSR), as exemplified by the ETSI Aurora project. The working group will not
be recreating functionality available in other protocols, such as SIP or
SDP. The working group will offer changes to existing protocols, with the
possible exception of RTSP, to the appropriate IETF work group for
consideration. This working group will explore modifications to RTSP, if
required.

The intention is to disband the work group within one year of chartering.

Goals and Milestones
--------------------
Mar 02	BOF at 53rd IETF
Jul 02	Informational Requirements RFC Published
Dec 02	Submit Internet Draft(s) Analyzing Existing Protocols
Dec 02	Submit Internet Draft Describing New Protocol (if required)
Mar 03	Drafts to IESG


Reading List
------------
"MRCP: Media Resource Control Protocol", draft-shanmugham-mrcp-01.txt
"Using Media Resource Control Protocol over SIP",
draft-robinson-mrcp-sip-00.txt


Mailing List
------------
The discussion list for MRCP is at mrcp@snowshore.com. To subscribe, send a
request to:
	majordomo@snowshore.com
with
	subscribe mrcp
in the body.

The list archive is at
http://flyingfox.snowshore.com/mrcp_archive/maillist.html

N.B.: This list replaces the mrcp@external.cisco.com list.


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



From megaco-admin@ietf.org  Sun Jan 27 07:14:43 2002
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 HAA28945
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 07:14:43 -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 HAA09883;
	Sun, 27 Jan 2002 07:05:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09852
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 07:05:51 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28890
	for <megaco@ietf.org>; Sun, 27 Jan 2002 07:05:47 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001768035@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Sun, 27 Jan 2002 17:51:04 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0RC4eu31507
	for <megaco@ietf.org>; Sun, 27 Jan 2002 17:34:40 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Date: Sun, 27 Jan 2002 17:43:22 +0530
Message-Id: <000001c1a72c$05113d20$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] TerminationID ASN encding
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: 7bit

Hi,

The annex A.2 of the rfc specifies....

----------------------------------------------------------------------------
----------------------
NOTE - The ASN.1 specification below contains a clause defining
   TerminationIDList as a sequence of TerminationIDs.  The length of
   this sequence SHALL be one, except possibly when used in
   contextAuditResult.
----------------------------------------------------------------------------
----------------------

Q. Does this mean that the Length in the TLV format should be coded as 1
irrespective
of the number of bytes that TerminationID occupy.

-
gokul


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


From megaco-admin@ietf.org  Sun Jan 27 07:41:08 2002
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 HAA29110
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 07:41:03 -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 HAA10665;
	Sun, 27 Jan 2002 07:34:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10640
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 07:34:22 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29078
	for <megaco@ietf.org>; Sun, 27 Jan 2002 07:34:18 -0500 (EST)
From: rahulr@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0RCYxE02680;
	Sun, 27 Jan 2002 18:04:59 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4E.0044F80D ; Sun, 27 Jan 2002 18:03:19 +0530
X-Lotus-FromDomain: HSS
To: gokulc@future.futsoft.com
cc: megaco@ietf.org
Message-ID: <65256B4E.0044F7B6.00@sandesh.hss.hns.com>
Date: Sun, 27 Jan 2002 18:07:11 +0530
Subject: Re: [Megaco] TerminationID ASN encding
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



hi gokul,

The Text in Annex A.2 that you have quoted actually talks of the number
of TerminationIDs in a TerminationIDList and not its length.
According to Annex A.2 the TerminationIDList shall contain only
"one TerminationID" except in case of contextAuditResult.

The length in TLV for TerminationIDList will certainly depend on the length
of the TerminationID.

Regards,
Rahul

> Hi,
>
> The annex A.2 of the rfc specifies....
>
> ----------------------------------------------------------------------------
> ----------------------
> NOTE - The ASN.1 specification below contains a clause defining
>    TerminationIDList as a sequence of TerminationIDs.  The length of
>    this sequence SHALL be one, except possibly when used in
>    contextAuditResult.
> ----------------------------------------------------------------------------
> ----------------------
>
> Q. Does this mean that the Length in the TLV format should be coded as 1
> irrespective
> of the number of bytes that TerminationID occupy.
>
> -
> gokul
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended. If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transmitted by this email including
damage from virus."






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


From daemon@optimus.ietf.org  Sun Jan 27 07:41:09 2002
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 HAA29118
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 07:41:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA10771
	for megaco-archive@odin.ietf.org; Sun, 27 Jan 2002 07:41:11 -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 HAA10665;
	Sun, 27 Jan 2002 07:34:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10640
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 07:34:22 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29078
	for <megaco@ietf.org>; Sun, 27 Jan 2002 07:34:18 -0500 (EST)
From: rahulr@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0RCYxE02680;
	Sun, 27 Jan 2002 18:04:59 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4E.0044F80D ; Sun, 27 Jan 2002 18:03:19 +0530
X-Lotus-FromDomain: HSS
To: gokulc@future.futsoft.com
cc: megaco@ietf.org
Message-ID: <65256B4E.0044F7B6.00@sandesh.hss.hns.com>
Date: Sun, 27 Jan 2002 18:07:11 +0530
Subject: Re: [Megaco] TerminationID ASN encding
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



hi gokul,

The Text in Annex A.2 that you have quoted actually talks of the number
of TerminationIDs in a TerminationIDList and not its length.
According to Annex A.2 the TerminationIDList shall contain only
"one TerminationID" except in case of contextAuditResult.

The length in TLV for TerminationIDList will certainly depend on the length
of the TerminationID.

Regards,
Rahul

> Hi,
>
> The annex A.2 of the rfc specifies....
>
> ----------------------------------------------------------------------------
> ----------------------
> NOTE - The ASN.1 specification below contains a clause defining
>    TerminationIDList as a sequence of TerminationIDs.  The length of
>    this sequence SHALL be one, except possibly when used in
>    contextAuditResult.
> ----------------------------------------------------------------------------
> ----------------------
>
> Q. Does this mean that the Length in the TLV format should be coded as 1
> irrespective
> of the number of bytes that TerminationID occupy.
>
> -
> gokul
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and should
not be circulated or used for any purpose other than for what it is intended. If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transmitted by this email including
damage from virus."






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



From daemon@optimus.ietf.org  Sun Jan 27 08:01:56 2002
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 HAA28953
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 07:14:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA09981
	for megaco-archive@odin.ietf.org; Sun, 27 Jan 2002 07:14:46 -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 HAA09883;
	Sun, 27 Jan 2002 07:05:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09852
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 07:05:51 -0500 (EST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28890
	for <megaco@ietf.org>; Sun, 27 Jan 2002 07:05:47 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001768035@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Sun, 27 Jan 2002 17:51:04 +0530
Received: from gokulc (gokulc.future.futsoft.com [10.8.3.8])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g0RC4eu31507
	for <megaco@ietf.org>; Sun, 27 Jan 2002 17:34:40 +0530
Reply-To: <gokulc@future.futsoft.com>
From: "gokulc" <gokulc@future.futsoft.com>
To: <megaco@ietf.org>
Date: Sun, 27 Jan 2002 17:43:22 +0530
Message-Id: <000001c1a72c$05113d20$0803080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] TerminationID ASN encding
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: 7bit

Hi,

The annex A.2 of the rfc specifies....

----------------------------------------------------------------------------
----------------------
NOTE - The ASN.1 specification below contains a clause defining
   TerminationIDList as a sequence of TerminationIDs.  The length of
   this sequence SHALL be one, except possibly when used in
   contextAuditResult.
----------------------------------------------------------------------------
----------------------

Q. Does this mean that the Length in the TLV format should be coded as 1
irrespective
of the number of bytes that TerminationID occupy.

-
gokul


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



From megaco-admin@ietf.org  Sun Jan 27 22:11:35 2002
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 WAA07435
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 22:11:35 -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 VAA06295;
	Sun, 27 Jan 2002 21:54:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06267
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 21:54:52 -0500 (EST)
Date: Sun, 27 Jan 2002 21:54:52 -0500 (EST)
Received: from mail.intermuz.com ([211.62.37.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07295
	for <megaco@ietf.org>; Sun, 27 Jan 2002 21:54:47 -0500 (EST)
Received: from defg.com [unverified [64.86.192.77]] by mail.intermuz.com;
	with SMTP id <WM020128101103000001006214@mail.intermuz.com>;
	Mon, 28 Jan 2002 11:49:36 +0900
Message-ID: <57383440$57f2$4b59>
Mime-Version: 1.0
X-Priority: 1 (Highest)
X-MSMail-Priority: High
Importance: High
Content-Type: multipart/mixed;
	boundary="----=_NextPart_23006_19079_3D3.4C177801F40B"
To: "megaco@ietf.org" <megaco@ietf.org>
From: "" <admin@webmasterdirect.org>
Reply-to: admin@webmasterdirect.org
Subject: [Megaco] Look
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


------=_NextPart_23006_19079_3D3.4C177801F40B
Content-Type: text/html; 
	charset="us-ascii"
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0079)http://lists.w3.org/Archives/Public/www-html-editor/2001OctDec/att-0174/00-part -->
<HTML><HEAD><TITLE>DVD Copy Utility</TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<META content=FrontPage.Editor.Document name=ProgId>
<META content="none, default" name="Microsoft Border"></HEAD>
<BODY text=#0000CC bgColor=#FFFFFF>
<div align="center">&nbsp;<A href="http://www.copydvd.net/"><IMG height=150 
src="http://www.copydvd.net/images/Gladiator.jpg" width=110 border=0> </A><A 
href="http://www.applied-computers.com/dvd.htm"></A><A 
href="http://www.copydvd.net/"><IMG height=150 
src="http://www.copydvd.net/images/buzz.jpg" width=110 border=0> </A><A 
href="http://www.copydvd.net/"></A><A 
href="http://www.copydvd.net/"></A> </div>
<P align=center><B><U><font color="#FF0000" size="6">Copy &amp; Burn DVD's &amp; 
  VHS's w/CD Burner!!!</font></U></B></P>
<P align=center>&nbsp;</P>
<ul>
  <BLOCKQUOTE> 
    <BLOCKQUOTE> 
      <p align="center"><font color="#000000"><b><font face="Times New Roman, Times, serif">Why 
        Spend upwards of $4000 on a DVD Burner when we will show you an alternative 
        that will do the exact same thing for only $19.95? </font></b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"><b>You 
        heard us right - for the price of just 1 DVD's, we'll show you how to 
        back up and/or create Your Own DVD's! </b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"><b>Just 
        upgraded to a DVD and still have a ton of VHS tapes lying around? With 
        this program, not only can you burn &amp; copy any DVD you've created, 
        you'll also be able to transfer all your VHS tapes to DVD format as well!! 
        </b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"></font></p>
      <p align="center"><b><font color="#000000" size="4">Regular Price:</font></b> 
        <img src="http://www.copydvd.net/images/crossed_out.gif" width="77" height="22"></p>
      <P align=center><font color="#000000" size="5"><B><U><A 
      href="http://www.copydvd.net/"></A></U></B></font><FONT color=#ffffff size=5><B><U></U></B></FONT><font color="#0000CC"><b><font color="#000000" size="4">For 
        a Limited Time Only, get yours today for just</font><font color="#000000"> 
        <b><font color=#ffffff size=5><b><u><a href="http://www.copydvd.net/order.html"><font color="#FF0000" size="4">ONLY 
        </font></a></u></b></font><font size="4" color="#FF0000"><u>$19.95!!</u></font></b><br>
        </font></b></font></P>
      <P align=center><FONT color=#ffffff size=5><U> <a href="http://www.copydvd.net/order.html"><B>ORDER 
        NOW</B></a> </U></FONT></P>
      <P align=center><a href="order.html"><img src="http://www.copydvd.net/images/visa-mastercard-amex.jpg" width="196" height="44" border="0"></a></P>
    </BLOCKQUOTE>
  </BLOCKQUOTE>
</ul>
<P align=center><FONT face="Times New Roman" color=#ffffff 
size=3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></P>
<P align=center><font face="Times New Roman, Times, serif" color="#000000"><b>You 
  want to know more? Visit us at <a href="http://www.copydvd.net">http://www.copydvd.net</a></b></font></P>
<P align=left><font face="Times New Roman, Times, serif"><b><font color="#000000">Win 
  $ 5000 NOW !!!<br>
  Forward this message to 5 of your friends (put our email: win@ewasher.org in 
  the cc field along with your 5 friends email addresses) and you will be automatically 
  entered in our drawing for $5000.</font></b></font></P>
<p align="left">&nbsp;</p>
<p align="left"><br>
</p>
<P align=left><font color="#000000" size="3" face="Times New Roman, Times, serif"><b>To 
  be opt out from our future mailing please email optout@ewasher.org with the 
  word remove in the subject line</b></font></P>
<P align=center>&nbsp;</P>
<P align=center><B><U><A href="mailto:remove@ewasher.org"><FONT 
color=#ffffff size=3>To be removed from this mailing list please send an email 
  to remove@ewasher.org with the word remove in the subject line</FONT></A></U></B></P>
</BODY><!--d5707a2e7fa2545155bc30c74b0431314ac0--></HTML>

------=_NextPart_23006_19079_3D3.4C177801F40B--

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


From daemon@optimus.ietf.org  Sun Jan 27 22:11:35 2002
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 WAA07445
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 22:11:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07040
	for megaco-archive@odin.ietf.org; Sun, 27 Jan 2002 22:11:38 -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 VAA06295;
	Sun, 27 Jan 2002 21:54:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06267
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 21:54:52 -0500 (EST)
Date: Sun, 27 Jan 2002 21:54:52 -0500 (EST)
Received: from mail.intermuz.com ([211.62.37.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07295
	for <megaco@ietf.org>; Sun, 27 Jan 2002 21:54:47 -0500 (EST)
Received: from defg.com [unverified [64.86.192.77]] by mail.intermuz.com;
	with SMTP id <WM020128101103000001006214@mail.intermuz.com>;
	Mon, 28 Jan 2002 11:49:36 +0900
Message-ID: <57383440$57f2$4b59>
Mime-Version: 1.0
X-Priority: 1 (Highest)
X-MSMail-Priority: High
Importance: High
Content-Type: multipart/mixed;
	boundary="----=_NextPart_23006_19079_3D3.4C177801F40B"
To: "megaco@ietf.org" <megaco@ietf.org>
From: "" <admin@webmasterdirect.org>
Reply-to: admin@webmasterdirect.org
Subject: [Megaco] Look
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


------=_NextPart_23006_19079_3D3.4C177801F40B
Content-Type: text/html; 
	charset="us-ascii"
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0079)http://lists.w3.org/Archives/Public/www-html-editor/2001OctDec/att-0174/00-part -->
<HTML><HEAD><TITLE>DVD Copy Utility</TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<META content=FrontPage.Editor.Document name=ProgId>
<META content="none, default" name="Microsoft Border"></HEAD>
<BODY text=#0000CC bgColor=#FFFFFF>
<div align="center">&nbsp;<A href="http://www.copydvd.net/"><IMG height=150 
src="http://www.copydvd.net/images/Gladiator.jpg" width=110 border=0> </A><A 
href="http://www.applied-computers.com/dvd.htm"></A><A 
href="http://www.copydvd.net/"><IMG height=150 
src="http://www.copydvd.net/images/buzz.jpg" width=110 border=0> </A><A 
href="http://www.copydvd.net/"></A><A 
href="http://www.copydvd.net/"></A> </div>
<P align=center><B><U><font color="#FF0000" size="6">Copy &amp; Burn DVD's &amp; 
  VHS's w/CD Burner!!!</font></U></B></P>
<P align=center>&nbsp;</P>
<ul>
  <BLOCKQUOTE> 
    <BLOCKQUOTE> 
      <p align="center"><font color="#000000"><b><font face="Times New Roman, Times, serif">Why 
        Spend upwards of $4000 on a DVD Burner when we will show you an alternative 
        that will do the exact same thing for only $19.95? </font></b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"><b>You 
        heard us right - for the price of just 1 DVD's, we'll show you how to 
        back up and/or create Your Own DVD's! </b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"><b>Just 
        upgraded to a DVD and still have a ton of VHS tapes lying around? With 
        this program, not only can you burn &amp; copy any DVD you've created, 
        you'll also be able to transfer all your VHS tapes to DVD format as well!! 
        </b></font></p>
      <p align="center"><font face="Times New Roman, Times, serif" color="#000000"></font></p>
      <p align="center"><b><font color="#000000" size="4">Regular Price:</font></b> 
        <img src="http://www.copydvd.net/images/crossed_out.gif" width="77" height="22"></p>
      <P align=center><font color="#000000" size="5"><B><U><A 
      href="http://www.copydvd.net/"></A></U></B></font><FONT color=#ffffff size=5><B><U></U></B></FONT><font color="#0000CC"><b><font color="#000000" size="4">For 
        a Limited Time Only, get yours today for just</font><font color="#000000"> 
        <b><font color=#ffffff size=5><b><u><a href="http://www.copydvd.net/order.html"><font color="#FF0000" size="4">ONLY 
        </font></a></u></b></font><font size="4" color="#FF0000"><u>$19.95!!</u></font></b><br>
        </font></b></font></P>
      <P align=center><FONT color=#ffffff size=5><U> <a href="http://www.copydvd.net/order.html"><B>ORDER 
        NOW</B></a> </U></FONT></P>
      <P align=center><a href="order.html"><img src="http://www.copydvd.net/images/visa-mastercard-amex.jpg" width="196" height="44" border="0"></a></P>
    </BLOCKQUOTE>
  </BLOCKQUOTE>
</ul>
<P align=center><FONT face="Times New Roman" color=#ffffff 
size=3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></P>
<P align=center><font face="Times New Roman, Times, serif" color="#000000"><b>You 
  want to know more? Visit us at <a href="http://www.copydvd.net">http://www.copydvd.net</a></b></font></P>
<P align=left><font face="Times New Roman, Times, serif"><b><font color="#000000">Win 
  $ 5000 NOW !!!<br>
  Forward this message to 5 of your friends (put our email: win@ewasher.org in 
  the cc field along with your 5 friends email addresses) and you will be automatically 
  entered in our drawing for $5000.</font></b></font></P>
<p align="left">&nbsp;</p>
<p align="left"><br>
</p>
<P align=left><font color="#000000" size="3" face="Times New Roman, Times, serif"><b>To 
  be opt out from our future mailing please email optout@ewasher.org with the 
  word remove in the subject line</b></font></P>
<P align=center>&nbsp;</P>
<P align=center><B><U><A href="mailto:remove@ewasher.org"><FONT 
color=#ffffff size=3>To be removed from this mailing list please send an email 
  to remove@ewasher.org with the word remove in the subject line</FONT></A></U></B></P>
</BODY><!--d5707a2e7fa2545155bc30c74b0431314ac0--></HTML>

------=_NextPart_23006_19079_3D3.4C177801F40B--

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



From megaco-admin@ietf.org  Sun Jan 27 22:27:41 2002
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 WAA07570
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 22:27:41 -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 WAA07126;
	Sun, 27 Jan 2002 22:14:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07099
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 22:14:27 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07473
	for <megaco@ietf.org>; Sun, 27 Jan 2002 22:14:23 -0500 (EST)
Received: from cisco.com (ssh-sj1.cisco.com [171.68.225.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA18383 for <megaco@ietf.org>; Sun, 27 Jan 2002 19:13:50 -0800 (PST)
Message-ID: <3C54C203.CDCD6D7B@cisco.com>
Date: Sun, 27 Jan 2002 22:14:12 -0500
From: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGCP 1.0bis - "Last Call"
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: 7bit

Greetings

We now have an updated version of the MGCP 1.0bis draft available at:


http://search.ietf.org/internet-drafts/draft-andreasen-mgcp-rfc2705bis-02.txt

Section 7.1 lists the changes made since the -01 version.

Thanks to the many questions and comments received over the last 6+
months, we believe the specification is at a stage where it is ready to
move forward, and hence we are issuing a "Last Call" for comments, which
will expire one month from today. Assuming we have no major outstanding
issues at that point, we will then ask for it to become an RFC.

If you have any questions or comments on the I-D, please send an e-mail
to the mgcp list at "MGCP@PULVER.COM" before March 1st.  If you are not
subscribed to this list but would like to, please send an e-mail to
"LISTSERV@LISTSERV.PULVER.COM" with "subscribe mgcp" in the body.


Regards

            Flemming



PS: We also have the MS-Word source document used to generate the I-D
available at

    http://www.softswitch.org/attachments/RFC2705bis-020122.doc

or through

   http://www.softswitch.org/educational/tech_docs.asp

where changes made since the -01 version (except grammar and some purely
editorial changes) appear with a red font.


--
Flemming Andreasen
Cisco Systems



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


From daemon@optimus.ietf.org  Sun Jan 27 22:27:42 2002
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 WAA07582
	for <megaco-archive@odin.ietf.org>; Sun, 27 Jan 2002 22:27:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA07377
	for megaco-archive@odin.ietf.org; Sun, 27 Jan 2002 22:27:45 -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 WAA07126;
	Sun, 27 Jan 2002 22:14:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07099
	for <megaco@optimus.ietf.org>; Sun, 27 Jan 2002 22:14:27 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07473
	for <megaco@ietf.org>; Sun, 27 Jan 2002 22:14:23 -0500 (EST)
Received: from cisco.com (ssh-sj1.cisco.com [171.68.225.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id TAA18383 for <megaco@ietf.org>; Sun, 27 Jan 2002 19:13:50 -0800 (PST)
Message-ID: <3C54C203.CDCD6D7B@cisco.com>
Date: Sun, 27 Jan 2002 22:14:12 -0500
From: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGCP 1.0bis - "Last Call"
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: 7bit

Greetings

We now have an updated version of the MGCP 1.0bis draft available at:


http://search.ietf.org/internet-drafts/draft-andreasen-mgcp-rfc2705bis-02.txt

Section 7.1 lists the changes made since the -01 version.

Thanks to the many questions and comments received over the last 6+
months, we believe the specification is at a stage where it is ready to
move forward, and hence we are issuing a "Last Call" for comments, which
will expire one month from today. Assuming we have no major outstanding
issues at that point, we will then ask for it to become an RFC.

If you have any questions or comments on the I-D, please send an e-mail
to the mgcp list at "MGCP@PULVER.COM" before March 1st.  If you are not
subscribed to this list but would like to, please send an e-mail to
"LISTSERV@LISTSERV.PULVER.COM" with "subscribe mgcp" in the body.


Regards

            Flemming



PS: We also have the MS-Word source document used to generate the I-D
available at

    http://www.softswitch.org/attachments/RFC2705bis-020122.doc

or through

   http://www.softswitch.org/educational/tech_docs.asp

where changes made since the -01 version (except grammar and some purely
editorial changes) appear with a red font.


--
Flemming Andreasen
Cisco Systems



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



From megaco-admin@ietf.org  Mon Jan 28 06:18:41 2002
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 GAA22191
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 06:18:41 -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 GAA03834;
	Mon, 28 Jan 2002 06:03: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 GAA03809
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 06:03:57 -0500 (EST)
Received: from mailweb9.rediffmail.com ([203.199.83.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA22059
	for <megaco@ietf.org>; Mon, 28 Jan 2002 06:03:51 -0500 (EST)
Received: (qmail 18352 invoked by uid 510); 28 Jan 2002 11:04:19 -0000
Date: 28 Jan 2002 11:04:19 -0000
Message-ID: <20020128110419.18351.qmail@mailweb9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 28 Jan 2002 11:04:19 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA03810
Subject: [Megaco] DOUBT
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


hi

   In RFC section 7.2.8 service change reason explanation for failover is given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy 


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


From daemon@optimus.ietf.org  Mon Jan 28 06:18:43 2002
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 GAA22207
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 06:18:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA04167
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 06:18:44 -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 GAA03834;
	Mon, 28 Jan 2002 06:03: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 GAA03809
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 06:03:57 -0500 (EST)
Received: from mailweb9.rediffmail.com ([203.199.83.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA22059
	for <megaco@ietf.org>; Mon, 28 Jan 2002 06:03:51 -0500 (EST)
Received: (qmail 18352 invoked by uid 510); 28 Jan 2002 11:04:19 -0000
Date: 28 Jan 2002 11:04:19 -0000
Message-ID: <20020128110419.18351.qmail@mailweb9.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 28 Jan 2002 11:04:19 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA03810
Subject: [Megaco] DOUBT
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


hi

   In RFC section 7.2.8 service change reason explanation for failover is given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy 


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



From megaco-admin@ietf.org  Mon Jan 28 08:07:08 2002
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 IAA23680
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 08:07:07 -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 HAA08059;
	Mon, 28 Jan 2002 07:57:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08034
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 07:57:00 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23392
	for <megaco@ietf.org>; Mon, 28 Jan 2002 07:56:57 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126R82>; Mon, 28 Jan 2002 07:56:29 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A44840493B@wench>
From: Carl Rutter <crutter@telica.com>
To: "'vidya  g'" <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] DOUBT
Date: Mon, 28 Jan 2002 07:56:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

There is also another line in the corrections RFC
>>Also sent from from the MG to the MGC when the MG
detects that MGC has failed <<<<

Primary is the one that was currently communicating 
with the MGC and then subsequently died.
The secondary would send up the SVC Msg with FailOver
method.

That's my understanding.

Carl
-----Original Message-----
From: vidya g [mailto:vdy73@rediffmail.com]
Sent: Monday, January 28, 2002 6:04 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT



hi

   In RFC section 7.2.8 service change reason explanation for failover is
given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy 


_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan 28 08:07:08 2002
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 IAA23692
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 08:07:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA08721
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 08:07:10 -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 HAA08059;
	Mon, 28 Jan 2002 07:57:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08034
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 07:57:00 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23392
	for <megaco@ietf.org>; Mon, 28 Jan 2002 07:56:57 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126R82>; Mon, 28 Jan 2002 07:56:29 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A44840493B@wench>
From: Carl Rutter <crutter@telica.com>
To: "'vidya  g'" <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] DOUBT
Date: Mon, 28 Jan 2002 07:56:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

There is also another line in the corrections RFC
>>Also sent from from the MG to the MGC when the MG
detects that MGC has failed <<<<

Primary is the one that was currently communicating 
with the MGC and then subsequently died.
The secondary would send up the SVC Msg with FailOver
method.

That's my understanding.

Carl
-----Original Message-----
From: vidya g [mailto:vdy73@rediffmail.com]
Sent: Monday, January 28, 2002 6:04 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT



hi

   In RFC section 7.2.8 service change reason explanation for failover is
given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy 


_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 28 08:47:50 2002
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 IAA25285
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 08:47:45 -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 IAA09984;
	Mon, 28 Jan 2002 08:37:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09960
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 08:37:18 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24684
	for <megaco@ietf.org>; Mon, 28 Jan 2002 08:37:12 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0SDb8E11013;
	Mon, 28 Jan 2002 19:07:09 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4F.004AA7E3 ; Mon, 28 Jan 2002 19:05:26 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4F.004A931C.00@sandesh.hss.hns.com>
Date: Mon, 28 Jan 2002 19:06:29 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Tom

My comments embedded.....





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.
<KN> I feel as per the convention and to some extent simple logic it
would be appropriate to allow terminations to detect events and signals
on only those streams which are explicitly defined on them. More so, because
in cases where there are multiple streams on multiple terminations
Eg:
A context with 4 terminations T1, T2, T3....
Streams 1 and 2 on T1,3 and 2 on T3.
T2 has currently no explicit stream defined on it.

          -------------------
          |              |
     T1----------1         -------T2
          |  |            |
          |  |--2_       |
          |      |       |
          |      |       |
          |      |       |
          |      |    3--------T3
          |      |       | |
          |       |____2--| |
          |              |
          -------------------
It would be questionable to expect the following combinations:
-    T2 detect events or apply signals on stream 1 or 2 or 3.
-    T1 detect events or apply signals on stream 3.
-    T3 detect events or apply signals on stream 1.
At the current moment these terminations are completely oblivious of the
stream IDs refered.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.
<KN> I have an opinion.....How does MGC tell MG to detect events
on all active streams on a termination. Does MGC have to repeat event IDs
in the event descriptor with all active stream IDs as parameters. Protocol
does not introduce any concept of stream ID as "*"(ALL).
From the current text, the stream ID 0 seems to be solving this problem.
Stream ID 0 is the default stream on all terminations,i.e., does not need to
be created explicitly through media descriptor (valid).
If event descriptor contains stream ID 0, "it does not refer to any specific
stream"(valid) but does refer to the termination as a whole.
The inference is that detect events on all streams (currently active on
stream-specific terminations like RTP/ TDMC or stream ID 0 on
nonstream-specific terminations like NAS). If the event is detected on any
stream, report the same to MGC with the specific stream ID.
A similar interpretation can also be made for signals.
And, the default stream ID remains 0 for events/ signals, but 1 for
media descriptor.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan 28 08:47:59 2002
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 IAA25295
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 08:47:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA10490
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 08:47:53 -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 IAA09984;
	Mon, 28 Jan 2002 08:37:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09960
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 08:37:18 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24684
	for <megaco@ietf.org>; Mon, 28 Jan 2002 08:37:12 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0SDb8E11013;
	Mon, 28 Jan 2002 19:07:09 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B4F.004AA7E3 ; Mon, 28 Jan 2002 19:05:26 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B4F.004A931C.00@sandesh.hss.hns.com>
Date: Mon, 28 Jan 2002 19:06:29 +0530
Subject: RE: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Tom

My comments embedded.....





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.
<KN> I feel as per the convention and to some extent simple logic it
would be appropriate to allow terminations to detect events and signals
on only those streams which are explicitly defined on them. More so, because
in cases where there are multiple streams on multiple terminations
Eg:
A context with 4 terminations T1, T2, T3....
Streams 1 and 2 on T1,3 and 2 on T3.
T2 has currently no explicit stream defined on it.

          -------------------
          |              |
     T1----------1         -------T2
          |  |            |
          |  |--2_       |
          |      |       |
          |      |       |
          |      |       |
          |      |    3--------T3
          |      |       | |
          |       |____2--| |
          |              |
          -------------------
It would be questionable to expect the following combinations:
-    T2 detect events or apply signals on stream 1 or 2 or 3.
-    T1 detect events or apply signals on stream 3.
-    T3 detect events or apply signals on stream 1.
At the current moment these terminations are completely oblivious of the
stream IDs refered.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.
<KN> I have an opinion.....How does MGC tell MG to detect events
on all active streams on a termination. Does MGC have to repeat event IDs
in the event descriptor with all active stream IDs as parameters. Protocol
does not introduce any concept of stream ID as "*"(ALL).
From the current text, the stream ID 0 seems to be solving this problem.
Stream ID 0 is the default stream on all terminations,i.e., does not need to
be created explicitly through media descriptor (valid).
If event descriptor contains stream ID 0, "it does not refer to any specific
stream"(valid) but does refer to the termination as a whole.
The inference is that detect events on all streams (currently active on
stream-specific terminations like RTP/ TDMC or stream ID 0 on
nonstream-specific terminations like NAS). If the event is detected on any
stream, report the same to MGC with the specific stream ID.
A similar interpretation can also be made for signals.
And, the default stream ID remains 0 for events/ signals, but 1 for
media descriptor.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 28 09:27:16 2002
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 JAA26877
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 09:27:11 -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 JAA13297;
	Mon, 28 Jan 2002 09:17:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13202
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 09:17:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26647
	for <megaco@ietf.org>; Mon, 28 Jan 2002 09:17:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0SEGUL18779;
	Mon, 28 Jan 2002 09:16:31 -0500 (EST)
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 g0SEGTp20397;
	Mon, 28 Jan 2002 09:16:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ7GNA>; Mon, 28 Jan 2002 09:15:51 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF1E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Mon, 28 Jan 2002 09:14:43 -0500
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

Your proposal that the default streamId (0) means "all active streams" is a
workable one for events, especially if the actual stream on which the signal
occurred is reported in the Notify.  I suspect signals are a bit more
problematic -- you only want a signal to go out on one stream, usually.

I'm still troubled by the implications of assuming that you can't detect
events on a stream not specifically defined at a given termination.  I'm
mainly worried about the NULL context.  The simplest way around that concern
is to assume that the media properties of physical terminations are
pre-provisioned.  In fact, people must be making that asumption now --
otherwise there would have been a lot more interest in my draft on SDP
attributes for TDM.  I intend to revive that draft shortly, by the way.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Monday, January 28, 2002 8:36 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

My comments embedded.....





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.
<KN> I feel as per the convention and to some extent simple logic it
would be appropriate to allow terminations to detect events and signals
on only those streams which are explicitly defined on them. More so, because
in cases where there are multiple streams on multiple terminations
Eg:
A context with 4 terminations T1, T2, T3....
Streams 1 and 2 on T1,3 and 2 on T3.
T2 has currently no explicit stream defined on it.

          -------------------
          |              |
     T1----------1         -------T2
          |  |            |
          |  |--2_       |
          |      |       |
          |      |       |
          |      |       |
          |      |    3--------T3
          |      |       | |
          |       |____2--| |
          |              |
          -------------------
It would be questionable to expect the following combinations:
-    T2 detect events or apply signals on stream 1 or 2 or 3.
-    T1 detect events or apply signals on stream 3.
-    T3 detect events or apply signals on stream 1.
At the current moment these terminations are completely oblivious of the
stream IDs refered.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.
<KN> I have an opinion.....How does MGC tell MG to detect events
on all active streams on a termination. Does MGC have to repeat event IDs
in the event descriptor with all active stream IDs as parameters. Protocol
does not introduce any concept of stream ID as "*"(ALL).
From the current text, the stream ID 0 seems to be solving this problem.
Stream ID 0 is the default stream on all terminations,i.e., does not need to
be created explicitly through media descriptor (valid).
If event descriptor contains stream ID 0, "it does not refer to any specific
stream"(valid) but does refer to the termination as a whole.
The inference is that detect events on all streams (currently active on
stream-specific terminations like RTP/ TDMC or stream ID 0 on
nonstream-specific terminations like NAS). If the event is detected on any
stream, report the same to MGC with the specific stream ID.
A similar interpretation can also be made for signals.
And, the default stream ID remains 0 for events/ signals, but 1 for
media descriptor.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan 28 09:27:16 2002
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 JAA26885
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 09:27:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA13852
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 09:27:19 -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 JAA13297;
	Mon, 28 Jan 2002 09:17:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13202
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 09:17:04 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26647
	for <megaco@ietf.org>; Mon, 28 Jan 2002 09:17:00 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0SEGUL18779;
	Mon, 28 Jan 2002 09:16:31 -0500 (EST)
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 g0SEGTp20397;
	Mon, 28 Jan 2002 09:16:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ7GNA>; Mon, 28 Jan 2002 09:15:51 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF1E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'knayar@hss.hns.com'" <knayar@hss.hns.com>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Mon, 28 Jan 2002 09:14:43 -0500
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

Your proposal that the default streamId (0) means "all active streams" is a
workable one for events, especially if the actual stream on which the signal
occurred is reported in the Notify.  I suspect signals are a bit more
problematic -- you only want a signal to go out on one stream, usually.

I'm still troubled by the implications of assuming that you can't detect
events on a stream not specifically defined at a given termination.  I'm
mainly worried about the NULL context.  The simplest way around that concern
is to assume that the media properties of physical terminations are
pre-provisioned.  In fact, people must be making that asumption now --
otherwise there would have been a lot more interest in my draft on SDP
attributes for TDM.  I intend to revive that draft shortly, by the way.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Monday, January 28, 2002 8:36 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

My comments embedded.....





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




You've opened up a good discussion.

1. You are right about streams also being bound to terminations.  Aside from
being able to define streams when the termination is in the NULL context, we
have the provision that a termination retains its current streams when it is
moved from one context to another.

2. I differ slightly on the interpretation of streams versus actual enabling
of flows, but this is at an abstract level that I don't think makes any
difference in behaviour.  My interpretation is that as soon as a stream is
created in a context, it introduces the potential of bi-directional exchange
of media between the context and each termination in it.  Of course, to have
an actual flow in each direction, you need the conditions you've stated:
Local and Remote defined on at least two terminations and sendRecv set on
both.

The real issue is whether a termination can detect events and send signals
on a stream not explicitly defined at that termination.  I think this is a
matter of convention -- we have to decide one way or the other.  I'll point
out that it has implications for detection of DTMF events in the NULL
context.
<KN> I feel as per the convention and to some extent simple logic it
would be appropriate to allow terminations to detect events and signals
on only those streams which are explicitly defined on them. More so, because
in cases where there are multiple streams on multiple terminations
Eg:
A context with 4 terminations T1, T2, T3....
Streams 1 and 2 on T1,3 and 2 on T3.
T2 has currently no explicit stream defined on it.

          -------------------
          |              |
     T1----------1         -------T2
          |  |            |
          |  |--2_       |
          |      |       |
          |      |       |
          |      |       |
          |      |    3--------T3
          |      |       | |
          |       |____2--| |
          |              |
          -------------------
It would be questionable to expect the following combinations:
-    T2 detect events or apply signals on stream 1 or 2 or 3.
-    T1 detect events or apply signals on stream 3.
-    T3 detect events or apply signals on stream 1.
At the current moment these terminations are completely oblivious of the
stream IDs refered.

3. I think I've made the point that H.248v1 requires that most of the events
and signals we have already defined must be applied to a non-zero stream.
Hence requiring that packages indicate which ones apply to stream 0 is not a
change in the protocol, just a clarification.

I do have a couple of alternatives which indeed would be changes to the
protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.

 (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
event or signal, or
 (b) If only one stream is defined on the specific termination, an
unspecified streamId selects that stream.
<KN> I have an opinion.....How does MGC tell MG to detect events
on all active streams on a termination. Does MGC have to repeat event IDs
in the event descriptor with all active stream IDs as parameters. Protocol
does not introduce any concept of stream ID as "*"(ALL).
From the current text, the stream ID 0 seems to be solving this problem.
Stream ID 0 is the default stream on all terminations,i.e., does not need to
be created explicitly through media descriptor (valid).
If event descriptor contains stream ID 0, "it does not refer to any specific
stream"(valid) but does refer to the termination as a whole.
The inference is that detect events on all streams (currently active on
stream-specific terminations like RTP/ TDMC or stream ID 0 on
nonstream-specific terminations like NAS). If the event is detected on any
stream, report the same to MGC with the specific stream ID.
A similar interpretation can also be made for signals.
And, the default stream ID remains 0 for events/ signals, but 1 for
media descriptor.

Actually, I think people are going to have to bite the bullet and start
specifying streamIds eventually if they don't do it now.  Choosing
alternative (b) would buy a bit of time.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Thursday, January 24, 2002 5:49 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

I would like to add more to your comments about streams being context
properties.

Streams are as good properties of the terminations too....
-    A stream can be created on a termination in the Null Context.
     (almost in all call flows including those in the RFC 3015 stream
descriptor
     or the default stream 1 is sent by the MGC in MODIFY command in the
     Null context).
-    To create a bi-directional stream, we need to send stream descriptor
     with (at the least mode=sendrecv) for both the terminations in the
context.
     The bi-directional stream cannot be created by just refering it in one
     termination.

Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
stream=1 (something similar to a unidirectional media flow) by specifying
stream descriptor for termination T1. At this point it would be incorrect
to assume that termination T2 can detect events or apply signals on the
stream
1.
(T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
totally
oblivious of stream 1).
To detect events or signals on the stream at T2, we need to first make T2
aware
of the stream.

Although, it would be a good idea to specify in package definitions about
which event/ signals etc. would apply on streamID=0, this would amount to
changing
the protocol....are you considering it for version2.

Please comment....

Thanks & Regards,
-Kapil Nayar





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM

To:   Kapil Nayar/HSS@HSS
cc:   "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  RE: [Megaco] Query about streamID 0




Hi.  See new comments [PTT2] below.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Wednesday, January 23, 2002 8:55 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] Query about streamID 0




Hi Tom

my comments embedded.




"Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM

To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
cc:

Subject:  RE: [Megaco] Query about streamID 0




Hi.

-----Original Message-----
From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
Sent: Tuesday, January 22, 2002 8:54 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Query about streamID 0




Hi Tom & list,

RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:

"The default streamID is 0, indicating that the event to be detected is not
related to a particular media stream."

Does the "streamID 0" refer to the complete termination (which means all the
active streams on the termination) ?

[PTT] No.  It really means as it says, that the event or signal is not
associated with any specific stream.  An example is an electrical signal
such as off-hook.
[KN] Does that mean that stream 0 is possible for only physical
terminations,
since electrical signals are more appropriate for physical terminations.
[PTT2] There can be applications of streamId 0 on ephemerals which don't
relate to specific streams.  Electrical signals were just an example.  I
suspect I could find a good example in one of my NAS packages of something
more abstract, but I won't take the time.  Just accept that we don't want to
foreclose the possibility of using this on ephemerals.

And, if some event is required to be detected on the ephemeral termination,
the event descriptor should clearly identify which stream it is required on.
(i.e., MGC cannot send an events descriptor for ephemeral termination
without
stream ID parameter since that defaults to stream ID 0, which may not be
applicable).
[PTT2] That has to be thought through for all terminations.
*** IG issue: It does strike me that you can know in advance (by definition
of the event or signal) whether streamId=0 will apply.  We should therefore
make it requirement to specify this in package definitions.

[PTT] On the other hand, an audio signal such as a DTMF tone is
associated with an audio stream.  (But I bet nobody has bothered to specify
stream 1 for DTMF events when they are using a default streamId for audio.
They should!)
[KN] Does that mean that before sending DTMFdet (dd/<?>) in events
descriptor,
MGC should have already created the stream 1 thru' the media descriptor
in a previous command?
[PTT2] StreamId=1 is the default stream created if you don't use a stream
descriptor, but just specify Local, Remote, and LocalControl.
*** IG issue: would it make more sense to have streamId=0 as the default for
signals and events, or have streamId=1 as the default?

A related doubt is...if an event descriptor refers
to a stream ID which is not previously created by the MGC, MG should
return an error.
[PTT2] I'm not sure.  Remember that streamIds are really a context property.
If a given streamId is supported somewhere in the context, then referring to
that streamId at a given termination implies that the termination also
supports it.  That means it could detect events or send signals on the
stream even if it doesn't know how to handle the media flows on that stream.
I suppose if this is the first mention of the streamId in the context, it
might be appropriate to reject the command.
***IG issue: The implication is that within any command, Stream Descriptors
for new streams MUST appear before Signals and Events descriptors referring
to those StreamIds.

Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
descriptor, event descriptor, signal descriptor ?

[PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
consistent with the meaning of that streamId for events and signals.  We
should have a note to the effect that streamId=0 is reserved in sections
7.1.4 (for thoroughness) and 7.1.6.

You can specify streamId=0 in a signals or events descriptor, but that's the
same as leaving it unspecified.

Please reply back...

Thanks,
Kapil Nayar



"DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
(HSS) and is intended solely for the use of the individual  to whom it is
addressed. It may contain  privileged or confidential information  and
should
not be circulated or used for any purpose other than for what it is
intended.If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."






_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 28 09:32:29 2002
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 JAA27118
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 09:32:28 -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 JAA13632;
	Mon, 28 Jan 2002 09:21:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13601
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 09:21:25 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26724
	for <megaco@ietf.org>; Mon, 28 Jan 2002 09:21:21 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFV69055;
	Mon, 28 Jan 2002 09:18:56 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'vidya  g'" <vdy73@rediffmail.com>, <megaco@ietf.org>
Subject: RE: [Megaco] DOUBT
Date: Mon, 28 Jan 2002 09:13:49 -0500
Message-ID: <001301c1a806$02e35e90$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <20020128110419.18351.qmail@mailweb9.rediffmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
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: 7bit

HI Vidya,
Primary MG IMO is the MG that was in communication with the MGC before
failure. A secondary(Redundant) MG is going to takeover the primary(failed)
MGs terminations.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
vidya g
Sent: Monday, January 28, 2002 6:04 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT



hi

   In RFC section 7.2.8 service change reason explanation for failover is
given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy


_______________________________________________
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


From daemon@optimus.ietf.org  Mon Jan 28 09:32:29 2002
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 JAA27126
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 09:32:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA14468
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 09:32:32 -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 JAA13632;
	Mon, 28 Jan 2002 09:21:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13601
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 09:21:25 -0500 (EST)
Received: from huginn.ctccom.net (Huginn.CTCCom.net [207.190.194.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26724
	for <megaco@ietf.org>; Mon, 28 Jan 2002 09:21:21 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by huginn.ctccom.net (Mirapoint)
	with SMTP id AFV69055;
	Mon, 28 Jan 2002 09:18:56 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'vidya  g'" <vdy73@rediffmail.com>, <megaco@ietf.org>
Subject: RE: [Megaco] DOUBT
Date: Mon, 28 Jan 2002 09:13:49 -0500
Message-ID: <001301c1a806$02e35e90$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <20020128110419.18351.qmail@mailweb9.rediffmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
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: 7bit

HI Vidya,
Primary MG IMO is the MG that was in communication with the MGC before
failure. A secondary(Redundant) MG is going to takeover the primary(failed)
MGs terminations.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
vidya g
Sent: Monday, January 28, 2002 6:04 AM
To: megaco@ietf.org
Subject: [Megaco] DOUBT



hi

   In RFC section 7.2.8 service change reason explanation for failover is
given as below

 6) Failover - sent from MG to MGC to indicate the primary MG is out
      of service and a secondary MG is taking over.

  What is this primary MG here.. ?

vdy


_______________________________________________
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



From megaco-admin@ietf.org  Mon Jan 28 18:49:39 2002
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 SAA11433
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 18:49:39 -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 SAA10927;
	Mon, 28 Jan 2002 18:38:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA10896
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 18:38:25 -0500 (EST)
Received: from hutmail.com ([61.79.57.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11270
	for <megaco@ietf.org>; Mon, 28 Jan 2002 18:38:15 -0500 (EST)
Message-Id: <200201282338.SAA11270@ietf.org>
Reply-To: turbozetq@hutmail.com
From: Lee <turbozetq@hutmail.com>
To: <megaco@ietf.org>
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 29 Jan 2002 08:36:24 +0900
X-User: 2.6-hkilfmmu-hojlnt-Ffkiq
Subject: [Megaco] [±¤°í]ÃÖ°íÀÇ È«º¸µ¥ÀÌÅÍÀÔ´Ï´Ù.
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

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=euc-kr">
<style>
<!-- A:link { text-decoration:none; } A:visited { text-decoration:none; } A:active { text-decoration:none; } A:hover { text-decoration:none; background:#C6E3F7; } -->
</style>
</head>
<body oncontextmenu="return false" bgcolor="white" text="black" link="blue" vlink="purple" alink ="red" ondragstart ="return false" onselectstart="return false">
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><br>¾È³çÇÏ½Ê´Ï±î? ¸ÞÀÏµ¥ÀÌÅÍ¸¦ Àú·ÅÇÑ 
°¡°Ý¿¡ µå¸³´Ï´Ù. 
°ü½É¾øÀ¸½Ã¸é ¸ÞÀÏÀ» »èÁ¦ÇØ ÁÖ½Ê½Ã¿À.<br><font face="±¼¸²">º» ¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í»çÇ×¿¡ ÀÇ°ÅÇÏ¿© Á¦¸ñ¿¡ 
[±¤°í]¶ó Ç¥½ÃµÈ ¸ÞÀÏÀÔ´Ï´Ù.<br>º» ³»¿ëÀº ½ºÆÔ¸ÞÀÏÀÇ À¯Çü¿¡ ¾Æ¹«°Íµµ ¼ÓÇÏÁö ¾Ê½À´Ï´Ù.(ÇÇ¶ó¹Ìµå, 
Çà¿îÀÇÆíÁö, ¼ºÀÎ°ü·ÃÈ«º¸ µî)<br>¶ÇÇÑ °¢ »çÀÌÆ®ÀÇ °ø°³°Ô½ÃÆÇ¿¡¼­ ÀÓÀÇÃßÃâÇÑ °ÍÀÌ¹Ç·Î ±ÍÇÏÀÇ 
½Å¿ëÁ¤º¸¿Í ¾Æ¹«·± ¿¬°üÀÌ ¾ø½À´Ï´Ù.<br><br>ÇÁ·Î±×·¥À¸·Î ÃßÃâÇÏ¿©&nbsp;ÀÛ¾÷ÇÑ 
¸ÞÀÏµ¥ÀÌÅÍÀÇ Æ¯Â¡Àº ´ÙÀ½°ú °°½À´Ï´Ù.<br></font><font color="#3366ff"><b>´ÙÀ½¿ìÇ¥Á¦?</b></font> 
¾È½ÉÇÏ½Ê½Ã¿À. Ã¶ÀúÇÑ ÀÛ¾÷À¸·Î ÇÑ¸ÞÀÏÀÌ ¾ø½À´Ï´Ù. (ÇÑ¸ÞÀÏ Æ÷ÇÔµÈ °Íµµ ÀÖÀ½)<br><font color="#3366ff"><b>Áßº¹¸ÞÀÏ?</b></font> 
¾È½ÉÇÏ½Ê½Ã¿À. Áßº¹¸ÞÀÏÀÌ ¾ø½À´Ï´Ù. ¼ö½Å°ÅºÎ¿¡ Æí¸®ÇÕ´Ï´Ù.<br><font color="#3366ff"><b>ÅëÇÕ?</b></font><font color="teal"><b> 
</b></font>Æí¸®ÇÏ°Ô »ç¿ëÇÏ½Ãµµ·Ï ¶È°°Àº °³¼ö·Î ³ª´©¾ú½À´Ï´Ù.<br><font color="#3366ff"><b>°¡°Ý?</b></font> Àú·ÅÇÕ´Ï´Ù. 
ºñ½ÎÁö ¾Ê½À´Ï´Ù.<br><font color="#3366ff"><b>È£È¯?</b></font> ÇÑÁÙ¿¡ 
ÇÏ³ª¾¿, ±×¸®°í TXT·Î ÀúÀåµÇ¾î ÀÖ½À´Ï´Ù.<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;¾î¶² 
ÇÁ·Î±×·¥°úµµ È£È¯°¡´ÉÇÕ´Ï´Ù.<br><br>...µîµîÀÇ ÀåÁ¡ÀÌ ÀÖ½À´Ï´Ù.<br>µå¶ó¸¶Æ½ÇÑ È«º¸¸¦ 
À§ÇÑ ÇÊ¼öµ¥ÀÌÅÍ! ÀÌ·± ±âÈ¸´Â ´Ù½Ã¿ÀÁö ¾Ê½À´Ï´Ù.<br>»çÀÌÆ®¸¦ Âü°íÇØ ÁÖ½Ê½Ã¿À. °ÇÀüÇÑ ¿ëµµ·Î ¾²Áö 
¾Ê´Â ºÐ¿¡°Ô ÆÇ¸ÅÇÏÁö ¾ÊÀ¸¸ç,<br>°¢Á¾ ÀÌ¿ë¿ëµµ¸¦ Á¢¼öÈÄ, ¾ö¼±ÇÏ¿© ¸îºÐ¿¡°Ô¸¸ ÆÇ¸ÅÇÕ´Ï´Ù.</span></p>
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><a href="http://move.to/adver" target="_blank"><b><font color="#0000cc">move.to/adver</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;</font><a href="http://come.to/adver" target="_blank"><font color="#0000cc">come.to/adver</font></a></b><a href="http://adver.ce.ro" target="_blank"><b><font color="#0000cc"><br>adver.ce.ro</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b><a href="http://adver.pe.ky" target="_blank"><b><font color="#0000cc">adver.pe.ky</font></b></a><font color="#0000cc"><b><br></b></font><a href="http://adver.ox.ro" target="_blank"><b><font color="#0000cc">adver.ox.ro</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b></span></p>
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><font color="black">Á¢¼ÓÀÌ 
´À¸®¸é adver2.(ce.ro / pe.ky / ox.ro)·Î Á¢¼ÓÇØ ÁÖ½Ê½Ã¿À.<br>°øÁö¾øÀÌ Áß´ÜµÇ¸é 
adver3, adver4, 5...ÀÌ·¸°Ô Á¢¼ÓÇÏ½Ã¸é µË´Ï´Ù.<br>ÀÌÀ¯¾øÀÌ »çÀÌÆ®¸¦ ºñ¹æ, ¹æÇØÇÏ´Â »ç¶÷¿¡°Ô ¼ÕÇØ¹è»óÀ» ¿ä±¸ÇÕ´Ï´Ù.<br>º» »çÀÌÆ®´Â È¸»ç³ª ±â¾÷ÀÌ 
¾Æ´Õ´Ï´Ù. ¿ÀÇØ¸¶½Ã±æ ¹Ù¶ø´Ï´Ù.<br><b>¶ÇÇÑ º» ¸ÞÀÏÀº »ç¿ëÀÚÀÇ ÆíÀÇ¸¦ À§ÇØ Àý´ë ÇÑ¹øÀÌ»ó 
¹ß¼ÛÇÏÁö ¾Ê½À´Ï´Ù.<br>µû¶ó¼­ ¼ö½Å°ÅºÎÇÏ½Ç ÇÊ¿ä°¡ ¾ø½À´Ï´Ù.</b><br>¹®ÀÇ»çÇ× ÀÖÀ¸½Ã¸é </font><A href="mailto:adver67@hotmail.com"><font color="black"><u>¸ÞÀÏ</u></font></a><font color="black">ÁÖ½Ê½Ã¿À.</font></span></p>
</body>
</html>

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


From daemon@optimus.ietf.org  Mon Jan 28 18:49:40 2002
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 SAA11443
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 18:49:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11388
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 18:49:43 -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 SAA10927;
	Mon, 28 Jan 2002 18:38:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA10896
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 18:38:25 -0500 (EST)
Received: from hutmail.com ([61.79.57.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11270
	for <megaco@ietf.org>; Mon, 28 Jan 2002 18:38:15 -0500 (EST)
Message-Id: <200201282338.SAA11270@ietf.org>
Reply-To: turbozetq@hutmail.com
From: Lee <turbozetq@hutmail.com>
To: <megaco@ietf.org>
Mime-Version: 1.0
Content-Type: text/html; charset="ks_c_5601-1987"
Date: Tue, 29 Jan 2002 08:36:24 +0900
X-User: 2.6-hkilfmmu-hojlnt-Ffkiq
Subject: [Megaco] [±¤°í]ÃÖ°íÀÇ È«º¸µ¥ÀÌÅÍÀÔ´Ï´Ù.
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

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=euc-kr">
<style>
<!-- A:link { text-decoration:none; } A:visited { text-decoration:none; } A:active { text-decoration:none; } A:hover { text-decoration:none; background:#C6E3F7; } -->
</style>
</head>
<body oncontextmenu="return false" bgcolor="white" text="black" link="blue" vlink="purple" alink ="red" ondragstart ="return false" onselectstart="return false">
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><br>¾È³çÇÏ½Ê´Ï±î? ¸ÞÀÏµ¥ÀÌÅÍ¸¦ Àú·ÅÇÑ 
°¡°Ý¿¡ µå¸³´Ï´Ù. 
°ü½É¾øÀ¸½Ã¸é ¸ÞÀÏÀ» »èÁ¦ÇØ ÁÖ½Ê½Ã¿À.<br><font face="±¼¸²">º» ¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í»çÇ×¿¡ ÀÇ°ÅÇÏ¿© Á¦¸ñ¿¡ 
[±¤°í]¶ó Ç¥½ÃµÈ ¸ÞÀÏÀÔ´Ï´Ù.<br>º» ³»¿ëÀº ½ºÆÔ¸ÞÀÏÀÇ À¯Çü¿¡ ¾Æ¹«°Íµµ ¼ÓÇÏÁö ¾Ê½À´Ï´Ù.(ÇÇ¶ó¹Ìµå, 
Çà¿îÀÇÆíÁö, ¼ºÀÎ°ü·ÃÈ«º¸ µî)<br>¶ÇÇÑ °¢ »çÀÌÆ®ÀÇ °ø°³°Ô½ÃÆÇ¿¡¼­ ÀÓÀÇÃßÃâÇÑ °ÍÀÌ¹Ç·Î ±ÍÇÏÀÇ 
½Å¿ëÁ¤º¸¿Í ¾Æ¹«·± ¿¬°üÀÌ ¾ø½À´Ï´Ù.<br><br>ÇÁ·Î±×·¥À¸·Î ÃßÃâÇÏ¿©&nbsp;ÀÛ¾÷ÇÑ 
¸ÞÀÏµ¥ÀÌÅÍÀÇ Æ¯Â¡Àº ´ÙÀ½°ú °°½À´Ï´Ù.<br></font><font color="#3366ff"><b>´ÙÀ½¿ìÇ¥Á¦?</b></font> 
¾È½ÉÇÏ½Ê½Ã¿À. Ã¶ÀúÇÑ ÀÛ¾÷À¸·Î ÇÑ¸ÞÀÏÀÌ ¾ø½À´Ï´Ù. (ÇÑ¸ÞÀÏ Æ÷ÇÔµÈ °Íµµ ÀÖÀ½)<br><font color="#3366ff"><b>Áßº¹¸ÞÀÏ?</b></font> 
¾È½ÉÇÏ½Ê½Ã¿À. Áßº¹¸ÞÀÏÀÌ ¾ø½À´Ï´Ù. ¼ö½Å°ÅºÎ¿¡ Æí¸®ÇÕ´Ï´Ù.<br><font color="#3366ff"><b>ÅëÇÕ?</b></font><font color="teal"><b> 
</b></font>Æí¸®ÇÏ°Ô »ç¿ëÇÏ½Ãµµ·Ï ¶È°°Àº °³¼ö·Î ³ª´©¾ú½À´Ï´Ù.<br><font color="#3366ff"><b>°¡°Ý?</b></font> Àú·ÅÇÕ´Ï´Ù. 
ºñ½ÎÁö ¾Ê½À´Ï´Ù.<br><font color="#3366ff"><b>È£È¯?</b></font> ÇÑÁÙ¿¡ 
ÇÏ³ª¾¿, ±×¸®°í TXT·Î ÀúÀåµÇ¾î ÀÖ½À´Ï´Ù.<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;¾î¶² 
ÇÁ·Î±×·¥°úµµ È£È¯°¡´ÉÇÕ´Ï´Ù.<br><br>...µîµîÀÇ ÀåÁ¡ÀÌ ÀÖ½À´Ï´Ù.<br>µå¶ó¸¶Æ½ÇÑ È«º¸¸¦ 
À§ÇÑ ÇÊ¼öµ¥ÀÌÅÍ! ÀÌ·± ±âÈ¸´Â ´Ù½Ã¿ÀÁö ¾Ê½À´Ï´Ù.<br>»çÀÌÆ®¸¦ Âü°íÇØ ÁÖ½Ê½Ã¿À. °ÇÀüÇÑ ¿ëµµ·Î ¾²Áö 
¾Ê´Â ºÐ¿¡°Ô ÆÇ¸ÅÇÏÁö ¾ÊÀ¸¸ç,<br>°¢Á¾ ÀÌ¿ë¿ëµµ¸¦ Á¢¼öÈÄ, ¾ö¼±ÇÏ¿© ¸îºÐ¿¡°Ô¸¸ ÆÇ¸ÅÇÕ´Ï´Ù.</span></p>
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><a href="http://move.to/adver" target="_blank"><b><font color="#0000cc">move.to/adver</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;</font><a href="http://come.to/adver" target="_blank"><font color="#0000cc">come.to/adver</font></a></b><a href="http://adver.ce.ro" target="_blank"><b><font color="#0000cc"><br>adver.ce.ro</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b><a href="http://adver.pe.ky" target="_blank"><b><font color="#0000cc">adver.pe.ky</font></b></a><font color="#0000cc"><b><br></b></font><a href="http://adver.ox.ro" target="_blank"><b><font color="#0000cc">adver.ox.ro</font></b></a><b><font color="#0000cc"> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</font></b></span></p>
<p style="LINE-HEIGHT: 113%"><span style="FONT-SIZE: 10pt"><font color="black">Á¢¼ÓÀÌ 
´À¸®¸é adver2.(ce.ro / pe.ky / ox.ro)·Î Á¢¼ÓÇØ ÁÖ½Ê½Ã¿À.<br>°øÁö¾øÀÌ Áß´ÜµÇ¸é 
adver3, adver4, 5...ÀÌ·¸°Ô Á¢¼ÓÇÏ½Ã¸é µË´Ï´Ù.<br>ÀÌÀ¯¾øÀÌ »çÀÌÆ®¸¦ ºñ¹æ, ¹æÇØÇÏ´Â »ç¶÷¿¡°Ô ¼ÕÇØ¹è»óÀ» ¿ä±¸ÇÕ´Ï´Ù.<br>º» »çÀÌÆ®´Â È¸»ç³ª ±â¾÷ÀÌ 
¾Æ´Õ´Ï´Ù. ¿ÀÇØ¸¶½Ã±æ ¹Ù¶ø´Ï´Ù.<br><b>¶ÇÇÑ º» ¸ÞÀÏÀº »ç¿ëÀÚÀÇ ÆíÀÇ¸¦ À§ÇØ Àý´ë ÇÑ¹øÀÌ»ó 
¹ß¼ÛÇÏÁö ¾Ê½À´Ï´Ù.<br>µû¶ó¼­ ¼ö½Å°ÅºÎÇÏ½Ç ÇÊ¿ä°¡ ¾ø½À´Ï´Ù.</b><br>¹®ÀÇ»çÇ× ÀÖÀ¸½Ã¸é </font><A href="mailto:adver67@hotmail.com"><font color="black"><u>¸ÞÀÏ</u></font></a><font color="black">ÁÖ½Ê½Ã¿À.</font></span></p>
</body>
</html>

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



From megaco-admin@ietf.org  Mon Jan 28 19:30:04 2002
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 TAA12024
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 19:30:04 -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 TAA12562;
	Mon, 28 Jan 2002 19:21:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA12531
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 19:21:38 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11846
	for <megaco@ietf.org>; Mon, 28 Jan 2002 19:21:35 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA26100
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:20:12 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA06499
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:21:34 +1100 (EST)
Message-ID: <3C55EBFA.C3C347A2@ericsson.com.au>
Date: Tue, 29 Jan 2002 11:25:30 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
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: 7bit

G'Day all,

I have uploaded a number of H.248 editors' contributions and company
contributions to the PICTEL website.
http://standard.pictel.com/ftp/avc-site/0202_Gen/

A list of the documents is below. The latest version of H.248 is among
them. Comments?

Regards, Christian

-------- Original Message --------
Subject: Fwd: Uploaded files to Incoming
Date: Thu, 24 Jan 2002 16:27:59 +0900
From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
To: ITU-SG16@echo.jf.INTEL.COM

Dear SG16 experts,

They are now available at /0202_Gen of the avc-site.

At 16:16 +1100 02/01/24, Christian Groves wrote:
>I have placed the following files in the incoming directory. Could you
>please move them to the Geneve directory?
>
>1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
>2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server Package
>3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing Package
>4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
>5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
>6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor Usage
>7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
>descriptor
>8. [DC-xxx_Packages_Guide] Packages Guide
>9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
>10. [DC-xxx_H248v2] Draft H.248v2

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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


From daemon@optimus.ietf.org  Mon Jan 28 19:30:04 2002
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 TAA12033
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jan 2002 19:30:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA12916
	for megaco-archive@odin.ietf.org; Mon, 28 Jan 2002 19:30:06 -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 TAA12562;
	Mon, 28 Jan 2002 19:21:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA12531
	for <megaco@optimus.ietf.org>; Mon, 28 Jan 2002 19:21:38 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11846
	for <megaco@ietf.org>; Mon, 28 Jan 2002 19:21:35 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA26100
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:20:12 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA06499
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:21:34 +1100 (EST)
Message-ID: <3C55EBFA.C3C347A2@ericsson.com.au>
Date: Tue, 29 Jan 2002 11:25:30 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
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: 7bit

G'Day all,

I have uploaded a number of H.248 editors' contributions and company
contributions to the PICTEL website.
http://standard.pictel.com/ftp/avc-site/0202_Gen/

A list of the documents is below. The latest version of H.248 is among
them. Comments?

Regards, Christian

-------- Original Message --------
Subject: Fwd: Uploaded files to Incoming
Date: Thu, 24 Jan 2002 16:27:59 +0900
From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
To: ITU-SG16@echo.jf.INTEL.COM

Dear SG16 experts,

They are now available at /0202_Gen of the avc-site.

At 16:16 +1100 02/01/24, Christian Groves wrote:
>I have placed the following files in the incoming directory. Could you
>please move them to the Geneve directory?
>
>1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
>2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server Package
>3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing Package
>4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
>5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
>6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor Usage
>7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
>descriptor
>8. [DC-xxx_Packages_Guide] Packages Guide
>9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
>10. [DC-xxx_H248v2] Draft H.248v2

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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



From megaco-admin@ietf.org  Tue Jan 29 00:39:01 2002
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 AAA18090
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 00:39:01 -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 AAA24292;
	Tue, 29 Jan 2002 00:21:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA24261
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 00:21:55 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17740
	for <megaco@ietf.org>; Tue, 29 Jan 2002 00:21:51 -0500 (EST)
Received: (qmail 1071 invoked by uid 510); 29 Jan 2002 05:21:09 -0000
Date: 29 Jan 2002 05:21:09 -0000
Message-ID: <20020129052109.1070.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 29 Jan 2002 05:21:08 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: Re: RE: [Megaco] DOUBT
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id AAA24263
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



hi

   Does it means that we need to maintain a 'hotstandby' for all MGs ( VMGs ).. ? ofcourse it depends on the application logic and the robustness we wish to have in our application, but what is the necessity that RFC says such a thing .. ? If this is how every one develops tha MG application, please let me know that

regs
vdy


On Mon, 28 Jan 2002 Madhu Babu Brahmanapally wrote :
> HI Vidya,
> Primary MG IMO is the MG that was in communication with 
> the MGC before
> failure. A secondary(Redundant) MG is going to takeover 
> the primary(failed)
> MGs terminations.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.or-
> g]On Behalf Of
> vidya g
> Sent: Monday, January 28, 2002 6:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] DOUBT
> 
> 
> 
> hi
> 
>    In RFC section 7.2.8 service change reason 
> explanation for failover is
> given as below
> 
>  6) Failover - sent from MG to MGC to indicate the 
> primary MG is out
>       of service and a secondary MG is taking over.
> 
>   What is this primary MG here.. ?
> 
> vdy
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Tue Jan 29 00:39:06 2002
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 AAA18100
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 00:39:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA25117
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 00:39:04 -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 AAA24292;
	Tue, 29 Jan 2002 00:21:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA24261
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 00:21:55 -0500 (EST)
Received: from mailweb31.rediffmail.com ([203.199.83.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17740
	for <megaco@ietf.org>; Tue, 29 Jan 2002 00:21:51 -0500 (EST)
Received: (qmail 1071 invoked by uid 510); 29 Jan 2002 05:21:09 -0000
Date: 29 Jan 2002 05:21:09 -0000
Message-ID: <20020129052109.1070.qmail@mailweb31.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 29 Jan 2002 05:21:08 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: Re: RE: [Megaco] DOUBT
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id AAA24263
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



hi

   Does it means that we need to maintain a 'hotstandby' for all MGs ( VMGs ).. ? ofcourse it depends on the application logic and the robustness we wish to have in our application, but what is the necessity that RFC says such a thing .. ? If this is how every one develops tha MG application, please let me know that

regs
vdy


On Mon, 28 Jan 2002 Madhu Babu Brahmanapally wrote :
> HI Vidya,
> Primary MG IMO is the MG that was in communication with 
> the MGC before
> failure. A secondary(Redundant) MG is going to takeover 
> the primary(failed)
> MGs terminations.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.or-
> g]On Behalf Of
> vidya g
> Sent: Monday, January 28, 2002 6:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] DOUBT
> 
> 
> 
> hi
> 
>    In RFC section 7.2.8 service change reason 
> explanation for failover is
> given as below
> 
>  6) Failover - sent from MG to MGC to indicate the 
> primary MG is out
>       of service and a secondary MG is taking over.
> 
>   What is this primary MG here.. ?
> 
> vdy
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 29 08:22:56 2002
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 IAA02361
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 08:22:52 -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 IAA28757;
	Tue, 29 Jan 2002 08:04:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28719
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 08:04:07 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01978
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:04:03 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126VNK>; Tue, 29 Jan 2002 08:03:35 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404948@wench>
From: Carl Rutter <crutter@telica.com>
To: "'vidya  g'" <vdy73@rediffmail.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: RE: [Megaco] DOUBT
Date: Tue, 29 Jan 2002 08:03:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I don't believe MG redundancy is required.
However since many of the systems designed
with MEGACO are for the Telco space and
must high reliability
the redundancy issues are covered.

Carl 

-----Original Message-----
From: vidya g [mailto:vdy73@rediffmail.com]
Sent: Tuesday, January 29, 2002 12:21 AM
To: Madhu Babu Brahmanapally
Cc: megaco@ietf.org
Subject: Re: RE: [Megaco] DOUBT




hi

   Does it means that we need to maintain a 'hotstandby' for all MGs ( VMGs
).. ? ofcourse it depends on the application logic and the robustness we
wish to have in our application, but what is the necessity that RFC says
such a thing .. ? If this is how every one develops tha MG application,
please let me know that

regs
vdy


On Mon, 28 Jan 2002 Madhu Babu Brahmanapally wrote :
> HI Vidya,
> Primary MG IMO is the MG that was in communication with 
> the MGC before
> failure. A secondary(Redundant) MG is going to takeover 
> the primary(failed)
> MGs terminations.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.or-
> g]On Behalf Of
> vidya g
> Sent: Monday, January 28, 2002 6:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] DOUBT
> 
> 
> 
> hi
> 
>    In RFC section 7.2.8 service change reason 
> explanation for failover is
> given as below
> 
>  6) Failover - sent from MG to MGC to indicate the 
> primary MG is out
>       of service and a secondary MG is taking over.
> 
>   What is this primary MG here.. ?
> 
> vdy
> 
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Tue Jan 29 08:22:57 2002
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 IAA02369
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 08:22:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA29725
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 08:23:00 -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 IAA28757;
	Tue, 29 Jan 2002 08:04:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28719
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 08:04:07 -0500 (EST)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01978
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:04:03 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <DF126VNK>; Tue, 29 Jan 2002 08:03:35 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404948@wench>
From: Carl Rutter <crutter@telica.com>
To: "'vidya  g'" <vdy73@rediffmail.com>,
        Madhu Babu Brahmanapally
	 <madhubabu@kenetec.com>
Cc: megaco@ietf.org
Subject: RE: RE: [Megaco] DOUBT
Date: Tue, 29 Jan 2002 08:03:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

I don't believe MG redundancy is required.
However since many of the systems designed
with MEGACO are for the Telco space and
must high reliability
the redundancy issues are covered.

Carl 

-----Original Message-----
From: vidya g [mailto:vdy73@rediffmail.com]
Sent: Tuesday, January 29, 2002 12:21 AM
To: Madhu Babu Brahmanapally
Cc: megaco@ietf.org
Subject: Re: RE: [Megaco] DOUBT




hi

   Does it means that we need to maintain a 'hotstandby' for all MGs ( VMGs
).. ? ofcourse it depends on the application logic and the robustness we
wish to have in our application, but what is the necessity that RFC says
such a thing .. ? If this is how every one develops tha MG application,
please let me know that

regs
vdy


On Mon, 28 Jan 2002 Madhu Babu Brahmanapally wrote :
> HI Vidya,
> Primary MG IMO is the MG that was in communication with 
> the MGC before
> failure. A secondary(Redundant) MG is going to takeover 
> the primary(failed)
> MGs terminations.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.or-
> g]On Behalf Of
> vidya g
> Sent: Monday, January 28, 2002 6:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] DOUBT
> 
> 
> 
> hi
> 
>    In RFC section 7.2.8 service change reason 
> explanation for failover is
> given as below
> 
>  6) Failover - sent from MG to MGC to indicate the 
> primary MG is out
>       of service and a secondary MG is taking over.
> 
>   What is this primary MG here.. ?
> 
> vdy
> 
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 29 09:43:49 2002
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 JAA04529
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 09:43:44 -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 JAA03883;
	Tue, 29 Jan 2002 09:25:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03854
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 09:25:41 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04073
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:25:37 -0500 (EST)
Received: from Bala (bruce [172.16.137.54] (may be forged))
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g0TEPrT04787
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:25:53 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Tue, 29 Jan 2002 09:25:48 -0500
Message-ID: <000e01c1a8d0$d8ffa0e0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <2415C206C515244DBFB12EC0C064A448404948@wench>
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MG 'deadly' failure
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: 7bit

Hi All,

Section 11.4, in RFC3015 talks about failure of a MG as follows:

"  If a MG fails, but is capable of sending a message to the MGC, it
   sends a ServiceChange with an appropriate method (graceful or forced)
   and specifies the Root TerminationID.  When it returns to service, it
   sends a ServiceChange with a "Restart" method."

But it does not talk about the scenario, where MG has a deadly failure,
where it cannot send any message to the MGC. What happens then? Does the
MGC instruct other MGs to take over? 

Lets assume that it does instruct another MG to take over. Does that
mean all the same physical terminations should be connected to both the
MGs at the same time, in order for the user to have the services back
(assuming it's a Residential Gateway)?

From a implementation point of view, do the physical terminations
(actual residential POTS ports) need to be connected to "two" MGs at the
same time in order to have failover when there is a 'deadly' MG crash?

Is there a RFC correction to cover this aspect?

Thanks in advance.

Cheers,
Bala


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


From daemon@optimus.ietf.org  Tue Jan 29 09:43:49 2002
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 JAA04539
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 09:43:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA05003
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 09:43:53 -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 JAA03883;
	Tue, 29 Jan 2002 09:25:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03854
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 09:25:41 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04073
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:25:37 -0500 (EST)
Received: from Bala (bruce [172.16.137.54] (may be forged))
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g0TEPrT04787
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:25:53 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Tue, 29 Jan 2002 09:25:48 -0500
Message-ID: <000e01c1a8d0$d8ffa0e0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <2415C206C515244DBFB12EC0C064A448404948@wench>
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MG 'deadly' failure
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: 7bit

Hi All,

Section 11.4, in RFC3015 talks about failure of a MG as follows:

"  If a MG fails, but is capable of sending a message to the MGC, it
   sends a ServiceChange with an appropriate method (graceful or forced)
   and specifies the Root TerminationID.  When it returns to service, it
   sends a ServiceChange with a "Restart" method."

But it does not talk about the scenario, where MG has a deadly failure,
where it cannot send any message to the MGC. What happens then? Does the
MGC instruct other MGs to take over? 

Lets assume that it does instruct another MG to take over. Does that
mean all the same physical terminations should be connected to both the
MGs at the same time, in order for the user to have the services back
(assuming it's a Residential Gateway)?

From a implementation point of view, do the physical terminations
(actual residential POTS ports) need to be connected to "two" MGs at the
same time in order to have failover when there is a 'deadly' MG crash?

Is there a RFC correction to cover this aspect?

Thanks in advance.

Cheers,
Bala


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



From megaco-admin@ietf.org  Tue Jan 29 09:53:00 2002
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 JAA04800
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 09:53:00 -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 JAA04840;
	Tue, 29 Jan 2002 09:40:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04794
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 09:40:45 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04443
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:40:36 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id IAA21852
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:40:09 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0TEe8m03410
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:40:08 -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 g0TEdmG20054
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:39:48 -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 g0TEdmT02503
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:39:48 -0600 (CST)
Message-ID: <3C56B434.B7F33607@alcatel.com>
Date: Tue, 29 Jan 2002 08:39:48 -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'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <OFA1731B2B.C2D26F93-ON80256B4B.003A8478@uk.marconicomms.com>
Content-Type: multipart/alternative;
 boundary="------------C71BD95717A75F8C478989A7"
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


--------------C71BD95717A75F8C478989A7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I agreed w/Wayne on option d which is how it was before v1 came out.

Then we got into these Reserve parameters discussion and changes
but I didn't think the statement should apply to Property parameters.


Wayne Cutler wrote:

>
>
> What about an option d) that would regard an absent Property as meaning
> "leave the existing value unchanged"?
>
> As a related question, I note that section 7.1.7 (Local Control Desc.)of
> the spec.
> says that:-
>
> "A new setting of the LocalControl Descriptor completely replaces the
> previous setting of that descriptor in the MG.  Thus to retain information
> from
> the previous setting the MGC must include that information in the new
> setting".
>
> Similar statements are made for the Events & Signals Descriptors.
>
> In the case where an MG supports a number of packages, this text is saying
> that an MGC
> wishing to change data/attributes in one Package in a given Descriptor is
> forced to repeat any previous data against any other Packages. This is
> perverse. So, can this text be qualified to say that the new Descriptor
> replaces only data relating to Packages present in the new/latest message?
>
> Regards,
> Wayne.
>
> ------------
> This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

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



--------------C71BD95717A75F8C478989A7
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>I&nbsp;agreed w/Wayne on option d which is how it was before v1 came
out.
<p>Then we got into these Reserve parameters discussion and changes
<br>but I&nbsp;didn't think the statement should apply to Property parameters.
<br>&nbsp;
<p>Wayne Cutler wrote:
<blockquote TYPE=CITE>&nbsp;
<p>What about an option d) that would regard an absent Property as meaning
<br>"leave the existing value unchanged"?
<p>As a related question, I note that section 7.1.7 (Local Control Desc.)of
<br>the spec.
<br>says that:-
<p>"A new setting of the LocalControl Descriptor completely replaces the
<br>previous setting of that descriptor in the MG.&nbsp; Thus to retain
information
<br>from
<br>the previous setting the MGC must include that information in the new
<br>setting".
<p>Similar statements are made for the Events &amp; Signals Descriptors.
<p>In the case where an MG supports a number of packages, this text is
saying
<br>that an MGC
<br>wishing to change data/attributes in one Package in a given Descriptor
is
<br>forced to repeat any previous data against any other Packages. This
is
<br>perverse. So, can this text be qualified to say that the new Descriptor
<br>replaces only data relating to Packages present in the new/latest message?
<p>Regards,
<br>Wayne.
<p>------------
<br>This e-mail and any attachments are confidential.&nbsp; If you are
not the intended recipient, please notify us immediately by reply e-mail
and then delete this message from your system. Do not copy this e-mail
or any attachments, use the contents for any purpose, or disclose the contents
to any other person: to do so could be a breach of confidence.
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------C71BD95717A75F8C478989A7--


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


From daemon@optimus.ietf.org  Tue Jan 29 09:53:01 2002
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 JAA04811
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 09:53:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA05357
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 09:53:05 -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 JAA04840;
	Tue, 29 Jan 2002 09:40:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04794
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 09:40:45 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04443
	for <megaco@ietf.org>; Tue, 29 Jan 2002 09:40:36 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id IAA21852
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:40:09 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0TEe8m03410
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:40:08 -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 g0TEdmG20054
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:39:48 -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 g0TEdmT02503
	for <megaco@ietf.org>; Tue, 29 Jan 2002 08:39:48 -0600 (CST)
Message-ID: <3C56B434.B7F33607@alcatel.com>
Date: Tue, 29 Jan 2002 08:39:48 -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'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <OFA1731B2B.C2D26F93-ON80256B4B.003A8478@uk.marconicomms.com>
Content-Type: multipart/alternative;
 boundary="------------C71BD95717A75F8C478989A7"
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


--------------C71BD95717A75F8C478989A7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I agreed w/Wayne on option d which is how it was before v1 came out.

Then we got into these Reserve parameters discussion and changes
but I didn't think the statement should apply to Property parameters.


Wayne Cutler wrote:

>
>
> What about an option d) that would regard an absent Property as meaning
> "leave the existing value unchanged"?
>
> As a related question, I note that section 7.1.7 (Local Control Desc.)of
> the spec.
> says that:-
>
> "A new setting of the LocalControl Descriptor completely replaces the
> previous setting of that descriptor in the MG.  Thus to retain information
> from
> the previous setting the MGC must include that information in the new
> setting".
>
> Similar statements are made for the Events & Signals Descriptors.
>
> In the case where an MG supports a number of packages, this text is saying
> that an MGC
> wishing to change data/attributes in one Package in a given Descriptor is
> forced to repeat any previous data against any other Packages. This is
> perverse. So, can this text be qualified to say that the new Descriptor
> replaces only data relating to Packages present in the new/latest message?
>
> Regards,
> Wayne.
>
> ------------
> This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

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



--------------C71BD95717A75F8C478989A7
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>I&nbsp;agreed w/Wayne on option d which is how it was before v1 came
out.
<p>Then we got into these Reserve parameters discussion and changes
<br>but I&nbsp;didn't think the statement should apply to Property parameters.
<br>&nbsp;
<p>Wayne Cutler wrote:
<blockquote TYPE=CITE>&nbsp;
<p>What about an option d) that would regard an absent Property as meaning
<br>"leave the existing value unchanged"?
<p>As a related question, I note that section 7.1.7 (Local Control Desc.)of
<br>the spec.
<br>says that:-
<p>"A new setting of the LocalControl Descriptor completely replaces the
<br>previous setting of that descriptor in the MG.&nbsp; Thus to retain
information
<br>from
<br>the previous setting the MGC must include that information in the new
<br>setting".
<p>Similar statements are made for the Events &amp; Signals Descriptors.
<p>In the case where an MG supports a number of packages, this text is
saying
<br>that an MGC
<br>wishing to change data/attributes in one Package in a given Descriptor
is
<br>forced to repeat any previous data against any other Packages. This
is
<br>perverse. So, can this text be qualified to say that the new Descriptor
<br>replaces only data relating to Packages present in the new/latest message?
<p>Regards,
<br>Wayne.
<p>------------
<br>This e-mail and any attachments are confidential.&nbsp; If you are
not the intended recipient, please notify us immediately by reply e-mail
and then delete this message from your system. Do not copy this e-mail
or any attachments, use the contents for any purpose, or disclose the contents
to any other person: to do so could be a breach of confidence.
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------C71BD95717A75F8C478989A7--


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



From megaco-admin@ietf.org  Tue Jan 29 10:59:07 2002
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 KAA07162
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 10:59:06 -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 KAA08803;
	Tue, 29 Jan 2002 10:51:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08771
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 10:51:35 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06857
	for <megaco@ietf.org>; Tue, 29 Jan 2002 10:51:32 -0500 (EST)
Received: (qmail 21695 invoked by uid 510); 29 Jan 2002 15:51:43 -0000
Date: 29 Jan 2002 15:51:43 -0000
Message-ID: <20020129155143.21694.qmail@mailFA9.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 29 Jan 2002 15:51:43 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA08772
Subject: [Megaco] Auditing Terminations
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


Hello All, 
Assume this scenario, 
MG(TrunkingGW) registered with MGC for the First Time (SvcChange- Restart.)
MGC wants to validate the terminations states, to findout any terminations that are out of Service. 
Inorder to do that MGC sends a audit request to MG as 
MEGACO/1 <anyMGC.com>:2944 
Transaction=1111 { 
   context = - { 
     AuditValue = * { Audit { Media } }
 }
}

The reply message would be very large message, with all the termination details. Is there any smart way to findout the terminations that are outofService.


Thanks in advance

Surya
 


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


From megaco-admin@ietf.org  Tue Jan 29 11:08:53 2002
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 LAA07599
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 11:08:48 -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 LAA09732;
	Tue, 29 Jan 2002 11:01:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09685
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 11:01:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07300
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:01:11 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0TG0hf18510
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:00:43 -0500 (EST)
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 g0TG0gr12062
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:00:42 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ8AVY>; Tue, 29 Jan 2002 11:00:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>,
        "'Wayne Cutler'" <Wayne.Cutler@marconi.com>
Subject: RE: [Megaco] Query about local control descriptor properties
Date: Tue, 29 Jan 2002 11:00:40 -0500
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

This seems like a practical solution for LocalControl, but if we accept it,
we have to change the text of the Recommendation, meaning that it only holds
for H.248v2.  I'll note that we have a real problem of interoperability
here.  My previous note on the interpretation of this clause presented three
alternatives, and I got E-mails (one private) in support of all three of
them.  

I don't quite see Wayne's point on the Signals and Events descriptors.  In
both cases, the semantics of the situation require the repetition of all of
the signals/events you want to keep.  You also need at least the KeepActive
parameter where it applies to signals.  Are you saying, Wayne, that once an
event or signal is specified, then if it is retained in replacement
descriptors it is unnecessary to respecify all the parameters that went
along with it the first time?  I could live with that as an IG
clarification.  Other views?


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, January 29, 2002 9:40 AM
To: 'megaco@ietf.org'
Subject: Re: [Megaco] Query about local control descriptor properties


  
I agreed w/Wayne on option d which is how it was before v1 came out. 
Then we got into these Reserve parameters discussion and changes 
but I didn't think the statement should apply to Property parameters. 
  
Wayne Cutler wrote: 
  
What about an option d) that would regard an absent Property as meaning 
"leave the existing value unchanged"? 
As a related question, I note that section 7.1.7 (Local Control Desc.)of 
the spec. 
says that:- 
"A new setting of the LocalControl Descriptor completely replaces the 
previous setting of that descriptor in the MG.  Thus to retain information 
from 
the previous setting the MGC must include that information in the new 
setting". 
Similar statements are made for the Events & Signals Descriptors. 
In the case where an MG supports a number of packages, this text is saying 
that an MGC 
wishing to change data/attributes in one Package in a given Descriptor is 
forced to repeat any previous data against any other Packages. This is 
perverse. So, can this text be qualified to say that the new Descriptor 
replaces only data relating to Packages present in the new/latest message? 
Regards, 
Wayne. 
------------ 
This e-mail and any attachments are confidential.  If you are not the
intended recipient, please notify us immediately by reply e-mail and then
delete this message from your system. Do not copy this e-mail or any
attachments, use the contents for any purpose, or disclose the contents to
any other person: to do so could be a breach of confidence. 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
-- 
  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


From daemon@optimus.ietf.org  Tue Jan 29 11:57:26 2002
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 KAA07169
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 10:59:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09195
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 10:59:09 -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 KAA08803;
	Tue, 29 Jan 2002 10:51:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08771
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 10:51:35 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06857
	for <megaco@ietf.org>; Tue, 29 Jan 2002 10:51:32 -0500 (EST)
Received: (qmail 21695 invoked by uid 510); 29 Jan 2002 15:51:43 -0000
Date: 29 Jan 2002 15:51:43 -0000
Message-ID: <20020129155143.21694.qmail@mailFA9.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 29 Jan 2002 15:51:43 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA08772
Subject: [Megaco] Auditing Terminations
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


Hello All, 
Assume this scenario, 
MG(TrunkingGW) registered with MGC for the First Time (SvcChange- Restart.)
MGC wants to validate the terminations states, to findout any terminations that are out of Service. 
Inorder to do that MGC sends a audit request to MG as 
MEGACO/1 <anyMGC.com>:2944 
Transaction=1111 { 
   context = - { 
     AuditValue = * { Audit { Media } }
 }
}

The reply message would be very large message, with all the termination details. Is there any smart way to findout the terminations that are outofService.


Thanks in advance

Surya
 


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



From daemon@optimus.ietf.org  Tue Jan 29 11:57:27 2002
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 LAA07619
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 11:08:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA10032
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 11:08:56 -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 LAA09732;
	Tue, 29 Jan 2002 11:01:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09685
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 11:01:15 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07300
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:01:11 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0TG0hf18510
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:00:43 -0500 (EST)
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 g0TG0gr12062
	for <megaco@ietf.org>; Tue, 29 Jan 2002 11:00:42 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ8AVY>; Tue, 29 Jan 2002 11:00:43 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>,
        "'Wayne Cutler'" <Wayne.Cutler@marconi.com>
Subject: RE: [Megaco] Query about local control descriptor properties
Date: Tue, 29 Jan 2002 11:00:40 -0500
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

This seems like a practical solution for LocalControl, but if we accept it,
we have to change the text of the Recommendation, meaning that it only holds
for H.248v2.  I'll note that we have a real problem of interoperability
here.  My previous note on the interpretation of this clause presented three
alternatives, and I got E-mails (one private) in support of all three of
them.  

I don't quite see Wayne's point on the Signals and Events descriptors.  In
both cases, the semantics of the situation require the repetition of all of
the signals/events you want to keep.  You also need at least the KeepActive
parameter where it applies to signals.  Are you saying, Wayne, that once an
event or signal is specified, then if it is retained in replacement
descriptors it is unnecessary to respecify all the parameters that went
along with it the first time?  I could live with that as an IG
clarification.  Other views?


-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, January 29, 2002 9:40 AM
To: 'megaco@ietf.org'
Subject: Re: [Megaco] Query about local control descriptor properties


  
I agreed w/Wayne on option d which is how it was before v1 came out. 
Then we got into these Reserve parameters discussion and changes 
but I didn't think the statement should apply to Property parameters. 
  
Wayne Cutler wrote: 
  
What about an option d) that would regard an absent Property as meaning 
"leave the existing value unchanged"? 
As a related question, I note that section 7.1.7 (Local Control Desc.)of 
the spec. 
says that:- 
"A new setting of the LocalControl Descriptor completely replaces the 
previous setting of that descriptor in the MG.  Thus to retain information 
from 
the previous setting the MGC must include that information in the new 
setting". 
Similar statements are made for the Events & Signals Descriptors. 
In the case where an MG supports a number of packages, this text is saying 
that an MGC 
wishing to change data/attributes in one Package in a given Descriptor is 
forced to repeat any previous data against any other Packages. This is 
perverse. So, can this text be qualified to say that the new Descriptor 
replaces only data relating to Packages present in the new/latest message? 
Regards, 
Wayne. 
------------ 
This e-mail and any attachments are confidential.  If you are not the
intended recipient, please notify us immediately by reply e-mail and then
delete this message from your system. Do not copy this e-mail or any
attachments, use the contents for any purpose, or disclose the contents to
any other person: to do so could be a breach of confidence. 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
-- 
  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



From megaco-admin@ietf.org  Tue Jan 29 12:44:57 2002
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 MAA10898
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 12:44:57 -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 MAA16696;
	Tue, 29 Jan 2002 12:33:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA16668
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 12:33:49 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10602
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:45 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0THXHf04680
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:17 -0500 (EST)
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 g0THXGr17222
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:16 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ8DJ2>; Tue, 29 Jan 2002 12:33:17 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF3B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] MG 'deadly' failure
Date: Tue, 29 Jan 2002 12:33:15 -0500
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

This is in the realm of implementation, not protocol specification.  So no
changes to the RFC are needed.



-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Tuesday, January 29, 2002 9:26 AM
To: megaco@ietf.org
Subject: [Megaco] MG 'deadly' failure


Hi All,

Section 11.4, in RFC3015 talks about failure of a MG as follows:

"  If a MG fails, but is capable of sending a message to the MGC, it
   sends a ServiceChange with an appropriate method (graceful or forced)
   and specifies the Root TerminationID.  When it returns to service, it
   sends a ServiceChange with a "Restart" method."

But it does not talk about the scenario, where MG has a deadly failure,
where it cannot send any message to the MGC. What happens then? Does the
MGC instruct other MGs to take over? 

Lets assume that it does instruct another MG to take over. Does that
mean all the same physical terminations should be connected to both the
MGs at the same time, in order for the user to have the services back
(assuming it's a Residential Gateway)?

From a implementation point of view, do the physical terminations
(actual residential POTS ports) need to be connected to "two" MGs at the
same time in order to have failover when there is a 'deadly' MG crash?

Is there a RFC correction to cover this aspect?

Thanks in advance.

Cheers,
Bala


_______________________________________________
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


From daemon@optimus.ietf.org  Tue Jan 29 12:45:01 2002
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 MAA10912
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 12:45:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA17279
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 12:45:01 -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 MAA16696;
	Tue, 29 Jan 2002 12:33:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA16668
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 12:33:49 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10602
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:45 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0THXHf04680
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:17 -0500 (EST)
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 g0THXGr17222
	for <megaco@ietf.org>; Tue, 29 Jan 2002 12:33:16 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <C8PZ8DJ2>; Tue, 29 Jan 2002 12:33:17 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF3B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] MG 'deadly' failure
Date: Tue, 29 Jan 2002 12:33:15 -0500
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

This is in the realm of implementation, not protocol specification.  So no
changes to the RFC are needed.



-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Tuesday, January 29, 2002 9:26 AM
To: megaco@ietf.org
Subject: [Megaco] MG 'deadly' failure


Hi All,

Section 11.4, in RFC3015 talks about failure of a MG as follows:

"  If a MG fails, but is capable of sending a message to the MGC, it
   sends a ServiceChange with an appropriate method (graceful or forced)
   and specifies the Root TerminationID.  When it returns to service, it
   sends a ServiceChange with a "Restart" method."

But it does not talk about the scenario, where MG has a deadly failure,
where it cannot send any message to the MGC. What happens then? Does the
MGC instruct other MGs to take over? 

Lets assume that it does instruct another MG to take over. Does that
mean all the same physical terminations should be connected to both the
MGs at the same time, in order for the user to have the services back
(assuming it's a Residential Gateway)?

From a implementation point of view, do the physical terminations
(actual residential POTS ports) need to be connected to "two" MGs at the
same time in order to have failover when there is a 'deadly' MG crash?

Is there a RFC correction to cover this aspect?

Thanks in advance.

Cheers,
Bala


_______________________________________________
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



From megaco-admin@ietf.org  Tue Jan 29 15:28:01 2002
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 PAA19931
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 15:28:01 -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 PAA27122;
	Tue, 29 Jan 2002 15:19:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27089
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 15:19:25 -0500 (EST)
Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19685
	for <megaco@ietf.org>; Tue, 29 Jan 2002 15:19:17 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0TKIde24196;
	Tue, 29 Jan 2002 15:18:40 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAX1Y7>; Tue, 29 Jan 2002 15:18:38 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01BA3E14@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Christian Groves <Christian.Groves@ericsson.com.au>,
        megaco ietf
	 <megaco@ietf.org>
Date: Tue, 29 Jan 2002 15:18:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A902.20625AF0"
Subject: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A902.20625AF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Actually, I have some.

The IG posted there is lacking the digit collection changes agreed upon =
in
Dublin.  Here are the changes as agreed upon:

Section 7.1.14.2:
Change: "The timers are configurable parameters to a DigitMap.  The =
Start
timer is started at the beginning of every digit map use, but can be
overridden."
To: "Default values of these timers should be provisioned on the MG, =
but can
be overridden by values specified within the DigitMap."

Section 7.1.14.3:
Change: "Finally, if conflicting timing specifiers are in effect in
different alternative sequences, the results are undefined."
To: "Finally, if conflicting timing specifiers are in effect in =
different
alternative sequences, the long timer shall be used."

Change: "The value of this threshold is assumed to be provisioned in =
the
MG."
To: "The value of this threshold is assumed to be provisioned in the =
MG,
but, like the T, L, and S timers, can be overridden by specification =
within
the DigitMap."

Section 7.1.14.4:
Change: "Subsequent events in the package are processed as per the =
currently
active event processing mechanisms."
To: "Subsequent digit events in the package are processed as follows:

=B7if EventBufferControl is ON, subsequent digit events are processed =
in the
same way as any other events;

=B7if EventBufferControl is OFF, if the active EventsDescriptor did not
change, and if individual digit events are not enabled within that
descriptor, then digit buffering will be initiated.  Buffering will =
continue
until the buffering time specified in the original digit map completion
event has expired or until the active EventsDescriptor is replaced.

The digit buffer shall take the logical form of a dial string which =
includes
the digit characters as represented in the digit map, possibly preceded =
by
'Z'.  The threshold value of tone duration used to identify long events
shall be the same as that used with the most recently completed digit =
map.

Buffering time defaults to zero (no buffering) unless explicitly set
otherwise within the digit map completion event.  If buffering ceases =
due to
buffering timer expiry, the contents of the digit buffer are discarded.

If buffering was stopped by a new EventsDescriptor, then if that
EventsDescriptor contains a new digit map completion event from the =
same
package as the previous one, any buffered digits are processed against =
the
digit map as described below.  Buffered digits not consumed by the new =
digit
map are handled as if they had were observed after that map completed.

If instead the new EventsDescriptor enables the reporting of individual
digit events, the entire set of buffered digits shall immediately be
processed, the applicable events reported, and the buffer cleared.

Finally, if the new EventsDescriptor enables neither a digit map =
completion
event nor the reporting of individual digit events from the package
concerned, the buffer contents are discarded and buffering is =
terminated."

(All of the paragraphs following the second bullet are part of that =
bullet
item.)

Section 7.1.14.5:

Change: "2. At each step, a timer is set to wait for the next event, =
based
either on the default timing rules given above or on explicit timing
specified in one or more alternative event sequences. If the timer =
expires
and a member of the candidate set of alternatives is fully satisfied, a
timeout completion with full match is reported.  If the timer expires =
and
part or none of any candidate alternative is satisfied, a timeout =
completion
with partial match is reported."
To: "2. At each step, if buffered digits are available, the oldest one =
(with
possible accompanying long digit (Z) qualifier) is removed from the =
buffer
and processing moves to the next step as if the digit event had just =
been
observed.  Otherwise a timer is set to wait for the next event, based =
either
on the default timing rules given above or on explicit timing specified =
in
one or more alternative event sequences. If the timer expires and a =
member
of the candidate set of alternatives is fully satisfied, a timeout
completion with full match is reported.  If the timer expires and part =
or
none of any candidate alternative is satisfied, a timeout completion =
with
partial match is reported.  In either case, if the digit map completion
event allows for detailed timeout reporting, the reported dial string =
will
end with 'L' or 'S' as appropriate."

Change (step 5): "The event removed from the current dial string will =
then
be reported as per the currently active event processing mechanisms."
To: "The event removed from the current dial string will then be =
reported as
a separate event, buffered, or discarded according to the rules =
described in
the previous section.  This statement is qualified as follows:

a) The digit map completion event may specify that the event be =
reported as
a parameter of that event.  This occurs independently of subsequent
processing of the digit event. =20

b) The digit map completion event may specify that the extra digit =
should be
discarded.  In this case, it is discarded immediately.  Any buffering =
or
other processing applies only to subsequent events."

Section 6.1.14.7:

Change: "=B7 the events in the package containing the specified digit =
map
completion event other than the completion event itself are not =
individually
notified, and"
To: "=B7 the events in the package containing the specified digit map
completion event other than the completion event itself are not =
individually
notified and have no side-effects unless separately enabled, and"

Change: "=B7 an event that triggers a partial match completion event is =
not
recognized and therefore has no side effects until reprocessed =
following the
recognition of the digit map completion event."
To: "=B7 an event that triggers a partial match completion event is not
recognized and therefore has no side effects unless and until =
reprocessed
following the recognition of the digit map completion event.  Similarly
buffered digit events are not recognized and have no side effects until
processed."

Annex C:

Change:=20

   digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer =
COMMA]
                          ["L" COLON Timer COMMA] digitMap=20
   Timer                =3D 1*2DIGIT

To:

   digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer =
COMMA]
                          ["L" COLON Timer COMMA] ["Z" COLON Timer =
COMMA]
                           digitMap=20
   Timer                =3D 1*2DIGIT
   ; Units are seconds for T, S, and L timers, and hundreds of =
milliseconds
for Z timer. =20
   ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to =
9.9 s.

Kevin


-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, January 28, 2002 7:26 PM
To: megaco ietf
Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]


G'Day all,

I have uploaded a number of H.248 editors' contributions and company
contributions to the PICTEL website.
http://standard.pictel.com/ftp/avc-site/0202_Gen/

A list of the documents is below. The latest version of H.248 is among
them. Comments?

Regards, Christian

-------- Original Message --------
Subject: Fwd: Uploaded files to Incoming
Date: Thu, 24 Jan 2002 16:27:59 +0900
From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
To: ITU-SG16@echo.jf.INTEL.COM

Dear SG16 experts,

They are now available at /0202_Gen of the avc-site.

At 16:16 +1100 02/01/24, Christian Groves wrote:
>I have placed the following files in the incoming directory. Could you
>please move them to the Geneve directory?
>
>1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
>2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server Package
>3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing =
Package
>4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
>5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
>6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor Usage
>7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
>descriptor
>8. [DC-xxx_Packages_Guide] Packages Guide
>9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
>10. [DC-xxx_H248v2] Draft H.248v2

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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

------_=_NextPart_001_01C1A902.20625AF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Fwd: Fwd: Uploaded files to Incoming]</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Actually, I have some.</FONT>
</P>

<P><FONT SIZE=3D2>The IG posted there is lacking the digit collection =
changes agreed upon in Dublin.&nbsp; Here are the changes as agreed =
upon:</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.2:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;The timers are configurable parameters =
to a DigitMap.&nbsp; The Start timer is started at the beginning of =
every digit map use, but can be overridden.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;Default values of these timers should be =
provisioned on the MG, but can be overridden by values specified within =
the DigitMap.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.3:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;Finally, if conflicting timing =
specifiers are in effect in different alternative sequences, the =
results are undefined.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;Finally, if conflicting timing specifiers =
are in effect in different alternative sequences, the long timer shall =
be used.&quot;</FONT></P>

<P><FONT SIZE=3D2>Change: &quot;The value of this threshold is assumed =
to be provisioned in the MG.&quot;</FONT>
<BR><FONT SIZE=3D2>To: &quot;The value of this threshold is assumed to =
be provisioned in the MG, but, like the T, L, and S timers, can be =
overridden by specification within the DigitMap.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.4:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;Subsequent events in the package are =
processed as per the currently active event processing =
mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>To: &quot;Subsequent digit events in the package are =
processed as follows:</FONT>
</P>

<P><FONT SIZE=3D2>=B7if EventBufferControl is ON, subsequent digit =
events are processed in the same way as any other events;</FONT>
</P>

<P><FONT SIZE=3D2>=B7if EventBufferControl is OFF, if the active =
EventsDescriptor did not change, and if individual digit events are not =
enabled within that descriptor, then digit buffering will be =
initiated.&nbsp; Buffering will continue until the buffering time =
specified in the original digit map completion event has expired or =
until the active EventsDescriptor is replaced.</FONT></P>

<P><FONT SIZE=3D2>The digit buffer shall take the logical form of a =
dial string which includes the digit characters as represented in the =
digit map, possibly preceded by 'Z'.&nbsp; The threshold value of tone =
duration used to identify long events shall be the same as that used =
with the most recently completed digit map.</FONT></P>

<P><FONT SIZE=3D2>Buffering time defaults to zero (no buffering) unless =
explicitly set otherwise within the digit map completion event.&nbsp; =
If buffering ceases due to buffering timer expiry, the contents of the =
digit buffer are discarded.</FONT></P>

<P><FONT SIZE=3D2>If buffering was stopped by a new EventsDescriptor, =
then if that EventsDescriptor contains a new digit map completion event =
from the same package as the previous one, any buffered digits are =
processed against the digit map as described below.&nbsp; Buffered =
digits not consumed by the new digit map are handled as if they had =
were observed after that map completed.</FONT></P>

<P><FONT SIZE=3D2>If instead the new EventsDescriptor enables the =
reporting of individual digit events, the entire set of buffered digits =
shall immediately be processed, the applicable events reported, and the =
buffer cleared.</FONT></P>

<P><FONT SIZE=3D2>Finally, if the new EventsDescriptor enables neither =
a digit map completion event nor the reporting of individual digit =
events from the package concerned, the buffer contents are discarded =
and buffering is terminated.&quot;</FONT></P>

<P><FONT SIZE=3D2>(All of the paragraphs following the second bullet =
are part of that bullet item.)</FONT>
</P>

<P><FONT SIZE=3D2>Section 7.1.14.5:</FONT>
</P>

<P><FONT SIZE=3D2>Change: &quot;2. At each step, a timer is set to wait =
for the next event, based either on the default timing rules given =
above or on explicit timing specified in one or more alternative event =
sequences. If the timer expires and a member of the candidate set of =
alternatives is fully satisfied, a timeout completion with full match =
is reported.&nbsp; If the timer expires and part or none of any =
candidate alternative is satisfied, a timeout completion with partial =
match is reported.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;2. At each step, if buffered digits are =
available, the oldest one (with possible accompanying long digit (Z) =
qualifier) is removed from the buffer and processing moves to the next =
step as if the digit event had just been observed.&nbsp; Otherwise a =
timer is set to wait for the next event, based either on the default =
timing rules given above or on explicit timing specified in one or more =
alternative event sequences. If the timer expires and a member of the =
candidate set of alternatives is fully satisfied, a timeout completion =
with full match is reported.&nbsp; If the timer expires and part or =
none of any candidate alternative is satisfied, a timeout completion =
with partial match is reported.&nbsp; In either case, if the digit map =
completion event allows for detailed timeout reporting, the reported =
dial string will end with 'L' or 'S' as appropriate.&quot;</FONT></P>

<P><FONT SIZE=3D2>Change (step 5): &quot;The event removed from the =
current dial string will then be reported as per the currently active =
event processing mechanisms.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;The event removed from the current dial =
string will then be reported as a separate event, buffered, or =
discarded according to the rules described in the previous =
section.&nbsp; This statement is qualified as follows:</FONT></P>

<P><FONT SIZE=3D2>a) The digit map completion event may specify that =
the event be reported as a parameter of that event.&nbsp; This occurs =
independently of subsequent processing of the digit event.&nbsp; =
</FONT></P>

<P><FONT SIZE=3D2>b) The digit map completion event may specify that =
the extra digit should be discarded.&nbsp; In this case, it is =
discarded immediately.&nbsp; Any buffering or other processing applies =
only to subsequent events.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 6.1.14.7:</FONT>
</P>

<P><FONT SIZE=3D2>Change: &quot;=B7 the events in the package =
containing the specified digit map completion event other than the =
completion event itself are not individually notified, =
and&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;=B7 the events in the package containing =
the specified digit map completion event other than the completion =
event itself are not individually notified and have no side-effects =
unless separately enabled, and&quot;</FONT></P>

<P><FONT SIZE=3D2>Change: &quot;=B7 an event that triggers a partial =
match completion event is not recognized and therefore has no side =
effects until reprocessed following the recognition of the digit map =
completion event.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;=B7 an event that triggers a partial match =
completion event is not recognized and therefore has no side effects =
unless and until reprocessed following the recognition of the digit map =
completion event.&nbsp; Similarly buffered digit events are not =
recognized and have no side effects until processed.&quot;</FONT></P>

<P><FONT SIZE=3D2>Annex C:</FONT>
</P>

<P><FONT SIZE=3D2>Change: </FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer =
COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] digitMap </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
</P>

<P><FONT SIZE=3D2>To:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer =
COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] [&quot;Z&quot; COLON =
Timer COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; digitMap </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ; Units are seconds for T, S, and L =
timers, and hundreds of milliseconds for Z timer.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ; Thus T, S, and L range from 1 to 99 =
seconds and Z from 100 ms to 9.9 s.</FONT>
</P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Christian Groves [<A =
HREF=3D"mailto:Christian.Groves@ericsson.com.au">mailto:Christian.Groves=
@ericsson.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 28, 2002 7:26 PM</FONT>
<BR><FONT SIZE=3D2>To: megaco ietf</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] [Fwd: Fwd: Uploaded files to =
Incoming]</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>G'Day all,</FONT>
</P>

<P><FONT SIZE=3D2>I have uploaded a number of H.248 editors' =
contributions and company</FONT>
<BR><FONT SIZE=3D2>contributions to the PICTEL website.</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://standard.pictel.com/ftp/avc-site/0202_Gen/" =
TARGET=3D"_blank">http://standard.pictel.com/ftp/avc-site/0202_Gen/</A><=
/FONT>
</P>

<P><FONT SIZE=3D2>A list of the documents is below. The latest version =
of H.248 is among</FONT>
<BR><FONT SIZE=3D2>them. Comments?</FONT>
</P>

<P><FONT SIZE=3D2>Regards, Christian</FONT>
</P>

<P><FONT SIZE=3D2>-------- Original Message --------</FONT>
<BR><FONT SIZE=3D2>Subject: Fwd: Uploaded files to Incoming</FONT>
<BR><FONT SIZE=3D2>Date: Thu, 24 Jan 2002 16:27:59 +0900</FONT>
<BR><FONT SIZE=3D2>From: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>Reply-To: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>To: ITU-SG16@echo.jf.INTEL.COM</FONT>
</P>

<P><FONT SIZE=3D2>Dear SG16 experts,</FONT>
</P>

<P><FONT SIZE=3D2>They are now available at /0202_Gen of the =
avc-site.</FONT>
</P>

<P><FONT SIZE=3D2>At 16:16 +1100 02/01/24, Christian Groves =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;I have placed the following files in the =
incoming directory. Could you</FONT>
<BR><FONT SIZE=3D2>&gt;please move them to the Geneve directory?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L =
Amendment 1</FONT>
<BR><FONT SIZE=3D2>&gt;2. [DC-xxx_Annex_M_1] Comments to H.248 Annex =
M.1 Audio Server Package</FONT>
<BR><FONT SIZE=3D2>&gt;3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac =
Quality Alert Ceasing Package</FONT>
<BR><FONT SIZE=3D2>&gt;4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 =
Package Attribute</FONT>
<BR><FONT SIZE=3D2>&gt;5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide =
Additions</FONT>
<BR><FONT SIZE=3D2>&gt;6. [DC-xxx_MuxDescription] Clarification of =
H.248 Mux Descriptor Usage</FONT>
<BR><FONT SIZE=3D2>&gt;7. [DC-xxx_Nx64K] Addition of Nx64K Service to =
the H.248 Mutliplex</FONT>
<BR><FONT SIZE=3D2>&gt;descriptor</FONT>
<BR><FONT SIZE=3D2>&gt;8. [DC-xxx_Packages_Guide] Packages Guide</FONT>
<BR><FONT SIZE=3D2>&gt;9. [DC-xxx_Profile_Pkg] Draft H.248 Annex =
M.profile Profile Package</FONT>
<BR><FONT SIZE=3D2>&gt;10. [DC-xxx_H248v2] Draft H.248v2</FONT>
</P>

<P><FONT SIZE=3D2>Best regards,</FONT>
</P>

<P><FONT SIZE=3D2>OKUBO Sakae</FONT>
<BR><FONT SIZE=3D2>*****************************************************=
****</FONT>
<BR><FONT SIZE=3D2>Global Information and Telecommunication Institute =
(GITI)</FONT>
<BR><FONT SIZE=3D2>Waseda University</FONT>
<BR><FONT SIZE=3D2>29-7 Waseda University Bldg.</FONT>
<BR><FONT SIZE=3D2>1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo</FONT>
<BR><FONT SIZE=3D2>169-0051 Japan</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; e-mail: =
okubo@giti.waseda.ac.jp</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tel: +81 =
3 3204 8194</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fax: +81 =
3 5286 3832</FONT>
<BR><FONT =
SIZE=3D2>*********************************************************</FONT=
>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A902.20625AF0--

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


From daemon@ns.ietf.org  Tue Jan 29 15:28:01 2002
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 PAA19941
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 15:28:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA27531
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 15:28:04 -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 PAA27122;
	Tue, 29 Jan 2002 15:19:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27089
	for <megaco@optimus.ietf.org>; Tue, 29 Jan 2002 15:19:25 -0500 (EST)
Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19685
	for <megaco@ietf.org>; Tue, 29 Jan 2002 15:19:17 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0TKIde24196;
	Tue, 29 Jan 2002 15:18:40 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAX1Y7>; Tue, 29 Jan 2002 15:18:38 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01BA3E14@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Christian Groves <Christian.Groves@ericsson.com.au>,
        megaco ietf
	 <megaco@ietf.org>
Date: Tue, 29 Jan 2002 15:18:34 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A902.20625AF0"
Subject: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A902.20625AF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Actually, I have some.

The IG posted there is lacking the digit collection changes agreed upon =
in
Dublin.  Here are the changes as agreed upon:

Section 7.1.14.2:
Change: "The timers are configurable parameters to a DigitMap.  The =
Start
timer is started at the beginning of every digit map use, but can be
overridden."
To: "Default values of these timers should be provisioned on the MG, =
but can
be overridden by values specified within the DigitMap."

Section 7.1.14.3:
Change: "Finally, if conflicting timing specifiers are in effect in
different alternative sequences, the results are undefined."
To: "Finally, if conflicting timing specifiers are in effect in =
different
alternative sequences, the long timer shall be used."

Change: "The value of this threshold is assumed to be provisioned in =
the
MG."
To: "The value of this threshold is assumed to be provisioned in the =
MG,
but, like the T, L, and S timers, can be overridden by specification =
within
the DigitMap."

Section 7.1.14.4:
Change: "Subsequent events in the package are processed as per the =
currently
active event processing mechanisms."
To: "Subsequent digit events in the package are processed as follows:

=B7if EventBufferControl is ON, subsequent digit events are processed =
in the
same way as any other events;

=B7if EventBufferControl is OFF, if the active EventsDescriptor did not
change, and if individual digit events are not enabled within that
descriptor, then digit buffering will be initiated.  Buffering will =
continue
until the buffering time specified in the original digit map completion
event has expired or until the active EventsDescriptor is replaced.

The digit buffer shall take the logical form of a dial string which =
includes
the digit characters as represented in the digit map, possibly preceded =
by
'Z'.  The threshold value of tone duration used to identify long events
shall be the same as that used with the most recently completed digit =
map.

Buffering time defaults to zero (no buffering) unless explicitly set
otherwise within the digit map completion event.  If buffering ceases =
due to
buffering timer expiry, the contents of the digit buffer are discarded.

If buffering was stopped by a new EventsDescriptor, then if that
EventsDescriptor contains a new digit map completion event from the =
same
package as the previous one, any buffered digits are processed against =
the
digit map as described below.  Buffered digits not consumed by the new =
digit
map are handled as if they had were observed after that map completed.

If instead the new EventsDescriptor enables the reporting of individual
digit events, the entire set of buffered digits shall immediately be
processed, the applicable events reported, and the buffer cleared.

Finally, if the new EventsDescriptor enables neither a digit map =
completion
event nor the reporting of individual digit events from the package
concerned, the buffer contents are discarded and buffering is =
terminated."

(All of the paragraphs following the second bullet are part of that =
bullet
item.)

Section 7.1.14.5:

Change: "2. At each step, a timer is set to wait for the next event, =
based
either on the default timing rules given above or on explicit timing
specified in one or more alternative event sequences. If the timer =
expires
and a member of the candidate set of alternatives is fully satisfied, a
timeout completion with full match is reported.  If the timer expires =
and
part or none of any candidate alternative is satisfied, a timeout =
completion
with partial match is reported."
To: "2. At each step, if buffered digits are available, the oldest one =
(with
possible accompanying long digit (Z) qualifier) is removed from the =
buffer
and processing moves to the next step as if the digit event had just =
been
observed.  Otherwise a timer is set to wait for the next event, based =
either
on the default timing rules given above or on explicit timing specified =
in
one or more alternative event sequences. If the timer expires and a =
member
of the candidate set of alternatives is fully satisfied, a timeout
completion with full match is reported.  If the timer expires and part =
or
none of any candidate alternative is satisfied, a timeout completion =
with
partial match is reported.  In either case, if the digit map completion
event allows for detailed timeout reporting, the reported dial string =
will
end with 'L' or 'S' as appropriate."

Change (step 5): "The event removed from the current dial string will =
then
be reported as per the currently active event processing mechanisms."
To: "The event removed from the current dial string will then be =
reported as
a separate event, buffered, or discarded according to the rules =
described in
the previous section.  This statement is qualified as follows:

a) The digit map completion event may specify that the event be =
reported as
a parameter of that event.  This occurs independently of subsequent
processing of the digit event. =20

b) The digit map completion event may specify that the extra digit =
should be
discarded.  In this case, it is discarded immediately.  Any buffering =
or
other processing applies only to subsequent events."

Section 6.1.14.7:

Change: "=B7 the events in the package containing the specified digit =
map
completion event other than the completion event itself are not =
individually
notified, and"
To: "=B7 the events in the package containing the specified digit map
completion event other than the completion event itself are not =
individually
notified and have no side-effects unless separately enabled, and"

Change: "=B7 an event that triggers a partial match completion event is =
not
recognized and therefore has no side effects until reprocessed =
following the
recognition of the digit map completion event."
To: "=B7 an event that triggers a partial match completion event is not
recognized and therefore has no side effects unless and until =
reprocessed
following the recognition of the digit map completion event.  Similarly
buffered digit events are not recognized and have no side effects until
processed."

Annex C:

Change:=20

   digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer =
COMMA]
                          ["L" COLON Timer COMMA] digitMap=20
   Timer                =3D 1*2DIGIT

To:

   digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer =
COMMA]
                          ["L" COLON Timer COMMA] ["Z" COLON Timer =
COMMA]
                           digitMap=20
   Timer                =3D 1*2DIGIT
   ; Units are seconds for T, S, and L timers, and hundreds of =
milliseconds
for Z timer. =20
   ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to =
9.9 s.

Kevin


-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, January 28, 2002 7:26 PM
To: megaco ietf
Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]


G'Day all,

I have uploaded a number of H.248 editors' contributions and company
contributions to the PICTEL website.
http://standard.pictel.com/ftp/avc-site/0202_Gen/

A list of the documents is below. The latest version of H.248 is among
them. Comments?

Regards, Christian

-------- Original Message --------
Subject: Fwd: Uploaded files to Incoming
Date: Thu, 24 Jan 2002 16:27:59 +0900
From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
To: ITU-SG16@echo.jf.INTEL.COM

Dear SG16 experts,

They are now available at /0202_Gen of the avc-site.

At 16:16 +1100 02/01/24, Christian Groves wrote:
>I have placed the following files in the incoming directory. Could you
>please move them to the Geneve directory?
>
>1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
>2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server Package
>3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing =
Package
>4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
>5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
>6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor Usage
>7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
>descriptor
>8. [DC-xxx_Packages_Guide] Packages Guide
>9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
>10. [DC-xxx_H248v2] Draft H.248v2

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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

------_=_NextPart_001_01C1A902.20625AF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Fwd: Fwd: Uploaded files to Incoming]</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Actually, I have some.</FONT>
</P>

<P><FONT SIZE=3D2>The IG posted there is lacking the digit collection =
changes agreed upon in Dublin.&nbsp; Here are the changes as agreed =
upon:</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.2:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;The timers are configurable parameters =
to a DigitMap.&nbsp; The Start timer is started at the beginning of =
every digit map use, but can be overridden.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;Default values of these timers should be =
provisioned on the MG, but can be overridden by values specified within =
the DigitMap.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.3:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;Finally, if conflicting timing =
specifiers are in effect in different alternative sequences, the =
results are undefined.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;Finally, if conflicting timing specifiers =
are in effect in different alternative sequences, the long timer shall =
be used.&quot;</FONT></P>

<P><FONT SIZE=3D2>Change: &quot;The value of this threshold is assumed =
to be provisioned in the MG.&quot;</FONT>
<BR><FONT SIZE=3D2>To: &quot;The value of this threshold is assumed to =
be provisioned in the MG, but, like the T, L, and S timers, can be =
overridden by specification within the DigitMap.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 7.1.14.4:</FONT>
<BR><FONT SIZE=3D2>Change: &quot;Subsequent events in the package are =
processed as per the currently active event processing =
mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>To: &quot;Subsequent digit events in the package are =
processed as follows:</FONT>
</P>

<P><FONT SIZE=3D2>=B7if EventBufferControl is ON, subsequent digit =
events are processed in the same way as any other events;</FONT>
</P>

<P><FONT SIZE=3D2>=B7if EventBufferControl is OFF, if the active =
EventsDescriptor did not change, and if individual digit events are not =
enabled within that descriptor, then digit buffering will be =
initiated.&nbsp; Buffering will continue until the buffering time =
specified in the original digit map completion event has expired or =
until the active EventsDescriptor is replaced.</FONT></P>

<P><FONT SIZE=3D2>The digit buffer shall take the logical form of a =
dial string which includes the digit characters as represented in the =
digit map, possibly preceded by 'Z'.&nbsp; The threshold value of tone =
duration used to identify long events shall be the same as that used =
with the most recently completed digit map.</FONT></P>

<P><FONT SIZE=3D2>Buffering time defaults to zero (no buffering) unless =
explicitly set otherwise within the digit map completion event.&nbsp; =
If buffering ceases due to buffering timer expiry, the contents of the =
digit buffer are discarded.</FONT></P>

<P><FONT SIZE=3D2>If buffering was stopped by a new EventsDescriptor, =
then if that EventsDescriptor contains a new digit map completion event =
from the same package as the previous one, any buffered digits are =
processed against the digit map as described below.&nbsp; Buffered =
digits not consumed by the new digit map are handled as if they had =
were observed after that map completed.</FONT></P>

<P><FONT SIZE=3D2>If instead the new EventsDescriptor enables the =
reporting of individual digit events, the entire set of buffered digits =
shall immediately be processed, the applicable events reported, and the =
buffer cleared.</FONT></P>

<P><FONT SIZE=3D2>Finally, if the new EventsDescriptor enables neither =
a digit map completion event nor the reporting of individual digit =
events from the package concerned, the buffer contents are discarded =
and buffering is terminated.&quot;</FONT></P>

<P><FONT SIZE=3D2>(All of the paragraphs following the second bullet =
are part of that bullet item.)</FONT>
</P>

<P><FONT SIZE=3D2>Section 7.1.14.5:</FONT>
</P>

<P><FONT SIZE=3D2>Change: &quot;2. At each step, a timer is set to wait =
for the next event, based either on the default timing rules given =
above or on explicit timing specified in one or more alternative event =
sequences. If the timer expires and a member of the candidate set of =
alternatives is fully satisfied, a timeout completion with full match =
is reported.&nbsp; If the timer expires and part or none of any =
candidate alternative is satisfied, a timeout completion with partial =
match is reported.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;2. At each step, if buffered digits are =
available, the oldest one (with possible accompanying long digit (Z) =
qualifier) is removed from the buffer and processing moves to the next =
step as if the digit event had just been observed.&nbsp; Otherwise a =
timer is set to wait for the next event, based either on the default =
timing rules given above or on explicit timing specified in one or more =
alternative event sequences. If the timer expires and a member of the =
candidate set of alternatives is fully satisfied, a timeout completion =
with full match is reported.&nbsp; If the timer expires and part or =
none of any candidate alternative is satisfied, a timeout completion =
with partial match is reported.&nbsp; In either case, if the digit map =
completion event allows for detailed timeout reporting, the reported =
dial string will end with 'L' or 'S' as appropriate.&quot;</FONT></P>

<P><FONT SIZE=3D2>Change (step 5): &quot;The event removed from the =
current dial string will then be reported as per the currently active =
event processing mechanisms.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;The event removed from the current dial =
string will then be reported as a separate event, buffered, or =
discarded according to the rules described in the previous =
section.&nbsp; This statement is qualified as follows:</FONT></P>

<P><FONT SIZE=3D2>a) The digit map completion event may specify that =
the event be reported as a parameter of that event.&nbsp; This occurs =
independently of subsequent processing of the digit event.&nbsp; =
</FONT></P>

<P><FONT SIZE=3D2>b) The digit map completion event may specify that =
the extra digit should be discarded.&nbsp; In this case, it is =
discarded immediately.&nbsp; Any buffering or other processing applies =
only to subsequent events.&quot;</FONT></P>

<P><FONT SIZE=3D2>Section 6.1.14.7:</FONT>
</P>

<P><FONT SIZE=3D2>Change: &quot;=B7 the events in the package =
containing the specified digit map completion event other than the =
completion event itself are not individually notified, =
and&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;=B7 the events in the package containing =
the specified digit map completion event other than the completion =
event itself are not individually notified and have no side-effects =
unless separately enabled, and&quot;</FONT></P>

<P><FONT SIZE=3D2>Change: &quot;=B7 an event that triggers a partial =
match completion event is not recognized and therefore has no side =
effects until reprocessed following the recognition of the digit map =
completion event.&quot;</FONT></P>

<P><FONT SIZE=3D2>To: &quot;=B7 an event that triggers a partial match =
completion event is not recognized and therefore has no side effects =
unless and until reprocessed following the recognition of the digit map =
completion event.&nbsp; Similarly buffered digit events are not =
recognized and have no side effects until processed.&quot;</FONT></P>

<P><FONT SIZE=3D2>Annex C:</FONT>
</P>

<P><FONT SIZE=3D2>Change: </FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer =
COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] digitMap </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
</P>

<P><FONT SIZE=3D2>To:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer =
COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] [&quot;Z&quot; COLON =
Timer COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; digitMap </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ; Units are seconds for T, S, and L =
timers, and hundreds of milliseconds for Z timer.&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ; Thus T, S, and L range from 1 to 99 =
seconds and Z from 100 ms to 9.9 s.</FONT>
</P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Christian Groves [<A =
HREF=3D"mailto:Christian.Groves@ericsson.com.au">mailto:Christian.Groves=
@ericsson.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 28, 2002 7:26 PM</FONT>
<BR><FONT SIZE=3D2>To: megaco ietf</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] [Fwd: Fwd: Uploaded files to =
Incoming]</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>G'Day all,</FONT>
</P>

<P><FONT SIZE=3D2>I have uploaded a number of H.248 editors' =
contributions and company</FONT>
<BR><FONT SIZE=3D2>contributions to the PICTEL website.</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://standard.pictel.com/ftp/avc-site/0202_Gen/" =
TARGET=3D"_blank">http://standard.pictel.com/ftp/avc-site/0202_Gen/</A><=
/FONT>
</P>

<P><FONT SIZE=3D2>A list of the documents is below. The latest version =
of H.248 is among</FONT>
<BR><FONT SIZE=3D2>them. Comments?</FONT>
</P>

<P><FONT SIZE=3D2>Regards, Christian</FONT>
</P>

<P><FONT SIZE=3D2>-------- Original Message --------</FONT>
<BR><FONT SIZE=3D2>Subject: Fwd: Uploaded files to Incoming</FONT>
<BR><FONT SIZE=3D2>Date: Thu, 24 Jan 2002 16:27:59 +0900</FONT>
<BR><FONT SIZE=3D2>From: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>Reply-To: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>To: ITU-SG16@echo.jf.INTEL.COM</FONT>
</P>

<P><FONT SIZE=3D2>Dear SG16 experts,</FONT>
</P>

<P><FONT SIZE=3D2>They are now available at /0202_Gen of the =
avc-site.</FONT>
</P>

<P><FONT SIZE=3D2>At 16:16 +1100 02/01/24, Christian Groves =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;I have placed the following files in the =
incoming directory. Could you</FONT>
<BR><FONT SIZE=3D2>&gt;please move them to the Geneve directory?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L =
Amendment 1</FONT>
<BR><FONT SIZE=3D2>&gt;2. [DC-xxx_Annex_M_1] Comments to H.248 Annex =
M.1 Audio Server Package</FONT>
<BR><FONT SIZE=3D2>&gt;3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac =
Quality Alert Ceasing Package</FONT>
<BR><FONT SIZE=3D2>&gt;4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 =
Package Attribute</FONT>
<BR><FONT SIZE=3D2>&gt;5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide =
Additions</FONT>
<BR><FONT SIZE=3D2>&gt;6. [DC-xxx_MuxDescription] Clarification of =
H.248 Mux Descriptor Usage</FONT>
<BR><FONT SIZE=3D2>&gt;7. [DC-xxx_Nx64K] Addition of Nx64K Service to =
the H.248 Mutliplex</FONT>
<BR><FONT SIZE=3D2>&gt;descriptor</FONT>
<BR><FONT SIZE=3D2>&gt;8. [DC-xxx_Packages_Guide] Packages Guide</FONT>
<BR><FONT SIZE=3D2>&gt;9. [DC-xxx_Profile_Pkg] Draft H.248 Annex =
M.profile Profile Package</FONT>
<BR><FONT SIZE=3D2>&gt;10. [DC-xxx_H248v2] Draft H.248v2</FONT>
</P>

<P><FONT SIZE=3D2>Best regards,</FONT>
</P>

<P><FONT SIZE=3D2>OKUBO Sakae</FONT>
<BR><FONT SIZE=3D2>*****************************************************=
****</FONT>
<BR><FONT SIZE=3D2>Global Information and Telecommunication Institute =
(GITI)</FONT>
<BR><FONT SIZE=3D2>Waseda University</FONT>
<BR><FONT SIZE=3D2>29-7 Waseda University Bldg.</FONT>
<BR><FONT SIZE=3D2>1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo</FONT>
<BR><FONT SIZE=3D2>169-0051 Japan</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; e-mail: =
okubo@giti.waseda.ac.jp</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tel: +81 =
3 3204 8194</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fax: +81 =
3 5286 3832</FONT>
<BR><FONT =
SIZE=3D2>*********************************************************</FONT=
>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A902.20625AF0--

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



From megaco-admin@ietf.org  Tue Jan 29 16:45:12 2002
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 QAA21804
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 16:45:11 -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 QAA01001;
	Tue, 29 Jan 2002 16:30:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA00881
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 16:30:08 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21475
	for <megaco@ietf.org>; Tue, 29 Jan 2002 16:30:04 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0TLU5300195;
	Tue, 29 Jan 2002 16:30:05 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id QAA16760;
	Tue, 29 Jan 2002 16:30:04 -0500 (EST)
Message-ID: <3C5713A0.DD68B0EE@lucent.com>
Date: Tue, 29 Jan 2002 16:26:56 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
CC: megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
References: <ABA227A15B80D511BD1A00508BF93A1C01BA3E14@zrtpd0jq.us.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------DE5A1B220F173E69BE7068A1"
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

This is a multi-part message in MIME format.
--------------DE5A1B220F173E69BE7068A1
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

No changes for IG or V2 were approved at the Dublin meeting.  Here is
the item from the Q.3 meeting report:


> 1.3.2.6 AVD-2141a: H.248 Digit Collection Corrections and Enhancements [Nortel]
>
> There was concern that some of the proposed changes (such as the matching rules) would not
> be compatible with V1 implementations. The proposal as a whole is complex, so removal of
> individual features in the proposal that are not backwards compatible may break entire
> proposal.
>
> In TD-40, the proposal was restructured to identify parts that would not be backward
> compatible. There was a lack of time to adequately review this contribution, but we recognize
> that many of the items in the proposal need attention. We will proceed as follows:
> · Separately identify items for the implementers guide and post these to the megaco and SG16
> lists
> · Separately identify items intended for V2 and post these to the megaco and SG16 lists
> · The proposed extended DTMF detection package is accepted as a new annex on the condition
> that the related material for V2 is accepted
>
> Understanding that sufficient time is needed to review the entire proposal, the material is
> accepted in principle, subject to further review and open to contributions or
> counter-proposals.
>

I have not seen a list of proposed items (extracted from TD-40) intended
for the IG or for V2 posted to the mailing list for discussion and so
have not included any of these items in my IG draft.

Kevin Boyle wrote:

>
>
> Actually, I have some.
>
> The IG posted there is lacking the digit collection changes agreed
> upon in Dublin.  Here are the changes as agreed upon:
>
> Section 7.1.14.2:
> Change: "The timers are configurable parameters to a DigitMap.  The
> Start timer is started at the beginning of every digit map use, but
> can be overridden."
>
> To: "Default values of these timers should be provisioned on the MG,
> but can be overridden by values specified within the DigitMap."
>
> Section 7.1.14.3:
> Change: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the results are undefined."
>
> To: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the long timer shall be used."
>
> Change: "The value of this threshold is assumed to be provisioned in
> the MG."
> To: "The value of this threshold is assumed to be provisioned in the
> MG, but, like the T, L, and S timers, can be overridden by
> specification within the DigitMap."
>
> Section 7.1.14.4:
> Change: "Subsequent events in the package are processed as per the
> currently active event processing mechanisms."
> To: "Subsequent digit events in the package are processed as follows:
>
> ·if EventBufferControl is ON, subsequent digit events are processed in
> the same way as any other events;
>
> ·if EventBufferControl is OFF, if the active EventsDescriptor did not
> change, and if individual digit events are not enabled within that
> descriptor, then digit buffering will be initiated.  Buffering will
> continue until the buffering time specified in the original digit map
> completion event has expired or until the active EventsDescriptor is
> replaced.
>
> The digit buffer shall take the logical form of a dial string which
> includes the digit characters as represented in the digit map,
> possibly preceded by 'Z'.  The threshold value of tone duration used
> to identify long events shall be the same as that used with the most
> recently completed digit map.
>
> Buffering time defaults to zero (no buffering) unless explicitly set
> otherwise within the digit map completion event.  If buffering ceases
> due to buffering timer expiry, the contents of the digit buffer are
> discarded.
>
> If buffering was stopped by a new EventsDescriptor, then if that
> EventsDescriptor contains a new digit map completion event from the
> same package as the previous one, any buffered digits are processed
> against the digit map as described below.  Buffered digits not
> consumed by the new digit map are handled as if they had were observed
> after that map completed.
>
> If instead the new EventsDescriptor enables the reporting of
> individual digit events, the entire set of buffered digits shall
> immediately be processed, the applicable events reported, and the
> buffer cleared.
>
> Finally, if the new EventsDescriptor enables neither a digit map
> completion event nor the reporting of individual digit events from the
> package concerned, the buffer contents are discarded and buffering is
> terminated."
>
> (All of the paragraphs following the second bullet are part of that
> bullet item.)
>
> Section 7.1.14.5:
>
> Change: "2. At each step, a timer is set to wait for the next event,
> based either on the default timing rules given above or on explicit
> timing specified in one or more alternative event sequences. If the
> timer expires and a member of the candidate set of alternatives is
> fully satisfied, a timeout completion with full match is reported.  If
> the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported."
>
> To: "2. At each step, if buffered digits are available, the oldest one
> (with possible accompanying long digit (Z) qualifier) is removed from
> the buffer and processing moves to the next step as if the digit event
> had just been observed.  Otherwise a timer is set to wait for the next
> event, based either on the default timing rules given above or on
> explicit timing specified in one or more alternative event sequences.
> If the timer expires and a member of the candidate set of alternatives
> is fully satisfied, a timeout completion with full match is reported.
> If the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported.  In
> either case, if the digit map completion event allows for detailed
> timeout reporting, the reported dial string will end with 'L' or 'S'
> as appropriate."
>
> Change (step 5): "The event removed from the current dial string will
> then be reported as per the currently active event processing
> mechanisms."
>
> To: "The event removed from the current dial string will then be
> reported as a separate event, buffered, or discarded according to the
> rules described in the previous section.  This statement is qualified
> as follows:
>
> a) The digit map completion event may specify that the event be
> reported as a parameter of that event.  This occurs independently of
> subsequent processing of the digit event.
>
> b) The digit map completion event may specify that the extra digit
> should be discarded.  In this case, it is discarded immediately.  Any
> buffering or other processing applies only to subsequent events."
>
> Section 6.1.14.7:
>
> Change: "· the events in the package containing the specified digit
> map completion event other than the completion event itself are not
> individually notified, and"
>
> To: "· the events in the package containing the specified digit map
> completion event other than the completion event itself are not
> individually notified and have no side-effects unless separately
> enabled, and"
>
> Change: "· an event that triggers a partial match completion event is
> not recognized and therefore has no side effects until reprocessed
> following the recognition of the digit map completion event."
>
> To: "· an event that triggers a partial match completion event is not
> recognized and therefore has no side effects unless and until
> reprocessed following the recognition of the digit map completion
> event.  Similarly buffered digit events are not recognized and have no
> side effects until processed."
>
> Annex C:
>
> Change:
>
>    digitMapValue        = ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] digitMap
>    Timer                = 1*2DIGIT
>
> To:
>
>    digitMapValue        = ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] ["Z" COLON Timer
> COMMA]
>                            digitMap
>    Timer                = 1*2DIGIT
>    ; Units are seconds for T, S, and L timers, and hundreds of
> milliseconds for Z timer.
>    ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to
> 9.9 s.
>
> Kevin
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 28, 2002 7:26 PM
> To: megaco ietf
> Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
>
> G'Day all,
>
> I have uploaded a number of H.248 editors' contributions and company
> contributions to the PICTEL website.
> http://standard.pictel.com/ftp/avc-site/0202_Gen/
>
> A list of the documents is below. The latest version of H.248 is among
>
> them. Comments?
>
> Regards, Christian
>
> -------- Original Message --------
> Subject: Fwd: Uploaded files to Incoming
> Date: Thu, 24 Jan 2002 16:27:59 +0900
> From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> To: ITU-SG16@echo.jf.INTEL.COM
>
> Dear SG16 experts,
>
> They are now available at /0202_Gen of the avc-site.
>
> At 16:16 +1100 02/01/24, Christian Groves wrote:
> >I have placed the following files in the incoming directory. Could
> you
> >please move them to the Geneve directory?
> >
> >1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
> >2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server
> Package
> >3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing
> Package
> >4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
> >5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
> >6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor
> Usage
> >7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
> >descriptor
> >8. [DC-xxx_Packages_Guide] Packages Guide
> >9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
> >10. [DC-xxx_H248v2] Draft H.248v2
>
> Best regards,
>
> OKUBO Sakae
> *********************************************************
> Global Information and Telecommunication Institute (GITI)
> Waseda University
> 29-7 Waseda University Bldg.
> 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
> 169-0051 Japan
>         e-mail: okubo@giti.waseda.ac.jp
>         Tel: +81 3 3204 8194
>         Fax: +81 3 5286 3832
> *********************************************************
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------DE5A1B220F173E69BE7068A1
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------DE5A1B220F173E69BE7068A1--


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


From daemon@ns.ietf.org  Tue Jan 29 16:45:12 2002
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 QAA21811
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 16:45:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA01955
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 16:45:16 -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 QAA01001;
	Tue, 29 Jan 2002 16:30:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA00881
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 16:30:08 -0500 (EST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21475
	for <megaco@ietf.org>; Tue, 29 Jan 2002 16:30:04 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0TLU5300195;
	Tue, 29 Jan 2002 16:30:05 -0500 (EST)
Received: from lucent.com (pctla2 [135.3.130.26])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id QAA16760;
	Tue, 29 Jan 2002 16:30:04 -0500 (EST)
Message-ID: <3C5713A0.DD68B0EE@lucent.com>
Date: Tue, 29 Jan 2002 16:26:56 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
CC: megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
References: <ABA227A15B80D511BD1A00508BF93A1C01BA3E14@zrtpd0jq.us.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------DE5A1B220F173E69BE7068A1"
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

This is a multi-part message in MIME format.
--------------DE5A1B220F173E69BE7068A1
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

No changes for IG or V2 were approved at the Dublin meeting.  Here is
the item from the Q.3 meeting report:


> 1.3.2.6 AVD-2141a: H.248 Digit Collection Corrections and Enhancements [Nortel]
>
> There was concern that some of the proposed changes (such as the matching rules) would not
> be compatible with V1 implementations. The proposal as a whole is complex, so removal of
> individual features in the proposal that are not backwards compatible may break entire
> proposal.
>
> In TD-40, the proposal was restructured to identify parts that would not be backward
> compatible. There was a lack of time to adequately review this contribution, but we recognize
> that many of the items in the proposal need attention. We will proceed as follows:
> · Separately identify items for the implementers guide and post these to the megaco and SG16
> lists
> · Separately identify items intended for V2 and post these to the megaco and SG16 lists
> · The proposed extended DTMF detection package is accepted as a new annex on the condition
> that the related material for V2 is accepted
>
> Understanding that sufficient time is needed to review the entire proposal, the material is
> accepted in principle, subject to further review and open to contributions or
> counter-proposals.
>

I have not seen a list of proposed items (extracted from TD-40) intended
for the IG or for V2 posted to the mailing list for discussion and so
have not included any of these items in my IG draft.

Kevin Boyle wrote:

>
>
> Actually, I have some.
>
> The IG posted there is lacking the digit collection changes agreed
> upon in Dublin.  Here are the changes as agreed upon:
>
> Section 7.1.14.2:
> Change: "The timers are configurable parameters to a DigitMap.  The
> Start timer is started at the beginning of every digit map use, but
> can be overridden."
>
> To: "Default values of these timers should be provisioned on the MG,
> but can be overridden by values specified within the DigitMap."
>
> Section 7.1.14.3:
> Change: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the results are undefined."
>
> To: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the long timer shall be used."
>
> Change: "The value of this threshold is assumed to be provisioned in
> the MG."
> To: "The value of this threshold is assumed to be provisioned in the
> MG, but, like the T, L, and S timers, can be overridden by
> specification within the DigitMap."
>
> Section 7.1.14.4:
> Change: "Subsequent events in the package are processed as per the
> currently active event processing mechanisms."
> To: "Subsequent digit events in the package are processed as follows:
>
> ·if EventBufferControl is ON, subsequent digit events are processed in
> the same way as any other events;
>
> ·if EventBufferControl is OFF, if the active EventsDescriptor did not
> change, and if individual digit events are not enabled within that
> descriptor, then digit buffering will be initiated.  Buffering will
> continue until the buffering time specified in the original digit map
> completion event has expired or until the active EventsDescriptor is
> replaced.
>
> The digit buffer shall take the logical form of a dial string which
> includes the digit characters as represented in the digit map,
> possibly preceded by 'Z'.  The threshold value of tone duration used
> to identify long events shall be the same as that used with the most
> recently completed digit map.
>
> Buffering time defaults to zero (no buffering) unless explicitly set
> otherwise within the digit map completion event.  If buffering ceases
> due to buffering timer expiry, the contents of the digit buffer are
> discarded.
>
> If buffering was stopped by a new EventsDescriptor, then if that
> EventsDescriptor contains a new digit map completion event from the
> same package as the previous one, any buffered digits are processed
> against the digit map as described below.  Buffered digits not
> consumed by the new digit map are handled as if they had were observed
> after that map completed.
>
> If instead the new EventsDescriptor enables the reporting of
> individual digit events, the entire set of buffered digits shall
> immediately be processed, the applicable events reported, and the
> buffer cleared.
>
> Finally, if the new EventsDescriptor enables neither a digit map
> completion event nor the reporting of individual digit events from the
> package concerned, the buffer contents are discarded and buffering is
> terminated."
>
> (All of the paragraphs following the second bullet are part of that
> bullet item.)
>
> Section 7.1.14.5:
>
> Change: "2. At each step, a timer is set to wait for the next event,
> based either on the default timing rules given above or on explicit
> timing specified in one or more alternative event sequences. If the
> timer expires and a member of the candidate set of alternatives is
> fully satisfied, a timeout completion with full match is reported.  If
> the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported."
>
> To: "2. At each step, if buffered digits are available, the oldest one
> (with possible accompanying long digit (Z) qualifier) is removed from
> the buffer and processing moves to the next step as if the digit event
> had just been observed.  Otherwise a timer is set to wait for the next
> event, based either on the default timing rules given above or on
> explicit timing specified in one or more alternative event sequences.
> If the timer expires and a member of the candidate set of alternatives
> is fully satisfied, a timeout completion with full match is reported.
> If the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported.  In
> either case, if the digit map completion event allows for detailed
> timeout reporting, the reported dial string will end with 'L' or 'S'
> as appropriate."
>
> Change (step 5): "The event removed from the current dial string will
> then be reported as per the currently active event processing
> mechanisms."
>
> To: "The event removed from the current dial string will then be
> reported as a separate event, buffered, or discarded according to the
> rules described in the previous section.  This statement is qualified
> as follows:
>
> a) The digit map completion event may specify that the event be
> reported as a parameter of that event.  This occurs independently of
> subsequent processing of the digit event.
>
> b) The digit map completion event may specify that the extra digit
> should be discarded.  In this case, it is discarded immediately.  Any
> buffering or other processing applies only to subsequent events."
>
> Section 6.1.14.7:
>
> Change: "· the events in the package containing the specified digit
> map completion event other than the completion event itself are not
> individually notified, and"
>
> To: "· the events in the package containing the specified digit map
> completion event other than the completion event itself are not
> individually notified and have no side-effects unless separately
> enabled, and"
>
> Change: "· an event that triggers a partial match completion event is
> not recognized and therefore has no side effects until reprocessed
> following the recognition of the digit map completion event."
>
> To: "· an event that triggers a partial match completion event is not
> recognized and therefore has no side effects unless and until
> reprocessed following the recognition of the digit map completion
> event.  Similarly buffered digit events are not recognized and have no
> side effects until processed."
>
> Annex C:
>
> Change:
>
>    digitMapValue        = ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] digitMap
>    Timer                = 1*2DIGIT
>
> To:
>
>    digitMapValue        = ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] ["Z" COLON Timer
> COMMA]
>                            digitMap
>    Timer                = 1*2DIGIT
>    ; Units are seconds for T, S, and L timers, and hundreds of
> milliseconds for Z timer.
>    ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to
> 9.9 s.
>
> Kevin
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 28, 2002 7:26 PM
> To: megaco ietf
> Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
>
> G'Day all,
>
> I have uploaded a number of H.248 editors' contributions and company
> contributions to the PICTEL website.
> http://standard.pictel.com/ftp/avc-site/0202_Gen/
>
> A list of the documents is below. The latest version of H.248 is among
>
> them. Comments?
>
> Regards, Christian
>
> -------- Original Message --------
> Subject: Fwd: Uploaded files to Incoming
> Date: Thu, 24 Jan 2002 16:27:59 +0900
> From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> To: ITU-SG16@echo.jf.INTEL.COM
>
> Dear SG16 experts,
>
> They are now available at /0202_Gen of the avc-site.
>
> At 16:16 +1100 02/01/24, Christian Groves wrote:
> >I have placed the following files in the incoming directory. Could
> you
> >please move them to the Geneve directory?
> >
> >1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
> >2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server
> Package
> >3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing
> Package
> >4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
> >5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
> >6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor
> Usage
> >7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
> >descriptor
> >8. [DC-xxx_Packages_Guide] Packages Guide
> >9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
> >10. [DC-xxx_H248v2] Draft H.248v2
>
> Best regards,
>
> OKUBO Sakae
> *********************************************************
> Global Information and Telecommunication Institute (GITI)
> Waseda University
> 29-7 Waseda University Bldg.
> 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
> 169-0051 Japan
>         e-mail: okubo@giti.waseda.ac.jp
>         Tel: +81 3 3204 8194
>         Fax: +81 3 5286 3832
> *********************************************************
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------DE5A1B220F173E69BE7068A1
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------DE5A1B220F173E69BE7068A1--


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



From megaco-admin@ietf.org  Tue Jan 29 22:28:13 2002
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 WAA28852
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 22:28:12 -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 WAA16950;
	Tue, 29 Jan 2002 22:18:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA16921
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 22:18:04 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28671
	for <megaco@ietf.org>; Tue, 29 Jan 2002 22:17:59 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA07922;
	Wed, 30 Jan 2002 14:16:37 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA07356;
	Wed, 30 Jan 2002 14:17:57 +1100 (EST)
Message-ID: <3C5766CA.80861467@ericsson.com.au>
Date: Wed, 30 Jan 2002 14:21:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF1E@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
event (stream ID x) - detect the event only on the particular streamID x

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
signal (stream ID x) - the signal only on the particular streamID x

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.

Now this is all rather acedemic if the termination only ever has one
stream.
I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
> 
> Your proposal that the default streamId (0) means "all active streams" is a
> workable one for events, especially if the actual stream on which the signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
> 
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> My comments embedded.....
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> You've opened up a good discussion.
> 
> 1. You are right about streams also being bound to terminations.  Aside from
> being able to define streams when the termination is in the NULL context, we
> have the provision that a termination retains its current streams when it is
> moved from one context to another.
> 
> 2. I differ slightly on the interpretation of streams versus actual enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional exchange
> of media between the context and each termination in it.  Of course, to have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
> 
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so, because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
> 
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
> 
> 3. I think I've made the point that H.248v1 requires that most of the events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not a
> change in the protocol, just a clarification.
> 
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> 
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
> 
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> I would like to add more to your comments about streams being context
> properties.
> 
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in one
>      termination.
> 
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
> 
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
> 
> Please comment....
> 
> Thanks & Regards,
> -Kapil Nayar
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.  See new comments [PTT2] below.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> my comments embedded.
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> 
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
> 
> "The default streamID is 0, indicating that the event to be detected is not
> related to a particular media stream."
> 
> Does the "streamID 0" refer to the complete termination (which means all the
> active streams on the termination) ?
> 
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want to
> foreclose the possibility of using this on ephemerals.
> 
> And, if some event is required to be detected on the ephemeral termination,
> the event descriptor should clearly identify which stream it is required on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by definition
> of the event or signal) whether streamId=0 will apply.  We should therefore
> make it requirement to specify this in package definitions.
> 
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default for
> signals and events, or have streamId=1 as the default?
> 
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> If a given streamId is supported somewhere in the context, then referring to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream Descriptors
> for new streams MUST appear before Signals and Events descriptors referring
> to those StreamIds.
> 
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
> 
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
> 
> You can specify streamId=0 in a signals or events descriptor, but that's the
> same as leaving it unspecified.
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."
> 
> _______________________________________________
> 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


From daemon@ns.ietf.org  Tue Jan 29 22:28:18 2002
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 WAA28860
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 22:28:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA17234
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 22:28:16 -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 WAA16950;
	Tue, 29 Jan 2002 22:18:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA16921
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 22:18:04 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28671
	for <megaco@ietf.org>; Tue, 29 Jan 2002 22:17:59 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id OAA07922;
	Wed, 30 Jan 2002 14:16:37 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA07356;
	Wed, 30 Jan 2002 14:17:57 +1100 (EST)
Message-ID: <3C5766CA.80861467@ericsson.com.au>
Date: Wed, 30 Jan 2002 14:21:46 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF1E@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
event (stream ID x) - detect the event only on the particular streamID x

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
signal (stream ID x) - the signal only on the particular streamID x

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.

Now this is all rather acedemic if the termination only ever has one
stream.
I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
> 
> Your proposal that the default streamId (0) means "all active streams" is a
> workable one for events, especially if the actual stream on which the signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
> 
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> My comments embedded.....
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> You've opened up a good discussion.
> 
> 1. You are right about streams also being bound to terminations.  Aside from
> being able to define streams when the termination is in the NULL context, we
> have the provision that a termination retains its current streams when it is
> moved from one context to another.
> 
> 2. I differ slightly on the interpretation of streams versus actual enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional exchange
> of media between the context and each termination in it.  Of course, to have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
> 
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so, because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
> 
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
> 
> 3. I think I've made the point that H.248v1 requires that most of the events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not a
> change in the protocol, just a clarification.
> 
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> 
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
> 
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> I would like to add more to your comments about streams being context
> properties.
> 
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in one
>      termination.
> 
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
> 
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
> 
> Please comment....
> 
> Thanks & Regards,
> -Kapil Nayar
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.  See new comments [PTT2] below.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> my comments embedded.
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> 
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
> 
> "The default streamID is 0, indicating that the event to be detected is not
> related to a particular media stream."
> 
> Does the "streamID 0" refer to the complete termination (which means all the
> active streams on the termination) ?
> 
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want to
> foreclose the possibility of using this on ephemerals.
> 
> And, if some event is required to be detected on the ephemeral termination,
> the event descriptor should clearly identify which stream it is required on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by definition
> of the event or signal) whether streamId=0 will apply.  We should therefore
> make it requirement to specify this in package definitions.
> 
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default for
> signals and events, or have streamId=1 as the default?
> 
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> If a given streamId is supported somewhere in the context, then referring to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream Descriptors
> for new streams MUST appear before Signals and Events descriptors referring
> to those StreamIds.
> 
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
> 
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
> 
> You can specify streamId=0 in a signals or events descriptor, but that's the
> same as leaving it unspecified.
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 29 23:24:04 2002
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 XAA00707
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:24:04 -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 XAA19300;
	Tue, 29 Jan 2002 23:09:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19269
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:09:36 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00528
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:31 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0U493f26636
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:03 -0500 (EST)
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 g0U491r15579
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA4W1W>; Tue, 29 Jan 2002 23:09:03 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Tue, 29 Jan 2002 23:09:02 -0500
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

Darn: hit the wrong button again.

Anyway, if everyone sees it this way let's go for it.  Do we need text
changes?



-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Tuesday, January 29, 2002 10:22 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
Subject: Re: [Megaco] Query about streamID 0


G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
event (stream ID x) - detect the event only on the particular streamID x

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
signal (stream ID x) - the signal only on the particular streamID x

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.

Now this is all rather acedemic if the termination only ever has one
stream.
I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
> 
> Your proposal that the default streamId (0) means "all active streams" is
a
> workable one for events, especially if the actual stream on which the
signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
> 
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that
concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> My comments embedded.....
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> You've opened up a good discussion.
> 
> 1. You are right about streams also being bound to terminations.  Aside
from
> being able to define streams when the termination is in the NULL context,
we
> have the provision that a termination retains its current streams when it
is
> moved from one context to another.
> 
> 2. I differ slightly on the interpretation of streams versus actual
enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional
exchange
> of media between the context and each termination in it.  Of course, to
have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
> 
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll
point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so,
because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
> 
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
> 
> 3. I think I've made the point that H.248v1 requires that most of the
events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not
a
> change in the protocol, just a clarification.
> 
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> 
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need
to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any
specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
> 
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> I would like to add more to your comments about streams being context
> properties.
> 
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in
one
>      termination.
> 
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
> 
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
> 
> Please comment....
> 
> Thanks & Regards,
> -Kapil Nayar
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.  See new comments [PTT2] below.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> my comments embedded.
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> 
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
mentions:
> 
> "The default streamID is 0, indicating that the event to be detected is
not
> related to a particular media stream."
> 
> Does the "streamID 0" refer to the complete termination (which means all
the
> active streams on the termination) ?
> 
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want
to
> foreclose the possibility of using this on ephemerals.
> 
> And, if some event is required to be detected on the ephemeral
termination,
> the event descriptor should clearly identify which stream it is required
on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by
definition
> of the event or signal) whether streamId=0 will apply.  We should
therefore
> make it requirement to specify this in package definitions.
> 
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to
specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default
for
> signals and events, or have streamId=1 as the default?
> 
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context
property.
> If a given streamId is supported somewhere in the context, then referring
to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that
stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream
Descriptors
> for new streams MUST appear before Signals and Events descriptors
referring
> to those StreamIds.
> 
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
> 
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
> 
> You can specify streamId=0 in a signals or events descriptor, but that's
the
> same as leaving it unspecified.
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes
Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email
including
> damage from virus."
> 
> _______________________________________________
> 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


From daemon@ns.ietf.org  Tue Jan 29 23:24:04 2002
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 XAA00717
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:24:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA19891
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 23:24:08 -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 XAA19300;
	Tue, 29 Jan 2002 23:09:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19269
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:09:36 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00528
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:31 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0U493f26636
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:03 -0500 (EST)
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 g0U491r15579
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:09:01 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA4W1W>; Tue, 29 Jan 2002 23:09:03 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Query about streamID 0
Date: Tue, 29 Jan 2002 23:09:02 -0500
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

Darn: hit the wrong button again.

Anyway, if everyone sees it this way let's go for it.  Do we need text
changes?



-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Tuesday, January 29, 2002 10:22 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
Subject: Re: [Megaco] Query about streamID 0


G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
event (stream ID x) - detect the event only on the particular streamID x

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
signal (stream ID x) - the signal only on the particular streamID x

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.

Now this is all rather acedemic if the termination only ever has one
stream.
I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
> 
> Your proposal that the default streamId (0) means "all active streams" is
a
> workable one for events, especially if the actual stream on which the
signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
> 
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that
concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> My comments embedded.....
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> You've opened up a good discussion.
> 
> 1. You are right about streams also being bound to terminations.  Aside
from
> being able to define streams when the termination is in the NULL context,
we
> have the provision that a termination retains its current streams when it
is
> moved from one context to another.
> 
> 2. I differ slightly on the interpretation of streams versus actual
enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional
exchange
> of media between the context and each termination in it.  Of course, to
have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
> 
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll
point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so,
because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
> 
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
> 
> 3. I think I've made the point that H.248v1 requires that most of the
events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not
a
> change in the protocol, just a clarification.
> 
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> 
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need
to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any
specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
> 
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> I would like to add more to your comments about streams being context
> properties.
> 
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in
one
>      termination.
> 
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
> 
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
> 
> Please comment....
> 
> Thanks & Regards,
> -Kapil Nayar
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> 
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.  See new comments [PTT2] below.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
> 
> Hi Tom
> 
> my comments embedded.
> 
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> 
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
> 
> Subject:  RE: [Megaco] Query about streamID 0
> 
> Hi.
> 
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
> 
> Hi Tom & list,
> 
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
mentions:
> 
> "The default streamID is 0, indicating that the event to be detected is
not
> related to a particular media stream."
> 
> Does the "streamID 0" refer to the complete termination (which means all
the
> active streams on the termination) ?
> 
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want
to
> foreclose the possibility of using this on ephemerals.
> 
> And, if some event is required to be detected on the ephemeral
termination,
> the event descriptor should clearly identify which stream it is required
on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by
definition
> of the event or signal) whether streamId=0 will apply.  We should
therefore
> make it requirement to specify this in package definitions.
> 
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to
specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default
for
> signals and events, or have streamId=1 as the default?
> 
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context
property.
> If a given streamId is supported somewhere in the context, then referring
to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that
stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream
Descriptors
> for new streams MUST appear before Signals and Events descriptors
referring
> to those StreamIds.
> 
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
> 
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
> 
> You can specify streamId=0 in a signals or events descriptor, but that's
the
> same as leaving it unspecified.
> 
> Please reply back...
> 
> Thanks,
> Kapil Nayar
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes
Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email
including
> damage from virus."
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Tue Jan 29 23:28:01 2002
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 XAA00800
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:28:01 -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 XAA19513;
	Tue, 29 Jan 2002 23:11:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19422
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:11:27 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00592
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:11:21 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA16124;
	Wed, 30 Jan 2002 15:10:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA03196;
	Wed, 30 Jan 2002 15:11:23 +1100 (EST)
Message-ID: <3C5761CC.2527ADF4@ericsson.com.au>
Date: Wed, 30 Jan 2002 14:00:28 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

I don't think we can accept the exception for property parameters this
would be a big problem for interoperabilty between v1 and v2. Having to
repeat the entire descriptor when we want to change one item I agree is
not nice but the list came to a consensus that it was the way it would
work.

The other problem arises is that if  "leave a property absent from a
descriptor" means keep the property as is, how do you then describe how
to delete a single property from a descriptor?

Regards, christian

Tom-PT Taylor wrote:
> 
> This seems like a practical solution for LocalControl, but if we accept it,
> we have to change the text of the Recommendation, meaning that it only holds
> for H.248v2.  I'll note that we have a real problem of interoperability
> here.  My previous note on the interpretation of this clause presented three
> alternatives, and I got E-mails (one private) in support of all three of
> them.
> 
> I don't quite see Wayne's point on the Signals and Events descriptors.  In
> both cases, the semantics of the situation require the repetition of all of
> the signals/events you want to keep.  You also need at least the KeepActive
> parameter where it applies to signals.  Are you saying, Wayne, that once an
> event or signal is specified, then if it is retained in replacement
> descriptors it is unnecessary to respecify all the parameters that went
> along with it the first time?  I could live with that as an IG
> clarification.  Other views?
> 
> -----Original Message-----
> From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> Sent: Tuesday, January 29, 2002 9:40 AM
> To: 'megaco@ietf.org'
> Subject: Re: [Megaco] Query about local control descriptor properties
> 
> 
> I agreed w/Wayne on option d which is how it was before v1 came out.
> Then we got into these Reserve parameters discussion and changes
> but I didn't think the statement should apply to Property parameters.
> 
> Wayne Cutler wrote:
> 
> What about an option d) that would regard an absent Property as meaning
> "leave the existing value unchanged"?
> As a related question, I note that section 7.1.7 (Local Control Desc.)of
> the spec.
> says that:-
> "A new setting of the LocalControl Descriptor completely replaces the
> previous setting of that descriptor in the MG.  Thus to retain information
> from
> the previous setting the MGC must include that information in the new
> setting".
> Similar statements are made for the Events & Signals Descriptors.
> In the case where an MG supports a number of packages, this text is saying
> that an MGC
> wishing to change data/attributes in one Package in a given Descriptor is
> forced to repeat any previous data against any other Packages. This is
> perverse. So, can this text be qualified to say that the new Descriptor
> replaces only data relating to Packages present in the new/latest message?
> Regards,
> Wayne.
> ------------
> This e-mail and any attachments are confidential.  If you are not the
> intended recipient, please notify us immediately by reply e-mail and then
> delete this message from your system. Do not copy this e-mail or any
> attachments, use the contents for any purpose, or disclose the contents to
> any other person: to do so could be a breach of confidence.
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> --
>   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 mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco


From daemon@ns.ietf.org  Tue Jan 29 23:28:02 2002
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 XAA00815
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:28:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA20100
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 23:28:06 -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 XAA19513;
	Tue, 29 Jan 2002 23:11:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19422
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:11:27 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00592
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:11:21 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA16124;
	Wed, 30 Jan 2002 15:10:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA03196;
	Wed, 30 Jan 2002 15:11:23 +1100 (EST)
Message-ID: <3C5761CC.2527ADF4@ericsson.com.au>
Date: Wed, 30 Jan 2002 14:00:28 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Tom,

I don't think we can accept the exception for property parameters this
would be a big problem for interoperabilty between v1 and v2. Having to
repeat the entire descriptor when we want to change one item I agree is
not nice but the list came to a consensus that it was the way it would
work.

The other problem arises is that if  "leave a property absent from a
descriptor" means keep the property as is, how do you then describe how
to delete a single property from a descriptor?

Regards, christian

Tom-PT Taylor wrote:
> 
> This seems like a practical solution for LocalControl, but if we accept it,
> we have to change the text of the Recommendation, meaning that it only holds
> for H.248v2.  I'll note that we have a real problem of interoperability
> here.  My previous note on the interpretation of this clause presented three
> alternatives, and I got E-mails (one private) in support of all three of
> them.
> 
> I don't quite see Wayne's point on the Signals and Events descriptors.  In
> both cases, the semantics of the situation require the repetition of all of
> the signals/events you want to keep.  You also need at least the KeepActive
> parameter where it applies to signals.  Are you saying, Wayne, that once an
> event or signal is specified, then if it is retained in replacement
> descriptors it is unnecessary to respecify all the parameters that went
> along with it the first time?  I could live with that as an IG
> clarification.  Other views?
> 
> -----Original Message-----
> From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> Sent: Tuesday, January 29, 2002 9:40 AM
> To: 'megaco@ietf.org'
> Subject: Re: [Megaco] Query about local control descriptor properties
> 
> 
> I agreed w/Wayne on option d which is how it was before v1 came out.
> Then we got into these Reserve parameters discussion and changes
> but I didn't think the statement should apply to Property parameters.
> 
> Wayne Cutler wrote:
> 
> What about an option d) that would regard an absent Property as meaning
> "leave the existing value unchanged"?
> As a related question, I note that section 7.1.7 (Local Control Desc.)of
> the spec.
> says that:-
> "A new setting of the LocalControl Descriptor completely replaces the
> previous setting of that descriptor in the MG.  Thus to retain information
> from
> the previous setting the MGC must include that information in the new
> setting".
> Similar statements are made for the Events & Signals Descriptors.
> In the case where an MG supports a number of packages, this text is saying
> that an MGC
> wishing to change data/attributes in one Package in a given Descriptor is
> forced to repeat any previous data against any other Packages. This is
> perverse. So, can this text be qualified to say that the new Descriptor
> replaces only data relating to Packages present in the new/latest message?
> Regards,
> Wayne.
> ------------
> This e-mail and any attachments are confidential.  If you are not the
> intended recipient, please notify us immediately by reply e-mail and then
> delete this message from your system. Do not copy this e-mail or any
> attachments, use the contents for any purpose, or disclose the contents to
> any other person: to do so could be a breach of confidence.
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> --
>   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 mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



From megaco-admin@ietf.org  Tue Jan 29 23:39:53 2002
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 XAA01290
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:39:49 -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 XAA20082;
	Tue, 29 Jan 2002 23:27:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19989
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:27:26 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00782
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:27:21 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0U4QpS15160;
	Tue, 29 Jan 2002 23:26:51 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAX2FY>; Tue, 29 Jan 2002 23:26:50 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01BA4068@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Terry L Anderson <tla@lucent.com>
Cc: megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
Date: Tue, 29 Jan 2002 23:26:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A946.57239880"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A946.57239880
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Oops.. my bad.  I misunderstood the report.  OK, how about we take my
original email, and figure out which items are IG-able, and which are =
not.
This forum is, I think, the best place to do that!

Any comments, anyone?

Kevin

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Tuesday, January 29, 2002 4:27 PM
To: Boyle, Kevin [NCRTP:3Z30:EXCH]
Cc: megaco ietf
Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]


No changes for IG or V2 were approved at the Dublin meeting.  Here is
the item from the Q.3 meeting report:


> 1.3.2.6 AVD-2141a: H.248 Digit Collection Corrections and =
Enhancements
[Nortel]
>
> There was concern that some of the proposed changes (such as the =
matching
rules) would not
> be compatible with V1 implementations. The proposal as a whole is =
complex,
so removal of
> individual features in the proposal that are not backwards compatible =
may
break entire
> proposal.
>
> In TD-40, the proposal was restructured to identify parts that would =
not
be backward
> compatible. There was a lack of time to adequately review this
contribution, but we recognize
> that many of the items in the proposal need attention. We will =
proceed as
follows:
> =B7 Separately identify items for the implementers guide and post =
these to
the megaco and SG16
> lists
> =B7 Separately identify items intended for V2 and post these to the =
megaco
and SG16 lists
> =B7 The proposed extended DTMF detection package is accepted as a new =
annex
on the condition
> that the related material for V2 is accepted
>
> Understanding that sufficient time is needed to review the entire
proposal, the material is
> accepted in principle, subject to further review and open to =
contributions
or
> counter-proposals.
>

I have not seen a list of proposed items (extracted from TD-40) =
intended
for the IG or for V2 posted to the mailing list for discussion and so
have not included any of these items in my IG draft.

Kevin Boyle wrote:

>
>
> Actually, I have some.
>
> The IG posted there is lacking the digit collection changes agreed
> upon in Dublin.  Here are the changes as agreed upon:
>
> Section 7.1.14.2:
> Change: "The timers are configurable parameters to a DigitMap.  The
> Start timer is started at the beginning of every digit map use, but
> can be overridden."
>
> To: "Default values of these timers should be provisioned on the MG,
> but can be overridden by values specified within the DigitMap."
>
> Section 7.1.14.3:
> Change: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the results are undefined."
>
> To: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the long timer shall be used."
>
> Change: "The value of this threshold is assumed to be provisioned in
> the MG."
> To: "The value of this threshold is assumed to be provisioned in the
> MG, but, like the T, L, and S timers, can be overridden by
> specification within the DigitMap."
>
> Section 7.1.14.4:
> Change: "Subsequent events in the package are processed as per the
> currently active event processing mechanisms."
> To: "Subsequent digit events in the package are processed as follows:
>
> =B7if EventBufferControl is ON, subsequent digit events are processed =
in
> the same way as any other events;
>
> =B7if EventBufferControl is OFF, if the active EventsDescriptor did =
not
> change, and if individual digit events are not enabled within that
> descriptor, then digit buffering will be initiated.  Buffering will
> continue until the buffering time specified in the original digit map
> completion event has expired or until the active EventsDescriptor is
> replaced.
>
> The digit buffer shall take the logical form of a dial string which
> includes the digit characters as represented in the digit map,
> possibly preceded by 'Z'.  The threshold value of tone duration used
> to identify long events shall be the same as that used with the most
> recently completed digit map.
>
> Buffering time defaults to zero (no buffering) unless explicitly set
> otherwise within the digit map completion event.  If buffering ceases
> due to buffering timer expiry, the contents of the digit buffer are
> discarded.
>
> If buffering was stopped by a new EventsDescriptor, then if that
> EventsDescriptor contains a new digit map completion event from the
> same package as the previous one, any buffered digits are processed
> against the digit map as described below.  Buffered digits not
> consumed by the new digit map are handled as if they had were =
observed
> after that map completed.
>
> If instead the new EventsDescriptor enables the reporting of
> individual digit events, the entire set of buffered digits shall
> immediately be processed, the applicable events reported, and the
> buffer cleared.
>
> Finally, if the new EventsDescriptor enables neither a digit map
> completion event nor the reporting of individual digit events from =
the
> package concerned, the buffer contents are discarded and buffering is
> terminated."
>
> (All of the paragraphs following the second bullet are part of that
> bullet item.)
>
> Section 7.1.14.5:
>
> Change: "2. At each step, a timer is set to wait for the next event,
> based either on the default timing rules given above or on explicit
> timing specified in one or more alternative event sequences. If the
> timer expires and a member of the candidate set of alternatives is
> fully satisfied, a timeout completion with full match is reported.  =
If
> the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported."
>
> To: "2. At each step, if buffered digits are available, the oldest =
one
> (with possible accompanying long digit (Z) qualifier) is removed from
> the buffer and processing moves to the next step as if the digit =
event
> had just been observed.  Otherwise a timer is set to wait for the =
next
> event, based either on the default timing rules given above or on
> explicit timing specified in one or more alternative event sequences.
> If the timer expires and a member of the candidate set of =
alternatives
> is fully satisfied, a timeout completion with full match is reported.
> If the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported.  In
> either case, if the digit map completion event allows for detailed
> timeout reporting, the reported dial string will end with 'L' or 'S'
> as appropriate."
>
> Change (step 5): "The event removed from the current dial string will
> then be reported as per the currently active event processing
> mechanisms."
>
> To: "The event removed from the current dial string will then be
> reported as a separate event, buffered, or discarded according to the
> rules described in the previous section.  This statement is qualified
> as follows:
>
> a) The digit map completion event may specify that the event be
> reported as a parameter of that event.  This occurs independently of
> subsequent processing of the digit event.
>
> b) The digit map completion event may specify that the extra digit
> should be discarded.  In this case, it is discarded immediately.  Any
> buffering or other processing applies only to subsequent events."
>
> Section 6.1.14.7:
>
> Change: "=B7 the events in the package containing the specified digit
> map completion event other than the completion event itself are not
> individually notified, and"
>
> To: "=B7 the events in the package containing the specified digit map
> completion event other than the completion event itself are not
> individually notified and have no side-effects unless separately
> enabled, and"
>
> Change: "=B7 an event that triggers a partial match completion event =
is
> not recognized and therefore has no side effects until reprocessed
> following the recognition of the digit map completion event."
>
> To: "=B7 an event that triggers a partial match completion event is =
not
> recognized and therefore has no side effects unless and until
> reprocessed following the recognition of the digit map completion
> event.  Similarly buffered digit events are not recognized and have =
no
> side effects until processed."
>
> Annex C:
>
> Change:
>
>    digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] digitMap
>    Timer                =3D 1*2DIGIT
>
> To:
>
>    digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] ["Z" COLON Timer
> COMMA]
>                            digitMap
>    Timer                =3D 1*2DIGIT
>    ; Units are seconds for T, S, and L timers, and hundreds of
> milliseconds for Z timer.
>    ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to
> 9.9 s.
>
> Kevin
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 28, 2002 7:26 PM
> To: megaco ietf
> Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
>
> G'Day all,
>
> I have uploaded a number of H.248 editors' contributions and company
> contributions to the PICTEL website.
> http://standard.pictel.com/ftp/avc-site/0202_Gen/
>
> A list of the documents is below. The latest version of H.248 is =
among
>
> them. Comments?
>
> Regards, Christian
>
> -------- Original Message --------
> Subject: Fwd: Uploaded files to Incoming
> Date: Thu, 24 Jan 2002 16:27:59 +0900
> From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> To: ITU-SG16@echo.jf.INTEL.COM
>
> Dear SG16 experts,
>
> They are now available at /0202_Gen of the avc-site.
>
> At 16:16 +1100 02/01/24, Christian Groves wrote:
> >I have placed the following files in the incoming directory. Could
> you
> >please move them to the Geneve directory?
> >
> >1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
> >2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server
> Package
> >3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing
> Package
> >4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
> >5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
> >6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor
> Usage
> >7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
> >descriptor
> >8. [DC-xxx_Packages_Guide] Packages Guide
> >9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
> >10. [DC-xxx_H248v2] Draft H.248v2
>
> Best regards,
>
> OKUBO Sakae
> *********************************************************
> Global Information and Telecommunication Institute (GITI)
> Waseda University
> 29-7 Waseda University Bldg.
> 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
> 169-0051 Japan
>         e-mail: okubo@giti.waseda.ac.jp
>         Tel: +81 3 3204 8194
>         Fax: +81 3 5286 3832
> *********************************************************
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


------_=_NextPart_001_01C1A946.57239880
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Oops.. my bad.&nbsp; I misunderstood the =
report.&nbsp; OK, how about we take my original email, and figure out =
which items are IG-able, and which are not.&nbsp; This forum is, I =
think, the best place to do that!</FONT></P>

<P><FONT SIZE=3D2>Any comments, anyone?</FONT>
</P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, January 29, 2002 4:27 PM</FONT>
<BR><FONT SIZE=3D2>To: Boyle, Kevin [NCRTP:3Z30:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: megaco ietf</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files =
to Incoming]</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>No changes for IG or V2 were approved at the Dublin =
meeting.&nbsp; Here is</FONT>
<BR><FONT SIZE=3D2>the item from the Q.3 meeting report:</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; 1.3.2.6 AVD-2141a: H.248 Digit Collection =
Corrections and Enhancements [Nortel]</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; There was concern that some of the proposed =
changes (such as the matching rules) would not</FONT>
<BR><FONT SIZE=3D2>&gt; be compatible with V1 implementations. The =
proposal as a whole is complex, so removal of</FONT>
<BR><FONT SIZE=3D2>&gt; individual features in the proposal that are =
not backwards compatible may break entire</FONT>
<BR><FONT SIZE=3D2>&gt; proposal.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; In TD-40, the proposal was restructured to =
identify parts that would not be backward</FONT>
<BR><FONT SIZE=3D2>&gt; compatible. There was a lack of time to =
adequately review this contribution, but we recognize</FONT>
<BR><FONT SIZE=3D2>&gt; that many of the items in the proposal need =
attention. We will proceed as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 Separately identify items for the =
implementers guide and post these to the megaco and SG16</FONT>
<BR><FONT SIZE=3D2>&gt; lists</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 Separately identify items intended for V2 =
and post these to the megaco and SG16 lists</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 The proposed extended DTMF detection =
package is accepted as a new annex on the condition</FONT>
<BR><FONT SIZE=3D2>&gt; that the related material for V2 is =
accepted</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Understanding that sufficient time is needed to =
review the entire proposal, the material is</FONT>
<BR><FONT SIZE=3D2>&gt; accepted in principle, subject to further =
review and open to contributions or</FONT>
<BR><FONT SIZE=3D2>&gt; counter-proposals.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>I have not seen a list of proposed items (extracted =
from TD-40) intended</FONT>
<BR><FONT SIZE=3D2>for the IG or for V2 posted to the mailing list for =
discussion and so</FONT>
<BR><FONT SIZE=3D2>have not included any of these items in my IG =
draft.</FONT>
</P>

<P><FONT SIZE=3D2>Kevin Boyle wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Actually, I have some.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The IG posted there is lacking the digit =
collection changes agreed</FONT>
<BR><FONT SIZE=3D2>&gt; upon in Dublin.&nbsp; Here are the changes as =
agreed upon:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.2:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;The timers are configurable =
parameters to a DigitMap.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&gt; Start timer is started at the beginning of =
every digit map use, but</FONT>
<BR><FONT SIZE=3D2>&gt; can be overridden.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Default values of these timers should =
be provisioned on the MG,</FONT>
<BR><FONT SIZE=3D2>&gt; but can be overridden by values specified =
within the DigitMap.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.3:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;Finally, if conflicting timing =
specifiers are in effect in</FONT>
<BR><FONT SIZE=3D2>&gt; different alternative sequences, the results =
are undefined.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Finally, if conflicting timing =
specifiers are in effect in</FONT>
<BR><FONT SIZE=3D2>&gt; different alternative sequences, the long timer =
shall be used.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;The value of this threshold is =
assumed to be provisioned in</FONT>
<BR><FONT SIZE=3D2>&gt; the MG.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;The value of this threshold is =
assumed to be provisioned in the</FONT>
<BR><FONT SIZE=3D2>&gt; MG, but, like the T, L, and S timers, can be =
overridden by</FONT>
<BR><FONT SIZE=3D2>&gt; specification within the DigitMap.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.4:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;Subsequent events in the package =
are processed as per the</FONT>
<BR><FONT SIZE=3D2>&gt; currently active event processing =
mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Subsequent digit events in the =
package are processed as follows:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =B7if EventBufferControl is ON, subsequent =
digit events are processed in</FONT>
<BR><FONT SIZE=3D2>&gt; the same way as any other events;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =B7if EventBufferControl is OFF, if the active =
EventsDescriptor did not</FONT>
<BR><FONT SIZE=3D2>&gt; change, and if individual digit events are not =
enabled within that</FONT>
<BR><FONT SIZE=3D2>&gt; descriptor, then digit buffering will be =
initiated.&nbsp; Buffering will</FONT>
<BR><FONT SIZE=3D2>&gt; continue until the buffering time specified in =
the original digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event has expired or until the =
active EventsDescriptor is</FONT>
<BR><FONT SIZE=3D2>&gt; replaced.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The digit buffer shall take the logical form of =
a dial string which</FONT>
<BR><FONT SIZE=3D2>&gt; includes the digit characters as represented in =
the digit map,</FONT>
<BR><FONT SIZE=3D2>&gt; possibly preceded by 'Z'.&nbsp; The threshold =
value of tone duration used</FONT>
<BR><FONT SIZE=3D2>&gt; to identify long events shall be the same as =
that used with the most</FONT>
<BR><FONT SIZE=3D2>&gt; recently completed digit map.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Buffering time defaults to zero (no buffering) =
unless explicitly set</FONT>
<BR><FONT SIZE=3D2>&gt; otherwise within the digit map completion =
event.&nbsp; If buffering ceases</FONT>
<BR><FONT SIZE=3D2>&gt; due to buffering timer expiry, the contents of =
the digit buffer are</FONT>
<BR><FONT SIZE=3D2>&gt; discarded.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; If buffering was stopped by a new =
EventsDescriptor, then if that</FONT>
<BR><FONT SIZE=3D2>&gt; EventsDescriptor contains a new digit map =
completion event from the</FONT>
<BR><FONT SIZE=3D2>&gt; same package as the previous one, any buffered =
digits are processed</FONT>
<BR><FONT SIZE=3D2>&gt; against the digit map as described below.&nbsp; =
Buffered digits not</FONT>
<BR><FONT SIZE=3D2>&gt; consumed by the new digit map are handled as if =
they had were observed</FONT>
<BR><FONT SIZE=3D2>&gt; after that map completed.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; If instead the new EventsDescriptor enables the =
reporting of</FONT>
<BR><FONT SIZE=3D2>&gt; individual digit events, the entire set of =
buffered digits shall</FONT>
<BR><FONT SIZE=3D2>&gt; immediately be processed, the applicable events =
reported, and the</FONT>
<BR><FONT SIZE=3D2>&gt; buffer cleared.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Finally, if the new EventsDescriptor enables =
neither a digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event nor the reporting of =
individual digit events from the</FONT>
<BR><FONT SIZE=3D2>&gt; package concerned, the buffer contents are =
discarded and buffering is</FONT>
<BR><FONT SIZE=3D2>&gt; terminated.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; (All of the paragraphs following the second =
bullet are part of that</FONT>
<BR><FONT SIZE=3D2>&gt; bullet item.)</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.5:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;2. At each step, a timer is set =
to wait for the next event,</FONT>
<BR><FONT SIZE=3D2>&gt; based either on the default timing rules given =
above or on explicit</FONT>
<BR><FONT SIZE=3D2>&gt; timing specified in one or more alternative =
event sequences. If the</FONT>
<BR><FONT SIZE=3D2>&gt; timer expires and a member of the candidate set =
of alternatives is</FONT>
<BR><FONT SIZE=3D2>&gt; fully satisfied, a timeout completion with full =
match is reported.&nbsp; If</FONT>
<BR><FONT SIZE=3D2>&gt; the timer expires and part or none of any =
candidate alternative is</FONT>
<BR><FONT SIZE=3D2>&gt; satisfied, a timeout completion with partial =
match is reported.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;2. At each step, if buffered digits =
are available, the oldest one</FONT>
<BR><FONT SIZE=3D2>&gt; (with possible accompanying long digit (Z) =
qualifier) is removed from</FONT>
<BR><FONT SIZE=3D2>&gt; the buffer and processing moves to the next =
step as if the digit event</FONT>
<BR><FONT SIZE=3D2>&gt; had just been observed.&nbsp; Otherwise a timer =
is set to wait for the next</FONT>
<BR><FONT SIZE=3D2>&gt; event, based either on the default timing rules =
given above or on</FONT>
<BR><FONT SIZE=3D2>&gt; explicit timing specified in one or more =
alternative event sequences.</FONT>
<BR><FONT SIZE=3D2>&gt; If the timer expires and a member of the =
candidate set of alternatives</FONT>
<BR><FONT SIZE=3D2>&gt; is fully satisfied, a timeout completion with =
full match is reported.</FONT>
<BR><FONT SIZE=3D2>&gt; If the timer expires and part or none of any =
candidate alternative is</FONT>
<BR><FONT SIZE=3D2>&gt; satisfied, a timeout completion with partial =
match is reported.&nbsp; In</FONT>
<BR><FONT SIZE=3D2>&gt; either case, if the digit map completion event =
allows for detailed</FONT>
<BR><FONT SIZE=3D2>&gt; timeout reporting, the reported dial string =
will end with 'L' or 'S'</FONT>
<BR><FONT SIZE=3D2>&gt; as appropriate.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change (step 5): &quot;The event removed from =
the current dial string will</FONT>
<BR><FONT SIZE=3D2>&gt; then be reported as per the currently active =
event processing</FONT>
<BR><FONT SIZE=3D2>&gt; mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;The event removed from the current =
dial string will then be</FONT>
<BR><FONT SIZE=3D2>&gt; reported as a separate event, buffered, or =
discarded according to the</FONT>
<BR><FONT SIZE=3D2>&gt; rules described in the previous section.&nbsp; =
This statement is qualified</FONT>
<BR><FONT SIZE=3D2>&gt; as follows:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; a) The digit map completion event may specify =
that the event be</FONT>
<BR><FONT SIZE=3D2>&gt; reported as a parameter of that event.&nbsp; =
This occurs independently of</FONT>
<BR><FONT SIZE=3D2>&gt; subsequent processing of the digit =
event.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; b) The digit map completion event may specify =
that the extra digit</FONT>
<BR><FONT SIZE=3D2>&gt; should be discarded.&nbsp; In this case, it is =
discarded immediately.&nbsp; Any</FONT>
<BR><FONT SIZE=3D2>&gt; buffering or other processing applies only to =
subsequent events.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 6.1.14.7:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;=B7 the events in the package =
containing the specified digit</FONT>
<BR><FONT SIZE=3D2>&gt; map completion event other than the completion =
event itself are not</FONT>
<BR><FONT SIZE=3D2>&gt; individually notified, and&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;=B7 the events in the package =
containing the specified digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event other than the completion =
event itself are not</FONT>
<BR><FONT SIZE=3D2>&gt; individually notified and have no side-effects =
unless separately</FONT>
<BR><FONT SIZE=3D2>&gt; enabled, and&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;=B7 an event that triggers a =
partial match completion event is</FONT>
<BR><FONT SIZE=3D2>&gt; not recognized and therefore has no side =
effects until reprocessed</FONT>
<BR><FONT SIZE=3D2>&gt; following the recognition of the digit map =
completion event.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;=B7 an event that triggers a partial =
match completion event is not</FONT>
<BR><FONT SIZE=3D2>&gt; recognized and therefore has no side effects =
unless and until</FONT>
<BR><FONT SIZE=3D2>&gt; reprocessed following the recognition of the =
digit map completion</FONT>
<BR><FONT SIZE=3D2>&gt; event.&nbsp; Similarly buffered digit events =
are not recognized and have no</FONT>
<BR><FONT SIZE=3D2>&gt; side effects until processed.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Annex C:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] =
digitMap</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] =
[&quot;Z&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; digitMap</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; ; Units are seconds for T, S, =
and L timers, and hundreds of</FONT>
<BR><FONT SIZE=3D2>&gt; milliseconds for Z timer.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; ; Thus T, S, and L range from =
1 to 99 seconds and Z from 100 ms to</FONT>
<BR><FONT SIZE=3D2>&gt; 9.9 s.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Kevin</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Christian Groves [<A =
HREF=3D"mailto:Christian.Groves@ericsson.com.au">mailto:Christian.Groves=
@ericsson.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, January 28, 2002 7:26 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: megaco ietf</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Megaco] [Fwd: Fwd: Uploaded files to =
Incoming]</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; G'Day all,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I have uploaded a number of H.248 editors' =
contributions and company</FONT>
<BR><FONT SIZE=3D2>&gt; contributions to the PICTEL website.</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://standard.pictel.com/ftp/avc-site/0202_Gen/" =
TARGET=3D"_blank">http://standard.pictel.com/ftp/avc-site/0202_Gen/</A><=
/FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; A list of the documents is below. The latest =
version of H.248 is among</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; them. Comments?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -------- Original Message --------</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Fwd: Uploaded files to Incoming</FONT>
<BR><FONT SIZE=3D2>&gt; Date: Thu, 24 Jan 2002 16:27:59 +0900</FONT>
<BR><FONT SIZE=3D2>&gt; From: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Reply-To: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: ITU-SG16@echo.jf.INTEL.COM</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Dear SG16 experts,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; They are now available at /0202_Gen of the =
avc-site.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; At 16:16 +1100 02/01/24, Christian Groves =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I have placed the following files in the =
incoming directory. Could</FONT>
<BR><FONT SIZE=3D2>&gt; you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;please move them to the Geneve =
directory?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;1. [DC-xxx_Annex_L_amm1] Proposed H.248 =
Annex L Amendment 1</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;2. [DC-xxx_Annex_M_1] Comments to H.248 =
Annex M.1 Audio Server</FONT>
<BR><FONT SIZE=3D2>&gt; Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac =
Quality Alert Ceasing</FONT>
<BR><FONT SIZE=3D2>&gt; Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 =
Package Attribute</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;5. [DC-xxx_Imp_Guide] H.248 Implementors' =
Guide Additions</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;6. [DC-xxx_MuxDescription] Clarification of =
H.248 Mux Descriptor</FONT>
<BR><FONT SIZE=3D2>&gt; Usage</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;7. [DC-xxx_Nx64K] Addition of Nx64K Service =
to the H.248 Mutliplex</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;descriptor</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;8. [DC-xxx_Packages_Guide] Packages =
Guide</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;9. [DC-xxx_Profile_Pkg] Draft H.248 Annex =
M.profile Profile Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;10. [DC-xxx_H248v2] Draft H.248v2</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Best regards,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; OKUBO Sakae</FONT>
<BR><FONT SIZE=3D2>&gt; =
*********************************************************</FONT>
<BR><FONT SIZE=3D2>&gt; Global Information and Telecommunication =
Institute (GITI)</FONT>
<BR><FONT SIZE=3D2>&gt; Waseda University</FONT>
<BR><FONT SIZE=3D2>&gt; 29-7 Waseda University Bldg.</FONT>
<BR><FONT SIZE=3D2>&gt; 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo</FONT>
<BR><FONT SIZE=3D2>&gt; 169-0051 Japan</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
e-mail: okubo@giti.waseda.ac.jp</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Tel: +81 3 3204 8194</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Fax: +81 3 5286 3832</FONT>
<BR><FONT SIZE=3D2>&gt; =
*********************************************************</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

<P><FONT SIZE=3D2>--</FONT>
</P>

<P><FONT =
SIZE=3D2>------------------------------------------------------------</F=
ONT>
<BR><FONT SIZE=3D2>Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A946.57239880--

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


From daemon@ns.ietf.org  Tue Jan 29 23:39:53 2002
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 XAA01301
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:39:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA20857
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 23:39:57 -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 XAA20082;
	Tue, 29 Jan 2002 23:27:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA19989
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:27:26 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00782
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:27:21 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0U4QpS15160;
	Tue, 29 Jan 2002 23:26:51 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAX2FY>; Tue, 29 Jan 2002 23:26:50 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01BA4068@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Terry L Anderson <tla@lucent.com>
Cc: megaco ietf <megaco@ietf.org>
Subject: RE: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]
Date: Tue, 29 Jan 2002 23:26:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A946.57239880"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A946.57239880
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Oops.. my bad.  I misunderstood the report.  OK, how about we take my
original email, and figure out which items are IG-able, and which are =
not.
This forum is, I think, the best place to do that!

Any comments, anyone?

Kevin

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Tuesday, January 29, 2002 4:27 PM
To: Boyle, Kevin [NCRTP:3Z30:EXCH]
Cc: megaco ietf
Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]


No changes for IG or V2 were approved at the Dublin meeting.  Here is
the item from the Q.3 meeting report:


> 1.3.2.6 AVD-2141a: H.248 Digit Collection Corrections and =
Enhancements
[Nortel]
>
> There was concern that some of the proposed changes (such as the =
matching
rules) would not
> be compatible with V1 implementations. The proposal as a whole is =
complex,
so removal of
> individual features in the proposal that are not backwards compatible =
may
break entire
> proposal.
>
> In TD-40, the proposal was restructured to identify parts that would =
not
be backward
> compatible. There was a lack of time to adequately review this
contribution, but we recognize
> that many of the items in the proposal need attention. We will =
proceed as
follows:
> =B7 Separately identify items for the implementers guide and post =
these to
the megaco and SG16
> lists
> =B7 Separately identify items intended for V2 and post these to the =
megaco
and SG16 lists
> =B7 The proposed extended DTMF detection package is accepted as a new =
annex
on the condition
> that the related material for V2 is accepted
>
> Understanding that sufficient time is needed to review the entire
proposal, the material is
> accepted in principle, subject to further review and open to =
contributions
or
> counter-proposals.
>

I have not seen a list of proposed items (extracted from TD-40) =
intended
for the IG or for V2 posted to the mailing list for discussion and so
have not included any of these items in my IG draft.

Kevin Boyle wrote:

>
>
> Actually, I have some.
>
> The IG posted there is lacking the digit collection changes agreed
> upon in Dublin.  Here are the changes as agreed upon:
>
> Section 7.1.14.2:
> Change: "The timers are configurable parameters to a DigitMap.  The
> Start timer is started at the beginning of every digit map use, but
> can be overridden."
>
> To: "Default values of these timers should be provisioned on the MG,
> but can be overridden by values specified within the DigitMap."
>
> Section 7.1.14.3:
> Change: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the results are undefined."
>
> To: "Finally, if conflicting timing specifiers are in effect in
> different alternative sequences, the long timer shall be used."
>
> Change: "The value of this threshold is assumed to be provisioned in
> the MG."
> To: "The value of this threshold is assumed to be provisioned in the
> MG, but, like the T, L, and S timers, can be overridden by
> specification within the DigitMap."
>
> Section 7.1.14.4:
> Change: "Subsequent events in the package are processed as per the
> currently active event processing mechanisms."
> To: "Subsequent digit events in the package are processed as follows:
>
> =B7if EventBufferControl is ON, subsequent digit events are processed =
in
> the same way as any other events;
>
> =B7if EventBufferControl is OFF, if the active EventsDescriptor did =
not
> change, and if individual digit events are not enabled within that
> descriptor, then digit buffering will be initiated.  Buffering will
> continue until the buffering time specified in the original digit map
> completion event has expired or until the active EventsDescriptor is
> replaced.
>
> The digit buffer shall take the logical form of a dial string which
> includes the digit characters as represented in the digit map,
> possibly preceded by 'Z'.  The threshold value of tone duration used
> to identify long events shall be the same as that used with the most
> recently completed digit map.
>
> Buffering time defaults to zero (no buffering) unless explicitly set
> otherwise within the digit map completion event.  If buffering ceases
> due to buffering timer expiry, the contents of the digit buffer are
> discarded.
>
> If buffering was stopped by a new EventsDescriptor, then if that
> EventsDescriptor contains a new digit map completion event from the
> same package as the previous one, any buffered digits are processed
> against the digit map as described below.  Buffered digits not
> consumed by the new digit map are handled as if they had were =
observed
> after that map completed.
>
> If instead the new EventsDescriptor enables the reporting of
> individual digit events, the entire set of buffered digits shall
> immediately be processed, the applicable events reported, and the
> buffer cleared.
>
> Finally, if the new EventsDescriptor enables neither a digit map
> completion event nor the reporting of individual digit events from =
the
> package concerned, the buffer contents are discarded and buffering is
> terminated."
>
> (All of the paragraphs following the second bullet are part of that
> bullet item.)
>
> Section 7.1.14.5:
>
> Change: "2. At each step, a timer is set to wait for the next event,
> based either on the default timing rules given above or on explicit
> timing specified in one or more alternative event sequences. If the
> timer expires and a member of the candidate set of alternatives is
> fully satisfied, a timeout completion with full match is reported.  =
If
> the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported."
>
> To: "2. At each step, if buffered digits are available, the oldest =
one
> (with possible accompanying long digit (Z) qualifier) is removed from
> the buffer and processing moves to the next step as if the digit =
event
> had just been observed.  Otherwise a timer is set to wait for the =
next
> event, based either on the default timing rules given above or on
> explicit timing specified in one or more alternative event sequences.
> If the timer expires and a member of the candidate set of =
alternatives
> is fully satisfied, a timeout completion with full match is reported.
> If the timer expires and part or none of any candidate alternative is
> satisfied, a timeout completion with partial match is reported.  In
> either case, if the digit map completion event allows for detailed
> timeout reporting, the reported dial string will end with 'L' or 'S'
> as appropriate."
>
> Change (step 5): "The event removed from the current dial string will
> then be reported as per the currently active event processing
> mechanisms."
>
> To: "The event removed from the current dial string will then be
> reported as a separate event, buffered, or discarded according to the
> rules described in the previous section.  This statement is qualified
> as follows:
>
> a) The digit map completion event may specify that the event be
> reported as a parameter of that event.  This occurs independently of
> subsequent processing of the digit event.
>
> b) The digit map completion event may specify that the extra digit
> should be discarded.  In this case, it is discarded immediately.  Any
> buffering or other processing applies only to subsequent events."
>
> Section 6.1.14.7:
>
> Change: "=B7 the events in the package containing the specified digit
> map completion event other than the completion event itself are not
> individually notified, and"
>
> To: "=B7 the events in the package containing the specified digit map
> completion event other than the completion event itself are not
> individually notified and have no side-effects unless separately
> enabled, and"
>
> Change: "=B7 an event that triggers a partial match completion event =
is
> not recognized and therefore has no side effects until reprocessed
> following the recognition of the digit map completion event."
>
> To: "=B7 an event that triggers a partial match completion event is =
not
> recognized and therefore has no side effects unless and until
> reprocessed following the recognition of the digit map completion
> event.  Similarly buffered digit events are not recognized and have =
no
> side effects until processed."
>
> Annex C:
>
> Change:
>
>    digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] digitMap
>    Timer                =3D 1*2DIGIT
>
> To:
>
>    digitMapValue        =3D ["T" COLON Timer COMMA] ["S" COLON Timer
> COMMA]
>                           ["L" COLON Timer COMMA] ["Z" COLON Timer
> COMMA]
>                            digitMap
>    Timer                =3D 1*2DIGIT
>    ; Units are seconds for T, S, and L timers, and hundreds of
> milliseconds for Z timer.
>    ; Thus T, S, and L range from 1 to 99 seconds and Z from 100 ms to
> 9.9 s.
>
> Kevin
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Monday, January 28, 2002 7:26 PM
> To: megaco ietf
> Subject: [Megaco] [Fwd: Fwd: Uploaded files to Incoming]
>
> G'Day all,
>
> I have uploaded a number of H.248 editors' contributions and company
> contributions to the PICTEL website.
> http://standard.pictel.com/ftp/avc-site/0202_Gen/
>
> A list of the documents is below. The latest version of H.248 is =
among
>
> them. Comments?
>
> Regards, Christian
>
> -------- Original Message --------
> Subject: Fwd: Uploaded files to Incoming
> Date: Thu, 24 Jan 2002 16:27:59 +0900
> From: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> Reply-To: OKUBO Sakae <okubo@GITI.WASEDA.AC.JP>
> To: ITU-SG16@echo.jf.INTEL.COM
>
> Dear SG16 experts,
>
> They are now available at /0202_Gen of the avc-site.
>
> At 16:16 +1100 02/01/24, Christian Groves wrote:
> >I have placed the following files in the incoming directory. Could
> you
> >please move them to the Geneve directory?
> >
> >1. [DC-xxx_Annex_L_amm1] Proposed H.248 Annex L Amendment 1
> >2. [DC-xxx_Annex_M_1] Comments to H.248 Annex M.1 Audio Server
> Package
> >3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac Quality Alert Ceasing
> Package
> >4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 Package Attribute
> >5. [DC-xxx_Imp_Guide] H.248 Implementors' Guide Additions
> >6. [DC-xxx_MuxDescription] Clarification of H.248 Mux Descriptor
> Usage
> >7. [DC-xxx_Nx64K] Addition of Nx64K Service to the H.248 Mutliplex
> >descriptor
> >8. [DC-xxx_Packages_Guide] Packages Guide
> >9. [DC-xxx_Profile_Pkg] Draft H.248 Annex M.profile Profile Package
> >10. [DC-xxx_H248v2] Draft H.248v2
>
> Best regards,
>
> OKUBO Sakae
> *********************************************************
> Global Information and Telecommunication Institute (GITI)
> Waseda University
> 29-7 Waseda University Bldg.
> 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
> 169-0051 Japan
>         e-mail: okubo@giti.waseda.ac.jp
>         Tel: +81 3 3204 8194
>         Fax: +81 3 5286 3832
> *********************************************************
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


------_=_NextPart_001_01C1A946.57239880
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] RE: [Fwd: Fwd: Uploaded files to Incoming]</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Oops.. my bad.&nbsp; I misunderstood the =
report.&nbsp; OK, how about we take my original email, and figure out =
which items are IG-able, and which are not.&nbsp; This forum is, I =
think, the best place to do that!</FONT></P>

<P><FONT SIZE=3D2>Any comments, anyone?</FONT>
</P>

<P><FONT SIZE=3D2>Kevin</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Terry L Anderson [<A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, January 29, 2002 4:27 PM</FONT>
<BR><FONT SIZE=3D2>To: Boyle, Kevin [NCRTP:3Z30:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: megaco ietf</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] RE: [Fwd: Fwd: Uploaded files =
to Incoming]</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>No changes for IG or V2 were approved at the Dublin =
meeting.&nbsp; Here is</FONT>
<BR><FONT SIZE=3D2>the item from the Q.3 meeting report:</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; 1.3.2.6 AVD-2141a: H.248 Digit Collection =
Corrections and Enhancements [Nortel]</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; There was concern that some of the proposed =
changes (such as the matching rules) would not</FONT>
<BR><FONT SIZE=3D2>&gt; be compatible with V1 implementations. The =
proposal as a whole is complex, so removal of</FONT>
<BR><FONT SIZE=3D2>&gt; individual features in the proposal that are =
not backwards compatible may break entire</FONT>
<BR><FONT SIZE=3D2>&gt; proposal.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; In TD-40, the proposal was restructured to =
identify parts that would not be backward</FONT>
<BR><FONT SIZE=3D2>&gt; compatible. There was a lack of time to =
adequately review this contribution, but we recognize</FONT>
<BR><FONT SIZE=3D2>&gt; that many of the items in the proposal need =
attention. We will proceed as follows:</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 Separately identify items for the =
implementers guide and post these to the megaco and SG16</FONT>
<BR><FONT SIZE=3D2>&gt; lists</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 Separately identify items intended for V2 =
and post these to the megaco and SG16 lists</FONT>
<BR><FONT SIZE=3D2>&gt; =B7 The proposed extended DTMF detection =
package is accepted as a new annex on the condition</FONT>
<BR><FONT SIZE=3D2>&gt; that the related material for V2 is =
accepted</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Understanding that sufficient time is needed to =
review the entire proposal, the material is</FONT>
<BR><FONT SIZE=3D2>&gt; accepted in principle, subject to further =
review and open to contributions or</FONT>
<BR><FONT SIZE=3D2>&gt; counter-proposals.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>I have not seen a list of proposed items (extracted =
from TD-40) intended</FONT>
<BR><FONT SIZE=3D2>for the IG or for V2 posted to the mailing list for =
discussion and so</FONT>
<BR><FONT SIZE=3D2>have not included any of these items in my IG =
draft.</FONT>
</P>

<P><FONT SIZE=3D2>Kevin Boyle wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Actually, I have some.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The IG posted there is lacking the digit =
collection changes agreed</FONT>
<BR><FONT SIZE=3D2>&gt; upon in Dublin.&nbsp; Here are the changes as =
agreed upon:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.2:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;The timers are configurable =
parameters to a DigitMap.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&gt; Start timer is started at the beginning of =
every digit map use, but</FONT>
<BR><FONT SIZE=3D2>&gt; can be overridden.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Default values of these timers should =
be provisioned on the MG,</FONT>
<BR><FONT SIZE=3D2>&gt; but can be overridden by values specified =
within the DigitMap.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.3:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;Finally, if conflicting timing =
specifiers are in effect in</FONT>
<BR><FONT SIZE=3D2>&gt; different alternative sequences, the results =
are undefined.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Finally, if conflicting timing =
specifiers are in effect in</FONT>
<BR><FONT SIZE=3D2>&gt; different alternative sequences, the long timer =
shall be used.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;The value of this threshold is =
assumed to be provisioned in</FONT>
<BR><FONT SIZE=3D2>&gt; the MG.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;The value of this threshold is =
assumed to be provisioned in the</FONT>
<BR><FONT SIZE=3D2>&gt; MG, but, like the T, L, and S timers, can be =
overridden by</FONT>
<BR><FONT SIZE=3D2>&gt; specification within the DigitMap.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.4:</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;Subsequent events in the package =
are processed as per the</FONT>
<BR><FONT SIZE=3D2>&gt; currently active event processing =
mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;Subsequent digit events in the =
package are processed as follows:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =B7if EventBufferControl is ON, subsequent =
digit events are processed in</FONT>
<BR><FONT SIZE=3D2>&gt; the same way as any other events;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =B7if EventBufferControl is OFF, if the active =
EventsDescriptor did not</FONT>
<BR><FONT SIZE=3D2>&gt; change, and if individual digit events are not =
enabled within that</FONT>
<BR><FONT SIZE=3D2>&gt; descriptor, then digit buffering will be =
initiated.&nbsp; Buffering will</FONT>
<BR><FONT SIZE=3D2>&gt; continue until the buffering time specified in =
the original digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event has expired or until the =
active EventsDescriptor is</FONT>
<BR><FONT SIZE=3D2>&gt; replaced.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; The digit buffer shall take the logical form of =
a dial string which</FONT>
<BR><FONT SIZE=3D2>&gt; includes the digit characters as represented in =
the digit map,</FONT>
<BR><FONT SIZE=3D2>&gt; possibly preceded by 'Z'.&nbsp; The threshold =
value of tone duration used</FONT>
<BR><FONT SIZE=3D2>&gt; to identify long events shall be the same as =
that used with the most</FONT>
<BR><FONT SIZE=3D2>&gt; recently completed digit map.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Buffering time defaults to zero (no buffering) =
unless explicitly set</FONT>
<BR><FONT SIZE=3D2>&gt; otherwise within the digit map completion =
event.&nbsp; If buffering ceases</FONT>
<BR><FONT SIZE=3D2>&gt; due to buffering timer expiry, the contents of =
the digit buffer are</FONT>
<BR><FONT SIZE=3D2>&gt; discarded.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; If buffering was stopped by a new =
EventsDescriptor, then if that</FONT>
<BR><FONT SIZE=3D2>&gt; EventsDescriptor contains a new digit map =
completion event from the</FONT>
<BR><FONT SIZE=3D2>&gt; same package as the previous one, any buffered =
digits are processed</FONT>
<BR><FONT SIZE=3D2>&gt; against the digit map as described below.&nbsp; =
Buffered digits not</FONT>
<BR><FONT SIZE=3D2>&gt; consumed by the new digit map are handled as if =
they had were observed</FONT>
<BR><FONT SIZE=3D2>&gt; after that map completed.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; If instead the new EventsDescriptor enables the =
reporting of</FONT>
<BR><FONT SIZE=3D2>&gt; individual digit events, the entire set of =
buffered digits shall</FONT>
<BR><FONT SIZE=3D2>&gt; immediately be processed, the applicable events =
reported, and the</FONT>
<BR><FONT SIZE=3D2>&gt; buffer cleared.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Finally, if the new EventsDescriptor enables =
neither a digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event nor the reporting of =
individual digit events from the</FONT>
<BR><FONT SIZE=3D2>&gt; package concerned, the buffer contents are =
discarded and buffering is</FONT>
<BR><FONT SIZE=3D2>&gt; terminated.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; (All of the paragraphs following the second =
bullet are part of that</FONT>
<BR><FONT SIZE=3D2>&gt; bullet item.)</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 7.1.14.5:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;2. At each step, a timer is set =
to wait for the next event,</FONT>
<BR><FONT SIZE=3D2>&gt; based either on the default timing rules given =
above or on explicit</FONT>
<BR><FONT SIZE=3D2>&gt; timing specified in one or more alternative =
event sequences. If the</FONT>
<BR><FONT SIZE=3D2>&gt; timer expires and a member of the candidate set =
of alternatives is</FONT>
<BR><FONT SIZE=3D2>&gt; fully satisfied, a timeout completion with full =
match is reported.&nbsp; If</FONT>
<BR><FONT SIZE=3D2>&gt; the timer expires and part or none of any =
candidate alternative is</FONT>
<BR><FONT SIZE=3D2>&gt; satisfied, a timeout completion with partial =
match is reported.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;2. At each step, if buffered digits =
are available, the oldest one</FONT>
<BR><FONT SIZE=3D2>&gt; (with possible accompanying long digit (Z) =
qualifier) is removed from</FONT>
<BR><FONT SIZE=3D2>&gt; the buffer and processing moves to the next =
step as if the digit event</FONT>
<BR><FONT SIZE=3D2>&gt; had just been observed.&nbsp; Otherwise a timer =
is set to wait for the next</FONT>
<BR><FONT SIZE=3D2>&gt; event, based either on the default timing rules =
given above or on</FONT>
<BR><FONT SIZE=3D2>&gt; explicit timing specified in one or more =
alternative event sequences.</FONT>
<BR><FONT SIZE=3D2>&gt; If the timer expires and a member of the =
candidate set of alternatives</FONT>
<BR><FONT SIZE=3D2>&gt; is fully satisfied, a timeout completion with =
full match is reported.</FONT>
<BR><FONT SIZE=3D2>&gt; If the timer expires and part or none of any =
candidate alternative is</FONT>
<BR><FONT SIZE=3D2>&gt; satisfied, a timeout completion with partial =
match is reported.&nbsp; In</FONT>
<BR><FONT SIZE=3D2>&gt; either case, if the digit map completion event =
allows for detailed</FONT>
<BR><FONT SIZE=3D2>&gt; timeout reporting, the reported dial string =
will end with 'L' or 'S'</FONT>
<BR><FONT SIZE=3D2>&gt; as appropriate.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change (step 5): &quot;The event removed from =
the current dial string will</FONT>
<BR><FONT SIZE=3D2>&gt; then be reported as per the currently active =
event processing</FONT>
<BR><FONT SIZE=3D2>&gt; mechanisms.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;The event removed from the current =
dial string will then be</FONT>
<BR><FONT SIZE=3D2>&gt; reported as a separate event, buffered, or =
discarded according to the</FONT>
<BR><FONT SIZE=3D2>&gt; rules described in the previous section.&nbsp; =
This statement is qualified</FONT>
<BR><FONT SIZE=3D2>&gt; as follows:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; a) The digit map completion event may specify =
that the event be</FONT>
<BR><FONT SIZE=3D2>&gt; reported as a parameter of that event.&nbsp; =
This occurs independently of</FONT>
<BR><FONT SIZE=3D2>&gt; subsequent processing of the digit =
event.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; b) The digit map completion event may specify =
that the extra digit</FONT>
<BR><FONT SIZE=3D2>&gt; should be discarded.&nbsp; In this case, it is =
discarded immediately.&nbsp; Any</FONT>
<BR><FONT SIZE=3D2>&gt; buffering or other processing applies only to =
subsequent events.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Section 6.1.14.7:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;=B7 the events in the package =
containing the specified digit</FONT>
<BR><FONT SIZE=3D2>&gt; map completion event other than the completion =
event itself are not</FONT>
<BR><FONT SIZE=3D2>&gt; individually notified, and&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;=B7 the events in the package =
containing the specified digit map</FONT>
<BR><FONT SIZE=3D2>&gt; completion event other than the completion =
event itself are not</FONT>
<BR><FONT SIZE=3D2>&gt; individually notified and have no side-effects =
unless separately</FONT>
<BR><FONT SIZE=3D2>&gt; enabled, and&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change: &quot;=B7 an event that triggers a =
partial match completion event is</FONT>
<BR><FONT SIZE=3D2>&gt; not recognized and therefore has no side =
effects until reprocessed</FONT>
<BR><FONT SIZE=3D2>&gt; following the recognition of the digit map =
completion event.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: &quot;=B7 an event that triggers a partial =
match completion event is not</FONT>
<BR><FONT SIZE=3D2>&gt; recognized and therefore has no side effects =
unless and until</FONT>
<BR><FONT SIZE=3D2>&gt; reprocessed following the recognition of the =
digit map completion</FONT>
<BR><FONT SIZE=3D2>&gt; event.&nbsp; Similarly buffered digit events =
are not recognized and have no</FONT>
<BR><FONT SIZE=3D2>&gt; side effects until processed.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Annex C:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Change:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] =
digitMap</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To:</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
digitMapValue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
[&quot;T&quot; COLON Timer COMMA] [&quot;S&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; [&quot;L&quot; COLON Timer COMMA] =
[&quot;Z&quot; COLON Timer</FONT>
<BR><FONT SIZE=3D2>&gt; COMMA]</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; digitMap</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; =
Timer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; =3D 1*2DIGIT</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; ; Units are seconds for T, S, =
and L timers, and hundreds of</FONT>
<BR><FONT SIZE=3D2>&gt; milliseconds for Z timer.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; ; Thus T, S, and L range from =
1 to 99 seconds and Z from 100 ms to</FONT>
<BR><FONT SIZE=3D2>&gt; 9.9 s.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Kevin</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Christian Groves [<A =
HREF=3D"mailto:Christian.Groves@ericsson.com.au">mailto:Christian.Groves=
@ericsson.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, January 28, 2002 7:26 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: megaco ietf</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Megaco] [Fwd: Fwd: Uploaded files to =
Incoming]</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; G'Day all,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I have uploaded a number of H.248 editors' =
contributions and company</FONT>
<BR><FONT SIZE=3D2>&gt; contributions to the PICTEL website.</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://standard.pictel.com/ftp/avc-site/0202_Gen/" =
TARGET=3D"_blank">http://standard.pictel.com/ftp/avc-site/0202_Gen/</A><=
/FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; A list of the documents is below. The latest =
version of H.248 is among</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; them. Comments?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; -------- Original Message --------</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Fwd: Uploaded files to Incoming</FONT>
<BR><FONT SIZE=3D2>&gt; Date: Thu, 24 Jan 2002 16:27:59 +0900</FONT>
<BR><FONT SIZE=3D2>&gt; From: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Reply-To: OKUBO Sakae =
&lt;okubo@GITI.WASEDA.AC.JP&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; To: ITU-SG16@echo.jf.INTEL.COM</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Dear SG16 experts,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; They are now available at /0202_Gen of the =
avc-site.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; At 16:16 +1100 02/01/24, Christian Groves =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I have placed the following files in the =
incoming directory. Could</FONT>
<BR><FONT SIZE=3D2>&gt; you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;please move them to the Geneve =
directory?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;1. [DC-xxx_Annex_L_amm1] Proposed H.248 =
Annex L Amendment 1</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;2. [DC-xxx_Annex_M_1] Comments to H.248 =
Annex M.1 Audio Server</FONT>
<BR><FONT SIZE=3D2>&gt; Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;3. [DC-xxx_Annex_M_qac] H.248 Annex M.qac =
Quality Alert Ceasing</FONT>
<BR><FONT SIZE=3D2>&gt; Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;4. [DC-xxx_Annex_N] H.248 Annex N SDP H.248 =
Package Attribute</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;5. [DC-xxx_Imp_Guide] H.248 Implementors' =
Guide Additions</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;6. [DC-xxx_MuxDescription] Clarification of =
H.248 Mux Descriptor</FONT>
<BR><FONT SIZE=3D2>&gt; Usage</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;7. [DC-xxx_Nx64K] Addition of Nx64K Service =
to the H.248 Mutliplex</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;descriptor</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;8. [DC-xxx_Packages_Guide] Packages =
Guide</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;9. [DC-xxx_Profile_Pkg] Draft H.248 Annex =
M.profile Profile Package</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;10. [DC-xxx_H248v2] Draft H.248v2</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Best regards,</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; OKUBO Sakae</FONT>
<BR><FONT SIZE=3D2>&gt; =
*********************************************************</FONT>
<BR><FONT SIZE=3D2>&gt; Global Information and Telecommunication =
Institute (GITI)</FONT>
<BR><FONT SIZE=3D2>&gt; Waseda University</FONT>
<BR><FONT SIZE=3D2>&gt; 29-7 Waseda University Bldg.</FONT>
<BR><FONT SIZE=3D2>&gt; 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo</FONT>
<BR><FONT SIZE=3D2>&gt; 169-0051 Japan</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
e-mail: okubo@giti.waseda.ac.jp</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Tel: +81 3 3204 8194</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Fax: +81 3 5286 3832</FONT>
<BR><FONT SIZE=3D2>&gt; =
*********************************************************</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

<P><FONT SIZE=3D2>--</FONT>
</P>

<P><FONT =
SIZE=3D2>------------------------------------------------------------</F=
ONT>
<BR><FONT SIZE=3D2>Terry L =
Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <A =
HREF=3D"mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2>Tel:908.582.7013&nbsp;&nbsp; Fax:908.582.6729</FONT>
<BR><FONT SIZE=3D2>Lucent Technologies/INS/Voice Over IP Access =
Networks</FONT>
<BR><FONT SIZE=3D2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ =
07974</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://its.lucent.com/~tla" =
TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) <A =
HREF=3D"http://www.gti.net/tla" =
TARGET=3D"_blank">http://www.gti.net/tla</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A946.57239880--

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



From megaco-admin@ietf.org  Tue Jan 29 23:49:00 2002
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 XAA01468
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:49:00 -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 XAA20799;
	Tue, 29 Jan 2002 23:37:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA20763
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:37:19 -0500 (EST)
Received: from mailweb14.rediffmail.com ([203.199.83.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01269
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:37:14 -0500 (EST)
Received: (qmail 9864 invoked by uid 510); 30 Jan 2002 04:36:22 -0000
Date: 30 Jan 2002 04:36:22 -0000
Message-ID: <20020130043622.9863.qmail@mailweb14.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 30 Jan 2002 04:36:22 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: "Terry L Anderson" <tla@lucent.com>
Cc: "megaco ietf" <megaco@ietf.org>, "Kevin Boyle" <kboyle@nortelnetworks.com>
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA20764
Subject: [Megaco] Digit Map spec
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


Hi all

   What are the possible pattern of digitmaps allowed in digit map discriptor.. ? Does it support regular expression patterns. In the example [1-7]xxx is given. Like this what all patterns are possible.. ?

vdy 


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


From daemon@ns.ietf.org  Tue Jan 29 23:49:03 2002
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 XAA01484
	for <megaco-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:49:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA21086
	for megaco-archive@odin.ietf.org; Tue, 29 Jan 2002 23:49:05 -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 XAA20799;
	Tue, 29 Jan 2002 23:37:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA20763
	for <megaco@ns.ietf.org>; Tue, 29 Jan 2002 23:37:19 -0500 (EST)
Received: from mailweb14.rediffmail.com ([203.199.83.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01269
	for <megaco@ietf.org>; Tue, 29 Jan 2002 23:37:14 -0500 (EST)
Received: (qmail 9864 invoked by uid 510); 30 Jan 2002 04:36:22 -0000
Date: 30 Jan 2002 04:36:22 -0000
Message-ID: <20020130043622.9863.qmail@mailweb14.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 30 Jan 2002 04:36:22 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: "Terry L Anderson" <tla@lucent.com>
Cc: "megaco ietf" <megaco@ietf.org>, "Kevin Boyle" <kboyle@nortelnetworks.com>
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA20764
Subject: [Megaco] Digit Map spec
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


Hi all

   What are the possible pattern of digitmaps allowed in digit map discriptor.. ? Does it support regular expression patterns. In the example [1-7]xxx is given. Like this what all patterns are possible.. ?

vdy 


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



From megaco-admin@ietf.org  Wed Jan 30 01:04:41 2002
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 BAA02643
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 01:04:41 -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 AAA23610;
	Wed, 30 Jan 2002 00:49:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA23581
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 00:49:22 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02545
	for <megaco@ietf.org>; Wed, 30 Jan 2002 00:49:21 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0U5nBC03253;
	Wed, 30 Jan 2002 06:49:11 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0U5nBr6010005;
	Wed, 30 Jan 2002 07:49:11 +0200 (EET)
Message-ID: <3C578955.FB4057EE@lmf.ericsson.se>
Date: Wed, 30 Jan 2002 07:49:09 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Christian Groves'" <Christian.Groves@ericsson.com.au>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I think the proposal sounds good. However, wouldn't it be more clear if
stream ID 0 was default, instead of stream ID 1? Just a detail, but
still...

Regards,

Christer Holmberg
Ericsson Finland



Tom-PT Taylor wrote:
> 
> Darn: hit the wrong button again.
> 
> Anyway, if everyone sees it this way let's go for it.  Do we need text
> changes?
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Tuesday, January 29, 2002 10:22 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> Subject: Re: [Megaco] Query about streamID 0
> 
> G'Day
> 
> My understanding of the combinations are the following:
> 
> event (no stream) - detect an event on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> detection equipment. ie. DTMF detector on the audio stream/s.
> event (stream ID 0) - as above
> event (stream ID x) - detect the event only on the particular streamID x
> 
> signal (no stream) - play the signal on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> playout equipment. Play a video on the video stream.
> signal (stream ID 0) - as above
> signal (stream ID x) - the signal only on the particular streamID x
> 
> Default streamID=1 if you leave the stream descriptor as just specify
> local and remote.
> 
> Now this is all rather acedemic if the termination only ever has one
> stream.
> I can't see the problem. What am I missing?
> 
> Regards, Christian
> 
> Tom-PT Taylor wrote:
> >
> > Your proposal that the default streamId (0) means "all active streams" is
> a
> > workable one for events, especially if the actual stream on which the
> signal
> > occurred is reported in the Notify.  I suspect signals are a bit more
> > problematic -- you only want a signal to go out on one stream, usually.
> >
> > I'm still troubled by the implications of assuming that you can't detect
> > events on a stream not specifically defined at a given termination.  I'm
> > mainly worried about the NULL context.  The simplest way around that
> concern
> > is to assume that the media properties of physical terminations are
> > pre-provisioned.  In fact, people must be making that asumption now --
> > otherwise there would have been a lot more interest in my draft on SDP
> > attributes for TDM.  I intend to revive that draft shortly, by the way.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Monday, January 28, 2002 8:36 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > My comments embedded.....
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > You've opened up a good discussion.
> >
> > 1. You are right about streams also being bound to terminations.  Aside
> from
> > being able to define streams when the termination is in the NULL context,
> we
> > have the provision that a termination retains its current streams when it
> is
> > moved from one context to another.
> >
> > 2. I differ slightly on the interpretation of streams versus actual
> enabling
> > of flows, but this is at an abstract level that I don't think makes any
> > difference in behaviour.  My interpretation is that as soon as a stream is
> > created in a context, it introduces the potential of bi-directional
> exchange
> > of media between the context and each termination in it.  Of course, to
> have
> > an actual flow in each direction, you need the conditions you've stated:
> > Local and Remote defined on at least two terminations and sendRecv set on
> > both.
> >
> > The real issue is whether a termination can detect events and send signals
> > on a stream not explicitly defined at that termination.  I think this is a
> > matter of convention -- we have to decide one way or the other.  I'll
> point
> > out that it has implications for detection of DTMF events in the NULL
> > context.
> > <KN> I feel as per the convention and to some extent simple logic it
> > would be appropriate to allow terminations to detect events and signals
> > on only those streams which are explicitly defined on them. More so,
> because
> > in cases where there are multiple streams on multiple terminations
> > Eg:
> > A context with 4 terminations T1, T2, T3....
> > Streams 1 and 2 on T1,3 and 2 on T3.
> > T2 has currently no explicit stream defined on it.
> >
> >           -------------------
> >           |              |
> >      T1----------1         -------T2
> >           |  |            |
> >           |  |--2_       |
> >           |      |       |
> >           |      |       |
> >           |      |       |
> >           |      |    3--------T3
> >           |      |       | |
> >           |       |____2--| |
> >           |              |
> >           -------------------
> > It would be questionable to expect the following combinations:
> > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > -    T1 detect events or apply signals on stream 3.
> > -    T3 detect events or apply signals on stream 1.
> > At the current moment these terminations are completely oblivious of the
> > stream IDs refered.
> >
> > 3. I think I've made the point that H.248v1 requires that most of the
> events
> > and signals we have already defined must be applied to a non-zero stream.
> > Hence requiring that packages indicate which ones apply to stream 0 is not
> a
> > change in the protocol, just a clarification.
> >
> > I do have a couple of alternatives which indeed would be changes to the
> > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> >
> >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > event or signal, or
> >  (b) If only one stream is defined on the specific termination, an
> > unspecified streamId selects that stream.
> > <KN> I have an opinion.....How does MGC tell MG to detect events
> > on all active streams on a termination. Does MGC have to repeat event IDs
> > in the event descriptor with all active stream IDs as parameters. Protocol
> > does not introduce any concept of stream ID as "*"(ALL).
> > >From the current text, the stream ID 0 seems to be solving this problem.
> > Stream ID 0 is the default stream on all terminations,i.e., does not need
> to
> > be created explicitly through media descriptor (valid).
> > If event descriptor contains stream ID 0, "it does not refer to any
> specific
> > stream"(valid) but does refer to the termination as a whole.
> > The inference is that detect events on all streams (currently active on
> > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > nonstream-specific terminations like NAS). If the event is detected on any
> > stream, report the same to MGC with the specific stream ID.
> > A similar interpretation can also be made for signals.
> > And, the default stream ID remains 0 for events/ signals, but 1 for
> > media descriptor.
> >
> > Actually, I think people are going to have to bite the bullet and start
> > specifying streamIds eventually if they don't do it now.  Choosing
> > alternative (b) would buy a bit of time.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Thursday, January 24, 2002 5:49 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > I would like to add more to your comments about streams being context
> > properties.
> >
> > Streams are as good properties of the terminations too....
> > -    A stream can be created on a termination in the Null Context.
> >      (almost in all call flows including those in the RFC 3015 stream
> > descriptor
> >      or the default stream 1 is sent by the MGC in MODIFY command in the
> >      Null context).
> > -    To create a bi-directional stream, we need to send stream descriptor
> >      with (at the least mode=sendrecv) for both the terminations in the
> > context.
> >      The bi-directional stream cannot be created by just refering it in
> one
> >      termination.
> >
> > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > stream=1 (something similar to a unidirectional media flow) by specifying
> > stream descriptor for termination T1. At this point it would be incorrect
> > to assume that termination T2 can detect events or apply signals on the
> > stream
> > 1.
> > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > totally
> > oblivious of stream 1).
> > To detect events or signals on the stream at T2, we need to first make T2
> > aware
> > of the stream.
> >
> > Although, it would be a good idea to specify in package definitions about
> > which event/ signals etc. would apply on streamID=0, this would amount to
> > changing
> > the protocol....are you considering it for version2.
> >
> > Please comment....
> >
> > Thanks & Regards,
> > -Kapil Nayar
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.  See new comments [PTT2] below.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Wednesday, January 23, 2002 8:55 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > my comments embedded.
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> >
> > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > cc:
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Tuesday, January 22, 2002 8:54 AM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Query about streamID 0
> >
> > Hi Tom & list,
> >
> > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> mentions:
> >
> > "The default streamID is 0, indicating that the event to be detected is
> not
> > related to a particular media stream."
> >
> > Does the "streamID 0" refer to the complete termination (which means all
> the
> > active streams on the termination) ?
> >
> > [PTT] No.  It really means as it says, that the event or signal is not
> > associated with any specific stream.  An example is an electrical signal
> > such as off-hook.
> > [KN] Does that mean that stream 0 is possible for only physical
> > terminations,
> > since electrical signals are more appropriate for physical terminations.
> > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > relate to specific streams.  Electrical signals were just an example.  I
> > suspect I could find a good example in one of my NAS packages of something
> > more abstract, but I won't take the time.  Just accept that we don't want
> to
> > foreclose the possibility of using this on ephemerals.
> >
> > And, if some event is required to be detected on the ephemeral
> termination,
> > the event descriptor should clearly identify which stream it is required
> on.
> > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > without
> > stream ID parameter since that defaults to stream ID 0, which may not be
> > applicable).
> > [PTT2] That has to be thought through for all terminations.
> > *** IG issue: It does strike me that you can know in advance (by
> definition
> > of the event or signal) whether streamId=0 will apply.  We should
> therefore
> > make it requirement to specify this in package definitions.
> >
> > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > associated with an audio stream.  (But I bet nobody has bothered to
> specify
> > stream 1 for DTMF events when they are using a default streamId for audio.
> > They should!)
> > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > descriptor,
> > MGC should have already created the stream 1 thru' the media descriptor
> > in a previous command?
> > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > descriptor, but just specify Local, Remote, and LocalControl.
> > *** IG issue: would it make more sense to have streamId=0 as the default
> for
> > signals and events, or have streamId=1 as the default?
> >
> > A related doubt is...if an event descriptor refers
> > to a stream ID which is not previously created by the MGC, MG should
> > return an error.
> > [PTT2] I'm not sure.  Remember that streamIds are really a context
> property.
> > If a given streamId is supported somewhere in the context, then referring
> to
> > that streamId at a given termination implies that the termination also
> > supports it.  That means it could detect events or send signals on the
> > stream even if it doesn't know how to handle the media flows on that
> stream.
> > I suppose if this is the first mention of the streamId in the context, it
> > might be appropriate to reject the command.
> > ***IG issue: The implication is that within any command, Stream
> Descriptors
> > for new streams MUST appear before Signals and Events descriptors
> referring
> > to those StreamIds.
> >
> > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > descriptor, event descriptor, signal descriptor ?
> >
> > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > consistent with the meaning of that streamId for events and signals.  We
> > should have a note to the effect that streamId=0 is reserved in sections
> > 7.1.4 (for thoroughness) and 7.1.6.
> >
> > You can specify streamId=0 in a signals or events descriptor, but that's
> the
> > same as leaving it unspecified.
> >
> > Please reply back...
> >
> > Thanks,
> > Kapil Nayar
> >
> > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> Limited
> > (HSS) and is intended solely for the use of the individual  to whom it is
> > addressed. It may contain  privileged or confidential information  and
> > should
> > not be circulated or used for any purpose other than for what it is
> > intended.If
> > you have received this message in error, please notify the originator
> > immediately. If you are not the intended recipient, you are notified that
> > you
> > are strictly prohibited from using, copying, altering, or disclosing the
> > contents of this message. HSS accepts no responsibility for loss or damage
> > arising from the use of the information transimitted by this email
> including
> > damage from virus."
> >
> > _______________________________________________
> > 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

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


From daemon@ns.ietf.org  Wed Jan 30 01:04:41 2002
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 BAA02650
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 01:04:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA24308
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 01:04:41 -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 AAA23610;
	Wed, 30 Jan 2002 00:49:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA23581
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 00:49:22 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02545
	for <megaco@ietf.org>; Wed, 30 Jan 2002 00:49:21 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0U5nBC03253;
	Wed, 30 Jan 2002 06:49:11 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0U5nBr6010005;
	Wed, 30 Jan 2002 07:49:11 +0200 (EET)
Message-ID: <3C578955.FB4057EE@lmf.ericsson.se>
Date: Wed, 30 Jan 2002 07:49:09 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'Christian Groves'" <Christian.Groves@ericsson.com.au>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

I think the proposal sounds good. However, wouldn't it be more clear if
stream ID 0 was default, instead of stream ID 1? Just a detail, but
still...

Regards,

Christer Holmberg
Ericsson Finland



Tom-PT Taylor wrote:
> 
> Darn: hit the wrong button again.
> 
> Anyway, if everyone sees it this way let's go for it.  Do we need text
> changes?
> 
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> Sent: Tuesday, January 29, 2002 10:22 PM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> Subject: Re: [Megaco] Query about streamID 0
> 
> G'Day
> 
> My understanding of the combinations are the following:
> 
> event (no stream) - detect an event on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> detection equipment. ie. DTMF detector on the audio stream/s.
> event (stream ID 0) - as above
> event (stream ID x) - detect the event only on the particular streamID x
> 
> signal (no stream) - play the signal on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> playout equipment. Play a video on the video stream.
> signal (stream ID 0) - as above
> signal (stream ID x) - the signal only on the particular streamID x
> 
> Default streamID=1 if you leave the stream descriptor as just specify
> local and remote.
> 
> Now this is all rather acedemic if the termination only ever has one
> stream.
> I can't see the problem. What am I missing?
> 
> Regards, Christian
> 
> Tom-PT Taylor wrote:
> >
> > Your proposal that the default streamId (0) means "all active streams" is
> a
> > workable one for events, especially if the actual stream on which the
> signal
> > occurred is reported in the Notify.  I suspect signals are a bit more
> > problematic -- you only want a signal to go out on one stream, usually.
> >
> > I'm still troubled by the implications of assuming that you can't detect
> > events on a stream not specifically defined at a given termination.  I'm
> > mainly worried about the NULL context.  The simplest way around that
> concern
> > is to assume that the media properties of physical terminations are
> > pre-provisioned.  In fact, people must be making that asumption now --
> > otherwise there would have been a lot more interest in my draft on SDP
> > attributes for TDM.  I intend to revive that draft shortly, by the way.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Monday, January 28, 2002 8:36 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > My comments embedded.....
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > You've opened up a good discussion.
> >
> > 1. You are right about streams also being bound to terminations.  Aside
> from
> > being able to define streams when the termination is in the NULL context,
> we
> > have the provision that a termination retains its current streams when it
> is
> > moved from one context to another.
> >
> > 2. I differ slightly on the interpretation of streams versus actual
> enabling
> > of flows, but this is at an abstract level that I don't think makes any
> > difference in behaviour.  My interpretation is that as soon as a stream is
> > created in a context, it introduces the potential of bi-directional
> exchange
> > of media between the context and each termination in it.  Of course, to
> have
> > an actual flow in each direction, you need the conditions you've stated:
> > Local and Remote defined on at least two terminations and sendRecv set on
> > both.
> >
> > The real issue is whether a termination can detect events and send signals
> > on a stream not explicitly defined at that termination.  I think this is a
> > matter of convention -- we have to decide one way or the other.  I'll
> point
> > out that it has implications for detection of DTMF events in the NULL
> > context.
> > <KN> I feel as per the convention and to some extent simple logic it
> > would be appropriate to allow terminations to detect events and signals
> > on only those streams which are explicitly defined on them. More so,
> because
> > in cases where there are multiple streams on multiple terminations
> > Eg:
> > A context with 4 terminations T1, T2, T3....
> > Streams 1 and 2 on T1,3 and 2 on T3.
> > T2 has currently no explicit stream defined on it.
> >
> >           -------------------
> >           |              |
> >      T1----------1         -------T2
> >           |  |            |
> >           |  |--2_       |
> >           |      |       |
> >           |      |       |
> >           |      |       |
> >           |      |    3--------T3
> >           |      |       | |
> >           |       |____2--| |
> >           |              |
> >           -------------------
> > It would be questionable to expect the following combinations:
> > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > -    T1 detect events or apply signals on stream 3.
> > -    T3 detect events or apply signals on stream 1.
> > At the current moment these terminations are completely oblivious of the
> > stream IDs refered.
> >
> > 3. I think I've made the point that H.248v1 requires that most of the
> events
> > and signals we have already defined must be applied to a non-zero stream.
> > Hence requiring that packages indicate which ones apply to stream 0 is not
> a
> > change in the protocol, just a clarification.
> >
> > I do have a couple of alternatives which indeed would be changes to the
> > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> >
> >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > event or signal, or
> >  (b) If only one stream is defined on the specific termination, an
> > unspecified streamId selects that stream.
> > <KN> I have an opinion.....How does MGC tell MG to detect events
> > on all active streams on a termination. Does MGC have to repeat event IDs
> > in the event descriptor with all active stream IDs as parameters. Protocol
> > does not introduce any concept of stream ID as "*"(ALL).
> > >From the current text, the stream ID 0 seems to be solving this problem.
> > Stream ID 0 is the default stream on all terminations,i.e., does not need
> to
> > be created explicitly through media descriptor (valid).
> > If event descriptor contains stream ID 0, "it does not refer to any
> specific
> > stream"(valid) but does refer to the termination as a whole.
> > The inference is that detect events on all streams (currently active on
> > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > nonstream-specific terminations like NAS). If the event is detected on any
> > stream, report the same to MGC with the specific stream ID.
> > A similar interpretation can also be made for signals.
> > And, the default stream ID remains 0 for events/ signals, but 1 for
> > media descriptor.
> >
> > Actually, I think people are going to have to bite the bullet and start
> > specifying streamIds eventually if they don't do it now.  Choosing
> > alternative (b) would buy a bit of time.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Thursday, January 24, 2002 5:49 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > I would like to add more to your comments about streams being context
> > properties.
> >
> > Streams are as good properties of the terminations too....
> > -    A stream can be created on a termination in the Null Context.
> >      (almost in all call flows including those in the RFC 3015 stream
> > descriptor
> >      or the default stream 1 is sent by the MGC in MODIFY command in the
> >      Null context).
> > -    To create a bi-directional stream, we need to send stream descriptor
> >      with (at the least mode=sendrecv) for both the terminations in the
> > context.
> >      The bi-directional stream cannot be created by just refering it in
> one
> >      termination.
> >
> > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > stream=1 (something similar to a unidirectional media flow) by specifying
> > stream descriptor for termination T1. At this point it would be incorrect
> > to assume that termination T2 can detect events or apply signals on the
> > stream
> > 1.
> > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > totally
> > oblivious of stream 1).
> > To detect events or signals on the stream at T2, we need to first make T2
> > aware
> > of the stream.
> >
> > Although, it would be a good idea to specify in package definitions about
> > which event/ signals etc. would apply on streamID=0, this would amount to
> > changing
> > the protocol....are you considering it for version2.
> >
> > Please comment....
> >
> > Thanks & Regards,
> > -Kapil Nayar
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.  See new comments [PTT2] below.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Wednesday, January 23, 2002 8:55 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > my comments embedded.
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> >
> > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > cc:
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Tuesday, January 22, 2002 8:54 AM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Query about streamID 0
> >
> > Hi Tom & list,
> >
> > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> mentions:
> >
> > "The default streamID is 0, indicating that the event to be detected is
> not
> > related to a particular media stream."
> >
> > Does the "streamID 0" refer to the complete termination (which means all
> the
> > active streams on the termination) ?
> >
> > [PTT] No.  It really means as it says, that the event or signal is not
> > associated with any specific stream.  An example is an electrical signal
> > such as off-hook.
> > [KN] Does that mean that stream 0 is possible for only physical
> > terminations,
> > since electrical signals are more appropriate for physical terminations.
> > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > relate to specific streams.  Electrical signals were just an example.  I
> > suspect I could find a good example in one of my NAS packages of something
> > more abstract, but I won't take the time.  Just accept that we don't want
> to
> > foreclose the possibility of using this on ephemerals.
> >
> > And, if some event is required to be detected on the ephemeral
> termination,
> > the event descriptor should clearly identify which stream it is required
> on.
> > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > without
> > stream ID parameter since that defaults to stream ID 0, which may not be
> > applicable).
> > [PTT2] That has to be thought through for all terminations.
> > *** IG issue: It does strike me that you can know in advance (by
> definition
> > of the event or signal) whether streamId=0 will apply.  We should
> therefore
> > make it requirement to specify this in package definitions.
> >
> > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > associated with an audio stream.  (But I bet nobody has bothered to
> specify
> > stream 1 for DTMF events when they are using a default streamId for audio.
> > They should!)
> > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > descriptor,
> > MGC should have already created the stream 1 thru' the media descriptor
> > in a previous command?
> > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > descriptor, but just specify Local, Remote, and LocalControl.
> > *** IG issue: would it make more sense to have streamId=0 as the default
> for
> > signals and events, or have streamId=1 as the default?
> >
> > A related doubt is...if an event descriptor refers
> > to a stream ID which is not previously created by the MGC, MG should
> > return an error.
> > [PTT2] I'm not sure.  Remember that streamIds are really a context
> property.
> > If a given streamId is supported somewhere in the context, then referring
> to
> > that streamId at a given termination implies that the termination also
> > supports it.  That means it could detect events or send signals on the
> > stream even if it doesn't know how to handle the media flows on that
> stream.
> > I suppose if this is the first mention of the streamId in the context, it
> > might be appropriate to reject the command.
> > ***IG issue: The implication is that within any command, Stream
> Descriptors
> > for new streams MUST appear before Signals and Events descriptors
> referring
> > to those StreamIds.
> >
> > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > descriptor, event descriptor, signal descriptor ?
> >
> > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > consistent with the meaning of that streamId for events and signals.  We
> > should have a note to the effect that streamId=0 is reserved in sections
> > 7.1.4 (for thoroughness) and 7.1.6.
> >
> > You can specify streamId=0 in a signals or events descriptor, but that's
> the
> > same as leaving it unspecified.
> >
> > Please reply back...
> >
> > Thanks,
> > Kapil Nayar
> >
> > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> Limited
> > (HSS) and is intended solely for the use of the individual  to whom it is
> > addressed. It may contain  privileged or confidential information  and
> > should
> > not be circulated or used for any purpose other than for what it is
> > intended.If
> > you have received this message in error, please notify the originator
> > immediately. If you are not the intended recipient, you are notified that
> > you
> > are strictly prohibited from using, copying, altering, or disclosing the
> > contents of this message. HSS accepts no responsibility for loss or damage
> > arising from the use of the information transimitted by this email
> including
> > damage from virus."
> >
> > _______________________________________________
> > 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

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



From megaco-admin@ietf.org  Wed Jan 30 02:18:55 2002
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 CAA11586
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 02:18:55 -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 CAA05995;
	Wed, 30 Jan 2002 02:06:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA05964
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 02:06:26 -0500 (EST)
Received: from web12604.mail.yahoo.com (web12604.mail.yahoo.com [216.136.173.227])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA11415
	for <megaco@ietf.org>; Wed, 30 Jan 2002 02:06:25 -0500 (EST)
Message-ID: <20020130070626.43019.qmail@web12604.mail.yahoo.com>
Received: from [202.92.113.241] by web12604.mail.yahoo.com via HTTP; Tue, 29 Jan 2002 23:06:26 PST
Date: Tue, 29 Jan 2002 23:06:26 -0800 (PST)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt
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

Hi,

I am new to this list, sorry for asking faq questions:

Will the drft-ietf-megaco-h248v2-00.txt replace
rfc3015? What is the current status of the
drft-ietf-megaco-h248v2-00.txt?

Thank you in advance.


__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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


From daemon@ns.ietf.org  Wed Jan 30 02:18:55 2002
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 CAA11595
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 02:18:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA06395
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 02:18:56 -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 CAA05995;
	Wed, 30 Jan 2002 02:06:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA05964
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 02:06:26 -0500 (EST)
Received: from web12604.mail.yahoo.com (web12604.mail.yahoo.com [216.136.173.227])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA11415
	for <megaco@ietf.org>; Wed, 30 Jan 2002 02:06:25 -0500 (EST)
Message-ID: <20020130070626.43019.qmail@web12604.mail.yahoo.com>
Received: from [202.92.113.241] by web12604.mail.yahoo.com via HTTP; Tue, 29 Jan 2002 23:06:26 PST
Date: Tue, 29 Jan 2002 23:06:26 -0800 (PST)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt
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

Hi,

I am new to this list, sorry for asking faq questions:

Will the drft-ietf-megaco-h248v2-00.txt replace
rfc3015? What is the current status of the
drft-ietf-megaco-h248v2-00.txt?

Thank you in advance.


__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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



From megaco-admin@ietf.org  Wed Jan 30 03:05:20 2002
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 DAA12198
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 03:05:20 -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 CAA08467;
	Wed, 30 Jan 2002 02:59:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA08432
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 02:59:04 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12067
	for <megaco@ietf.org>; Wed, 30 Jan 2002 02:58:56 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0U7vM910262
	for <megaco@ietf.org>; Wed, 30 Jan 2002 13:27:24 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQQRGX01.PRT for <megaco@ietf.org>; Wed, 30 Jan 2002
          13:28:09 +0530 
Message-ID: <0ad301c1a964$338d3340$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: <megaco@ietf.org>
Date: Wed, 30 Jan 2002 13:30:36 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [Megaco] Doubt on package extension
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0AD0_01C1A992.4D1D9BF0"

------=_NextPart_000_0AD0_01C1A992.4D1D9BF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi ,

DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg , suppose i want to play d0 follwed by call  waiting tone , which of =
the foll apply .=20

A - tonegen/playtone(toneid list=3D d0,cw )=20
B -dtmfgen/playtone(toneid list=3D d0 )  followed by  =
callprogtonegen/playtone(toneid list=3D cw )
C -dtmfgen/d0 followed by callprogtonegen/cw=20


Reg
Usha


------=_NextPart_000_0AD0_01C1A992.4D1D9BF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Hi ,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>DTMF Gen and Call =
ProgressToneGen pkg=20
both extend tone gen package .</FONT><FONT face=3DArial color=3D#008080=20
size=3D2>&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>So for a =
termination&nbsp;that=20
supports ToneGen, DTMFGen and Call ProgToneGen Pkg , suppose i want to=20
play&nbsp;d0&nbsp;follwed by call &nbsp;waiting tone , which of the foll =
apply .=20
</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial color=3D#008080=20
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>A - =
tonegen/playtone(toneid list=3D=20
d0,cw ) </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>B =
-dtmfgen/playtone(toneid list=3D d0=20
)&nbsp; followed by&nbsp;&nbsp;callprogtonegen/playtone(toneid list=3D =
cw=20
)</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>C -dtmfgen/d0 followed =
by=20
callprogtonegen/cw </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial color=3D#008080=20
size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Reg</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Usha</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0AD0_01C1A992.4D1D9BF0--



------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8--


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


From daemon@ns.ietf.org  Wed Jan 30 03:05:22 2002
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 DAA12212
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 03:05:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA09199
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 03:05:22 -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 CAA08467;
	Wed, 30 Jan 2002 02:59:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA08432
	for <megaco@ns.ietf.org>; Wed, 30 Jan 2002 02:59:04 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12067
	for <megaco@ietf.org>; Wed, 30 Jan 2002 02:58:56 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0U7vM910262
	for <megaco@ietf.org>; Wed, 30 Jan 2002 13:27:24 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQQRGX01.PRT for <megaco@ietf.org>; Wed, 30 Jan 2002
          13:28:09 +0530 
Message-ID: <0ad301c1a964$338d3340$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: <megaco@ietf.org>
Date: Wed, 30 Jan 2002 13:30:36 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [Megaco] Doubt on package extension
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0AD0_01C1A992.4D1D9BF0"

------=_NextPart_000_0AD0_01C1A992.4D1D9BF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi ,

DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg , suppose i want to play d0 follwed by call  waiting tone , which of =
the foll apply .=20

A - tonegen/playtone(toneid list=3D d0,cw )=20
B -dtmfgen/playtone(toneid list=3D d0 )  followed by  =
callprogtonegen/playtone(toneid list=3D cw )
C -dtmfgen/d0 followed by callprogtonegen/cw=20


Reg
Usha


------=_NextPart_000_0AD0_01C1A992.4D1D9BF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Hi ,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>DTMF Gen and Call =
ProgressToneGen pkg=20
both extend tone gen package .</FONT><FONT face=3DArial color=3D#008080=20
size=3D2>&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>So for a =
termination&nbsp;that=20
supports ToneGen, DTMFGen and Call ProgToneGen Pkg , suppose i want to=20
play&nbsp;d0&nbsp;follwed by call &nbsp;waiting tone , which of the foll =
apply .=20
</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial color=3D#008080=20
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>A - =
tonegen/playtone(toneid list=3D=20
d0,cw ) </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>B =
-dtmfgen/playtone(toneid list=3D d0=20
)&nbsp; followed by&nbsp;&nbsp;callprogtonegen/playtone(toneid list=3D =
cw=20
)</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>C -dtmfgen/d0 followed =
by=20
callprogtonegen/cw </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial color=3D#008080=20
size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Reg</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Usha</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0AD0_01C1A992.4D1D9BF0--



------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-14e16077-1551-11d6-a941-00b0d0d06be8--


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



From megaco-admin@ietf.org  Wed Jan 30 04:02:26 2002
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 EAA12827
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:02:26 -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 DAA11364;
	Wed, 30 Jan 2002 03:53:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11334
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 03:53:14 -0500 (EST)
Received: from cvis21.Marconicomms.com (cvis21.marconicomms.com [195.99.244.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12687
	for <megaco@ietf.org>; Wed, 30 Jan 2002 03:53:12 -0500 (EST)
Received: from cvis06.marconicomms.com (unverified) by cvis21.Marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f435dc58c3012b45@cvis21.Marconicomms.com>;
 Wed, 30 Jan 2002 08:52:35 +0000
Received: from cvdgwy01.uk.marconicomms.com by cvis06.marconicomms.com with ESMTP
 (8.10.2+Sun/cvms-34) id g0U8qfN02019; Wed, 30 Jan 2002 08:52:41 GMT
Subject: RE: [Megaco] Query about local control descriptor properties
To: taylor@nortelnetworks.com
Cc: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
From: "Wayne Cutler" <Wayne.Cutler@marconi.com>
Date: Wed, 30 Jan 2002 08:52:38 +0000
Message-ID: <OF520AF66E.2A1CE275-ON80256B50.005A2611@uk.marconicomms.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.8 |June 18, 2001) at
 30/01/2002 08:52:36
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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 Taylor wrote:-
>I don't quite see Wayne's point on the Signals and Events descriptors.  In
>both cases, the semantics of the situation require the repetition of all
of
>the signals/events you want to keep.  You also need at least the
KeepActive
>parameter where it applies to signals.  Are you saying, Wayne, that once
an
>event or signal is specified, then if it is retained in replacement
>descriptors it is unnecessary to respecify all the parameters that went
>along with it the first time?  I could live with that as an IG
>clarification.  Other views?

On second thoughts, I think you're right and the MGC would require to
always explicitly change/repeat Events & Signals. So, my comment applies
only to Properties. Having raised the comment against Properties, I then
incorrectly applied it to Events/Signals
to common the rules up across the different descriptors.

Wayne.





------------
This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.

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


From daemon@optimus.ietf.org  Wed Jan 30 04:02:26 2002
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 EAA12836
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:02:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA12076
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 04:02:27 -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 DAA11364;
	Wed, 30 Jan 2002 03:53:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11334
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 03:53:14 -0500 (EST)
Received: from cvis21.Marconicomms.com (cvis21.marconicomms.com [195.99.244.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12687
	for <megaco@ietf.org>; Wed, 30 Jan 2002 03:53:12 -0500 (EST)
Received: from cvis06.marconicomms.com (unverified) by cvis21.Marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f435dc58c3012b45@cvis21.Marconicomms.com>;
 Wed, 30 Jan 2002 08:52:35 +0000
Received: from cvdgwy01.uk.marconicomms.com by cvis06.marconicomms.com with ESMTP
 (8.10.2+Sun/cvms-34) id g0U8qfN02019; Wed, 30 Jan 2002 08:52:41 GMT
Subject: RE: [Megaco] Query about local control descriptor properties
To: taylor@nortelnetworks.com
Cc: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
From: "Wayne Cutler" <Wayne.Cutler@marconi.com>
Date: Wed, 30 Jan 2002 08:52:38 +0000
Message-ID: <OF520AF66E.2A1CE275-ON80256B50.005A2611@uk.marconicomms.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(Release 5.0.8 |June 18, 2001) at
 30/01/2002 08:52:36
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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 Taylor wrote:-
>I don't quite see Wayne's point on the Signals and Events descriptors.  In
>both cases, the semantics of the situation require the repetition of all
of
>the signals/events you want to keep.  You also need at least the
KeepActive
>parameter where it applies to signals.  Are you saying, Wayne, that once
an
>event or signal is specified, then if it is retained in replacement
>descriptors it is unnecessary to respecify all the parameters that went
>along with it the first time?  I could live with that as an IG
>clarification.  Other views?

On second thoughts, I think you're right and the MGC would require to
always explicitly change/repeat Events & Signals. So, my comment applies
only to Properties. Having raised the comment against Properties, I then
incorrectly applied it to Events/Signals
to common the rules up across the different descriptors.

Wayne.





------------
This e-mail and any attachments are confidential.  If you are not the intended recipient, please notify us immediately by reply e-mail and then delete this message from your system. Do not copy this e-mail or any attachments, use the contents for any purpose, or disclose the contents to any other person: to do so could be a breach of confidence.

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



From megaco-admin@ietf.org  Wed Jan 30 04:47:39 2002
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 EAA13350
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:47:39 -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 EAA13566;
	Wed, 30 Jan 2002 04:36:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13536
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 04:36:00 -0500 (EST)
Received: from mailFA2.rediffmail.com ([202.54.124.147])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA13236
	for <megaco@ietf.org>; Wed, 30 Jan 2002 04:35:53 -0500 (EST)
Received: (qmail 21933 invoked by uid 510); 30 Jan 2002 09:37:23 -0000
Date: 30 Jan 2002 09:37:23 -0000
Message-ID: <20020130093723.21932.qmail@mailFA2.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 30 Jan 2002 09:37:23 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA13537
Subject: [Megaco] QRY about the failed command
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


Hi all

  In RFC, page number 61 it says that

 "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."

  This statement is some what confusing. What I understand is even if a non optional 
command fails in an action, the action will be cancelled and the next action will be taken 
for processing and the commands in that action will be processed.. is that right .. ?

vdy
   


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


From daemon@optimus.ietf.org  Wed Jan 30 04:47:40 2002
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 EAA13359
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:47:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA13898
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 04:47:41 -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 EAA13566;
	Wed, 30 Jan 2002 04:36:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13536
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 04:36:00 -0500 (EST)
Received: from mailFA2.rediffmail.com ([202.54.124.147])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA13236
	for <megaco@ietf.org>; Wed, 30 Jan 2002 04:35:53 -0500 (EST)
Received: (qmail 21933 invoked by uid 510); 30 Jan 2002 09:37:23 -0000
Date: 30 Jan 2002 09:37:23 -0000
Message-ID: <20020130093723.21932.qmail@mailFA2.rediffmail.com>
Received: from unknown (63.118.187.193) by rediffmail.com via HTTP; 30 Jan 2002 09:37:23 -0000
MIME-Version: 1.0
From: "vidya  g" <vdy73@rediffmail.com>
Reply-To: "vidya  g" <vdy73@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA13537
Subject: [Megaco] QRY about the failed command
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


Hi all

  In RFC, page number 61 it says that

 "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."

  This statement is some what confusing. What I understand is even if a non optional 
command fails in an action, the action will be cancelled and the next action will be taken 
for processing and the commands in that action will be processed.. is that right .. ?

vdy
   


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



From megaco-admin@ietf.org  Wed Jan 30 09:20:22 2002
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 JAA19754
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:20:22 -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 JAA27507;
	Wed, 30 Jan 2002 09:04:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27476
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:04:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18890
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:04:13 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE3e802032;
	Wed, 30 Jan 2002 09:03:40 -0500 (EST)
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 g0UE3ct26878;
	Wed, 30 Jan 2002 09:03:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA46SS>; Wed, 30 Jan 2002 09:03:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt
Date: Wed, 30 Jan 2002 09:03:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A996.EA8221F0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A996.EA8221F0
Content-Type: text/plain;
	charset="iso-8859-1"

We work together closely with ITU-T Study Group 16.  All going well, they
will approve H.248v2 in the coming two weeks.  There will undoubtedly be
changes from what I recorded in draft-ietf-megaco-h248v2-00.txt, so I'll
up-version that document.  Then we'll put it through Last Call so we can
turn it into an RFC obsoleting RFC 3015.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Wednesday, January 30, 2002 2:06 AM
To: megaco@ietf.org
Subject: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt


Hi,

I am new to this list, sorry for asking faq questions:

Will the drft-ietf-megaco-h248v2-00.txt replace
rfc3015? What is the current status of the
drft-ietf-megaco-h248v2-00.txt?

Thank you in advance.


__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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

------_=_NextPart_001_01C1A996.EA8221F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>We work together closely with ITU-T Study Group =
16.&nbsp; All going well, they will approve H.248v2 in the coming two =
weeks.&nbsp; There will undoubtedly be changes from what I recorded in =
draft-ietf-megaco-h248v2-00.txt, so I'll up-version that =
document.&nbsp; Then we'll put it through Last Call so we can turn it =
into an RFC obsoleting RFC 3015.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Y Hu [<A =
HREF=3D"mailto:yh86us@yahoo.com">mailto:yh86us@yahoo.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 30, 2002 2:06 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Re: =
drft-ietf-megaco-h248v2-00.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>I am new to this list, sorry for asking faq =
questions:</FONT>
</P>

<P><FONT SIZE=3D2>Will the drft-ietf-megaco-h248v2-00.txt =
replace</FONT>
<BR><FONT SIZE=3D2>rfc3015? What is the current status of the</FONT>
<BR><FONT SIZE=3D2>drft-ietf-megaco-h248v2-00.txt?</FONT>
</P>

<P><FONT SIZE=3D2>Thank you in advance.</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>__________________________________________________</FONT>
<BR><FONT SIZE=3D2>Do You Yahoo!?</FONT>
<BR><FONT SIZE=3D2>Great stuff seeking new owners in Yahoo! Auctions! =
</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://auctions.yahoo.com" =
TARGET=3D"_blank">http://auctions.yahoo.com</A></FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A996.EA8221F0--

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


From daemon@optimus.ietf.org  Wed Jan 30 09:20:23 2002
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 JAA19778
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:20:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA28668
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 09:20:25 -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 JAA27507;
	Wed, 30 Jan 2002 09:04:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27476
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:04:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18890
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:04:13 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE3e802032;
	Wed, 30 Jan 2002 09:03:40 -0500 (EST)
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 g0UE3ct26878;
	Wed, 30 Jan 2002 09:03:38 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA46SS>; Wed, 30 Jan 2002 09:03:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt
Date: Wed, 30 Jan 2002 09:03:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1A996.EA8221F0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1A996.EA8221F0
Content-Type: text/plain;
	charset="iso-8859-1"

We work together closely with ITU-T Study Group 16.  All going well, they
will approve H.248v2 in the coming two weeks.  There will undoubtedly be
changes from what I recorded in draft-ietf-megaco-h248v2-00.txt, so I'll
up-version that document.  Then we'll put it through Last Call so we can
turn it into an RFC obsoleting RFC 3015.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Wednesday, January 30, 2002 2:06 AM
To: megaco@ietf.org
Subject: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt


Hi,

I am new to this list, sorry for asking faq questions:

Will the drft-ietf-megaco-h248v2-00.txt replace
rfc3015? What is the current status of the
drft-ietf-megaco-h248v2-00.txt?

Thank you in advance.


__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

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

------_=_NextPart_001_01C1A996.EA8221F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Megaco] Re: drft-ietf-megaco-h248v2-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>We work together closely with ITU-T Study Group =
16.&nbsp; All going well, they will approve H.248v2 in the coming two =
weeks.&nbsp; There will undoubtedly be changes from what I recorded in =
draft-ietf-megaco-h248v2-00.txt, so I'll up-version that =
document.&nbsp; Then we'll put it through Last Call so we can turn it =
into an RFC obsoleting RFC 3015.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Y Hu [<A =
HREF=3D"mailto:yh86us@yahoo.com">mailto:yh86us@yahoo.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, January 30, 2002 2:06 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Re: =
drft-ietf-megaco-h248v2-00.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>I am new to this list, sorry for asking faq =
questions:</FONT>
</P>

<P><FONT SIZE=3D2>Will the drft-ietf-megaco-h248v2-00.txt =
replace</FONT>
<BR><FONT SIZE=3D2>rfc3015? What is the current status of the</FONT>
<BR><FONT SIZE=3D2>drft-ietf-megaco-h248v2-00.txt?</FONT>
</P>

<P><FONT SIZE=3D2>Thank you in advance.</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>__________________________________________________</FONT>
<BR><FONT SIZE=3D2>Do You Yahoo!?</FONT>
<BR><FONT SIZE=3D2>Great stuff seeking new owners in Yahoo! Auctions! =
</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://auctions.yahoo.com" =
TARGET=3D"_blank">http://auctions.yahoo.com</A></FONT>
</P>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Megaco mailing list</FONT>
<BR><FONT SIZE=3D2>Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/megaco" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</A></FON=
T>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A996.EA8221F0--

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



From megaco-admin@ietf.org  Wed Jan 30 09:45:35 2002
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 JAA20752
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:45:34 -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 JAA29641;
	Wed, 30 Jan 2002 09:32:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29563
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:32:46 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20196
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:32:40 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0UEVH918299
	for <megaco@ietf.org>; Wed, 30 Jan 2002 20:01:17 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQR9PF01.479; Wed, 30 Jan 2002 20:02:03 +0530 
Message-ID: <117501c1a99b$3b8ac620$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Taylor Tom-PT [CAR:B800:EXCH]" <taylor@americasm01.nt.com>,
        <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102AF4C@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 20:04:31 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1172_01C1A9C9.54CD5CF0"

------=_NextPart_000_1172_01C1A9C9.54CD5CF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is option A invalid for the reason that tonegen package is designed only =
for extension,or does the rule apply to any base package ?

    Acc to  12.4 of AVD_2128 =20
---- For example, if Package A defines event e1, and Package B extends =
Package A, then B/e1 is an event for a termination implementing Package =
B. By definition, the MG MUST also implement the base Package, but it =
optional to publish the base package as an allowed interface. If it does =
publish A, then A would be reported on the Package Descriptor in =
AuditValue as well as B, and event A/e1 would be available on a =
termination. If the MG does not publish A, then only B/e1 would be =
available=20
----

Going by the above , option A  is allowed if tonegen package is =
published .=20

TIA,
usha
  ----- Original Message -----=20
  From: Taylor, Tom-PT [CAR:B800:EXCH]=20
  To: 'Usha Iyer' ; megaco@ietf.org=20
  Sent: Wednesday, January 30, 2002 7:37 PM
  Subject: RE: [Megaco] Doubt on package extension


  Assuming DTMFgen defines d0 as both a signal and a toneId, and =
similarly for
  cw in callProgToneGen, then either B or C is valid.

  -----Original Message-----
  From: Usha Iyer [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 3:01 AM
  To: megaco@ietf.org
  Subject: [Megaco] Doubt on package extension


  Hi ,
  =20
  DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
  So for a termination that supports ToneGen, DTMFGen and Call =
ProgToneGen Pkg
  , suppose i want to play d0 follwed by call  waiting tone , which of =
the
  foll apply .=20
  =20
  A - tonegen/playtone(toneid list=3D d0,cw )=20
  B -dtmfgen/playtone(toneid list=3D d0 )  followed by
  callprogtonegen/playtone(toneid list=3D cw )
  C -dtmfgen/d0 followed by callprogtonegen/cw=20
  =20
  =20
  Reg
  Usha


------=_NextPart_000_1172_01C1A9C9.54CD5CF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Is&nbsp;option A =
invalid for the=20
reason that tonegen package is designed only for extension,or does the =
rule=20
apply to&nbsp;any base package ?</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp;&nbsp; Acc =
to &nbsp;12.4=20
of AVD_2128&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>---- <FONT size=3D2>For =
example, if=20
Package A defines event e1, and Package B extends Package A, then B/e1 =
is an=20
event for a termination implementing Package B. By definition, the MG =
MUST also=20
implement the base Package, but it optional to publish the base package =
as an=20
allowed interface. If it does publish A, then A would be reported on the =
Package=20
Descriptor in AuditValue as well as B, and event A/e1 would be available =
on a=20
termination. If the MG does not publish A, then only B/e1 would be =
available=20
</FONT></FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>----</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Going by the above =
,&nbsp;option=20
A&nbsp; is allowed if tonegen package is published . </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>TIA,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>usha</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dtaylor@americasm01.nt.com=20
  href=3D"mailto:taylor@americasm01.nt.com">Taylor, Tom-PT =
[CAR:B800:EXCH]</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dusha.iyer@wipro.com=20
  href=3D"mailto:usha.iyer@wipro.com">'Usha Iyer'</A> ; <A =
title=3Dmegaco@ietf.org=20
  href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 30, =
2002 7:37=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Megaco] Doubt on =
package=20
  extension</DIV>
  <DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080=20
  size=3D2></FONT><BR></DIV>Assuming DTMFgen defines d0 as both a signal =
and a=20
  toneId, and similarly for<BR>cw in callProgToneGen, then either B or C =
is=20
  valid.<BR><BR>-----Original Message-----<BR>From: Usha Iyer=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 3:01 =

  AM<BR>To: <A =
href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR>Subject:=20
  [Megaco] Doubt on package extension<BR><BR><BR>Hi ,<BR>&nbsp;<BR>DTMF =
Gen and=20
  Call ProgressToneGen pkg both extend tone gen package .&nbsp; <BR>So =
for a=20
  termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg<BR>,=20
  suppose i want to play d0 follwed by call&nbsp; waiting tone , which =
of=20
  the<BR>foll apply . <BR>&nbsp;<BR>A - tonegen/playtone(toneid list=3D =
d0,cw )=20
  <BR>B -dtmfgen/playtone(toneid list=3D d0 )&nbsp; followed=20
  by<BR>callprogtonegen/playtone(toneid list=3D cw )<BR>C -dtmfgen/d0 =
followed by=20
  callprogtonegen/cw=20
<BR>&nbsp;<BR>&nbsp;<BR>Reg<BR>Usha<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_1172_01C1A9C9.54CD5CF0--



------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8--


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


From daemon@optimus.ietf.org  Wed Jan 30 09:45:35 2002
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 JAA20766
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:45:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00452
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 09:45:38 -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 JAA29641;
	Wed, 30 Jan 2002 09:32:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29563
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:32:46 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20196
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:32:40 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0UEVH918299
	for <megaco@ietf.org>; Wed, 30 Jan 2002 20:01:17 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQR9PF01.479; Wed, 30 Jan 2002 20:02:03 +0530 
Message-ID: <117501c1a99b$3b8ac620$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Taylor Tom-PT [CAR:B800:EXCH]" <taylor@americasm01.nt.com>,
        <megaco@ietf.org>
References: <4D79C746863DD51197690002A52CDA000102AF4C@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 20:04:31 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1172_01C1A9C9.54CD5CF0"

------=_NextPart_000_1172_01C1A9C9.54CD5CF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is option A invalid for the reason that tonegen package is designed only =
for extension,or does the rule apply to any base package ?

    Acc to  12.4 of AVD_2128 =20
---- For example, if Package A defines event e1, and Package B extends =
Package A, then B/e1 is an event for a termination implementing Package =
B. By definition, the MG MUST also implement the base Package, but it =
optional to publish the base package as an allowed interface. If it does =
publish A, then A would be reported on the Package Descriptor in =
AuditValue as well as B, and event A/e1 would be available on a =
termination. If the MG does not publish A, then only B/e1 would be =
available=20
----

Going by the above , option A  is allowed if tonegen package is =
published .=20

TIA,
usha
  ----- Original Message -----=20
  From: Taylor, Tom-PT [CAR:B800:EXCH]=20
  To: 'Usha Iyer' ; megaco@ietf.org=20
  Sent: Wednesday, January 30, 2002 7:37 PM
  Subject: RE: [Megaco] Doubt on package extension


  Assuming DTMFgen defines d0 as both a signal and a toneId, and =
similarly for
  cw in callProgToneGen, then either B or C is valid.

  -----Original Message-----
  From: Usha Iyer [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 3:01 AM
  To: megaco@ietf.org
  Subject: [Megaco] Doubt on package extension


  Hi ,
  =20
  DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
  So for a termination that supports ToneGen, DTMFGen and Call =
ProgToneGen Pkg
  , suppose i want to play d0 follwed by call  waiting tone , which of =
the
  foll apply .=20
  =20
  A - tonegen/playtone(toneid list=3D d0,cw )=20
  B -dtmfgen/playtone(toneid list=3D d0 )  followed by
  callprogtonegen/playtone(toneid list=3D cw )
  C -dtmfgen/d0 followed by callprogtonegen/cw=20
  =20
  =20
  Reg
  Usha


------=_NextPart_000_1172_01C1A9C9.54CD5CF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Is&nbsp;option A =
invalid for the=20
reason that tonegen package is designed only for extension,or does the =
rule=20
apply to&nbsp;any base package ?</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp;&nbsp; Acc =
to &nbsp;12.4=20
of AVD_2128&nbsp;&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>---- <FONT size=3D2>For =
example, if=20
Package A defines event e1, and Package B extends Package A, then B/e1 =
is an=20
event for a termination implementing Package B. By definition, the MG =
MUST also=20
implement the base Package, but it optional to publish the base package =
as an=20
allowed interface. If it does publish A, then A would be reported on the =
Package=20
Descriptor in AuditValue as well as B, and event A/e1 would be available =
on a=20
termination. If the MG does not publish A, then only B/e1 would be =
available=20
</FONT></FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>----</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Going by the above =
,&nbsp;option=20
A&nbsp; is allowed if tonegen package is published . </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>TIA,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>usha</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dtaylor@americasm01.nt.com=20
  href=3D"mailto:taylor@americasm01.nt.com">Taylor, Tom-PT =
[CAR:B800:EXCH]</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dusha.iyer@wipro.com=20
  href=3D"mailto:usha.iyer@wipro.com">'Usha Iyer'</A> ; <A =
title=3Dmegaco@ietf.org=20
  href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, January 30, =
2002 7:37=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Megaco] Doubt on =
package=20
  extension</DIV>
  <DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080=20
  size=3D2></FONT><BR></DIV>Assuming DTMFgen defines d0 as both a signal =
and a=20
  toneId, and similarly for<BR>cw in callProgToneGen, then either B or C =
is=20
  valid.<BR><BR>-----Original Message-----<BR>From: Usha Iyer=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 3:01 =

  AM<BR>To: <A =
href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR>Subject:=20
  [Megaco] Doubt on package extension<BR><BR><BR>Hi ,<BR>&nbsp;<BR>DTMF =
Gen and=20
  Call ProgressToneGen pkg both extend tone gen package .&nbsp; <BR>So =
for a=20
  termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg<BR>,=20
  suppose i want to play d0 follwed by call&nbsp; waiting tone , which =
of=20
  the<BR>foll apply . <BR>&nbsp;<BR>A - tonegen/playtone(toneid list=3D =
d0,cw )=20
  <BR>B -dtmfgen/playtone(toneid list=3D d0 )&nbsp; followed=20
  by<BR>callprogtonegen/playtone(toneid list=3D cw )<BR>C -dtmfgen/d0 =
followed by=20
  callprogtonegen/cw=20
<BR>&nbsp;<BR>&nbsp;<BR>Reg<BR>Usha<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_1172_01C1A9C9.54CD5CF0--



------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

-----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
------------------------------------------------------------------------------------------------------------------------

------=_NextPartTM-000-c9b67c74-157a-11d6-a941-00b0d0d06be8--


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



From megaco-admin@ietf.org  Wed Jan 30 10:11:39 2002
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 KAA21635
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:11:39 -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 JAA00986;
	Wed, 30 Jan 2002 09:59:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00953
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:59:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21194
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:59:29 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UEwq810020
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:58:53 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UEwoh07677
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:58:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA48V0>; Wed, 30 Jan 2002 09:58:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 09:58:54 -0500
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

This doesn't feel right to me, and the cases are not exactly the same.  Here
we have a parameter value which is unknown in the base package.  Even though
toneGen is known there, the parameter value is not.  In my view this means
you have to address that value through the extension which defined it (or
extensions of that extension).


-----Original Message-----
From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 9:35 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
Subject: Re: [Megaco] Doubt on package extension


Is option A invalid for the reason that tonegen package is designed only for
extension,or does the rule apply to any base package ?
 
    Acc to  12.4 of AVD_2128  
---- For example, if Package A defines event e1, and Package B extends
Package A, then B/e1 is an event for a termination implementing Package B.
By definition, the MG MUST also implement the base Package, but it optional
to publish the base package as an allowed interface. If it does publish A,
then A would be reported on the Package Descriptor in AuditValue as well as
B, and event A/e1 would be available on a termination. If the MG does not
publish A, then only B/e1 would be available 
----
 
Going by the above , option A  is allowed if tonegen package is published . 
 
TIA,
usha
----- Original Message ----- 
From: Taylor, Tom-PT [CAR:B800:EXCH] 
To: 'Usha Iyer' ; megaco@ietf.org 
Sent: Wednesday, January 30, 2002 7:37 PM
Subject: RE: [Megaco] Doubt on package extension


Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha

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


From daemon@optimus.ietf.org  Wed Jan 30 10:11:44 2002
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 KAA21645
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:11:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02093
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 10:11:42 -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 JAA00986;
	Wed, 30 Jan 2002 09:59:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00953
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:59:33 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21194
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:59:29 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UEwq810020
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:58:53 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UEwoh07677
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:58:50 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA48V0>; Wed, 30 Jan 2002 09:58:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 09:58:54 -0500
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

This doesn't feel right to me, and the cases are not exactly the same.  Here
we have a parameter value which is unknown in the base package.  Even though
toneGen is known there, the parameter value is not.  In my view this means
you have to address that value through the extension which defined it (or
extensions of that extension).


-----Original Message-----
From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 9:35 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
Subject: Re: [Megaco] Doubt on package extension


Is option A invalid for the reason that tonegen package is designed only for
extension,or does the rule apply to any base package ?
 
    Acc to  12.4 of AVD_2128  
---- For example, if Package A defines event e1, and Package B extends
Package A, then B/e1 is an event for a termination implementing Package B.
By definition, the MG MUST also implement the base Package, but it optional
to publish the base package as an allowed interface. If it does publish A,
then A would be reported on the Package Descriptor in AuditValue as well as
B, and event A/e1 would be available on a termination. If the MG does not
publish A, then only B/e1 would be available 
----
 
Going by the above , option A  is allowed if tonegen package is published . 
 
TIA,
usha
----- Original Message ----- 
From: Taylor, Tom-PT [CAR:B800:EXCH] 
To: 'Usha Iyer' ; megaco@ietf.org 
Sent: Wednesday, January 30, 2002 7:37 PM
Subject: RE: [Megaco] Doubt on package extension


Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha

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



From megaco-admin@ietf.org  Wed Jan 30 10:16:55 2002
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 JAA19753
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:20:22 -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 JAA27788;
	Wed, 30 Jan 2002 09:07:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27740
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:07:54 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19064
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE7H802574
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:17 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE7Fh03918
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:15 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA46XN>; Wed, 30 Jan 2002 09:07:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Usha Iyer'" <usha.iyer@wipro.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 09:07:06 -0500
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

Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha
 

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


From daemon@optimus.ietf.org  Wed Jan 30 10:16:55 2002
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 JAA19779
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 09:20:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA28669
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 09:20:25 -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 JAA27788;
	Wed, 30 Jan 2002 09:07:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27740
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 09:07:54 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19064
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE7H802574
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:17 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0UE7Fh03918
	for <megaco@ietf.org>; Wed, 30 Jan 2002 09:07:15 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QA46XN>; Wed, 30 Jan 2002 09:07:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF4C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Usha Iyer'" <usha.iyer@wipro.com>, megaco@ietf.org
Subject: RE: [Megaco] Doubt on package extension
Date: Wed, 30 Jan 2002 09:07:06 -0500
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

Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha
 

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



From megaco-admin@ietf.org  Wed Jan 30 10:45:40 2002
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 KAA22937
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:45:40 -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 KAA03492;
	Wed, 30 Jan 2002 10:35:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03460
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 10:35:35 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22590
	for <megaco@ietf.org>; Wed, 30 Jan 2002 10:35:33 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UFW9504754;
	Wed, 30 Jan 2002 10:32:10 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA07797;
	Wed, 30 Jan 2002 10:31:52 -0500 (EST)
Message-ID: <3C5811B8.4D49E634@lucent.com>
Date: Wed, 30 Jan 2002 10:31:05 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco ietf <megaco@ietf.org>, Kevin Boyle <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] Digit Map spec
References: <20020130043622.9863.qmail@mailweb14.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------41166A52376FEFB027D08F78"
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

This is a multi-part message in MIME format.
--------------41166A52376FEFB027D08F78
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DigitMap syntax is explained in 7.1.14 and of course the ABNF is given in Annex B.  They do NOT allow full regular expressions.

vidya g wrote:

> Hi all
>
>    What are the possible pattern of digitmaps allowed in digit map discriptor.. ? Does it support regular expression patterns. In the example [1-7]xxx is given. Like this what all patterns are possible.. ?
>
> vdy
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--------------41166A52376FEFB027D08F78
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------41166A52376FEFB027D08F78--


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


From daemon@optimus.ietf.org  Wed Jan 30 10:45:45 2002
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 KAA22947
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:45:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA04044
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 10:45:41 -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 KAA03492;
	Wed, 30 Jan 2002 10:35:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA03460
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 10:35:35 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22590
	for <megaco@ietf.org>; Wed, 30 Jan 2002 10:35:33 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UFW9504754;
	Wed, 30 Jan 2002 10:32:10 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA07797;
	Wed, 30 Jan 2002 10:31:52 -0500 (EST)
Message-ID: <3C5811B8.4D49E634@lucent.com>
Date: Wed, 30 Jan 2002 10:31:05 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco ietf <megaco@ietf.org>, Kevin Boyle <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] Digit Map spec
References: <20020130043622.9863.qmail@mailweb14.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------41166A52376FEFB027D08F78"
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

This is a multi-part message in MIME format.
--------------41166A52376FEFB027D08F78
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DigitMap syntax is explained in 7.1.14 and of course the ABNF is given in Annex B.  They do NOT allow full regular expressions.

vidya g wrote:

> Hi all
>
>    What are the possible pattern of digitmaps allowed in digit map discriptor.. ? Does it support regular expression patterns. In the example [1-7]xxx is given. Like this what all patterns are possible.. ?
>
> vdy
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--------------41166A52376FEFB027D08F78
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------41166A52376FEFB027D08F78--


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



From megaco-admin@ietf.org  Wed Jan 30 10:56:39 2002
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 KAA23290
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:56:39 -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 KAA04167;
	Wed, 30 Jan 2002 10:47:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04127
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 10:47:30 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22980
	for <megaco@ietf.org>; Wed, 30 Jan 2002 10:47:28 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UFlT512982;
	Wed, 30 Jan 2002 10:47:29 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA08342;
	Wed, 30 Jan 2002 10:47:27 -0500 (EST)
Message-ID: <3C58155F.1F1FC3AB@lucent.com>
Date: Wed, 30 Jan 2002 10:46:39 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------78C56CF2FB3B9FB9A8998FCE"
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

This is a multi-part message in MIME format.
--------------78C56CF2FB3B9FB9A8998FCE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The statement (in 8.0) IS misleading but your understanding is also incorrect.

8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
the entire Transaction (not just the action).

Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.

Do folks think this sentence should be corrected in IG?

vidya g wrote:

> Hi all
>
>   In RFC, page number 61 it says that
>
>  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
>
>   This statement is some what confusing. What I understand is even if a non optional
> command fails in an action, the action will be cancelled and the next action will be taken
> for processing and the commands in that action will be processed.. is that right .. ?
>
> vdy
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--------------78C56CF2FB3B9FB9A8998FCE
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------78C56CF2FB3B9FB9A8998FCE--


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


From daemon@optimus.ietf.org  Wed Jan 30 10:56:40 2002
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 KAA23301
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 10:56:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA04700
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 10:56:41 -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 KAA04167;
	Wed, 30 Jan 2002 10:47:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04127
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 10:47:30 -0500 (EST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22980
	for <megaco@ietf.org>; Wed, 30 Jan 2002 10:47:28 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UFlT512982;
	Wed, 30 Jan 2002 10:47:29 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id KAA08342;
	Wed, 30 Jan 2002 10:47:27 -0500 (EST)
Message-ID: <3C58155F.1F1FC3AB@lucent.com>
Date: Wed, 30 Jan 2002 10:46:39 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vidya g <vdy73@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com>
Content-Type: multipart/mixed;
 boundary="------------78C56CF2FB3B9FB9A8998FCE"
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

This is a multi-part message in MIME format.
--------------78C56CF2FB3B9FB9A8998FCE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The statement (in 8.0) IS misleading but your understanding is also incorrect.

8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
the entire Transaction (not just the action).

Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.

Do folks think this sentence should be corrected in IG?

vidya g wrote:

> Hi all
>
>   In RFC, page number 61 it says that
>
>  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
>
>   This statement is some what confusing. What I understand is even if a non optional
> command fails in an action, the action will be cancelled and the next action will be taken
> for processing and the commands in that action will be processed.. is that right .. ?
>
> vdy
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--------------78C56CF2FB3B9FB9A8998FCE
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------78C56CF2FB3B9FB9A8998FCE--


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



From daemon@optimus.ietf.org  Wed Jan 30 11:46:29 2002
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 LAA24682
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 11:46:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA07787
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 11:46:30 -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 LAA06471;
	Wed, 30 Jan 2002 11:28:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06442
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 11:28:34 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24159
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:31 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UGS3M02089
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:03 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA09610
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:01 -0500 (EST)
Message-ID: <3C581EE1.F11D8357@lucent.com>
Date: Wed, 30 Jan 2002 11:27:14 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco Mailing List <megaco@ietf.org>
Content-Type: multipart/mixed;
 boundary="------------8B937DED0F4A280D8BA4C05D"
Subject: [Megaco] H.248 Annex M.ka KeepAlive package
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

This is a multi-part message in MIME format.
--------------8B937DED0F4A280D8BA4C05D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I submitted an editors draft of the proposed H.248 Annex M.ka KeepAlive
Package to the Geneva meeting.  It appears as TD 2-014 in WP2.  But
recently I have received a comment about the Maximum Inactivity Time
being in integral units of seconds.  High capacity MGs might find 1
second as being too long.  It was proposed that we define the unit to be
"hundredths of seconds" as it is for duration of TO signals.  Leaving
the range as 0..65535 still permits a inactive time as long as 655 sec
or over 10 min which seems more than adequate.  I will propose that
change to hundredths of sec when the document is discussed in Geneva.
Does anyone have a concern with the new range being
1/100 sec to 655 sec.  ?

--------------8B937DED0F4A280D8BA4C05D
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------8B937DED0F4A280D8BA4C05D--


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



From megaco-admin@ietf.org  Wed Jan 30 12:46:57 2002
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 LAA24675
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 11:46:28 -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 LAA06471;
	Wed, 30 Jan 2002 11:28:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06442
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 11:28:34 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24159
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:31 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0UGS3M02089
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:03 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA09610
	for <megaco@ietf.org>; Wed, 30 Jan 2002 11:28:01 -0500 (EST)
Message-ID: <3C581EE1.F11D8357@lucent.com>
Date: Wed, 30 Jan 2002 11:27:14 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco Mailing List <megaco@ietf.org>
Content-Type: multipart/mixed;
 boundary="------------8B937DED0F4A280D8BA4C05D"
Subject: [Megaco] H.248 Annex M.ka KeepAlive package
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

This is a multi-part message in MIME format.
--------------8B937DED0F4A280D8BA4C05D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I submitted an editors draft of the proposed H.248 Annex M.ka KeepAlive
Package to the Geneva meeting.  It appears as TD 2-014 in WP2.  But
recently I have received a comment about the Maximum Inactivity Time
being in integral units of seconds.  High capacity MGs might find 1
second as being too long.  It was proposed that we define the unit to be
"hundredths of seconds" as it is for duration of TO signals.  Leaving
the range as 0..65535 still permits a inactive time as long as 655 sec
or over 10 min which seems more than adequate.  I will propose that
change to hundredths of sec when the document is discussed in Geneva.
Does anyone have a concern with the new range being
1/100 sec to 655 sec.  ?

--------------8B937DED0F4A280D8BA4C05D
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------8B937DED0F4A280D8BA4C05D--


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


From megaco-admin@ietf.org  Wed Jan 30 14:07:42 2002
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 OAA29418
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 14:07:42 -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 NAA15478;
	Wed, 30 Jan 2002 13:55:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15447
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 13:54:58 -0500 (EST)
Received: from mailFA6.rediffmail.com ([202.54.124.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29033
	for <megaco@ietf.org>; Wed, 30 Jan 2002 13:54:55 -0500 (EST)
Received: (qmail 26639 invoked by uid 510); 30 Jan 2002 18:56:51 -0000
Date: 30 Jan 2002 18:56:51 -0000
Message-ID: <20020130185651.26638.qmail@mailFA6.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 30 Jan 2002 18:56:51 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA15448
Subject: [Megaco] Where Can I find Interoperability test profile ?
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


http://megaco.iol.unh.edu/draft-rosen-megaco-test-profile-01.txt seems does not existing anymore ?. Anyone point me to the right link ?

regards

Surya


 


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


From daemon@optimus.ietf.org  Wed Jan 30 14:07:47 2002
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 OAA29434
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 14:07:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA16894
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 14:07:44 -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 NAA15478;
	Wed, 30 Jan 2002 13:55:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15447
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 13:54:58 -0500 (EST)
Received: from mailFA6.rediffmail.com ([202.54.124.151])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29033
	for <megaco@ietf.org>; Wed, 30 Jan 2002 13:54:55 -0500 (EST)
Received: (qmail 26639 invoked by uid 510); 30 Jan 2002 18:56:51 -0000
Date: 30 Jan 2002 18:56:51 -0000
Message-ID: <20020130185651.26638.qmail@mailFA6.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 30 Jan 2002 18:56:51 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA15448
Subject: [Megaco] Where Can I find Interoperability test profile ?
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


http://megaco.iol.unh.edu/draft-rosen-megaco-test-profile-01.txt seems does not existing anymore ?. Anyone point me to the right link ?

regards

Surya


 


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



From megaco-admin@ietf.org  Wed Jan 30 15:09:02 2002
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 PAA01095
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 15:08:57 -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 OAA19576;
	Wed, 30 Jan 2002 14:51:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19508
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 14:51:25 -0500 (EST)
Received: from mailweb26.rediffmail.com ([203.199.83.30])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00704
	for <megaco@ietf.org>; Wed, 30 Jan 2002 14:51:22 -0500 (EST)
Received: (qmail 7154 invoked by uid 510); 30 Jan 2002 19:52:11 -0000
Date: 30 Jan 2002 19:52:11 -0000
Message-ID: <20020130195211.7153.qmail@mailweb26.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 30 Jan 2002 19:52:11 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA19511
Subject: [Megaco] ServiceChangeReq for terminations
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


Upon establishing session(Cold Start) with MGC, would GW is requied to send ServiceChange with method (FORCED) for the terminations, that are outofService ?.

Please answer .

with regards

Surya 


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


From daemon@optimus.ietf.org  Wed Jan 30 15:09:03 2002
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 PAA01106
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 15:09:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA20840
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 15:09:04 -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 OAA19576;
	Wed, 30 Jan 2002 14:51:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19508
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 14:51:25 -0500 (EST)
Received: from mailweb26.rediffmail.com ([203.199.83.30])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00704
	for <megaco@ietf.org>; Wed, 30 Jan 2002 14:51:22 -0500 (EST)
Received: (qmail 7154 invoked by uid 510); 30 Jan 2002 19:52:11 -0000
Date: 30 Jan 2002 19:52:11 -0000
Message-ID: <20020130195211.7153.qmail@mailweb26.rediffmail.com>
Received: from unknown (63.111.211.2) by rediffmail.com via HTTP; 30 Jan 2002 19:52:11 -0000
MIME-Version: 1.0
From: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
Reply-To: "Suryapratap  vamsi" <suryavamsi2@rediffmail.com>
To: megaco@ietf.org
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA19511
Subject: [Megaco] ServiceChangeReq for terminations
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


Upon establishing session(Cold Start) with MGC, would GW is requied to send ServiceChange with method (FORCED) for the terminations, that are outofService ?.

Please answer .

with regards

Surya 


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



From megaco-admin@ietf.org  Wed Jan 30 16:58:37 2002
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 QAA03155
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 16:58:37 -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 QAA25045;
	Wed, 30 Jan 2002 16:48:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA25017
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 16:48:26 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02942
	for <megaco@ietf.org>; Wed, 30 Jan 2002 16:48:22 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0ULlrQ07957
	for <megaco@ietf.org>; Wed, 30 Jan 2002 16:47:54 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA15507; Wed, 30 Jan 2002 16:47:51 -0500 (EST)
Cc: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco <megaco@ietf.org>
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA15493; Wed, 30 Jan 2002 16:47:47 -0500 (EST)
Message-ID: <3C586959.CBFDD664@bell-labs.com>
Date: Wed, 30 Jan 2002 16:44:57 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
Original-CC: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco <megaco@ietf.org>
Subject: Re: [Megaco] Doubt on package extension
References: <4D79C746863DD51197690002A52CDA000102AF4E@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


We've been around on this subject before.  

Here are some notes I compiled for my own use.  Too bad
I didn't reference the specific mailing list messages
on which they're based.

Perhaps the language used will stimulate someone's memory.


/* NOTES:
 * Given packges A with event a1 and B with event b1 where B extends A:
 *
 *      A/a1, B/b1, & B/a1 are legal.
 *      A/b1 is not.
 *
 * Note that we search DOWN the extension chain from B to verify a1.
 *
 * Packages may also define new parameter VALUES for the packages they extend.
 * So if A/a1 has a parameter ap1, B may define a value bv1 making
 *
 *      A/a1 { ap1=bv1 } legal, and
 *      B/a1 { ap1=bv1 } legal.
 *
 * Note that we search UP the extension chain (tree) to verify v1!
 */


-troy


Tom-PT Taylor wrote:
> 
> This doesn't feel right to me, and the cases are not exactly the same.  Here
> we have a parameter value which is unknown in the base package.  Even though
> toneGen is known there, the parameter value is not.  In my view this means
> you have to address that value through the extension which defined it (or
> extensions of that extension).
> 
> -----Original Message-----
> From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 30, 2002 9:35 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
> Subject: Re: [Megaco] Doubt on package extension
> 
> Is option A invalid for the reason that tonegen package is designed only for
> extension,or does the rule apply to any base package ?
> 
>     Acc to  12.4 of AVD_2128
> ---- For example, if Package A defines event e1, and Package B extends
> Package A, then B/e1 is an event for a termination implementing Package B.
> By definition, the MG MUST also implement the base Package, but it optional
> to publish the base package as an allowed interface. If it does publish A,
> then A would be reported on the Package Descriptor in AuditValue as well as
> B, and event A/e1 would be available on a termination. If the MG does not
> publish A, then only B/e1 would be available
> ----
> 
> Going by the above , option A  is allowed if tonegen package is published .
> 
> TIA,
> usha
> ----- Original Message -----
> From: Taylor, Tom-PT [CAR:B800:EXCH]
> To: 'Usha Iyer' ; megaco@ietf.org
> Sent: Wednesday, January 30, 2002 7:37 PM
> Subject: RE: [Megaco] Doubt on package extension
> 
> Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
> cw in callProgToneGen, then either B or C is valid.
> 
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 30, 2002 3:01 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt on package extension
> 
> Hi ,
> 
> DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .
> So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
> , suppose i want to play d0 follwed by call  waiting tone , which of the
> foll apply .
> 
> A - tonegen/playtone(toneid list= d0,cw )
> B -dtmfgen/playtone(toneid list= d0 )  followed by
> callprogtonegen/playtone(toneid list= cw )
> C -dtmfgen/d0 followed by callprogtonegen/cw
> 
> 
> Reg
> Usha
> 
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Wed Jan 30 16:58:38 2002
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 QAA03164
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 16:58:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA25214
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 16:58:40 -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 QAA25045;
	Wed, 30 Jan 2002 16:48:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA25017
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 16:48:26 -0500 (EST)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02942
	for <megaco@ietf.org>; Wed, 30 Jan 2002 16:48:22 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0ULlrQ07957
	for <megaco@ietf.org>; Wed, 30 Jan 2002 16:47:54 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA15507; Wed, 30 Jan 2002 16:47:51 -0500 (EST)
Cc: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco <megaco@ietf.org>
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id QAA15493; Wed, 30 Jan 2002 16:47:47 -0500 (EST)
Message-ID: <3C586959.CBFDD664@bell-labs.com>
Date: Wed, 30 Jan 2002 16:44:57 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
Original-CC: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco <megaco@ietf.org>
Subject: Re: [Megaco] Doubt on package extension
References: <4D79C746863DD51197690002A52CDA000102AF4E@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


We've been around on this subject before.  

Here are some notes I compiled for my own use.  Too bad
I didn't reference the specific mailing list messages
on which they're based.

Perhaps the language used will stimulate someone's memory.


/* NOTES:
 * Given packges A with event a1 and B with event b1 where B extends A:
 *
 *      A/a1, B/b1, & B/a1 are legal.
 *      A/b1 is not.
 *
 * Note that we search DOWN the extension chain from B to verify a1.
 *
 * Packages may also define new parameter VALUES for the packages they extend.
 * So if A/a1 has a parameter ap1, B may define a value bv1 making
 *
 *      A/a1 { ap1=bv1 } legal, and
 *      B/a1 { ap1=bv1 } legal.
 *
 * Note that we search UP the extension chain (tree) to verify v1!
 */


-troy


Tom-PT Taylor wrote:
> 
> This doesn't feel right to me, and the cases are not exactly the same.  Here
> we have a parameter value which is unknown in the base package.  Even though
> toneGen is known there, the parameter value is not.  In my view this means
> you have to address that value through the extension which defined it (or
> extensions of that extension).
> 
> -----Original Message-----
> From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 30, 2002 9:35 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
> Subject: Re: [Megaco] Doubt on package extension
> 
> Is option A invalid for the reason that tonegen package is designed only for
> extension,or does the rule apply to any base package ?
> 
>     Acc to  12.4 of AVD_2128
> ---- For example, if Package A defines event e1, and Package B extends
> Package A, then B/e1 is an event for a termination implementing Package B.
> By definition, the MG MUST also implement the base Package, but it optional
> to publish the base package as an allowed interface. If it does publish A,
> then A would be reported on the Package Descriptor in AuditValue as well as
> B, and event A/e1 would be available on a termination. If the MG does not
> publish A, then only B/e1 would be available
> ----
> 
> Going by the above , option A  is allowed if tonegen package is published .
> 
> TIA,
> usha
> ----- Original Message -----
> From: Taylor, Tom-PT [CAR:B800:EXCH]
> To: 'Usha Iyer' ; megaco@ietf.org
> Sent: Wednesday, January 30, 2002 7:37 PM
> Subject: RE: [Megaco] Doubt on package extension
> 
> Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
> cw in callProgToneGen, then either B or C is valid.
> 
> -----Original Message-----
> From: Usha Iyer [mailto:usha.iyer@wipro.com]
> Sent: Wednesday, January 30, 2002 3:01 AM
> To: megaco@ietf.org
> Subject: [Megaco] Doubt on package extension
> 
> Hi ,
> 
> DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .
> So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
> , suppose i want to play d0 follwed by call  waiting tone , which of the
> foll apply .
> 
> A - tonegen/playtone(toneid list= d0,cw )
> B -dtmfgen/playtone(toneid list= d0 )  followed by
> callprogtonegen/playtone(toneid list= cw )
> C -dtmfgen/d0 followed by callprogtonegen/cw
> 
> 
> Reg
> Usha
> 
> _______________________________________________
> 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



From megaco-admin@ietf.org  Wed Jan 30 20:39:16 2002
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 UAA06113
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 20:39:15 -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 UAA04208;
	Wed, 30 Jan 2002 20:26:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA04179
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 20:26:46 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05876
	for <megaco@ietf.org>; Wed, 30 Jan 2002 20:26:44 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id TAA05787
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:26:15 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0V1QFr20027
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:26:15 -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 g0V1PUG02716
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:25:30 -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 g0V1PUT11332
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:25:30 -0600 (CST)
Message-ID: <3C589D09.20028887@alcatel.com>
Date: Wed, 30 Jan 2002 19:25:29 -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'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com> <3C5761CC.2527ADF4@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------888EC4B6B622E16B6D1F10C2"
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


--------------888EC4B6B622E16B6D1F10C2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


If we just limit the discussion to LocalControlDescriptor and not thing about or
descriptor
in general or specifically Signal/Event Descriptor, the phrase

"how to delete a single property from descriptor"

What does it mean to delete a single property from LocalControlDescriptor?

From the Standard

7.1.7 LocalControl Descriptor

   The LocalControl Descriptor contains the Mode property, the
   ReserveGroup and ReserveValue properties and properties of a
   termination (defined in Packages) that are stream specific, and are
   of interest between the MG and the MGC.  Values of properties may be
   underspecified as in section 7.1.1.

LocalControlDescriptor always contains these properties which are always part
of a termination.
The only thing that changes is the value of the property or for properties that
are dependent
on what packages are supported by a termination.

For properties that can be added or deleted because of what packages are
supported by
a termination, MGC can't tell MG what package it needs to add or delete.
So I am not sure what deleting property really mean here?


Christian/Tom,
Do you happen to know the thread that this change was discussed and consensus was

reached?

Thanks
Chuong

Christian Groves wrote:

> G'Day Tom,
>
> I don't think we can accept the exception for property parameters this
> would be a big problem for interoperabilty between v1 and v2. Having to
> repeat the entire descriptor when we want to change one item I agree is
> not nice but the list came to a consensus that it was the way it would
> work.
>
> The other problem arises is that if  "leave a property absent from a
> descriptor" means keep the property as is, how do you then describe how
> to delete a single property from a descriptor?
>
> Regards, christian
>
> Tom-PT Taylor wrote:
> >
> > This seems like a practical solution for LocalControl, but if we accept it,
> > we have to change the text of the Recommendation, meaning that it only holds
> > for H.248v2.  I'll note that we have a real problem of interoperability
> > here.  My previous note on the interpretation of this clause presented three
> > alternatives, and I got E-mails (one private) in support of all three of
> > them.
> >
> > I don't quite see Wayne's point on the Signals and Events descriptors.  In
> > both cases, the semantics of the situation require the repetition of all of
> > the signals/events you want to keep.  You also need at least the KeepActive
> > parameter where it applies to signals.  Are you saying, Wayne, that once an
> > event or signal is specified, then if it is retained in replacement
> > descriptors it is unnecessary to respecify all the parameters that went
> > along with it the first time?  I could live with that as an IG
> > clarification.  Other views?
> >
> > -----Original Message-----
> > From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> > Sent: Tuesday, January 29, 2002 9:40 AM
> > To: 'megaco@ietf.org'
> > Subject: Re: [Megaco] Query about local control descriptor properties
> >
> >
> > I agreed w/Wayne on option d which is how it was before v1 came out.
> > Then we got into these Reserve parameters discussion and changes
> > but I didn't think the statement should apply to Property parameters.
> >
> > Wayne Cutler wrote:
> >
> > What about an option d) that would regard an absent Property as meaning
> > "leave the existing value unchanged"?
> > As a related question, I note that section 7.1.7 (Local Control Desc.)of
> > the spec.
> > says that:-
> > "A new setting of the LocalControl Descriptor completely replaces the
> > previous setting of that descriptor in the MG.  Thus to retain information
> > from
> > the previous setting the MGC must include that information in the new
> > setting".
> > Similar statements are made for the Events & Signals Descriptors.
> > In the case where an MG supports a number of packages, this text is saying
> > that an MGC
> > wishing to change data/attributes in one Package in a given Descriptor is
> > forced to repeat any previous data against any other Packages. This is
> > perverse. So, can this text be qualified to say that the new Descriptor
> > replaces only data relating to Packages present in the new/latest message?
> > Regards,
> > Wayne.
> > ------------
> > This e-mail and any attachments are confidential.  If you are not the
> > intended recipient, please notify us immediately by reply e-mail and then
> > delete this message from your system. Do not copy this e-mail or any
> > attachments, use the contents for any purpose, or disclose the contents to
> > any other person: to do so could be a breach of confidence.
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
> > --
> >   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

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



--------------888EC4B6B622E16B6D1F10C2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>If we just limit the discussion to LocalControlDescriptor and not thing
about or descriptor
<br>in general or specifically Signal/Event Descriptor, the phrase
<p>"how to delete a single property from descriptor"
<p>What does it mean to delete a single property from LocalControlDescriptor?
<p>From the Standard
<p>7.1.7 LocalControl Descriptor
<p>&nbsp;&nbsp; The LocalControl Descriptor contains the Mode property,
the
<br>&nbsp;&nbsp; ReserveGroup and ReserveValue properties and properties
of a
<br>&nbsp;&nbsp; termination (defined in Packages) that are stream specific,
and are
<br>&nbsp;&nbsp; of interest between the MG and the MGC.&nbsp; Values of
properties may be
<br>&nbsp;&nbsp; underspecified as in section 7.1.1.
<p>LocalControlDescriptor always contains these properties which are always
part
<br>of a termination.
<br>The only thing that changes is the value of the property or for properties
that are dependent
<br>on what packages are supported by a termination.
<p>For properties that can be added or deleted because of what packages
are supported by
<br>a termination, MGC can't tell MG&nbsp;what package it needs to add
or delete.
<br>So I&nbsp;am not sure what deleting property really mean here?
<br>&nbsp;
<p>Christian/Tom,
<br>Do you happen to know the thread that this change was discussed and
consensus was
<br>reached?
<p>Thanks
<br>Chuong
<p>Christian Groves wrote:
<blockquote TYPE=CITE>G'Day Tom,
<p>I don't think we can accept the exception for property parameters this
<br>would be a big problem for interoperabilty between v1 and v2. Having
to
<br>repeat the entire descriptor when we want to change one item I agree
is
<br>not nice but the list came to a consensus that it was the way it would
<br>work.
<p>The other problem arises is that if&nbsp; "leave a property absent from
a
<br>descriptor" means keep the property as is, how do you then describe
how
<br>to delete a single property from a descriptor?
<p>Regards, christian
<p>Tom-PT Taylor wrote:
<br>>
<br>> This seems like a practical solution for LocalControl, but if we
accept it,
<br>> we have to change the text of the Recommendation, meaning that it
only holds
<br>> for H.248v2.&nbsp; I'll note that we have a real problem of interoperability
<br>> here.&nbsp; My previous note on the interpretation of this clause
presented three
<br>> alternatives, and I got E-mails (one private) in support of all three
of
<br>> them.
<br>>
<br>> I don't quite see Wayne's point on the Signals and Events descriptors.&nbsp;
In
<br>> both cases, the semantics of the situation require the repetition
of all of
<br>> the signals/events you want to keep.&nbsp; You also need at least
the KeepActive
<br>> parameter where it applies to signals.&nbsp; Are you saying, Wayne,
that once an
<br>> event or signal is specified, then if it is retained in replacement
<br>> descriptors it is unnecessary to respecify all the parameters that
went
<br>> along with it the first time?&nbsp; I could live with that as an
IG
<br>> clarification.&nbsp; Other views?
<br>>
<br>> -----Original Message-----
<br>> From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>> Sent: Tuesday, January 29, 2002 9:40 AM
<br>> To: 'megaco@ietf.org'
<br>> Subject: Re: [Megaco] Query about local control descriptor properties
<br>>
<br>>
<br>> I agreed w/Wayne on option d which is how it was before v1 came out.
<br>> Then we got into these Reserve parameters discussion and changes
<br>> but I didn't think the statement should apply to Property parameters.
<br>>
<br>> Wayne Cutler wrote:
<br>>
<br>> What about an option d) that would regard an absent Property as meaning
<br>> "leave the existing value unchanged"?
<br>> As a related question, I note that section 7.1.7 (Local Control Desc.)of
<br>> the spec.
<br>> says that:-
<br>> "A new setting of the LocalControl Descriptor completely replaces
the
<br>> previous setting of that descriptor in the MG.&nbsp; Thus to retain
information
<br>> from
<br>> the previous setting the MGC must include that information in the
new
<br>> setting".
<br>> Similar statements are made for the Events &amp; Signals Descriptors.
<br>> In the case where an MG supports a number of packages, this text
is saying
<br>> that an MGC
<br>> wishing to change data/attributes in one Package in a given Descriptor
is
<br>> forced to repeat any previous data against any other Packages. This
is
<br>> perverse. So, can this text be qualified to say that the new Descriptor
<br>> replaces only data relating to Packages present in the new/latest
message?
<br>> Regards,
<br>> Wayne.
<br>> ------------
<br>> This e-mail and any attachments are confidential.&nbsp; If you are
not the
<br>> intended recipient, please notify us immediately by reply e-mail
and then
<br>> delete this message from your system. Do not copy this e-mail or
any
<br>> attachments, use the contents for any purpose, or disclose the contents
to
<br>> any other person: to do so could be a breach of confidence.
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------888EC4B6B622E16B6D1F10C2--


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


From daemon@optimus.ietf.org  Wed Jan 30 20:39:16 2002
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 UAA06123
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 20:39:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA05077
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 20:39: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 UAA04208;
	Wed, 30 Jan 2002 20:26:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA04179
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 20:26:46 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05876
	for <megaco@ietf.org>; Wed, 30 Jan 2002 20:26:44 -0500 (EST)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id TAA05787
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:26:15 -0600 (CST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g0V1QFr20027
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:26:15 -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 g0V1PUG02716
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:25:30 -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 g0V1PUT11332
	for <megaco@ietf.org>; Wed, 30 Jan 2002 19:25:30 -0600 (CST)
Message-ID: <3C589D09.20028887@alcatel.com>
Date: Wed, 30 Jan 2002 19:25:29 -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'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about local control descriptor properties
References: <4D79C746863DD51197690002A52CDA000102AF36@zcard0kc.ca.nortel.com> <3C5761CC.2527ADF4@ericsson.com.au>
Content-Type: multipart/alternative;
 boundary="------------888EC4B6B622E16B6D1F10C2"
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


--------------888EC4B6B622E16B6D1F10C2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


If we just limit the discussion to LocalControlDescriptor and not thing about or
descriptor
in general or specifically Signal/Event Descriptor, the phrase

"how to delete a single property from descriptor"

What does it mean to delete a single property from LocalControlDescriptor?

From the Standard

7.1.7 LocalControl Descriptor

   The LocalControl Descriptor contains the Mode property, the
   ReserveGroup and ReserveValue properties and properties of a
   termination (defined in Packages) that are stream specific, and are
   of interest between the MG and the MGC.  Values of properties may be
   underspecified as in section 7.1.1.

LocalControlDescriptor always contains these properties which are always part
of a termination.
The only thing that changes is the value of the property or for properties that
are dependent
on what packages are supported by a termination.

For properties that can be added or deleted because of what packages are
supported by
a termination, MGC can't tell MG what package it needs to add or delete.
So I am not sure what deleting property really mean here?


Christian/Tom,
Do you happen to know the thread that this change was discussed and consensus was

reached?

Thanks
Chuong

Christian Groves wrote:

> G'Day Tom,
>
> I don't think we can accept the exception for property parameters this
> would be a big problem for interoperabilty between v1 and v2. Having to
> repeat the entire descriptor when we want to change one item I agree is
> not nice but the list came to a consensus that it was the way it would
> work.
>
> The other problem arises is that if  "leave a property absent from a
> descriptor" means keep the property as is, how do you then describe how
> to delete a single property from a descriptor?
>
> Regards, christian
>
> Tom-PT Taylor wrote:
> >
> > This seems like a practical solution for LocalControl, but if we accept it,
> > we have to change the text of the Recommendation, meaning that it only holds
> > for H.248v2.  I'll note that we have a real problem of interoperability
> > here.  My previous note on the interpretation of this clause presented three
> > alternatives, and I got E-mails (one private) in support of all three of
> > them.
> >
> > I don't quite see Wayne's point on the Signals and Events descriptors.  In
> > both cases, the semantics of the situation require the repetition of all of
> > the signals/events you want to keep.  You also need at least the KeepActive
> > parameter where it applies to signals.  Are you saying, Wayne, that once an
> > event or signal is specified, then if it is retained in replacement
> > descriptors it is unnecessary to respecify all the parameters that went
> > along with it the first time?  I could live with that as an IG
> > clarification.  Other views?
> >
> > -----Original Message-----
> > From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> > Sent: Tuesday, January 29, 2002 9:40 AM
> > To: 'megaco@ietf.org'
> > Subject: Re: [Megaco] Query about local control descriptor properties
> >
> >
> > I agreed w/Wayne on option d which is how it was before v1 came out.
> > Then we got into these Reserve parameters discussion and changes
> > but I didn't think the statement should apply to Property parameters.
> >
> > Wayne Cutler wrote:
> >
> > What about an option d) that would regard an absent Property as meaning
> > "leave the existing value unchanged"?
> > As a related question, I note that section 7.1.7 (Local Control Desc.)of
> > the spec.
> > says that:-
> > "A new setting of the LocalControl Descriptor completely replaces the
> > previous setting of that descriptor in the MG.  Thus to retain information
> > from
> > the previous setting the MGC must include that information in the new
> > setting".
> > Similar statements are made for the Events & Signals Descriptors.
> > In the case where an MG supports a number of packages, this text is saying
> > that an MGC
> > wishing to change data/attributes in one Package in a given Descriptor is
> > forced to repeat any previous data against any other Packages. This is
> > perverse. So, can this text be qualified to say that the new Descriptor
> > replaces only data relating to Packages present in the new/latest message?
> > Regards,
> > Wayne.
> > ------------
> > This e-mail and any attachments are confidential.  If you are not the
> > intended recipient, please notify us immediately by reply e-mail and then
> > delete this message from your system. Do not copy this e-mail or any
> > attachments, use the contents for any purpose, or disclose the contents to
> > any other person: to do so could be a breach of confidence.
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
> > --
> >   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

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



--------------888EC4B6B622E16B6D1F10C2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>If we just limit the discussion to LocalControlDescriptor and not thing
about or descriptor
<br>in general or specifically Signal/Event Descriptor, the phrase
<p>"how to delete a single property from descriptor"
<p>What does it mean to delete a single property from LocalControlDescriptor?
<p>From the Standard
<p>7.1.7 LocalControl Descriptor
<p>&nbsp;&nbsp; The LocalControl Descriptor contains the Mode property,
the
<br>&nbsp;&nbsp; ReserveGroup and ReserveValue properties and properties
of a
<br>&nbsp;&nbsp; termination (defined in Packages) that are stream specific,
and are
<br>&nbsp;&nbsp; of interest between the MG and the MGC.&nbsp; Values of
properties may be
<br>&nbsp;&nbsp; underspecified as in section 7.1.1.
<p>LocalControlDescriptor always contains these properties which are always
part
<br>of a termination.
<br>The only thing that changes is the value of the property or for properties
that are dependent
<br>on what packages are supported by a termination.
<p>For properties that can be added or deleted because of what packages
are supported by
<br>a termination, MGC can't tell MG&nbsp;what package it needs to add
or delete.
<br>So I&nbsp;am not sure what deleting property really mean here?
<br>&nbsp;
<p>Christian/Tom,
<br>Do you happen to know the thread that this change was discussed and
consensus was
<br>reached?
<p>Thanks
<br>Chuong
<p>Christian Groves wrote:
<blockquote TYPE=CITE>G'Day Tom,
<p>I don't think we can accept the exception for property parameters this
<br>would be a big problem for interoperabilty between v1 and v2. Having
to
<br>repeat the entire descriptor when we want to change one item I agree
is
<br>not nice but the list came to a consensus that it was the way it would
<br>work.
<p>The other problem arises is that if&nbsp; "leave a property absent from
a
<br>descriptor" means keep the property as is, how do you then describe
how
<br>to delete a single property from a descriptor?
<p>Regards, christian
<p>Tom-PT Taylor wrote:
<br>>
<br>> This seems like a practical solution for LocalControl, but if we
accept it,
<br>> we have to change the text of the Recommendation, meaning that it
only holds
<br>> for H.248v2.&nbsp; I'll note that we have a real problem of interoperability
<br>> here.&nbsp; My previous note on the interpretation of this clause
presented three
<br>> alternatives, and I got E-mails (one private) in support of all three
of
<br>> them.
<br>>
<br>> I don't quite see Wayne's point on the Signals and Events descriptors.&nbsp;
In
<br>> both cases, the semantics of the situation require the repetition
of all of
<br>> the signals/events you want to keep.&nbsp; You also need at least
the KeepActive
<br>> parameter where it applies to signals.&nbsp; Are you saying, Wayne,
that once an
<br>> event or signal is specified, then if it is retained in replacement
<br>> descriptors it is unnecessary to respecify all the parameters that
went
<br>> along with it the first time?&nbsp; I could live with that as an
IG
<br>> clarification.&nbsp; Other views?
<br>>
<br>> -----Original Message-----
<br>> From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>> Sent: Tuesday, January 29, 2002 9:40 AM
<br>> To: 'megaco@ietf.org'
<br>> Subject: Re: [Megaco] Query about local control descriptor properties
<br>>
<br>>
<br>> I agreed w/Wayne on option d which is how it was before v1 came out.
<br>> Then we got into these Reserve parameters discussion and changes
<br>> but I didn't think the statement should apply to Property parameters.
<br>>
<br>> Wayne Cutler wrote:
<br>>
<br>> What about an option d) that would regard an absent Property as meaning
<br>> "leave the existing value unchanged"?
<br>> As a related question, I note that section 7.1.7 (Local Control Desc.)of
<br>> the spec.
<br>> says that:-
<br>> "A new setting of the LocalControl Descriptor completely replaces
the
<br>> previous setting of that descriptor in the MG.&nbsp; Thus to retain
information
<br>> from
<br>> the previous setting the MGC must include that information in the
new
<br>> setting".
<br>> Similar statements are made for the Events &amp; Signals Descriptors.
<br>> In the case where an MG supports a number of packages, this text
is saying
<br>> that an MGC
<br>> wishing to change data/attributes in one Package in a given Descriptor
is
<br>> forced to repeat any previous data against any other Packages. This
is
<br>> perverse. So, can this text be qualified to say that the new Descriptor
<br>> replaces only data relating to Packages present in the new/latest
message?
<br>> Regards,
<br>> Wayne.
<br>> ------------
<br>> This e-mail and any attachments are confidential.&nbsp; If you are
not the
<br>> intended recipient, please notify us immediately by reply e-mail
and then
<br>> delete this message from your system. Do not copy this e-mail or
any
<br>> attachments, use the contents for any purpose, or disclose the contents
to
<br>> any other person: to do so could be a breach of confidence.
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a>
<br>> --
<br>>&nbsp;&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>>&nbsp;&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
<br>>&nbsp;&nbsp; **** The opinions expressed are not those of Alcatel
USA, Inc ****
<br>>
<br>>
<br>> _______________________________________________
<br>> Megaco mailing list
<br>> Megaco@ietf.org
<br>> <a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
&nbsp; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet: Chuong.Nguyen@usa.alcatel.com
&nbsp; 1000 Coit Road Plano, Texas 75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613
&nbsp; **** The opinions expressed are not those of Alcatel USA, Inc ****</pre>
&nbsp;</html>

--------------888EC4B6B622E16B6D1F10C2--


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



From megaco-admin@ietf.org  Wed Jan 30 23:57:05 2002
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 XAA10650
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:57:05 -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 XAA11945;
	Wed, 30 Jan 2002 23:43:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11879
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:15 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10258
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:09 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04626;
	Thu, 31 Jan 2002 15:41:46 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06081;
	Thu, 31 Jan 2002 15:43:08 +1100 (EST)
Message-ID: <3C588708.6A7033A0@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:51:36 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] H.248 Annex M.ka KeepAlive package
References: <3C581EE1.F11D8357@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

How about 1/10 sec that gives you 6553 sec? I can see anybody sending a
keep alive every 1ms.

Cheers, Christian

Terry L Anderson wrote:
> 
> I submitted an editors draft of the proposed H.248 Annex M.ka KeepAlive
> Package to the Geneva meeting.  It appears as TD 2-014 in WP2.  But
> recently I have received a comment about the Maximum Inactivity Time
> being in integral units of seconds.  High capacity MGs might find 1
> second as being too long.  It was proposed that we define the unit to be
> "hundredths of seconds" as it is for duration of TO signals.  Leaving
> the range as 0..65535 still permits a inactive time as long as 655 sec
> or over 10 min which seems more than adequate.  I will propose that
> change to hundredths of sec when the document is discussed in Geneva.
> Does anyone have a concern with the new range being
> 1/100 sec to 655 sec.  ?



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


From daemon@optimus.ietf.org  Wed Jan 30 23:57:10 2002
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 XAA10662
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:57:05 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12376
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 23:57:09 -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 XAA11945;
	Wed, 30 Jan 2002 23:43:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11879
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:15 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10258
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:09 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04626;
	Thu, 31 Jan 2002 15:41:46 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06081;
	Thu, 31 Jan 2002 15:43:08 +1100 (EST)
Message-ID: <3C588708.6A7033A0@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:51:36 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco Mailing List <megaco@ietf.org>
Subject: Re: [Megaco] H.248 Annex M.ka KeepAlive package
References: <3C581EE1.F11D8357@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

How about 1/10 sec that gives you 6553 sec? I can see anybody sending a
keep alive every 1ms.

Cheers, Christian

Terry L Anderson wrote:
> 
> I submitted an editors draft of the proposed H.248 Annex M.ka KeepAlive
> Package to the Geneva meeting.  It appears as TD 2-014 in WP2.  But
> recently I have received a comment about the Maximum Inactivity Time
> being in integral units of seconds.  High capacity MGs might find 1
> second as being too long.  It was proposed that we define the unit to be
> "hundredths of seconds" as it is for duration of TO signals.  Leaving
> the range as 0..65535 still permits a inactive time as long as 655 sec
> or over 10 min which seems more than adequate.  I will propose that
> change to hundredths of sec when the document is discussed in Geneva.
> Does anyone have a concern with the new range being
> 1/100 sec to 655 sec.  ?



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



From megaco-admin@ietf.org  Wed Jan 30 23:59:14 2002
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 XAA10717
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:59:14 -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 XAA11948;
	Wed, 30 Jan 2002 23:43:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11884
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:16 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10260
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04630;
	Thu, 31 Jan 2002 15:41:48 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06086;
	Thu, 31 Jan 2002 15:43:09 +1100 (EST)
Message-ID: <3C588803.11CF5ED0@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:55:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com> <3C58155F.1F1FC3AB@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

The behaviour already is mentioned in 8.0 the paragraph after "At the
first failing Command...". States: "Commands may be marked as "Optional"
which can override this behaviour -  if a command marked as Optional
results in an error, subsequent commands in the Transaction will be
executed.  If a command fails, the MG shall as far as possible restore
the state that existed prior to the attempted execution of the command
before continuing with command processing."

Regards, Christian

Terry L Anderson wrote:
> 
> The statement (in 8.0) IS misleading but your understanding is also incorrect.
> 
> 8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
> the entire Transaction (not just the action).
> 
> Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.
> 
> Do folks think this sentence should be corrected in IG?
> 
> vidya g wrote:
> 
> > Hi all
> >
> >   In RFC, page number 61 it says that
> >
> >  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
> >
> >   This statement is some what confusing. What I understand is even if a non optional
> > command fails in an action, the action will be cancelled and the next action will be taken
> > for processing and the commands in that action will be processed.. is that right .. ?
> >
> > vdy
> >
> >
> > _______________________________________________
> > 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


From daemon@optimus.ietf.org  Wed Jan 30 23:59:15 2002
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 XAA10727
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:59:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12417
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 23:59:18 -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 XAA11948;
	Wed, 30 Jan 2002 23:43:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11884
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:16 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10260
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:10 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04630;
	Thu, 31 Jan 2002 15:41:48 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06086;
	Thu, 31 Jan 2002 15:43:09 +1100 (EST)
Message-ID: <3C588803.11CF5ED0@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:55:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com> <3C58155F.1F1FC3AB@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Terry,

The behaviour already is mentioned in 8.0 the paragraph after "At the
first failing Command...". States: "Commands may be marked as "Optional"
which can override this behaviour -  if a command marked as Optional
results in an error, subsequent commands in the Transaction will be
executed.  If a command fails, the MG shall as far as possible restore
the state that existed prior to the attempted execution of the command
before continuing with command processing."

Regards, Christian

Terry L Anderson wrote:
> 
> The statement (in 8.0) IS misleading but your understanding is also incorrect.
> 
> 8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
> the entire Transaction (not just the action).
> 
> Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.
> 
> Do folks think this sentence should be corrected in IG?
> 
> vidya g wrote:
> 
> > Hi all
> >
> >   In RFC, page number 61 it says that
> >
> >  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
> >
> >   This statement is some what confusing. What I understand is even if a non optional
> > command fails in an action, the action will be cancelled and the next action will be taken
> > for processing and the commands in that action will be processed.. is that right .. ?
> >
> > vdy
> >
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Wed Jan 30 23:59:20 2002
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 XAA10745
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:59:20 -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 XAA12031;
	Wed, 30 Jan 2002 23:43:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11935
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:19 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10263
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:12 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04634;
	Thu, 31 Jan 2002 15:41:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06059;
	Thu, 31 Jan 2002 15:43:05 +1100 (EST)
Message-ID: <3C588577.50A2E5C7@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:44:55 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com> <3C578955.FB4057EE@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Christer,

I think we still need stream ID 1 as an instance of local and remote is
associated with a single stream. The rules below give stream ID 0 a
slightly different semantic.

Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> I think the proposal sounds good. However, wouldn't it be more clear if
> stream ID 0 was default, instead of stream ID 1? Just a detail, but
> still...
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> Tom-PT Taylor wrote:
> >
> > Darn: hit the wrong button again.
> >
> > Anyway, if everyone sees it this way let's go for it.  Do we need text
> > changes?
> >
> > -----Original Message-----
> > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > Sent: Tuesday, January 29, 2002 10:22 PM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> > Subject: Re: [Megaco] Query about streamID 0
> >
> > G'Day
> >
> > My understanding of the combinations are the following:
> >
> > event (no stream) - detect an event on the termination irrespective of
> > what streams are on the termination. The MG will insert the correct
> > detection equipment. ie. DTMF detector on the audio stream/s.
> > event (stream ID 0) - as above
> > event (stream ID x) - detect the event only on the particular streamID x
> >
> > signal (no stream) - play the signal on the termination irrespective of
> > what streams are on the termination. The MG will insert the correct
> > playout equipment. Play a video on the video stream.
> > signal (stream ID 0) - as above
> > signal (stream ID x) - the signal only on the particular streamID x
> >
> > Default streamID=1 if you leave the stream descriptor as just specify
> > local and remote.
> >
> > Now this is all rather acedemic if the termination only ever has one
> > stream.
> > I can't see the problem. What am I missing?
> >
> > Regards, Christian
> >
> > Tom-PT Taylor wrote:
> > >
> > > Your proposal that the default streamId (0) means "all active streams" is
> > a
> > > workable one for events, especially if the actual stream on which the
> > signal
> > > occurred is reported in the Notify.  I suspect signals are a bit more
> > > problematic -- you only want a signal to go out on one stream, usually.
> > >
> > > I'm still troubled by the implications of assuming that you can't detect
> > > events on a stream not specifically defined at a given termination.  I'm
> > > mainly worried about the NULL context.  The simplest way around that
> > concern
> > > is to assume that the media properties of physical terminations are
> > > pre-provisioned.  In fact, people must be making that asumption now --
> > > otherwise there would have been a lot more interest in my draft on SDP
> > > attributes for TDM.  I intend to revive that draft shortly, by the way.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Monday, January 28, 2002 8:36 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > My comments embedded.....
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS
> > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > You've opened up a good discussion.
> > >
> > > 1. You are right about streams also being bound to terminations.  Aside
> > from
> > > being able to define streams when the termination is in the NULL context,
> > we
> > > have the provision that a termination retains its current streams when it
> > is
> > > moved from one context to another.
> > >
> > > 2. I differ slightly on the interpretation of streams versus actual
> > enabling
> > > of flows, but this is at an abstract level that I don't think makes any
> > > difference in behaviour.  My interpretation is that as soon as a stream is
> > > created in a context, it introduces the potential of bi-directional
> > exchange
> > > of media between the context and each termination in it.  Of course, to
> > have
> > > an actual flow in each direction, you need the conditions you've stated:
> > > Local and Remote defined on at least two terminations and sendRecv set on
> > > both.
> > >
> > > The real issue is whether a termination can detect events and send signals
> > > on a stream not explicitly defined at that termination.  I think this is a
> > > matter of convention -- we have to decide one way or the other.  I'll
> > point
> > > out that it has implications for detection of DTMF events in the NULL
> > > context.
> > > <KN> I feel as per the convention and to some extent simple logic it
> > > would be appropriate to allow terminations to detect events and signals
> > > on only those streams which are explicitly defined on them. More so,
> > because
> > > in cases where there are multiple streams on multiple terminations
> > > Eg:
> > > A context with 4 terminations T1, T2, T3....
> > > Streams 1 and 2 on T1,3 and 2 on T3.
> > > T2 has currently no explicit stream defined on it.
> > >
> > >           -------------------
> > >           |              |
> > >      T1----------1         -------T2
> > >           |  |            |
> > >           |  |--2_       |
> > >           |      |       |
> > >           |      |       |
> > >           |      |       |
> > >           |      |    3--------T3
> > >           |      |       | |
> > >           |       |____2--| |
> > >           |              |
> > >           -------------------
> > > It would be questionable to expect the following combinations:
> > > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > > -    T1 detect events or apply signals on stream 3.
> > > -    T3 detect events or apply signals on stream 1.
> > > At the current moment these terminations are completely oblivious of the
> > > stream IDs refered.
> > >
> > > 3. I think I've made the point that H.248v1 requires that most of the
> > events
> > > and signals we have already defined must be applied to a non-zero stream.
> > > Hence requiring that packages indicate which ones apply to stream 0 is not
> > a
> > > change in the protocol, just a clarification.
> > >
> > > I do have a couple of alternatives which indeed would be changes to the
> > > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> > >
> > >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > > event or signal, or
> > >  (b) If only one stream is defined on the specific termination, an
> > > unspecified streamId selects that stream.
> > > <KN> I have an opinion.....How does MGC tell MG to detect events
> > > on all active streams on a termination. Does MGC have to repeat event IDs
> > > in the event descriptor with all active stream IDs as parameters. Protocol
> > > does not introduce any concept of stream ID as "*"(ALL).
> > > >From the current text, the stream ID 0 seems to be solving this problem.
> > > Stream ID 0 is the default stream on all terminations,i.e., does not need
> > to
> > > be created explicitly through media descriptor (valid).
> > > If event descriptor contains stream ID 0, "it does not refer to any
> > specific
> > > stream"(valid) but does refer to the termination as a whole.
> > > The inference is that detect events on all streams (currently active on
> > > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > > nonstream-specific terminations like NAS). If the event is detected on any
> > > stream, report the same to MGC with the specific stream ID.
> > > A similar interpretation can also be made for signals.
> > > And, the default stream ID remains 0 for events/ signals, but 1 for
> > > media descriptor.
> > >
> > > Actually, I think people are going to have to bite the bullet and start
> > > specifying streamIds eventually if they don't do it now.  Choosing
> > > alternative (b) would buy a bit of time.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Thursday, January 24, 2002 5:49 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > I would like to add more to your comments about streams being context
> > > properties.
> > >
> > > Streams are as good properties of the terminations too....
> > > -    A stream can be created on a termination in the Null Context.
> > >      (almost in all call flows including those in the RFC 3015 stream
> > > descriptor
> > >      or the default stream 1 is sent by the MGC in MODIFY command in the
> > >      Null context).
> > > -    To create a bi-directional stream, we need to send stream descriptor
> > >      with (at the least mode=sendrecv) for both the terminations in the
> > > context.
> > >      The bi-directional stream cannot be created by just refering it in
> > one
> > >      termination.
> > >
> > > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > > stream=1 (something similar to a unidirectional media flow) by specifying
> > > stream descriptor for termination T1. At this point it would be incorrect
> > > to assume that termination T2 can detect events or apply signals on the
> > > stream
> > > 1.
> > > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > > totally
> > > oblivious of stream 1).
> > > To detect events or signals on the stream at T2, we need to first make T2
> > > aware
> > > of the stream.
> > >
> > > Although, it would be a good idea to specify in package definitions about
> > > which event/ signals etc. would apply on streamID=0, this would amount to
> > > changing
> > > the protocol....are you considering it for version2.
> > >
> > > Please comment....
> > >
> > > Thanks & Regards,
> > > -Kapil Nayar
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS
> > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > Hi.  See new comments [PTT2] below.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Wednesday, January 23, 2002 8:55 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > my comments embedded.
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > > cc:
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > Hi.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Tuesday, January 22, 2002 8:54 AM
> > > To: 'megaco@ietf.org'
> > > Subject: [Megaco] Query about streamID 0
> > >
> > > Hi Tom & list,
> > >
> > > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> > mentions:
> > >
> > > "The default streamID is 0, indicating that the event to be detected is
> > not
> > > related to a particular media stream."
> > >
> > > Does the "streamID 0" refer to the complete termination (which means all
> > the
> > > active streams on the termination) ?
> > >
> > > [PTT] No.  It really means as it says, that the event or signal is not
> > > associated with any specific stream.  An example is an electrical signal
> > > such as off-hook.
> > > [KN] Does that mean that stream 0 is possible for only physical
> > > terminations,
> > > since electrical signals are more appropriate for physical terminations.
> > > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > > relate to specific streams.  Electrical signals were just an example.  I
> > > suspect I could find a good example in one of my NAS packages of something
> > > more abstract, but I won't take the time.  Just accept that we don't want
> > to
> > > foreclose the possibility of using this on ephemerals.
> > >
> > > And, if some event is required to be detected on the ephemeral
> > termination,
> > > the event descriptor should clearly identify which stream it is required
> > on.
> > > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > > without
> > > stream ID parameter since that defaults to stream ID 0, which may not be
> > > applicable).
> > > [PTT2] That has to be thought through for all terminations.
> > > *** IG issue: It does strike me that you can know in advance (by
> > definition
> > > of the event or signal) whether streamId=0 will apply.  We should
> > therefore
> > > make it requirement to specify this in package definitions.
> > >
> > > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > > associated with an audio stream.  (But I bet nobody has bothered to
> > specify
> > > stream 1 for DTMF events when they are using a default streamId for audio.
> > > They should!)
> > > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > > descriptor,
> > > MGC should have already created the stream 1 thru' the media descriptor
> > > in a previous command?
> > > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > > descriptor, but just specify Local, Remote, and LocalControl.
> > > *** IG issue: would it make more sense to have streamId=0 as the default
> > for
> > > signals and events, or have streamId=1 as the default?
> > >
> > > A related doubt is...if an event descriptor refers
> > > to a stream ID which is not previously created by the MGC, MG should
> > > return an error.
> > > [PTT2] I'm not sure.  Remember that streamIds are really a context
> > property.
> > > If a given streamId is supported somewhere in the context, then referring
> > to
> > > that streamId at a given termination implies that the termination also
> > > supports it.  That means it could detect events or send signals on the
> > > stream even if it doesn't know how to handle the media flows on that
> > stream.
> > > I suppose if this is the first mention of the streamId in the context, it
> > > might be appropriate to reject the command.
> > > ***IG issue: The implication is that within any command, Stream
> > Descriptors
> > > for new streams MUST appear before Signals and Events descriptors
> > referring
> > > to those StreamIds.
> > >
> > > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > > descriptor, event descriptor, signal descriptor ?
> > >
> > > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > > consistent with the meaning of that streamId for events and signals.  We
> > > should have a note to the effect that streamId=0 is reserved in sections
> > > 7.1.4 (for thoroughness) and 7.1.6.
> > >
> > > You can specify streamId=0 in a signals or events descriptor, but that's
> > the
> > > same as leaving it unspecified.
> > >
> > > Please reply back...
> > >
> > > Thanks,
> > > Kapil Nayar
> > >
> > > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> > Limited
> > > (HSS) and is intended solely for the use of the individual  to whom it is
> > > addressed. It may contain  privileged or confidential information  and
> > > should
> > > not be circulated or used for any purpose other than for what it is
> > > intended.If
> > > you have received this message in error, please notify the originator
> > > immediately. If you are not the intended recipient, you are notified that
> > > you
> > > are strictly prohibited from using, copying, altering, or disclosing the
> > > contents of this message. HSS accepts no responsibility for loss or damage
> > > arising from the use of the information transimitted by this email
> > including
> > > damage from virus."
> > >
> > > _______________________________________________
> > > 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



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


From daemon@optimus.ietf.org  Wed Jan 30 23:59:26 2002
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 XAA10755
	for <megaco-archive@odin.ietf.org>; Wed, 30 Jan 2002 23:59:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA12434
	for megaco-archive@odin.ietf.org; Wed, 30 Jan 2002 23:59:24 -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 XAA12031;
	Wed, 30 Jan 2002 23:43:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11935
	for <megaco@optimus.ietf.org>; Wed, 30 Jan 2002 23:43:19 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10263
	for <megaco@ietf.org>; Wed, 30 Jan 2002 23:43:12 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id PAA04634;
	Thu, 31 Jan 2002 15:41:49 +1100 (EST)
Received: from ericsson.com.au ([146.11.236.100])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id PAA06059;
	Thu, 31 Jan 2002 15:43:05 +1100 (EST)
Message-ID: <3C588577.50A2E5C7@ericsson.com.au>
Date: Thu, 31 Jan 2002 10:44:55 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com> <3C578955.FB4057EE@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

G'Day Christer,

I think we still need stream ID 1 as an instance of local and remote is
associated with a single stream. The rules below give stream ID 0 a
slightly different semantic.

Christian

Christer Holmberg wrote:
> 
> Hi,
> 
> I think the proposal sounds good. However, wouldn't it be more clear if
> stream ID 0 was default, instead of stream ID 1? Just a detail, but
> still...
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> Tom-PT Taylor wrote:
> >
> > Darn: hit the wrong button again.
> >
> > Anyway, if everyone sees it this way let's go for it.  Do we need text
> > changes?
> >
> > -----Original Message-----
> > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > Sent: Tuesday, January 29, 2002 10:22 PM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> > Subject: Re: [Megaco] Query about streamID 0
> >
> > G'Day
> >
> > My understanding of the combinations are the following:
> >
> > event (no stream) - detect an event on the termination irrespective of
> > what streams are on the termination. The MG will insert the correct
> > detection equipment. ie. DTMF detector on the audio stream/s.
> > event (stream ID 0) - as above
> > event (stream ID x) - detect the event only on the particular streamID x
> >
> > signal (no stream) - play the signal on the termination irrespective of
> > what streams are on the termination. The MG will insert the correct
> > playout equipment. Play a video on the video stream.
> > signal (stream ID 0) - as above
> > signal (stream ID x) - the signal only on the particular streamID x
> >
> > Default streamID=1 if you leave the stream descriptor as just specify
> > local and remote.
> >
> > Now this is all rather acedemic if the termination only ever has one
> > stream.
> > I can't see the problem. What am I missing?
> >
> > Regards, Christian
> >
> > Tom-PT Taylor wrote:
> > >
> > > Your proposal that the default streamId (0) means "all active streams" is
> > a
> > > workable one for events, especially if the actual stream on which the
> > signal
> > > occurred is reported in the Notify.  I suspect signals are a bit more
> > > problematic -- you only want a signal to go out on one stream, usually.
> > >
> > > I'm still troubled by the implications of assuming that you can't detect
> > > events on a stream not specifically defined at a given termination.  I'm
> > > mainly worried about the NULL context.  The simplest way around that
> > concern
> > > is to assume that the media properties of physical terminations are
> > > pre-provisioned.  In fact, people must be making that asumption now --
> > > otherwise there would have been a lot more interest in my draft on SDP
> > > attributes for TDM.  I intend to revive that draft shortly, by the way.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Monday, January 28, 2002 8:36 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > My comments embedded.....
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS
> > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > You've opened up a good discussion.
> > >
> > > 1. You are right about streams also being bound to terminations.  Aside
> > from
> > > being able to define streams when the termination is in the NULL context,
> > we
> > > have the provision that a termination retains its current streams when it
> > is
> > > moved from one context to another.
> > >
> > > 2. I differ slightly on the interpretation of streams versus actual
> > enabling
> > > of flows, but this is at an abstract level that I don't think makes any
> > > difference in behaviour.  My interpretation is that as soon as a stream is
> > > created in a context, it introduces the potential of bi-directional
> > exchange
> > > of media between the context and each termination in it.  Of course, to
> > have
> > > an actual flow in each direction, you need the conditions you've stated:
> > > Local and Remote defined on at least two terminations and sendRecv set on
> > > both.
> > >
> > > The real issue is whether a termination can detect events and send signals
> > > on a stream not explicitly defined at that termination.  I think this is a
> > > matter of convention -- we have to decide one way or the other.  I'll
> > point
> > > out that it has implications for detection of DTMF events in the NULL
> > > context.
> > > <KN> I feel as per the convention and to some extent simple logic it
> > > would be appropriate to allow terminations to detect events and signals
> > > on only those streams which are explicitly defined on them. More so,
> > because
> > > in cases where there are multiple streams on multiple terminations
> > > Eg:
> > > A context with 4 terminations T1, T2, T3....
> > > Streams 1 and 2 on T1,3 and 2 on T3.
> > > T2 has currently no explicit stream defined on it.
> > >
> > >           -------------------
> > >           |              |
> > >      T1----------1         -------T2
> > >           |  |            |
> > >           |  |--2_       |
> > >           |      |       |
> > >           |      |       |
> > >           |      |       |
> > >           |      |    3--------T3
> > >           |      |       | |
> > >           |       |____2--| |
> > >           |              |
> > >           -------------------
> > > It would be questionable to expect the following combinations:
> > > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > > -    T1 detect events or apply signals on stream 3.
> > > -    T3 detect events or apply signals on stream 1.
> > > At the current moment these terminations are completely oblivious of the
> > > stream IDs refered.
> > >
> > > 3. I think I've made the point that H.248v1 requires that most of the
> > events
> > > and signals we have already defined must be applied to a non-zero stream.
> > > Hence requiring that packages indicate which ones apply to stream 0 is not
> > a
> > > change in the protocol, just a clarification.
> > >
> > > I do have a couple of alternatives which indeed would be changes to the
> > > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> > >
> > >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > > event or signal, or
> > >  (b) If only one stream is defined on the specific termination, an
> > > unspecified streamId selects that stream.
> > > <KN> I have an opinion.....How does MGC tell MG to detect events
> > > on all active streams on a termination. Does MGC have to repeat event IDs
> > > in the event descriptor with all active stream IDs as parameters. Protocol
> > > does not introduce any concept of stream ID as "*"(ALL).
> > > >From the current text, the stream ID 0 seems to be solving this problem.
> > > Stream ID 0 is the default stream on all terminations,i.e., does not need
> > to
> > > be created explicitly through media descriptor (valid).
> > > If event descriptor contains stream ID 0, "it does not refer to any
> > specific
> > > stream"(valid) but does refer to the termination as a whole.
> > > The inference is that detect events on all streams (currently active on
> > > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > > nonstream-specific terminations like NAS). If the event is detected on any
> > > stream, report the same to MGC with the specific stream ID.
> > > A similar interpretation can also be made for signals.
> > > And, the default stream ID remains 0 for events/ signals, but 1 for
> > > media descriptor.
> > >
> > > Actually, I think people are going to have to bite the bullet and start
> > > specifying streamIds eventually if they don't do it now.  Choosing
> > > alternative (b) would buy a bit of time.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Thursday, January 24, 2002 5:49 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > I would like to add more to your comments about streams being context
> > > properties.
> > >
> > > Streams are as good properties of the terminations too....
> > > -    A stream can be created on a termination in the Null Context.
> > >      (almost in all call flows including those in the RFC 3015 stream
> > > descriptor
> > >      or the default stream 1 is sent by the MGC in MODIFY command in the
> > >      Null context).
> > > -    To create a bi-directional stream, we need to send stream descriptor
> > >      with (at the least mode=sendrecv) for both the terminations in the
> > > context.
> > >      The bi-directional stream cannot be created by just refering it in
> > one
> > >      termination.
> > >
> > > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > > stream=1 (something similar to a unidirectional media flow) by specifying
> > > stream descriptor for termination T1. At this point it would be incorrect
> > > to assume that termination T2 can detect events or apply signals on the
> > > stream
> > > 1.
> > > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > > totally
> > > oblivious of stream 1).
> > > To detect events or signals on the stream at T2, we need to first make T2
> > > aware
> > > of the stream.
> > >
> > > Although, it would be a good idea to specify in package definitions about
> > > which event/ signals etc. would apply on streamID=0, this would amount to
> > > changing
> > > the protocol....are you considering it for version2.
> > >
> > > Please comment....
> > >
> > > Thanks & Regards,
> > > -Kapil Nayar
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS
> > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > Hi.  See new comments [PTT2] below.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Wednesday, January 23, 2002 8:55 AM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] Query about streamID 0
> > >
> > > Hi Tom
> > >
> > > my comments embedded.
> > >
> > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> > >
> > > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > > cc:
> > >
> > > Subject:  RE: [Megaco] Query about streamID 0
> > >
> > > Hi.
> > >
> > > -----Original Message-----
> > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > Sent: Tuesday, January 22, 2002 8:54 AM
> > > To: 'megaco@ietf.org'
> > > Subject: [Megaco] Query about streamID 0
> > >
> > > Hi Tom & list,
> > >
> > > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> > mentions:
> > >
> > > "The default streamID is 0, indicating that the event to be detected is
> > not
> > > related to a particular media stream."
> > >
> > > Does the "streamID 0" refer to the complete termination (which means all
> > the
> > > active streams on the termination) ?
> > >
> > > [PTT] No.  It really means as it says, that the event or signal is not
> > > associated with any specific stream.  An example is an electrical signal
> > > such as off-hook.
> > > [KN] Does that mean that stream 0 is possible for only physical
> > > terminations,
> > > since electrical signals are more appropriate for physical terminations.
> > > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > > relate to specific streams.  Electrical signals were just an example.  I
> > > suspect I could find a good example in one of my NAS packages of something
> > > more abstract, but I won't take the time.  Just accept that we don't want
> > to
> > > foreclose the possibility of using this on ephemerals.
> > >
> > > And, if some event is required to be detected on the ephemeral
> > termination,
> > > the event descriptor should clearly identify which stream it is required
> > on.
> > > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > > without
> > > stream ID parameter since that defaults to stream ID 0, which may not be
> > > applicable).
> > > [PTT2] That has to be thought through for all terminations.
> > > *** IG issue: It does strike me that you can know in advance (by
> > definition
> > > of the event or signal) whether streamId=0 will apply.  We should
> > therefore
> > > make it requirement to specify this in package definitions.
> > >
> > > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > > associated with an audio stream.  (But I bet nobody has bothered to
> > specify
> > > stream 1 for DTMF events when they are using a default streamId for audio.
> > > They should!)
> > > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > > descriptor,
> > > MGC should have already created the stream 1 thru' the media descriptor
> > > in a previous command?
> > > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > > descriptor, but just specify Local, Remote, and LocalControl.
> > > *** IG issue: would it make more sense to have streamId=0 as the default
> > for
> > > signals and events, or have streamId=1 as the default?
> > >
> > > A related doubt is...if an event descriptor refers
> > > to a stream ID which is not previously created by the MGC, MG should
> > > return an error.
> > > [PTT2] I'm not sure.  Remember that streamIds are really a context
> > property.
> > > If a given streamId is supported somewhere in the context, then referring
> > to
> > > that streamId at a given termination implies that the termination also
> > > supports it.  That means it could detect events or send signals on the
> > > stream even if it doesn't know how to handle the media flows on that
> > stream.
> > > I suppose if this is the first mention of the streamId in the context, it
> > > might be appropriate to reject the command.
> > > ***IG issue: The implication is that within any command, Stream
> > Descriptors
> > > for new streams MUST appear before Signals and Events descriptors
> > referring
> > > to those StreamIds.
> > >
> > > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > > descriptor, event descriptor, signal descriptor ?
> > >
> > > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > > consistent with the meaning of that streamId for events and signals.  We
> > > should have a note to the effect that streamId=0 is reserved in sections
> > > 7.1.4 (for thoroughness) and 7.1.6.
> > >
> > > You can specify streamId=0 in a signals or events descriptor, but that's
> > the
> > > same as leaving it unspecified.
> > >
> > > Please reply back...
> > >
> > > Thanks,
> > > Kapil Nayar
> > >
> > > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> > Limited
> > > (HSS) and is intended solely for the use of the individual  to whom it is
> > > addressed. It may contain  privileged or confidential information  and
> > > should
> > > not be circulated or used for any purpose other than for what it is
> > > intended.If
> > > you have received this message in error, please notify the originator
> > > immediately. If you are not the intended recipient, you are notified that
> > > you
> > > are strictly prohibited from using, copying, altering, or disclosing the
> > > contents of this message. HSS accepts no responsibility for loss or damage
> > > arising from the use of the information transimitted by this email
> > including
> > > damage from virus."
> > >
> > > _______________________________________________
> > > 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



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



From megaco-admin@ietf.org  Thu Jan 31 02:06:35 2002
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 CAA20689
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 02:06:35 -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 BAA26515;
	Thu, 31 Jan 2002 01:53:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA26484
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 01:53:31 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12266
	for <megaco@ietf.org>; Thu, 31 Jan 2002 01:53:28 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0V6rBC06748;
	Thu, 31 Jan 2002 07:53:11 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0V6rBr6025887;
	Thu, 31 Jan 2002 08:53:11 +0200 (EET)
Message-ID: <3C58E9D5.7D34A4C9@lmf.ericsson.se>
Date: Thu, 31 Jan 2002 08:53:09 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com> <3C578955.FB4057EE@lmf.ericsson.se> <3C588577.50A2E5C7@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I think we still need stream ID 1 as an instance of local and remote is
>associated with a single stream. The rules below give stream ID 0 a
>slightly different semantic.

True, and it would mean that one must always use a stream descriptor for
a non-zero streamID (currently it's not needed for streamID 1, since
it's default). I just thought it would be more clear...

Regards,

Christer Holmberg
Ericsson Finland



> 
> Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I think the proposal sounds good. However, wouldn't it be more clear if
> > stream ID 0 was default, instead of stream ID 1? Just a detail, but
> > still...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > Darn: hit the wrong button again.
> > >
> > > Anyway, if everyone sees it this way let's go for it.  Do we need text
> > > changes?
> > >
> > > -----Original Message-----
> > > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > > Sent: Tuesday, January 29, 2002 10:22 PM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> > > Subject: Re: [Megaco] Query about streamID 0
> > >
> > > G'Day
> > >
> > > My understanding of the combinations are the following:
> > >
> > > event (no stream) - detect an event on the termination irrespective of
> > > what streams are on the termination. The MG will insert the correct
> > > detection equipment. ie. DTMF detector on the audio stream/s.
> > > event (stream ID 0) - as above
> > > event (stream ID x) - detect the event only on the particular streamID x
> > >
> > > signal (no stream) - play the signal on the termination irrespective of
> > > what streams are on the termination. The MG will insert the correct
> > > playout equipment. Play a video on the video stream.
> > > signal (stream ID 0) - as above
> > > signal (stream ID x) - the signal only on the particular streamID x
> > >
> > > Default streamID=1 if you leave the stream descriptor as just specify
> > > local and remote.
> > >
> > > Now this is all rather acedemic if the termination only ever has one
> > > stream.
> > > I can't see the problem. What am I missing?
> > >
> > > Regards, Christian
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > Your proposal that the default streamId (0) means "all active streams" is
> > > a
> > > > workable one for events, especially if the actual stream on which the
> > > signal
> > > > occurred is reported in the Notify.  I suspect signals are a bit more
> > > > problematic -- you only want a signal to go out on one stream, usually.
> > > >
> > > > I'm still troubled by the implications of assuming that you can't detect
> > > > events on a stream not specifically defined at a given termination.  I'm
> > > > mainly worried about the NULL context.  The simplest way around that
> > > concern
> > > > is to assume that the media properties of physical terminations are
> > > > pre-provisioned.  In fact, people must be making that asumption now --
> > > > otherwise there would have been a lot more interest in my draft on SDP
> > > > attributes for TDM.  I intend to revive that draft shortly, by the way.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Monday, January 28, 2002 8:36 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > My comments embedded.....
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS
> > > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > You've opened up a good discussion.
> > > >
> > > > 1. You are right about streams also being bound to terminations.  Aside
> > > from
> > > > being able to define streams when the termination is in the NULL context,
> > > we
> > > > have the provision that a termination retains its current streams when it
> > > is
> > > > moved from one context to another.
> > > >
> > > > 2. I differ slightly on the interpretation of streams versus actual
> > > enabling
> > > > of flows, but this is at an abstract level that I don't think makes any
> > > > difference in behaviour.  My interpretation is that as soon as a stream is
> > > > created in a context, it introduces the potential of bi-directional
> > > exchange
> > > > of media between the context and each termination in it.  Of course, to
> > > have
> > > > an actual flow in each direction, you need the conditions you've stated:
> > > > Local and Remote defined on at least two terminations and sendRecv set on
> > > > both.
> > > >
> > > > The real issue is whether a termination can detect events and send signals
> > > > on a stream not explicitly defined at that termination.  I think this is a
> > > > matter of convention -- we have to decide one way or the other.  I'll
> > > point
> > > > out that it has implications for detection of DTMF events in the NULL
> > > > context.
> > > > <KN> I feel as per the convention and to some extent simple logic it
> > > > would be appropriate to allow terminations to detect events and signals
> > > > on only those streams which are explicitly defined on them. More so,
> > > because
> > > > in cases where there are multiple streams on multiple terminations
> > > > Eg:
> > > > A context with 4 terminations T1, T2, T3....
> > > > Streams 1 and 2 on T1,3 and 2 on T3.
> > > > T2 has currently no explicit stream defined on it.
> > > >
> > > >           -------------------
> > > >           |              |
> > > >      T1----------1         -------T2
> > > >           |  |            |
> > > >           |  |--2_       |
> > > >           |      |       |
> > > >           |      |       |
> > > >           |      |       |
> > > >           |      |    3--------T3
> > > >           |      |       | |
> > > >           |       |____2--| |
> > > >           |              |
> > > >           -------------------
> > > > It would be questionable to expect the following combinations:
> > > > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > > > -    T1 detect events or apply signals on stream 3.
> > > > -    T3 detect events or apply signals on stream 1.
> > > > At the current moment these terminations are completely oblivious of the
> > > > stream IDs refered.
> > > >
> > > > 3. I think I've made the point that H.248v1 requires that most of the
> > > events
> > > > and signals we have already defined must be applied to a non-zero stream.
> > > > Hence requiring that packages indicate which ones apply to stream 0 is not
> > > a
> > > > change in the protocol, just a clarification.
> > > >
> > > > I do have a couple of alternatives which indeed would be changes to the
> > > > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> > > >
> > > >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > > > event or signal, or
> > > >  (b) If only one stream is defined on the specific termination, an
> > > > unspecified streamId selects that stream.
> > > > <KN> I have an opinion.....How does MGC tell MG to detect events
> > > > on all active streams on a termination. Does MGC have to repeat event IDs
> > > > in the event descriptor with all active stream IDs as parameters. Protocol
> > > > does not introduce any concept of stream ID as "*"(ALL).
> > > > >From the current text, the stream ID 0 seems to be solving this problem.
> > > > Stream ID 0 is the default stream on all terminations,i.e., does not need
> > > to
> > > > be created explicitly through media descriptor (valid).
> > > > If event descriptor contains stream ID 0, "it does not refer to any
> > > specific
> > > > stream"(valid) but does refer to the termination as a whole.
> > > > The inference is that detect events on all streams (currently active on
> > > > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > > > nonstream-specific terminations like NAS). If the event is detected on any
> > > > stream, report the same to MGC with the specific stream ID.
> > > > A similar interpretation can also be made for signals.
> > > > And, the default stream ID remains 0 for events/ signals, but 1 for
> > > > media descriptor.
> > > >
> > > > Actually, I think people are going to have to bite the bullet and start
> > > > specifying streamIds eventually if they don't do it now.  Choosing
> > > > alternative (b) would buy a bit of time.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Thursday, January 24, 2002 5:49 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > I would like to add more to your comments about streams being context
> > > > properties.
> > > >
> > > > Streams are as good properties of the terminations too....
> > > > -    A stream can be created on a termination in the Null Context.
> > > >      (almost in all call flows including those in the RFC 3015 stream
> > > > descriptor
> > > >      or the default stream 1 is sent by the MGC in MODIFY command in the
> > > >      Null context).
> > > > -    To create a bi-directional stream, we need to send stream descriptor
> > > >      with (at the least mode=sendrecv) for both the terminations in the
> > > > context.
> > > >      The bi-directional stream cannot be created by just refering it in
> > > one
> > > >      termination.
> > > >
> > > > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > > > stream=1 (something similar to a unidirectional media flow) by specifying
> > > > stream descriptor for termination T1. At this point it would be incorrect
> > > > to assume that termination T2 can detect events or apply signals on the
> > > > stream
> > > > 1.
> > > > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > > > totally
> > > > oblivious of stream 1).
> > > > To detect events or signals on the stream at T2, we need to first make T2
> > > > aware
> > > > of the stream.
> > > >
> > > > Although, it would be a good idea to specify in package definitions about
> > > > which event/ signals etc. would apply on streamID=0, this would amount to
> > > > changing
> > > > the protocol....are you considering it for version2.
> > > >
> > > > Please comment....
> > > >
> > > > Thanks & Regards,
> > > > -Kapil Nayar
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS
> > > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi.  See new comments [PTT2] below.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Wednesday, January 23, 2002 8:55 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > my comments embedded.
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > > > cc:
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Tuesday, January 22, 2002 8:54 AM
> > > > To: 'megaco@ietf.org'
> > > > Subject: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom & list,
> > > >
> > > > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> > > mentions:
> > > >
> > > > "The default streamID is 0, indicating that the event to be detected is
> > > not
> > > > related to a particular media stream."
> > > >
> > > > Does the "streamID 0" refer to the complete termination (which means all
> > > the
> > > > active streams on the termination) ?
> > > >
> > > > [PTT] No.  It really means as it says, that the event or signal is not
> > > > associated with any specific stream.  An example is an electrical signal
> > > > such as off-hook.
> > > > [KN] Does that mean that stream 0 is possible for only physical
> > > > terminations,
> > > > since electrical signals are more appropriate for physical terminations.
> > > > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > > > relate to specific streams.  Electrical signals were just an example.  I
> > > > suspect I could find a good example in one of my NAS packages of something
> > > > more abstract, but I won't take the time.  Just accept that we don't want
> > > to
> > > > foreclose the possibility of using this on ephemerals.
> > > >
> > > > And, if some event is required to be detected on the ephemeral
> > > termination,
> > > > the event descriptor should clearly identify which stream it is required
> > > on.
> > > > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > > > without
> > > > stream ID parameter since that defaults to stream ID 0, which may not be
> > > > applicable).
> > > > [PTT2] That has to be thought through for all terminations.
> > > > *** IG issue: It does strike me that you can know in advance (by
> > > definition
> > > > of the event or signal) whether streamId=0 will apply.  We should
> > > therefore
> > > > make it requirement to specify this in package definitions.
> > > >
> > > > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > > > associated with an audio stream.  (But I bet nobody has bothered to
> > > specify
> > > > stream 1 for DTMF events when they are using a default streamId for audio.
> > > > They should!)
> > > > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > > > descriptor,
> > > > MGC should have already created the stream 1 thru' the media descriptor
> > > > in a previous command?
> > > > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > > > descriptor, but just specify Local, Remote, and LocalControl.
> > > > *** IG issue: would it make more sense to have streamId=0 as the default
> > > for
> > > > signals and events, or have streamId=1 as the default?
> > > >
> > > > A related doubt is...if an event descriptor refers
> > > > to a stream ID which is not previously created by the MGC, MG should
> > > > return an error.
> > > > [PTT2] I'm not sure.  Remember that streamIds are really a context
> > > property.
> > > > If a given streamId is supported somewhere in the context, then referring
> > > to
> > > > that streamId at a given termination implies that the termination also
> > > > supports it.  That means it could detect events or send signals on the
> > > > stream even if it doesn't know how to handle the media flows on that
> > > stream.
> > > > I suppose if this is the first mention of the streamId in the context, it
> > > > might be appropriate to reject the command.
> > > > ***IG issue: The implication is that within any command, Stream
> > > Descriptors
> > > > for new streams MUST appear before Signals and Events descriptors
> > > referring
> > > > to those StreamIds.
> > > >
> > > > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > > > descriptor, event descriptor, signal descriptor ?
> > > >
> > > > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > > > consistent with the meaning of that streamId for events and signals.  We
> > > > should have a note to the effect that streamId=0 is reserved in sections
> > > > 7.1.4 (for thoroughness) and 7.1.6.
> > > >
> > > > You can specify streamId=0 in a signals or events descriptor, but that's
> > > the
> > > > same as leaving it unspecified.
> > > >
> > > > Please reply back...
> > > >
> > > > Thanks,
> > > > Kapil Nayar
> > > >
> > > > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> > > Limited
> > > > (HSS) and is intended solely for the use of the individual  to whom it is
> > > > addressed. It may contain  privileged or confidential information  and
> > > > should
> > > > not be circulated or used for any purpose other than for what it is
> > > > intended.If
> > > > you have received this message in error, please notify the originator
> > > > immediately. If you are not the intended recipient, you are notified that
> > > > you
> > > > are strictly prohibited from using, copying, altering, or disclosing the
> > > > contents of this message. HSS accepts no responsibility for loss or damage
> > > > arising from the use of the information transimitted by this email
> > > including
> > > > damage from virus."
> > > >
> > > > _______________________________________________
> > > > 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

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


From daemon@optimus.ietf.org  Thu Jan 31 03:02:00 2002
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 CAA20699
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 02:06:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA27209
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 02:06:37 -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 BAA26515;
	Thu, 31 Jan 2002 01:53:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA26484
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 01:53:31 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12266
	for <megaco@ietf.org>; Thu, 31 Jan 2002 01:53:28 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g0V6rBC06748;
	Thu, 31 Jan 2002 07:53:11 +0100 (MET)
Received: from lmf.ericsson.se (lmf04630pc.lmf.ericsson.se [131.160.30.135])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g0V6rBr6025887;
	Thu, 31 Jan 2002 08:53:11 +0200 (EET)
Message-ID: <3C58E9D5.7D34A4C9@lmf.ericsson.se>
Date: Thu, 31 Jan 2002 08:53:09 +0200
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'knayar@hss.hns.com'" <knayar@hss.hns.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <4D79C746863DD51197690002A52CDA000102AF46@zcard0kc.ca.nortel.com> <3C578955.FB4057EE@lmf.ericsson.se> <3C588577.50A2E5C7@ericsson.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit


Hi,

>I think we still need stream ID 1 as an instance of local and remote is
>associated with a single stream. The rules below give stream ID 0 a
>slightly different semantic.

True, and it would mean that one must always use a stream descriptor for
a non-zero streamID (currently it's not needed for streamID 1, since
it's default). I just thought it would be more clear...

Regards,

Christer Holmberg
Ericsson Finland



> 
> Christian
> 
> Christer Holmberg wrote:
> >
> > Hi,
> >
> > I think the proposal sounds good. However, wouldn't it be more clear if
> > stream ID 0 was default, instead of stream ID 1? Just a detail, but
> > still...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > Tom-PT Taylor wrote:
> > >
> > > Darn: hit the wrong button again.
> > >
> > > Anyway, if everyone sees it this way let's go for it.  Do we need text
> > > changes?
> > >
> > > -----Original Message-----
> > > From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
> > > Sent: Tuesday, January 29, 2002 10:22 PM
> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > Cc: 'knayar@hss.hns.com'; 'megaco@ietf.org'
> > > Subject: Re: [Megaco] Query about streamID 0
> > >
> > > G'Day
> > >
> > > My understanding of the combinations are the following:
> > >
> > > event (no stream) - detect an event on the termination irrespective of
> > > what streams are on the termination. The MG will insert the correct
> > > detection equipment. ie. DTMF detector on the audio stream/s.
> > > event (stream ID 0) - as above
> > > event (stream ID x) - detect the event only on the particular streamID x
> > >
> > > signal (no stream) - play the signal on the termination irrespective of
> > > what streams are on the termination. The MG will insert the correct
> > > playout equipment. Play a video on the video stream.
> > > signal (stream ID 0) - as above
> > > signal (stream ID x) - the signal only on the particular streamID x
> > >
> > > Default streamID=1 if you leave the stream descriptor as just specify
> > > local and remote.
> > >
> > > Now this is all rather acedemic if the termination only ever has one
> > > stream.
> > > I can't see the problem. What am I missing?
> > >
> > > Regards, Christian
> > >
> > > Tom-PT Taylor wrote:
> > > >
> > > > Your proposal that the default streamId (0) means "all active streams" is
> > > a
> > > > workable one for events, especially if the actual stream on which the
> > > signal
> > > > occurred is reported in the Notify.  I suspect signals are a bit more
> > > > problematic -- you only want a signal to go out on one stream, usually.
> > > >
> > > > I'm still troubled by the implications of assuming that you can't detect
> > > > events on a stream not specifically defined at a given termination.  I'm
> > > > mainly worried about the NULL context.  The simplest way around that
> > > concern
> > > > is to assume that the media properties of physical terminations are
> > > > pre-provisioned.  In fact, people must be making that asumption now --
> > > > otherwise there would have been a lot more interest in my draft on SDP
> > > > attributes for TDM.  I intend to revive that draft shortly, by the way.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Monday, January 28, 2002 8:36 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > My comments embedded.....
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS
> > > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > You've opened up a good discussion.
> > > >
> > > > 1. You are right about streams also being bound to terminations.  Aside
> > > from
> > > > being able to define streams when the termination is in the NULL context,
> > > we
> > > > have the provision that a termination retains its current streams when it
> > > is
> > > > moved from one context to another.
> > > >
> > > > 2. I differ slightly on the interpretation of streams versus actual
> > > enabling
> > > > of flows, but this is at an abstract level that I don't think makes any
> > > > difference in behaviour.  My interpretation is that as soon as a stream is
> > > > created in a context, it introduces the potential of bi-directional
> > > exchange
> > > > of media between the context and each termination in it.  Of course, to
> > > have
> > > > an actual flow in each direction, you need the conditions you've stated:
> > > > Local and Remote defined on at least two terminations and sendRecv set on
> > > > both.
> > > >
> > > > The real issue is whether a termination can detect events and send signals
> > > > on a stream not explicitly defined at that termination.  I think this is a
> > > > matter of convention -- we have to decide one way or the other.  I'll
> > > point
> > > > out that it has implications for detection of DTMF events in the NULL
> > > > context.
> > > > <KN> I feel as per the convention and to some extent simple logic it
> > > > would be appropriate to allow terminations to detect events and signals
> > > > on only those streams which are explicitly defined on them. More so,
> > > because
> > > > in cases where there are multiple streams on multiple terminations
> > > > Eg:
> > > > A context with 4 terminations T1, T2, T3....
> > > > Streams 1 and 2 on T1,3 and 2 on T3.
> > > > T2 has currently no explicit stream defined on it.
> > > >
> > > >           -------------------
> > > >           |              |
> > > >      T1----------1         -------T2
> > > >           |  |            |
> > > >           |  |--2_       |
> > > >           |      |       |
> > > >           |      |       |
> > > >           |      |       |
> > > >           |      |    3--------T3
> > > >           |      |       | |
> > > >           |       |____2--| |
> > > >           |              |
> > > >           -------------------
> > > > It would be questionable to expect the following combinations:
> > > > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > > > -    T1 detect events or apply signals on stream 3.
> > > > -    T3 detect events or apply signals on stream 1.
> > > > At the current moment these terminations are completely oblivious of the
> > > > stream IDs refered.
> > > >
> > > > 3. I think I've made the point that H.248v1 requires that most of the
> > > events
> > > > and signals we have already defined must be applied to a non-zero stream.
> > > > Hence requiring that packages indicate which ones apply to stream 0 is not
> > > a
> > > > change in the protocol, just a clarification.
> > > >
> > > > I do have a couple of alternatives which indeed would be changes to the
> > > > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> > > >
> > > >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > > > event or signal, or
> > > >  (b) If only one stream is defined on the specific termination, an
> > > > unspecified streamId selects that stream.
> > > > <KN> I have an opinion.....How does MGC tell MG to detect events
> > > > on all active streams on a termination. Does MGC have to repeat event IDs
> > > > in the event descriptor with all active stream IDs as parameters. Protocol
> > > > does not introduce any concept of stream ID as "*"(ALL).
> > > > >From the current text, the stream ID 0 seems to be solving this problem.
> > > > Stream ID 0 is the default stream on all terminations,i.e., does not need
> > > to
> > > > be created explicitly through media descriptor (valid).
> > > > If event descriptor contains stream ID 0, "it does not refer to any
> > > specific
> > > > stream"(valid) but does refer to the termination as a whole.
> > > > The inference is that detect events on all streams (currently active on
> > > > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > > > nonstream-specific terminations like NAS). If the event is detected on any
> > > > stream, report the same to MGC with the specific stream ID.
> > > > A similar interpretation can also be made for signals.
> > > > And, the default stream ID remains 0 for events/ signals, but 1 for
> > > > media descriptor.
> > > >
> > > > Actually, I think people are going to have to bite the bullet and start
> > > > specifying streamIds eventually if they don't do it now.  Choosing
> > > > alternative (b) would buy a bit of time.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Thursday, January 24, 2002 5:49 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > I would like to add more to your comments about streams being context
> > > > properties.
> > > >
> > > > Streams are as good properties of the terminations too....
> > > > -    A stream can be created on a termination in the Null Context.
> > > >      (almost in all call flows including those in the RFC 3015 stream
> > > > descriptor
> > > >      or the default stream 1 is sent by the MGC in MODIFY command in the
> > > >      Null context).
> > > > -    To create a bi-directional stream, we need to send stream descriptor
> > > >      with (at the least mode=sendrecv) for both the terminations in the
> > > > context.
> > > >      The bi-directional stream cannot be created by just refering it in
> > > one
> > > >      termination.
> > > >
> > > > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > > > stream=1 (something similar to a unidirectional media flow) by specifying
> > > > stream descriptor for termination T1. At this point it would be incorrect
> > > > to assume that termination T2 can detect events or apply signals on the
> > > > stream
> > > > 1.
> > > > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > > > totally
> > > > oblivious of stream 1).
> > > > To detect events or signals on the stream at T2, we need to first make T2
> > > > aware
> > > > of the stream.
> > > >
> > > > Although, it would be a good idea to specify in package definitions about
> > > > which event/ signals etc. would apply on streamID=0, this would amount to
> > > > changing
> > > > the protocol....are you considering it for version2.
> > > >
> > > > Please comment....
> > > >
> > > > Thanks & Regards,
> > > > -Kapil Nayar
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS
> > > > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi.  See new comments [PTT2] below.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Wednesday, January 23, 2002 8:55 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom
> > > >
> > > > my comments embedded.
> > > >
> > > > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> > > >
> > > > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > > > cc:
> > > >
> > > > Subject:  RE: [Megaco] Query about streamID 0
> > > >
> > > > Hi.
> > > >
> > > > -----Original Message-----
> > > > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > > > Sent: Tuesday, January 22, 2002 8:54 AM
> > > > To: 'megaco@ietf.org'
> > > > Subject: [Megaco] Query about streamID 0
> > > >
> > > > Hi Tom & list,
> > > >
> > > > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor
> > > mentions:
> > > >
> > > > "The default streamID is 0, indicating that the event to be detected is
> > > not
> > > > related to a particular media stream."
> > > >
> > > > Does the "streamID 0" refer to the complete termination (which means all
> > > the
> > > > active streams on the termination) ?
> > > >
> > > > [PTT] No.  It really means as it says, that the event or signal is not
> > > > associated with any specific stream.  An example is an electrical signal
> > > > such as off-hook.
> > > > [KN] Does that mean that stream 0 is possible for only physical
> > > > terminations,
> > > > since electrical signals are more appropriate for physical terminations.
> > > > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > > > relate to specific streams.  Electrical signals were just an example.  I
> > > > suspect I could find a good example in one of my NAS packages of something
> > > > more abstract, but I won't take the time.  Just accept that we don't want
> > > to
> > > > foreclose the possibility of using this on ephemerals.
> > > >
> > > > And, if some event is required to be detected on the ephemeral
> > > termination,
> > > > the event descriptor should clearly identify which stream it is required
> > > on.
> > > > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > > > without
> > > > stream ID parameter since that defaults to stream ID 0, which may not be
> > > > applicable).
> > > > [PTT2] That has to be thought through for all terminations.
> > > > *** IG issue: It does strike me that you can know in advance (by
> > > definition
> > > > of the event or signal) whether streamId=0 will apply.  We should
> > > therefore
> > > > make it requirement to specify this in package definitions.
> > > >
> > > > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > > > associated with an audio stream.  (But I bet nobody has bothered to
> > > specify
> > > > stream 1 for DTMF events when they are using a default streamId for audio.
> > > > They should!)
> > > > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > > > descriptor,
> > > > MGC should have already created the stream 1 thru' the media descriptor
> > > > in a previous command?
> > > > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > > > descriptor, but just specify Local, Remote, and LocalControl.
> > > > *** IG issue: would it make more sense to have streamId=0 as the default
> > > for
> > > > signals and events, or have streamId=1 as the default?
> > > >
> > > > A related doubt is...if an event descriptor refers
> > > > to a stream ID which is not previously created by the MGC, MG should
> > > > return an error.
> > > > [PTT2] I'm not sure.  Remember that streamIds are really a context
> > > property.
> > > > If a given streamId is supported somewhere in the context, then referring
> > > to
> > > > that streamId at a given termination implies that the termination also
> > > > supports it.  That means it could detect events or send signals on the
> > > > stream even if it doesn't know how to handle the media flows on that
> > > stream.
> > > > I suppose if this is the first mention of the streamId in the context, it
> > > > might be appropriate to reject the command.
> > > > ***IG issue: The implication is that within any command, Stream
> > > Descriptors
> > > > for new streams MUST appear before Signals and Events descriptors
> > > referring
> > > > to those StreamIds.
> > > >
> > > > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > > > descriptor, event descriptor, signal descriptor ?
> > > >
> > > > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > > > consistent with the meaning of that streamId for events and signals.  We
> > > > should have a note to the effect that streamId=0 is reserved in sections
> > > > 7.1.4 (for thoroughness) and 7.1.6.
> > > >
> > > > You can specify streamId=0 in a signals or events descriptor, but that's
> > > the
> > > > same as leaving it unspecified.
> > > >
> > > > Please reply back...
> > > >
> > > > Thanks,
> > > > Kapil Nayar
> > > >
> > > > "DISCLAIMER: This message is proprietary to Hughes Software Systmes
> > > Limited
> > > > (HSS) and is intended solely for the use of the individual  to whom it is
> > > > addressed. It may contain  privileged or confidential information  and
> > > > should
> > > > not be circulated or used for any purpose other than for what it is
> > > > intended.If
> > > > you have received this message in error, please notify the originator
> > > > immediately. If you are not the intended recipient, you are notified that
> > > > you
> > > > are strictly prohibited from using, copying, altering, or disclosing the
> > > > contents of this message. HSS accepts no responsibility for loss or damage
> > > > arising from the use of the information transimitted by this email
> > > including
> > > > damage from virus."
> > > >
> > > > _______________________________________________
> > > > 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

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



From megaco-admin@ietf.org  Thu Jan 31 03:12:16 2002
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 DAA21765
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:12:16 -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 CAA29570;
	Thu, 31 Jan 2002 02:54:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29541
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 02:54:34 -0500 (EST)
Received: from sess01.rdp.asi.alcatel.es ([159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21377
	for <megaco@ietf.org>; Thu, 31 Jan 2002 02:54:31 -0500 (EST)
Received: from sers002.rpi.ses.alcatel.es (sers002 [159.23.193.30])
	by sess01.rdp.asi.alcatel.es (8.11.2/8.11.2) with ESMTP id g0V7s1K06328;
	Thu, 31 Jan 2002 08:54:01 +0100 (MET)
Received: from alcatel.es (sevsf075 [159.23.195.75])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id IAA27662;
	Thu, 31 Jan 2002 08:53:47 +0100 (MET)
Message-ID: <3C58F650.A9582861@alcatel.es>
Date: Thu, 31 Jan 2002 08:46:24 +0100
From: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
Organization: ALCATEL
X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Suryapratap vamsi <suryavamsi2@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ServiceChangeReq for terminations
References: <20020130195211.7153.qmail@mailweb26.rediffmail.com>
Content-Type: multipart/alternative;
 boundary="------------6784B9AB2D92B9EF1919FB52"
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


--------------6784B9AB2D92B9EF1919FB52
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think so
but no ServiceChange (Restart) is required because the terminations are supossed to be
in InService state.

Regards
Fernando

Suryapratap vamsi wrote:

> Upon establishing session(Cold Start) with MGC, would GW is requied to send ServiceChange with method (FORCED) for the terminations, that are outofService ?.
>
> Please answer .
>
> with regards
>
> Surya
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------6784B9AB2D92B9EF1919FB52
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I think so
<br>but no ServiceChange&nbsp;(Restart) is required because the terminations
are supossed to be
<br>in InService state.
<p>Regards
<br>Fernando
<p>Suryapratap vamsi wrote:
<blockquote TYPE=CITE>Upon establishing session(Cold Start) with MGC, would
GW is requied to send ServiceChange with method (FORCED) for the terminations,
that are outofService ?.
<p>Please answer .
<p>with regards
<p>Surya
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
Fernando Vallejo Lazaro
Phone:&nbsp; +34 91 330 8279
SW&nbsp; Wireline ASD-Madrid
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALCATEL</pre>
&nbsp;</html>

--------------6784B9AB2D92B9EF1919FB52--


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


From daemon@optimus.ietf.org  Thu Jan 31 03:12:17 2002
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 DAA21778
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:12:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA00666
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 03:12:19 -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 CAA29570;
	Thu, 31 Jan 2002 02:54:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29541
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 02:54:34 -0500 (EST)
Received: from sess01.rdp.asi.alcatel.es ([159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21377
	for <megaco@ietf.org>; Thu, 31 Jan 2002 02:54:31 -0500 (EST)
Received: from sers002.rpi.ses.alcatel.es (sers002 [159.23.193.30])
	by sess01.rdp.asi.alcatel.es (8.11.2/8.11.2) with ESMTP id g0V7s1K06328;
	Thu, 31 Jan 2002 08:54:01 +0100 (MET)
Received: from alcatel.es (sevsf075 [159.23.195.75])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id IAA27662;
	Thu, 31 Jan 2002 08:53:47 +0100 (MET)
Message-ID: <3C58F650.A9582861@alcatel.es>
Date: Thu, 31 Jan 2002 08:46:24 +0100
From: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
Organization: ALCATEL
X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Suryapratap vamsi <suryavamsi2@rediffmail.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ServiceChangeReq for terminations
References: <20020130195211.7153.qmail@mailweb26.rediffmail.com>
Content-Type: multipart/alternative;
 boundary="------------6784B9AB2D92B9EF1919FB52"
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


--------------6784B9AB2D92B9EF1919FB52
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think so
but no ServiceChange (Restart) is required because the terminations are supossed to be
in InService state.

Regards
Fernando

Suryapratap vamsi wrote:

> Upon establishing session(Cold Start) with MGC, would GW is requied to send ServiceChange with method (FORCED) for the terminations, that are outofService ?.
>
> Please answer .
>
> with regards
>
> Surya
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------6784B9AB2D92B9EF1919FB52
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I think so
<br>but no ServiceChange&nbsp;(Restart) is required because the terminations
are supossed to be
<br>in InService state.
<p>Regards
<br>Fernando
<p>Suryapratap vamsi wrote:
<blockquote TYPE=CITE>Upon establishing session(Cold Start) with MGC, would
GW is requied to send ServiceChange with method (FORCED) for the terminations,
that are outofService ?.
<p>Please answer .
<p>with regards
<p>Surya
<p>_______________________________________________
<br>Megaco mailing list
<br>Megaco@ietf.org
<br><a href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</a></blockquote>

<pre>--&nbsp;
Fernando Vallejo Lazaro
Phone:&nbsp; +34 91 330 8279
SW&nbsp; Wireline ASD-Madrid
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALCATEL</pre>
&nbsp;</html>

--------------6784B9AB2D92B9EF1919FB52--


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



From megaco-admin@ietf.org  Thu Jan 31 03:39:12 2002
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 DAA22123
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:39:12 -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 DAA02058;
	Thu, 31 Jan 2002 03:32:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01945
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 03:31:53 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22078
	for <megaco@ietf.org>; Thu, 31 Jan 2002 03:31:37 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh.hss.hns.com [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0V8UvA25477;
	Thu, 31 Jan 2002 14:01:02 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B52.002E9C50 ; Thu, 31 Jan 2002 13:59:06 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B52.002E9A75.00@sandesh.hss.hns.com>
Date: Thu, 31 Jan 2002 14:01:00 +0530
Subject: Re: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Christian

Sorry for the delayed reply.
My comments are embedded...
Thanks,
-Kapil




Christian Groves <Christian.Groves@ericsson.com.au> on 01/30/2002 08:51:46 AM

To:   Tom-PT Taylor <taylor@nortelnetworks.com>
cc:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  Re: [Megaco] Query about streamID 0




G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
[KN] - Does that mean stream ID 0 refers to ANY stream or just the
APPROPRIATE stream(s)...like DTMF detector on the audio stream(s).
If it is the later, it means that packages (events) are defined
for streams and not just terminations ?

event (stream ID x) - detect the event only on the particular streamID x
[KN] - This is OK!

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
[KN] - Does that mean stream ID 0 refers to ALL streams or just the
APPROPRIATE stream(s)...like video on the video stream(s).
If it is the later, it means that packages (signals) are defined
for streams and not just terminations ?

signal (stream ID x) - the signal only on the particular streamID x
[KN] - This is OK!

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.
[KN] - Isn't it similar to saying that stream 0 is a default stream
(a Null stream) which is not explicitly created thru' media desc but
may be referred in other descriptors like..event, signals etc.

Now this is all rather acedemic if the termination only ever has one
stream.

I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
>
> Your proposal that the default streamId (0) means "all active streams" is a
> workable one for events, especially if the actual stream on which the signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
>
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> My comments embedded.....
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
>
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> You've opened up a good discussion.
>
> 1. You are right about streams also being bound to terminations.  Aside from
> being able to define streams when the termination is in the NULL context, we
> have the provision that a termination retains its current streams when it is
> moved from one context to another.
>
> 2. I differ slightly on the interpretation of streams versus actual enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional exchange
> of media between the context and each termination in it.  Of course, to have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
>
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so, because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
>
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
>
> 3. I think I've made the point that H.248v1 requires that most of the events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not a
> change in the protocol, just a clarification.
>
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
>
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
>
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> I would like to add more to your comments about streams being context
> properties.
>
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in one
>      termination.
>
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
>
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
>
> Please comment....
>
> Thanks & Regards,
> -Kapil Nayar
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
>
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> Hi.  See new comments [PTT2] below.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> my comments embedded.
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
>
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> Hi.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
>
> Hi Tom & list,
>
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
>
> "The default streamID is 0, indicating that the event to be detected is not
> related to a particular media stream."
>
> Does the "streamID 0" refer to the complete termination (which means all the
> active streams on the termination) ?
>
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want to
> foreclose the possibility of using this on ephemerals.
>
> And, if some event is required to be detected on the ephemeral termination,
> the event descriptor should clearly identify which stream it is required on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by definition
> of the event or signal) whether streamId=0 will apply.  We should therefore
> make it requirement to specify this in package definitions.
>
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default for
> signals and events, or have streamId=1 as the default?
>
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> If a given streamId is supported somewhere in the context, then referring to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream Descriptors
> for new streams MUST appear before Signals and Events descriptors referring
> to those StreamIds.
>
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
>
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
>
> You can specify streamId=0 in a signals or events descriptor, but that's the
> same as leaving it unspecified.
>
> Please reply back...
>
> Thanks,
> Kapil Nayar
>
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."
>
> _______________________________________________
> 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


From daemon@optimus.ietf.org  Thu Jan 31 03:39:13 2002
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 DAA22133
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 03:39:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA02338
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 03:39:15 -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 DAA02058;
	Thu, 31 Jan 2002 03:32:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01945
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 03:31:53 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22078
	for <megaco@ietf.org>; Thu, 31 Jan 2002 03:31:37 -0500 (EST)
From: knayar@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh.hss.hns.com [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g0V8UvA25477;
	Thu, 31 Jan 2002 14:01:02 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B52.002E9C50 ; Thu, 31 Jan 2002 13:59:06 +0530
X-Lotus-FromDomain: HSS
To: Christian Groves <Christian.Groves@ericsson.com.au>
cc: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B52.002E9A75.00@sandesh.hss.hns.com>
Date: Thu, 31 Jan 2002 14:01:00 +0530
Subject: Re: [Megaco] Query about streamID 0
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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



Hi Christian

Sorry for the delayed reply.
My comments are embedded...
Thanks,
-Kapil




Christian Groves <Christian.Groves@ericsson.com.au> on 01/30/2002 08:51:46 AM

To:   Tom-PT Taylor <taylor@nortelnetworks.com>
cc:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>

Subject:  Re: [Megaco] Query about streamID 0




G'Day

My understanding of the combinations are the following:

event (no stream) - detect an event on the termination irrespective of
what streams are on the termination. The MG will insert the correct
detection equipment. ie. DTMF detector on the audio stream/s.
event (stream ID 0) - as above
[KN] - Does that mean stream ID 0 refers to ANY stream or just the
APPROPRIATE stream(s)...like DTMF detector on the audio stream(s).
If it is the later, it means that packages (events) are defined
for streams and not just terminations ?

event (stream ID x) - detect the event only on the particular streamID x
[KN] - This is OK!

signal (no stream) - play the signal on the termination irrespective of
what streams are on the termination. The MG will insert the correct
playout equipment. Play a video on the video stream.
signal (stream ID 0) - as above
[KN] - Does that mean stream ID 0 refers to ALL streams or just the
APPROPRIATE stream(s)...like video on the video stream(s).
If it is the later, it means that packages (signals) are defined
for streams and not just terminations ?

signal (stream ID x) - the signal only on the particular streamID x
[KN] - This is OK!

Default streamID=1 if you leave the stream descriptor as just specify
local and remote.
[KN] - Isn't it similar to saying that stream 0 is a default stream
(a Null stream) which is not explicitly created thru' media desc but
may be referred in other descriptors like..event, signals etc.

Now this is all rather acedemic if the termination only ever has one
stream.

I can't see the problem. What am I missing?

Regards, Christian


Tom-PT Taylor wrote:
>
> Your proposal that the default streamId (0) means "all active streams" is a
> workable one for events, especially if the actual stream on which the signal
> occurred is reported in the Notify.  I suspect signals are a bit more
> problematic -- you only want a signal to go out on one stream, usually.
>
> I'm still troubled by the implications of assuming that you can't detect
> events on a stream not specifically defined at a given termination.  I'm
> mainly worried about the NULL context.  The simplest way around that concern
> is to assume that the media properties of physical terminations are
> pre-provisioned.  In fact, people must be making that asumption now --
> otherwise there would have been a lot more interest in my draft on SDP
> attributes for TDM.  I intend to revive that draft shortly, by the way.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Monday, January 28, 2002 8:36 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> My comments embedded.....
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
>
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> You've opened up a good discussion.
>
> 1. You are right about streams also being bound to terminations.  Aside from
> being able to define streams when the termination is in the NULL context, we
> have the provision that a termination retains its current streams when it is
> moved from one context to another.
>
> 2. I differ slightly on the interpretation of streams versus actual enabling
> of flows, but this is at an abstract level that I don't think makes any
> difference in behaviour.  My interpretation is that as soon as a stream is
> created in a context, it introduces the potential of bi-directional exchange
> of media between the context and each termination in it.  Of course, to have
> an actual flow in each direction, you need the conditions you've stated:
> Local and Remote defined on at least two terminations and sendRecv set on
> both.
>
> The real issue is whether a termination can detect events and send signals
> on a stream not explicitly defined at that termination.  I think this is a
> matter of convention -- we have to decide one way or the other.  I'll point
> out that it has implications for detection of DTMF events in the NULL
> context.
> <KN> I feel as per the convention and to some extent simple logic it
> would be appropriate to allow terminations to detect events and signals
> on only those streams which are explicitly defined on them. More so, because
> in cases where there are multiple streams on multiple terminations
> Eg:
> A context with 4 terminations T1, T2, T3....
> Streams 1 and 2 on T1,3 and 2 on T3.
> T2 has currently no explicit stream defined on it.
>
>           -------------------
>           |              |
>      T1----------1         -------T2
>           |  |            |
>           |  |--2_       |
>           |      |       |
>           |      |       |
>           |      |       |
>           |      |    3--------T3
>           |      |       | |
>           |       |____2--| |
>           |              |
>           -------------------
> It would be questionable to expect the following combinations:
> -    T2 detect events or apply signals on stream 1 or 2 or 3.
> -    T1 detect events or apply signals on stream 3.
> -    T3 detect events or apply signals on stream 1.
> At the current moment these terminations are completely oblivious of the
> stream IDs refered.
>
> 3. I think I've made the point that H.248v1 requires that most of the events
> and signals we have already defined must be applied to a non-zero stream.
> Hence requiring that packages indicate which ones apply to stream 0 is not a
> change in the protocol, just a clarification.
>
> I do have a couple of alternatives which indeed would be changes to the
> protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
>
>  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> event or signal, or
>  (b) If only one stream is defined on the specific termination, an
> unspecified streamId selects that stream.
> <KN> I have an opinion.....How does MGC tell MG to detect events
> on all active streams on a termination. Does MGC have to repeat event IDs
> in the event descriptor with all active stream IDs as parameters. Protocol
> does not introduce any concept of stream ID as "*"(ALL).
> >From the current text, the stream ID 0 seems to be solving this problem.
> Stream ID 0 is the default stream on all terminations,i.e., does not need to
> be created explicitly through media descriptor (valid).
> If event descriptor contains stream ID 0, "it does not refer to any specific
> stream"(valid) but does refer to the termination as a whole.
> The inference is that detect events on all streams (currently active on
> stream-specific terminations like RTP/ TDMC or stream ID 0 on
> nonstream-specific terminations like NAS). If the event is detected on any
> stream, report the same to MGC with the specific stream ID.
> A similar interpretation can also be made for signals.
> And, the default stream ID remains 0 for events/ signals, but 1 for
> media descriptor.
>
> Actually, I think people are going to have to bite the bullet and start
> specifying streamIds eventually if they don't do it now.  Choosing
> alternative (b) would buy a bit of time.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Thursday, January 24, 2002 5:49 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> I would like to add more to your comments about streams being context
> properties.
>
> Streams are as good properties of the terminations too....
> -    A stream can be created on a termination in the Null Context.
>      (almost in all call flows including those in the RFC 3015 stream
> descriptor
>      or the default stream 1 is sent by the MGC in MODIFY command in the
>      Null context).
> -    To create a bi-directional stream, we need to send stream descriptor
>      with (at the least mode=sendrecv) for both the terminations in the
> context.
>      The bi-directional stream cannot be created by just refering it in one
>      termination.
>
> Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> stream=1 (something similar to a unidirectional media flow) by specifying
> stream descriptor for termination T1. At this point it would be incorrect
> to assume that termination T2 can detect events or apply signals on the
> stream
> 1.
> (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> totally
> oblivious of stream 1).
> To detect events or signals on the stream at T2, we need to first make T2
> aware
> of the stream.
>
> Although, it would be a good idea to specify in package definitions about
> which event/ signals etc. would apply on streamID=0, this would amount to
> changing
> the protocol....are you considering it for version2.
>
> Please comment....
>
> Thanks & Regards,
> -Kapil Nayar
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
>
> To:   Kapil Nayar/HSS@HSS
> cc:   "'megaco@ietf.org'" <megaco@ietf.org>
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> Hi.  See new comments [PTT2] below.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Wednesday, January 23, 2002 8:55 AM
> To: Taylor, Tom-PT [CAR:B800:EXCH]
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] Query about streamID 0
>
> Hi Tom
>
> my comments embedded.
>
> "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
>
> To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> cc:
>
> Subject:  RE: [Megaco] Query about streamID 0
>
> Hi.
>
> -----Original Message-----
> From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> Sent: Tuesday, January 22, 2002 8:54 AM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Query about streamID 0
>
> Hi Tom & list,
>
> RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
>
> "The default streamID is 0, indicating that the event to be detected is not
> related to a particular media stream."
>
> Does the "streamID 0" refer to the complete termination (which means all the
> active streams on the termination) ?
>
> [PTT] No.  It really means as it says, that the event or signal is not
> associated with any specific stream.  An example is an electrical signal
> such as off-hook.
> [KN] Does that mean that stream 0 is possible for only physical
> terminations,
> since electrical signals are more appropriate for physical terminations.
> [PTT2] There can be applications of streamId 0 on ephemerals which don't
> relate to specific streams.  Electrical signals were just an example.  I
> suspect I could find a good example in one of my NAS packages of something
> more abstract, but I won't take the time.  Just accept that we don't want to
> foreclose the possibility of using this on ephemerals.
>
> And, if some event is required to be detected on the ephemeral termination,
> the event descriptor should clearly identify which stream it is required on.
> (i.e., MGC cannot send an events descriptor for ephemeral termination
> without
> stream ID parameter since that defaults to stream ID 0, which may not be
> applicable).
> [PTT2] That has to be thought through for all terminations.
> *** IG issue: It does strike me that you can know in advance (by definition
> of the event or signal) whether streamId=0 will apply.  We should therefore
> make it requirement to specify this in package definitions.
>
> [PTT] On the other hand, an audio signal such as a DTMF tone is
> associated with an audio stream.  (But I bet nobody has bothered to specify
> stream 1 for DTMF events when they are using a default streamId for audio.
> They should!)
> [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> descriptor,
> MGC should have already created the stream 1 thru' the media descriptor
> in a previous command?
> [PTT2] StreamId=1 is the default stream created if you don't use a stream
> descriptor, but just specify Local, Remote, and LocalControl.
> *** IG issue: would it make more sense to have streamId=0 as the default for
> signals and events, or have streamId=1 as the default?
>
> A related doubt is...if an event descriptor refers
> to a stream ID which is not previously created by the MGC, MG should
> return an error.
> [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> If a given streamId is supported somewhere in the context, then referring to
> that streamId at a given termination implies that the termination also
> supports it.  That means it could detect events or send signals on the
> stream even if it doesn't know how to handle the media flows on that stream.
> I suppose if this is the first mention of the streamId in the context, it
> might be appropriate to reject the command.
> ***IG issue: The implication is that within any command, Stream Descriptors
> for new streams MUST appear before Signals and Events descriptors referring
> to those StreamIds.
>
> Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> descriptor, event descriptor, signal descriptor ?
>
> [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> consistent with the meaning of that streamId for events and signals.  We
> should have a note to the effect that streamId=0 is reserved in sections
> 7.1.4 (for thoroughness) and 7.1.6.
>
> You can specify streamId=0 in a signals or events descriptor, but that's the
> same as leaving it unspecified.
>
> Please reply back...
>
> Thanks,
> Kapil Nayar
>
> "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> (HSS) and is intended solely for the use of the individual  to whom it is
> addressed. It may contain  privileged or confidential information  and
> should
> not be circulated or used for any purpose other than for what it is
> intended.If
> you have received this message in error, please notify the originator
> immediately. If you are not the intended recipient, you are notified that
> you
> are strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. HSS accepts no responsibility for loss or damage
> arising from the use of the information transimitted by this email including
> damage from virus."
>
> _______________________________________________
> 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



From megaco-admin@ietf.org  Thu Jan 31 10:00:16 2002
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 KAA28496
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 10:00:16 -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 JAA20097;
	Thu, 31 Jan 2002 09:46:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20064
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 09:46:42 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28098
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:46:37 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0VEkcI17219;
	Thu, 31 Jan 2002 09:46:38 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA12867;
	Thu, 31 Jan 2002 09:46:07 -0500 (EST)
Message-ID: <3C59587E.7B4C9B5D@lucent.com>
Date: Thu, 31 Jan 2002 09:45:19 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com> <3C58155F.1F1FC3AB@lucent.com> <3C588803.11CF5ED0@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------4B49805C24588ADCFEDB5566"
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

This is a multi-part message in MIME format.
--------------4B49805C24588ADCFEDB5566
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

You are right.  I (and Vidya G) should have read a little further.  I agree, no change is needed.

Christian Groves wrote:

> G'Day Terry,
>
> The behaviour already is mentioned in 8.0 the paragraph after "At the
> first failing Command...". States: "Commands may be marked as "Optional"
> which can override this behaviour -  if a command marked as Optional
> results in an error, subsequent commands in the Transaction will be
> executed.  If a command fails, the MG shall as far as possible restore
> the state that existed prior to the attempted execution of the command
> before continuing with command processing."
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > The statement (in 8.0) IS misleading but your understanding is also incorrect.
> >
> > 8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
> > the entire Transaction (not just the action).
> >
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.
> >
> > Do folks think this sentence should be corrected in IG?
> >
> > vidya g wrote:
> >
> > > Hi all
> > >
> > >   In RFC, page number 61 it says that
> > >
> > >  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
> > >
> > >   This statement is some what confusing. What I understand is even if a non optional
> > > command fails in an action, the action will be cancelled and the next action will be taken
> > > for processing and the commands in that action will be processed.. is that right .. ?
> > >
> > > vdy
> > >
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------4B49805C24588ADCFEDB5566
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------4B49805C24588ADCFEDB5566--


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


From daemon@optimus.ietf.org  Thu Jan 31 10:00:19 2002
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 KAA28513
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 10:00:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA21059
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 10:00:23 -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 JAA20097;
	Thu, 31 Jan 2002 09:46:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20064
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 09:46:42 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28098
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:46:37 -0500 (EST)
Received: from teton.mh.lucent.com (h135-3-130-2.lucent.com [135.3.130.2])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0VEkcI17219;
	Thu, 31 Jan 2002 09:46:38 -0500 (EST)
Received: from lucent.com (mhapps3 [135.3.131.203])
	by teton.mh.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA12867;
	Thu, 31 Jan 2002 09:46:07 -0500 (EST)
Message-ID: <3C59587E.7B4C9B5D@lucent.com>
Date: Thu, 31 Jan 2002 09:45:19 -0500
From: Terry L Anderson <tla@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: Re: [Megaco] QRY about the failed command
References: <20020130093723.21932.qmail@mailFA2.rediffmail.com> <3C58155F.1F1FC3AB@lucent.com> <3C588803.11CF5ED0@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------4B49805C24588ADCFEDB5566"
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

This is a multi-part message in MIME format.
--------------4B49805C24588ADCFEDB5566
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

You are right.  I (and Vidya G) should have read a little further.  I agree, no change is needed.

Christian Groves wrote:

> G'Day Terry,
>
> The behaviour already is mentioned in 8.0 the paragraph after "At the
> first failing Command...". States: "Commands may be marked as "Optional"
> which can override this behaviour -  if a command marked as Optional
> results in an error, subsequent commands in the Transaction will be
> executed.  If a command fails, the MG shall as far as possible restore
> the state that existed prior to the attempted execution of the command
> before continuing with command processing."
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > The statement (in 8.0) IS misleading but your understanding is also incorrect.
> >
> > 8.2.2 (including changes from IG 6.36) make it clear that the first non-optional command that fails ends processing of
> > the entire Transaction (not just the action).
> >
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in 8.0.
> >
> > Do folks think this sentence should be corrected in IG?
> >
> > vidya g wrote:
> >
> > > Hi all
> > >
> > >   In RFC, page number 61 it says that
> > >
> > >  "  At the first failing Command in a Transaction, processing of the remaining Commands in that Transaction stops."
> > >
> > >   This statement is some what confusing. What I understand is even if a non optional
> > > command fails in an action, the action will be cancelled and the next action will be taken
> > > for processing and the commands in that action will be processed.. is that right .. ?
> > >
> > > vdy
> > >
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:908.582.7013   Fax:908.582.6729
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------4B49805C24588ADCFEDB5566
Content-Type: text/x-vcard; charset=us-ascii;
 name="tla.vcf"
Content-Description: Card for Terry L Anderson
Content-Disposition: attachment;
 filename="tla.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Anderson;Terry L
tel;fax:908.582.6729
tel;work:908.582.7013
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
version:2.1
email;internet:tla@lucent.com
title:DMTS
note:http://www.gti.net/tla  or http://teton.mh.lucent.com/~tla (Lucent internal)
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
x-mozilla-cpt:;-4752
fn:Terry L Anderson
end:vcard

--------------4B49805C24588ADCFEDB5566--


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



From megaco-admin@ietf.org  Thu Jan 31 10:11:33 2002
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 KAA28833
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 10:11:33 -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 JAA20569;
	Thu, 31 Jan 2002 09:54:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20538
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 09:54:47 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28299
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VEsD508495
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:13 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VEsB525696
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAVT2Y>; Thu, 31 Jan 2002 09:54:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF58@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>, ITU-SG16@echo.jf.INTEL.COM
Date: Thu, 31 Jan 2002 09:54:18 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Files Uploaded
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

I have uploaded the following files to the PictureTel site:

d229_T38_SIP.zip
IETF Work on T.38 SIP Call Flows 
Source: Canada (Contact Glen Parsons)

d230_T38Dcorr.doc
Proposed Changes to Recommendation T.38 Annex D
Source: Canada (Contact Glen Parsons)

d231_T38D_IANA.doc
IANA Registrations for Recommendaiton T.38 Annex D
Source: Canada (Contact Glen Parsons)

td2-xxxDraftH248M1.zip
Draft H.248 Annex M.1 Advanced Audio Server packages For Consent
Source: Editor (Contact Tom Taylor)

td2-xxx-EdResponseD186.doc
Editor's Response To D.186
Source: Editor H.248 Annex M.1 (Contact Tom Taylor)

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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


From daemon@optimus.ietf.org  Thu Jan 31 10:11:34 2002
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 KAA28842
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 10:11:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA22326
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 10:11:39 -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 JAA20569;
	Thu, 31 Jan 2002 09:54:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20538
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 09:54:47 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28299
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:42 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VEsD508495
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:13 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VEsB525696
	for <megaco@ietf.org>; Thu, 31 Jan 2002 09:54:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAVT2Y>; Thu, 31 Jan 2002 09:54:14 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF58@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>, ITU-SG16@echo.jf.INTEL.COM
Date: Thu, 31 Jan 2002 09:54:18 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Files Uploaded
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

I have uploaded the following files to the PictureTel site:

d229_T38_SIP.zip
IETF Work on T.38 SIP Call Flows 
Source: Canada (Contact Glen Parsons)

d230_T38Dcorr.doc
Proposed Changes to Recommendation T.38 Annex D
Source: Canada (Contact Glen Parsons)

d231_T38D_IANA.doc
IANA Registrations for Recommendaiton T.38 Annex D
Source: Canada (Contact Glen Parsons)

td2-xxxDraftH248M1.zip
Draft H.248 Annex M.1 Advanced Audio Server packages For Consent
Source: Editor (Contact Tom Taylor)

td2-xxx-EdResponseD186.doc
Editor's Response To D.186
Source: Editor H.248 Annex M.1 (Contact Tom Taylor)

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From megaco-admin@ietf.org  Thu Jan 31 11:11:23 2002
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 LAA01221
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 11:11:23 -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 KAA26136;
	Thu, 31 Jan 2002 10:50:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26082
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 10:50:14 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00359
	for <megaco@ietf.org>; Thu, 31 Jan 2002 10:50:08 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id KAA23165;
	Thu, 31 Jan 2002 10:49:06 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <D5FLBVNT>; Thu, 31 Jan 2002 10:49:05 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239D83@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco
	 <megaco@ietf.org>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
Subject: RE: [Megaco] Doubt on package extension
Date: Thu, 31 Jan 2002 10:49:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Just to confirm Tom's interpretation is correct, and answer Usha's question.  

Since the parameter is not defined in the base package, must use the extended package to address it.  Also, since in this case the base class (tonegen) has no function of its own, just defines signals but no parameters, it is dubious to me an implementation should even expose it -- just expose the extended packages.  It is not "illegal" to expose the base package in cases such as this, just useless and confusing.  

I believe the IG text on this was made quite clear, hence v2 should now be also.  Have to admit, I have not specifically checked...

-- Peter Blatherwick

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: January 30, 2002 09:59
To: 'usha.iyer@wipro.com'; megaco
Subject: RE: [Megaco] Doubt on package extension


This doesn't feel right to me, and the cases are not exactly the same.  Here
we have a parameter value which is unknown in the base package.  Even though
toneGen is known there, the parameter value is not.  In my view this means
you have to address that value through the extension which defined it (or
extensions of that extension).


-----Original Message-----
From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 9:35 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
Subject: Re: [Megaco] Doubt on package extension


Is option A invalid for the reason that tonegen package is designed only for
extension,or does the rule apply to any base package ?
 
    Acc to  12.4 of AVD_2128  
---- For example, if Package A defines event e1, and Package B extends
Package A, then B/e1 is an event for a termination implementing Package B.
By definition, the MG MUST also implement the base Package, but it optional
to publish the base package as an allowed interface. If it does publish A,
then A would be reported on the Package Descriptor in AuditValue as well as
B, and event A/e1 would be available on a termination. If the MG does not
publish A, then only B/e1 would be available 
----
 
Going by the above , option A  is allowed if tonegen package is published . 
 
TIA,
usha
----- Original Message ----- 
From: Taylor, Tom-PT [CAR:B800:EXCH] 
To: 'Usha Iyer' ; megaco@ietf.org 
Sent: Wednesday, January 30, 2002 7:37 PM
Subject: RE: [Megaco] Doubt on package extension


Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha

_______________________________________________
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


From daemon@optimus.ietf.org  Thu Jan 31 11:11:24 2002
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 LAA01232
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 11:11:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA00038
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 11:11:27 -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 KAA26136;
	Thu, 31 Jan 2002 10:50:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26082
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 10:50:14 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00359
	for <megaco@ietf.org>; Thu, 31 Jan 2002 10:50:08 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id KAA23165;
	Thu, 31 Jan 2002 10:49:06 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <D5FLBVNT>; Thu, 31 Jan 2002 10:49:05 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239D83@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'usha.iyer@wipro.com'" <usha.iyer@wipro.com>, megaco
	 <megaco@ietf.org>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
Subject: RE: [Megaco] Doubt on package extension
Date: Thu, 31 Jan 2002 10:49:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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

Just to confirm Tom's interpretation is correct, and answer Usha's question.  

Since the parameter is not defined in the base package, must use the extended package to address it.  Also, since in this case the base class (tonegen) has no function of its own, just defines signals but no parameters, it is dubious to me an implementation should even expose it -- just expose the extended packages.  It is not "illegal" to expose the base package in cases such as this, just useless and confusing.  

I believe the IG text on this was made quite clear, hence v2 should now be also.  Have to admit, I have not specifically checked...

-- Peter Blatherwick

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: January 30, 2002 09:59
To: 'usha.iyer@wipro.com'; megaco
Subject: RE: [Megaco] Doubt on package extension


This doesn't feel right to me, and the cases are not exactly the same.  Here
we have a parameter value which is unknown in the base package.  Even though
toneGen is known there, the parameter value is not.  In my view this means
you have to address that value through the extension which defined it (or
extensions of that extension).


-----Original Message-----
From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 9:35 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
Subject: Re: [Megaco] Doubt on package extension


Is option A invalid for the reason that tonegen package is designed only for
extension,or does the rule apply to any base package ?
 
    Acc to  12.4 of AVD_2128  
---- For example, if Package A defines event e1, and Package B extends
Package A, then B/e1 is an event for a termination implementing Package B.
By definition, the MG MUST also implement the base Package, but it optional
to publish the base package as an allowed interface. If it does publish A,
then A would be reported on the Package Descriptor in AuditValue as well as
B, and event A/e1 would be available on a termination. If the MG does not
publish A, then only B/e1 would be available 
----
 
Going by the above , option A  is allowed if tonegen package is published . 
 
TIA,
usha
----- Original Message ----- 
From: Taylor, Tom-PT [CAR:B800:EXCH] 
To: 'Usha Iyer' ; megaco@ietf.org 
Sent: Wednesday, January 30, 2002 7:37 PM
Subject: RE: [Megaco] Doubt on package extension


Assuming DTMFgen defines d0 as both a signal and a toneId, and similarly for
cw in callProgToneGen, then either B or C is valid.

-----Original Message-----
From: Usha Iyer [mailto:usha.iyer@wipro.com]
Sent: Wednesday, January 30, 2002 3:01 AM
To: megaco@ietf.org
Subject: [Megaco] Doubt on package extension


Hi ,
 
DTMF Gen and Call ProgressToneGen pkg both extend tone gen package .  
So for a termination that supports ToneGen, DTMFGen and Call ProgToneGen Pkg
, suppose i want to play d0 follwed by call  waiting tone , which of the
foll apply . 
 
A - tonegen/playtone(toneid list= d0,cw ) 
B -dtmfgen/playtone(toneid list= d0 )  followed by
callprogtonegen/playtone(toneid list= cw )
C -dtmfgen/d0 followed by callprogtonegen/cw 
 
 
Reg
Usha

_______________________________________________
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



From megaco-admin@ietf.org  Thu Jan 31 12:25:23 2002
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 MAA04480
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:25:23 -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 MAA06139;
	Thu, 31 Jan 2002 12:02:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06110
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 12:02:54 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03440
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:02:40 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0VH1H924510
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:31:18 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQTBBG00.3YN; Thu, 31 Jan 2002 22:32:04 +0530 
Message-ID: <0d7b01c1aa79$5d5b6500$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Blatherwick Peter" <Peter_Blatherwick@Mitel.COM>,
        "megaco" <megaco@ietf.org>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
References: <29B5A21C13C8D51190F900805F65B4EC239D83@rndex50.ottawa.mitel.com>
Subject: Re: [Megaco] Doubt on package extension
Date: Thu, 31 Jan 2002 22:34:37 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0D78_01C1AAA7.76BF8D90"

------=_NextPart_000_0D78_01C1AAA7.76BF8D90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Peter/All,

    The IGAdditions doc does say that the ToneGen and ToneDet packages =
are designed for extension and not for direct control... however i was =
unable to locate the text that addresses my query .
I should have mentioned it but what i quoted was just an example. I'd =
just like to know whether it is illegal (not whether it is confusing) =
for the base package (if published) to refer to parameter values defined =
in the packages that extend it and not just for the specific example =
that i quoted=20
( Acc. to Troy's mail , all the options that i quoted are allowed & you =
also say  that it is not illegal. )

TIA,
usha
  =20
  ----- Original Message -----=20
  From: Blatherwick, Peter=20
  To: 'usha.iyer@wipro.com' ; megaco=20
  Cc: 'Tom-PT Taylor'=20
  Sent: Thursday, January 31, 2002 9:19 PM
  Subject: RE: [Megaco] Doubt on package extension


  Just to confirm Tom's interpretation is correct, and answer Usha's =
question. =20

  Since the parameter is not defined in the base package, must use the =
extended package to address it.  Also, since in this case the base class =
(tonegen) has no function of its own, just defines signals but no =
parameters, it is dubious to me an implementation should even expose it =
-- just expose the extended packages.  It is not "illegal" to expose the =
base package in cases such as this, just useless and confusing. =20

  I believe the IG text on this was made quite clear, hence v2 should =
now be also.  Have to admit, I have not specifically checked...

  -- Peter Blatherwick

  -----Original Message-----
  From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
  Sent: January 30, 2002 09:59
  To: 'usha.iyer@wipro.com'; megaco
  Subject: RE: [Megaco] Doubt on package extension


  This doesn't feel right to me, and the cases are not exactly the same. =
 Here
  we have a parameter value which is unknown in the base package.  Even =
though
  toneGen is known there, the parameter value is not.  In my view this =
means
  you have to address that value through the extension which defined it =
(or
  extensions of that extension).


  -----Original Message-----
  From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 9:35 AM
  To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
  Subject: Re: [Megaco] Doubt on package extension


  Is option A invalid for the reason that tonegen package is designed =
only for
  extension,or does the rule apply to any base package ?
  =20
      Acc to  12.4 of AVD_2128 =20
  ---- For example, if Package A defines event e1, and Package B extends
  Package A, then B/e1 is an event for a termination implementing =
Package B.
  By definition, the MG MUST also implement the base Package, but it =
optional
  to publish the base package as an allowed interface. If it does =
publish A,
  then A would be reported on the Package Descriptor in AuditValue as =
well as
  B, and event A/e1 would be available on a termination. If the MG does =
not
  publish A, then only B/e1 would be available=20
  ----
  =20
  Going by the above , option A  is allowed if tonegen package is =
published .=20
  =20
  TIA,
  usha
  ----- Original Message -----=20
  From: Taylor, Tom-PT [CAR:B800:EXCH]=20
  To: 'Usha Iyer' ; megaco@ietf.org=20
  Sent: Wednesday, January 30, 2002 7:37 PM
  Subject: RE: [Megaco] Doubt on package extension


  Assuming DTMFgen defines d0 as both a signal and a toneId, and =
similarly for
  cw in callProgToneGen, then either B or C is valid.

  -----Original Message-----
  From: Usha Iyer [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 3:01 AM
  To: megaco@ietf.org
  Subject: [Megaco] Doubt on package extension


  Hi ,
  =20
  DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
  So for a termination that supports ToneGen, DTMFGen and Call =
ProgToneGen Pkg
  , suppose i want to play d0 follwed by call  waiting tone , which of =
the
  foll apply .=20
  =20
  A - tonegen/playtone(toneid list=3D d0,cw )=20
  B -dtmfgen/playtone(toneid list=3D d0 )  followed by
  callprogtonegen/playtone(toneid list=3D cw )
  C -dtmfgen/d0 followed by callprogtonegen/cw=20
  =20
  =20
  Reg
  Usha

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

------=_NextPart_000_0D78_01C1AAA7.76BF8D90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Hi =
Peter/All,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp;&nbsp;=20
The&nbsp;IGAdditions doc does say that the ToneGen and ToneDet packages =
are=20
designed for extension and not for direct control...&nbsp;however i was =
unable=20
to locate the&nbsp;text that&nbsp;addresses my query .</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>I </FONT><FONT =
face=3DArial=20
color=3D#008080 size=3D2>should have mentioned&nbsp;it but what=20
i&nbsp;quoted&nbsp;was just an&nbsp;example.&nbsp;</FONT><FONT =
face=3DArial=20
color=3D#008080 size=3D2>I'd&nbsp;just like to know whether&nbsp;it is =
illegal (not=20
whether it&nbsp;is confusing) for the base package (if published) to =
refer to=20
parameter values defined in the packages that extend it&nbsp;and =
not&nbsp;just=20
for the specific example that i quoted </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>(&nbsp;Acc. to Troy's =
mail&nbsp;, all=20
the&nbsp;options that i quoted are allowed&nbsp;&amp; you also say =
&nbsp;that it=20
is not illegal.&nbsp;)</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>TIA,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>usha</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp; =
</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3DPeter_Blatherwick@Mitel.COM=20
  href=3D"mailto:Peter_Blatherwick@Mitel.COM">Blatherwick, Peter</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dusha.iyer@wipro.com=20
  href=3D"mailto:'usha.iyer@wipro.com'">'usha.iyer@wipro.com'</A> ; <A=20
  title=3Dmegaco@ietf.org href=3D"mailto:megaco@ietf.org">megaco</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dtaylor@nortelnetworks.com=20
  href=3D"mailto:taylor@nortelnetworks.com">'Tom-PT Taylor'</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 31, =
2002 9:19=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Megaco] Doubt on =
package=20
  extension</DIV>
  <DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><BR></DIV>Just to confirm Tom's interpretation is =
correct, and=20
  answer Usha's question.&nbsp; <BR><BR>Since the parameter is not =
defined in=20
  the base package, must use the extended package to address it.&nbsp; =
Also,=20
  since in this case the base class (tonegen) has no function of its =
own, just=20
  defines signals but no parameters, it is dubious to me an =
implementation=20
  should even expose it -- just expose the extended packages.&nbsp; It =
is not=20
  "illegal" to expose the base package in cases such as this, just =
useless and=20
  confusing.&nbsp; <BR><BR>I believe the IG text on this was made quite =
clear,=20
  hence v2 should now be also.&nbsp; Have to admit, I have not =
specifically=20
  checked...<BR><BR>-- Peter Blatherwick<BR><BR>-----Original=20
  Message-----<BR>From: Tom-PT Taylor=20
  [mailto:taylor@nortelnetworks.com]<BR>Sent: January 30, 2002 =
09:59<BR>To: <A=20
  href=3D"mailto:'usha.iyer@wipro.com'">'usha.iyer@wipro.com'</A>;=20
  megaco<BR>Subject: RE: [Megaco] Doubt on package =
extension<BR><BR><BR>This=20
  doesn't feel right to me, and the cases are not exactly the =
same.&nbsp;=20
  Here<BR>we have a parameter value which is unknown in the base =
package.&nbsp;=20
  Even though<BR>toneGen is known there, the parameter value is =
not.&nbsp; In my=20
  view this means<BR>you have to address that value through the =
extension which=20
  defined it (or<BR>extensions of that =
extension).<BR><BR><BR>-----Original=20
  Message-----<BR>From: <A=20
  href=3D"mailto:usha.iyer@wipro.com">usha.iyer@wipro.com</A>=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 9:35 =

  AM<BR>To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco<BR>Subject: Re: =
[Megaco]=20
  Doubt on package extension<BR><BR><BR>Is option A invalid for the =
reason that=20
  tonegen package is designed only for<BR>extension,or does the rule =
apply to=20
  any base package ?<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp; Acc to&nbsp; 12.4 =
of=20
  AVD_2128&nbsp; <BR>---- For example, if Package A defines event e1, =
and=20
  Package B extends<BR>Package A, then B/e1 is an event for a =
termination=20
  implementing Package B.<BR>By definition, the MG MUST also implement =
the base=20
  Package, but it optional<BR>to publish the base package as an allowed=20
  interface. If it does publish A,<BR>then A would be reported on the =
Package=20
  Descriptor in AuditValue as well as<BR>B, and event A/e1 would be =
available on=20
  a termination. If the MG does not<BR>publish A, then only B/e1 would =
be=20
  available <BR>----<BR>&nbsp;<BR>Going by the above , option A&nbsp; is =
allowed=20
  if tonegen package is published . <BR>&nbsp;<BR>TIA,<BR>usha<BR>----- =
Original=20
  Message ----- <BR>From: Taylor, Tom-PT [CAR:B800:EXCH] <BR>To: 'Usha =
Iyer' ;=20
  <A href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A> <BR>Sent: =
Wednesday,=20
  January 30, 2002 7:37 PM<BR>Subject: RE: [Megaco] Doubt on package=20
  extension<BR><BR><BR>Assuming DTMFgen defines d0 as both a signal and =
a=20
  toneId, and similarly for<BR>cw in callProgToneGen, then either B or C =
is=20
  valid.<BR><BR>-----Original Message-----<BR>From: Usha Iyer=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 3:01 =

  AM<BR>To: <A =
href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR>Subject:=20
  [Megaco] Doubt on package extension<BR><BR><BR>Hi ,<BR>&nbsp;<BR>DTMF =
Gen and=20
  Call ProgressToneGen pkg both extend tone gen package .&nbsp; <BR>So =
for a=20
  termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg<BR>,=20
  suppose i want to play d0 follwed by call&nbsp; waiting tone , which =
of=20
  the<BR>foll apply . <BR>&nbsp;<BR>A - tonegen/playtone(toneid list=3D =
d0,cw )=20
  <BR>B -dtmfgen/playtone(toneid list=3D d0 )&nbsp; followed=20
  by<BR>callprogtonegen/playtone(toneid list=3D cw )<BR>C -dtmfgen/d0 =
followed by=20
  callprogtonegen/cw=20
  =
<BR>&nbsp;<BR>&nbsp;<BR>Reg<BR>Usha<BR><BR>______________________________=
_________________<BR>Megaco=20
  mailing list<BR><A =
href=3D"mailto:Megaco@ietf.org">Megaco@ietf.org</A><BR><A=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.=
org/mailman/listinfo/megaco</A></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0D78_01C1AAA7.76BF8D90--



------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

**************************Disclaimer************************************
      


Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.



 ********************************************************************

------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8--


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


From megaco-admin@ietf.org  Thu Jan 31 12:38:27 2002
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 MAA04833
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:38:27 -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 MAA07846;
	Thu, 31 Jan 2002 12:24:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07820
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 12:24:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04436
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:24:01 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VHNY516322
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:23:34 -0500 (EST)
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 g0VHNXb23703
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:23:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAVXYA>; Thu, 31 Jan 2002 12:23:32 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF60@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 31 Jan 2002 12:23:31 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: Files Uploaded
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

FYI

-----Original Message-----
From: OKUBO Sakae [mailto:okubo@GITI.WASEDA.AC.JP]
Sent: Thursday, January 31, 2002 11:31 AM
To: ITU-SG16@echo.jf.INTEL.COM
Subject: Re: Files Uploaded


At 09:54 -0500 02/01/31, Tom-PT Taylor wrote:
>I have uploaded the following files to the PictureTel site:
>
>d229_T38_SIP.zip
>IETF Work on T.38 SIP Call Flows
>Source: Canada (Contact Glen Parsons)
>
>d230_T38Dcorr.doc
>Proposed Changes to Recommendation T.38 Annex D
>Source: Canada (Contact Glen Parsons)
>
>d231_T38D_IANA.doc
>IANA Registrations for Recommendaiton T.38 Annex D
>Source: Canada (Contact Glen Parsons)
>
>td2-xxxDraftH248M1.zip
>Draft H.248 Annex M.1 Advanced Audio Server packages For Consent
>Source: Editor (Contact Tom Taylor)
>
>td2-xxx-EdResponseD186.doc
>Editor's Response To D.186
>Source: Editor H.248 Annex M.1 (Contact Tom Taylor)

They have been moved to the following place:

using browser
  http://standard.pictel.com/ftp/avc-site/0202_Gen/

using ftp tool
  ftp://standard.pictel.com/avc-site/0202_Gen/

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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


From daemon@optimus.ietf.org  Thu Jan 31 12:38:28 2002
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 MAA04843
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:38:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA08966
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 12:38:30 -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 MAA07846;
	Thu, 31 Jan 2002 12:24:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07820
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 12:24:16 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04436
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:24:01 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VHNY516322
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:23:34 -0500 (EST)
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 g0VHNXb23703
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:23:33 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAVXYA>; Thu, 31 Jan 2002 12:23:32 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF60@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 31 Jan 2002 12:23:31 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: Files Uploaded
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

FYI

-----Original Message-----
From: OKUBO Sakae [mailto:okubo@GITI.WASEDA.AC.JP]
Sent: Thursday, January 31, 2002 11:31 AM
To: ITU-SG16@echo.jf.INTEL.COM
Subject: Re: Files Uploaded


At 09:54 -0500 02/01/31, Tom-PT Taylor wrote:
>I have uploaded the following files to the PictureTel site:
>
>d229_T38_SIP.zip
>IETF Work on T.38 SIP Call Flows
>Source: Canada (Contact Glen Parsons)
>
>d230_T38Dcorr.doc
>Proposed Changes to Recommendation T.38 Annex D
>Source: Canada (Contact Glen Parsons)
>
>d231_T38D_IANA.doc
>IANA Registrations for Recommendaiton T.38 Annex D
>Source: Canada (Contact Glen Parsons)
>
>td2-xxxDraftH248M1.zip
>Draft H.248 Annex M.1 Advanced Audio Server packages For Consent
>Source: Editor (Contact Tom Taylor)
>
>td2-xxx-EdResponseD186.doc
>Editor's Response To D.186
>Source: Editor H.248 Annex M.1 (Contact Tom Taylor)

They have been moved to the following place:

using browser
  http://standard.pictel.com/ftp/avc-site/0202_Gen/

using ftp tool
  ftp://standard.pictel.com/avc-site/0202_Gen/

Best regards,

OKUBO Sakae
*********************************************************
Global Information and Telecommunication Institute (GITI)
Waseda University
29-7 Waseda University Bldg.
1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
        e-mail: okubo@giti.waseda.ac.jp
        Tel: +81 3 3204 8194
        Fax: +81 3 5286 3832
*********************************************************

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



From daemon@optimus.ietf.org  Thu Jan 31 13:17:04 2002
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 MAA04491
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 12:25:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA07921
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 12:25:28 -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 MAA06139;
	Thu, 31 Jan 2002 12:02:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06110
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 12:02:54 -0500 (EST)
Received: from wiproecmx1.wipro.com (wiproecmx1.wipro.com [164.164.31.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03440
	for <megaco@ietf.org>; Thu, 31 Jan 2002 12:02:40 -0500 (EST)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [164.164.23.6])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g0VH1H924510
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:31:18 +0530 (IST)
Received: from ushaiyer ([192.168.178.84]) by
          ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GQTBBG00.3YN; Thu, 31 Jan 2002 22:32:04 +0530 
Message-ID: <0d7b01c1aa79$5d5b6500$54b2a8c0@wipro.com>
From: "Usha Iyer" <usha.iyer@wipro.com>
To: "Blatherwick Peter" <Peter_Blatherwick@Mitel.COM>,
        "megaco" <megaco@ietf.org>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
References: <29B5A21C13C8D51190F900805F65B4EC239D83@rndex50.ottawa.mitel.com>
Subject: Re: [Megaco] Doubt on package extension
Date: Thu, 31 Jan 2002 22:34:37 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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

This is a multi-part message in MIME format.

------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0D78_01C1AAA7.76BF8D90"

------=_NextPart_000_0D78_01C1AAA7.76BF8D90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Peter/All,

    The IGAdditions doc does say that the ToneGen and ToneDet packages =
are designed for extension and not for direct control... however i was =
unable to locate the text that addresses my query .
I should have mentioned it but what i quoted was just an example. I'd =
just like to know whether it is illegal (not whether it is confusing) =
for the base package (if published) to refer to parameter values defined =
in the packages that extend it and not just for the specific example =
that i quoted=20
( Acc. to Troy's mail , all the options that i quoted are allowed & you =
also say  that it is not illegal. )

TIA,
usha
  =20
  ----- Original Message -----=20
  From: Blatherwick, Peter=20
  To: 'usha.iyer@wipro.com' ; megaco=20
  Cc: 'Tom-PT Taylor'=20
  Sent: Thursday, January 31, 2002 9:19 PM
  Subject: RE: [Megaco] Doubt on package extension


  Just to confirm Tom's interpretation is correct, and answer Usha's =
question. =20

  Since the parameter is not defined in the base package, must use the =
extended package to address it.  Also, since in this case the base class =
(tonegen) has no function of its own, just defines signals but no =
parameters, it is dubious to me an implementation should even expose it =
-- just expose the extended packages.  It is not "illegal" to expose the =
base package in cases such as this, just useless and confusing. =20

  I believe the IG text on this was made quite clear, hence v2 should =
now be also.  Have to admit, I have not specifically checked...

  -- Peter Blatherwick

  -----Original Message-----
  From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
  Sent: January 30, 2002 09:59
  To: 'usha.iyer@wipro.com'; megaco
  Subject: RE: [Megaco] Doubt on package extension


  This doesn't feel right to me, and the cases are not exactly the same. =
 Here
  we have a parameter value which is unknown in the base package.  Even =
though
  toneGen is known there, the parameter value is not.  In my view this =
means
  you have to address that value through the extension which defined it =
(or
  extensions of that extension).


  -----Original Message-----
  From: usha.iyer@wipro.com [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 9:35 AM
  To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco
  Subject: Re: [Megaco] Doubt on package extension


  Is option A invalid for the reason that tonegen package is designed =
only for
  extension,or does the rule apply to any base package ?
  =20
      Acc to  12.4 of AVD_2128 =20
  ---- For example, if Package A defines event e1, and Package B extends
  Package A, then B/e1 is an event for a termination implementing =
Package B.
  By definition, the MG MUST also implement the base Package, but it =
optional
  to publish the base package as an allowed interface. If it does =
publish A,
  then A would be reported on the Package Descriptor in AuditValue as =
well as
  B, and event A/e1 would be available on a termination. If the MG does =
not
  publish A, then only B/e1 would be available=20
  ----
  =20
  Going by the above , option A  is allowed if tonegen package is =
published .=20
  =20
  TIA,
  usha
  ----- Original Message -----=20
  From: Taylor, Tom-PT [CAR:B800:EXCH]=20
  To: 'Usha Iyer' ; megaco@ietf.org=20
  Sent: Wednesday, January 30, 2002 7:37 PM
  Subject: RE: [Megaco] Doubt on package extension


  Assuming DTMFgen defines d0 as both a signal and a toneId, and =
similarly for
  cw in callProgToneGen, then either B or C is valid.

  -----Original Message-----
  From: Usha Iyer [mailto:usha.iyer@wipro.com]
  Sent: Wednesday, January 30, 2002 3:01 AM
  To: megaco@ietf.org
  Subject: [Megaco] Doubt on package extension


  Hi ,
  =20
  DTMF Gen and Call ProgressToneGen pkg both extend tone gen package . =20
  So for a termination that supports ToneGen, DTMFGen and Call =
ProgToneGen Pkg
  , suppose i want to play d0 follwed by call  waiting tone , which of =
the
  foll apply .=20
  =20
  A - tonegen/playtone(toneid list=3D d0,cw )=20
  B -dtmfgen/playtone(toneid list=3D d0 )  followed by
  callprogtonegen/playtone(toneid list=3D cw )
  C -dtmfgen/d0 followed by callprogtonegen/cw=20
  =20
  =20
  Reg
  Usha

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

------=_NextPart_000_0D78_01C1AAA7.76BF8D90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>Hi =
Peter/All,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp;&nbsp;=20
The&nbsp;IGAdditions doc does say that the ToneGen and ToneDet packages =
are=20
designed for extension and not for direct control...&nbsp;however i was =
unable=20
to locate the&nbsp;text that&nbsp;addresses my query .</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>I </FONT><FONT =
face=3DArial=20
color=3D#008080 size=3D2>should have mentioned&nbsp;it but what=20
i&nbsp;quoted&nbsp;was just an&nbsp;example.&nbsp;</FONT><FONT =
face=3DArial=20
color=3D#008080 size=3D2>I'd&nbsp;just like to know whether&nbsp;it is =
illegal (not=20
whether it&nbsp;is confusing) for the base package (if published) to =
refer to=20
parameter values defined in the packages that extend it&nbsp;and =
not&nbsp;just=20
for the specific example that i quoted </FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>(&nbsp;Acc. to Troy's =
mail&nbsp;, all=20
the&nbsp;options that i quoted are allowed&nbsp;&amp; you also say =
&nbsp;that it=20
is not illegal.&nbsp;)</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>TIA,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>usha</FONT></DIV>
<DIV><FONT face=3DArial color=3D#008080 size=3D2>&nbsp;&nbsp; =
</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3DPeter_Blatherwick@Mitel.COM=20
  href=3D"mailto:Peter_Blatherwick@Mitel.COM">Blatherwick, Peter</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dusha.iyer@wipro.com=20
  href=3D"mailto:'usha.iyer@wipro.com'">'usha.iyer@wipro.com'</A> ; <A=20
  title=3Dmegaco@ietf.org href=3D"mailto:megaco@ietf.org">megaco</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dtaylor@nortelnetworks.com=20
  href=3D"mailto:taylor@nortelnetworks.com">'Tom-PT Taylor'</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 31, =
2002 9:19=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Megaco] Doubt on =
package=20
  extension</DIV>
  <DIV><FONT face=3DArial color=3D#008080 size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT face=3DArial=20
  color=3D#008080 size=3D2></FONT><FONT face=3DArial color=3D#008080 =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#008080 size=3D2></FONT><FONT face=3DArial =
color=3D#008080=20
  size=3D2></FONT><BR></DIV>Just to confirm Tom's interpretation is =
correct, and=20
  answer Usha's question.&nbsp; <BR><BR>Since the parameter is not =
defined in=20
  the base package, must use the extended package to address it.&nbsp; =
Also,=20
  since in this case the base class (tonegen) has no function of its =
own, just=20
  defines signals but no parameters, it is dubious to me an =
implementation=20
  should even expose it -- just expose the extended packages.&nbsp; It =
is not=20
  "illegal" to expose the base package in cases such as this, just =
useless and=20
  confusing.&nbsp; <BR><BR>I believe the IG text on this was made quite =
clear,=20
  hence v2 should now be also.&nbsp; Have to admit, I have not =
specifically=20
  checked...<BR><BR>-- Peter Blatherwick<BR><BR>-----Original=20
  Message-----<BR>From: Tom-PT Taylor=20
  [mailto:taylor@nortelnetworks.com]<BR>Sent: January 30, 2002 =
09:59<BR>To: <A=20
  href=3D"mailto:'usha.iyer@wipro.com'">'usha.iyer@wipro.com'</A>;=20
  megaco<BR>Subject: RE: [Megaco] Doubt on package =
extension<BR><BR><BR>This=20
  doesn't feel right to me, and the cases are not exactly the =
same.&nbsp;=20
  Here<BR>we have a parameter value which is unknown in the base =
package.&nbsp;=20
  Even though<BR>toneGen is known there, the parameter value is =
not.&nbsp; In my=20
  view this means<BR>you have to address that value through the =
extension which=20
  defined it (or<BR>extensions of that =
extension).<BR><BR><BR>-----Original=20
  Message-----<BR>From: <A=20
  href=3D"mailto:usha.iyer@wipro.com">usha.iyer@wipro.com</A>=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 9:35 =

  AM<BR>To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco<BR>Subject: Re: =
[Megaco]=20
  Doubt on package extension<BR><BR><BR>Is option A invalid for the =
reason that=20
  tonegen package is designed only for<BR>extension,or does the rule =
apply to=20
  any base package ?<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp; Acc to&nbsp; 12.4 =
of=20
  AVD_2128&nbsp; <BR>---- For example, if Package A defines event e1, =
and=20
  Package B extends<BR>Package A, then B/e1 is an event for a =
termination=20
  implementing Package B.<BR>By definition, the MG MUST also implement =
the base=20
  Package, but it optional<BR>to publish the base package as an allowed=20
  interface. If it does publish A,<BR>then A would be reported on the =
Package=20
  Descriptor in AuditValue as well as<BR>B, and event A/e1 would be =
available on=20
  a termination. If the MG does not<BR>publish A, then only B/e1 would =
be=20
  available <BR>----<BR>&nbsp;<BR>Going by the above , option A&nbsp; is =
allowed=20
  if tonegen package is published . <BR>&nbsp;<BR>TIA,<BR>usha<BR>----- =
Original=20
  Message ----- <BR>From: Taylor, Tom-PT [CAR:B800:EXCH] <BR>To: 'Usha =
Iyer' ;=20
  <A href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A> <BR>Sent: =
Wednesday,=20
  January 30, 2002 7:37 PM<BR>Subject: RE: [Megaco] Doubt on package=20
  extension<BR><BR><BR>Assuming DTMFgen defines d0 as both a signal and =
a=20
  toneId, and similarly for<BR>cw in callProgToneGen, then either B or C =
is=20
  valid.<BR><BR>-----Original Message-----<BR>From: Usha Iyer=20
  [mailto:usha.iyer@wipro.com]<BR>Sent: Wednesday, January 30, 2002 3:01 =

  AM<BR>To: <A =
href=3D"mailto:megaco@ietf.org">megaco@ietf.org</A><BR>Subject:=20
  [Megaco] Doubt on package extension<BR><BR><BR>Hi ,<BR>&nbsp;<BR>DTMF =
Gen and=20
  Call ProgressToneGen pkg both extend tone gen package .&nbsp; <BR>So =
for a=20
  termination that supports ToneGen, DTMFGen and Call ProgToneGen =
Pkg<BR>,=20
  suppose i want to play d0 follwed by call&nbsp; waiting tone , which =
of=20
  the<BR>foll apply . <BR>&nbsp;<BR>A - tonegen/playtone(toneid list=3D =
d0,cw )=20
  <BR>B -dtmfgen/playtone(toneid list=3D d0 )&nbsp; followed=20
  by<BR>callprogtonegen/playtone(toneid list=3D cw )<BR>C -dtmfgen/d0 =
followed by=20
  callprogtonegen/cw=20
  =
<BR>&nbsp;<BR>&nbsp;<BR>Reg<BR>Usha<BR><BR>______________________________=
_________________<BR>Megaco=20
  mailing list<BR><A =
href=3D"mailto:Megaco@ietf.org">Megaco@ietf.org</A><BR><A=20
  =
href=3D"https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.=
org/mailman/listinfo/megaco</A></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0D78_01C1AAA7.76BF8D90--



------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

**************************Disclaimer************************************
      


Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.



 ********************************************************************

------=_NextPartTM-000-fb534031-1658-11d6-a941-00b0d0d06be8--


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



From megaco-admin@ietf.org  Thu Jan 31 13:44:48 2002
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 NAA07569
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 13:44:48 -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 NAA11504;
	Thu, 31 Jan 2002 13:20:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11476
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 13:20:42 -0500 (EST)
Received: from zzzconn03.fibre.com (207-104-129-169.afc.com [207.104.129.169])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06797
	for <megaco@ietf.org>; Thu, 31 Jan 2002 13:20:38 -0500 (EST)
Received: FROM xconn01.fibre.com BY zzzconn03.fibre.com ; Thu Jan 31 10:13:44 2002 -0800
Received: by xconn01.fibre.com with Internet Mail Service (5.5.2653.19)
	id <TGCG7A96>; Thu, 31 Jan 2002 07:48:57 -0800
Message-ID: <2525B519863CD311907600A0C9AB1B83036F2D33@zzzmail01.fibre.com>
From: Donald Houck <Donald.Houck@afc.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 31 Jan 2002 07:39:01 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Permanent signaling state
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

Hi All,

Is there a permanent signaling state equivalence in the MEGACO world?  If so
what would the call flow look like?

Also, does a Metallic Loop Testing Package exist if so when will it be
released?

Thanks,

Don

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


From daemon@optimus.ietf.org  Thu Jan 31 13:44:49 2002
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 NAA07579
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 13:44:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA12914
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 13:44:52 -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 NAA11504;
	Thu, 31 Jan 2002 13:20:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11476
	for <megaco@optimus.ietf.org>; Thu, 31 Jan 2002 13:20:42 -0500 (EST)
Received: from zzzconn03.fibre.com (207-104-129-169.afc.com [207.104.129.169])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06797
	for <megaco@ietf.org>; Thu, 31 Jan 2002 13:20:38 -0500 (EST)
Received: FROM xconn01.fibre.com BY zzzconn03.fibre.com ; Thu Jan 31 10:13:44 2002 -0800
Received: by xconn01.fibre.com with Internet Mail Service (5.5.2653.19)
	id <TGCG7A96>; Thu, 31 Jan 2002 07:48:57 -0800
Message-ID: <2525B519863CD311907600A0C9AB1B83036F2D33@zzzmail01.fibre.com>
From: Donald Houck <Donald.Houck@afc.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 31 Jan 2002 07:39:01 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Permanent signaling state
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

Hi All,

Is there a permanent signaling state equivalence in the MEGACO world?  If so
what would the call flow look like?

Also, does a Metallic Loop Testing Package exist if so when will it be
released?

Thanks,

Don

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



From megaco-admin@ietf.org  Thu Jan 31 14:26:51 2002
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 OAA09007
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:26:51 -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 OAA13917;
	Thu, 31 Jan 2002 14:04:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13870
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:04:36 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08234
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:04:30 -0500 (EST)
Received: through eSafe SMTP Relay 1011795511; Thu Jan 31 21:03:21 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6GC01>; Thu, 31 Jan 2002 20:37:18 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF018E8083@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Terry L Anderson <tla@lucent.com>,
        Christian Groves
	 <Christian.Groves@ericsson.com.au>
Cc: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 20:37:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA86.4EE318D0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA86.4EE318D0
Content-Type: text/plain;
	charset="iso-8859-1"

I have a question related to this.  Consider the following requirements:

1.	Commands within a Transaction are executed sequentially. (8).
2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors.
3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1).
4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1).

Now, suppose I have a wildcarded command with multiple descriptors.  Rules 1
and 3 seem to imply that I must process all descriptors for the first
termination before I process any descriptors for the second termination.  On
the other hand, rules 2 and 4 seem to allow bulk handling of a single
descriptor for all terminations simultaneously, before handling the next
descriptor in the same bulk fashion.  This facilitates efficient storage if,
for example, a digit map or requested event is specified for a wildcarded
termination.

Is either interpretation permitted?  The previous discussion in this thread
suggests that it is, because if an error occurs, the command should still be
completed for each matching termination, and it could be in either case.

Raphael Tryster

	-----Original Message-----
	From:	Terry L Anderson [SMTP:tla@lucent.com]
	Sent:	Thursday, 31 January, 2002 4:45 PM
	To:	Christian Groves
	Cc:	vidya g; megaco@ietf.org
	Subject:	Re: [Megaco] QRY about the failed command

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed.

	Christian Groves wrote:

	> G'Day Terry,
	>
	> The behaviour already is mentioned in 8.0 the paragraph after "At
the
	> first failing Command...". States: "Commands may be marked as
"Optional"
	> which can override this behaviour -  if a command marked as
Optional
	> results in an error, subsequent commands in the Transaction will
be
	> executed.  If a command fails, the MG shall as far as possible
restore
	> the state that existed prior to the attempted execution of the
command
	> before continuing with command processing."
	>
	> Regards, Christian
	>
	> Terry L Anderson wrote:
	> >
	> > The statement (in 8.0) IS misleading but your understanding is
also incorrect.
	> >
	> > 8.2.2 (including changes from IG 6.36) make it clear that the
first non-optional command that fails ends processing of
	> > the entire Transaction (not just the action).
	> >
	> > Perhaps the exception indicated in 8.2.2 should also be
mentioned in 8.0.
	> >
	> > Do folks think this sentence should be corrected in IG?
	> >
	> > vidya g wrote:
	> >
	> > > Hi all
	> > >
	> > >   In RFC, page number 61 it says that
	> > >
	> > >  "  At the first failing Command in a Transaction, processing
of the remaining Commands in that Transaction stops."
	> > >
	> > >   This statement is some what confusing. What I understand is
even if a non optional
	> > > command fails in an action, the action will be cancelled and
the next action will be taken
	> > > for processing and the commands in that action will be
processed.. is that right .. ?
	> > >
	> > > vdy
	> > >
	> > >
	> > > _______________________________________________
	> > > Megaco mailing list
	> > > Megaco@ietf.org
	> > > https://www1.ietf.org/mailman/listinfo/megaco

	--

	------------------------------------------------------------
	Terry L Anderson              mailto:tla@lucent.com
	Tel:908.582.7013   Fax:908.582.6729
	Lucent Technologies/INS/Voice Over IP Access Networks
	Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
	http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


	*** eSafe scanned this email for malicious content ***
	*** IMPORTANT: Do not open attachments from unrecognized senders
*** << File: Card for Terry L Anderson >> 

------_=_NextPart_001_01C1AA86.4EE318D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question related to this.&nbsp;=
 Consider the following requirements:</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">Commands</FONT><FONT SIZE=3D=
2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">within a Transacti=
on are executed sequentially.</FONT><FONT SIZE=3D2 FACE=3D"Arial"> (8).</=
FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The descriptors SHALL be processed in t=
he order in which</FONT><FONT SIZE=3D2 FACE=3D"Arial"> they appear (7.2).=
&nbsp; Exception (7.1.14.1):</FONT> <FONT SIZE=3D2 FACE=3D"Arial">It is</=
FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">=
permissible for a digit map completion event within an Events</FONT><FONT=
 SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Descriptor=
 to refer by name to a DigitMap which is defined by a</FONT><FONT SIZE=3D=
2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">DigitMap Descripto=
r within the same command, regardless of the</FONT><FONT SIZE=3D2 FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">transmitted order of the re=
spective descriptors.</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When the TerminationId of a</FONT><FONT=
 SIZE=3D2 FACE=3D"Arial"></FONT>&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> comm=
and is wildcarded, the effect shall be as if the command was</FONT><FONT =
SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">repeated wi=
th each of the TerminationIds matched.</FONT><FONT SIZE=3D2 FACE=3D"Arial=
"> (7.1.1).</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The order of attempts when multiple</FO=
NT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Te=
rminationIDs match is not specified.</FONT><FONT SIZE=3D2 FACE=3D"Arial">=
 (7.2.1).</FONT></LI>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Now, suppose I have a wildcarded command=
 with multiple descriptors.&nbsp; Rules 1 and 3 seem to imply that I must=
 process all descriptors for the first termination before I process any d=
escriptors for the second termination.&nbsp; On the other hand, rules 2 a=
nd 4 seem to allow bulk handling of a single descriptor for all terminati=
ons simultaneously, before handling the next descriptor in the same bulk =
fashion.&nbsp; This facilitates efficient storage if, for example, a digi=
t map or requested event is specified for a wildcarded termination.</FONT=
></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is either interpretation permitted?&nbsp=
; The previous discussion in this thread suggests that it is, because if =
an error occurs, the command should still be completed for each matching =
termination, and it could be in either case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Terry L Anderson [=
SMTP:tla@lucent.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 4:45 PM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Megaco] QRY =
about the failed command</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">You are right.&nbsp; I (and Vidya =
G) should have read a little further.&nbsp; I agree, no change is needed.=
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves wrote:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; G'Day Terry,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The behaviour already is men=
tioned in 8.0 the paragraph after &quot;At the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; first failing Command...&quo=
t;. States: &quot;Commands may be marked as &quot;Optional&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; which can override this beha=
viour -&nbsp; if a command marked as Optional</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; results in an error, subsequ=
ent commands in the Transaction will be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; executed.&nbsp; If a command=
 fails, the MG shall as far as possible restore</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; the state that existed prior=
 to the attempted execution of the command</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; before continuing with comma=
nd processing.&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Terry L Anderson wrote:</FON=
T>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; The statement (in 8.0) =
IS misleading but your understanding is also incorrect.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; 8.2.2 (including change=
s from IG 6.36) make it clear that the first non-optional command that fa=
ils ends processing of</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; the entire Transaction (=
not just the action).</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Perhaps the exception i=
ndicated in 8.2.2 should also be mentioned in 8.0.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Do folks think this sen=
tence should be corrected in IG?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; vidya g wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Hi all</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp;&nbsp; In RFC=
, page number 61 it says that</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp; &quot;&nbsp;=
 At the first failing Command in a Transaction, processing of the remaini=
ng Commands in that Transaction stops.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp;&nbsp; This s=
tatement is some what confusing. What I understand is even if a non optio=
nal</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; command fails in a=
n action, the action will be cancelled and the next action will be taken<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; for processing and=
 the commands in that action will be processed.. is that right .. ?</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; vdy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; __________________=
_____________________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco mailing lis=
t</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco@ietf.org</F=
ONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; <A HREF=3D"https:/=
/www1.ietf.org/mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ie=
tf.org/mailman/listinfo/megaco</A></FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">----------------------------------=
--------------------------</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Terry L Anderson&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A HREF=3D"=
mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Tel:908.582.7013&nbsp;&nbsp; Fax:=
908.582.6729</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Lucent Technologies/INS/Voice Ove=
r IP Access Networks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Rm 2B-121, 600 Mountain Av, Murra=
y Hill, NJ 07974</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"http://its.lucent.com/=
~tla" TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) =
<A HREF=3D"http://www.gti.net/tla" TARGET=3D"_blank">http://www.gti.net/t=
la</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">*** eSafe scanned this email for m=
alicious content ***</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">*** IMPORTANT: Do not open attach=
ments from unrecognized senders&nbsp; *** &lt;&lt; File: Card for Terry L=
 Anderson &gt;&gt; </FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1AA86.4EE318D0--

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


From daemon@ns.ietf.org  Thu Jan 31 14:26:52 2002
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 OAA09017
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:26:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA15530
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 14:26:55 -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 OAA13917;
	Thu, 31 Jan 2002 14:04:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13870
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:04:36 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08234
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:04:30 -0500 (EST)
Received: through eSafe SMTP Relay 1011795511; Thu Jan 31 21:03:21 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6GC01>; Thu, 31 Jan 2002 20:37:18 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF018E8083@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Terry L Anderson <tla@lucent.com>,
        Christian Groves
	 <Christian.Groves@ericsson.com.au>
Cc: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 20:37:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA86.4EE318D0"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA86.4EE318D0
Content-Type: text/plain;
	charset="iso-8859-1"

I have a question related to this.  Consider the following requirements:

1.	Commands within a Transaction are executed sequentially. (8).
2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors.
3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1).
4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1).

Now, suppose I have a wildcarded command with multiple descriptors.  Rules 1
and 3 seem to imply that I must process all descriptors for the first
termination before I process any descriptors for the second termination.  On
the other hand, rules 2 and 4 seem to allow bulk handling of a single
descriptor for all terminations simultaneously, before handling the next
descriptor in the same bulk fashion.  This facilitates efficient storage if,
for example, a digit map or requested event is specified for a wildcarded
termination.

Is either interpretation permitted?  The previous discussion in this thread
suggests that it is, because if an error occurs, the command should still be
completed for each matching termination, and it could be in either case.

Raphael Tryster

	-----Original Message-----
	From:	Terry L Anderson [SMTP:tla@lucent.com]
	Sent:	Thursday, 31 January, 2002 4:45 PM
	To:	Christian Groves
	Cc:	vidya g; megaco@ietf.org
	Subject:	Re: [Megaco] QRY about the failed command

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed.

	Christian Groves wrote:

	> G'Day Terry,
	>
	> The behaviour already is mentioned in 8.0 the paragraph after "At
the
	> first failing Command...". States: "Commands may be marked as
"Optional"
	> which can override this behaviour -  if a command marked as
Optional
	> results in an error, subsequent commands in the Transaction will
be
	> executed.  If a command fails, the MG shall as far as possible
restore
	> the state that existed prior to the attempted execution of the
command
	> before continuing with command processing."
	>
	> Regards, Christian
	>
	> Terry L Anderson wrote:
	> >
	> > The statement (in 8.0) IS misleading but your understanding is
also incorrect.
	> >
	> > 8.2.2 (including changes from IG 6.36) make it clear that the
first non-optional command that fails ends processing of
	> > the entire Transaction (not just the action).
	> >
	> > Perhaps the exception indicated in 8.2.2 should also be
mentioned in 8.0.
	> >
	> > Do folks think this sentence should be corrected in IG?
	> >
	> > vidya g wrote:
	> >
	> > > Hi all
	> > >
	> > >   In RFC, page number 61 it says that
	> > >
	> > >  "  At the first failing Command in a Transaction, processing
of the remaining Commands in that Transaction stops."
	> > >
	> > >   This statement is some what confusing. What I understand is
even if a non optional
	> > > command fails in an action, the action will be cancelled and
the next action will be taken
	> > > for processing and the commands in that action will be
processed.. is that right .. ?
	> > >
	> > > vdy
	> > >
	> > >
	> > > _______________________________________________
	> > > Megaco mailing list
	> > > Megaco@ietf.org
	> > > https://www1.ietf.org/mailman/listinfo/megaco

	--

	------------------------------------------------------------
	Terry L Anderson              mailto:tla@lucent.com
	Tel:908.582.7013   Fax:908.582.6729
	Lucent Technologies/INS/Voice Over IP Access Networks
	Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
	http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


	*** eSafe scanned this email for malicious content ***
	*** IMPORTANT: Do not open attachments from unrecognized senders
*** << File: Card for Terry L Anderson >> 

------_=_NextPart_001_01C1AA86.4EE318D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question related to this.&nbsp;=
 Consider the following requirements:</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">Commands</FONT><FONT SIZE=3D=
2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">within a Transacti=
on are executed sequentially.</FONT><FONT SIZE=3D2 FACE=3D"Arial"> (8).</=
FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The descriptors SHALL be processed in t=
he order in which</FONT><FONT SIZE=3D2 FACE=3D"Arial"> they appear (7.2).=
&nbsp; Exception (7.1.14.1):</FONT> <FONT SIZE=3D2 FACE=3D"Arial">It is</=
FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">=
permissible for a digit map completion event within an Events</FONT><FONT=
 SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Descriptor=
 to refer by name to a DigitMap which is defined by a</FONT><FONT SIZE=3D=
2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">DigitMap Descripto=
r within the same command, regardless of the</FONT><FONT SIZE=3D2 FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">transmitted order of the re=
spective descriptors.</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When the TerminationId of a</FONT><FONT=
 SIZE=3D2 FACE=3D"Arial"></FONT>&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> comm=
and is wildcarded, the effect shall be as if the command was</FONT><FONT =
SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">repeated wi=
th each of the TerminationIds matched.</FONT><FONT SIZE=3D2 FACE=3D"Arial=
"> (7.1.1).</FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The order of attempts when multiple</FO=
NT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Te=
rminationIDs match is not specified.</FONT><FONT SIZE=3D2 FACE=3D"Arial">=
 (7.2.1).</FONT></LI>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Now, suppose I have a wildcarded command=
 with multiple descriptors.&nbsp; Rules 1 and 3 seem to imply that I must=
 process all descriptors for the first termination before I process any d=
escriptors for the second termination.&nbsp; On the other hand, rules 2 a=
nd 4 seem to allow bulk handling of a single descriptor for all terminati=
ons simultaneously, before handling the next descriptor in the same bulk =
fashion.&nbsp; This facilitates efficient storage if, for example, a digi=
t map or requested event is specified for a wildcarded termination.</FONT=
></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is either interpretation permitted?&nbsp=
; The previous discussion in this thread suggests that it is, because if =
an error occurs, the command should still be completed for each matching =
termination, and it could be in either case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Terry L Anderson [=
SMTP:tla@lucent.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 4:45 PM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Megaco] QRY =
about the failed command</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">You are right.&nbsp; I (and Vidya =
G) should have read a little further.&nbsp; I agree, no change is needed.=
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves wrote:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; G'Day Terry,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The behaviour already is men=
tioned in 8.0 the paragraph after &quot;At the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; first failing Command...&quo=
t;. States: &quot;Commands may be marked as &quot;Optional&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; which can override this beha=
viour -&nbsp; if a command marked as Optional</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; results in an error, subsequ=
ent commands in the Transaction will be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; executed.&nbsp; If a command=
 fails, the MG shall as far as possible restore</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; the state that existed prior=
 to the attempted execution of the command</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; before continuing with comma=
nd processing.&quot;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards, Christian</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Terry L Anderson wrote:</FON=
T>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; The statement (in 8.0) =
IS misleading but your understanding is also incorrect.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; 8.2.2 (including change=
s from IG 6.36) make it clear that the first non-optional command that fa=
ils ends processing of</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; the entire Transaction (=
not just the action).</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Perhaps the exception i=
ndicated in 8.2.2 should also be mentioned in 8.0.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Do folks think this sen=
tence should be corrected in IG?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; vidya g wrote:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Hi all</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp;&nbsp; In RFC=
, page number 61 it says that</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp; &quot;&nbsp;=
 At the first failing Command in a Transaction, processing of the remaini=
ng Commands in that Transaction stops.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;&nbsp;&nbsp; This s=
tatement is some what confusing. What I understand is even if a non optio=
nal</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; command fails in a=
n action, the action will be cancelled and the next action will be taken<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; for processing and=
 the commands in that action will be processed.. is that right .. ?</FONT=
>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; vdy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; __________________=
_____________________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco mailing lis=
t</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco@ietf.org</F=
ONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; <A HREF=3D"https:/=
/www1.ietf.org/mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ie=
tf.org/mailman/listinfo/megaco</A></FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">----------------------------------=
--------------------------</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Terry L Anderson&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A HREF=3D"=
mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Tel:908.582.7013&nbsp;&nbsp; Fax:=
908.582.6729</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Lucent Technologies/INS/Voice Ove=
r IP Access Networks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Rm 2B-121, 600 Mountain Av, Murra=
y Hill, NJ 07974</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"http://its.lucent.com/=
~tla" TARGET=3D"_blank">http://its.lucent.com/~tla</A> (Lucent internal) =
<A HREF=3D"http://www.gti.net/tla" TARGET=3D"_blank">http://www.gti.net/t=
la</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">*** eSafe scanned this email for m=
alicious content ***</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">*** IMPORTANT: Do not open attach=
ments from unrecognized senders&nbsp; *** &lt;&lt; File: Card for Terry L=
 Anderson &gt;&gt; </FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1AA86.4EE318D0--

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



From megaco-admin@ietf.org  Thu Jan 31 14:34:29 2002
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 OAA09348
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:34:29 -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 OAA14966;
	Thu, 31 Jan 2002 14:20:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14899
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:19:54 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08737
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:19:50 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0VJJpn03532
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:19:52 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA24316; Thu, 31 Jan 2002 14:19:49 -0500 (EST)
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA24312; Thu, 31 Jan 2002 14:19:47 -0500 (EST)
Message-ID: <3C599828.31F3F3D6@bell-labs.com>
Date: Thu, 31 Jan 2002 14:16:56 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: MEGACO list <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] old &/or searchable archive?
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: 7bit


Is the old, searchable archive available somewhere?
It used to be at

http://standards.nortelnetworks.com/archives/megaco.html

Is there a searchable form of the new archive somewhere?


The files at ftp://ftp.ietf.org/ietf-mail-archive/megaco/
are a pain.

-troy

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


From daemon@ns.ietf.org  Thu Jan 31 14:34:30 2002
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 OAA09359
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:34:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA16708
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 14:34:33 -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 OAA14966;
	Thu, 31 Jan 2002 14:20:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14899
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:19:54 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08737
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:19:50 -0500 (EST)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g0VJJpn03532
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:19:52 -0500 (EST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA24316; Thu, 31 Jan 2002 14:19:49 -0500 (EST)
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id OAA24312; Thu, 31 Jan 2002 14:19:47 -0500 (EST)
Message-ID: <3C599828.31F3F3D6@bell-labs.com>
Date: Thu, 31 Jan 2002 14:16:56 -0500
From: Troy Cauble <troy@bell-labs.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: MEGACO list <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] old &/or searchable archive?
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: 7bit


Is the old, searchable archive available somewhere?
It used to be at

http://standards.nortelnetworks.com/archives/megaco.html

Is there a searchable form of the new archive somewhere?


The files at ftp://ftp.ietf.org/ietf-mail-archive/megaco/
are a pain.

-troy

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



From megaco-admin@ietf.org  Thu Jan 31 14:37:51 2002
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 OAA09462
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:37:50 -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 OAA15679;
	Thu, 31 Jan 2002 14:28:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15645
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:28:38 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09103
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:28:33 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VJRdc12927;
	Thu, 31 Jan 2002 14:27:40 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAYAX5>; Thu, 31 Jan 2002 14:27:39 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01C21A1B@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Raphael Tryster <raphael@tdsoft.com>, Terry L Anderson
	 <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 14:27:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA8D.56F10030"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA8D.56F10030
Content-Type: text/plain;
	charset="iso-8859-1"

You should process the full command on each termination is turn, just as if
the terminations had been expressed individually in their own command.
Requirement 4 (by the numbering below) indicates that it is up to the MG to
figure which order the terms go in, if more than one matches the wildcard.
 
Kevin

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Thursday, January 31, 2002 1:37 PM
To: Terry L Anderson; Christian Groves
Cc: vidya g; megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



I have a question related to this.  Consider the following requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 

2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 

3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 

4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1). 


Now, suppose I have a wildcarded command with multiple descriptors.  Rules 1
and 3 seem to imply that I must process all descriptors for the first
termination before I process any descriptors for the second termination.  On
the other hand, rules 2 and 4 seem to allow bulk handling of a single
descriptor for all terminations simultaneously, before handling the next
descriptor in the same bulk fashion.  This facilitates efficient storage if,
for example, a digit map or requested event is specified for a wildcarded
termination.

Is either interpretation permitted?  The previous discussion in this thread
suggests that it is, because if an error occurs, the command should still be
completed for each matching termination, and it could be in either case.

Raphael Tryster 

	BM__MailData-----Original Message----- 
From:   Terry L Anderson [SMTP:tla@lucent.com] 
Sent:   Thursday, 31 January, 2002 4:45 PM 
To:     Christian Groves 
Cc:     vidya g; megaco@ietf.org 
Subject:        Re: [Megaco] QRY about the failed command 

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed. 

	Christian Groves wrote: 

	> G'Day Terry, 
> 
> The behaviour already is mentioned in 8.0 the paragraph after "At the 
> first failing Command...". States: "Commands may be marked as "Optional" 
> which can override this behaviour -  if a command marked as Optional 
> results in an error, subsequent commands in the Transaction will be 
> executed.  If a command fails, the MG shall as far as possible restore 
> the state that existed prior to the attempted execution of the command 
> before continuing with command processing." 
> 
> Regards, Christian 
> 
> Terry L Anderson wrote: 
> > 
> > The statement (in 8.0) IS misleading but your understanding is also
incorrect. 
> > 
> > 8.2.2 (including changes from IG 6.36) make it clear that the first
non-optional command that fails ends processing of

	> > the entire Transaction (not just the action). 
> > 
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in
8.0. 
> > 
> > Do folks think this sentence should be corrected in IG? 
> > 
> > vidya g wrote: 
> > 
> > > Hi all 
> > > 
> > >   In RFC, page number 61 it says that 
> > > 
> > >  "  At the first failing Command in a Transaction, processing of the
remaining Commands in that Transaction stops."

	> > > 
> > >   This statement is some what confusing. What I understand is even if
a non optional 
> > > command fails in an action, the action will be cancelled and the next
action will be taken 
> > > for processing and the commands in that action will be processed.. is
that right .. ? 
> > > 
> > > vdy 
> > > 
> > > 
> > > _______________________________________________ 
> > > Megaco mailing list 
> > > Megaco@ietf.org 
> > > https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  

	-- 

	------------------------------------------------------------ 
Terry L Anderson              mailto:tla@lucent.com <mailto:tla@lucent.com>

Tel:908.582.7013   Fax:908.582.6729 
Lucent Technologies/INS/Voice Over IP Access Networks 
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
http://its.lucent.com/~tla <http://its.lucent.com/~tla>  (Lucent internal)
http://www.gti.net/tla <http://www.gti.net/tla>  


	*** eSafe scanned this email for malicious content *** 
*** IMPORTANT: Do not open attachments from unrecognized senders  *** <<
File: Card for Terry L Anderson >> 


------_=_NextPart_001_01C1AA8D.56F10030
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>

<META content="MSHTML 5.50.4912.300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=810272319-31012002><FONT face=Arial color=#0000ff size=2>You 
should process the full command on each termination is turn, just as if the 
terminations had been expressed individually in their own command.&nbsp; 
Requirement 4 (by the numbering below) indicates that it is up to the MG to 
figure which order the terms go in, if more than one matches the 
wildcard.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=810272319-31012002><FONT face=Arial color=#0000ff 
size=2>Kevin</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Raphael Tryster 
  [mailto:raphael@tdsoft.com]<BR><B>Sent:</B> Thursday, January 31, 2002 1:37 
  PM<BR><B>To:</B> Terry L Anderson; Christian Groves<BR><B>Cc:</B> vidya g; 
  megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] QRY about the failed 
  command<BR><BR></FONT></DIV>
  <P><FONT face=Arial size=2>I have a question related to this.&nbsp; Consider 
  the following requirements:</FONT> </P>
  <OL type=1>
    <LI><FONT face=Arial size=2>Commands</FONT><FONT face=Arial size=2></FONT> 
    <FONT face=Arial size=2>within a Transaction are executed 
    sequentially.</FONT><FONT face=Arial size=2> (8).</FONT> 
    <LI><FONT face=Arial size=2>The descriptors SHALL be processed in the order 
    in which</FONT><FONT face=Arial size=2> they appear (7.2).&nbsp; Exception 
    (7.1.14.1):</FONT> <FONT face=Arial size=2>It is</FONT><FONT face=Arial 
    size=2></FONT> <FONT face=Arial size=2>permissible for a digit map 
    completion event within an Events</FONT><FONT face=Arial size=2></FONT> 
    <FONT face=Arial size=2>Descriptor to refer by name to a DigitMap which is 
    defined by a</FONT><FONT face=Arial size=2></FONT> <FONT face=Arial 
    size=2>DigitMap Descriptor within the same command, regardless of 
    the</FONT><FONT face=Arial size=2></FONT> <FONT face=Arial 
    size=2>transmitted order of the respective descriptors.</FONT> 
    <LI><FONT face=Arial size=2>When the TerminationId of a</FONT><FONT 
    face=Arial size=2></FONT>&nbsp;<FONT face=Arial size=2> command is 
    wildcarded, the effect shall be as if the command was</FONT><FONT face=Arial 
    size=2></FONT> <FONT face=Arial size=2>repeated with each of the 
    TerminationIds matched.</FONT><FONT face=Arial size=2> (7.1.1).</FONT> 
    <LI><FONT face=Arial size=2>The order of attempts when multiple</FONT><FONT 
    face=Arial size=2></FONT> <FONT face=Arial size=2>TerminationIDs match is 
    not specified.</FONT><FONT face=Arial size=2> (7.2.1).</FONT> <BR></LI></OL>
  <P><FONT face=Arial size=2>Now, suppose I have a wildcarded command with 
  multiple descriptors.&nbsp; Rules 1 and 3 seem to imply that I must process 
  all descriptors for the first termination before I process any descriptors for 
  the second termination.&nbsp; On the other hand, rules 2 and 4 seem to allow 
  bulk handling of a single descriptor for all terminations simultaneously, 
  before handling the next descriptor in the same bulk fashion.&nbsp; This 
  facilitates efficient storage if, for example, a digit map or requested event 
  is specified for a wildcarded termination.</FONT></P>
  <P><FONT face=Arial size=2>Is either interpretation permitted?&nbsp; The 
  previous discussion in this thread suggests that it is, because if an error 
  occurs, the command should still be completed for each matching termination, 
  and it could be in either case.</FONT></P>
  <P><FONT face=Tahoma size=2>Raphael Tryster</FONT> </P>
  <UL>
    <P><A name=_MailData><FONT face=Arial size=2>-----Original 
    Message-----</FONT></A> <BR><B><FONT face=Arial size=2>From:&nbsp;&nbsp; 
    Terry L Anderson [SMTP:tla@lucent.com]</FONT></B> <BR><B><FONT face=Arial 
    size=2>Sent:&nbsp;&nbsp;</FONT></B> <FONT face=Arial size=2>Thursday, 31 
    January, 2002 4:45 PM</FONT> <BR><B><FONT face=Arial 
    size=2>To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT face=Arial 
    size=2>Christian Groves</FONT> <BR><B><FONT face=Arial 
    size=2>Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT face=Arial size=2>vidya 
    g; megaco@ietf.org</FONT> <BR><B><FONT face=Arial 
    size=2>Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT 
    face=Arial size=2>Re: [Megaco] QRY about the failed command</FONT> </P>
    <P><FONT face="Courier New" size=2>You are right.&nbsp; I (and Vidya G) 
    should have read a little further.&nbsp; I agree, no change is 
    needed.</FONT> </P>
    <P><FONT face="Courier New" size=2>Christian Groves wrote:</FONT> </P>
    <P><FONT face="Courier New" size=2>&gt; G'Day Terry,</FONT> <BR><FONT 
    face="Courier New" size=2>&gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; The behaviour already is mentioned in 8.0 the paragraph after 
    "At the</FONT> <BR><FONT face="Courier New" size=2>&gt; first failing 
    Command...". States: "Commands may be marked as "Optional"</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; which can override this behaviour -&nbsp; if 
    a command marked as Optional</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    results in an error, subsequent commands in the Transaction will be</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; executed.&nbsp; If a command fails, 
    the MG shall as far as possible restore</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; the state that existed prior to the attempted execution of the 
    command</FONT> <BR><FONT face="Courier New" size=2>&gt; before continuing 
    with command processing."</FONT> <BR><FONT face="Courier New" 
    size=2>&gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; Regards, 
    Christian</FONT> <BR><FONT face="Courier New" size=2>&gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; Terry L Anderson wrote:</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; The statement (in 8.0) IS misleading but your understanding 
    is also incorrect.</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; 8.2.2 (including 
    changes from IG 6.36) make it clear that the first non-optional command that 
    fails ends processing of</FONT></P>
    <P><FONT face="Courier New" size=2>&gt; &gt; the entire Transaction (not 
    just the action).</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; Perhaps the 
    exception indicated in 8.2.2 should also be mentioned in 8.0.</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; Do folks think this sentence should be 
    corrected in IG?</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; vidya g wrote:</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; Hi all</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; &gt;&nbsp;&nbsp; In RFC, page number 61 it says that</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;&nbsp; "&nbsp; At the first failing 
    Command in a Transaction, processing of the remaining Commands in that 
    Transaction stops."</FONT></P>
    <P><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;&nbsp;&nbsp; This statement is some 
    what confusing. What I understand is even if a non optional</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; command fails in an action, the 
    action will be cancelled and the next action will be taken</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; for processing and the commands in 
    that action will be processed.. is that right .. ?</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; &gt; vdy</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt; &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; 
    _______________________________________________</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; Megaco mailing list</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; Megaco@ietf.org</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; <A target=_blank 
    href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
    </P>
    <P><FONT face="Courier New" size=2>--</FONT> </P>
    <P><FONT face="Courier New" 
    size=2>------------------------------------------------------------</FONT> 
    <BR><FONT face="Courier New" size=2>Terry L 
    Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    <A href="mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT> <BR><FONT 
    face="Courier New" size=2>Tel:908.582.7013&nbsp;&nbsp; 
    Fax:908.582.6729</FONT> <BR><FONT face="Courier New" size=2>Lucent 
    Technologies/INS/Voice Over IP Access Networks</FONT> <BR><FONT 
    face="Courier New" size=2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 
    07974</FONT> <BR><FONT face="Courier New" size=2><A target=_blank 
    href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</A> (Lucent 
    internal) <A target=_blank 
    href="http://www.gti.net/tla">http://www.gti.net/tla</A></FONT> </P><BR>
    <P><FONT face="Courier New" size=2>*** eSafe scanned this email for 
    malicious content ***</FONT> <BR><FONT face="Courier New" size=2>*** 
    IMPORTANT: Do not open attachments from unrecognized senders&nbsp; *** 
    &lt;&lt; File: Card for Terry L Anderson &gt;&gt; 
</FONT></P></UL></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1AA8D.56F10030--

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


From daemon@ns.ietf.org  Thu Jan 31 14:37:52 2002
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 OAA09472
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:37:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17280
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 14:37:55 -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 OAA15679;
	Thu, 31 Jan 2002 14:28:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15645
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:28:38 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09103
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:28:33 -0500 (EST)
Received: from zrtpd00y.us.nortel.com (zrtpd00y.us.nortel.com [47.140.202.33])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VJRdc12927;
	Thu, 31 Jan 2002 14:27:40 -0500 (EST)
Received: by zrtpd00y.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <CJLAYAX5>; Thu, 31 Jan 2002 14:27:39 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C01C21A1B@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Raphael Tryster <raphael@tdsoft.com>, Terry L Anderson
	 <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: vidya g <vdy73@rediffmail.com>, megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 14:27:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA8D.56F10030"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA8D.56F10030
Content-Type: text/plain;
	charset="iso-8859-1"

You should process the full command on each termination is turn, just as if
the terminations had been expressed individually in their own command.
Requirement 4 (by the numbering below) indicates that it is up to the MG to
figure which order the terms go in, if more than one matches the wildcard.
 
Kevin

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Thursday, January 31, 2002 1:37 PM
To: Terry L Anderson; Christian Groves
Cc: vidya g; megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



I have a question related to this.  Consider the following requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 

2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 

3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 

4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1). 


Now, suppose I have a wildcarded command with multiple descriptors.  Rules 1
and 3 seem to imply that I must process all descriptors for the first
termination before I process any descriptors for the second termination.  On
the other hand, rules 2 and 4 seem to allow bulk handling of a single
descriptor for all terminations simultaneously, before handling the next
descriptor in the same bulk fashion.  This facilitates efficient storage if,
for example, a digit map or requested event is specified for a wildcarded
termination.

Is either interpretation permitted?  The previous discussion in this thread
suggests that it is, because if an error occurs, the command should still be
completed for each matching termination, and it could be in either case.

Raphael Tryster 

	BM__MailData-----Original Message----- 
From:   Terry L Anderson [SMTP:tla@lucent.com] 
Sent:   Thursday, 31 January, 2002 4:45 PM 
To:     Christian Groves 
Cc:     vidya g; megaco@ietf.org 
Subject:        Re: [Megaco] QRY about the failed command 

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed. 

	Christian Groves wrote: 

	> G'Day Terry, 
> 
> The behaviour already is mentioned in 8.0 the paragraph after "At the 
> first failing Command...". States: "Commands may be marked as "Optional" 
> which can override this behaviour -  if a command marked as Optional 
> results in an error, subsequent commands in the Transaction will be 
> executed.  If a command fails, the MG shall as far as possible restore 
> the state that existed prior to the attempted execution of the command 
> before continuing with command processing." 
> 
> Regards, Christian 
> 
> Terry L Anderson wrote: 
> > 
> > The statement (in 8.0) IS misleading but your understanding is also
incorrect. 
> > 
> > 8.2.2 (including changes from IG 6.36) make it clear that the first
non-optional command that fails ends processing of

	> > the entire Transaction (not just the action). 
> > 
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in
8.0. 
> > 
> > Do folks think this sentence should be corrected in IG? 
> > 
> > vidya g wrote: 
> > 
> > > Hi all 
> > > 
> > >   In RFC, page number 61 it says that 
> > > 
> > >  "  At the first failing Command in a Transaction, processing of the
remaining Commands in that Transaction stops."

	> > > 
> > >   This statement is some what confusing. What I understand is even if
a non optional 
> > > command fails in an action, the action will be cancelled and the next
action will be taken 
> > > for processing and the commands in that action will be processed.. is
that right .. ? 
> > > 
> > > vdy 
> > > 
> > > 
> > > _______________________________________________ 
> > > Megaco mailing list 
> > > Megaco@ietf.org 
> > > https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  

	-- 

	------------------------------------------------------------ 
Terry L Anderson              mailto:tla@lucent.com <mailto:tla@lucent.com>

Tel:908.582.7013   Fax:908.582.6729 
Lucent Technologies/INS/Voice Over IP Access Networks 
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
http://its.lucent.com/~tla <http://its.lucent.com/~tla>  (Lucent internal)
http://www.gti.net/tla <http://www.gti.net/tla>  


	*** eSafe scanned this email for malicious content *** 
*** IMPORTANT: Do not open attachments from unrecognized senders  *** <<
File: Card for Terry L Anderson >> 


------_=_NextPart_001_01C1AA8D.56F10030
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>

<META content="MSHTML 5.50.4912.300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=810272319-31012002><FONT face=Arial color=#0000ff size=2>You 
should process the full command on each termination is turn, just as if the 
terminations had been expressed individually in their own command.&nbsp; 
Requirement 4 (by the numbering below) indicates that it is up to the MG to 
figure which order the terms go in, if more than one matches the 
wildcard.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=810272319-31012002><FONT face=Arial color=#0000ff 
size=2>Kevin</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Raphael Tryster 
  [mailto:raphael@tdsoft.com]<BR><B>Sent:</B> Thursday, January 31, 2002 1:37 
  PM<BR><B>To:</B> Terry L Anderson; Christian Groves<BR><B>Cc:</B> vidya g; 
  megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] QRY about the failed 
  command<BR><BR></FONT></DIV>
  <P><FONT face=Arial size=2>I have a question related to this.&nbsp; Consider 
  the following requirements:</FONT> </P>
  <OL type=1>
    <LI><FONT face=Arial size=2>Commands</FONT><FONT face=Arial size=2></FONT> 
    <FONT face=Arial size=2>within a Transaction are executed 
    sequentially.</FONT><FONT face=Arial size=2> (8).</FONT> 
    <LI><FONT face=Arial size=2>The descriptors SHALL be processed in the order 
    in which</FONT><FONT face=Arial size=2> they appear (7.2).&nbsp; Exception 
    (7.1.14.1):</FONT> <FONT face=Arial size=2>It is</FONT><FONT face=Arial 
    size=2></FONT> <FONT face=Arial size=2>permissible for a digit map 
    completion event within an Events</FONT><FONT face=Arial size=2></FONT> 
    <FONT face=Arial size=2>Descriptor to refer by name to a DigitMap which is 
    defined by a</FONT><FONT face=Arial size=2></FONT> <FONT face=Arial 
    size=2>DigitMap Descriptor within the same command, regardless of 
    the</FONT><FONT face=Arial size=2></FONT> <FONT face=Arial 
    size=2>transmitted order of the respective descriptors.</FONT> 
    <LI><FONT face=Arial size=2>When the TerminationId of a</FONT><FONT 
    face=Arial size=2></FONT>&nbsp;<FONT face=Arial size=2> command is 
    wildcarded, the effect shall be as if the command was</FONT><FONT face=Arial 
    size=2></FONT> <FONT face=Arial size=2>repeated with each of the 
    TerminationIds matched.</FONT><FONT face=Arial size=2> (7.1.1).</FONT> 
    <LI><FONT face=Arial size=2>The order of attempts when multiple</FONT><FONT 
    face=Arial size=2></FONT> <FONT face=Arial size=2>TerminationIDs match is 
    not specified.</FONT><FONT face=Arial size=2> (7.2.1).</FONT> <BR></LI></OL>
  <P><FONT face=Arial size=2>Now, suppose I have a wildcarded command with 
  multiple descriptors.&nbsp; Rules 1 and 3 seem to imply that I must process 
  all descriptors for the first termination before I process any descriptors for 
  the second termination.&nbsp; On the other hand, rules 2 and 4 seem to allow 
  bulk handling of a single descriptor for all terminations simultaneously, 
  before handling the next descriptor in the same bulk fashion.&nbsp; This 
  facilitates efficient storage if, for example, a digit map or requested event 
  is specified for a wildcarded termination.</FONT></P>
  <P><FONT face=Arial size=2>Is either interpretation permitted?&nbsp; The 
  previous discussion in this thread suggests that it is, because if an error 
  occurs, the command should still be completed for each matching termination, 
  and it could be in either case.</FONT></P>
  <P><FONT face=Tahoma size=2>Raphael Tryster</FONT> </P>
  <UL>
    <P><A name=_MailData><FONT face=Arial size=2>-----Original 
    Message-----</FONT></A> <BR><B><FONT face=Arial size=2>From:&nbsp;&nbsp; 
    Terry L Anderson [SMTP:tla@lucent.com]</FONT></B> <BR><B><FONT face=Arial 
    size=2>Sent:&nbsp;&nbsp;</FONT></B> <FONT face=Arial size=2>Thursday, 31 
    January, 2002 4:45 PM</FONT> <BR><B><FONT face=Arial 
    size=2>To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT face=Arial 
    size=2>Christian Groves</FONT> <BR><B><FONT face=Arial 
    size=2>Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT face=Arial size=2>vidya 
    g; megaco@ietf.org</FONT> <BR><B><FONT face=Arial 
    size=2>Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT 
    face=Arial size=2>Re: [Megaco] QRY about the failed command</FONT> </P>
    <P><FONT face="Courier New" size=2>You are right.&nbsp; I (and Vidya G) 
    should have read a little further.&nbsp; I agree, no change is 
    needed.</FONT> </P>
    <P><FONT face="Courier New" size=2>Christian Groves wrote:</FONT> </P>
    <P><FONT face="Courier New" size=2>&gt; G'Day Terry,</FONT> <BR><FONT 
    face="Courier New" size=2>&gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; The behaviour already is mentioned in 8.0 the paragraph after 
    "At the</FONT> <BR><FONT face="Courier New" size=2>&gt; first failing 
    Command...". States: "Commands may be marked as "Optional"</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; which can override this behaviour -&nbsp; if 
    a command marked as Optional</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    results in an error, subsequent commands in the Transaction will be</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; executed.&nbsp; If a command fails, 
    the MG shall as far as possible restore</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; the state that existed prior to the attempted execution of the 
    command</FONT> <BR><FONT face="Courier New" size=2>&gt; before continuing 
    with command processing."</FONT> <BR><FONT face="Courier New" 
    size=2>&gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; Regards, 
    Christian</FONT> <BR><FONT face="Courier New" size=2>&gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; Terry L Anderson wrote:</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; The statement (in 8.0) IS misleading but your understanding 
    is also incorrect.</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; 8.2.2 (including 
    changes from IG 6.36) make it clear that the first non-optional command that 
    fails ends processing of</FONT></P>
    <P><FONT face="Courier New" size=2>&gt; &gt; the entire Transaction (not 
    just the action).</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; Perhaps the 
    exception indicated in 8.2.2 should also be mentioned in 8.0.</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; Do folks think this sentence should be 
    corrected in IG?</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; vidya g wrote:</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; Hi all</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; &gt;&nbsp;&nbsp; In RFC, page number 61 it says that</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;&nbsp; "&nbsp; At the first failing 
    Command in a Transaction, processing of the remaining Commands in that 
    Transaction stops."</FONT></P>
    <P><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;&nbsp;&nbsp; This statement is some 
    what confusing. What I understand is even if a non optional</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; command fails in an action, the 
    action will be cancelled and the next action will be taken</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; for processing and the commands in 
    that action will be processed.. is that right .. ?</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt;</FONT> <BR><FONT face="Courier New" 
    size=2>&gt; &gt; &gt; vdy</FONT> <BR><FONT face="Courier New" size=2>&gt; 
    &gt; &gt;</FONT> <BR><FONT face="Courier New" size=2>&gt; &gt; &gt;</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; 
    _______________________________________________</FONT> <BR><FONT 
    face="Courier New" size=2>&gt; &gt; &gt; Megaco mailing list</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; Megaco@ietf.org</FONT> 
    <BR><FONT face="Courier New" size=2>&gt; &gt; &gt; <A target=_blank 
    href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
    </P>
    <P><FONT face="Courier New" size=2>--</FONT> </P>
    <P><FONT face="Courier New" 
    size=2>------------------------------------------------------------</FONT> 
    <BR><FONT face="Courier New" size=2>Terry L 
    Anderson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    <A href="mailto:tla@lucent.com">mailto:tla@lucent.com</A></FONT> <BR><FONT 
    face="Courier New" size=2>Tel:908.582.7013&nbsp;&nbsp; 
    Fax:908.582.6729</FONT> <BR><FONT face="Courier New" size=2>Lucent 
    Technologies/INS/Voice Over IP Access Networks</FONT> <BR><FONT 
    face="Courier New" size=2>Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 
    07974</FONT> <BR><FONT face="Courier New" size=2><A target=_blank 
    href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</A> (Lucent 
    internal) <A target=_blank 
    href="http://www.gti.net/tla">http://www.gti.net/tla</A></FONT> </P><BR>
    <P><FONT face="Courier New" size=2>*** eSafe scanned this email for 
    malicious content ***</FONT> <BR><FONT face="Courier New" size=2>*** 
    IMPORTANT: Do not open attachments from unrecognized senders&nbsp; *** 
    &lt;&lt; File: Card for Terry L Anderson &gt;&gt; 
</FONT></P></UL></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1AA8D.56F10030--

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



From megaco-admin@ietf.org  Thu Jan 31 14:59:50 2002
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 OAA10293
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:59:46 -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 OAA19292;
	Thu, 31 Jan 2002 14:52:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19169
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:52:08 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10022
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:52:02 -0500 (EST)
Received: through eSafe SMTP Relay 1011795511; Thu Jan 31 22:08:45 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6GDAM>; Thu, 31 Jan 2002 21:42:41 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF018E808B@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Kevin Boyle <kboyle@nortelnetworks.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 21:42:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA8F.70CEC990"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA8F.70CEC990
Content-Type: text/plain;
	charset="iso-8859-1"

Hello Kevin,

Thanks for your quick reply.  What I gathered from the requirement I listed
as 4 is that the ordering of a wildcard is undefined.  Therefore, if an MG
is permitted to process the entire command for termination2 before the
entire command for termination 1, or the reverse, it should be OK to process
the two terminations in parallel, one descriptor at a time.  Thus, using
shorthand C for command and D for descriptor:

C1D1, C1D2, C2D1, C2D2 is OK.  Therefore, C1D1 may come first and C2D2 may
come last.
C2D1, C2D2, C1D1, C1D2 is OK.  Therefore, C2D1 may come before C1D2.

Then it stands to reason that the parallel execution sequence: C1D1, C2D1,
C1D2, C2D2 is also OK, because each bilateral temporal relationship in it
also exists in one of the sequences that we know are permitted.

Can you think of any bad behaviour that would result from following my line
of reasoning?

Raphael Tryster


	-----Original Message-----
	From:	Kevin Boyle [SMTP:kboyle@nortelnetworks.com]
	Sent:	Thursday, 31 January, 2002 9:28 PM
	To:	Raphael Tryster; Terry L Anderson; Christian Groves
	Cc:	vidya g; megaco@ietf.org
	Subject:	RE: [Megaco] QRY about the failed command

	You should process the full command on each termination is turn,
just as if the terminations had been expressed individually in their own
command.  Requirement 4 (by the numbering below) indicates that it is up to
the MG to figure which order the terms go in, if more than one matches the
wildcard.
	 
	Kevin

		-----Original Message-----
		From: Raphael Tryster [mailto:raphael@tdsoft.com]
		Sent: Thursday, January 31, 2002 1:37 PM
		To: Terry L Anderson; Christian Groves
		Cc: vidya g; megaco@ietf.org
		Subject: RE: [Megaco] QRY about the failed command
		
		

		I have a question related to this.  Consider the following
requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 
2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 
3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 
4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1). 


		Now, suppose I have a wildcarded command with multiple
descriptors.  Rules 1 and 3 seem to imply that I must process all
descriptors for the first termination before I process any descriptors for
the second termination.  On the other hand, rules 2 and 4 seem to allow bulk
handling of a single descriptor for all terminations simultaneously, before
handling the next descriptor in the same bulk fashion.  This facilitates
efficient storage if, for example, a digit map or requested event is
specified for a wildcarded termination.

		Is either interpretation permitted?  The previous discussion
in this thread suggests that it is, because if an error occurs, the command
should still be completed for each matching termination, and it could be in
either case.

		Raphael Tryster 

		-----Original Message----- 
		From:   Terry L Anderson [SMTP:tla@lucent.com] 
		Sent:   Thursday, 31 January, 2002 4:45 PM 
		To:     Christian Groves 
		Cc:     vidya g; megaco@ietf.org 
		Subject:        Re: [Megaco] QRY about the failed command 

		You are right.  I (and Vidya G) should have read a little
further.  I agree, no change is needed. 

		Christian Groves wrote: 

		> G'Day Terry, 
		> 
		> The behaviour already is mentioned in 8.0 the paragraph
after "At the 
		> first failing Command...". States: "Commands may be marked
as "Optional" 
		> which can override this behaviour -  if a command marked
as Optional 
		> results in an error, subsequent commands in the
Transaction will be 
		> executed.  If a command fails, the MG shall as far as
possible restore 
		> the state that existed prior to the attempted execution of
the command 
		> before continuing with command processing." 
		> 
		> Regards, Christian 
		> 
		> Terry L Anderson wrote: 
		> > 
		> > The statement (in 8.0) IS misleading but your
understanding is also incorrect. 
		> > 
		> > 8.2.2 (including changes from IG 6.36) make it clear
that the first non-optional command that fails ends processing of

		> > the entire Transaction (not just the action). 
		> > 
		> > Perhaps the exception indicated in 8.2.2 should also be
mentioned in 8.0. 
		> > 
		> > Do folks think this sentence should be corrected in IG? 
		> > 
		> > vidya g wrote: 
		> > 
		> > > Hi all 
		> > > 
		> > >   In RFC, page number 61 it says that 
		> > > 
		> > >  "  At the first failing Command in a Transaction,
processing of the remaining Commands in that Transaction stops."

		> > > 
		> > >   This statement is some what confusing. What I
understand is even if a non optional 
		> > > command fails in an action, the action will be
cancelled and the next action will be taken 
		> > > for processing and the commands in that action will be
processed.. is that right .. ? 
		> > > 
		> > > vdy 
		> > > 
		> > > 
		> > > _______________________________________________ 
		> > > Megaco mailing list 
		> > > Megaco@ietf.org 
		> > > https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  

		-- 

		------------------------------------------------------------

		Terry L Anderson              mailto:tla@lucent.com
<mailto:tla@lucent.com>  
		Tel:908.582.7013   Fax:908.582.6729 
		Lucent Technologies/INS/Voice Over IP Access Networks 
		Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
		http://its.lucent.com/~tla <http://its.lucent.com/~tla>
(Lucent internal) http://www.gti.net/tla <http://www.gti.net/tla>  


		*** eSafe scanned this email for malicious content *** 
		*** IMPORTANT: Do not open attachments from unrecognized
senders  *** << File: Card for Terry L Anderson >> 
	

------_=_NextPart_001_01C1AA8F.70CEC990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello Kevin,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for your quick reply.&nbsp; What =
I gathered from the requirement I listed as 4 is that the ordering of a w=
ildcard is undefined.&nbsp; Therefore, if an MG is permitted to process t=
he entire command for termination2 before the entire command for terminat=
ion 1, or the reverse, it should be OK to process the two terminations in=
 parallel, one descriptor at a time.&nbsp; Thus, using shorthand C for co=
mmand and D for descriptor:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">C1D1, C1D2, C2D1, C2D2 is OK.&nbsp; Ther=
efore, C1D1 may come first and C2D2 may come last.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">C2D1, C2D2, C1D1, C1D2 is OK.&nbsp; The=
refore, C2D1 may come before C1D2.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Then it stands to reason that the parall=
el execution sequence: C1D1, C2D1, C1D2, C2D2 is also OK, because each bi=
lateral temporal relationship in it also exists in one of the sequences t=
hat we know are permitted.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Can you think of any bad behaviour that =
would result from following my line of reasoning?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Kevin Boyle [SMTP:=
kboyle@nortelnetworks.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 9:28 PM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Raphael Tryster; Terry L Anderson; Chris=
tian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">RE: [Megaco] QRY =
about the failed command</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You should process the=
 full command on each termination is turn, just as if the terminations ha=
d been expressed individually in their own command.=A0 Requirement 4 (by =
the numbering below) indicates that it is up to the MG to figure which or=
der the terms go in, if more than one matches the wildcard.</FONT></P>

<P><FONT FACE=3D"Arial">=A0</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Kevin</FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">-----Original Message-----<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Raphael Tryster [<A HREF=3D"mailto:raphael@tdsoft.=
com">mailto:raphael@tdsoft.com</A>]<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Thursday, January 31, 2002 1:37 PM<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> Terry L Anderson; Christian Groves<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> vidya g; megaco@ietf.org<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: [Megaco] QRY about the failed command<BR>
<BR>
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question related to this.=A0 Co=
nsider the following requirements:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">Commands</FONT><FONT FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">within a Transaction are ex=
ecuted sequentially. (8).</FONT><FONT FACE=3D"Arial"> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The descriptors SHALL be processed in t=
he order in which they appear (7.2).=A0 Exception (7.1.14.1):</FONT><FONT=
 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">It is</FONT><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">permissible for a dig=
it map completion event within an Events</FONT><FONT FACE=3D"Arial"></FON=
T> <FONT SIZE=3D2 FACE=3D"Arial">Descriptor to refer by name to a DigitMa=
p which is defined by a</FONT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2=
 FACE=3D"Arial">DigitMap Descriptor within the same command, regardless o=
f the</FONT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">tr=
ansmitted order of the respective descriptors.</FONT><FONT FACE=3D"Arial"=
> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When the TerminationId of a</FONT><FONT=
 FACE=3D"Arial">=A0</FONT><FONT SIZE=3D2 FACE=3D"Arial"> command is wildc=
arded, the effect shall be as if the command was</FONT><FONT FACE=3D"Aria=
l"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">repeated with each of the Termin=
ationIds matched. (7.1.1).</FONT><FONT FACE=3D"Arial"> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The order of attempts when multiple</FO=
NT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Termination=
IDs match is not specified. (7.2.1).</FONT><FONT FACE=3D"Arial"><BR>
</FONT></LI>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Now, suppose I have a wildcarded command=
 with multiple descriptors.=A0 Rules 1 and 3 seem to imply that I must pr=
ocess all descriptors for the first termination before I process any desc=
riptors for the second termination.=A0 On the other hand, rules 2 and 4 s=
eem to allow bulk handling of a single descriptor for all terminations si=
multaneously, before handling the next descriptor in the same bulk fashio=
n.=A0 This facilitates efficient storage if, for example, a digit map or =
requested event is specified for a wildcarded termination.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is either interpretation permitted?=A0 T=
he previous discussion in this thread suggests that it is, because if an =
error occurs, the command should still be completed for each matching ter=
mination, and it could be in either case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT><FONT FACE=3D"Ari=
al"> </FONT>
</P>

<P><A NAME=3D"BM__MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original M=
essage-----</FONT></A><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">From:=A0=A0 Terry L Anderson [SMT=
P:tla@lucent.com]</FONT></B><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:=A0=A0</FONT></B><FONT FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 =
4:45 PM</FONT><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">To:=A0=A0=A0=A0</FONT></B><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FON=
T><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:=A0=A0=A0=A0</FONT></B><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.=
org</FONT><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:=A0=A0=A0=A0=A0=A0=A0</FO=
NT></B><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Me=
gaco] QRY about the failed command</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">You are right.=A0 I (and Vidya G) =
should have read a little further.=A0 I agree, no change is needed.</FONT=
><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves wrote:</FONT><FON=
T FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; G'Day Terry,</FONT><FONT FACE=
=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The behaviour already is =
mentioned in 8.0 the paragraph after &quot;At the</FONT><FONT FACE=3D"Ari=
al"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; first failing Command...&=
quot;. States: &quot;Commands may be marked as &quot;Optional&quot;</FONT=
><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; which can override this b=
ehaviour -=A0 if a command marked as Optional</FONT><FONT FACE=3D"Arial">=
<BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; results in an error, subs=
equent commands in the Transaction will be</FONT><FONT FACE=3D"Arial"><BR=
>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; executed.=A0 If a command=
 fails, the MG shall as far as possible restore</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; the state that existed pr=
ior to the attempted execution of the command</FONT><FONT FACE=3D"Arial">=
<BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; before continuing with co=
mmand processing.&quot;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards, Christian</FONT>=
<FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Terry L Anderson wrote:</=
FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; The statement (in 8.=
0) IS misleading but your understanding is also incorrect.</FONT><FONT FA=
CE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; 8.2.2 (including cha=
nges from IG 6.36) make it clear that the first non-optional command that=
 fails ends processing of</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; the entire Transaction (=
not just the action).</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Perhaps the exceptio=
n indicated in 8.2.2 should also be mentioned in 8.0.</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Do folks think this =
sentence should be corrected in IG?</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; vidya g wrote:</FONT=
><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Hi all</FONT><F=
ONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0=A0 In RFC, p=
age number 61 it says that</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0 &quot;=A0 At=
 the first failing Command in a Transaction, processing of the remaining =
Commands in that Transaction stops.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0=A0 This stat=
ement is some what confusing. What I understand is even if a non optional=
</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; command fails i=
n an action, the action will be cancelled and the next action will be tak=
en</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; for processing =
and the commands in that action will be processed.. is that right .. ?</F=
ONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; vdy</FONT><FONT=
 FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; _______________=
________________________________</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco mailing =
list</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco@ietf.org=
</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT> <A HREF=3D=
"https://www1.ietf.org/mailman/listinfo/megaco"><U><FONT COLOR=3D"#0000FF=
" SIZE=3D2 FACE=3D"Courier New">https://www1.ietf.org/mailman/listinfo/me=
gaco</FONT></U></A><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--</FONT><FONT FACE=3D"Arial"> </F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">----------------------------------=
--------------------------</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Terry L Anderson=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0</FONT> <A HREF=3D"mailto:tla@lucent.com"><U><FON=
T COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">mailto:tla@lucent.com</=
FONT></U></A><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Tel:908.582.7013=A0=A0 Fax:908=

</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Lucent Technologies/INS/Voice =
Over IP Access Networks</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Rm 2B-121, 600 Mountain Av, Mu=
rray Hill, NJ 07974</FONT><FONT FACE=3D"Arial"><BR>
</FONT><A HREF=3D"http://its.lucent.com/~tla"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">http://its.lucent.com/~tla</FONT></U></A><F=
ONT SIZE=3D2 FACE=3D"Courier New"> (Lucent internal)</FONT> <A HREF=3D"ht=
tp://www.gti.net/tla"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier=
 New">http://www.gti.net/tla</FONT></U></A><FONT FACE=3D"Arial"> </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">*** eSafe scanned this email for m=
alicious content ***</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">*** IMPORTANT: Do not open att=
achments from unrecognized senders=A0 *** &lt;&lt; File: Card for Terry L=
 Anderson &gt;&gt;</FONT>=20
</UL>
<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1AA8F.70CEC990--

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


From daemon@ns.ietf.org  Thu Jan 31 14:59:55 2002
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 OAA10311
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 14:59:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19845
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 14:59:55 -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 OAA19292;
	Thu, 31 Jan 2002 14:52:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19169
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 14:52:08 -0500 (EST)
Received: from exchange.td-soft.co.il (mail.tdsoft.com [212.143.64.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10022
	for <megaco@ietf.org>; Thu, 31 Jan 2002 14:52:02 -0500 (EST)
Received: through eSafe SMTP Relay 1011795511; Thu Jan 31 22:08:45 2002
Received: by Exchange with Internet Mail Service (5.5.2653.19)
	id <CNR6GDAM>; Thu, 31 Jan 2002 21:42:41 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF018E808B@Exchange>
From: Raphael Tryster <raphael@tdsoft.com>
To: Kevin Boyle <kboyle@nortelnetworks.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 21:42:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AA8F.70CEC990"
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AA8F.70CEC990
Content-Type: text/plain;
	charset="iso-8859-1"

Hello Kevin,

Thanks for your quick reply.  What I gathered from the requirement I listed
as 4 is that the ordering of a wildcard is undefined.  Therefore, if an MG
is permitted to process the entire command for termination2 before the
entire command for termination 1, or the reverse, it should be OK to process
the two terminations in parallel, one descriptor at a time.  Thus, using
shorthand C for command and D for descriptor:

C1D1, C1D2, C2D1, C2D2 is OK.  Therefore, C1D1 may come first and C2D2 may
come last.
C2D1, C2D2, C1D1, C1D2 is OK.  Therefore, C2D1 may come before C1D2.

Then it stands to reason that the parallel execution sequence: C1D1, C2D1,
C1D2, C2D2 is also OK, because each bilateral temporal relationship in it
also exists in one of the sequences that we know are permitted.

Can you think of any bad behaviour that would result from following my line
of reasoning?

Raphael Tryster


	-----Original Message-----
	From:	Kevin Boyle [SMTP:kboyle@nortelnetworks.com]
	Sent:	Thursday, 31 January, 2002 9:28 PM
	To:	Raphael Tryster; Terry L Anderson; Christian Groves
	Cc:	vidya g; megaco@ietf.org
	Subject:	RE: [Megaco] QRY about the failed command

	You should process the full command on each termination is turn,
just as if the terminations had been expressed individually in their own
command.  Requirement 4 (by the numbering below) indicates that it is up to
the MG to figure which order the terms go in, if more than one matches the
wildcard.
	 
	Kevin

		-----Original Message-----
		From: Raphael Tryster [mailto:raphael@tdsoft.com]
		Sent: Thursday, January 31, 2002 1:37 PM
		To: Terry L Anderson; Christian Groves
		Cc: vidya g; megaco@ietf.org
		Subject: RE: [Megaco] QRY about the failed command
		
		

		I have a question related to this.  Consider the following
requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 
2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 
3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 
4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1). 


		Now, suppose I have a wildcarded command with multiple
descriptors.  Rules 1 and 3 seem to imply that I must process all
descriptors for the first termination before I process any descriptors for
the second termination.  On the other hand, rules 2 and 4 seem to allow bulk
handling of a single descriptor for all terminations simultaneously, before
handling the next descriptor in the same bulk fashion.  This facilitates
efficient storage if, for example, a digit map or requested event is
specified for a wildcarded termination.

		Is either interpretation permitted?  The previous discussion
in this thread suggests that it is, because if an error occurs, the command
should still be completed for each matching termination, and it could be in
either case.

		Raphael Tryster 

		-----Original Message----- 
		From:   Terry L Anderson [SMTP:tla@lucent.com] 
		Sent:   Thursday, 31 January, 2002 4:45 PM 
		To:     Christian Groves 
		Cc:     vidya g; megaco@ietf.org 
		Subject:        Re: [Megaco] QRY about the failed command 

		You are right.  I (and Vidya G) should have read a little
further.  I agree, no change is needed. 

		Christian Groves wrote: 

		> G'Day Terry, 
		> 
		> The behaviour already is mentioned in 8.0 the paragraph
after "At the 
		> first failing Command...". States: "Commands may be marked
as "Optional" 
		> which can override this behaviour -  if a command marked
as Optional 
		> results in an error, subsequent commands in the
Transaction will be 
		> executed.  If a command fails, the MG shall as far as
possible restore 
		> the state that existed prior to the attempted execution of
the command 
		> before continuing with command processing." 
		> 
		> Regards, Christian 
		> 
		> Terry L Anderson wrote: 
		> > 
		> > The statement (in 8.0) IS misleading but your
understanding is also incorrect. 
		> > 
		> > 8.2.2 (including changes from IG 6.36) make it clear
that the first non-optional command that fails ends processing of

		> > the entire Transaction (not just the action). 
		> > 
		> > Perhaps the exception indicated in 8.2.2 should also be
mentioned in 8.0. 
		> > 
		> > Do folks think this sentence should be corrected in IG? 
		> > 
		> > vidya g wrote: 
		> > 
		> > > Hi all 
		> > > 
		> > >   In RFC, page number 61 it says that 
		> > > 
		> > >  "  At the first failing Command in a Transaction,
processing of the remaining Commands in that Transaction stops."

		> > > 
		> > >   This statement is some what confusing. What I
understand is even if a non optional 
		> > > command fails in an action, the action will be
cancelled and the next action will be taken 
		> > > for processing and the commands in that action will be
processed.. is that right .. ? 
		> > > 
		> > > vdy 
		> > > 
		> > > 
		> > > _______________________________________________ 
		> > > Megaco mailing list 
		> > > Megaco@ietf.org 
		> > > https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  

		-- 

		------------------------------------------------------------

		Terry L Anderson              mailto:tla@lucent.com
<mailto:tla@lucent.com>  
		Tel:908.582.7013   Fax:908.582.6729 
		Lucent Technologies/INS/Voice Over IP Access Networks 
		Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 
		http://its.lucent.com/~tla <http://its.lucent.com/~tla>
(Lucent internal) http://www.gti.net/tla <http://www.gti.net/tla>  


		*** eSafe scanned this email for malicious content *** 
		*** IMPORTANT: Do not open attachments from unrecognized
senders  *** << File: Card for Terry L Anderson >> 
	

------_=_NextPart_001_01C1AA8F.70CEC990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.1=
2">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello Kevin,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for your quick reply.&nbsp; What =
I gathered from the requirement I listed as 4 is that the ordering of a w=
ildcard is undefined.&nbsp; Therefore, if an MG is permitted to process t=
he entire command for termination2 before the entire command for terminat=
ion 1, or the reverse, it should be OK to process the two terminations in=
 parallel, one descriptor at a time.&nbsp; Thus, using shorthand C for co=
mmand and D for descriptor:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">C1D1, C1D2, C2D1, C2D2 is OK.&nbsp; Ther=
efore, C1D1 may come first and C2D2 may come last.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">C2D1, C2D2, C1D1, C1D2 is OK.&nbsp; The=
refore, C2D1 may come before C1D2.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Then it stands to reason that the parall=
el execution sequence: C1D1, C2D1, C1D2, C2D2 is also OK, because each bi=
lateral temporal relationship in it also exists in one of the sequences t=
hat we know are permitted.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Can you think of any bad behaviour that =
would result from following my line of reasoning?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Kevin Boyle [SMTP:=
kboyle@nortelnetworks.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 9:28 PM</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">Raphael Tryster; Terry L Anderson; Chris=
tian Groves</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">RE: [Megaco] QRY =
about the failed command</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">You should process the=
 full command on each termination is turn, just as if the terminations ha=
d been expressed individually in their own command.=A0 Requirement 4 (by =
the numbering below) indicates that it is up to the MG to figure which or=
der the terms go in, if more than one matches the wildcard.</FONT></P>

<P><FONT FACE=3D"Arial">=A0</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Kevin</FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">-----Original Message-----<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Raphael Tryster [<A HREF=3D"mailto:raphael@tdsoft.=
com">mailto:raphael@tdsoft.com</A>]<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Thursday, January 31, 2002 1:37 PM<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> Terry L Anderson; Christian Groves<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> vidya g; megaco@ietf.org<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: [Megaco] QRY about the failed command<BR>
<BR>
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a question related to this.=A0 Co=
nsider the following requirements:</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">Commands</FONT><FONT FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">within a Transaction are ex=
ecuted sequentially. (8).</FONT><FONT FACE=3D"Arial"> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The descriptors SHALL be processed in t=
he order in which they appear (7.2).=A0 Exception (7.1.14.1):</FONT><FONT=
 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">It is</FONT><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">permissible for a dig=
it map completion event within an Events</FONT><FONT FACE=3D"Arial"></FON=
T> <FONT SIZE=3D2 FACE=3D"Arial">Descriptor to refer by name to a DigitMa=
p which is defined by a</FONT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2=
 FACE=3D"Arial">DigitMap Descriptor within the same command, regardless o=
f the</FONT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">tr=
ansmitted order of the respective descriptors.</FONT><FONT FACE=3D"Arial"=
> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">When the TerminationId of a</FONT><FONT=
 FACE=3D"Arial">=A0</FONT><FONT SIZE=3D2 FACE=3D"Arial"> command is wildc=
arded, the effect shall be as if the command was</FONT><FONT FACE=3D"Aria=
l"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">repeated with each of the Termin=
ationIds matched. (7.1.1).</FONT><FONT FACE=3D"Arial"> </FONT></LI>
<LI><FONT SIZE=3D2 FACE=3D"Arial">The order of attempts when multiple</FO=
NT><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Termination=
IDs match is not specified. (7.2.1).</FONT><FONT FACE=3D"Arial"><BR>
</FONT></LI>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Now, suppose I have a wildcarded command=
 with multiple descriptors.=A0 Rules 1 and 3 seem to imply that I must pr=
ocess all descriptors for the first termination before I process any desc=
riptors for the second termination.=A0 On the other hand, rules 2 and 4 s=
eem to allow bulk handling of a single descriptor for all terminations si=
multaneously, before handling the next descriptor in the same bulk fashio=
n.=A0 This facilitates efficient storage if, for example, a digit map or =
requested event is specified for a wildcarded termination.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is either interpretation permitted?=A0 T=
he previous discussion in this thread suggests that it is, because if an =
error occurs, the command should still be completed for each matching ter=
mination, and it could be in either case.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT><FONT FACE=3D"Ari=
al"> </FONT>
</P>

<P><A NAME=3D"BM__MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original M=
essage-----</FONT></A><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">From:=A0=A0 Terry L Anderson [SMT=
P:tla@lucent.com]</FONT></B><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:=A0=A0</FONT></B><FONT FACE=3D=
"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Thursday, 31 January, 2002 =
4:45 PM</FONT><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">To:=A0=A0=A0=A0</FONT></B><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Christian Groves</FON=
T><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Cc:=A0=A0=A0=A0</FONT></B><FONT F=
ACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">vidya g; megaco@ietf.=
org</FONT><FONT FACE=3D"Arial"><BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:=A0=A0=A0=A0=A0=A0=A0</FO=
NT></B><FONT FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Re: [Me=
gaco] QRY about the failed command</FONT><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">You are right.=A0 I (and Vidya G) =
should have read a little further.=A0 I agree, no change is needed.</FONT=
><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Christian Groves wrote:</FONT><FON=
T FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; G'Day Terry,</FONT><FONT FACE=
=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; The behaviour already is =
mentioned in 8.0 the paragraph after &quot;At the</FONT><FONT FACE=3D"Ari=
al"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; first failing Command...&=
quot;. States: &quot;Commands may be marked as &quot;Optional&quot;</FONT=
><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; which can override this b=
ehaviour -=A0 if a command marked as Optional</FONT><FONT FACE=3D"Arial">=
<BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; results in an error, subs=
equent commands in the Transaction will be</FONT><FONT FACE=3D"Arial"><BR=
>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; executed.=A0 If a command=
 fails, the MG shall as far as possible restore</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; the state that existed pr=
ior to the attempted execution of the command</FONT><FONT FACE=3D"Arial">=
<BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; before continuing with co=
mmand processing.&quot;</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Regards, Christian</FONT>=
<FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt;</FONT><FONT FACE=3D"Arial=
"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; Terry L Anderson wrote:</=
FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; The statement (in 8.=
0) IS misleading but your understanding is also incorrect.</FONT><FONT FA=
CE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; 8.2.2 (including cha=
nges from IG 6.36) make it clear that the first non-optional command that=
 fails ends processing of</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; the entire Transaction (=
not just the action).</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Perhaps the exceptio=
n indicated in 8.2.2 should also be mentioned in 8.0.</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; Do folks think this =
sentence should be corrected in IG?</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; vidya g wrote:</FONT=
><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt;</FONT><FONT FACE=3D"=
Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Hi all</FONT><F=
ONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0=A0 In RFC, p=
age number 61 it says that</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0 &quot;=A0 At=
 the first failing Command in a Transaction, processing of the remaining =
Commands in that Transaction stops.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FACE=3D=
"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;=A0=A0 This stat=
ement is some what confusing. What I understand is even if a non optional=
</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; command fails i=
n an action, the action will be cancelled and the next action will be tak=
en</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; for processing =
and the commands in that action will be processed.. is that right .. ?</F=
ONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; vdy</FONT><FONT=
 FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT><FONT FAC=
E=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; _______________=
________________________________</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco mailing =
list</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt; Megaco@ietf.org=
</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">&gt; &gt; &gt;</FONT> <A HREF=3D=
"https://www1.ietf.org/mailman/listinfo/megaco"><U><FONT COLOR=3D"#0000FF=
" SIZE=3D2 FACE=3D"Courier New">https://www1.ietf.org/mailman/listinfo/me=
gaco</FONT></U></A><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--</FONT><FONT FACE=3D"Arial"> </F=
ONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">----------------------------------=
--------------------------</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Terry L Anderson=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0</FONT> <A HREF=3D"mailto:tla@lucent.com"><U><FON=
T COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier New">mailto:tla@lucent.com</=
FONT></U></A><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Tel:908.582.7013=A0=A0 Fax:908=

</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Lucent Technologies/INS/Voice =
Over IP Access Networks</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">Rm 2B-121, 600 Mountain Av, Mu=
rray Hill, NJ 07974</FONT><FONT FACE=3D"Arial"><BR>
</FONT><A HREF=3D"http://its.lucent.com/~tla"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier New">http://its.lucent.com/~tla</FONT></U></A><F=
ONT SIZE=3D2 FACE=3D"Courier New"> (Lucent internal)</FONT> <A HREF=3D"ht=
tp://www.gti.net/tla"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier=
 New">http://www.gti.net/tla</FONT></U></A><FONT FACE=3D"Arial"> </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">*** eSafe scanned this email for m=
alicious content ***</FONT><FONT FACE=3D"Arial"><BR>
</FONT><FONT SIZE=3D2 FACE=3D"Courier New">*** IMPORTANT: Do not open att=
achments from unrecognized senders=A0 *** &lt;&lt; File: Card for Terry L=
 Anderson &gt;&gt;</FONT>=20
</UL>
<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C1AA8F.70CEC990--

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



From megaco-admin@ietf.org  Thu Jan 31 15:37:13 2002
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 PAA11508
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 15:37:13 -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 PAA21257;
	Thu, 31 Jan 2002 15:22:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21226
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 15:22:21 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11072
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:22:16 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VKLm523104
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:21:48 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VKLk503865
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:21:46 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAV703>; Thu, 31 Jan 2002 15:21:46 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF63@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>,
        "Kevin Boyle"<kboyle@nortelnetworks.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 15:21:46 -0500
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

I see some implementation trade-offs here, but no real protocol issues.

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Thursday, January 31, 2002 2:43 PM
To: Boyle, Kevin [NCRTP:3Z30:EXCH]
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



Hello Kevin, 

Thanks for your quick reply.  What I gathered from the requirement I listed
as 4 is that the ordering of a wildcard is undefined.  Therefore, if an MG
is permitted to process the entire command for termination2 before the
entire command for termination 1, or the reverse, it should be OK to process
the two terminations in parallel, one descriptor at a time.  Thus, using
shorthand C for command and D for descriptor:

C1D1, C1D2, C2D1, C2D2 is OK.  Therefore, C1D1 may come first and C2D2 may
come last. 
C2D1, C2D2, C1D1, C1D2 is OK.  Therefore, C2D1 may come before C1D2. 

Then it stands to reason that the parallel execution sequence: C1D1, C2D1,
C1D2, C2D2 is also OK, because each bilateral temporal relationship in it
also exists in one of the sequences that we know are permitted.

Can you think of any bad behaviour that would result from following my line
of reasoning? 

Raphael Tryster 


	BM__MailData-----Original Message----- 
From:   Kevin Boyle [SMTP:kboyle@nortelnetworks.com] 
Sent:   Thursday, 31 January, 2002 9:28 PM 
To:     Raphael Tryster; Terry L Anderson; Christian Groves 
Cc:     vidya g; megaco@ietf.org 
Subject:        RE: [Megaco] QRY about the failed command 

	You should process the full command on each termination is turn,
just as if the terminations had been expressed individually in their own
command.  Requirement 4 (by the numbering below) indicates that it is up to
the MG to figure which order the terms go in, if more than one matches the
wildcard.

	  
Kevin 

	-----Original Message-----
From: Raphael Tryster [ mailto:raphael@tdsoft.com
<mailto:raphael@tdsoft.com> ]
Sent: Thursday, January 31, 2002 1:37 PM
To: Terry L Anderson; Christian Groves
Cc: vidya g; megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



	I have a question related to this.  Consider the following
requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 

2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 

3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 

4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1).



	Now, suppose I have a wildcarded command with multiple descriptors.
Rules 1 and 3 seem to imply that I must process all descriptors for the
first termination before I process any descriptors for the second
termination.  On the other hand, rules 2 and 4 seem to allow bulk handling
of a single descriptor for all terminations simultaneously, before handling
the next descriptor in the same bulk fashion.  This facilitates efficient
storage if, for example, a digit map or requested event is specified for a
wildcarded termination.

	Is either interpretation permitted?  The previous discussion in this
thread suggests that it is, because if an error occurs, the command should
still be completed for each matching termination, and it could be in either
case.

	Raphael Tryster 

	BM__MailData-----Original Message-----
From:   Terry L Anderson [SMTP:tla@lucent.com]
Sent:   Thursday, 31 January, 2002 4:45 PM
To:     Christian Groves
Cc:     vidya g; megaco@ietf.org
Subject:        Re: [Megaco] QRY about the failed command 

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed. 

	Christian Groves wrote: 

	> G'Day Terry,
>
> The behaviour already is mentioned in 8.0 the paragraph after "At the
> first failing Command...". States: "Commands may be marked as "Optional"
> which can override this behaviour -  if a command marked as Optional
> results in an error, subsequent commands in the Transaction will be
> executed.  If a command fails, the MG shall as far as possible restore
> the state that existed prior to the attempted execution of the command
> before continuing with command processing."
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > The statement (in 8.0) IS misleading but your understanding is also
incorrect.
> >
> > 8.2.2 (including changes from IG 6.36) make it clear that the first
non-optional command that fails ends processing of

	> > the entire Transaction (not just the action).
> >
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in
8.0.
> >
> > Do folks think this sentence should be corrected in IG?
> >
> > vidya g wrote:
> >
> > > Hi all
> > >
> > >   In RFC, page number 61 it says that
> > >
> > >  "  At the first failing Command in a Transaction, processing of the
remaining Commands in that Transaction stops."

	> > >
> > >   This statement is some what confusing. What I understand is even if
a non optional
> > > command fails in an action, the action will be cancelled and the next
action will be taken
> > > for processing and the commands in that action will be processed.. is
that right .. ?
> > >
> > > vdy
> > >
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > >  <https://www1.ietf.org/mailman/listinfo/megaco>
https://www1.ietf.org/mailman/listinfo/megaco 

	-- 

	------------------------------------------------------------
Terry L Anderson               <mailto:tla@lucent.com> mailto:tla@lucent.com
Tel:908.582.7013   Fax:908 Lucent Technologies/INS/Voice Over IP Access
Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
 <http://its.lucent.com/~tla> http://its.lucent.com/~tla (Lucent internal)
<http://www.gti.net/tla> http://www.gti.net/tla 


	*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders  *** <<
File: Card for Terry L Anderson >> 

	


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


From daemon@ns.ietf.org  Thu Jan 31 15:37:18 2002
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 PAA11518
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 15:37:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA22101
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 15:37: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 PAA21257;
	Thu, 31 Jan 2002 15:22:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21226
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 15:22:21 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11072
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:22:16 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VKLm523104
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:21:48 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0VKLk503865
	for <megaco@ietf.org>; Thu, 31 Jan 2002 15:21:46 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAV703>; Thu, 31 Jan 2002 15:21:46 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF63@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>,
        "Kevin Boyle"<kboyle@nortelnetworks.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command
Date: Thu, 31 Jan 2002 15:21:46 -0500
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

I see some implementation trade-offs here, but no real protocol issues.

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Thursday, January 31, 2002 2:43 PM
To: Boyle, Kevin [NCRTP:3Z30:EXCH]
Cc: megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



Hello Kevin, 

Thanks for your quick reply.  What I gathered from the requirement I listed
as 4 is that the ordering of a wildcard is undefined.  Therefore, if an MG
is permitted to process the entire command for termination2 before the
entire command for termination 1, or the reverse, it should be OK to process
the two terminations in parallel, one descriptor at a time.  Thus, using
shorthand C for command and D for descriptor:

C1D1, C1D2, C2D1, C2D2 is OK.  Therefore, C1D1 may come first and C2D2 may
come last. 
C2D1, C2D2, C1D1, C1D2 is OK.  Therefore, C2D1 may come before C1D2. 

Then it stands to reason that the parallel execution sequence: C1D1, C2D1,
C1D2, C2D2 is also OK, because each bilateral temporal relationship in it
also exists in one of the sequences that we know are permitted.

Can you think of any bad behaviour that would result from following my line
of reasoning? 

Raphael Tryster 


	BM__MailData-----Original Message----- 
From:   Kevin Boyle [SMTP:kboyle@nortelnetworks.com] 
Sent:   Thursday, 31 January, 2002 9:28 PM 
To:     Raphael Tryster; Terry L Anderson; Christian Groves 
Cc:     vidya g; megaco@ietf.org 
Subject:        RE: [Megaco] QRY about the failed command 

	You should process the full command on each termination is turn,
just as if the terminations had been expressed individually in their own
command.  Requirement 4 (by the numbering below) indicates that it is up to
the MG to figure which order the terms go in, if more than one matches the
wildcard.

	  
Kevin 

	-----Original Message-----
From: Raphael Tryster [ mailto:raphael@tdsoft.com
<mailto:raphael@tdsoft.com> ]
Sent: Thursday, January 31, 2002 1:37 PM
To: Terry L Anderson; Christian Groves
Cc: vidya g; megaco@ietf.org
Subject: RE: [Megaco] QRY about the failed command



	I have a question related to this.  Consider the following
requirements: 

1.	Commands within a Transaction are executed sequentially. (8). 

2.	The descriptors SHALL be processed in the order in which they appear
(7.2).  Exception (7.1.14.1): It is permissible for a digit map completion
event within an Events Descriptor to refer by name to a DigitMap which is
defined by a DigitMap Descriptor within the same command, regardless of the
transmitted order of the respective descriptors. 

3.	When the TerminationId of a  command is wildcarded, the effect shall
be as if the command was repeated with each of the TerminationIds matched.
(7.1.1). 

4.	The order of attempts when multiple TerminationIDs match is not
specified. (7.2.1).



	Now, suppose I have a wildcarded command with multiple descriptors.
Rules 1 and 3 seem to imply that I must process all descriptors for the
first termination before I process any descriptors for the second
termination.  On the other hand, rules 2 and 4 seem to allow bulk handling
of a single descriptor for all terminations simultaneously, before handling
the next descriptor in the same bulk fashion.  This facilitates efficient
storage if, for example, a digit map or requested event is specified for a
wildcarded termination.

	Is either interpretation permitted?  The previous discussion in this
thread suggests that it is, because if an error occurs, the command should
still be completed for each matching termination, and it could be in either
case.

	Raphael Tryster 

	BM__MailData-----Original Message-----
From:   Terry L Anderson [SMTP:tla@lucent.com]
Sent:   Thursday, 31 January, 2002 4:45 PM
To:     Christian Groves
Cc:     vidya g; megaco@ietf.org
Subject:        Re: [Megaco] QRY about the failed command 

	You are right.  I (and Vidya G) should have read a little further.
I agree, no change is needed. 

	Christian Groves wrote: 

	> G'Day Terry,
>
> The behaviour already is mentioned in 8.0 the paragraph after "At the
> first failing Command...". States: "Commands may be marked as "Optional"
> which can override this behaviour -  if a command marked as Optional
> results in an error, subsequent commands in the Transaction will be
> executed.  If a command fails, the MG shall as far as possible restore
> the state that existed prior to the attempted execution of the command
> before continuing with command processing."
>
> Regards, Christian
>
> Terry L Anderson wrote:
> >
> > The statement (in 8.0) IS misleading but your understanding is also
incorrect.
> >
> > 8.2.2 (including changes from IG 6.36) make it clear that the first
non-optional command that fails ends processing of

	> > the entire Transaction (not just the action).
> >
> > Perhaps the exception indicated in 8.2.2 should also be mentioned in
8.0.
> >
> > Do folks think this sentence should be corrected in IG?
> >
> > vidya g wrote:
> >
> > > Hi all
> > >
> > >   In RFC, page number 61 it says that
> > >
> > >  "  At the first failing Command in a Transaction, processing of the
remaining Commands in that Transaction stops."

	> > >
> > >   This statement is some what confusing. What I understand is even if
a non optional
> > > command fails in an action, the action will be cancelled and the next
action will be taken
> > > for processing and the commands in that action will be processed.. is
that right .. ?
> > >
> > > vdy
> > >
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > >  <https://www1.ietf.org/mailman/listinfo/megaco>
https://www1.ietf.org/mailman/listinfo/megaco 

	-- 

	------------------------------------------------------------
Terry L Anderson               <mailto:tla@lucent.com> mailto:tla@lucent.com
Tel:908.582.7013   Fax:908 Lucent Technologies/INS/Voice Over IP Access
Networks
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
 <http://its.lucent.com/~tla> http://its.lucent.com/~tla (Lucent internal)
<http://www.gti.net/tla> http://www.gti.net/tla 


	*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders  *** <<
File: Card for Terry L Anderson >> 

	


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



From megaco-admin@ietf.org  Thu Jan 31 17:57:39 2002
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 RAA14971
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 17:57:33 -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 RAA29336;
	Thu, 31 Jan 2002 17:48:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29309
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 17:48:03 -0500 (EST)
Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14790
	for <megaco@ietf.org>; Thu, 31 Jan 2002 17:47:56 -0500 (EST)
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.29 2002/01/25 02:32:19 root Exp $) with ESMTP id g0VMlMh12691
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:47:22 GMT
Received: from fmsmsxvs040.fm.intel.com (fmsmsxv040-1.fm.intel.com [132.233.48.108])
	by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.11 2001/11/09 23:28:01 root Exp $) with SMTP id g0VMlRN00748
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:47:27 GMT
Received: from FMSMSX016.fm.intel.com ([132.233.42.195])
 by fmsmsxvs040.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002013114472824265
 ; Thu, 31 Jan 2002 14:47:28 -0800
Received: by fmsmsx016.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <DWCL6X1V>; Thu, 31 Jan 2002 14:47:57 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500DDF6584@FMSMSX37>
From: "Zhang, Yuyong" <yuyong@trillium.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
Cc: megaco@ietf.org
Date: Thu, 31 Jan 2002 14:47:54 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AAA9.51E98D20"
Subject: [Megaco] How the ServiceState of TermStateDescriptor in MediaDescriptor is
 used?
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AAA9.51E98D20
Content-Type: text/plain;
	charset="ISO-8859-1"

G'day, Tom, All
 
I am not very clear how the ServiceState in TermStateDescriptor is used.
 
If a MGC sends this ServiceState to MG, what the "Test", "Out of Service",
or "In Service" state means to a MG, what is the MG's behavior in receiving
such state? I just don't know in what situation, a MGC will sends this
ServiceState to MG.
 
If a MG wants to send termination state to the MGC, then the ServiceChange
with ServiceChangeDescriptor will do.
 
The only way I see the ServiceState to be used is when MG replys an AUDIT on
MediaDescriptor, MG sends the termination state on this.
 
Any thoughts on this?
 
Regards,
 
Yuyong

------_=_NextPart_001_01C1AAA9.51E98D20
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>G'day, 
Tom, All</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>I am 
not very clear how the ServiceState in TermStateDescriptor is 
used.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>If a 
MGC sends this ServiceState to MG, what the "Test", "Out of Service", or "In 
Service" state means to a MG, what is the MG's behavior in receiving such state? 
I just don't know in what situation, a MGC will sends this ServiceState to 
MG.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>If a 
MG wants to send termination state to the MGC, then the ServiceChange with 
ServiceChangeDescriptor will do.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>The 
only way I see the ServiceState to be used is when MG replys an AUDIT on 
MediaDescriptor, MG sends the termination state on this.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>Any 
thoughts on this?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002>Regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002>Yuyong</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C1AAA9.51E98D20--

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


From daemon@ns.ietf.org  Thu Jan 31 17:57:40 2002
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 RAA14981
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 17:57:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA29720
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 17:57:43 -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 RAA29336;
	Thu, 31 Jan 2002 17:48:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA29309
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 17:48:03 -0500 (EST)
Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14790
	for <megaco@ietf.org>; Thu, 31 Jan 2002 17:47:56 -0500 (EST)
Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.29 2002/01/25 02:32:19 root Exp $) with ESMTP id g0VMlMh12691
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:47:22 GMT
Received: from fmsmsxvs040.fm.intel.com (fmsmsxv040-1.fm.intel.com [132.233.48.108])
	by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.11 2001/11/09 23:28:01 root Exp $) with SMTP id g0VMlRN00748
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:47:27 GMT
Received: from FMSMSX016.fm.intel.com ([132.233.42.195])
 by fmsmsxvs040.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002013114472824265
 ; Thu, 31 Jan 2002 14:47:28 -0800
Received: by fmsmsx016.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <DWCL6X1V>; Thu, 31 Jan 2002 14:47:57 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D500DDF6584@FMSMSX37>
From: "Zhang, Yuyong" <yuyong@trillium.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
Cc: megaco@ietf.org
Date: Thu, 31 Jan 2002 14:47:54 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1AAA9.51E98D20"
Subject: [Megaco] How the ServiceState of TermStateDescriptor in MediaDescriptor is
 used?
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

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1AAA9.51E98D20
Content-Type: text/plain;
	charset="ISO-8859-1"

G'day, Tom, All
 
I am not very clear how the ServiceState in TermStateDescriptor is used.
 
If a MGC sends this ServiceState to MG, what the "Test", "Out of Service",
or "In Service" state means to a MG, what is the MG's behavior in receiving
such state? I just don't know in what situation, a MGC will sends this
ServiceState to MG.
 
If a MG wants to send termination state to the MGC, then the ServiceChange
with ServiceChangeDescriptor will do.
 
The only way I see the ServiceState to be used is when MG replys an AUDIT on
MediaDescriptor, MG sends the termination state on this.
 
Any thoughts on this?
 
Regards,
 
Yuyong

------_=_NextPart_001_01C1AAA9.51E98D20
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>RE: [Megaco] QRY about the failed command</TITLE>

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>G'day, 
Tom, All</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>I am 
not very clear how the ServiceState in TermStateDescriptor is 
used.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>If a 
MGC sends this ServiceState to MG, what the "Test", "Out of Service", or "In 
Service" state means to a MG, what is the MG's behavior in receiving such state? 
I just don't know in what situation, a MGC will sends this ServiceState to 
MG.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>If a 
MG wants to send termination state to the MGC, then the ServiceChange with 
ServiceChangeDescriptor will do.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>The 
only way I see the ServiceState to be used is when MG replys an AUDIT on 
MediaDescriptor, MG sends the termination state on this.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=512133922-31012002>Any 
thoughts on this?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002>Regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=512133922-31012002>Yuyong</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C1AAA9.51E98D20--

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



From megaco-admin@ietf.org  Thu Jan 31 21:29:40 2002
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 VAA17844
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 21:29:40 -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 VAA07535;
	Thu, 31 Jan 2002 21:21:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07506
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 21:21:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17728
	for <megaco@ietf.org>; Thu, 31 Jan 2002 21:21:31 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA00809;
	Fri, 1 Feb 2002 13:20:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.239.111])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA07177;
	Fri, 1 Feb 2002 13:21:21 +1100 (EST)
Message-ID: <3C59DA73.2BD28758@ericsson.com.au>
Date: Fri, 01 Feb 2002 10:59:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: knayar@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <65256B52.002E9A75.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Kapil,

Please see my answers below.

Regards, Christian

knayar@hss.hns.com wrote:
> 
> Hi Christian
> 
> Sorry for the delayed reply.
> My comments are embedded...
> Thanks,
> -Kapil
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/30/2002 08:51:46 AM
> 
> To:   Tom-PT Taylor <taylor@nortelnetworks.com>
> cc:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  Re: [Megaco] Query about streamID 0
> 
> G'Day
> 
> My understanding of the combinations are the following:
> 
> event (no stream) - detect an event on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> detection equipment. ie. DTMF detector on the audio stream/s.
> event (stream ID 0) - as above
> [KN] - Does that mean stream ID 0 refers to ANY stream or just the
> APPROPRIATE stream(s)...like DTMF detector on the audio stream(s).
> If it is the later, it means that packages (events) are defined
> for streams and not just terminations ?

[CHG] The appropriate stream could be any of the streams. Packages are
on the termination by virtue that there properties, streams, event,
statistics are used by the various descriptors on the termination.

> 
> event (stream ID x) - detect the event only on the particular streamID x
> [KN] - This is OK!
> 
> signal (no stream) - play the signal on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> playout equipment. Play a video on the video stream.
> signal (stream ID 0) - as above
> [KN] - Does that mean stream ID 0 refers to ALL streams or just the
> APPROPRIATE stream(s)...like video on the video stream(s).
> If it is the later, it means that packages (signals) are defined
> for streams and not just terminations ?

[CHG] See above

> 
> signal (stream ID x) - the signal only on the particular streamID x
> [KN] - This is OK!
> 
> Default streamID=1 if you leave the stream descriptor as just specify
> local and remote.
> [KN] - Isn't it similar to saying that stream 0 is a default stream
> (a Null stream) which is not explicitly created thru' media desc but
> may be referred in other descriptors like..event, signals etc.

[CHG] YEs I guess so.

> 
> Now this is all rather acedemic if the termination only ever has one
> stream.
> 
> I can't see the problem. What am I missing?
> 
> Regards, Christian
> 
> Tom-PT Taylor wrote:
> >
> > Your proposal that the default streamId (0) means "all active streams" is a
> > workable one for events, especially if the actual stream on which the signal
> > occurred is reported in the Notify.  I suspect signals are a bit more
> > problematic -- you only want a signal to go out on one stream, usually.
> >
> > I'm still troubled by the implications of assuming that you can't detect
> > events on a stream not specifically defined at a given termination.  I'm
> > mainly worried about the NULL context.  The simplest way around that concern
> > is to assume that the media properties of physical terminations are
> > pre-provisioned.  In fact, people must be making that asumption now --
> > otherwise there would have been a lot more interest in my draft on SDP
> > attributes for TDM.  I intend to revive that draft shortly, by the way.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Monday, January 28, 2002 8:36 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > My comments embedded.....
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > You've opened up a good discussion.
> >
> > 1. You are right about streams also being bound to terminations.  Aside from
> > being able to define streams when the termination is in the NULL context, we
> > have the provision that a termination retains its current streams when it is
> > moved from one context to another.
> >
> > 2. I differ slightly on the interpretation of streams versus actual enabling
> > of flows, but this is at an abstract level that I don't think makes any
> > difference in behaviour.  My interpretation is that as soon as a stream is
> > created in a context, it introduces the potential of bi-directional exchange
> > of media between the context and each termination in it.  Of course, to have
> > an actual flow in each direction, you need the conditions you've stated:
> > Local and Remote defined on at least two terminations and sendRecv set on
> > both.
> >
> > The real issue is whether a termination can detect events and send signals
> > on a stream not explicitly defined at that termination.  I think this is a
> > matter of convention -- we have to decide one way or the other.  I'll point
> > out that it has implications for detection of DTMF events in the NULL
> > context.
> > <KN> I feel as per the convention and to some extent simple logic it
> > would be appropriate to allow terminations to detect events and signals
> > on only those streams which are explicitly defined on them. More so, because
> > in cases where there are multiple streams on multiple terminations
> > Eg:
> > A context with 4 terminations T1, T2, T3....
> > Streams 1 and 2 on T1,3 and 2 on T3.
> > T2 has currently no explicit stream defined on it.
> >
> >           -------------------
> >           |              |
> >      T1----------1         -------T2
> >           |  |            |
> >           |  |--2_       |
> >           |      |       |
> >           |      |       |
> >           |      |       |
> >           |      |    3--------T3
> >           |      |       | |
> >           |       |____2--| |
> >           |              |
> >           -------------------
> > It would be questionable to expect the following combinations:
> > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > -    T1 detect events or apply signals on stream 3.
> > -    T3 detect events or apply signals on stream 1.
> > At the current moment these terminations are completely oblivious of the
> > stream IDs refered.
> >
> > 3. I think I've made the point that H.248v1 requires that most of the events
> > and signals we have already defined must be applied to a non-zero stream.
> > Hence requiring that packages indicate which ones apply to stream 0 is not a
> > change in the protocol, just a clarification.
> >
> > I do have a couple of alternatives which indeed would be changes to the
> > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> >
> >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > event or signal, or
> >  (b) If only one stream is defined on the specific termination, an
> > unspecified streamId selects that stream.
> > <KN> I have an opinion.....How does MGC tell MG to detect events
> > on all active streams on a termination. Does MGC have to repeat event IDs
> > in the event descriptor with all active stream IDs as parameters. Protocol
> > does not introduce any concept of stream ID as "*"(ALL).
> > >From the current text, the stream ID 0 seems to be solving this problem.
> > Stream ID 0 is the default stream on all terminations,i.e., does not need to
> > be created explicitly through media descriptor (valid).
> > If event descriptor contains stream ID 0, "it does not refer to any specific
> > stream"(valid) but does refer to the termination as a whole.
> > The inference is that detect events on all streams (currently active on
> > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > nonstream-specific terminations like NAS). If the event is detected on any
> > stream, report the same to MGC with the specific stream ID.
> > A similar interpretation can also be made for signals.
> > And, the default stream ID remains 0 for events/ signals, but 1 for
> > media descriptor.
> >
> > Actually, I think people are going to have to bite the bullet and start
> > specifying streamIds eventually if they don't do it now.  Choosing
> > alternative (b) would buy a bit of time.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Thursday, January 24, 2002 5:49 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > I would like to add more to your comments about streams being context
> > properties.
> >
> > Streams are as good properties of the terminations too....
> > -    A stream can be created on a termination in the Null Context.
> >      (almost in all call flows including those in the RFC 3015 stream
> > descriptor
> >      or the default stream 1 is sent by the MGC in MODIFY command in the
> >      Null context).
> > -    To create a bi-directional stream, we need to send stream descriptor
> >      with (at the least mode=sendrecv) for both the terminations in the
> > context.
> >      The bi-directional stream cannot be created by just refering it in one
> >      termination.
> >
> > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > stream=1 (something similar to a unidirectional media flow) by specifying
> > stream descriptor for termination T1. At this point it would be incorrect
> > to assume that termination T2 can detect events or apply signals on the
> > stream
> > 1.
> > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > totally
> > oblivious of stream 1).
> > To detect events or signals on the stream at T2, we need to first make T2
> > aware
> > of the stream.
> >
> > Although, it would be a good idea to specify in package definitions about
> > which event/ signals etc. would apply on streamID=0, this would amount to
> > changing
> > the protocol....are you considering it for version2.
> >
> > Please comment....
> >
> > Thanks & Regards,
> > -Kapil Nayar
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.  See new comments [PTT2] below.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Wednesday, January 23, 2002 8:55 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > my comments embedded.
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> >
> > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > cc:
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Tuesday, January 22, 2002 8:54 AM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Query about streamID 0
> >
> > Hi Tom & list,
> >
> > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
> >
> > "The default streamID is 0, indicating that the event to be detected is not
> > related to a particular media stream."
> >
> > Does the "streamID 0" refer to the complete termination (which means all the
> > active streams on the termination) ?
> >
> > [PTT] No.  It really means as it says, that the event or signal is not
> > associated with any specific stream.  An example is an electrical signal
> > such as off-hook.
> > [KN] Does that mean that stream 0 is possible for only physical
> > terminations,
> > since electrical signals are more appropriate for physical terminations.
> > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > relate to specific streams.  Electrical signals were just an example.  I
> > suspect I could find a good example in one of my NAS packages of something
> > more abstract, but I won't take the time.  Just accept that we don't want to
> > foreclose the possibility of using this on ephemerals.
> >
> > And, if some event is required to be detected on the ephemeral termination,
> > the event descriptor should clearly identify which stream it is required on.
> > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > without
> > stream ID parameter since that defaults to stream ID 0, which may not be
> > applicable).
> > [PTT2] That has to be thought through for all terminations.
> > *** IG issue: It does strike me that you can know in advance (by definition
> > of the event or signal) whether streamId=0 will apply.  We should therefore
> > make it requirement to specify this in package definitions.
> >
> > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > associated with an audio stream.  (But I bet nobody has bothered to specify
> > stream 1 for DTMF events when they are using a default streamId for audio.
> > They should!)
> > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > descriptor,
> > MGC should have already created the stream 1 thru' the media descriptor
> > in a previous command?
> > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > descriptor, but just specify Local, Remote, and LocalControl.
> > *** IG issue: would it make more sense to have streamId=0 as the default for
> > signals and events, or have streamId=1 as the default?
> >
> > A related doubt is...if an event descriptor refers
> > to a stream ID which is not previously created by the MGC, MG should
> > return an error.
> > [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> > If a given streamId is supported somewhere in the context, then referring to
> > that streamId at a given termination implies that the termination also
> > supports it.  That means it could detect events or send signals on the
> > stream even if it doesn't know how to handle the media flows on that stream.
> > I suppose if this is the first mention of the streamId in the context, it
> > might be appropriate to reject the command.
> > ***IG issue: The implication is that within any command, Stream Descriptors
> > for new streams MUST appear before Signals and Events descriptors referring
> > to those StreamIds.
> >
> > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > descriptor, event descriptor, signal descriptor ?
> >
> > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > consistent with the meaning of that streamId for events and signals.  We
> > should have a note to the effect that streamId=0 is reserved in sections
> > 7.1.4 (for thoroughness) and 7.1.6.
> >
> > You can specify streamId=0 in a signals or events descriptor, but that's the
> > same as leaving it unspecified.
> >
> > Please reply back...
> >
> > Thanks,
> > Kapil Nayar
> >
> > "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> > (HSS) and is intended solely for the use of the individual  to whom it is
> > addressed. It may contain  privileged or confidential information  and
> > should
> > not be circulated or used for any purpose other than for what it is
> > intended.If
> > you have received this message in error, please notify the originator
> > immediately. If you are not the intended recipient, you are notified that
> > you
> > are strictly prohibited from using, copying, altering, or disclosing the
> > contents of this message. HSS accepts no responsibility for loss or damage
> > arising from the use of the information transimitted by this email including
> > damage from virus."
> >
> > _______________________________________________
> > 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


From daemon@ns.ietf.org  Thu Jan 31 22:17:06 2002
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 VAA17853
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 21:29:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA07760
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 21:29:44 -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 VAA07535;
	Thu, 31 Jan 2002 21:21:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07506
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 21:21:37 -0500 (EST)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17728
	for <megaco@ietf.org>; Thu, 31 Jan 2002 21:21:31 -0500 (EST)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id NAA00809;
	Fri, 1 Feb 2002 13:20:01 +1100 (EST)
Received: from ericsson.com.au ([146.11.239.111])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id NAA07177;
	Fri, 1 Feb 2002 13:21:21 +1100 (EST)
Message-ID: <3C59DA73.2BD28758@ericsson.com.au>
Date: Fri, 01 Feb 2002 10:59:47 +1100
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: knayar@hss.hns.com
CC: Tom-PT Taylor <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Query about streamID 0
References: <65256B52.002E9A75.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit

Hello Kapil,

Please see my answers below.

Regards, Christian

knayar@hss.hns.com wrote:
> 
> Hi Christian
> 
> Sorry for the delayed reply.
> My comments are embedded...
> Thanks,
> -Kapil
> 
> Christian Groves <Christian.Groves@ericsson.com.au> on 01/30/2002 08:51:46 AM
> 
> To:   Tom-PT Taylor <taylor@nortelnetworks.com>
> cc:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> 
> Subject:  Re: [Megaco] Query about streamID 0
> 
> G'Day
> 
> My understanding of the combinations are the following:
> 
> event (no stream) - detect an event on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> detection equipment. ie. DTMF detector on the audio stream/s.
> event (stream ID 0) - as above
> [KN] - Does that mean stream ID 0 refers to ANY stream or just the
> APPROPRIATE stream(s)...like DTMF detector on the audio stream(s).
> If it is the later, it means that packages (events) are defined
> for streams and not just terminations ?

[CHG] The appropriate stream could be any of the streams. Packages are
on the termination by virtue that there properties, streams, event,
statistics are used by the various descriptors on the termination.

> 
> event (stream ID x) - detect the event only on the particular streamID x
> [KN] - This is OK!
> 
> signal (no stream) - play the signal on the termination irrespective of
> what streams are on the termination. The MG will insert the correct
> playout equipment. Play a video on the video stream.
> signal (stream ID 0) - as above
> [KN] - Does that mean stream ID 0 refers to ALL streams or just the
> APPROPRIATE stream(s)...like video on the video stream(s).
> If it is the later, it means that packages (signals) are defined
> for streams and not just terminations ?

[CHG] See above

> 
> signal (stream ID x) - the signal only on the particular streamID x
> [KN] - This is OK!
> 
> Default streamID=1 if you leave the stream descriptor as just specify
> local and remote.
> [KN] - Isn't it similar to saying that stream 0 is a default stream
> (a Null stream) which is not explicitly created thru' media desc but
> may be referred in other descriptors like..event, signals etc.

[CHG] YEs I guess so.

> 
> Now this is all rather acedemic if the termination only ever has one
> stream.
> 
> I can't see the problem. What am I missing?
> 
> Regards, Christian
> 
> Tom-PT Taylor wrote:
> >
> > Your proposal that the default streamId (0) means "all active streams" is a
> > workable one for events, especially if the actual stream on which the signal
> > occurred is reported in the Notify.  I suspect signals are a bit more
> > problematic -- you only want a signal to go out on one stream, usually.
> >
> > I'm still troubled by the implications of assuming that you can't detect
> > events on a stream not specifically defined at a given termination.  I'm
> > mainly worried about the NULL context.  The simplest way around that concern
> > is to assume that the media properties of physical terminations are
> > pre-provisioned.  In fact, people must be making that asumption now --
> > otherwise there would have been a lot more interest in my draft on SDP
> > attributes for TDM.  I intend to revive that draft shortly, by the way.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Monday, January 28, 2002 8:36 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > My comments embedded.....
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/24/2002 09:07:47 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > You've opened up a good discussion.
> >
> > 1. You are right about streams also being bound to terminations.  Aside from
> > being able to define streams when the termination is in the NULL context, we
> > have the provision that a termination retains its current streams when it is
> > moved from one context to another.
> >
> > 2. I differ slightly on the interpretation of streams versus actual enabling
> > of flows, but this is at an abstract level that I don't think makes any
> > difference in behaviour.  My interpretation is that as soon as a stream is
> > created in a context, it introduces the potential of bi-directional exchange
> > of media between the context and each termination in it.  Of course, to have
> > an actual flow in each direction, you need the conditions you've stated:
> > Local and Remote defined on at least two terminations and sendRecv set on
> > both.
> >
> > The real issue is whether a termination can detect events and send signals
> > on a stream not explicitly defined at that termination.  I think this is a
> > matter of convention -- we have to decide one way or the other.  I'll point
> > out that it has implications for detection of DTMF events in the NULL
> > context.
> > <KN> I feel as per the convention and to some extent simple logic it
> > would be appropriate to allow terminations to detect events and signals
> > on only those streams which are explicitly defined on them. More so, because
> > in cases where there are multiple streams on multiple terminations
> > Eg:
> > A context with 4 terminations T1, T2, T3....
> > Streams 1 and 2 on T1,3 and 2 on T3.
> > T2 has currently no explicit stream defined on it.
> >
> >           -------------------
> >           |              |
> >      T1----------1         -------T2
> >           |  |            |
> >           |  |--2_       |
> >           |      |       |
> >           |      |       |
> >           |      |       |
> >           |      |    3--------T3
> >           |      |       | |
> >           |       |____2--| |
> >           |              |
> >           -------------------
> > It would be questionable to expect the following combinations:
> > -    T2 detect events or apply signals on stream 1 or 2 or 3.
> > -    T1 detect events or apply signals on stream 3.
> > -    T3 detect events or apply signals on stream 1.
> > At the current moment these terminations are completely oblivious of the
> > stream IDs refered.
> >
> > 3. I think I've made the point that H.248v1 requires that most of the events
> > and signals we have already defined must be applied to a non-zero stream.
> > Hence requiring that packages indicate which ones apply to stream 0 is not a
> > change in the protocol, just a clarification.
> >
> > I do have a couple of alternatives which indeed would be changes to the
> > protocol.  PEOPLE SHOULD SPEAK UP ON THIS QUICKLY.
> >
> >  (a) Default streamId is 1 rather than 0 if streamId is unspecified for an
> > event or signal, or
> >  (b) If only one stream is defined on the specific termination, an
> > unspecified streamId selects that stream.
> > <KN> I have an opinion.....How does MGC tell MG to detect events
> > on all active streams on a termination. Does MGC have to repeat event IDs
> > in the event descriptor with all active stream IDs as parameters. Protocol
> > does not introduce any concept of stream ID as "*"(ALL).
> > >From the current text, the stream ID 0 seems to be solving this problem.
> > Stream ID 0 is the default stream on all terminations,i.e., does not need to
> > be created explicitly through media descriptor (valid).
> > If event descriptor contains stream ID 0, "it does not refer to any specific
> > stream"(valid) but does refer to the termination as a whole.
> > The inference is that detect events on all streams (currently active on
> > stream-specific terminations like RTP/ TDMC or stream ID 0 on
> > nonstream-specific terminations like NAS). If the event is detected on any
> > stream, report the same to MGC with the specific stream ID.
> > A similar interpretation can also be made for signals.
> > And, the default stream ID remains 0 for events/ signals, but 1 for
> > media descriptor.
> >
> > Actually, I think people are going to have to bite the bullet and start
> > specifying streamIds eventually if they don't do it now.  Choosing
> > alternative (b) would buy a bit of time.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Thursday, January 24, 2002 5:49 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > I would like to add more to your comments about streams being context
> > properties.
> >
> > Streams are as good properties of the terminations too....
> > -    A stream can be created on a termination in the Null Context.
> >      (almost in all call flows including those in the RFC 3015 stream
> > descriptor
> >      or the default stream 1 is sent by the MGC in MODIFY command in the
> >      Null context).
> > -    To create a bi-directional stream, we need to send stream descriptor
> >      with (at the least mode=sendrecv) for both the terminations in the
> > context.
> >      The bi-directional stream cannot be created by just refering it in one
> >      termination.
> >
> > Assuming there are terminations T1 and T2 in a context. Now, MGC creates a
> > stream=1 (something similar to a unidirectional media flow) by specifying
> > stream descriptor for termination T1. At this point it would be incorrect
> > to assume that termination T2 can detect events or apply signals on the
> > stream
> > 1.
> > (T2 is neither a source nor a sink for stream 1 at this point, i.e., it is
> > totally
> > oblivious of stream 1).
> > To detect events or signals on the stream at T2, we need to first make T2
> > aware
> > of the stream.
> >
> > Although, it would be a good idea to specify in package definitions about
> > which event/ signals etc. would apply on streamID=0, this would amount to
> > changing
> > the protocol....are you considering it for version2.
> >
> > Please comment....
> >
> > Thanks & Regards,
> > -Kapil Nayar
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/23/2002 08:00:37 PM
> >
> > To:   Kapil Nayar/HSS@HSS
> > cc:   "'megaco@ietf.org'" <megaco@ietf.org>
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.  See new comments [PTT2] below.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Wednesday, January 23, 2002 8:55 AM
> > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] Query about streamID 0
> >
> > Hi Tom
> >
> > my comments embedded.
> >
> > "Tom-PT Taylor" <taylor@nortelnetworks.com> on 01/22/2002 11:35:00 PM
> >
> > To:   Kapil Nayar/HSS@HSS, "'megaco@ietf.org'" <megaco@ietf.org>
> > cc:
> >
> > Subject:  RE: [Megaco] Query about streamID 0
> >
> > Hi.
> >
> > -----Original Message-----
> > From: knayar@hss.hns.com [mailto:knayar@hss.hns.com]
> > Sent: Tuesday, January 22, 2002 8:54 AM
> > To: 'megaco@ietf.org'
> > Subject: [Megaco] Query about streamID 0
> >
> > Hi Tom & list,
> >
> > RFC 3015 Section 7.1.9 Event Descriptor & 7.1.11 Signal Descriptor mentions:
> >
> > "The default streamID is 0, indicating that the event to be detected is not
> > related to a particular media stream."
> >
> > Does the "streamID 0" refer to the complete termination (which means all the
> > active streams on the termination) ?
> >
> > [PTT] No.  It really means as it says, that the event or signal is not
> > associated with any specific stream.  An example is an electrical signal
> > such as off-hook.
> > [KN] Does that mean that stream 0 is possible for only physical
> > terminations,
> > since electrical signals are more appropriate for physical terminations.
> > [PTT2] There can be applications of streamId 0 on ephemerals which don't
> > relate to specific streams.  Electrical signals were just an example.  I
> > suspect I could find a good example in one of my NAS packages of something
> > more abstract, but I won't take the time.  Just accept that we don't want to
> > foreclose the possibility of using this on ephemerals.
> >
> > And, if some event is required to be detected on the ephemeral termination,
> > the event descriptor should clearly identify which stream it is required on.
> > (i.e., MGC cannot send an events descriptor for ephemeral termination
> > without
> > stream ID parameter since that defaults to stream ID 0, which may not be
> > applicable).
> > [PTT2] That has to be thought through for all terminations.
> > *** IG issue: It does strike me that you can know in advance (by definition
> > of the event or signal) whether streamId=0 will apply.  We should therefore
> > make it requirement to specify this in package definitions.
> >
> > [PTT] On the other hand, an audio signal such as a DTMF tone is
> > associated with an audio stream.  (But I bet nobody has bothered to specify
> > stream 1 for DTMF events when they are using a default streamId for audio.
> > They should!)
> > [KN] Does that mean that before sending DTMFdet (dd/<?>) in events
> > descriptor,
> > MGC should have already created the stream 1 thru' the media descriptor
> > in a previous command?
> > [PTT2] StreamId=1 is the default stream created if you don't use a stream
> > descriptor, but just specify Local, Remote, and LocalControl.
> > *** IG issue: would it make more sense to have streamId=0 as the default for
> > signals and events, or have streamId=1 as the default?
> >
> > A related doubt is...if an event descriptor refers
> > to a stream ID which is not previously created by the MGC, MG should
> > return an error.
> > [PTT2] I'm not sure.  Remember that streamIds are really a context property.
> > If a given streamId is supported somewhere in the context, then referring to
> > that streamId at a given termination implies that the termination also
> > supports it.  That means it could detect events or send signals on the
> > stream even if it doesn't know how to handle the media flows on that stream.
> > I suppose if this is the first mention of the streamId in the context, it
> > might be appropriate to reject the command.
> > ***IG issue: The implication is that within any command, Stream Descriptors
> > for new streams MUST appear before Signals and Events descriptors referring
> > to those StreamIds.
> >
> > Can MGC send streamID value 0 in a MEGACO command/ descriptor. eg: media
> > descriptor, event descriptor, signal descriptor ?
> >
> > [PTT] Logically, you cannot use streamId = 0 in a media descriptor and be
> > consistent with the meaning of that streamId for events and signals.  We
> > should have a note to the effect that streamId=0 is reserved in sections
> > 7.1.4 (for thoroughness) and 7.1.6.
> >
> > You can specify streamId=0 in a signals or events descriptor, but that's the
> > same as leaving it unspecified.
> >
> > Please reply back...
> >
> > Thanks,
> > Kapil Nayar
> >
> > "DISCLAIMER: This message is proprietary to Hughes Software Systmes Limited
> > (HSS) and is intended solely for the use of the individual  to whom it is
> > addressed. It may contain  privileged or confidential information  and
> > should
> > not be circulated or used for any purpose other than for what it is
> > intended.If
> > you have received this message in error, please notify the originator
> > immediately. If you are not the intended recipient, you are notified that
> > you
> > are strictly prohibited from using, copying, altering, or disclosing the
> > contents of this message. HSS accepts no responsibility for loss or damage
> > arising from the use of the information transimitted by this email including
> > damage from virus."
> >
> > _______________________________________________
> > 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



From megaco-admin@ietf.org  Thu Jan 31 22:52:49 2002
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 WAA20933
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 22:52:45 -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 WAA10963;
	Thu, 31 Jan 2002 22:45:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA10934
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 22:45:29 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20858
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:45:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g113it526192
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:44:55 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g113ir520999
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:44:53 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAWB4H>; Thu, 31 Jan 2002 22:44:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF66@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Zhang, Yuyong'" <yuyong@trillium.com>
Cc: megaco@ietf.org
Date: Thu, 31 Jan 2002 22:44:54 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: How the ServiceState of TermStateDescriptor in MediaDescripto
 r is used?
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

One possibility is that the termination is one of a group, such that when
the MGC send down a request for an outgoing trunk, the MG chooses an
available member of that group (e.g. Add=groupname/${...).  Then setting a
particular trunk to out of service state ensures that the MG won't choose
it.

-----Original Message-----
From: Zhang, Yuyong [mailto:yuyong@trillium.com]
Sent: Thursday, January 31, 2002 5:48 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: How the ServiceState of TermStateDescriptor in MediaDescriptor is
used?


G'day, Tom, All
 
I am not very clear how the ServiceState in TermStateDescriptor is used.
 
If a MGC sends this ServiceState to MG, what the "Test", "Out of Service",
or "In Service" state means to a MG, what is the MG's behavior in receiving
such state? I just don't know in what situation, a MGC will sends this
ServiceState to MG.
 
If a MG wants to send termination state to the MGC, then the ServiceChange
with ServiceChangeDescriptor will do.
 
The only way I see the ServiceState to be used is when MG replys an AUDIT on
MediaDescriptor, MG sends the termination state on this.
 
Any thoughts on this?
 
Regards,
 
Yuyong


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


From daemon@ns.ietf.org  Thu Jan 31 22:52:50 2002
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 WAA20944
	for <megaco-archive@odin.ietf.org>; Thu, 31 Jan 2002 22:52:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA11155
	for megaco-archive@odin.ietf.org; Thu, 31 Jan 2002 22:52:54 -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 WAA10963;
	Thu, 31 Jan 2002 22:45:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA10934
	for <megaco@ns.ietf.org>; Thu, 31 Jan 2002 22:45:29 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20858
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:45:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g113it526192
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:44:55 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g113ir520999
	for <megaco@ietf.org>; Thu, 31 Jan 2002 22:44:53 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <D8QAWB4H>; Thu, 31 Jan 2002 22:44:54 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102AF66@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Zhang, Yuyong'" <yuyong@trillium.com>
Cc: megaco@ietf.org
Date: Thu, 31 Jan 2002 22:44:54 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: How the ServiceState of TermStateDescriptor in MediaDescripto
 r is used?
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

One possibility is that the termination is one of a group, such that when
the MGC send down a request for an outgoing trunk, the MG chooses an
available member of that group (e.g. Add=groupname/${...).  Then setting a
particular trunk to out of service state ensures that the MG won't choose
it.

-----Original Message-----
From: Zhang, Yuyong [mailto:yuyong@trillium.com]
Sent: Thursday, January 31, 2002 5:48 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: How the ServiceState of TermStateDescriptor in MediaDescriptor is
used?


G'day, Tom, All
 
I am not very clear how the ServiceState in TermStateDescriptor is used.
 
If a MGC sends this ServiceState to MG, what the "Test", "Out of Service",
or "In Service" state means to a MG, what is the MG's behavior in receiving
such state? I just don't know in what situation, a MGC will sends this
ServiceState to MG.
 
If a MG wants to send termination state to the MGC, then the ServiceChange
with ServiceChangeDescriptor will do.
 
The only way I see the ServiceState to be used is when MG replys an AUDIT on
MediaDescriptor, MG sends the termination state on this.
 
Any thoughts on this?
 
Regards,
 
Yuyong


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



